Configuration notes for DHCP clients

  • Is this section to be deprecated (removed from FI 08.0.61)?
    When using DHCP on a router, if you have a DHCP address for one interface, and you want to connect to the DHCP server from another interface, you must disable DHCP on the first interface, and then enable DHCP on the second interface.
  • At bootup, if the router already has a static IP address, the DHCP client is disabled after initial discovery. In this scenario, if the user tries to enable the DHCP client on another interface, the DHCP client is not enabled. This behavior is similar if the device has a dynamic IP address as well. This is to avoid any update of image or configuration on the running device.
  • When DHCP is disabled, and then re-enabled, or if the system is rebooted, the TFTP process requires approximately three minutes to run in the background before file images can be downloaded manually.
  • Once a port is assigned a leased IP address, it is bound by the terms of the lease regardless of the link state of the port.

DHCP support for 802.1BR-enabled devices

DHCP is supported on 802.1BR-enabled devices as a normal stacking device, with the exception that the client is not supported on Port Extender (PE) devices running a router image, as the DHCP client is not supported on VE interfaces.