command stringlengths 2 75 | syntax stringlengths 0 289k | hierarchy_level stringlengths 0 6.91k | description stringlengths 0 45.2k | options listlengths 0 499 | required_privilege_level stringlengths 0 330k | release_information stringlengths 0 3.14k | related_documentation listlengths 0 22 |
|---|---|---|---|---|---|---|---|
destination-override | destination-override {
syslog host ip-address;
} | [edit system tracing] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "syslog",
"desc": "Specify the system process log files to send to the remote tracing host."
},
{
"name": "host ip-address",
"desc": "Specify the IP address to which to send tracing information."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Junos OS Tracing and Logging Operations"
] |
destination-path-group | destination-path-group group-name {
active-probe-properties {
active-probe-only ;
}
inline-gre-encap
overlay-path {
overlay-path-name;
}
probe-routing-instance {
routing-instance-name;
}
} | [edit security advance-policy-based-routing] | Define a group containing multiple overlay paths terminating at a same destination.
In releases prior to Junos OS release 20.2R1, AppQoE determines the applicable destination path group
and binds the application sessions to that particular destination-path-group. Based on the application’s
SLA requirements and link pr... | [
{
"name": "group-name",
"desc": "Name that identifies the destination path group."
},
{
"name": "active-probe-properties",
"desc": "Specify additional active probe property."
},
{
"name": "active-probe-only",
"desc": "Enable active probing only to the destination"
},
{
"name"... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Application Quality of Experience",
"Advanced Policy-Based Routing"
] |
destination-pool | destination-pool nat-pool-name; | [edit services nat rule rule-name term term-name then translated] | Specify the destination address pool for translated traffic. | [
{
"name": "nat-pool-name",
"desc": "Destination pool name."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Network Address Translation Rules Overview"
] |
destination-port (applications) | destination-port port-value; | [edit applications application application-name] | Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) destination port number. | [
{
"name": "port-value",
"desc": "Identifier for the port or range of ports. For a complete list of supported application"
},
{
"name": "'application application-name'",
"desc": ""
},
{
"name": "TCP Destination Port 0 Invalid",
"desc": ""
},
{
"name": "error: configuration che... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"ALG Descriptions",
"Configuring Application Sets",
"Configuring Application Properties",
"Examples: Configuring Application Protocols",
"Verifying the Output of ALG Sessions",
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
destination-port (Applications) | destination-port port-identifier; | [edit applications application application-name],
[edit applications application application-name term term-name] | Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) destination port number, which
combines with protocol to identify an application type. The Internet Assigned Numbers Authority (IANA)
assigns port numbers. See the IANA Service Name and Transport Protocol Port Number Registry at
http://www.iana.org/ass... | [
{
"name": "port-identifier",
"desc": "Range of ports. You can use a numeric value or one of the text synonyms listed in Table"
},
{
"name": "afs",
"desc": ""
},
{
"name": "bgp",
"desc": ""
},
{
"name": "biff",
"desc": ""
},
{
"name": "bootpc",
"desc": ""
},
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement modified in Junos OS Release 8.5. | [
"Security Policy Application Sets Overview"
] |
destination-port (firewall) | destination-port <destination-port>; | [edit firewall family family-name filter filter-name term term-name from ip-version ip-version
protocol (tcp | udp)] | Configure the destination port of the Layer 4 header. | [
{
"name": "destination-port",
"desc": "The destination port of the Layer 4 header. Range: 0 through 65,535"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1R1. | [
"Firewall Filter Match Conditions for MPLS-Tagged IPv4 or IPv6 Traffic"
] |
destination-port (Flow Monitoring Logs for NAT) | destination-port port-number; | [edit services jflow-log collector collector-name] | Specify the UDP port of the destination to be used in the UDP header for the generated flow
monitoring logs. This is a required setting. | [
{
"name": "port-number",
"desc": "UDP port number for the test frames."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding NAT Event Logging in Flow Monitoring Format on an MX Series Router or NFX250",
"Configuring Log Generation of NAT Events in Flow Monitoring Record Format on an MX Series",
"Router or NFX250",
"Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats",
"Exa... |
destination-port (PCP) | destination-port high maximum-value low minimum-value; | [edit services pcp rule rule-name term term-name from] | Specify the destination port range that must be matched for the PCP rule. A PCP rule assigns the PCP
server that handles selected traffic.
PCP is supported on the MS-DPC, MS-100, MS-400, and MS-500 MultiServices PICS. Starting in Junos
OS Release 17.4R1, PCP is also supported on the MS-MPC and MS-MIC. | [
{
"name": "maximum-value",
"desc": "Upper boundary for the port range."
},
{
"name": "minimum-value",
"desc": "Lower boundary for the port range."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R1. | [
"Configuring Port Control Protocol"
] |
destination-port (protocols pcep) | destination-port port-number; | [edit protocols pcep pce pce-id] | Specify the TCP port number of the Path Computation Element (PCE) to which the Path Computation
Client (PCC) should connect. | [
{
"name": "port-number",
"desc": "Destination TCP port number. Range: 1 through 65535 Default: 4189"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support for PTX Series added in Junos OS Release 14.2.
Support for QFXswitches added in Junos OS Release 16.1R3. | [] |
destination-port (RADIUS Snoop Segment) | destination-port destination-port; | [edit access radius snoop-segments segment-name] | Specify the destination port for accounting messages to snoop. | [
{
"name": "destination-port",
"desc": "Destination port of accounting messages. Default: 1813 Range: 1 through 65,535"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring Snooping of RADIUS Accounting Requests for IP-Based Subscribers",
"Snooping RADIUS Accounting Requests for IP-Based Subscribers Overview",
"IP-Based Subscriber Setup Overview"
] |
destination-port (RPM and TWAMP) | destination-port port; | [edit services monitoring rpm owner name test name] | Specify the User Datagram Protocol (UDP) or Transmission Control Protocol (TCP) port to which a probe
is sent. This statement is used only for TCP or UDP probe types.
The value for the destination-port can be only 7 when you configure the destination port along with
hardware timestamping. A constraint check prevents y... | [
{
"name": "port",
"desc": "Port number 7 or from 862 through 65,535."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.3 for EX Series switches.
Statement introduced in Junos OS Release 13.2 for PTX Series Packet Transport Routers.
Support at the [edit services rpm twamp client control-connection control-client-name] hierarchy level
introduced... | [
"Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, and MX Series",
"Routers",
"Configuring BGP Neighbor Discovery Through RPM",
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches"
] |
destination-port (Security Destination NAT) | destination-port (port-or-low <to high>); | [edit security nat destination rule-set rule-set-name rule rule-name match] | Specify a destination port or port range to match the rule. Up to eight port or port ranges are supported. | [
{
"name": "port",
"desc": "Specify a destination port number."
},
{
"name": "low",
"desc": "Specify the lower limit of the destination port range."
},
{
"name": "<to high>",
"desc": "Specify the upper limit of the destination port range."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. Statement modified in Junos OS Release 12.1X47-D10. | [] |
destination-port (Security Forwarding Options) | destination-port port-number; | [edit security forwarding-options mirror-filter filter-name] | Specify a Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) destination port
number to be matched for mirroring. You can specify a numeric value or one of the text synonyms listed
in Table 34 on page 5741.
Table 34: Ports Supported by Services Interfaces
Port Name
Corresponding Port Number
afs
bgp
b... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [] |
destination-port (Security Signature Attack) | destination-port {
match (equal | greater-than | less-than | not-equal);
value destination-port;
} | [edit security idp custom-attack attack-name attack-type signature protocol udp],
[edit security idp custom-attack attack-name attack-type signature protocol tcp] | Specify the port number of the attack target. | [
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value destination-port",
"desc": "Match the port number of the attack target."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
destination-port (Security Source NAT) | destination-port (port-or-low <to high>); | [edit security nat source rule-set rule-set-name rule rule-name match] | Specify a destination port or port range to match the rule. Up to eight port or port ranges are supported. | [
{
"name": "port",
"desc": "Specify a destination port number."
},
{
"name": "low",
"desc": "Specify the lower limit of the destination port range."
},
{
"name": "<to high>",
"desc": "Specify the upper limit of the destination port range."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. Statement modified in Junos OS Release 12.1X47-D10. | [] |
destination-port (Security Static NAT) | destination-port (port-or-low | <to high>); | [edit security nat static rule-set rule-set-name rule rule-name match] | Specify a destination port or port range to allow static NAT to map ports. | [
{
"name": "port-or-low",
"desc": "Specify the port name or the lower limit of the port range."
},
{
"name": "to high",
"desc": "Specify the upper limit of the port range."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. | [] |
destination-port (SNMP) | destination-port port-number; | [edit snmp trap-group] | Assign a trap port number other than the default.
Default
If you omit this statement, the default port is 162. | [
{
"name": "port-number",
"desc": "SNMP trap port number."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring SNMP Trap Groups"
] |
destination-port (Subscriber Secure Policy) | destination-port port-number; | [edit services radius-flow-tap policy policy-name inet drop-policy rule-name from],
[edit services radius-flow-tap policy policy-name inet6 drop-policy rule-name from] | Specify the destination IP address for the radius-flow-tap policy. | [
{
"name": "port-number",
"desc": "Number of the IPv4 or IPv6 destination port for the radius-flow-tap policy."
}
] | flow-tap—To view this statement in the configuration.
flow-tap-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Subscriber Secure Policy Overview",
"Configuring RADIUS-Initiated Subscriber Secure Policy Mirroring Overview"
] |
destination-port range | destination-port range highmaximum-value low minimum-value; | [edit services nat rule rule-name term term-name from] | Specify the destination port range for rule matching. | [
{
"name": "maximum-value",
"desc": "Upper limit of port range for matching."
},
{
"name": "minimum-value",
"desc": "Lower limit of port range for matching."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Configuring Port Forwarding for Static Destination Address Translation"
] |
destination-port-range (HTTP Header Enrichment) | destination-port-range {
high port-number low port-number;
} | [edit services hcm tag-rule rule-name term term-number from] | Specify a port range that the HTTP request destination port number must match. You can specify
multiple port ranges by including the destination-port-range statement multiple times.
After this criterion and the other match criteria specified for the term are matched, the HTTP header
enrichment actions specified for the... | [
{
"name": "high port-number",
"desc": "Upper limit of the port range."
},
{
"name": "low port-number",
"desc": "Lower limit of the port range."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview"
] |
destination-ports (HTTP Header Enrichment) | destination-ports value; | [edit services hcm tag-rule rule-name term term-number from] | Specify the HTTP request destination port number that must be matched. You can specify multiple ports
by including the destination-ports statement multiple times.
After this criterion and the other match criteria specified for the term are matched, the HTTP header
enrichment actions specified for the term are applied t... | [
{
"name": "value",
"desc": "Port number."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview"
] |
destination-prefix (Destination NAT Next Gen Services) | destination-prefix destination-prefix; | [edit services nat destination rule-set rule-set rule rule-name then destination-nat] | Specify the IPv6 prefix that is used to embed an IPv4 destination address in an IPv6 address. The
destination-prefix statement is used in Stateful NAT64 and 464XLAT translations. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [] |
destination-prefix (IDS) | destination-prefix prefix-value; | [edit services ids rule rule-name term term-name then aggregation] | Specify a prefix length for destination IPv4 address aggregation for the IDS rule. This applies session
limits to an aggregation of all attacks to a subnet of the specified length.
For example, if you configure a value of 24 for destination-prefix, then attacks to 10.1.1.2 and 10.1.1.3
are counted as attacks to the 10.... | [
{
"name": "prefix-value",
"desc": "Integer value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Actions in IDS Rules",
"Configuring Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
destination-prefix (Security Forwarding Options) | destination-prefix destination-prefix; | [edit security forwarding-options mirror-filter filter-name] | Specify the destination IP prefix or address to be matched for mirroring. | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [] |
destination-prefix (Services NAT) | destination-prefix destination-prefix; | [edit services nat rule rule-name term term-name then translated] | Specify the destination prefix for translated traffic. | [
{
"name": "destination-prefix",
"desc": "IPv4 or IPv6 destination prefix value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6.
destination-prefix option enhanced to support IPv6 addresses in Junos OS Release 8.5. | [
"Network Address Translation Rules Overview"
] |
destination-prefix-ipv6 (IDS) | destination-prefix-ipv6 prefix; | [edit services ids rule rule-name term term-name then aggregation] | Specify a prefix length for destination IPv6 address aggregation for the IDS rule. This applies session
limits to an aggregation of all attacks to a subnet of the specified length.
For example, if you configure a value of 64 for destination-prefix-ipv6, then attacks to
2001:db8:1234:72a2::2 and 2001:db8:1234:72a2::3 ar... | [
{
"name": "prefix-value",
"desc": "Integer value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring Actions in IDS Rules",
"Configuring Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
destination-prefix-list (HTTP Header Enrichment) | destination-prefix-list {
(prefix-name | prefix-name except);
} | [edit services hcm tag-rule rule-name term term-number from] | Specify the destination prefix list that the HTTP request destination IP address must match. You can
specify multiple prefix lists by including the destination-prefix-list statement multiple times.
After this criterion and the other match criteria specified for the term are matched, the HTTP header
enrichment actions ... | [
{
"name": "prefix-name",
"desc": "Name of the prefix list. NOTE: The prefix list must already be defined at the [edit policy-options prefix-list] hierarchy level."
},
{
"name": "prefix-name",
"desc": ""
},
{
"name": "except",
"desc": "Exclude addresses that are in the specified prefi... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring HTTP Header Enrichment Overview"
] |
destination-prefix-list (PCP) | destination-prefix-list list-name; | [edit services pcp rule rule-name term term-name from] | Specify the destination prefix list that must be matched for the PCP rule. You configure the prefix list by
including the prefix-list statement at the [edit policy-options] hierarchy level. A PCP rule assigns the PCP
server that handles selected traffic.
PCP is supported on the MS-DPC, MS-100, MS-400, and MS-500 MultiS... | [
{
"name": "list-name",
"desc": "Destination prefix list."
},
{
"name": "except",
"desc": "(Optional) Prevent the specified prefix list from matching the PCP rule."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R1. | [
"Configuring Port Control Protocol"
] |
destination-prefix-list (Services AACL) | destination-prefix-list list-name; | [edit services aacl rule rule-name term term-name from] | Specify the destination prefix list for rule matching. You configure the prefix list by including the prefix-
list statement at the [edit policy-options] hierarchy level. | [
{
"name": "list-name",
"desc": "Destination prefix list."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring Match Conditions in AACL Rules"
] |
destination-prefix-list (Services CoS) | destination-prefix-list list-name <except>; | [edit services cos rule rule-name term term-name from] | Specify the destination prefix list for rule matching. You configure the prefix list by including the prefix-
list statement at the [edit policy-options] hierarchy level. | [
{
"name": "list-name",
"desc": "Destination prefix list."
},
{
"name": "except",
"desc": "(Optional) Exclude the specified prefix list from rule matching."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Configuring CoS Rules",
"https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/config-",
"guide-policy/config-guide-policy.html"
] |
destination-prefix-list (Services IDS) | destination-prefix-list list-name <except>; | [edit services ids rule rule-name term term-name from] | Specify the destination prefix list for rule matching. You configure the prefix list by including the prefix-
list statement at the [edit policy-options] hierarchy level. | [
{
"name": "list-name",
"desc": "Destination prefix list."
},
{
"name": "except",
"desc": "(Optional) Exclude the specified prefix list from rule matching."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/config-",
"guide-policy/config-guide-policy.html",
"Configuring Match Conditions in IDS Rules"
] |
destination-prefix-list (Services NAT) | destination-prefix-list list-name <except>; | [edit services nat rule rule-name term term-name from] | Specify the destination prefix list for rule matching. You configure the prefix list by including the prefix-
list statement at the [edit policy-options] hierarchy level.
If the translation-type statement in the then statement of the nat rule is set to stateful-nat-64, the
destination prefix list for rule matching must... | [
{
"name": "list-name",
"desc": "Destination prefix list."
},
{
"name": "except",
"desc": "(Optional) Exclude the specified prefix list from rule matching."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Network Address Translation Rules Overview",
"https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/config-",
"guide-policy/config-guide-policy.html"
] |
destination-prefix-list (Services Stateful Firewall) | destination-prefix-list list-name <except>; | [edit services stateful-firewall rule rule-name term term-name from] | Specify the destination prefix list for rule matching. You configure the prefix list by including the prefix-
list statement at the [edit policy-options] hierarchy level. | [
{
"name": "list-name",
"desc": "Destination prefix list."
},
{
"name": "except",
"desc": "(Optional) Exclude the specified prefix list from rule matching."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Configuring Match Conditions in Stateful Firewall Rules",
"https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/config-",
"guide-policy/config-guide-policy.html"
] |
destination-profile | destination-profile name; | [edit interfaces interface-name unit logical-unit-number family inet address address],
[edit interfaces interface-name unit logical-unit-number family inet unnumbered-address
interface-name destination address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet a... | For interfaces with PPP encapsulation, assign PPP properties to the remote destination end. You define
the profile at the [edit access group-profile name ppp] hierarchy level. | [
{
"name": "name",
"desc": "Profile name defined at the [edit access group-profile name ppp] hierarchy level."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IPCP Options for Interfaces with PPP Encapsulation",
"Junos OS Administration Library for Routing Devices"
] |
destination-realm (Gx-Plus) | destination-realm realm; | [edit access gx-plus partition partition-name] | Configure the realm in which the PCRF host resides. | [
{
"name": "realm",
"desc": "Realm in which the PCRF host resides."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Gx-Plus",
"Configuring the Gx-Plus Partition"
] |
destination-realm (JSRC) | destination-realm realm | [edit jsrc partition partition-name] | Configure the realm in which the SAE host resides. | [
{
"name": "realm",
"desc": "Realm in which the SAE host resides."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"JSRC Configuration Overview",
"Configuring the JSRC Partition"
] |
destination-realm (OCS Partition) | destination-realm ocs-realm-name; | [edit access ocs partition partition-name] | Configure the Destination-Realm AVP value in all CCR-GY messages. | [
{
"name": "ocs-realm-name",
"desc": "Name of the Destination-Real AVP value to be used in all CCR-GY messages."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the OCS Partition",
"3GPP Policy and Charging Control Overview for Wireline Provisioning and Accounting",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interactions Between t... |
destination-realm (PCRF Partition) | destination-realm pcrf-realm-name; | [edit access pcrf partition partition-name] | Configure the Destination-Realm AVP value in all CCR-GX messages. | [
{
"name": "pcrf-realmname",
"desc": "Value of the Destination-Real AVP to be used in all CCR-GX messages."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the PCRF Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Interactions Between the PCRF, PCEF, and OCS",
"Understanding Upstream and Downstream Messages for the PCR... |
destination-threshold | destination-threshold number; | [edit security screen ids-option screen-name tcp syn-flood] | Specify the number of SYN segments received per second for a single destination IP address before the
device begins dropping connection requests to that destination. If a protected host runs multiple
services, you might want to set a threshold based only on the destination IP address, regardless of the
destination port... | [
{
"name": "number",
"desc": "Number of SYN segments received per second before the device begins dropping connection"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.2. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
destination-udp-port (FTI) | destination-udp-port destination-udp-port; | [edit interfaces name unit name tunnel encapsulation vxlan-gpe] | Assign a numeric value to write to the destination-udp-port-field to identify a Virtual Extensible LAN
(VXLAN). The range is 1 through 65,535. | [] | routing | Statement introduced in Junos OS Release 18.3R1. | [
"Flexible Tunnel Interfaces Overview",
"Configuring Flexible Tunnel Interfaces",
"Example: Configuring Flexible Tunnel Interfaces on MX Series Routers"
] |
destination-udp-port | destination-udp-port port-number; | [edit services monitoring rfc2544 tests test-name test-name] | (Required if you specify inet as the family.) Specify the UDP port of the destination to be used in the
UDP header for the generated frames. For other families, if you do not specify the UDP port, the default
value of 4041 is used. | [
{
"name": "port-number",
"desc": ""
},
{
"name": "UDP port number for the test frames",
"desc": "Default: 4041"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X52.
Statement introduced in Junos OS Evolved Release 21.1R1. | [
"Configuring an RFC 2544-Based Benchmarking Test",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers"
] |
destinations (Event Policy) | destinations {
destination-name {
archive-sites {
url <password password>;
}
transfer-delay seconds;
}
} | [edit event-options] | Define one or more destinations, each with a unique name. You can reference a destination within an
event policy to indicate where to upload command output and various files, such as system log files and
core files. | [
{
"name": "destination-name",
"desc": "User-defined name of a destination."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Define Destinations for Event Policy File Archiving"
] |
destinations | destinations {
ftp:url {
password "password";
}
} | [edit services flow-collector] | Specify the primary and secondary destination FTP servers.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Destination FTP Servers for Flow Records"
] |
destined-port | destined-port port id; | [edit services nat port-forwarding map-name] | Specify the destination port number that needs to be translated to another port.
The destined-port statement is supported on the MS-DPC, MS-100, MS-400, and MS-500 MultiServices
PICS. Starting in Junos OS Release 17.4R1, the destined-port statement is also supported on the MS-MPC
and MS-MIC. | [
{
"name": "port id",
"desc": "The destination port number from where traffic will be forwarded."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Configuring Port Forwarding for Static Destination Address Translation",
"Configuring Port Forwarding Without Destination Address Translation"
] |
destruct-timeout (L2TP) | destruct-timeout seconds; | [edit services l2tp] | Set how long the router attempts to maintain dynamic destinations, tunnels, and sessions after they
have been destroyed.
BEST PRACTICE: Before you downgrade to a Junos OS Release that does not support
this statement, unconfigure the statement by issuing no services l2tp destruct-timeout. | [
{
"name": "seconds",
"desc": "Length of the destruct timeout."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"L2TP Tunnel Switching For Multiple-Domain Networks",
"L2TP LAC Subscriber Configuration",
"L2TP LNS Inline Service Interfaces"
] |
detect-loc | detect-loc; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain md-name maintenance-
association ma-name mep mep-id remote-mep mep-id ]
[edit protocols oam ethernet link-fault-management interface interface-name ] | Specify whether Ethernet OAM continuity checks are performed for an individual remote maintenance
end point (MEP).
When you configure the detect-loc statement at [edit protocols oam ethernet link-fault-management interface
interface-name] hierarchy level, a loss-of-continuity (LOC) defect is raised when the peer is not... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Configuring a MEP to Generate and Respond to CFM Protocol Messages"
] |
detection (Network Isolation Groups) | detection {
hold-time (<down milliseconds> <up milliseconds>);
link-tracking {
failure-type link;
interface name;
minimum-links minimum-links;
}
service-tracking {
core-isolation;
}
} | [edit logical-systems name protocols network-isolation group],
[edit protocols network-isolation group] | Configure detection parameters in a network isolation group for an EVPN network. The device uses
these parameters to detect network isolation condition changes. You also specify how long to delay
before the device records and acts on a network isolation status change.
A network isolation condition means a bridge domain... | [
{
"name": "hold-time down",
"desc": ""
},
{
"name": "milliseconds",
"desc": "When evaluating the device has experienced a network isolation condition, the time the device waits in milliseconds before declaring the network is not reachable. Specify a value of 1 or more milliseconds. This setting ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 23.1R1.
service-tracking option added in Junos OS and Junos OS Evolved Release 23.2R1. | [
"Determine IRB Interface State Changes from Local L2 Interface or Remote Connectivity Status in",
"EVPN Fabrics"
] |
detection-time (BFD for PIM) | detection-time {
threshold milliseconds;
} | [edit protocols pim interface interface-name bfd-liveness-detection],
[edit routing-instances routing-instance-name protocols pim interface interface-name bfd-
liveness-detection] | Enable BFD failure detection. The BFD failure detection timers are adaptive and can be adjusted to be
faster or slower. The lower the BFD failure detection timer value, the faster the failure detection and
vice versa. For example, the timers can adapt to a higher value if the adjacency fails (that is, the timer
detects... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2.
Support for BFD authentication introduced in Junos OS Release 9.6. | [
"Configuring BFD for PIM"
] |
detection-time (BFD Liveness Detection) | detection-time {
threshold milliseconds;
} | [edit logical-systems name routing-instances name protocols (evpn | l2vpn | vpls) oam bfd-liveness-
detection],
[edit logical-systems name routing-instances name protocols (evpn | l2vpn | vpls) neighbor neighbor-
id oam bfd-liveness-detection],
[edit logical-systems name routing-instances name protocols (evpn | l2vpn |... | Enable BFD failure detection. The BFD failure detection timers are adaptive and can be adjusted to be
faster or slower. The lower the BFD failure detection timer value, the faster the failure detection and
vice versa. For example, the timers can adapt to a higher value if the adjacency fails (that is, the timer
detects... | [
{
"name": "threshold",
"desc": ""
},
{
"name": "milliseconds",
"desc": "Specify the threshold for the adaptation of the BFD session detection time. When the detection time adapts to a value equal to or greater than the threshold, a single trap and a single system log message are sent. NOTE: The ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration | Statement introduced in Junos OS Release 8.2.
Support for BFD authentication introduced in Junos OS Release 9.6. | [
"Understanding How BFD Detects Network Failures",
"Configuring BFD for Layer 2 VPN and VPLS",
"Example: Configuring BFD for BGP",
"Example: Configuring BFD for Static Routes for Faster Network Failure Detection",
"bfd-liveness-detection"
] |
detection-time (LAG) | detection-time {
threshold milliseconds;
} | [edit interfaces aex aggregated-ether-options bfd-liveness-detection] | Configure BFD timers for aggregated Ethernet interfaces. | [
{
"name": "threshold",
"desc": ""
},
{
"name": "milliseconds",
"desc": "Specify the maximum time interval for detecting a BFD neighbor. If the transmit interval is greater than this value, the device triggers a trap."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Configuring Micro BFD Sessions for LAG",
"Example: Configuring Independent Micro BFD Sessions for LAG",
"Understanding Independent Micro BFD Sessions for LAG"
] |
detection-time (Liveness Detection) | detection-time {
threshold milliseconds;
} | [edit protocols iccp peer liveness-detection] | The Bidirectional Forwarding Detection (BFD) timers are adaptive and can be adjusted to be faster or
slower.
The remaining statement is explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [] |
detection-time | detection-time {
threshold milliseconds;
} | [edit system services dhcp-local-server liveness-detection method bfd],
[edit system services dhcp-local-server dhcpv6 liveness-detection method bfd],
[edit forwarding-options dhcp-relay liveness-detection method bfd], [edit forwarding-options dhcp-
relay dhcpv6 liveness-detection method bfd],
[edit system services dhc... | Enable failure detection. The BFD failure detection timers are adaptive and can be adjusted to be faster
or slower. For example, the timers can adapt to a higher value if the adjacency fails, or a neighbor can
negotiate a higher value for a timer than the one configured.
The remaining statements are explained separatel... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Example: Configuring Group Liveness Detection with BFD for DHCP Local Server Clients",
"Example: Configuring Global Liveness Detection with BFD for DHCP Relay Agent Clients"
] |
detector | detector {
protocol-name protocol-name {
tunable-name tunable-name {
tunable-value protocol-value;
}
}
} | [edit security idp sensor-configuration] | Configure protocol detector engine for a specific service. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
deterministic (Source NAT Next Gen Services) | deterministic {
block-size block-size;
host {
address address;
}
include-boundary-addresses;
} | [edit services nat source pool nat-pool-name port] | Configure deterministic NAT to ensure that the original internal source IPv4 or IPv6 address and port
always map to the same post-NAT IPv4 address and block of ports. In addition, the reverse mapping of a
given translated external IPv4 address and port are always mapped to the same internal IP address.
This eliminates ... | [
{
"name": "block-size block-size",
"desc": "The number of ports in the port block. Range: 1 to 64,512 Default: 256"
},
{
"name": "host address",
"desc": ""
},
{
"name": "address",
"desc": "The first usable pre-NAT subscriber address, which is used to perform the deterministic NAT m... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Deterministic NAPT for Next Gen Services"
] |
deterministic-ar-policy | deterministic-ar-policy [ deterministic-ar-policy-name ... ]; | [edit routing-instances name protocols evpn assisted-replication leaf] | Assign routing policies to an EVPN instance on an assisted replication (AR) leaf device to
deterministically steer multicast flows to specific preferred AR replicator devices. With this feature, you
can control how the leaf device load-balances multicast flows among the available AR replicator devices,
rather than usin... | [
{
"name": "deterministic-ar-policy-name",
"desc": "Routing policy name that deterministically directs matching multicast flows to specified AR replicators. You set deterministic AR routing policy conditions to match multicast flows in the from clause of the policy statement at the [edit policy-options polic... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.4R2. | [
"Deterministic Load Balancing and Traffic Steering to AR Replicators",
"Routing Policy Match Conditions",
"Actions in Routing Policy Terms",
"deterministic-nat-configuration-log-interval (Source NAT Next Gen"
] |
Services) | deterministic-nat-configuration-log-interval seconds; | [edit services nat source pool nat-pool-name port] | Configure the interval at which the syslog is generated for the deterministic NAT configuration.
(Deterministic NAPT for Next Gen Services is available only for MX series devices.) | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Deterministic NAPT for Next Gen Services"
] |
deterministic-port-block-allocation | deterministic-port-block-allocation {
block-size block-size;
include-boundary-addresses;
} | [edit services nat pool pool-name port] | Configure algorithm-based allocation of blocks of destination ports. By specifying this method, you
ensure that an incoming (source) IP address and port always map to the same destination IP address and
port block, thus eliminating the need for logging address translations. | [
{
"name": "block-size",
"desc": "Maximum number of ports that can be allocated to a user."
},
{
"name": "where",
"desc": "64512 is derived from (65535 - 1023) because the regular port assignments start from 1024. Number of subscribers is derived from the from clause of the applicable NAT rule. ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Configuring Deterministic NAPT"
] |
device-attribute (Easy EVPN LAG Configuration) | device-attribute {
loopback {
peer1-subnet peer1-subnet;
peer2-subnet peer2-subnet;
}
peer-id peer-id;
peer-to-peer {
overlay-connectivity {
ibgp;
}
peer-subnet {
inet inet;
inet6 inet6;
interface-name [ interface-name ... ];
}
underlay-connectivity {
o... | [edit services evpn] | Specify device-specific parameters as part of a generated Ethernet VPN (EVPN) fabric configuration.
You use the statements in the [edit services evpn] hierarchy level to simplify configuring an EVPN fabric
with Ethernet segment identifier (ESI) link aggregation groups (LAGs) in the topology. The feature you
enable with... | [
{
"name": "loopback",
"desc": ""
},
{
"name": "(peer1-subnet",
"desc": ""
},
{
"name": "peer1-subnet",
"desc": ""
},
{
"name": "peer2-subnet",
"desc": "Specify the device loopback IPv4 subnet address for each of the peer PE devices. The [edit services evpn] commit script ... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.2R1. | [
"Easy EVPN LAG (EZ-LAG) Configuration"
] |
device-authentication | device-authentication {
(encrypted-password "password" | plain-text-password);
} | [edit system] | Configure the authentication password used when accessing individual QFabric system components
with the request component login command.
NOTE: Configuring this statement overrides the password for individual QFabric system
components that was set during the initial QFabric system setup procedure. | [
{
"name": "encrypted-password \"password\"",
"desc": "Specify the MD5 or other encrypted authentication password. You"
},
{
"name": "plain-text-password",
"desc": "Plain-text password. The CLI prompts you for the password and then encrypts it."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Example: Configuring QFabric System Login Classes",
"Performing the QFabric System Initial Setup on a QFX3100 Director Group"
] |
device-count (MX Series) | device-count number; | [edit chassis aggregated-devices ethernet]
[edit chassis aggregated-devices sonet] | Configure the number of aggregated logical devices available to the router.
Starting in Junos release 14.2, for MX series routers, aggregated Ethernet interfaces created under a
logical system can be individually named. Prior to 14.2, ae interfaces were named automatically (AE1,
AE2) etc. upon setting the device count.... | [
{
"name": "number",
"desc": "Set the number of aggregated logical devices that will be available for configuration."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement functionality updated in Junos OS Release 14.2, as described below. | [
"Configuring Junos OS for Supporting Aggregated Devices",
"Configuring Aggregated SONET/SDH Interfaces"
] |
device-count (Pseudowire Subscriber Interfaces) | device-count number; | [edit chassis pseudowire-service] | Configure the number of pseudowire logical devices available to the router. The statement also defines
the available interface names for the pseudowire interfaces.
NOTE: When you subsequently configure the pseudowire interfaces, you must specify
the interface names in the range from ps0 up to ps(device-count - 1). For ... | [
{
"name": "number",
"desc": "Number of devices. Range: 1 through 7000, 1 through 18000 for MX2010 and MX2020 routers with the MX2K-MPC9E"
},
{
"name": "or MX2K-MPC11E line card",
"desc": ""
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1.
Increased upper limit in Junos OS Release 20.4R1. | [
"MPLS Pseudowire Subscriber Logical Interfaces",
"MPLS Pseudowire Subscriber Logical Interfaces",
"MPLS Pseudowire Subscriber Logical Interfaces"
] |
device-count | device-count number; | [edit chassis aggregated-devices ethernet],
[edit chassis node-group name aggregated-devices ethernet] | Configure the number of aggregated Ethernet logical devices available to the switch. | [
{
"name": "number",
"desc": "Maximum number of aggregated Ethernet logical interfaces on the switch."
},
{
"name": "EX4200 and EX4500 Virtual Chassis",
"desc": "Range: 1 through 239 for EX8200 Virtual Chassis Range: 1 through 255 for standalone EX8200 switches Range: 1 through 480 for standalo... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Range updated in Junos OS Release 9.5 for EX Series switches. | [
"Understanding Link Aggregation and Link Aggregation Control Protocol in a Junos Fusion",
"Configuring Link Aggregation",
"Example: Configuring Link Aggregation Between a QFX Series Product and an Aggregation Switch",
"Example: Configuring Aggregated Ethernet High-Speed Uplinks Between an EX4200 Virtual Chass... |
devices | devices device-names; | [edit logical-systems logical-system-name protocols rsvp],
[edit protocols rsvp] | Specifies one of the virtual tunnel (VT) interfaces to de-encapsulate the egress traffic for ultimate-hop
popping on point-to-multipoint LSPs. If no device is specified, the selection process is performed
automatically.
Default
The device selection process is performed automatically if no device is configured. Junos OS... | [
{
"name": "device-names",
"desc": "Specify which VT interfaces are used to handle the RSVP traffic."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Enabling Ultimate-Hop Popping on Point-to-Multipoint LSPs",
"Understanding Redundant Virtual Tunnel Interfaces in MBGP MVPNs"
] |
df-election | df-election {
backoff-period milliseconds;
offer-period milliseconds;
robustness-count number;
} | [edit logical-systems logical-system-name protocols pim interface (Protocols PIM) interface-name
bidirectional],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
interface (Protocols PIM) interface-name bidirectional],
[edit protocols pim interface (Protocols PIM) inter... | Optionally, configure the designated forwarder (DF) election parameters for bidirectional PIM.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Understanding Bidirectional PIM",
"Example: Configuring Bidirectional PIM"
] |
df-election-granularity | df-election-granularity {
per-esi {
lacp-oos-on-ndf;
}
per-esi-vlan;
per-evi;
} | [edit interfaces name esi],
[edit interfaces name unit number esi] | Configure the designated forwarder (DF) election granularity per member link for an aggregated
Ethernet interface in an EVPN multihoming configuration.
The per-esi lacp-oos-on-ndf setting enables EVPN multihoming when:
•
The peer provider edge (PE) devices in the multihomed Ethernet segment (ES) operate in active-
stan... | [] | interface | Statement introduced in Junos OS Release 20.4R1. | [
"MC-LAG Concepts"
] |
df-election-type | df-election-type {
mod;
preference {
least;
non-revertive;
value value;
}
} | [edit dynamic-profiles name interfaces name esi],
[edit dynamic-profiles name logical-systems name interfaces name esi],
[edit interfaces name esi],
[edit interfaces name unit number esi],
[edit protocols evpn interconnect esi],
[edit routing-instances name protocols evpn interconnect esi] | Choose how the device elects the designated forwarder (DF) for an Ethernet segment among the
multihoming peer provider edge (PE) devices in an Ethernet VPN (EVPN) network.
NOTE: If you configure the "df-election-granularity" on page 5825 "per-evi" on page
12916 option, you must also configure the df-election-type mod o... | [
{
"name": "mod",
"desc": "Use MOD-based DF election. The device uses MOD-based DF election by default if you don't configure the df-election-type statement at all. See CLI Explorer."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3 for MX Series Routers with MPC and MIC interfaces.
Support added in Junos OS Release 20.3R1 at the [edit protocols evpn interconnect esi] and [edit routing-
instances routing-instance-name protocols evpn interconnect esi] hierarchy levels. | [] |
dh-group (Security IKE) | dh-group (group1 | group2 | group5 | group14 | group15 | group16 | group19 | group20 | group21 |
group24); | [edit security ike proposal proposal-name] | Specify the IKE Diffie-Hellman group. The device does not delete existing IPsec SAs when you update
the dh-group configuration in the IKE proposal. | [
{
"name": "dh-group",
"desc": "Diffie-Hellman group for key establishment."
},
{
"name": "group1",
"desc": "768-bit Modular Exponential (MODP) algorithm."
},
{
"name": "group2",
"desc": "1024-bit MODP algorithm."
},
{
"name": "group5",
"desc": "1536-bit MODP algorithm."
... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5.
Support for the group14 option added in Junos OS Release 11.1.
Support for group19, group20, and group24 options added in Junos OS Release 12.1X45-D10.
Support for group19 and group20 options added in Junos OS Release 15.1X49-D70 for vSRX Virtual
Firewall.
Support for group... | [
"IPsec Overview",
"Installing Junos IKE package"
] |
dh-group (services) | dh-group (group1 | group2 | group5 |group14 | group15 | group16 | group19 | group20 | group24); | [edit services ipsec-vpn ike proposal proposal-name] | Configure the IKE Diffie-Hellman prime modulus group to use for performing the new Diffie-Hellman
exchange. | [
{
"name": "group1",
"desc": "768-bit."
},
{
"name": "group2",
"desc": "1024-bit."
},
{
"name": "group5",
"desc": "1536-bit."
},
{
"name": "group14",
"desc": "2048-bit."
},
{
"name": "group15",
"desc": "3072-bit."
},
{
"name": "group16",
"desc": "40... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
group15, group16, and group24 options added in Junos OS Release 17.4R1. | [
"Configuring IKE Proposals"
] |
dh-group | dh-group (group1 | group2 | group5 | group14); | [edit security ike proposal ike-proposal-name] | Configure the IKE Diffie-Hellman group. | [
{
"name": "dh-group",
"desc": "Type of Diffie-Hellman prime modulus group when performing the new Diffie-Hellman"
},
{
"name": "exchange. It can be one of the following:",
"desc": ""
},
{
"name": "group1",
"desc": "768-bit."
},
{
"name": "group2",
"desc": "1024-bit."
},... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Diffie-Hellman Group for an IKE Proposal"
] |
dhcp (DHCP Client) | dhcp {
client-identifier {
(ascii string | hexadecimal string);
}
force-discover;
lease-time (length | infinite);
metric;
no-dns-install;
options;
requested-options;
retransmission-attempt value;
retransmission-interval seconds;
server-address server-address;
upda... | Configure a Dynamic Host Configuration Protocol (DHCP) client for an IPv4 interface for logical systems
and tenant systems.
The remaining statements are described separately.
NOTE: Starting in Junos OS Release 18.1R1, DHCPv4 and DHCPv6 clients are
supported on management interfaces (fxp0 and em0) configured in the non-... | [
{
"name": "client-identifier duid-type",
"desc": "Identify a client by a client-identifier value. This statement is mandatory."
},
{
"name": "no-dns-install",
"desc": "Do not add DNS information to the DHCP client even after it is learned from the DHCP server."
},
{
"name": "options",
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
The logical-systems and tenants options are introduced in Junos OS Release 18.4R1. | [
"Understanding Interfaces",
"Configuring a DHCP Client"
] | |
dhcp security statistics | [] | Output Fields
Table 35: <name-of-command> Output Fields
Field Name
Field Description
Level of Output
Sample Output
<name-of-sample-output-command>
user@host> command-name option1 option2
<name-of-sample-output-command>
user@host> command-name option1 option2
Release Information | [] | ||||
dhcp | dhcp {
boot-file filename;
boot-server (address | hostname);
default-lease-time seconds;
domain-name domain-name;
domain-search [domain-list];
maximum-lease-time seconds;
name-server {
address;
}
next-servernext-server
option option-identifier-code ;
pool address/pre... | [edit system services]
[edit logical-systems logical -system-name system services] | Configure a router, or a switch as a DHCP server. A DHCP server can allocate network addresses and
deliver configuration information to client hosts on a TCP/IP network.
The remaining statements are explained separately. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
The logical-systems option is introduced in Junos OS Release 18.4R1. | [] |
dhcp-attributes (Access IPv4 Address Pools) | dhcp-attributes {
boot-file boot-file-name;
boot-server boot-server-name;
domain-name domain-name;
grace-period seconds;
maximum-lease-time (seconds | infinite);
name-server ipv4-address;
netbios-node-type (b-node | h-node | m-node | p-node);
next-server next-server-name;
option dhcp... | [edit access address-assignment pool pool-name family inet] | Configure attributes for IPv4 address pools that can be used by different clients. The DHCP attributes
for this statement uses standard IPv4 DHCP options. | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"DHCP Overview"
] |
dhcp-attributes (Access IPv6 Address Pools) | dhcp-attributes {
dns-server ipv6-address;
grace-period seconds;
maximum-lease-time (seconds | infinite);
option dhcp-option-identifier-code {
array {
byte [8-bit-value];
flag [ false| off |on |true];
integer [32-bit-numeric-values];
ip-address [i... | [edit access address-assignment pool pool-name family inet6] | Configure attributes for address pools that can be used by different clients. | [
{
"name": "dns-server IPv6-address",
"desc": "Specify a DNS server to which clients can send DNS queries."
},
{
"name": "grace-period seconds",
"desc": "Specify the grace period offered with the lease."
},
{
"name": "maximum-lease-time seconds",
"desc": "Specify the maximum length of... | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"DHCP Overview"
] |
dhcp-attributes (Address-Assignment Pools) | dhcp-attributes {
boot-file filename;
boot-server (address | hostname);
dns-server [ ipv6-address ];
domain-name domain-name;
exclude-prefix-len exclude-prefix-length;
grace-period seconds;
maximum-lease-time seconds;
name-server [ server-list ];
netbios-node-type node-type;
opti... | [edit access address-assignment pool pool-name family family] | Configure DHCP attributes for the protocol family in a specific address pool. The attributes determine
options and behaviors for the DHCP clients. | [
{
"name": "boot-file",
"desc": "Set the boot file advertised to DHCP clients. After the client receives an IP address and the boot file location from the DHCP server, the client uses the boot image stored in the boot file to complete DHCP setup. This configuration is equivalent to DHCP option 67."
},
{
... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
exclude-prefix-len statement introduced in Junos OS Release 17.3 for MX Series. | [
"Address-Assignment Pools for Subscriber Management",
"DHCP Client Attribute and Address Assignment",
"DHCP Lease Times for IP Addresses"
] |
dhcp-client | dhcp-client {
client-identifier {
prefix {
host-name;
logical-system-name;
routing-instance-name;
}
use-interface-description (device | logical);
user-id (ascii string| hexadecimal string);
}
force-discover;
lease-time (length | infini... | [edit interfaces interface-name unit logical-unit-number family family] | Configure the Dynamic Host Configuration Protocol (DHCP) client. | [
{
"name": "force-discover",
"desc": "Forces the DHCP client to send a DHCP discover packet after one to three failed"
},
{
"name": "lease-time",
"desc": "Specify the time to negotiate and exchange DHCP information."
},
{
"name": "infinite",
"desc": "Lease never expires."
},
{
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10.
Starting with Junos OS Release 17.4R1 and Junos OS Release 15.1X49-D60, on all SRX Series Firewalls
and vSRX Virtual Firewall instances, the CLI option dhcp-client at [edit interfaces interface-name unit
logical-unit-number family inet] hierarchy is changed to dhcp ... | [
"DHCP Overview"
] |
dhcp-local-server (System Services) | dhcp-local-server {
dhcpv6 {
authentication {
password password;
username-include {
circuit-type;
client-id;
delimiter delimiter-character;
domain-name domain-name;
interface-name;
logica... | [edit system services] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"DHCP Overview"
] |
dhcp-local-server | dhcp-local-server {
access-profile profile-name;
allow-active-leasequery {
idle-timeout seconds;
peer-address address;
timeout seconds;
}
allow-bulk-leasequery {
max-connections number-of-connections;
max-empty-replies number-of-replies;
restricted-request... | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services],
[edit logical-systems logical-system-name system services],
[edit routing-instances routing-instance-name system services],
[edit system services] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Understanding Differences Between Legacy DHCP and Extended DHCP",
"DHCPv6 Local Server Overview"
] |
dhcp-option82 | dhcp-option82 {
circuit-id {
prefix hostname;
use-interface-description;
use-vlan-id;
}
remote-id {
prefix hostname | mac | none;
use-interface-description;
use-string string;
}
vendor-id <string>;
} | [edit ethernet-switching-options secure-access-port vlan (all | vlan-name)],
[edit forwarding-options helpers bootp],
[edit forwarding-options helpers bootp interface interface-name] | When the switch receives a DHCP request from a DHCP client connected on one of the switch's
interfaces, have the switch insert DHCP option 82 (also known as the DHCP relay agent information
option) information in the DHCP request packet header before it forwards or relays the request to a
DHCP server. The server uses t... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Example: Setting Up DHCP Option 82 Using the Same VLAN",
"Example: Setting Up DHCP Option 82",
"http://tools.ietf.org/html/rfc3046."
] |
dhcp-relay (DHCP Spoofing Prevention) | dhcp-relay {
group group-name {
interface interface-name;
}
} | [edit routing-instances routing-instance-name bridge-domains bridge-domain-name forwarding-
options],
[edit routing-instances routing-instance-name forwarding-options] | Configure Dynamic Host Configuration Protocol (DHCP) snooping on the router. When acting as a
snooping agent, the MX Series router typically is located between the client and the DHCP relay agent.
It creates filters by “snooping” DHCP messages and binding DHCP-issued IP addresses to the MAC
address of the client. Thes... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4 (MX Series routers only). | [
"Preventing DHCP Spoofing on MX Series 5G Universal Routing Platforms"
] |
dhcp-relay (Easy EVPN LAG Configuration) | dhcp-relay name {
dhcp-server-address dhcp-server-address;
relay-source DHCP-relay-source-interface;
vrf-instance vrf-instance-id;
}; | [edit services evpn evpn-vxlan] | Specify Dynamic Host Configuration Protocol (DHCP) relay parameters for a generated configuration for
an Ethernet VPN (EVPN) fabric with Virtual Extensible LAN (VXLAN) encapsulation.
You use the statements in the [edit services evpn] hierarchy level to simplify configuring an EVPN fabric
with Ethernet segment identifie... | [
{
"name": "name",
"desc": "The group name to identify a DHCP server and relay group. The commit script generates configuration statements to create the DHCP relay group."
},
{
"name": "dhcp-server-address dhcp-",
"desc": ""
},
{
"name": "server-address",
"desc": "(Required) The IP ad... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.2R1. | [
"Easy EVPN LAG (EZ-LAG) Configuration",
"DHCP Relay Agent over EVPN-VXLAN",
"https://www.juniper.net/documentation/us/en/software/junos/dhcp/index.html"
] |
dhcp-relay | dhcp-relay {
access-profile profile-name;
active-leasequery {
idle-timeout seconds;
peer-address address;
timeout seconds;
topology-discovery;
}
active-server-group server-group-name;
authentication {
password password-string;
username-include {
... | [edit forwarding-options],
[edit logical-systems logical-system-name forwarding-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options],
[edit routing-instances routing-instance-name forwarding-options] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Extended DHCP Relay Agent Overview",
"DHCPv6 Relay Agent Overview",
"DHCP Relay Proxy Overview",
"Specifying Authentication Support"
] |
dhcp-security (MX Series) | dhcp-security {
arp-inspection;
group group-name {
interface interface-name {
static-ip ip-address {
mac mac-address;
}
}
overrides {
no-option82;
trusted;
untrusted;
}
}
ip-source-guard;
... | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security] | Configure port security features on the switching device. DHCP snooping is enabled automatically if you
configure any of the following port security features within this hierarchy:
•
Dynamic ARP inspection (DAI)
•
IP source guard
•
DHCP option 82
•
Static IP | [
{
"name": "mac-address",
"desc": "Value (in hexadecimal format) of the address assigned to this device."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Applying CoS Forwarding Classes to Prioritize Inspected Packets",
"Configuring IP Source Guard (non-ELS)",
"Configuring DHCP Option 82 on a Router with Bridge Domain",
"Configuring Static DHCP IP Addresses for DHCP snooping (MX routers)"
] |
dhcp-security | dhcp-security {
arp-inspection;
dhcpv6-options {
light-weight-dhcpv6-relay;
option-16 {
use-string string;
}
option-18 {
prefix {
host-name;
logical-system-name;
routing-instance-name;
vlan-i... | [edit vlans vlan-name forwarding-options] | Configure DHCP or DHCPv6 snooping on the switch. DHCP snooping is also enabled automatically if
you configure any of the following port security features within this hierarchy:
•
Dynamic ARP inspection (DAI)
•
IP source guard
•
DHCP option 82
•
Static IP
For switches that support DHCPv6, both DHCP snooping and DHCPv6 s... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10 .
Support for static-ipv6, neighbor-discovery-inspection, ipv6-source-guard, no-dhcpv6-snooping, and no-option37
introduced in Junos OS Release 13.2X51-D20 for EX Series switches.
Support for dhcpv6-options, option-16, option-18, option-37, no-dhcpv6-options, no-opt... | [
"Enabling Dynamic ARP Inspection (ELS)",
"Configuring IP Source Guard (ELS)",
"Setting Up DHCP Option 82 on the Switch with No Relay (ELS)",
"Configuring Static DHCP IP Addresses for DHCP snooping (ELS)",
"Microsegmentation Using Group-Based Policies"
] |
dhcp-service | dhcp-service {
accept-max-tcp-connections max-tcp-connections;
dhcp-snooping-file(local_pathname | remote_URL) {
write-interval interval;
}
dhcpv6-snooping-file {
location;
write-interval seconds;
}
(disable | enable);
interface-traceoptions {
file filename <... | [edit system processes] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10.
Support for log option introduced in Junos OS Release 19.1R1 for SRX Series Firewalls. | [
"Configuring Persistent Bindings in the DHCP or DHCPv6 (ELS)"
] |
dhcp-snooping-file (EX) | dhcp-snooping-file {
location ( local_pathname | remote_URL);
timeout seconds;
write-interval seconds;
} | [edit ethernet-switching-options secure-access-port] | Ensure that IP-MAC bindings persist through switch reboots by specifying a local pathname or a remote
URL for the storage location of the DHCP snooping database file.
The remaining statements are explained separately. See CLI Explorer.
Default
The IP-MAC bindings in the DHCP snooping database file are not persistent. I... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Configuring Persistent Bindings in the DHCP or DHCPv6 (non-ELS)",
"Understanding DHCP Snooping (non-ELS)"
] |
dhcp-snooping-file | dhcp-snooping-file (local_pathname | remote_URL);
write-interval seconds;
} | [edit system processes dhcp-service] | Ensure that IP-MAC bindings persist through the device reboots by specifying a local pathname or a
remote URL for the storage location of the DHCP snooping database file. You must specify how
frequently the device writes the database entries into the DHCP snooping database file.
The remaining statement is explained sep... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10. | [
"Configuring Persistent Bindings in the DHCP or DHCPv6 (ELS)",
"Configuring Static DHCP IP Addresses for DHCP snooping (MX routers)",
"Understanding DHCP Snooping (non-ELS)"
] |
dhcp-tags (Adjustment Control Profiles) | dhcp-tags {
algorithm algorithm;
priority priority;
} | [edit class-of-service adjustment-control-profiles profile-name application] | Configure the shaping rate adjustment controls for the DHCP tags application. DHCP tags are supported
for session negotiation for DHCPv4 and DHCPv6 over IP demux and VLAN demux interfaces. This
means that shaping rates received from DHCP option 82 in the DISCOVER message or DHCPv6 option
17 in the SOLICIT can be used t... | [
{
"name": "algorithm",
"desc": "Rate adjustment algorithm used by the DHCP Tags application. Values:"
},
{
"name": "adjust-always",
"desc": "Adjust the shaping rate unconditionally."
},
{
"name": "adjust-greater",
"desc": "Adjust the shaping rate if it is greater than the configured... | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1R1. | [
"Configuring CoS Adjustment Control Profiles",
"CoS Adjustment Control Profiles Overview",
"Verifying the CoS Adjustment Control Profile Configuration"
] |
dhcp-trusted | (dhcp-trusted | no-dhcp-trusted); | [edit ethernet-switching-options secure-access-port interface (all | interface-name)] | Allow DHCP responses from the specified interfaces (ports) or all interfaces.
•
dhcp-trusted—Allow DHCP responses.
•
no-dhcp-trusted—Deny DHCP responses.
Default
Trusted for trunk ports, untrusted for access ports. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Example: Configuring Port Security (non-ELS)",
"Example: Protecting against Rogue DHCP Server Attacks",
"Enabling a Trusted DHCP Server (non-ELS)"
] |
dhcpv6 (DHCP Local Server) | dhcpv6 {
access-profile profile-name;
allow-active-leasequery {
idle-timeout seconds;
peer-address address;
timeout seconds;
}
allow-bulk-leasequery {
max-connections number-of-connections;
max-empty-replies number-of-replies;
restricted-requestor;
... | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server],
[edit logical-systems logical-system-name system services dhcp-local-server],
[edit routing-instances routing-instance-name system services dhcp-local-server],
[edit system services dhcp-local-server] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"DHCPv6 Local Server Overview"
] |
dhcpv6 (DHCP Relay Agent) | dhcpv6 {
access-profile profile-name;
active-leasequery {
idle-timeout seconds;
peer-address address;
timeout seconds;
topology-discovery;
}
active-server-group server-group-name;
}
authentication {
password password-string;
username-include {
... | [edit forwarding-options dhcp-relay],
[edit logical-systems logical-system-name forwarding-options dhcp-relay],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options dhcp-relay],
[edit routing-instances routing-instance-name forwarding-options dhcp-relay] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
Support for forward-snooped-clients introduced in Junos OS Release 15.1X53-D56 for EX Series switches
and Junos OS Release 17.1R1. | [
"DHCPv6 Relay Agent Overview",
"Specifying Authentication Support"
] |
dhcpv6 (System Services) | dhcpv6 {
authentication {
password password;
username-include {
circuit-type;
client-id;
delimiter delimiter-character;
domain-name domain-name;
interface-name;
logical-system-name;
relay-agent-interface-id;
... | [edit system services] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "duplicate-clients-on-interface",
"desc": "Allow duplicate clients on different interfaces in a subnet."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"DHCP Overview"
] |
dhcpv6-client | dhcpv6-client {
client-ia-type {
ia-na;
ia-pd;
}
client-identifier duid-type (duid-ll | duid-llt | vendor);
client-type (autoconfig | stateful);
interface-identifier interface_id;
rapid-commit;
req-option (dns-server | domain | fqdn | nis-domain | nis-server | ntp-server | sip-do... | [edit interfaces interface-name unit logical-unit-number family inet6]
[edit logical-systems name interfaces name unit name family inet6]
[edit tenants tenant-name interfaces name unit name family inet6] | Configure the Dynamic Host Configuration Protocol version 6 (DHCPv6) client.
NOTE: NOTE: Starting in Junos OS Release 17.3R1 (on MX Series) and Junos OS Release
18.3R1 (on SRX Series), DHCPv4 and DHCPv6 clients are supported on management
interfaces (fxp0 and em0) configured in the non-default management routing instan... | [
{
"name": "client-ia-type",
"desc": "Identity association type for DHCPv6 client. This statement is mandatory."
},
{
"name": "client-identifier duid-type",
"desc": "Identity a client by a client-identifier value. This statement is mandatory."
},
{
"name": "client-type",
"desc": "Iden... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10.
Statement introduced in Junos OS Release 24.2R1 for NFX Series Routers.
The logical-systems and tenants options are introduced in Junos OS Release 18.4R1. | [
"DHCP Overview",
"Minimum DHCPv6 Client Configuration on SRX Series Devices"
] |
dhcpv6-options | dhcpv6-options {
option-16 {
use-string string;
}
option-18 {
prefix {
host-name;
logical-system-name;
routing-instance-name;
vlan-id;
vlan-name;
}
use-interface-mac;
use-interface-index (device | logical);
... | [edit vlans vlan-name forwarding-options dhcp-security] | Configure optional information to be included in DHCPv6 packets during the DHCPv6 snooping
process.
The remaining statements are explained separately. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10 . | [
"Setting Up DHCP Option 82 on the Switch with No Relay (ELS)",
"Configuring Static DHCP IP Addresses for DHCP snooping (ELS)"
] |
dhcpv6-snooping-file | dhcpv6-snooping-file (local_pathname | remote_URL);
location local_pathname | remote_URL;
timeout seconds;
write-interval seconds;
} | For platforms with Enhanced Layer 2 Software (ELS):
[edit system processes dhcp-service],
For platforms without ELS:
[edit ethernet-switching-options secure-access-port] | Ensure that IP-MAC bindings persist through switch reboots by specifying a local pathname or a remote
URL for the storage location of the DHCPv6 snooping database file.
The remaining statements are explained separately. See CLI Explorer.
Default
The IP-MAC bindings in the DHCPv6 snooping database are not persistent. I... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51-D20.
Support at the [edit ethernet-switching-options secure-access-port] hierarchy level introduced in Junos OS
14.1X53-D10 for EX Series switches. | [
"Configuring Persistent Bindings in the DHCP or DHCPv6 (ELS)",
"Understanding DHCP Snooping (non-ELS)"
] |
diag-port-authentication | diag-port-authentication (encrypted-password "password" | plain-text-password); | [edit system] | Configure a password for performing diagnostics on the router’s System Control Board (SCB), System
and Switch Board (SSB), Switching and Forwarding Module (SFM), or Forwarding Engine Board (FEB)
port.
For routers that have more than one SSB, the same password is used for both SSBs.
NOTE: Do not run diagnostics on the S... | [
{
"name": "encrypted-password password",
"desc": "Use MD5 or other encrypted authentication. Specify the MD5 or other"
},
{
"name": "plain-text-password",
"desc": "Use a plain-text password. The CLI prompts you for the password and then encrypts"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Diagnostic Tools Overview",
"show interfaces diagnostics optics"
] |
dial-options (Dynamic Profiles) | dial-options {
ipsec-interface-id name;
l2tp-interface-id name;
(shared | dedicated);
} | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number] | Specify the options for configuring logical interfaces in dynamic profiles for group and user sessions in
L2TP or IPsec dynamic endpoint tunneling. | [
{
"name": "dedicated",
"desc": "(LNS on M Series routers and MX Series routers only) Specify that a logical interface can host only one session at a time."
},
{
"name": "ipsec-interface-id name",
"desc": "Interface identifier for group of dynamic peers. This identifier must be replicated at the ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"L2TP LNS Inline Service Interfaces"
] |
dial-options | dial-options {
ipsec-interface-id name;
l2tp-interface-id name;
(shared | dedicated);
} | [edit interfaces sp-fpc/pic/port unit logical-unit-number],
[edit interfaces si-fpc/pic/port unit logical-unit-number],
[edit logical-systems logical-system-name interfaces sp-fpc/pic/port unit logical-unit-number],
[edit logical-systems logical-system-name interfaces si-fpc/pic/port unit logical-unit-number] | Specify the options for configuring logical interfaces for group and user sessions in L2TP or IPsec
dynamic endpoint tunneling. | [
{
"name": "dedicated",
"desc": "(LNS on M Series routers and MX Series routers only) Specify that a logical interface can host"
},
{
"name": "ipsec-interface-id name",
"desc": "(M Series routers only) Interface identifier for group of dynamic peers. This"
},
{
"name": "l2tp-interface-id ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
The [edit ...si-...] hierarchy levels introduced in Junos OS Release 11.4. | [
"Configuring the Identifier for Logical Interfaces that Provide L2TP Services",
"Configuring Dynamic Endpoints for IPsec Tunnels",
"Configuring Options for the LNS Inline Services Logical Interface"
] |
dial-string | dial-string [ dial-string-numbers ]; | [edit interfaces br-pim/0/port unit logical-unit-number dialer-options],
[edit logical-systems logical-system-name interfaces br-pim/0/port unit logical-unit-number
dialer-options] | On J Series Services Routers with ISDN interfaces, specify one or more ISDN dial strings used to reach a
destination subnetwork. | [
{
"name": "dial-string-numbers",
"desc": "One or more strings of numbers to call."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [] |
dialer | dialer filter-name; | [edit interfaces interface-name unit logical-unit-number family family],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family] | Apply a dialer filter to an interface. To create the dialer filter, include the dialer-filter statement at the
[edit firewall filter family family] hierarchy level. | [
{
"name": "filter-name",
"desc": "Dialer filter name."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.