Cisco Gigabit Ethernet Switch Module for HP BladeSystem p-Class Release Notes, Cisco IOS Release 12.2(25)SEE1 and later

15
Cisco Gigabit Ethernet Switch Module for HP BladeSystem p-Class Release Notes, Cisco IOS Release 12.2(25)SEE1 and later
459516-002
Open Caveats
CSCsd85770
When you apply the mls qos trust dscp global configuration command to a port, this error message
might appear.
Master sets trust failed, sets to untrust modetrust type update
failed on ifc GigabitEthernetx/x
Switch(config-if)#Tcam write failed trust dscp
%QOSMGR-4-COMMAND_FAILURE: Execution of slave:HQM_IDBTRUST_CMD
command failed on GigabitEthernetx/x
The workaround is to apply the sdm prefer qos global configuration command before you enter the
mls qos trust dscp global configuration command.
CSCsd86177
When you remove and reconfigure a loopback interface, it does not appear in the ifTable.
The workaround is to reload the switch.
CSCse03859
If the switch is in VTP server mode and VLANs with IDs greater than 255 (256 and above) are
created, DHCP snooping does not work properly on these VLANs.
The workaround is to put the switch in VTP transparent mode before creating the VLANs.
CSCse14774
If a switch is connected to a third-party router through an EtherChannel and the EtherChannel is
running in Link Aggregation Control Protocol (LACP) mode, the interfaces in the EtherChannel
might go down after you enter the switchport trunk native vlan vlan-id interface configuration
command to change the native VLAN from VLAN 1 (the default) to a different VLAN ID.
These are the workarounds. You only need to do one of these:
Do not change the native VLAN ID from the default setting of VLAN 1.
If you need to change the native VLAN ID to a VLAN other than VLAN 1, do not run the
EtherChannel in LACP mode, and change the mode to On by using the channel-group
channel-group-number mode on interface configuration command.
CSCsc26726
Sometimes interfaces Gi0/23 & Gi0/24 will not link up with another switch when the interface speed
is set to an explicit value instead of autonegotiated. This does not happen when a copper SFP is used
with interfaces Gi0/17 - Gi0/20.
The workaround is to autonegotiate the speed with the other device, or to use a different cable type.
Use a straight through cable for switch to switch connection, or a cross-over cable for switch to any
non switch device connection. If the other device is capable of auto MDIX even with speed not set
to auto, then use that. When an improper cable is used only one side of the connection needs to use
auto MDIX to achieve a link.