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 |
|---|---|---|---|---|---|---|---|
receiver (Graceful Restart for BGP Helper) | receiver {
enable:
disable;
} | [edit logical-systems logical-system-name protocols bgp graceful-restart long-lived],
[edit logical-systems logical-system-name protocols bgp group group-name graceful-restart long-
lived],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address
graceful-restart long-lived],
[edit log... | Enable the long-lived graceful restart mechanism for a BGP receiver or helper router to preserve BGP
routing details for a longer period from a failed BGP peer. Long-lived graceful restart receiver or helper
mode is enabled by default, unless ordinary graceful restart receiver or helper mode is disabled.
The long-lived... | [
{
"name": "enable",
"desc": "Enable long-lived BGP graceful restart for a receiver or helper router"
},
{
"name": "disable",
"desc": "Disable long-lived BGP graceful restart for a receiver or helper router"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Graceful Restart Options for BGP",
"Junos OS High Availability User Guide"
] |
receiver | receiver {
install;
mode (proxy | transparent);
(source-list | source-vlans) vlan-list;
translate;
} | [edit protocols igmp-snooping vlan vlan-name data-forwarding],
[edit logical-systems name protocols igmp-snooping vlan vlan-name data-forwarding] | Configure a VLAN as a multicast receiver VLAN of a multicast source VLAN (MVLAN) using the
multicast VLAN registration (MVR) feature.
You must associate an MVR receiver VLAN with at least one data-forwarding source MVLAN. You can
configure an MVR receiver VLAN with multiple source MVLANs using the source-list or source... | [
{
"name": "install",
"desc": "Install forwarding table entries (also called bridging entries) on the MVR receiver VLAN when MVR is enabled. By default, MVR only installs bridging entries on the source MVLAN for a group address. You cannot configure the install option for a data-forwarding receiver VLAN that... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6.
Statement and mode, source-list, and translate options introduced in Junos OS Release 18.3R1 for EX4300
switches (ELS switches).
Statement and mode, source-list, and translate options added in Junos OS Release 18.4R1 for EX2300 and
EX3400 switches (ELS switches). | [
"Understanding Multicast VLAN Registration",
"Configuring Multicast VLAN Registration on EX Series Switches",
"Example: Configuring Multicast VLAN Registration on EX Series Switches Without ELS"
] |
recommendation-tlv | recommendation-tlv {
no-auto-negotiation;
} | [edit protocols dcbx interface interface-name enhanced-transmission-selection] | Enable DCBX to send the ETS Recommendation TLV (also known as the Information TLV) on egress. This
feature is valid only if the interface DCBX mode is IEEE DCBX. If the interface DCBX mode is DCBX
version 1.01, this statement has no effect. (DCBX version 1.01 does not advertise separate TLVs for
individual attributes.... | [
{
"name": "no-auto-negotiation",
"desc": "Disable sending of the ETS recommendation TLV."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring DCBX Autonegotiation"
] |
recommended | recommended; | [edit security idp dynamic-attack-group dynamic-attack-group-name filters] | Specify recommended filter to add predefined attacks recommended by Juniper Networks to the
dynamic attack group. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
recommended-action | recommended-action (close | close-client | close-server | drop | drop-packet | ignore | none); | [edit security idp custom-attack attack-name] | When the security device detects an attack, it performs the specified action. | [
{
"name": "close",
"desc": "Reset the client and the server."
},
{
"name": "close-client",
"desc": "Reset the client."
},
{
"name": "close-server",
"desc": "Reset the server."
},
{
"name": "drop",
"desc": "Drop the particular packet and all subsequent packets of the flow.... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
reconfigure (DHCP Local Server) | reconfigure {
attempts attempt-count;
clear-on-terminate;
strict;
support-option-pd-exclude;
timeout timeout-value;
token token-value;
trigger {
radius-disconnect;
}
} | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6],
[edit logical-systems logical-system-name routing-instances routing-instanc... | Enable dynamic reconfiguration triggered by the DHCP local server of all DHCP clients or only the
DHCP clients serviced by the specified group of interfaces. A group configuration takes precedence over
a DHCP local server configuration. The strict statement is available only for DHCPv6.
The remaining statements are exp... | [
{
"name": "support-option-pd-exclude",
"desc": "Request to exclude prefix option in the reconfigure message."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
Support at the [edit ... dhcpv6 ...] hierarchy levels introduced in Junos OS Release 10.4.
support-option-pd-exclude statement introduced in Junos OS Release 17.3 for the MX Series. | [
"Dynamic Reconfiguration of DHCP Servers and Clients"
] |
reconnect-time | reconnect-time seconds; | [edit logical-systems logical-system-name protocols ldp graceful-restart],
[edit protocols ldp graceful-restart],
[edit routing-instances routing-instance-name protocols ldp graceful-restart] | Specify the length of time required to reestablish a Label Distribution Protocol (LDP) session after
graceful restart. | [
{
"name": "seconds",
"desc": "Time required for reconnection."
}
] | 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 LDP Graceful Restart",
"MPLS Applications User Guide",
"Configuring Graceful Restart Options for LDP"
] |
record (Origin Validation for BGP) | record destination {
maximum-length prefix-length {
origin-autonomous-system as-number {
validation-state (invalid | valid);
}
}
} | [edit logical-systems logical-system-name routing-instances instance-name routing-options
validation static],
[edit logical-systems logical-system-name routing-options validation static],
[edit routing-instances instance-name routing-options validation static],
[edit routing-options validation static] | Configure the network prefix for the route validation (RV) record.
An RV record matches any route whose prefix matches the RV prefix, whose prefix length does not
exceed the "maximum-length" on page 10973 given in the RV record, and whose origin AS equals the
"origin-autonomous-system" on page 12428 given in the RV rec... | [
{
"name": "destination",
"desc": "Network prefix for the RV record."
}
] | 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. | [
"Use Case and Benefit of Origin Validation for BGP",
"Understanding Origin Validation for BGP",
"Example: Configuring Origin Validation for BGP"
] |
record | (record | no-record); | [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 (primary |
secondary) path-name],
[edit protocols mpls],
[edit protocols mpls label-switched-p... | Specify whether an LSP should actively record the path by sending the record route object (RRO). The
RRO is used to record the path that the LSP traverses. It includes the IP address and router/node ID of
each RSVP node in the path. Recording the LSP path can be useful for diagnostics and also provides loop
detection.
... | [] | 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. | [
"Disabling Path Route Recording by LSPs"
] |
record-route-option (IDS Screen Next Gen Services) | record-route-option; | [edit services screen ids-option screen-name ip] | Identify and drop IPv4 packets that have the IP option of 7 (Record Route). | [] | 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"
] |
recover-time (DDoS) | recover-time seconds; | [edit system ddos-protection protocols protocol-group (aggregate | packet-type)] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches)
Configure how much time must pass since the last detected DDoS violation before the traffic is
considered to have recovered from the attack and returned to normal. | [
{
"name": "seconds",
"desc": "Period required for the traffic to recover."
}
] | 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"
] |
recovered-clock | recovered-clock {
port port-number;
} | [edit chassis fpc slot-number pic pic-number] | Select the port where the synchronous clock may be recovered. | [
{
"name": "port-number",
"desc": "Port number where the synchronous clock may be recovered."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X48. | [
"Clock Sources for PTX Series Packet Transport Routers",
"Synchronizing Internal Stratum 3 Clock to External Clock Sources on PTX Series Routers"
] |
recovery | recovery {
automatic;
configuration-only;
configuration-preference;
no-automatic;
on-upgrade;
} | [edit system snapshot] | Configure system snapshot recovery management options. | [
{
"name": "automatic",
"desc": "This option automatically recovers the Junos volume when necessary. When you issue the request system snapshot command, the configuration on the device is stored in the OAM volume along with the creation of the recovery snapshot."
},
{
"name": "configuration-only",
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.2R1. | [] |
recovery | recovery {
(auto | manual);
timer timer-value;
} | [edit interfaces interfaces-name link-degrade-monitor] | Configure the mechanism to be used to recover a degraded link. The recovery options supported are
auto and manual. | [
{
"name": "auto",
"desc": "Recover a degraded link automatically. Use this option with the media-based action when there are no Layer 2 or Layer 3 protocols configured on the interface. If this option is configured, the degraded link is monitored at user-configured intervals; and if the link quality is foun... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Link Degrade Monitoring Overview"
] |
recovery-time (LDP) | recovery-time seconds; | [edit logical-systems logical-system-name protocols ldp graceful-restart],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp
graceful-restart],
[edit protocols ldp graceful-restart],
[edit routing-instances routing-instance-name protocols ldp graceful-restart] | Specify the length of time a router or switch waits for Label Distribution Protocol (LDP) neighbors to
assist it with a graceful restart. | [
{
"name": "seconds",
"desc": "Time the router waits for LDP to restart gracefully."
}
] | 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 Graceful Restart Options for LDP",
"Configuring Recovery Time and Maximum Recovery Time"
] |
recovery-timeout | recovery-timeout seconds; | [edit interfaces interface-name unit 0 family bridge] | Configure an interface to be temporarily disabled when MAC limiting, MAC move limiting, or rate-
limiting is in effect with the action shutdown. This enables the affected interface to recover automatically
from the error condition after the specified period of time:
•
If you configure MAC limiting with the shutdown opt... | [
{
"name": "seconds",
"desc": "Number of seconds that the interface remains in a disabled state due to a port error prior to automatic recovery. Range: 10 through 3600"
}
] | system—To view this statement in the configuration.
system–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10. | [
"Understanding MAC Limiting",
"Configuring Autorecovery From the Disabled State on Secure Interfaces of a Security Device (CLI",
"Procedure)",
"Configuring MAC Limiting (ELS)",
"Configuring MAC Move Limiting (ELS)",
"Enabling and Disabling Storm Control (ELS)",
"Example: Configuring MAC Limiting on a Se... |
recycle-bandwidth-profiles | recycle-bandwidth-profiles profile name {
evpn-irb percentage;
fti-virtual-loop percentage;
ingress-egress-mcast percentage;
mcast-tunnel-services percentage;
srv6 percentage;
srv6-ext percentage;
tunnel-services percentage;
vrf-leak percentage;
} | [edit system packet-forwarding-options] | evpn-irb
Set bandwidth in percentage to be allocated for EVPN IRB interface replication.
fti-virtual-loop
Set bandwidth in percentage to be allocated for an FTI virtual loop. You must
configure this option to support the FlowTapLite feature on ACX routers
running Junos OS Evolved.
ingress-egress-mcast
Set bandwidth in ... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.4R1.
Statement introduced in Junos OS Evolved Release 24.1R1 for ACX7K Series Routers.
fti-virtual-loop option introduced in Junos OS Evolved Release 24.4R1.
mcast-tunnel-services option introduced in Junos OS Evolved Release 25.4R1. | [
"Recycle Bandwidth Management",
"Example: Configuring Recycle Bandwidth"
] |
red-buffer-occupancy | red-buffer-occupancy {
weighted-averaged [ instant-usage-weight-exponent exponent-value ];
} | [edit chassis fpc slot-number pic pic-number ],
[edit chassis lcc number fpc slot-number pic pic-number] | Configure the IQ PIC to base random early detection (RED) queue management on a simple moving
average buffer occupancy calculation. If you do not include this statement, the IQ PIC bases RED on an
instantaneous buffer occupancy value. As an option, you can specify that the IQ PIC bases RED on a
weighted moving average ... | [
{
"name": "weighted-averaged",
"desc": "Configure the IQ PIC to base RED processing on a simple moving average of"
},
{
"name": "instant-usage-weight-exponent exponent-value",
"desc": "(Optional) Specify the integer to be used as the negative"
}
] | 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. | [
"Managing Transient Traffic Bursts by Configuring Weighted RED Buffer Occupancy",
"Example: Managing Transient Traffic Bursts by Configuring Weighted RED Buffer Occupancy"
] |
red-differential-delay | red-differential-delay milliseconds; | [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options] | For link services interfaces only, configure the red differential delay among bundle links to give warning
when a link has a differential delay that exceeds the configured threshold. | [
{
"name": "milliseconds",
"desc": "Red differential delay threshold."
}
] | 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 Differential Delay Alarms on Link Services Physical Interfaces with MLFR FRF.16"
] |
redial-delay | redial-delay time; | [edit interfaces dln unit logical-unit-number dialer-options],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number dialer-options] | On J Series Services Routers with interfaces configured for ISDN with dialout, specify the delay (in
seconds) between two successive calls made by the dialer. To configure callback mode, include the
callback statement at the [edit interfaces dln unit logical-unit-number dialer-options] hierarchy level.
If the callback ... | [
{
"name": "time",
"desc": "Delay (in seconds) between two successive calls."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [
"ISDN Interfaces Overview"
] |
redirect (PCC Action Profiles) | redirect {
url url-name;
} | [edit unified-edge pcef pcc-action-profiles profile-name],
[edit services pcef pcc-action-profiles profile-name] | Specify HTTP redirection to a URL. If you configure this, the PCC action profile can only be used in PCC
rules that match only HTTP-based applications and all flows.
If you are using Junos OS Subscriber Aware, specify the redirection at the [edit unified-edge pcef pcc-
action-profiles profile-name] hierarchy level.
If ... | [] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef pcc-action-profiles profile-name] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series.
Support for Next Gen Services for Junos OS Broadband Subscriber Management introduced in Juno... | [
"Configuring Policy and Charging Control Action Profiles For Junos OS Subscriber Aware",
"Configuring Policy and Charging Control Action Profiles for Subscriber Management"
] |
redirect-traffic | redirect-traffic (all | unauthenticated); | [edit services unified-access-control captive-portal policy] | Specify to redirect traffic destined for protected sources to the IC Series device. You can choose to
redirect all traffic or only unauthenticated traffic. | [
{
"name": "all",
"desc": "Redirect all traffic destined for the protected sources to the IC Series device. Specify this option"
},
{
"name": "unauthenticated",
"desc": "Redirect unauthenticated traffic destined for the protected sources to the IC Series"
}
] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Firewall User Authentication Overview"
] |
redirect-url | redirect-url url; | [edit services unified-access-control captive-portal policy] | Specify to redirect traffic destined for protected sources to a specified URL.
You can configure the following options in the redirect URL string:
•
%dest-url%—Specifies the protected resource which the user is trying to access.
•
%enforcer-id%—Specifies the ID assigned to the Junos OS Enforcer by the IC Series device.... | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Firewall User Authentication Overview"
] |
redirect-wx (Application Services) | redirect-wx; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
application-services] | ForSRX300, SRX320, SRX340, SRX345, SRX380, or SRX550M devices, define the acceleration zone
security policy for WX redirection of packets to the WXC Integrated Service Module (ISM 200) for WAN
acceleration. During the redirection process, the direction of the WX packet and its type determine
further processing of the p... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Security Policies Overview"
] |
redistribute-all-traffic (Aggregated Multiservices) | redistribute-all-traffic {
enable-rejoin;
} | [edit interfaces interface-name load-balancing-options member-failure-options] | Enable the option to redistribute traffic of a failed active member to the other active members.
For many-to-one (N:1) high availability support for Network Address Translation (NAT), the traffic for
the failed member is automatically redistributed to the other active members.
The remaining statement is explained separ... | [] | 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.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Understanding Aggregated Multiservices Interfaces",
"Example: Configuring an Aggregated Multiservices Interface (AMS)"
] |
redundancy (Graceful Switchover) | redundancy {
failover {
on-disk-failure;
on-loss-of-keepalives;
}
graceful-switchover;
} | [edit chassis] | Enable redundant Routing Engines on a Virtual Chassis with two or more member switches or on a
Virtual Chassis Fabric, on a standalone EX6200 or EX8200 switch with more than one Routing Engine.
The remaining statements are explained separately. See CLI Explorer.
Default
Redundancy is enabled for the Routing Engines. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Configuring Graceful Routing Engine Switchover in a Virtual Chassis",
"Configuring Graceful Routing Engine Switchover",
"Installing Software on an EX Series Switch with Redundant Routing Engines (CLI Procedure)",
"High Availability Features for EX Series Switches Overview"
] |
redundancy (Junos OS Evolved) | redundancy {
feed-redundancy {
slot psm slot number;
}
source-redundancy;
} | [edit chassis psm] | PSM Source/Feed Redundancy configuration. This command is only supported on the PTX10004,
PTX10008, and PTX10016 platforms with JNP10K-PWR-AC3 PSM. | [
{
"name": "source-redundancy",
"desc": "Toggle Source Redundancy for PSM"
},
{
"name": "feed-redundancy",
"desc": "Toggle Feed Redundancy for PSM"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.4R1. | [
"Managing Power"
] |
redundancy (Junos OS) | redundancy {
feed-redundancy {
slot pem slot number;
}
source-redundancy;
} | [edit chassis lcc name pem],
[edit chassis pem] | PEM Source/Feed Redundancy configuration. This command is only supported on the MX10004 and
MX10008 platforms with JNP10K-PWR-AC3 PSM. | [
{
"name": "feed-redundancy",
"desc": "Toggle Feed Redundancy for PEM"
},
{
"name": "source-redundancy",
"desc": "Toggle Source Redundancy for PEM"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [
"Managing Power"
] |
redundancy (M:N Subscriber Redundancy) | redundancy {
interface name {
local-inet-address v4-address;
local-inet6-address v6-address;
shared-key string;
virtual-inet-address virtual-inet-address;
virtual-inet6-address virtual-inet6-address;
}
group group-name {
interface interface-name {
... | [edit system services subscriber-management] | Enable M:N subscriber group redundancy. This global configuration applies to all subscribers in
redundancy groups across the chassis.
For dual-stack subscribers, you must configure both virtual IPv4 and virtual IPv6 addresses on the
interface. | [
{
"name": "group group-name",
"desc": "Name of the redundancy group."
},
{
"name": "hot-standby",
"desc": "Specifies the backup BNG, which is ready to switchover the traffic from the primary BNG immediately without any disruption during primary BNG failure."
},
{
"name": "interface",
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1.
local-inet-address, local-inet6-address, pseudo-wire, and shared-key options added in Junos OS Release
20.1R1.
service-activation-on-failover introduced in Junos OS Release 22.2R1. | [
"How to Configure M:N Subscriber Redundancy with VRRP and DHCP Binding Synchronization"
] |
redundancy (Power Management) | redundancy {
n-plus-n (Power Management);
} | [edit chassis psu] | Configure N+N power supply redundancy for power management on an EX6200 or EX8200 switch.
The remaining statement is explained separately. See CLI Explorer.
Default
N+1 power supply redundancy is configured by default. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Power Supply Redundancy (CLI Procedure)"
] |
redundancy (satellite-management) | redundancy {
n-plus-n;
} | [edit chassis satellite-management psu] | Configure N+N power supply redundancy for the satellite devices in a Junos Fusion.
The remaining statement is explained separately. See CLI Explorer.
Default
N+1 power supply redundancy is configured on each satellite device by default. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1. | [
"Understanding Power over Ethernet in a Junos Fusion"
] |
redundancy | redundancy {
cfeb slot (always | preferred);
failover {
on-disk-failure;
on-loss-of-keepalives;
on-re-to-fpc-stale;;
}
feb {
redundancy-group group-name {
description description;
feb slot-number (backup | primary);
no-auto-failover;
... | [edit chassis] | Configure redundancy options. | [] | 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 Routing Engine Redundancy",
"Configuring CFEB Redundancy on the M10i Router",
"Configuring FEB Redundancy on the M120 Router",
"Configuring SFM Redundancy on M40e and M160 Routers",
"Configuring SSB Redundancy on the M20 Router"
] |
redundancy-event (Services Redundancy Daemon) | redundancy-event event-name {
monitor {
link-down interface-name;
peer {
(mastership-acquire | mastership-release);
}
process routing abort;
process routing restart;
}
] | [edit event-options] | Configure events monitored to trigger change of primary role and routing using inter-chassis
redundancy. | [
{
"name": "event-name",
"desc": "Alphanumeric name for a monitored event."
},
{
"name": "link-down interface-name",
"desc": "Name of an interface, link, or link aggregation, to monitor."
},
{
"name": "peer mastership-acquire",
"desc": "(Optional) Monitor primary-role acquisition peer... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 17.1.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Configuring Inter-Chassis Services Redundancy for Next Gen Services",
"Configuring the Service Redundancy Daemon"
] |
redundancy-group (Chassis - MX Series) | redundancy-group {
interface-type {
redundant-logical-tunnel {
device count;
}
redundant-virtual-tunnel {
device count;
}
}
} | [edit chassis] | Configure redundant logical tunnels, redundant virtual tunnels, or both on MX Series 5G Universal
Routing Platforms.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Redundant Virtual Tunnels Providing Resiliency in Delivering Multicast Traffic Overview",
"Configuring Redundant Virtual Tunnels to Provide Resiliency in Delivering Multicast Traffic",
"Example: Configuring Redundant Virtual Tunnels to Provide Resiliency in Delivering Multicast Traffic"
] |
redundancy-group (Chassis Cluster) | redundancy-group group-number {
gratuitous-arp-count number;
hold-down-interval number;
interface-monitor interface-name {
weight number;
}
ip-monitoring{
family {
inet {
ipv4-address {
interface {
logical-int... | [edit chassis cluster] | Define a redundancy group. Except for redundancy group 0, a redundancy group is a logical interface
consisting of two physical Ethernet interfaces, one on each chassis. One interface is active, and the
other is on standby. When the active interface fails, the standby interface becomes active. The logical
interface is c... | [
{
"name": "group-number",
"desc": "Redundancy group identification number. NOTE: The maximum number of redundancy groups is equal to the number of redundant Ethernet interfaces that you configure. Range: 0 through 128"
},
{
"name": "interface-monitor",
"desc": "Specify a redundancy group interf... | 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. | [] |
redundancy-group (Interfaces) | redundancy-group number ; | [edit interfaces interface-name redundant-ether-options] | Specify the redundancy group that a redundant Ethernet interface belongs to. | [
{
"name": "number",
"desc": "Number of the redundancy group that the redundant interface belongs to. Failover properties of"
}
] | 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. | [
"Interfaces User Guide for Security Devices"
] |
redundancy-group (Redundant Tunnel) | redundancy-group {
member-interface interface-name {
(active | backup);
minimum-links number-of-links;
}
} | [edit interfaces interface-name] | Configure member tunnels of redundant logical or virtual tunnels. | [
{
"name": "active",
"desc": "Set the interface to the active mode."
},
{
"name": "backup",
"desc": "Set the interface to the backup mode."
},
{
"name": "minimum-links",
"desc": "Specify the minimum number of active links required for the interface to remain up. The remaining statemen... | interface—To view this statement in the configuration.
interface-control—To view this statement in the configuration. | minimum-links option introduced in Junos OS Release 24.2.
Statement introduced in Junos OS Release 13.3. | [
"Redundant Virtual Tunnels Providing Resiliency in Delivering Multicast Traffic Overview",
"Configuring Redundant Virtual Tunnels to Provide Resiliency in Delivering Multicast Traffic",
"Example: Configuring Redundant Virtual Tunnels to Provide Resiliency in Delivering Multicast Traffic",
"Example: Configurin... |
redundancy-group | redundancy-group group-name {
description description;
feb slot-number (backup | primary);
no-auto-failover;
} | [edit chassis redundancy feb] | On M120 routers only, configure a Forwarding Engine Board (FEB) redundancy group. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Configuring FEB Redundancy on the M120 Router"
] |
redundancy-group-id (Junos Fusion) | redundancy-group-id redundancy-group-id-number; | [edit chassis satellite-management redundancy-groups redundancy-group-name] | Defines a redundancy group ID number for a redundancy group in a Junos Fusion using dual aggregation
devices.
A Junos Fusion using dual aggregation devices must have one redundancy group that includes both
aggregation devices and all satellite devices. The redundancy group must be configured individually on
each aggreg... | [
{
"name": "redundancy-group-id-number",
"desc": "The user-defined redundancy group ID number. Range: 1 through 255"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1. | [
"Configuring or Expanding a Junos Fusion Enterprise"
] |
redundancy-interface-process | redundancy-interface-process {
command binary-file-path;
disable;
failover (alternate-media | other-routing-engine);
} | [edit system processes] | Specify as an active or backup process of an application server, configure to process traffic for more than
one logical application server. | [
{
"name": "command binary-file-path",
"desc": "Path to the binary process."
},
{
"name": "disable",
"desc": "Disable the redundancy interface management process."
},
{
"name": "failover",
"desc": "Configure the device to reboot if the software process fails four times within 30 secon... | 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. | [] |
redundancy-mode (MX and SRX Platforms) | redundancy-mode (increased-bandwidth | redundant) | [edit chassis fabric] | Configure the active control boards to be in redundancy mode or increased fabric bandwidth mode.
In increased fabric bandwidth mode, which is the default behavior for MX Series routers with Switch
Control Board (SCB), the maximum number of available fabric planes are used. The MX Series routers
that contain the Enhance... | [
{
"name": "increased-bandwidth",
"desc": "Enable increased fabric bandwidth mode for the control boards, which causes all the available fabric planes to be used."
},
{
"name": "redundant",
"desc": "Enable redundancy mode for the control boards, which causes all the FPCs to use 4 fabric planes as... | 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. | [
"Detection and Corrective Actions of Line Cards on MX Series Routers",
"Detection and Recovery of Fabric-Related Failures Caused by Loss of Connectivity on MX Series",
"Routers",
"MX Series Routers Fabric Resiliency",
"Configuring Fabric Redundancy Mode for Active Control Boards on MX Series Routers"
] |
redundancy-mode (Junos and Junos EVO) | redundancy-mode(active-active | active-backup); | [edit chassis cluster] | Redundancy mode for the cluster (Reboot all nodes simultaneously after change). | [
{
"name": "active-active",
"desc": "Primary and secondary nodes in active mode"
},
{
"name": "active-backup",
"desc": "Primary in active, secondary in backup mode"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.4R1. Use Feature Explorer to confirm platform and release
support for specific features. | [] |
redundancy-options (Adaptive Services Interfaces) | redundancy-options {
primary sp-fpc/pic/port;
secondary sp-fpc/pic/port;
hot-standby
} | [edit interfaces rspnumber]
[edit interfaces rmsnumber] | Specify the primary and secondary (backup) adaptive services interfaces. | [] | 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 AS or Multiservices PIC Redundancy"
] |
redundancy-options (Aggregated Multiservices) | redundancy-options {
primary mams-a/b/0;
secondary mams-a/b/0;
} | [edit interfaces interface-name] | Configure warm standby for an aggregated multiservices (AMS) interface. Specify a primary and a
secondary (backup) member services interface for the AMS interface. The primary interface is the
service interface that you want to back up, and it is the active interface unless it fails. The secondary
interface is the back... | [
{
"name": "primary mams-a/b/0",
"desc": "Name of the primary services interface, where a is the FPC slot number and b is the PIC slot number."
},
{
"name": "secondary mams-a/b/0",
"desc": "Name of the secondary (backup) services interface, where a is the FPC slot number and b is the PIC slot num... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Configuring Warm Standby for Services Interfaces"
] |
redundancy-options (Link Services IQ PIC Interfaces) | redundancy-options {
(hot-standby | warm-standby);
primary lsq-fpc/pic/port;
secondary lsq-fpc/pic/port;
} | [edit interfaces rlsqnumber] | Specify the primary and secondary (backup) Link Services IQ PIC interfaces. | [] | 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. | [
"Configuring LSQ Interface Redundancy in a Single Router Using Virtual Interfaces"
] |
redundancy-options (Stateful Synchronization) | redundancy-options {
redundancy-local {
data-address address;
}
redundancy-peer {
ipaddress address;
}
replication-threshold seconds;
routing-instance instance-name;
apply-groups (apply-groups-except |redundancy-local | redundancy-peer)
replication-options (apply-groups |... | [edit interfaces interface-name] | Specify the primary and secondary (backup) adaptive services PIC interfaces. | [
{
"name": "data-address address",
"desc": "Internal IP address of the local redundant PIC."
},
{
"name": "ipaddress address",
"desc": "Internal IP address of the remote redundant PIC."
},
{
"name": "instance-name",
"desc": "Name of the routing instance to apply to the HA synchronizat... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card (interfaces of type vms-x/y/z). | [
"Configuring Inter-Chassis Stateful Synchronization for Long Lived NAT and Stateful Firewall Flows",
"(MS-MPC, MS-MIC) (Release 16.1 and later)",
"Inter-Chassis High Availability for MS-MIC and MS-MPC (Release 15.1 and earlier)"
] |
redundancy-policy (Interchassis Services Redundancy) | redundancy-policy policy-name {
redundancy-events [event-list] {
then {
acquire-mastership;
<add-static-route destination {
(next-hop next-hop | receive);
routing-instance routing-instance
}>
<broadcast-warning> ;
<... | [edit policy-options] | Specify the actions to be taken for redundancy events. These include acquiring or releasing primary role
and adding or deleting static routes. | [
{
"name": "acquire-mastership",
"desc": "Switch from standby to primary role."
},
{
"name": "add-static-route",
"desc": ""
},
{
"name": "destination",
"desc": "(Optional) Use the specified destination IP address and prefix for an added signal route."
},
{
"name": "broadcast-w... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 17.1.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Configuring Inter-Chassis Services Redundancy for Next Gen Services",
"Configuring the Service Redundancy Daemon"
] |
redundancy-set | redundancy-set redundancy-set {
healthcheck-timer-interval healthcheck-timer-interval;
hold-time hold-time;
keepalive keepalive;
redundancy-group redundancy-group;
redundancy-policy [redundancy-policy-list]
} | [edit services] | Specify the characteristics of a redundancy set. | [
{
"name": "healthcheck-timer-interval healthcheck-",
"desc": ""
},
{
"name": "timer-interval",
"desc": "Frequency of health check probes in seconds. Range: 0 through 3600 seconds"
},
{
"name": "hold-time",
"desc": "Maximum wait time for a health check response. When this time expire... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 17.1.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Configuring Inter-Chassis Services Redundancy for Next Gen Services",
"Configuring the Service Redundancy Daemon"
] |
redundancy-set-id (Service Set) | redundancy-set-id redundancy-set; | [edit services service-set service-set-name] | Specify the identifier of the redundancy set to use in the stateful synchronization of services for a
service set. | [
{
"name": "redundancy-set",
"desc": "Identifier for the redundancy set. The identifier can be a number from 1-100."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Configuring Inter-Chassis Services Redundancy for Next Gen Services",
"Configuring the Service Redundancy Daemon"
] |
redundant-ether-options | redundant-ether-options {
(flow-control | no-flow-control);
lacp {
(active | passive);
periodic (fast | slow);
}
link-speed speed;
(loopback | no-loopback);
minimum-links number;
redundancy-group number;
source-address-filter mac-address;
(source-filtering | no-so... | [edit interfaces interface-name] | Configure Ethernet redundancy options for a chassis cluster.
In a chassis cluster setup, a redundant Ethernet interface is a pseudointerface that includes at minimum
one physical interface from each node of the cluster.
A reth is a special type of interface that has the characteristics of aggregated Ethernet interface. | [
{
"name": "flow-control",
"desc": "Enable flow control."
},
{
"name": "link-speed",
"desc": "Link speed of individual interface that joins the reth interface. Values:"
},
{
"name": "100m",
"desc": "Links are 100 Mbps"
},
{
"name": "10g",
"desc": "Links are 10 Gbps"
},
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Example: Enabling Eight-Queue Class of Service on Redundant Ethernet Interfaces on SRX Series",
"Devices in a Chassis Cluster",
"Example: Configuring Chassis Cluster Redundant Ethernet Interfaces"
] |
redundant-logical-tunnel | redundant-logical-tunnel {
device-count count;
} | [edit chassis redundancy-group interface-type] | Configure redundant logical tunnels on MX Series 5G Universal Routing Platforms. | [
{
"name": "count",
"desc": "Specify the number of the redundant logical tunnels. For Junos OS Release 13.3R1, 13.3R2, and 14.1R1 the valid range is from 1 through 16. For Junos OS Release 13.3R3 and 14.1R2 and later releases the valid range is from 1 through 255."
}
] | interface—To view this statement in the configuration.
interface-control—To view this statement in the configuration. | Statement introduced in Junos OS Release 13.3.
Support for up to 255 redundant logical tunnels added to Junos OS Release 13.3R3 and 14.1R2. | [
"Redundant Logical Tunnels Overview",
"Configuring Redundant Logical Tunnels",
"Example: Configuring Redundant Logical Tunnels"
] |
redundant-parent (Interfaces Fast Ethernet) | redundant-parent interface-name; | [edit interfaces interface-name fastether-options] | Configure Fast Ethernet-specific interface properties for Ethernet redundancy in a chassis cluster. | [
{
"name": "interface",
"desc": "Parent redundant interface of the Fast Ethernet interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Understanding Ethernet Interfaces"
] |
redundant-parent (Interfaces Gigabit Ethernet) | redundant-parent interface-name; | [edit interfaces interface-name gigether-options] | Configure Gigabit Ethernet-specific interface properties for Ethernet redundancy in a chassis cluster. | [
{
"name": "interface",
"desc": "Parent redundant interface of the Gigabit Ethernet interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Release 9.0 of Junos OS. | [] |
redundant-parent (Interfaces) | redundant-parent redundant-ethernet-interface-name; | [edit interfaces interface-name gigether-options]
[edit interfaces interface-name fastether-options] | Specify redundant Ethernet interfaces (reth) and assign local (child) interfaces to the reth interfaces. A
redundant Ethernet interface contains a pair of Fast Ethernet interfaces or a pair of Gigabit Ethernet
interfaces that are referred to as child interfaces of the redundant Ethernet interface. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Example: Configuring Chassis Cluster Redundant Ethernet Interfaces"
] |
redundant-power-system | EX2200 switch:
redundant-power-system {
priority (0|1|2|3|4|5|6)
}
}
EX3300 switch:
redundant-power-system {
member vc-member-number {
priority (0|1|2|3|4|5|6)
}
} | [edit] | Configure Redundant Power System (RPS) member to ensure higher- switches always receive power
backup.
The remaining statements are explained separately. See CLI Explorer. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Determining and Setting Priority for Switches Connected to an EX Series RPS"
] |
redundant-pseudo-interface-options | redundant-pseudo-interface-options {
redundancy-group redundancy-group-number;
} | [edit interfaces lo0] | Configure the loopback pseudointerface in a redundancy group.
Redundancy groups are used to bundle interfaces into a group for failover purpose in a chassis cluster
setup. You can configure a loopback interface as an alternative physical interface to reach the peer
gateway. Loopback interfaces can be configured on any ... | [
{
"name": "redundancy-group-number",
"desc": "Configure the redundancy group number. Range: 0 through 255"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. | [
"Understanding the Loopback Interface for a High Availability VPN"
] |
redundant-sources | redundant-sources [ addresses ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast flow-map flow-map-name],
[edit logical-systems logical-system-name routing-options multicast flow-map flow-map-name],
[edit routing-instances routing-instance-name routing-options multicast flow-map flow-map-nam... | Configure a list of redundant sources for multicast flows defined by a flow map. | [
{
"name": "addresses",
"desc": "List of IPv4 or IPv6 addresses for use as redundant (backup) sources for multicast flows"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Example: Configuring a Multicast Flow Map"
] |
redundant-trunk-group | redundant-trunk-group {
group name {
interface interface-name <primary>;
interface interface-name;
preempt-cutover-timer seconds;
}
} | For platforms with ELS:
[edit switch-options]
For platforms without ELS:
[edit ethernet-switching-options] | Configure a primary link and secondary link on trunk ports. If the primary link fails, the secondary link
automatically takes over without waiting for normal spanning-tree protocol convergence.
The remaining statements are explained separately. See CLI Explorer. | [] | 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.
Hierarchy level [edit switch-options] introduced in Junos OS Release 13.2X50-D10 (ELS). (See Using the
Enhanced Layer 2 Software CLI for information about ELS.) | [
"Example: Configuring Redundant Trunk Links for Faster Recovery on EX Series Switches",
"Example: Configuring Redundant Trunk Links for Faster Recovery on Devices with ELS Support",
"Understanding Redundant Trunk Links (Legacy RTG Configuration)"
] |
redundant-virtual-tunnel | redundant-virtual-tunnel {
device-count count;
} | [edit chassis redundancy-group interface-type] | Configure redundant virtual tunnels on MX Series 5G Universal Routing Platforms. | [
{
"name": "device-count count",
"desc": "Specify the number of redundant virtual tunnels."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.2. | [
"Redundant Virtual Tunnels Providing Resiliency in Delivering Multicast Traffic Overview",
"Configuring Redundant Virtual Tunnels to Provide Resiliency in Delivering Multicast Traffic",
"Example: Configuring Redundant Virtual Tunnels to Provide Resiliency in Delivering Multicast Traffic"
] |
reference-bandwidth (Protocols IS-IS) | reference-bandwidth reference-bandwidth; | [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] | Optimize routing based on bandwidth by setting the reference bandwidth used in calculating the default
interface cost.
All IS-IS interfaces have a cost, which is a routing metric that is used in the IS-IS link-state calculation.
Routes with lower total path metrics are preferred over those with higher path metrics. Whe... | [
{
"name": "reference-bandwidth",
"desc": "Reference bandwidth value in bits per second."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Understanding IS-IS Configuration",
"Example: Configuring IS-IS",
"https://www.juniper.net/us/en/training/certification/JNCIP_studyguide.pdf"
] |
reference-bandwidth (Protocols OSPF) | reference-bandwidth reference-bandwidth; | [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... | Set the reference bandwidth used in calculating the default interface cost. The cost is calculated using
the following formula:
cost = ref-bandwidth/bandwidth | [
{
"name": "reference-bandwidth",
"desc": "Reference bandwidth, in bits per second."
}
] | 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: Controlling the Cost of Individual OSPF Network Segments"
] |
reflect-etype | reflect-etype ethertype-value; | [edit services monitoring rfc2544 tests test-name test-name] | Specify the EtherType to be used for reflection of the test frames. EtherType is a two-octet field in an
Ethernet frame that defines the protocol in the frame payload. This statement is valid only if you
configure the test mode to be a reflector. If you do not configure this statement, all EtherTypes are
reflected. | [
{
"name": "ethertype-value",
"desc": "Identifier for the EtherType. The EtherType value appears in the Ethernet type field of the packet. It specifies the protocol being transported in the Ethernet frame. For instance, the EtherType for IPv4 is 0x0800. So, if you specify the value as 2048, IPv4 packets are ... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X53.
Statement introduced in Junos OS Evolved Release 22.4R1. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers",
"Supported RFC 2544-Based Benchmarking Statements on MX Series Routers",
"Configuring an RFC 2544-Based Benchmarking Test"
] |
reflect-mode | [edit services monitoring rfc2544 tests test-name test-name] | Specify the reflection mode for the benchmarking test. | [
{
"name": "mac-rewrite",
"desc": "(Junos OS ACX Series routers only) Enable rewriting of the MAC address on the reflected frames. You configure which MAC addresses the software should use with the source-mac-address and destination-mac-address configuration statements."
},
{
"name": "mac-swap",
... | 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.
Statement introduced in Junos OS Evolved Release 22.4R1. | [
"Understanding RFC2544-Based Benchmarking Tests for E-LAN and E-Line Services on MX Series",
"Routers",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers",
"Configuring an RFC 2544-Based Benchmarking Test"
] | |
reflective-relay | reflective-relay; | [edit interfaces interface-name unit logical-unit-number family ethernet-switching] | Configure a switch interface to return packets back to a device on the same interface that was used to
deliver the packets.
Default
Switch interfaces are not configured for reflective relay. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Example: Configuring Reflective Relay for Use with VEPA Technology on QFX Switches",
"Configuring Reflective Relay on Switches"
] |
reflexive | revert | reverse | reflexive; | revert; | reverse {
application-profile profile-name;
dscp (alias | bits);
forwarding-class class-name;
syslog;
} | [edit services cos rule rule-name term term-name then] | reflexive—Applies the CoS rule actions to flows in the reverse direction as well as to flows in the
matching direction.
revert—Stores the DSCP and forwarding class of a packet that is received in the match direction of the
rule and then applies that DSCP and forwarding class to packets that are received in the reverse
... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1.
revert option introduced in Junos OS Release 16.1R5 and 17.4R1. | [
"Configuring CoS Rules on Services PICs",
"Configuring CoS Rules"
] |
refresh (Commit Scripts) | refresh; | [edit system scripts commit],
[edit system scripts commit file filename] | Overwrite the local copy of all enabled commit scripts or a single enabled commit script with the copy
located at the source URL, as specified in the source statement at the same hierarchy level. If the load-
scripts-from-flash statement is configured, the device refreshes the scripts on the flash drive instead of
the ... | [] | maintenance—To execute this statement in configuration mode. | Statement introduced in Junos OS Release 7.4. | [
"Configuring and Using a Master Source Location for a Script",
"Example: Configuring and Refreshing from the Master Source for a Script"
] |
refresh (Event Scripts) | refresh; | [edit event-options event-script],
[edit event-options event-script file filename] | Overwrite the local copy of all enabled event scripts or a single enabled event script with the copy
located at the source URL, as specified in the source statement at the same hierarchy level. If the load-
scripts-from-flash statement is configured, the device refreshes the scripts on the flash drive instead of
the ha... | [] | maintenance—To execute this statement in configuration mode. | Statement introduced in Junos OS Release 9.6. | [
"Configure and Use a Master Source Location for a Script",
"Example: Configure and Refresh from the Master Source for a Script"
] |
refresh (JET) | refresh; | [edit system extensions extension-service application file filename] | Overwrite the local copy of all enabled Juniper Extension Toolkit (JET) scripts or a single enabled JET
script with the copy located at the source URL, as specified in the source statement at the same hierarchy
level. If the load-scripts-from-flash statement is configured, the device refreshes the scripts on the flash
... | [] | maintenance—To execute this statement in configuration mode. | Statement introduced in Junos OS Release 18.1R1. | [
"Configuring and Using a Master Source Location for a Script",
"Example: Configuring and Refreshing from the Master Source for a Script",
"Management Interface in a Non-Default Instance"
] |
refresh (Op Scripts) | refresh; | [edit system scripts op],
[edit system scripts op file filename] | Overwrite the local copy of all enabled op scripts or a single enabled op script with the copy located at
the source URL, as specified in the source statement at the same hierarchy level. If the load-scripts-from-
flash statement is configured, the device refreshes the scripts on the flash drive instead of the hard dis... | [] | maintenance—To execute this statement in configuration mode. | Statement introduced in Junos OS Release 7.6. | [
"Configuring and Using a Master Source Location for a Script",
"Example: Configuring and Refreshing from the Master Source for a Script"
] |
refresh (SNMP Scripts) | refresh; | [edit system scripts snmp],
[edit system scripts snmp file filename] | Overwrite the local copy of all enabled SNMP scripts or a single enabled SNMP script with the copy
located at the source URL, as specified in the source statement at the same hierarchy level. If the load-
scripts-from-flash statement is configured, the device refreshes the scripts on the flash drive instead of
the hard... | [] | maintenance—To execute this statement in configuration mode. | Statement introduced in Junos OS Release 15.1. | [
"Configuring and Using a Master Source Location for a Script",
"Example: Configuring and Refreshing from the Master Source for a Script"
] |
refresh-from (Commit Scripts) | refresh-from url; | [edit system scripts commit],
[edit system scripts commit file filename] | Overwrite the local copy of all enabled commit scripts or a single enabled commit script with the copy
located at the specified URL. If the load-scripts-from-flash statement is configured, the device refreshes
the scripts on the flash drive instead of the hard disk.
The update operation occurs as soon as you issue the ... | [
{
"name": "url",
"desc": "The source specified as an HTTPS URL, HTTP URL, FTP URL, or secure copy (scp)-style remote file specification."
}
] | maintenance—To execute this statement in configuration mode. | Statement introduced in Junos OS Release 7.4. | [
"Using an Alternate Source Location for a Script"
] |
refresh-from (Event Scripts) | refresh-from url; | [edit event-options event-script],
[edit event-options event-script file filename] | Overwrite the local copy of all enabled event scripts or a single enabled event script with the copy
located at the specified URL. If the load-scripts-from-flash statement is configured, the device refreshes
the scripts on the flash drive instead of the hard disk.
The update operation occurs as soon as you issue the se... | [
{
"name": "url",
"desc": "Source specified as an HTTPS URL, HTTP URL, FTP URL, or secure copy (scp)-style remote file specification."
}
] | maintenance—To execute this statement in configuration mode. | Statement introduced in Junos OS Release 9.6. | [
"Use an Alternate Source Location for a Script"
] |
refresh-from (JET) | refresh-from url; | [edit system extensions extension-service application file filename] | Overwrite the local copy of all enabled Juniper Extension Toolkit (JET) scripts or a single enabled JET
script with the copy located at the specified URL. If the load-scripts-from-flash statement is configured,
the device refreshes the scripts on the flash drive instead of the hard disk.
The update operation occurs as ... | [
{
"name": "url",
"desc": "The source specified as a HTTPS URL, HTTP URL, FTP URL, or secure copy (scp)-style remote file specification."
}
] | maintenance—To execute this statement in configuration mode. | Statement introduced in Junos OS Release 18.1R1. | [
"Using an Alternate Source Location for a Script"
] |
refresh-from (Op Scripts) | refresh-from url; | [edit system scripts op],
[edit system scripts op file filename] | Overwrite the local copy of all enabled op scripts or a single enabled op script with the copy located at
the specified URL. If the load-scripts-from-flash statement is configured, the device refreshes the scripts
on the flash drive instead of the hard disk.
The update operation occurs as soon as you issue the set refr... | [
{
"name": "url",
"desc": "Source specified as an HTTPS URL, HTTP URL, FTP URL, or secure copy (scp)-style remote file specification."
}
] | maintenance—To execute this statement in configuration mode. | Statement introduced in Junos OS Release 7.6. | [
"Using an Alternate Source Location for a Script"
] |
refresh-from (SNMP Scripts) | refresh-from url; | [edit system scripts snmp],
[edit system scripts snmp file filename] | Overwrite the local copy of all enabled SNMP scripts or a single enabled SNMP script with the copy
located at the specified URL. If the load-scripts-from-flash statement is configured, the device refreshes
the scripts on the flash drive instead of the hard drive.
The update operation occurs as soon as you issue the set... | [
{
"name": "url",
"desc": "The source specified as an HTTPS URL, HTTP URL, FTP URL, or secure copy (scp)-style remote file specification."
}
] | maintenance—To execute this statement in configuration mode. | Statement introduced in Junos OS Release 15.1. | [
"Use an Alternate Source Location for a Script"
] |
refresh-interval | refresh-interval number-of-hours; | [edit security pki ca-profile ca-profile-name revocation-check crl] | (Adaptive services interfaces only) Specify the amount of time between certificate revocation list (CRL)
updates. | [
{
"name": "number-of-hours",
"desc": "Time interval, in hours, between CRL updates."
}
] | 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"
] |
refresh-rate (Flow Monitoring Logs for NAT) | refresh-rate packets packets seconds seconds; | [edit services jflow-log template-profile template–profile-name] | Specify the refresh rate for transmitting flow template records with version 9 and IPFIX templates for
NAT events to the collector, in either packets or seconds. | [
{
"name": "packets",
"desc": "Number of packets after which templates are sent to the collector."
},
{
"name": "seconds",
"desc": "Number of seconds after which templates are sent to the collector"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding NAT Event Logging in Flow Monitoring Format on an MX Series Router or NFX250",
"Configuring Log Generation of NAT Events in Flow Monitoring Record Format on an MX Series",
"Router or NFX250",
"Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats",
"Exa... |
refresh-time | refresh-time seconds; | [edit logical-systems logical-system-name protocols rsvp],
[edit protocols rsvp] | Set the refresh time. | [
{
"name": "seconds",
"desc": "Refresh time."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Timers for RSVP Refresh Messages"
] |
regex (Class Attribute) | regex “value”; | [edit unified-edge gateways tdf gateway-name domains domain-name subscription-id use-class] | Configure a regular expression to parse the Class attribute contents of the accounting request from the
BNG, PGW, or GGSN. | [
{
"name": "value",
"desc": "Regular expression that parses the contents of the Class attribute. For example, the following configuration generates \" 000118191129ALICE:DRAV3:\" out of \" 000118191129#000118191129#ALICE:DRAV3:#7168#nflat#ADSL##\": [edit unified-edge gateways tdf TDF1 domains domain1 subscrip... | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring a Set of IP-Based TDF Subscriber Properties with a TDF Domain"
] |
regex-additive-logic | regex-additive-logic; | [edit system] | Enable additive logic (that is, deny by default / allow some as specified) to be used in regular expressions
in the allow-configuration-regexps and deny-configuration-regexps statements at the [edit system login class
class-name] hierarchy level.
When you enable additive logic, the allow-configuration-regexps statement... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Example: Configuring User Permissions with Access Privileges for Configuration Statements and",
"Hierarchies",
"Example: Using Additive Logic With Regular Expressions to Specify Access Privileges",
"Regular Expressions for Allowing and Denying Junos OS Operational Mode Commands,",
"Configuration Statements... |
regexp | regexp regular-expression; | [edit security idp custom-attack attack-name attack-type signature] | Specify a Perl Compatible Regular Expression (PCRE) expression. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
region | region region-name{
incoming;
ingress-replication {
create-new-ucast-tunnel;
label-switched-path {
llabel-switched-path-template (Multicast){
(default-template | lsp-template-name);
}
}
}
ldp-p2mp;
rsvp-te {
label-switched-path... | [edit protocols mvpn inter-region-template template template-name] | Specify the regions based on the BGP peer groups. The regions support different tunnel types such as
incoming, ingress replication, ldp-p2mp, or rsvp-te. The incoming tunnel indicates that the tunnel type
across the area boundary router (ABR) is not changed. A template is used to define the tunnel type for
each region. | [
{
"name": "incoming",
"desc": "Specify the tunnel type to be same across area boundary router (ABR)."
}
] | 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. | [
"Segmented Inter-Area Point-to-Multipoint Label-Switched Paths Overview",
"Example: Configuring Segmented Inter-Area P2MP LSP",
"Configuring Segmented Inter-Area P2MP LSP"
] |
register-limit | register-limit {
family (inet | inet6) {
log-interval seconds;
maximum limit;
threshold value;
}
log-interval seconds;
maximum limit;
threshold value;
} | [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 a limit for the number of incoming (S,G) PIM registers.
NOTE: The maximum limit settings that you configure with the maximum and the family
(inet | inet6) maximum statements are mutually exclusive. For example, if you configure a
global maximum PIM register message limit, you cannot configure a limit at the f... | [
{
"name": "family (inet | inet6)",
"desc": "(Optional) Specify either IPv4 or IPv6 messages to be counted towards the"
}
] | 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. | [
"Example: Configuring PIM State Limits",
"clear pim join",
"clear pim register"
] |
register-probe-time | register-probe-time register-probe-time; | [edit protocols pim rp] | Specify the amount of time before the register suppression time (RST) expires when a designated switch
can send a NULL-Register to the rendezvous point (RP). | [
{
"name": "register-probe-time",
"desc": "Amount of time before the RST expires. Default: 5 seconds Range: 5 to 60 seconds"
}
] | 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. | [
"PIM Overview",
"Understanding PIM Sparse Mode"
] |
registration | registration (forbidden | normal | restricted); | [edit protocols mvrp interface (all | interface-name)],
[edit routing-instances routing-instance-name protocols mvrp interface (all | interface-name)],
[edit logical-systems logical-system-name protocols mvrp interface (all | interface-name)],
[edit logical-systems logical-system-name routing-instances routing-instance... | Specifies the Multiple VLAN Registration Protocol (MVRP) registration mode for the interface if MVRP is
enabled.
Default
normal—The interface or interfaces accept MVRP messages and participate in MVRP. | [
{
"name": "forbidden",
"desc": "The interface or interfaces do not register and do not participate in MVRP."
},
{
"name": "normal",
"desc": "The interface or interfaces accept MVRP messages and participate in MVRP."
},
{
"name": "restricted",
"desc": "The interface or interfaces igno... | 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. | [
"Configuring Multiple VLAN Registration Protocol (MVRP) on Switches",
"Example: Configuring Automatic VLAN Administration Using MVRP on MX Series Routers",
"Understanding Multiple VLAN Registration Protocol (MVRP) for Dynamic VLAN Registration",
"Configuring Multiple VLAN Registration Protocol (MVRP) to Manag... |
reject (Security) | reject {
profile redirect-profile-name;
ssl-proxy {
profile-name ssl-proxy-profile-name;
}
} | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then] | Block the service at the firewall. The device drops the packet and sends a TCP reset (RST) segment to
the source host for TCP traffic and an ICMP “destination unreachable, port unreachable” message (type
3, code 3) for UDP traffic. For types of traffic other than TCP and UDP, the device drops the packet
without notifyi... | [
{
"name": "profile",
"desc": "Profile for redirect HTTP/HTTPS traffic."
},
{
"name": "SSL-proxy",
"desc": "SSL proxy profile for decrypt HTTPS traffic."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. Starting in Junos OS Release 19.2, options profile and
ssl-proxy are added. | [
"Security Policies Overview"
] |
reject-unauthorized-ipv6cp | reject-unauthorized-ipv6cp; | [edit protocols ppp-service] | Configure the router to reject any IPv6 Control Protocol (IPv6CP) negotiation messages on dynamic
interfaces when no appropriate IPv6 address or prefix has been received from AAA. IPv6CP negotiation
attempts are also rejected when only a Framed-IPv6-Prefix attribute is received but router
advertisement is not enabled i... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Avoiding Negotiation of IPv6CP in the Absence of an Authorized Address"
] |
rejoin-timeout (Aggregated Multiservices) | rejoin-timeout rejoin-timeout; | [edit interfaces interface-name load-balancing-options member-failure-options drop-member-
traffic] | Configure the time by when failed members (members in the DISCARD state) should rejoin the aggregated
Multiservices (AMS) interface automatically. All members that do not rejoin by the configured time are
moved to the INACTIVE state and the traffic meant for each of the members is dropped.
If multiple members fail arou... | [
{
"name": "rejoin-timeout",
"desc": "Time, in seconds, by which a failed member must rejoin."
}
] | 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.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Understanding Aggregated Multiservices Interfaces",
"Example: Configuring an Aggregated Multiservices Interface (AMS)"
] |
relay (AMT Protocol) | relay {
accounting;
family {
inet {
anycast-prefix ip-prefix/<prefix-length>;
local-address ip-address;
}
}
secret-key-timeout minutes;
tunnel-devicesvalue ;
tunnel-limit number;
unicast-stream-limitnumber;
} | [edit logical-systems logical-system-name protocols amt],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols amt],
[edit protocols amt],
[edit routing-instances routing-instance-name protocols amt] | Configure the protocol address family, secret key timeout, and tunnel limit for Automatic Multicast
Tunneling (AMT) relay functions.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring the AMT Protocol"
] |
relay (IGMP) | relay {
defaults {
(accounting | no-accounting);
group-policy [ policy-names ];
query-interval seconds;
query-response-interval seconds;
robust-count number;
ssm-map ssm-map-name;
version version;
}
} | [edit logical-systems logical-system-name statement-name protocols igmp amt],
[edit logical-systems logical-system-name routing-instances routing-instance-name statement-name
protocols igmp amt],
[edit protocols igmp amt],
[edit routing-instances routing-instance-name statement-name protocols igmp amt] | Configure default Automatic Multicast Tunneling (AMT) interface attributes.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Default IGMP Parameters for AMT Interfaces"
] |
relay-agent-interface-id (DHCP Local Server) | relay-agent-interface-id; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 authentication username-include],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 group group-name authentication user... | Specify that the DHCPv6 Relay Agent Interface-ID option (option 18) in the client PDU name is
concatenated with the username during the subscriber authentication or DHCP client authentication
process. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Creating Unique Usernames for DHCP Clients"
] |
relay-agent-interface-id (DHCPv6 Relay Agent Username) | relay-agent-interface-id; | [edit forwarding-options dhcp-relay dhcpv6 authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 group group-name authentication username-include],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6 authentication
username-include],
[edit logical-systems logical-sys... | Specify that the DHCPv6 Relay Agent Interface-ID option (option 18) in the client PDU name is
concatenated with the username during the subscriber authentication process. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"DHCPv6 Relay Agent Overview",
"Creating Unique Usernames for DHCP Clients"
] |
relay-agent-interface-id (DHCPv6 Relay Agent) | relay-agent-interface-id {
include-irb-and-l2;
keep-incoming-interface-id ;
no-vlan-interface-name;
prefix prefix;
use-interface-description (logical | device);
use-option-82 <strict>;
use-vlan-id;
} | [edit forwarding-options dhcp-relay dhcpv6],
[edit forwarding-options dhcp-relay dhcpv6 group group-name],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6 ...],
[edit logical-systems logical-system-name forwardin... | Insert the DHCPv6 Relay Agent Interface-ID option (option 18) in DHCPv6 packets destined for the
DHCPv6 server.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
Support at the [edit ... dual-stack-group dual-stack-group-name] hierarchy level introduced in Junos OS
Release 15.1. | [
"Extended DHCP Relay Agent Overview",
"DHCPv6 Relay Agent Overview",
"Inserting DHCPv6 Interface-ID Option (Option 18) In DHCPv6 Packets"
] |
relay-agent-option | relay-agent-option; | [edit forwarding-options helpers bootp],
[edit logical-systems routing-instances instance-name forwarding-options helpers bootp],
[edit routing-instances instance-name forwarding-options helpers bootp] | Enable the DHCP relay agent information option which allows DHCP to forward information from
clients on different VRF routing instances. The functionality is described in RFC 3046, DHCP Relay
Agent Information Option. For the Junos OS implementation, the DHCP option number is 82, and the
suboption ID is 1. The suboptio... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0. | [
"Configuring Routers, Switches, and Interfaces as DHCP and BOOTP Relay Agents"
] |
relay-agent-option-79 | relay-agent-option-79; | [edit forwarding-options dhcp-relay dhcpv6] | 21.2R1
Starting with Junos OS Release 21.2R1, QFX Series switches support the relay-agent-option-79 CLI
statement in a stateless DHCPv6 relay configuration. You can configure stateless DHCPv6 relay using
the forward-only CLI statement at the [edit forwarding-options dhcp-relay dhcpv6] hierarchy level. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Inserting the DHCPv6 Client MAC Address Option (Option 79) In DHCPv6 Packets"
] |
relay-agent-remote-id (DHCP Local Server) | relay-agent-remote-id; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 authentication username-include],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 group group-name authentication user... | Specify that the DHCPv6 Relay Agent Remote-ID option (option 37) in the client PDU name is
concatenated with the username during the subscriber authentication or DHCP client authentication
process. In order to generate an ASCII version of the username, the router concatenates only the
remote-id portion of option 37 to ... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6.
For MX Series routers only, enterprise-id and remote-id options introduced in Junos OS Release 12.3R3.
For MX Series routers only, the enterprise-id and remote-id options are obsoleted starting in Junos OS
Releases 12.3R7, 13.2R4, 13.3R2, and 14.1R1. | [
"Creating Unique Usernames for DHCP Clients"
] |
relay-agent-remote-id (DHCPv6 Relay Agent Username) | relay-agent-remote-id; | [edit forwarding-options dhcp-relay dhcpv6 authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 group group-name authentication username-include],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name],
[edit logical-systems logical-system-name forwarding-options dhcp-relay... | Specify that the DHCPv6 Relay Agent Remote-ID option (option 37) in the client PDU name is
concatenated with the username during the subscriber authentication or client authentication process.
In order to generate an ASCII version of the username, the router concatenates only the remote-id
portion of option 37 to the u... | [] | 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.
For MX Series routers only, enterprise-id and remote-id options introduced in Junos OS Release 12.3R3.
For MX Series routers only, the enterprise-id and remote-id options are obsoleted starting in Junos OS
Releases 12.3R7, 13.2R4, 13.3R2, and 14.1R1.
Support at the [edit .... | [
"DHCPv6 Relay Agent Overview",
"Creating Unique Usernames for DHCP Clients"
] |
relay-agent-remote-id (DHCPv6 Relay Agent) | relay-agent-remote-id {
include-irb-and-l2;
keep-incoming-remote-id ;
no-vlan-interface-name;
prefix prefix;
use-interface-description (logical | device);
use-option-82 <strict>;
use-vlan-id;
} | [edit forwarding-options dhcp-relay dhcpv6],
[edit forwarding-options dhcp-relay dhcpv6 group group-name],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6 ... ],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options dhcp-relay dhcpv6 ... ],
... | 21.2R1
Starting with Junos OS Release 21.2R1, QFX Series switches support the relay-agent-remote-id CLI
statement in a stateless DHCPv6 relay configuration. You can configure stateless DHCPv6 relay using
the forward-only CLI statement at the [edit forwarding-options dhcp-relay dhcpv6] hierarchy level. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Extended DHCP Relay Agent Overview",
"DHCPv6 Relay Agent Overview",
"DHCPv6 Relay Agent Options",
"Configuring DHCPv6 Relay Agent Options"
] |
relay-agent-subscriber-id (DHCP Local Server) | relay-agent-subscriber-id; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 authentication username-include],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 group group-name authentication user... | Specify that the DHCPv6 Relay Agent Subscriber-ID option (option 38) in the client PDU name is
concatenated with the username during the subscriber authentication process. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Creating Unique Usernames for DHCP Clients"
] |
relay-agent-subscriber-id (DHCPv6 Relay Agent) | relay-agent-subscriber-id; | [edit forwarding-options dhcp-relay dhcpv6 authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 group group-name authentication username-include],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6 authentication
username-include],
[edit logical-systems logical-sys... | Specify that the DHCPv6 Relay Agent Subscriber-ID option (option 38) in the client PDU name is
concatenated with the username during the subscriber authentication process. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"DHCPv6 Relay Agent Overview",
"Creating Unique Usernames for DHCP Clients"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.