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 |
|---|---|---|---|---|---|---|---|
route-monitoring | route-monitoring {
none;
loc-rib;
post-policy {
exclude-non-eligible;
}
pre-policy {
exclude-non-feasible;
}
rib-out {
post-policy;
pre-policy;
}
} | [edit logical-systems logical-system-name protocols bgp bmp],
[edit logical-systems logical-system-name protocols bgp group group-name bmp],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address bmp],
[edit logical-systems logical-system-name routing-options bmp],
[edit logical-syste... | Specify whether BMP should send pre-policy route monitoring messages, post-policy route monitoring
messages, both types of messages, or none at all. The pre-policy can be configured to exclude routes
that are non-feasible for the decision process (for example, a route loop). The post-policy can be
configured to exclude... | [
{
"name": "none",
"desc": "Explicitly disables BMP route monitoring. Default: If you configure the route-monitoring statement at the [edit routing-options bmp] hierarchy level, the default option is pre-policy. NOTE: If post-policy or pre-policy is not configured explicitly, then the default mode pre-polic... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51-D15.
rib-out option introduced in Junos OS Release 19.1R1.
loc-rib option introduced in Junos OS Release 19.2R1. | [
"Configuring BGP Monitoring Protocol Version 3"
] |
route-record | route-record; | [edit logical-systems logical-system-name routing-options],
[edit routing-options] | Export the AS path and routing information to the traffic sampling process.
Before you can perform flow aggregation, the routing protocol process must export the AS path and
routing information to the sampling process.
NOTE: Starting with Junos OS Release 15.1, when you commit a minor configuration
change, the routing ... | [] | 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. | [
"Enabling Flow Aggregation",
"Junos OS Services Interfaces Library for Routing Devices"
] |
route-refresh-priority | route-refresh-priority (expedited | priority priority-queue-number (1-16)); | [edit logical-systems logical-system-name protocols bgp family family-name sub-family],
[edit logical-systems logical-system-name protocols bgp group group-name family family-name sub-
family],
[edit protocols bgp family family-name sub-family],
[edit protocols bgp group group-name family family-name sub-family],
[edit... | Within BGP route prioritization, the route-refresh-priority statement allows you to set specific priority
levels for BGP routes that are to be refreshed. The route-refresh-priority statement can be configured for
BGP neighbors during BGP configuration, or for sub-families within the following address families:
•
evpn
•... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Understanding BGP Route Prioritization"
] |
route-suppression (DHCP Local Server and Relay Agent) | route-suppression (access | access-internal | destination); | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit forwarding-options dhcp-relay group group-name],
[edit forwarding-options dhcp-relay dhcpv6 group group-name],
[edit logical-systems logical-system-name ...],
[edit logical-systems logical-system-name routing-instances routing-inst... | Configure the jdhcpd process to suppress the installation of access, access-internal, or destination
routes during client binding.
NOTE: You cannot suppress access-internal routes when the subscriber is configured
with both IA_NA and IA_PD addresses over IP demux interfaces—the IA_PD route relies
on the IA_NA route for... | [
{
"name": "access",
"desc": "(DHCPv6 only) Suppress installation of access routes. You can use the access and access-internal options in the same statement for DHCPv6."
},
{
"name": "access-internal",
"desc": "In a DHCPv4 hierarchy, suppress installation of both access-internal and destination r... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Preventing DHCP from Installing Access, Access-Internal, and Destination Routes by Default"
] |
route-target (Protocols BGP) | route-target {
accepted-prefix-limit {
maximum number;
teardown <percentage> <idle-timeout (forever | time-in-minutes)>;
drop-excess <percentage>;
hide-excess <percentage>;
}
advertise-default;
external-paths number;
prefix-limit {
maximum number;
tear... | [edit logical-systems logical-system-name protocols bgp family],
[edit logical-systems logical-system-name protocols bgp group group-name family],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address family],
[edit logical-systems logical-system-name routing-instances routing-instan... | Limit the number of prefixes advertised on BGP peers specifically to the peers that need the updates. | [
{
"name": "advertise-default",
"desc": "Advertise default routes and suppress more specific routes."
},
{
"name": "external-paths number",
"desc": "Number of external paths accepted for route filtering."
}
] | 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 an Export Policy for BGP Route Target Filtering for VPNs",
"Example: Configuring Proxy BGP Route Target Filtering for VPNs"
] |
route-target (Protocols MVPN) | route-target {
export-target {
target target-community;
unicast;
}
import-target {
target {
target-value;
receiver target-value;
sender target-value;
}
unicast {
receiver;
sender;
}
}
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
mvpn],
[edit routing-instances routing-instance-name protocols mvpn] | Enable you to override the Layer 3 VPN import and export route targets used for importing and
exporting routes for the MBGP MVPN NLRI.
Default
The multicast VPN routing instance uses the import and export route targets configured for the Layer 3
VPN. | [] | 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. | [
"Configuring VRF Route Targets for Routing Instances for an MBGP MVPN"
] |
route-target-filter | route-target-filter destination {
group group-name;
local;
neighbor address;
} | [edit logical-systems logical-system-name routing-options rib bgp.rtarget.0 static],
[edit routing-options rib bgp.rtarget.0 static] | Statically configure route target filtering. Route target filtering allows you to distribute VPN routes to
only the routers that need them. In VPN networks without route target filtering configured, BGP
distributes all static VPN routes to all of the VPN peer routers. You can add static routes to the
bgp.rtarget.0 rout... | [
{
"name": "destination",
"desc": "Allows you to specify the static route destination. This value must be in the format x:y/ len. The x value is either an IP address or an AS number followed by an optional L to indicate a 4 byte AS number, and y is a number (for example, 123456L:100/64)."
},
{
"name"... | 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 Static Route Target Filtering for VPNs",
"Reducing Network Resource Use with Static Route Target Filtering for VPNs"
] |
route-target-prefix-count | route-target-prefix-count countorhigher; | [edit logical-systems name policy-options policy-statement name from],
[edit logical-systems name policy-options policy-statement name term name from],
[edit policy-options policy-statement name from],
[edit policy-options policy-statement name term name from] | Number of BGP prefixes limit | [
{
"name": "count",
"desc": "Number of BGP prefixes limit Range: 0 through 10000000"
},
{
"name": "orhigher",
"desc": "Match higher or equal values"
}
] | [none specified]
Release Information | [] | |
route-timeout (Protocols RIP) | route-timeout seconds; | [edit logical-systems logical-system-name protocols rip],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip],
[edit logical-systems logical-system-name protocols rip group group-name],
[edit logical-systems logical-system-name protocols rip group group-name neighbor neighbo... | Configure the route timeout interval for RIP. If a route is not refreshed after being installed in the routing
table by the specified timeout interval, the route is marked as invalid and is removed from the routing
table after the hold-down period expires. | [
{
"name": "seconds",
"desc": "Estimated time to wait before making updates to the routing table."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Example: Configuring RIP Timers",
"RIP Demand Circuits Overview"
] |
route-timeout (Protocols RIPng) | route-timeout seconds; | [edit logical-systems logical-system-name protocols ripng],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ripng],
[edit protocols ripng],
[edit routing-instances routing-instance-name protocols ripng] | Configure the route timeout interval for RIPng. | [
{
"name": "seconds",
"desc": "Estimated time to wait before making updates to the routing table."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6.
Support for routing instances introduced in Junos OS Release 9.0. | [
"Example: Configuring RIPng Update Interval"
] |
router-advertisement (Dynamic Profiles) | router-advertisement {
interface interface-name {
current-hop-limit number;
default-lifetime seconds;
(managed-configuration | no-managed-configuration);
max-advertisement-interval seconds;
min-advertisement-interval seconds;
(other-stateful-configuration | no-other... | [edit dynamic-profiles protocols] | Enable router advertisement in a dynamic client profile or a dynamic service profile.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"IPv6 WAN Link Addressing with NDRA",
"Dynamic Router Advertisement Configuration Overview"
] |
router-advertisement | router-advertisement {
interface interface-name {
current-hop-limit current-hop-limit;
default-lifetime seconds;
dns-search-list name {
lifetime seconds;
}
dns-server-address name {
lifetime seconds;
}
downstream name;
downstrea... | [edit logical-systems name protocols],
[edit protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "accept-current-hop-limit-max",
"desc": "(Optional) Current hop limit acceptable maximum for incoming RA. Range: 1 through 255 units."
},
{
"name": "accept-current-hop-limit-min",
"desc": "(Optional) Current hop limit acceptable minimum for incoming RA. Range: 1 through 255 units."
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring IPv6 Interfaces and Enabling Neighbor Discovery",
"Secure IPv6 Neighbor Discovery"
] |
router-advertisement-guard | router-advertisement-guard {
interface interface-name {
mark-interface (trusted | block);
policy policy-name (stateful | stateless);
}
vlans (vlan-name | all) {
policy policy-name (stateful | stateless);
}
policy policy-name {
accept {
match-list {
... | [edit forwarding-options access-security] | Configure IPv6 Router Advertisement (RA) guard. In an IPv6 deployment, RA guard protects against
rogue RA messages generated either maliciously or unintentionally by unauthorized or improperly
configured routers connecting to the network segment. An RA guard policy is used to validate incoming
RA messages on the basis ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D55. | [
"Understanding IPv6 Router Advertisement Guard",
"Configuring Stateful IPv6 Router Advertisement Guard"
] |
router-discovery | router-discovery {
disable;
address address {
(advertise | ignore);
(broadcast | multicast);
(ineligible | priority number);
}
interface interface-name {
lifetime seconds;
max-advertisement-interval seconds;
min-advertisement-interval seconds;
}
tr... | [edit logical-systems logical-system-name protocols],
[edit protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | 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 the ICMP Protocol for Discovering Gateways to Other Networks",
"Example: Configuring the ICMP Protocol for Discovering Gateways to Other Networks"
] |
router-id | router-id address; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options] | Specify the routing device’s IP address.
The router identifier is used by BGP and OSPF to identify the routing device from which a packet
originated. The router identifier usually is the IP address of the local routing device. The router ID is
chosen based on a specific hierarchy. The router uses the manually configure... | [
{
"name": "address",
"desc": "IP address of 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. | [
"Examples: Configuring External BGP Peering",
"Examples: Configuring Internal BGP Peering"
] |
routing (System Processes) | routing {
force-32-bit | force-64-bit | auto-64-bit;
} | [edit system processes],
[edit logical-systems logical-system name system processes] | Configure routing protocols process (rpd) mode.
Default
force-32-bit mode is used in Junos 15.1F2 and prior releases
auto-64-bit mode is used starting in Junos 15.1F3 | [
{
"name": "auto-64-bit",
"desc": "(Optional) Enable to use 64-bit mode. If the system is 64-bit capable and has at least 16 GB of RAM, then auto-64-bit will cause the Routing Engine to run in 64-bit mode. Otherwise, it will run in 32-bit mode. NOTE: This option is not applicable for logical systems. Startin... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3 R4. | [
"Disabling Junos OS Processes"
] |
routing-engine (Chassis Redundancy) | routing-engine slot-number (backup | disabled | master); | [edit chassis redundancy] | Configure Routing Engine redundancy.
Default
By default, the Routing Engine in slot 0 is the primary Routing Engine and the Routing Engine in slot 1 is
the backup Routing Engine. | [
{
"name": "slot-number",
"desc": "Specify the slot number (0 or 1)."
},
{
"name": "master",
"desc": "Routing Engine in the specified slot is the primary."
},
{
"name": "backup",
"desc": "Routing Engine in the specified slot is the backup."
},
{
"name": "disabled",
"desc":... | 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"
] |
routing-engine (Chassis) | routing-engine {
on-disk-failure (Chassis Routing Engine)
{
No Link Title (halt | reboot);
}
disk {
ssd-series ssd-series-name {
id id-num {
id-threshold id-threshold-value;
id-value (norm | raw);
id-flag (high | low);
... | [edit chassis] | Configure a Routing Engine to halt or reboot automatically when a hard disk error occurs. A hard disk
error may cause a Routing Engine to enter a state in which it responds to local pings and interfaces
remain up, but no other processes are responding. Rebooting or halting prevents this. You can also
configure the devi... | [
{
"name": "disk",
"desc": "Configure health check parameters for the SSD."
},
{
"name": "ssd-series ssd-series-name",
"desc": "Specify the SSD series name."
},
{
"name": "id id-num",
"desc": "Specify the ID of the SSD smart attribute for which you are configuring the health check. Yo... | 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.
The disk-failure-action statement added in Junos OS Release 9.0. | [
"Enable Routing Engine to Reboot on Hard Disk Errors"
] |
routing-engine (SNMP Resource Level) | routing-engine {
resource <cpu | memory | open-files-count | process-count | storage | temperature |
traceoptions > ;
{
interval <interval in secs>;
moderate-threshold <percentage level>;
high-threshold <percentage level>;
critical-threshold <percentage level>;
action ... | [edit snmp health-monitor routing-engine] | 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": "interval",
"desc": "Monitoring interval in seconds."
},
{
"name": "moderate-threshold",
"desc": "Percentage of moderate threshold level resource utilization."
},
{
"name": "high-threshold",
"desc": "Percentage of high-threshold level resource utilization."
},
{
"na... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. Statement modified in Junos OS Release
15.1X49-D10. | [] |
routing-engine | routing-engine {
on-disk-failure {
disk-failure-action (halt | reboot);
}
} | [edit chassis]
[edit chassis interconnect-device name],
[edit chassis node-group name] | Configure a Routing Engine to halt or reboot automatically when a hard disk error occurs. A hard disk
error may cause a Routing Engine to enter a state in which it responds to local pings and interfaces
remain up, but no other processes are responding. Rebooting or halting prevents this. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Enabling a Routing Engine to Reboot on Hard Disk Errors",
"Junos OS High Availability User Guide"
] |
routing-engine-mode (CSDS) | routing-engine-mode; | [edit services traffic-load-balance] | Enable Routing Engine (RE)-based health-check for CSDS Traffic Orchestrator (CSDS-TO). | [] | 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. | [] |
routing-engine-profile | routing-engine-profile profile-name {
fields {
field-name;
}
file filename;
interval minutes;
start-time time;
} | [edit accounting-options] | Create a Routing Engine profile to collect selected Routing Engine statistics and write them to a file in
the /var/log directory. | [
{
"name": "profile-name",
"desc": "Name of the Routing Engine statistics profile."
},
{
"name": "start-time",
"desc": ""
},
{
"name": "time",
"desc": "(Optional) Specify the start time in yyyy-mm-dd.hh:mm local time format for the accounting profile. Sometimes, if the time at which t... | 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. | [
"Configure the Routing Engine Profile"
] |
routing-engine-services | routing-engine-services; | [edit services service-set service-set service-set-options] | When configuring a Routing Engine-based captive portal service, specify the service set options to apply
to a service set. The services interfaces on the Routing Engine are identified with an si- prefix (for
example, si-1/1/0). The si- interface contains all redirect and rewrite traffic and services for the Routing
Eng... | [] | 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.
Support for Next Gen Services introduced in Junos OS Release 19.3R2. | [
"HTTP Redirect Service Overview",
"Configuring MS-MPC-Based or MX-SPC3-Based Static HTTP Redirect Services",
"Configuring MS-MPC-Based or MX-SPC3-Based Converged HTTP Redirect Services",
"Configuring Routing Engine-Based, Static HTTP Redirect Services",
"Configuring Routing Engine-Based, Converged HTTP Redi... |
routing-header | routing-header {
header-type {
match (equal | greater-than | less-than | not-equal);
value header-value;
}
} | [edit set security idp custom-attack attack-name attack-type signature protocol ipv6 extension-
header] | Specify the IPv6 routing header type. The routing-header option inspects the routing-header type field
and reports a custom attack if a match with the specified value is found. The routing-header option
supports the following routing header types: routing-header-type0, routing-header-type1, and so on. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
routing-instance (Access LDAP) | routing-instance routing-instance-name; | [edit access ldap-server server-address],
[edit access profile profile-name ldap-server server-address] | Configure the routing instance used to send LDAP packets to the LDAP server. A routing instance is a
collection of routing tables, the interfaces contained in the routing tables, and the routing protocol
parameters that control the information in the routing tables. | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance."
}
] | 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"
] |
routing-instance (Access RADIUS) | routing-instance routing-instance-name; | [edit access radius-server server-address],
[edit access profile profile-name radius-server server-address] | Configure the routing instance used to send RADIUS packets to the RADIUS server. A routing instance
is a collection of routing tables, the interfaces contained in the routing tables, and the routing protocol
parameters that control the information in the routing tables. | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance."
}
] | secret—To view this statement in the configuration.
secret-control—To add this statement to the configuration. | Statement modified in Release 8.5 of Junos OS. | [
"Firewall User Authentication Overview"
] |
routing-instance (Advanced Policy-Based Routing) | routing-instance name ; | [edit security advance-policy-based-routing profile profile-name rule rule-name then] | Specify a specific routing instance to which the device sends the matched packets.
When traffic arrives at the specified zone or interface, it is matched by the advanced policy-based
routing (APBR) profile (application profile). The application profile matches applications and application
groups and if the matching ru... | [
{
"name": "name",
"desc": "Specify the name of the routing instance."
}
] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | [
"Example: Configuring Advanced Policy-Based Routing for Application-Aware Traffic Management",
"Solution",
"Understanding Advanced Policy-Based Routing"
] | |
routing-instance (Diameter Peer) | routing-instance routing-instance-name ; | [edit diameter peer peer-name] | Specify a routing instance for a Diameter peer. Alternatively, you can include the logical-system
statement at the [edit diameter peer peer-name] hierarchy level to configure a logical and routing instance. | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance."
}
] | 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 Peers"
] |
routing-instance (Diameter Transport) | routing-instance routing-instance-name ; | [edit diameter transport transport-name] | Specify a routing instance for the Diameter transport layer connection. | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance."
}
] | 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 the Diameter Transport"
] |
routing-instance (Event Scripts) | routing-instance routing-instance-name; | [edit event-options event-script file filename] | Configure the routing instance you want to use to update automation scripts. To use a management
instance, configure the management-instance statement along with the routing-instance statement, thus
enabling event scripts to use the non-default management routing instance mgmt_junos when
refreshing the scripts. | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance. For the management instance, use mgmt_junos. Otherwise, you can specify any routing instance name. NOTE: You must also define the routing instance under the [edit routing-instances] hierarchy level."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"management-instance",
"Management Interface in a Non-Default Instance"
] |
routing-instance (Flow Monitoring) | routing-instance instance-name; | [edit forwarding-options sampling family (inet | inet6 | mpls) output flow-server hostname],
[edit forwarding-options sampling instance sampling-instance-name family (inet | inet6 | mpls)
output flow-server hostname] | Configure a non-default VPN routing and forwarding (VRF) instance through which flow collectors can
be reachable for inline flow monitoring. You cannot configure a flow collector to be reachable through
non-default VRF instances for version 5 and version 8 flows. You can configure a flow collector to be
reachable throu... | [
{
"name": "instance-name",
"desc": "Name of a routing instance that has been configured at the [edit routing-instance]"
}
] | 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.
Statement introduced in Junos OS Evolved Release 24.2R1 at the [edit forwarding-options sampling
instance sampling-instance-name family (inet | inet6 | mpls) output flow-server hostname] hierarchy
level. | [
"Directing Traffic Sampling Output to a Server Running the cflowd Application",
"Understand Inline Active Flow Monitoring"
] |
routing-instance (Forwarding-options Analyzer) | routing-instance {
instance-name {
bridge-domain bridge-domain-name;
}
vlan (vlan-id | vlan-name);
} | [edit forwarding-options analyzer analyzer-name input egress],
[edit forwarding-options analyzer analyzer-name input ingress],
[edit forwarding-options analyzer analyzer-name output] | Configure routing instance. | [
{
"name": "instance-name",
"desc": "Name of the routing instance."
}
] | 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. | [] |
routing-instance (Interfaces) | routing-instance {
destination routing-instance-name;
} | [edit interfaces interface-name unit logical-unit-number tunnel],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
tunnel] | Specify the destination routing instance that points to the routing table containing the tunnel
destination address.
Default
The default Internet routing table inet.0. | [] | 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 Tunnel Interfaces for Routing Table Lookup"
] |
routing-instance (JET Scripts) | routing-instance routing-instance-name; | [edit system extensions extension-service application file filename] | Configure the routing instance you want to use to update Automation scripts. To use a management
instance, configure the management-instance statement along with the routing-instance statement, thus
enabling JET scripts to use the non-default management routing instance mgmt_junos when refreshing
the scripts. | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance. For the management instance, use mgmt_junos. Otherwise, you can specify any routing instance name. NOTE: You must also define the routing instance under the [edit routing-instances] hierarchy level."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"management-instance",
"Management Interface in a Non-Default Instance"
] |
routing-instance (Junos Telemetry Interface) | routing-instance routing-instance-name; | [edit services analytics export-profile export-profile-name] | For legacy gRPC dialout connections, configure a routing instance in an export profile. You can only
configure the routing instance in an export profile for legacy remote procedure call (gRPC) dial-out
connections. An error is returned if the routing instance configured is used with User Datagram Protocol
(UDP) transpo... | [
{
"name": "routing-instance",
"desc": "A routing instance to be used for gRPC transport."
}
] | Edit | Statement introduced in Junos OS Evolved 24.2R1 (for IPv6) on
Statement introduced in Junos OS Evolved 24.2R1 (for IPv6) on ACX7024, ACX7024X, ACX7100-32C,
ACX7100-48L, ACX7332, ACX7348, ACX7509, ACX7900, PTX10001-36MR, PTX10003, PTX10004,
PTX10008, PTX10016, QFX5130E-32CD, QFX5130-48C, QFX5130-48CM, QFX5220, and QFX5... | [
"Using gRPC Dial-Out for Secure Telemetry Collection"
] |
routing-instance (L2TP Destination) | routing-instance routing-instance-name {
drain;
} | [edit services l2tp destination address ip-address] | Specify the routing instance in which the destination is created. | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"L2TP Tunnel Switching For Multiple-Domain Networks"
] |
routing-instance (L2TP Tunnel Destination) | routing-instance routing-instance-name {
drain;
} | [edit services l2tp tunnel name tunnel-name address ip-address] | Specify the routing instance in which the tunnel to the destination address is created. | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"L2TP Tunnel Switching For Multiple-Domain Networks"
] |
routing-instance (NAPT) | routing-instance ri-name; | [edit logical-systems name tenants name security nat source pool],
[edit security nat source pool],
[edit services nat source pool],
[edit tenants name security nat source pool] | The routing instance associated with the pool when it is used for inline NAPT. | [
{
"name": "ri-name",
"desc": "Routing instance name"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1 on MX304 and MX10K (with LC9600 line card) | [] |
routing-instance (PCC Action Profiles) | routing-instance {
downlink downlink-vrf-name;
uplink uplink-vrf-name;
} | [edit unified-edge pcef pcc-action-profiles profile-name steering],
[edit services pcef pcc-action-profiles profile-name steering] | Specify the routing instance that a PCC action profile uses for steering traffic. | [
{
"name": "downlink downlink-vrf-name",
"desc": "Use the specified name of the routing instance for downlink traffic (to the access side) or the predefined dynamic interface variable ."
},
{
"name": "uplink uplink-vrf-name",
"desc": "Use the specified name of the routing instance for uplink traf... | 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 16.1.
Support at the [edit services pcef pcc-action-profiles profile-name steering] 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 introduc... | [
"Configuring Policy and Charging Control Action Profiles For Junos OS Subscriber Aware",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Configuring Policy and Charging Control Action Profiles for Subscriber Management",
"Understanding Application-Aware Po... |
routing-instance (Port Mirroring) | routing-instance instance-name; | [edit forwarding-options] analyzer name output]
[edit forwarding-options port-mirroring [instance name] family inet output interface name] | Configure a port mirroring instance. You do not specify an input for this instance. Instead, you, create a
firewall filter that specifies the required traffic and directs it to the mirror. This instance type is useful for
controlling which types of traffic should be mirrored. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [] |
routing-instance (PPPoE Service Name Tables) | routing-instance routing-instance-name; | [edit protocols pppoe service-name-tables table-name service service-name],
[edit protocols pppoe service-name-tables table-name service service-name agent-specifier aci
circuit-id-string ari remote-id-string] | Use in conjunction with the dynamic-profile statement at the same hierarchy levels to specify the routing
instance in which to instantiate a dynamic PPPoE interface. You can associate a routing instance with a
named service entry, empty service entry, or any service entry configured in a PPPoE service name table, or
wi... | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance in which the router instantiates the dynamic PPPoE"
}
] | 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 PPPoE Service Name Tables",
"Assigning a Dynamic Profile and Routing Instance to a Service Name or ACI/ARI Pair for Dynamic",
"PPPoE Interface Creation"
] |
routing-instance (RPM) | routing-instance instance-name; | [edit services monitoring rpm owner name test name] | Specify the routing instance used by the probes. The routing instance is also applicable for control
connection.
NOTE: The media interface from where the TWAMP control and test or data packets
arrive and exit the si- logical interface must be a part of the same routing instance. | [
{
"name": "instance-name",
"desc": "Routing instance configured at the [edit routing-instance] hierarchy level."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.3 for EX Series switches.
Statement introduced in Junos OS Release 13.2 for PTX Series Packet Transport routers.
Support at the [edit services rpm twamp client control-connection control-client-name] hierarchy level
introduced ... | [
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches",
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
routing-instance (Security Content Security) | routing-instance name; | [edit security utm feature-profile anti-virus sophos-engine pattern-update]
[edit security utm feature-profile web-filtering juniper-enhanced server]
[edit security utm feature-profile web-filtering websense-redirect profile wr server]
[edit security utm feature-profile anti-virus sophos-engine server]
[edit security u... | Configure the routing instance name. A routing instance is a collection of routing tables, interfaces, and
routing protocol parameters. The set of interfaces belongs to the routing tables, and the routing protocol
parameters control the information in the routing tables. Each routing instance has a unique name. | [
{
"name": "name",
"desc": "Specify the name of the routing instance."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D90.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Support for Avira engine added in Junos OS Release 18.4R1. | [] |
routing-instance (Security Destination NAT) | routing-instance (routing-instance-name | default); | [edit security nat destination pool pool-name] | Specify the routing instance on which to perform the route lookup for the address in the pool. It is not a
mandatory flag.
A destination NAT pool that does not specify a specific routing instance will default to the routing
instance of the ingress zone. You can configure a NAT pool to exist in the default routing insta... | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance."
},
{
"name": "default",
"desc": "Use the default routing instance."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. | [] |
routing-instance (Security Source NAT) | routing-instance routing-instance-name; | [edit security nat source pool pool-name] | Specify the routing instance to which the pool is bound. It is not a mandatory flag. If the user does not
configure the routing instance, by default the pool belongs to routing-instance inet.0. | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. | [] |
routing-instance (Services) | routing-instance routing-instance-name{
family inet {
address ip-address;
}
} | [edit services app-engine compute-cluster compute-cluster-name local-management],
[edit services app-engine virtual-machines instance instance-name local-management] | (Optional) Configure a routing instance for the JunosV App Engine infrastructure. Packets are restricted
to the specified routing instance. By specifying the routing instance, the JunosV App Engine
infrastructure can be made to operate in a non-default routing instance. This feature ensures that
JunosV App Engine traff... | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [] |
routing-instance (SNMP) | routing-instance routing-instance-name {
source-address address;
} | [edit snmp community community-name],
[edit snmp community community-name logical-system logical-system-name],
[edit snmp trap-group group],
[edit snmp trap-options] | Specify a routing instance for SNMPv1 and SNMPv2 trap targets. All targets configured in the trap
group use this routing instance.
If the routing instance is defined within a logical system, include the logical-system logical-system-name
statement at the [edit snmp community community-name] hierarchy level and specify ... | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3.
Added to the [edit snmp community community-name] hierarchy level in Junos OS Release 8.4.
Added to the [edit snmp community community-name logical-system logical-system-name] hierarchy level in Junos
OS Release 9.1. | [
"Specify a Routing Instance in an SNMPv1 or SNMPv2c Community"
] |
routing-instance (SNMPv3) | routing-instance routing-instance-name; | [edit snmp v3 target-address target-address-name] | Specify a routing instance for an SNMPv3 trap target. | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [] |
routing-instance (Syslog) | routing-instance routing-instance-name; | [edit system syslog],
[edit system syslog host ip-address] | Configure the routing instance name for the routing instance that you want the syslog client to use. If
you want to use the reserved non-default management routing instance mgmt_junos, make sure you
configure the management-instance statement.
NOTE: You must also define the routing instance you want to use under the [e... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R1. | [
"Management Interface in a Non-Default Instance",
"System Logging and Routing Instances"
] |
routing-instance (System Scripts) | routing-instance routing-instance-name; | [edit system scripts commit file filename],
[edit system scripts op file filename],
[edit system scripts snmp file filename] | Configure the routing instance you want to use to update automation scripts. To use a management
instance, configure the management-instance statement along with the routing-instance statement, thus
enabling commit, op, and SNMP scripts to use the non-default management routing instance
mgmt_junos when refreshing the s... | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance. For the management instance, use mgmt_junos. Otherwise, you can specify any routing instance name. NOTE: You must also define the routing instance under the [edit routing-instances] hierarchy level."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"management-instance",
"Management Interface in a Non-Default Instance"
] |
routing-instance (Tunnel Profile) | routing-instance routing-instance-name; | [edit access tunnel-profile profile-name tunnel tunnel-id] | Specify a routing instance for a tunnel. | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"L2TP LAC Tunneling for Subscribers"
] |
routing-instance | routing-instance routing-instance-name; | [edit firewall family inet filter filter-name term
term-name then] | Specify a specific virtual routing instance to which the switch sends matched packets. | [
{
"name": "routing-instance-name",
"desc": "Name of a virtual routing instance."
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Example: Using Filter-Based Forwarding to Route Application Traffic to a Security Device",
"Configuring Virtual Routing Instances on EX Series Switches",
"Understanding Filter-Based Forwarding for EX Series Switches"
] |
routing-instance-access | [edit snmp]
routing-instance-access {
access-list {
routing-instance;
routing-instance restrict;
}
} | [edit snmp] | Enable SNMP managers in routing instances other than the default routing instance to access SNMP
information. For information about the access-list option, see "access-list" on page 1854. | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [
"Enable SNMP Access over Routing Instances"
] |
routing-instance-list (TWAMP) | routing-instance-list {
instance-name {
port number;
}
} | [edit services rpm twamp server] | Configure the Two-Way Active Measurement Protocol (TWAMP) servers on specific routing instances,
instead of associating the TWAMP server at the system-level to apply to all routing instances configured
on a router. The default routing instance is Internet routing table inet.0. If you do not specify a routing
instance, ... | [
{
"name": "instance-name",
"desc": "Name of the routing instance, a maximum of 31 characters."
},
{
"name": "number",
"desc": "Port number."
}
] | system—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring TWAMP on MX, M, T, and PTX Series Routers and EX4300 Series Switches"
] |
routing-instance-name (circuit-id) | routing-instance--name; | [edit vlans vlan-name forwarding-options dhcp-security option-82 circuit-id prefix] | Specify that the routing instance name used by the VLAN is included with the circuit ID suboption in the
DHCP option 82 information that is inserted by the switch into the packet header of a DHCP request
before it forwards or relays the request to a DHCP server | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Setting Up DHCP Option 82 on the Switch with No Relay (ELS)",
"Understanding DHCP Option 82"
] |
routing-instance-name (DHCP Local Server) | routing-instance-name; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server authentication username-include],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 authentication username-include],
[edit logic... | Specify that the routing instance name be concatenated with the username during the subscriber
authentication or DHCP client authentication process. No routing instance name is concatenated if the
configuration is in the default routing instance. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Specifying Authentication Support"
] |
routing-instance-name (DHCP Relay Agent) | routing-instance-name; | [edit forwarding-options dhcp-relay authentication username-include],
[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 auth... | Specify that the routing instance name is concatenated with the username during the subscriber
authentication or client authentication process. No routing instance name is concatenated if the
configuration is in the default routing instance. Use the statement at the [edit ... dhcpv6] hierarchy levels
to configure DHCPv... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
Support at the [edit ... dhcpv6] hierarchy levels 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.
The tenants option is introduced in Junos OS Release 18.4R1. | [
"Specifying Authentication Support",
"Creating Unique Usernames for DHCP Clients"
] |
routing-instance-name (Static Subscribers) | routing-instance-name; | [edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers authentication username-include],
[edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers group group-name authentication username-inclu... | Specify that the name of the routing instance is included as part of the username created for all static
subscribers or for the static subscribers in the specified group. The group version of the statement takes
precedence over the global version. The username is also sent to RADIUS in the Access-Request
message. | [] | 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. | [
"Subscribers over Static Interfaces Configuration Overview",
"Configuring the Static Subscriber Global Username",
"Configuring the Static Subscriber Group Username"
] |
routing-instance-name | routing-instance-name; | [edit bridge-domains bridge domain name forwarding-options dhcp-security option-82 circuit-id
prefix] | Specify that the routing instance name be included within the optional prefix for the circuit ID suboption
in the DHCP option 82 information that is inserted by the switch into the packet header of a DHCP
request before it forwards or relays the request to a DHCP server. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10. | [
"Setting Up DHCP Option 82 on the Switch with No Relay (ELS)",
"Configuring DHCP Option 82 on a Router with Bridge Domain"
] |
routing-instances (CoS) | routing-instances routing-instance-name {
classifiers {
dscp (classifier-name | default);
dscp-ipv6 (classifier-name | default);
exp (classifier-name | default);
ieee-802.1 (classifier-name | default);
no-default;
}
policy-map policy-map-name {
}
} | [edit class-of-service] | For routing instances with VRF table labels enabled, apply a DSCP, MPLS EXP, or IEEE 802.1 classifier to
the routing instance. You can apply the default classifier or one that is previously defined.
Apply the no-default option to disable the application of any default classifier to the routing instance.
You can also a... | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance."
},
{
"name": "classifier-name",
"desc": "Name of the behavior aggregate DSCP, MPLS EXP, or IEEE 802.1 classifier."
},
{
"name": "policy-map-name",
"desc": "Name of the policy map that defines the rewrite rules... | 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.
no-default and policy-map options added in Junos OS Release 16.1. | [
"Configuring a Custom Forwarding Class for Each Queue",
"Applying Custom MPLS EXP Classifiers to Routing Instances in Layer 3 VPNs"
] |
routing-instances (Dynamic Profiles) | routing-instances routing-instance-name {
interface interface-name;
multicast-snooping-options {
}
routing-options {
access {
route prefix {
metric route-cost;
next-hop next-hop;
preference route-distance;
tag route-tag... | [edit dynamic-profiles]
[edit logical-systems logical-system-name ] | Dynamically configure an additional routing entity for a router in a dynamic client profile or a dynamic
service profile. | [
{
"name": "routing-instance-name",
"desc": "The routing instance variable ($junos-routing-instance). The routing instance"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6.
Support at the logical-systems hierarchy level was introduced in Junos OS Release 14.2. | [
"Configuring a Dynamic Profile for use by a Retailer in the DHCPv4 Solution"
] |
routing-instances (JDAF) | routing-instances [ routing-instance-names ]; | [edit services jdaf] | Configure the routing instances on which Juniper Distributed Application Framework (JDAF) is enabled.
If the jdaf statement is not configured, then JDAF is disabled. | [
{
"name": "routing-instances",
"desc": ""
},
{
"name": "[ routing-instance-names ]",
"desc": "Name or names of routing instances for JDAF clients. If multiple names are being configured, these can be set as an open set of values."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [] |
routing-instances (Logical Systems) | routing-instances routing-instance-name { ... } | [edit],
[edit logical-systems logical-system-name] | Configure an additional routing entity for a router or switch. You can create multiple instances of BGP,
IS-IS, OSPF, OSPF version 3 (OSPFv3), and RIP for a router or switch.
Default
Routing instances are disabled for the router or switch. | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance, a maximum of 31 characters. The remaining"
},
{
"name": "non-forwarding-vrf",
"desc": "Enable this option to not create a routing and forwarding (VRF) table for local or"
}
] | 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 EVPN Routing Instances",
"Configuring Routing Instances on PE Routers in VPNs"
] |
routing-instances (Multiple Routing Entities) | routing-instances routing-instance-name { ... } | [edit],
[edit logical-systems logical-system-name] | Configure an additional routing entity for a router. You can create multiple instances of BGP, IS-IS, OSPF,
OSPFv3, and RIP for a router. You can also create multiple routing instances for separating routing
tables, routing policies, and interfaces for individual wholesale subscribers (retailers) in a Layer 3
wholesale... | [
{
"name": "routing-instance-name",
"desc": ""
},
{
"name": "remote-vtep-list",
"desc": "Configure static remote VXLAN tunnel endpoints."
},
{
"name": "remote-vtep-v6-list",
"desc": "Configure static IPv6 remote VXLAN tunnel endpoints."
}
] | 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.
remote-vtep-v6-list statement introduced in Junos OS Release 17.3 for MX Series routers with MPC and
MIC interfaces. | [
"Example: Configuring Interprovider Layer 3 VPN Option A",
"Example: Configuring Interprovider Layer 3 VPN Option B",
"Example: Configuring Interprovider Layer 3 VPN Option C"
] |
routing-instances (RPM) | routing-instances instance-name; | [edit services rpm bgp],
[edit services rpm bgp logical-system logical-system-name] | Specify the routing instance used by the probes. | [
{
"name": "instance-name",
"desc": "A routing instance configured at the [edit routing-instances] 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 7.6. | [
"Configuring BGP Neighbor Discovery Through RPM"
] |
routing-instances | routing-instances routing-instance-name {
instance-type virtual-router;
interface interface-name;
} | [edit] | Configure a virtual routing entity. | [
{
"name": "routing-instance-name",
"desc": "Name for this routing instance."
}
] | routing—To view this statement in the configuration.routing-control—To add this statement to the
configuration. | Statement introduced in Junos OS Release 9.2. | [
"Example: Using Virtual Routing Instances to Route Among VLANs on EX Series Switches",
"Configuring Virtual Routing Instances on EX Series Switches"
] |
routing-interface | routing-interface routing-interface-name; | [edit bridge-domains bridge-domain-name],
[edit logical-systems logical-system-name bridge-domains bridge-domain-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name bridge-domains
bridge-domain-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name] | (MX Series routers only) Specify a routing interface to include in a bridge domain or a VPLS routing
instance.
When you configure routing-interface irb.x, the VPLS connection comes up, even if no customer edge
(CE) interfaces are configured. This works with one site configured, but not when multiple sites
(multisite) a... | [
{
"name": "routing-interface-name",
"desc": "Name of the routing interface to include in the bridge domain or the VPLS"
}
] | 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. | [
"Configuring a Bridge Domain",
"Configuring a Layer 2 Virtual Switch"
] |
routing-options (Dynamic Profiles) | routing-options {
access {
route prefix {
metric route-cost;
next-hop next-hop;
preference route-distance;
tag route-tag;
tag2 route-tag2;
}
}
access-internal {
route subscriber-ip-address {
qualified-next-hop u... | [edit dynamic-profiles profile-name],
[edit dynamic-profiles profile-name routing-instances $junos-routing-instance] | Configure protocol-independent routing properties in a dynamic client profile.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | 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.
Support at the [edit dynamic-profiles profile-name routing-instances $junos-routing-instance] hierarchy level
introduced in Junos OS Release 10.1. | [
"Configuring Dynamic Access Routes for Subscriber Management",
"Configuring Dynamic Access-Internal Routes for DHCP and PPP Subscribers"
] |
routing-options (Junos Node Slicing) | routing-options {
static {
route route {
next-hop next-hop;
}
}
} | [edit ] | Configure static routes for JDM. | [
{
"name": "route route",
"desc": "Static route destination."
},
{
"name": "next-hop next-hop",
"desc": "Specify the address of the next hop to destination."
}
] | root | Statement introduced in Junos OS Release 17.2. | [] |
routing-options (QFabric System) | routing-options {
multicast {
no-make-before-break;
}
} | [edit fabric] | (QFabric systems only) Set routing options in a QFabric system. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Understanding the QFabric System Data Plane"
] |
routing-options | routing-options { ... }
For information on the complete list of options under routing-options, see [edit routing-options] and
Protocol-Independent Routing Properties User Guide. | [edit],
[edit logical-systems logical-system-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit tenants tenant-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | Configure protocol-independent routing properties. | [] | 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.
The [edit tenants tenant-name routing-instances routing-instance-name] hierarchy level introduced in
Junos OS Release 18.3R1. | [
"[edit routing-options]",
"Protocol-Independent Routing Properties User Guide"
] |
routing-options-max-ecmp | maximum-ecmp (16 | 32 | 64 | 96 | 128 | 160 | 192 | 224 | 256 | 288 | 320 | 352 | 384 | 416 |
448 | 480 | 512); | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit logical-systems logical-system-name routing-options],
[edit logical-systems logical-system-name tenants tenant-name routing-instances routing-instance-
name routing-options],
[edit routing-instances routing-instan... | On cRPD, you can control the maximum ECMP limit for nexthops using routing-options maximum-
ecmp. You can use routing-options maximum-ecmp on other platforms but the ECMP limit specified
using routing-options maximum-ecmp must be less than chassis maximum-ecmp.
Default
The default value of ECMP next-hop limit on cRPD i... | [] | routing—To view this statement in the configuration. | Statement introduced in Junos OS Release 21.1R1. | [
"Protocol-Independent Routing Properties User Guide"
] |
routing-service (Dynamic Profiles) | routing-service (disable <:$junos-routing-services> | enable<:$junos-routing-services>); | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-name] | Enable configuration of additional routing protocols required by client connections on dynamically
created enhanced subscriber management interfaces.
NOTE: When clients use only the standard access-internal routes, access routes, and
framed routes, you do not need to configure routing services. In other words, the rout... | [
{
"name": "disable",
"desc": "Disable routing services for all subscribers instantiated on the interface by the profile."
},
{
"name": "disable:$junos-routing-services",
"desc": "Prevent routing services from being enabled or disabled by the value of the Routing-Services VSA (26-212) for the sub... | interface | Statement introduced in Junos OS Release 18.4R1. | [
"Junos OS Enhanced Subscriber Management",
"Juniper Networks VSAs Supported by the AAA Service Framework",
"AAA Access Messages and Supported RADIUS Attributes and Juniper Networks VSAs for Junos OS",
"Predefined Variables in Dynamic Profiles"
] |
rp | rp {
auto-rp {
(announce | discovery | mapping);
(mapping-agent-election | no-mapping-agent-election);
}
bidirectional {
address address {
group-ranges {
destination-ip-prefix</prefix-length>;
}
hold-time seconds;
prior... | [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] | Configure the routing device as an actual or potential RP. A routing device can be an RP for more than
one group.
The remaining statements are explained separately. See CLI Explorer.
Default
If you do not include the rp statement, the routing device can never become the RP. | [] | 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 PIM Sparse Mode"
] |
rp-register-policy | rp-register-policy [ policy-names ]; | [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] | Apply one or more policies to control incoming PIM register messages. | [
{
"name": "policy-names",
"desc": "Name of one or more import policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring Register Message Filters on a PIM RP and DR"
] |
rp-set | rp-set {
address address <forward-msdp-sa>;
} | [edit logical-systems logical-system-name protocols pim local family (inet | inet6) anycast-pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
local family (inet | inet6) anycast-pim],
[edit protocols pim local family (inet | inet6) anycast-pim],
[edit routing-instanc... | Configure a set of rendezvous point (RP) addresses for anycast RP. You can configure up to 15 RPs.
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 7.4. | [
"Example: Configuring PIM Anycast With or Without MSDP"
] |
rpc | rpc {
program-number rpc-program-number;
} | [edit security idp custom-attack attack-name attack-type chain protocol-binding],
[edit security idp custom-attack attack-name attack-type signature protocol-binding] | Allow IDP to match the attack for a specified remote procedure call (RPC) program number. | [
{
"name": "program-number rpc-program-number",
"desc": "RPC program number."
}
] | 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. | [] |
rpc-program-number (Applications) | rpc-program-number number; | [edit applications application application-name ]
[edit applications application application-name term term-name] | Specify the remote procedure call (RPC) or Distributed Computing Environment (DCE) value. | [
{
"name": "number",
"desc": "RPC or DCE program value."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement modified in Junos OS Release 8.5. | [
"Security Policy Application Sets Overview"
] |
rpc-program-number | rpc-program-number number; | [edit applications application application-name] | Remote procedure call (RPC) or Distributed Computing Environment (DCE) value. | [
{
"name": "number",
"desc": "RPC or DCE program value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"ALG Descriptions",
"Configuring an RPC Program Number",
"Examples: Configuring Application Protocols",
"Verifying the Output of ALG Sessions"
] |
rpf-check (Dynamic Profiles) | rpf-check {
fail-filter filter-name;
mode loose;
} | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family] | Reduce forwarding of IP packets that might be spoofing and address by checking whether traffic is
arriving on an expected path that the sender would use to reach the destination. You can include this
statement with the inet protocol family only. When the traffic passes the check, it is forwarded to the
destination addr... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Unicast RPF in Dynamic Profiles for Subscriber Interfaces",
"Configuring Unicast RPF Strict Mode"
] |
rpf-check | rpf-check; | [edit interfaces interface-name unit logical-unit-number family inet],
[edit interfaces interface-name unit logical-unit-number family inet6] | Enable a reverse-path forwarding (RPF) check on unicast traffic.
On EX3200 and EX4200 switches, enable a reverse-path forwarding (RPF) check on unicast traffic
(except ECMP packets) on all ingress interfaces.
On EX4300 switches, enable a reverse-path forwarding (RPF) check on unicast traffic, including ECMP
packets, on... | [
{
"name": "fail-filter",
"desc": "A filter to evaluate when packets are received on the interface. If the RPF check fails, this"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for interface ps0 (pseudowire subscriber logical interface device) added in Junos OS Release
15.1. | [
"Configuring Unicast RPF Strict Mode",
"Configuring Unicast RPF Loose Mode",
"Configuring a Pseudowire Subscriber Logical Interface Device",
"Example: Configuring Unicast RPF (On a Switch)"
] |
rpf-check-policy (Routing Options RPF) | rpf-check-policy [ policy-names ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options multicast] | Apply policies for disabling RPF checks on arriving multicast packets. The policies must be correctly
configured. | [
{
"name": "policy-names",
"desc": "Name of one or more multicast RPF check policies."
}
] | 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. | [
"Example: Configuring RPF Policies"
] |
rpf-check-policy (Routing Options) | rpf-check-policy policy; | [edit logical-systems logical-system-name routing-options multicast],
[edit routing-options multicast] | Enable you to control whether a reverse path forwarding (RPF) check is performed for a source and
group entry before installing a route in the multicast forwarding cache. This makes it possible to use
point-to-multipoint LSPs to distribute multicast traffic to Protocol Independent Multicast (PIM) islands
situated downs... | [
{
"name": "policy",
"desc": "Name of the RPF check routing policy."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0. | [
"Configuring a Multicast RPF Check Policy for Point-to-Multipoint LSPs"
] |
rpf-loose-mode-discard | rpf-loose-mode-discard {
family {
inet;
inet6;
}
} | [edit forwarding-options] | Configure unicast reverse path forwarding (unicast RPF) loose mode with the ability to discard packets
with the source address pointing to the discard next hop. | [
{
"name": "inet",
"desc": "IPv4 address family."
},
{
"name": "inet6",
"desc": "IPv6 address family."
}
] | interface-control—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Understanding Unicast RPF (Routers)"
] |
rpf-selection | rpf-selection {
group group-address {
sourcesource-address {
next-hop next-hop-address;
}
wildcard-source {
next-hop next-hop-address;
}
}
prefix-list prefix-list-addresses {
source source-address {
next-hop next-hop-address;
... | [edit routing-instances routing-instance-name protocols pim]
[edit protocols pim] | Configure the PIM RPF next-hop neighbor for a specific group and source for a VRF routing instance.
NOTE: Starting in Junos OS 17.4R1, you can configure rpf-selection statement at the
[edit protocols pim] hierarchy level.
The remaining statements are explained separately. See CLI Explorer.
Default
If you omit the rpf-s... | [
{
"name": "source-address",
"desc": "Specific source address for the PIM group."
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in JUNOS Release 10.4. | [
"Example: Configuring PIM RPF Selection"
] |
rpf-vector (PIM) | rpf-vector {
policy (rpf-vector)[ policy-name];
} | [edit dynamic-profiles name protocols pim],
[edit logical-systems name protocols pim],
[edit logical-systems name routing-instances name protocols pim],
[edit protocols pim],
[edit routing-instances name protocols pim] | This feature provides a way for PIM source-specific multicast (SSM) to resolve Vector Type Length (TLV)
for multicast in a seamless Multiprotocol Label Switching (MPLS) networks. In other words, it enables
PIM to build multicast trees through an MPLS core. rpf-vector implements RFC 5496, Reverse Path
Forwarding (RPF) ... | [
{
"name": "policy",
"desc": "Create a filter policy to determine whether or not to apply rpf-vector."
}
] | routing | Statement introduced in Junos OS Release 17.3R1. | [
"policy (rpf-vector)"
] |
rpm (Interfaces) | rpm (client client | server server | twamp-client twamp-client | twamp-server twamp-server); | [edit interfaces interface-name unit logical-unit-number] | Associate an RPM or TWAMP client (router or switch that originates RPM or TWAMP probes) or RPM
or TWAMP server with a specified interface.
NOTE: The TWAMP client is applicable only for si- interfaces. | [
{
"name": "client",
"desc": "Identifier for RPM client router or switch."
},
{
"name": "server",
"desc": "Identifier for RPM server."
},
{
"name": "twamp-client",
"desc": "Identifier for RPM TWAMP client router."
},
{
"name": "twamp-server",
"desc": "Identifier for RPM TW... | 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. | [
"Configuring RPM Timestamping on MX, M, T, and PTX Series Routers and EX Series Switches"
] |
rpm (Services) | rpm {
owner name {
test test-name {
data-fill data;
data-size size;
destination-port port;
dscp-code-points dscp-bits;
history-size size;
moving-average-size number;
offload-type {
none;
pfe-t... | [edit services monitoring] | 23.4R1 Evo
Starting in Junos OS Evolved Release 23.4R1 for the ACX7024, ACX7100, ACX7332, ACX7348,
ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD,
QFX5130-48C, QFX5130-48CM, QFX5220, and QFX5700, you can configure tcp-ping, http-get, and
http-metadata-get probe types for RPM.
21.4R1
Starti... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Evolved Release 20.1R1.
traps option introduced in Junos OS Evolved Release 21.2R1.
source-address option and the local-link sub-option of the target-address option for TWAMP Light test
sessions introduced in Junos OS Release 21.4R1.
tcp... | [
"Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, and MX Series",
"Routers",
"Configuring BGP Neighbor Discovery Through RPM"
] |
rpm-scale | rpm-scale {
destination {
interface interface-name.logical-unit-number;
subunit-cnt subunit-cnt;
}
source {
address-base ipv4-address-base;
count ipv4-count;
step ipv4-step;
}
source-inet6 {
address-base ipv6-address-base;
count ipv6-count;
... | [edit services rpm probe owner test test-name] | Configure the generation of multiple IPv4 RPM tests for a probe owner. Starting in Junos OS Release
18.2R1, you can also configure the generation of multiple IPv6 RPM tests for a probe owner. Tests are
generated for multiple combinations of source and target addresses, which are incremented based on
your configuration.... | [
{
"name": "interface-name.logical-unit-",
"desc": ""
},
{
"name": "number",
"desc": "The services interface that is generating RPM probes and the logical unit number that is used for the first test that is generated."
},
{
"name": "ipv4-address-base",
"desc": "The IPv4 source or targ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1. | [
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches"
] |
rpm-tracking | rpm-tracking {
route destination-prefix {
metric metric;
next-hop next-hop {;
rpm-probe name rpm-test test-name;
}
preference preference;
tag tag;
}
} | [edit routing-instances name routing-options],
[edit routing-options] | RPM-tracked static routes are coupled with a given RPM test instance. Routes can be installed or
removed according to the results of the given RPM test. When installed, these routes are automatically
given a preference of 1, and so are preferred over static routes that may already exist with the same
prefix.
If the RP... | [
{
"name": "route destination-prefix",
"desc": "(Required) Configure an RPM-tracked static route. Must be a IPv4 or IPv6 destination prefix."
},
{
"name": "next-hop next-hop",
"desc": "(Required) Configure a next-hop address. Must be a IPv4 or IPv6 address. You can configure up to 16 multiple pat... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Support introduced in Junos OS Release 18.4 R1.
next-hop option added in Junos OS Release 19.1R1.
preference and tag options added in Junos OS Release 20.4R1. | [
"Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, and MX Series",
"Routers"
] |
rpt-spt | rpt-spt; | [edit logical-systems profile-name routing-instances instance-name protocols mvpn mvpn-mode],
[edit routing-instances instance-name protocols mvpn mvpn-mode] | Use rendezvous-point trees for customer PIM (C-PIM) join messages, and switch to the shortest-path
tree after the source is known. | [] | 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. | [] |
rsh | rsh {
disable;
traceoptions {
flag {
all {
extensive
}
}
}
} | [edit logical-systems name security alg],
[edit logical-systems name tenants name security alg],
[edit security alg],
[edit services alg],
[edit tenants name security alg] | 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": "disable",
"desc": "Disable the RSH ALG. By default, the RSH ALG is disabled."
},
{
"name": "traceoptions",
"desc": "Configure RSH ALG tracing options."
},
{
"name": "flag",
"desc": "Trace operation to perform."
},
{
"name": "all",
"desc": "Trace all events."
... | 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.
The tenant option is introduced in Junos OS Release 18.3R1. | [
"Understanding the RSH ALG"
] |
rst-invalidate-session | rst-invalidate-session; | [edit security flow tcp-session] | Enable the device to mark a session for immediate termination when it receives a TCP reset (RST)
message. By default, this feature is disabled.
NOTE: On SRX Series Firewalls with rst-invalidate-session configured the invalidation of
the session occurs immediately whereas without rst-invalidate-session configured the
se... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Understanding Traffic Processing on Security Devices"
] |
rst-sequence-check | rst-sequence-check; | [edit security flow tcp-session] | Verify that the TCP sequence number in a TCP segment with the RST bit enabled matches the previous
sequence number for a packet in that session or is the next higher number incrementally. If the
sequence number does not match either of these expected numbers, the device drops the packet and
sends the host a TCP ACK mes... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Understanding Traffic Processing on Security Devices"
] |
rstp | [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] | Configure Rapid Spanning Tree Protocol (RSTP). RSTP is defined in the IEEE 802.1D-2004 specification
and is used to prevent loops in Layer 2 networks, which results in shorter convergence times than those
provided by basic Spanning Tree Protocol (STP).
VSTP and RSTP can be configured concurrently. You can selectively c... | [] | 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.
bpdu-block-on-edge statement added in Junos OS Release 9.4.
bpdu-timeout-action statement added in Junos OS Release 9.4.
Support for logic systems added in Junos OS Release 9.6.
Statement updated in Junos OS Release 15.1 for EX Series and QFX Series switches to support
conf... | [
"Configuring Rapid Spanning Tree Protocol",
"Understanding RSTP",
"Configuring RSTP on EX Series Switches (CLI Procedure)",
"Example: Faster Convergence and Improved Network Stability with RSTP on EX Series Switches"
] | |
rsvp | rsvp {
associated-bidirectional-lspsingle-sided-provisioning;
authentication-key (Protocols RSVP) authentication-key;
cross-credibility-cspf;
(disable | enable);
expand-flood-reflector-hop;
fast-rerouteoptimize-timer seconds;
graceful-deletion-timeout seconds;
graceful-restart (P... | [edit logical-systems name protocols],
[edit logical-systems name routing-instances name protocols],
[edit logical-systems name tenants name routing-instances name protocols],
[edit protocols],
[edit routing-instances name protocols],
[edit tenants name routing-instances name protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "cross-credibility-cspf",
"desc": "Enable path computation across credibility levels. The constraint path"
},
{
"name": "authentication key",
"desc": "Authentication key. Neighboring routers use the password to verify the authenticity"
},
{
"name": "graceful deletion timeout",
... | 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. | [
"Minimum RSVP Configuration",
"Example: Configuring MPLS on EX8200 and EX4500 Switches",
"Configuring MPLS on Provider Edge EX8200 and EX4500 Switches Using Circuit Cross-Connect",
"Configuring MPLS on EX8200 and EX4500 Provider Switches"
] |
rsvp-error-hold-time | rsvp-error-hold-time seconds; | [edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls] | Amount of time MPLS retains RSVP PathErr messages and considers them for CSPF computations. The
more time you configure, the more time a source node (ingress of an RSVP LSP) can have to learn about
the failures of its LSP by monitoring PathErr messages transmitted from downstream nodes.
Information from the PathErr mes... | [
{
"name": "seconds",
"desc": "Amount of time MPLS retains RSVP PathErr messages and considers them for CSPF"
}
] | 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. | [
"Improving Traffic Engineering Database Accuracy with RSVP PathErr Messages"
] |
rsvp-te (Protocols MVPN) | rsvp-te{
label-switched-path-template (Multicast){
(default-template | lsp-template-name);
}
static-lsp static-lsp;
} | [edit protocols mvpn inter-region-template template template-name all-regions],
[edit protocols mvpn inter-region-template template template-name region region-name] | Configure to unicast, broadcast, and multicast traffic flooding using point-to-multipoint LSPs. | [
{
"name": "static-lsp static-lsp",
"desc": "Create a static point-to-multipoint LSP and automatically include all of the neighbors in the routing instance."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 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"
] |
rsvp-te (Routing Instances Provider Tunnel Selective) | rsvp-te {
label-switched-path-template {
(default-template | lsp-template-name);
}
static-lsp lsp-name;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel],
[edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel selective group address source source-address],
[edit logical-systems logical-system-name routing-instances routing-inst... | Configure the properties of the RSVP traffic-engineered point-to-multipoint LSP for MBGP MVPNs.
The remaining statements are explained separately. See CLI Explorer.
NOTE: Junos OS Release 11.2 and earlier do not support point-to-multipoint LSPs with
next-generation multicast VPNs on MX80 routers. | [] | 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. | [
"Configuring Point-to-Multipoint LSPs for an MBGP MVPN"
] |
rsvp-te (Routing Instances Provider Tunnel) | rsvp-te {
label-switched-path-template {
(default-template | lsp-template-name);
}
static-lsp lsp-name;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel],
[edit routing-instances routing-instance-name provider-tunnel] | [
{
"name": "static-lsp lsp-name",
"desc": "Create a static point-to-multipoint LSP and automatically include all of the neighbors"
}
] | 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. | [
"Flooding Unknown Traffic Using Point-to-Multipoint LSPs in VPLS"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.