Release Notes for Cisco Catalyst Blade Switch 3120 for HP Cisco IOS Release 12.2(40)EX

20
Release Notes for Cisco Catalyst Blade Switch 3120 for HP, Cisco IOS Release 12.2(40)EX1
OL-12250-01
Open Caveats
• CSCsi65551
In certain situations during master switch failover, a VLAN that has been error disabled on a port
might be re-enabled after the master switch failover, even though the port has not been configured
for automatic recovery.
There is no workaround.
• CSCsi67680 platforms
When unicast routing is disabled and then re-enabled, virtual routing and forwarding (VRF) routing
is disabled on the switch interfaces.
The workaround is to enter the shut and no shut interface configuration commands on the affected
interfaces.
• CSCsi70454
The configuration file used for the configuration replacement feature requires the character string
end\n at the end of the file. The Windows Notepad text editor does not add the end\n string, and the
configuration rollback does not work.
These are the workarounds. (You only need to do one of these.)
– Do not use a configuration file that is stored by or edited with Windows Notepad.
– Manually add the character string end\n to the end of the file.
The workaround is to configure routed IPv4 multicast and IPv6 unicast traffic in different switch
ports.
• CSCsi73653
After a stack-master failover, switch ports in the stack cannot detect new devices. This only affects
new devices connected to the switch ports. Devices that were connected to active ports before the
failover remain in a trusted state.
There is no workaround.
• CSCsj10198
When a per-port per-VLAN policy map (a hierarchical VLAN-based policy map) is attached to a
VLAN interface, and you remove the child-policy policer from the policy map and then add it back,
the policy map fails to re-attach to the same SVI.
The workaround is to delete the child policy, which removes it from the parent policy. Then recreate
the child policy (with the same or a different name), and reference it in the parent policy. The parent
policy then successfully attaches to the SVI.
• CSCsj22678
A delay can occur when you remove an access control list (ACL) from a switch stack under these
conditions:
– A QoS, per-port policy map is attached to a large number of SVIs in the stack.
– A per-VLAN QoS, per-port policer policy map is attached to a large number of switched virtual
interfaces (SVIs) in the stack.
– The ACL to be removed is being used by the policy map.
– There are three or more switches in the stack.