Cisco Cisco IOS Software Release 12.2(54)SE
21
Release Notes for the Catalyst 3750 Metro Switch Cisco IOS Release 12.2(54)SE
OL-22236-01
Important Notes
VLAN
•
If the number of VLANs times the number of trunk ports exceeds 13,000, the switch can stop.
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
•
A CPUHOG message sometimes appears when you configure a private VLAN. Enable port security
on one or more of the ports affected by the private VLAN configuration.
on one or more of the ports affected by the private VLAN configuration.
There is no workaround. (CSCed71422)
•
When you apply a per-VLAN QoS per-port policer policy-map to a VLAN SVI, the second-level
(child) policy-map in use cannot be re-used by another policy-map.
(child) policy-map in use cannot be re-used by another policy-map.
The workaround is to define another policy-map name for the second-level policy-map with the
same configuration to be used for another policy-map. (CSCef47377)
same configuration to be used for another policy-map. (CSCef47377)
Important Notes
•
Cisco IOS Release 12.2(50)SE introduced the virtual circuit (VC) auto-sense signaling feature for
hierarchical virtual private LAN service (H-VPLS), the xconnect of the SVI, to interoperate with the
ASR 9000 Series routers. The default signaling for H-VPLS is now VC type 5. The local
Catalyst 3750 Metro PE switch boots up signaling for VC type 5. If the remote provider-edge switch
also supports type 5, H-VPLS comes up with type 5. If the remote switch supports only VC type 4,
the local PE switch resets and renegotiates for VC type 4, and the H-VPLS comes up with type 4.
H-VPLS comes up whether the remote PE supports VC type 4 or VC type 5. Before Cisco IOS
Release 12.2(50)SE, H-VPLS would not come up unless the remote provider edge device also
supported VC type 4.
hierarchical virtual private LAN service (H-VPLS), the xconnect of the SVI, to interoperate with the
ASR 9000 Series routers. The default signaling for H-VPLS is now VC type 5. The local
Catalyst 3750 Metro PE switch boots up signaling for VC type 5. If the remote provider-edge switch
also supports type 5, H-VPLS comes up with type 5. If the remote switch supports only VC type 4,
the local PE switch resets and renegotiates for VC type 4, and the H-VPLS comes up with type 4.
H-VPLS comes up whether the remote PE supports VC type 4 or VC type 5. Before Cisco IOS
Release 12.2(50)SE, H-VPLS would not come up unless the remote provider edge device also
supported VC type 4.
By definition, the local PE H-VPLS VLAN should not be relevant for the VPLS network. Because
the local PE SVI with the xconnect and the remote PE SVI with the xconnect do not need to be on
the same VLAN, it does not matter if the VLAN is carried across the transport network or not.
However, problems could occur if a service provider deployed the Catalyst 3750M switch using the
H-VPLS VLAN as the customer VLAN when H-VPLS came up with VC type 5 because the
customer VLAN tag would not be consistent across the transport. The new behavior is now
consistent with the Cisco default.
the local PE SVI with the xconnect and the remote PE SVI with the xconnect do not need to be on
the same VLAN, it does not matter if the VLAN is carried across the transport network or not.
However, problems could occur if a service provider deployed the Catalyst 3750M switch using the
H-VPLS VLAN as the customer VLAN when H-VPLS came up with VC type 5 because the
customer VLAN tag would not be consistent across the transport. The new behavior is now
consistent with the Cisco default.
•
Cisco IOS Release 12.2(40)SE and later:
If the switch has interfaces with automatic QoS for voice over IP (VoIP) configured and you upgrade
the switch software to Cisco IOS Release 12.2(40)SE (or later), when you enter the auto qos voip
cisco-phone interface configuration command on another interface, you might see this message:
the switch software to Cisco IOS Release 12.2(40)SE (or later), when you enter the auto qos voip
cisco-phone interface configuration command on another interface, you might see this message:
AutoQoS Error: ciscophone input service policy was not properly applied
policy map AutoQoS-Police-CiscoPhone not configured
If this happens, enter the no auto qos voip cisco-phone interface command on all interface with this
configuration to delete it. Then enter the auto qos voip cisco-phone command on each of these
interfaces to reapply the configuration.
configuration to delete it. Then enter the auto qos voip cisco-phone command on each of these
interfaces to reapply the configuration.
•
The behavior of the no logging on global configuration command changed in Cisco IOS
Release 12.2(25)EY and later. In software releases earlier than Cisco IOS Release 12.2(25)EY, both
of these command pairs disabled logging to the console:
Release 12.2(25)EY and later. In software releases earlier than Cisco IOS Release 12.2(25)EY, both
of these command pairs disabled logging to the console:
–
the no logging on and then the no logging console global configuration commands
–
the logging on and then the no logging console global configuration commands