Specifications
1132
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(28)S2
Conditions: This symptom is observed on a Cisco 12410 that is configured with two Performance
Route Processors (PRP-1) that function in Route Processor Redundancy (RPR) mode and that runs
one of the following images:
–
The c12kprp-p-mz image of Cisco IOS Release 12.0(24)S3.
–
The c12kprp-p-mz image of Cisco IOS Release 12.0(23)S4.
–
The c12kprp-k3p-mz image of Cisco IOS Release 12.0(27)S2
This list is not all-inclusive: the symptom may also occur in Release 12.0(20)S, Release 12.0(20)ST,
and later releases.
The symptom occurs when the do command is interleaved between configuration commands.
Workaround: Verify that the configuration command is properly accepted by entering the show
running-config command.
• CSCef33670
Symptoms: An Engine 4 egress line card that switches traffic may reset when the ingress line card
is shut down.
Conditions: This symptom is observed on a Cisco 12000 series when the ingress line card is an
Engine 3 POS line card and when IP-to-tag traffic is switched.
Workaround: There is no workaround.
• CSCef39284
Symptoms: A router may crash when you enter the crypto key generate dss key-name command.
Conditions: This symptom is observed on a Cisco 12012 that is configured for SSH but may occur
on any Cisco platform that is configured for SSH.
Workaround: There is no workaround.
• CSCef40001
Symptoms: When the police cir percent command is configured as a service-policy input on an
MFR or MLP bundle CFI, the maximum bandwidth that is allocated by the service policy is a T1 link
bandwidth.
Conditions: This symptom is observed on a Cisco router that runs Cisco IOS Release 12.0(28)S or
an interim release for Release 12.0(30)S when a police-policy input is applied on the bundle CFI
over a 1-port OC-12 channelized ISE line card. Note, however, that this caveat is resolved in
Release 12.0(30)S.
Workaround: There is no workaround.
• CSCef44242
Symptoms: Policing parameters may not be applied correctly, causing traffic to be dropper.
Conditions: This symptom is observed when you apply ingress policies to a multilink interface.
To verify if the parameters are applied correctly, enter the show policy-map interface
interface-name. The CIR (in bps) shows whether or not the parameter was applied.
Workaround: Remove the service policy and reapply it to the multilink interface.
• CSCef45609
Symptoms: An Engine 3 Quad OC-12 line card that is configured with multicast VPNs may punt
traffic to the RP when multicast is disabled by entering the no ip multicast-routing distributed
command and then re-enabled by entering the ip multicast-routing distributed command.