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 |
|---|---|---|---|---|---|---|---|
dscp-ipv6 (Class of Service) | dscp-ipv6 rewrite-name {
import (rewrite-name | default);
forwarding-class class-name {
loss-priority level {
code-point [ aliases ] [ bit-patterns ];
}
}
}
Hierarchy (Classifiers)
[edit class-of-service classifiers],
Hierarchy (Code-Point Aliases)
[edit class-of-service code-po... | Define the Differentiated Services code point (DSCP) IPv6 mapping that is applied to the packets.
NOTE: On switches that use different classifiers for unicast and multidestination
(multicast, broadcast, and destination lookup fail) traffic, there is no DSCP IPv6 classifier
for multidestination (multicast, broadcast, an... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Defining CoS Code-Point Aliases",
"Understanding Applying CoS Classifiers and Rewrite Rules to Interfaces"
] | |
dscp-ipv6 (Class of Service) | dscp-ipv6 rewrite-name {
import (rewrite-name | default);
forwarding-class class-name {
loss-priority level {
code-point [ aliases ] [ bit-patterns ];
}
}
}
Hierarchy (Classifiers)
[edit class-of-service classifiers],
Hierarchy (Code-Point Aliases)
[edit class-of-service code-poi... | Define the Differentiated Services code point (DSCP) IPv6 mapping that is applied to the packets.
NOTE: On devices that use different classifiers for unicast and multidestination
(multicast, broadcast, and destination lookup fail) traffic, there is no DSCP IPv6 classifier
for multidestination (multicast, broadcast, and... | [
{
"name": "protocol",
"desc": ""
},
{
"name": "mpls",
"desc": "(Optional for ingress MPLS tunnel nodes) On devices that support this option, rewrite the MPLS EXP bits in the MPLS header independently of the IPv6 DSCP value for IPv6 packets entering an MPLS tunnel."
}
] | 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.
Support for protocol mpls option introduced in Junos OS Release 10.4R2. | [
"Configuring Rewrite Rules",
"Setting IPv6 DSCP and MPLS EXP Values Independently",
"Configuring DSCP Values for IPv6 Packets Entering the MPLS Tunnel",
"Applying Rewrite Rules to Output Logical Interfaces",
"Defining CoS Code-Point Aliases",
"Understanding Applying CoS Classifiers and Rewrite Rules to In... | |
dscp-ipv6 (Dynamic Classifiers) | dscp-ipv6 (classifier-name | default); | [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-
number classifiers] | For IPv6 traffic, apply a Differentiated Services (DiffServ) code point (DSCP) classifier to a subscriber
interface in a dynamic profile. | [
{
"name": "classifier-name",
"desc": "Name of a classifier mapping configured at the [edit class-of-service classifiers dscp-ipv6]"
},
{
"name": "default",
"desc": "The default mapping."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 10.1. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Applying a Classifier to a Subscriber Interface in a Dynamic Profile",
"classifiers (Definition)"
] |
dscp-ipv6 (Dynamic Rewrite Rules) | dscp-ipv6 (rewrite-name | default); | [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-
number rewrite-rules] | For IPv6 traffic, apply a DSCP rewrite rule to a subscriber interface in a dynamic profile. | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules dscp-ipv6] hierarchy level."
},
{
"name": "default",
"desc": "The default mapping."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release10.1. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"rewrite-rules"
] |
dscp-mapping-classifier | dscp-mapping-classifier ipv4-classifier-name
dscp-ipv6-mapping-classifier ipv6-classifier-name | [edit forwarding-options family (inet | inet6)] | Enable the BGP FlowSpec filter on a device. Configure BGP Flow Specification (FlowSpec) DSCP action
to forward packets using the forwarding class and loss priority information across the network
effectively.
NOTE: On Junos OS Evolved version 22.4 and earlier, we don’t support the DSCP
marking action as part of BGP Flow... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.1 for PTX series and MX series devices. | [] |
dscp-rewrite | dscp-rewrite {
code-point 6 bit patterns;
} | [edit security alg sip]
[edit security alg h323]
[edit security alg mgcp]
[edit security alg sccp] | Specify a rewrite-rule for the traffic that passes through a voice over IP Application Layer Gateway (VoIP
ALG). | [
{
"name": "6-bit patterns",
"desc": "Value of the code point in binary form."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Understanding VoIP DSCP Rewrite Rules"
] |
dsl (Access-Line Rate Adjustment) | dsl {
adsl {
overhead-bytes bytes;
total-adjust percentage;
}
adsl2 {
overhead-bytes bytes;
total-adjust percentage;
}
adsl2-plus {
overhead-bytes bytes;
total-adjust percentage;
}
gfast {
overhead-adjust percentage;
overhead-by... | [edit system access-line] | Configure adjustments to actual DSL data rates as follows:
•
Multiply the actual data rate by a percentage for only downstream rates or for both upstream an
downstream rates
•
Adjust the encapsulation overhead by adding to or subtracting from the total cell or frame bytes a
specified number of bytes
The actual (unadjus... | [
{
"name": "adsl",
"desc": "Sets attributes for ADSL access lines."
},
{
"name": "adsl2",
"desc": "Sets attributes for ADSL2 access lines."
},
{
"name": "adsl2-plus",
"desc": "Sets attributes for ADSL2+ access lines."
},
{
"name": "gfast",
"desc": "Sets attributes for G.fa... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R1. | [
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Neighbors and Operations"
] |
dsl-sfp-options | dsl-sfp-options {
adsl-options {
encap encapsulation;
vci identifier;
vpi identifier;
annex (auto | annexj-off);
}
gfast-options{
carrier carrier setting;
}
vdsl-options {
carrier carrier setting;
profile profile;
}
} | [edit interfaces interface name] | Configure ADSL properties on SRX Series Firewalls.
Follow these example pre-configuration steps with the SFP inserted on slot 8 of the device, required for
Annex J support. You must configure one logical interface for xDSL SFP control path to work.
1. ADSL and Annex J on inet interface:
user@host# set interfaces ge-0/0... | [
{
"name": "adsl-options",
"desc": "Options of ADSL interface."
},
{
"name": "annex (auto | annexj-off)",
"desc": "The Annex type."
},
{
"name": "carrier",
"desc": "Carrier setting on VDSL. Supported VDSL carriers are A43, B43, and auto. Supported G.fast carriers are A43, A43c, B43, a... | routing—To view this statement in the configuration.
routing–control—To add this statement to the configuration.
system—To view this statement in the configuration.
system–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [
"Configuring ADSL Interfaces"
] |
dslite-softwire-initiator | dslite-softwire-initiator {
maximum amount;
reserved amount;
} | [edit system security-profile] | Specifies the number of IPv6 dual-stack lite (DS-Lite) softwire initiators that connects to the softwire
concentrator configured in either a user logical system or the primary logical system. The option is
configured in the security profile that is bound to the logical system.
Only the primary administrator can create ... | [
{
"name": "maximum amount",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its"
},
{
"name": "are available",
"desc": "that is, if they are not allocated to other logical systems. The maximum allowed quota"
},
{
"name": "reserved amount",
"desc... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Understanding IPv6 Dual-Stack Lite in Logical Systems"
] |
dsr | dsr (ignore | normal | require); | [edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options] | For EIA-530 and V.35 interfaces only, configure the from-DCE signal, data-set-ready (DSR). | [
{
"name": "ignore",
"desc": "The from-DCE signal is ignored."
},
{
"name": "normal",
"desc": "Normal DSR signal handling as defined by the TIA/EIA Standard 530."
},
{
"name": "require",
"desc": "The from-DCE signal must be asserted."
}
] | 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 the Serial Signal Handling"
] |
dsr-polarity | dsr-polarity (negative | positive); | [edit interfaces interface-name serial-options] | Configure DSR signal polarity. | [
{
"name": "positive",
"desc": "Positive signal polarity."
},
{
"name": "negative",
"desc": "Negative signal polarity."
}
] | 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 Serial Signal Polarities"
] |
dtcp-only (System Services) | dtcp-only; | [edit system services] | Prevent RADIUS-initiated subscriber secure policy mirroring from being enabled, while allowing both
DTCP-initiated mirroring and DTCP-based flow-tap services (FlowTapLite) to be enabled. This statement
has no effect on existing RADIUS-initiated mirroring services. You must issue the statement before such
services are a... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R1. | [
"Disabling RADIUS-Initiated Subscriber Secure Policy Mirroring",
"Subscriber Secure Policy Overview",
"Configuring Support for Subscriber Secure Policy Mirroring",
"Configuring FlowTapLite on MX Series Routers and M320 Routers with FPCs"
] |
dte-options | dte-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore... | [edit interfaces interface-name serial-options] | For M Series and T Series routers, configure the serial interface signal characteristics.
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 in Junos OS Release 8.3.
Statement previously known as control-leads. | [
"Configuring the Serial Signal Handling"
] |
dtr | dtr signal-handling-option; | [edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options] | For EIA-530 and V.35 interfaces only, configure the to-DCE signal, data-transmit-ready (DTR). | [
{
"name": "signal-handling-option",
"desc": "Signal handling for the DTR signal. The signal handling can be one of the following:"
},
{
"name": "assert",
"desc": "The to-DCE signal must be asserted."
},
{
"name": "auto-synchronize",
"desc": "Normal DTR signal with automatic synchroni... | 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 the Serial Signal Handling"
] |
dtr-circuit | dtr-circuit (balanced | unbalanced); | [edit interfaces interface-name serial-options] | For EIA-530 and V.35 interfaces only, configure a DTR circuit. | [
{
"name": "balanced",
"desc": "Balanced DTR signal."
},
{
"name": "unbalanced",
"desc": "Unbalanced DTR signal."
}
] | 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 the Serial DTR Circuit"
] |
dtr-polarity | dtr-polarity (negative | positive); | [edit interfaces interface-name serial-options] | Configure DTR signal polarity. | [
{
"name": "positive",
"desc": "Positive signal polarity."
},
{
"name": "negative",
"desc": "Negative signal polarity."
}
] | 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 Serial Signal Polarities"
] |
dual-dr | dual-dr {
enhanced;
} | [edit dynamic-profiles name protocols pim interface],
[edit logical-systems name protocols pim interface],
[edit logical-systems name routing-instances name protocols pim interface],
[edit logical-systems name tenants name routing-instances name protocols pim interface],
[edit protocols pim interface],
[edit routing-i... | Enable PIM dual designated router mode for a pair of Multichassis Link Aggregation Group (MC-LAG)
peers managing VLAN multicast traffic and Layer 3 multicast traffic over IRB interfaces.
PIM dual designated router mode sets up one device in a pair of MC-LAG peers as a primary designated
router (DR) and the other device... | [
{
"name": "none",
"desc": "Enable default dual designated router mode (available for backwards compatibility)."
},
{
"name": "enhanced",
"desc": "Enable enhanced PIM dual designated router mode (recommended if available)."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51 for the QFX Series.
Statement introduced in Junos OS Release 16.1 for the MX Series.
Statement with enhanced option introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center. | [
"Understanding Multichassis Link Aggregation Groups"
] |
dual-phase-bootup | dual-phase-bootup; | [edit system] | You can prevent the device from reaching an amnesiac state post-reboot by configuring the dual-phase-
bootup feature before the reboot. When a device has a scaled configuration or has a lot of constraints to
be validated, upon reboot it may take more than 45 minutes to finish. This lengthy reboot time exceeds
the limit... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [
"Rescue and Recovery of Configuration File (Junos OS)"
] |
dual-stack (DHCP Local Server Overrides) | dual-stack dual-stack-group-name; | [edit logical-systems name routing-instances routing-instance-name system services dhcp-local-
server ...],
[edit logical-systems name system services dhcp-local-server ...],
[edit routing-instances name system services dhcp-local-server ...],
[edit system services dhcp-local-server group group-name interface interface... | Assigns the specified dual-stack group to both legs (DHCP and DHCPv6) of the DHCP dual stack. The
dual-stack group defines the common configuration settings for DHCP and DHCPv6 subscribers on both
legs. These settings take precedence over all other configurations, such as those specified in global,
group, or interface ... | [
{
"name": "dual-stack-group-name",
"desc": "Name of the globally configured dual-stack group."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement in the configuration. | Statement introduced in Junos OS Release 17.3R1. | [
"Single-Session DHCP Dual-Stack Overview",
"Configuring Single-Session DHCP Dual-Stack Support"
] |
dual-stack (DHCP Relay Agent Overrides) | dual-stack dual-stack-group-name; | [edit forwarding-options dhcp-relay overrides],
[edit forwarding-options dhcp-relay dhcpv6 overrides],
[edit forwarding-options dhcp-relay dhcpv6 group group-name overrides],
[edit forwarding-options dhcp-relay dhcpv6 group group-name interface interface-name overrides],
[edit forwarding-options dhcp-relay group group-... | Assigns the specified dual-stack group to both legs (DHCP and DHCPv6) of the DHCP dual stack. The
dual-stack group defines the common configuration settings for DHCP and DHCPv6 subscribers on both
legs. These settings take precedence over all other configurations, such as those specified in global,
group, or interface ... | [
{
"name": "dual-stack-group-name",
"desc": "Name of the globally configured dual-stack group."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement in the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Single-Session DHCP Dual-Stack Overview",
"Configuring Single-Session DHCP Dual-Stack Support"
] |
dual-stack-group (DHCP Local Server) | dual-stack-group name {
access-profile access-profile;
authentication {
password password-string;
username-include {
circuit-type;
delimiter delimiter-character;
domain-name domain-name-string;
interface-description (device-interface | logical-int... | [edit logical-systems name routing-instances name system services dhcp-local-server],
[edit logical-systems name system services dhcp-local-server],
[edit routing-instances name system services dhcp-local-server],
[edit system services dhcp-local-server] | Specifies common configuration settings that are used for both legs (DHCP and DHCPv6) of the DHCP
local server dual-stack, and names the dual-stack group.
When applied, the dual-stack configuration takes precedence over all other configurations, such as
those specified in global, group, or interface settings. | [
{
"name": "name",
"desc": "Name of the dual-stack group. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement in the configuration. | Statement introduced in Junos OS Release 17.3R1. | [
"Single-Session DHCP Dual-Stack Overview",
"DHCP Liveness Detection Using ARP and Neighbor Discovery Packets",
"Configuring RADIUS Reauthentication for DHCP Subscribers",
"RADIUS Reauthentication As an Alternative to RADIUS CoA for DHCP Subscribers"
] |
dual-stack-group (DHCP Relay Agent) | dual-stack-group name {
access-profile profile-name;
authentication {
password password-string;
username-include {
circuit-type;
delimiter delimiter-character;
domain-name domain-name-string;
interface-description (device-interface | logical-inter... | [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] | Specifies common configuration settings that are used for both legs (DHCP and DHCPv6) of the DHCP
dual stack, and names the dual stack group.
The group is assigned to each leg of the DHCP dual-stack with the "dual-stack" on page 6316 statement
in the overrides stanza. When applied, the dual-stack configuration takes pr... | [
{
"name": "name",
"desc": "Name of the dual-stack group. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement in the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Single-Session DHCP Dual-Stack Overview",
"Configuring Single-Session DHCP Dual-Stack Support",
"DHCP Liveness Detection Using ARP and Neighbor Discovery Packets"
] |
dual-stack-interface-client-limit (DHCP Local Server and Relay Agent) | dual-stack-interface-client-limit number; | [edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name],
[edit logical-systems name forwarding-options dhcp-relay dual-stack-group dual-stack-group-name],
[edit logical-systems name routing-instances name forwarding-options dhcp-relay dual-stack-group
dual-stack-group-name],
[edit logical-systems n... | Limit the number of clients allowed on an interface.
NOTE: For dual-stack subscribers, always use this statement instead of the "interface-
client-limit" on page 9410 (DHCP Relay Agent) or "interface-client-limit" on page 9407
(DHCP Local Server) statements. | [
{
"name": "number",
"desc": "Maximum number of dual-stack subscribers that can log in per interface. Range: 1 through 500,000"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R1. | [
"Single-Session DHCP Dual-Stack Overview"
] |
dual-transport | dual-transport {
inet-lsr-id inet-lsr-id;
inet6-lsr-id inet6-lsr-id;
} | [edit protocols ldp] | Configure to allow Junos LDP to establish the TCP connection over IPv4 with IPv4 neighbors, and over
IPv6 with IPv6 neighbors as a single-stack LSR. inet-lsr-id and inet6-lsr-id are the two LSR IDs that have
to be configured to establish an LDP session over IPv4 and IPv6 TCP transport. These two IDs should be
non-zero ... | [
{
"name": "inet-lsr-id inet-lsr-id",
"desc": "Configure the LSR ID to establish an LDP session over IPv4 TCP transport."
},
{
"name": "inet6-lsr-id inet6-lsr-id",
"desc": "Configure the LSR ID to establish an LDP session over IPv6 TCP transport."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"LDP Native IPv6 Support Overview",
"Example: Configuring LDP Native IPv6 Support",
"Configuring LDP Native IPv6 Support"
] |
dualstack-support (JSRC) | dualstack-support; | [edit jsrc] | Configure JSRC provisioning for dual-stack subscribers so that it reports information about the separate
stacks for a given subscriber, using a single JSRC session. By default (and in all cases for releases earlier
than Junos OS Release 18.1R1), the DHCPv4 and DHCPv6 stacks are treated as a single subscriber; the
remo... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"JSRC Configuration Overview"
] |
dump-on-flow-control | dump-on-flow-control; | [edit interfaces interface-name multiservice-options] | This option supports high availability functionality and can be used with various service interfaces,
including rsp, rms, lsq, and rlsq. | [] | 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 Multiservice Physical Interface Properties",
"Junos OS Services Interfaces Library for Routing Devices"
] |
duplicate-clients (DHCPv6 Local Server and Relay Agent) | duplicate-clients incoming-interface; | [edit forwarding-options dhcp-relay dhcpv6],
[edit logical-systems logical-system-name ...],
[edit logical-systems logical-system-name routing-instances routing-instance-name ...],
[edit routing-instances routing-instance-name ...],
[edit system services dhcp-local-server dhcpv6] | Specify the criteria that the jdhcpd process uses to support duplicate clients. The router uses the
additional criteria to distinguish between the duplicate clients.
Duplicate clients have the same DUID (DHCP unique identifier). Typically, the router treats a request
from a duplicate client as a renegotiation, and repl... | [
{
"name": "incoming-interface",
"desc": "Allow duplicate clients when the incoming DHCPv6 requests are received over different underlying interfaces."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"DHCPv6 Duplicate Client DUIDs",
"Configuring the Router to Use Underlying Interfaces to Distinguish Between DHCPv6 Duplicate",
"Client DUIDs"
] |
duplicate-clients-in-subnet (DHCP Local Server and DHCP Relay Agent) | duplicate-clients-in-subnet (incoming-interface | option-82); | [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],
[edit logical-... | 16.1R5
Starting in Junos OS Release 16.1R5, 16.2R2, 17.1R2, and 17.2R1, only the ACI (suboption 1) and ARI
(suboption 2) are used. Other suboptions, such as Vendor-Specific (suboption 9) are ignored. | [
{
"name": "incoming-interface",
"desc": "Use the incoming interface information in packets to differentiate between duplicate clients."
},
{
"name": "option-82",
"desc": "Use the option 82 information to differentiate between duplicate clients. Starting in Junos OS Release 16.1R5, 16.2R2, 17.1R2... | 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.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"DHCPv4 Duplicate Client In Subnet Overview",
"Guidelines for Configuring Support for DHCPv4 Duplicate Clients",
"Configuring the Router to Distinguish Between DHCPv4 Duplicate Clients Based on Their Incoming",
"Interfaces",
"Configuring the Router to Distinguish Between DHCPv4 Duplicate Clients Based on Op... |
duplicate-mac-detection | duplicate-mac-detection {
action (block | no-mac-suppression | shutdown);
auto-recovery-time minutes;
auto-recovery-time-seconds seconds;
detection-threshold detection-threshold;
detection-window seconds;
exclude-list exclude-list;
include-local-moves;
} | [edit logical-systems logical-systems-name protocols evpn],
[edit logical-systems logical-systems-name routing-instances routing-instance-name protocols evpn],
[edit protocols evpn],
[edit routing-instances routing-instance-name protocols evpn] | Configure duplicate MAC address detection settings. You can configure a threshold for MAC address
mobility events and the window for detecting the number of MAC address mobility events. In addition,
you can configure the optional recovery time that the Juniper Networks device waits before the
duplicate MAC address is u... | [
{
"name": "action",
"desc": "Block the duplicate MAC address. You can also shut down the duplicate MAC address's corresponding local interface."
},
{
"name": "block",
"desc": "When the device detects a duplicate MAC address, the device blocks the"
},
{
"name": "no-mac-suppression",
"... | routing | Statement introduced in Junos OS Release 17.4R1.
exclude-list statement introduced in Junos OS Release 25.2R1 and Junos OS Evolved Release 25.2R1. | [
"Overview of MAC Mobility",
"Changing Duplicate MAC Address Detection Settings",
"Configuring Loop Detection for Duplicate MAC Addresses",
"EVPN Duplicate MAC Detection Exclusion Lists"
] |
duplicate-protection (Dynamic PPPoE) | duplicate-protection {
include {
relay-session-id;
}
} | [edit dynamic-profiles name interfaces name unit name family pppoe],
[edit dynamic-profiles name interfaces name unit name pppoe-underlying-options],
[edit dynamic-profiles name interfaces interface-set name pppoe-underlying-options],
[edit interfaces name unit name family pppoe],
[edit interfaces name unit name pppoe-... | Prevent the activation of another dynamic PPPoE logical interface on the same underlying interface
when a dynamic PPPoE logical interface for a client with the same media access control (MAC) address
is already active on that interface. Duplicate protection is disabled by default. Enabling duplicate
protection has no e... | [
{
"name": "include",
"desc": "(Optional) Configure include relay-session-id option to allow multiple PPPoE sessions from the same source MAC address. Service Provider deployments with multi-service access nodes (MSANs) that do not support agent circuit identifier (ACI) or agent remote identifier (ARI) inser... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1.
Support for the [edit ... family pppoe] hierarchies introduced in Junos OS Release 11.2.
Support for the include relay-session-id introduced in Junos OS Release 25.2R1. | [
"Configuring an Underlying Interface for Dynamic PPPoE Subscriber Interfaces",
"Configuring the PPPoE Family for an Underlying Interface",
"Configuring Lockout of PPPoE Subscriber Sessions",
"Dynamic PPPoE Subscriber Interfaces over Static Underlying Interfaces Overview"
] |
duplicates-dropped-periodicity | duplicates-dropped-periodicity seconds; | [edit services dynamic-flow-capture capture-group client-name] | Specify the frequency for sending notifications to affected control sources when transmission of
duplicate sets of data is restricted because the max-duplicates threshold has been reached. | [
{
"name": "seconds",
"desc": "Period for sending DuplicatesDropped notifications."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Limiting the Number of Duplicates of a Packet"
] |
duplication (Access Profile) | duplication; | [edit access profile profile-name accounting] | Configure the router to send accounting reports to both the RADIUS accounting server configured in
the access profile for the wholesaler and the RADIUS accounting server configured in the access profile
for the retailer.
Default
The router sends accounting reports to the accounting servers that are in the context in wh... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Configuring Authentication and Accounting Parameters for Subscriber Access",
"Understanding RADIUS Accounting Duplicate Reporting"
] |
duplication-filter (Access Profile) | duplication-filter (interim-duplicated | interim-original) <exclude-attributes>; | [edit access profile profile-name accounting] | Configure which accounting servers receive accounting messages when RADIUS duplication accounting
is configured in the access profile. | [
{
"name": "exclude-attributes",
"desc": "(Optional) Filter RADIUS attributes from duplicated accounting interim messages based on the exclude statement configuration in the corresponding duplication access profile. You can configure exclude-attributes alone, or with interim-duplicated or interim-original."
... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Authentication and Accounting Parameters for Subscriber Access",
"Understanding RADIUS Accounting Duplicate Reporting",
"Configuring Duplication Filters for RADIUS Accounting Duplicate Reporting",
"Configuring Per-Subscriber Session Accounting"
] |
duplication-vrf (Duplicate Accounting) | duplication-vrf {
access-profile-name profile-name;
vrf-name vrf-name;
} | [edit access profile profile-name accounting] | Configure the router to send duplicate accounting information to the RADIUS accounting servers
defined in up to five access profiles all in the same nondefault VRF (LS:RI combination).
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax sec... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3R3 and supported in later 12.3Rx releases.
Statement supported in Junos OS Release 13.2 and later releases. (Not supported in Junos OS Release
13.1.) | [
"Understanding RADIUS Accounting Duplicate Reporting",
"Configuring Authentication and Accounting Parameters for Subscriber Access"
] |
duration (PoE) | duration hours; | [edit poe interface (all | interface-name) telemetries] | Modifies the duration for which telemetry records are stored. If telemetry logging continues beyond the
specified duration, the older records are discarded one by one as new records are collected. | [
{
"name": "hours",
"desc": "Hours for which telemetry data should be retained."
}
] | 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. | [] |
duration | duration hours; | [edit poe interface (all | interface-name) telemetries] | Modify the duration over which data is collected when you are monitoring the power consumption of a
PoE interface. | [
{
"name": "hours",
"desc": "Number of hours over which the data is to be collected."
}
] | 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 PoE Interfaces with Different Priorities on an EX Series Switch",
"Configuring PoE Interfaces on EX Series Switches"
] |
dvmrp | dvmrp {
disable;
export [ policy-names ];
import [ policy-names ];
interface interface-name {
disable;
hold-time seconds;
metric metric;
mode (forwarding | unicast-routing);
}
rib-group group-name;
traceoptions {
file filename <files number> <size siz... | [edit logical-systems logical-system-name protocols],
[edit protocols] | 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... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | NOTE: Distance Vector Multicast Routing Protocol (DVMRP) was deprecated in Junos
OS Release 16.1. Although DVMRP commands continue to be available and configurable
in the CLI, they are no longer visible and are scheduled for removal in a subsequent
release.
Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring DVMRP"
] |
dynamic (Security) | dynamic {
connections-limit number;
distinguished-name {
container container-string;
wildcard wildcard-string
}
general-ikeid;
hostname domain-name;
ike-user-type (group-ike-id | shared-ike-id);
inet ip-address;
inet6 ipv6-address;
reject-duplicate-connection;
us... | [edit security ike gateway gateway-name] | Specify the identifier for the remote gateway with a dynamic IPv4 or IPv6 address. Use this statement to
set up a VPN with a gateway that has an unspecified IPv4 or IPv6 address. | [
{
"name": "connections-limit",
"desc": "Configure the number of concurrent connections that the group profile supports. When the maximum number of connections is reached, no more dynamic virtual private network (VPN) endpoints dialup users attempting to access an IPsec VPN are allowed to begin Internet Key ... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 8.5. Support for the inet6 option added in Junos OS Release
11.1.
general-ikeid option under [edit security ike gateway gateway-name dynamic] hierarchy is introduced in Junos
OS Release 21.1R1. | [
"IPsec Overview",
"Example: Configuring AutoVPN with Pre-Shared Key"
] |
dynamic (services) | dynamic {
ike-policy policy-name;
ipsec-policy policy-name;
} | [edit services ipsec-vpn rule rule-name term term-name then] | Define a dynamic IPsec SA. | [
{
"name": "ike-policy policy-name",
"desc": "Name of the IKE policy. This statement is optional for the non-preshared-key"
},
{
"name": "ipsec-policy policy-name",
"desc": "Name of the IPsec policy. This statement is optional and the default policy is"
}
] | 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 Security Associations"
] |
dynamic (Source Packet Routing) | dynamic {
protected {
mandatory;
}
unprotected {
mandatory;
}
} | [edit protocols source-packet-routing segment-list] | Enable dynamic computation of segment routing label-switched paths (LSPs) based on tunnel
destination and translation service to fetch the corresponding segment identifiers (SIDs).
NOTE:
When the dynamic statement is enabled, all the next hops must have an IP address assigned as a
minimum configuration. In the case of... | [
{
"name": "protected",
"desc": "(Optional) Ensures a protected adjacency SID is used for the links of the LSP."
},
{
"name": "unprotected",
"desc": "(Optional) Ensures an unprotected adjacency SID is used for the links of the LSP."
},
{
"name": "mandatory",
"desc": "(Optional) Enable... | routing | Statement introduced in Junos OS Release 19.2R1. | [
"Understanding Static Segment Routing LSP in MPLS Networks"
] |
dynamic | dynamic {
ipsec-policy ipsec-policy-name;
replay-window-size (32 | 64);
} | [edit security ipsec security-association name] | Define a dynamic IPsec SA. | [
{
"name": "ipsec-policy ipsec-policy-name",
"desc": "Name of the IPsec policy."
},
{
"name": "replay-window-size",
"desc": "(Optional) Antireplay window size. It can be one of the following values:"
},
{
"name": "32",
"desc": "32-packet window size."
},
{
"name": "64",
"d... | 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 Dynamic IPsec Security Associations",
"Associating the Configured Security Association with a Logical Interface"
] |
dynamic-address | dynamic-address {
address-name name {
description description;
profile {
category name {
feed feed;
property name {
string name;
}
}
feed-name name;
}
session-scan;
}
feed... | [edit security]
[edit logical-systems logical-system-name security]
[edit tenants tenant-name security ] | 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": "address-name",
"desc": "Security dynamic address name."
},
{
"name": "feed-server",
"desc": "Security dynamic address feed-server. Starting with Junos OS Release 25.2R1, you can authenticate dynamic address feed servers before downloading feeds into the SRX Series devices and vSRX 3.0... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R1. | [] |
dynamic-application (Security Policies) | dynamic-application dynamic-application-name | dynamic-application-group-name | any | none; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name match]
[edit security policies global policy policy-name match] | Specify the dynamic applications or dynamic application groups used as match criteria within a security
policy.
By adding dynamic applications to the match criteria, the data traffic is classified based on the Layer 7
application inspection results. Application Identification (AppID) identifies dynamic or real-time Lay... | [
{
"name": "dynamic-application-",
"desc": ""
},
{
"name": "name |",
"desc": ""
},
{
"name": "dynamic-application-",
"desc": ""
},
{
"name": "group-name",
"desc": "Specify dynamic applications or dynamic application groups. Examples for dynamic applications or dynamic appl... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Unified Security Policies",
"Application Identification Support for Unified Policies",
"Example: Configure Application Firewall with Unified Policy"
] |
dynamic-application (Security) | dynamic-application {
profile profile name {
redirect-message {
type {
custom-text {
content content;
}
redirect-url {
content content;
}
}
}
}
traceoptions {
... | [edit security] | 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... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Application Identification Support for Unified Policies"
] |
dynamic-application | dynamic-application [system-application]; | [edit security application-firewall rule-sets rule-set-name rule rule-name match] | Specify the dynamic application names for match criteria in application firewall rule set.
An application firewall configuration permits, rejects, or denies traffic based on the application of the
traffic. The AppFW consists of one or more rule sets with rules that specify match criteria, including
dynamic applications... | [
{
"name": "system-application",
"desc": "Set of system applications for match criteria."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Application Firewall Overview"
] |
dynamic-application-group | dynamic-application-group [system-application-group]; | [edit security application-firewall rule-sets rule-set-name rule rule-name match] | Specify the dynamic application group to match. When you define application firewall rules, you can
specify dynamic application groups as match criteria.
With application identification, multiple applications can be configured in a dynamic application groups
for consistent reuse. AppFW rules permit and deny traffic by ... | [
{
"name": "system-application-group",
"desc": "Set of groups defining one or more system applications for match criteria."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Application Firewall Overview"
] |
dynamic-attack-group | dynamic-attack-group name {
filters {
age-of-attack
{
greater-than value;
less-than value;
}
category (Security Dynamic Attack Group) {
values [ values ... ];
}
cvss-score
{
greater-t... | [edit security idp]
[edit tenants tenant-name security idp] | Configure a dynamic attack group. A dynamic attack group selects its members based on the filters
specified in the group. Therefore, the list of attacks is updated (added or removed) when a new signature
database is used. | [
{
"name": "dynamic-attack-group-name",
"desc": "Name of the dynamic attack group."
}
] | 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.
The expression option added in Junos OS Release 11.4.
Additional tags under filters of dynamic attack groups (CVSS score, age-of-attack, file-type, vulnerability-
type) are added in Junos OS Release 18.2R1 for dynamic attacks grouping of IDP signatures. The
Product and Vend... | [] |
dynamic-attack-groups (Security IDP) | dynamic-attack-groups attack-group-name; | [edit security idp idp-policy policy-name rulebase-exempt rule rule-name match attacks]
[edit security idp idp-policy policy-name rulebase-ips rule rule-name match attacks] | Specify a name for the dynamic attack group. | [
{
"name": "attack-group-name",
"desc": "Name of the dynamic attack group."
}
] | 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. | [] |
dynamic-bidirectional-transport | dynamic-bidirectional-transport {
template template;
} | [edit protocols rsvp peer-interface peer-interface-name] | Enable the dynamic setup of associated bidirectional packet LSP for transporting non-packet
Generalized Multiprotocol Label Switching (GMPLS) label-switched path (LSP). | [
{
"name": "template template",
"desc": "Name of the template for the dynamic bidirectional packet LSP."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
dynamic-class-of-service-options (Dynamic Traffic Shaping) | dynamic-class-of-service-options {
vendor-specific-tags tag;
} | [edit dynamic-profiles profile-name class-of-service] | Configure CoS attributes applied to dynamic interfaces or interface sets based on access line
information received in PPPoE discovery packets on dynamic subscriber interfaces. The packets convey
the information in PPPoE-IA tags. | [
{
"name": "vendor-specific-tags tag",
"desc": "Specify one or more of the following PPPoE-IA tags to set CoS attributes:"
},
{
"name": "access-loop-encapsulation",
"desc": "Set the overhead-accounting CoS attribute based on the Access-Loop-Encapsulation tag (0x91). The tag enables the router to ... | 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.
apply-to-interface-set option added in Junos OS Release 19.3R1. | [
"Setting Shaping Rate and Overhead Accounting Based on PPPoE Vendor-Specific Tags",
"Configuring the Shaping Rate and Overhead Accounting Based on PPPoE Vendor-Specific Tags on",
"Dynamic Subscriber Interfaces",
"Bandwidth Management for Downstream Traffic in Edge Networks Overview"
] |
dynamic-db | dynamic-db; | [edit logical-systems logical-system-name policy-options as-path path-name],
[edit logical-systems logical-system-name policy-options as-path-group group-name],
[edit logical-systems logical-system-name policy-options community community-name],
[edit logical-systems logical-system-name policy-options condition conditio... | Define routing policies and policy objects that reference policies configured in the dynamic database at
the [edit dynamic] hierarchy level. | [] | routing—To view this statement in the configuration.
routing-control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Example: Configuring Dynamic Routing Policies"
] |
dynamic-dns | dynamic-dns {
client hostname {
agent agent-name;
interface interface-name;
password server-password;
server server-name;
username user-name;
}
} | [edit system services] | Configure the device as a dynamic DNS server that maintains the list of the changed addresses and their
associated domain names registered with it. The device updates these DDNS servers with this
information periodically or whenever there is a change in IP addresses. | [
{
"name": "client",
"desc": "Specifies the hostname of the registered client."
},
{
"name": "agent",
"desc": "Specifies the name of the dynamic DNS agent."
},
{
"name": "interface",
"desc": "Specifies the interface whose IP address is mapped to the registered domain name."
},
{
... | 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. | [
"DNS Overview"
] |
dynamic-filter | dynamic-filter; | [edit services security-metadata-streaming policy] | Configure dynamic filtering options for security metadata streaming policy on SRX Series Firewalls.
Security metadata streaming policy sends the metadata and connection patterns of a IoT device traffic to
Juniper Networks ATP Cloud. Juniper ATP Cloud uses the streamed data to get details such as brand,
device model, cl... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.1R1 on SRX Series Firewalls with Juniper Advanced
Threat Prevention Cloud (Juniper ATP Cloud). | [] |
dynamic-flow-capture | dynamic-flow-capture {
capture-group client-name {
content-destination identifier {
address address;
hard-limit bandwidth;
hard-limit-target bandwidth;
soft-limit bandwidth;
soft-limit-clear bandwidth;
ttl hops;
}
contr... | [edit services] | Define the dynamic flow capture properties to be applied to traffic.
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 in Junos OS Release 7.4. | [
"Understanding Junos Capture Vision"
] |
dynamic-load-balance | dynamic-load-balance | [edit firewall family firewall filter family name filter firewall filter name term term name
then] | Selectively enable or disable dynamic load balancing based on rdma-opcode match or any match available
in firewall filters. Available for INET, INET6, and ethernet-switching firewall filter families, the mode of
selective dynamic load balancing depends on the global dynamic load balancing setting, which could be
per pe... | [
{
"name": "1. enable - Enable dynamic load balancing",
"desc": ""
},
{
"name": "2. disable- Disable dynamic load balancing",
"desc": ""
}
] | firewall - To view this statement in the configuration
firewall-control - To add this statement to the configuration | Statement introduced in Junos OS Evolved Release 24.1R1. | [
"Dynamic Load Balancing (DLB)"
] |
dynamic-peers | dynamic-peers; | [edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name],
[edit protocols rip group group-name neighbor neighbor-name] | Configure an interface to have dynamic peers in a point-to-multipoint RIP network. | [] | 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. | [
"Example: Configuring Point-to-Multipoint RIP Networks"
] |
dynamic-policy-control | dynamic-policy-control {
pcc-rules {
[rule-name number];
}
pcc-rulebases {
[rulebase-name];
}
diameter-profile gx-profile-name;
} | [edit unified-edge pcef profiles profile-name] | Configure the dynamic policy control for the PCC rules, PCC rulebases, or both in a PCEF profile. You
can configure a maximum of 32 PCC rules in a PCEF profile. There is no limit to the number of PCC
rulebases you can configure in a PCEF profile.
NOTE: If you configure the dynamic-policy-control statement for a PCEF pr... | [] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring a Policy and Charging Enforcement Function Profile for Junos OS Subscriber Aware",
"Dynamic Policies",
"Understanding How Subscriber-Aware Policy and Charging Control Rules Are Provisioned",
"Dynamically by a PCRF"
] |
dynamic-pool | dynamic-pool <dynamic-pool>{
family {
inet6 {
from-interface <interface>;
delegated-prefix-length <network-prefix-length>;
range <range-name> {
masked-low <masked-low>;
masked-high <masked-high>;
prefix-length <prefix-length... | [edit access address-assignment (Access)] | Configure the dynamic pool updated by the client running on the WAN interface. | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D70. | [
"address-assignment (Access)",
"IP Address Assignment Pool"
] |
dynamic-profile (Demux) | dynamic-profile profile-name {
network ip-address {
range name {
low lower-limit;
high upper-limit;
}
}
} | [edit interfaces interface-name unit unit-number demux inet auto-configure address-ranges]
[edit interfaces interface-name unit unit-number demux inet6 auto-configure address-ranges] | Assign a dynamic profile and specify address options for the demultiplexing (demux) interface options. | [
{
"name": "profile-name",
"desc": "Name of the dynamic profile for the demultiplexing (demux) interface options."
},
{
"name": "network ip-address",
"desc": "Configure an IPv4 or IPv6 address for a dynamic profile for the demultiplexing (demux) interface options."
},
{
"name": "range <ra... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"IP Demultiplexing Interfaces on Packet-Triggered Subscribers Services Overview",
"Configuring Packet Triggered Subscribers Using IP Demux Interfaces in Dynamic Profiles"
] |
dynamic-profile (DHCP Local Server) | dynamic-profile profile-name {
aggregate-clients (merge | replace);
use-primary primary-profile-name;
} | [edit system services dhcp-local-server],
[edit system services dhcp-local-server dual-stack-group dual-stack-group-name],
[edit system services dhcp-local-server dhcpv6],
[edit system services dhcp-local-server dhcpv6 group group-name],
[edit system services dhcp-local-server dhcpv6 group group-name interface interfac... | Specify the dynamic profile that is attached to all interfaces, a named group of interfaces, or a specific
interface. | [
{
"name": "profile-name",
"desc": "Name of the dynamic profile."
}
] | 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.
Options aggregate-clients and use-primary introduced in Junos OS Release 9.3.
Support at the [edit ... interface] hierarchy levels introduced in Junos OS Release 11.2. | [
"Attaching Dynamic Profiles to DHCP Subscriber Interfaces or DHCP Client Interfaces",
"Configuring a Default Subscriber Service"
] |
dynamic-profile (DHCP Relay Agent) | dynamic-profile profile-name {
aggregate-clients (merge | replace);
use-primary primary-profile-name;
} | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit forwarding-options dhcp-relay dhcpv6 group group-name],
[edit forwarding-options dhcp-relay dhcpv6 group group-name interface interface-name],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name],
[edit forwa... | Specify the dynamic profile that is attached to all interfaces, to a named group of interfaces, or to a
specific interface.
M120 and M320 routers do not support DHCPv6. | [
{
"name": "profile-name",
"desc": "Name of the dynamic profile."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4.
Support at the [edit ... dual-stack-group dual-stack-group-name] hierarchy level introduced in Junos OS
Release 15.1. | [
"Attaching Dynamic Profiles to DHCP Subscriber Interfaces or DHCP Client Interfaces",
"Grouping Interfaces with Common DHCP Configurations",
"Configuring a Default Subscriber Service"
] |
dynamic-profile (Domain Map) | dynamic-profile profile-name; | [edit access domain map domain-map-name] | Dynamic profile that is used for subscriber sessions associated with the domain map. | [
{
"name": "profile-name",
"desc": "Name of dynamic profile."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Specifying a Dynamic Profile in a Domain Map"
] |
dynamic-profile (Dynamic Access-Line-Identifier VLANs) | dynamic-profile profile-name; | [edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit auto-configure line-identity],
[edit interfaces interface-name unit logical-unit-number auto-configure line-identity] | Attach a dynamic profile to a static or dynamic underlying VLAN interface to create a dynamic VLAN on
the interface, based on receiving a trusted option in the DHCP or PPPoE discovery packet. The trusted
option can be the ACI, ARI, both ACI and ARI, or neither. The VLAN is known as an access-line-identifier
VLAN. | [
{
"name": "profile-name",
"desc": "Name of the dynamic profile."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS 17.1. | [
"Configuring Dynamic Underlying VLAN Interfaces to Use Access-Line Identifiers",
"Configuring Dynamic VLAN Subscriber Interfaces Based on Access-Line Identifiers"
] |
dynamic-profile (Dynamic ACI VLANs) | dynamic-profile profile-name; | [edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit auto-configure agent-circuit-identifier],
[edit interfaces interface-name unit logical-unit-number auto-configure agent-circuit-identifier] | Attach a dynamic profile for an agent circuit identifier (ACI) interface set to a static or dynamic
underlying VLAN interface. | [
{
"name": "profile-name",
"desc": "Name of the dynamic profile that defines the ACI interface set."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring Dynamic Underlying VLAN Interfaces to Use Agent Circuit Identifier Information",
"Configuring Static Underlying VLAN Interfaces to Use Agent Circuit Identifier Information"
] |
dynamic-profile (Dynamic PPPoE) | dynamic-profile profile-name; | [edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family pppoe],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
pppoe],
[edit interfaces interface-name unit logical-unit-number family pppoe],
[edit interfaces interface-name unit logical-unit-... | Attach a PPPoE dynamic profile to an underlying Ethernet interface. This underlying interface is
configured with either the encapsulation ppp-over-ether statement or the family pppoe statement; the two
statements are mutually exclusive. When the router creates a dynamic PPPoE logical interface on the
underlying interfa... | [
{
"name": "profile-name",
"desc": "Name of a previously configured PPPoE dynamic profile, up to 64 characters in length,"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1.
Support for the [edit ... family pppoe] hierarchies introduced in Junos OS Release 11.2. | [
"Configuring an Underlying Interface for Dynamic PPPoE Subscriber Interfaces",
"Configuring the PPPoE Family for an Underlying Interface",
"Dynamic PPPoE Subscriber Interfaces over Static Underlying Interfaces Overview"
] |
dynamic-profile (L2TP) | dynamic-profile profile-name; | [edit services l2tp tunnel-group name] | Assign a dynamic profile to the tunnel group for dynamic LNS sessions. | [
{
"name": "profile-name",
"desc": "Name of the dynamic profile for the tunnel group."
}
] | 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"
] |
dynamic-profile (PPP) | dynamic-profile profile-name; | [edit interfaces interface-name unit logical-unit-number ppp-options] | Specify the dynamic profile that is attached to the interface. On the MX Series routers, this statement is
supported on PPPoE interfaces only. | [] | 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.
Support for MLPPP on LSQ interfaces introduced in Junos OS Release 10.2. | [
"Dynamic Profiles Overview",
"Configuring a Basic Dynamic Profile",
"Attaching Dynamic Profiles to Static PPP Subscriber Interfaces",
"Attaching Dynamic Profiles to MLPPP Bundles",
"Hardware Requirements for PPP Subscriber Services on Non-Ethernet Interfaces"
] |
dynamic-profile (PPPoE Service Name Tables) | dynamic-profile profile-name; | [edit protocols pppoe service-name-tables table-name service service-name],
[edit protocols pppoe service-name-tables table-name service service-name agent-specifier aci
circuit-id-string ari remote-id-string] | Specify a dynamic profile to instantiate a dynamic PPPoE interface. You can associate a dynamic profile
with a named service entry, empty service entry, or any service entry configured in a PPPoE service name
table, or with an agent circuit identifier/agent remote identifier (ACI/ARI) pair defined for these services.
T... | [
{
"name": "profile-name",
"desc": "Name of the dynamic profile that the router uses to instantiate a dynamic PPPoE interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring PPPoE Service Name Tables",
"Assigning a Dynamic Profile and Routing Instance to a Service Name or ACI/ARI Pair for Dynamic",
"PPPoE Interface Creation"
] |
dynamic-profile (Stacked VLAN) | dynamic-profile profile-name {
accept (any | dhcp-v4 |dhcp-v6| inet | inet6 | pppoe);
access-profile vlan-dynamic-profile-name;
ranges (any | low-tag–high-tag),(any | low-tag–high-tag);
} | [edit interfaces interface-name auto-configure stacked-vlan-ranges] | Configure a dynamic profile for use when configuring dynamic stacked VLANs. | [
{
"name": "profile-name",
"desc": "Name of the dynamic profile that you want to use when configuring dynamic stacked"
}
] | 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. | [
"Dynamic Profiles Overview",
"Configuring a Basic Dynamic Profile",
"Configuring an Interface to Use the Dynamic Profile Configured to Create Stacked VLANs"
] |
dynamic-profile (Static Subscribers) | dynamic-profile profile-name {
aggregate-clients (merge | replace);
} | [edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers],
[edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers group group-name],
[edit logical-systems logical-system-name system services sta... | Specify the dynamic client profile that is instantiated at login and de-instantiated at logout for all static
subscribers on interfaces configured at the [edit system services static-subscribers interface] hierarchy
level or for the static subscribers in a specific group. The group version of the statement takes
preced... | [
{
"name": "profile-name",
"desc": "Name of the dynamic client profile profile."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Subscribers over Static Interfaces Configuration Overview",
"Specifying the Static Subscriber Global Dynamic Profile",
"Specifying the Static Subscriber Group Dynamic Profile"
] |
dynamic-profile (VLAN) | dynamic-profile profile-name {
accept (any | dhcp-v4 |dhcp-v6| inet | inet6 | pppoe);
accept-out-of-band protocol;
access-profilevlan-dynamic-profile-name;
ranges (any | low-tag)–(any | high-tag);
} | [edit interfaces interface-name auto-configure vlan-ranges] | Configure a dynamic profile for use when configuring dynamic VLANs. | [
{
"name": "profile-name",
"desc": "Name of the dynamic profile that you want to use when configuring dynamic VLANs."
}
] | 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. | [
"Dynamic Profiles Overview",
"Configuring a Basic Dynamic Profile",
"Configuring an Interface to Use the Dynamic Profile Configured to Create Single-Tag VLANs"
] |
dynamic-profile-options | dynamic-profile-options {
versioning;
} | [edit system] | Configure global dynamic profile options.
The remaining statement is explained separately. Search for a statement in CLI Explorer or click a linked
statement in the Syntax section for details. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Versioning for Dynamic Profiles"
] |
dynamic-profiles | dynamic-profiles {
profile-name {
class-of-service {
dynamic-class-of-service-options {
vendor-specific-tags tag;
}
interfaces {
interface-name ;
}
unit logical-unit-number {
classifiers {... | [edit] | Create dynamic profiles for use with DHCP or PPP client access. | [
{
"name": "profile-name",
"desc": "Name of the dynamic profile; string of up to 80 alphanumeric characters."
},
{
"name": "reassemble-packets",
"desc": "(Optional) Enables IPv4 reassembly of fragmented GRE packets conveyed across a soft GRE tunnel from a Wi-Fi access point to a Wi-Fi access gate... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Support at the filter, policer, hierarchical-policer, three-color-policer, and policy options hierarchy levels
introduced in Junos OS Release 11.4. | [
"Configuring a Basic Dynamic Profile",
"Configuring Dynamic VLANs Based on Agent Circuit Identifier Information",
"Dynamic Profiles for Subscriber Management"
] |
dynamic-requests | dynamic-requests {
routing-instance routing-instance-name;
source-address source-address;
source-port source-port;
} | [edit access radsec destination ] | Configure RADSEC clients to receive and process dynamic requests. RADSEC servers can be a source of
dynamic RADIUS requests such as Change of Authorization (CoA) and RADIUS-initiated disconnect
(RID) messages.
You must configure the IP address of the RADSEC server as the source address for the requests. You can
also sp... | [
{
"name": "routing-instance",
"desc": ""
},
{
"name": "routing-instance-name",
"desc": "Specify the routing instance name."
},
{
"name": "source-address ip-address",
"desc": "(Required) Configure the source IP address, which is the IP address of the RADSEC server. If the source addre... | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1. | [
"https://www.juniper.net/documentation/us/en/software/junos/user-access/topics/task/radsec-",
"configuring.html"
] |
dynamic-requests-secret (RADIUS Server) | dynamic-requests-secret password; | [edit access radius servers name] | Configure the secret password to be used for change of authorization requests from the RADIUS server.
Default
Use the same password that is used for authentication requests. | [
{
"name": "password",
"desc": "Password for dynamic requests."
}
] | 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 RADIUS Servers",
"Understanding Network Elements",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules"
] |
dynamic-server | dynamic-server {
group group-name {
neighbor-discovery-router-advertisement <ndra-pool>;
interface interface-name {
overrides {
delegated-pool <delegated-pool>;
ia-na-pool <ia-na-pool>;
interface-client-limit in... | [edit logical-systems name routing-instances name system services dhcp-local-server dhcpv6],
[edit logical-systems name system services dhcp-local-server dhcpv6],
[edit logical-systems name tenants name routing-instances name system services dhcp-local-server
dhcpv6],
[edit routing-instances name system services dhcp-... | Configure the server running on a LAN interface. | [
{
"name": "group group-name",
"desc": "Name of the group. neighbor-discovery-router-advertisement ndra-pool Name of the address-assignment pool used to assign the router advertisement prefix."
},
{
"name": "interface interface-name",
"desc": "Name of the interface."
},
{
"name": "ia-na-p... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D70. | [] |
dynamic-threshold-profile (CoS) | dynamic-threshold-profile {
profile-name {
ingress {
(priority-group < priority-group> dynamic-threshold dynamic-threshold | priority-
group-all dynamic-threshold dynamic-threshold);
}
}
} | [edit class-of-service] | You create a dynamic threshold profile by mapping dynamic thresholds (alpha values) to priority groups
for shared buffer pools. You then associate the dynamic threshold profile with an ingress interface to
enable per-interface level shared buffer allocation. | [
{
"name": "name",
"desc": "Dynamic threshold profile name"
},
{
"name": "priority-group",
"desc": "Select the priority group to apply a dynamic threshold to. This and the priority-group-all option are mutually exclusive. Range: 0-7"
},
{
"name": "priority-group-all",
"desc": "Apply t... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.4R1. | [] |
dynamic-threshold-profile (CoS Interfaces) | dynamic-threshold-profile profile-name; | [edit class-of-service interfaces interface-name] | Apply a dynamic threshold profile to a physical interface. You can create dynamic thresholds (alpha
values) per priority group for shared buffer pools and then associate the dynamic threshold profile with
an ingress interface. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.4R1. | [] |
dynamic-tunnel-gre-key | dynamic-tunnel-gre-key dynamic-tunnel-gre-key; | [edit routing-options dynamic-tunnels tunnel-attributes] | Enable traffic flow identification by configuring a GRE key that will be used to identify an individual
traffic flow in a GRE tunnel. RFC2890 describes the enhancements to the GRE header that includes the
key field and its use in identifying individual traffic flow in a tunnel. The encapsulating router uses the
GRE key... | [
{
"name": "dynamic-tunnel-gre-key",
"desc": "An identifier for a individual traffic flow within a GRE tunnel. Range: 1 through 4,294,967,295."
}
] | routing | Statement introduced in Junos OS Release 20.1R1 | [
"tunnel-attributes",
"show dynamic-tunnels database"
] |
dynamic-tunnel-reassembly | dynamic-tunnel-reassembly (off | on); | [edit logical-systems name routing-instances name routing-options dynamic-tunnels tunnel-attributes],
[edit logical-systems name routing-options dynamic-tunnels tunnel-attributes],
[edit logical-systems name tenants name routing-instances name routing-options dynamic-tunnels
tunnel-attributes],
[edit routing-instances... | Use this statement to enable or disable IPV6 fragment reassembly for forwarding Ipv4 traffic. You can
configure multiple tunnels and specify different attributes for each tunnel. Service providers with IPv6
infrastructure can configure individual tunnels for each customer to route IPv4 traffic. | [
{
"name": "off",
"desc": "Disable reassembly check"
},
{
"name": "on",
"desc": "Enable reassembly check. By default, this is disabled."
}
] | routing | Statement introduced in Junos OS Release 19.2R1. | [] |
dynamic-tunnels | dynamic-tunnels tunnel-name {
bgp-signal;
destination-networks prefix;
gre;
ipip
rsvp-te entry-name {
destination-networks network-prefix;
label-switched-path-template (Multicast) {
default-template;
template-name;
}
}
source-address address;... | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-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... | [
{
"name": "bgp-signal",
"desc": "Enable the creation of a tunnel signaled by BGP."
},
{
"name": "gre",
"desc": "Enable dynamic generic routing encapsulation type tunnel mode for IPv4. Values:"
},
{
"name": "next-hop-based-tunnel",
"desc": "Enable next hop base dynamic-tunnel for ste... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
bgp-signal option introduced in Junos OS Release 17.4R1.
srv6 option introduced in Junos OS Evolved Release 25.2R1. | [
"extended-nexthop",
"tunnel-attributes",
"Example: Configuring a Two-Tiered Virtualized Data Center for Large Enterprise Networks",
"Understanding Redistribution of IPv4 Routes with IPv6 Next Hop into BGP"
] |
dynamic-vpn | dynamic-vpn {
access-profile profile-name;
clients configuration-name {
ipsec-vpn vpn-name;
remote-exceptions ip-address/mask;
remote-protected-resources ip-address/mask;
user username;
user-groups user-group-name;
}
config-check;
force-upgrade;
interfac... | [edit security] | 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": "access-profile",
"desc": "Specify the access profile to use for Extended Authentication for remote users trying to download the Access Manager. This feature is supported on SRX300, SRX320, SRX340, SRX345, and SRX550HM devices."
},
{
"name": "clients",
"desc": "Create a client configur... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
config-check and interface options introduced in Junos OS Release 12.1X44-D10. | [
"Dynamic VPN Overview",
"E"
] |
e1-options (BITS Interfaces Signal Type) | e1-options {
framing (g704 | g704-no-cro4);
} | [edit chassis synchronization interfaces bits ] | Specify options for the E1 signal type for the building-integrated timing supply (BITS) interface. Valid
only if e1 is the signal-type configured at the [edit chassis synchronization source interfaces interface-name
bits signal-type] hierarchy. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"External Clock Synchronization Overview for ACX Series Routers",
"Configuring External Clock Synchronization for ACX Series Routers",
"Synchronous Ethernet Overview"
] |
e1-options (Clock Synchronization) | e1-options {
framing (g704 | g704-no-crc4);
line-encoding (ami | hdb3);
sabit bit;
} | [edit chassis synchronization interfaces external],
[edit chassis synchronization interfaces (external-0/0 | external-1/0)] | Configure the E1 interface options. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [] |
e2e-transparent | e2e-transparent; | [edit protocols ptp] | NOTE: If IGMP snooping is enabled on routers and switches that are configured with a
PTP Transparent Clock, the PTP devices will not perform an IGMP join on 224.0.1.129.
You will need to configure a static IGMP configuration in order to forward the PTP
traffic.
For example:
set protocols igmp-snooping vlan vlan-name in... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D25.
Statement introduced in Junos OS Release 20.1R1 EVO for QFX5220 devices
Statement introduced in Junos OS Release 24.2R1 EVO for QFX5130-48C devices | [
"Configuring Transparent Clock Mode for Precision Time Protocol"
] |
eapol-address (MACSec) | eapol-address (pae | provider-bridge | lldp-multicast | destination unicast-address); | [edit security macsec connectivity-association connectivity-association-name mka] | Configure an EAPoL destination MAC address. The eapol-address pae is the default configuration.
To establish a MACsec session, MACsec Key Agreement PDUs (MKPDUs) are sent or received between
nodes. These PDUs are Extensible Authentication Protocol over LAN (EAPoL) packets and, by default,
their destination MAC address ... | [
{
"name": "pae",
"desc": "The Port Access Entity option is mapped to MAC address 01:80:C2:00:00:03. Do not use if 802.1X authentication is configured on the provider network."
},
{
"name": "provider-bridge",
"desc": "The provider bridge option is mapped to MAC address 01:80:C2:00:00:00. Do not u... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1.
Option for destination unicast address introduced in Junos OS Release 19.3R1 for MX Series routers. | [
"Configuring Advanced MACsec Features"
] |
eapol-block | eapol-block {
captive-portal;
mac-radius;
server-fail <seconds>;
} | [edit logical-systems name protocols dot1x authenticator interface (all | interface-names)],
[edit logical-systems name protocols dot1x authenticator interface (all | interface-names) (server-
reject-bridge-domain | server-reject-vlan)],
[edit protocols dot1x authenticator interface (all | interface-names)],
[edit prot... | Enable the device to ignore Extensible Authentication Protocol over LAN (EAPoL)-Start messages
received from a client that has been authenticated so that the device does not trigger re-authentication.
The device typically attempts to restart the authentication procedure by contacting the authentication
server when it r... | [
{
"name": "captive-portal",
"desc": "Configure the device to ignore EAPoL-Start messages received from a client that has been authenticated using captive portal authentication."
},
{
"name": "mac-radius",
"desc": "Configure the device to ignore EAPoL-Start messages received from a client that ha... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2.
Support at the [edit protocols dot1x authenticator interface interface-name] hierarchy level introduced in
Junos OS Releases 14.1X53-D40 and 15.1X53-D51 for EX Series switches.
captive-portal and mac-radius introduced in Junos OS Release 17.2R1. | [
"Example: Configuring Fallback Options on EX Series Switches for EAP-TTLS Authentication and",
"Odyssey Access Clients"
] |
early-ageout | early-ageout seconds; | [edit security flow aging] | Define the value before the device aggressively ages out a session from its session table. | [
{
"name": "seconds",
"desc": "Amount of time that elapses before the device aggressively ages out a session."
}
] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Understanding Traffic Processing on Security Devices"
] |
east-interface | east-interface {
node-id mac-address;
control-channel channel-name {
vlan number;
interface name interface-name
}
interface-none
ring-protection-link-end;
} | [edit protocols protection-group ethernet-ring ring-name] | Define one of the two interface ports for Ethernet ring protection, the other being defined by the west-
interface statement at the same hierarchy level. The interface must use the control channel's logical
interface name. The control channel is a dedicated VLAN channel for the ring port.
EX Series switches do not use ... | [] | 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.
Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 14.153-D10 for QFX Series switches. | [
"Ethernet Ring Protection Switching Overview",
"Ethernet Ring Protection Using Ring Instances for Load Balancing",
"Example: Configuring Ethernet Ring Protection Switching on EX Series Switches",
"Example: Configuring Ethernet Ring Protection Switching on QFX Series and EX Series Switches",
"Supporting ELS"... |
echo-req | echo-req {
alarm-threshold (Security GPRS) {
forward number;
reverse number;
}
drop-threshold (Security GPRS) {
forward number;
reverse number;
}
} | [edit security gtp profile profile-name path-rate-limit message-type] | Configure the echo-req parameter to limit the number of packets per minute for the GPRS tunneling
protocol (GTP) echo request.
From Junos OS Release 20.4R1 onwards, the [edit security gprs gtp profile profile-name path-rate-limit
message-type] hierarchy level is replaced by [edit security gtp profile profile-name path-... | [
{
"name": "alarm-threshold",
"desc": "To set alarm threshold for path rate limiting."
},
{
"name": "drop-threshold",
"desc": "To set drop threshold for path rate limiting."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10. | [
"Understanding Path Rate Limiting for GTP Control Messages",
"Example: Limiting the Message Rate and Path Rate for GTP Control Messages"
] |
ecmp | ecmp; | [edit logical-systems logical-system-name protocols ldp oam bfd-liveness-detection],
[edit logical-systems logical-system-name protocols ldp oam fec address bfd-liveness-detection],
[edit protocols ldp oam bfd-liveness-detection],
[edit protocols ldp oam fec address bfd-liveness-detection] | Allows LDP to establish BFD sessions for all ECMP paths configured for the specified FEC. If you
configure the ecmp statement, you must also configure the periodic-traceroute statement for the specified
FEC. If you do not do so, the commit operation fails. You can configure the periodic-traceroute statement
at the glob... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring ECMP-Aware BFD for LDP LSPs"
] |
ecmp-alb | ecmp-alb {
apply-groups;
apply-groups-except;
tolerance;
} | [edit chassis] | Enable adaptive load balancing for equal-cost multipath (ECMP) next hops.
NOTE: The ecmp-alb statement can be enabled only when the [edit chassis network-services
enhanced-ip] statement is configured.
Starting in Junos OS Release 20.1R1, you can configure adaptive load balancing for
ECMP next hops on multiple Packet Fo... | [
{
"name": "apply-groups",
"desc": "Specify the groups from which to inherit configuration data."
},
{
"name": "apply-groups-except",
"desc": "Specify the groups from which configuration data should not be inherited."
},
{
"name": "tolerance",
"desc": "Specify the adaptive tolerance i... | 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. | [] |
ecmp-fast-reroute | ecmp-fast-reroute; | [edit logical-systems logical-system-name routing-options forwarding-table ],
[edit routing-options forwarding-table] | Enables equal-cost multipath (ECMP) fast reroute protection. If a link fails, ECMP uses fast reroute
protection to shift packet forwarding to operational links to reduce packet loss. Fast reroute protection
updates ECMP information for the interface without waiting for route table updates. When the next
route table upd... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Command introduced before Junos OS Release 17.4. | [
"ECMP Flow-Based Forwarding"
] |
ecmp-local-bias | ecmp-local-bias; | [edit forwarding-options load-balance] | By default, equal cost multi-path (ECMP) traffic flows are distributed more-or-less equally between
forwarding next-hops. Enable ecmp-local-bias to have ECMP traffic prefer local forwarding next-hops (that
is, local to the packet forwarding engine (PFE) that is performing the packet look up) over remote ones,
and to di... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1. | [
"Configuring Per-Prefix Load Balancing"
] |
ecmp-resilient-hash | ecmp-resilient-hash; | [edit forwarding-options enhanced-hash-key] | Enable resilient hashing for ECMP groups, to minimize remapping of destination paths. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10. | [
"Configure Resilient Hashing for LAGs/ECMP Groups"
] |
edge | edge; | [edit logical-systems logical-system-name protocols (mstp | rstp | vstp) interface interface-name],
[edit logical-systems logical-system-name protocols mstp msti msti-id interface interface-name],
[edit logical-systems logical-system-name protocols vstp vlan vlan-id interface interface-name],
[edit logical-systems logi... | For Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol (VSTP), or Multiple Spanning
Tree Protocol (MSTP), configure interfaces as edge ports or edge interfaces. Edge ports do not expect to
receive BPDUs. If a BPDU is received, the port becomes a non edge port unless set protocols (vstp|rstp|
mstp) bpdu-bl... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Statement updated in Junos OS Release 9.4 for EX Series switches to add VSTP support.
Support for logical systems added in Junos OS Release 9.6. | [
"Understanding STP",
"Example: Configuring Network Regions for VLANs with MSTP on Switches"
] |
edge-virtual-bridging | edge-virtual-bridging {
traceoptions {
file filename <files number> <no-stamp> <replace> <size size> <world-readable | no-world-
readable>;
flag flag ;
}
vsi-discovery {
interface interface-name
vsi-policy vsi-policy-name
}
} | [edit protocols] | 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 12.1. | [
"Example: Configuring Edge Virtual Bridging for Use with VEPA Technology on an EX Series Switch",
"Configuring Edge Virtual Bridging on an EX Series Switch"
] |
edit | edit statement-path | Move inside the specified statement hierarchy. If the statement does not exist, it is created.
You cannot use the edit command to change the value of identifiers. You must use the set command. | [
{
"name": "statement-path",
"desc": "Path to the statement."
}
] | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy. | Command introduced before Junos OS Release 7.4. | [
"Displaying the Current Configuration"
] | |
effective-aigp | effective-aigp <metric-offset>; | [edit fabric protocols bgp group name metric-out],
[edit logical-systems name protocols bgp group name metric-out],
[edit logical-systems name routing-instances name protocols bgp group name metric-out],
[edit logical-systems name tenants name routing-instances name protocols bgp group name metric-out],
[edit protocols... | To track the effective AIGP metric. Effective AIGP is the AIGP value advertised with the route plus the
IGP cost to reach the nexthop. | [
{
"name": "metric-offset",
"desc": "Metric offset for MED."
}
] | routing | Statement introduced in Junos OS Release 20.2R1. | [] |
effective-shaping-rate | effective-shaping-rate; | [edit chassis] | Specify that the Cos-Effective-Shaping-Rate VSA [26–177] included in RADIUS Acct-Start, Acct-Stop,
and Interim-Acct messages reports the actual rate of the downstream traffic for a subscriber, in kilobits
per second. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Reporting the Effective Shaping Rate for Subscribers"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.