Cisco Cisco Fiber IGESM Switch Module for IBM Release Notes

Page of 28
 
12
Release Notes for the Cisco Systems Intelligent Gigabit Ethernet Switch Modules for the IBM BladeCenter
43W7806
Limitations and Restrictions
Using the spanning-tree bpduguard enable interface configuration command on the internal 
management module ports (ports 15 and 16) might change the port state to error -disabled. Because 
the switch does not allow the administrative state on the management module ports to be changed 
through the CLI, HTTP, or SNMP, the internal management module port remains in the 
error-disabled state. An entry in the system message log is added.
This problem only occurs when there are two switches in the BladeCenter chassis. The first switch 
sends out the BPDU packet on its interface, and it is received by the second switch being monitored. 
If there are no other switches present in the chassis, the interface does not go into error-disabled 
state. 
The workaround is to reboot the switch after disabling BPDU guard on the switch or on the internal 
management module ports. Make sure that the saved configuration for the switch does not have 
BPDU guard enabled. (CSCee27729)
When a PC is attached to a switch through a hub, is authenticated on an IEEE 802.1x multiple-hosts 
port, is moved to another port, and is then attached through another hub, the switch does not 
authenticate the PC.
The workaround is to decrease the number of seconds between re-authentication attempts by 
entering the dot1x timeout reauth-period seconds interface configuration command. 
(CSCeg41561)
The bootloader on a switch can take a long time to load the IOS image (longer than 40 seconds), 
even when there is a valid image pointed to by the bootloader.
There is no workaround. (CSCeh01976)
IP connectivity and VLAN access to a switch are lost under these conditions:
The switch is restored to the factory defaults.
The switch is reloaded. 
A saved configuration file that has the VTP domain name set to something other than null is 
transferred to the switch using TFTP.
These are the workarounds. You only need to do one of these
After resetting the factory defaults on the switch, edit the switch configuration file and change 
the VTP domain name so that it matches the VTP name in the saved configuration file you are 
going to TFTP onto the switch.
Before using TFTP to transfer the saved configuration file onto the switch, use a text editor to 
remove the VTP domain name in the saved configuration file. After you transfer the file and 
reload the switch, edit the configuration file and change the VTP domain name back to the 
desired name.
If you are starting from a switch that is set to the factory defaults, transfer the configuration file 
with TFTP and reload the switch. Connect to the switch through the console port and reload the 
switch again. 
Instead of transferring the configuration file by TFTP, use a text editor to open the configuration 
file on the switch and copy and paste in the new configuration file. (CSC54813)
When the switch is fast aging MAC addresses or learning MAC addresses at an extremely high rate, 
frames are lost for about one or two seconds when the switch is updating the MAC address table. A 
Topology Change Notification can contribute to the occurrence of this symptom.
The workaround to reduce unnecessary Topology Change Notifications is to use the spanning-tree 
portfast [trunk] interface configuration command to configure Port Fast on all switch ports in the 
entire VLAN that are connected to end-stations. (CSCei63842)