Cisco Cisco IOS Software Release 12.0 S
2319
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Resolved Caveats—Cisco IOS Release 12.0(16)S
•
CSCdt29214
A Cisco 12000 series Internet router that is running the gsr-p-mz.120-12.S2.1227 image and has a
line card that is configured with an extremely long access control list (ACL) may experience a line
card reload during a reload or a change of the ACL. There is no workaround.
line card that is configured with an extremely long access control list (ACL) may experience a line
card reload during a reload or a change of the ACL. There is no workaround.
•
CSCdt30100
A line card may reload on a Cisco 12000 series Internet router that is running Cisco IOS
Release 12.0(13)S. There is no workaround.
Release 12.0(13)S. There is no workaround.
•
CSCdt31092
A Cisco 7507 router may reload after the access-list compiled global configuration command is
entered. There is no workaround.
entered. There is no workaround.
•
CSCdt31256
A secondary console will not be accessible in a dual-Route Processor (RP) system. There is no
workaround.
workaround.
•
CSCdt31521
A Multiprotocol Label Switching (MPLS) router with a large number of Border Gateway Protocol
(BGP) routes (VPNv4 or IPv4) may experience a memory leak if the route to the BGP neighbor
flaps. The memory leak is approximately 100 bytes per BGP route for each route flap. The leak can
be detected by unusually large memory consumption by Tag Forwarding Information Base (TFIB)
tag rewrites as seen in the output of the show memory [summary] | include TFIB command. There
is no workaround.
(BGP) routes (VPNv4 or IPv4) may experience a memory leak if the route to the BGP neighbor
flaps. The memory leak is approximately 100 bytes per BGP route for each route flap. The leak can
be detected by unusually large memory consumption by Tag Forwarding Information Base (TFIB)
tag rewrites as seen in the output of the show memory [summary] | include TFIB command. There
is no workaround.
•
CSCdt32774
The line cards on a Cisco 12000 series Internet router that is running Cisco IOS Release
12.0(14.6)S1 and that has Multiprotocol Label Switching (MPLS) enabled may reload under certain
conditions. In this situation, when one line card with an interface configured with MPLS is reloaded
manually, other line cards may experience the following bus error:
12.0(14.6)S1 and that has Multiprotocol Label Switching (MPLS) enabled may reload under certain
conditions. In this situation, when one line card with an interface configured with MPLS is reloaded
manually, other line cards may experience the following bus error:
%LCINFO-3-CRASH: Line card in slot 0 crashed
This situation has been observed where there is double recursion (for example, a Border Gateway
Protocol [BGP] recursive route over a static recursive route).
Protocol [BGP] recursive route over a static recursive route).
Workaround: Avoid the use of static recursive routes to BGP peers.
•
CSCdt34120
A Cisco 12000 series Internet router that is running the gsr-p-mz.120-15.S.bin image may
experience a situation where interface counters are reporting incorrect values. In this situation, the
interface rates are sometimes showing rates greater than the link maximum rate, and Simple
Network Management Protocol (SNMP) polls are also reporting incorrect values. This condition has
been observed with 4-Port OC-3 Packet-over-SONET (POS) Engine 0 line cards and 4-Port OC-3
ATM Engine 0 line cards. There is no workaround.
experience a situation where interface counters are reporting incorrect values. In this situation, the
interface rates are sometimes showing rates greater than the link maximum rate, and Simple
Network Management Protocol (SNMP) polls are also reporting incorrect values. This condition has
been observed with 4-Port OC-3 Packet-over-SONET (POS) Engine 0 line cards and 4-Port OC-3
ATM Engine 0 line cards. There is no workaround.
•
CSCdt36418
This situation occurs with a very specific type of service policy. The policy must have priority
enabled in the first class, and the kbps assigned to the priority class must be exactly equal to the
interface or PVC rate. In such cases, this policy should be denied as an invalid policy. Instead, the
policy is accepted, and if subsequent classes try to allocate bandwidth by entering the bandwidth
interface configuration command, the Route Switch Processor (RSP) reloads. Attaching a policy of
this type should be avoided. There is no workaround.
enabled in the first class, and the kbps assigned to the priority class must be exactly equal to the
interface or PVC rate. In such cases, this policy should be denied as an invalid policy. Instead, the
policy is accepted, and if subsequent classes try to allocate bandwidth by entering the bandwidth
interface configuration command, the Route Switch Processor (RSP) reloads. Attaching a policy of
this type should be avoided. There is no workaround.