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 |
|---|---|---|---|---|---|---|---|
source-packet-routing (Protocols OSPF) | source-packet-routing {
adjacency-segment {
hold-time hold-time;
}
disable;
explicit-null;
node-segment {
index-range index range;
ipv4-index index;
}
flex-algorithm name {
color color;
defin... | [edit logical-systems logical-system-name protocols ospf],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ospf],
[edit protocols ospf],
[edit routing-instances routing-instance-name protocols ospf] | Configures source packet routing in networking (SPRING) feature.
Default
Disabled on all the levels. | [
{
"name": "adjacency-segment",
"desc": "Configure attributes for adjacency segments in source packet routing in networking (SPRING), or configure segment routing (SR) to ensure that the adjacency segment"
},
{
"name": "<hold-time",
"desc": ""
},
{
"name": "hold-time>",
"desc": "ident... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2.
The strict-asla-based-flex-algorithm option introduced in Junos OS and Junos OS Evolved Release 22.2R1. | [
"OSPF Overview"
] |
source-packet-routing (Routing Instances Protocols EVPN) | source-packet-routing {
srv6 locator loc-name (end-dt2-sid | micro-dt2-sid | end-dx2v-sid | micro-dx2v-sid);
} | [edit logical-systems name routing-instances name protocols evpn],
[edit routing-instances name protocols evpn] | Enable IPv6 segment routing for EVPN E-LAN and EVPN-VPWS services. | [
{
"name": "locator loc-name",
"desc": "Required. Name of the SRv6 locator (defined at [edit routing-options source-packet-routing srv6])."
},
{
"name": "end-dt2-sid",
"desc": "Segment Routing Header-based End.DT2 SIDs."
},
{
"name": "micro-dt2-sid",
"desc": "Micro-SID based End.DT2 S... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4 R1 and Junos OS Evolved Release 23.4R1. | [
"Configuring EVPN VPWS over SRv6 with Traffic Engineering"
] |
source-packet-routing (routing-options) | mapping-server-entry mapping-server-entry; | [edit logical-systems name routing-instances name routing-options],
[edit logical-systems name routing-options],
[edit routing-instances name routing-options],
[edit routing-options] | Configure interoperability between islands of devices supporting only segment routing and LDP in an
LDP network domain where there is gradual deployment of segment routing. | [] | routing | Statement introduced in Junos OS Release 18.2R1. | [] |
source-packet-routing (Segment Routing Traffic Engineering) | source-packet-routing {
inherit-label-nexthops;
lsp-external-controller name;
maximum-segment-list-depth maximum-segment-list-depth
maximum-srv6-te-segment-list-depth maximum-srv6-segment-list-depth;
preference preference;
preserve-nexthop-hierarchy;
retry-timer seconds;
sbfd-frr;
se... | [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": "inherit-label-nexthops",
"desc": "Inherit label next hops for first hop in all the segment lists. When the inherit-label-nexthops is configured at the [edit protocols source-packet-routing] hierarchy, it is applied globally, and takes precedence over individual segment- list level configuration. ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1 for the MX Series and PTX Series with FPC-PTX-P1-
A.
telemetry option introduced in Junos OS Release 18.3R1 for the MX Series and PTX Series with FPC-
PTX-P1-A.
inherit-label-nexthops and retry-timer statements introduced in Junos OS Release 19.1R1 on MX Series
routers.
t... | [
"extended-nexthop-color",
"sr-preference-override",
"Segment Routing Traffic Engineering at BGP Ingress Peer Overview",
"Understanding Static Segment Routing LSP in MPLS Networks",
"Understanding SR-TE Policy for SRv6 Tunnel"
] |
source-pool | source-pool nat-pool-name; | [edit services nat rule rule-name term term-name then translated] | Specify the source address pool for translated traffic. | [] | 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"
] |
source-port (Applications) | source-port port-number; | [edit applications application application-name ]
[edit applications application application-name term term-name] | Specify the source port identifier. | [
{
"name": "port-number",
"desc": "Identifier for the port. You can use a numeric value or one of the text synonyms listed in"
}
] | 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"
] |
source-port (firewall) | source-port <source-port>; | [edit firewall family family-name filter filter-name term term-name from ip-version ip-version
protocol (tcp|udp)] | Configure the source port of the Layer 4 header. | [
{
"name": "source-port",
"desc": "The source port of the Layer 4 header. Range: 0 through 65,535"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1R1. | [
"Firewall Filter Match Conditions for MPLS-Tagged IPv4 or IPv6 Traffic"
] |
source-port (Security Forwarding Options) | source-port port-number; | [edit security forwarding-options mirror-filter filter-name] | Specify a Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) source port number to
be matched for mirroring. You can specify a numeric value or one of the text synonyms listed in Table
1892 on page 29399.
Table 1892: Ports Supported by Services Interfaces
Port Name
Corresponding Port Number
afs
bgp
b... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [] |
source-port (Security IDP) | source-port {
match (equal | greater-than | less-than | not-equal);
value source-port;
} | [edit security idp custom-attack attack-name attack-type signature protocol udp],
[edit security idp custom-attack attack-name attack-type signature protocol tcp] | Specify the port number on the attacking device. | [
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value source-port",
"desc": "Port number on the attacking device."
}
] | 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. | [] |
source-port (Security Source NAT Rule Set) | source-port (port-or-low <to high>); | [edit security nat source rule-set rule-set-name rule rule-name match] | Specify the port number or port range for a source rule. Up to 8 ports or port ranges are supported. | [
{
"name": "port",
"desc": "Specify a port number."
},
{
"name": "low",
"desc": "Specify the lower limit of the port range."
},
{
"name": "<to high>",
"desc": "Specify the upper limit of the port range."
}
] | 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. | [] |
source-port (Security Static NAT Rule Set) | source-port (port or low <to high>); | [edit security nat static rule-set rule-set-name rule rule-name match] | Specify the port or port range for a source rule. Up to 8 ports or port ranges are supported. | [
{
"name": "port",
"desc": "Specify a port number."
},
{
"name": "low",
"desc": "Specify the lower limit of the port range."
},
{
"name": "<to high>",
"desc": "Specify the upper limit of the port range."
}
] | 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. | [] |
source-port (Subscriber Secure Policy) | source-port port-number; | [edit services radius-flow-tap policy policy-name inet drop-policy rule-name from],
[edit services radius-flow-tap policy policy-name inet6 drop-policy rule-name from] | Specify the match source port for the radius-flow-tap policy. | [
{
"name": "port-number",
"desc": "Number of the IPv4 or IPv6 source port for the radius-flow-tap policy."
}
] | flow-tap—To view this statement in the configuration.
flow-tap-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Subscriber Secure Policy Overview",
"Configuring RADIUS-Initiated Subscriber Secure Policy Mirroring Overview"
] |
source-port | source-port port-number; | [edit applications application application-name] | Source port identifier. | [
{
"name": "port-value",
"desc": "Identifier for the port. For a complete list, see Configuring Source and Destination Ports."
}
] | 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 Application Properties",
"Configuring Source and Destination Ports",
"Verifying the Output of ALG Sessions"
] |
source-prefix (IDS) | source-prefix prefix-value; | [edit services ids rule rule-name term term-name then aggregation] | Specify the prefix length for source IPv4 address aggregation for the IDS rule. This applies session limits
to an aggregation of all attacks from within a subnet of the specified length.
For example, if you configure a value of 24 for source-prefix, then attacks from 10.1.1.2 and 10.1.1.3 are
counted as attacks from th... | [
{
"name": "prefix-value",
"desc": "Integer 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. | [
"Configuring IDS Rules on an MS-DPC",
"Configuring Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
source-prefix (Security Forwarding Options) | source-prefix source-prefix; | [edit security forwarding-options mirror-filter filter-name] | Specify the source IP prefix or address to be matched for mirroring. | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [] |
source-prefix (Services NAT) | source-prefix source-prefix; | [edit services nat rule rule-name term term-name then translated] | Specify the source prefix for translated traffic. | [
{
"name": "source-prefix",
"desc": "IPv4 or IPv6 source prefix value."
}
] | 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.
source-prefix option enhanced to support IPv6 addresses in Junos OS Release 8.5. | [
"Network Address Translation Rules Overview"
] |
source-prefix-ipv6 (IDS) | source-prefix-ipv6 prefix-value; | [edit services ids rule rule-name term term-name then aggregation] | Specify the prefix length for source IPv6 address aggregation for the IDS rule. This applies session limits
to an aggregation of all attacks from within a subnet of the specified length.
For example, if you configure a value of 64 for source-prefix-ipv6, then attacks from
2001:db8:1234:72a2::2 and 2001:db8:1234:72a2::3... | [
{
"name": "prefix-value",
"desc": "Integer value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring IDS Rules on an MS-DPC",
"Configuring Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
source-prefix-list (PCP) | source-prefix-list list-name <except>; | [edit services pcp rule rule-name term term-name from] | Specify the source prefix list that must be matched for the PCP rule. You configure the prefix list by
including the prefix-list statement at the [edit policy-options] hierarchy level. A PCP rule assigns the PCP
server that handles selected traffic.
PCP is supported on the MS-DPC, MS-100, MS-400, and MS-500 MultiServic... | [
{
"name": "list-name",
"desc": "Source prefix list."
},
{
"name": "except",
"desc": "(Optional) Prevent the specified prefix list from matching the PCP rule."
}
] | 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"
] |
source-prefix-list (Services AACL) | source-prefix-list list-name; | [edit services aacl rule rule-name term term-name from] | Specify the source prefix list for rule matching. You configure the prefix list by including the prefix-list
statement at the [edit policy-options] hierarchy level. | [
{
"name": "list-name",
"desc": "Source prefix list."
}
] | 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 Match Conditions in AACL Rules"
] |
source-prefix-list (Services CoS) | source-prefix-list list-name <except>; | [edit services cos rule rule-name term term-name from] | Specify the source prefix list for rule matching. You configure the prefix list by including the prefix-list
statement at the [edit policy-options] hierarchy level. | [
{
"name": "list-name",
"desc": "Destination prefix list."
},
{
"name": "except",
"desc": "(Optional) Exclude the specified prefix list from rule matching."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Configuring CoS Rules",
"https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/config-",
"guide-policy/config-guide-policy.html"
] |
source-prefix-list (Services IDS) | source-prefix-list list-name <except>; | [edit services ids rule rule-name term term-name from] | Specify the source prefix list for rule matching. You configure the prefix list by including the prefix-list
statement at the [edit policy-options] hierarchy level. | [
{
"name": "list-name",
"desc": "Destination prefix list."
},
{
"name": "except",
"desc": "(Optional) Exclude the specified prefix list from rule matching."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Configuring Match Conditions in IDS Rules",
"https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/config-",
"guide-policy/config-guide-policy.html"
] |
source-prefix-list (Services NAT) | source-prefix-list list-name <except>; | [edit services nat rule rule-name term term-name from] | Specify the source prefix list for rule matching. You configure the prefix list by including the prefix-list
statement at the [edit policy-options] hierarchy level. | [
{
"name": "list-name",
"desc": "Destination prefix list."
},
{
"name": "except",
"desc": "(Optional) Exclude the specified prefix list from rule matching."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Network Address Translation Rules Overview",
"https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/config-",
"guide-policy/config-guide-policy.html"
] |
source-prefix-list (Services Stateful Firewall) | source-prefix-list list-name <except>; | [edit services stateful-firewall rule rule-name term term-name from] | Specify the source prefix list for rule matching. You configure the prefix list by including the prefix-list
statement at the [edit policy-options] hierarchy level. | [
{
"name": "list-name",
"desc": "Destination prefix list."
},
{
"name": "except",
"desc": "(Optional) Exclude the specified prefix list from rule matching."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Configuring Match Conditions in Stateful Firewall Rules",
"https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/config-",
"guide-policy/config-guide-policy.html"
] |
source-route-option (IDS Screen Next Gen Services) | source-route-option; | [edit services screen ids-option screen-name ip] | Identify and drop IPv4 packets that have either the IP option of 3 (Loose Source Routing) or the IP
option of 9 (Strict Source Routing). | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
source-routing | source-routing {
(ip | ipv6)
} | [edit routing-options] | Enable source routing.
Source routing allows a sender of a packet to partially or completely specify the route the packet takes
through the network. In contrast, in non-source routing protocols, routers in the network determine the
path based on the packet's destination.
NOTE: We recommend that you not use source routi... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement for IPv6 introduced in Junos OS Release 8.2.
Statement for IPv4 introduced in Junos OS Release 8.5.
Statement introduced in Junos OS Release 9.0. | [
"Example: Configuring Filter-Based Forwarding on the Source Address"
] |
source-routing (TWAMP) | source-routing {
forward (srmpls-nodes <label hop1...n> | srv6-nodes <IPv6 SID hop1...n>);
return (srmpls-nodes <label hop1...n> | srv6-nodes <IPv6 SID hop1...n>);
} | [edit services monitoring twamp client control-connection name test-session name]
[edit services rpm twamp client control-connection name test-session name] | TWAMP supports segment routing as defined in RFC 8402, which broadly specifies the segment routing
architecture. We support two types of segment routing for TWAMP probes:
•
SR-MPLS: Uses a list of labels, each representing a segment end node.
•
SRv6: Uses a type 4 IPv6 routing header introduced in RFC 8754, with each s... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 24.4R1.
Statement introduced in Junos OS Release 25.4R1. | [] |
source-routing-path | source-routing-path name {
binding-sid binding-sid;
color color;
lsp-external-controller;
metric value;
no-ingress;
primary name {
compute {
compute-profile-name;
}
lsp-external-controller;
return-path return-segment-list-name
weight weight;
... | [edit logical-systems name protocols source-packet-routing],
[edit protocols source-packet-routing] | Configure a source-routing label switched path (LSP) for steering traffic at an ingress router. Specify a
binding segment identifier from the static label range. Configure other parameters such as color, weight,
preference, and segment routing preference for traffic engineering.
Starting with Junos OS Release 18.1R1, c... | [
{
"name": "name",
"desc": "Specify a name to identify a source routing path. NOTE: The combined length of tunnel-name and LSP name must not exceed 53 characters for per-path telemetry to work."
},
{
"name": "binding-sid",
"desc": "(Optional) Specify the binding label to enable transit functional... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1.
The metric, no-ingress, and secondary statements are introduced in Junos OS Release 18.1R1.
lsp-external-controller statement introduced in Junos OS Release 20.1R1.
srv6 option introduced in Junos OS Release 21.3R1.
return-path option introduced in Junos OS Evolved Rele... | [
"extended-nexthop-color",
"sr-preference-override",
"Segment Routing Traffic Engineering at BGP Ingress Peer Overview",
"Enable Segment Routing for the Path Computation Element Protocol"
] |
source-routing-path-template | source-routing-path-template name {
bfd-liveness-detection;
ldp-tunneling;
metric metric;
no-ingress;
primary name {
compute {
compute-profile-name;
}
lsp-external-controller;
weight weight;
}
secondary name;
compute {
compute-profile-... | [edit protocols source-packet-routing] | Configure a source-routing path template for dynamic creation of segment routing label-switched paths
(LSPs). | [
{
"name": "name",
"desc": "Name of the source routing path."
},
{
"name": "bfd-liveness-detection",
"desc": "Configure Bidirectional Forwarding Detection (BFD) options for PCE-initiated segment routing LSP template. See \"bfd-liveness-detection\" on page 3161 for more information."
},
{
... | routing | Statement introduced in Junos OS Release 19.2R1.
bfd-liveness-detection and ldp-tunneling options introduced in Junos OS Release 19.4R1.
lsp-external-controller statement introduced in Junos OS Release 20.1R1.
compute statement introduced in Junos OS Release 20.4R1. | [
"Understanding Static Segment Routing LSP in MPLS Networks",
"source-routing-path-template-map"
] |
source-threshold | source-threshold number; | [edit security screen ids-option screen-name tcp syn-flood] | Specify the number of SYN segments that the device can receive per second from a single source IP
address (regardless of the destination IP address and port number) before the device begins dropping
connection requests from that source. | [
{
"name": "number",
"desc": "Number of SYN segments to be received per second before the device starts dropping"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.2. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
source-tree (MBGP MVPN) | source-tree; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols mvpn
static-umh],
[edit routing-instances routing-instance-name protocols mvpn static-umh] | Specify that a statically selected upstream multicast hop (UMH) only affects type 7 (S,G) routes.
The source-tree option is mandatory. Type 6 routes are sent toward the rendezvous point (RP), and use
the dynamic UMH selection that is configured with the unicast-umh-election statement, or the default
method of highest I... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider",
"Tunnels",
"Example: Configuring Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider",
"Tunnels"
] |
source-udp-port (RFC 2544 Benchmarking) | source-udp-port port-number; | [edit services monitoring rfc2544 tests test-name test-name] | Specify the UDP port of the source to be used in the UDP header for the generated frames. If you do
not specify the UDP port, the default value of 4041 is used. | [
{
"name": "port-number",
"desc": "Source UDP port number for the test frames Default: 4041"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X52.
Statement introduced in Junos OS Release 21.1R1. | [
"Configuring an RFC 2544-Based Benchmarking Test",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers"
] |
spam-action | spam-action (block | tag-header | tag-subject); | [edit security utm default-configuration]
[edit security utm feature-profile anti-spam sbl profile profile-name] | Configure the action to be taken by the device when spam is detected. | [
{
"name": "block",
"desc": "Block e-mail."
},
{
"name": "tag-header",
"desc": "Tag header of e-mail."
},
{
"name": "tag-subject",
"desc": "Tag subject of e-mail."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Example: Configuring Server-Based Antispam Filtering",
"Example: Configuring Local List Antispam Filtering"
] |
speed (24-port and 12-port 10 Gigabit Ethernet PIC) | speed 1G | 10G | [edit chassis fpc slot-number pic pic-number],
[edit chassis fpc slot-number pic pic-number port port-number],
[edit chassis lcc number fpc slot-number pic pic-number mixed-rate-mode] | Configure the port speed on the following interface modules:
•
PF-24XGE-SFPP or the PF-12XGE-SFPP PIC on a T4000 standalone router or on an LCC in a TX
Matrix Plus routing matrix with 3D SIBs
NOTE: To change the port speed from 10 Gbps to 1 Gbps on PF-24XGE-SFPP and
PF-12XGE-SFPP PICs, SFP optics is required.
•
P1-PTX-... | [
{
"name": "1 G",
"desc": ""
},
{
"name": "1 Gbps",
"desc": ""
},
{
"name": "10 G",
"desc": ""
},
{
"name": "10 Gbps",
"desc": ""
}
] | 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. | [
"Modes of Operation",
"Configuring Mixed-Rate Mode Operation"
] |
speed (Chassis Cluster) | set chassis cluster control-port speed (1g |10g);
Hierarchy
[edit chassis cluster] | The SRX4600 supports three different PIC types—8-port 10-Gigabit Ethernet PIC, 4-port 40-Gigabit or
100-Gigabit Ethernet PIC, and 4-port 10-Gigabit Ethernet PIC (in a chassis cluster). Out of the four ports
on the 10-Gigabit Ethernet PIC in a chassis cluster, two ports are fabric ports and the other two ports
are chass... | [
{
"name": "1g",
"desc": "Link speed of 1 Gbps"
},
{
"name": "10g",
"desc": "Link speed of 10 Gbps"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1 for SRX4600. | [] | |
speed (Ethernet) | speed (10g | 25g | 40g | 50g | 100g | 200g | 400g); | [edit interfaces interface-name ether-options] | auto-negotiation
Automatically negotiate the speed based on the speed of the other end of the link.
auto
Automatically negotiate the speed (10 Mbps, 100 Mbps, or 1 Gbps) based on the
speed of the other end of the link.
auto-10m-100m
Automatically negotiate the speed (10 Mbps or 100 Mbps) based on the speed of the
other... | [
{
"name": "supported on different routing platforms:",
"desc": "Table 1894: Speed and Autonegotiation support on Routers Router Speed Autonegotiation Supported"
},
{
"name": "(Yes/No) ?",
"desc": ""
},
{
"name": "ACX Series",
"desc": ""
},
{
"name": "10M",
"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.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.1 for the QFX Series.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Metro Routers.
Statement introduced in Junos OS Release 13.2X50-... | [
"Speed and Autonegotiation",
"Port Settings",
"Configuring the Interface Speed",
"Configuring the Interface Speed on Ethernet Interfaces",
"Configuring Gigabit Ethernet Autonegotiation",
"Configuring Gigabit Ethernet Interfaces for EX Series Switches with ELS support",
"Configuring Gigabit and 10-Gigabi... |
speed (Fibre Channel Interfaces) | speed (auto-negotiation | 2g | 4g | 8g); | [edit interfaces interface-name fibrechannel-options] | Configure FC interface speed. | [
{
"name": "auto-negotiation",
"desc": "Automatically negotiate interface speed to match the speed of the attached link (2"
},
{
"name": "2g",
"desc": "2 Gbps link speed"
},
{
"name": "4g",
"desc": "4 Gbps link speed"
},
{
"name": "8g",
"desc": "8 Gbps link speed"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Example: Setting Up Fibre Channel and FCoE VLAN Interfaces in an FCoE-FC Gateway Fabric",
"Converting an Ethernet Interface To a Fibre Channel Interface",
"Configuring a Physical Fibre Channel Interface",
"Understanding Interfaces on an FCoE-FC Gateway"
] |
speed (Gigabit Ethernet interface - MX Series) | speed (1G | 10G); | [edit interfaces intf-name gigether-options] | (MX10003, MX204, MX10008, and MX10016 routers) the 10-Gbps port can operate in 1-Gbps mode
also. When a port operates in 10-Gbps speed, you can change the operating speed to 1-Gpbs using the
configuration speed 1G in this configuration statement. After you commit this configuration, the operating
speed of the 10-Gbps p... | [
{
"name": "1G",
"desc": "Supported ports operate at 1-Gbps speed."
},
{
"name": "10G",
"desc": "Supported ports operate at 10-Gbps speed."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"Port Speed"
] |
speed (Gigabit Ethernet interface) | speed (1g |10g); | [edit interfaces interface-name gigether-options] | Configure the operating speed of the 8-port 10-Gigabit Ethernet PIC from default 10-Gbps port speed
to 1-Gbps port speed. Each of the interfaces in the 8-port 10-Gigabit Ethernet PIC can be independently
configured to 1Gbps or 10Gbps speeds. For information about platforms support, see hardware
compatibility tool (HCT)... | [
{
"name": "1g",
"desc": "Link speed of 1 Gbps"
},
{
"name": "10g",
"desc": "Link speed of 10 Gbps"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [] |
speed (Interfaces) | speed (100m |10m | 1g); | [edit interfaces interface-name speed] | Configure the operating speed for the 2-Port 10 Gigabit Ethernet XPIM. | [
{
"name": "100m",
"desc": "Link speed of 100 Mbps"
},
{
"name": "10g",
"desc": "Link speed of 10 Gbps"
},
{
"name": "10m",
"desc": "Link speed of 10 Mbps"
},
{
"name": "1g",
"desc": "Link speed of 1 Gbps"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Junos OS Release 10.2. | [
"Understanding Ethernet Interfaces",
"Example: Configuring the 2-Port 10-Gigabit Ethernet XPIM Interface"
] |
speed (MX Series DPC) | speed (auto | 1Gbps | 100Mbps | 10Mbps); | [edit interfaces ge-fpc/pic/port] | On MX Series routers with Combo Line Rate DPCs and Tri-Rate Copper SFPs you can set auto
negotiation of speed. To specify the auto negotiation speed, use the speed (auto | 1Gbps | 100Mbps | 10Mbps)
statement under the [edit interface ge-/fpc/pic/port] hierarchy level. The auto option will attempt to
automatically match... | [] | 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 Gigabit Ethernet Autonegotiation"
] |
speed | speed (oc3-stm1 | oc12-stm4 | oc48-stm16 | 10G | 25G | 40G | 50G | 100G | 200G | 400G | 800G); | [edit chassis fpc slot-number pic pic-number port port-number] | Configure the port speed for the ports on a line card or a device with a built-in FPC.
Default
oc3-stm1 | [
{
"name": "100g",
"desc": "Supported ports operate at 100-Gbps speed."
},
{
"name": "10g",
"desc": "Supported ports operate at 10-Gbps speed."
},
{
"name": "1g",
"desc": "Supported ports operate at 1-Gbps speed."
},
{
"name": "200g",
"desc": "Supported ports operate at 20... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2.
Support for PTX3000 and PTX5000 introduced in Junos OS Release 15.1F3 and 16.1R2.
Support for MPC7E (Multi-Rate) introduced in Junos OS Release 15.1F4.
Support for PTX1000 introduced in Junos OS Release 16.1X65.
Support for MX10003 MPC introduced in Junos OS Release 17.3R1... | [
"Configuring Port Speed on Multi-Rate MICs"
] |
spf-options (Protocols IS-IS) | spf-options {
delay milliseconds;
holddown milliseconds;
rapid-runs number;
} | [edit logical-systems logical-system-name protocols isis],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
isis],
[edit protocols isis],
[edit routing-instances routing-instance-name protocols isis] | Configure options for running the shortest-path-first (SPF) algorithm.
Running the SPF algorithm is usually the beginning of a series of larger system-wide events. For
example, the SPF algorithm can lead to interior gateway protocol (IGP) prefix changes, which then lead
to BGP nexthop resolution changes. Consider what ... | [
{
"name": "delay milliseconds",
"desc": "Time interval between the detection of a topology change and when the SPF"
},
{
"name": "holddown milliseconds",
"desc": "Time interval to hold down, or wait before a subsequent SPF algorithm runs after"
},
{
"name": "rapid-runs number",
"desc... | 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. | [
"Understanding Loop-Free Alternate Routes for IS-IS",
"Example: Configuring Node-Link Protection for IS-IS Routes in a Layer 3 VPN"
] |
spf-options (Protocols OSPF) | spf-options {
delay milliseconds;
holddown milliseconds;
rapid-runs number;
} | [edit logical-systems logical-system-name protocols (ospf | ospf3)],
[edit logical-systems logical-system-name protocols ospf topology (default | ipv4-multicast |
name)],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast)],
[edit logical-systems logical-sy... | Configure options for running the shortest-path-first (SPF) algorithm. You can configure the following:
•
A delay for when to run the SPF algorithm after a network topology change is detected.
•
The maximum number of times the SPF algorithm can run in succession.
•
A hold-down interval after the SPF algorithm runs the ... | [
{
"name": "delay milliseconds",
"desc": "Time interval between the detection of a topology change and when the SPF"
},
{
"name": "holddown milliseconds",
"desc": "Time interval to hold down, or to wait before a subsequent SPF algorithm runs"
},
{
"name": "rapid-runs number",
"desc": ... | 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.
Support for Multitopology Routing introduced in Junos OS Release 9.0.
Support for Multitopology Routing introduced in Junos OS Release 9.0 for EX Series switches.
Support for the realm statement introduced in Junos OS Release 9.2.
Support for the realm statement introduced ... | [
"Example: Configuring SPF Algorithm Options for OSPF",
"Example: Configuring Multitopology Routing to Provide Redundancy for Multicast Traffic over",
"Separate Network Paths",
"Example: Configuring Multitopology Routing for Class-Based Forwarding of Voice, Video, and Data",
"Traffic",
"Understanding Multi... |
spi (Junos OS) | spi spi-value; | [edit security ipsec security-association sa-name manual direction (inbound | outbound | bi-
directional)] | Configure the security parameter index (SPI) for a security association (SA). | [
{
"name": "spi-value",
"desc": "An arbitrary value that uniquely identifies which SA to use at the receiving host (the"
}
] | 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. | [] |
spi (Junos-FIPS Software) | spi spi-value; | [edit security ipsec internal security-association manual direction] | The security parameter index (SPI) value used for the internal Routing Engine-to-Routing Engine IPsec
security association (SA) configuration. | [
{
"name": "spi-value",
"desc": "Integer to use for this SPI."
}
] | Crypto Officer—To add and view this statement in the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IPsec for Enabling Internal Communications Between Routing Engines for Junos OS in",
"FIPS Mode"
] |
spi | spi spi-value; | [edit services ipsec-vpn rule rule-name term term-name then manual direction direction] | Configure the SPI for an SA. | [
{
"name": "spi-value",
"desc": "An arbitrary value that uniquely identifies which SA to use at the receiving host (the"
}
] | 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. | [
"Configuring Security Associations"
] |
spid1 | spid1 spid1-string; | [edit interfaces br-pim/0/port isdn-options] | Configure the Service Profile Identifier (SPID). | [
{
"name": "spid1-string",
"desc": "Numeric SPID."
}
] | 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. | [] |
spid2 | spid2 spid2-string; | [edit interfaces br-pim/0/port isdn-options] | Configure an additional SPID. | [
{
"name": "spid2-string",
"desc": "Numeric SPID."
}
] | 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. | [] |
splitting-merging | splitting-merging {
maximum-member-lsps number;
maximum-signaling-bandwidth bps;
merging-bandwidth bps;
minimum-member-lsps number;
minimum-signaling-bandwidth bps;
normalization;
sampling;
splitting-bandwidth bps;
splitting-merging-threshold percent;
no-normalize-same-members; ... | [edit protocols mpls container-label-switched-path lsp-name] | Perform splitting and merging. | [
{
"name": "maximum-member-lsps number",
"desc": "Number of label-switched paths (LSPs) that a container LSP can have as member LSPs at maximum. Default: 1"
},
{
"name": "maximum-signaling-bandwidth",
"desc": ""
},
{
"name": "bandwidth",
"desc": "Amount of bandwidth in bits per secon... | 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.
Statement introduced for QFX Series switches in Junos OS Release 15.1X53-D30. | [] |
spring-te (Dynamic Tunnels) | spring-te {
destination-networks name;
source-routing-path-template name {
(color [ color ... ] | color-any);
}
} | [edit routing-options dynamic-tunnels] | Enable next hop-base dynamic tunnel mode. | [
{
"name": "source-routing-path-",
"desc": ""
},
{
"name": "template",
"desc": "Configure template color mapping for segment routing traffic-engineered (SPRING-TE) dynamic LSP parameters."
},
{
"name": "template-name",
"desc": ""
},
{
"name": "color",
"desc": "Specify set ... | routing | Statement introduced in Junos OS Release 19.2R1. | [
"Understanding Static Segment Routing LSP in MPLS Networks"
] |
spring-te | spring-te {
apply-groups
apply-groups-except
groups
color
discriminator
endpoint
origin-addr
origin-as
... | [edit policy-options policy-statement name from traffic-engineering] | Specify SPRING-TE policy related parameters. | [
{
"name": "color",
"desc": "Color of the SPRING-TE policy candidate path"
},
{
"name": "discriminator",
"desc": "Discriminator of the SPRING-TE policy candidate path"
},
{
"name": "endpoint",
"desc": "Endpoint of the SPRING-TE policy candidate path"
},
{
"name": "origin-addr"... | routing | [
"Link-State Distribution using BGP"
] | |
spring-te-lsp-next-hop | spring-te-lsp-next-hop{
<nexthop>
lsp-source {
bgp;
dtm;
pcep;
static;
}
} | [edit logical-systems name routing-options static route destination],
[edit logical-systems name routing-options rib rib name static route destination]
[edit routing-options static route destination],
[edit routing-options rib rib name static route destination] | The configuration allows you to resolve static route over SR-TE tunnels. | [
{
"name": "nexthop",
"desc": "Name of the SR-TE tunnel to reach destination address."
},
{
"name": "lsp-source",
"desc": "Source of tunnel creation and the following source types are currently supported. If the"
},
{
"name": "bgp",
"desc": ""
},
{
"name": "dtm",
"desc": "... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1. | [] |
spring-traffic-engineering-edit-protocols | spring-traffic-engineering {
lsp-external-controller controller-name;
preference;
traceoptions;
} | [edit protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and rest... | [
{
"name": "preference",
"desc": "(Optional) Configure the preference value for the traffic engineered label-switched paths"
},
{
"name": "(LSPs). Default: 8",
"desc": ""
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2 on MX Series routers. | [] |
spt-only | spt-only; | [edit logical-systems profile-name routing-instances instance-name protocols mvpn mvpn-mode],
[edit routing-instances instance-name protocols mvpn mvpn-mode] | Set the MVPN mode to learn about active multicast sources using multicast VPN source-active routes.
This is the default mode. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Configuring SPT-Only Mode for Multiprotocol BGP-Based Multicast VPNs"
] |
spt-threshold | spt-threshold {
infinity [ policy-names ];
} | [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] | Set the SPT threshold to infinity for a source-group address pair. Last-hop multicast routing devices
running PIM sparse mode can forward the same stream of multicast packets onto the same LAN through
an RPT rooted at the RP or an SPT rooted at the source. By default, last-hop routing devices transition
to a direct SPT... | [] | 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. | [
"Example: Configuring the PIM SPT Threshold Policy"
] |
sql | sql {
disable;
traceoptions {
flag {
all <extensive>;
}
}
} | [edit security alg]
[edit tenants tenant-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 SQL ALG. By default, the SQL ALG is enabled."
},
{
"name": "traceoptions",
"desc": "Configure SQL 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 SQLNET ALG"
] |
squelch | squelch {
method (ais | ql-dnu | rai | shut);
} | [edit chassis synchronization esmc-transmit interfaces]
[edit chassis synchronization output interfaces bits] | ssu-b
Timing quality of a type VI timeReceiver clock (option-1 only).
st2
Clock traceable to Stratum 2 (option-2 only).
st3
Clock traceable to Stratum 3 (option-2 only).
st3e
Clock traceable to Stratum 3E (option-2 only).
st4
Clock traceable to Stratum 4 free-run (option-2 only).
stu
Clock traceable to an unknown quali... | [
{
"name": "method",
"desc": "Specify the method to squelch the transmitting signal. Choose from the following options:"
},
{
"name": "ais",
"desc": "Transmits an alarm indication signal (AIS)."
},
{
"name": "ql-dnu",
"desc": "Transmits a Synchronous Digital Hierarchy (SDH) synchroniz... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.2R1. | [] |
sr-preference-override | sr-preference-override sr-preference-override; | [edit logical-systems name protocols bgp],
[edit protocols bgp] | Configure a preference value that allows the user to override BGP installed segment routing policies and
replace a segment routing traffic engineering preference value that is received from the controller with
an override value for BGP segment routing policies. BGP chooses a higher preference value over a lower
value. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1 on the MX Series and PTX Series with FPC-PTX-P1-
A. | [
"segment-list",
"BGP Egress Traffic Engineering"
] |
srgb (Protocols BGP) | srgb index-range index-range start-label start-label; | [edit fabric protocols bgp source-packet-routing],
[edit logical-systems name protocols bgp source-packet-routing],
[edit logical-systems name routing-instances name protocols bgp source-packet-routing],
[edit logical-systems name tenants name routing-instances name protocols bgp source-packet-
routing],
[edit protoco... | Set the SRGB global block in SPRING | [
{
"name": "index-range",
"desc": "Index to the SRGB start label block Range: 16 through 1048575"
},
{
"name": "start-label",
"desc": "Start range for SRGB label block Range: 16 through 1048575"
}
] | routing | Statement introduced in Junos OS Release 20.4R1. | [] |
srgb (Protocols IS-IS) | srgb {
start-label start-label-value;
index-range index range-value;
} | [edit logical-systems name protocols isis source-packet-routing],
[edit logical-systems name routing-instances name protocols isis source-packet-routing],
[edit protocols isis source-packet-routing],
[edit routing-instances name protocols isis source-packet-routing] | Configure the segment routing global block (SRGB) in source packet routing in networking (SPRING) or
segment routing (SR). The SRGB label range is based on the start label and the index range. The value of
the start label indicates the start of the label range, and the value of the index range along with the
value of t... | [
{
"name": "index-range index-range-value",
"desc": "Index range of the SRGB label block. Range: 32 through 1,048,559"
},
{
"name": "start-label start-label-value",
"desc": "Start of the SRGB label block. Range: 16 through 1,048,575"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2.
Statement introduced in Junos OS Release 17.3 for QFX5110 and QFX5200 switches. | [
"Understanding Adjacency Segments, Anycast Segments, and Configurable SRGB in SPRING",
"Configuring Segment Routing Global Blocks Label Ranges in SPRING for IS-IS Protocol",
"Example: Configuring Segment Routing Global Blocks in SPRING for IS-IS to Increase Network Speed"
] |
srgb-label-range | srgb-label-range <range-start> <range-end> | [edit protocols mpls label-range],
[edit protocols ospf source-packet-routing srgb] | SRGB configured under mpls label-range is termed as global SRGB. The MPLS label range is based on the
start range and the end range. The value of the start range indicates the start of the label range, and the
value of the end range along with the value of the start range indicate the end of the label range. | [
{
"name": "<range-start> <range-end>",
"desc": "Start range and end range of the global SRGB label block."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1. | [] |
srlg | srlg {
srlg-name {
srlg-cost srlg-cost;
srlg-value srlg-value;
}
} | [edit routing-options],
[edit logical-systems logical-system-name routing-options]
[edit protocols mpls interface interface-name] | Configure Shared Risk Link Group (SRLG) parameters. | [
{
"name": "srlg-cost srlg-cost",
"desc": "Specify a cost for the SRLG ranging from 1 through 65535."
},
{
"name": "srlg-value srlg-value",
"desc": "Specify a Group ID for the SRLG ranging from 1 through 4294967295."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Example: Configuring SRLG"
] |
srlg-cost | srlg-cost srlg-cost; | [edit routing-options srlg],
[edit logical-systems logical-system-name routing-options srlg] | Specify a cost for the Shared Risk Link Group (SRLG) ranging from 1 through 65535. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Example: Configuring SRLG"
] |
srlg-value | srlg-value srlg-value; | [edit routing-options srlg],
[edit logical-systems logical-system-name routing-options srlg] | Specify a Group ID for the Shared Risk Link Group (SRLG) ranging from 1 through 4294967295. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Example: Configuring SRLG"
] |
srv6 (Protocols BGP) | srv6 {
locator locator-name {
end-dt4-sid end-dt4-sid | end-dt6-sid end-dt6-sid | end-dt46-sid end-dt46-sid |
non-default;
micro-dt4-sid micro-sid-value | micro-dt6-sid micro-sid-value | micro-dt46-sid
micro-sid-value | non-default;
} | [edit fabric protocols bgp source-packet-routing],
[edit logical-systems name protocols bgp source-packet-routing],
[edit logical-systems name routing-instances name protocols bgp source-packet-routing],
[edit logical-systems name tenants name routing-instances name protocols bgp source-packet-
routing],
[edit protocol... | Enable IPv6 segment routing capability in BGP. You can also configure BGP-based Layer 3 services over
the SRv6 core network with BGP as the control pane and SRv6 as the dataplane. | [
{
"name": "locator locator-name",
"desc": "Specify a name to identify the locator."
},
{
"name": "end-dt4-sid end-dt4-sid",
"desc": "(optional) Specify the SID to enable IPv4 transport over SRv6 core network."
},
{
"name": "end-dt6-sid end-dt6-sid",
"desc": "(optional) Specify the SI... | routing | Statement introduced in Junos OS Release 20.4R1.
end-dt46-sid option introduced in Junos OS Release 22.1R1
micro-dt4-sid micro-sid-value, micro-dt6-sid micro-sid-value, micro-dt46-sid micro-sid-value, and non-default;
options introduced in Junos OS Evolved Release 23.2R1 and Junos OS Release 23.4R1. | [] |
srv6 (Routing Options) | srv6 {
block block-name;
locator locator-name;
no-reduced-srh;
transit-srh-insert;
traceoptions;
oam;
} | [edit routing-instances name routing-options source-packet-routing],
[edit routing-options source-packet-routing],
[edit tenants name routing-instances name routing-options source-packet-routing] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and rest... | [
{
"name": "no-reduced-",
"desc": ""
},
{
"name": "srh",
"desc": "Configure non-reduced Segment Routing Header (SRH) mode of tunnel encapsulation if you want to preserve the entire SID list in the SRH. In an SRv6 domain, an SRv6 segment can have multiple SRHs in an IPv6 header. Note that multiple... | routing | Statement introduced in Junos OS Release 20.3R1. | [
"Overview of SRv6 Network Programming in IS-IS Networks",
"Example: Configuring SRv6 Network Programming in IS-IS Networks"
] |
srv6-binding-sid | srv6-binding-sid {
locator name {
static-sid;
no-reduced-srh;
}
} | [edit logical-systems name protocols source-packet-routing source-routing-path],
[edit protocols source-packet-routing source-routing-path] | Configure Classical SRv6 binding SID.
NOTE: Make sure to configure the classic SRv6 "locator" on page 10418 at the [edit
routing-options] hierarchy level. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.2R1. | [
"Binding SID (BSID) for Static SRv6 TE Tunnels"
] |
srv6-sid | srv6-sid {
as as;
router-id router-id;
prefix prefix;
system-id system-id;
} | [edit logical-systems name policy-options policy-statement name from traffic-engineering],
[edit policy-options policy-statement name from traffic-engineering] | Configure filter options for a traffic engineering policy. You can specify additional parameters, such as
autonomous system (AS), prefix, router ID, and system ID for filtering SRV6 SID related traffic. SRv6
enables IPv6 segment routing capability in BGP. | [
{
"name": "as as",
"desc": "Specify an AS to filter traffic"
},
{
"name": "router-id router-id",
"desc": "Specify an IP prefix to match the router-ID against."
},
{
"name": "prefix",
"desc": "Specify an IPv6 prefix to match against."
},
{
"name": "system-id system-id",
"d... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.3R1. | [
"Link-State Distribution using SRv6"
] |
ssb | ssb slot-number (always | preferred); | [edit chassis redundancy] | On M20 routers, configure which System and Switch Board (SSB) is the primary and which is the
backup.
Default
By default, the SSB in slot 0 is the primary and the SSB in slot 1 is the backup. | [
{
"name": "slot-number",
"desc": "Specify which slot is the primary and which is the backup."
},
{
"name": "always",
"desc": "Define this SSB as the sole device."
},
{
"name": "preferred",
"desc": "Define this SSB as the preferred device of at least two."
}
] | 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 SSB Redundancy on the M20 Router"
] |
ssh (NETCONF) | ssh {
client-alive-count-max number;
client-alive-interval seconds;
connection-limit limit;
port port-number;
rate-limit limit;
} | [edit system services netconf] | Enable access to the NETCONF SSH subsystem using the default port number 830, as specified by RFC
4742. | [
{
"name": "client-alive-count-",
"desc": ""
},
{
"name": "max number",
"desc": "(Optional) Threshold of client-alive responses that can be missed before the sshd process disconnects the client, thereby terminating the NETCONF session. Use this statement in conjunction with the client-alive-inter... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5.
client-alive-count-max and client-alive-interval options added in Junos OS Release 21.1R1 and Junos OS
Evolved Release 21.4R1. | [] |
ssh (System Services) | ssh {
access-disable-external;
authentication-order [method 1 method2...];
authorized-keys-command authorized-keys-command;
authorized-keys-command-user authorized-keys-command-user;
(authorized-principals principal-names | authorized-principals-command program-path)
authorized-principals-file... | [edit system services] | Allow SSH requests from remote systems to access the local device. | [
{
"name": "access-disable-external",
"desc": "Disable external SSH access without disabling internal SSH access."
},
{
"name": "allow-tcp-forwarding",
"desc": "Enable a user to create an SSH tunnel over a CLI session to a disaggregated Junos OS platform by using SSH. Starting in Junos OS Release... | 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.
ciphers, hostkey-algorithm, key-exchange, and macs statements introduced in Junos OS Release 11.2.
max-sessions-per-connection and no-tcp-forwarding statements introduced in Junos OS Release 11.4.
SHA-2 options introduced in Junos OS Release 12.1.
Support for the curve2... | [
"Configuring SSH Service for Remote Access to the Router or Switch",
"Junos OS User Authentication Methods",
"Configuring clear-text or SSL Service for Junos XML Protocol Client Applications",
"Configuring SSH Service for Remote Access to the Disaggregated Junos OS Platform"
] |
ssh | ssh host
<bypass-routing>
<verbose>
<extensive>
<inet | inet6>
<interface interface-name>
<routing-instance routing-instance-name>
<source address>
<v2>
<port port-number> | Use the SSH program to open a connection between a local router or switch and a remote system and
execute commands on the remote system. You can issue the ssh command from the Junos OS CLI to log
in to a remote system or from a remote system to log in to the local router or switch. When executing
this command, you incl... | [
{
"name": "host",
"desc": "Name or address of the remote system."
},
{
"name": "bypass-routing",
"desc": "(Optional) Bypass the normal routing tables and send ping requests directly to a system on an attached network. If the system is not on a directly attached network, an error is returned. Use... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
ssh
user@switch> ssh user
Host key not found from the list of known hosts.
Are you sure you want to continue connecting (yes/no)? yes
Host ?user' added to the list of known hosts.
user@device's pass... | Command introduced before Junos OS Release 7.4.
Command introduced in Junos OS Release 11.1 for the QFX Series.
Command introduced in Junos OS Release 14.1X53-D20 for OCX Series switches.
The command tenant option is introduced in Junos OS Release 19.2R1 for SRX Series. | [
"Configuring SSH Host Keys for Secure Copying of Data"
] | |
ssh-known-hosts | ssh-known-hosts {
fetch-from-server server;
host hostname {
dsa-key key;
ecdsa-sha2-nistp256-key key;
ecdsa-sha2-nistp384-key key;
ecdsa-sha2-nistp521-key key;
ed25519-key key;
rsa-key key;
}
load-key-file filename;
} | [edit security] | Configure SSH support for known hosts and for administering SSH host key updates. | [
{
"name": "fetch-from-server server",
"desc": "Retrieve SSH public host key information from the specified server. Specify by server name or IP address."
},
{
"name": "host host-name",
"desc": "Hostname of the SSH known host entry. This option has the following suboptions:"
},
{
"name": ... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Configuring SSH Host Keys for Secure Copying of Data"
] |
ssl (Services) | ssl {
initiation {
profile profile-name {
actions {
crl {
disable;
if-not-present (allow | drop);
ignore-hold-instruction-code;
}
ignore-server-auth-failure;
}
cl... | [edit services] | 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... | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. The crl statement is supported from 15.1X49-
D30. The protocol-version statement is updated to include tls11 and tls12 from Junos OS Release
15.1X49-D30. | [
"Configuring SSL Forward Proxy",
"Firewall User Authentication Overview"
] |
ssl | ssl {
address ip-address;
hot-reloading;
local-certificate local-certificate;
mutual-authentication {
certificate-authority certificate-authority-profile-name;
client-certificate-request (no-certificate | request-certificate | request-certificate-
and-verify | require-certificate | requi... | [edit system services extension-service request-response grpc] | Configure API connection settings based on Secure Sockets Layer (SSL) technology. | [
{
"name": "address ip-address",
"desc": "Specify the IP address to listen for incoming connections. If you use the default IP address 0.0.0.0, the JET service process (jsd) listens on the IP address in the default routing instance. Default: 0.0.0.0"
},
{
"name": "mutual-authentication",
"desc":... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1.
mutual-authentication, client-certificate-request, and certificate-authority options added in Junos OS Release
17.4R1.
hot-reloading option added in Junos OS Release 20.4R1.
use-pki option added in Junos OS Evolved Release 22.2R1. | [
"JET Service Process Overview",
"Configuring Request-Response Service for JET Applications"
] |
ssl-encryption | ssl-encryption (any | no | yes); | [edit security application-firewall rule-sets rule-set-name rule rule-name match] | Distinguishes between encrypted and unencrypted SSL traffic as match criteria for the rule. In
application firewall usage, this option lets you specify different actions for encrypted and unencrypted
SSL traffic.
Starting in Junos OS Release 18.2R1 application firewall (AppFW) functionality is deprecated. As a part
of ... | [
{
"name": "any",
"desc": "Matches both encrypted and unencrypted SSL traffic."
},
{
"name": "no",
"desc": "Matches unencrypted SSL traffic only."
},
{
"name": "yes",
"desc": "Matches encrypted SSL traffic only."
}
] | 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. | [
"Configuring SSL Forward Proxy"
] |
ssl-inspection | ssl-inspection {
cache-prune-chunk-size number;
key-protection;
maximum-cache-size number;
session-id-cache-timeout seconds;
sessions number;
} | [edit security idp sensor-configuration] | 15.1X49-D100
Starting from 15.1X49, the IDP SSL Inspection feature is deprecated. Juniper recommends use of
SSL Proxy feature. | [
{
"name": "cache-prune-chunk-size",
"desc": "Number of cache entries to delete when pruning SSL session ID cache."
},
{
"name": "Syntax: cache-prune-chunk-size",
"desc": "Number of cache entries to delete when pruning SSL"
},
{
"name": "key-protection",
"desc": "Enabling key protecti... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statements introduced in Junos OS Release 9.3.
Options cache-prune-chunk-size and maximum-cache-size introduced in Junos OS Release 10.2.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [] |
ssl-proxy (Application Services) | ssl-proxy {
profile-name profile-name
} | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
application-services] | Enable SSL proxy and identify the name of the SSL proxy profile to be used. This option is supported on
SRX340, SRX345, SRX550M, SRX1500, SRX4100, SRX4200, SRX5400, SRX5600, and SRX5800
devices. | [
{
"name": "profile-name",
"desc": "SSL proxy profile."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Configuring SSL Forward Proxy"
] |
ssl-termination-profile | ssl-termination-profile profile-name; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
firewall-authentication pass-through]
[edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
firewall-authentication user-firewall] | Specify the SSL termination profile used for SSL offloading. | [
{
"name": "profile-name",
"desc": "Specify the name of the SSL termination profile used to the SSL offload."
}
] | 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. | [
"Security Policies Overview"
] |
ssm-groups | ssm-groups [ ip-addresses ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options multicast] | Configure source-specific multicast (SSM) groups.
By default, the SSM group multicast address is limited to the IP address range from 232.0.0.0 through
232.255.255.255. However, you can extend SSM operations into another Class D range by including the
ssm-groups statement in the configuration. The default SSM address r... | [
{
"name": "ip-addresses",
"desc": "List of one or more additional SSM group addresses separated by a space."
}
] | 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 Source-Specific Multicast Groups with Any-Source Override"
] |
ssm-map (Dynamic IGMP Interface) | ssm-map ssm-map-name; | [edit dynamic-profiles profile-name protocols igmp interface interface-name] | 16.1R5
Starting in Junos OS Release 16.1R5, 16.2R3, 17.1R3, and 17.2R2, the ssm-map statement is deprecated
and no longer supported. Starting in Junos OS Release 17.3R1, the statement is removed from the CLI. | [
{
"name": "ssm-map-name",
"desc": "Name of SSM map."
}
] | 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.
Statement became non-functional in Junos OS Release 15.1R4.
Statement deprecated in Junos OS Release 16.1R5, 16.2R3, 17.1R3, 17.2R2, and 17.3R1.
Statement removed from CLI in Junos OS Release 17.3R1.
Change History Table
Feature support is determined by the platform and re... | [
"Dynamic IGMP Configuration Overview",
"Configuring Dynamic DHCP Client Access to a Multicast Network",
"Source-Specific Multicast Groups Overview"
] |
ssm-map (Dynamic MLD Interface) | ssm-map ssm-map-name; | [edit dynamic-profiles profile-name protocols mld interface interface-name] | 16.1R5
Starting in Junos OS Release 16.1R5, 16.2R3, 17.1R3, and 17.2R2, the ssm-map statement is deprecated
and no longer supported. Starting in Junos OS Release 17.3R1, the statement is removed from the CLI. | [
{
"name": "ssm-map-name",
"desc": "Name of SSM map."
}
] | 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.
Statement became non-functional in Junos OS Release 15.1R4.
Statement deprecated in Junos OS Release 16.1R5, 16.2R3, 17.1R3, 17.2R2, and 17.3R1.
Statement removed from CLI in Junos OS Release 17.3R1.
Change History Table
Feature support is determined by the platform and re... | [
"Dynamic MLD Configuration Overview",
"Example: Configuring SSM Mapping"
] |
ssm-map (Protocols IGMP AMT) | ssm-map ssm-map-name; | [edit logical-systems logical-system-name protocols igmp amt relay defaults],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols igmp
amt relay defaults],
[edit protocols igmp amt relay defaults],
[edit routing-instances routing-instance-name protocols igmp amt relay defaults] | Apply a source-specific multicast (SSM) map to all Automatic Multicast Tunneling (AMT) interfaces. | [
{
"name": "ssm-map-name",
"desc": "Name of the SSM map."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Default IGMP Parameters for AMT Interfaces"
] |
ssm-map (Protocols IGMP) | ssm-map ssm-map-name; | [edit logical-systems logical-system-name protocols igmp interface interface-name],
[edit protocols igmp interface interface-name] | Apply an SSM map to an IGMP interface. | [
{
"name": "ssm-map-name",
"desc": "Name of SSM map."
}
] | 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 SSM Mapping"
] |
ssm-map (Protocols MLD) | ssm-map ssm-map-name; | [edit logical-systems logical-system-name protocols mld interface interface-name],
[edit protocols mld interface interface-name] | Apply an SSM map to an MLD interface. | [
{
"name": "ssm-map-name",
"desc": "Name of SSM map."
}
] | 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 SSM Mapping"
] |
ssm-map (Routing Options Multicast) | ssm-map ssm-map-name {
policy [ policy-names ];
source [ addresses ];
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options multicast] | Configure SSM mapping. | [
{
"name": "ssm-map-name",
"desc": "Name of the SSM map."
}
] | 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 SSM Mapping"
] |
ssm-map-policy (Dynamic IGMP Interface) | ssm-map-policy ssm-map-policy-name; | [edit dynamic-profiles profile-name protocols igmp interface interface-name] | 16.1R5
Starting in Junos OS Release 16.1R5, 16.2R3, 17.1R3, 17.2R2, and 17.3R1, use this statement instead of
the ssm-map statement to associate the policy with the dynamic IGMP interface for all releases with
enhanced subscriber management. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R5.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Configuring SSM Mapping for Dynamic IGMP and MLD",
"Dynamic IGMP Configuration Overview",
"Example: Configuring SSM Maps for Different Groups to Different Sources"
] |
ssm-map-policy (Dynamic MLD Interface) | ssm-map-policy ssm-map-policy-name; | [edit dynamic-profiles profile-name protocols mld interface interface-name] | 16.1R5
Starting in Junos OS Release 16.1R5, 16.2R3, 17.1R3, 17.2R2, and 17.3R1, use this statement instead of
the ssm-map statement to associate the policy with the dynamic MLD interface for all releases with
enhanced subscriber management. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R5.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Configuring SSM Mapping for Dynamic IGMP and MLD",
"Dynamic MLD Configuration Overview",
"Example: Configuring SSM Maps for Different Groups to Different Sources"
] |
ssm-map-policy (IGMP) | ssm-map-policy ssm-map-policy-name; | [edit logical-systems logical-system-name protocols igmp interface interface-name],
[edit protocols igmp interface interface-name] | Apply an SSM map policy to a statically configured IGMP interface.
For dynamically-configured IGMP interfaces, use the ssm-map-policy (Dynamic IGMP Interface) statement. | [
{
"name": "ssm-map-policy-name",
"desc": "Name of SSM map policy."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Example: Configuring SSM Maps for Different Groups to Different Sources"
] |
ssm-map-policy (MLD) | ssm-map-policy ssm-map-policy-name; | [edit logical-systems logical-system-name protocols mld interface interface-name],
[edit protocols mld interface interface-name] | Apply an SSM map policy to a statically configured MLD interface.
For dynamically-configured MLD interfaces, use the ssm-map-policy (Dynamic MLD Interface) statement. | [
{
"name": "ssm-map-policy-name",
"desc": "Name of SSM map policy."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Example: Configuring SSM Maps for Different Groups to Different Sources"
] |
stacked-interface-set (Dynamic Profiles) | stacked-interface-set {
interface-set-name interface-set-name {
interface-set-name interface-set-name;
}
} | [edit dynamic-profiles profile-name interfaces] | For MX Series routers with MPCs that support 5-level hierarchical scheduling, define an interface set
over interface set hierarchy. The child interface set (L3) contains subscriber logical interfaces, and the
parent interface set (L2) contains one or more interface sets as members.
NOTE: For both interface-sets in the... | [
{
"name": "interface-set-name",
"desc": "Name of the interface set to be configured or one of the following Junos OS"
},
{
"name": "predefined variables:",
"desc": ""
},
{
"name": "$junos-aggregation-interface-set-name",
"desc": "L2 interface-set representing a logical intermediate n... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R1. | [
"CoS for Interface Sets of Subscribers Overview"
] |
stacked-vlan-ranges (RADIUS Options) | stacked-vlan-ranges (any | low-outer-tag–high-outer-tag),any; | [edit interfaces interface-name radius-options nas-port-options nas-port-options-name] | Configure the stacked VLAN (S-VLAN) range of subscribers to which the named NAS-Port options
definition applies.
NOTE: You can configure a maximum of 16 NAS-Port options definitions per physical
interface. Each definition can include a maximum of 32 VLAN ranges or 32 S-VLAN
ranges, but cannot include a combination of V... | [
{
"name": "any",
"desc": "Entire S-VLAN range representing all S-VLAN IDs. The inner tag (S-VLAN ID) of the S-VLAN range must be configured as any to represent all inner VLAN ID tags."
},
{
"name": "low-outer-tag",
"desc": "Outer VLAN ID tag representing the lower limit of the S-VLAN range. Ran... | 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. | [
"RADIUS NAS Port Attributes and Options",
"RADIUS NAS Port Attributes and Options"
] |
stacked-vlan-ranges | stacked-vlan-ranges {
access-profile profile-name;
authentication {
packet-types [packet-types];
password password-string;
username-include {
circuit-type;
delimiter delimiter-character;
domain-name domain-name-string;
interface-name;
... | [edit interfaces interface-name auto-configure] | Configure multiple VLANs. Each VLAN is assigned a VLAN ID number from the range.
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.5. | [
"Configuring an Interface to Use the Dynamic Profile Configured to Create Stacked VLANs",
"Configuring Interfaces to Support Both Single and Stacked VLANs"
] |
stacked-vlan-tagging | stacked-vlan-tagging; | [edit interfaces interface-name] | For Gigabit Ethernet IQ interfaces, Gigabit Ethernet, 10-Gigabit Ethernet LAN/WAN PIC, and 100-
Gigabit Ethernet Type 5 PIC with CFP, enable stacked VLAN tagging for all logical interfaces on the
physical interface.
For pseudowire subscriber interfaces, enable stacked VLAN tagging for logical interfaces on the
pseudowi... | [] | 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.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Metro Routers. | [
"Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview"
] |
stale-labels-holddown-period | stale-labels-holddown-period stale-labels-holddown-period; | [edit fabric protocols bgp],
[edit protocols bgp],
[edit routing-instances name protocols bgp] | Configure a time duration for which the BGP allocated MPLS labels are retained after they go stale.
Holding the stale labels without deleting them immediately allows the upstream peers to receive and
install the new labeled advertisements. Note that these MPLS stale labels are retained even when MPLS
fast reroute (FRR)... | [
{
"name": "stale-labels-holddown-period",
"desc": "Specify a time duration in seconds for which the MPLS labels allocated by BGP are kept after they go stale. Range: 1 through 600"
}
] | •
routing—To view this statement in the configuration.
•
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1. | [] |
stale-routes-time (Fabric Control) | stale-routes-time seconds; | [edit fabric protocols fabric-control graceful-restart] | Set the length of time that the fabric control Routing Engine waits to receive messages from devices
before declaring them down. Configure a stale routes time of 1800 seconds if the number of VLAN
members (vmembers) exceeds 32k. | [
{
"name": "seconds",
"desc": "Amount of time that the fabric control Routing Engine waits to receive messages from other devices before declaring them down. Default: 900 seconds Range: 900 to 1800 seconds"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X52-D10. | [
"Understanding Bridging and VLANs on Switches",
"Understanding Routing Engines in the QFabric System"
] |
stale-routes-time | stale-routes-time seconds; | [edit logical-systems logical-routing-name protocols bgp graceful-restart],
[edit logical-systems logical-routing-name routing-instances routing-instance-name protocols bgp
graceful-restart],
[edit protocols bgp graceful-restart],
[edit routing-instances routing-instance-name protocols bgp graceful-restart] | Specify the maximum time that stale routes are kept during a restart. The stale-routes-time statement
allows you to set the length of time the routing device waits to receive messages from restarting
neighbors before declaring them down. | [
{
"name": "seconds",
"desc": "Time the router device waits to receive messages from restarting neighbors before declaring"
}
] | 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. | [
"Configuring Graceful Restart Options for BGP",
"Configuring Graceful Restart for QFabric Systems"
] |
stale-time (Long-Lived Graceful Restart for BGP Restarter) | stale-time interval; | [edit logical-systems logical-system-name protocols bgp family (l2vpn | route-target | inet)
(labeled-unicast | flow) graceful-restart long-lived restarter],
[edit logical-systems logical-system-name protocols bgp group group-name family (l2vpn | route-
target | inet) (labeled-unicast | flow) graceful-restart long-li... | Specify the period of time for which stale routes must be preserved by using le the long-lived graceful
restart capability for BGP sessions on the restarting router. When LLGR restarter is enabled or disabled
for a family or the stale- time is changed, the session is reset so that the new capability can be sent to
the... | [
{
"name": "interval",
"desc": "Period as a measure of the number of weeks, days, hours, minutes, and seconds for which stale routes must be maintained when long-lived graceful restart mechanism is enabled on the restarter router. The range of values for stale-time is from 1 to 16777215 (2^24 – 1) seconds. T... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Graceful Restart Options for BGP",
"Junos OS High Availability User Guide"
] |
stamp (Sampling) | (stamp | no-stamp); | [edit forwarding-options sampling family (inet |inet6 |mpls) output file] | Include a timestamp with each line in the output file. | [
{
"name": "no-stamp",
"desc": "Do not include timestamps. This is the default."
},
{
"name": "stamp",
"desc": "Include a timestamp with each line of packet sampling information."
}
] | 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 Traffic Sampling on MX, M and T Series Routers",
"Collecting Traffic Sampling Output in a File"
] |
standby (Protocols Layer 2 Circuit) | standby; | [edit logical-systems logical-system-name protocols l2circuit local-switching interface
interface-name end-interface interface interface-name backup-neighbor address],
[edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name backup-neighbor address],
[edit logical-system... | Configure the pseudowire to the specified backup neighbor as the standby. When you configure this
statement, traffic flows over both the active and standby pseudowires to the backup device (either a CE
device or PE router). The backup device drops the traffic from the standby pseudowire, unless the active
pseudowire fa... | [] | 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.
Hierarchy levels associated with the backup-neighbor statement added in Junos OS Release 9.2. | [
"Configuring Layer 2 Circuits over Both RSVP and LDP LSPs",
"Configuring Pseudowire Redundancy on the PE Router",
"Example: Configuring Layer 2 Circuit Switching Protection"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.