If you run the CLI-based setup program, the IP address that the Dynamic Host Configuration
Protocol (DCHP) 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 DCHP 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)

Disable auto-QoS on the interface.

Change the routed port to a nonrouted port or the reverse.

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)