Using Nonmatching Option 60 Strings to Process DHCP Client Traffic

If the option 60 string received in the DHCP client packet does not match the configured ASCII or hexadecimal string, you can specify the default action that the DHCP relay agent uses for the associated DHCP client packets.

In rare instances, the extended DHCP relay agent might receive a DHCP client packet with an option 60 string of zero (0) length. In this case, there is nothing in the option 60 string against which to match. As a result, such packets are treated as if they contained nonmatching option 60 strings; that is, they can be relayed to a default DHCP relay server, forwarded to a default DHCP extended local server, or dropped.

• To relay client traffic to a default extended DHCP relay server that you specify:
  [edit forwarding-options dhcp-relay relay-option-60 vendor-option]user@host# set default-relay-server-group relayServer16
• To forward client traffic to a default extended DHCP local server that you specify:
  [edit forwarding-options dhcp-relay relay-option-60 vendor-option]user@host# set default-local-server-group localServer25
• To drop (discard) the nonmatching packets:
  [edit forwarding-options dhcp-relay relay-option-60 vendor-option]user@host# set drop

Related Topics

• Example: Using Option 60 Strings to Forward DHCP Client Traffic
• Example: Using Option 60 Strings to Drop DHCP Client Traffic