Cisco Cisco Gigabit Ethernet Switch Module (CGESM) for HP
8
Cisco Gigabit Ethernet Switch Module for HP BladeSystem p-Class Release Notes, Cisco IOS Release 12.2(44)SE and Later
464831-006
Limitations and Restrictions
The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)
1.
Disable auto-QoS on the interface.
2.
Change the routed port to a nonrouted port or the reverse.
3.
Re-enable auto-QoS on the interface. (CSCec44169)
•
The DHCP snooping binding database is not written to flash or a remote file in either of these
situations:
situations:
–
The DHCP snooping database file is manually removed from the file system. After you enable
the DHCP snooping database by configuring a database URL, a database file is created. If you
manually remove the file from the system, the DHCP snooping database does not create another
database file. You need to disable the DHCP snooping database and enable it again to create the
database file.
the DHCP snooping database by configuring a database URL, a database file is created. If you
manually remove the file from the system, the DHCP snooping database does not create another
database file. You need to disable the DHCP snooping database and enable it again to create the
database file.
–
The URL for the configured DHCP snooping database was replaced because the original URL
is not accessible. The new URL might not take effect after the timeout of the old URL.
is not accessible. The new URL might not take effect after the timeout of the old URL.
No workaround is necessary; these are the designed behaviors. (CSCed50819)
•
When connected to some third-party devices that send early preambles, a switch port operating at
100 Mb/s full duplex or 100 Mb/s half duplex might bounce the line protocol up and down. The
problem is observed only when the switch is receiving frames.
100 Mb/s full duplex or 100 Mb/s half duplex might bounce the line protocol up and down. The
problem is observed only when the switch is receiving frames.
The workaround is to configure the port for 10 Mb/s and half duplex or to connect a hub or a
nonaffected device to the switch. (CSCed39091)
nonaffected device to the switch. (CSCed39091)
•
When port security is enabled on an interface in restricted mode and the switchport block unicast
interface command has been entered on that interface, MAC addresses are incorrectly forwarded
when they should be blocked
interface command has been entered on that interface, MAC addresses are incorrectly forwarded
when they should be blocked
The workaround is to enter the no switchport block unicast interface configuration command on
that specific interface. (CSCee93822)
that specific interface. (CSCee93822)
•
A traceback error occurs if a crypto key is generated after an SSL client session.
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch.
(CSCef59331)
(CSCef59331)
•
When system jumbo MTU size is configured on a switch and the egress ports can support jumbo
frames, the egress SPAN jumbo frames are not forwarded to the SPAN destination ports.
frames, the egress SPAN jumbo frames are not forwarded to the SPAN destination ports.
There is no workaround. (CSCsj21718)
Ethernet
Subnetwork Access Protocol (SNAP) encapsulated IP packets are dropped without an error message being
reported at the interface. The switch does not support SNAP-encapsulated IP packets. There is no
workaround. (CSCdz89142)
reported at the interface. The switch does not support SNAP-encapsulated IP packets. There is no
workaround. (CSCdz89142)
HSRP
When the active switch fails in a switch cluster that uses HSRP redundancy, the new active switch might
not contain a full cluster member list. The workaround is to ensure that the ports on the standby cluster
members are not in the spanning-tree blocking state. To verify that these ports are not in the blocking
state, see the “Configuring STP” chapter in the software configuration guide. (CSCec76893)
not contain a full cluster member list. The workaround is to ensure that the ports on the standby cluster
members are not in the spanning-tree blocking state. To verify that these ports are not in the blocking
state, see the “Configuring STP” chapter in the software configuration guide. (CSCec76893)