- 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);
- }
- }
- [edit forwarding-options dhcp-relay],
- [edit forwarding-options dhcp-relay group group-name],
- [edit logical-systems logical-system-name forwarding-options dhcp-relay],
- [edit logical-systems logical-system-name forwarding-options dhcp-relay group group-name],
- [edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options dhcp-relay],
- [edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options
dhcp-relay group group-name],
- [edit routing-instances routing-instance-name forwarding-options dhcp-relay],
- [edit routing-instances routing-instance-name forwarding-options dhcp-relay group group-name]
Statement introduced in JUNOS Release 9.0.
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, or to drop selected DHCP client packets. This feature is useful in network environments where DHCP clients access services provided by multiple vendors and DHCP servers.
You can use the relay-option-60 statement and its subordinate statements at the [edit forwarding-options dhcp-relay] hierarchy level to configure option 60 support globally, or at the [edit forwarding-options dhcp-relay group group-name] hierarchy level to configure option 60 support for a named group of interfaces. You can also configure option 60 support for the extended DHCP relay agent on a per logical system and per routing instance basis.
The statements are explained separately.
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.