Cisco Cisco Fiber IGESM Switch Module for IBM Release Notes

Page of 28
 
8
Release Notes for the Cisco Systems Intelligent Gigabit Ethernet Switch Modules for the IBM BladeCenter
43W7806
Limitations and Restrictions
The ip http authentication enable global configuration command is not saved to the configuration 
file. Therefore, this configuration is lost after a reboot.
The workaround is to manually enter the command again after a reboot. (CSCdv67047)
If a port is configured as a secure port with the violation mode as restrict, the secure ports might 
process packets even after the maximum number of MAC addresses is reached, but those packets are 
not forwarded to other ports. (CSCdw02638)
If the STP root port changes on the switch, the connections between the switch and the internal 
100 Mbps management module ports (ports 15 and 16) do not immediately change to the forwarding 
state. They remain in the listening state for a few seconds, during which time any traffic between the 
switch and management module is lost. This occurs if all of these conditions exist:
The switch is in IEEE 802.1w rapid STP (RSTP) mode.
An EtherChannel is configured between the switch external ports and any directly connected 
switches.
The STP root port is part of the EtherChannel group. 
There is no workaround. (CSCed89186)
You can apply ACLs to a management VLAN or to any traffic that is going directly to the CPU, such 
as SNMP, Telnet, or web traffic. For information on creating ACLs for these interfaces, see the 
“Configuring IP Services” section of the Cisco IOS IP and IP Routing Configuration Guide for 
Cisco IOS Release 12.1 
and the Cisco IOS IP and IP Routing Command Reference for Cisco IOS 
Release 12.1
.
The SSH feature uses a large amount of switch memory, which limits the number of VLANs, trunk 
ports, and cluster members that you can configure on the switch. Before you download the 
cryptographic software image, your switch configuration must meet these conditions:
The number of trunk ports multiplied by the number of VLANs on the switch must be less than 
or equal to 128. These are examples of switch configurations that meet this condition:
If the switch has 2 trunk ports, it can have up to 64 VLANs.
If the switch has 32 VLANs, it can have up to 4 trunk ports.
If your switch has a saved configuration that does not meet these conditions and you upgrade the 
switch software to the cryptographic software image, the switch might run out of memory. If this 
happens, the switch does not operate properly. For example, it might continuously reload.
If the switch runs out of memory, this message appears:
%SYS-2-MALLOCFAIL: Memory allocation of (number_of_bytes) bytes failed ...
The workaround is to check your switch configuration and to ensure that it meets the previous 
conditions. (CSCdw66805)
When you use the policy-map global configuration command to create a policy map and do not 
specify any action for a class map, the association between that class map and policy map is not 
saved when you exit policy-map configuration mode.
The workaround is to specify an action in the policy map. (CSCdx75308)