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 |
|---|---|---|---|---|---|---|---|
sbl | sbl {
profile profile-name {
custom-tag-string [string];
(sbl-default-server | no-sbl-default-server);
spam-action (block | tag-header | tag-subject);
}
} | [edit security utm default-configuration]
[edit security utm feature-profile anti-spam] | Configure Content Security server-based antispam features. | [] | 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. | [] |
sbl-default-server | sbl-default-server; | [edit security utm default-configuration]
[edit security utm feature-profile anti-spam sbl profile profile-name] | Enable the default SBL server lookup. You should enable this feature if you are using server-based spam
filtering. (The SBL server is predefined on the device. It ships with the name and address of the SBL
server.) | [] | 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. | [] |
scale-mode | scale-mode {
adaptive-interval (interval | no-adaptive-sampling);
disable;
} | [edit protocols sflow] | Configure scale-mode to manage adaptive sampling behavior in the sFlow technology configuration. | [
{
"name": "adaptive-interval",
"desc": "Interval for adaptive sampling."
},
{
"name": "interval",
"desc": "Adaptive sampling interval in seconds. You can set a fixed polling interval for"
},
{
"name": "no-adaptive-sampling",
"desc": "Disables adaptive sampling completely. It also ter... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [] |
scale-mode | scale-mode | [edit firewall family filter] | Programs the filter on a single replication instance instead of the default behavior of programming the
filter on two replication instances. Use scale-mode to accommodate more firewall filter terms, when the
need is to provide more scale than performance. | [] | 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.1 | [] |
scale-optimized | scale-optimized; | [edit firewall family protocol-family-name filter filter-name],
[edit logical-systems logical-system-name firewall family protocol-family-name filter filter-
name] | Specify to optimize the interface specific firewall filters in the PFE itself.
When an interface specific firewall filter is configured with multiple Interface bind point instances, the
PTX halp software allocates resources for each interface instance separately, and the resources
consumption is directly proportional ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1. | [
"Guidelines for Configuring Firewall Filters"
] |
scan-extension | scan-extension filename; | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name scan-
options] | For antivirus file extension scanning, configure the scan extension setting by specifying the name of the
defined file extension list. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Kaspersky feature is not supported from Junos OS Release 15.1X49-D10 onwards. For previous
releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
scan-mode | scan-mode (all | by-extension); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name scan-
options] | 15.1X49-D10
The scan-mode is not supported from Junos OS Release 15.1X49-D10 onwards. | [
{
"name": "all",
"desc": "Scan all files."
},
{
"name": "by-extension",
"desc": "Scan only files with extensions specified in a file extension list custom object."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The scan-mode is not supported from Junos OS Release 15.1X49-D10 onwards. For previous releases,
the statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Change History Table
Feature support is determined by the platform an... | [] |
scan-options (Security Antivirus Avira Engine) | scan-options {
content-size-limit value;
decompress-layer-limit value;
(no-pre-detection | pre-detection);
timeout value;
(uri-check|no-uri-check);
} | [edit security utm default-configuration anti-virus] | Configure the antivirus feature to scan specific types of traffic based on various scanning configuration
parameters. The scan engine scans the data by accessing the virus pattern database. You can download
and uninstall the Avira scan engine. The antivirus module is the software subsystem on the gateway
device that sc... | [] | 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.
The [edit antivirus scan-options] hierarchy level is deprecated in Junos OS Release 18.2R1. | [] |
scan-options (Security Antivirus Juniper Express Engine) | scan-options {
content-size-limit value;
(intelligent-prescreening | no-intelligent-prescreening);
timeout value;
} | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name] | 15.1X49-D10
The scan-options (Security Antivirus Juniper Express Engine) is not supported from Junos OS
Release 15.1X49-D10 onwards. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The scan-options (Security Antivirus Juniper Express Engine) is not supported from Junos OS Release
15.1X49-D10 onwards. For previous releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Change History Table
Featu... | [] |
scan-options (Security Antivirus Kaspersky Lab Engine) | scan-options {
content-size-limit value;
decompress-layer-limit value;
(intelligent-prescreening | no-intelligent-prescreening);
scan-extension filename;
scan-mode (all | by-extension);
timeout value;
} | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name] | 15.1X49-D10
The Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10 onwards. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10 onwards. For
previous releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Change History Table
Feature support is determined by ... | [] |
scan-options (Security Antivirus Sophos Engine) | scan-options {
content-size-limit value;
(no-uri-check | uri-check);
timeout value;
} | [edit security utm default-configuration antivirus scan-options] | Configure the antivirus feature to scan specific types of traffic based on various scanning configuration
parameters. | [] | 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] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
sccp | sccp {
application-screen {
call-flood {
threshold rate;
}
unknown-message {
permit-nat-applied;
permit-routed;
}
}
disable;
dscp-rewrite {
code-point string;
}
inactive-media-timeout value-in-seconds;
traceoptions ... | [edit logical-systems name security alg],
[edit logical-systems name tenants name security alg],
[edit security alg],
[edit services alg],
[edit tenants name security alg] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "disable",
"desc": "Disable the SCCP ALG. By default, the SCCP ALG is enabled."
}
] | 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 SCCP ALGs"
] |
scheduler (Dynamic Scheduler Maps) | scheduler scheduler-name; | [edit dynamic-profiles profile-name class-of-service scheduler-maps map-name forwarding-class class-
name] | Associate a scheduler with a scheduler map in a dynamic profile. | [
{
"name": "scheduler-name",
"desc": "Either the specific name of the scheduler configuration block or the scheduler variable"
}
] | 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. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Schedulers in a Dynamic Profile for Subscriber Access",
"Dynamic Variables Overview"
] |
scheduler (Fabric Queues) | scheduler scheduler-name; | [edit class-of-service fabric scheduler-map priority (high | low)] | Define scheduler name. For M320, MX Series, T Series routers and for EX Series switches only, specify a
scheduler to associate with a fabric queue. For fabric CoS configuration, schedulers are restricted to
transmit rates and drop profiles. | [
{
"name": "scheduler-name",
"desc": "Name of the scheduler configuration block."
}
] | 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. | [
"Associating Schedulers with Fabric Priorities"
] |
scheduler (Interconnect Device) | scheduler scheduler-name; | [edit class-of-service scheduler-map-forwarding-class-sets scheduler-map-fcset-name forwarding-class-
set fabric-forwarding-class-set-name] | Map a scheduler to a fabric forwarding class set using a fabric scheduler map. All of the forwarding
classes in the fabric forwarding class set use the mapped scheduler. | [
{
"name": "scheduler-name",
"desc": "Name of the scheduler to map to the fabric forwarding class set."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1R2. | [
"Example: Configuring Queue Schedulers",
"Example: Configuring CoS Scheduling Across the QFabric System",
"Understanding CoS Scheduling Across the QFabric System"
] |
scheduler (Scheduler Map) | scheduler scheduler-name; | [edit class-of-service scheduler-maps map-name] | Associate a scheduler with a scheduler map. | [
{
"name": "scheduler-name",
"desc": "Name of the scheduler configuration block."
}
] | 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 Schedulers"
] |
scheduler (Security Policies) | scheduler scheduler-name {
daily {
(all-day | exclude | start-time hh:mm stop-time hh:mm);
}
description text;
friday {
(all-day | exclude | start-time hh:mm stop-time hh:mm);
}
monday {
(all-day | exclude | start-time hh:mm stop-time hh:mm);
}
saturday {
... | [edit schedulers],
[edit tenants tenant-name schedulers] | Create or modify a scheduler that defines when security policies are in effect.
You configure a scheduler to start at a specific date and time or start on a recurrent basis. | [
{
"name": "scheduler-name",
"desc": "Name of the scheduler. The scheduler name must consist of 1 to 63 characters that can"
}
] | 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 description option added in Junos OS Release 12.1.
The scheduler option added under the set tenants tenant-name schedulers hierarchy in Junos OS Release
18.3R1. | [
"Security Policies Overview"
] |
scheduler (System Security Profile) | scheduler {
maximum maximum;
reserved reserved;
} | [edit system security-profile] | Specify the number of schedulers that user logical system administrators and primary logical system
administrators can configure for their logical systems if the security profile is bound to the logical
systems.
The primary administrator:
•
uses security profiles to provision logical systems with resources.
•
binds sec... | [
{
"name": "maximum",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its reserved amount allows, it can utilize resources configured for the global maximum amount if they are"
},
{
"name": "available",
"desc": "that is, if they are not allocated to other lo... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Understanding Logical Systems for SRX Series Services Gateways"
] |
scheduler | scheduler scheduler-name; | [edit class-of-service scheduler-maps map-name forwarding-class class-name] | Map a scheduler to a forwarding class using a scheduler map.
NOTE: On QFX5200 only, absolute CoS rate limits for transmit rate and shaping rate do
not reflect 50g and 100g interfaces. Therefore this statement does not affect those
interfaces for QFX5200 in release 15.1X53-D30. | [
{
"name": "scheduler-name",
"desc": "Name of the scheduler to map to the forwarding class."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [] |
scheduler-map (CoS Virtual Channels) | scheduler-map map-name; | [edit class-of-service virtual-channel-groups group-name virtual-channel-name] | Apply a scheduler map to this virtual channel. | [
{
"name": "map-name",
"desc": "Name of the scheduler map."
}
] | 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. | [] |
scheduler-map (Dynamic Traffic Shaping) | scheduler-map (map-name); | [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | Associate a scheduler map name with a traffic-control profile in a dynamic profile.
The scheduler map can be defined dynamically (at the [edit dynamic-profiles profile-name class-of-service
scheduler-maps] hierarchy level) or statically (at the [edit class-of-service scheduler-maps] hierarchy level). | [
{
"name": "map-name",
"desc": "Name of the scheduler map or the Junos predefined variable ($junos-cos-scheduler-map). When"
}
] | 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.
The $junos-cos-scheduler-map variable introduced in Junos OS Release 9.4. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Traffic Scheduling and Shaping for Subscriber Access"
] |
scheduler-map (Fabric Queues) | scheduler-map priority (high | low) scheduler scheduler-name; | [edit class-of-service fabric] | Mapping of fabric traffic to packet schedulers. For M320, MX Series, T Series routers, and for EX Series
switches only, associate a scheduler with a fabric priority.
On EX Series switches, this statement is supported only on EX8200 standalone switches and EX8200
Virtual Chassis.
The remaining statements are explained s... | [] | 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. | [
"Associating Schedulers with Fabric Priorities"
] |
scheduler-map (Interfaces and Traffic-Control Profiles) | scheduler-map map-name;
Hierarchy Level (Enhanced Transmission Selection (ETS) Hierarchical Scheduling)
[edit class-of-service traffic-control-profiles traffic-control-profile-name] | [edit class-of-service interfaces interface-name] | Associate a scheduler map with a traffic control profile. | [
{
"name": "map-name",
"desc": "Name of the scheduler map."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [] |
scheduler-map (Interfaces and Traffic-Control Profiles) | scheduler-map map-name; | [edit class-of-service interfaces interface-name],
[edit class-of-service interfaces interface-name unit logical-unit-number],
[edit class-of-service traffic-control-profiles traffic-control-profile-name]
[edit class-of-service multi-destination] | Associate a scheduler map with an interface, a logical interface, a traffic-control profile, or with a
multidestination traffic configuration. . | [
{
"name": "map-name",
"desc": "Name of the scheduler map."
}
] | 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 Schedulers",
"Oversubscribing Interface Bandwidth"
] |
scheduler-map-chassis | scheduler-map-chassis (derived | map-name); | [edit class-of-service interfaces interface-type-fpc/pic/*] | For IQ and IQ2 interfaces, as well as on the 10x10GE MIC with SFP+, assign a custom scheduler to the
packet forwarding component queues that control the aggregated traffic transmitted into the entire PIC.
Default
On Intelligent Queuing (IQ) and Intelligent Queuing 2 (IQ2) interfaces, as well as on the 10x10GE MIC
with... | [
{
"name": "derived",
"desc": "Sets the chassis queues to derive their scheduling configuration from the associated logical"
},
{
"name": "map-name",
"desc": "Name of the scheduler map configured at the [edit class-of-service scheduler-maps] hierarchy"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Applying Scheduler Maps to Chassis-Level Queues"
] |
scheduler-map-forwarding-class-sets | scheduler-map-forwarding-class-sets fabric-scheduler-map-name {
forwarding-class-set fabric-forwarding-class-set-name scheduler scheduler-name;
} | [edit class-of-service] | Specify a fabric scheduler map name to map a scheduler configuration to a fabric forwarding class set.
All of the forwarding classes in the fabric forwarding class set use the mapped scheduler. | [
{
"name": "fabric-scheduler-map-name",
"desc": "Name of the fabric scheduler map."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1R2. | [
"Configuring CoS Fabric Forwarding Class Set Scheduler Maps (Fabric Scheduler to Fabric FC-Set",
"Mapping)",
"Example: Configuring Queue Schedulers",
"Example: Configuring CoS Scheduling Across the QFabric System",
"Understanding CoS Scheduling Across the QFabric System"
] |
scheduler-maps (Definition) | scheduler-maps {
map-name {
forwarding-class class-name scheduler scheduler-name;
}
} | [edit class-of-service] | Create a map of schedulers to forwarding classes (which you associate with queues). You then apply the
scheduler map to an interface, a logical interface, or a traffic-control profile, thus creating an association
of schedulers to queues. | [
{
"name": "map-name",
"desc": "Name of the scheduler map."
}
] | 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. | [] |
scheduler-maps (Dynamic CoS Definition) | scheduler-maps {
map-name {
forwarding-class class-name scheduler scheduler-name;
}
} | [edit dynamic-profiles profile-name class-of-service] | Specify a scheduler map name in a dynamic client profile or a dynamic service profile and associate it
with the scheduler configuration and forwarding class. | [
{
"name": "map-name",
"desc": "Name of the scheduler map."
}
] | 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.
Support at the [edit dynamic-profiles profile-name] hierarchy level introduced in Junos OS Release 9.3. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Schedulers in a Dynamic Profile for Subscriber Access"
] |
scheduler-name | scheduler-name scheduler-name; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name] | Specify the schedule (as defined by the scheduler scheduler-name statement) for which the policy is in
effect. | [
{
"name": "scheduler-name",
"desc": "Name of the scheduler."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Security Policies Overview"
] |
schedulers (CoS) | schedulers {
scheduler-name {
buffer-dynamic-threshold (Schedulers) value;
buffer-size (percent percentage | remainder);
drop-profile-map loss-priority (low | medium-high | high) protocol protocol drop-profile drop-
profile-name;
excess-rate;
explicit-congestion-noti... | [edit class-of-service] | Specify scheduler name and parameter values such as minimum bandwidth (transmit-rate), maximum
bandwidth (shaping-rate), and priority (priority). | [
{
"name": "scheduler-name",
"desc": "Name of the scheduler."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
buffer-dynamic-threshold option introduced in Junos OS Evolved Release 22.3R1. | [] |
schedulers (CoS) | schedulers {
scheduler-name {
adjust-minimum rate;
adjust-percent percentage;
buffer-dynamic-threshold value;
buffer-rate (percent percent | rate);
buffer-size (seconds | percent percentage | remainder | temporal microseconds);
drop-profile-map loss-priority (any | l... | [edit class-of-service] | Specify scheduler name and parameter values such as minimum bandwidth (transmit-rate), maximum
bandwidth (shaping-rate), and priority (priority). | [
{
"name": "scheduler-name",
"desc": "Name of the scheduler to be configured."
}
] | 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.
buffer-dynamic-threshold option introduced in Junos OS Evolved Release 22.3R1. | [
"How Schedulers Define Output Queue Properties",
"Default Schedulers Overview",
"Configuring Schedulers",
"Configuring a Scheduler"
] |
schedulers (Dynamic CoS Definition) | schedulers {
scheduler-name{
adjust-minimum rate;
adjust-percent percentage;
buffer-size (percent percentage | remainder | temporal microseconds | $junos-cos-
scheduler-bs);
drop-profile-map loss-priority (any | low | medium-low | medium-high | high) protocol (any |
non-tcp | tcp) d... | [edit dynamic-profiles profile-name class-of-service] | Specify scheduler name and parameter values in a dynamic client profile or a dynamic service profile. | [
{
"name": "scheduler-name",
"desc": "Name of the scheduler to be configured or the Junos OS predefined variable ($junos-cos-scheduler). The predefined variable is replaced with the scheduler name obtained from the RADIUS server"
}
] | 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.
The $junos-cos-scheduler predefined variable introduced in Junos OS Release 9.4. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Schedulers in a Dynamic Profile for Subscriber Access"
] |
schedulers (Security Policies) | schedulers { ... } | [edit] | Configure schedules for security policies that allow you to control network traffic flow and enforce
network security. | [] | 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 schedulers option added under the tenants hierarchy in
Junos OS Release 18.3R1. | [
"Security Policies Overview"
] |
schema | schema {
openconfig {
unhide;
}
} | [edit system] | Specify whether OpenConfig statements are available and viewable in the CLI. | [
{
"name": "openconfig",
"desc": ""
},
{
"name": "unhide",
"desc": "Unhide the OpenConfig statements in the CLI. By default, the OpenConfig schema is not available through the CLI. To rehide the OpenConfig statements, use the following"
},
{
"name": "command:",
"desc": ""
},
{
... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1. | [
"Installing the OpenConfig Package"
] |
schema-version (Flat-File Accounting Options) | schema-version schema-name; | [edit accounting-options flat-file-profile profile-name] | Specify the name of the XML schema that defines the contents and format of the accounting file, and
appears in the accounting record header. | [
{
"name": "schema-name",
"desc": "Name of the schema."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R4. | [
"Configuring Flat-File Accounting for Layer 2 Wholesale",
"Configuring Flat-File Accounting for Extensible Subscriber Services Management",
"Flat-File Accounting Overview"
] |
scope (Security IDP Chain Attack) | scope (session | transaction); | [edit security idp custom-attack attack-name attack-type chain] | Specify whether the match should occur over a single session or can be made across multiple
transactions within a session. | [
{
"name": "session",
"desc": "Allow multiple matches for the object within the same session."
},
{
"name": "transaction",
"desc": "Match the object across multiple transactions that occur within the same session."
}
] | 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. | [] |
scope (Security IDP Custom Attack) | scope (destination | peer | source); | [edit security idp custom-attack attack-name time-binding] | Specify whether the counting of the attack is from the same source IP address, the same destination IP
address, or a peer. | [
{
"name": "destination",
"desc": "IDP detects attacks to a given destination IP address for the specified number of times,"
},
{
"name": "peer",
"desc": "IDP detects attacks between source and destination IP addresses of the sessions for the"
},
{
"name": "source",
"desc": "IDP detec... | 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. | [] |
scope | scope scope-name {
interface [ interface-names ];
prefix destination-prefix;
} | [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 multicast scoping. | [
{
"name": "scope-name",
"desc": "Name of the multicast scope."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Examples: Configuring Administrative Scoping"
] |
scope-policy | scope-policy [ policy-names ]; | [edit logical-systems logical-system-name routing-options multicast],
[edit routing-options multicast]
NOTE: You can configure a scope policy at these two hierarchy levels only. You cannot
apply a scope policy to a specific routing instance, because all scoping policies are
applied to all routing instances. However, yo... | Apply policies for scoping. The policy must be correctly configured at the edit policy-options policy-
statement hierarchy level. | [
{
"name": "policy-names",
"desc": "Name of one or more multicast scope policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Examples: Configuring Administrative Scoping"
] |
screen (Security Zones) | screen screen-name; | [edit security zones functional-zone management],
[edit security zones security-zone zone-name] | Specify a security screen for a security zone. | [
{
"name": "screen-name",
"desc": "Name of the screen."
}
] | 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. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
screen | screen {
ids-option name {
aggregation {
destination-prefix-mask destination-prefix-mask;
destination-prefix-v6-mask destination-prefix-v6-mask;
source-prefix-mask source-prefix-mask;
source-prefix-v6-mask source-prefix-v6-mask;
}
alarm-without... | [edit security],
[edit tenants tenant-name security] | 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": "ids-options",
"desc": ""
},
{
"name": "screen-name",
"desc": "Name of the screen configured at the security screen ids-options level. Define screens for the intrusion detection service (IDS)."
},
{
"name": "trap",
"desc": "Configure trap interval. Enable or disable the sen... | 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 description option added in Junos OS Release 12.1.
The tenant option is introduced in Junos OS Release 18.3R1. | [
"Attack Detection and Prevention Overview"
] |
scripts | scripts {
commit {
allow-transients;
dampen {
dampen-options {
cpu-factor cpu-factor;
line-interval line-interval;
time-interval time-interval;
}
}
direct-access;
file filename {
allow-transie... | [edit system] | Configure scripting mechanisms for Junos OS commit, op, or SNMP scripts.
NOTE: The traceoptions statement is not supported on QFabric systems. | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Commit Script Overview",
"Op Script Overview",
"SNMP Script Overview",
"Storing and Enabling Scripts"
] |
sctp | sctp {
log (Security SCTP) name;
multichunk-inspection disable;
nullpdu {
protocol (ID-0x0000 | ID-0xFFFF);
}
profile (Security SCTP) name {
association-timeout association-timeout;
drop (Security SCTP) {
m3ua-service name;
payload-protocol name;
... | [edit security] | 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... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. Support for the nat-only option added in Junos OS
Release 12.1X45-D10. Support for the profile statement added in Junos OS Release 12.1X46-D10. | [
"Understanding Stream Control Transmission Protocol",
"SCTP Configuration"
] |
sdsl-bytes | sdsl-bytes bytes; | [edit protocols ancp qos-adjust] | 17.4R1
Starting in Junos OS Release 17.4R1, this statement is deprecated and replaced by the sdsl-overhead-
bytes option of the access-line statement at the [edit system] hierarchy level. | [
{
"name": "bytes",
"desc": "Number of bytes added to or subtracted from the actual downstream frame overhead. Range: -100 through 100 bytes Default: 0 bytes"
}
] | 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 deprecated in Junos OS Release 17.4R1.
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 the ANCP Agent to Report Traffic Rates to CoS",
"Traffic Rate Reporting and Adjustment by the ANCP Agent",
"Configuring the ANCP Agent"
] |
sdsl-overhead-adjust | sdsl-overhead-adjust percentage; | [edit protocols ancp qos-adjust] | 17.4R1
Starting in Junos OS Release 17.4R1, this statement is deprecated and replaced by the sdsl-overhead-
adjust option of the access-line statement at the [edit system] hierarchy level. | [
{
"name": "percentage",
"desc": "Percentage by which to multiply the rate. Range: 80 through 100 percent Default: 100 percent"
}
] | 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 deprecated in Junos OS Release 17.4R1.
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 the ANCP Agent to Report Traffic Rates to CoS",
"Traffic Rate Reporting and Adjustment by the ANCP Agent",
"Configuring the ANCP Agent"
] |
search | search {
admin-search {
distinguished-name distinguished-name;
password password;
}
search-filter filter-name;
} | [edit access ldap-options],
[edit access profile profile-name ldap-options] | Specify that a search is used to get a user's LDAP distinguished name (DN). The search is performed
based on the search filter and the part typed in by the user during authentication. | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [
"Example: Configuring Integrated User Firewall on SRX Series"
] |
search-filter | search-filter filter-name; | [edit access ldap-options search],
[edit access profile profile-name ldap-options search] | Specify that a search filter is used to find the user's LDAP distinguished name (DN). For example, a filter
of cn specifies that the search matches a user whose common name is the username. | [
{
"name": "filter-name",
"desc": "Name of the filter used to find the user's distinguished name."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [
"Example: Configuring Integrated User Firewall on SRX Series"
] |
secondary (Adaptive Services Interfaces) | secondary interface-name; | [edit interfaces (rsp0 | rsp1) redundancy-options] | Specify the secondary (backup) adaptive services interface. | [
{
"name": "interface-name",
"desc": "The identifier for the adaptive services interface, which must be of the form sp-fpc/pic/"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring AS or Multiservices PIC Redundancy"
] |
secondary (Label Switched Path) | secondary path-name {
standby;
} | [edit protocols mpls label-switched-path lsp-name] | Specify one or more secondary paths to use for the label switched path (LSP). You can configure more
than one secondary path. All secondary paths are equal, and the first one that is available is chosen. | [
{
"name": "path-name",
"desc": "Name of a secondary path that you created with the path statement."
}
] | 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 Path Protection in an MPLS Network (CLI Procedure)"
] |
secondary (Link Services IQ PIC Interfaces) | secondary interface-name; | [edit interfaces rlsqnumber redundancy-options] | Specify the secondary (backup) Link Services IQ PIC interface. | [
{
"name": "interface-name",
"desc": "The identifier for the Link Services IQ PIC interface, which must be of the form lsq-fpc/pic/port."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring LSQ Interface Redundancy in a Single Router Using Virtual Interfaces"
] |
secondary (Precision Time Protocol) | secondary interface name; | [edit protocols ptp client interface interface-name],
[edit protocols ptp master interface interface-name] | Configure the secondary member link in an aggregated Ethernet bundle to enable Precision Time
Protocol (PTP) over a link aggregation group. PTP switches over to the secondary member in the
aggregated Ethernet bundle when the primary aggregated Ethernet link is down. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1. | [
"Configuring Precision Time Protocol",
"Example: Configuring Precision Time Protocol",
"Precision Time Protocol Overview"
] |
secondary (Protocols MPLS) | secondary path-name {
adaptive;
admin-group {
exclude [ group-names ];
include-all [ group-names ];
include-any [ group-names ];
}
bandwidth bps;
class-of-service cos-value;
hop-limit number;
no-cspf;
no-decrement-ttl;
optimize-timer seconds;
prefere... | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name] | Specify one or more secondary paths to use for the LSP. You can configure more than one secondary
path. All secondary paths are equal, and the first one that is available is chosen.
You can specify secondary paths even if you have not specified any primary paths.
Optionally, you can specify preference, CoS, and bandwid... | [
{
"name": "path-name",
"desc": "Name of a path that you created with the path statement."
}
] | 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 Primary and Secondary LSPs"
] |
secondary connection (Identity Management Advanced Query) | secondary {
address address;
ca-profile ca-profile;
client-id client-id;
client-secret client-secret;
interface interface-name;
routing-instance routing-instance -name;
source source-address;
} | [edit services user-identification identity-management connection] | Configure parameters that the SRX Series Firewall uses to connect to the Juniper Identity Management
Service (JIMS) secondary server and authenticate to it to obtain an access token. JIMS requires that the
SRX Series Firewall use OAuth2 to authenticate to it before the SRX Series Firewall can query the JIMS
server for ... | [
{
"name": "address",
"desc": "IP address of the secondary server."
},
{
"name": "ca-profile",
"desc": ""
},
{
"name": "CA profile name",
"desc": ""
},
{
"name": "client-id",
"desc": "Client ID for OAuth2 grant"
},
{
"name": "client-secret",
"desc": "Client sec... | 1. services—To view this statement in the configuration.
2. services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D100.
IPv6 address support introduced in Junos OS Release 18.3R1.
Source, interface, and routing-instance options are introduced in Junos OS Release 21.1R1.
Option ca-profile introduced in Junos OS Release 23.2R1. | [
"Understanding Advanced Query Feature for Obtaining User Identity Information from JIMS"
] |
secondary-dns | secondary-dns secondary-dns; | [edit access group-profile profile-name ppp],
[edit access profile profile-name client client-name ppp] | Configure the secondary DNS server. | [
{
"name": "secondary-dns",
"desc": "An IPv4 address."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Point-to-Point Protocol (PPP)"
] |
secondary-interface (Aggregated Inline Services) | secondary-interface interface-name; | [edit interfaces asix aggregated-inline-services-options] | Specify the secondary (backup) inline services member link in the asi bundle. You must also configure a
primary (active) member link on a different MPC with the primary-interface statement. The secondary
member provides 1:1 redundancy for subscriber service sessions on the primary member link. The
bandwidth configured ... | [
{
"name": "interface-name",
"desc": "Name of an inline services physical interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces"
] |
secondary-server | secondary-server {
address ipv4-address;
login sender-email-address {
password password;
}
} | [edit smtp] | Configure Simple Mail Transfer Protocol (SMTP) secondary server for access authorization for SMTP
requests. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement added in Junos OS Release 10.0. | [] |
secondary-vtep-address | secondary-vtep-address anycast IP address; | [edit dynamic-profiles name protocols pim],
[edit logical-systems name protocols pim],
[edit logical-systems name routing-instances name protocols pim],
[edit logical-systems name tenants name routing-instances name protocols pim],
[edit protocols pim],
[edit routing-instances name protocols pim],
[edit tenants name ro... | The secondary Virtual Tunnel End Point (VTEP) address.
The anycast IP address must match the address under set routing-instances instance name vtep-source-
interface inet evpn-mpls-encap vxlan-source-ip address.
In earlier versions of Junos, the anycast IP address was used by PIM as the primary address to build the
VTE... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.2R1. | [
"EVPN-over-VXLAN Supported Functionality"
] |
secondary-wins | secondary-wins secondary-wins; | [edit access group-profile profile-name ppp],
[edit access profile profile-name client client-name ppp] | Configure the secondary Windows Internet name server. | [
{
"name": "secondary-wins",
"desc": "An IPv4 address."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Point-to-Point Protocol (PPP)",
"Layer 2 Tunneling Protocol (L2TP)"
] |
secret (Access Profile) | secret password; | [edit access profile profile-name radius-server server-address] | Specify the RADIUS secret password, which is shared between the router and the RADIUS server. The
device uses this secret to encrypt the user's password that is sent to the RADIUS server. | [
{
"name": "password",
"desc": "RADIUS secret. Maximum length is 256 characters."
}
] | secret—To view this statement in the configuration.
secret-control—To add this statement to the configuration. | Statement modified in Release 8.5 of Junos OS. | [
"Example: Configuring the Device as a Junos OS Enforcer Using IPsec (CLI)"
] |
secret (RADIUS Client) | secret password; | [edit access radius clients client-name accounting] | Specify a shared secret to be used by the MX Series router and the RADIUS client for accounting. | [
{
"name": "password",
"desc": "Shared secret to use ; it can include spaces if the character string is enclosed in quotation marks. Maximum length is 256 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 RADIUS Clients That Send Accounting Requests for IP-Based Subscribers"
] |
secret (RADIUS Server) | secret password; | [edit access radius-server address],
[edit access profile profile-name radius-server address],
[edit access radius-disconnect client-address] | Configure a shared secret to be used by the device and the RADIUS server. | [
{
"name": "password",
"desc": "Shared secret to use. Range: 1 through 64 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 RADIUS Servers",
"Understanding Network Elements",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules",
"External Authentication Servers",
"RADIUS Servers and Parameters for Subscriber Access",
"Example: Configure CHAP Authentication with RADIUS",
"RADIUS Authenti... |
secret (Tunnel Profile) | secret password; | [edit access tunnel-profile profile-name tunnel tunnel-id] | Specify the tunnel password sent to the LNS for authentication. | [
{
"name": "password",
"desc": "Cleartext password."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"L2TP LAC Tunneling for Subscribers"
] |
secret-key-timeout | secret-key-timeout minutes; | [edit logical-systems logical-system-name protocols amt relay],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols amt
relay],
[edit protocols amt relay],
[edit routing-instances routing-instance-name protocols amt relay] | Specify the period in minutes after which the local opaque secret key used in the Automatic Multicast
Tunneling (AMT) Message Authentication Code (MAC) times out and is regenerated.
Default
60 minutes | [
{
"name": "minutes",
"desc": "Number of minutes to wait before generating a new MAC opaque secret key."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring the AMT Protocol"
] |
secure | secure {
security-level {
(default | secure-messages-only);
}
cryptographic-address {
key-length number;
key-pair pathname;
}
timestamp {
clock-drift number;
known-peer-window seconds;
new-peer-window seconds;
}
traceoptions {
file file... | [edit protocols neighbor-discovery] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Secure IPv6 Neighbor Discovery"
] |
secure-access-port | secure-access-port {
dhcp-snooping-file {
location local_pathname | remote_URL;
timeout seconds;
write-interval seconds;
}
dhcpv6-snooping-file {
location local_pathname | remote_URL;
timeout seconds;
write-interval seconds;
}
interface (all | interfac... | [edit ethernet-switching-options] | Configure port security features, including MAC limiting, dynamic ARP inspection, whether interfaces
can receive DHCP responses, DHCP snooping, IP source guard, DHCP option 82, MAC move limiting,
and FIP snooping.
The remaining statements are explained separately. See CLI Explorer. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Support for IPv6 introduced in Junos OS Release 14.1X53-D10 for EX Series switches. | [
"Example: Configuring Port Security (non-ELS)",
"Example: Protecting Against Address Spoofing and Layer 2 DoS Attacks",
"Example: Configuring IP Source Guard on a Data VLAN That Shares an Interface with a Voice VLAN",
"Example: Setting Up DHCP Option 82 Using the Same VLAN",
"Example: Configuring an FCoE Tr... |
secure-channel | secure-channel secure-channel-name {
direction (inbound | outbound);
encryption;
id {
mac-address mac-address;
port-id port-id-number;
}
offset (0|30|50);
security-association security-association-number {
key key-string;
}
} | [edit security macsec connectivity-association connectivity-association-name] | Create and configure a secure channel to enable and configure MACsec when MACsec is enabled using
static secure association key (SAK) security mode.
You do not need to use this option to enable MACsec using static connectivity association key (CAK)
security mode. All configuration for MACsec using static CAK security m... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D15. | [
"Configuring MACsec on EX, QFX and SRX Devices"
] |
secure-nat-mapping (Source NAT Next Gen Services) | secure-nat-mapping {
eif-flow-limit number-of-flows;
mapping-refresh (inbound | inbound-outbound | outbound);
} | [edit services nat source rule-set rule-set rule rule-name then source-nat] | For endpoint-independent mapping, configure the maximum number of simultaneous inbound flows and
the direction in which mappings are refreshed. | [
{
"name": "eif-flow-limit number-of-flows",
"desc": "Maximum number of simultaneous inbound flows. Range: 0 through 655334"
},
{
"name": "mapping-refresh (inbound | inbound-outbound |",
"desc": ""
},
{
"name": "outbound)",
"desc": "Direction in which mappings are refreshed."
}
] | 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. | [] |
secure-nat-mapping | secure-nat-mapping {
mapping-refresh (inbound | outbound | inbound-outbound);
eif-flow-limit number-of-flows’
} | [edit services nat rule rule-name term term-name then translated] | Specify configuration options that help prevent or minimize the effect of attempted denial of service
(DOS) attacks for NAT operations. | [] | 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. | [
"Protecting CGN Devices Against Denial of Service (DOS) Attacks"
] |
secure-neighbor-discovery | secure-neighbor-discovery {
command binary-file-path;
disable;
failover (alternate-media | other-routing-engine);
} | [edit system processes] | Provide support for protecting Secure Neighbor Discovery Protocol (SEND) messages. | [
{
"name": "command binary-file-path",
"desc": "Path to the binary process."
},
{
"name": "disable",
"desc": "Disable the Secure Neighbor Discovery (SEND) protocol process."
},
{
"name": "failover",
"desc": "Configure the device to reboot if the software process fails four times withi... | 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. | [] |
secure-proxy | secure-proxy {
profile name {
drop-on-dns-error;
dynamic-web-application;
dynamic-web-application-group;
proxy-address name {
ip ip-address;
port port-number;
}
}
} | [edit services web-proxy] | Configure secure Web proxy profile.
When you configure secure Web proxy on SRX Series Firewall, it intercepts the session and allows
sessions that are interested in specific application and are destined to a configured external web-proxy.
The device connects sessions directly to the Web server bypassing the external pr... | [
{
"name": "profile name",
"desc": "Name of the secure Web proxy profile."
},
{
"name": "drop-on-dns-error",
"desc": "Drop the Web proxy session on DNS error."
},
{
"name": "dynamic-web-application",
"desc": "Dynamic web application."
},
{
"name": "dynamic-web-application-grou... | flow-tap | Statement introduced in Junos OS Release 19.2R1. | [
"Secure Web Proxy"
] |
secure-wire (System Security Profile) | secure-wire {
maximum maximum;
reserved reserved;
} | [edit system security-profile] | Specify maximum and reserved quota of a user logical system. If the user logical system requires more of
a resource than its reserved amount allows, it can utilize resources configured for the global maximum
amount if the resources are available—that is, if they are not allocated to other user logical systems. | [
{
"name": "maximum",
"desc": "A maximum allowed quota of a user logical system. Range: 0 through 255"
},
{
"name": "reserved",
"desc": "A reserved quota of a user logical system. Default: 0"
}
] | admin | Statement introduced in Junos OS Release 19.3R1. | [
"Secure Wire for Logical Systems"
] |
secured-port-block-allocation | secured-port-block-allocation {
active-block-timeout timeout-seconds;
block-size block-size;
max-blocks-per-address max-blocks;
} | [edit services nat pool pool-name port] | When you use block allocation, one or more blocks of ports in a NAT pool address range are available
for assignment to a subscriber.
Port block allocation is supported on MX series routers with MS-DPCs and on M Series routers with
MS-100, MS-400, and MS-500 MultiServices PICS. Port block allocation is supported on MX s... | [
{
"name": "active-block-timeout",
"desc": "Interval, in seconds, during which a block is active. After the timeout elapses, a new block is allocated, even if ports are available in the active block."
},
{
"name": "timeout-seconds",
"desc": "Range: 0 through 86400. When you specify 0, the active ... | 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. | [
"Configuring Address Pools for Network Address Port Translation (NAPT) Overview"
] |
securid-server | securid-server {
server-name configuration-file filepath;
} | [edit access] | Configure SecurID server for SecurID authentication type. | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 9.1 of Junos OS. | [
"Understanding External Authentication Servers"
] |
security | security {
authentication-key-chains {
key-chain key-chain-name {
key key {
secret secret-data;
start-time yyyy-mm-dd.hh:mm:ss;
}
}
certificates {
cache-size bytes;
cache-timeout-negative seconds;
certification-aut... | [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... | [] | Statement introduced in Junos OS Release 11.1. | [] | |
security-association (IPSec) | security-association sa-name {
manual {
direction bidirectional {
authentication {
algorithm (hmac-md5-96 | hmac-sha1-96 | hmac-sha-256 | hmac-sha-384 | hmac-
sha-512);
key {
ascii-text key;
hexadecimal key;
... | [edit security ipsec] | Configure a manual IPsec security association (SA) to be applied to an OSPF or OSPFv3 interface or
virtual link. IPsec can provide authentication and confidentiality to OSPF or OSPFv3 routing packets. | [
{
"name": "sa-name",
"desc": "Name of the SA."
},
{
"name": "description",
"desc": "Specify a text description for the SA."
},
{
"name": "direction",
"desc": "Direction of the manual SA. For this feature, the direction must be bidirectional. Decrypt and authenticate the incoming and ... | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X46-D20.
Authentication algorithm configuration options, hmac-md5-96, hmac-sha1-96, hmac-sha-256, hmac-
sha-384, and hmac-sha-512 are added in Junos OS Release 22.2R1 for MX240, MX480, and MX960
with MX-SPC3, SRX Series Firewalls and vSRX Virtual Firewall running iked proces... | [
"Understanding OSPF and OSPFv3 Authentication on SRX Series Devices"
] |
security-association (Junos OS) | security-association sa-name {
dynamic {
ipsec-policy policy-name;
replay-window-size (32 | 64);
}
manual {
direction (inbound | outbound | bi-directional) {
authentication {
algorithm (hmac-sha1-96 | hmac-sha2-256);
key (ascii-text key |... | [edit security ipsec] | Configure an IPsec security association. | [
{
"name": "sa-name",
"desc": "Name of the security association."
}
] | 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.
NOTE: You must configure the IPsec keys as hexadecimal keys for maximum key
strength with Junos OS in FIPS mode. | [
"Configuring Security Associations for IPsec on an ES PIC"
] |
security-association (Junos-FIPS Software) | security-association sa-name {
dynamic {
ipsec-policy policy-name;
replay-window-size (32 | 64);
}
manual {
direction (inbound | outbound | bi-directional) {
authentication {
algorithm (hmac-sha1-96 | hmac-sha2-256);
key (ascii-text key |... | [edit security ipsec] | Configure an IPsec security association. | [
{
"name": "sa-name",
"desc": "Name of the security association."
}
] | Crypto Officer—To view and add this statement in the configuration. | Statement introduced before Junos OS Release 7.4.
NOTE: We recommend that you configure the IPsec keys as hexadecimal keys for
maximum key strength with Junos OS in FIPS mode. | [] |
security-association (MACSec) | security-association security-association-number {
key key-string;
} | [edit security macsec connectivity-association connectivity-association-name secure-channel
secure-channel-name] | Specifies the number of one of the security associations in the secure channel when MACsec is enabled
using static secure association key (SAK) security mode. Because SAKs are created by the key server
when MACsec is enabled using static connectivity association key (CAK) security mode, the security-
association statem... | [
{
"name": "security-association-",
"desc": ""
},
{
"name": "number",
"desc": "Specifies the security association number and creates the SAK. The security association number is a whole number between 0 and 3. You can configure two security associations in a secure channel when enabling MACsec usi... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Media Access Control Security (MACsec) on Routers"
] |
security-association | security-association security-association-number {
key key-string;
} | [edit security macsec connectivity-association connectivity-association-name secure-channel secure-
channel-name] | Specifies the number of one of the security associations in the secure channel when MACsec is enabled
using static secure association key (SAK) security mode. Because SAKs are created by the key server
when MACsec is enabled using static connectivity association key (CAK) security mode, the security-
association statem... | [
{
"name": "security-association-",
"desc": ""
},
{
"name": "number",
"desc": "Specifies the security association number and creates the SAK. The security association number is a whole number between 0 and 3. You can configure two security associations in a secure channel when enabling MACsec usi... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D15. | [
"Configuring MACsec on EX, QFX and SRX Devices"
] |
security-intelligence (IDP) | security-intelligence {
add-attacker-ip-to-feed feed-name;
add-target-ip-to-feed feed-name;
} | [edit security idp idp-policy (Security) name rulebase-ips name rule (Security IPS Rulebase) then
(Security IDP Policy) application-services security-intelligence] | Generate security intelligence feeds, you can configure the IDP rule with threat profiles to define the
different types of feeds. You can configure attacker IP feed and target IP feed.
To allow the SRX to generate, leverage, and propagate its own threat-intelligence feeds (custom as well
as infected-hosts) based off of... | [
{
"name": "add-attacker-ip-to-feed",
"desc": "Specify the desired feed-name (attacker-ip-to feed)."
},
{
"name": "add-target-ip-to-feed",
"desc": "Specify the desired feed-name (target-ip-to-feed)"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.2R1. | [] |
security-intelligence (Services) | authentication {
auth-token auth-token;
tls-profile tls-profile;
traceoptions {
no-remote-trace;
file [ filename <files number> <size bytes> <match expression> <world-readable | no-
world-readable>];
flag [all | feed | ipc];
level [all| error | info | notice | verbose | ... | [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": "authentication",
"desc": "Configure authentication, such as an auth token or TLS profile, to commute with the feed server. This operation is performed by the ops script used to enroll your devices and is typically not required afterwards. If you have problems establishing a connection with the Ju... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2 on MX Series routers with Juniper Juniper Advanced
Threat Prevention Cloud (ATP).
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240,
MX480, and MX960. This support runs inline on the MPC card. | [] |
security-intelligence | security-intelligence {
(add-source-ip-to-feed feed-name | add-destination-ip-to-feed feed-name) | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
application-services]
[edit security policies from-zone zone-name to-zone zone-name policy policy-name then deny
application-services ]
[edit security policies from-zone zone-name to-zone zone-name policy policy-name then re... | Starting in Junos OS Release 20.2R1, you can add source and destination addresses to the security
intelligence (SecIntel) profiles to generate security feeds in a security policy by configuring the security-
intelligence command. After the feeds are generated, you can configure other security policies to use the
feeds ... | [
{
"name": "add-destination-ip-to-feed",
"desc": "Add the destination IP address to thesecurity feed."
},
{
"name": "add-source-ip-to-feed",
"desc": "Add the source IP address to the security feed. The feed-name must be predefined and installed by SecIntel with the feed type and a specific ID."
... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.2R1. | [] |
security-intelligence-policy | security-intelligence-policy {
geo-ip
threat-level threat-level {
policy-map policy-name
};
threat-action {
drop;
drop-and-log;
drop-and-sample;
drop-log-and-sample;
log;
log-and-sample;
sample;
}
white-list;
black-list;... | [edit services web-filter profile profile-name]
[edit services web-filter profile profile-name url-filter-template template-name] | Define the threat level and action for the Web filter profile. The packets are redirected at the Packet
Forwarding Engine based on the configured threat-level action associated with the threat-level of the
destination IP address. | [
{
"name": "threat-level",
"desc": "Define the Web filtering threat level. The value ranges from 1 through 10"
},
{
"name": "policy-map",
"desc": "Map the threat level to a user-attribute defined by the url-filterd."
},
{
"name": "threat-action",
"desc": "Define the way the Packet For... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R1 on MX Series routers with Juniper Advanced Threat
Prevention Cloud (Juniper ATP Cloud) .
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240,
MX480, and MX960 with the MX-SPC3 services card | [] |
security-intelligence(services) | security-intelligence {
authentication {
auth-token auth-token;
tls-profile tls-profile;
}
category {
all;
category-name {
Blacklist {
disable;
}
CC {
disable;
}
DNS {
... | [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": "authentication",
"desc": "Configure authentication, such as an auth token or TLS profile, to commute with the feed server. This operation is performed by the ops script used to enroll your devices and is typically not required afterwards. If you have problems establishing a connection with the Ju... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Command introduced in Junos OS 12.1X46. Starting with Junos OS 15.1X49-D110, this command adds
the feed-name option which can be used in security intelligence rules. Prior to Junos OS 15.1X49-D100
you could perform HTTP URL redirect based on threat levels. With feed-name, you can now perform HTTP
URL redirection based... | [
"Configure DNS Sinkhole",
"Configure and Deploy Adaptive Threat Profiling",
"Configure the SRX Series Firewall to Block Outbound Requests to a C&C Host",
"Configure the SRX Series Firewall to Block Infected Hosts",
"Configure Juniper Advanced Threat Prevention Cloud With Geolocation IP",
"Configure Revers... |
security-level (Defining Access Privileges) | security-level (authentication | none | privacy) {
notify-view view-name;
read-view view-name;
write-view view-name;
} | [edit snmp v3 vacm access group group-name (default-context-prefix | context-prefix context-
prefix) security-model (any | usm | v1 | v2c)] | Define the security level used for access privileges.
Default
none | [
{
"name": "authentication",
"desc": "Provide authentication but no encryption."
},
{
"name": "none",
"desc": "No authentication and no encryption."
},
{
"name": "privacy",
"desc": "Provide 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. | [] |
security-level (Generating SNMP Notifications) | security-level (authentication | none | privacy); | [edit snmp v3 target-parameters target-parameters-name parameters] | Configure the security level to use when generating SNMP notifications.
Default
none | [
{
"name": "authentication",
"desc": "Provide authentication but no encryption."
},
{
"name": "none",
"desc": "No authentication and no encryption."
},
{
"name": "privacy",
"desc": "Provide 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. | [] |
security-level | security-level {
(default | secure-messages-only);
} | [edit protocols neighbor-discovery secure] | Configure the type of security mode for Secure Neighbor Discovery. | [
{
"name": "default",
"desc": "Accept and transmit both secure and unsecured messages."
},
{
"name": "secure-messages-only",
"desc": "Accept secure messages only. Discard unsecured messages."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Secure IPv6 Neighbor Discovery"
] |
security-log | security-log {
command binary-file-path;
disable;
failover (alternate-media | other-routing-engine);
} | [edit system processes] | Specify the security log process. | [
{
"name": "command binary-file-path",
"desc": "Path to the binary process."
},
{
"name": "disable",
"desc": "Disable the security log process."
},
{
"name": "failover",
"desc": "Configure the device to reboot if the software process fails four times within 30 seconds,"
},
{
"... | 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. | [] |
security-log-percent-full | security-log-percent-full percentage; | [edit security alarms potential-violation] | Raise a security alarm when security log exceeds a specified percent of total capacity. | [
{
"name": "percentage",
"desc": "Percentage of security log capacity at which a security alarm is raised."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [] |
security-metadata-streaming | security-metadata-streaming {
dns-cache {
custom-list [benign <domin-name> | c2 <domain-name>];
}
policy policy-name {
dns {
cache {
ttl {
benign value;
c2 value;
}
}
de... | [edit services] | Configure security metadata streaming policy on SRX Series Firewalls to send the metadata and
connection patterns of a network traffic to Juniper Networks ATP Cloud for encrypted traffic insights.
After configuring the security metadata streaming policy, attach it to the security policy at zone-level.
set security poli... | [
{
"name": "dns-cache",
"desc": "Configure a list of static benign and command-and-control (C2) domains in the Domain Name System (DNS) cache to take immediate action on configured domains. Only wildcard domains are allowed. The domain format must be *.domain_name.domain_ending . The entries configured in DN... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.2R1 on SRX Series Firewalls with Juniper Advanced
Threat Prevention Cloud (Juniper ATP Cloud). | [
"application-services (security-metadata-streaming)",
"show services security-metadata-streaming"
] |
security-mode (SRX) | security-mode (dynamic | static-cak | static-sak); | [edit security macsec connectivity-association] | Configure the MACsec security mode for the connectivity association.
We recommend enabling MACsec on switch-to-switch Ethernet links using static connectivity
association key (CAK) security mode. Static CAK security mode ensures security by frequently
refreshing to a new random secure association key (SAK) and by only ... | [
{
"name": "security-mode",
"desc": "Specifies the MACsec security mode. Options include:"
},
{
"name": "dynamic",
"desc": "Dynamic mode."
},
{
"name": "static-cak",
"desc": "Static connectivity association key (CAK) mode."
},
{
"name": "static-sak",
"desc": "Static secure... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D60. | [
"Understanding Media Access Control Security (MACsec)",
"Configuring Media Access Control Security (MACsec)"
] |
security-mode | security-mode security-mode; | [edit security macsec connectivity-association connectivity-association-name] | Configure the MACsec security mode for the connectivity association.
To enable MACsec on a switch-to-host link, you must use dynamic connectivity association key (CAK)
mode. For links that connect switches or routers—switch-to-switch, switch-to-router, or router-to-router
—you can use static CAK mode or dynamic CAK mod... | [
{
"name": "security-mode",
"desc": "Specifies the MACsec security mode. Options include:"
},
{
"name": "dynamic",
"desc": "Dynamic CAK mode."
},
{
"name": "static-cak",
"desc": "Static CAK mode."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D15.
The dynamic security mode option was introduced in Junos OS Release 14.1X53-D10. | [
"Configuring MACsec on EX, QFX and SRX Devices"
] |
security-model (Access Privileges) | security-model (usm | v1 | v2c); | [edit snmp v3 vacm access group group-name (default-context-prefix | context-prefix context-
prefix)] | Configure the security model for an SNMPv3 group. The security model is used to determine access
privileges for the group. | [
{
"name": "usm",
"desc": "SNMPv3 security model."
},
{
"name": "v1",
"desc": "SNMPv1 security model."
},
{
"name": "v2c",
"desc": "SNMPv2c security model."
}
] | 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. | [] |
security-model (Group) | security-model (usm | v1 | v2c) {
security-name security-name {
group group-name;
}
} | [edit snmp v3 vacm security-to-group] | Define a security model for a group. | [
{
"name": "usm",
"desc": "SNMPv3 security model."
},
{
"name": "v1",
"desc": "SNMPv1 security model."
},
{
"name": "v2c",
"desc": "SNMPv2c security model."
}
] | 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. | [] |
security-model (SNMP Notifications) | security-model (usm | v1 | v2c); | [edit snmp v3 target-parameters target-parameters-name parameters] | Configure the security model for an SNMPv3 group. The security model is used for SNMP notifications. | [
{
"name": "usm",
"desc": "SNMPv3 security model."
},
{
"name": "v1",
"desc": "SNMPv1 security model."
},
{
"name": "v2c",
"desc": "SNMPv2c security model."
}
] | 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. | [] |
security-name (Community String) | security-name security-name; | [edit snmp v3 snmp-community community-index] | Associate a community string with the security name of a user. The community string, which is used for
SNMPv1 and SNMPv2c clients in an SNMPv3 system, is configured at the [edit snmp v3 snmp-community
community-index] hierarchy level. | [
{
"name": "security-name",
"desc": "Name that is used for messaging security and user access control."
}
] | 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. | [] |
security-name (Security Group) | security-name security-name {
group group-name;
} | [edit snmp v3 vacm security-to-group security-model (usm | v1 | v2c)] | Associate a group or a community string with a configured security group. | [
{
"name": "security-name",
"desc": "Username configured at the [edit snmp v3 usm local-engine user username] hierarchy level. For"
}
] | 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. | [] |
security-name (SNMP Notifications) | security-name security-name; | [edit snmp v3 target-parameters target-parameters-name parameters] | Configure the security name used when generating SNMP notifications. | [
{
"name": "security-name",
"desc": "If the SNMPv3 USM security model is used, identify the user when generating the SNMP"
}
] | 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. | [] |
security-option (IDS Screen Next Gen Services) | security-option; | [edit services screen ids-option screen-name ip] | Identify and drop IPv4 packets that have the IP option of 2 (Security). | [] | 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"
] |
security-package | security-package {
automatic (Security) {
enable;
interval hours;
start-time start-time;
}
install {
ignore-version-check;
ignore-appid-failure;
}
proxy-profile proxy-profile;
source-address address;
url url-name;
} | [edit security idp] | Configure the device to automatically download the updated signature database from the specified URL.
When you configure signature installation to enable the ignore-appid-failure option, IDP signature
download/installation does not fail even if application identification download/installation fails during
IDP signature... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration.
NOTE: The option download-timeout is a hidden option in CLI help and not intended for
general use. It is retained for backward compatibility. A warning message is displayed if
you use this option. | Statement introduced in Junos OS Release 9.2.
Option ignore-appid-failure is introduced in Junos OS Release 18.3R1.
Option proxy-profile is introduced in Junos OS Release 18.3R1. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.