Примечания к выпуску для Cisco Cisco Fiber IGESM Switch Module for IBM

Скачать
Страница из 28
 
10
Release Notes for the Cisco Systems Intelligent Gigabit Ethernet Switch Modules for the IBM BladeCenter
43W7806
Limitations and Restrictions
When you connect a switch to another switch through a trunk port and the number of VLANs on the 
first switch is lower than the number on the connected switch, interface errors are received on the 
management VLAN of the first switch.
The workaround is to match the configured VLANs on each side of the trunk port. (CSCea23138)
When you enable Port Fast on a static-access port and then change the port to dynamic, Port Fast 
remains enabled. However, if you change the port back to static, Port Fast is disabled. 
The workaround is to configure Port Fast globally by using the spanning-tree portfast global 
configuration command. (CSCea24969)
When using the SPAN feature, the monitoring port receives copies of sent and received traffic for 
all monitored ports. If the monitoring port is oversubscribed, it will probably become congested. 
This might also affect how one or more of the monitored ports forwards traffic.
If there is not a good distribution of MAC addresses on a port channel, the switch might drop packets 
even though the port-channel has not reached 100 percent utilization.
The workaround is to use a different load balancing method (for example, use destination-based 
forwarding instead of source-based forwarding). (CSCeb75386)
If the switch has learned over 4000 MAC addresses, the clear mac address-table dynamic user 
EXEC command does not clear all of the addresses from the MAC address table. 
The workaround is to repeatedly enter the clear mac address-table dynamic user EXEC command 
until the address table is cleared. (CSCec02055)
Port security is not supported on the internal 100 Mbps management module ports (ports 15 and 16). 
Preventing port security on these ports prevents the blocking of communication between the 
management module and the switch. (CSCec10814)
After a topology change in STP, some server or workstations connected to the management VLAN 
can transfer data because the affected switch ports start forwarding before they move to the 
forwarding state.
Note
If the terminal does not belong to management VLAN, this failure does not occur.
The workaround is to place the ports in static-access mode for a single VLAN if the topology 
supports this configuration. (CSCec13986)
The output of the show flowcontrol user EXEC command incorrectly shows that the switch is not 
receiving and sending pause frames. 
The workaround is to use the show controllers ethernet-controller privileged EXEC command to 
display the sent and received pause packets for a specific port. (CSCec74979)
If the internal 100 Mbps management module ports (ports 15 and 16) and the external 10/100/1000 
ports (ports 17 to 20) are members of a VLAN or multiple VLANs, the spanning-tree states 
incorrectly show that a Layer 2 loop has occurred. In reality, there is no STP loop. (CSCed03370)
The Ethernet ports on the management module have a fixed static trunk configuration. This 
configuration cannot be changed. IP phones should not be connected to these management module 
ports. (CSCed11638)