Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

vendor-option

date_range 20-Nov-23

Syntax

content_copy zoom_out_map
vendor-option {
    (default-relay-server-group server-group-name | default-local-server-group local-server-group-name | drop);
    (equals | starts-with) (ascii match-string | hexadecimal match-hex) {
        (drop | local-server-group local-server-group-name | relay-server-group server-group-name);
    }
}

Hierarchy Level

content_copy zoom_out_map
[edit forwarding-options dhcp-relay relay-option-60],
[edit forwarding-options dhcp-relay group group-name relay-option-60],
[edit logical-systems logical-system-name forwarding-options dhcp-relay relay-option-60],
[edit logical-systems logical-system-name forwarding-options dhcp-relay group group-name relay-option-60],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options dhcp-relay relay-option-60],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options dhcp-relay group group-name relay-option-60],
[edit routing-instances routing-instance-name forwarding-options dhcp-relay relay-option-60],
[edit routing-instances routing-instance-name forwarding-options dhcp-relay group group-name relay-option-60]

Description

Configure the match criteria when you use the DHCP vendor class identifier option (option 60) in DHCP client packets to forward client traffic to specific DHCP servers. The extended DHCP relay agent compares the option 60 vendor-specific strings received in DHCP client packets against the match criteria that you specify. If there is a match, you can define certain actions for the associated DHCP client packets.

The vendor-option statement enables you to specify either an exact, left-to-right match (with the equals statement) or a partial match (with the starts-with statement), and configure either an ASCII match string (with the ascii statement) or a hexadecimal match string (with the hexadecimal statement).

You can configure an unlimited number of match strings. Match strings do not support the use of wildcard attributes.

Options

equals—Exact, left-to-right match of the ASCII or hexadecimal match string with the option 60 string.

starts-with—Partial match of the ASCII or hexadecimal match string with the option 60 string. The option 60 string can contain a superset of the ASCII or hexadecimal match string, provided that the leftmost characters of the option 60 string entirely match the characters in the configured match string. When you use the starts-with statement, the longest match rule applies; that is, the router matches the string “test123” before it matches the string “test”.

ascii match-string—ASCII match string of 1 through 255 alphanumeric characters.

hexadecimal match-hex—Hexadecimal match string of 1 through 255 hexadecimal characters (0 through 9, a through f, A through F).

The remaining statements are explained separately. See CLI Explorer.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

Release Information

Statement introduced in JUNOS Release 9.0.

footer-navigation