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 |
|---|---|---|---|---|---|---|---|
simple-filter (Applying to an Interface) | simple-filter {
input filter-name;
} | [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] | Apply a simple filter to an interface. You can apply simple filters to the family inet only, and only in the
input direction. | [
{
"name": "input filter-name",
"desc": "Name of one filter to evaluate when packets are received on 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 7.6. | [
"Configuring Multifield Classifiers"
] |
simple-filter (Interfaces) | simple-filter; | [edit interfaces interfaces-name unit logical-unit-number family family-name] | Apply a simple filter to an interface. You can apply simple filters on ingress interfaces only. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Understanding Ethernet Interfaces"
] |
simple-filter | simple-filter filter-name {
term term-name {
from {
match-conditions;
}
then {
forwarding-class class-name;
loss-priority (high | low | medium);
}
}
} | [edit firewall family inet],
[edit logical-systems logical-system-name firewall family inet] | Configure simple filters. | [
{
"name": "filter-name",
"desc": "Name that identifies the simple filter. The name must be a non-reserved string of not more than 64 characters. No special characters are restricted. To include spaces in the name, enclose them in quotation marks (“ ”)."
},
{
"name": "from",
"desc": "Match packet... | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6.
Logical systems support introduced in Junos OS Release 9.3. | [
"Simple Filter Overview",
"How Simple Filters Evaluate Packets",
"Guidelines for Configuring Simple Filters",
"Guidelines for Applying Simple Filters"
] |
simple-mail-client-service | simple-mail-client-service {
command binary-file-path;
disable;
} | [edit system processes] | Specify the SMTP client process. | [
{
"name": "command binary-file-path",
"desc": "Path to the binary process."
},
{
"name": "disable",
"desc": "Disable the SMTP client process."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
single-home (Junos Fusion) | single-home {
satellite [slot-id |slot-id-range | all];
} | [edit chassis satellite-management] | Specify that the links connecting the satellite device to the aggregation device are connected to the
aggregation device only. | [] | 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"
] |
single-rate | single-rate {
(color-aware | color-blind);
committed-information-rate bps;
committed-burst-size bytes;
excess-burst-size bytes;
} | [edit dynamic-profiles profile-name firewall three-color-policer name],
[edit firewall three-color-policer policer-name],
[edit logical-systems logical-system-name firewall three-color-policer policer-name] | Configure a single-rate three-color policer in which marking is based on the committed information rate
(CIR), committed burst size (CBS), and excess burst size (EBS).
Packets that conform to the CIR or the CBS are assigned low loss priority (green). Packets that exceed
the CIR and the CBS but are within the EBS are as... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Logical systems support introduced in Junos OS Release 9.3.
Support at the [edit dynamic-profiles ... three-color-policer name] hierarchy level introduced in Junos OS
Release 11.4. | [
"Three-Color Policer Configuration Overview"
] |
sip (Application Profile) | sip {
video {
dscp (alias | bits);
forwarding-class class-name;
}
voice {
dscp (alias | bits);
forwarding-class class-name;
}
} | [edit services cos application-profile profile-name] | Set the appropriate dscp and forwarding-class value for SIP traffic.
Default
By default, the system will not alter the DSCP or forwarding class for SIP traffic. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Configuring CoS Rules on Services PICs"
] |
sip (Security) | sip {
application-screen {
protect {
deny (all | varname);
timeout varseconds;
}
unknown-message {
permit-nat-applied;
permit-routed;
}
}
bulk-call-mode;
c-timeout varminutes;
disable;
dscp-rewrite {
code-po... | [edit logical-systems name security alg],
[edit logical-systems name tenants name security alg],
[edit security 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 SIP ALG. Use the set security alg alg-name disable CLI command to disable the SIP"
},
{
"name": "distribution-ip",
"desc": "Configure IPv4 or IPv6 distribution IP addresses. You can configure up to 20 IP"
}
] | 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.
The distribution-ip option introduced in Junos OS Release 18.1R1 for SRX5400, SRX5600, and SRX5800
devices.
The tenant option is introduced in Junos OS Release 18.3R1. | [
"Understanding the SIP ALG"
] |
sip (Services CoS Next Gen Services) | sip {
data {
dscp (alias | bits);
forwarding-class class-name;
}
} | [edit services cos application-profile profile-name] | Configure CoS actions for SIP traffic in an application profile. The application profile can then be used in
CoS rule actions. | [
{
"name": "dscp (alias | bits)",
"desc": "Either a code point alias or a DSCP bit value to apply to the SIP packets."
},
{
"name": "forwarding-class class-name",
"desc": "Forwarding class name to apply to the SIP packets. The choices are:"
},
{
"name": "assured-forwarding",
"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. | [
"Class of Service for Services PICs (Next Gen Services)"
] |
sip | sip {
video {
dscp (alias | bits);
forwarding-class class-name;
}
voice {
dscp (alias | bits);
forwarding-class class-name;
}
} | [edit services cos application-profile profile-name] | Set the appropriate dscp and forwarding-class value for SIP traffic.
Default
By default, the system will not alter the DSCP or forwarding class for SIP traffic.
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 9.3. | [
"Configuring CoS Rules"
] |
sip-call-hold-timeout | sip-call-hold-timeout seconds; | [edit applications application application-name] | Timeout period for SIP calls placed on hold, in seconds. | [
{
"name": "seconds",
"desc": "Length of time the application holds a SIP call open before it times out."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"ALG Descriptions",
"Configuring SIP",
"Examples: Configuring Application Protocols",
"Verifying the Output of ALG Sessions"
] |
sip-password | sip-password simple-ip-password; | [edit interfaces interface-name cellular-options gsm-options profiles profile-name] | Configure the password provided by the service provider for connection to a Global System for Mobile
Communications (GSM) cellular network. | [
{
"name": "simple-ip-password",
"desc": "Password."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Understanding Ethernet Interfaces"
] |
sip-server | sip-server [address | name]; | [edit system services dhcp],
[edit system services dhcp],
[edit system services dhcp pool],
[edit system services dhcp static-binding] | Configure Session Initiation Protocol (SIP) server addresses or names for DHCP servers. | [
{
"name": "address",
"desc": "IPv4 address of the SIP server. To configure multiple SIP servers, include multiple address"
},
{
"name": "name",
"desc": "Fully qualified domain name of the SIP server. To configure multiple SIP servers, include multiple"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Configure DHCP SIP Server",
"Configuring a DHCP Server on Switches"
] |
sip-user-id | sip-user-id simple-ip-user-id; | [edit interfaces interface-name cellular-options gsm-options profiles profile-name] | Configure the username provided by the service provider for connection to a Global System for Mobile
Communications (GSM) cellular network. | [
{
"name": "simple-ip-user-id",
"desc": "Username."
}
] | 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. | [] |
site (Layer 2 VPNs and Circuits) | site site-name {
hot-standby;
site-identifier identifier;
site-preference preference-value {
backup;
primary;
}
interface interface-name {
description text;
remote-site-id remote-site-ID;
}
static incoming-label label;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
l2vpn],
[edit routing-instances routing-instance-name protocols l2vpn] | Specify the site name, site identifier, and interfaces connecting to the site. Allows you to configure a
remote site ID for remote sites. | [
{
"name": "hot-standby",
"desc": "Turn on the protector behavior for the site. This keeps backup pseudowire in continuous standby mode and ready for traffic forwarding."
},
{
"name": "site-identifier",
"desc": ""
},
{
"name": "identifier",
"desc": "Numerical identifier for the site u... | 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.
hot-standby option introduced in Junos OS Release 14.2 for MX Series routers. | [
"Configuring the Site",
"Configuring an MPLS-Based Layer 2 VPN (CLI Procedure)"
] |
site (VPLS Multihoming for FEC 128) | site site-name {
mac-pinning;
active-interface (any | primary interface-name);
best-site;
interface interface-name {
interface-mac-limit limit;
}
mesh-group mesh-group-name;
multi-homing;
site-identifier identifier;
site-preference preference-value;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls],
[edit routing-instances routing-instance-name protocols vpls] | Specify the site name and site identifier for a site. Allows you to configure a remote site ID for remote
sites. | [
{
"name": "site-name",
"desc": "Name of the site."
}
] | 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. | [] |
site (VPLS Multihoming for FEC 129) | site site-name {
active-interface interface-name {
any;
primary interface-name;
}
identifier identifier;
interface interface-name {
preference preference-value;
}
peer-active;
preference (preference-value | backup | primary);
} | [edit logical-systems logical-system-name routing-instances instance-name protocols vpls multi-
homing],
[edit routing-instances instance-name protocols vpls multi-homing] | For VPLS autodiscovery (FEC 129), specify the parameters for a VPLS site that is multihomed to two or
more provider edge (PE) routers.
NOTE: In the VPLS documentation, the word router in terms such as PE router is used to
refer to any device that provides routing functions. | [
{
"name": "site-name",
"desc": "Name of the site."
}
] | 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. | [
"Example: Configuring VPLS Multihoming (FEC 129)"
] |
site-identifier (Layer 2 Circuits) | site-identifier identifier; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
l2vpn site site-name],
[edit routing-instances routing-instance-name protocols l2vpn site site-name] | Specify the numerical identifier for the local Layer 2 VPN site. | [
{
"name": "identifier",
"desc": "The numerical identifier for the Layer 2 VPN site, which can be any number from 1"
}
] | 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 Site",
"Configuring an MPLS-Based Layer 2 VPN (CLI Procedure)"
] |
site-identifier (VPLS) | site-identifier identifier; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
site site-name],
[edit routing-instances routing-instance-name protocols vpls site site-name] | Specify the numerical identifier for the local VPLS site. | [
{
"name": "identifier",
"desc": "Specify the numerical identifier for the local VPLS site. The identifier must be an unsigned"
}
] | 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 VPLS Site Name and Site Identifier"
] |
site-preference | site-preference preference-value {
backup;
primary;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
l2vpn site site-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
site site-name],
[edit routing-instances routing-instance-name protocols l2vpn site site-name],
[edit rout... | Specify the preference value advertised for a particular Layer 2 VPN or VPLS site. The site preference
value is encoded in the BGP local preference attribute. When a PE router receives multiple
advertisements with the same VE identifier, the advertisement with the highest local preference value is
preferred. You can us... | [
{
"name": "preference-value",
"desc": "Specify the preference value advertised for a Layer 2 VPN or VPLS site."
},
{
"name": "backup",
"desc": "Set the preference value to 1."
},
{
"name": "primary",
"desc": "Set the preference value to 65,535."
}
] | 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.
Statement introduced for Layer 2 VPNs in Junos OS Release 9.1. | [
"Configuring a Site Preference and Layer 2 VPN Multihoming",
"Configuring the VPLS Site Preference"
] |
site-range | site-range number; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls],
[edit routing-instances routing-instance-name protocols vpls] | Specify an upper limit on the maximum site identifier that can be accepted to allow a pseudowire to be
brought up. Pseudowires cannot be established to sites with site identifiers greater than the configured
site range. If you issue the show vpls connections command, such sites are displayed as OR (out of range). | [
{
"name": "number",
"desc": "Maximum number of site identifiers. We recommend using the default value. Range: 1 through 65,534 Default: 65,534"
}
] | 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 Site Range"
] |
site-reputation-action | site-reputation-action {
harmful (block | log-and-permit | permit | quarantine);
fairly-safe (block | log-and-permit | permit | quarantine);
moderately-safe (block | log-and-permit | permit | quarantine);
suspicious (block | log-and-permit | permit | quarantine);
very-safe (block | log-and-p... | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering juniper-enhanced profile profile-name category
category-name] | Specify the action to be taken depending on the site reputation returned for all types of URLs whether it
is categorized or uncategorized.
NOTE: Starting with Junos OS Release 17.4R1, the reputation base scores are
configurable. Users can apply global reputation values, provided by the Websense
ThreatSeeker Cloud (TSC)... | [
{
"name": "fairly-safe",
"desc": "Permit, log-and-permit, block, or quarantine a request if a site-reputation of 70 through 79 is returned."
},
{
"name": "harmful",
"desc": "Permit, log-and-permit, block, or quarantine a request if a site-reputation of zero through 59 is returned."
},
{
... | 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.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
size (Interface) | size bytes; | [edit accounting-options file filename] | Specify attributes of an accounting-data log file. | [
{
"name": "bytes",
"desc": "Maximum size of each log file, in bytes, kilobytes (KB), megabytes (MB), or gigabytes (GB). When a"
}
] | 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 Accounting Options, Source Class Usage and Destination Class Usage Options"
] |
size (Next Gen Services Global System Logging) | size size; | [edit services rtlog traceoptions file] | 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": "size",
"desc": "Maximum trace file size Default: 128k Range: through"
}
] | 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"
] |
size (Sampling and Traceoptions) | size bytes; | [edit forwarding-options helperstraceoptions file],
[edit forwarding-options port-mirroring traceoptions file],
[edit forwarding-options sampling family family-name output file],
[edit forwarding-options sampling traceoptions file] | 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": "bytes",
"desc": "Maximum size of each traffic sampling file or trace log file, in kilobytes (KB), megabytes (MB), or"
}
] | 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. | [
"Collecting Traffic Sampling Output in a File",
"Tracing Traffic-Sampling Operations"
] |
size (Security Web Filtering Cache) | size value; | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering surf-control-integrated cache]
[edit security utm feature-profile web-filtering juniper-enhanced cache] | Set the cache size parameters for Web filtering. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The surf-control feature is not supported from Junos OS Release 15.1X49-D10 onwards. For previous
releases, statement introduced in Junos OS Release 9.5.
Statement introduced in Junos OS Release 11.4 .
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
size (Services) | size size; | [edit services ssl traceoptions file file-name] | 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": "size",
"desc": "Specify the maximum trace file size."
}
] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. | [
"Configuring SSL Forward Proxy",
"Firewall User Authentication Overview"
] |
size (System) | size size; | [edit system syslog archive],
[edit system syslog file filename archive] | Configure the maximum amount of data that the Junos OS logging utility writes to a log file logfile
before archiving it (closing it, compressing it, and changing its name to logfile.0.gz). The utility then
opens and writes to a new file called logfile. For information about the number of archive files that the
utility ... | [
{
"name": "size",
"desc": "Maximum size of each system log file, in kilobytes (KB), megabytes (MB), or gigabytes (GB)."
},
{
"name": "of gigabytes",
"desc": "Range: 64 KB through 1 GB Default: 1 MB for MX Series routers the QFX Series, and the OCX Series"
}
] | 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. | [
"Specify Log File Size, Number, and Archiving Properties",
"System Log Explorer"
] |
size (VNF) | size size; | [edit virtual-network-functions] | Size of the memory in kilobytes. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D40. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
size | size bytes; | [edit forwarding-options port-mirroring traceoptions file],
[edit forwarding-options sampling family (inet |inet6 |mpls) output file],
[edit forwarding-options sampling traceoptions file] | 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": "bytes",
"desc": "Maximum size of each traffic sampling file or trace log file, in kilobytes (KB), megabytes (MB),"
}
] | 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 Port Mirroring on M, T MX, ACX, and PTX Series Routers",
"Configuring Traffic Sampling on MX, M and T Series Routers"
] |
skew-timer-disable | skew-timer-disable; | [edit protocols vrrp] | Disable the skew timer, thereby reducing the time required to transition from the backup state to the
primary state.
NOTE: The skew-timer-disable statement is used when there is only one primary router
and one backup router in the network.
Default
By default, the skew timer is enabled for all the VRRP groups. | [] | 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. | [
"Improving the Convergence Time for VRRP",
"Configuring VRRP to Improve Convergence Time"
] |
skip-arp-iteration (RFC 2544 Benchmarking) | skip-arp-iteration; | [edit services monitoring rfc2544 tests test-name test-name] | Disable the Address Resolution Protocol (ARP) test iteration for IPv4 or inet services during a
benchmarking test. This parameter is valid only for an inet family. An ARP test iteration is a 3-second
iteration that is run for all inet tests. The results of this iteration are disregarded in the test result
calculations.... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X53.
Statement introduced in Junos OS Evolved Release 23.4R1. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
skip-multicast-router-port-sync-nlri | skip-multicast-router-port-sync-nlri; | [edit protocols evpn] | Turn off automatically synchronizing the multicast router (mrouter) interface status for an Ethernet
segment identifier (ESI) on multihoming peer border leaf (BL) devices in an EVPN-VXLAN bridged
overlay network.
Some platforms support mrouter port synchronization by default, so you don't need to manually
configure the... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement and automatic synchronization introduced in Junos OS Evolved Releases 25.4R1 and
25.2X100D10. | [] |
sla-iterator-profile | sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
} | [edit protocols oam ethernet connectivity-fault-management maintenance-domain md-name maintenance-
association ma-name mep mep-id remote-mep remote-mep-id] | Configure a remote MEP with an iterator profile and specify the options.
Y.1731 performance monitoring (PM) over Aggregated Ethernet Interfaces is not supported on EX4300
switches. | [
{
"name": "profile-name",
"desc": "Name of the iterator profile configured for a remote MEP. For more information about"
}
] | Configure—To enter configuration mode.
Control—To modify any configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configure an Iterator Profile",
"Configure a Remote MEP with an Iterator Profile",
"Verify the Configuration of an Iterator Profile",
"Manage Iterator Statistics"
] |
sla-iterator-profiles (OAM CFM) | sla-iterator-profiles {
profile-name {
calculation-weight {
delay delay-value;
delay-variation delay-variation-value;
}
cycle-time cycle-time-value;
iteration-period iteration-period-value;
measurement-type two-way-delay;
passive;
}
} | [edit protocols oam ethernet connectivity-fault-management performance-monitoring] | Configure an iterator application and specify the iterator profile options. | [
{
"name": "profile-name",
"desc": "Name of the iterator profile."
}
] | Configure—To enter configuration mode.
Control—To modify any configuration. | Statement introduced in Junos OS Release 11.4. | [
"Configure an Iterator Profile on a Switch (CLI Procedure)"
] |
sla-iterator-profiles | sla-iterator-profiles {
profile-name {
avg-fd-twoway-threshold;
avg-ifdv-twoway-threshold;
avg-flr-forward-threshold;
avg-flr-backward-threshold;
calculation-weight {
delay delay-weight;
delay-variation delay-variation-weight;
}... | [edit protocols oam ethernet connectivity-fault-management performance-monitoring] | Configure an iterator application and specify the iterator profile options. | [
{
"name": "profile-name",
"desc": "Name of the iterator profile. For more information about configuring the iterator profile, see"
}
] | Configure—To enter configuration mode.
Control—To modify any configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configure an Iterator Profile",
"Configure a Remote MEP with an Iterator Profile",
"Verify the Configuration of an Iterator Profile",
"Manage Iterator Statistics"
] |
sla-options | sla-options {
dynamic-load-balancer;
log (disabled | syslog);
max-passive-probe-limit {
interval refresh-interval;
number-of-probes probes;
}
} | [edit security advance-policy-based-routing] | Specify global SLA options for Application Quality of Experience (AppQoE). | [
{
"name": "dynamic-load-",
"desc": ""
},
{
"name": "balancer",
"desc": "Enable the session-based load balancing functionality. When you enable session-based load balancing option, the application traffic distribution depends on the weight value that you configure at the [edit security advance-po... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1.
dynamic-load-balancer option added in Junos OS Release 21.2R1. | [
"Application Quality of Experience",
"Advanced Policy-Based Routing"
] |
sla-rule | sla-rule sla-rule-name {
active-probe-params {
probe-params-name;
}
link-type-affinity strict;
metrics-profile {
metric-profile-name;
}
passive-probe-params {
sampling-percentage {
percentage;
}
sampling-period {
period;
}
... | [edit security advance-policy-based-routing] | Configure an SLA rule.
An SLA rule includes all information required to measure the SLA and to identify whether any SLA
violation has occurred or not. It contains the complete probe profiles, time interval which the profiles
need to be sent, preferred SLA configuration, and so on.
When you configure an APBR rule, you m... | [
{
"name": "active-probe-params probe-params-name",
"desc": "Name of the active probe parameter. Associate the active probe parameter with the SLA rule."
},
{
"name": "affinity",
"desc": "Define link type affinity. For strict affinity, AppQoE ensures that the selected path is always from the pref... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1.
The options preferred-link-type and link-type-affinity are introduced in Junos OS Release 18.4R1.
The options sla-export-factor and violation-count are moved to [edit security advance-policy-based-routing
sla-rule] hierarchy in Junos OS Release 19.2R1.
The options prefer... | [
"Application Quality of Experience",
"Advanced Policy-Based Routing"
] |
sla-tracking | sla-tracking {
route destination-prefix {
metric metric;
next-hop next-hop {;
rpm {
owner name;
test test-name;
}
twamp {
connection name;
test test-name;
}
}
preference prefe... | [edit routing-options] | (Junos OS Evolved only) You configure this configuration statement when you want to install static
routes only if they meet the criteria of a given service level agreement (SLA). You configure an RPM or
TWAMP test instance with the criteria for the SLA at either the [edit services monitoring rpm] or the [edit
services ... | [
{
"name": "metric metric",
"desc": "(Optional) Set the route metric for the destination prefix. The route with the lowest metric is active in the routing table. Default: 1 Range: 1 through 16."
},
{
"name": "next-hop next-hop",
"desc": "(Required) Configure a next-hop address. Must be an IPv4 ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Support introduced in Junos OS Evolved Release 24.4R1. | [] |
slaac-snooping | slaac-snooping {
interface (interface-name | all) {
auto-dad {
retries retry-count;
retrans-interval seconds;
}
mark-interface {
trusted;
}
max-allowed-contentions {
count integer;
duration seconds;
}
}... | [edit forwarding-options access-security] | Configure IPv6 stateless address auto-configuration (SLAAC) snooping. SLAAC enables an IPv6 client to
generate its own addresses using a combination of locally-available information and information
advertised by routers through Neighbor Discovery Protocol (NDP). NDP messages are unsecured, which
makes SLAAC susceptible... | [
{
"name": "link-local expiry",
"desc": ""
},
{
"name": "interval seconds",
"desc": "Configure the expiration period for a link-local address learned by SLAAC. When the lease for the address expires, the snooping device sends a DAD message with the client address as the target. If the client is s... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1. | [
"IPv6 Stateless Address Auto-configuration (SLAAC) Snooping"
] |
slamon-services | slamon-services rfc2544; | [edit chassis fpc slot-number] | (MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003 (with the LC2103 card)
routers only) Enable service-level agreement (SLA) monitoring services support for RFC 2544-based
benchmarking tests on MX Series routers with the MPC1 (MX-MPC1-3D), MPC2 (MX-MPC2-3D), the
16-port 10-Gigabit Ethernet MPC (MPC-3D-16X... | [
{
"name": "rfc2544",
"desc": "Enable support for RFC 2544-based benchmarking tests."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1. | [
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers",
"Configuring an RFC 2544-Based Benchmarking Test",
"Enabling Support for RFC 2544-Based Benchmarking Tests on MX Series Routers"
] |
slave | [edit protocols ptp] | Configure the timeReceiver with parameters.
NOTE: Multicast mode is not supported on the QFX Series, ACX5448, ACX5448-D, and
ACX5448-M devices. | [
{
"name": "announce-interval",
"desc": "Configure the logarithmic mean interval for the announce messages to be sent by the timeTransmitter. Range: 0 through 3 seconds Default: 1"
},
{
"name": "announce-timeout",
"desc": "Specify the number of announce messages a timeReceiver must miss before ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring Precision Time Protocol",
"Example: Configuring Precision Time Protocol",
"Precision Time Protocol Overview",
"Configuring the Precision Time Protocol G.8275.2 Enhanced Profile (Telecom Profile)"
] | |
slice (CoS Interfaces) | slice name {
output-traffic-control-profile profile-name;
} | [edit class-of-service interfaces],
[edit dynamic-profiles name class-of-service interfaces] | Assign output traffic control profiles to slices to provide hierarchical CoS for slices.
At the core of the slice per-hop behavior (PHB) in the data plane is the hierarchical class of service (CoS)
queuing. In the network slicing architecture, each slice has a designated queue set consisting of queues
corresponding to ... | [
{
"name": "name",
"desc": "Name of the network slice"
},
{
"name": "output-traffic-control-profile",
"desc": "Name of the traffic control profile"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.3R1 for MX Series routers. | [
"Hierarchical Class of Service for Network Slicing"
] |
slice (export routing policy action) | slice slice-name | [edit policy-options policy-statement policy-name term term-name then] | Enables a matched route to be marked with the slice identifier corresponding to the slice name specified
in the Class of Service configuration. The slice export routing policy action is supported for routes that
also undergo color or transport-class based route resolution. | [] | •
routing—To view this statement in the configuration
•
routing-control—To add this statement to the configuration | Statement introduced in Junos OS 22.2R1. | [] |
slice (firewall filter action) | slice slice-name | [edit firewall family family-name filter filter-name term term-name then] | Mark packets that pass the match conditions of the rule with the slice identifier corresponding to the
slice name specified in the Class of Service configuration.
NOTE: family-name can be inet, inet6, mpls, or any. | [] | •
firewall—To view this statement in the configuration
•
firewall-control—To add this statement to the configuration | Statement introduced in Junos OS 22.2R1. | [] |
slice (firewall filter match condition) | slice slice-name | [edit firewall family family-name filter filter-name term term-name from] | Match the slice identifier of the packet.
NOTE: family-name can be inet, inet6, mpls, or any. | [] | •
firewall—To view this statement in the configuration
•
firewall-control—To add this statement to the configuration | Statement introduced in Junos OS 22.2R1. | [] |
slow-pfe-alarm | slow-pfe-alarm; | [edit chassis] | Enable the slow Packet Forwarding Engine alarm on a M Series, MX Series, or a T Series router. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1R6, 12.2R5, 12.3R3, 13.1R2, and 13.2R1. | [
"Configuring Slow Packet Forwarding Engine Alarm"
] |
smart-check | smart-check {
ssd-series ssd-series-name {
id id-num {
id-threshold id-threshold-value;
id-value (norm | raw);
id-flag (high | low);
}
}
} | [edit chassis routing-engine disk] | Configure the device to perform health monitoring on the Routing Engine disk and raise alarm when an
error occurs. You can specify threshold value for each smart attribute of the solid-state drive (SSD). The
device raises an alarm when the threshold is breached. You can view the alarms by using the command
show chassis... | [
{
"name": "disk",
"desc": "Configure health check parameters for the SSD."
},
{
"name": "ssd-series ssd-series-name",
"desc": "Specify the SSD series name."
},
{
"name": "id id-num",
"desc": "Specify the ID of the SSD smart attribute for which you are configuring the health check. Yo... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1. | [
"Managing Errors"
] |
smart-optimize-timer | smart-optimize-timer seconds; | [edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls] | Enable the smart optimization timer. When you enable the smart optimization timer on a router, the
Junos OS operates on the assumption that the original LSP path is preferable to any alternate or
secondary path. When you enable the smart optimization timer and an LSP fails and its traffic is
switched to an alternate pa... | [
{
"name": "seconds",
"desc": "(Optional) Specify the number of seconds to wait before switching an LSP back to its original"
}
] | 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 Smart Optimize Timer for LSPs",
"Optimizing Signaled LSPs"
] |
smg-service (Enhanced Subscriber Management) | smg-service {
failover other-routing-engine;
traceoptions {
file filename <files number> <match regular-expression > <size maximum-file-size> <world-
readable | no-world-readable>;
flag flag <disable>;
level level;
no-remote-trace
}
} | [edit system processes] | 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... | [] | trace—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1R3. | [
"Configuring Junos OS Enhanced Subscriber Management",
"Configuring the Subscriber Management Database Trace Log Filename"
] |
smtp-profile (Security Content Security Policy Antispam) | smtp-profile profile-name; | [edit security utm default-configuration]
[edit security utm utm-policy policy-name anti-spam] | Configure a Content Security policy for the antispam SMTP protocol and attach this policy to a security
profile to implement it. | [] | 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. | [] |
smtp-profile (Security Content Security Policy Antivirus) | smtp-profile profile-name; | [edit security utm default-configuration]
[edit security utm utm-policy policy-name anti-virus] | Configure a Content Security policy for the antivirus SMTP protocol and attach this policy to a security
profile to implement it. | [] | 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. | [] |
smtp-profile (Security Content Security Policy Content Filtering) | smtp-profile profile-name; | [edit security utm default-configuration]
[edit security utm utm-policy policy-name content-filtering] | Configure a Content Security policy for the content-filtering SMTP protocol and attach this policy to a
security profile to implement it. | [] | 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. | [] |
snapshot | snapshot {
configuration;
no-configuration;
recovery {
automatic;
configuration-only;
configuration-preference;
no-automatic;
on-upgrade;
}
} | [edit system] | Configure system snapshot options. The configuration and no-configuration options are used for creating
non-recovery snapshots and recovery is used for recovery snapshot.
This statement provides flexibility and control over the snapshot process. | [
{
"name": "configuration",
"desc": "Save configuration in snapshot. When you configure the configuration option and issue the request system snapshot command, it stores the configuration files as part of the non-recovery snapshot."
},
{
"name": "no-configuration",
"desc": "When you configure the... | system—To view this statement in the configuration.
System-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.2R1. | [] |
snext | snext margin; | [edit interfaces interface-name shdsl-options snr-margin],
[edit logical-systems logical-system-name interfaces interface-name shdsl-options snr-margin] | For J Series Services Routers only, configure self-near-end crosstalk (SNEXT) signal-to-noise ratio (SNR)
margin for a SHDSL line. When configured, the line trains at higher than SNEXT threshold. The SNR
margin is the difference between the desired SNR and the actual SNR. | [
{
"name": "margin",
"desc": "Desired SNEXT margin. Possible values are disabled or a margin between –10dB and 10 dB."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [] |
snmp (SNMP Scripts) | snmp {
file filename {
cert-file path;
checksum hash-algorithm hash-value;
oid id {
priority;
}
python-script-user username;
refresh;
refresh-from;
routing-instance routing-instance-name;
... | [edit system scripts] | For Junos OS SNMP scripts, configure the SNMP scripting mechanism.
The remaining statements are explained separately. See CLI Explorer. | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Storing and Enabling Scripts"
] |
snmp | [edit] | 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": "authentication",
"desc": "Provides authentication but no encryption."
},
{
"name": "privacy",
"desc": "Provides authentication and encryption."
}
] | 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. | [] | |
snmp-command | snmp-command command; | [edit applications application application-name] | SNMP command format. | [
{
"name": "command",
"desc": "Supported commands are SNMP get, get-next, set, and trap."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"ALG Descriptions",
"Configuring an SNMP Command for Packet Matching",
"Examples: Configuring Application Protocols",
"Verifying the Output of ALG Sessions"
] |
snmp-community | snmp-community community-index {
community-name community-name;
security-name security-name;
tag tag-name;
} | [edit snmp v3] | Configure the SNMP community. | [
{
"name": "community-index",
"desc": "(Optional) String that identifies an SNMP community."
}
] | 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. | [] |
snmp-options | snmp-options {
backward-traps-only-from-established;
emit-inet-address-length-in-oid;
} | [edit protocols bgp] | Configure the SNMP options and customize the behavior of BGP-related MIBs. By default, SNMP
generates traps when a session moves from a higher state to a lower state. For example, from Active to
Idle or from Established to Idle. This can result in many uninteresting traps, especially when there are a
large number of un... | [
{
"name": "backward-traps-only-from-established",
"desc": "Limit the generation of traps for backward transitions to session states that are moving from Established state only."
},
{
"name": "emit-inet-address-length-in-oid",
"desc": "Emit Length in OID for InetAddress MIB type. This option ensu... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Example: Viewing BGP Trace Files on Logical Systems"
] |
snmp-trap-thresholds (Next Gen Services) | snmp-trap-thresholds {
flow high percent low percent;
nat-address-port high percent low percent;
session high percent low percent;
} | [edit services service-set] | Define snmp traps for Next Gen Services service sets. | [
{
"name": "session",
"desc": "Specify the low and high session threshold limits for generating SNMP traps. The default for high = 90%. The default for low = 70%."
}
] | system | Statement introduced in Junos OS Release 19.3R2. | [] |
snmp-trap-thresholds | snmp-trap-thresholds {
flows high high-threshold | low low-threshold;
nat-address-port high high-threshold | low low-threshold;
}
} | [edit services service-set service-set-name] | Configures SNMP flow thresholds for all flows for a service set or flows for all NAT pools configured for
a service set.. | [
{
"name": "flows high high-threshold",
"desc": "Configure the upper limit for all flows on the service set. The limit is expressed"
},
{
"name": "flows low low-threshold",
"desc": "Configure the lower limit for all flows on the service set . The limit is expressed as"
},
{
"name": "nat-a... | 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. | [
"Configuring Service Set Limitations"
] |
snmp-value-match-msmic (Services NAT Options) | snmp-value-match-msmic; | [edit services service-set service-set-name nat-options] | Match the values for MS-MIC-specific objects in the jnxNatObjects MIB table with the values for MS-
DPC objects. Use the deactivate services service-set service-set-name nat-options snmp-value-match-msmic
configuration mode command to disable this feature. By default, this feature is disabled. | [] | control—To add this statement to the configuration. | Statement introduced with Junos OS Release 13.3R7 | [
"Configuring Service Rules",
"Troubleshooting the Mismatch of jnxNatObjects Values for MS-DPC and MS-MIC"
] |
snoop-pseudowires | snoop-pseudowires; | [edit routing-instances routing-instance-name igmp-snooping-options],
[edit logical-systems logical-system -name routing-instances routing-instance-nameigmp-snooping-
options] | The default IGMP snooping implementation for a VPLS instance adds each pseudowire interface to its
oif list. It includes traffic from the ingress PE that is sent to egress PE even if there is no interest. The
snoop-pseudowires option prevents multicast traffic from traversing the pseudowire (to egress PEs) unless
there... | [] | 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. | [
"Example: Configuring IGMP Snooping"
] |
snoop-segment (TDF Domain Selection) | snoop-segment snoop-segment-name; | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from] | Specify the snoop segment that matches the RADIUS request.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selected. | [
{
"name": "snoop-segment-name",
"desc": "Name of the snoop segment."
}
] | 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 Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview",... |
snoop-segments (RADIUS) | snoop-segments snoop-segment-name {
destination-ip-address destination-address;
<destination-port destination-port;>
<request-cache-timeout timeout;>
shared-secret secret;
source-interface source-interface;
<source-ip-address source-address;>
} | [edit access radius] | Specify which accounting messages to snoop. You must specify at least the destination IP address for
the accounting messages, the shared secret, and the source interface. | [
{
"name": "snoop-segment-name",
"desc": "Name for the snoop segment. The maximum length is 32 characters."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring Snooping of RADIUS Accounting Requests for IP-Based Subscribers",
"Snooping RADIUS Accounting Requests for IP-Based Subscribers Overview",
"IP-Based Subscriber Setup Overview"
] |
snoop-segments (TDF Gateway) | snoop-segments [snoop-segment-name]; | [edit unified-edge gateways tdf gateway-name aaa] | Specify one or more snoop segments that control RADIUS accounting request snooping for the TDF
gateway. The snoop segments must already be configured at the [edit access radius] hierarchy level. | [
{
"name": "snoop-segment-name",
"desc": "Name of a snoop segment."
}
] | 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 Snooping of RADIUS Accounting Requests for IP-Based Subscribers",
"Snooping RADIUS Accounting Requests for IP-Based Subscribers Overview",
"IP-Based Subscriber Setup Overview"
] |
snr-margin | snr-margin {
snext margin;
} | [edit interfaces interface-name shdsl-options],
[edit logical-systems logical-system-name interfaces interface-name shdsl-options] | For J Series Services Routers only, configure the SHDSL signal-to-noise ratio (SNR) margin. The SNR
margin is the difference between the desired SNR and the actual SNR. Configuring the SNR creates a
more stable SHDSL connection by making the line train at a SNR margin higher than the threshold. If
any external noise be... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [] |
sockets | sockets value; | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering websense-redirect profile profile-name] | Enter the number of sockets used for communicating between the client and server. The default is 1. | [] | 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. | [] |
soft-gre | soft-gre group-name {
destination-networks [prefix];
dynamic-profile profile-name;
tunnel {
tunnel-name {
remote-address mdu-ip-address;
}
}
service-interface psn;
source-address wag-ip-address;
<tunnel-idle-timeout seconds>;
} | [edit services] | Configure the conditions for enabling dynamic-bridged generic routing encapsulation (GRE) tunnel
creation on the MX Series router Wi-Fi access gateway (WAG). You can configure the tunnel conditions
for both IPv4 and IPv6 networks. The IP addresses for source-address, destination-networks, and remote-
address specified ... | [
{
"name": "destination-networks [prefix]",
"desc": "Use the specified IP subnets from which soft-GRE connection requests from the customer can be processed."
},
{
"name": "group-name",
"desc": "Name of the dynamic GRE tunnel group."
},
{
"name": "dynamic-profile",
"desc": ""
},
{... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1.
The option tunnel added in Junos OS Release 25.2R1.
Statement support for IPv6 soft-GRE tunnels introduced in Junos OS Release 25.4R1. | [
"Wi-Fi Access Gateway Deployment Model Overview",
"Supported Access Models for Dynamic-Bridged GRE Tunnels on the Wi-Fi Access Gateway",
"Configuring Conditions for Enabling Dynamic-Bridged GRE Tunnel Creation",
"Static Subscribers Over Statically Configured Soft GRE Tunnels"
] |
soft-limit | soft-limit bandwidth; | [edit services dynamic-flow-capture capture-group client-name content-destination identifier] | Specify a bandwidth threshold at which congestion notifications are sent to each control source of the
criteria that point to this content destination. If the control source is configured with the syslog
statement, a log message also be generated. | [
{
"name": "bandwidth",
"desc": "Soft limit threshold, in bits per second."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Configuring the Content Destination"
] |
soft-limit-clear | soft-limit-clear bandwidth; | [edit services dynamic-flow-capture capture-group client-name content-destination identifier] | Specify a bandwidth threshold at which the latch set by the soft-limit threshold is cleared. | [
{
"name": "bandwidth",
"desc": "Soft-limit clear threshold, in bits per second."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Configuring the Content Destination"
] |
soft-preemption (Protocols MPLS) | soft-preemption; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name] | Attempt to establish a new path for a preempted LSP before tearing it down. | [] | 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 MPLS Soft Preemption"
] |
soft-preemption (Protocols RSVP) | soft-preemption {
cleanup-timer seconds;
} | [edit logical-systems logical-system-name protocols rsvp preemption],
[edit protocols rsvp preemption] | Enable soft preemption to attempt to establish a new path for a preempted LSP before tearing it down. | [
{
"name": "cleanup-timer",
"desc": "A value of 0 disables soft preemption."
}
] | 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 MPLS Soft Preemption"
] |
software-upgrade | software-upgrade | [edit chassis high-availability] | Enable software upgrade mode. Use this configuration option when you want to upgrade your security
device in Multinode High Availability. This statement marks SRG status as offline and diverts the transit
traffic to the other node.
Once you complete the software upgrade, delete the statement on both nodes using the com... | [] | interface | Statement introduced in Junos OS Release 22.3R1. | [
"Software Upgrade in Multinode High Availability"
] |
softwire-concentrator | softwire-concentrator {
ds-lite ds-lite-softwire-concentrator {
auto-update-mtu;
flow-limit flow-limit | session-limit-per-prefix session-limit-per-prefix;
mtu-v6 bytes;
softwire-address address;
}
map-e
v6rd v6rd-softwire-concentator {
ipv4-prefix ipv4-prefix;
... | [edit services softwire] | Configure settings for a softwire concentrator.
Softwires are supported on the MS-DPC, MS-100, MS-400, and MS-500 line cards. Starting in Junos OS
release 17.4R1, softwires for DS-Lite are supported on MX Series routers with MS-MPCs and MS-MICs. | [] | 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 option introduced in Junos OS Release 18.2R1 for MX Series Routers with MPC and MIC
interfaces. | [
"Configuring a DS-Lite Softwire Concentrator",
"Configuring a 6rd Softwire Concentrator"
] |
softwire-name (Next Gen Services) | softwire-name v6rd-softwire-concentrator {
ipv4-prefix ipv4-prefix;
mtu-v4 number-of-bytes;
softwire-concentrator address;
softwire-type v6rd;
v6rd-prefix v6rd-prefix
} | [edit services softwires] | Configure a 6rd softwire concentrator. A 6rd softwire allows an IPv6 end user to send traffic over an
IPv4 network to reach an IPv6 network. The softwire concentrator decapsulates IPv6 packets that were
encapsulated in IPv4 packets by a software initiator at the customer edge WAN, and forwards the
packets for IPv6 rout... | [
{
"name": "ipv4-prefix ipv4-prefix",
"desc": "IPv4 prefix of the customer edge (CE) network."
},
{
"name": "mtu-v4 number-of-bytes",
"desc": "The size, in bytes, of the maximum transmission unit for IPv6 packets encapsulated in IPv4. Compute this as the maximum expected IPv4 packet size plus 20.... | 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"
] |
softwire-name (Security) | softwire-name name {
mtu-v6 mtu-v6;
post-fragmentation(off | on);
power-mode-disable;
pre-fragmentation(clear-df-bit | off | on);
services-offload-off;
softwire-concentrator softwire-concentrator;
softwire-type(IPv4-in-IPv6);
} | [edit security softwires],
[edit security softwires softwire-types] | Configure softwire object. | [
{
"name": "mtu-v6",
"desc": "MTU for the softwire tunnel. Range: 1280 through 9192"
},
{
"name": "post-fragmentation",
"desc": "Post fragmentation options for the softwire tunnel."
},
{
"name": "off",
"desc": "Disable post-fragmentation for the softwire tunnel."
},
{
"name":... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 24.2R1. | [] |
softwire-options | softwire-options {
dslite-ipv6-prefix-length dslite-ipv6-prefix-length ;
} | [edit services service-set service-set-name] | Specify the IPv6 prefix length associated with a subscriber’s basic broadband bridging device that is
subject to a limited number of sessions.
This feature is supported on MX Series routers equipped with MS-DPCs. Starting in Junos OS Release
18.2R1, this option is also supported on MS-MPCs and MS-MICs. | [
{
"name": "dslite-ipv6-prefix-length",
"desc": "Subnet prefix representing the size of the subnet subject to session limitation. Values: 56, 64, 96, 128"
},
{
"name": "Default: 0",
"desc": "no limitation."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1.
Support added in Junos OS 20.2R1 for Next Gen Services on MX240, MX480, and MX960 routers. | [
"DS-Lite Per Subnet Limitation Overview"
] |
softwire-rules | (softwire-rule rule-name | softwire-rule-sets rule-set-name); | [edit services service-set service-set-name] | Specify the DS-Lite or 6rd rules or rule set included in this service set. You can configure multiple rules;
however, you can only configure one rule set for each service set.
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-Li... | [
{
"name": "rule-name",
"desc": "Identifier for the collection of terms that constitute this rule."
},
{
"name": "rule-set-name",
"desc": "Identifier for the set of rules to be included."
}
] | 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 Service Rules"
] |
softwire-types (Next Gen Services) | softwire-types {
ds-lite ds-lite-softwire-concentrator {
auto-update-mtu;
flow-limit flow-limit | session-limit-per-prefix session-limit-per-prefix;
mtu-v6 bytes;
softwire-address address;
}
map-e
v6rd v6rd-softwire-concentator {
ipv4-prefix ipv4-prefix;
v... | [edit services softwires] | Configure ds-lite, 6rd and MAP-E softwire objects. | [
{
"name": "ds-lite",
"desc": "Specify options for DS-Lite softwites."
},
{
"name": "v6rd",
"desc": "Specify options for v6rd softwites."
},
{
"name": "map-e",
"desc": "Specify options for map-e softwires."
},
{
"name": "auto-update-mtu",
"desc": "This option is not curren... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.2 for Next Gen Services on MX240, MX480 and MX960. | [] |
softwires (Next Gen Services) | softwires {
rule-set name {
match-direction (input | output);
rule name {
then {
(ds-lite ds-lite | map-e map-e | v6rd v6rd);
}
}
}
softwire-name na... | [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... | [] | system | Statement introduced in Junos OS Release 20.2 for Next Gen Services. | [] |
softwires | softwires {
rule-set name {
match-direction (input | output);
rule name {
then {
v6rd v6rd;
}
}
}
softwire-name name {
ipv4-prefix ipv4-prefix;
mtu-v4 mtu-v4;
mtu-v6 mtu-v6;
post-fragmentation(off | on);
... | [edit logical-systems name security],
[edit security]
[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... | [
{
"name": "map-e",
"desc": "Name of the map-e rules configuration."
},
{
"name": "softwire-name",
"desc": "Name of the softwire configuration."
},
{
"name": "traceoptions",
"desc": "Traceoptions for Network Security DS-Lite."
},
{
"name": "mtu-v6",
"desc": "Specify the co... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 12.1. | [] |
softwires-rule-set (Service Set Next Gen Services) | softwires-rule-set softwire-rule-set-name; | [edit services service-set service-set-name] | Specify the softwire rule-set that contains the rule to be used with the service set. | [] | 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"
] |
solicit-router-advertisement-unicast | solicit-router-advertisement-unicast; | [edit protocols router-advertisement interface interface-name] | Configure devices to send router advertisements as unicast in response to the router solicitation
message sent by IPv6 routers. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1R1 onwards. | [
"https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/config-",
"guide-routing/config-guide-routing-neighbor-discovery.html"
] |
sonet | sonet {
device-count number;
} | [edit chassis aggregated-devices] | Configure properties for SONET/SDH aggregated devices on the router. | [] | 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 Junos OS for Supporting Aggregated Devices"
] |
sophos-engine | sophos-engine {
file-reputation-action {
potentially-unwanted-applications (block | log-and-permit | permit);
unknown (block | log-and-permit | permit);
}
server {
host host;
port port;
... | [edit security utm default-configuration anti-virus],
[edit logical-systems name security utm default-configuration anti-virus],
[edit logical-systems name tenants name security utm default-configuration anti-virus],
[edit tenants name security utm default-configuration anti-virus] | Configure the Content Security Sophos antivirus feature. | [
{
"name": "file-reputation-action",
"desc": "Specify the Sophos file reputation action. File reputation based actions provides more control over security. potentially-unwanted-applications (block | log-and-"
},
{
"name": "permit | permit)",
"desc": "Specify Sophos file reputation actions such as... | 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.
The [edit security utm default-configuration anti-virus] hierarchy level is introduced in Junos OS Release
18.2R1.
The file-reputation-action and proxy-profile options are introduced in Junos OS Release 24.4R1. | [] |
source (Application Identification) | source ip ip-address-prefix; | [edit services application-identification application application-name address-mapping] | Specify the source IP address for address mapping-based application identification. | [
{
"name": "ip-address-prefix",
"desc": "IP address and prefix for matching."
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Application Identification Overview",
"Configuring Custom Application Signatures",
"Application Identification Overview"
] |
source (Bridge Domains) | source ip-address; | [edit bridge-domains bridge-domain-name protocols igmp-snooping interface interface-name static
group],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-
snooping interface interface-name static group],
[edit routing-instances routing-instance-name bridge-domains bridge-d... | Statically define multicast group source addresses on an interface. | [
{
"name": "ip-address",
"desc": "IP address to use as the source for the group."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Example: Configuring IGMP Snooping"
] |
source (Chassis Synchronization) | source {
(bits | gps) {
priority number;
quality-level (prc | prs |sec | smc | ssu-a | ssu-b | st2 | st3 | st3e | st4 | stu | tnc);
request request (force-switch | lockout);
}
interfaces interface-name {
priority number;
quality-level (prc | prs |sec | smc | ssu-a | s... | [edit chassis synchronization] | Configure a clock source used by the clock selection process. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"External Clock Synchronization Overview for ACX Series Routers",
"Configuring External Clock Synchronization for ACX Series Routers",
"Synchronous Ethernet Overview",
"show chassis synchronization"
] |
source (Commit Scripts) | source url; | [edit system scripts commit file filename] | Specify the location of the master source file for a commit script. When you issue the set refresh
configuration mode command at the same hierarchy level, the local copy of the script is overwritten by
the version stored at the specified URL. If the load-scripts-from-flash statement is configured, the device
refreshes ... | [
{
"name": "url",
"desc": "The source specified as an HTTPS URL, HTTP URL, FTP URL, or scp-style remote file specification. If you specify an HTTPS URL, you must also configure the cert-file statement at the same hierarchy level. Specify the path to the certificate (Root CA or self-signed) that the device wi... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configure and Use a Master Source Location for a Script",
"Example: Configure and Refresh from the Master Source for a Script",
"Overview of Updating Scripts from a Remote Source"
] |
source (Distributed IGMP) | source source-address <distributed>; | [edit protocols pim static group multicast-group-address] | Specify an IP unicast source address for a multicast group being statically configured on an interface. | [
{
"name": "distributed",
"desc": "(Optional) Enable a static join for multiple multicast address groups so that all Packet Forwarding Engines receive traffic, but preprovision only one multicast group."
},
{
"name": "source-address",
"desc": "Specific IP unicast source address for a multicast gr... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X50. | [
"Enabling Distributed IGMP",
"Junos OS Multicast Protocols User Guide",
"Junos OS Multicast Protocols User Guide"
] |
source (Dynamic IGMP Interface) | source source; | [edit dynamic-profiles profile-name protocols igmp interface interface-name static] | Specify the IP version 4 (IPv4) unicast address to send data on an interface. | [
{
"name": "source",
"desc": "IPv4 unicast address."
}
] | 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. | [
"Dynamic IGMP Configuration Overview",
"Configuring Dynamic DHCP Client Access to a Multicast Network",
"Enabling IGMP Static Group Membership"
] |
source (Dynamic MLD Interface) | source ip-address {
source-count number;
source-increment increment;
} | [edit dynamic-profiles profile-name protocols mld interface interface-name static group multicast-
group-address] | IP version 6 (IPv6) unicast source address for the multicast group being configured on a dynamic
interface. | [
{
"name": "ip-address",
"desc": "One or more IPv6 unicast addresses."
}
] | 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. | [
"Dynamic MLD Configuration Overview",
"Enabling MLD Static Group Membership"
] |
source (Event Scripts) | source url; | [edit event-options event-script file filename] | Specify the location of the master source file for an event script. When you issue the set refresh
configuration mode command at the same hierarchy level, the local copy of the script is overwritten by
the version stored at the specified URL. If the load-scripts-from-flash statement is configured, the device
refreshes ... | [
{
"name": "url",
"desc": "Master source file for an event script specified as an HTTPS URL, HTTP URL, FTP URL, or scp-style remote file specification. If you specify an HTTPS URL, you must also configure the cert-file statement at the same hierarchy level. Specify the path to the certificate (Root CA or sel... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configure and Use a Master Source Location for a Script",
"Example: Configure and Refresh from the Master Source for a Script"
] |
source (GRE Encapsulation) | source {
address address;
} | [edit interfaces fti number unit logical-unit-number tunnel encapsulation (gre | ipip | udp )] | Specify the source address of the tunnel.
Default
Source address is not required. Not configuring a source address indicates that the tunnel will terminate
on the destination address.
NOTE: Starting in Junos OS Evolved Release 20.3R1, when you do not configure the
"tunnel-termination" on page 31418, configuring the sou... | [
{
"name": "address",
"desc": "Interface address prefix of the source address."
}
] | interface | Statement introduced for GRE tunnels in Junos OS Evolved Release 20.2R1.
Statement introduced for IPIP tunnels in Junos OS Evolved Release 20.4R1.
Statement introduced for UDP tunnels in Junos OS Evolved Release 21.1R1. | [] |
source (Interfaces) | source source-address; | [edit interfaces interface-name unit logical-unit-number tunnel address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
tunnel address] | Specify the source address of the tunnel.
Default
If you do not specify a source address, the tunnel uses the unit’s primary address as the source address
of the tunnel. | [
{
"name": "source-address",
"desc": "Address of the local side of the tunnel. This is the address that is placed in the outer IP"
}
] | 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. | [
"Tunnel Services Overview",
"multicast-only",
"Junos OS Services Interfaces Library for Routing Devices"
] |
source (JET Scripts) | source url; | [edit system extensions extension-service application file filename] | Specify the location of the master source file for a JET script. When you issue the set refresh
configuration mode command at the same hierarchy level, the local copy of the script is overwritten by
the version stored at the specified URL. If the load-scripts-from-flash statement is configured, the device
refreshes the... | [
{
"name": "url",
"desc": "Master source file for a JET script specified as an HTTPS URL, HTTP URL, FTP URL, or scp-style remote file specification. If you specify an HTTPS URL, you must also configure the cert-file statement at the same hierarchy level. Specify the path to the certificate (Root CA or self-s... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"Configuring and Using a Master Source Location for a Script",
"Example: Configuring and Refreshing from the Master Source for a Script"
] |
source (Multicast VLAN Registration) | source {
groups group-prefix;
} | [edit protocols igmp-snooping vlan vlan-name data-forwarding] | Configure a VLAN to be a multicast source VLAN (MVLAN), and specify the IP address range of the
multicast source groups.
To configure a data-forwarding VLAN as an MVLAN, you also configure one or more multicast receiver
VLANs (MVR receiver VLANs) with hosts that might be interested in receiving traffic on the MVLAN for... | [
{
"name": "groups",
"desc": ""
},
{
"name": "group-prefix",
"desc": "IP address range of the source groups. Each MVLAN must have exactly one groups statement. If there are multiple MVLANs on the switch, their group ranges must be unique."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Example: Configuring Multicast VLAN Registration on EX Series Switches Without ELS",
"Configuring Multicast VLAN Registration on EX Series Switches"
] |
source (Op Scripts) | source url; | [edit system scripts op file filename] | Specify the location of the master source file for an op script. When you issue the set refresh
configuration mode command at the same hierarchy level, the local copy of the script is overwritten by
the version stored at the specified URL. If the load-scripts-from-flash statement is configured, the device
refreshes the... | [
{
"name": "url",
"desc": "Master source file for an op script specified as an HTTPS URL, HTTP URL, FTP URL, or scp-style remote file specification. If you specify an HTTPS URL, you must also configure the cert-file statement at the same hierarchy level. Specify the path to the certificate (Root CA or self-s... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configure and Use a Master Source Location for a Script",
"Example: Configure and Refresh from the Master Source for a Script"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.