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 |
|---|---|---|---|---|---|---|---|
option-type | option-type {
match (equal | greater-than | less-than | not-equal);
value header-value;
} | [edit security idp custom-attack attack-name attack-type signature protocol ipv6 extension-
header destination-option] | Specify the type of option for destination header type. | [
{
"name": "value",
"desc": "Match a decimal value. Range: 0 through 255"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
optional (Commit Scripts) | optional; | [edit system scripts commit file filename] | Allow a commit operation to succeed even if the commit script specified in the file statement is missing
from the appropriate commit script directory on the device.
NOTE: Commit scripts are stored on a device’s hard disk in the /var/db/scripts/commit
directory or on the flash drive in the /config/scripts/commit directo... | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Controlling Execution of Commit Scripts During Commit Operations"
] |
optional (Event Scripts) | optional; | [edit event-options event-script] | For Junos OS event scripts, globally indicate the physical presence of the scripts as optional to allow
commits to proceed if they are missing. Scripts can be missing, for example, if the primary storage on the
device running Junos OS becomes corrupted.
If you do not configure the optional statement, the event process ... | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 16.1. | [] |
optional-parameters | optional-parameters parameter-name parameter-value; | [edit security idp custom-attack attack-name attack-type signature] | Configure the Hyperscan optional parameters to enhance the pattern matching process. | [
{
"name": "max-offset",
"desc": "Maximum offset in the data stream at which the pattern match ends."
},
{
"name": "min-length",
"desc": "Minimum match length required to successfully match the pattern."
},
{
"name": "min-offset",
"desc": "Minimum offset in the data stream at which th... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1R1. | [] |
options (Access Profile) | options {
accounting-session-id-format (decimal | description);
calling-station-id-delimiter delimiter-character;
calling-station-id-format {
agent-circuit-id;
agent-remote-id;
interface-description;
nas-identifier;
}
chap-challenge-in-request-authenticator;
clien... | [edit access profile profile-name radius] | Configure the options used by RADIUS authentication and accounting servers. | [
{
"name": "accounting-session-id-format",
"desc": "(EX Series, MX Series only) Configure the format the router or switch uses to identify the accounting session. The default is decimal. Values:"
},
{
"name": "decimal",
"desc": "Use the decimal format."
},
{
"name": "description",
"d... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
juniper-dsl-attributes introduced in Junos OS Release 11.4.
nas-port-id-delimiter introduced in Junos OS Release 11.4. Statement introduced in Junos OS Release
13.2X50-D10 for EX Series switches.
calling-station-id-delimiter introduced in Junos OS Release 13.1.
ip-address-c... | [
"RADIUS Servers and Parameters for Subscriber Access",
"RADIUS Authentication and Accounting Basic Configuration"
] |
options (Routing Options) | options {
syslog (level level | upto level level);
} | [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] | Configure the types of system logging messages sent about the routing protocols process to the system
message logging file. These messages are also displayed on the system console. You can log messages at
a particular level, or up to and including a particular level. | [
{
"name": "level level",
"desc": "Severity of the message. It can be one or more of the following levels, in order of decreasing"
},
{
"name": "urgency:",
"desc": ""
},
{
"name": "alert",
"desc": "Conditions that should be corrected immediately, such as a corrupted system database."
... | 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. | [
"Junos OS Administration Library for Routing Devices"
] |
options (Class of Service) | options {
hierarchical-scheduler-disable;
} | [edit class-of-service] | Configure class-of-service optional parameters. | [
{
"name": "hierarchical-scheduler-disable",
"desc": "Disable HCoS scheduler mode. You must disable HCoS scheduler mode and reboot the device to ECN packet statistics."
}
] | 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. | [] |
options-template-id | options-template-id id; | [edit services flow-monitoring version9 template template-name],
[edit services flow-monitoring version-ipfix template template-name] | Define a unique options template ID to be used for flow aggregation of version 9 and IPFIX flows. After
a re-start of the exporting process, the software may re-assign option template IDs.
MX and QFX Series
The options template ID can be a value in the range of 1024 through 65535. If you do not configure
values for the... | [
{
"name": "id",
"desc": "Unique identifier for the options template to be used for version 9 or IPFIX flows. The range 0-255"
}
] | 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 Release 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"
] |
order (Application Identification) | order order; | [edit services application-identification application name address-mapping name],
[edit services application-identification application application-name icmp-mapping],
[edit services application-identification application application-name ip-protocol-mapping],
[edit services application-identification application appli... | Define application matching priority. For address configurations, the order number resolves the conflict
when multiple address entries are matched for a specific session. The lower number has a higher
priority. | [
{
"name": "order",
"desc": "Order sequence number. This value is mandatory and must be unique. Default: 0 Range: 0 through 65,535"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support for Next Gen Services introduced in Junos OS Release 19.3R1 on MX Series.
Support at the [edit services application-identification application application-name] hierarchy level
introduced in Junos OS Releases 19.3R2 and 19.4R1 on MX Series MX240, MX480 and MX960 us... | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
order (Security IDP) | order; | [edit security idp custom-attack attack-name attack-type chain] | Create a compound attack object that must match each member signature or protocol anomaly in the
order you specify. If you do not specify an ordered match, the compound attack object still must match
all members, but the attacks or protocol anomalies can appear in random order. | [] | 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. | [] |
order (Services Application Identification) | order number; | [edit services application-identification nested-application name signature name member name],
[edit services application-identification rule rule-name address] | Define application matching priority. For address configurations, the order number resolves the conflict
when multiple address entries are matched for a specific session. The lower number has higher priority. | [
{
"name": "number",
"desc": "Order number. This value is mandatory and must be unique."
}
] | 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 APPID Rules",
"Application Identification for Nested Applications"
] |
order | order [ accounting-method ]; | [edit access profile profile-name accounting] | Set the order in which the Junos OS tries different accounting methods for client activity. When a client
logs in, the software tries the accounting methods in the specified order. | [
{
"name": "accounting-method",
"desc": "One or more accounting methods. When a client logs in, the software tries the"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"RADIUS Authentication and Accounting Basic Configuration"
] |
order-priority (Application Identification) | order-priority (high | low); | [edit services application-identification application application-name address-mapping name],
[edit services application-identification application application-name icmp-mapping],
[edit services application-identification application application-name ip-protocol-mapping],
[edit services application-identification appli... | Define the priority of signatures when both a custom signature and predefined signature apply to a
protocol bundle. | [
{
"name": "high",
"desc": "Custom signatures have priority over predefined signatures."
},
{
"name": "low",
"desc": "Predefined signatures have priority over custom signatures. Default: high"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support for Next Gen Services introduced in Junos OS Releases 19.3R2 and 19.4R1 on MX Series
MX240, MX480 and MX960 using the MX-SPC3 services card. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
origin (Diameter Base Protocol) | origin {
host hostname;
realm realm-name;
} | [edit access diameter] | Specify values of the Origin-Realm AVP and the Origin-Host AVP used in all messages sent by the
Diameter instance. These values must be unique for each session PIC.
The remaining statements are explained separately. See CLI Explorer. | [] | 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. | [] |
origin (Diameter Base Protocol) | origin realm realm-name host hostname | [edit diameter] | Specify the hostname and realm of the endpoint node that originates Diameter messages for the
Diameter instance. The Diameter instance supplies these values to be conveyed by the Origin-Realm-
AVP and Origin-Host-AVP for all messages sent by the Diameter instance.
NOTE: Both the host and realm are mandatory. | [
{
"name": "host hostname",
"desc": "Name of the message origin host that is supplied as the value of the Origin-Host AVP for all Diameter messages in the Diameter master instance."
},
{
"name": "realm realm-name",
"desc": "Name of the message origin realm, that is supplied as the value of the Or... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configuring Diameter",
"Configuring the Origin Attributes of the Diameter Instance"
] |
origin-autonomous-system (Origin Validation for BGP) | origin-autonomous-system as-number {
validation-state (invalid | valid);
} | [edit logical-systems logical-system-name routing-instances instance-name routing-options
validation static record destination maximum-length prefix-length],
[edit logical-systems logical-system-name routing-options validation static record destination
maximum-length prefix-length],
[edit routing-instances instance-n... | Configure the legitimate originator autonomous system (AS). This is a required statement. | [
{
"name": "as-number",
"desc": "Configure a legitimate originator AS number."
},
{
"name": "validation-state (invalid |",
"desc": ""
},
{
"name": "valid)",
"desc": "Configure the validation state for a route validation record. Values: Configure one of two mutually exclusive validati... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring Origin Validation for BGP",
"Use Case and Benefit of Origin Validation for BGP",
"Understanding Origin Validation for BGP",
"Example: Configuring Origin Validation for BGP"
] |
origin-validation | origin-validation accept | reject; | [edit protocols bgp ebgp-community-cleanup],
[edit protocols bgp group group-name ebgp-community-cleanup],
[edit protocols bgp group group-name neighbor address ebgp-community-cleanup] | You can choose to accept or reject the origin validation extended communities received from an eBGP
peer. The default behavior of Origin Validation State Extended Community (OVS EC) is to reject any
eBGP peer received. You can configure it to accept the community when needed by choosing the origin-
validation accept op... | [] | Statement ontroduced in Junos OS Release 22.2R1. | [] | |
originator | originator {
max-advertisements max-advertisements;
metric metric;
unplanned-lifetime seconds;
} | [edit logical-systems name protocols isis prefix-unreachable],
[edit logical-systems name routing-instances name protocols isis prefix-unreachable],
[edit logical-systems name tenants name routing-instances name protocols isis prefix-
unreachable],
[edit protocols isis prefix-unreachable],
[edit routing-instances name ... | Parameters for originating unreachable prefix advertisements. | [
{
"name": "max-advertisements",
"desc": "Maximum UPAs that can be originated at any point of time Range: 1 through 10000"
},
{
"name": "metric",
"desc": "Metric value of unplanned UPA Range: 4261412865 through 4294967295"
},
{
"name": "unplanned-lifetime",
"desc": "Lifetime of unpl... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1. | [] |
ospf3 | ospf3 {
domain-id domain-id;
domain-vpn-tag number;
route-type-community (iana | vendor);
traffic-engineering {
<advertise-unnumbered-interfaces>;
<credibility-protocol-preference>;
ignore-lsp-metrics;
multicast-rpf-routes;
no-topology;
shortcuts {
... | [edit logical-systems logical-system-name protocols],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit protocols],
[edit routing-instances routing-instance-name protocols] | Enable OSPFv3 routing on the routing device. You must include the ospf3 statement to enable OSPFv3.
By default, OSPFv3 is disabled. | [
{
"name": "domain-id",
"desc": ""
},
{
"name": "domain-id",
"desc": "The domain ID identifies the OSPF domain from which the route originated. If the router ID is not configured in the routing instance, the router ID is derived from an interface address belonging to the routing instance. The def... | 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. | [
"Understanding OSPF Configurations"
] |
ospf | ospf {
domain-id domain-id;
domain-vpn-tag number;
route-type-community (iana | vendor);
traffic-engineering {
<advertise-unnumbered-interfaces>;
<credibility-protocol-preference>;
ignore-lsp-metrics;
multicast-rpf-routes;
no-topology;
shortcuts {
... | [edit logical-systems logical-system-name protocols],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit protocols],
[edit routing-instances routing-instance-name protocols] | Enable OSPF routing on the routing device. You must include the ospf statement to enable OSPF on the
routing device. By default, OSPF is disabled. | [
{
"name": "domain-id",
"desc": ""
},
{
"name": "domain-id",
"desc": "The domain ID identifies the OSPF domain from which the route originated. If the router ID is not configured in the routing instance, the router ID is derived from an interface address belonging to the routing instance. The def... | 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. | [
"Understanding OSPF Configurations"
] |
ospf-instance | ospf-instance igpinstance-
name{ ... } | [edit logical-systems logical-system-name protocols],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit protocols] | Enable multiple IGP instances of OSPFv2 routing on the routing device. The OSPFv2 IGP instance is
associated with the default routing-instance and the default RIB. An OSPFv2 IGP instance exports
routes installed in the RIB by another OSPFv2 IGP instance using standard Junos OS routing policy
configuration. 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 24.2R1. | [] |
oss-map | oss-map {
model-name t640|t1600;
} | [edit chassis] | Configure the operations support systems (OSS) mapping feature to map a T4000 chassis to a T1600
chassis or a T640 chassis, so that the T4000 chassis is represented as a T1600 chassis or a T640 chassis,
respectively. The configuration helps prevent requalifying the T1600 chassis and T640 chassis as a new
chassis on the... | [
{
"name": "model-name t640",
"desc": "Perform OSS mapping on a T4000 chassis to represent it as a T640 chassis, thereby"
},
{
"name": "model-name t1600",
"desc": "Perform OSS mapping on a T4000 chassis to represent it as a T1600 chassis, thereby"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3R3, 13.1R2, and 13.2R1. | [
"Configuring OSS Mapping to Represent a T4000 Chassis as a T1600 or a T640 Chassis",
"Example: Configuring a T4000 Chassis to Represent a T640 Chassis"
] |
otc-local-role | otc-local-role {
customer|provider|peer|route-server|route-server-client {
strict|not-negotiated;
}
} | [edit protocols bgp],
[edit protocols bgp group groupname],
[edit protocols bgp group groupname neighbor peer address] | strict
BGP local role strict mode
not-negotiated
BGP local role not-negotiated mode
Provider
Provider role
customer
Customer role
peer
Peer role
route-server
Route-Server role
route-server-client
Route-Server-Client role | [
{
"name": "strict",
"desc": ""
},
{
"name": "not-negotiated",
"desc": "Provider"
},
{
"name": "customer",
"desc": ""
},
{
"name": "peer",
"desc": ""
},
{
"name": "route-server",
"desc": ""
},
{
"name": "route-server-client",
"desc": ""
}
] | routing—To view this statement in the configuration.
routing-control— To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1. | [] |
other | other {
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] | Use other parameter to limit the number of packets per second for all the other GTPv0/GTPv1-C/
GTPv2-C messages.
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-rate-limit mes... | [
{
"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"
] |
other-bytes | other-bytes bytes; | [edit protocols ancp qos-adjust] | 17.4R1
Starting in Junos OS Release 17.4R1, this statement is deprecated and replaced by the other-overhead-
bytes option of the access-line statement at the [edit system] hierarchy level. | [
{
"name": "bytes",
"desc": "Number of bytes added to or subtracted from the actual downstream frame overhead. Range: -100 through 100 bytes Default: 0 bytes"
}
] | 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.
Statement deprecated in Junos OS Release 17.4R1.
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 | [
"Configuring the ANCP Agent to Report Traffic Rates to CoS",
"Traffic Rate Reporting and Adjustment by the ANCP Agent",
"Configuring the ANCP Agent"
] |
other-overhead-adjust | other-overhead-adjust percentage; | [edit protocols ancp qos-adjust] | 17.4R1
Starting in Junos OS Release 17.4R1, this statement is deprecated and replaced by the other-overhead-
adjust option of the access-line statement at the [edit system] hierarchy level. | [
{
"name": "percentage",
"desc": "Percentage by which to multiply the rate. Range: 80 through 100 percent Default: 100 percent"
}
] | 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.
Statement deprecated in Junos OS Release 17.4R1.
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 | [
"Configuring the ANCP Agent to Report Traffic Rates to CoS",
"Traffic Rate Reporting and Adjustment by the ANCP Agent",
"Configuring the ANCP Agent"
] |
other-stateful-configuration (Dynamic Router Advertisement) | (other-stateful-configuration | no-other-stateful-configuration); | [edit dynamic-profiles protocols router-advertisement interface interface-name] | Specify whether to enable autoconfiguration of other nonaddress-related information:
•
no-other-stateful-configuration—Disable autoconfiguration of other nonaddress-related information.
•
other-stateful-configuration—Enable autoconfiguration of other nonaddress-related information.
Default
The configured object is disa... | [] | 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"
] |
other-stateful-configuration | (other-stateful-configuration | no-other-stateful-configuration); | [edit logical-systems logical-system-name protocols router-advertisement interface interface-
name],
[edit protocols router-advertisement interface interface-name] | Specify whether to enable autoconfiguration of other nonaddress-related information:
•
no-other-stateful-configuration—Disable autoconfiguration of other nonaddress-related information.
•
other-stateful-configuration—Enable autoconfiguration of other nonaddress-related information.
Default
By default, stateful autoconf... | [] | 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",
"Secure IPv6 Neighbor Discovery"
] |
otn-options | otn-options {
bytes (otn-options) transmit-payload-type value;
fec (efec | gfec | gfec-sdfec | none );
(is-ma | no-is-ma);
(laser-enable | no-laser-enable);
(line-loopback | no-line-loopback);
(local-loopback | no-local-loopback);
(odu-ttim-action-enable | no-odu-ttim-action-enable);
(ot... | [edit interfaces ge-fpc/pic/port],
[edit interfaces xe-fpc/pic/port],
[edit interfaces et-fpc/pic/port] | Specify the Ethernet optical transport network (OTN) interface and options. | [] | interfaces—To view this statement in the configuration.
interfaces-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
bytes, is-ma, local-loopback, no-is-ma, no-local-loopback, no-odu-ttim-action-enable, no-otu-ttim-action-enable, no-
prbs, odu-delay-management, odu-ttim-action-enable, otu-ttim-action-enable, prbs, preemptive-fast-reroute, and signal-
degrade statements introduced in Junos... | [
"10-Gigabit Ethernet OTN Options Configuration Overview",
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
otu4 | otu4; | [edit interfaces interface-name otn-options rate] | Sets the line rate or speed of the OTN signal to optical channel transport unit 4 (OTU4).
Default
By default, the rate is OTU4 on PTX Series routers. | [
{
"name": "otu4",
"desc": ""
},
{
"name": "OTU4 line rate or 100 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.2. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
otu-ttim-action-enable | (otu-ttim-action-enable | no-otu-ttim-action-enable); | [edit interfaces interface-name otn-options] | Specify whether consequent action for Optical Channel Transport Unit (OTU) TTIM is enabled or
disabled.
Default
If you omit the otu-ttim-action-enable statement, consequent action for OTU TTIM is disabled. | [
{
"name": "otu-ttim-action-enable",
"desc": "Enable consequent action for OTU TTIM."
},
{
"name": "no-otu-ttim-action-enable",
"desc": "Disable consequent action for OTU 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"
] |
out-delay | out-delay seconds; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Control how often BGP and the routing table exchange route information by specifying how long a route
must be present in the Junos OS routing table before it is exported to BGP. Use this time delay to help
bundle routing updates and to avoid sending updates too often.
Alternatively or in addition, external BGP (EBGP) s... | [
{
"name": "seconds",
"desc": "Output delay time."
}
] | 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. | [] |
out-of-resources (Security Antivirus Sophos Engine) | default (block | log-and-permit | permit); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus sophos-engine profile profile-name fallback-
options] | Virus scanning requires a great deal of memory and CPU resources. Due to resource constraints,
memory allocation requests can be denied by the system. When out-of-resources occurs, scanning is
terminated. | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
},
{
"name": "permit",
"desc": "Permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Sophos Antivirus Configuration Overview"
] |
out-of-resources | out-of-resources (block | (log-and-permit); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name
fallback-options]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name fallback-
options] | Virus scanning requires a great deal of memory and CPU resources. Due to resource constraints,
memory allocation requests can be denied by the system. When out-of-resources occurs, scanning is
terminated. The default action is block. | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
outbound-https | outbound-https {
client client-id {
address {
port port;
trusted-cert trusted-cert;
}
device-id device-id;
reconnect-strategy (in-order | sticky);
secret password;
... | [edit system services] | Configure a Junos device that’s behind a firewall to initiate outbound HTTPS connections to
communicate with client management applications on the other side of the firewall. The outbound-https
configuration is consumed by the outbound HTTPS extension service. You must configure this service at
the [edit system extensi... | [
{
"name": "client client-id",
"desc": "Define a device-initiated outbound HTTPS connection. This value serves to uniquely identify the outbound-https configuration stanza. Each stanza represents a connection to a single outbound HTTPS client. Thus, the administrator is free to assign the client-id any meani... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.3R1.
Statement introduced in Junos OS Evolved Release 22.4R1. | [
"NETCONF and Shell Sessions over Enhanced Outbound HTTPS"
] |
outbound-route-filter | outbound-route-filter {
bgp-orf-cisco-mode;
prefix-based {
accept {
(inet | inet6);
}
}
} | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Configure a BGP peer to accept outbound route filters from a remote peer. | [
{
"name": "accept",
"desc": "Specify that outbound route filters from a BGP peer be accepted."
},
{
"name": "inet",
"desc": "Specify that IPv4 prefix-based outbound route filters be accepted."
},
{
"name": "inet6",
"desc": "Specify that IPv6 prefix-based outbound route filters be acc... | 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. | [
"Example: Configuring BGP Prefix-Based Outbound Route Filtering"
] |
outbound-ssh | outbound-ssh {
client client-id {
address {
port port-number;
retry number;
timeout seconds;
}
device-id device-id;
keep-alive {
retry number;
timeout seconds;
}
proxy-server {
dhcp;
s... | [edit system services] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "client client-id",
"desc": "Defines a device-initiated connection. This value serves to uniquely identify the outbound-ssh configuration stanza. Each outbound-ssh stanza represents a single outbound SSH connection. Thus, the administrator is free to assign the client-id any meaningful unique valu... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Support for IPv6 addresses added in Junos OS Release 12.1X47-D15.
routing-instance option introduced in Junos OS Release 19.3R1 for SRX Series and MX Series devices. | [] |
outer-tag-protocol-id (RFC 2544 Benchmarking) | outer-tag-protocol-id; | [edit services rpm rfc2544-benchmarkingtests test-name test-name] | TPID to be used in the outer VLAN tag. Supported values are 0x8100, 0x88a8, 0x9100, 0x9200 | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X53. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
outgoing-queue | outgoing-queue {
<high-watermark high-watermark>;
<low-watermark low-watermark>;
size size;
} | [edit access diameter peer peer-name] | Configure the outgoing queue properties for this peer. When the queue size reaches the high
watermark, the peer is marked unavailable, any new messages to the Diameter network element are not
sent to this peer, and the SNMP trap Diameter_PeerOutQHiWMarkNotif is generated. When the queue
size descends below the low wate... | [
{
"name": "high-watermark high-watermark",
"desc": "(Optional) Use the specified high watermark for this peer. Range: 1 through 100 percent Default: 80"
},
{
"name": "low-watermark low-watermark",
"desc": "(Optional) Use the specified low watermark for this peer. Range: 1 through 100 percent ... | 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 Diameter Peers"
] |
output (Accounting) | output {
aggregate-export-interval seconds;
cflowd hostname {
aggregation {
autonomous-system;
destination-prefix;
protocol-port;
source-destination-prefix {
caida-compliant;
}
source-prefix;
}
autono... | [edit forwarding-options accounting name] | Configure cflowd, output interfaces, and flow properties.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Discard Accounting",
"Configuring Discard Accounting"
] |
output (Congestion Notification) | output {
ieee-802.1 {
code-point [code-point-bits] {
flow-control-queue [queue | list-of-queues];
}
}
} | [edit class-of-service congestion-notification-profile profile-name] | Configure priority-based flow control (PFC) on output queues. | [] | 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. | [
"Configuring CoS PFC (Congestion Notification Profiles)",
"Example: Configuring Two or More Lossless FCoE IEEE 802.1p Priorities on Different FCoE Transit",
"Switch Interfaces",
"Example: Configuring Two or More Lossless FCoE Priorities on the Same FCoE Transit Switch",
"Interface",
"Example: Configuring ... |
output (Dynamic Service Sets) | output {
service-set service-set-name {
service-filter filter-name;
}
} | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family service],
[edit dynamic-profiles profile-name interfaces pp0 unit $junos–interface–unit family family service] | Define the output service sets and filters to be applied to traffic by a dynamic profile.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [
{
"name": "service-set-name",
"desc": "Name of the service set."
}
] | 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 of the [edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit” family family
service] hierarchy level introduced in Junos OS Release 10.1. | [
"Dynamic Service Sets Overview",
"Associating Service Sets with Interfaces in a Dynamic Profile"
] |
output (Forwarding Table) | output filter-name; | [edit forwarding-options family (inet | inet6 | mpls) filter],
[edit routing-instances routing-instance-name forwarding-options family (inet | inet6 | mpls)
filter] | Configure filtering on the egress traffic of the forwarding table. | [
{
"name": "filter-name",
"desc": "Name of the applied filter."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Applying Forwarding Table Filters"
] |
output (Mirroring) | output {
bridge-domain bridge-domain-name;
interface interface-name;
next-hop-group next-hop-group-name;
routing-instance {
instance-name {
bridge-domain {
bridge-domain-name;
}
}
vlan (vlan-id | vlan-name);
}
vlan (vlan-id | vlan-... | [edit forwarding-options analyzer analyzer-name] | Configure the destination for mirrored traffic, either an interface on the network device for local
monitoring, or a VLAN or bridge domain, for remote monitoring.
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 13.2X50-D10. | [
"Example: Configuring Port Mirroring Analyzers for Local Monitoring of Employee Resource Use",
"Example: Configuring Port Mirroring for Remote Monitoring of Employee Resource Use"
] |
output (Monitoring) | output {
cflowd hostname port port-number;
export-format format;
flow-active-timeout seconds;
flow-export-destination {
(cflowd-collector | collector-pic);
}
flow-inactive-timeout seconds;
interface interface-name {
engine-id number;
engine-type number;
input-... | [edit forwarding-options monitoring name family inet] | Configure cflowd, output interfaces, and flow properties.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Flow Monitoring"
] |
output (Port Mirroring) | output {
interface interface-name {
next-hop address;
}
no-filter-check;
}
Syntax: QFX10000 Switches
output {
dscp dscp-value;
forwarding-class class-name;
ip-destination-address address;
ip-source-address address;
policer policer-name;
} | [edit forwarding-options port-mirroring family (inet | inet6)],
[edit forwarding-options port-mirroring instance instance-name] | Configure output interfaces and flow properties.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Port Mirroring on M, T MX, ACX, and PTX Series Routers"
] |
output (Port Mirroring) | output {
file file-name {
linear;
max-size value;
}
interface interface-name {
next-hop address;
}
next-hop-group group-name{
group-type inet6;
interface interface-name {
next-hop ipv6-address;
}
next-hop-subgroup group-na... | [edit forwarding-options port-mirroring family (any | ccc | inet | inet6 | mpls | vpls)],
[edit forwarding-options port-mirroring instance instance-name family (any | ccc | inet | inet6 |
mpls | vpls)] | Configure the port-mirroring destination properties. | [
{
"name": "file file-name",
"desc": "PCAP file to save self-mirrored packets to."
},
{
"name": "linear",
"desc": "Write mode of the mirrored-packet file. (The default write mode is circular.)"
},
{
"name": "max-size value",
"desc": "Maximum size of the mirrored-packet file. Up to 5MB... | 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.
vpls option introduced in Junos OS Release 9.3 for MX Series routers only; support extended to M7i,
M10i, M120, and M320 routers in Junos OS Release 9.5.
ccc option introduced in Junos OS Release 9.6 for M120 and M320 routers only.
server-profile option introduced in Ju... | [
"Configuring Port Mirroring",
"Configuring Active Flow Monitoring on PTX Series Packet Transport Routers"
] |
output (Sampling) | output {
aggregate-export-interval seconds;
flow-active-timeout seconds;
flow-inactive-timeout seconds;
flow-server hostname {
aggregation {
autonomous-system;
destination-prefix;
protocol-port;
source-destination-prefix {
caida-com... | [edit forwarding-options sampling instance instance-name family (inet |inet6 |mpls)],
[edit forwarding-options sampling family (inet |inet6 |mpls | vpls)] | Configure cflowd or flow monitoring, output files and interfaces, and flow properties.
The remaining statements are explained separately. See CLI Explorer.
NOTE: The inline-jflow statement is valid only under the [edit forwarding-options sampling
instance instance-name family family output] hierarchy level. The file st... | [] | 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 IPv6 addresses for the flow-server address and source-address address statements within
sampling instances introduced in Junos OS Evolved Release 23.1R1. | [
"Configuring Traffic Sampling on MX, M and T Series Routers",
"Collecting Traffic Sampling Output in a File"
] |
output (Security Forwarding Options) | output {
destination-mac mac-address;
interface interface-name;
} | [edit security forwarding-options mirror-filter filter-name] | Specify the MAC address or interface for mirrored traffic.
Starting in Junos OS Release 18.4R1, if the output X2 interface of a mirror filter is configured for an st0
interface to filter traffic that you want to analyze, the packet is duplicated and encrypted by the IPsec
tunnel bound to the st0 interface. This enhance... | [
{
"name": "destination-mac mac-address",
"desc": "Specify the MAC address for the mirrored traffic."
},
{
"name": "interface interface-name",
"desc": "Specify the logical interface for the mirrored traffic."
}
] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [] |
output (Service Set) | output {
[ service-set service-set-name <service-filter filter-name> ];
} | [edit interface interface-name unit logical-unit-number family inet service],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet service] | Define the output service sets and filters to be applied to traffic. | [] | 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. | [
"Applying Filters and Services to Interfaces"
] |
output interfaces (Chassis Synchronization) | output {
interfaces {
external {
holdover-mode-disable;
minimum-quality (prc | prs | sec | smc | ssu-a | ssu-b | st2 | st3 | st3e | st4 |
stu | tnc);
source-mode (chassis | line);
tx-dnu-to-line-source-enable;
wander-filter-disable;
... | [edit chassis synchronization] | Configure the options for clock output interfaces. | [
{
"name": "external",
"desc": "(SCBE only) Specify the properties of the external output interface."
},
{
"name": "(external-0/0 | external-1/0)",
"desc": "(SCBE2 only) Specify the properties of the external output interface."
},
{
"name": "holdover-mode-disable",
"desc": "Disable ho... | 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. | [] |
output | output {
interface interface-name;
ip-address ip-address;
vlan (vlan-id | vlan-name);
routing-instance instance-name {
ip-address address;
}
} | For platforms without ELS:
[edit ethernet-switching-options analyzer name]
For platforms with ELS:
[edit forwarding-options analyzer name],
[edit forwarding-options port-mirroring instance name family ethernet-switching] | Configure the destination for mirrored traffic, either an interface on the switch (for local monitoring) or a
VLAN (for remote monitoring).
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
Option output vlan added in Junos OS Release 12.1 for the QFX Series. | [] |
output-chain | output-chain [ filter-name ] | [edit interfaces interface-name unit logical-unit-number family family filter] | The output-chain command works like the next filter term to allow multiple levels of filtering on the
interface in both the ingress and egress direction. For example, you can implement a combination of
classification and firewall filter rules for evaluation, wherein the first filter performs a generic filter
classifica... | [
{
"name": "[ filter-names ]",
"desc": "Name of each filter in the chain that is to be evaluated when packets are received on"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R1.
Statement introduced in Junos OS Evolved Release 21.4R1 (PTX10001-36MR, PTX10004, PTX10008,
and PTX10016). | [
"Example: Using Firewall Filter Chains",
"Understanding Multiple Firewall Filters Applied as a List",
"Applying a Filter to an Interface"
] |
output-filename (Event Policy) | output-filename filename; | [edit event-options policy policy-name then event-script filename],
[edit event-options policy policy-name then execute-commands] | Instruct an event policy to write the output of the invoked commands or event script to a file. For op
scripts, this statement is optional.
The output-filename argument is a descriptive string that is included in the filename of the output file. The
name of the output file also includes the hostname and timestamp to en... | [
{
"name": "filename",
"desc": "String included in the filename of the output file."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5.
Support at the [edit event-options policy policy-name then event-script filename] hierarchy level introduced in
Junos OS Release 7.6. | [
"Configure an Event Policy to Execute Operational Mode Commands",
"Execute Event Scripts in an Event Policy"
] |
output-format (Event Policy) | output-format (text | xml); | [edit event-options policy policy-name then event-script filename],
[edit event-options policy policy-name then execute-commands] | Specify the format (ASCII text or XML) for the output of event scripts or commands executed by an
event policy.
NOTE: Event script output is always emitted in XML format even if you configure the
output-format text statement under the [edit event-options policy policy-name then event-
script filename] hierarchy.
Defaul... | [
{
"name": "text",
"desc": "Formatted ASCII text."
},
{
"name": "xml",
"desc": "Junos Extensible Markup Language (XML) tags."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5.
Support at the [edit event-options policy policy-name then event-script filename] hierarchy level introduced in
Junos OS Release 8.3. | [
"Configure an Event Policy to Execute Operational Mode Commands",
"Execute Event Scripts in an Event Policy"
] |
output-forwarding-class-map | output-forwarding-class-map forwarding-class-map-name; | [edit class-of-service forwarding-classes-interface-specific] | Apply a configured forwarding class map to a logical interface. | [
{
"name": "forwarding-class-map-name",
"desc": "Name of a forwarding class mapping configured at the [edit class-of-service forwarding-classes-interface-specific] hierarchy level."
}
] | interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [] |
output-interface (CCC) | output-interface [interface-name 1 interface-name n]; | [edit protocols connections p2mp-transmit-switch p2mp-transmit-switch-name] | Specify one or more output interfaces to switch traffic on an incoming CCC interface to one or more
outgoing CCC interfaces. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring CCC Switching for Point-to-Multipoint LSPs"
] |
output-interface-index | output-interface-index number; | [edit forwarding-options monitoring name output interface interface-name] | Specify a value for the output interface index that overrides the default supplied by SNMP. | [
{
"name": "number",
"desc": "Output interface index value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Flow Monitoring"
] |
output-policer | output-policer policer-name; | [edit interfaces interface-name unit logical-unit-number layer2-policer],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
layer2-policer] | Apply a single-rate two-color policer to the Layer 2 output traffic at the logical interface. The output-
policer and output-three-color statements are mutually exclusive. | [
{
"name": "policer-name",
"desc": "Name of the single-rate two-color policer that you define at the [edit firewall] hierarchy"
}
] | 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. | [
"Two-Color and Three-Color Policers at Layer 2",
"Applying Layer 2 Policers to Gigabit Ethernet Interfaces",
"Configuring Gigabit Ethernet Policers"
] |
output-priority-map | output-priority-map {
classifier {
premium {
forwarding-class class-name {
loss-priority (high | low);
}
}
}
} | [edit interfaces interface-name gigether-options ethernet-switch-profile ethernet-policer-profile]
[edit interfaces interface-name ether-options ethernet-switch-profile ethernet-policer-profile] | For Gigabit Ethernet IQ and 10-Gigabit Ethernet interfaces only, define the output policer priority map
to be applied to outgoing frames on this interface.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Gigabit Ethernet Policers"
] |
output-queue-priority | [edit logical-systems logical-system-name protocols bgp family family-name sub-family],
[edit logical-systems logical-system-name protocols bgp group group-name family family-name sub-
family],
[edit protocols bgp family family-name sub-family],
[edit protocols bgp group group-name neighbor neighbor-id family family-na... | When configuring the queues for BGP route prioritization, the output-queue-priority statement allows you
to specify the number of tokens that are available within each of the 17 BGP output priority queues.
This allows you to balance the amount of work that can be done within the route prioritization queues.
When implem... | [] | 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. | [
"Understanding BGP Route Prioritization"
] | |
output-three-color | output-three-color policer-name; | [edit interfaces interface-name unit logical-unit-number layer2-policer]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
layer2-policer] | Apply a single-rate or two-rate three-color policer to the Layer 2 output traffic at the logical interface.
The output-three-color and output-policer statements are mutually exclusive. | [
{
"name": "policer-name",
"desc": "Name of the single-rate or two-rate three-color policer."
}
] | 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. | [
"Two-Color and Three-Color Policers at Layer 2",
"Applying Layer 2 Policers to Gigabit Ethernet Interfaces",
"Configuring Gigabit Ethernet Policers"
] |
output-traffic-control-profile (Dynamic CoS Definition) | output-traffic-control-profile (profile-name | $junos-cos-traffic-control-profile); | [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-
number] | Apply an output traffic scheduling and shaping profile to the logical interface. | [
{
"name": "profile-name",
"desc": "Name of the traffic-control profile to be applied to this interface"
},
{
"name": "$junos-cos-traffic-control-profile",
"desc": "Variable for the traffic-control profile that is specified for the logical"
}
] | 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.
Variable $junos-cos-traffic-control-profile introduced in Junos OS Release 11.2. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Applying Traffic Shaping and Scheduling to a Subscriber Interface in a Dynamic Profile",
"Using the CLI to Modify Traffic-Control Profiles That Are Currently Applied to Subscribers"
] |
output-traffic-control-profile | output-traffic-control-profile profile-name;
output-traffic-control-profile profile-name shared-instance instance-name; | [edit class-of-service interfaces interface-name ],
[edit class-of-service interfaces interface-name unit logical-unit-number],
[edit class-of-service interfaces interface-name interface-set interface-set-name]
[edit class-of-service interfaces interface-name slice slice-name]
[edit class-of-service interfaces interfac... | Apply the specified CoS traffic control profile (traffic scheduling and shaping configuration objects) to
the output traffic at the physical interface, logical interface, interface set, slice, or forwarding class set
(priority group). | [
{
"name": "profile-name",
"desc": "Name of the traffic-control profile to be applied to this interface."
},
{
"name": "shared-instance instance-name",
"desc": "For platforms that support this option, name of the shared scheduler and"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6.
interface-set option added in Junos OS Release 8.5. | [
"Oversubscribing Interface Bandwidth",
"Configuring Traffic Control Profiles for Shared Scheduling and Shaping",
"Configuring Hierarchical Schedulers for CoS",
"Configuring Interface Sets",
"Example: Configuring CoS Hierarchical Port Scheduling (ETS)",
"Example: Configuring Traffic Control Profiles (Prior... |
output-traffic-control-profile-remaining | output-traffic-control-profile-remaining profile-name; | [edit class-of-service interfaces interface-name],
[edit class-of-service interfaces interface-name interface-set interface-set-name] | Apply the specified traffic control profile (traffic scheduling and shaping configuration objects) to the
remaining output traffic at the physical interface or interface set. The remaining traffic is transmitted by
the default interface or interface set.
You can map the TCP to the interface or interface set by using th... | [
{
"name": "profile-name",
"desc": "Name of the traffic-control profile for remaining traffic to be applied to this interface or"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring Hierarchical Schedulers for CoS",
"Configuring Remaining Common Queues on MIC and MPC Interfaces"
] |
output-vlan-map (Aggregated Ethernet) | output-vlan-map {
(pop | push | swap);
tag-protocol-id tpid;
vlan-id number;
} | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Define the rewrite profile to be applied to outgoing frames on this logical interface. On MX Series
routers, this statement only applies to aggregated Ethernet inferfaces using Gigabit Ethernet IQ, 10-
Gigabit Ethernet IQ2 and IQ2-E interfaces and 100-Gigabit Ethernet Type 5 PIC with CFP..
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 8.2.
Starting in Junos OS Release 17.3R1, input-vlan-map for outer vlan is supported for L2 circuit over
aggregated Ethernet interfaces for QFX10000 Series switches. | [
"Stacking and Rewriting Gigabit Ethernet VLAN Tags"
] |
output-vlan-map (Dynamic Interfaces) | output-vlan-map {
inner-tag-protocol-id tpid;
inner-vlan-id number;
(pop | swap);
tag-protocol-id tpid;
vlan-id number;
} | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number] | For dynamic interfaces, define the rewrite profile to be applied to outgoing frames on this logical
interface.
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 to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Stacking and Rewriting VLAN Tags for the Layer 2 Wholesale Solution"
] |
output-vlan-map | output-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
} | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | For EX Series switches, defines the rewrite operation to be applied to outgoing frames.
For MX Series routers and NFX Series devices’ Gigabit Ethernet IQ and 10-Port 10-Gigabit Ethernet
SFPP interfaces only, defines the rewrite operation to be applied to outgoing frames on this logical
interface.
The remaining statemen... | [] | 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.
pop-pop, pop-swap, push-push, swap-push, and swap-swap statements added in Junos OS Release 8.1. | [
"Stacking and Rewriting Gigabit Ethernet VLAN Tags"
] |
outputs (Analytics) | outputs {
file {
parameters {
path file-path;
}
}
kafka {
parameters {
server ip-address;
topic topic-name;
encoding encoding-type;
}
}
output-ipfix {
parameters {
collector-address ip-address;
... | [edit services analytics agent service-agents agent-name] | Configure parameters for the Network Telemetry Framework (NTF) agent output plug-in.
NOTE: When you modify the output plug-in configuration of a service agent instance,
the associated service agent daemon is restarted. | [
{
"name": "file parameters",
"desc": "Configure parameters for sending data in a log file to a data collector."
},
{
"name": "path pathname",
"desc": "Path for the log file to which to save the data. For example, path /tmp/"
},
{
"name": "example_file.log",
"desc": ""
},
{
"n... | system | Statement introduced in Junos OS Release 18.3R1.
kafka and file options added in Junos OS Release 18.4R1 on MX Series and PTX Series routers. | [
"Configuring the BNG as an IPFIX Mediator to Collect and Export IPFIX Data",
"Configuring the Collection and Export of Local Telemetry Data on the IPFIX Mediator",
"Configuring NTF Agent",
"IPFIX Mediation on the BNG",
"Telemetry Data Collection on the IPFIX Mediator for Export to an IPFIX Collector"
] |
over (Application Identification) | over protocol-type {
chain-order;
signature name {
member name {
context {
context;
}
direction {
any;
client-to-server;
server-to-client;
}
pattern pattern;
depth b... | [edit services application-identification application application-name] | Specify set of L4/L7 application that carries given application
Configure a custom signature based on Layer 4/Layer 7 applications. You create Layer 7-based custom
application signatures for the identification of multiple applications running on the same Layer 7
protocols. For example, applications such as Facebook and... | [
{
"name": "protocol-type",
"desc": "Application protocol"
},
{
"name": "\"chain-order\" on",
"desc": ""
},
{
"name": "page 3485",
"desc": "The order of members is used to match the pattern (Next Gen Services)"
},
{
"name": "signature name",
"desc": "Name of the custom app... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D40.
Support for Next Gen Services introduced in Junos OS Releases 19.3R2 and 19.4R1 on MX Series
MX240, MX480 and MX960 using the MX-SPC3 services card. | [
"Understanding Junos OS Application Identification Custom Application Signatures"
] |
over-limit | over-limit (block | log-and-permit); | [edit security utm default-configuration]
[edit security utm utm-policy policy-name traffic-options sessions-per-client] | In an attempt to consume all available resources and hinder the ability of the device, a malicious user
might generate a large amount of traffic all at once. To prevent such activity from succeeding, you can
impose a session throttle to limit sessions and configure an action to occur when the limit is exceeded. | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
}
] | 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.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
overall-packet (Flat-File Accounting Options) | overall-packet {
all-fields;
input-bytes;
input-discards;
input-errors;
input-packets;
inputv6-bytes;
inputv6-packets;
output-bytes;
output-errors;
output-packets;
outputv6-bytes;
outputv6-packets;
input-v4-bytes;
input-v4-packets;
output-v4-bytes;
output-... | [edit accounting-options flat-file-profile profile-name fields] | Specify overall packet statistics to be collected for the interface. | [
{
"name": "all-fields",
"desc": "Collect all overall packet statistics available for the interface context, logical or physical."
},
{
"name": "input-bytes",
"desc": "Collect the number of octets received on the interface."
},
{
"name": "input-discards",
"desc": "(Physical 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.1R4. | [
"Configuring Flat-File Accounting for Layer 2 Wholesale",
"Configuring Flat-File Accounting for Extensible Subscriber Services Management",
"Flat-File Accounting Overview"
] |
overflow-pool | overflow-pool (interface | pool-name); | [edit security nat source pool pool-name] | Specify a source pool to use when the current address pool is exhausted. Currently the statement is
applicable for IPv4 addresses only.
NOTE: The length of the IPv6 prefix must be 96 when the pool is used for NAT-PT. | [
{
"name": "interface",
"desc": "Allow the interface pool to support overflow."
},
{
"name": "pool-name",
"desc": "Name of the source address pool."
}
] | security — To view this statement in the configuration.
security-control — To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. | [] |
overhead-accounting (ANCP) | overhead-accounting; | [edit protocols ancp interfaces interface-name] | Prevent ANCP from performing an adjustment on the actual downstream data rate that ANCP receives
from the DSLAM for the difference between the customer premise equipment (CPE) protocol overhead
and the B-RAS protocol overhead. You include this statement when you want CoS to perform the
adjustment on the data rate from ... | [] | 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. | [
"Configuring the ANCP Agent"
] |
overhead-accounting (Dynamic Traffic Shaping) | overhead-accounting {
bytes bytes;
cell-mode cell-mode-bytes cell-mode-bytes;
frame-mode frame-mode-bytes frame-mode-bytes;
} | [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | Configure the mode to shape downstream ATM traffic based on either frames or cells.
Default
The default is frame-mode. | [] | 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. | [
"CoS Adjustment Control Profiles Overview",
"Configuring Dynamic Shaping Parameters to Account for Overhead in Downstream Traffic Rates",
"Bandwidth Management for Downstream Traffic in Edge Networks Overview",
"egress-shaping-overhead"
] |
overhead-accounting | overhead-accounting {
bytes bytes;
cell-mode cell-mode-bytes cell-mode-bytes;
frame-mode frame-mode-bytes frame-mode-bytes;
} | [edit class-of-service traffic-control-profiles profile-name] | Configure the mode to shape downstream traffic.
Default | [
{
"name": "bytes",
"desc": "Shaping overhead adjustment value, in bytes. This options allows you to add/subtract the number of overhead bytes to/from the packet to determine the shaped session packet 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.2.
bytes option introduced in Junos OS Evolved Release 23.1R1. | [
"Configuring Static Shaping Parameters to Account for Overhead in Downstream Traffic Rates",
"Configuring Dynamic Shaping Parameters to Account for Overhead in Downstream Traffic Rates"
] |
overlay (Packet Forwarding Options) | overlay {
interface-num interface-num;
next-hop next-hop;
} | [edit system packet-forwarding-options] | Configure overlay interface and next-hop size. Configuration will be followed by a PFE restart for the
configuration to take effect. | [
{
"name": "interface-num",
"desc": "Number of L3 Interfaces. Must be multiple of 1024. This will restart PFE. Range: 1024 through 7168 Default is 4096"
},
{
"name": "next-hop",
"desc": "Number of L3 Next-hops. Must be multiple of 4096. This will restart PFE. Range: 4096 through 28762 Default i... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 24.4R1 | [] |
overlay-ecmp | overlay-ecmp; | [edit forwarding-options vxlan-routing] | Enable two-level equal-cost multipath next hops.
On QFX5110, QFX5120, EX4650, EX4400, and EX4100 switches, you must configure this statement
for Ethernet VPN Virtual Extensible LAN (EVPN-VXLAN) overlay networks when overlay routing is
configured (e.g. Overlay routing using pure Type 5 or IRB). For more information abou... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1. | [] |
overlay-path | overlay-path overlay-path-name {
probe-path {
local ip-address;
remote ip-address
}
tunnel-path {
local ip-address;
remote ip-address
}
} | [edit security advance-policy-based-routing] | Configure overlay path to specify the destinations to which the active probe data needs to be sent.
Overlay paths are configured for all overlay endpoints. Overlay path configuration includes two set of IP
addresses—tunnel IP addresses and probe IP addresses.
You need to create the overlay setup between local and remot... | [
{
"name": "overlay-path-name",
"desc": "Overlay path name."
},
{
"name": "probe-path",
"desc": "Probe IP addresses are used as probes’ start and end addresses to send over the corresponding tunnel paths. Probe IP addresses must be unique across individual overlay paths."
},
{
"name": "lo... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Application Quality of Experience",
"Advanced Policy-Based Routing",
"overload (Protocols IS-IS)"
] |
overload (Protocols OSPF) | overload {
timeout seconds;
} | [edit logical-systems logical-system-name protocols (ospf | ospf3)],
[edit logical-systems logical-system-name protocols ospf topology (default | ipv4-multicast |
name)],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast)],
[edit logical-systems logical-sy... | Configure the local routing device so that it appears to be overloaded. You might do this when you want
the routing device to participate in OSPF routing, but do not want it to be used for transit traffic.
NOTE: Traffic destined to directly attached interfaces continues to reach the routing
device. | [
{
"name": "timeout seconds",
"desc": "(Optional) Number of seconds at which the overloading is reset. If no timeout interval is"
}
] | 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.
Support for Multitopology Routing introduced in Junos OS Release 9.0.
Support for Multitopology Routing introduced in Junos OS Release 9.0 for EX Series switches.
Support for the realm statement introduced in Junos OS Release 9.2.
Support for the realm statement introd... | [
"Example: Configuring OSPF to Make Routing Devices Appear Overloaded",
"Example: Configuring Multitopology Routing for Class-Based Forwarding of Voice, Video, and Data",
"Traffic",
"Example: Configuring Multitopology Routing to Provide Redundancy for Multicast Traffic over",
"Separate Network Paths"
] |
overload-pool | overload-pool overload-pool-name; | [edit services nat rule rule-name term term-name then translated] | Specify an address pool that can be used if the source pool becomes exhausted. | [
{
"name": "overload-pool-name",
"desc": "Name of the overload pool."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Network Address Translation Rules Overview"
] |
overload-prefix | overload-prefix overload-prefix; | [edit services nat rule rule-name term term-name then translated] | Specify the prefix that can be used if the source pool becomes exhausted. | [
{
"name": "overload-prefix",
"desc": "Prefix value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Network Address Translation Rules Overview"
] |
override (PIM Static RP) | override; | [edit logical-systems logical-system-name protocols pim rp local],
[edit logical-systems logical-system-name protocols pim rp local family inet],
[edit logical-systems logical-system-name protocols pim rp local family inet6],
[edit logical-systems logical-system-name protocols pim rp static address address],
[edit logi... | When you configure both static RP mapping and dynamic RP mapping (such as auto-RP) in a single
routing instance, allow the static mapping to take precedence for a given group range, and allow
dynamic RP mapping for all other groups.
Default | [] | 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. | [
"Configuring Static RP",
"Configuring PIM Auto-RP"
] |
override (RADIUS Options) | override {
calling-station-id remote-circuit-id;
nas-ip-address tunnel-client-gateway-address;
nas-port tunnel-client-nas-port;
nas-port-type tunnel-client-nas-port-type;
} | [edit access profile profile-name radius options] | Override the values for certain RADIUS options. | [
{
"name": "calling-station-id remote-",
"desc": ""
},
{
"name": "circuit-id",
"desc": "Override the Calling-Station-ID format for the string that the LAC sends to the LNS in the Calling Number AVP 22. AVP 22 is included in the incoming-call request (ICRQ) packet when the L2TP session is being es... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3R1.
nas-ip-address tunnel-client-gateway-address and nas-port tunnel-client-nas-port options added in Junos OS
Release 17.3R1 on MX Series.
calling-station-id remote-circuit-id option added in Junos OS Release 13.3R1 on MX Series. | [
"L2TP Subscriber Access Lines and Connection Speeds",
"RADIUS Servers and Parameters for Subscriber Access"
] |
override | override tag vlan-tag dynamic-profile profile name; | [edit interfaces interface-name auto-configure vlan-ranges],
[edit interfaces interface-name auto-configure stacked-vlan-ranges] | Override dynamic profile assignment to individual VLANs that are already part of a previously defined
VLAN range and dynamic profile. | [
{
"name": "vlan-tag",
"desc": "VLAN tag that you want to override."
},
{
"name": "profile-name",
"desc": "Name of the dynamic profile that you want to use when overriding the specified VLAN tag."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Overriding the Dynamic Profile Used for an Individual VLAN",
"Configuring an Interface to Use the Dynamic Profile Configured to Create Stacked VLANs",
"Configuring an Interface to Use the Dynamic Profile Configured to Create Single-Tag VLANs"
] |
override-chap-password | override-chap-password password; | [edit access domain map domain-map-name] | Configure a CHAP password to override the existing password for authenticating any subscriber
associated with the domain map. The override CHAP password replaces the CHAP challenge response
that the PPP client sends to the server for authentication.
The CHAP challenge response is normally sent in the RADIUS Access-Requ... | [] | access—To view this statement in the configuration.
access-control—To add this statement in the configuration. | Statement introduced in Junos OS Release 21.3R1. | [
"Changing the Username and Password to Simplify Off-Chassis Provisioning"
] |
override-firewall | override-firewall; | [edit class-of-service host-outbound-traffic],
[edit dynamic-profiles name class-of-service host-outbound-traffic] | Junos OS release 16.1 and earlier support forwarding-class and dscp-code-point firewall filters. These
settings would take precedence over the same configuration if set at the class-of-service host-outbound-
traffic level of the hierarchy, as applied to Routing Engine output traffic.
Starting with Junos OS release 16.1... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1 | [] |
override-interval | override-interval milliseconds; | [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name protocols pim interface (Protocols PIM) interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
interface (Protocols PIM) interface-name],
[edit protocols pim],
... | Set the maximum time in milliseconds to delay sending override join messages for a multicast network
that has join suppression enabled. When a router or switch sees a prune message for a join it is currently
suppressing, it waits for the interval specified by the override timer before it sends an override join
message. | [] | 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. | [
"Example: Enabling Join Suppression"
] |
override-password (Domain Map) | override-password password | [edit access domain map domain-map-name] | Specify a password to be used as the authenticating password for all outgoing authentication requests
for subscribers who match the domain map.
NOTE: This override works only when PAP is the authentication method. It does not
work for CHAP. | [
{
"name": "password",
"desc": "Name of the password."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Changing the Username and Password to Simplify Off-Chassis Provisioning"
] |
overrides (DHCP Local Server) | overrides{
always-process-option-request-option;
asymmetric-lease-time seconds;
asymmetric-prefix-lease-time seconds;
client-discover-match <option60-and-option82 | incoming-interface>;
client-negotiation-match incoming-interface;
delay-advertise {
based-on (option-15 | option-16 | optio... | [edit system services dhcp-local-server],
[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 interface-name],
[edit system services dhcp-local-server group group-name],
[edit system ... | Override the default configuration settings for the extended DHCP local server. Specifying the overrides
statement with no subordinate statements removes all DHCP local server overrides at that hierarchy
level.
•
To override global DHCP local server configuration options, include the overrides statement and its
subordi... | [] | 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.
Support for the allow-no-end option introduced in Junos OS Release 14.1X53-D15 for EX Series switches. | [
"Understanding Differences Between Legacy DHCP and Extended DHCP",
"Overriding the Default DHCP Local Server Configuration Settings",
"Configuring a DHCP Server on Switches"
] |
overrides (DHCP Relay Agent) | overrides {
allow-no-end-option;
allow-snooped-clients;
always-write-giaddr;
always-write-option-82;
asymmetric-lease-time seconds;
asymmetric-prefix-lease-time seconds;
bootp-support;
based-on {
(option-60 {..} | option-77 {..} | option-82 {..})
client-discover-match <option60... | [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 group group-name],
[edit forwarding-options dhcp-rel... | Override the default configuration settings for the extended DHCP relay agent. Specifying the overrides
statement with no subordinate statements removes all DHCP relay agent overrides at that hierarchy
level. Use the statement at the [edit ... dhcpv6] hierarchy levels to configure DHCPv6 support.
M120 and M320 routers ... | [] | 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.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4. | [
"Extended DHCP Relay Agent Overview",
"Overriding the Default DHCP Relay Configuration Settings"
] |
overrides (DHCP Security for MX Series) | overrides (trusted | untrusted | no-option82); | [edit bridge-domains bridge-domain-names forwarding-options dhcp-security group group-name] | Modify selected attributes of a specific interface within a group of interfaces configured within a
specified bridge domain. | [
{
"name": "no-option 82",
"desc": "The interface specified in this group does not support DHCP option 82."
},
{
"name": "trusted",
"desc": "The interface specified in this group is trusted. DHCP snooping does not apply to the"
},
{
"name": "trusted interface. Likewise, DAI and IP source ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Configuring DHCP Option 82 on a Router with Bridge Domain",
"Understanding DHCP Option 82"
] |
overrides (DHCP Security) | overrides {
no-dhcpv6-options;
no-option16;
no-option18;
no-option37;
no-option82;
trusted;
untrusted;
} | [edit vlans vlan-name forwarding-options dhcp-security group group-name] | Modify selected DHCP attributes for a group of interfaces that is configured within a specified VLAN. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10.
Support for the no-option37 option introduced in Junos OS Release 13.2X51-D20 for EX Series switches.
Support for the no-dhcpv6-options, no-option16 and no-option18 options introduced in Junos OS Release 14.2
for EX Series switches. | [
"Enabling a Trusted DHCP Server (ELS)",
"Understanding DHCP Snooping (non-ELS)",
"Understanding DHCP Option 82"
] |
overrides (Enhanced Subscriber Management) | overrides {
event {
catastrophic-failure {
reboot (master | standby);
}
}
force-show-arp-resolve;
interfaces {
family (inet | inet6) {
layer2-liveness-detection;
ipoe-dynamic-arp-enable;
receive-gratuitous-arp;
}
}
... | [edit system services subscriber-management] | Override the default configuration settings for the Junos OS enhanced subscriber management software
for subscriber management. | [
{
"name": "force-show-arp-resolve",
"desc": "Force the output of the show arp command to display the IP address by the hostname of each device."
},
{
"name": "ra-initial-interval-max",
"desc": ""
},
{
"name": "seconds",
"desc": "Specify the high end of the range from which the router... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1R3.
ra-initial-interval-max and ra-initial-interval-min options added in Junos OS Release 18.2R1.
ipoe-dynamic-arp-enable and receive-gratuitous-arp options added in Junos OS Release 18.4R1.
force-show-arp-resolve option added in Junos OS Release 23.1R1. | [
"Configuring Junos OS Enhanced Subscriber Management",
"Junos OS Enhanced Subscriber Management Overview",
"DHCP Liveness Detection Using ARP and Neighbor Discovery Packets",
"Configuring an Interval Range for Unsolicited Router Advertisements to IPv6 Neighbors"
] |
overrides (System Services DHCP) | overrides
{
interface-client-limit number;
always-add-option-dns-server;
always-process-option-request-option;
asymmetric-lease-time seconds;
asymmetric-prefix-lease-time seconds;
client-negotiation-matchincoming-interface;
delay-advertise {
based-on {
option-15 {
... | [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 interface-name] | Override the default configuration settings for the extended DHCP local server. Specifying the overrides
statement with no subordinate statements removes all DHCP local server overrides at that hierarchy
level.
•
To override global DHCP local server configuration options, include the overrides statement and its
subordi... | [
{
"name": "interface-client-limit number",
"desc": "Sets the maximum number of DHCP clients per interface allowed for a"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Additional Configurations for DHCP Clients"
] |
oversize-message-drop | oversize-message-drop; | [edit logical-systems name security alg dns],
[edit logical-systems name tenants name security alg dns],
[edit security alg dns],
[edit services alg dns],
[edit tenants name security alg dns] | Enable or disable oversize message drop.
When you enable the oversize-message-drop command, Domain Name System (DNS) packets that exceed
the threshold (range from 512 through 8192) are dropped.
When you disable the oversize-message-drop command, DNS Application Layer Gateway (ALG) will only
record and forward the overs... | [
{
"name": "oversize-message-drop",
"desc": "Drop the oversized DNS packets for which the packet length exceed the threshold"
}
] | 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-D55. | [] |
ovlan-cfi (RFC 2544 Benchmarking) | ovlan-cfi; | [edit services rpm rfc2544-benchmarkingtests test-name test-name] | CFI bit to be used in the outer VLAN tag. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X53. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
ovlan-id (RFC 2544 Benchmarking) | ovlan-id number; | [edit services rpm rfc2544-benchmarkingtests test-name test-name] | Configure the outer VLAN ID for the test frames. This parameter is applicable for single-tagged and
dual-tagged packets. | [
{
"name": "number",
"desc": "VLAN ID number. Range: 0 through 4094"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X53. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
ovlan-priority (RFC 2544 Benchmarking) | ovlan-priority value; | [edit services rpm rfc2544-benchmarking tests test-name test-name] | Configure the priority value for the IEEE 802.1p bit in the outer VLAN tag. This parameter is valid only
for a bridge family for an Ethernet LAN (ELAN) or an Ethernet Line (E-LINE) service. | [
{
"name": "value",
"desc": "IEEE 802.1p priority value in the outer VLAN tag Range: 0 through 7"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X53. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
ovsdb | ovsdb {
controller ip-address {
inactivity-probe-duration milliseconds;
maximum-backoff-duration milliseconds;
protocol protocol {
port number;
}
}
interfaces interface-name;
traceoptions {
file <filename> <files number> <match regular-expressio... | [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 14.1R2. | [
"Understanding the OVSDB Protocol Running on Juniper Networks Devices"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.