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 |
|---|---|---|---|---|---|---|---|
rsvp-te (Routing Options) | rsvp-te entry-name {
destination-networks network-prefix;
label-switched-path-template (Multicast) {
default-template;
template-name;
}
} | [edit logical-systems logical-system-name routing-options dynamic-tunnels tunnel-name],
[edit routing-options dynamic-tunnels tunnel-name] | Enable RSVP to automatically establish LSPs for any new PE router added to a full mesh of LSPs. To
enable this feature, you must configure the rsvp-te statement on all of the PE routers in the full mesh. | [
{
"name": "entry-name",
"desc": "Specify the entry for the RSVP tunnel."
}
] | 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. | [
"Configuring RSVP Automatic Mesh",
"Configuring Dynamic Point-to-Multipoint Flooding LSPs"
] |
rtf-prefix-list | rtf-prefix-list name route-targets | [edit logical-systems logical-system-name policy-options],
[edit logical-systems logical-system-name policy-options policy-statement policy-name term term-
name],
[edit policy-options],
[edit policy-options policy-statement policy-name term term-name] | Define a list of route target prefixes for use in a routing policy statement. These prefixes are only useful
for filtering routes in the bgp.rtarget.0 table.
The route target filtering prefix is in the format: AS number:route target extended community/length.
The first number represents the autonomous system (AS) of th... | [
{
"name": "name",
"desc": "Name that identifies the list of route target filtering prefixes. The name can contain letters,"
},
{
"name": "route-targets",
"desc": "List of route target filtering prefixes, one route target filter per line in the configuration."
}
] | 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 an Export Policy for BGP Route Target Filtering for VPNs",
"Configuring BGP Route Target Filtering for VPNs",
"Understanding Proxy BGP Route Target Filtering for VPNs",
"Understanding How to Define BGP Communities and Extended Communities",
"Routing Policies, Firewall Filters, and Traf... |
rtlog (Next Gen Services Global System Logging) | rtlog {
name {
apply-groups group-names;
apply-groups-except group-names;
flag name;
file filename,
no-remote-trace;
}
} | [edit services] | Enable global system logging for Next Gen Services.
traceoptions
Specify the options to include in the trace.
All other options are explained separtely. | [] | system | Statement introduced in Junos OS Release 19.3R2. | [
"Understanding Next Gen Services CGNAT Global System Logging",
"Enabling Global System Logging for Next Gen Services",
"Configuring System Logging to One or More Remote Servers for Next Gen Services",
"Configuring Local System Logging for Next Gen Services"
] |
rtp | rtp {
f-max-period number;
maximum-contexts number <force>;
port {
minimum port-number;
maximum port-number;
}
queues [ queue-numbers ];
} | [edit interfaces interface-name unit logical-unit-number compression],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
compression] | Configure the RTP properties for voice services traffic.
The remaining statements are described separately. | [] | 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 Compression of Voice Traffic"
] |
rts | rts (assert | de-assert | normal); | [edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options] | For EIA-530 and V.35 interfaces only, configure the to-DCE signal, request to send (RTS). | [
{
"name": "assert",
"desc": "The to-DCE signal must be asserted."
},
{
"name": "de-assert",
"desc": "The to-DCE signal must be deasserted."
},
{
"name": "normal",
"desc": "Normal RTS signal handling, as defined by the TIA/EIA Standard 530."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Serial Signal Handling"
] |
rts-polarity | rts-polarity (negative | positive); | [edit interfaces interface-name serial-options] | Configure RTS signal polarity. | [
{
"name": "negative",
"desc": "Negative signal polarity."
},
{
"name": "positive",
"desc": "Positive signal polarity."
}
] | 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 Serial Signal Polarities"
] |
rtsp | rtsp {
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 RTSP ALG. By default, the RTSP ALG is enabled."
},
{
"name": "traceoptions",
"desc": "Configure RTSP 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 RTSP ALG"
] |
rule (AACL Rule Set) | rule rule-name {
match-direction (input | output | input-output);
term term-name {
from {
application-group-any;
application-groups [ application-group-names ];
application-unknown;
applications [ application-names ];
destination-address addres... | [edit services aacl],
[edit services aacl rule-set rule-set-name] | Specify the rule the router uses when applying this service. | [
{
"name": "rule-name",
"desc": "Identifier for the collection of terms that constitute this rule."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring AACL Rules"
] |
rule (Advanced Policy-Based Routing) | rule rule-name {
disable-midstream-routing;
match {
category (juniper-enhanced-category | custom-category);
dynamic-application [system-application | any];
dynamic-application-group [system-application-group];
dscp dscp-value;
}
then {
application-services-bypass;... | [edit security advance-policy-based-routing profile profile-name] | Configure rules for the advanced policy-based routing (APBR) profile (application profile). Associate the
rule with one or more than one dynamic applications or application groups or URL categories as follows:
•
For matching the dynamic applications, APBR consults the application identification (AppID) and
application ... | [
{
"name": "disable-midstream-",
"desc": ""
},
{
"name": "routing",
"desc": "Selectively disable APBR in the middle of a session for a specific APBR rule."
},
{
"name": "match",
"desc": "Define a match criteria for matching the traffic in APBR profile rule."
},
{
"name": "cate... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D60. The option category is introduced in Junos OS
Release 18.3R1. Junos OS Release 19.3R1 supports the option dscp. Junos OS Release 20.1R1 supports
the option any for dynamic-application. | [
"Example: Configuring Advanced Policy-Based Routing for Application-Aware Traffic Management",
"Solution",
"Understanding Advanced Policy-Based Routing"
] |
rule (Application Firewall) | rule rule-name {
match {
dynamic-application [system-application];
dynamic-application-groups [system-application-group];
ssl-encryption (any | yes | no);
}
then {
deny {
block-message block-message;
}
permit permit;
reject {
bl... | [edit security application-firewall rule-sets name ] | Specify rules for application firewall.
You need to create rules to permit, reject, or deny traffic for dynamic applications to configure
application firewall rule sets within the security policy. The application firewall support in the policies
provides additional security control for dynamic applications.
Starting in... | [
{
"name": "match",
"desc": "Specify security rule match-criteria"
},
{
"name": "dynamic-application",
"desc": "Select dynamic applications as match criteria."
},
{
"name": "dynamic-application-group",
"desc": "Select dynamic applications group as match criteria."
},
{
"name":... | security | Statement introduced in Junos OS Release 11.1. Statement updated in Junos OS Release 12.1X44-D10
to include the ssl-encryption and reject options. The block-message options added in Junos OS Release
12.1X45-D10. | [
"Application Firewall Overview"
] |
rule (Application Identification) | rule rule-name {
address {
destination {
ip address</prefix-length>;
port-range {
tcp [ ports-and-port-ranges ];
udp [ ports-and-port-ranges ];
}
}
source {
ip address</prefix-length>;
port-range {
... | [edit services application-identification] | Define properties for application-identification rule processing. | [
{
"name": "rule-name",
"desc": "Unique identifier for the rule."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring APPID Rules"
] |
rule (Captive Portal Content Delivery) | rule rule-name {
match-direction (input | output | input-output);
term term-name {
from {
destination-address address <except>;
}
then {
accept;
insert tag-name tag-name tag-value tag-value;
redirect url;
rewrite destination-add... | [edit dynamic-profiles profile-name services captive-portal-content-delivery],
[edit services captive-portal-content-delivery] | Specify the rule the router uses when applying this service. Use the statement at the [edit services...]
hierarchy level for static CPCD. Use the statement at the [edit dynamic-profiles profile-name services...]
hierarchy level for converged services CPCD. | [
{
"name": "rule-name",
"desc": "Identifier for the collection of terms that constitute this rule."
}
] | services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
Support at the [edit dynamic-profiles profile-name services captive-portal-content-delivery rule rule-name term
term-name] hierarchy level added in Junos OS Release 17.2R1.
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... |
rule (casb-policy) | rules rule-name {
match {
application application-name {
activity activity-name {
[param-name param-value param-name param-value]
}
instance instance-name;
}
application-group application-group-nam... | [edit security casb casb-policy policy-name] | Configure Cloud Access Security Broker (CASB) policy rule. CASB policy rule includes set of match
criteria defining the conditions that must be satisfied to apply the policy and a set of actions to be
performed in case of a match—allow, deny, or log actions. | [
{
"name": "match",
"desc": ""
},
{
"name": "rule-name",
"desc": "Define a match criteria for matching the traffic in CASB policy rule. You can specify"
},
{
"name": "following:",
"desc": ""
},
{
"name": "application application-name",
"desc": "Enter the supported applicat... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.2R1. | [] |
rule (Destination NAT Next Gen Services) | rule rule-name {
match {
application [application-name]
destination-address (NAT Next Gen Services) (address | any-unicast);
destination-address-name address-name;
source-address (address | any-unicast);
source-address-name address-name;
}
}
then {
destinatio... | [edit services nat destination rule-set rule-set] | Configure a destination NAT rule, which translates the destination address of IP packets.
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 19.3R2. | [] |
rule (HTTP Header Enrichment for Tag Rule Set) | rule rule-name; | [edit services hcm tag-rule-set] | Specify the tag rule that you want to be a part of the tag rule set.
NOTE: The tag rule must already be defined at the [edit services hcm] hierarchy level. | [
{
"name": "rule-name",
"desc": "Name of the tag rule. To specify multiple tag rules, include the rule statement multiple times."
}
] | 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. | [
"Configuring HTTP Header Enrichment Overview"
] |
rule (IDS MS-DPC) | rule rule-name {
match-direction (input | output | input-output);
term term-name {
from {
application-sets set-name;
applications [ application-names ];
destination-address (address | any-unicast) <except>;
destination-address-range low minimum-value high... | [edit services ids],
[edit services ids rule-set rule-set-name] | Specify the rule the router uses when applying this service on the MS-DPC. | [
{
"name": "rule-name",
"desc": "Identifier for the collection of terms that constitute this rule."
}
] | 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 IDS Rules on an MS-DPC"
] |
rule (IDS MS-MPC) | rule {
match-direction (input | output | input-output);
term {
then {
aggregation (IDS) {
destination-prefix prefix-value | destination-prefix-ipv6 prefix-value;
source-prefix prefix-value | source-prefix-ipv6 prefix-value;
}
allow-ip-o... | [edit services ids ] | Configure network attack protection for a service set on an MS-MPC.
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 17.1. | [
"Configuring Protection Against Network Attacks on an MS-MPC"
] |
rule (Including in Rule Set) | rule rule-name; | [edit services application-identification rule-set rule-set-name] | Identify rules for inclusion in application rule set. | [
{
"name": "rule-name",
"desc": "Unique identifier for the rule."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring APPID Rules"
] |
rule (IP Reassembly) | rule rule-name {
match-direction direction;
} | [edit services ip-reassembly] | Configure an IP reassembly rule, which is used for inline IP reassembly on the inline services interface.
The IP reassembly rule can be attached to a service set to indicate that the service set is of type IP
reassembly. For inline IP reassembly, each rule must include the match-direction statement, which
specifies the... | [
{
"name": "rule-name",
"desc": "Name of the IP reassembly rule. Range: Up to 63 characters The remaining statement is 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 13.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 IP Inline Reassembly for L2TP",
"IP Packet Fragment Reassembly for L2TP Overview"
] |
rule (LRF) | rule lrf-rule-name {
then {
report {
collector collector-name;
template template-name;
time-limit time-interval;
volume-limit volume;
}
}
} | [edit services lrf profile profile-name] | Configure an LRF rule, which controls how data sessions are logged and reported. In this release, the
matching conditions for an LRF rule are identified in a static PCC rule, not in the LRF rule. | [
{
"name": "lrf-rule-name",
"desc": "Name of the LRF rule. Range: Up to 63 characters. 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 17.1.
Support for Next Gen Services introduced in Junos OS Release 19.3R1 on MX Series. | [
"Configuring Logging and Reporting for Junos OS Subscriber Aware",
"Configuring an LRF Profile for Subscribers",
"Configuring Logging and Reporting for Subscriber Management"
] |
rule (PCP) | rule rule-name {
match-direction (input | output);
term term-name {
from {
application-sets set-name;
applications [ application-name ];
destination-address address <except>;
destination-address-range high maximum-value low minimum-value <except>;
... | [edit services pcp] | Configure a rule to assign the port control protocol (PCP) server that handles selected traffic. PCP
enables hosts to operate servers for a long time (as in the case of a webcam) or a short time (for
example, while playing a game or on a phone call) when behind a NAT device, including when behind a
carrier-grade NAT op... | [
{
"name": "rule-name",
"desc": "Rule name The remaining statements are explained separately."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R1. | [
"Configuring Port Control Protocol"
] |
rule (Security Destination NAT) | rule rule-name {
description text;
match {
application {
[application];
any;
}
(destination-address ip-address| destination-address-name address-name);
destination-port (port-or-low <to high>);
protocol [protocol-name-or-number];
source-add... | [edit security nat destination rule-set rule-set-name] | Define a destination NAT rule. | [
{
"name": "rule-name",
"desc": "Name of the destination NAT rule."
},
{
"name": "description",
"desc": "Description of the destination NAT rule."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. The description option added in Junos OS Release 12.1.
Statement modified in Junos OS Release 12.1X45-D10. Statement modified in Junos OS Release
12.1X47-D10. | [] |
rule (Security Exempt Rulebase) | rule rule-name {
description text;
match (Security IDP Policy) {
attacks (Security IPS Rulebase) {
custom-attack-groups [attack-group-name];
custom-attacks [attack-name];
dynamic-attack-groups [attack-group-name];
predefined-attack-groups [attack-group-nam... | [edit security idp idp-policy policy-name rulebase-exempt] | Specify exempt rule to create, modify, delete, and reorder the rules in a rulebase. | [
{
"name": "rule-name",
"desc": "Name of the exempt rulebase rule."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
rule (Security IPS Rulebase) | rule rule-name {
description text;
match (Security IDP Policy) {
application (application-name | any | default);
attacks (Security IPS Rulebase) {
custom-attack-groups [attack-group-name];
custom-attacks [attack-name];
dynamic-attack-groups [attack-group-name]... | [edit security idp idp-policy policy-name rulebase-ips] | Specify IPS rule to create, modify, delete, and reorder the rules in a rulebase. | [
{
"name": "rule-name",
"desc": "Name of the IPS rulebase rule."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Starting in Junos OS Release 18.2R1, IDP policy is available within unified security policy. When IDP
policy is available within the unified security policy then the IDP polciy configurations are simplified.
Configuring source or destination address, source and destination-... | [] |
rule (Security Source NAT) | rule rule-name {
description text;
match {
application {
[application];
any;
}
(destination-address <ip-address> | destination-address-name <address-name>);
destination-port (port-or-low <to high>);
protocol [protocol-name-or-number];
sour... | [edit security nat source rule-set rule-set-name] | Define a source NAT rule. | [
{
"name": "rule-name",
"desc": "Name of the source NAT rule."
},
{
"name": "description",
"desc": "Description of the source NAT rule."
}
] | 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. The description option added in Junos OS Release 12.1.
Statement modified in Junos OS Release 12.1X45-D10. Statement modified in Junos OS Release
12.1X47-D10. | [] |
rule (Security Static NAT) | rule rule-name {
description text;
match {
(destination-address <ip-address> | destination-address-name <address-name>);
destination-port (port-or-low | <to high>);
source-address [ip-address];
source-address-name [ip-address-name];
source-port (port-or-low <to high>);
... | [edit security nat static rule-set rule-set-name] | Define a static NAT rule. | [
{
"name": "rule-name",
"desc": "Name of the static NAT rule."
},
{
"name": "Description",
"desc": "Description of the static NAT rule."
}
] | 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. The description option added in Junos OS Release 12.1.
Statement modified in Junos OS Release 12.1X45-D10. Statement modified in Junos OS Release
12.3X48-D25. | [] |
rule (Services CoS Next Gen Services) | rule rule-name {
match-direction (input | input-output | output);
policy policy-name {
match {
application [ application-names ];
destination-address address;
destination-address-range low minimum-value high maximum-value;
destination-port port-number;
... | [edit services cos] | Configure a services CoS rule, which specifies Differentiated Services (DiffServ) code point (DSCP)
marking and forwarding-class assignment for packets that are processed by a service set. The CoS rule
identifies the matching conditions for packet source and destination addresses and for packet
applications, and the ac... | [
{
"name": "match-direction",
"desc": ""
},
{
"name": "(input | input-output | output)",
"desc": "The direction in which the rule is matched."
},
{
"name": "input",
"desc": "Apply the rule match on input. If the CoS rule is assigned to an interface service set, input means traffic ent... | 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. | [
"Class of Service for Services PICs (Next Gen Services)"
] |
rule (Services CoS) | rule rule-name {
match-direction (input | output | input-output);
term term-name {
from {
application-sets set-name;
applications [ application-names ];
destination-address address;
destination-prefix-list list-name <except>;
source-address add... | [edit services cos],
[edit services cos rule-set rule-set-name] | Specify the rule the router uses when applying this service. | [
{
"name": "rule-name",
"desc": "Identifier for the collection of terms that constitute this rule."
}
] | 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 CoS Rules",
"Configuring CoS Rules on Services PICs"
] |
rule (Services NAT) | rule rule-name {
match-direction (input | output);
term term-name {
from {
application-sets set-name;
applications [ application-names ];
destination-address (address | any-unicast) <except>;
destination-address-range low minimum-value high maximum-value <... | [edit services nat],
[edit services nat rule-set rule-set-name] | Specify the rule the router uses when applying this service.
NOTE: You are limited to a maximum of 200 terms for a NAT rule that is applied to an
inline services (type si) interface. If you specify more than 200 terms, you will receive
following error when you commit the configuration:
[edit]
'service-set service-set... | [
{
"name": "rule-name",
"desc": "Identifier for the collection of terms that make up this rule. The remaining statements are explained separately."
}
] | 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. | [
"Network Address Translation Rules Overview"
] |
rule (Services Stateful Firewall) | rule rule-name {
match-direction (input | output | input-output);
term term-name {
from {
application-sets set-name;
applications [ application-names ];
destination-address (address | any-ipv4 | any-ipv6 | any-unicast) <except>;
destination-address-range ... | [edit services stateful-firewall],
[edit services stateful-firewall rule-set rule-set-name] | Specify the rule the router uses when applying this service. | [
{
"name": "rule-name",
"desc": "Identifier for the collection of terms that constitute this rule."
}
] | 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 Stateful Firewall Rules"
] |
rule (Softwire) | rule rule-name {
match-direction (input | output);
term term-name {
then {
(ds-lite ds-lite-softwire-concentrator | map-e name | v6rd v6rd-softwire-
concentrator);
}
}
} | [edit services softwire],
[edit services softwire rule-set rule-set-name] | Configure a rule to apply a softwire concentrator for a flow.
Softwire rules are supported on the MS-DPC, MS-100, MS-400, and MS-500 line cards. Starting in
Junos OS release 17.4R1, softwire rules for DS-Lite are supported on MX Series routers with MS-MPCs
and MS-MICs. | [
{
"name": "rule-name",
"desc": "Identifier for the collection of terms that constitute this rule."
},
{
"name": "input",
"desc": "Apply the rule match on the input side of the interface."
},
{
"name": "output",
"desc": "Apply the rule match on the output side of the 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.4.
map-e name option introduced in Junos OS Release 18.2R1 for MX Series Routers with MPC and MIC
interfaces. | [
"Configuring Softwire Rules"
] |
rule (Source NAT Next Gen Services) | rule rule-name {
match {
application [application-name]
destination-address (NAT Next Gen Services) address;
destination-address-name address-name;
source-address (address | any-unicast);
source-address-name address-name;
}
then {
source-nat {
clat... | [edit services nat source rule-set rule-set] | Configure a source NAT rule, which translates the source address of IP packets.
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 19.3R2. | [] |
rule | rule rule-name {
match-direction (input | output);
term term-name {
from {
destination-address address;
ipsec-inside-interface interface-name;
source-address address;
}
then {
anti-replay-window-size bits;
backup-remote-gateway ... | [edit services ipsec-vpn],
[edit services ipsec-vpn rule-set rule-set-name] | Specify the rule the router uses when applying this service. | [
{
"name": "rule-name",
"desc": "Identifier for the collection of terms that comprise this rule."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IPsec Rules",
"Configuring IPsec Rule Sets",
"Configuring Security Associations"
] |
rule-activation-time | rule-activation-time {
<day-of-week | day-of-month month>;
<hour:min>;
} | [edit unified-edge pcef pcc-time-of-day-profiles profile-name] | Specify the time of day, day of the week or day of the month, or month of the year to activate a PCC
rule or rulebase. You can specify the time of day, the day, or both. If you specify the day of the month,
you can also specify the month of the year, which results in the yearly activation of the rule or rulebase.
Use t... | [
{
"name": "day-of-week",
"desc": "(Optional) Day of the week on which to activate a PCC rule or rulebase."
},
{
"name": "day-of-month",
"desc": "(Optional) Day of the month on which to activate a PCC rule or rulebase. Syntax: DAYn, where n can be from 1 through 31, or Last-day-of-month, which d... | 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 Static Time-of-Day PCC Rule Activation and Deactivation in a Junos OS Subscriber",
"Aware PCEF Profile",
"Understanding Static Time-of-Day PCC Rule Activation and Deactivation"
] |
rule-deactivation-time | rule-deactivation-time {
<day-of-week | day-of-month month>;
<hour:min>;
} | [edit unified-edge pcef pcc-time-of-day-profiles profile-name] | Specify the time of day, day of the week or day of the month, or month of the year to deactivate a PCC
rule or rulebase. You can specify the time of day, the day, or both. If you specify the day of the month,
you can also specify the month of the year, which results in the yearly deactivation of the rule or
rulebase. U... | [
{
"name": "day-of-week",
"desc": "(Optional) Day of the week on which to deactivate a PCC rule or rulebase."
},
{
"name": "day-of-month",
"desc": "(Optional) Day of the month on which to deactivate a PCC rule or rulebase. Syntax: DAYn, where n can be from 1 through 31, or Last-day-of-month, whi... | 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 Static Time-of-Day PCC Rule Activation and Deactivation in a Junos OS Subscriber",
"Aware PCEF Profile",
"Understanding Static Time-of-Day PCC Rule Activation and Deactivation"
] |
rule-session-count-alarm (Security Destination NAT Rule Set) | rule-session-count-alarm (clear-threshold value | raise-threshold value): | [edit security nat destination rule-set rule-set-name rule rule-name then destination-nat] | Define session count alarm thresholds for a specific Network Address Translation (NAT) destination rule.
When the session count exceeds the upper (raise) threshold or falls below the lower (clear) threshold, an
SNMP trap is triggered. | [
{
"name": "clear-threshold value",
"desc": "Lower threshold at which an SNMP trap is triggered."
},
{
"name": "raise-threshold value",
"desc": "Upper threshold at which an SNMP trap is triggered. NOTE: If you enter a value for raise-threshold but not for clear-threshold, clear-threshold is autom... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10. | [] |
rule-session-count-alarm (Security Source NAT Rule Set) | rule-session-count-alarm (clear-threshold value | raise-threshold value): | [edit security nat source rule-set rule-set-name rule rule-name then source-nat ] | Define session count alarm thresholds for a specific Network Address Translation (NAT) source rule.
When the session count exceeds the upper (raise) threshold or falls below the lower (clear) threshold, an
SNMP trap is triggered. | [
{
"name": "clear-threshold value",
"desc": "Lower threshold at which an SNMP trap is triggered."
},
{
"name": "raise-threshold value",
"desc": "Upper threshold at which an SNMP trap is triggered. NOTE: If you enter a value for raise-threshold but not for clear-threshold, clear-threshold is autom... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10. | [] |
rule-session-count-alarm (Security Static NAT Rule Set) | rule-session-count-alarm (clear-threshold value | raise-threshold value); | [edit security nat static rule-set rule-set-name rule rule-name then static-nat ] | Define session count alarm thresholds for a specific static Network Address Translation (NAT) rule.
When the session count exceeds the upper (raise) threshold or falls below the lower (clear) threshold, an
SNMP trap is triggered. | [
{
"name": "clear-threshold value",
"desc": "Lower threshold at which an SNMP trap is triggered."
},
{
"name": "raise-threshold value",
"desc": "Upper threshold at which an SNMP trap is triggered. NOTE: If you enter a value for raise-threshold but not for clear-threshold, clear-threshold is autom... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10. | [] |
rule-set (Captive Portal Content Delivery) | rule-set rule-set-name {
[rule rule-name];
} | [edit services captive-portal-content-delivery] | Define a set of captive portal content delivery rules that the router uses when applying this service. This
statement is supported only for static CPCD; it is not supported for converged services CPCD. | [
{
"name": "rule-set-name",
"desc": "Identifier for the collection of rules that constitute this rule set."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
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... |
rule-set (Security Destination NAT) | rule-set rule-set-name {
description text;
from {
interface [interface-name];
routing-group [routing-group-name]];
routing-instance [routing-instance-name];
zone [zone-name];
}
rule rule-name {
description text;
match {
application {
... | [edit security nat destination] | Configure a set of rules for destination NAT. | [
{
"name": "rule-set-name",
"desc": "Name of the rule set."
},
{
"name": "description",
"desc": "Description of the rule set."
}
] | 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. The description option added in Junos OS Release 12.1.
Statement modified in Junos OS Release 12.1X45-D10. Statement modified in Junos OS Release
12.1X47-D10.
The routing-group option is added in Junos OS Release 22.2R1. | [] |
rule-set (Security Source NAT) | rule-set rule-set-name {
description text;
from {
interface [interface-name];
routing-group [routing-group-name]];
routing-instance [routing-instance-name];
zone [zone-name];
}
rule rule-name {
description text;
match {
application {
... | [edit security nat source] | Configure a set of rules for source NAT.
NOTE: When zones are not configured under rule-set and when active source NAT is
configured with missing mandatory statement “from” then, the following message is
displayed when performing commit “Missing mandatory statement: 'from' error:
configuration check-out failed” and the... | [
{
"name": "rule-set-name",
"desc": "Name of the rule set."
},
{
"name": "description",
"desc": "Description of the rule set."
}
] | 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. The description option added in Junos OS Release 12.1.
Statement modified in Junos OS Release 12.1X45-D10. Statement modified in Junos OS Release
12.1X47-D10.
The routing-group option is added in Junos OS Release 22.2R1. | [] |
rule-set (Security Static NAT) | rule-set rule-set-name {
description text;
from {
interface [interface-name];
routing-group [routing-group-name]];
routing-instance [routing-instance-name];
zone [zone-name];
}
rule rule-name {
description text;
match {
(destination-address ip... | [edit security nat static] | Configure a set of rules for static NAT. | [
{
"name": "rule-set-name",
"desc": "Name of the rule set."
},
{
"name": "description",
"desc": "Description of the rule set."
}
] | 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. The description option added in Junos OS Release 12.1.
The rule-session-count-alarm, source-address, source-address-name, and source-port options added in Junos OS
Release 12.1X45-D10.
The routing-group option is added in Junos OS Release 22.2R1. | [] |
rule-set (Services AACL) | rule-set rule-set-name {
[rule rule-names ];
} | [edit services aacl] | Specify the rule set the router uses when applying this service. | [
{
"name": "rule-set-name",
"desc": "Identifier for the collection of rules that constitute this rule set."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring AACL Rule Sets"
] |
rule-set (Services Application Identification) | rule-set rule-set-name {
rule application-rule-name;
} | [edit services application-identification],
[edit services application-identification profile profile-name] | Define members of rule set. | [
{
"name": "rule-set-name",
"desc": "Unique identifier for the rule set."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring APPID Rules"
] |
rule-set (Services CoS Next Gen Services) | rule-set rule-set-name {
[ rule rule-name ];
} | [edit services cos] | Configure a set of services CoS rules. You can then assign the rule set to a service set, which processes
the rules in the order they appear. Once a rule matches the packet, the router performs the
corresponding action, and no further rules are applied. | [
{
"name": "rule rule-name",
"desc": "The name of each rule in the rule set."
},
{
"name": "rule-set-name",
"desc": "The name for the set of rules."
}
] | 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. | [
"Class of Service for Services PICs (Next Gen Services)"
] |
rule-set (Services CoS) | rule-set rule-set-name {
[ rule rule-name ];
} | [edit services cos] | Specify the rule set the router uses when applying this service. | [
{
"name": "rule-set-name",
"desc": "Identifier for the collection of rules that constitute this rule set."
}
] | 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 CoS Rule Sets on Services PICs"
] |
rule-set (Services IDS) | rule-set rule-set-name {
[ rule rule-names ];
} | [edit services ids] | Specify the rule set the router uses when applying this service. | [
{
"name": "rule-set-name",
"desc": "Identifier for the collection of rules that constitute this rule set."
}
] | 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 IDS Rule Sets on an MS-DPC"
] |
rule-set (Services NAT) | rule-set rule-set-name {
[ rule rule-names ];
} | [edit services nat] | Specify the rule set the router uses when applying this service. | [
{
"name": "rule-set-name",
"desc": "Identifier for the collection of rules that constitute this rule set."
}
] | 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. | [
"Network Address Translation Rules Overview"
] |
rule-set (Services Stateful Firewall) | rule-set rule-set-name {
[ rule rule-names ];
} | [edit services stateful-firewall] | Specify the rule set the router uses when applying this service. | [
{
"name": "rule-set-name",
"desc": "Identifier for the collection of rules that constitute this rule set."
}
] | 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 Stateful Firewall Rule Sets"
] |
rule-set (Softwire) | rule-set rule-set-name {
rule rule-name;
} | [edit services softwire] | Specify the rule set the router uses when applying this service. | [
{
"name": "rule-set-name",
"desc": "Identifier for the collection of rules that constitute this rule set."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Configuring Softwire Rules"
] |
rule-set (Softwires Next Gen Services) | rule-set rule-set-name {
match-direction (input | output);
rule rule-name {
then {
ds-lite ds-lite-concentrator-name
map-e map-e-concentrator-name
v6rd v6rd-softwire-concentrator;
}
}
} | [edit services softwires] | Configure a rule to apply a DS-Lite, MAP-E, or v6rd softwire concentrator to a flow. | [
{
"name": "input",
"desc": "Apply the rule on the input side of the interface."
},
{
"name": "output",
"desc": "Apply the rule on the output side of the interface."
},
{
"name": "rule rule-name",
"desc": "Name of the rule."
},
{
"name": "rule-set rule-set-name",
"desc": "... | 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. | [
"6rd Softwires in Next Gen Services"
] |
rule-set | rule-set rule-set-name {
[ rule rule-names ];
} | [edit services ipsec-vpn] | Specify the rule set the router uses when applying this service. | [
{
"name": "rule-set-name",
"desc": "Identifier for the collection of rules that constitute this rule set."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IPsec Rule Sets",
"Configuring IPsec Rules"
] |
rule-sets (CoS AppQoS) | rule-sets {
rule-set-name {
rule rule-name {
match {
application application-name;
application-any;
application-group application-group-name;
application-known;
application-unknown;
}
then {
... | [edit class-of-service application-traffic-control]
[edit logical-systems logical-system-name class-of-service application-traffic-control]
[edit tenants tenant-name class-of-service application-traffic-control] | Defines AppQoS rule sets and the rules that establish priorities based on quality-of-service requirements
for the associated applications. AppQoS rules can be included in policy statements to implement
application-aware quality of service control. | [
{
"name": "rule-set-name",
"desc": "Name used to refer to a collection of AppQoS rules."
},
{
"name": "rule rule-name",
"desc": "Name applied to the match criteria and resulting actions that control the quality-of-service provided to any matching applications."
},
{
"name": "application ... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
Support at the following hierarchy levels introduced in Junos OS Release 19.3R1: [edit logical-systems
logical-system-name class-of-service application-traffic-control], and [edit tenants tenant-name class-of-service
application-traffic-control]. | [
"Example: Configuring AppQoS"
] |
rule-sets (Security Application Firewall) | rule-sets rule-set-name {
default-rule {
(deny [block-message] | permit | reject [block-message]);
}
profile profile-name;
rule rule-name {
match {
dynamic-application [system-application];
dynamic-application-groups [system-application-group];
ssl-enc... | [edit security application-firewall] | Configure the set of rules for the application firewall.
The application firewall is defined by a collection of rule sets. These rule sets can be defined
independently and shared across network security policies. A rule set defines the rules that specify
match criteria, including dynamic applications, and the action to... | [
{
"name": "rule-set-name",
"desc": "Name of the rule set."
},
{
"name": "profile profile-name",
"desc": "Profile for block message."
},
{
"name": "default-rule",
"desc": "Specify default rule."
},
{
"name": "rule",
"desc": "Specify security rule match-criteria"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. Statement updated in Junos OS Release 12.1X44-D10
to include the ssl-encryption and reject options. The block-message options added in Junos OS Release
12.1X45-D10. | [
"Example: Configuring an Application Group for Application Firewall"
] |
rulebase-exempt | rulebase-exempt {
rule rule-name {
description text;
match (Security IDP Policy) {
attacks (Security IPS Rulebase) {
custom-attack-groups [attack-group-name];
custom-attacks [attack-name];
dynamic-attack-groups [attack-group-name];
... | [edit security idp idp-policy policy-name] | Configure the exempt rulebase to skip detection of a set of attacks in certain traffic.
NOTE: You must configure the IPS rulebase before configuring the exempt rulebase. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Starting in Junos OS Release 18.2R1, IDP policy is available within unified security policy. IDP policy
configurations are simplified and made available under the unified policy as one of the policy.
Configuring source or destination address, source and destination-except,... | [] |
rulebase-ips | rulebase-ips {
rule (Security IPS Rulebase) rule-name {
description text;
match (Security IDP Policy) {
application (application-name | any | default);
attacks (Security IPS Rulebase) {
custom-attack-groups [attack-group-name];
custom-attacks [... | [edit security idp idp-policy policy-name] | Configure the IPS rulebase to detect attacks based on stateful signature and protocol anomalies. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
run | run command | Run a top-level CLI command without exiting from configuration mode. | [
{
"name": "command",
"desc": "CLI top-level command."
}
] | configure—To enter configuration mode. | Command introduced before Junos OS Release 7.4. | [
"Understanding Configuration Mode"
] | |
run-length | run-length number; | [edit forwarding-options port-mirroring input],
[edit forwarding-options port-mirroring instance port-mirroring-instance-name input],
[edit forwarding-options port-mirroring family (inet|inet6) input],
[edit forwarding-options sampling input],
[edit forwarding-options sampling instance instance-name input] | Set the number of samples following the initial trigger event. The configuration enables you to sample
packets following those already being sampled.
NOTE: The run-length statement is not supported when you configure inline flow
monitoring (by including the inline-jflow statement at the [edit forwarding-options samplin... | [
{
"name": "number",
"desc": "Number of samples."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Applying Forwarding Table Filters",
"Configuring Port Mirroring on M, T MX, ACX, and PTX Series Routers",
"Configuring Traffic Sampling on MX, M and T Series Routers"
] |
rx-buffers | rx-buffers (on | off); | [edit interfaces interface-name ether-options configured-flow-control] | Enable or disable an interface to generate and send Ethernet PAUSE messages. If you enable the receive
buffers to generate and send PAUSE messages, when the receive buffers reach a certain level of fullness,
the interface sends a PAUSE message to the connected peer. If the connected peer is properly
configured, it stop... | [
{
"name": "on | off",
"desc": "Enable or disable an interface to generate and send Ethernet PAUSE messages."
}
] | 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. | [
"Configuring CoS Asymmetric Ethernet PAUSE Flow Control",
"Enabling and Disabling CoS Symmetric Ethernet PAUSE Flow Control",
"Understanding CoS Flow Control (Ethernet PAUSE and PFC)"
] |
rx-connect-speed-when-equal (L2TP LAC) | rx-connect-speed-when-equal | [edit services l2tp] | Enable sending the receive connect speed, which is represented by AVP 38, even when its value is equal
to that of the transmit connect speed, which is represented by AVP 24. By default, AVP 38 is sent from
the LAC to the LNS during the establishment of an L2TP tunnel session, only when its value is different
from AVP 2... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1. | [
"L2TP Subscriber Access Lines and Connection Speeds",
"L2TP Subscriber Access Lines and Connection Speeds"
] |
rx-enable | expected-defect {
rx-enable ; | [edit protocols oam ethernet connectivity-fault-management expected-defect] | Enable the ethernet expected defect (ETH-ED) function to process the received EDM PDUs.
The remaining statements are explained separately. See CLI Explorer.
Default
The MEP does not process EDM PDUs. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1. | [] |
rx-max-duration | expected-defect {
rx-max-duration ; | [edit protocols oam ethernet connectivity-fault-management expected-defect] | Duration to indicate the maximum acceptable value at which the loss of continuity alarms are
suppressed. If the duration in the received EDM PDU exceeds this configured value then the duration
value will be truncated to this configured value and loss of continuity (LoC) alarms shall be suppressed
for this duration. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1. | [] |
rx-window-size (L2TP) | rx-window-size packets; | [edit services l2tp tunnel] | Configure the L2TP receive window size for an L2TP tunnel. | [
{
"name": "packets",
"desc": "Number of packets that a peer can transmit without receiving an acknowledgment from the"
}
] | 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. | [
"L2TP Tunnel Switching For Multiple-Domain Networks",
"L2TP LAC Subscriber Configuration",
"L2TP LNS Inline Service Interfaces",
"S",
"show interfaces (M Series, MX Series, T Series Routers, and PTX Series Management and Internal",
"show security user-identification device-provision authentication-source ... |
s6a | s6a {
partition name {
destination-host destination-host;
destination-realm destination-realm;
diameter-instance diameter-instance;
max-outstanding-requests max-outstanding-requests;
response-timeout seconds;
}
} | [edit access] | S6a is a Diameter-based authentication application used by the Mobility Management Entity (MME)
nodes to retrieve authentication information from Home Subscriber Server (HSS). Specify the
destination and transmission parameters for the S6a protocol. | [
{
"name": "destination-host",
"desc": "Name of the host where the S6A server application resides; generally, this value is not set unless needed."
},
{
"name": "destination-realm",
"desc": "Name of the realm where the S6a server application resides."
},
{
"name": "diameter-instance",
... | access | Statement introduced in Junos OS Release 19.3R1. | [
"Example: Configure S6a Application",
"Diameter Base Protocol Overview"
] |
s-nssai | s-nssai name {
sd sd;
sst(embb | miot | urllc | v2x);
} | [edit services agf tracking-area name plmn] | Configure the single network slice selection assistance information (S-NSSAI). The S-NSSAI is used to
uniquely identify a network slice. It consists of two components. For a fixed network residential gateway
(FN-RG), the Access Gateway Function (AGF) sends a proxy S-NSSAI message to the Access and
Mobility Management F... | [
{
"name": "name",
"desc": "Single network slice selection assistance information identifier Range:0 through 128"
},
{
"name": "sd",
"desc": "Selection differentiator Default: 0 Range: 0 through 16777215"
},
{
"name": "sst",
"desc": "Slice service type"
},
{
"name": "embb",... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.3R1. | [] |
sa-hold-time (Protocols MSDP) | sa-hold-time seconds; | [edit logical-systems logical-system-name protocols msdp],
[edit logical-systems logical-system-name protocols msdp group group-name peer address],
[edit logical-systems logical-system-name protocols msdp peer address],
[edit logical-systems logical-system-name routing-instances instance-name protocols msdp],
[edit log... | Specify the source address (SA) message hold time to use when maintaining a connection with the
MSDP peer. Each entry in an SA cache has an associated hold time. The hold timer is started when an
SA message is received by an MSDP peer. The timer is reset when another SA message is received
before the timer expires. If ... | [
{
"name": "seconds",
"desc": "Source address message hold time."
}
] | 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. | [
"Examples: Configuring MSDP"
] |
sa-multicast (100-Gigabit Ethernet) | sa-multicast; | [edit chassis fpc slot pic slot forwarding-mode] | Configure the 100-Gigabit Ethernet PIC or MIC to interoperate with other Juniper Networks 100-
Gigabit Ethernet PICs.
NOTE: The default packet steering mode for PD-1CE-CFP-FPC4 is SA multicast bit
mode. No SA multicast configuration is required to enable this mode.
sa-multicast supports interoperability between the fol... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Interoperability Between the 100-Gigabit Ethernet PICs PD-1CE-CFP-FPC4 and PF-1CGE-CFP",
"Configuring the Interoperability Between the 100-Gigabit Ethernet PICs PF-1CGE-CFP and PD-1CE-",
"CFP-FPC4",
"Configuring 100-Gigabit Ethernet MICs to Interoperate with Type 4 100-Gigabit Ethernet PICs",
"(PD-1CE-CFP-... |
sa-multicast (PTX Series Packet Transport Routers) | sa-multicast; | [edit chassis fpc slot pic slot port port-number forwarding-mode] | Configure source address (SA) multicast bit mode on the 100-Gigabit Ethernet PIC P1-PTX-2-100GE-
CFP to enable interoperability with 100-Gigabit Ethernet PIC PD-1CE-CFP-FPC4.
NOTE: When SA multicast bit steering mode is configured on a PTX Series Packet
Transport Router 100-Gigabit Ethernet port, VLANs are not supporte... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X48R4. | [
"Interoperability Between the 100-Gigabit Ethernet PICs PD-1CE-CFP-FPC4 and P1-PTX-2-100GE-",
"CFP",
"Configuring the Interoperability Between the 100-Gigabit Ethernet PICs P1-PTX-2-100GE-CFP and",
"PD-1CE-CFP-FPC4"
] |
sabit | sabit bit; | [edit chassis synchronization interfaces external e1-options],
[edit chassis synchronization interfaces (external-0/0 | external-1/0) e1-options],
[edit chassis synchronization interfaces bits e1-options] | Configure the SA bit for exchanging the SSM quality on the E1 interface. | [
{
"name": "bit",
"desc": "SA bit value. Range: 4 through 8."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [] |
saegw access-network-peers | access-network-peers {
local-address [ local-address ... ];
n3-requests n3-requests;
peer-groups name {
peer {
address [ address ... ];
hostname hostname;
}
routing-instance routing-instance;
}
routing-instance routing-instance;
t3-response seconds... | [edit services mobile-edge gateways saegw] | Use this section to define the connection to and characteristics of data plane peers. | [
{
"name": "local-address",
"desc": "Required. IPv4 address(es) of the local end of the GTP-U connection. NOTE: There is no limit to the number of data plane peers that can connect to the SAEGW-U."
},
{
"name": "n3-requests",
"desc": "Number of retries of peer management request messages upon t3-... | system | Statement introduced in Junos OS Release 19.4R1. | [] |
saegw control-plane-peers | control-plane-peers {
apn-services {
apns name {
mobile-interface mobile-interface;
source-validation {
}
}
heartbeat-interval seconds;
local-address [ local-address ... ];
n3-requests n3-requests;
path-management (disable | enable);
peer-groups name {... | [edit services mobile-edge gateways saegw] | Use this section to define the connection to and characteristics of control plane peers (SAEGW-C, SGW-
C, or PGW-C). | [
{
"name": "heartbeat-interval",
"desc": "Time between two successive heartbeat requests (seconds). Range: 60 through 255 Default: 60"
},
{
"name": "local-address",
"desc": "Required. IPv6 or IPv4 or both addresses of the local end of the PFCP connection. NOTE: If you are connecting to multiple... | system | Statement introduced in Junos OS Release 19.4R1. | [] |
saegw system | system {
anchor-pfes {
interface interface-name {
colocated-4g-pgw;
colocated-4g-sgw;
}
}
class-of-service {
... }
destination {
... }
service-mode (mobile-edge SAEGW) {
... }
} | [edit services mobile-edge gateways saegw] | Define the anchor PFEs for the SAEGW-U. The anchor PFEs are the line cards where the GTP-U data
packets from access-network-peers are decapsulated and sent towards the SGi interface to the core
network. Similarly, packets from the SGi interface are encapsulated in GTP-U by the anchor PFEs and
sent towards the RAN. | [
{
"name": "anchor-pfes",
"desc": "Define the anchor PFEs by providing their interface names. Syntax: interface interface-name"
},
{
"name": "colocated-4g-pgw",
"desc": "(Optional) Attach the PGW-U gateway type to the anchor PFE to optimize throughput of 4G traffic."
},
{
"name": "coloca... | system | Statement introduced in Junos OS Release 19.4R1.
colocated-4g-pgw and colocated-4g-sgw options introduced in Junos OS Release 21.3R1.
class-of-service and destination options introduced in Junos OS Release 22.2R1.
service-mode maintenance options introduced in Junos OS Release 23.1R1. | [] |
saegw | saegw name {
access-network-peers {
...}
control-plane-peers {
...}
core-network-peers {
...}
system {
...}
} | [edit services mobile-edge gateways] | Define the gateway name.
NOTE: Only a single instance of the gateway can be defined on the MX Series router. | [
{
"name": "name",
"desc": "Gateway name"
}
] | system | Statement introduced in Junos OS Release 19.4R1.
core-network-peers option introduced in Junos OS Release 20.4R1. | [] |
saegw-core-network-peers | core-network-peers {
echo-interval seconds;
local-address [ local-address ... ];
n3-requests n3-requests;
path-management (disable | enable);
peer-groups name {
peer {
address [ address ... ];
hostname hostname;
}
routing-instance routing-instance;
... | [edit services mobile-edge gateways saegw] | Define core-facing GTP-U peers (SGW-U to PGW-U and vice versa). | [
{
"name": "echo-interval",
"desc": "Time between origination of two successive echo requests (seconds). You must enable path-management for echo requests to occur. Range: 60 through 255 Default: 60"
},
{
"name": "local-address",
"desc": "Required. IPv4 address(es) of the local end of the GTP-U... | system | Statement introduced in Junos OS Release 20.4R1. | [] |
sak-rekey-interval | sak-rekey-interval seconds; | [edit security macsec connectivity-association connectivity-association-name mka] | Configure a timer-based refresh of the secure association key (SAK) on a MACsec-secured link. This
ensures that the SAK is frequently updated, making it less vulnerable to attack.
In static CAK mode, the SAK is generated by the key server and is periodically refreshed. The refresh
interval is based on packet counter mo... | [
{
"name": "seconds",
"desc": "The length of the SAK refresh interval in seconds. Range: 60 through 86,400 seconds"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.3R1. | [
"Configuring Advanced MACsec Features"
] |
saml (Access Profile) | saml {
service-provider service-provider;
identity-provider domain {
idp-name idp-name;
}
} | [edit access profile name] | Describe Security Assertion Markup Language (SAML) configuration for the access profile. | [
{
"name": "identity-provider domain",
"desc": "Specify the identity provider (IdP) parameters for the profile. Values: any or specify user's domain such as example.net."
},
{
"name": "idp-name idp-name",
"desc": "Specify the IDP name."
},
{
"name": "service-provider service-provider",
... | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.4R1. | [] |
saml | saml {
identity-provider identity-provider {
attribute-mapping {
attribute-name assertion-attribute <mandatory | optional>;
address-pool assertion-attribute <mandatory | optional>;
firstname assertion-attribute <mandatory | optional>;
group assertion-attribute... | [edit access] | Describe Security Assertion Markup Language (SAML) authentication parameters. | [
{
"name": "identity-provider identity-provider",
"desc": "Specify the identity provider (IdP) configuration details."
},
{
"name": "service-provider service-provider",
"desc": "Specify the service provider configuration details."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.4R1. | [] |
saml-options | saml-options {
no-assertion-cache;
} | [edit access] | Specify the option to avoid caching Security Assertion Markup Language (SAML) assertions from the
identity provider (IdP). | [
{
"name": "no-assertion-cache",
"desc": "Do not cache assertions from IdP. We recommend not using this option for SAML-based user authentication in Juniper Secure Connect to ensure the establishment of remote access VPN tunnel."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.4R1. | [] |
sample | sample
{
aggregate
{
range range;
}
} | [edit system ddos-protection protocols] | aggregate
Configure aggregate for all Sampling traffic
range
(PTX10008, PTX10001-36MR, PTX10001, and
PTX10004 routers only)
range <0 to 150000>
range
(PTX10003-80C and PTX10003-160C routers only)
range <0 to 50000> | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration.
Release Information | [] | |
sample-once | sample-once; | [edit forwarding-options sampling] | Explicitly sample a packet for active monitoring only once. When you configure the sample-once
statement, the ingress interface sets a flag for any packets that it selects for sampling, and the egress
interface does not sample any flagged packets. Setting this option avoids duplication of packets in cases
where samplin... | [] | 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. | [
"Configuring Traffic Sampling on MX, M and T Series Routers"
] |
sample-rate | sample-rate {
egress number;
ingress number;
} | [edit protocols sflow],
[edit protocols sflow interfaces interface-name] | Specify the number of egress or ingress packets out of which one packet is sampled. If no interface
sampling rates are configured, the global sampling rates take effect. If neither is configured, by default
both ingress and egress packet sampling are disabled.
Default
By default, both egress and ingress sampling rates ... | [
{
"name": "egress number",
"desc": "Value for egress sampling rate."
},
{
"name": "ingress number",
"desc": "Value for ingress sampling rate."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3.
The option number (which immediately followed sample-rate) is no longer available and options egress
number and ingress number added in Junos OS Release 10.4 for EX Series switches. | [
"Configuring sFlow Technology for Network Monitoring (CLI Procedure)",
"Example: Configuring sFlow Technology to Monitor Network Traffic on EX Series Switches"
] |
sample-type | sample-type (absolute-value | delta-value); | [edit snmp rmon alarm index] | Configure the method of sampling the selected variable (monitored object). When you configure an
SNMP RMON alarm, you can specify the sample type. | [
{
"name": "absolute-value",
"desc": "Actual value of the selected variable is used when comparing against the thresholds."
},
{
"name": "delta-value",
"desc": "Difference between samples of the selected variable is used when comparing against the"
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Remote Nework Monitoring (RMON)"
] |
sampling (Forwarding Options) | sampling {
disable;
family (inet | inet6 | mpls | vpls) {
disable;
output {
aggregate-export-interval seconds;
file {
disable;
filename filename;
files number;
size bytes;
(stamp | no-stamp);
... | [edit forwarding-options] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for IPv6 addresses for the flow-server address and source-address address statements within
sampling instances introduced in Junos OS Evolved Release 23.1R1. | [
"Configuring Traffic Sampling on MX, M and T Series Routers",
"Applying Forwarding Table Filters",
"Collecting Traffic Sampling Output in the Cisco Systems NetFlow Services Export Version 9 Format",
"Directing Traffic Sampling Output to a Server Running the cflowd Application",
"Configuring Port Mirroring",... |
sampling (Interfaces) | sampling direction; | [edit interfaces interface-name unit logical-unit-number family inet],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet] | Configure the direction of traffic to be sampled. | [
{
"name": "direction can be one of the following:",
"desc": ""
},
{
"name": "input",
"desc": "Configure at least one expected ingress point."
},
{
"name": "output",
"desc": "Configure at least one expected egress point."
},
{
"name": "input output",
"desc": "On a single i... | 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. | [
"Junos OS Services Interfaces Library for Routing Devices",
"Configuring Flow Monitoring"
] |
sampling (Protocols MPLS) | sampling {
cut-off-threshold percentile;
use-average-aggregate;
use-percentile percentile;
} | [edit protocols mpls container-label-switched-path lsp-name splitting-merging] | Configure traffic sampling. By default, sampling mode is set to Max Aggregate which means the system will
compare each new sample with the previous sample. If the new sample is higher than the old sample,
then the newer sample is considered Sampled Aggregate bandwidth
Max Aggregate Example
If normalization happens ever... | [
{
"name": "cut-off-threshold",
"desc": ""
},
{
"name": "percentile",
"desc": "Specify the percentile value to be used as a cut-off threshold in removing outlier bandwidth samples. All the aggregate bandwidth samples determined as outliers are used for computing aggregate bandwidth used at the ti... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
sampling | sampling {
command binary-file-path;
disable;
failover (alternate-media | other-routing-engine);
} | [edit system processes] | Perform packet sampling based on particular input interfaces and various fields in the packet header. | [
{
"name": "command binary-file-path",
"desc": "Path to the binary process."
},
{
"name": "disable",
"desc": "Disable the traffic sampling control process."
},
{
"name": "failover",
"desc": "Configure the device to reboot if the software process fails four times within 30 seconds,"
... | system—To view this in the configuration.
system-control—To add this to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Understanding Traffic Processing on Security Devices"
] |
sampling-instance | sampling-instance instance-name; | [edit chassis fpc slot-number],
[edit chassis lcc number fpc routing-matrix-slot-number],
[edit chassis member member-number fpc slot slot-number] | Associate a defined sampling instance with a specific FPC, MPC, or DPC for active sampling instances
configured at the [edit forwarding-options sampling] hierarchy level.
For M120 routers with FEB, this statement must also be configured under [edit chassis feb slot-number],
in addition to the [edit forwarding-options s... | [] | 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.
Support at the [edit chassis member member-number fpc slot slot-number] hierarchy level introduced in Junos
OS Release 14.1. | [
"Associating Sampling Instances for Active Flow Monitoring with a Specific FPC, MPC, or DPC",
"Inline Flow Monitoring for Virtual Chassis Overview"
] |
sanity-poll | sanity-poll {
retry-count number;
on-error {
raise-alarm;
power (cycle | off);
write-coredump;
}
} | [edit chassis cfeb slot-number],
[edit chassis feb slot-number],
[edit chassis fpc slot-number],
[edit chassis lcc number fpc number] | Enable sanity polling and start periodic sanity checking for a particular FPC. The periodic sanity check
includes checking for error conditions such as “register sanity issues,” “high temperature,” “hardware
failure,” and so on in the FPC.
NOTE: Currently, periodic sanity check is performed only on the routing chip reg... | [] | 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. | [
"Configuring Sanity Polling"
] |
sap | sap {
disable;
listen address <port port>;
} | [edit logical-systems logical-system-name protocols],
[edit protocols] | Enable the router to listen to session directory announcements for multimedia and other multicast
sessions.
SAP and SDP always listen on the default SAP address and port, 224.2.127.254:9875. To have SAP
listen on additional addresses or pairs of address and port, include a listen statement for each address or
pair. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Session Announcement Protocol"
] |
satellite (Junos Fusion Automatic Satellite Conversion) | satellite [slot-id | range | all]; | [edit chassis satellite-management auto-satellite-conversion] | Specify the interface to enable automatic software conversion in a Junos Fusion.
The device that is cabled to the slot specified in this command is automatically converted into a satellite
device.
Additional configuration steps are required to add satellite devices to a Junos Fusion using automatic
satellite conversio... | [
{
"name": "slot-id",
"desc": "Specifies the FPC slot identifier of the device that will be automatically converted into a satellite device. The FPC identifier must be mapped to a cascade port interface before this command is operational. See Configuring or Expanding a Junos Fusion Enterprise or Configuring ... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring Junos Fusion Provider Edge",
"Configuring or Expanding a Junos Fusion Enterprise"
] |
satellite (Junos Fusion Satellite Device Homing) | satellite [slot-id |slot-id-range | all]; | [edit chassis satellite-management single-home] | Specify which satellite device links are single-homed to the aggregation device.
You must enter this statement to configure a Junos Fusion when the aggregation device is running Junos
OS Release 14.2R3 or 14.2R4. You are not required to enter this command when the aggregation device
is running Junos OS Release 14.2R5 o... | [
{
"name": "slot-id",
"desc": "Specifies that a link from a specified satellite device is single-homed to the aggregation device. The slot-id is the satellite device member number."
},
{
"name": "slot-id-range",
"desc": "Specifies that the links from a range of specified satellite devices are sin... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3.
Statement introdcued in Junos OS Release 16.1R1 for Junos Fusion Enterprise. | [
"Configuring Junos Fusion Provider Edge",
"Configuring or Expanding a Junos Fusion Enterprise"
] |
satellite (Junos Fusion Satellite Software Upgrade Groups) | satellite [slot-id | range | all]; | [edit chassis satellite-management upgrade-groups upgrade-group-name] | Specify the satellite device to add to the satellite software upgrade group.
This statement is entered on an aggregation device in a Junos Fusion. Software upgrade groups are
configured and managed using the aggregation device. | [
{
"name": "slot-id",
"desc": "Specifies the FPC slot identification number of the satellite device that is being added to the satellite software upgrade group."
},
{
"name": "range",
"desc": "Specifies a range of FPC slot identifiers to add to the satellite software upgrade group. For instance, ... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring Junos Fusion Provider Edge",
"Configuring or Expanding a Junos Fusion Enterprise"
] |
satellite-management (Junos Fusion) | satellite-management {
aging-timer aging-timer;
auto-satellite-conversion {
satellite [slot-id | range | all];
}
cluster cluster-name{
cascade-ports interface-name;
cluster-id cluster-id-number;
fpc slot-id{
alias alias;
description description;
... | [edit chassis] | Configure and manage a Junos Fusion.
If you enter the delete chassis satellite-management command to delete a Junos Fusion configuration,
we recommend also rebooting the Routing Engines on your device to maximize device performance. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring or Expanding a Junos Fusion Enterprise",
"Configuring Junos Fusion Provider Edge"
] |
satellite-policies | satellite-policies {
<candidate-uplink-port-profile policy-name> {
<holddownholddown-time>;
<minimum-linksnumber-of-links>;
<uplink-port-group uplink-port-group-name>;
term term-name {
from {
product-model model-name;
<holddown holddown-tim... | [edit policy-options] | Configure satellite policies for a Junos Fusion. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring Junos Fusion Provider Edge",
"Configuring or Expanding a Junos Fusion Enterprise"
] |
save (Configuration Mode) | save filename | All hierarchy levels | Save the configuration to an ASCII file. The contents of the current level of the statement hierarchy (and
below) are saved, along with the statement hierarchy containing it. This allows a section of the
configuration to be saved, while fully specifying the statement hierarchy.
For information on valid filename and URL... | [
{
"name": "filename",
"desc": "Name of the saved file. You can specify a filename in one of the following ways:"
},
{
"name": "filename",
"desc": "File in the user’s home directory (the current directory) on the local flash drive."
},
{
"name": "path/filename",
"desc": "File on the l... | configure—To enter configuration mode.
Sample Output
The following is an example of a save scenario:
Save a File Using Secure Copy Protocol (scp) with ’source-address’ and ’routing-instance’
options
To save the configuration to a remote system, enter the following save command using scp with the
source-address and rout... | Command introduced before Junos OS Release 7.4. | [
"Deactivating and Reactivating Statements and Identifiers in a Device Configuration"
] |
save | save (<dhcp-security-snoop>filename)
QFX and VMX Series
save (<dhcp-security-snoop | dhcpv6-security-snoop | slaac-security-snoop>filename) | Save the configuration to an ASCII file. The contents of the current level of the statement hierarchy (and
below) are saved, along with the statement hierarchy containing it. This allows a section of the
configuration to be saved, while fully specifying the statement hierarchy.
For information on valid filename and URL... | [
{
"name": "filename",
"desc": "Name of the saved file. You can specify a filename in one of the following ways:"
},
{
"name": "filename",
"desc": "File in the user’s home directory (the current directory) on the local flash drive."
},
{
"name": "path/filename",
"desc": "File on the l... | NOTE: The save commands for dhcp-security-snoop, dhcpv6-security-snoop, and slaac-security-
snoop are restricted to admin only.
view | Command introduced before Junos OS Release 7.4. | [
"Deactivating and Reactivating Statements and Identifiers in a Device Configuration"
] | |
saved-core-context (System) | (saved-core-context | no-saved-core-context); | [edit system] | Configure whether the device saves core files generated by internal Junos processes, along with
contextual information (system log files and a copy of the current configuration).
•
saved-core-context—The device saves each core file and its associated context in a compressed tar file
named /var/tmp/process-name.core.co... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Saving Core Files from Junos OS Processes"
] |
saved-core-files (System) | saved-core-files number; | [edit system] | Save core files generated by internal Junos processes, but not the associated contextual information
(configuration and system log files). | [
{
"name": "number",
"desc": "Maximum number of core files to save per executable. Default: 5 Range: 1 through 10"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Saving Core Files from Junos OS Processes"
] |
sbfd (protocols bfd) | sbfd {
local-discriminator local-discriminator;
local-discriminator-ip local-discriminator-ip;
} | [edit protocols bfd sbfd] | Configure seamless BFD (S-BFD) parameters in the BFD protocol. | [
{
"name": "local-discriminator",
"desc": "Local discriminator for seamless BFD responder"
},
{
"name": "local-discriminator-ip",
"desc": "Local discriminator IP address for sBFD responder"
}
] | routing | Statement local-discriminator-ip introduced in Junos OS Release 22.4R1. | [
"Routing Engine-based S-BFD for Segment-Routing Traffic Engineering with First-Hop Label",
"Resolution"
] |
sbfd | sbfd {
remote-discriminator remote-discriminator;
destination-ipv6-local-host;
} | [edit protocols source-packet-routing source-routing-path name primary name bfd-liveness-detection
(LSP)],
[edit protocols source-packet-routing source-routing-path name secondary name bfd-liveness-detection
(LSP)] | Configure seamless BFD (S-BFD) parameters in the source routing path. | [
{
"name": "remote-discriminator",
"desc": "Remote discriminator of reflector Range: 1 through 4294967295"
},
{
"name": "destination-ipv6-local-host",
"desc": "Enforce the use of an IPv6 local host address, for S-BFD responders that only supports IPv6 local host address."
}
] | routing | Statement introduced in Junos OS Release 19.1R1. | [
"Routing Engine-based S-BFD for Segment-Routing Traffic Engineering with First-Hop Label",
"Resolution"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.