Configuring self-defined DHCP options
CAUTION: Be cautious when configuring self-defined DHCP options because such configuration may affect the DHCP operation process. | ||
By configuring self-defined DHCP options, you can
Define new DHCP options. New configuration options will come out with DHCP development. To support these new options, you can add them into the attribute list of the DHCP server.
Define existing DHCP options. Vendors use Option 43 to define options that have no unified definitions in RFC 2132. The self-defined DHCP option enables DHCP clients to obtain vendor-specific information.
Extend existing DHCP options. When the current DHCP options cannot meet the customers' requirements (for example, you cannot use the dns-list command to configure more than eight DNS server addresses), you can configure a self-defined option for extension.
To configure a self-defined DHCP option in the DHCP address pool:
Step | Command | Remarks |
---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter DHCP address pool view. | dhcp server ip-pool pool-name [ extended ] | N/A |
3. Configure a self-defined DHCP option. | option code { ascii ascii-string | hex hex-string&<1-16> | ip-address ip-address&<1-8> } | No DHCP option is configured by default. |
Table 2: Description of common options
Option | Option name | Corresponding command | Command parameter |
---|---|---|---|
3 | Router Option | gateway-list | ip-address |
6 | Domain Name Server Option | dns-list | ip-address |
15 | Domain Name | domain-name | ascii |
44 | NetBIOS over TCP/IP Name Server Option | nbns-list | ip-address |
46 | NetBIOS over TCP/IP Node Type Option | netbios-type | hex |
66 | TFTP server name | tftp-server | ascii |
67 | Bootfile name | bootfile-name | ascii |
43 | Vendor Specific Information | N/A | hex |