[Contents] [Prev] [Next] [Index] [Report an Error]

Using Option 60 Information to Forward Client Traffic to Specific DHCP Servers

You can configure the extended DHCP relay agent to use the DHCP vendor class identifier option (option 60) in DHCP client packets to forward client traffic to specific DHCP servers. This feature is useful in network environments where DHCP clients access services provided by multiple vendors and DHCP servers. For example, a DHCP client might gain Internet access from a particular DHCP server provided by one vendor, and access IPTV service from a different DHCP server provided by another vendor. The option 60 string enables vendors to include vendor-specific information in DHCP client packets.

To use option 60 vendor-specific information to select a DHCP server to which to forward the client packets, include the relay-option-60 statement:




relay-option-60 {



vendor-option {


(equals | starts-with) (ascii match-string | hexadecimal match-hex) {
(relay-server-group server-group-name |

local-server-group local-server-group-name |

drop);
}


(default-relay-server-group server-group-name |

default-local-server-group local-server-group-name |

drop);
}


}

To configure option 60 support globally, include the relay-option-60 statement and subordinate statements at the [edit forwarding-options dhcp-relay] hierarchy level. To configure option 60 support for a named group of interfaces, include the relay-option-60 statement and subordinate statements at the [edit forwarding-options dhcp-relay group group-name] hierarchy level. You can also configure option 60 support for the extended DHCP relay agent on a per logical system and per routing instance basis.

[Contents] [Prev] [Next] [Index] [Report an Error]