Cisco Cisco Fiber IGESM Switch Module for IBM Release Notes
7
Release Notes for the Cisco Systems Intelligent Gigabit Ethernet Switch Modules for the IBM BladeCenter
43W7806
Limitations and Restrictions
•
Internal loopback in half-duplex mode causes input errors. We recommend that you configure the
PHY to operate in full duplex before setting the internal loopback. (CSCds20365)
PHY to operate in full duplex before setting the internal loopback. (CSCds20365)
•
A source-based distribution port group does not share the broadcast with all the group members.
When the destination of the packets is a broadcast, or an unknown unicast, or a multicast, the packets
are forwarded on only one port member of a port group, not being shared among all members of the
port group. (CSCdt24814)
When the destination of the packets is a broadcast, or an unknown unicast, or a multicast, the packets
are forwarded on only one port member of a port group, not being shared among all members of the
port group. (CSCdt24814)
•
When you enter the show controllers ethernet-controller interface-id or show interfaces
interface-id counters privileged EXEC command and a large number of erroneous frames are
received on an interface, the receive-error counts might be smaller than the actual values, and the
receive-unicast frame count might be larger than the actual frame count. (CSCdt27223)
interface-id counters privileged EXEC command and a large number of erroneous frames are
received on an interface, the receive-error counts might be smaller than the actual values, and the
receive-unicast frame count might be larger than the actual frame count. (CSCdt27223)
•
Two problems occur when a switch is in transparent mode:
–
If the switch is a leaf switch, any new VLANs added to it are not propagated upstream through
VTP messages. As a result, the switch does not receive flooded traffic for that VLAN.
VTP messages. As a result, the switch does not receive flooded traffic for that VLAN.
–
If the switch is connected to two VTP servers, it forwards their pruning messages. If the switch
has a port on a VLAN that is not requested by other servers through their pruning messages, it
does not receive flooded traffic for that VLAN.
has a port on a VLAN that is not requested by other servers through their pruning messages, it
does not receive flooded traffic for that VLAN.
There is no workaround. (CSCdt48011)
•
The receive count output for the show controllers ethernet-controller interface-id privileged
EXEC command shows the incoming packets count before the ASIC either drops or allows the
packet or not. Therefore, for ports in the STP blocking states, even though the receive count shows
incoming frames, the packet is not forwarded to the other port. (CSCdu83640)
EXEC command shows the incoming packets count before the ASIC either drops or allows the
packet or not. Therefore, for ports in the STP blocking states, even though the receive count shows
incoming frames, the packet is not forwarded to the other port. (CSCdu83640)
•
In some network topologies, when UplinkFast is enabled on all switches but BackboneFast is not
enabled on all switches, a temporary loop might occur when the STP root switch is changed.
enabled on all switches, a temporary loop might occur when the STP root switch is changed.
The workaround is to enable BackboneFast on all switches. (CSCdv02941)
•
At times, the Window XP pop-up window might not appear while authenticating a client
(supplicant) because the user information is already stored in Windows XP. However, the Extensible
Authentication Protocol over LAN (EAPOL) response to the switch (authenticator) might have an
empty user ID that causes the IEEE 802.1x port to be unauthenticated.
(supplicant) because the user information is already stored in Windows XP. However, the Extensible
Authentication Protocol over LAN (EAPOL) response to the switch (authenticator) might have an
empty user ID that causes the IEEE 802.1x port to be unauthenticated.
The workaround is to manually re-initiate authentication by either logging off or by detaching the
link and then reconnecting it. (CSCdv19671)
link and then reconnecting it. (CSCdv19671)
•
If two switches are connected and access ports connect two VLANs whose VLAN IDs are separated
by the correct multiple of 64, the two switches might use the same bridge ID in the same
spanning-tree instances. This might cause a loss of connectivity in the VLANs as the spanning tree
blocks the ports that should be forwarding.
by the correct multiple of 64, the two switches might use the same bridge ID in the same
spanning-tree instances. This might cause a loss of connectivity in the VLANs as the spanning tree
blocks the ports that should be forwarding.
The workaround is to not cross-connect VLANs. For example, do not use an access port to connect
VLAN 1 to VLAN 65 on either the same switch or from one switch to another switch.
(CSCdv27247)
VLAN 1 to VLAN 65 on either the same switch or from one switch to another switch.
(CSCdv27247)
•
You can configure up to 256 multicast VLAN registration (MVR) groups by using the mvr vlan
group interface configuration command, but only 255 groups are supported on a switch at one time.
If you statically add a 256th group, and 255 groups are already configured, the switch continues
trying (and failing) to add the new group.
group interface configuration command, but only 255 groups are supported on a switch at one time.
If you statically add a 256th group, and 255 groups are already configured, the switch continues
trying (and failing) to add the new group.
The workaround is to set the mode to dynamic for switches that are connected to IGMP-capable devices.
The new group can join the multicast stream if another stream is dynamically removed from the group.
(CSCdv45190)
The new group can join the multicast stream if another stream is dynamically removed from the group.
(CSCdv45190)