Cisco Cisco IOS Software Release 12.2(52)SE

Page de 34
 
28
Release Notes for the Catalyst 3550-24-DC Multilayer Switch, Cisco IOS Release 12.2(52)SE
OL-19712-01
Open Caveats
Open Caveats
These are the Cisco IOS severity-3 open configuration caveats in this software release:
CSCdx95501
When a community string is assigned by the cluster command switch, you cannot get any 
dot1dBridge MIB objects by using a community string with a VLAN entity from a cluster member 
switch.
The workaround is to manually add the cluster community string with the VLAN entity on the 
member switches for all active VLANs shown in the show spanning-tree summary display. This 
is an example of such a change, where cluster member 3 has spanning tree on vlan 1-3, and the 
cluster commander community string is public@es3.
Mbr3(config)# snmp community public@es3@1 RO
Mbr3(config)# snmp community public@es3@2 RO
Mbr3(config)# snmp community public@es3@3 RO
CSCsz18634 
On a switch running Cisco IOS release 12.2(46)SE, the output of the show interfaces privileged 
EXEC command shows 0 packets for port channel input and output rates.
The workaround is to reload the switch by entering the reload privileged EXEC command.
CSCtc02635
On switches running Cisco IOS release 12.2(50)SE3 running MAC authentication bypass with 
multidomain authentication (MDA, IP phones connected to a port might not be able to regain 
network connectivity in the VOICE domain if the session times out and all RADIUS servers are 
unreachable.
There is no workaround.
Resolved Caveats
This release resolves these previously open caveats:
CSCsw68528
On switches running Cisco IOS Release 12.2(44)SE or 12.2(46)SE, when you enter the show mvr 
interface
 interface-id members privileged EXEC command to see status of an MVR port, an MVR 
member port that is not connected always shows as ACTIVE.
The workaround is to use the show mvr interface interface-id or the show mvr members privileged 
EXEC command. These command outputs show the correct status of an MVR port.
CSCsx78068 
If you enable 802.1Q native VLAN tagging by entering the vlan dot1q tag native global 
configuration command and then change the native VLAN ID on an ingress trunk port by entering 
the switchport trunk native vlan vlan-id interface command, untagged traffic is forwarded instead 
of being dropped. 
The workaround is to use one of these methods:
Enter a shutdown followed by a no shutdown interface configuration command on the trunk 
port.
Disable and then reenable native VLAN tagging by entering the no vlan dot1q tag native 
global configuration command followed by the vlan dot1q tag native command.