Specifications

1043
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(29)S
• CSCee63825
Symptoms: When BGP receives an update with only a VPN label change, BGP may not update the
TFIB with the new label information.
Conditions: This symptom is observed when BGP receives an update with only a VPN label change
but without any nexthop changes.
When the symptom occurs, enter the clear ip route vrf vrf-name command to return to proper
operation.
Workaround: There is no workaround.
• CSCee65066
Symptoms: The CISCO-PIM-MIB trap ciscoPimInvalidJoinPrune is supposed to contain the
following varbinds:
1.3.6.1.4.1.9.9.184.1.1.4 - cpimLastErrorOriginType
1.3.6.1.4.1.9.9.184.1.1.5 - cpimLastErrorOrigin
1.3.6.1.4.1.9.9.184.1.1.6 - cpimLastErrorGroupType
1.3.6.1.4.1.9.9.184.1.1.7 - cpimLastErrorGroup
1.3.6.1.4.1.9.9.184.1.1.8 - cpimLastErrorRPType
1.3.6.1.4.1.9.9.184.1.1.9 - cpimLastErrorRP
1.3.6.1.4.1.9.9.184.1.1.2 - cpimInvalidJoinPruneMsgsRcvd
However, when the trap is sent, a wrong OID is used for the cpimInvalidJoinPruneMsgsRcvd.
From a sniffer trace, the following varbind is seen: 1.3.6.1.4.1.9.9.184.2.0.5.0. The actual value sent
is correct, though.
Similarly, another CISCO-PIM-MIB trap, ciscoPimInvalidRegister, has the wrong varbind for
cpimInvalidRegisterMsgsRcvd. However the value sent is correct in this case too.
Conditions: This symptom is platform-independent and software-independent. Note that the actual
value that is sent in the wrong OID for cpimInvalidJoinPruneMsgsRcvd or
cpimInvalidRegisterMsgsRcvd is correct. However, this situation causes confusion on the traps
receiver side because the receiver cannot decode the traps correctly.
Workaround: There is no workaround.
• CSCee67164
Symptoms: A router LSA is not generated for a loopback address.
Conditions: This symptom is observed when you assign an IP address to an unnumbered interface.
Workaround: Enter the shutdown command followed by the no shutdown command on the
loopback interface.
• CSCee67450
A Cisco device running Cisco IOS and enabled for the Border Gateway Protocol (BGP) is
vulnerable to a Denial of Service (DoS) attack from a malformed BGP packet. Only devices with
the bgp log-neighbor-changes command configured are vulnerable. The BGP protocol is not
enabled by default, and must be configured in order to accept traffic from an explicitly defined peer.
Unless the malicious traffic appears to be sourced from a configured, trusted peer, it would be
difficult to inject a malformed packet.
If a misformed packet is received and queued up on the interface, this bug may also be triggered by
other means which are not considered remotely exploitable such as the use of the show ip bgp
neighbors command or running the debug ip bgp neighbor updates command for a configured
BGP neighbor.