
720
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(32)S
• CSCsb95210
Symptoms: There is no traffic or traffic forwarded to an incorrect interface based upon the DSCP
value of the IP packet.
Conditions: This symptom occurs when interfaces are deleted and added back with MQC.
Workaround: There is no workaround.
• CSCsb96092
Symptoms: When Virtual Router Redundancy Protocol (VRRP) is configured on a
Cisco 12000 series and the FIB becomes disabled, VRRP becomes active in the groups for which it
is configured and responds to ARP requests for the virtual address.
Conditions: This symptom is observed on a Cisco 12000 series when VRRP is configured and dCEF
is disabled as a consequence of a memory allocation failure in the FIB.
Workaround: There is no workaround.
• CSCsb98254
Symptoms: A router may fail when you reload a Gigabit Ethernet (GE) line card or port adapter that
has link-bundling enabled.
Conditions: This symptom is observed on a Cisco router when dot1q is configured on a GE interface
of the line card or port adapter and when MPLS is enabled on an uplink.
Workaround: There is no workaround.
• CSCsb98654
Symptoms: The MQC may not take effect after you have applied a policy to an interface of a 4-port
OC-48 POS Engine 4+ line card.
Conditions: This symptom is observed on a Cisco 12000 series that runs the gsr-p-mz image of an
interim release for Cisco IOS Release 12.0(32)S.
Workaround: Reload the line card.
• CSCsc01577
Symptoms: Source Border Gateway Protocol Policy Accounting (BGPPA) counters do not
increment.
Conditions: This symptom is observed on a Cisco 12000 series when you enter the show cef
interface type number policy-statistics command.
Workaround: There is no workaround.
• CSCsc02825
Symptoms: In Cisco IOS software that is running the Multiprotocol Label Switching (MPLS) Label
Distribution Protocol (LDP), the router could reload while trying to access a bad virtual address.
Conditions: This symptom may be observed when LDP is being used. It will not be observed with
TDP. It may happen when LDP receives a protocol message larger than 512 bytes right after
receiving several Label Mapping messages smaller than 25 bytes. This problem is likely to be
accompanied by the presence of one of the following error message:
Address Error (load or instruction fetch) exception, CPU signal 10, PC = 0xD0D0D0D
The above error message may be preceded by one of the following four error messages:
%ALIGN-1-FATAL: Corrupted program counter
pc=0xD0D0D0D, ra=0x61164128, sp=0x64879B98
%TDP-3-BAD_PIE: peer x.x.x.x; unknown pie type 0x11E
%TDP-3-UNEXPECTED_PIE: peer x.x.x.x unexpected pie type 0x0
Kommentare zu diesen Handbüchern