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 |
|---|---|---|---|---|---|---|---|
authentication-server | authentication-server [server-addresses]; | [edit access profile profile-name radius] | Configure the RADIUS server for authentication. To configure multiple RADIUS servers, include multiple
server addresses. The servers are tried in order and in a round-robin fashion until a valid response is
received from one of the servers or until all the configured retry limits are reached. | [
{
"name": "server-addresses",
"desc": "Configure one or more RADIUS server addresses."
}
] | 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.
Statement introduced in Junos OS Release 14.1X53-D20 for OCX Series switches. | [
"Example: Connecting a RADIUS Server for 802.1X to an EX Series Switch",
"show network-access aaa statistics authentication"
] |
authentication-sha224 | authentication-sha224 {
authentication-key authentication-key;
authentication-password authentication-password;
} | [edit snmp v3 usm local-engine user username],
[edit snmp v3 usm remote-engine engine-id user username] | Configure the secure hash algorithm (SHA)224 as the authentication type for the SNMPv3 user. You can
use this configuration statement for local and remote user. | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1.
Statement introduced in Junos OS Evolved Release 22.4R1. | [
"Configuring SHA Authentication"
] |
authentication-sha256 | authentication-sha256 {
authentication-key authentication-key;
authentication-password authentication-password;
} | [edit snmp v3 usm local-engine user username],
[edit snmp v3 usm remote-engine engine-id user username] | Configure the secure hash algorithm (SHA)256 as the authentication type for the SNMPv3 user. You can
use this configuration statement for local and remote user. | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1.
Statement introduced in Junos OS Evolved Release 22.4R1. | [
"Configuring SHA Authentication"
] |
authentication-sha348 | authentication-sha348 {
authentication-key authentication-key;
authentication-password authentication-password;
} | [edit snmp v3 usm local-engine user username],
[edit snmp v3 usm remote-engine engine-id user username] | Configure the secure hash algorithm (SHA)348 as the authentication type for the SNMPv3 user. You can
use this configuration statement for local and remote user. | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1. | [
"Configuring SHA Authentication"
] |
authentication-sha512 | authentication-sha512 {
authentication-key authentication-key;
authentication-password authentication-password;
} | [edit snmp v3 usm local-engine user username],
[edit snmp v3 usm remote-engine engine-id user username] | Configure the secure hash algorithm (SHA)512 as the authentication type for the SNMPv3 user. You can
use this configuration statement for local and remote user.
NOTE: The SRX4600 Series Firewall supports HMAC-SHA-512 only when Junos-ike package is
installed. | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1. | [
"Configuring SHA Authentication"
] |
authentication-sha | authentication-sha {
(authentication-key authentication-key | authentication-password authentication-password);
} | [edit snmp v3 usm local-engine user username],
[edit snmp v3 usm remote-engine engine-id user username] | Configure the secure hash algorithm (SHA) as the authentication type for the SNMPv3 user.
NOTE: You can configure only one authentication type for each SNMPv3 user.
For authentication, you can either enter a password in clear text, which is immediately encrypted, or, if
you already have the encrypted version (known as ... | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring SHA Authentication"
] |
authentication-source (Services User Identification ClearPass) | authentication-source aruba-clearpass {
authentication-entry-timeout (Services User Identification) minutes;
invalid-authentication-entry-timeoutminutes;
no-user-query (Services User Identification);
traceoptions (Services User Identification) {
file filename files files match match size size(w... | [edit services user-identification] | 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 rest... | [
{
"name": "name",
"desc": "Aruba ClearPass authentication source name."
},
{
"name": "authentication-entry-timeout",
"desc": "Aruba ClearPass authentication entry timeout number. Range: 10 through 1440 minutes"
},
{
"name": "invalid-authentication-entry-timeout",
"desc": "Invalid au... | 1. services—To view this statement in the configuration.
2. services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
authentication-source (Services User Identification Device Identity) | authentication-source (active-directory | network-access-controller) | [edit services user-identification device-information] | Specify the device identity authentication source. The integrated user firewall device identity
authentication feature enables you to control access to resources based on the identity of the device
and not that of the user of the device. Supported authentication sources include Active Directory and
third-party network ... | [
{
"name": "active-directory",
"desc": "Specifies Microsoft Active Directory as the authentication source. The SRX Series Firewall obtains the device identity information for authenticated devices from Active Directory. It reads the Active Directory domain controller event logs to obtain the IP addresses of ... | 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-D70. | [
"Device Identity",
"Active Directory as Identity Source",
"Authentication Table"
] |
authentication-type (Protocols RIP) | authentication-type type; | [edit logical-systems logical-system-name protocols rip],
[edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip],
[edit logical-systems logical-system-name routing-instances routin... | Configure the type of authentication for RIP route queries received on an interface.
Default
If you do not include this statement and the authentication-key statement, RIP authentication is disabled. | [
{
"name": "type",
"desc": "Authentication type:"
},
{
"name": "md5",
"desc": "Use the MD5 algorithm to create an encoded checksum of the packet. The encoded checksum is"
},
{
"name": "none",
"desc": "Disable authentication. If none is configured, the configured authentication key 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. | [
"Example: Configuring Route Authentication for RIP using single MD5 key"
] |
authentication-type | authentication-type (md5 | simple); | [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-
group group-id],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet address address vrrp-group group-id] | Enable Virtual Router Redundancy Protocol (VRRP) IPv4 authentication and specify the authentication
scheme for the VRRP group. If you enable authentication, you must specify a password by including the
authentication-key statement. The specific type of authentication used by OSPF is encoded in this field.
All devices i... | [
{
"name": "authentication",
"desc": "Authentication scheme:"
},
{
"name": "simple",
"desc": "Use a simple password. The password is included in the transmitted packet, so this method of authentication is relatively insecure."
},
{
"name": "md5",
"desc": "Use the MD5 algorithm to crea... | 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 VRRP Authentication (IPv4 Only)",
"version-3",
"Understanding VRRP on SRX Series Devices",
"Example: Configuring VRRP/VRRPv3 on Chassis Cluster Redundant Ethernet Interfaces"
] |
authentication-whitelist | authentication-whitelist {
mac-address {
bridge-domain-assignment bridge-domain-assignment;
interface interface-name;
vlan-assignment ( vlan-id |vlan-name);
} | [edit ethernet-switching-options],
[edit logical-systems name switch-options],
[edit switch-options] | Configure MAC addresses to exclude from RADIUS authentication. The authentication allowlist provides
an authentication bypass mechanism for supplicants connecting to a port, permitting devices, such as
printers, to be connected to the network without going through the authentication process. | [
{
"name": "mac-address",
"desc": "The MAC address of the device for which RADIUS authentication should be bypassed and the device permitted access to the port."
},
{
"name": "bridge-domain-assignment bridge-",
"desc": ""
},
{
"name": "domain-assignment",
"desc": "(MX Series only) Spe... | 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.
The [edit switch-options] hierarchy level was introduced in Junos OS Release 13.2X50-D10 for EX Series
switches (ELS). | [
"Example: Setting Up Captive Portal Authentication on an EX Series Switch",
"Example: Setting Up Captive Portal Authentication on an EX Series Switch with ELS Support",
"Configuring Captive Portal Authentication (CLI Procedure)",
"Configuring Captive Portal Authentication (CLI Procedure) on an EX Series Switc... |
authenticator | authenticator {
authentication-profile-name access-profile-name;
interface (all | [ interface-names ]) {
authentication-order (captive-portal | dot1x | mac-radius);
disable;
guest-bridge-domain guest-bridge-domain;
guest-vlan guest-vlan;
ignore-port-bounce;
mac-ra... | [edit logical-systems name protocols dot1x],
[edit protocols dot1x] | Specify the group of servers to be used for IEEE 802.1X or MAC RADIUS authentication for Port-Based
Network Access Control, configure interfaces for 802.1x authentication, and configure static MAC
bypass for 802.1x and MAC RADIUS authentication. 802.1X authentication is supported on interfaces
that are members of priva... | [
{
"name": "authentication-profile-name",
"desc": ""
},
{
"name": "access-profile-name",
"desc": "Specify the name of the access profile to be used for 802.1X or MAC RADIUS user authentication. The access profile is configured at the [edit access profile] hierarchy level and contains the RADIUS s... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
no-mac-table-binding introduced in Junos OS Release 11.1.
radius-options introduced in Junos OS Release 12.1.
add-interface-text-description introduced in Junos OS Release 18.4.
ip-mac-session-binding introduced in Junos OS Release 20.2R1. | [
"Example: Connecting a RADIUS Server for 802.1X to an EX Series Switch",
"Example: Configuring MAC RADIUS Authentication on an EX Series Switch",
"Configuring 802.1X Interface Settings (CLI Procedure)",
"Specifying RADIUS Server Connections on Switches (CLI Procedure)",
"Example: Configuring Static MAC Bypa... |
authorization (icap-redirect profile) | authorization {
authorization-type authorization-type;
credentials (ascii ascii | base64 base64);
} | [edit services icap-redirect profile name server name] | User authentication for the ICAP server if the request needs to be authorized. | [
{
"name": "authorization-type",
"desc": "Authentication type for the ICAP server. Authorization type is basic by default."
},
{
"name": "credentials",
"desc": "Credentials (user name and password) for authentication to ICAP server. Values:"
},
{
"name": "ascii ascii",
"desc": "ASCII... | system | Statement introduced in Junos OS Release 18.1R1. | [
"ICAP Service Redirect"
] |
authorization (SNMP) | authorization authorization; | [edit snmp community community-name] | Set the access authorization for SNMP Get, GetBulk, GetNext, and Set requests. | [
{
"name": "authorization",
"desc": "Access authorization level:"
},
{
"name": "read-only",
"desc": "Enable Get, GetNext, and GetBulk requests."
},
{
"name": "read-write",
"desc": "Enable all requests, including Set requests. You must configure a view to enable Set"
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring SNMP Communities"
] |
authorization-order | authorization-order [ authorization-methods ]; | [edit access profile profile-name] | Set the order in which AAA tries different methods to verify that a client is authorized access to the
router or switch. For each login attempt, AAA tries the authorization methods in order, from first to last.
A given subscriber does not undergo both authentication and authorization as separate steps. When
both authen... | [
{
"name": "authorization-methods",
"desc": "Ordered list of methods to use for authorization attempts. The list includes one or more of the following methods in any combination:"
},
{
"name": "jsrc",
"desc": "Use the JSRC application in an SRC environment to request authorization"
},
{
"... | 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.
nasreq option added in Junos OS Release 16.1. | [
"JSRC Configuration Overview",
"Authorizing Subscribers with JSRC"
] |
auto-bandwidth (MPLS Statistics) | auto-bandwidth; | [edit logical-systems logical-system-name protocols mpls statistics],
[edit protocols mpls statistics] | Collect statistics related to automatic bandwidth. | [] | routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Automatic Bandwidth Allocation for LSPs",
"Configuring MPLS to Gather Statistics"
] |
auto-bandwidth (MPLS Tunnel) | auto-bandwidth {
adjust-interval seconds;
adjust-threshold percent;
adjust-threshold-absolute;
adjust-threshold-activate-bandwidthbps
adjust-threshold-overflow-limit number;
adjust-threshold-underflow-limit number;
maximum-bandwidth bps;
minimum-bandwidth bps;
minimum-bandwidth-adjus... | [edit protocols mpls label-switched-path lsp-name] | Allow an MPLS tunnel to automatically adjust its bandwidth allocation based on the volume of traffic
flowing through the tunnel.
NOTE: In calculating the value for Max AvgBW (relative to the ingress LSP), the sample
collected during make before break (MBB) is ignored to prevent inaccurate results. The
first sample afte... | [
{
"name": "adjust-threshold-absolute adjust-",
"desc": ""
},
{
"name": "threshold-absolute-value",
"desc": "Configure an absolute value based threshold along with the percentage based threshold that helps avoid the bandwidth getting triggered for LSPs of both small and large bandwidth reservatio... | 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 Automatic Bandwidth Allocation for LSPs"
] |
auto-bandwidth | auto-bandwidth {
template name {
adjust-interval adjust-interval;
adjust-threshold adjust-threshold;
auto-bandwidth-subscription auto-bandwidth-subscription;
statistic-collection-interval statistic-collection-interval;
}
traceoptions {
file filename <files files> ... | [edit logical-systems name routing-instances name routing-options],
[edit logical-systems name routing-options],
[edit routing-instances name routing-options],
[edit routing-options] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "template name",
"desc": "Specify an auto-bandwidth template name with a maximum length of 64 characters."
},
{
"name": "adjust-interval",
"desc": "Specify the time interval after which the average bandwidth utilization is measured. Range: 30 through 3600 seconds Default: 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 17.3R1. | [] |
auto-configuration (System) | auto-configuration {
traceoptions {
file {
filename;
files number;
match reqular-expression;
size maximum-file-size;
(world-readable | no-world-readable);
}
flag flag;
level (all | error | info | notice | verbose | warning);
... | [edit system] | 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": "traceoptions",
"desc": "Set the trace options."
},
{
"name": "file",
"desc": "Configure the trace file information."
},
{
"name": "filename",
"desc": "Name of the file to receive the output of the tracing operation. Enclose the name within"
},
{
"name": "files numb... | 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. | [
"Autoinstallation Overview",
"Configuring Autoinstallation of Configuration Files"
] |
auto-configuration | auto-configuration {
command binary-file-path;
disable;
} | [edit system processes] | Configure the autoconfiguration process. | [
{
"name": "command binary-file-path",
"desc": "Path to the binary process."
},
{
"name": "disable",
"desc": "Disable the autoconfiguration process."
}
] | 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. | [
"Autoinstallation Overview",
"Configuring Autoinstallation of Configuration Files"
] |
auto-configure (Demux) | auto-configure {
address-ranges {
authentication {
password password-string;
username-include {
auth-server-realm realm-string;
delimiter delimiter-character;
domain-name domain-name;
interface-name;
sou... | [edit interfaces interface-name unit unit-number demux inet]
[edit interfaces interface-name unit unit-number demux inet6] | Enable the configuration of dynamic, auto-sensed subscriber interfaces for the demultiplexing (demux)
interface options. The remaining statement is 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 18.1R1. | [
"IP Demultiplexing Interfaces on Packet-Triggered Subscribers Services Overview",
"Configuring Packet Triggered Subscribers Using IP Demux Interfaces in Dynamic Profiles"
] |
auto-configure (Dynamic VLAN Interface Sets) | auto-configure {
agent-circuit-identifier {
dynamic-profile profile-name;
}
line-identity {
includes {
accept-no-ids {
mac-address;
}
circuit-id;
remote-id;
}
dynamic-profile profile-name;
}
} | [edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit],
[edit interfaces interface-name unit logical-unit-number] | Enable the configuration of dynamic, auto-sensed VLAN subscriber interfaces on a static or dynamic
underlying VLAN interface. Use the agent-circuit-identifier statement to configure dynamic VLANs based
only on the ACI.
Use the line-identity statement to configure dynamic VLANs that can be initiated by receipt of ACI, A... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring Dynamic Underlying VLAN Interfaces to Use Agent Circuit Identifier Information",
"Configuring Static Underlying VLAN Interfaces to Use Agent Circuit Identifier Information",
"Configuring Dynamic Underlying VLAN Interfaces to Use Access-Line Identifiers",
"Configuring Dynamic VLAN Subscriber Inter... |
auto-configure (IPv4) | auto-configure {
address-ranges {
session-timeout seconds;
dynamic-profile dynamic-profile {
network network-address;
}
authentication {
username-in... | [edit dynamic-profiles name interfaces junos-interface-ifd-name unit junos-interface-unit family
inet | Defines the parameters for creating dynamic VLAN (DVLAN) interface on receiving the first VLAN
packet from the client. | [
{
"name": "dynamic-profile",
"desc": ""
},
{
"name": "dynamic-profile",
"desc": "Name of the dynamic profile."
},
{
"name": "session-timeout",
"desc": ""
},
{
"name": "seconds",
"desc": "Duration of the active dynamic IP subscriber in seconds. If you do not configure the ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.2R1. | [
"BNG Redundancy for DHCP Subscribers Using Packet Triggered Based Recovery"
] |
auto-configure (IPv6) | auto-configure {
address-ranges {
session-timeout seconds;
dynamic-profile dynamic-profile {
prefix prefix;
}
authentication {
username-include {
... | [edit dynamic-profiles name interfaces junos-interface-ifd-name unit junos-interface-unit family
inet6 | Defines the parameters for creating dynamic VLAN (DVLAN) interface on receiving the first VLAN
packet from the client. | [
{
"name": "dynamic-profile",
"desc": ""
},
{
"name": "dynamic-profile",
"desc": "Name of the dynamic profile."
},
{
"name": "session-timeout",
"desc": ""
},
{
"name": "seconds",
"desc": "Duration of the active dynamic IP subscriber in seconds. If you do not configure the ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.2R1. | [
"BNG Redundancy for DHCP Subscribers Using Packet Triggered Based Recovery"
] |
auto-configure | auto-configure {
static-vlan-identity {
interface-tag name
}
vlan-ranges {
access-profile profile-name;
authentication {
packet-types [packet-types];
password password-string;
username-include{
circuit-id;
circuit... | [edit interfaces interface-name] | Enable the configuration of dynamic, auto-sensed VLANs. | [
{
"name": "static-vlan-identity",
"desc": "(Only for Junos OS Evolved that support subscriber management) Static VLAN identity configuration. This configuration creates dynamic VLAN for static IFL. The remove-when-no-subscribers option is not applicable when you configure static-vlan-identity. The remaining... | 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 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"
] |
auto-configure-trigger interface (ANCP) | auto-configure-trigger interface interface-name; | [edit protocols ancp neighbor ip-address] | Map an ANCP neighbor to a subscriber-facing physical interface on the router, so that ANCP Port Up
and Port Down messages trigger notifications to the auto-configuration daemon (autoconfd) to initiate
VLAN creation (Port Up) or removal (Port Down). | [
{
"name": "interface-name",
"desc": "Name of the physical interface. Can be any of the following interface types: ae, ge, xe, et, demux, ps."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R4.
ps interface type support added in Junos OS Release 19.3R1. | [
"Configuring ANCP Neighbors",
"Configuring the ANCP Agent"
] |
auto-conversion | auto-conversion; | [edit virtual-chassis] | Enable automatic Virtual Chassis port (VCP) conversion (also called VCP autoprovisioning) in a Virtual
Chassis.
VCP links connect members in a Virtual Chassis using supported VCP ports on the member switches.
Ports that are supported as VCPs and are not dedicated VCPs or configured as VCPs by default must be
converted ... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Releases 14.1X53-D47 and 15.1R7. | [
"Virtual Chassis Overview for Switches",
"Understanding Virtual Chassis Components",
"Setting an Uplink Port on an EX Series or QFX Series Switch as a Virtual Chassis Port"
] |
auto-dad (SLAAC Snooping) | auto-dad {
retries retry-count;
retrans-interval seconds;
} | [edit forwarding-options access-security slaac-snooping interface (interface-name | all)] | Configure parameters for Duplicate Address Detection (DAD) to be performed by the SLAAC snooping
device. DAD is used by IPv6 clients to verify the uniqueness of addresses obtained through stateless
address auto-configuration (SLAAC). DAD sends a Neighbor Solicitation message destined to the new
address. If there is a r... | [
{
"name": "retries retry-count",
"desc": "Configure the number of times that auto-DAD sends a Neighbor Solicitation message to verify the uniqueness of an address obtained through SLAAC."
},
{
"name": "retrans-interval",
"desc": ""
},
{
"name": "seconds",
"desc": "Configure the inter... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1. | [
"IPv6 Stateless Address Auto-configuration (SLAAC) Snooping"
] |
auto-derive | auto-derive {
lacp-pe-system-id-and-admin-key;
type-1-lacp;
type-3-system-mac {
local-discriminator number;
mac mac-address;
}
} | [edit interfaces aeX esi]
[edit interfaces aeX unit logical-unit-number esi] | Configure aggregated Ethernet interfaces and aggregated Ethernet logical interfaces to automatically
derive Ethernet segment identifiers (ESIs) from the Link Aggregation Control Protocol (LACP)
configuration.
We support the lacp-pe-system-id-and-admin-key option in the following environments:
•
On Juniper Networks dev... | [
{
"name": "lacp-pe-system-id-and-",
"desc": ""
},
{
"name": "admin-key",
"desc": "Specify that the ESI is automatically derived from the system id and admin key in the LACP configuration for the aggregated Ethernet interface on the local device (actor). NOTE: In Junos OS 22.2R1,lacp was rename t... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced on MX Series routers, QFX Series switches, and Junos on White Box in Junos OS
Release 18.4R1.
type-1-lacp and type-3-system-mac options introduced in Junos OS Release 22.2R1.
lacp option renamed and aliased to lacp-pe-system-id-and-admin-key in Junos OS Release 22.2R1.
Support for EVPN-MPLS introdu... | [] |
auto-discovery | auto-discovery; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name mep mep-id]
[edit logical-systems name protocols oam ethernet connectivity-fault-management maintenance-
domain name maintenance-association name mep mep-id] | Enable the MEP to accept continuity check messages from all remote MEPs.
The auto-discovery option is not available on SRX1500, SRX4100, SRX4200, and SRX4600 devices. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Statement introduced in Junos OS Release 10.2 for EX Series Switches. | [
"Configuring a MEP to Generate and Respond to CFM Protocol Messages"
] |
auto-discovery-only | auto-discovery-only; | [edit logical-systems logical-system-name protocols bgp family l2vpn],
[edit logical-systems logical-system-name protocols bgp group group-name family l2vpn],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address family
l2vpn],
[edit logical-systems logical-system-name routing-insta... | Enable the router to process only the autodiscovery network layer reachability information (NLRI)
update messages for VPWS and LDP-based Layer 2 VPN and VPLS update messages
(BGP_L2VPN_AD_NLRI) (FEC 129).
Specifically, the auto-discovery-only statement notifies the routing process (rpd) to expect autodiscovery-
related... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4R2. | [
"Example: Configuring BGP Autodiscovery for LDP VPLS",
"Example: Configuring BGP Autodiscovery for LDP VPLS with User-Defined Mesh Groups",
"Example: Configuring FEC 129 BGP Autodiscovery for VPWS"
] |
auto-export | auto-export {
disable;
family inet {
disable;
flow {
disable;
rib-group rib-group;
}
multicast {
disable;
rib-group rib-group;
}
unicast {
disable;
rib-group rib-group;
}
}
fa... | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "family",
"desc": "Address family."
},
{
"name": "inet",
"desc": "IP version 4 (IPv4) address family."
},
{
"name": "multicast",
"desc": "Multicast routing information."
},
{
"name": "unicast",
"desc": "Unicast routing information."
}
] | 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. | [
"Technology Overview: Understanding the Auto Export Feature"
] |
auto-image-upgrade | auto-image-upgrade; | [edit chassis] | Enable automatic software download using Zero Touch Provisioning (ZTP).
If the auto-image-upgrade statement is included in the factory default configuration, then ZTP will start
automatically when the device is booted up. Otherwise, ZTP will start with the first power cycle after
the auto-image-update statement is conf... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Upgrading Software by Using Automatic Software Download for Switches",
"Understanding Software Installation on EX Series Switches"
] |
auto-load-rebalance | auto-load-rebalance; | [edit fc-fabrics fabric-name proxy] | Configure the system to rebalance NP_Port link loads automatically on an FCoE-FC gateway proxy fabric
if the link loads become unbalanced. Load rebalancing is a disruptive action that forces some or all
sessions (depending on the configured load-balancing algorithm) to log out and then log in again. When
sessions log ... | [] | storage—To view this statement in the configuration.
storage-control—To add this statement to the configuration. | Command introduced in Junos OS Release 12.3. | [
"Defining the Proxy Load-Balancing Algorithm",
"Example: Configuring Automated Fibre Channel Interface Load Rebalancing",
"Simulating On-Demand Fibre Channel Link Load Rebalancing (Dry Run Test)",
"Understanding Load Balancing in an FCoE-FC Gateway Proxy Fabric",
"Monitoring Fibre Channel Interface Load Bal... |
auto-negotiation (QFX Series) | (auto-negotiation | no-auto-negotiation); | [edit interfaces interface-name ether-options] | Explicitly enable or disable autonegotiation. Autonegotiation is enabled by default, and will
autonegotiate the speed with the link partner. We recommend that you keep autonegotiation enabled
for interfaces operating at 1G and 10G.
•
auto-negotiation—Enable autonegotiation.
•
no-auto-negotiation—Disable autonegotiation... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring Gigabit and 10-Gigabit Ethernet Interfaces for EX4600 and QFX Series Switches",
"Junos OS Network Interfaces Library for Routing Devices"
] |
auto-negotiation | (auto-negotiation | no-auto-negotiation) <remote-fault (local-interface-online | local-interface-
offline)>; | [edit interfaces interface-name ether-options],
[edit interfaces interface-name gigether-options],
[edit interfaces ge-pim/0/0 switch-options switch-port port-number] | For Gigabit Ethernet interfaces on EX Series devices enable auto-negotiation. Auto-negotiation is
supported in some ACX devices. In ACX5448, ACX5448-D, ACX5448-M and ACX710, auto-negotiation
is supported on 1G interface. Beginning with Junos 21.1R1 and beyond, no-auto-negotiation
configuration through CLI is supported ... | [
{
"name": "remote-fault (local-interface-online | local-interface-offline)",
"desc": "(Optional) For M Series, MX Series, T Series,"
}
] | 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. | [
"Gigabit Ethernet Autonegotiation Overview",
"Configuring Gigabit Ethernet Interfaces (CLI Procedure)",
"Configuring Gigabit Ethernet Interfaces for EX Series Switches with ELS support"
] |
auto-policing | auto-policing {
class all (drop | loss-priority-high | loss-priority-low);
class ctnumber (drop | loss-priority-high | loss-priority-low);
} | [edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls] | Enable the automatic policing of all the MPLS LSPs on the router or logical system. | [
{
"name": "class all",
"desc": "Apply the same policer action to all the class types (ct0, ct1, ct2, and ct3)."
},
{
"name": "class ctnumber",
"desc": "Specific class type (ct0, ct1, ct2, or ct3) to which to apply a policer action."
},
{
"name": "Policer actions",
"desc": "You can sp... | 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.
Statement introduced for QFX10000 Series switches in release 15.1X53-D40.
Statement introduced for MX240, MX480, MX960, MX2010, and MX2020 routers with MPC10E and
MPC11E line cards in Junos OS 20.2R1. | [
"Configuring Automatic Policers"
] |
auto-provisioned | auto-provisioned; | [edit virtual-chassis] | Enable the auto-provisioned configuration mode for a Virtual Chassis Fabric (VCF).
When a VCF is autoprovisioned, you can plug and play leaf devices into your VCF. You do not need to
manually configure the required VCF parameters. When you interconnect a leaf device into the VCF, the
leaf device is automatically config... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51-D20. | [
"Autoprovisioning a Virtual Chassis Fabric",
"Understanding Virtual Chassis Fabric Configuration"
] |
auto-re-enrollment (Security) | auto-re-enrollment {
acme {
certificate-id certificate-id-name {
acme-key-id acme-key-id;
ca-profile-name ca-profile-name;
re-enroll-time (days value| hours value| percentage value);
re-enroll-trigger-time-percentage percentage;
re-generat... | [edit security pki] | Configure the automatic reenrollment of a local end-entity (EE) certificate. Auto-reenrollment requests
that the issuing CA replace a device certificate before its specified expiration date. | [
{
"name": "certificate-id",
"desc": "Auto reenrollment configuration for certificate ID."
},
{
"name": "acme-key-id",
"desc": "Specify the ACME account key identifier."
},
{
"name": "ca-profile-name",
"desc": "Specify the name of the certificate authority (CA) profile to be used for ... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.0. cmpv2 and scep options added in Junos OS Release 15.1X49-
D40.
Support for re-enroll-time (days value| hours value| percentage value) option added in Junos OS Release
21.4R1.
The acme optioin added in Junos OS Release 22.4R1. | [
"Basic Elements of PKI in Junos OS",
"show security ipsec statistics (MX240, MX480, MX960, SRX Series Firewalls and vSRX Virtual"
] |
auto-re-enrollment | auto-re-enrollment {
certificate-id {
ca-profile ca-profile-name;
challenge-password password;
re-enroll-trigger-time-percentage percentage;
re-generate-keypair;
validity-period days;
}
} | [edit security pki] | Specify auto-reenrollment parameters for a certificate authority (CA) issued router certificate. Auto-
reenrollment requests that the issuing CA replace a router certificate before its specified expiration date. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring Auto-Reenrollment of a Router Certificate",
"Configuring Digital Certificates for Adaptive Services Interfaces"
] |
auto-reconnect | auto-reconnect seconds; | [edit interfaces interface-name unit logical-unit-number pppoe-options],
[edit logical-systems logical-system-name interfaces interface-name
unit logical-unit-number pppoe-options] | PPP over Ethernet interfaces, configure the amount of time to wait before reconnecting after a session
has terminated. | [
{
"name": "seconds",
"desc": "Time to wait before reconnecting after a session has terminated."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the PPPoE Automatic Reconnect Wait Timer"
] |
auto-recovery | auto-recovery; | [edit logical-systems name protocols isis dynamic-overload],
[edit logical-systems name routing-instances name protocols isis dynamic-overload],
[edit logical-systems name tenants name routing-instances name protocols isis dynamic-overload],
[edit protocols isis dynamic-overload],
[edit routing-instances name protocol... | Enable Auto-recovery to recover from dynamic overload state.
IS-IS enters a dynamic overload state when the prefix limit is reached or when the LSP fragment space is
exhausted. Enabling auto-recovery prevents ISIS from flushing of all the LSP fragments. When the
fragment space becomes available, IS-IS exits from the dy... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.1 | [] |
auto-rp | auto-rp {
(announce | discovery | mapping);
(mapping-agent-election | no-mapping-agent-election);
} | [edit logical-systems logical-system-name protocols pim rp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp],
[edit protocols pim rp],
[edit routing-instances routing-instance-name protocols pim rp] | Configure automatic RP announcement and discovery. | [
{
"name": "announce",
"desc": "Configure the routing device to listen only for mapping packets and also to advertise itself if"
},
{
"name": "discovery",
"desc": "Configure the routing device to listen only for mapping packets."
},
{
"name": "mapping",
"desc": "Configures the routing... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5.
The auto-rp options announce and mapping are not supported on QFX5220-32CD devices running Junos OS
Evolved Release 19.3R1, 19.4R1, or 20.1R1. | [
"Configuring PIM Auto-RP"
] |
auto-satellite-conversion (Junos Fusion) | auto-satellite-conversion {
satellite [slot-id | range | all];
} | [edit chassis satellite-management] | Enable automatic satellite conversion in a Junos Fusion.
Automatic satellite conversion automatically configures a switch into a satellite device when it is cabled
into the aggregation device.
Additional configuration steps are required to add satellite devices to a Junos Fusion using automatic
satellite conversion. Se... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring or Expanding a Junos Fusion Enterprise",
"Configuring Junos Fusion Provider Edge"
] |
auto-sense | auto-sense {
hold-down hold-down;
} | [edit fabric protocols bgp group name link-bandwidth],
[edit logical-systems name protocols bgp group name link-bandwidth],
[edit logical-systems name routing-instances name protocols bgp group name link-bandwidth],
[edit logical-systems name tenants name routing-instances name protocols bgp group name link-
bandwidth]... | Enable auto-sensing of link-bandwidth and attaching the link-bandwidth community on a route at
import. BGP can communicate link speeds to remote peers, enabling better optimization of traffic
distribution for load balancing. This facilitates the integration of devices with different transmission
speeds within the netw... | [
{
"name": "hold-down",
"desc": "Hold down in secs for link bandwidth auto-sense Range: 0 through 3600"
}
] | 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. | [] |
auto-service-id | auto-service-id; | [edit logical-systems name routing-instances name protocols evpn],
[edit routing-instances name protocols evpn] | Enable auto-derivation of EVPN-VPWS service instance identifier. When you enable auto-service-id, the
device derives the VPWS service ID from the normalized VLAN ID.
NOTE: This option only applies to the EVPN-VPWS flexible cross-connect (FXC) VLAN
aware service (VLAN signaled flexible cross connect). | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [] |
auto-snapshot | auto-snapshot; | [edit system] | Enable the automatic snapshot feature, which allows the device to automatically fix a corrupt Junos OS
file in the primary root partition. If the automatic snapshot feature is enabled, the device automatically
takes a snapshot of the Junos OS root file system in the alternate root partition and copies it onto the
prima... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring Dual-Root Partitions"
] |
auto-sw-sync | auto-sw-sync node node-name (disable | enable); | [edit system] | (Junos OS Evolved only) When you add a new Routing Engine to the device and the new Routing Engine
has a different software version than the rest of the system, by default the Routing Engine is kept out of
the system. If you want a new Routing Engine's software and configuration to be automatically upgraded
and synchro... | [
{
"name": "disable | enable",
"desc": "(Required) Specify whether to disable or enable automatic software synchronization from the primary node to the new Routing Engine. Default: Disable"
},
{
"name": "node node-name",
"desc": "Specify the node to be synchronized (fpc0 | re0 | re1). Deprecated... | 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.2R1.
node option deprecated as of Junos OS Evolved Release 20.4R2. | [
"Replace a Routing Engine in a Dual-Routing Engine System"
] |
auto-sw-update | auto-sw-update {
(ex-4200 | ex-4300 | ex-4500 | ex-4600 | ex-2300 | ex-3400 | ex-4000 | ex-4100 | ex-4400)
package-name package-name;
} | [edit virtual-chassis] | Enable the automatic software update feature for Virtual Chassis or Virtual Chassis Fabric (VCF)
configurations.
You should only use the keywords that specify a device or device family—ex-4300, ex-4600, qfx-3, and qfx-5
—when configuring automatic software update on a mixed mode Virtual Chassis or Virtual Chassis Fabri... | [
{
"name": "package-name",
"desc": ""
},
{
"name": "package-name",
"desc": "Specify the software package name or a path to a Junos OS software image to update new members being added to a Virtual Chassis or VCF. . If the software package is located on a local directory on the switch, use the fol... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statements introduced in Junos OS Release 10.0 for EX Series switches.
The ex-4200 and ex-4500 options introduced in Junos OS Release 12.2 for EX Series switches.
Statements introduced in Junos OS Release 13.2X50-D15 for the QFX Series.
The ex-4300, qfx-3, and qfx-5 options introduced in Junos OS Release 13.2X51-D20.
S... | [
"Configuring Automatic Software Update on Virtual Chassis Member Switches",
"Understanding Software Upgrades in a Virtual Chassis",
"Understanding Software Upgrades in a Virtual Chassis Fabric",
"Example: Configuring Automatic Software Update on EX4200 Virtual Chassis Member Switches"
] |
auto-targeted-session | auto-targeted-session {
maximum-sessions number;
teardown-delay seconds;
} | [edit logical-systems logical-system-name protocols ldp],
[edit protocols ldp] | Configure session parameters for LDP sessions established with the remote LFA node that are
automatically targeted using the loopback addresses. Configure parameters of automatically targeted
sessions for remote LFA only. | [
{
"name": "maximum-sessions",
"desc": ""
},
{
"name": "number",
"desc": "Specify the maximum number of auto-targeted LDP sessions allowed. Include this statement to optimize the use of router memory. Default: 100 Range: 1 through 1000"
},
{
"name": "teardown-delay",
"desc": ""
},... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
autodiscovery | autodiscovery {
inet-mdt;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
mvpn family inet],
[edit routing-instances routing-instance-name protocols pim mvpn family inet] | For draft-rosen 7, enable the PE routers in the VPN to discover one another automatically. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
Statement moved to [..protocols pim mvpn family inet] from [.. protocols pim mvpn] in Junos OS Release
13.3. | [
"Example: Configuring Source-Specific Multicast for Draft-Rosen Multicast VPNs"
] |
autodiscovery-only | autodiscovery-only {
intra-as {
inclusive;
}
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols mvpn
family (inet | inet6)],
[edit routing-instances routing-instance-name protocols mvpn family (inet | inet6)] | Enable the Rosen multicast VPN to use the MDT-SAFI autodiscovery NLRI. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
Statement moved to [..protocols pim mvpn family inet] from [.. protocols mvpn] in Junos OS Release 13.3.
Support for IPv6 added in Junos OS Release 17.3R1. | [
"Example: Configuring Source-Specific Multicast for Draft-Rosen Multicast VPNs"
] |
autoinstallation (JNU Satellite Devices) | autoinstallation {
delete-after-commit;
configuration-servers {
url;
}
interfaces {
interface-name {
bootp;
rarp;
}
}
} | [edit system] | (Satellite devices in a JNU group) Download a configuration file automatically from an FTP or HTTP
server. When you power on a router or switch configured for autoinstallation, it requests an IP address
from a Dynamic Host Configuration Protocol (DHCP) server. When the router or switch has an address,
it sends a reques... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Autoinstallation of Satellite Devices in a Junos Node Unifier Group",
"Autoinstallation Process on Satellite Devices in a Junos Node Unifier Group",
"Configuring Autoinstallation of Configuration Files",
"Configuring Autoinstallation of Configuration Files"
] |
autoinstallation | autoinstallation;
autoinstallation {
configuration-servers {
url {
password password;
}
}
interfaces {
interface-name {
bootp;
rarp;
}
}
usb {
disable;
}
} | [edit system] | Specify the configuration for autoinstallation. Download a configuration file automatically from an FTP,
Hypertext Transfer Protocol (HTTP), or Trivial FTP (TFTP) server. When you power on a router or switch
configured for autoinstallation, it requests an IP address from a Dynamic Host Configuration Protocol
(DHCP) ser... | [] | 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. | [
"ACX Series Autoinstallation Overview",
"Before You Begin Autoinstallation on an ACX Series Universal Metro Router",
"Autoinstallation Configuration of ACX Series Universal Metro Routers",
"USB Autoinstallation on ACX Series Routers",
"Verifying Autoinstallation on ACX Series Universal Metro Routers",
"sh... |
automatic (Security) | automatic {
enable;
interval (Security IDP) hours;
start-time (Security IDP) start-time;
}
NOTE: The option download-timeout is a hidden option in CLI help and not intended for
general use. It is retained for backward compatibility. A warning message is displayed if
you use this option. | [edit security idp security-package] | Enable the device to automatically download the updated signature database from the specified URL. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
automatic (Source NAT Next Gen Services) | automatic (random-allocation | round-robin); | [edit services nat source pool nat-pool-name port] | Configure automatic port assignment for source NAT with port translation, except for deterministic
NAT. Automatic port assignment uses the port range 1024 through 65535. Specify either random
allocation or round-robin allocation. Random allocation randomly assigns a port from the range 1024
through 65535 for each port ... | [
{
"name": "random-allocation",
"desc": "Randomly assigns a port from the range 1024 through 65535 for each port translation."
},
{
"name": "round-robin",
"desc": "First assigns port 1024, and uses the next higher port for each successive port assignment. Round robin allocation is the default."
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [] |
automatic | automatic {
interval hour;
start-time time;
} | [edit services application-identification download] | Define automatic download properties. | [
{
"name": "interval hour",
"desc": "Download interval in hours. The default is 24 and the range is from 1 through 168."
},
{
"name": "start-time time",
"desc": "Start-time value. The default is 0:00 and the range is from 0:00 through 24:00."
}
] | 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 Automatic Download of Application Package Updates"
] |
automatic-site-id | automatic-site-id {
collision-detect-time seconds;
new-site-wait-time seconds;
reclaim-wait-time minimum seconds maximum seconds;
startup-wait-time seconds;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
site site-name],
[edit routing-instances routing-instance-name protocols vpls site site-name] | Enable automatic site identifiers for VPLS routing instances.
When you configure automatic-site-id for the first time, you must deactivate and then activate protocol
vpls. However, if you already have automatic-site-id configured, you do not need to deactivate and then
activate protocol vpls. | [
{
"name": "collision-detect-time",
"desc": "The time in seconds to wait after a claim advertisement is sent to the other routers"
},
{
"name": "new-site-wait-time",
"desc": "The time in seconds to wait to receive VPLS information for a newly configured"
},
{
"name": "reclaim-wait-time",
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Configuring Automatic Site Identifiers for VPLS"
] |
autonomous (Dynamic Router Advertisement) | (autonomous | no-autonomous); | [edit dynamic-profiles profile-name protocols router-advertisement interface interface-name
prefix prefix] | Specify whether prefixes in the router advertisement messages are used for stateless address
autoconfiguration:
•
autonomous—Use prefixes for address autoconfiguration.
•
no-autonomous—Do not use prefixes for address autoconfiguration.
Default
autonomous | [] | 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"
] |
autonomous | (autonomous | no-autonomous); | [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 prefixes in the router advertisement messages are used for stateless address
autoconfiguration:
•
autonomous—Use prefixes for address autoconfiguration.
•
no-autonomous—Do not use prefixes for address autoconfiguration.
Default
autonomous | [] | 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"
] |
autonomous-system | autonomous-system autonomous-system <asdot-notation> <loops number> {
independent-domain <no-attrset>;
} | [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] | Specify the routing device’s AS number.
An autonomous system (AS) is a set of routing devices that are under a single technical administration
and that generally use a single interior gateway protocol (IGP) and metrics to propagate routing
information within the set of routing devices. An AS appears to other ASs to hav... | [
{
"name": "autonomous-system",
"desc": "AS number. Use a number assigned to you by the NIC."
},
{
"name": "[edit]",
"desc": ""
},
{
"name": "routing-options {",
"desc": ""
},
{
"name": "autonomous-system 65546;",
"desc": ""
},
{
"name": "}",
"desc": "Range: 0.... | 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.
asdot-notation option introduced in Junos OS Release 9.3.
asdot-notation option introduced in Junos OS Release 9.3 for EX Series switches.
no-attrset option introduced in Junos OS Release 10.4. | [
"Examples: Configuring External BGP Peering",
"Examples: Configuring Internal BGP Peering"
] |
autonomous-system-type (Flow Monitoring) | autonomous-system-type (origin | peer); | [edit forwarding-options accounting output cflowd hostname],
[edit forwarding-options sampling instance instance-name family (inet |inet6 |mpls) output flow-
server hostname],
[edit forwarding-options sampling family (inet |inet6 |mpls) output flow-server hostname] | Specify the type of AS numbers that cflowd exports.
Default
origin | [
{
"name": "origin",
"desc": "Export origin AS numbers of the packet source address in the Source Autonomous System"
},
{
"name": "peer",
"desc": "Export peer AS numbers through which the packet passed in the Source Autonomous System"
}
] | 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. | [
"Enabling Flow Aggregation",
"Directing Traffic Sampling Output to a Server Running the cflowd Application"
] |
autostate-exclude | autostate-exclude; | [edit interfaces interface-name ether-options] | Specify not to include an IRB interface in the state calculation for VLAN members. The default behavior
is not to exclude an IRB interface in the state calculation unless all the ports on the interface go down.
Because an IRB interface often has multiple ports in a single VLAN, the state calculation for a VLAN
member m... | [] | 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-D40 and Junos OS Release 17.3R1. | [
"Excluding an IRB Interface from State Calculations on a QFX Series Switch",
"show ethernet-switching interface"
] |
auxiliary | auxiliary {
disable;
insecure;
type terminal-type;
port-type (mini-usb | rj45);
} | [edit system ports] | Configure the characteristics of the auxiliary port.
Default
The auxiliary port is disabled. disable is the default option. | [
{
"name": "disable",
"desc": "Disable the port."
},
{
"name": "insecure",
"desc": "Disable super user access or root logins to establish terminal connection."
},
{
"name": "type terminal-type",
"desc": "Type of terminal that is connected to the port. Range: ansi, vt100, small-xterm,... | 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.
port-type introduced in Junos OS Release 11.3 for EX Series switches. | [
"Configuring Junos OS to Set Console and Auxiliary Port Properties",
"Configuring Console and Auxiliary Port Properties",
"Configuring the Console Port Type (CLI Procedure)"
] |
auxiliary-spi (Security IPsec) | auxiliary-spi auxiliary-spi-value; | [edit security ipsec security-association sa-name manual direction (inbound | outbound | bi-
directional)] | Configure the auxiliary Security Parameter Index (SPI) for a manual SA. Use the auxiliary SPI when you
configure the protocol statement to use the bundle option. | [
{
"name": "auxiliary-spi-value",
"desc": "Arbitrary value that uniquely identifies which SA to use at the receiving host (the"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Manual IPsec Security Associations for an ES PIC"
] |
auxiliary-spi | auxiliary-spi spi-value; | [edit services ipsec-vpn rule rule-name term term-name then manual direction direction] | Configure an auxiliary Security Parameter Index (SPI) for a manual SA. Use the auxiliary SPI when you
configure the protocol statement to use the bundle option. | [
{
"name": "spi-value",
"desc": "An arbitrary value that uniquely identifies which SA to use at the receiving host (the"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Security Associations"
] |
avg-fd-twoway-threshold | avg-fd-twoway-threshold avg-fd-twoway-threshold-value{
flap-trap-monitor seconds;} | [edit protocols oam ethernet connectivity-fault-management performance-monitoring sla-iterator-profiles
profile-name] | Configure the threshold value for average frame delay, in microseconds, for two-way Ethernet frame
delay measurement (ETH-DM). When the configured threshold for average frame delay is exceeded, an
SNMP trap is generated for ETH-DM. SNMP traps are triggered if you configure either the average
frame-delay threshold or th... | [
{
"name": "avg-fd-twoway-threshold-value",
"desc": "Threshold value for average frame delay, in microseconds, for two-way"
},
{
"name": "flap-trap-monitor seconds",
"desc": "Duration in seconds, for summarizing flap occurrences and send out a single"
}
] | Configure—To enter configuration mode.
Control—To modify any configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring an Iterator Profile",
"Configure an Iterator Profile on a Switch (CLI Procedure)"
] |
avg-flr-backward-threshold | avg-flr-backward-threshold avg-flr-backward-threshold-value;{
flap-trap-monitor seconds; } | [edit protocols oam ethernet connectivity-fault-management performance-monitoring sla-iterator-profiles
profile-name] | Configure the threshold value for average frame loss ratio, in milli-percent, in the backward or
downstream direction for Ethernet loss measurement (ETH-LM) and Ethernet synthetic loss
measurement (ETH-SLM). When the configured threshold for average backward frame loss ratio is
exceeded, an SNMP trap is generated for E... | [
{
"name": "avg-flr-backward-threshold-value",
"desc": "Threshold value for average frame loss ratio in the backward or"
},
{
"name": "flap-trap-monitor seconds",
"desc": "Duration in seconds, for summarizing flap occurrences and send out a single"
}
] | configure—To enter configuration mode.
control—To modify any configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring an Iterator Profile",
"Configure an Iterator Profile on a Switch (CLI Procedure)"
] |
avg-flr-forward-threshold | avg-flr-forward-threshold avg-flr-forward-threshold-value;{
flap-trap-monitor seconds; } | [edit protocols oam ethernet connectivity-fault-management performance-monitoring sla-iterator-profiles
profile-name] | Configure the threshold value for average frame loss ratio, in milli-percent, in the upstream or forward
direction for Ethernet loss measurement (ETH-LM) and Ethernet synthetic loss measurement (ETH-
SLM). When the configured threshold for average forward frame loss ratio is exceeded, an SNMP trap is
generated for ETH-... | [
{
"name": "avg-flr-forward-threshold-value",
"desc": "Threshold value for average frame loss ratio in the forward or upstream"
},
{
"name": "flap-trap-monitor seconds",
"desc": "Duration in seconds, for summarizing flap occurrences and send out a single"
}
] | configure—To enter configuration mode.
control—To modify any configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring an Iterator Profile",
"Configure an Iterator Profile on a Switch (CLI Procedure)"
] |
avg-ifdv-twoway-threshold | avg-ifdv-twoway-threshold avg-ifdv-twoway-threshold-value; {
flap-trap-monitor seconds; } | [edit protocols oam ethernet connectivity-fault-management performance-monitoring sla-iterator-profiles
profile-name] | Configure the threshold value for average frame delay variation, in microseconds, for two-way Ethernet
frame delay measurement (ETH-DM). When the configured threshold for average frame delay variation
is exceeded, an SNMP trap is generated for ETH-DM. SNMP traps are triggered if you configure either
the average frame-d... | [
{
"name": "avg-ifdv-twoway-threshold-value",
"desc": "Threshold value for average frame delay variation, in microseconds, for"
},
{
"name": "flap-trap-monitor seconds",
"desc": "Duration in seconds, for summarizing flap occurrences and send out a single"
}
] | configure—To enter configuration mode.
control—To modify any configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring an Iterator Profile",
"Configure an Iterator Profile on a Switch (CLI Procedure)"
] |
avira-engine | avira-engine {
pattern-update {
email-notify {
admin-email admin-email;
custom-message custom-message;
custom-message-subject custom-message-subject;
}
interval interval;
no-autoupdate;
proxy-profile proxy-profile;
routing-instance... | [edit security utm default-configuration anti-virus] | The Avira scan engine is a licensed feature provided as a downloadable module. Download and install
the Avira scan engine either through SRX with Internet connectivity to Juniper hosted URL, user hosted
URL, or manually.
The Antivirus engine provides a full file-based virus scanning function which is available through ... | [] | security— To view this statement in the configuration.
security-control— To add this statement to the configuration. | The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Statement introduced in Junos OS Release 18.4R1. | [] |
avp (L2TP Tunnel Switching) | avp {
bearer-type;
calling-number;
cisco-nas-port-info;
} | [edit access tunnel-switch-profile profile-name] | Specify the action taken on L2TP AVPs that are negotiated when the first session is created; these AVPs
are contained in the L2TP packets that are switched by the tunnel switch profile.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax se... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"L2TP Tunnel Switching For Multiple-Domain Networks",
"B"
] |
backoff-period | backoff-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 backoff period for bidirectional PIM. The backoff-
period statement configures the period that the acting DF waits between receiving a better DF Offer
and sending the Pass message to transfer DF responsibility.
NOTE: Junos OS checks rendezvous point (RP) unicast reachab... | [
{
"name": "milliseconds",
"desc": "Period that the acting DF waits between receiving a better DF Offer and sending the Pass"
}
] | 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"
] |
backup (MBGP MVPN) | backup address; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols mvpn
static-umh],
[edit routing-instances routing-instance-name protocols mvpn static-umh] | Define a backup upstream multicast hop (UMH) for type 7 (S,G) routes.
If the primary UMH is unavailable, the backup is used. If neither UMH is available, no UMH is selected. | [
{
"name": "address",
"desc": "Address of the backup UMH."
}
] | 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. | [
"Understanding Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider",
"Tunnels",
"Example: Configuring Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider",
"Tunnels"
] |
backup (OCS Partition) | backup {
limit;
timeout seconds;
overflow (deny-login | drop-oldest);
} | [edit access ocs partition partition-name] | Provides file backup for OCS data when both primary and alternative paths to the OCS are down. | [
{
"name": "limit",
"desc": "The limit on the total number of backup entries. The login fails if the backup entries exceeds the prescribed limit."
},
{
"name": "timeout seconds",
"desc": "The timeout for backup operation."
},
{
"name": "overflow (deny-login | drop-",
"desc": ""
},
... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1. | [
"Configuring the OCS Partition",
"Gy File Backup Overview",
"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",
"Underst... |
backup-bridge-priority | backup-bridge-priority priority; | [edit logical-systems logical-system-name protocols (mstp | rstp)],
[edit logical-systems logical-system-name protocols vstp vlan vlan-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(mstp | rstp)],
[edit logical-systems logical-system-name routing-instances routing-ins... | Determine the priority of the backup bridge in a VPLS multihomed Layer 2 ring with MPLS
infrastructure. | [
{
"name": "priority",
"desc": "The backup bridge priority can be set only in increments of 4096."
}
] | 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. | [
"Understanding VPLS Multihoming",
"Configuring VPLS Root Protection Topology Change Actions to Control Individual VLAN Spanning-",
"Tree Behavior"
] |
backup-destination | backup-destination destination-address; | [edit interfaces interface-name unit logical-unit-number tunnel], [edit logical-systems logical-
system-name interfaces interface-name unit logical-unit-number tunnel] | For tunnel interfaces, specify the remote address of the backup tunnel. | [
{
"name": "destination-address",
"desc": "Address of the remote side of the connection."
}
] | 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 IPsec Tunnel Redundancy"
] |
backup-interface (Layer 2 Circuits) | backup-interface interface-name; | [edit logical-systems logical-system-name protocols l2circuit local-switching interface
interface-name end-interface interface interface-name],
[edit protocols l2circuit local-switching interface interface-name end-interface interface
interface-name] | Specify the interface to be used by the protection pseudowire in connection protection configurations
for Layer 2 circuits. | [] | 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. | [
"Example: Configuring Layer 2 Circuit Switching Protection"
] |
backup-interface | backup-interface interface-name; | [edit interfaces interface-name es-options] | Configure a backup ES Physical Interface Card (PIC). When the primary ES PIC has a servicing failure, the
backup becomes active, inherits all the tunnels and security associations (SAs), and acts as the new next
hop for IPsec traffic. | [
{
"name": "interface-name",
"desc": "Name of ES interface to serve as the backup."
}
] | 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 ES PIC Redundancy"
] |
backup-liveness-detection | backup-liveness-detection {
backup-peer-ip ipv4-address;
routing-instance routing-instance;
} | [edit protocols iccp peer] | Determine whether a peer is up or down by exchanging keepalive messages over the management link
between the two Inter-Chassis Control Protocol (ICCP) peers.
When an ICCP connection is operationally down, the status of the peers hosting a multichassis link
aggregation group (MC-LAG) is detected by sending liveness dete... | [
{
"name": "routing-instance",
"desc": ""
},
{
"name": "routing-instance",
"desc": "You can configure the name of the management routing instance on which backup-peer-ip is reachable, if it is not the default routing instance."
}
] | 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.
routing-instance option introduced in Junos OS Release 24.2R2 | [
"Configuring Multichassis Link Aggregation on MX Series Routers"
] |
backup-neighbor | backup-neighbor address {
community name;
mtu number;
hot-standby;
psn-tunnel-endpoint address;
standby;
static;
virtual-circuit-id number;
} | [edit logical-systems logical-system-name protocols l2circuit local-switching interface
interface-name],
[edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
neighbor ... | Configure pseudowire redundancy for Layer 2 circuits and VPLS. A redundant pseudowire can act as a
backup connection and can be configured between a PE router and a CE device or between PE routers,
maintaining Layer 2 circuit and VPLS services after certain types of failures. This feature can help
improve the reliabili... | [
{
"name": "address",
"desc": "Specifies the address for the backup neighbor."
}
] | 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. | [
"Configuring Pseudowire Redundancy on the PE Router",
"Example: Configuring Layer 2 Circuit Switching Protection"
] |
backup-on-failure (Accounting Options) | backup-on-failure (master-and-slave | master-only); | [edit accounting-options file filename] | Configure the router to save a copy of the accounting file locally, to the /var/log/pfedBackup directory
of the relevant Routing Engine, in the event that file transfer to the remote archive sites cannot be
completed. | [
{
"name": "master-and-slave",
"desc": "Back up accounting files from both the primary Routing Engine and the backup Routing Engine."
},
{
"name": "master-only",
"desc": "Back up accounting files from only the primary Routing Engine."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Accounting-Data Log Files",
"Configuring Flat-File Accounting for Layer 2 Wholesale",
"Configuring Flat-File Accounting for Extensible Subscriber Services Management",
"Flat-File Accounting Overview"
] |
backup-options | backup-options {
interface interface-name;
} | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Configure an interface to be used as a backup interface if the primary interface goes down. This is used
to support ISDN dial backup operation.
The remaining statement is 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. | [] |
backup-pe-group | backup-pe-group group-name {
backups [ addresses ];
local-address address;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options multicast] | Configure a backup provider edge (PE) group for ingress PE redundancy when point-to-multipoint label-
switched paths (LSPs) are used for multicast distribution. | [
{
"name": "group-name",
"desc": "Name of the group for PE backups."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Example: Configuring Ingress PE Redundancy"
] |
backup-peer-ip | backup-peer-ip ipv4-address; | [edit protocols iccp peer backup-liveness-detection] | Specify the IP address of the peer being used as a backup peer in the Bidirectional Forwarding Detection
(BFD) configuration. You can specify any IP address in the default routing-instance. We recommend
using the management IP addresses associated with fxp0 or em0 for redundancy in the event of a network
disruption. | [] | 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. | [] |
backup-remote-gateway | backup-remote-gateway address; | [edit services ipsec-vpn rule rule-name term term-name then] | Define the backup remote address to which the IPsec traffic is directed when the primary remote
gateway is down. Configuring this statement also enables the dead peer detection (DPD) protocol. | [
{
"name": "address",
"desc": "Backup remote IPv4 or IPv6 address."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IPsec Rules"
] |
backup-router | backup-router address <destination destination-address>; | [edit system] | Set a default router (running IP version 4 [IPv4]) to use while the local router (running IPv4) is booting
and if the routing protocol processes fail to start. Junos OS or Junos OS Evolved removes the route to
this router as soon as the software starts. | [
{
"name": "address",
"desc": "Address of the default router."
},
{
"name": "destination",
"desc": ""
},
{
"name": "destination-address",
"desc": "(Optional) Destination address that is reachable through the backup router. You can include this option to achieve network reachability wh... | 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 Evolved Release 25.4R1. | [
"Configuring a Backup Router"
] |
backup-selection (Protocols IS-IS) | backup-selection {
destination prefix {
interface (interface-name| all){
admin-group {
exclude [ group-name ];
include-all [ group-name ];
include-any [ group-name ];
preference [ group-name ];
}
bandwidt... | [edit logical-systems logical-system-name routing-options],
[edit logical-systems logical-system-name routing-instances instance-name routing-options],
[edit routing-instances instance-name routing-options],
[edit routing-options] | Define backup selection policies, per prefix per primary next-hop interface, to enforce loop-free
alternate (LFA) selection based on admin-group, srlg, bandwidth, protection-type, node, node-tag, and
metric attributes of the backup path.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "destination",
"desc": ""
},
{
"name": "prefix",
"desc": "Define the backup selection policy for a particular destination prefix or for all the prefixes. The prefix is the destination prefix name and prefix length. You can specify 0/0 for the IPv4 least-specific prefix or 0::0/0 for th... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Understanding Backup Selection Policy for IS-IS Protocol",
"Example: Configuring Backup Selection Policy for IS-IS Protocol"
] |
backup-selection (Protocols OSPF) | backup-selection {
destination prefix {
interface (interface-name| all){
admin-group {
exclude [ group-name ];
include-all [ group-name ];
include-any [ group-name ];
preference [ group-name ];
}
bandwid... | [edit logical-systems logical-system-name routing-options],
[edit logical-systems logical-system-name routing-instances instance-name routing-options],
[edit routing-instances instance-name routing-options],
[edit routing-options] | Define backup selection policies, per prefix per primary next-hop interface, to enforce loop-free
alternate (LFA) selection based on admin-group, srlg, bandwidth, protection-type, node, and metric
attributes of the backup path. | [
{
"name": "destination",
"desc": ""
},
{
"name": "prefix",
"desc": "Define the backup selection policy for a particular destination prefix or for all the prefixes. The value prefix defines the destination prefix name and prefix length. You can specify 0/0 for the IPv4 least-specific prefix or 0:... | 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. | [
"Example: Configuring Backup Selection Policy for the OSPF or OSPF3 Protocol",
"Configuring Backup Selection Policy for the OSPF Protocol",
"Understanding Backup Selection Policy for OSPF Protocol"
] |
backup-spf-options (Protocols IS-IS) | backup-spf options {
node-link-degradation;
per-prefix-calculation;
remote-backup-calculation;
use-source-packet-routing;
} | [edit logical-systems logical-system-name protocols isis],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
isis],
[edit protocols isis],
[edit routing-instances routing-instance-name protocols isis] | Configure options for running the shortest-path-first (SPF) algorithm for backup next hops for protected
interfaces. Use these options to override the default behavior of having Junos OS calculate backup
paths for all the topologies in an instance when at least one interface is configured with link protection
or node-l... | [
{
"name": "node-link-degradation",
"desc": "Degrade an interface from node-link to link protection in case no node protection LFA route is found for a given destination node."
},
{
"name": "per-prefix-calculation",
"desc": "Calculate backup next hops for non-best prefix originators."
},
{
... | routing—To view this statement in the configuration.
routing-control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4R3.
node-link-degradation option added in Junos OS Release 14.2.
use-source-packet-routing option introduced in Junos OS Release 16.2R1 for MX Series and PTX Series
routers.
Support for this option introduced in Junos OS Release 17.2R1 for QFX5100 and QFX10000 switches.
Supp... | [
"Example: Configuring MPLS Egress Protection for Layer 3 VPN Services",
"Example: Configuring Layer 3 VPN Egress Protection with RSVP and LDP"
] |
backup-spf-options (Protocols OSPF) | backup-spf-options {
disable;
downstream-paths-only;
no-install;
node-link-degradation;
per-prefix-calculation {
all;
externals;
stubs;
summary;
}
remote-backup-calculation;
} | [edit logical-systems logical-system-name protocols (ospf | ospf3)],
[edit logical-systems logical-system-name protocols ospf topology (default | name)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(ospf | ospf3)],
[edit logical-systems logical-system-name routing-instan... | Configure options for running the shortest-path-first (SPF) algorithm for backup next hops for protected
interfaces. Use these options to override the default behavior of having Junos OS calculate backup
paths for all the topologies in an instance when at least one interface is configured with link protection
or node-l... | [
{
"name": "disable",
"desc": "Do not calculate backup next hops for the specified instance or topology."
},
{
"name": "downstream-paths-only",
"desc": "Calculate and install only downstream paths as defined in RFC 5286, Basic Specification for IP Fast Reroute: Loop-Free Alternates for the specif... | routing—To view this statement in the configuration.
routing-control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
node-link-degradation, per-prefix-calculation, and remote-backup-calculation options introduced in Junos OS
Release 15.1.
Support for remote-backup-calculation option introduced in Junos OS Release 18.2R1 for QFX5100,
QFX5110, and QFX5200 switches. | [
"Configuring Backup SPF Options for Protected OSPF Interfaces"
] |
backups | backups [ addresses ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast backup-pe-group group-name],
[edit logical-systems logical-system-name routing-options multicast backup-pe-group group-name],
[edit routing-instances routing-instance-name routing-options multicast backup-pe-gro... | Configure the address of backup PEs for ingress PE redundancy when point-to-multipoint label-
switched paths (LSPs) are used for multicast distribution. | [
{
"name": "addresses",
"desc": "Addresses of other PEs in the backup group."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Example: Configuring Ingress PE Redundancy"
] |
backward-frr-enable | (backward-frr-enable | no-backward-frr-enable); | [edit interfaces interface-name otn-options preemptive-fast-reroute] | Enable or disable backward fast reroute status insertion.
Enable backward fast reroute to insert local pre-forward error correction (FEC) bit error rate (BER) status
into transmitted OTN frames, notifying the remote interface. The remote interface can use the
information to reroute traffic to a different interface. Whe... | [
{
"name": "backward-frr-enable",
"desc": "Enable backward fast reroute status insertion."
},
{
"name": "no-backward-frr-enable",
"desc": "Do not enable backward fast reroute status insertion."
}
] | 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. | [
"Understanding Pre-FEC BER Monitoring and BER Thresholds",
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
bad-inner-header | bad-inner-header; | [edit security screen ids-option ids-option-name ip tunnel] | Enable IP tunnel bad inner header IDS option. | [] | 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-D10. | [
"Attack Detection and Prevention Overview"
] |
bad-option (IDS Screen Next Gen Services) | bad-option; | [edit services screen ids-option screen-name ip] | Identify and drop any packet with incorrectly formatted IPv4 options or IPv6 extension headers.
Incorrectly formatted IPv4 options or IPv6 extension headers can cause unpredictable issues, depending
on the IP stack implementation of routers and the target. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
bandwidth (DDoS) | bandwidth packets-per-second; | For MX Series routers, T4000 routers, and EX9200 switches:
[edit system ddos-protection protocols protocol-group (aggregate | packet-type)]
For ACX Series routers, PTX Series routers and QFX Series switches:
[edit system ddos-protection protocols (DDoS) protocol-group (aggregate | packet-type)] | Configure the DDoS bandwidth rate limit; that is, the maximum traffic rate (packets per second) allowed
by the specified policer. When the value is exceeded, a violation is declared. | [
{
"name": "packets-per-second",
"desc": "Number of packets per second that are allowed by the aggregate or packet-type"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Control Plane DDoS Protection Aggregate or Individual Packet Type Policers"
] |
bandwidth (Fast Reroute, Signaled, and Multiclass LSPs) | bandwidth bps {
ct0 bps;
ct1 bps;
ct2 bps;
ct3 bps;
} | [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 fast-
reroute],
[edit logical-systems logical-system-name protocols mpls label-switched... | When configuring an LSP, specify the traffic rate associated with the LSP.
When configuring fast reroute, allocate bandwidth for the reroute path. By default, no bandwidth is
reserved for the rerouted path. The fast reroute bandwidth does not need to be identical to that
allocated for the LSP itself.
When configuring a... | [
{
"name": "bps",
"desc": "Bandwidth, in bits per second. You can specify this as an integer value. You can also use the"
},
{
"name": "ctnumber bps",
"desc": "Bandwidth for the specified class type, in bits per second. You can specify this as an integer"
}
] | 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.
Statement introduced in Junos OS Release 12.3X50 for the QFX Series. | [
"Configuring Fast Reroute",
"Configuring the Bandwidth Value for LSPs",
"Configuring Traffic-Engineered LSPs",
"Configuring Class-Type Bandwidth Constraints for Multiclass LSPs"
] |
bandwidth (Inline Services) | bandwidth bandwidth-value; | [edit chassis fpc slot-number pic number inline-services] | Configure the amount of bandwidth in gigabits per second reserved on each Packet Forwarding Engine
for tunnel traffic using inline services. Configuring the bandwidth creates a virtual tunnel interface that is
represented as si-<fpc/pic/port>.
Starting in Junos OS Release 16.2, you are not longer required to explicitly... | [
{
"name": "bandwidth-value",
"desc": "Amount of bandwidth in Gbps to reserve for tunnel traffic using inline services. You can"
},
{
"name": "configure bandwidth values can be as follows:",
"desc": ""
},
{
"name": "1g",
"desc": "10g through 100g in 10 Gbps increments: 10g, 20g, 30g, ... | 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.
20g, 30g, and 40g options added in Junos OS Release 14.1R3.
100g option added in Junos OS Release 18.2R1 on MX Series Routers with MPC7E, MPC8E, and MPC9E
line cards.
50g, 60g, 70g, 80g, 90g, 200g, 300g and 400g options added in Junos OS Release 18.3R1. | [
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces"
] |
bandwidth (Interfaces) | bandwidth rate; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Configure the bandwidth value for an interface. This statement is valid for all logical interface types
except multilink and aggregated interfaces.
NOTE: We recommend that you be careful when setting this value. Any interface
bandwidth value that you configure using the bandwidth statement affects how the
interface cos... | [
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps) or cells per second (cps). You can specify a value in bits per"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Interface Bandwidth"
] |
bandwidth (Interfaces) | bandwidth bandwidth; | [edit interfaces interface-name radio-router] | This option controls the weight of the current (vs. maximum) data rate (value 0–100). | [] | 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. | [
"PPPoE-Based Radio-to-Router Protocols Overview"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.