DHCP Clients
In this section:
- DHCP ClientA host on an IP network can use BOOTP or DHCP to obtain its IP address from a BOOTP or DHCP server. To obtain the address, the client sends a BOOTP or DHCP request.
- BootP and DHCP relay parameters
- Configuring an IP helper addressTo forward a client broadcast request for a UDP application when the client and server are on different networks, you must configure a helper address on the interface connected to the client.
- Configuring the BOOTP and DHCP reply source addressYou can configure the device so that a BOOTP/DHCP reply to a client contains the server IP address as the source address instead of the router IP address.
- Changing the IP Address Used for Stamping
BootP and DHCP RequestsWhen a Layer 3 switch forwards a BootP or DHCP request, the Gateway Address field is "stamped".
- Changing the maximum number of hops to a BootP relay serverEach BootP or DHCP request includes a Hop Count field. The Hop Count field indicates how many routers the request has passed through.
- DHCP Auto-Provisioning
- Auto-Provisioning Using the bootfile.bin OptionYou can configure the image name with a .bin extension on the server.
- DHCP Auto-Provisioning Using the Manifest File OptionSupport for DHCP auto-provisioning using the manifest file option was introduced in FastIron 08.0.40.
- DHCP Auto-Provisioning EnhancementsAuto-provisioning allows DHCP clients to boot up with the latest flash image and configuration without manual intervention. DHCP auto-provisioning enhancements have been introduced in FastIron 08.0.80 so that you can override the default behavior. The current behavior is that the ICX device (DHCP client) is forced to download the application image type based on the current version of the device.
- Configuring DHCP Auto-Provisioning Enhancements
- DHCP auto-provisioning optionsThe following options are supported by the client for auto-provisioning.
- DHCP client behavior with Layer 3 routing imageUp until now Brocade devices supported the DHCP client IP address discovery and auto-update feature on out-of-band interfaces, physical interface ports part of default and non-default VLANs.
- Auto-deployment of Layer 3 image and monitoringThe following flowchart illustrates DHCP auto-deployment with a Layer 3 router image.
- Disabling or re-enabling the DHCP client The DHCP client is enabled by default. You can disable or re-enable DHCP client on a switch or a router.
- DHCP auto-provisioning on Layer 2 and Layer 3 devicesDHCP auto-provisioning enhancements have been introduced for Layer 2 and Layer 3 devices.
- Configuration notes for DHCP clients
- Configuration Notes and Feature Limitations for DHCP Auto-ProvisioningThe following configuration notes and feature limitations apply to DHCP auto-provisioning.
- Disabling or re-enabling auto-provisioningDHCP auto-provisioning is enabled by default. You can disable or re-enable DHCP auto-provisioning on a switch or a router.
- Dynamic DHCP options configuration processingThe system can differentiate between manually configured DHCP options and DHCP options that were obtained dynamically from the server. Manually configured DHCP options are retained even when the dynamic IP address is released.
- Discovery of SZ based on DHCP Option 43 Beginning with SmartZone release 5.0, the administrator can monitor and manage switches and routers in the ICX 7000 series switches running FastIron version 08.0.80 or above. ICX (the DHCP client) can parse the value of DHCP option 43 containing SZ IP addresses received from the DHCP server and connect to Smartzone.
- Verifying dynamic DHCP options for a switchYou can identify dynamically obtained DHCP options for a switch.
- Verifying dynamic DHCP options for a routerYou can identify dynamically obtained DHCP options for a router.