Cisco Gigabit Ethernet Switch Module for HP p-Class BladeSystem Release Notes, Cisco IOS Release 12.2(25)SED

7
Configuration
These are the configuration limitations:
• If you run the CLI-based setup program, the IP address that the Dynamic Host Configuration Protocol (DHCP)
provides is reflected as a static IP address in the config.text file. The workaround is to not run setup if DHCP
is required for your configuration.
• If you start and then end the autoinstall program before the DHCP server replies, DHCP requests are
ignored. The workaround is to wait until you see the IP address appear when it is provided by the DHCP
server.
• A static IP address might be removed when the previously acquired DHCP IP address lease expires. This
problem occurs under these conditions:
• When the switch is booted without a configuration (no config.text file in flash memory).
• When the switch is connected to a DHCP server that is configured to give an address to it (the dynamic
IP address is assigned to VLAN 1).
• When an IP address is configured on VLAN 1 before the dynamic address lease assigned to VLAN 1
expires.
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:
• 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 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.
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
Mbps full duplex or 100 Mbps 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 Mbps and half duplex or to connect a hub or a nonaffected
device to the switch. (CSCed39091)
• 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)
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)
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 Cisco Gigabit Ethernet Switch Module for HP p-Class BladeSystem Software
Configuration Guide. (CSCec76893)
IP
When the rate of received DHCP requests exceeds 2,000 packets per minute for a long time, the response time
might be slow when you are using the console. The workaround is to use rate limiting on DHCP traffic to prevent
a denial of service attack from occurring. (CSCeb59166)