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 |
|---|---|---|---|---|---|---|---|
retry-count (Chassis Cluster) | retry-count number; | [edit chassis cluster redundancy-group group-number ip-monitoring] | Specify the number of consecutive ping attempts that must fail before an IP address monitored by the
redundancy group is declared unreachable in IP address monitoring.
In the IP address monitoring, you can configure redundancy groups to monitor upstream resources by
pinging specific IP addresses that are reachable thro... | [
{
"name": "number",
"desc": "Number of consecutive ping attempt failures before a monitored IP address is declared"
}
] | 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. | [] |
retry-count (Event Policy) | retry-count number retry-interval seconds; | [edit event-options policy policy-name then event-script filename destination destination-name],
[edit event-options policy policy-name then execute-commands destination destination-name],
[edit event-options policy policy-name then upload filename (filename | committed) destination
destination-name] | Configure an event policy to retry a file upload operation if the first attempt fails.
Default
If you do not include this statement, the file upload operation is attempted one time only. | [
{
"name": "number",
"desc": "Number of retries."
},
{
"name": "retry-interval seconds",
"desc": "Length of time to wait between retries."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 8.4. | [
"Configure an Event Policy to Retry the File Upload Action"
] |
retry-count (FPC Error Condition) | retry-count number; | [edit chassis cfeb slot-number],
[edit chassis cluster redundancy-group group-number ip-monitoring],
[edit chassis feb slot-number],
[edit chassis fpc slot-number sanity-poll],
[edit chassis lcc number fpc number sanity-poll] | Number of times sanity polling periodically checks for an error condition in the FPC. | [
{
"name": "number",
"desc": "Number of times sanity polling is allowed to check for an error condition."
}
] | 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. | [
"Configure Sanity Polling"
] |
retry-count (Security Log) | retry-count retry-count; | [edit logical-systems name security log],
[edit logical-systems name tenants name security log],
[edit security log],
[edit tenants name security log] | Specify the maximum number attempts to send accounting message to the RADIUS accounting server in
case of a transmission failure. | [
{
"name": "retry-count",
"desc": "The number of times you attempt to send accounting messages to the RADIUS"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.2R1. | [] |
retry-count (SNMP) | retry-count number; | [edit snmp v3 target-address target-address-name] | Configure the retry count for SNMP informs. | [
{
"name": "number",
"desc": "Maximum number of times the inform is transmitted if no acknowledgment is received. If no"
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [] |
retry-delay | retry-delay seconds; | [edit services flow-collector] | Configure the amount of time the flow collector interface waits between retry attempts. | [
{
"name": "seconds",
"desc": "Amount of time between transfer retry attempts."
}
] | 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 Retry Attempts"
] |
retry-interval (Chassis Cluster) | retry-interval interval; | [edit chassis cluster redundancy-group group-number ip-monitoring ] | Specify the ping packet send frequency (in seconds) for each IP address monitored by the redundancy
group.
In the IP address monitoring, you can configure redundancy groups to monitor upstream resources by
pinging specific IP addresses that are reachable through redundant Ethernet interfaces on either node in
a cluster... | [
{
"name": "interval",
"desc": "Pause time (in seconds) between each ping sent to each IP address monitored by the"
}
] | 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. | [] |
retry-interval | retry-interval seconds; | [edit security pki ca-profile ca-profile-name enrollment] | (Adaptive services interfaces only) Specify the amount of time the router should wait between
enrollment retries. | [
{
"name": "seconds",
"desc": "Time interval, in seconds, between enrollment retries."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [] |
retry-limit (Protocols Link Management) | retry-limit number; | [edit logical-systems logical-system-name protocols link-management peer peer-name lmp-protocol],
[edit protocols link-management peer peer-name lmp-protocol] | Specify how many times the Link Management Protocol (LMP) sends Config and LinkSummary messages
on the LMP control channel without receiving an appropriate acknowledgment before it logs a message
and restarts the LMP control channel configuration process. | [
{
"name": "number",
"desc": "Maximum number of times messages are sent without receiving an acknowledgment."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Controlling Message Exchange for LMP Control Channels"
] |
retry-limit | retry-limit number; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name] | Maximum number of times the ingress router tries to establish the primary path. This counter is reset
each time a primary path is created successfully. When the limit is exceeded, no more connection
attempts are made. Intervention is then required to restart the connection. | [
{
"name": "number",
"desc": "Maximum number of tries to establish the primary path."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Connection Between Ingress and Egress Routers"
] |
retry-options | retry-options {
backoff-factor seconds;
backoff-threshold number;
lockout-period minutesNice,
maximum-time seconds;
minimum-time seconds;
tries-before-disconnect number;
} | [edit system login] | Limit the number of times a user can attempt to log in through SSH or Telnet before being disconnected. | [
{
"name": "backoff-factor",
"desc": ""
},
{
"name": "seconds",
"desc": "Length of delay in seconds after each failed login attempt. The length of delay increases by this value for each subsequent failed login attempt after the value specified in the backoff-threshold option. Default: 5 Range: ... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0.
maximum-time option introduced in Junos OS Release 9.6.
lockout-period option introduced in Junos OS Release 11.2. | [
"Limiting the Number of User Login Attempts for SSH and Telnet Sessions"
] |
retry-timer | retry-timer seconds; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name] | Amount of time the ingress router waits between attempts to establish the primary path. | [
{
"name": "seconds",
"desc": "Amount of time between attempts to connect to the primary path."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Connection Between Ingress and Egress Routers"
] |
reverse | reverse {
ssh {
port port;
}
telnet {
port port;
}
} | [edit system services] | Allow connections to device connected to the AUX port. Available for SRX series devices only. | [] | flow-tap—To view this statement in the configuration.
flow-tap-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [] |
reverse-oif-mapping | reverse-oif-mapping {
no-qos-adjust;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast interface interface-name],
[edit logical-systems logical-system-name routing-options multicast interface interface-name],
[edit routing-instances routing-instance-name routing-options multicast interface interfa... | Enable the routing device to identify a subscriber VLAN or interface based on an IGMP or MLD request
it receives over the multicast VLAN.
The remaining statement is explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
The no-qos-adjust statement added in Junos OS Release 9.5.
The no-qos-adjust statement introduced in Junos OS Release 9.5 for EX Series switches. | [
"Example: Configuring Multicast with Subscriber VLANs"
] |
reverse-route-packet-mode-vr | reverse-route-packet-mode-vr; | [edit security flow advanced-options] | When processing a server to client traffic, if the route is changed, the server to client traffic is rerouted.
The traffic is rerouted using the virtual router from the first incoming session interface. The command
allows reverse route lookup with packet mode using virtual router. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Understanding Packet-Based Processing"
] |
reverse-tcp-mss | reverse-tcp-mss mss-value; | [edit security policies from-zone zone-name to-zone zone-name
policy policy-name then permit tcp-options] | Configure the TCP maximum segment size (MSS) for packets that match a specific policy and travel in
the reverse direction of a session. The value you configure replaces the TCP MSS value when the value
in the packet is higher than the one you specify.
The reverse-tcp-mss value per policy takes precedence over a global ... | [] | 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-D20. | [
"tcp-mss (Security Flow)",
"syn-flood-protection-mode"
] |
revert-interval (Access LDAP) | revert-interval seconds; | [edit access ldap-options],
[edit access profile profile-name ldap-options] | Specify the amount of time that elapses before the primary server is contacted if a backup server is
being used. | [
{
"name": "seconds",
"desc": "Number of seconds that elapse before the primary server is contacted."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [
"Example: Configuring RADIUS and LDAP User Authentication"
] |
revert-interval (Access RADIUS) | revert-interval seconds; | [edit access radius-options] | Specify the amount of time that elapses before the primary server is contacted if a backup server is
being used. | [
{
"name": "seconds",
"desc": "Number of seconds that elapse before the primary server is contacted."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [] |
revert-interval (Access) | revert-interval interval; | [edit access profile profile-name radius options],
[edit access radius-options] | Configure the amount of time the router or switch waits after a server has become unreachable. The
router or switch rechecks the connection to the server when the specified interval expires. If the server
is then reachable, it is used in accordance with the order of the server list. | [
{
"name": "interval",
"desc": "Amount of time to wait."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"RADIUS Servers and Parameters for Subscriber Access",
"RADIUS Authentication and Accounting Basic Configuration"
] |
revert-interval (RADIUS Server) | revert-interval seconds; | [edit access radius servers name] | Configure the amount of time that must pass after a RADIUS server is first marked dead until it is
marked as alive by Junos OS. When Junos OS marks the RADIUS server as alive, it can again send
requests to the RADIUS server. | [
{
"name": "seconds",
"desc": "Number of seconds after which a dead server is marked active. Range: 0 through 4,294,967,295 Default: 300 seconds"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring RADIUS Servers",
"Understanding Network Elements",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules"
] |
revert-time (Protocols Layer 2 Circuits) | revert-time seconds maximum seconds; | [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 address],
[edit protocols l2circuit neighbor address interface interface-name],
[edit routing-instances ro... | Specify a revert time for redundant Layer 2 circuits and VPLS pseudowires. When you have configured
redundant pseudowires for Layer 2 circuits or VPLS, traffic is switched to the backup connection in the
event that the primary connection fails. If you configure a revert time, when the configured time expires
traffic is... | [
{
"name": "seconds",
"desc": "Revert time in seconds."
},
{
"name": "maximum seconds",
"desc": "Number of seconds to delay path restoration after the revert-time delay."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2.
maximum option introduced in Junos OS Release 13.2.
The range and maximum range for revert-time increased from 600 to 3600 and 1200 to 7200 seconds
in Junos OS Release 23.1R1. | [
"Configuring Redundant Pseudowires for Layer 2 Circuits and VPLS"
] |
revert-timer | revert-timer seconds; | [edit logical-systems logical-system-name protocols mpls],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls],
[edit protocols mpls label-switched-path lsp-name] | Specify the amount of time (in seconds) that an LSP must wait before traffic reverts to a primary path. If
during this time the primary path experiences any connectivity problem or stability problem, the timer is
restarted.
If you have configured BFD on the LSP, the Junos OS waits until the BFD session is restored befo... | [
{
"name": "seconds",
"desc": "Time in seconds."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
BFD behavior modified in Junos OS Release 9.0. | [
"Configuring the Revert Timer for LSPs"
] |
revertive | revertive; | [edit interfaces aeX aggregated-ether-options lacp link-protection] | Enable the ability to switch to a better priority link (if one is available).
NOTE: By default, LACP link protection is revertive. However, you can use this
statement to define a specific aggregated Ethernet interface as revertive to override a
global non-revertive statement specified at the [edit chassis] hierarchy le... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Configuring LACP Link Protection of Aggregated Ethernet Interfaces for Switches"
] |
revision-level | revision-level revision-level; | [edit logical-systems logical-system-name protocols mstp],
[edit logical-systems logical-system-name routing-instances routing-instance-name
protocols mstp],
[edit protocols mstp],
[edit routing-instances routing-instance-name protocols mstp] | For Multiple Spanning Tree Protocol (MSTP), set the revision number of the MSTP configuration. | [
{
"name": "revision-level",
"desc": "Configure the revision number of the MSTP region configuration."
}
] | 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.
Support for logical systems added in Junos OS Release 9.6. | [
"Understanding MSTP",
"Configuring Multiple Spanning Tree Protocol",
"Example: Configuring Network Regions for VLANs with MSTP on Switches"
] |
revocation-check (Security PKI) | revocation-check {
crl:
disable;
ocsp:
use-crl;
use-ocsp;
} | [edit security pki ca-profile ca-profile-name] | Specify the method the device uses to verify the revocation status of digital certificates. | [
{
"name": "crl",
"desc": "Only certificate revocation list (CRL) is supported. A CRL is a time-stamped list identifying revoked certificates, which is signed by a CA and made available to the participating IPsec peers on a regular periodic basis. You should also specify the location (URL) to retrieve the CR... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 8.5. Support for ocsp, use-crl, and use-ocsp options added in
Junos OS Release 12.1X46-D20. | [
"Basic Elements of PKI in Junos OS"
] |
revocation-check | revocation-check {
disable;
crl {
refresh-interval number-of-hours;
url {
url-name;
}
}
} | [edit security pki ca-profile ca-profile-name] | Specify the method to verify revocation status of digital certificates for J Series Services Routers and
Adaptive Services (AS) and MultiServices PICs installed in M Series and T Series routers. | [
{
"name": "disable",
"desc": "Disable verification of status of digital certificates. Use disable temporarily in cases where a"
},
{
"name": "crl",
"desc": "Only certificate revocation list (CRL) is supported. A CRL is a time-stamped list identifying revoked"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Enroll a Certificate"
] |
rewrite-rules (CoS Host Outbound Traffic) | rewrite-rules; | [edit class-of-service host-outbound-traffic ieee-802.1] | Apply the IEEE 802.1p rewrite rules associated with the egress logical interface to the IEEE 802.1p PCP
field for all host outbound traffic on that interface.
NOTE: Enabling IEEE 802.1p rewrite rules for host outbound traffic on a DPC without
creating any corresponding IEEE 802.1p rewrite rules on a logical interface ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Applying Egress Interface Rewrite Rules to the IEEE 802.1p Field for All Host Outbound Traffic on",
"the Interface",
"Rewriting Packet Headers to Ensure Forwarding Behavior",
"Configuring Rewrite Rules"
] |
rewrite-rules (Definition) | rewrite-rules {
type rewrite-name {
import (rewrite-name | default);
forwarding-class class-name {
loss-priority level code-point [ aliases ] [ bit-patterns ];
}
}
} | [edit class-of-service] | Configure rewrite rules that map traffic to code points when traffic exits the system. You then apply the
rewrite rules to egress interfaces. | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping."
},
{
"name": "type",
"desc": "Traffic type."
}
] | 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.
ieee-802.1ad option introduced in Junos OS Release 9.2. | [
"Configuring Rewrite Rules",
"Understanding CoS MPLS EXP Classifiers and Rewrite Rules",
"Configuring Rewrite Rules for MPLS EXP Classifiers",
"Defining CoS Rewrite Rules",
"Understanding CoS Rewrite Rules",
"Understanding CoS MPLS EXP Classifiers and Rewrite Rules"
] |
rewrite-rules (Dynamic CoS Interfaces) | rewrite-rules {
dscp (rewrite-name | default);
dscp-ipv6 (rewrite-name | default);
ieee-802.1 (rewrite-name | default) vlan-tag (outer | outer-and-inner);
inet-precedence (rewrite-name | default);
}
} | [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-
number] | Associate a rewrite-rules configuration or default mapping with a specific interface in a dynamic profile. | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules]"
},
{
"name": "default",
"desc": "The default mapping."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"rewrite-rules"
] |
rewrite-rules (Interfaces) | rewrite-rules {
dscp (rewrite-name | default) protocol (inet-both | inet-outer | mpls);
dscp-ipv6 (rewrite-name | default) protocol mpls;
exp (rewrite-name | default) protocol protocol-types;
exp-push-push-push default;
exp-swap-push-push default;
ieee-802.1 (rewrite-name | default) vlan-tag (ou... | [edit class-of-service interfaces interface-name],
[edit class-of-service interfaces interface-name unit logical-unit-number] | Associate a rewrite-rules configuration or default mapping with a specific interface.
Integrated Bridging and Routing (IRB) interfaces are used to tie together Layer 2 switched and Layer 3
routed domains on MX routers. MX routers support classifiers and rewrite rules on the IRB interface at
the [edit class-of-service ... | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules]"
},
{
"name": "default",
"desc": "The default mapping."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Rewrite Rules",
"Applying Rewrite Rules to Output Logical Interfaces"
] |
rewrite-value (Fibre Channel Interfaces) | rewrite-value {
input {
ieee-802.1{
code-point code-point-bits;
}
}
} | [edit class-of-service interfaces fibre-channel-interface-name] | Configure the IEEE 802.1p code point value (priority) for all traffic received from the Fibre Channel (FC)
network on the specified FC interface. Instead of using the default priority 3 (011) for FCoE traffic, the
priority is rewritten to the specified priority before being forwarded. This works in conjunction with
co... | [] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"Example: Configuring IEEE 802.1p Priority Remapping on an FCoE-FC Gateway",
"Understanding CoS IEEE 802.1p Priority Remapping on an FCoE-FC Gateway",
"Understanding CoS Classifiers"
] | |
rfc2544 | rfc2544 {
test-profile profile-name {
bandwidth bandwidth;
packet-size size;
step-percent percent;
test-type (throughput | latency | frame-loss | back-back-frames);
}
tests{
test-name test-name {
destination-ipv4-address address;
destination... | [edit services monitoring] | Configure the parameters for the RFC 2544-based benchmarking test to examine and analyze the
performance characteristics of a network interconnecting device. You must configure a test profile,
which specifies the type of test and the manner in which it must be performed, and associate the test
profile with a test name.... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 21.1R1.
Support for the destination-mac-address, direction, disable-signature-check, in-service, ip-swap, reflect-etype,
reflect-mode, service-type, source-mac-address, and udp-tcp-port-swap configuration statements introduced in
Junos OS Evolved 22.4R1.
Support for band... | [
"RFC 2544-Based Benchmarking Tests Overview"
] |
rfc2544-benchmarking | [edit services rpm] | Configure the parameters for the RFC 2544-based benchmarking test to examine and analyze the
performance characteristics of a network interconnecting device. You must configure a test profile for
the initiator (ACX routers only), which specifies the type of test and the manner in which it must be
performed, and associa... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X52. | [
"Configuring an RFC 2544-Based Benchmarking Test",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers"
] | |
rfc6514-compliant-safi129 (Protocols BGP) | rfc6514-compliant-safi129 | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor neighbor-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protoco... | Parse and send BGP VPN multicast traffic according to Subsequent Address Family Identifier (SAFI) 129,
as defined in RFC 6514 (that is, length, prefix). The Network Layer Reachability Information (NLRI)
format used for BGP VPN multicast in previous releases of Junos OS was SAFI 128, which was length,
label, prefix. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring BGP Neighbor Discovery Through RPM"
] |
rfc7775-compliance | rfc7775-compliance; | [edit logical-systems name protocols isis],
[edit logical-systems name routing-instances name protocols isis],
[edit logical-systems name tenants name routing-instances name protocols isis],
[edit protocols isis],
[edit routing-instances name protocols isis],
[edit tenants name routing-instances name protocols isis] | Enable this option for up/down bit and prefix attribute sub-tlv. When you enable this option, IS-IS
advertises Extended Reachability Prefix Attribute Flag Sub-TLV without policy configuration per RFC
7775. Enable this feature to use route preference rules defined in RFC 7775 for TLVs 135,235,236, and
237.
ISIS Route Pr... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.4R1. | [] |
rfc-compliant (NETCONF) | rfc-compliant; | [edit system services netconf] | Require that the NETCONF server enforce certain behaviors that are compliant with RFC 4741,
NETCONF Configuration Protocol, during NETCONF sessions.
When you configure the rfc-compliant statement:
•
The NETCONF server explicitly declares the NETCONF namespace in its replies and qualifies all
NETCONF tags with the nc pr... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring RFC-Compliant NETCONF Sessions"
] |
rib (General) | rib routing-table-name {
aggregate {
defaults {
... aggregate-options ...
}
route destination-prefix {
policy policy-name;
... aggregate-options ...
}
generate {
defaults {
generate-options;
}
... | [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] | Create a routing table.
Explicitly creating a routing table with routing-table-name is optional if you are not adding any static,
martian, aggregate, or generated routes to the routing table and if you also are creating a routing table
group.
NOTE: The IPv4 multicast routing table (inet.1) and the IPv6 multicast routin... | [
{
"name": "routing-table-name",
"desc": "Name of the routing table, in the following format: protocol [.identifier]."
}
] | 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.
policy-multipath statement introduced in Junos Release 19.1R1 for all platfroms. | [
"Example: Creating Routing Tables",
"Policy-Based Multipath Routes Overview"
] |
rib (Multitopology Routing) | rib routing-table-name {
static {
route destination-prefix {
next-hop;
}
static-options;
}
} | [edit logical-systems logical-system-name routing-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options] | Configure a static route to install routes in the routing table for a specific topology. | [
{
"name": "routing-table-name",
"desc": "Name of the routing table for a topology. Use the following format: logical-system-name/routing-instance-name:topology-name.protocol.identifier. Include the routing instance string only"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement support for multitopology routing introduced in Junos OS Release 9.0.
Statement introduced in Junos OS Release 9.0. | [
"Example: Removing the Class E Prefix on Martian Addresses",
"Example: Configuring IPv6 BGP Routes over IPv4 Transport",
"Enabling Layer 2 VPN and VPLS Signaling",
"Understanding Martian Addresses"
] |
rib (Protocols BGP) | rib (inet.3 | inet6.3) ; | [edit logical-systems logical-system-name protocols bgp family (inet | inet6) labeled-unicast],
[edit logical-systems logical-system-name protocols bgp group group-name family (inet | inet6)
labeled-unicast],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address
family (inet | inet... | You can allow both labeled and unlabeled routes to be exchanged in a single session. The labeled routes
are placed in the inet.3 or inet6.3 routing table, and both labeled and unlabeled unicast routes can be
sent or received by the router. | [
{
"name": "inet.3",
"desc": "Name of the routing table for IPv4."
},
{
"name": "inet6.3",
"desc": "Name of the routing table for IPv6."
}
] | 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 BGP Routes over IPv4 Transport",
"Enabling Layer 2 VPN and VPLS Signaling",
"Understanding Multiprotocol BGP"
] |
rib (Route Resolution) | rib routing-table-name {
import [ policy-names ];
resolution-ribs [ routing-table-names ];
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options resolution],
[edit logical-systems logical-system-name routing-options resolution],
[edit routing-instances routing-instance-name routing-options resolution],
[edit routing-options resolution] | Specify a routing table name for route resolution.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring Route Resolution on PE Routers"
] |
rib-export-strip (Policy Options) | rib-export-strip <cluster-list>; | [edit policy-options policy-statement name then] | Configure a policy to strip the BGP cluster list attribute from a cloned route. This policy is used in
conjuction with the [edit routing-options rib-exports] statement. | [
{
"name": "cluster-list",
"desc": "Strip the BGP cluster list attribute from a cloned route. The BGP originator id attribute is implicitly set to \"self\" when the cluster list attribute is removed."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1. | [] |
rib-exports (Routing Options) | rib-exports {
restart-timer; value in seconds;
rib-export-group {
policy;
to-rib;
}
traceoptions {
file;
flag;
}
} | [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": "restart-timer",
"desc": "Specify the time in seconds to support graceful restart. Default: 45 seconds"
},
{
"name": "rib-export-group",
"desc": "Specify the RIB-Export group name, and then configure additional statements to create and export routes."
},
{
"name": "to-rib",
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1.
rib-export-strip statement introduced in Junos OS Release 25.2R1. | [] |
rib-group (Protocols BGP) | rib-group group-name; | [edit logical-systems logical-system-name protocols bgp family inet (labeled-unicast | unicast |
multicast)],
[edit logical-systems logical-system-name protocols bgp group group-name family inet (labeled-
unicast | unicast | multicast)],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor... | Add unicast prefixes to unicast and multicast tables. | [
{
"name": "group-name",
"desc": "Name of the routing table group. The name must start with a letter and can include letters,"
}
] | 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: Exporting Specific Routes from One Routing Table Into Another Routing Table",
"Example: Populating a Routing Table Created by Virtual Router Configuration",
"Understanding Multiprotocol BGP"
] |
rib-group (Protocols DVMRP) | rib-group group-name; | [edit logical-systems logical-system-name protocols dvmrp],
[edit protocols dvmrp] | Associate a routing table group with DVMRP. | [
{
"name": "group-name",
"desc": "Name of the routing table group. The name must be one that you defined with the rib-groups statement at the [edit routing-options] hierarchy level."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | NOTE: Distance Vector Multicast Routing Protocol (DVMRP) was deprecated in Junos
OS Release 16.1. Although DVMRP commands continue to be available and configurable
in the CLI, they are no longer visible and are scheduled for removal in a subsequent
release.
Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring DVMRP"
] |
rib-group (Protocols IS-IS) | rib-group {
inet group-name;
inet6 group-name;
} | [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] | Install routes learned from IS-IS routing instances into routing tables in the IS-IS routing table group. You
can install IPv4 routes or IPv6 routes.
Support for IPv6 routing table groups in IS-IS enables IPv6 routes that are learned from IS-IS routing
instances to be installed into other routing tables defined in an I... | [
{
"name": "group-name",
"desc": "Name of the routing table group."
},
{
"name": "inet",
"desc": "Install IPv4 IS-IS routes."
},
{
"name": "inet6",
"desc": "Install IPv6 IS-IS routes."
}
] | 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: Exporting Specific Routes from One Routing Table Into Another Routing Table",
"Example: Populating a Routing Table Created by Virtual Router Configuration",
"Understanding Multiprotocol BGP"
] |
rib-group (Protocols MSDP) | rib-group group-name; | [edit logical-systems logical-system-name protocols msdp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
msdp],
[edit protocols msdp],
[edit routing-instances routing-instance-name protocols msdp] | Associate a routing table group with MSDP. | [
{
"name": "group-name",
"desc": "Name of the routing table group. The name must be one that you defined with the rib-groups statement at the [edit routing-options] hierarchy level."
}
] | 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 MSDP in a Routing Instance"
] |
rib-group (Protocols OSPF) | rib-group group-name; | [edit logical-systems logical-system-name protocols (ospf | ospf3)],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(ospf | ospf3)],
[edit logical-systems log... | Install routes learned from OSPF routing instances into routing tables in the OSPF routing table group. | [
{
"name": "group-name",
"desc": "Name of the routing table group."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for the realm statement introduced in Junos OS Release 9.2.
Support for the realm statement introduced in Junos OS Release 9.2 for EX Series switches. | [
"Example: Exporting Specific Routes from One Routing Table Into Another Routing Table",
"Example: Populating a Routing Table Created by Virtual Router Configuration",
"Understanding Multiprotocol BGP",
"interface-routes",
"rib-group"
] |
rib-group (Protocols PIM) | rib-group {
inet group-name;
inet6 group-name;
} | [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim] | Associate a routing table group with PIM. | [
{
"name": "table-name",
"desc": "Name of the routing table. The name must be one that you defined with the rib-groups"
}
] | 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 a Dedicated PIM RPF Routing Table"
] |
rib-group (Protocols RIP) | rib-group group-name; | [edit logical-systems logical-system-name protocols rip],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip],
[edit protocols rip],
[edit routing-instances routing-instance-name protocols rip] | Install RIP routes into multiple routing tables by configuring a routing table group. | [
{
"name": "group-name",
"desc": "Name of the routing table group."
}
] | 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: Redistributing Routes Between Two RIP Instances"
] |
rib-group (Routing Options) | rib-group group-name; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options interface-routes],
[edit logical-systems logical-system-name routing-options interface-routes],
[edit logical-systems logical-system-name routing-options rib routing-table-name static],
[edit logical-systems logical-syste... | Configure which routing table groups interface routes are imported into. | [
{
"name": "group-name",
"desc": "Name of the routing table group. The name must start with a letter and can include letters,"
}
] | 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: Populating a Routing Table Created by Virtual Router Configuration",
"Example: Exporting Specific Routes from One Routing Table Into Another Routing Table"
] |
rib-group (Source Packet Routing) | rib-group {
ipv4 rib-group-name;
ipv4-color rib-group-name;
ipv6 rib-group-name;
ipv6-color rib-group-name;
tag rib-group-name;
} | [edit logical-systems name protocols source-packet-routing],
[edit protocols source-packet-routing] | Enable rib-group import policies on segment routing traffic-engineering (SR-TE). | [
{
"name": "rib-group-name",
"desc": "Rib-group import policy."
},
{
"name": "ipv4 | ipv6",
"desc": "Import policy to be applied on IPv4 or IPv6 uncolored route, respectively."
},
{
"name": "ipv4-color | ipv6-color",
"desc": "Import policy to be applied on IPv4 or IPv6 colored route, ... | routing | Statement introduced in Junos OS Release 20.4R1. | [
"Static Segment Routing Label Switched Path"
] |
rib-groups | rib-groups {
group-name {
export-rib group-name;
import-policy [ policy-names ];
import-rib [ group-names ];
}
} | [edit logical-systems logical-system-name routing-options],
[edit routing-options] | Group one or more routing tables to form a routing table group. A routing protocol can import routes
into all the routing tables in the group and can export routes from a single routing table.
Each routing table group must contain one or more routing tables that Junos OS uses when importing
routes (specified in the imp... | [
{
"name": "group-name",
"desc": "Name of the routing table group. The name must start with a letter and can include letters,"
}
] | 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: Exporting Specific Routes from One Routing Table Into Another Routing Table"
] |
rib-list | rib-list name {
rib-list-item name;
} | [edit logical-systems name policy-options],
[edit policy-options] | Define a set of RIBs and assign a name to the list. You can even use wildcards as a list item. | [
{
"name": "name",
"desc": "Assign a name to the RIB list."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.4 R1 | [] |
rib-service (programmable-rpd) | rib-service {
dynamic-next-hop-interface (enable | disable);
} | [edit routing-options programmable-rpd] | Configure programmable routing protocol process (prpd) options that apply only to the RIB Service API. | [
{
"name": "dynamic-next-hop-",
"desc": ""
},
{
"name": "interface",
"desc": ""
},
{
"name": "(enable |",
"desc": ""
},
{
"name": "disable)",
"desc": "Disable or enable dynamic next-hop interface binding. When enabled, programmed RIB routes react to Up, Down, Add, and Dele... | routing | Statement introduced in Junos OS Release 20.2R1. | [
"Understanding Programmable Flexible VXLAN Tunnels"
] |
rib-sharding | rib-sharding {
number-of-shards;
} | [edit system processes routing bgp] | Enable BGP RIB sharding. BGP RIB sharding is to split the BGP process across routes. Different routes
are hashed into different threads to achieve concurrency. BGP RIB sharding splits a unified BGP RIB into
several sub RIBs and each sub RIB handles a subset of BGP routes. Each sub RIB is served by a separate
RPD thread... | [
{
"name": "number of shards",
"desc": "the number of sharding threads created. If you configure rib-sharding on a routing"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4R1.
Support for NSR with sharding introduced in Junos OS Release 22.2.
BGP sharding supports IPv4, IPv6, L3VPN and BGP-LU from Junos OS Release 20.4R1. | [] |
rift | rift {
capabilities;
default-prefixes;
default-prefixes-advertisement;
export;
external-preference external-preference;
interface interface-name;
level;
lie-receive-address;
lie-receive-port port-number;
name name;
node-id (node-id | auto);
overload timeout seconds;
p... | [edit protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and rest... | [
{
"name": "capabilities",
"desc": "Enable the RIFT capability of reducing flooding globally. See \"capabilities\" on page 3406 for more information."
},
{
"name": "deafult-prefixes",
"desc": "Explicitly specify default prefixes generated in southbound direction. See \"default-prefixes\" on page ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4R1. | [
"Understanding Junos Implementation of Routing in Fat Tree (RIFT) Protocol"
] |
ring-id | ring-id number; | [edit protocols protection-group ethernet-ring ring-name] | Specify the ring ID. | [
{
"name": "number",
"desc": "Ring ID number."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Ethernet Ring Protection Switching Overview",
"Configuring Ethernet Ring Protection Switching on Switches (CLI Procedure)"
] |
ring-protection-link-end | ring-protection-link-end; | [edit protocols protection-group ethernet-ring ring-name (east-interface | west-interface)] | Specify that the port is one side of a ring protection link (RPL) by setting the RPL end flag. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Ethernet Ring Protection Switching Overview",
"Example: Configuring Ethernet Ring Protection Switching on EX Series Switches",
"Example: Configuring Ethernet Ring Protection Switching on QFX Series and EX Series Switches",
"Supporting ELS",
"Configuring Ethernet Ring Protection Switching on Switches (CLI P... |
ring-protection-link-owner | ring-protection-link-owner; | [edit protocols protection-group ethernet-ring ring-name] | Specify the ring protection link (RPL) owner flag in the Ethernet protection ring. Include this statement
only once for each ring (only one node can function as the RPL owner). | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Ethernet Ring Protection Switching Overview",
"Example: Configuring Ethernet Ring Protection Switching on EX Series Switches",
"Example: Configuring Ethernet Ring Protection Switching on QFX Series and EX Series Switches",
"Supporting ELS"
] |
riot-loopback | riot-loopback; | [edit vlans name vxlan] | Assign a VLAN that enables routing in and out of VXLAN tunnels (RIOT) for symmetric EVPN Type 2
and Type 5 routing.
Some Juniper switching platforms don't have native VXLAN routing hardware support for Layer 3
VXLAN gateway functions. Instead, supporting switches can use an intermediary loopback port in a
two-pass proc... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced for EVPN Type 5 routing in Junos OS Release 21.3R1.
Support added for symmetric EVPN Type 2 routing in Junos OS Release 21.4R1. | [
"Using a RIOT Loopback Port to Route Traffic in an EVPN Network",
"Symmetric Integrated Routing and Bridging with EVPN Type 2 Routes in EVPN-VXLAN Fabrics"
] |
rip | rip {...} | [edit logical-systems logical-system-name protocols],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit protocols],
[edit routing-instances routing-instance-name protocols] | Enable RIP routing on the routing device.
Default
RIP is disabled on the routing device. | [] | 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 RIP"
] |
ripng | ripng {...} | [edit logical-systems logical-system-name protocols],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit protocols],
[edit routing-instances routing-instance-name protocols] | Enable RIPng routing on the routing device.
Default
RIPng is disabled on the routing device. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for routing instances introduced in Junos OS Release 9.0. | [] |
rising-event-index | rising-event-index index; | [edit snmp rmon alarm index] | Set the index of the event entry that is used when a rising alarm threshold is exceeded. The rising-event
index is specified when you configure an SNMP RMON alarm. If this value is zero, no event is triggered. | [
{
"name": "index",
"desc": "Index of the event entry that is used when a rising threshold is crossed."
}
] | 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. | [
"Remote Nework Monitoring (RMON)"
] |
rising-threshold (Health Monitor) | rising-threshold percentage; | [edit snmp health-monitor],
[edit snmp health-monitor idp] | Set the upper threshold for the monitored object when you configure a health monitor alarm. By setting
a rising and a falling threshold for a monitored object, you can be alerted whenever the value of the
variable falls outside the allowable operational range. | [
{
"name": "percentage",
"desc": "The lower threshold for the alarm entry."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0. | [
"Configure Health Monitoring on Devices Running Junos OS"
] |
rising-threshold (RMON) | rising-threshold integer; | [edit snmp rmon alarm index] | Set the upper threshold for the sampled variable (monitored object) when you configure an SNMP
RMON alarm. By setting a rising and a falling threshold for a variable, you can be alerted whenever the
value of the variable falls outside the allowable operational range. | [
{
"name": "integer",
"desc": "The lower threshold for the alarm entry."
}
] | 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. | [
"Remote Nework Monitoring (RMON)"
] |
rmon | rmon {
alarm index {
description (RMON) description;
falling-event-index index;
falling-threshold integer;
falling-threshold-interval seconds;
interval seconds;
request-type;
rising-event-index index;
rising-threshold integer;
sample-type (abso... | [edit snmp] | Provide comprehensive network fault diagnosis, planning, and performance tuning information. RMON
delivers this information in nine groups of monitoring elements, each providing specific sets of data to
meet common network monitoring requirements. Each group is optional, so that vendors do not need to
support all the g... | [] | snmp—To view this statement in the configuration.
snmp–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"RMON MIB Event, Alarm, Log, and History Control Tables",
"RMON Overview",
"Junos OS Network Management Configuration Guide"
] |
rng | rng [dyce | fortuna | hmac-drbg]; | [edit system] | Configure a system cryptographically secure pseudo-random number generator (CSPRNG). By default,
rng is not configured.
NOTE:
•
Only root users can configure rng options.
•
A device reboot is required for the change to take effect.
•
In FIPS mode, HMAC-DRBG will be the only active RNG available.
Default
Federal Infor... | [
{
"name": "fortuna",
"desc": "Configure the fortuna CSPRNG."
},
{
"name": "hmac-drbg",
"desc": "Configure the HMAC DRBG CSPRNG."
},
{
"name": "dyce",
"desc": "Configure the Da Yan Concentrator and Extender of Random Data (DYCE) CSPRNG."
}
] | system-To view this statement in the configuration. | [] | |
roaming-mode | roaming-mode (home-only | automatic) | [edit interfaces interface-name cellular-options] | Specify whether the 3G wireless modem interface can access networks other than the home network. | [
{
"name": "home-only",
"desc": "No roaming is allowed."
},
{
"name": "automatic",
"desc": "Allows access to networks other than the home network. This 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 9.5. | [
"Understanding Ethernet Interfaces"
] |
robust-count (IGMP Snooping) | robust-count number; | [edit bridge-domains bridge-domain-name protocols igmp-snooping interface interface-name],
[edit bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id interface interface-
name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-
snooping interface interface... | Configure the number of queries a device sends before removing a multicast group from the multicast
forwarding table. We recommend that the robust count be set to the same value on all multicast routers
and switches in the VLAN.
This option provides fine-tuning to allow for expected packet loss on a subnet. You can wai... | [
{
"name": "number",
"desc": "Number of intervals the switch waits before timing out a multicast group."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Example: Configuring IGMP Snooping",
"Example: Configuring IGMP Snooping on SRX Series Devices"
] |
robust-count (MLD Snooping) | robust-count number; | [edit protocols mld-snooping vlan (all | vlan-name)]
[edit routing-instances instance-name protocols mld-snooping vlan vlan-name] | Configure the number of queries the switch sends before removing a multicast group from the multicast
forwarding table. We recommend that the robust count be set to the same value on all multicast routers
and switches in the VLAN.
Default
The default is the value of the robust-count statement configured for MLD. The de... | [
{
"name": "number",
"desc": "Number of queries the switch sends before timing out a multicast group."
}
] | 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.
Support at the [edit routing-instances instance-name protocols mld-snooping vlan vlan-name] hierarchy level
introduced in Junos OS Release 13.3 for EX Series switches. | [
"Example: Configuring MLD Snooping on SRX Series Devices",
"Configuring MLD Snooping on an EX Series Switch VLAN (CLI Procedure)",
"Understanding MLD Snooping"
] |
robust-count (Protocols IGMP AMT) | robust-count number; | [edit logical-systems logical-system-name protocols igmp amt relay defaults],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols igmp
amt relay defaults],
[edit protocols igmp amt relay defaults],
[edit routing-instances routing-instance-name protocols igmp amt relay defaults] | Configure the expected IGMP packet loss on an Automatic Multicast Tunneling (AMT) tunnel. If a tunnel
is expected to have packet loss, increase the robust count. | [
{
"name": "number",
"desc": "Number of packets that can be lost before the AMT protocol deletes the multicast state."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Default IGMP Parameters for AMT Interfaces"
] |
robust-count (Protocols IGMP) | robust-count number; | [edit logical-systems logical-system-name protocols igmp],
[edit protocols igmp] | Tune the expected packet loss on a subnet. This factor is used to calculate the group member interval,
other querier present interval, and last-member query count. | [
{
"name": "number",
"desc": "Robustness variable."
}
] | 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. | [
"Modifying the IGMP Robustness Variable"
] |
robust-count (Protocols MLD) | robust-count number; | [edit logical-systems logical-system-name protocols mld],
[edit protocols mld] | Tune for the expected packet loss on a subnet. | [
{
"name": "number",
"desc": "Time interval. This interval must be less than the interval between general host-query"
}
] | 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: Modifying the MLD Robustness Variable"
] |
robustness-count | robustness-count number; | [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 interf... | Configure the designated forwarder (DF) election robustness count for bidirectional PIM. When a DF
election Offer or Winner message fails to be received, the message is retransmitted. The robustness-
count statement sets the minimum number of DF election messages that must fail to be received for DF
election to fail. T... | [
{
"name": "number",
"desc": "Number of transmission attempts for DF election messages."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Understanding Bidirectional PIM",
"Example: Configuring Bidirectional PIM"
] |
role (MX Series Virtual Chassis) | role (routing-engine | line-card); | [edit virtual-chassis member member-id] | As part of the preprovisioned configuration for an MX Series Virtual Chassis, assign the role to be
performed by each member router in the Virtual Chassis. The preprovisioned configuration permanently
associates the member ID and role with the member router’s chassis serial number. | [
{
"name": "routing-engine",
"desc": "Enable the member router to function as the primary router or backup router of the"
},
{
"name": "line-card",
"desc": "Explicitly configuring a member router with the line-card role is not supported in the current"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Preprovisioned Member Information for a Virtual Chassis",
"Example: Configuring Interchassis Redundancy for MX Series 5G Universal Routing Platforms Using a",
"Virtual Chassis",
"Virtual Chassis Components Overview",
"Global Roles and Local Roles in a Virtual Chassis",
"Split Detection Behavi... |
role (Protocols OpenFlow) | role equal; | [edit protocols openflow switch switch-name controller] | Specify the role of each OpenFlow controller when configuring more than one controller for a virtual
switch. A single controller configuration automatically puts the controller in active mode. In active mode,
the virtual switch automatically initiates a connection to the controller. | [
{
"name": "equal",
"desc": "Configure the controller as the active controller in a single controller configuration."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Understanding Support for OpenFlow on Devices Running Junos OS"
] |
role | role (line-card | routing-engine); | [edit virtual-chassis member member-id] | Specify the roles of the members of the Virtual Chassis or a Virtual Chassis Fabric (VCF) in a
preprovisioned Virtual Chassis. For a mixed Virtual Chassis or VCF, see Understanding Mixed EX Series
and QFX Series Virtual Chassis or Understanding Mixed Virtual Chassis Fabric for any recommendations
or requirements for as... | [
{
"name": "line-card",
"desc": "Enables the member to be eligible to function only in the linecard role. Any member of the"
},
{
"name": "routing-engine",
"desc": "Enables the member to function as a primary or backup Routing Engine of the Virtual"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Autoprovisioning a Virtual Chassis Fabric",
"Preprovisioning a Virtual Chassis Fabric",
"Configuring an EX2300, EX3400, or EX4300 Virtual Chassis",
"Configuring EX4600 Switches in a Mixed or Non-Mixed Virtual Chassis",
"Configuring an EX9200 Virtual Chassis",
"Configuring an EX4650 or a QFX Series Virtua... |
rollback | rollback <number | rescue | revision revision-string> | Return to a previously committed configuration. The software saves the last 50 committed
configurations, including the rollback number, date, time, and name of the user who issued the commit
configuration command.
You can use rollback 0 to discarded any pending, uncommitted changes you want to clear from a
candidate co... | [
{
"name": "none",
"desc": "(Optional) Return to the most recently saved configuration."
},
{
"name": "number",
"desc": "(Optional) Configuration to return to. The range of values is from 0 through 49. The most recently saved configuration is number 0, and the oldest saved configuration is number... | rollback—To roll back to configurations other than the one most recently committed. | Command introduced before Junos OS Release 7.4.
Option revision introduced in Junos OS Release 20.4R1 and Junos OS Evolved Release 20.4R1. | [] | |
root-address | root-address root-address; | [edit logical-systems name routing-instances name provider-tunnel ldp-p2mp],
[edit logical-systems name tenants name routing-instances name provider-tunnel ldp-p2mp],
[edit routing-instances name provider-tunnel ldp-p2mp],
[edit tenants name routing-instances name provider-tunnel ldp-p2mp] | Configure the non-default loopback address for LDP point to multi-point provider tunnels.
NOTE: A maximum of 9000 ingress replication provider tunnels are supported with 3
root addresses.
A maximum of 3 VRFs can be mapped to 3 root addresses. | [] | Statement introduced in Junos OS Release 24.4R1. | [] | |
root-authentication | root-authentication {
encrypted-password "password";
no-public-keys;
ssh-ecdsa name {
from hosts;
}
ssh-ed25519 name {
from hosts;
}
ssh-rsa name {
from hosts;
}
} | [edit system] | Configure the authentication methods for the root-level user, whose username is root.
You can use the ssh-ecdsa, ssh-ed25519, or ssh-rsa statements to directly configure SSH ECDSA, ED25519,
or RSA keys to authenticate root logins. You can configure more than one public key for SSH
authentication of root logins as well ... | [
{
"name": "encrypted-password",
"desc": ""
},
{
"name": "\"password\"",
"desc": "Specify the MD5 or other password. You can specify only one encrypted password. You cannot configure a blank password using blank quotation marks (\" \"). You must configure a password whose number of characters ran... | 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. | [] |
root-ca (Services) | root-ca root-certificate; | [edit services ssl proxy profile profile-name]
[edit services ssl termination profile profile-name] | Root certificate for interdicting server certificates in proxy mode. This statement is supported on the
SRX1500, SRX5400, SRX5600, and SRX5800 devices and vSRX Virtual Firewall. | [
{
"name": "root-ca-name",
"desc": "Specify root certificate for interdicting server certificates in proxy mode."
}
] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. | [
"Configuring SSL Forward Proxy",
"Firewall User Authentication Overview"
] |
root-logical-system | root-logical-system; | [edit system security-profile] | Specify root-logical-system to bind the security profile to the primary logical system.
The primary administrator uses security profiles to provision logical systems with resources. The security
profile containing this statement must be bound to root-logical-system only.
Only the primary administrator can create securi... | [
{
"name": "none",
"desc": ""
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Understanding Logical Systems for SRX Series Services Gateways"
] |
root-login (JDM) | root-login (allow | deny ); | [edit system services ssh] | Control user access to the JDM through SSH.
Default
root-login allow is the default. | [
{
"name": "allow",
"desc": "Allow users to log in to the JDM as root through SSH."
},
{
"name": "deny",
"desc": "Disable users from logging in to the JDM as root through SSH. This configuration option is"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3. | [
"Setting Up Junos Node Slicing"
] |
root-streaming | root-streaming; | [edit security log],
[edit logical-systems name security log],
[edit tenants name security log] | The root-streaming option allows the user logical systems and tenant systems to generate the logs using
the root system's stream configuration. If you configure root-streaming option under user logical systems
and tenant systems in stream mode, all the logs of this user logical system and tenant systems will be
sent ou... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.3R1. | [] |
route (Access Internal) | route subscriber-ip-address {
next-hop next-hop;
qualified-next-hop underlying-interface {
mac-address address;
}
} | [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
access-internal],
[edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
rib routing-table-name access-internal],
[edit dynamic-profiles profile-name routing-options access-internal] | Dynamically configure parameters for an access-internal route. | [
{
"name": "subscriber-ip-address",
"desc": "Either the specific IP address you want to assign to the access-internal route or"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Support at the [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
access-internal] and [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-
options rib routing-table-name access-internal] hierarchy... | [
"Routes for DHCP and PPP Subscriber Access Networks"
] |
route (Access) | route prefix {
metric route-cost;
next-hop next-hop;
preference route-distance;
qualified-next-hop
tag route-tag;
tag2 route-tag2;
} | [edit routing-options access],
[edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
access],
[edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
rib routing-table-name access],
[edit dynamic-profiles profile-name routing-options access... | Dynamically configure the parameters for access routes. | [
{
"name": "prefix",
"desc": "Either the specific route prefix that you want to assign to the access route or one of the"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Support at the [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
access] and [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options rib
routing-table-name access] hierarchy levels introduced ... | [
"Routes for DHCP and PPP Subscriber Access Networks"
] |
route (Access-Internal) | route ip-prefix</prefix-length> {
next-hop next-hop;
qualified-next-hop next-hop;
} | [edit routing-options access-internal] | Configure the parameters for internal access routes. | [
{
"name": "ip-prefix</prefix-length>",
"desc": "Specific route prefix that you want to assign to the internal access route."
}
] | 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. | [] |
route (chassis) | route; | [edit chassis memory-enhanced] | Allocate more jtree memory for routing tables over firewall filters. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement added in Junos OS Release 10.4. | [
"Allocating More Memory for Routing Tables, Firewall Filters, and Layer 3 VPN Labels"
] |
route (Diameter Network Element) | route dne-route-name {
destination realm realm-name <host hostname>;
function function-name <partition partition-name>;
metric route-metric;
} | [edit diameter network-element element-name forwarding] | Define a route reachable through the Diameter network element by associating a metric with a
combination of destination and function partition. | [
{
"name": "dne-route-name",
"desc": "Route name defined for the Diameter network element."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configuring Diameter",
"Configuring Diameter Network Elements"
] |
route (Interfaces) | route prefix routing-instance instance-name priority-cost priority; | [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-
group group-id track],
[edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-
group group-id track],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit... | Enable route tracking for a Virtual Router Redundancy Protocol (VRRP) group. | [
{
"name": "prefix",
"desc": "Route to be tracked for this VRRP group."
},
{
"name": "priority-cost priority",
"desc": "The value subtracted from the configured VRRP priority when the tracked"
},
{
"name": "routing-instance instance-name",
"desc": "Routing instance in which the route ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Configuring a Route to Be Tracked for a VRRP Group"
] |
route-accounting | route-accounting; | [edit forwarding-options family inet6] | Enables the collection of transit IPv6 statistics at both the physical interface and logical interface levels
on third-generation FPCs (FPC3-PTX-U2 and FPC3-PTX-U3 on PTX5000 and FPC3-SFF-PTX-U0 and
FPC3-SFF-PTX-U1 on PTX3000), PTX1000, and PTX10008. Enable this statement prior to the route
being created.
Egress accoun... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Configuring IPv6 Accounting"
] |
route-active-on | route-active-on (node0 | node1); | [edit policy-options condition condition-name] | In chassis cluster configurations, the incoming traffic from the core network is sent to the interface that
exists on the current active node . For a route advertised by BGP, a policy is applied on BGP
configuration before exporting routes. An additional term in the policy match condition determines the
current active ... | [
{
"name": "node0",
"desc": "Route active on node 0"
},
{
"name": "node1",
"desc": "Route active on node 1"
}
] | 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 Conditional Route Advertising in a Chassis Cluster"
] |
route-attributes | route-attributes {
as-path {
export-action (allow | skip);
import-action (allow | skip);
}
community {
export-action (allow | skip);
import-action (allow | skip);
}
preference {
export-action (allow | skip);
import-action (allow | skip);
}
} | [edit routing-instances name protocols evpn ip-prefix-routes] | You can use the route-attributes import and export options to control which attributes to carry between
the IP and EVPN routes. Use the export option when generating EVPN routes from IP routes and the
import option when generating IP routes from EVPN routes. | [
{
"name": "as-path",
"desc": ""
},
{
"name": "export-action",
"desc": ""
},
{
"name": "allow",
"desc": "Inherit as-path from IP routes to EVPN routes."
},
{
"name": "skip",
"desc": "Do not inherit as-path from IP routes to EVPN routes."
},
{
"name": "import-action... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | [] | |
route-change-timeout | route-change-timeout seconds; | [edit security flow] | Specify the session timeout when a session is rerouted but there is a reroute failure (for example, the
new route uses a different egress zone from the previous route). | [
{
"name": "seconds",
"desc": "Amount of time before sessions are timed out."
}
] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 8.5. Support. | [
"Understanding Traffic Processing on Security Devices"
] |
route-distinguisher | route-distinguisher (as-number:id | ip-address:id); | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
l2vpn mesh-group mesh-group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
mesh-group... | Specify an identifier attached to a route that distinguishes to which VPN or virtual private LAN service
(VPLS) the route belongs. Each routing instance must have a unique route distinguisher (RD) associated
with it. The RD places bounds around a VPN so the device can use the same IP address prefixes in
different VPNs... | [
{
"name": "as-number:number",
"desc": "as-number is an assigned AS number, and number is any 2-byte or 4-byte value. The AS"
},
{
"name": "number:id",
"desc": "Number and identifer expressed in one of these formats: 16-bit number:32-bit identifier or"
},
{
"name": "ip-address:id",
"d... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support at [edit routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name] hierarchy
level introduced in Junos OS Release 11.2.
Support at [edit routing-instances routing-instance-name protocols l2vpn mesh-group mesh-group-name] hierarchy
level ... | [
"Example: Configuring BGP Route Target Filtering for VPNs",
"Example: Configuring FEC 129 BGP Autodiscovery for VPWS",
"Configuring EVPN Routing Instances",
"Configuring Routing Instances on PE Routers in VPNs",
"Configuring an MPLS-Based Layer 2 VPN (CLI Procedure)",
"Configuring an MPLS-Based Layer 3 VP... |
route-distinguisher-id | route-distinguisher-id ip-address; | [edit logical-systems logical-system-name routing-options],
[edit routing-options] | The automatic Route-Distinguisher feature uses the route-distinguisher-id command to create a Type 1
Route-Distinguisher to the routing instance, based on RFC 4364, BGP/MPLS IP Virtual Private
Networks (VPNs).
The 4-octet Administrator subfield of the Route-Distinguisher uses the IP address that is configured as the
ro... | [
{
"name": "ip-address",
"desc": "Address for routing instance."
}
] | 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 BGP Route Target Filtering for VPNs",
"Configuring Routing Instances on PE Routers in VPNs"
] |
route-distinguisher-id-use-router-id | route-distinguisher-id-use-router-id; | [edit logical-systems name routing-instances name routing-options],
[edit logical-systems name routing-options],
[edit logical-systems name tenants name routing-instances name routing-options],
[edit routing-instances name routing-options],
[edit routing-options] | Configure automatic route distinguisher to use the master instance router-ID as the route-distinguisher-
id so that you do not need to allocate and manage another IP address for that purpose. | [] | 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. | [] |
route-filter | route-filter (no-walkup | walkup); | [edit logical-systems logical-system-name policy-options defaults],
[edit logical-systems logical-system-name policy-options policy-statement policy-statement-name
defaults],
[edit policy-options defaults],
[edit policy-options policy-statement policy-statement-name defaults] | Enable or disable walkup globally or locally for route filters in a particular policy statement or globally.
The walkup feature examines more than the longest match route filters in a policy statement term with
more than one route filter, allowing consolidation of terms and a potential performance enhancement.
Default
... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Walkup for Route Filters Overview",
"Configuring Walkup for Route Filters to Improve Operational Efficiency",
"Example: Configuring Walkup for Route Filters Globally to Improve Operational Efficiency",
"Example: Configuring Walkup for Route Filters Locally to Improve Operational Efficiency"
] |
route-filter-list | [edit logical-systems logical-system-name policy-statement policy-statement-name term term-name
from],
[edit policy-options policy-statement policy-statement-name term term-name from] | The route filter list is a user-configured list of individual route filters that you create at the [edit policy-
options] hierarchy level. Each item in the list consists of a complete route filter statement, made up of a
destination prefix, a match type, and an optional action. You can re-use the list in different poli... | [
{
"name": "list-name",
"desc": "Name of route-filter-list of routes to match."
},
{
"name": "exact",
"desc": "Exactly match the prefix length."
},
{
"name": "longer",
"desc": "Mask is greater than the prefix length."
},
{
"name": "orlonger",
"desc": "Mask is greater than ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1.
Support on PTX1000, PTX10000, and PTX10003 Packet Transport Routers introduced in Junos OS
Release 20.2R1 for the following list-level qualifiers: exact, longer, orlonger, prefix-length-range, and upto. | [
"Understanding Route Filters for Use in Routing Policy Match Conditions",
"Example: Configuring Routing Policy Prefix Lists"
] | |
route-localization | route-localization {
inet;
inet6;
} | [edit chassis] | Configure FIB localization for IPv4 and IPv6 routes. | [
{
"name": "inet",
"desc": "Configure FIB localization for IPv4 routes."
},
{
"name": "inet6",
"desc": "Configure FIB localization for IPv6 routes."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Example: Configuring Packet Forwarding Engine FIB Localization"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.