Specifications
52
Release Notes for Cisco IOS Release 12.0 S
78-7130-11 Rev. B0
Caveats
• CSCdr64558
If a redundant power supply on a Cisco 12012 Gigabit Switch Router (GSR) is disabled and later
reenabled, the GSR might report alarms that relate to fan speed. There is no workaround.
• CSCdr68063
A Cisco 12000 series Gigabit Switch Router (GSR) may reload if more than 1500 Multiprotocol
Label Switching (MPLS) tunnels are configured. There is no workaround.
• CSCdr71218
A Cisco 12000 series Gigabit Switch Router (GSR) experiences an interprocess communication
(IPC) timeout when 400 ATM subinterfaces are configured for tag switching and Intermediate
System-to-Intermediate System (IS-IS) and a microcode reload is performed on the ATM line card.
A microcode reload should not be performed on the ATM line card in this configuration scheme.
There is no workaround.
• CSCdr75832
A Cisco 12000 series Gigabit Switch Router (GSR) may lose Intermediate System-to-Intermediate
System (IS-IS) messages because of a queue overflow if 400 ATM subinterfaces are configured for
tag switching and IS-IS. Tag switching should only be enabled on less than 400 subinterfaces.
There is no workaround.
• CSCdr77321
On a Cisco 12000 series Gigabit Switch Router (GSR), an extended access control list (ACL) that
denies IP traffic from being sent to a range of IP addresses might deny MPLS-tagged outbound
traffic on a 3-port Gigabit Ethernet line card port under the following conditions:
–
MPLS is enabled on the router.
–
An extended ACL is defined that denies IP traffic from being sent to a range of IP addresses
(for example, access-list 100 deny ip any 3.1.0.0 0.0.255.255).
–
That extended ACL is applied to inbound traffic on a port of a 3-port Gigabit Ethernet line card
(for example, interface GigabitEthernet6/0 and ip access-group 100 in would deny inbound
IP traffic with a destination address of 3.1.x.x).
–
That same ACL is applied to outbound traffic on a port of a different 3-port Gigabit Ethernet
line card in the same router, but MPLS is enabled on that port (for example, interface
GigabitEthernet1/0, ip access-group 100 out, and tag-switching ip).
–
The same ACL is then removed from the inbound port (for example, interface
GigabitEthernet6/0 and ip access-group 100 in).
This situation occurs even though an extended ACL should not affect outbound Multiprotocol
Label Switching (MPLS) traffic. For the given example, the result is that although the ACL is no
longer applied to the inbound port, outbound traffic with a destination address of 3.1.x.x is blocked
even though MPLS tags are being applied to it.
Workaround: Remove and then reapply the ACL to the outbound port. For example, enter the
following global configuration commands:
configure {terminal} interface GigabitEthernet1/0 no ip access-group 100 out exit exit
configure {terminal} interface GigabitEthernet1/0 ip access-group 100 out exit exit
After these commands are entered, MPLS-tagged outbound traffic will flow normally.
• CSCdr77367
Multiprotocol Label Switching (MPLS) Traffic Engineering tunnels may fail temporarily if a link
along the path from the tunnel head end to the tail end fails. This situation occurs even if there are
alternate paths from the tunnel head end to the tail end with sufficient resources to support the