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 |
|---|---|---|---|---|---|---|---|
nssu | nssu {
rcp-count number;
upgrade-group group-name {
fpcs (slot-number | [list-of-slot-numbers]);
member member-id {
fpcs (slot-number | [list-of-slot-numbers]);
}
}
} | [edit chassis] | Configure parameters that affect the nonstop software upgrade (NSSU) process.
NOTE: You use the "request system software nonstop-upgrade" on page 15892
command to initiate NSSU.
The rcp-count option (available only on QFX5100 switches) sets the number of parallel rcp sessions that
NSSU uses to copy the new software to ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
rcp-count statement introduced in Junos OS Release 14.1X53-D40 for QFX5100 switches only. | [
"Configuring Line-Card Upgrade Groups for Nonstop Software Upgrade",
"Example: Configuring Line-Card Upgrade Groups for Nonstop Software Upgrade on EX Series",
"Switches"
] |
ntp (QFabric) | ntp {
authentication-key number type type value password;
server address <key key-number> <version value> <prefer>;
} | [edit system] | Configure Network Time Protocol (NTP) on the switch. | [
{
"name": "authentication-key",
"desc": "Configure NTP authentication keys so authenticated packets can be sent."
},
{
"name": "server",
"desc": "Configure the switch to operate in client mode with the remote system at the specified server address."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring NTP Authentication Keys (QFabric System)",
"Configuring the NTP Time Server and Time Services (QFabric System)"
] |
ntp threshold | threshold action (accept | reject) value; | [edit system ntp] | Assign a threshold value for Network Time Protocol (NTP) adjustment that is outside of the acceptable
NTP update and specify whether to accept or reject NTP synchronization when the proposed time from
the NTP server exceeds the configured threshold value. If accept is the specified action, the system
synchronizes the d... | [
{
"name": "value",
"desc": "Specify the maximum value in seconds allowed for NTP adjustment. Range: 1 through 600. Default: The default value is 400."
},
{
"name": "action",
"desc": "Specify the actions for NTP abnormal adjustment."
},
{
"name": "accept",
"desc": "Enable log mode f... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D70.
Statement qualified for Junos OS Evolved Release 25.4R1. | [
"NTP Time Synchronization on SRX Series Devices"
] |
ntp | ntp {
authentication-key key-number type (md5 | sha1 | sha256) value password;
boot-server (address | hostname);
broadcast <address> <key key-number> <routing-instance-name routing-instance-name> <ttl
value> <version value>;
broadcast-client;
interval-range value;
multicast-client <address>;
... | [edit system] | Configure NTP on the device. In both standalone and chassis cluster modes, the primary Routing Engine
runs the NTP process to get the time from the external NTP server. Although the secondary Routing
Engine runs the NTP process in an attempt to get the time from the external NTP server, this attempt
fails because of ne... | [
{
"name": "authentication-key",
"desc": ""
},
{
"name": "key_number",
"desc": "Configure key (key ID, key type, and key value) to authenticate NTP packets with the devices (servers and clients). The authentication key has two fields:"
},
{
"name": "type",
"desc": "When authentication... | 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.
routing-instance option for the server statement introduced in Junos OS Release 18.1.
restrict statement introduced in Junos OS Release 20.1. | [
"Synchronizing and Coordinating Time Distribution Using NTP",
"Understanding NTP Time Servers",
"Configuring NTP Authentication Keys",
"NTP Time Synchronization on SRX Series Devices",
"Configuring the NTP Time Server and Time Services",
"Configuring the Switch to Listen for Broadcast Messages Using NTP",... |
nullpdu | nullpdu {
protocol (ID-0x0000 | ID-0xFFFF);
} | [edit security sctp] | Use the nullpdu function to configure the Stream Control Transmission Protocol (SCTP) null protocol
data unit (PDU) value. If you set the null PDU value to 0xFFFF, then the payload protocol identifier value
is replaced with 0xFFFF and the user data field is not modified. If you set the null PDU value to 0x0000,
then th... | [
{
"name": "protocol",
"desc": "To specify the SCTP null PDU payload protocol identifier."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X47-D10. | [
"Understanding SCTP Multichunk Inspection"
] |
num-65-127-prefix | num-65-127-prefix number; | [edit chassis forwarding-options profile-name] | For the Unified Forwarding Table (UFT) feature, specify how much forwarding table memory to allocate
for IPv6 entries with prefix lengths in the range of /65 through /127. The ability to allocate flexibly the
memory for IPv6 entries with prefixes in this range extends the use of this memory space to
accommodate the app... | [
{
"name": "number",
"desc": "Specify a numerical value. Range: (Junos OS Release 13.2x51-D10 only) 1 through 128. Each increment represents 16 IPv6 prefixes with lengths in the range of /65 through /127, for a total maximum of 2,058 prefixes (16 x 128 = 2,048). Default: 1 (16 IPv6 prefixes with lengths in... | 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.
Support for QFX5200 Series switches introduced in Junos OS Release 15.1X53-D30. | [
"Configuring the Unified Forwarding Table on Switches"
] |
number-of-frames | number-of-frames value; | [edit interfaces interface-name otn-options odu-delay-management] | Specify the number of consequent frames to declare a delay measurement (DM) session completed. | [
{
"name": "value",
"desc": "Number of consequent frames to declare DM completed."
}
] | 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. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
number-of-ports | number-of-ports number-of-active-physical-ports; | [edit chassis fpc fpc-slot pic pic-number pic-mode pic-speed] | Administratively enable physical ports, for example, to prevent oversubscription of the line card fabric
interface. By default, all available ports are enabled. When disabled, the LED on the affected line card
will appear yellow on capable line cards.
(MX Series with 16x10GE MPC, MPC3, MPC4, MPC5, and MPC6) You can dis... | [
{
"name": "number-of-active-physical-ports",
"desc": "Specify the number of physical ports to enable on PICs or MICs on an"
}
] | 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 MPC3, MPC4, MPC5, and MPC6 introduced in Junos OS Release 13.3R2.
Support for MPC7E-MRATE MPC introduced in Junos OS Release 15.1F4.
Support for MPC8E and MPC9E introduced in Junos OS Release 15.1F5.
Support for MX10003 MPC introduced in Junos OS Release 17.3R1... | [
"Configuring the Number of Active Ports on 16x10GE 3D MPC",
"Port Speed on MIC-MRATE Overview",
"Port Speed on MPC7E-MRATE Overview",
"Port Speed on MX204 Overview"
] |
number-of-sub-ports (interface) | number-of-sub-ports <number-of-sub-ports>; | [edit interfaces interface-name] | Specifies the number of channelized interfaces that you can configure on a physical port with the
specified speed. | [
{
"name": "number-of-sub-ports number-of-subports",
"desc": "Specify the number of sub-ports per physical port."
},
{
"name": "(PTX10003-80C and PTX10003-160C routers)",
"desc": "1, 2, and 4."
},
{
"name": "(JNP10K-LC1201)",
"desc": "0 through 7."
},
{
"name": "(JNP10K-LC1202... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1R1.
Interface hierarchy introduced in Junos OS Evolved Release 20.1R2 for JNP10K-LC1201 line cards on
PTX10008 routers. | [
"Port Speed",
"O"
] |
oam (Layer 2 Circuit Protocols) | oam {
bfd-liveness-detection;
ping-interval;
ping-multiplier ping-count;
} | [edit routing-instances routing-instance-name protocols l2vpn],
[edit routing-instances routing-instance-name protocols vpls],
[edit routing-instances routing-instance-name protocols vpls neighbor address],
[edit protocols l2circuit neighbor address interface interface-name] | Allows you to configure bidirectional forwarding detection (BFD) and a control channel for a
pseudowire, in addition to the corresponding operations and management functions to be used over
that control channel. BFD provides a low resource fault detection mechanism for the continuous
monitoring of the pseudowire data p... | [
{
"name": "bfd-liveness-detection",
"desc": "The bfd-liveness-detection statement and substatements are described in the Junos OS Routing Protocols Library."
},
{
"name": "ping-multiplier",
"desc": ""
},
{
"name": "ping-count",
"desc": "Specify the number of LSP ping packets to delay... | 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.
Support for VPLS FEC 129 introduced in Junos OS Release 12.2.
ping-multiplier statement introduced in Junos OS Release 16.1. | [
"Configuring BFD for VCCV for Layer 2 VPNs, Layer 2 Circuits, and VPLS"
] |
oam (MX Series) | oam {
ethernet {
connectivity-fault-management {
action-profile profile-name {
default-actions {
interface-down;
}
}
performance-monitoring {
delegate-server-processing;
hardware-assisted-... | [edit protocols] | For Ethernet interfaces on M320, M120, MX Series, and T Series routers and PTX Series Packet
Transport Routers, provide IEEE 802.3ah Operation, Administration, and Maitenance (OAM) support.
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.2. | [
"IEEE 802.3ah OAM Link-Fault Management Overview"
] |
oam (Protocols LDP) | oam {
bfd-liveness-detection {
detection-time threshold milliseconds;
ecmp;
failure-action {
remove-nexthop;
remove-route;
}
holddown-interval milliseconds;
ingress-policy ingress-policy-name;
minimum-interval milliseconds;
min... | [edit logical-systems logical-system-name protocols ldp]
[edit protocols ldp] | Configure Operation, Administration, and Maintenance (OAM) and Bidirectional Forwarding Detection
(BFD) protocol for LDP. | [
{
"name": "fec fec-address",
"desc": "Specify the forwarding equivalence class (FEC) address. You must either specify a FEC"
},
{
"name": "lsp-ping-interval seconds",
"desc": "Specify the duration of the LSP ping interval in seconds. To issue a ping on an"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6.
lsp-ping-interval option introduced in Junos OS Release 9.4. | [
"Configuring BFD for LDP LSPs"
] |
oam (Protocols MPLS) | oam {
bfd-liveness-detection{
failure-action teardown;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
minimum-transmit-interval milliseconds;
multiplier detection-time-multiplier;
}
lsp-ping-interval seconds;
mpls-tp-mode;
performance-mo... | [edit protocols mpls],
[edit protocols mpls label-switched-path lsp-name]
[edit protocols mpls label-switched-path lsp-name primary path-name] | Enable Operation, Administration, and Maintenance (OAM) for RSVP-signaled LSPs. | [
{
"name": "lsp-ping-interval seconds",
"desc": "Specify the duration of the LSP ping interval in seconds. To issue a ping on an"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6.
lsp-ping-interval option introduced in Junos OS Release 9.4.
performance-monitoring configuration statement introduced in Junos OS Release 15.1. | [
"Configuring BFD for MPLS IPv4 LSPs"
] |
oam detection-disable | oam detection-disable | [edit chassis fabric] | Disable the fabric Operation, Administration, Maintenance (OAM) feature, which helps you detect
failures in fabric paths when a switch fabric card (switch interface board or SIB) or an FPC transitions
from online to offline state or vice versa.
NOTE: This command is not applicable to Junos OS Evolved Releases 20.4R2 an... | [] | Interface—To view this statement in the configuration. | Interface-control—To add this statement to the configuration. | [
"Error Handling by Fabric OAM"
] |
oam runtime-disable | oam runtime-disable | [edit chassis fabric] | Disable the runtime fabric Operation, Administration, Maintenance (OAM) feature, which helps you
detect and report failures in fabric planes during system runtime.
Default
The runtime Fabric OAM feature is enabled by default. | [] | Interface—To view this statement in the configuration. | Interface-control—To add this statement to the configuration. | [] |
oam | oam {
ethernet{
connectivity-fault-management {
action-profile profile-name {
action {
interface-down;
}
default-actions {
interface-down;
}
event {
adjacen... | [edit protocols] | Provide IEEE 802.3ah Operation, Administration, and Maintenance (OAM) link fault management (LFM)
support for Ethernet interfaces on EX Series switches or configure connectivity fault management (CFM)
for IEEE 802.1ag Operation, Administration, and Management (OAM) support on the switches.
The remaining statements are ... | [] | 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.
connectivity-fault-management introduced in Junos OS Release 10.2 for EX Series switches. | [
"Example: Configure Ethernet OAM Link Fault Management",
"Example: Configure Ethernet OAM Connectivity Fault Management on EX Series Switches",
"Configure Ethernet OAM Link Fault Management",
"Configure Ethernet OAM Connectivity Fault Management (CLI Procedure)"
] |
oam-on-svlan (Ethernet Interfaces) | oam-on-svlan; | [edit interfaces interface-name] | Enable propagation of the Ethernet IEEE 802.1ag Operation, Administration, and Maintenance (OAM)
state of a static single-tagged service VLAN (S-VLAN) logical interface to the dynamic or static double-
tagged customer VLAN (C-VLAN) logical interface and associated subscriber interfaces configured on
the S-VLAN. The sta... | [] | 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. | [
"Configuring Ethernet OAM Support for Service VLANs with Double-Tagged Customer VLANs",
"Ethernet OAM Support for Service VLANs Overview"
] |
object-cache-size | object-cache-size value; | [edit chassis fpc slot-number pic pic-number adaptive-services service-package extension-
provider] | Configure the size of the object cache. When this setting is changed, the PIC reboots. | [
{
"name": "value",
"desc": "Amount of object cache, in MB. Only values in increments of 128 MB are allowed."
}
] | 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. | [] |
object-names | object-names {
mib-object-name;
} | [edit accounting-options mib-profile profile-name] | Specify the name of each MIB object for which MIB statistics are collected for an accounting-data log
file. | [
{
"name": "mib-object-name",
"desc": "Name of a MIB object. You can specify more than one MIB object name."
}
] | 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. | [
"Configure the MIB Profile"
] |
observation-domain-id | observation-domain-id domain-id; | [edit services flow-monitoring version-ipfix template template-name] | For IPFIX flows, an identifier of an observation domain is locally unique to an exporting process of the
templates. The export process uses the observation domain ID to uniquely identify to the collection
process in which the flows were metered. We recommend that you configure this ID to be unique for
each IPFIX flow. ... | [
{
"name": "domain-id",
"desc": "Identifier for the observation domain for IPFIX flows."
}
] | 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.
Statement introduced in Junos OS Evolved 22.4R1. | [
"Configuring Observation Domain ID and Source ID for Version 9 and IPFIX Flows",
"Configuring Template ID and Options Template ID for Version 9 and IPFIX Flows"
] |
oc192 | oc192; | [edit interfaces interface-name otn-options rate] | Set the line rate or speed of the OTN signal to optical channel transport unit 2 (OTU2). | [
{
"name": "oc192",
"desc": ""
},
{
"name": "OTU2 line rate or 10 Gbps",
"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.3 for MX Series routers. | [
"10-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
ocs (Diameter Applications) | ocs {
global {
service-context-id service-context;
}
partition partition-name {
called-station-id station-name;
charging-id number;
destination-host ocs-hostname;
destination-realm ocs-realm-name;
diameter-instance;
draining;
draining-response... | [edit access] | Configure the Online Charging System (OCS) global attributes and partition. The OCS interacts with the
Policy and Charging Enforcement Function (PCEF). The PCEF optionally reports usage and receives
additional authorizations from the OCS using the 3rd Generation Partnership Project (3GPP) Gy
protocol. Broadband PCEF (B... | [] | 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... |
ocsp (Security PKI) | ocsp {
connection-failure (disable | fallback-crl);
disable-responder-revocation-check;
nonce-payload (enable | disable);
url ocsp-url;
} | [edit security pki ca-profile ca-profile-name revocation-check] | Configure Online Certificate Status Protocol (OCSP) to check the revocation status of a certificate. | [
{
"name": "connection-failure",
"desc": "(Optional) Specify action to take if there is a connection failure to the OCSP responder. If this option is not configured and there is no response from the OCSP responder, certificate validation will fail."
},
{
"name": "disable",
"desc": "Skip the revoc... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X46-D20. | [
"Basic Elements of PKI in Junos OS"
] |
odu-backward-frr-enable | odu-backward-frr-enable; | [edit interfaces interface-name otn-options preemptive-fast-reroute] | Insert the ODU status into the transmitted OTN frames and monitor the received OTN frames for the
ODU BER status.
Default
By default, FRR ODU backward FRR insertion is disabled. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1R2. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
odu-delay-management | odu-delay-management {
(bypass | no-bypass);
(monitor-end-point | no-monitor-end-point);
number-of-frames value;
(no-start-measurement | start-measurement;
} | [edit interfaces interface-name otn-options] | Specify Optical Channel Data Unit (ODU) delay management options.
Default
If you omit the odu-delay-management statement, the ODU delay management options are disabled. | [] | 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. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
odu-signal-degrade | odu-signal-degrade {
ber-threshold-clear;
ber-threshold-signal-degrade;
interval
} | [edit interfaces interface-name otn-options] | Specify optical channel data unit (ODU) signal degradation threshold-related values.
Default
If you omit the odu-signal-degrade statement, the default threshold values are used.
The following are the default threshold values for optical channel data unit (ODU) signal degradation for
the P2-100GE-OTN PIC:
•
ber-threshol... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1R2. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
odu-signal-degrade-monitor-enable | odu-signal-degrade-monitor-enable; | [edit interfaces interface-name otn-options preemptive-fast-reroute] | Enable monitoring of signal degradation of ODU BER in the received OTN frames.
Default
By default, FRR signal degrade monitoring disabled. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1R2. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
odu-ttim-action-enable | (odu-ttim-action-enable | no-odu-ttim-action-enable); | [edit interfaces interface-name otn-options] | Specify whether consequent action for Optical Channel Data Unit (ODU) TTIM is enabled or disabled.
Default
If you omit the odu-ttim-action-enable statement, consequent action for ODU TTIM is disabled. | [
{
"name": "odu-ttim-action-enable",
"desc": "Enable consequent action for ODU TTIM."
},
{
"name": "no-odu-ttim-action-enable",
"desc": "Disable consequent action for ODU TTIM."
}
] | 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. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
off (Destination NAT Next Gen Services) | off; | [edit services nat destination rule-set rule-set-name rule rule-name then destination-nat] | Tun off destination address translation for the rule. Use this statement when configuring port forwarding
without destination address translation. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [] | |
offer-period | offer-period milliseconds; | [edit logical-systems logical-system-name protocols pim interface (Protocols PIM) interface-name
bidirectional df-election],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
interface (Protocols PIM) interface-name bidirectional df-election],
[edit protocols pim interfac... | Configure the designated forwarder (DF) election offer period for bidirectional PIM. When a DF election
Offer or Winner message fails to be received, the message is retransmitted. The offer-period statement
modifies the interval between repeated DF election messages. The robustness-count statement
determines the minimu... | [
{
"name": "milliseconds",
"desc": "Interval to wait before retransmitting DF Offer and Winner messages."
}
] | 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"
] |
offline-on-fabric-bandwidth-reduction | offline-on-fabric-bandwidth-reduction; | [edit chassis fpc slot-number] | Configure an FPC with degraded fabric bandwidth offline, to avoid causing a null route in the chassis for
an extended time. | [] | 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. | [
"Disabling an FPC with Degraded Fabric Bandwidth",
"Managing Bandwidth Degradation"
] |
offload-type | offload-type {
none;
pfe-timestamp;
} | [edit services monitoring rpm owner name test test-name] | Enable timestamping of RPM probe messages in the Packet Forwarding Engine (PFE) host processor, by
offloading the processing of RPM probes to the PFE. This feature is supported only with icmp-ping, icmp-
ping-timestamp, udp-ping, and udp-ping-timestamp probe types. | [
{
"name": "none",
"desc": "Timestamping performed on the Routing Engine"
},
{
"name": "pfe-timestamp",
"desc": "Timestamping performed on the PFE"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 20.1. | [
"Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, and MX Series",
"Routers"
] |
offloads | offloads {
disable;
} | [edit virtual-network-functions] | Offloads configuration for the VNF interface.
NOTE: This feature is available only in enhanced-orchestration mode. | [
{
"name": "disable",
"desc": "Disable the offloads option that offloads the configuration for the VNF interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D471. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
offset (MX Series) | offset (0 |30 | 50); | [edit security macsec connectivity-association connectivity-association-name],
[edit security macsec connectivity-association connectivity-association-name secure-channel
secure-channel-name] | Specifies the number of octets in an Ethernet frame that are sent in unencrypted plain-text when
encryption is enabled for MACsec.
Setting the offset to 30 allows a feature to see the IPv4 header and the TCP/UDP header while
encrypting the remaining traffic. Setting the offset to 50 allows a feature to see the IPv6 hea... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Media Access Control Security (MACsec) on Routers"
] |
offset | offset (0 |30 | 50); | [edit security macsec connectivity-association connectivity-association-name]
[edit security macsec connectivity-association connectivity-association-name secure-channel secure-
channel-name] | Specifies the number of octets in an Ethernet frame that are sent in unencrypted plain-text when
encryption is enabled for MACsec.
Configure a confidentiality offset for MACsec. When MACsec is enabled with encryption, the
confidentiality offset specifies a number of octets in an Ethernet frame that are sent in unencryp... | [] | 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-D15.
Statement introduced on SRX Series Firewalls in Junos OS Release 15.1X49-D60. | [
"Configuring MACsec on EX, QFX and SRX Devices",
"Understanding Media Access Control Security (MACsec)",
"Configuring Media Access Control Security (MACsec)"
] |
oid (SNMP Scripts) | oid id {
priority;
} | [edit system scripts snmp file filename] | For Junos OS SNMP scripts, specify the global object identifier (OID), associated with a subtree of
object in the management information base (MIB), to be mapped to the SNMP script. Specify the OID
using either a sequence of dotted integers or a subtree name. | [
{
"name": "priority",
"desc": "(Optional) Override the default registration priority of the OID. The highest priority is 1; the lowest priority is 255. Default: 127 Range: 1 through 255"
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Example: Processing Unsupported OIDs with an SNMP Script"
] |
oid (SNMPv3) | oid oid <include | exclude>; | [edit snmp v3 notify-filter profile-name] | Specify an object identifier (OID) used to represent a subtree of MIB objects. This OID is a prefix that
the represented MIB objects have in common.
Default
include. The subtree of MIB objects represented by the specified OID is included. | [
{
"name": "exclude",
"desc": "Exclude the subtree of MIB objects represented by the specified OID."
},
{
"name": "include",
"desc": "Include the subtree of MIB objects represented by the specified OID."
},
{
"name": "oid",
"desc": "Object identifier used to represent a subtree of MIB... | 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. | [] |
oid | oid object-identifier <exclude | include>; | [edit snmp view view-name] | Specify an object identifier (OID) used to represent a subtree of MIB objects.
Default
include. The subtree of MIB objects represented by the specified OID is included. | [
{
"name": "exclude",
"desc": "Exclude the subtree of MIB objects represented by the specified OID."
},
{
"name": "include",
"desc": "Include the subtree of MIB objects represented by the specified OID."
},
{
"name": "object-identifier",
"desc": "OID used to represent a subtree of MIB... | 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. | [] |
oif-map (Dynamic IGMP Interface) | oif-map map-name; | [edit dynamic-profiles profile-name protocols igmp interface interface-name] | Associates an OIF map to the IGMP interface using a dynamic profile. The OIF map is a routing policy
statement that can contain multiple terms. | [
{
"name": "map-name",
"desc": "Name of the OIF map."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [] |
oif-map (Dynamic MLD Interface) | oif-map map-name; | [edit dynamic-profiles profile-name protocols mld interface interface-name] | Associate an outgoing interface (OIF) map to a dynamic MLD logical interface. The OIF map is a routing
policy statement that can contain multiple terms. | [
{
"name": "map-name",
"desc": "Name of the OIF map."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Dynamic MLD Configuration Overview",
"Example: Configuring Multicast with Subscriber VLANs"
] |
oif-map (IGMP Interface) | oif-map map-name; | [edit logical-systems logical-system-name protocols igmp interface interface-name],
[edit protocols igmp interface interface-name] | Associates an outgoing interface (OIF) map to the IGMP interface. The OIF map is a routing policy
statement that can contain multiple terms. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Example: Configuring Multicast with Subscriber VLANs"
] |
oif-map (MLD Interface) | oif-map map-name; | [edit logical-systems logical-system-name protocols mld interface interface-name],
[edit protocols mld interface interface-name] | Associate an outgoing interface (OIF) map to an MLD logical interface. The OIF map is a routing policy
statement that can contain multiple terms. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Example: Configuring Multicast with Subscriber VLANs"
] |
oism (Multicast Snooping Options) | oism {
(conserve-mcast-routes-in-pfe | install-star-g-routes);
} | [edit multicast-snooping-options],
[edit routing-instances name multicast-snooping-options] | Set optimized intersubnet multicast (OISM) options. You can use OISM to optimize multicast traffic flow
in an EVPN-VXLAN fabric.
NOTE: The functions of the conserve-mcast-routes-in-pfe option and the install-star-g-
routes option are mutually exclusive, so you can use only one or the other of these
options in a routin... | [
{
"name": "conserve-mcast-",
"desc": ""
},
{
"name": "routes-in-pfe",
"desc": "(ACX Series routers, QFX5130 switches, and QFX5700 switches) Conserve Packet Forwarding Engine (PFE) multicast route table space on the device by not installing Layer 2 (L2) multicast snooping (*,G) and (S,G) states i... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1 and Junos OS Evolved 22.1R1.
conserve-multicast-routes-in-pfe option introduced in Junos OS Evolved Releases 22.4R2 and 23.1R1. | [
"Optimized Inter-Subnet Multicast in EVPN Networks",
"Assisted Replication Multicast Optimization in EVPN Networks"
] |
oism | oism {
enhanced {
forward-on-source-bridge-domain {
forward-policy [ forwarding-policy-name ... ]
}
}
originate-smet-on-revenue-vlan-too;
pim-evpn-gateway {
external-irb irb-interface-name;
peg-df-election {
delay-time seconds;
... | [edit protocols evpn],
[edit routing-instances name protocols evpn] | Set optimized intersubnet multicast (OISM) options in a Layer 3 (L3) virtual routing and forwarding (VRF)
routing instance or in the default L3 routing instance on an EVPN fabric device.
See Feature Explorer for the devices that support this statement in the default L3 routing instance (at
the [edit protocols evpn] hie... | [
{
"name": "originate-smet-on-",
"desc": ""
},
{
"name": "revenue-vlan-too",
"desc": "Originate selective multicast Ethernet tag (SMET) routes on revenue VLANs (or bridge domains) upon receiving a local IGMP report. SMET routes are EVPN Type 6 routes. The revenue VLANs are the customer VLANs that... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1.
peg-df-election option added in Junos OS and Junos OS Evolved Release 23.3R1.
enhanced options added in Junos OS and Junos OS Evolved Release 25.2R1.
Support in the default L3 routing instance introduced in Junos OS Evolved Release 25.4R1. | [
"IPv4 Inter-VLAN Multicast Forwarding Modes for EVPN-VXLAN Overlay Networks",
"Optimized Inter-Subnet Multicast in EVPN Networks",
"PEG DF Election"
] |
omit-no-export (Graceful Restart for BGP Helper) | omit-no-export; | [edit logical-systems logical-system-name protocols bgp graceful-restart long-lived advertise-to-
non-llgr-neighbor],
[edit logical-systems logical-system-name protocols bgp group group-name graceful-restart long-
lived advertise-to-non-llgr-neighbor],
[edit logical-systems logical-system-name protocols bgp group group... | Cause the no-export BGP community to be prevented from being automatically added to routes
advertised to external BGP neighbors (presumed to be CE routers). The no-export routes containing this
community name are not advertised outside a BGP confederation boundary. In VPN deployments, for
example, BGP is often used as ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Graceful Restart Options for BGP",
"Junos OS High Availability User Guide"
] |
omit-wildcard-address | omit-wildcard-address; | [edit dynamic-profiles name routing-options (Dynamic Profiles) multicast] | Omit wildcard source and group fields in S-PMSI AD / Leaf AD NLRI updates sent by Junos devices. This
helps to avoid format mismatches on wildcard addresses thereby maximizing MVPN interoperability
with devices from other vendors.
Default
omit-wildcard-address is disabled by default. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1R2 | [] |
on-demand-address-allocation | on-demand-address-allocation; | [edit logical-systems name routing-instances name system services dhcp-local-server dual-stack-group
dual-stack-group-name],
[edit logical-systems name system services dhcp-local-server dual-stack-group dual-stack-group-
name],
[edit routing-instances name system services dhcp-local-server dual-stack-group dual-stack-... | Enables an address or prefix to be allocated on demand when a dual-stack subscriber session is
established. Starting in Junos OS Release 18.1R1, when reauthentication is configured, enables per-
family address allocation as each family’s DHCP session is established. In earlier released, applies only to
the second famil... | [] | 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. | [
"Configuring RADIUS Reauthentication for DHCP Subscribers",
"RADIUS Reauthentication As an Alternative to RADIUS CoA for DHCP Subscribers",
"Single-Session DHCP Dual-Stack Overview",
"Configuring Access Profile Options for Interactions with RADIUS Servers",
"Attaching Access Profiles to DHCP Subscriber Inte... |
on-demand-ip-address | on-demand-ip-address; | [edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit],
[edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit ppp-options],
[edit interfaces pp0 unit unit-number ppp-options],
[edit protocols ppp-service] | For IPv4 and IPv6 dual-stack PPP subscribers, enables on-demand allocation and de-allocation of an
IPv4 address after initial PPP authentication for a subscriber who does not have an existing IPv4
address.
Configuration changes take effect as follows:
•
When you change this setting for a dynamic PPP interface (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 13.1. | [
"Conserving IPv4 Addresses for Dual-Stack PPP Subscribers Using On-Demand IPv4 Address",
"Allocation",
"Configuring Static On-Demand IPv4 Address Allocation for Dual-Stack PPP Subscribers",
"Configuring Dynamic On-Demand IPv4 Address Allocation for Dual-Stack PPP Subscribers",
"Configuring Global On-Demand ... |
on-disk-failure (Chassis Routing Engine) | on-disk-failure {
disk-failure-action (halt | reboot);
} | [edit chassis routing-engine] | Instruct the router to halt or reboot if it detects hard disk errors on the Routing Engine. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before JUNOS Release 7.4.
The disk-failure-action statement added in JUNOS Release 9.0. | [
"Enabling a Routing Engine to Reboot on Hard Disk Errors"
] |
on-disk-failure | on-disk-failure {
disk-failure-action (halt | reboot);
} | [edit chassis redundancy]
[edit chassis routing-engine] | Instruct the router to halt or reboot if it detects hard disk errors on the Routing Engine. | [] | 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. | [
"Enabling a Routing Engine to Reboot on Hard Disk Errors",
"Installing Software on an EX Series Switch with Redundant Routing Engines (CLI Procedure)",
"High Availability Features for EX Series Switches Overview"
] |
on-error | on-error {
raise-alarm;
power (cycle | off);
write-coredump;
} | [edit chassis cfeb slot-number],
[edit chassis feb slot-number],
[edit chassis fpc slot-number sanity-poll],
[edit chassis lcc number fpc number sanity-poll] | Instruct the FPC or FEB or CFEB to perform actions during an error condition. | [
{
"name": "raise-alarm",
"desc": "Generate and display a chassis alarm in case of an error."
},
{
"name": "power cycle",
"desc": "Reboot the FPC or FEB or CFEB after generating a core file. This statement is useful in case"
},
{
"name": "power off",
"desc": "Halt the FPC or FEB or CF... | 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 Sanity Polling"
] |
on-link (Dynamic Router Advertisement) | (on-link | no-on-link); | [edit dynamic-profiles profile-name protocols router-advertisement interface interface-
nameprefix prefix] | Specify whether to enable prefixes to be used for onlink determination:
•
no-on-link—Disable prefixes from being used for onlink determination.
•
on-link—Enable prefixes to be used for onlink determination.
Default
The configured object is enabled unless explicitly disabled. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"IPv6 WAN Link Addressing with NDRA",
"Dynamic Router Advertisement Configuration Overview"
] |
on-link | (on-link | no-on-link); | [edit logical-systems logical-system-name protocols router-advertisement interface interface-
name prefix prefix],
[edit protocols router-advertisement interface interface-name prefix prefix] | Specify whether to enable prefixes to be used for onlink determination:
•
no-on-link—Disable prefixes from being used for onlink determination.
•
on-link—Enable prefixes to be used for onlink determination.
Router advertisement messages carry prefixes and information about them. A prefix is onlink when it is
assigned t... | [] | 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. | [
"Example: Configuring IPv6 Interfaces and Enabling Neighbor Discovery"
] |
on-loss-of-keepalives | on-loss-of-keepalives; | [edit chassis redundancy failover] | Instruct the backup router to take primary role if it detects a loss of keepalive signal from the primary
Routing Engine.
Default
The on-loss-of-keepalives statement must be included at the [edit chassis redundancy failover] hierarchy
level for failover to occur.
When the on-loss-of-keepalives statement is included but... | [] | 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. | [
"On Detection of a Loss of Keepalive Signal from the Primary Routing Engine"
] |
on-re-to-fpc-stale | on-re-to-fpc-stale; | [edit chassis redundancy failover] | Instruct the backup router to take mastership if the em0 (MX240, MX480, MX960, MX2010, and
MX2020) or management Ethernet Interface (MX10008, MX10016, PTX10008, PTX10016, QFX10008,
and QFX10016) fails on the master Routing Engine. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.2 on the MX240, MX480, MX960, MX2010, and
MX2020.
Statement added in Junos OS Release 22.2R1 on the MX10008, MX10016, PTX10008, PTX10016,
QFX10008, and QFX10016. | [] |
one-to-one (Aggregated Multiservices) | one-to-one {
preferred-backup preferred-backup;
} | [edit interfaces interface-name load-balancing-options high-availability-options] | Configure a single interface to be the preferred one-to-one (1:1) backup for an active aggregated
multiservices (AMS) interface. If the active interface fails, the backup interface takes over. A 1:1
(stateful) configuration synchronizes traffic states and data structures between the active and backup
PICs. This is requ... | [
{
"name": "preferred-backup",
"desc": ""
},
{
"name": "preferred-backup",
"desc": "Use the specified interface as the preferred backup member interface. The member interface format is mams-a/b/0, where a is the Flexible PIC Concentrator (FPC) slot number and b is the PIC slot number."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.2. | [
"Understanding Aggregated Multiservices Interfaces",
"Example: Configuring an Aggregated Multiservices Interface (AMS)"
] |
one-way-hardware-timestamp | one-way-hardware-timestamp; | [edit services rpm probe owner test test-name] | Enable timestamping of RPM probe messages for one-way delay and jitter measurements. You must
configure this statement along with the destination-interface statement to invoke timestamping. This
feature is supported only with icmp-ping, icmp-ping-timestamp, udp-ping, and udp-ping-timestamp probe types.
NOTE: Starting i... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5.
Statement introduced in Junos OS Release 19.1 for PTX Series routers. | [
"Configuring RPM Timestamping on MX, M, T, and PTX Series Routers and EX Series Switches"
] |
onlink-subnet-only | onlink-subnet-only; | [edit protocols neighbor-discovery] | Enable this option to prevent the device from responding to a neighbor solicitation (NS) from a prefix
that is not included as one of the device interface prefixes.
After configuring the onlink-subnet-only statement, the Routing Engine needs to be restarted using the
request system reboot both-routing-engines command. ... | [] | admin— To view this statement in the configuration.
admin-control— To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Understanding How to Control Inbound Traffic Based on Protocols",
"https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/config-",
"guide-routing/config-guide-routing-neighbor-discovery.html"
] |
op (Op Scripts) | op {
allow-url-for-python;
dampen {
dampen-options {
cpu-factor cpu-factor;
line-interval line-interval;
time-interval time-interval;
}
}
file filename {
allow-commands "regular-expression";
... | [edit system scripts] | Configure an operation scripting mechanism. | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Storing and Enabling Scripts"
] |
op invoke-debugger cli | op invoke-debugger cli filename
<detail>
<argument-name argument-value> | Invoke an interactive debugger to trace the execution of an op script that is enabled in the configuration.
When you execute this command for a SLAX script, the device invokes the SLAX debugger and displays
the (sdb) prompt. When you execute this command for a Python script, the device invokes the pdb
interactive debug... | [
{
"name": "detail",
"desc": "Display detailed output."
},
{
"name": "argument-name",
"desc": ""
},
{
"name": "argument-value",
"desc": "(Optional) Specify one or more arguments for the script. For each argument you include on the command line, you must specify a corresponding value f... | maintenance
Output Fields
When you enter the op invoke-debugger cli command, depending on the script type, the CLI displays
either the (sdb) or (Pdb) prompt where you can enter debugging commands.
Sample Output
op invoke-debugger cli (SLAX script)
user@host> op invoke-debugger cli script1.slax
sdb: The SLAX Debugger (... | Command introduced in Junos OS Release 13.1.
Support for the Python debugger added in Junos OS Release 16.1. | [
"SLAX Debugger, Profiler, and callflow"
] | |
op | op filename
<detail>
<argument-name argument-value>
<key (md5 | sha-256 | sha1) key-value
<url url> | Execute an op script. To execute local op scripts, you must configure the op script filename at the [edit
system scripts op file] hierarchy level.
Op scripts can be stored in one of the following locations:
•
On the local device in the /var/db/scripts/op directory on the hard disk
•
On the local device in the /config/s... | [
{
"name": "detail",
"desc": "(Optional) Display detailed output."
},
{
"name": "argument-name",
"desc": ""
},
{
"name": "argument-value",
"desc": "(Optional) Specify one or more arguments to the script. For each argument you include on the command line, you must specify a correspondi... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
op
user@host> op script1 interface ge-0/2/0.0 protocol inet
op url
user@host> op url https://www.example.net/opscripts/script1.slax key sha-256
150bf53383769f3bfedd41fe73320777f208d4fda81230cb... | Command introduced in Junos OS Release 7.6.
key option introduced in Junos OS Release 10.0.
url option introduced in Junos OS Release 10.0. | [
"Executing an Op Script on the Local Device",
"Executing an Op Script from a Remote Site"
] | |
open-timeout | open-timeout seconds; | [edit interfaces interface-name services-options]
[edit services service-set service-set-name service-set-options tcp-session] | Configure a timeout period for Transmission Control Protocol (TCP) session establishment. | [
{
"name": "seconds",
"desc": "Timeout period."
}
] | 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 added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Configuring Default Timeout Settings for Services Interfaces"
] |
openflow (Protocols OpenFlow) | openflow {
switch switch-name {
controller {
address address;
id id;
protocol tcp {
port port;
}
role equal;
}
default-action (drop | packet-in);
interfaces {
interface-name port-id port;
... | [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... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"OpenFlow Support on Juniper Networks Devices",
"Understanding Support for OpenFlow on Devices Running Junos OS",
"OpenFlow Operational Mode Commands"
] |
operating-mode | operating-mode mode; | [edit interfaces at-fpc/pic/port dsl-options] | For J Series Services Routers only, modify the operating mode of the digital subscriber line for an ATM
interface. | [
{
"name": "mode",
"desc": "Operating mode for ATM-over-ADSL interfaces. The mode can be one of the following:"
},
{
"name": "adsl2plus",
"desc": "Set the ADSL line to train in the ITU G.992.5 mode."
},
{
"name": "ansi-dmt",
"desc": "Set the ADSL line to train in the ANSI T1.413 Issue... | 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. | [
"ATM-over-ADSL Overview"
] |
operation | operation operation-name; | [edit accounting-options mib-profile profile-name] | Specify the name of the operation used to collect MIB statistics for an accounting-data log file. | [
{
"name": "operation-name",
"desc": "Name of the operation to use. You can specify a get, get-next, or walk operation."
}
] | 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. | [
"Configure the MIB Profile"
] |
optical-options (IPLC) | optical-options {
disable-edfa;
disable-osc;
expansion-card {
fpc fpc-slot;
}
express-in {
fpc fpc-slot;
}
no-disable-edfa;
no-disable-osc;
switch interface-name{
}
tca tca-identifier (enable-tca | no-enable-tca) (threshold number | threshold-24hrs number) ;
wavelength nm{
wss-express-in fpc-slot;
}
}
} | [edit chassis chassis fpc slot] | Configure the settings for the integrated photonic line card (IPLC). The options under this statement
enables you to increase the IPLC channel capacity to 64 channels, configure express in and out traffic
from another IPLC base module, create a single two-degree IPLC node, switch express traffic to optical
interfaces i... | [
{
"name": "slot",
"desc": "Specify the slot number the IPLC resides in. Range: 0 through 15"
},
{
"name": "disable-edfa",
"desc": "Disable both erbium-doped fiber amplifiers on the IPLC. Disabling the erbium-doped fiber amplifiers on the IPLC is required as a preliminary step whenever the you n... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Releases 15.1F6 and 17.1R1. | [
"Understanding How to Configure the Integrated Photonic Line Card",
"Configuring a Two-Degree Node for Express Traffic",
"Configuring Wavelengths on the Integrated Photonic Line Card Add and Drop Ports"
] |
optics (Chassis) | optics {
pm {
interval-length (10s|30s|1min|5min|15min);
}
} | [edit chassis] | Enable the optics performance monitor to manage and maintain optical networks by continuously
collecting and storing diagnostic data for optical parameters. | [
{
"name": "pm",
"desc": ""
},
{
"name": "interval-length",
"desc": "Set the interval length"
}
] | 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.2R1 for PTX Series routers. | [] |
optics-options | optics-options
application
{ hostid id mediaid id [ domainid id ];
}
{
appselid
{ id id;
}
alarm low-light-alarm {
(link-down | syslog);
}
encoding (differential | non-differential);
fec (hgfec | sdfec | sdfec15 | sdfec25);
high-pola... | [edit interfaces interface-name] | For 10-Gigabit Ethernet, 100-Gigabit Ethernet, or 400-Gigabit Ethernet ZR/ZR+ dense wavelength-
division multiplexing (DWDM) interfaces only, configure full C-band International Telecommunication
Union (ITU)-Grid tunable optics. | [
{
"name": "application hostid id mediaid id [ domainid id ]",
"desc": "Displays host ID, media ID of a selected application."
},
{
"name": "appselid",
"desc": "Configure the appsel number."
},
{
"name": "host-side-fec",
"desc": "Enable or disable the FEC on the host side optics."
}... | 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.
alarm option and warning options introduced in Junos OS Release 10.0.
Statement and tx-power option introduced in Junos OS Release 13.2 for PTX Series routers.
tca option introduced in Junos OS Release 14.2 for PTX Series routers.
los-alarm-threshold and los-alarm-warni... | [] |
optimal-route-reflection | optimal-route-reflection {
export policy;
igp-backup igp-backup;
igp-primary igp-primary;
} | [edit protocols bgp group] | Enable optimal route reflection for BGP group. | [
{
"name": "export",
"desc": "Optimal route reflection export policy."
},
{
"name": "igp-backup",
"desc": "Backup node identifier for this client group."
},
{
"name": "igp-primary",
"desc": "Primary node identifier for this client group."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.1R1. | [] |
optimize-adaptive-teardown | optimize-adaptive-teardown {
p2p;
delay;
timeout;
} | [edit protocols mpls] | Uses RPD infrastructure to determine when all the routes using the old LSP instance have fully shifted
to the new LSP instance after MBB switchover. When this statement is configured, the optimize-hold-
dead-delay statement, which delays the teardown of the old LSP instance after MBB switchover, is
ignored. | [
{
"name": "p2p",
"desc": "Only point-to-point LSPs configured in the system will be affected."
},
{
"name": "delaydelay-value",
"desc": "Delays the tearing down of old optimized LSP paths based on the configured value. Range: from 3 through 65535 seconds Default: 10 seconds NOTE: The delay CLI... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1R1. | [
"Optimizing Signaled LSPs",
"Achieving a Make-Before-Break, Hitless Switchover for LSPs"
] |
optimize-aggregate-frr | aggregated-ether-options {
minimum-links 2;
optimize-aggregate-frr;
link-speed 10g;
lacp {
active;
}
} | [edit dynamic-profiles name interfaces name aggregated-ether-options],
[edit dynamic-profiles name logical-systems name interfaces name aggregated-ether-options],
[edit interfaces name aggregated-ether-options] | Enable Aggregate fast reroute optimization.
NOTE: This knob has been deprecated. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [] | |
optimize-aggressive | optimize-aggressive; | [edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls] | If enabled, the LSP reoptimization is based solely on the IGP metric. The reoptimization process ignores
the available bandwidth ratio calculations, the least-fill 10 percent congestion improvement rule, and the
hop-counts rule. This statement makes reoptimization more aggressive than the default.
Default
Aggressive o... | [] | 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. | [
"Optimizing Signaled LSPs"
] |
optimize-hold-dead-delay | optimize-hold-dead-delay seconds; | [edit logical-systems logical-system-name protocols mpls],
[edit logical-systems logical-system-name protocols mpls label-switch-path lsp-name],
[edit protocols mpls],
[edit protocols mpls label-switch-path lsp-name] | Allows you to specify the amount of time to delay the tear down of old paths after the router has
switched traffic to new optimized paths. This delay timer starts when the timer specified by the optimize-
switchover-delay statement has elapsed, which is typically 30 seconds, and at the start of the next retry
sequence ... | [
{
"name": "seconds",
"desc": "Configure the time in seconds to wait before tearing down the old paths that were in use prior to the last LSP optimization. Default: 60 to 90 seconds Range: 0 through 65,535 seconds"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | [
"Optimizing Signaled LSPs"
] | |
optimize-switchover-delay | optimize-switchover-delay seconds; | [edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls] | Delays the switch over of LSPs to newly optimized paths. You only need to configure this statement on
routers acting as the ingress for the affected LSPs (you do not need to configure this statement on
transit or egress routers). The specified delay helps to ensure that the new optimized paths have been
established bef... | [
{
"name": "seconds",
"desc": "Configure the time in seconds to wait before switching LSPs to newly optimized paths. Default: 1 second Range: 1 through 900 seconds"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1R1. | [
"Optimizing Signaled LSPs"
] |
optimize-timer (Protocols MPLS) | optimize-timer seconds; | [edit logical-systems logical-system-name protocols mpls],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name (primary |
secondary) path-name],
[edit protocols mpls],
[edit protocols mpls label-sw... | Enable periodic reoptimization of an LSP that is already set up. If topology changes occur, an existing
path might become suboptimal, and a subsequent recomputation might be able to determine a better
path.
NOTE: This feature is useful only on LSPs for which constrained-path computation is
enabled; that is, for which t... | [
{
"name": "seconds",
"desc": "Length of the optimize timer, in seconds."
}
] | 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. | [
"Optimizing Signaled LSPs"
] |
optimize-timer (Protocols RSVP) | optimize-timer seconds; | [edit logical-systems logical-system-name protocols rsvp interface interface-name link-
protection],
[edit protocols rsvp interface interface-name link-protection] | Configure an optimize timer for a bypass LSP. The optimize timer initiates a periodic optimization
process that reshuffles data LSPs among bypass LSPs to achieve the most efficient use of network
resources. The optimization process attempts to either minimize the number of bypasses currently in
use, minimize the total ... | [
{
"name": "seconds",
"desc": "Specify the number of seconds between optimizations."
}
] | 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. | [
"Configuring the Optimization Interval for Bypass LSPs"
] |
option (DHCP server) | option {
[ (id-number option-type option-value) | (id-number array option-type option-value) ];
} | [edit system services dhcp],
[edit system services dhcp pool],
[edit system services dhcp static-binding] | Configure one or more user-defined options that are not included in the Junos default implementation
of the DHCP server. For example, if a client requests a DHCP option that is not included in the DHCP
server, you can create a user-defined option that enables the server to respond to the client’s request. | [
{
"name": "id-number",
"desc": "Any whole number. The ID number is used to index the option and must be unique across"
},
{
"name": "option-type",
"desc": "Any of the following types: byte, byte-stream, flag, integer, ip-address, short, string, unsigned-integer, unsigned-short."
},
{
"na... | 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.0 . | [] |
option (Security IDP) | option {
match (equal | greater-than | less-than | not-equal);
value tcp-option;
} | [edit security idp custom-attack attack-name attack-type signature protocol tcp] | Specify the TCP option type (kind field in the TCP header). | [
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value tcp-option",
"desc": "Match the option value."
}
] | 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. | [] |
option-15 (DHCP Relay Agent) | option-15 {
default-action {
drop drop;
forward-only forward-only;
}
equals {
ascii name {
drop drop;
forward-only forward-only;
}
hexadecimal name {
drop drop;
forward-only forward-only;
}
}
not-present ... | [edit bridge-domains name forwarding-options dhcp-relay dhcpv6 group name relay-option],
[edit bridge-domains name forwarding-options dhcp-relay dhcpv6 relay-option],
[edit forwarding-options dhcp-relay dhcpv6 group name relay-option],
[edit forwarding-options dhcp-relay dhcpv6 relay-option],
[edit logical-systems name... | Specify that the payload of the Option 15 (Vendor Class Identifier) from the client PDU is concatenated
with the username during the subscriber authentication or client authentication process. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4. | [
"DHCPv4 and DHCPv6 Forward-Only Action for Relay Traffic with Unknown DHCP Server Address"
] |
option-16 (DHCP Relay Agent) | option-16 {
default-action {
drop drop;
forward-only forward-only;
}
equals {
ascii name {
drop drop;
forward-only forward-only;
}
hexadecimal name {
drop drop;
forward-only forward-only;
}
}
not-present... | [edit bridge-domains name forwarding-options dhcp-relay dhcpv6 group name relay-option],
[edit bridge-domains name forwarding-options dhcp-relay dhcpv6 relay-option],
[edit forwarding-options dhcp-relay dhcpv6 group name relay-option],
[edit forwarding-options dhcp-relay dhcpv6 relay-option],
[edit logical-systems name... | Specify that the payload of the Option 16 (Vendor Class Identifier) from the client PDU is concatenated
with the username during the subscriber authentication or client authentication process. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4. | [
"DHCPv4 and DHCPv6 Forward-Only Action for Relay Traffic with Unknown DHCP Server Address"
] |
option-16 (DHCPv6 Snooping) | option-16 {
use-string string;
} | [edit vlans vlan-name forwarding-options dhcp-security dhcpv6-options] | Configure the DHCPv6 Vendor ID option (option 16) to be included in DHCPv6 requests from clients
before forwarding them to a DHCPv6 server. Option 16 provides the server with information about the
vendor that manufactured the hardware on which the DHCP client is running. When configured, the
switch will overwrite any e... | [
{
"name": "use-string string",
"desc": "Define a custom string to be used as the DHCPv6 vendor identifier."
}
] | 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 . | [
"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)"
] |
option-18 (DHCPv6 Snooping) | option-18 {
prefix {
host-name;
logical-system-name;
routing-instance-name;
vlan-id;
vlan-name;
}
use-interface-index (device | logical);
use-interface-description (device | logical);
use-interface-mac;
use-interface-name (device | logical);
use-stri... | [edit vlans vlan-name forwarding-options dhcp-security dhcpv6-options] | Configure the DHCPv6 Relay Agent Interface ID option (option 18) to insert information in DHCPv6
requests from clients before forwarding them to a DHCPv6 server. Option 18 provides information
about the port on which the request was received, which the server can use to assign IP addresses,
prefixes, and other configur... | [
{
"name": "use-interface-mac",
"desc": "Use the MAC address of the interface in the DHCPv6 interface ID."
},
{
"name": "use-string string",
"desc": "Use a custom string in the DHCPv6 interface ID. 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. | [] |
option-18 (Interface-ID for DHCPv6 Autosense VLANs) | option-18; | [edit interfaces interface-name auto-configure vlan-ranges authentication username-include],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication username-include] | Specify that Option 18 (Interface-ID) information received in the innermost DHCPv6 Relay-Forward
message header is concatenated with the username during the subscriber authentication process. | [] | 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. | [
"Configuring VLAN Interface Username Information for AAA Authentication",
"Inserting DHCPv6 Interface-ID Option (Option 18) In DHCPv6 Packets",
"Creating Unique Usernames for DHCP Clients",
"Using DHCP Option 18 and Option 37 in Authentication Usernames for DHCPv6 Autosense VLANs"
] |
option-37 (DHCPv6 Snooping) | option-37 {
prefix {
host-name;
logical-system-name;
routing-instance-name;
vlan-id;
vlan-name;
}
use-interface-index (device | logical);
use-interface-description (device | logical);
use-interface-mac;
use-interface-name (device | logical);
use-strin... | [edit vlans vlan-name forwarding-options dhcp-security dhcpv6-options] | Configure the DHCPv6 Relay Agent Remote ID option (option 37) to insert information in DHCPv6
requests from clients before forwarding them to a DHCPv6 server. Option 37 provides information
about the remote host, which the server can use to assign IP addresses, prefixes, and other configuration
parameters for the clien... | [
{
"name": "use-interface-mac",
"desc": "Use the MAC address of the interface in the DHCPv6 remote ID."
},
{
"name": "use-string string",
"desc": "Use a custom string in the DHCPv6 remote ID. 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)"
] |
option-37 (Relay Agent Remote-ID for DHCPv6 Autosense VLANs) | option-37; | [edit interfaces interface-name auto-configure vlan-ranges authentication username-include],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication username-include] | Specify that Option 37 (DHCPv6 Relay Agent Remote-ID) information, received in the innermost
DHCPv6 Relay-Forward message header, is concatenated with the username during the subscriber
authentication process. | [] | 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. | [
"Configuring VLAN Interface Username Information for AAA Authentication",
"Creating Unique Usernames for DHCP Clients",
"Inserting DHCPv6 Interface-ID Option (Option 18) In DHCPv6 Packets",
"Using DHCP Option 18 and Option 37 in Authentication Usernames for DHCPv6 Autosense VLANs"
] |
option-60 (DHCP Local Server) | option-60; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server authentication username-include],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server group group-name authentication username-include],
[... | Specify that the payload of Option 60 (Vendor Class Identifier) from the client PDU be concatenated
with the username during the subscriber authentication or DHCP client authentication process. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Specifying Authentication Support"
] |
option-60 (DHCP Relay Agent) | option-60 {
default-action {
drop drop;
forward-only forward-only;
local-server-group local-server-group;
}
equals {
ascii name {
drop drop;
forward-only forward-only;
local-server-group local-server-group;
}
hexadecimal nam... | [edit bridge-domains name forwarding-options dhcp-relay group name relay-option],
[edit bridge-domains name forwarding-options dhcp-relay relay-option],
[edit forwarding-options dhcp-relay group name relay-option],
[edit forwarding-options dhcp-relay relay-option],
[edit logical-systems name bridge-domains name forward... | Specify that the payload of the Option 60 (Vendor Class Identifier) from the client PDU is concatenated
with the username during the subscriber authentication or client authentication process. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
Statement updated in Junos OS Release 17.4R1 for MX Series. | [
"Specifying Authentication Support",
"DHCPv4 and DHCPv6 Forward-Only Action for Relay Traffic with Unknown DHCP Server Address"
] |
option-77 (DHCP Relay Agent) | option-77 {
default-action {
drop drop;
forward-only forward-only;
local-server-group local-server-group;
}
equals {
ascii name {
drop drop;
forward-only forward-only;
local-server-group local-server-group;
}
hexadecimal na... | [edit bridge-domains name forwarding-options dhcp-relay group name relay-option],
[edit bridge-domains name forwarding-options dhcp-relay relay-option],
[edit forwarding-options dhcp-relay group name relay-option],
[edit forwarding-options dhcp-relay relay-option],
[edit logical-systems name bridge-domains name forward... | Specify that the payload of the Option 77 (Vendor Class Identifier) from the client PDU is concatenated
with the username during the subscriber authentication or client authentication process. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4. | [
"DHCPv4 and DHCPv6 Forward-Only Action for Relay Traffic with Unknown DHCP Server Address"
] |
option-79 | option-79; | [edit vlans vlan-name forwarding-options dhcp-security dhcpv6-options] | Configure the DHCPv6 client link layer option (option 79) to include the source MAC address in
DHCPv6 requests from clients before the messages are forwarded to a DHCPv6 server. In a dual-stack
network environment in which devices act as both DHCPv4 and DHCPv6 clients, the client MAC
address can be used to associate DH... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Inserting the DHCPv6 Client MAC Address Option (Option 79) In DHCPv6 Packets"
] |
option-82 (Address-Assignment Pools) | option-82 {
circuit-id value range named-range;
remote-id value range named-range;
} | [edit access address-assignment pool pool-name family inet dhcp-attributes option-match],
[edit access protocol-attributes attribute-set-name option-match] | Specify the list of option 82 suboption match criteria used to select the named address range used for
the client. The server matches the option 82 value in the user PDU to the specified option 82 match
criteria and uses the named address range associated with the string. | [
{
"name": "circuit-id",
"desc": "Configure the address-assignment pool named-range to use for a particular option 82 Agent Circuit ID value. Values:"
},
{
"name": "value",
"desc": "String for the Agent Circuit ID suboption (suboption 1) of the DHCP relay"
},
{
"name": "range named-range... | 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. | [
"Address-Assignment Pools for Subscriber Management"
] |
option-82 (DHCP Local Server Authentication) | option-82 <circuit-id> <remote-id>; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server authentication username-include],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server group group-name authentication username-include],
[... | Specify the type of Option 82 information from the client PDU that is concatenated with the username
during the subscriber authentication or DHCP client authentication process. You can specify either,
both, or neither of the Agent Circuit ID and Agent Remote ID suboptions. If you specify both, the Agent
Circuit ID is s... | [
{
"name": "circuit-id",
"desc": "(Optional) Agent Circuit ID suboption (suboption 1)."
},
{
"name": "remote-id",
"desc": "(Optional) Agent Remote ID suboption (suboption 2)."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Specifying Authentication Support"
] |
option-82 (DHCP Local Server Pool Matching) | option-82; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server pool-match-order],
[edit logical-systems logical-system-name system services dhcp-local-server pool-match-order],
[edit routing-instances routing-instance-name system services dhcp-local-server pool-matc... | Configure the extended DHCP local server to use the option 82 value in the DHCP client DHCP PDU
together with the ip-address-first method to determine which address-assignment pool to use. You must
configure the ip-address-first statement before configuring the option-82 statement. The DHCP local
server first determine... | [] | 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. | [
"Configuring How the Extended DHCP Local Server Determines Which Address-Assignment Pool to",
"Use",
"Understanding Differences Between Legacy DHCP and Extended DHCP",
"Address-Assignment Pools Overview"
] |
option-82 (DHCP Relay Agent) | option-82 <circuit-id> <remote-id>; | [edit forwarding-options dhcp-relay authentication username-include],
[edit forwarding-options dhcp-relay group group-name authentication username-include],
[edit logical-systems logical-system-name forwarding-options dhcp-relay authentication username-
include],
[edit logical-systems logical-system-name forwarding-opt... | Specify the option 82 that is concatenated with the username during the subscriber authentication or
client authentication process. You can specify either, both, or neither the Agent Circuit ID and the Agent
Remote ID suboptions. If you specify both, the Agent Circuit ID is supplied first, followed by a delimiter,
and ... | [
{
"name": "circuit-id",
"desc": "(Optional) The string for the Agent Circuit ID suboption (suboption 1)."
},
{
"name": "remote-id",
"desc": "(Optional) The string for the Agent Remote ID suboption (suboption 2)."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Specifying Authentication Support"
] |
option-82 (interfaces) | option-82 <circuit-id> <remote-id>; | [edit interfaces interface-name auto-configure vlan-ranges authentication username-include],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication username-include] | Specify that the option 82 information from the client PDU is concatenated with the username during
the subscriber authentication process.
For autosense VLANs, you can additionally specify Option 82 suboption information that is
concatenated with the username. You can specify either both or neither of the Agent Circuit... | [
{
"name": "none",
"desc": "Use the raw payload of Option 82 from the PDU."
},
{
"name": "circuit-id",
"desc": "(Optional) Use the Agent Circuit ID suboption (suboption 1)."
},
{
"name": "remote-id",
"desc": "(Optional) Use the Agent Remote ID suboption (suboption 2)."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
Options circuit-id and remote-id introduced in Junos OS Release 11.4. | [
"Configuring VLAN Interface Username Information for AAA Authentication",
"Using DHCP Option 82 Suboptions in Authentication Usernames for Autosense VLANs"
] |
option-82 | option-82 {
circuit-id {
prefix (host-name | routing-instance-name);
use-interface-description;
use-vlan-id;
}
remote-id {
host-name;
mac (Option 82);
use-interface-description;
use-string string;
}
vendor-id {
... | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security] | Have the device insert DHCP option 82 (also known as the DHCP relay agent information option)
information in the DHCP request packet header of a DHCP request that it receives from a DHCP client
connected to one of its interfaces before it forwards or relays that DHCP request to a DHCP server. The
server uses the option... | [] | 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. | [
"Setting Up DHCP Option 82 on the Switch with No Relay (ELS)",
"Understanding DHCP Option 82",
"Understanding DHCP Snooping (non-ELS)",
"http://tools.ietf.org/html/rfc3046"
] |
option-match | option-match {
option-82 {
circuit-id value range named-range;
remote-id value range named-range;
}
} | [edit access address-assignment pool pool-name family inet dhcp-attributes],
[edit access protocol-attributes attribute-set-name] | Specify a list of match criteria used to determine which named address range in the address-assignment
pool to use. The extended DHCP local server matches this information to the match criteria specified in
the client PDUs. For example, for option 82 match criteria, the server matches the option 82 value in the
user PD... | [] | 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. | [
"Address-Assignment Pools for Subscriber Management"
] |
option-number (DHCP Relay Agent Option) | option-number option-number; | [edit forwarding-options dhcp-relay relay-option],
[edit forwarding-options dhcp-relay dhcpv6 relay-option],
[edit forwarding-options dhcp-relay group group-name relay-option],
[edit forwarding-options dhcp-relay dhcpv6 group group-name relay-option],
[edit logical-systems logical-system-name forwarding-options dhcp-re... | Specify the DHCP option DHCP relay agent uses for selective processing of client traffic. You can
configure support globally or for a named group of interfaces. You can also configure support for the
extended DHCP relay agent on a per logical system and per routing instance basis.
Use the [edit forwarding-options dhcp-... | [
{
"name": "option-number",
"desc": "The DHCP or DHCPv6 option in the incoming traffic."
},
{
"name": "15 (DHCPv6 only)",
"desc": "Use DHCPv6 option 15 (User Class Option) in packets"
},
{
"name": "16 (DHCPv6 only)",
"desc": "(MX Series routers and EX Series switches only) Use DHCPv6 ... | 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. | [
"Using DHCP Option Information to Selectively Process DHCP Client Traffic"
] |
option-order (DHCP Relay Agent) | option-order name; | [edit bridge-domains name forwarding-options dhcp-relay group name relay-option],
[edit bridge-domains name forwarding-options dhcp-relay relay-option],
[edit forwarding-options dhcp-relay group name relay-option],
[edit forwarding-options dhcp-relay relay-option],
[edit logical-systems name bridge-domains name forward... | Options precedence order | [
{
"name": "name",
"desc": "Option number Values:"
},
{
"name": "60",
"desc": "Option 60"
},
{
"name": "77",
"desc": "Option 77"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4. | [
"DHCPv4 and DHCPv6 Forward-Only Action for Relay Traffic with Unknown DHCP Server Address"
] |
option-refresh-rate (Services) | option-refresh-rate | [edit services flow-monitoring version9 template template-name] | Specifies the frequency at which the flow generator needs to send the Jflow options template (both
template and system scope) to the collector.
Option refresh rate can be configured as number of packets. If the number of packets configured is “n”, it
indicates that after every export of “n” data packets to the collecto... | [
{
"name": "packets",
"desc": "Specify the number of packets. The range is from 1 through 480,000."
},
{
"name": "seconds",
"desc": "Specify the number of seconds. The range is from 10 through 600."
}
] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Flow Aggregation to Use Version 9 Flow Templates"
] |
option-refresh-rate | option-refresh-rate packets packets seconds seconds; | [edit services flow-monitoring version9 template template-name],
[edit services flow-monitoring version-ipfix template template-name] | Specify the frequency at which the flow generator sends updates about template options, such as
sampling rate, to the flow collector. Specify the refresh rate, in either the number of packets or seconds. | [
{
"name": "packets",
"desc": "Refresh rate, in number of packets."
},
{
"name": "seconds",
"desc": "Refresh rate, in number of seconds."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3.
Support at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level added in
Junos OS Release 10.2.
Support at the [edit services flow-monitoring version9 template template-name] hierarchy level added in Junos
OS Release 16.1 for MPLS traffic... | [
"Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9",
"Flow Templates",
"Configuring Inline J-Flow to Use IPFIX Flow Templates on MX, vMX and T Series Routers, EX Series",
"Switches, NFX Series Devices, and SRX Devices"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.