Cisco Cisco IOS Software Release 12.2(53)SE

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)

When connected to some third-party devices that send early preambles, a switch port operating at 
100 Mp/s full duplex or 100 Mp/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 Mp/s and half duplex or to connect a hub or a 
nonaffected device to the switch. (CSCed39091)

The DHCP snooping binding database is not written to flash memory or a remote file in any of these 
situations: 

The DHCP snooping database file is manually removed from the file system. After enabling the 
DHCP snooping database by configuring a database URL, a database file is created. If the file 
is manually removed from the file 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 
was not accessible. The new URL might not take effect after the timeout of the old URL.

No workaround is necessary. (CSCed50819)

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

The workaround is to enter the no switchport block unicast interface configuration command on 
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)

When you enter the boot host retry timeout global configuration command to specify the amount 
of time that the client should keep trying to download the configuration and you do not enter a 
timeout value, the default value is zero, which should mean that the client keeps trying indefinitely. 
However, the client does not keep trying to download the configuration.

The workaround is to always enter a non zero value for the timeout value when you enter the boot 
host retry timeout timeout-value command. (CSCsk65142)