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 |
|---|---|---|---|---|---|---|---|
service-interface (Services Interfaces) | service-interface interface-name; | [edit services service-set service-set-name interface-service] | Specify the name for the services interface associated with an interface-wide service set. | [
{
"name": "interface-name",
"desc": "Identifier of the service interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Configuring Service Sets to be Applied to Services Interfaces",
"Applying Services to Subscriber-Aware Traffic with a Service Set"
] |
service-interface-pools | service-interface-pools {
pool pool-name {
interface interface-name.unit-number;
}
} | [edit services] | Configure service interface pools used for VPN aggregation. | [] | 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 Service Interface Pools"
] |
service-mode (mobile-edge SAEGW) | service-mode {
maintenance
}
} | [edit services mobile-edge gateways saegw gateway-name system] | Enter maintenance mode for SAEGW gateways. This makes your gateway inactive for new sessions, but
traffic flow and existing sessions will continue uninterrupted. Critical session modify and session delete
messages are also allowed in maintenance mode.
When you enter maintenance mode, a duration is set for the maintenan... | [] | system | Juniper Networks released this statement in Junos OS Release 23.1R1. | [] |
service-mode | service-mode service-mode-options; | [edit routing-instances vrf-name access address-assignment address-pools juniper-pool],
[edit unified-edge gateways tdf gateway-name],
[edit unified-edge gateways tdf gateway-name domains domain-name],
[edit unified-edge tdf gateway-name system interface interface-name],
[edit unified-edge gateways tdf gateway-name sys... | Set maintenance mode for a network element so that you can carry out maintenance tasks such as
deleting or modifying the element, for example, an address pool.
When in the maintenance mode active phase, you can modify all the valid attributes on the network
element. In other cases, you can modify only the non-maintenan... | [
{
"name": "service-mode-options",
"desc": "Type of the service mode. Currently, only maintenance mode is supported."
}
] | 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 16.1. | [
"Maintenance Mode Overview for Subscriber Aware Policy Enforcement"
] |
service-name | service-name name; | [edit interfaces pp0 unit logical-unit-number pppoe-options],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number pppoe-options] | PPP over Ethernet interfaces, configure the service to be requested from the PPP over Ethernet server;
that is, the access concentrator. For example, you can use this statement to indicate an Internet service
provider (ISP) name or a class of service. | [
{
"name": "name",
"desc": "Service to be requested from the PPP over Ethernet server."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the PPPoE Service Name"
] |
service-name-table | service-name-table table-name; | [edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family pppoe],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
pppoe],
[edit interfaces interface-name unit logical-unit-number family pppoe],
[edit interfaces interface-name unit logical-unit-n... | Specify the PPPoE service name table assigned to a PPPoE underlying interface. This underlying
interface is configured with either the encapsulation ppp-over-ether statement or the family pppoe statement;
the two statements are mutually exclusive.
NOTE: The [edit ... family pppoe] hierarchies are supported only on MX S... | [
{
"name": "table-name",
"desc": "Name of the PPPoE service name table, a string of up to 32 alphanumeric characters."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
Support at the [edit ... family pppoe] hierarchies introduced in Junos OS Release 11.2. | [
"Configuring PPPoE Service Name Tables",
"Assigning a Service Name Table to a PPPoE Underlying Interface",
"Configuring the PPPoE Family for an Underlying Interface"
] |
service-name-tables | service-name-tables table-name {
service service-name {
drop;
delay seconds;
terminate;
dynamic-profile profile-name;
routing-instance routing-instance-name;
max-sessions number;
agent-specifier {
aci circuit-id-string ari remote-id-string {
... | [edit protocols pppoe] | Create and configure a PPPoE service name table. Specify the action taken for each service and remote
access concentrator on receipt of a PPPoE Active Discovery Initiation (PADI) packet. You can also
specify the dynamic profile and routing instance that the router uses to instantiate a dynamic PPPoE
interface, and the ... | [
{
"name": "table-name",
"desc": "Name of the PPPoE service name table, a string of up to 32 alphanumeric characters."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
dynamic-profile, routing-instance, max-sessions, and static-interface options introduced in Junos OS Release
10.2. | [
"Configuring PPPoE Service Name Tables",
"Creating a Service Name Table"
] |
service-offload (CSDS) | service-offload {
flow-table-size flow-table-size;
} | [edit chassis fpc] | Enables the Express Path functionality on the specified FPC slot on the router in the Connected Security
Distributed Services (CSDS) Architecture.
When you configure the option, the device disables the mobility edge functionality. After configuring
the option, you must reboot the FPC using the command request chassis f... | [
{
"name": "flow-table-size",
"desc": "(Optional) Size of service-offload flow table size in units per ASIC, where 1 unit = 256 K flow entries. Default: 48 Range: 1 through 48 Reboot the FPC if you change the default value."
}
] | interface—To view this statement in the configuration
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [
"CSDS Overview"
] |
service-offloading (CSDS) | service-offloading {
service-offloading-rule name {
ip-reassembly partial;
tlb-vrf name;
}
} | [edit services] | Configure service offload rules on the router for Express Path in the Connected Security Distributed
Services (CSDS) Architecture. When you configure the statement, the firewall offloads the flow to the
router in the CSDS solution. | [
{
"name": "service-offloading-rule name",
"desc": "Specify service offload rule name."
},
{
"name": "ip-reassembly partial",
"desc": "Specify partial ip-reassembly."
},
{
"name": "tlb-vrf name",
"desc": "Specify the service-offload VRF name."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [
"Express Path in CSDS Architecture"
] |
service-order | service-order {
forward-flow [ service-name1 service-name2 ];
reverse-flow [ service-name1 service-name2 ];
} | [edit services service-set service-set-name] | Define the order of services in service set to be applied to traffic coming to the PIC.
NOTE: If the extension-service statement is specified, the service-order statement is
mandatory. | [
{
"name": "forward-flow",
"desc": "Order of services in service set to be applied in forward flow."
},
{
"name": "reverse-flow",
"desc": "Order of services in service set to be applied in reverse flow. If you want the order to be the"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"extension-service"
] |
service-package | service-package {
extension-provider {
control-cores control-number;
data-cores data-number;
data-flow-affinity {
hash-key (layer-3 | layer-4);
}
forwarding-db-size size;
object-cache-size size;
package package-name;
policy-db-size size;
... | [edit chassis fpc slot-number pic pic-number adaptive-services] | For adaptive services and multi-services interfaces, enable a service package on the specified Physical
Interface Card (PIC).
NOTE: By default, the MS-MPC and MS-MIC cards come up with extension-provider as
service-package, irrespective of the configuration. These cards do not support any other
service-package configur... | [
{
"name": "layer-2",
"desc": "Enable a Layer 2 service package on the specified PIC."
},
{
"name": "layer-3",
"desc": "Enable a Layer 3 service package on the specified 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.
Statement introduced on MX Series 5G Universal Routing Platforms with MS-DPCs in Junos OS Release
9.6. | [
"Enabling Service Packages",
"Configuring MS-MPC-Based or MX-SPC3-Based Static HTTP Redirect Services",
"Configuring MS-MPC-Based or MX-SPC3-Based Converged HTTP Redirect Services"
] |
service-pics | service-pics {
[interface interface-name];
} | [edit unified-edge gateways tdf gateway-name system] | Specify the service interfaces that represent the service PICs used for anchoring subscriber-aware
services in the TDF Gateway.
The remaining statement is explained separately. See CLI Explorer. | [] | 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 Service PICs",
"TDF Gateway Service PICs and Session PICs for Subscriber-Aware Traffic Treatment"
] |
service-port (Inline Services) | service-port port-number | [edit chassis fpc slot-number pic number inline-services] | For MX Series 5G Universal Routing Platforms, configure the port number of the inline service interface.
The range is 0 through 3. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.1R1. | [] |
service-port (UDP, Dynamic Flow Capture) | service-port port-number; | [edit services dynamic-flow-capture capture-group client-name control-source identifier] | Identify the User Datagram Protocol (UDP) port number for control protocol requests. | [
{
"name": "port-number",
"desc": "Port number for control protocol request messages."
}
] | 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. | [
"Configuring the Control Source"
] |
service-profile (DHCP Local Server) | service-profile dynamic-profile-name; | [edit system services dhcp-local-server],
[edit system services dhcp-local-server dual-stack-group dual-stack-group-name],
[edit system services dhcp-local-server dhcpv6],
[edit system services dhcp-local-server dhcpv6 group group-name],
[edit system services dhcp-local-server dhcpv6 group group-name interface interfac... | Specify the default subscriber service or DHCP client management service, which is activated when the
subscriber or client logs in and no other service is activated by a RADIUS server or a provisioning server.
•
To specify the default service for all DHCP local server clients, include the service-profile statement at
t... | [
{
"name": "dynamic-profile-name",
"desc": "Name of the dynamic profile that defines the service."
}
] | 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 Differences Between Legacy DHCP and Extended DHCP",
"Default Subscriber Service Overview",
"Configuring a Default Subscriber Service"
] |
service-profile (DHCP Relay Agent) | service-profile dynamic-profile-name; | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name],
[edit forwarding-options dhcp-relay group group-name],
[edit forwarding-options dhcp-relay group group-name interface interface-name],
[edit forwarding-options ... | Specify the default subscriber service (or the default DHCP client management service), which is
activated when the subscriber (or client) logs in and no other service is activated by a RADIUS server or
a provisioning server.
•
To specify the default service for all DHCP relay agent clients, include the service-profile... | [
{
"name": "dynamic-profile-name",
"desc": "Name of the dynamic service profile."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2.
Support at the [edit ... dhcpv6 ...] hierarchy levels introduced in Junos OS Release 11.4.
Support at the [edit ... dual-stack-group dual-stack-group-name] hierarchy level introduced in Junos OS
Release 15.1. | [
"Attaching Dynamic Profiles to DHCP Subscriber Interfaces or DHCP Client Interfaces",
"Grouping Interfaces with Common DHCP Configurations",
"Default Subscriber Service Overview"
] |
service-profile (L2TP) | service-profile profile-name(parameter)&profile-name; | [edit access profile profile-name client client-name l2tp]
[edit services l2tp tunnel-group group-name] | Configure one or more dynamic service profiles to be applied to subscriber sessions at activation for all
subscribers in the specified tunnel group or on the specified LAC. Services are typically applied to L2TP
sessions with RADIUS VSAs or CoA requests. In multivendor environments, you might use only standard
attribut... | [
{
"name": "profile-name",
"desc": "Name of a dynamic service profile that defines a service to be applied to L2TP subscriber sessions. You can specify one or more service profiles, separated by an ampersand (&)."
},
{
"name": "parameter",
"desc": "(Optional) Value to be passed to the service whe... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1 on MX Series routers. | [
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces"
] |
service-profile (Static Subscribers) | service-profile service-profile-name; | [edit system services static-subscribers],
[edit system services static-subscribers group group-name] | Specify the service profile to apply services for all static subscribers at the global level and at the group
level. You can use service-profile to assign a default service profile to be applied to a static-subscriber
session if the policy server is unavailable. | [
{
"name": "service-profile-name",
"desc": "Name of the service profile."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1. | [
"JSRC and Subscribers on Static Interfaces",
"JSRC and Subscribers on Static Interfaces",
"JSRC and Subscribers on Static Interfaces"
] |
service-provider (SAML) | service-provider service-provider {
assertion-waittime assertion-waittime;
encrypted-assertions;
entity-id entity-id;
hash-algorithm <sha-256 | sha-384 | sha-512>;
sign-auth-request;
sp-certificate sp-certificate;
} | [edit access saml] | Describe Security Assertion Markup Language (SAML) service provider configuration details. | [
{
"name": "assertion-waittime assertion-waittime",
"desc": "Set the maximum waiting time for an assertion from the Identity Provider (IdP). Value: Within a range of 1 to 600 seconds Default: 30 seconds"
},
{
"name": "encrypted-assertions",
"desc": "Specify that the IdP must provide encrypted a... | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.4R1. | [] |
service-set (Application-Aware Control Policy) | service-set service-set-name {
application-identification–profile app-id-profile-name;
interface-service {
service-interface interface-name;
}
hcm-profile profile-name;
lrf-profile profile-name;
pcef-profile pcef-profile-name;
service-set-options {
subscriber-awareness;
... | [edit services] | Configure a service set to identify the service interface that handles application-aware policy control. | [
{
"name": "application-identification–profile",
"desc": ""
},
{
"name": "app-id-profile-name",
"desc": "Specify a dummy application identification profile that you configured at the [edit services application-identification profile] hierarchy level. This profile is a placeholder profile with no ... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement options for application-aware policy control introduced in Junos OS Release 17.2R1 on MX
Series for Broadband Subscriber Management.
USF support for statement options for application-aware policy control introduced in Junos OS Release
19.3R2 on MX Series for Broadband Subscriber Management.
static-subscriber... | [
"Identifying the Service Interface That Handles Subscriber Management Application-Aware Policy",
"Control",
"Configuring Logging and Reporting for Subscriber Management"
] |
service-set (Dynamic Service Sets) | service-set service-set-name {
service-filter filter-name;
} | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family service input],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family service output],
[edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit famil... | Define one or more service sets in a dynamic profile. Service sets are applied to an interface. If you
define multiple service sets, the router software evaluates the filters in the order in which they appear in
the configuration. You can use the predefined dynamic interface variables $junos-input-service-set, $junos-
... | [
{
"name": "service-set-name",
"desc": "Name of 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 9.5.
Support at the [edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit” family family
service input] and [edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit” family family
service output] hierarchy levels introduced in Junos... | [
"Dynamic Service Sets Overview",
"Associating Service Sets with Interfaces in a Dynamic Profile"
] |
service-set (Interfaces) | service-set service-set-name; | [edit interfaces interface-name unit logical-unit-number family inet service (input | output)],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet service (input | output)] | Define one or more service sets to be applied to an interface. If you define multiple service sets, the
router software evaluates the filters in the order in which they appear in the configuration. | [
{
"name": "service-set-name",
"desc": "Name of the service set."
}
] | 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.
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. | [
"Guidelines for Configuring Service Filters"
] |
service-set (Services) | service-set service-set-name {
allow-multicast;
captive-portal-content-delivery-profile;
cos-options {
match-rules-on-reverse-flow;
}
cos-rules [cos-rule-name];
cos-rule-sets;
extension-service service-name {
provider-specific-rules-configuration;
}
flow;
hcm-prof... | [edit services] | Define the service set.
NOTE: Use the web-filter-profile option starting in Junos OS Release 18.3R1 and use the
url-filter-profile option in Junos OS Releases before 18.3R1. | [
{
"name": "service-set-name",
"desc": "Name of the service set. You can include special characters, such as a forward slash (/),"
}
] | 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.
pgcp-rules and pgcp-rule-sets options added in Junos OS Release 8.4.
server-set-options option added in Junos OS Release 10.1.
ptsp-rules and ptsp-rule-sets options added in Junos OS Release 10.2.
softwire-rules and clear-rule-sets options added in Junos OS Release 10.4... | [
"Understanding Service Sets"
] |
service-set (Subscriber-Aware) | service-set service-set-name {
service-set-options {
subscriber-awareness;
static-subscriber-application;
}
hcm profile hcm-profile-name;
lrf-profile profile-name;
pcef-profile pcef-profile-name;
application-identification-profile app-id-profile-name;
nat-rules rule-name;
... | [edit services] | Configure subscriber-aware services by creating a subscriber-aware service set to be applied to a TDF
interface. | [
{
"name": "service-set-name",
"desc": "Name of the service set. The remaining statements are explained separately."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
static-subscriber-application option added in Junos OS Release 21.2R1. | [
"Applying Services to Subscriber-Aware Traffic with a Service Set",
"Configuring Logging and Reporting for Junos OS Subscriber Aware"
] |
service-set (TDF Interface) | service-set service-set-name; | [edit interfaces mif unit number family inet service input],
[edit interfaces mif unit number family inet service output] | Apply the service set to the service input and output of the TDF interface (mif) that is part of a TDF
domain.
The output service set for the mif is not used by the MX Series router, but it must be configured so that
the configuration commit does not fail. | [
{
"name": "service-set-name",
"desc": "Name of the service set that is being applied to the TDF interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Applying Services to Subscriber-Aware Traffic with a Service Set"
] |
service-set-options (Next Gen Services Services) | service-set-options {
bypass-traffic-on-exceeding-flow-limits;
disable-global-timeout-override;
disable-session-open-syslog ;
enable-asymmetric-traffic-processing;
inactivity-non-tcp-timeout ;
max-sessions-per-subscriber
session-limit;
session-timeout;
tcp-session {
inactivi... | [edit services service-set service-set-name] | Specify the service set options to apply to a service set.
disable-session-open-syslog
Disable session open information from being collected in system logs.
inactivity-non-tcp-timeout
Specify the inactivity timeout period for non-TCP established sessions.
The remaining statements are explained separately. See CLI Explo... | [] | 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 Service Sets to be Applied to Services Interfaces",
"Configuring APPID Support for Unidirectional Traffic"
] |
service-set-options | service-set-options {
bypass-traffic-on-exceeding-flow-limits;
bypass-traffic-on-pic-failure;
enable-asymmetric-traffic-processing;
enable-descriptive-session-syslog;
header-integrity-check;
routing-engine-services;
static-subscriber-application;
subscriber-awareness;
support-uni-... | [edit services service-set service-set-name] | Specify the service set options to apply to a service set.
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 10.1.
enable-asymmetric-traffic-processing and support-uni-directional-traffic options added in Junos OS Release
11.2.
routing-engine-services option added in Junos OS Release 15.1.
enable-change-on-ams-redistribution option added in Junos OS Release 15.1.
subscriber-awareness o... | [
"Configuring Service Sets to be Applied to Services Interfaces",
"Configuring APPID Support for Unidirectional Traffic"
] |
service-tracking (Network Isolation Groups) | service-tracking {
core-isolation;
} | [edit protocols network-isolation group name detection] | Enable service tracking in a network isolation group to detect core isolation condition changes.
When you set this option, you must also do the following:
•
In the same network isolation group definition, configure the actions the device should take upon
detecting a core isolation condition.
To do this, configure the s... | [
{
"name": "core-isolation",
"desc": "Enable service tracking for EVPN core isolation conditions."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 23.2R1. | [
"Layer 2 Interface Status Tracking and Shutdown Actions for EVPN Core Isolation Conditions"
] |
service-tracking-action (Network Isolation Groups) | service-tracking-action (lacp-out-of-sync | link-down); | [edit protocols network-isolation group name] | Set the action the device takes for the interface or interfaces associated with a configured network
isolation group profile, when the device detects a network isolation condition change.
A network isolation group encompasses the parameters that the device uses to:
•
Detect when an EVPN instance. a bridge domain, or a ... | [
{
"name": "lacp-out-of-sync",
"desc": "Set LACP out of sync state for the associated ESI LAG interfaces."
},
{
"name": "link-down",
"desc": "Bring down the interface or interfaces."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 23.2R1. | [
"Layer 2 Interface Status Tracking and Shutdown Actions for EVPN Core Isolation Conditions"
] |
service-type (MAC-VRF Routing Instances) | service-type (vlan-aware | vlan-based | vlan-bundle); | [edit logical-systems name routing-instances mac-vrf routing-instance name],
[edit logical-systems name tenants name routing-instances mac-vrf routing-instance name],
[edit routing-instances mac-vrf routing-instance name],
[edit tenants name routing-instances mac-vrf routing-instance name] | Select the type of VLAN service that the MAC-VRF routing instance provides. The selected option
controls how the routing instance maps VLANs to the forwarding instances on the device. | [
{
"name": "vlan-aware",
"desc": "Map one or more routing instances of type Virtual Switch to many VLAN IDs (VIDs) and multiple bridge tables. Each bridge table corresponds to a different VLAN."
},
{
"name": "vlan-based",
"desc": "Map one routing instance of type EVPN to one VLAN. Only one bridge... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [
"MAC-VRF Routing Instance Type Overview"
] |
service-type (RFC 2544 Benchmarking Tests) | service-type (elan | eline) ; | [edit services rpm rfc2544-benchmarkingtests test-name test-name] | Configure the service under test. Possible values are elan and eline. This statement is applicable only for
the bridge family, the ethernet-switching family, or when the mode is configured as reflect. When the service
type is elan, MAC addresses are swapped by default on the reflected frames. The no-mac-swap option is ... | [
{
"name": "elan",
"desc": "Specify the ELAN service type."
},
{
"name": "eline",
"desc": "Specify the E-Line service type."
}
] | 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 22.4R1. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring an RFC 2544-Based Benchmarking Test",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers"
] |
service-type | service-type (elan | eline); | [edit routing-instances routing-instance-name service-groups] | For IEEE 802.1ah provider backbone bridge (PBB) configurations, configure the service type for the
service group in the customer routing instance (I-component). | [
{
"name": "elan",
"desc": "Connects a set of customer endpoints (like a bridged Ethernet network). E-LAN service is also"
},
{
"name": "eline",
"desc": "Connects two customer Ethernet ports over a WAN. E-LINE service is also known as point-to-point service."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in JUNOS Release 10.0. | [] |
services (Captive Portal Content Delivery) | services {
...
captive-portal-content-delivery {
auto-deactivate value;
profile name
cpcd-rule-sets rule-set-name;
cpcd-rules rule-name;
dynamic;
http-redirect-options url;
ipda-rewrite-options {
destination-address dest... | [edit],
[edit dynamic-profiles profile-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": "auto-deactivate",
"desc": ""
},
{
"name": "value",
"desc": "(Optional) Specify one of the following values to determine whether the redirect service is removed automatically when the router receives the subscriber’s initial HTTP-GET"
},
{
"name": "message:",
"desc": ""
}... | services—To view this statement in the configuration.
services–control—To add this statement to the configuration.
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
Support at the [edit dynamic-profiles profile-name services] hierarchy level added in Junos OS Release
17.2R1.
Statement introduced in Junos OS Release 10.4.
Support at the [edit dynamic-profiles profile-name services] hierarchy level added in Junos OS Release
17.2R1.
Supp... | [
"HTTP Redirect Service Overview",
"Configuring MS-MPC-Based or MX-SPC3-Based Static HTTP Redirect Services",
"Configuring MS-MPC-Based or MX-SPC3-Based Converged HTTP Redirect Services",
"Configuring Routing Engine-Based, Static HTTP Redirect Services",
"Configuring Routing Engine-Based, Converged HTTP Redi... |
services (Hierarchy) | services { ... } | [edit] | Define the service rules to be applied to traffic.
The remaining statements are explained separately. See "[edit services]" on page 1174 | [] | 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. | [
"Understanding Service Sets"
] |
services (IDS) | services ids { ... } | [edit] | Define the service rules to be applied to traffic. | [
{
"name": "ids",
"desc": "Identifies the IDS set of rules statements."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IDS Rules on an MS-DPC"
] |
services (Interfaces) | services severity-level; | [edit interfaces interface-name services-options syslog host hostname] | Specify the system logging severity level.
Starting with Junos OS release 17.4R1, you can configure up to a maximum of four system log servers
(combination of local system log hosts and remote system log collectors) for each service set for ms
interface under [edit interfaces interface-name services-options] hierarchy. | [
{
"name": "severity-level",
"desc": "Assigns a severity level to the facility. Valid entries include:"
},
{
"name": "alert",
"desc": "Conditions that should be corrected immediately."
},
{
"name": "any",
"desc": "Matches any level."
},
{
"name": "critical",
"desc": "Criti... | 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.
You can configure multiple system log hosts from Junos OS Release 17.4R1 onwards. | [
"Configuring System Logging for Services Interfaces"
] |
services (IPsec VPN) | services ipsec-vpn { ... } | [edit] | Define the service rules to be applied to traffic. | [
{
"name": "ipsec-vpn",
"desc": "Identifies the IPsec set of rules statements."
}
] | 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. | [] |
services (L2TP System Logging) | services severity-level; | [edit services l2tp tunnel-group group-name syslog host hostname] | Specify the system logging severity level. | [
{
"name": "severity-level",
"desc": "Assigns a severity level to the facility. Valid entries include:"
},
{
"name": "alert",
"desc": "Conditions that should be corrected immediately."
},
{
"name": "any",
"desc": "Matches any level."
},
{
"name": "critical",
"desc": "Criti... | 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 L2TP Tunnel Groups"
] |
services (L2TP) | services l2tp { ... } | [edit] | Define the service properties to be applied to traffic. | [
{
"name": "l2tp",
"desc": "Identifies the L2TP set of services statements."
}
] | 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. | [
"L2TP Services Configuration Overview"
] |
services (NAT) | services nat { ... } | [edit] | Define the service rules to be applied to traffic. | [
{
"name": "nat",
"desc": "Identifies the NAT set of rules statements."
}
] | 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. | [] |
services (Stateful Firewall) | services stateful-firewall { ... } | [edit] | Define the service rules to be applied to traffic. | [
{
"name": "stateful-firewall",
"desc": "Identifies the stateful firewall set of rules statements."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Junos Network Secure Overview"
] |
services (System Logging) | services severity-level; | [edit services service-set service-set-name syslog host hostname] | Specify the severity level for system logging messages.
Starting in Junos OS Release 17.4R1, you can configure up to a maximum of four system log servers
(combination of local system log hosts and remote system log collectors) for each service set under [edit
services service-set service-set-name] hierarchy level. | [
{
"name": "severity-level",
"desc": "Assigns a severity level to the facility. Valid entries are:"
},
{
"name": "alert",
"desc": "Conditions that should be corrected immediately."
},
{
"name": "any",
"desc": "Matches any level."
},
{
"name": "critical",
"desc": "Critical ... | 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.
You can configure multiple system log hosts from Junos OS Release 17.4R1 onwards. | [
"Configuring System Logging for Service Sets"
] |
services (system services) | services {
bbe-stats-service {...}
database-replication {...}
dhcp {...}
dhcp-local-server {...}
dns {...}
dtcp-only;
dynamic-dns {...}
extensible-subscriber-services {...}
extension-service {...}
finger {...}
flow-tap-dtcp {...}
ftp {...}
grpc-tunnel {...}
http {... | [edit system] | Configure the router or switch so that users on remote systems can access the local router or switch
through the DHCP server, DTCP over SSH, finger, outbound HTTPS, rlogin, SSH, telnet, Web
management, Junos XML protocol SSL, and network utilities. Also, enable configuration of third-party
applications developed using ... | [
{
"name": "bbe-stats-service",
"desc": "Change the default values of BBE subscriber accounting statistics. The accounting statistics are polled or pushed from the PFE to RE depending on the FPC type, to send"
},
{
"name": "to RADIUS server",
"desc": ""
},
{
"name": "dtcp-only",
"desc... | 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.
extension-service option added in Junos OS Release 16.1 for MX80, MX104, MX240, MX480, MX960,
MX2010, MX2020, vMX Series.
grpc option added in Junos OS Release 16.2 for MX80, MX104, MX240, MX480, MX960, MX2010,
MX2020, vMX Series.
allow-tcp-forwarding option added in J... | [] |
services-memory (resource-manager) | services-memory {
match {
threshold threshold;
}
then {
alarm;
drop-flows;
fail-close;
fail-open;
log;
}
} | [edit security resource-manager] | Configure resource manager services-memory options to control the behavior of the device based on
memory load. | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [
"Traffic Processing on SRX Series Devices Overview"
] |
services-offload (Security) | services-offload; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit] | Enable services offloading within a security policy for SRX4600, SRX5400, SRX5600, and SRX5800
devices. | [] | 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. | [
"Security Policies Overview",
"Understanding Security Policy Elements"
] |
services-offload | services-offload {
low-latency;
per-session-statistics;
} | [edit chassis fpc fpc-slot-number pic pic-slot-number] | Enables the Express Path mode (formerly known as services offloading) mode on the selected network
processor. Services-offload is not enabled by default.
When services-offload is enabled, only the first packets of a session goes to the Services Processing Unit
(SPU), rest of packets in services-offload mode does not go... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Understanding Traffic Processing on Security Devices"
] |
services-options (Next Gen Services Interfaces) | services-options {
enable-subscriber-analysis
fragment-limit;
jflow-log {
message-rate-limit messages-per-second;
}
session-limit {
maximum number;
rate new-sessions-per-second;
cpu-load-threshold percentage;
}
flow
traceoptions {
f... | [edit interfaces interfaces-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": "file",
"desc": "Configure the trace file options."
},
{
"name": "filename",
"desc": "Name of the file to receive the output of the tracing operation. Enclose the name within quotation marks. All files are placed in the directory /var/log. By default, the name of the file is the name o... | 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.
Support introduced in Junos OS Release 20.3R1 for Next Gen Services on MX240, MX480 and MX960
routers for the flow configuration statement. | [] |
services-options | services-options {
cgn-pic;
close-timeout seconds;
fragment-limit number-of-fragments;
disable-global-timeout-override;
ignore-errors <alg> <tcp>;
inactivity-non-tcp-timeout seconds;
inactivity-tcp-timeout seconds;
inactivity-timeout seconds;
open-timeout seconds;
pba-interim-log... | [edit interfaces interface-name] | Define the service options to be applied on an interface.
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 before Junos OS Release 7.4. | [
"Configuring Default Timeout Settings for Services Interfaces",
"Configuring System Logging for Services Interfaces"
] |
services-redundancy-group | services-redundancy-group name {
activeness-priority activeness-priority;
activeness-probe {
bfd-liveliness {
destination-ip;
interface;
minimum-interval;
multiplier;
routing-instance
source-ip;
}
dest-ip {
ip-address;
routing-instance routing-instance;
src-ip src-ip;
... | [edit chassis high-availability] | Configure a service redundacy group (SRG). An SRG includes and manages a collection of resources on
both nodes of a Multinode High Availability and it fails over between the two devices. You can configure
upto 20 SRGs in a Multinode Highavailability setup. | [
{
"name": "name",
"desc": "Services redundancy group identifier. Range: 0 through 20"
},
{
"name": "active-signal-route",
"desc": "IP address used for route preference advertisement. You must specify the active signal route along with the route-exists policy in the policy-options statement. Sig... | interface | Statement introduced in Junos OS Release 20.4R1.
Multi SRG1s (SRG1+) support is added in Junos OS Release 22.4R1.
install-on-failure-route option is added in Junos OS Release 22.4R2. | [
"Example: Configure Multinode High Availability in a Layer 3 Network",
"Example: Configure Multinode High Availability in a Default Gateway Deployment",
"Example: Configure Multinode High Availability in a Default Gateway Deployment"
] |
session (Origin Validation for BGP) | session server-ip-address {
database <database-name>;
hold-time seconds;
local-address local-ip-address;
port port-number;
preference number;
record-lifetime seconds;
refresh-time seconds;
traceoptions {
file filename <files number> <size size> <(world-readable | no-world-readabl... | [edit logical-systems logical-system-name routing-instances instance-name routing-options
validation group group-name],
[edit logical-systems logical-system-name routing-options validation group group-name],
[edit routing-instances instance-name routing-options validation group group-name],
[edit routing-options valid... | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and rest... | [
{
"name": "server-ip-address",
"desc": "Specify the IP address of the RPKI cache server."
},
{
"name": "database",
"desc": ""
},
{
"name": "database-name",
"desc": "Specify a named validation database."
},
{
"name": "hold-time",
"desc": ""
},
{
"name": "seconds",
... | 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. | [
"Use Case and Benefit of Origin Validation for BGP",
"Understanding Origin Validation for BGP",
"Example: Configuring Origin Validation for BGP"
] |
session (Protocols LDP) | session session-address {
authentication-algorithm (aes-128-cmac-96 | hmac-sha-1-96 | md5);
authentication-key authentication-key;
authentication-key-chain authentication-key-chain;
downstream-on-demand downstream-on-demand;
(mtu-discovery | no-mtu-discovery);
transport-address transport-address... | [edit logical-systems name protocols ldp],
[edit logical-systems name routing-instances name protocols ldp],
[edit protocols ldp],
[edit routing-instances name protocols ldp] | Configure Label Distribution Protocol (LDP) session parameters by specifying the session destination
address.
The TCP maximum segment size (TCP-mss) is a non-configurable derivative of maximum transmission
unit (MTU). The TCP-mss derived for an LDP and the maximum LDP TCP-mss size are dependent on the
MTU size of the i... | [
{
"name": "session-address",
"desc": "Session destination address."
},
{
"name": "authentication-algorithm",
"desc": "Authentication algorithm name. Values:"
},
{
"name": "aes-128-cmac-96",
"desc": "Cipher-based Message Authentication Code (AES128)"
},
{
"name": "hmac-sha-1-... | routing | Statement introduced before Junos OS Release 7.4.
authentication-algorithm statement introduced in Junos OS Release 7.6.
transport-address option introduced in Junos OS Releasse 19.1R1 for all platforms. | [
"Configuring the TCP MD5 Signature for LDP Sessions"
] |
session (Security IKE) | session {
full-open {
incoming-exchange-max-rates {
ike-rekey value;
ipsec-rekey value;
keepalive value;
}
}
half-open {
timeout seconds;
backoff-timeouts {... | [edit security ike] | Defines IKE session configuration.
In the configuration hierarchy, you can set the system level parameters of the IKE session to manage the
behavior of the negotiations with the remote peer. You configure these settings to control high load
scenarios. | [
{
"name": "full-open",
"desc": "Define the full open IKE session parameters."
},
{
"name": "half-open",
"desc": "Define the half open IKE session parameters."
},
{
"name": "incoming-exchange-",
"desc": ""
},
{
"name": "max-rates",
"desc": "Define the full open IKE session... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | session statement introduced in Junos OS Release 23.4R1. | [
"IKE Protection from DDoS Attacks"
] |
session (System Services) | session {
idle-timout minutes;
session-limit number;
} | [edit system services web-management] | Configure parameters for web-management sessions. Web management allows for configuration of the
SRX Series Firewall using the J-Web interface. You can configure the idle-timeout parameter for web-
management sessions and the maximum number of concurrent sessions. | [
{
"name": "idle-timeout",
"desc": ""
},
{
"name": "minutes",
"desc": "Configure in minutes the time-out parameter for all web-management sessions. The idle-timeout parameter specifies the length of time that a session can be idle before it is terminated. Default: 1440 Range: 1 to 1440"
},
... | system—To view this in the configuration.
system-control—To add this to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Firewall User Authentication Overview",
"Dynamic VPN Overview"
] |
session (Web Management) | session {
idle-timeout minutes;
session-limit number of sessions;
} | [edit system services web-management] | Configure limits for the number of minutes a session can be idle before it times out, and configure the
number of simultaneous J-Web user login sessions. | [
{
"name": "idle-timeout minutes",
"desc": "Configure the number of minutes a session can be idle before it times out. Range: 1 through 1440 minutes Default: 30 minutes"
},
{
"name": "session-limit number of",
"desc": ""
},
{
"name": "sessions",
"desc": "Configure the maximum number... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [] |
session-affinity | session-affinity ipsec | [edit security flow load-distribution] | Enable VPN session affinity. In session affinity feature, we’ve optimized tunnel redistribution. After
tunnel redistribution, the data path might not be optimal, hence we recommend that you enable VPN
session affinity to ensure that the data path is optimized. During optimization, the current data path
experiences a hi... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4R5.
Starting with Junos OS Release 15.1X49-D10, IPsec session affinity is supported for IPsec tunnel-based
traffic by the SRX5K-MPC3-100G10G (IOC3) and the SRX5K-MPC3-40G10G (IOC3) for SRX5400,
SRX5600, and SRX5800 devices through improved flow module and session cache. | [
"IPsec Overview"
] |
session-close | session-close; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then log] | Enable traffic to which the policy applies to be logged at the end of a session.
Session-ager is a process that runs at regular intervals and cleans up inactive sessions. The timestamp of
the session-close log is the time that session-ager closes the session. | [] | 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",
"Understanding Security Policy Rules",
"Understanding Security Policy Elements"
] |
session-drop-hold-down | session-drop-hold-down time; | [edit security nat source] | Specify the session hold time value to hold the NAT source session without expiring. The session hold
time value must be 30 seconds through 28,800 seconds (eight hours). | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1. | [] |
session-establishment-hold-time | session-establishment-hold-time seconds; | [edit protocols iccp],
[edit protocols iccp peer] | Specify the time during which an Inter-Chassis Control Protocol (ICCP) connection must be established
after IP route reachability between MC-LAG peers is up. When an MC-LAG peer detects IP route
reachability to the MC-LAG peer, it tries to connect to it during the session-establishment-hold-time.
NOTE: On QFX and EX Se... | [
{
"name": "seconds",
"desc": "Time (in seconds) within which a successful ICCP connection must be established."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [] |
session-expiry (MX Series in Enhanced LAN Mode) | session-expiry seconds; | [edit protocols authentication-access-control interface (all | interface-names)] | Configure the maximum duration in seconds of a session. | [
{
"name": "seconds",
"desc": "Duration of session."
}
] | 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. | [] |
session-group | session-group name {
authentication-algorithm (aes-128-cmac-96 | hmac-sha-1-96 | md5);
authentication-key authentication-key;
authentication-key-chain authentication-key-chain;
downstream-on-demand;
(mtu-discovery | no-mtu-discovery);
transport-address transport-address;
} | [edit logical-systems name protocols ldp],
[edit logical-systems name routing-instances name protocols ldp],
[edit protocols ldp],
[edit routing-instances name protocols ldp] | Specify the prefix address of the aggregated group of LDP neighbors for the remote end of the LDP
session.
The session-group statement is useful when an LDP neighbor is dynamic; for instance, in the case of
remote loop free alternate (LFA), a targeted or indirect LDP neighbor is automatically picked from any of
the nod... | [
{
"name": "name",
"desc": "Session destination address or prefix length."
},
{
"name": "authentication-algorithm",
"desc": "Authentication algorithm name. Values:"
},
{
"name": "aes-128-cmac-96",
"desc": "Cipher-based Message Authentication Code (AES128)"
},
{
"name": "(96 b... | 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.
transport-address option introduced in Junos OS Releasse 19.1R1 for all platforms.
Starting in Junos OS Evolved 22.1R1 Release, MD5 authentication algorithm is supported for all
platforms. | [
"Configuring the TCP MD5 Signature for LDP Sessions"
] |
session-id-change-limiter-indirect | forwarding-table {
session-id-change-limiter-indirect;
} | [edit routing-options] | Creates additional indirect nexthop in the nexthop chain to store session-id changes. When a session-id
is changed in any of the indirect nexthop, the Packet Forwarding Engine must reprogram all the parent
nodes of the indirect-nexthop. To limit the number of parent nodes that will be re-programmed, an
additional indir... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.4.
Statement introduced in Junos OS Evolved Release 22.2. | [] |
session-init | session-init; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then log] | Enable traffic to which the policy applies to be logged at the beginning of a session. | [] | 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",
"Understanding Security Policy Rules",
"Understanding Security Policy Elements"
] |
session-limit (IDS MS-DPC) | session-limit {
by-destination (IDS MS-DPC) {
hold-time seconds;
maximum number;
packets number;
rate number;
}
by-pair (IDS MS-DPC) {
hold-time seconds;
maximum number;
packets number;
rate number;
}
by-source (IDS MS-DPC) {
h... | [edit services ids rule rule-name term term-name then] | Enable flow limitation by configuring thresholds on source, destination, or stateful firewall and network
address translation (NAT) paired traffic flows when using the MS-DPC. | [] | 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 Actions in IDS Rules"
] |
session-limit (IDS MS-MPC) | session-limit {
by-destination {
by-protocol {
icmp {
maximum number;
packets number;
rate number;
}
tcp {
maximum number;
packets number;
rate number;
}
... | [edit services ids rule rule-name term term-name then] | Configure the IDS rule session limits for an individual destination or source address or subnet. This
protects against network probing attacks and network flooding attacks. This IDS rule can only be
assigned to a service set on an MS-MPC.
You can specify limits for specific protocols (ICMP, TCP, and UDP), or specify li... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
session-limit (Service Set Next Gen Services) | session-limit {
maximum number;
} | [edit services service-set service-set-name service-set-options] | Specify the maximum number of sessions allowed simultaneously on the service set. If you specify the
maximum number of sessions to be zero, it indicates that the configuration is not effective. You must
specify a value higher than zero for the maximum number of sessions. | [
{
"name": "number",
"desc": "Maximum number of sessions. Range: 1 through 4,294,967,295"
}
] | 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. | [] |
session-limit (System Services) | session-limit; | [edit system services web-management session] | Configure the maximum allowed number of concurrent web management sessions. Using the CLI, you
can limit the number of concurrent sessions from 1 to 1024. Each session remains open for 24 hours
(1440 minutes).
You can also set an idle time-out parameter to override the default to specify the length of time a
session ca... | [
{
"name": "session-limit",
"desc": ""
},
{
"name": "number",
"desc": "Default: unlimited sessions Range: 1 to 1024 sessions"
}
] | system—To view this in the configuration.
system-control—To add this to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Firewall User Authentication Overview",
"Dynamic VPN Overview"
] |
session-limit | session-limit {
maximum number;
rate (Interface Services) new-sessions-per-second;
cpu-load-threshold percentage;
} | [edit interfaces interface-name services-options] | Restrict the maximum number of sessions and the session rate on services cards.
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.6.
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. | [] |
session-limit-per-username (Access Profile) | session-limit-per-username number; | [edit access profile profile-name] | Limit the number of active sessions allowed for a username associated with a given access profile. This
enables you to control credential sharing by legitimate subscribers. After the limit is configured, existing
subscriber sessions for the access profile are tracked as active sessions, as are any new sessions that do
... | [
{
"name": "number",
"desc": "Maximum number of subscriber sessions allowed per username in the access profile. Range: 1 through 16"
}
] | access | Statement introduced in Junos OS Release 18.4R1. | [
"Session Options for Subscriber Access",
"Session Options for Subscriber Access"
] |
session-memory (resource-manager) | session-memory {
match {
threshold threshold;
}
then {
alarm;
drop-flows;
log;
session-aggressive-ageout {
early-ageout early-ageout;
}
}
} | [edit security resource-manager] | Configure resource manager session-memory options to control the behavior of the device based on the
sessions that the device is handling. | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [
"Traffic Processing on SRX Series Devices Overview"
] |
session-mode | session-mode (automatic | multihop | singlehop); | [edit system services dhcp-local-server liveness-detection method bfd],
[edit system services dhcp-local-server dhcpv6 liveness-detection method bfd],
[edit forwarding-options dhcp-relay liveness-detection], [edit forwarding-options dhcp-relay
dhcpv6 liveness-detection method bfd],
[edit system services dhcp-local-ser... | Configure the session mode. | [
{
"name": "automatic",
"desc": "Configure single-hop BFD sessions if the peer is directly connected to the router interface and multihop BFD sessions if the peer is not directly connected to the router interface."
},
{
"name": "multihop",
"desc": "Configure multihop BFD sessions and passive DHCP... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Example: Configuring Group Liveness Detection with BFD for DHCP Local Server Clients",
"Example: Configuring Global Liveness Detection with BFD for DHCP Relay Agent Clients"
] |
session-offload | session-offload; | [edit chassis fpc slot-number pic number adaptive-services service-package extension-provider] | Enable session offloading on a per-PIC basis for a Multiservices PIC.
Default
Session offloading is disabled. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced on MX Series 5G Universal Routing Platforms with MS-DPCs in Junos OS Release
9.6. | [
"Enabling Session Offloading for Multiservices DPCs"
] |
session-options (Access Profile) | session-options {
client-group [group-names];
client-idle-timeout minutes;
client-session-timeout minutes;
} | [edit access profile profile-name] | Define options that control a user's session after successful 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 RADIUS and LDAP User Authentication"
] |
session-options | session-options {
client-group [ group-names ];
client-idle-timeout minutes;
client-idle-timeout-ingress-only;
client-session-timeoutminutes;
pcc-context {
input-service-filter-name filter-name;
input-service-set-name service-set-name;
ipv6-input-service-filter-name filter-na... | [edit access profile profile-name] | (MX Series and SRX Series Firewalls) Define options to place limits on subscriber access based on how
long the session has been up, how long the user has been inactive, or both.
(MX Series) Define options to modify a subscriber username at login based on the subscriber’s access
profile.
(MX Series) Specify characteris... | [
{
"name": "client-idle-",
"desc": ""
},
{
"name": "timeout",
"desc": "Specify the grace period that begins after an authenticated user terminates all sessions and connections. Authentication is not required if a new connection is initiated during the grace period by the same user. During this pe... | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Session Options for Subscriber Access",
"Enabling Direct PCC Rule Activation by a PCRF for Subscriber Management"
] |
session-persistence-scan | session-persistence-scan; | [edit security nat source] | Specify the sessions to be retained if there is a change in NAT configuration. The existing sessions are
retained, if the new session and existing sessions are in the same security zone. | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1. | [] |
session-pics (Diameter) | session-pics {
group {
group-name {
[session-pic interface-name];
}
}
} | [edit unified-edge tdf gateway-name diameter network-element element-name] | Configure the session PICs that are serving this Diameter network element for Diameter bindings on this
TDF gateway.
NOTE: If you want to set up Diameter bindings for session PICs on the TDF gateway,
contact Juniper Networks Professional Services for assistance. | [
{
"name": "group-name",
"desc": "Name of the session PIC group that is serving the Diameter network element."
},
{
"name": "interface-name",
"desc": "Name of interface representing session PIC. Syntax: The interface must be a valid multiservices interface (ams or ms-a/b/0, where a is the Flexib... | 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. | [] |
session-pics | session-pics {
[interface interface-name];
} | [edit unified-edge gateways tdf gateway-name system] | Specify the service interfaces that represent the session PICs used for the control plane in the TDF
gateway.
The remaining statement is explained separately. See CLI Explorer. | [] | 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 Session PICs",
"TDF Gateway Service PICs and Session PICs for Subscriber-Aware Traffic Treatment"
] |
session-protection | session-protection {
timeout seconds;
} | [edit logical-systems logical-system-name protocols ldp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp],
[edit protocols ldp],
[edit routing-instances routing-instance-name protocols ldp] | Configure when an LDP session is torn down and resignaled after the router stops receiving hello
messages from a neighboring router. You might want to modify this behavior to prevent an LDP session
from being unnecessarily terminated and reestablished. The LDP session remains up for the duration
specified as long as th... | [
{
"name": "timeout seconds",
"desc": "Time in seconds before the LDP session is torn down and resignaled."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | [
"Configuring LDP Session Protection"
] | |
session-scan | session-scan; | [edit security dynamic-address address-name name] | Session scan provides an efficient method to traverse the session table to check and update each
session. You can configure the session-scan option at two levels, entry level and module level. The entry
level session-scan requests session scan only when the configured entries have the new addresses, while
the module le... | [] | security | Statement introduced in Junos OS Release 20.4R1. | [] |
session-timeout (Application Identification) | session-timeout seconds; | [edit services application-identification application application-name] | Define session lifetime for the specified application in seconds. | [
{
"name": "seconds",
"desc": "Duration of session."
}
] | 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. | [
"Defining an Application Identification"
] |
session-timeout (Interfaces) | session-timeout seconds; | [edit interfaces interface-name services-options] | Define session lifetime globally for the Multiservices interface in seconds. | [
{
"name": "seconds",
"desc": "Duration of session."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Defining an Application Identification"
] |
session-timeout (Service Set Next Gen Services) | session-timeout seconds; | [edit services service-set service-set-name service-set-options] | Define session lifetime for the service set in seconds. The session is closed after this amount of time,
even if traffic is running on the session. | [
{
"name": "seconds",
"desc": "Duration of session."
}
] | 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. | [] |
session-timeout | session-timeout session-timeout; | [edit dynamic-profiles name interfaces name unit name demux inet auto-configure address-ranges],
[edit dynamic-profiles name interfaces name unit name family inet auto-configure address-ranges],
[edit dynamic-profiles name interfaces interface-range name unit name demux inet auto-configure
address-ranges],
[edit dynam... | Self destruct or auto clear timeout in seconds for auto configuration of session timeout. | [] | [none specified] | Statement introduced in Junos OS release 24.4R1. | [] |
session-update-interval | session-update-interval session-update-interval; | [edit security application-tracking] | Configure the interval between session update messages for long-lived sessions being monitored by
AppTrack. Byte count, packet count, and start and end times are updated and logged when the amount
of time between session start or the previous update and the current time exceeds the interval. | [
{
"name": "session-update-interval",
"desc": "Minutes between updates."
}
] | 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. | [
"Example: Configuring AppTrack"
] |
sessions-limit-group (L2TP) | sessions-limit-group limit-group-name {
maximum-sessions number;
} | [edit services l2tp] | Create a group of clients so that you can limit the number of L2TP sessions allowed for the client group.
You can create up to 200 groups. | [
{
"name": "limit-group-name",
"desc": "Identifier of the session-limit group for which the session limit is configured. The remaining statement is explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"L2TP LAC Tunneling for Subscribers",
"L2TP LAC Subscriber Configuration",
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces",
"L2TP for Subscriber Access Overview"
] |
set chassis cluster cluster-id node node-number reboot | set chassis cluster cluster-id cluster-id node node-number reboot | Sets the chassis cluster identifier (ID) and node ID on each device, and reboots the devices to enable
clustering. The system uses the chassis cluster ID and chassis cluster node ID to apply the correct
configuration for each node (for example, when you use the apply-groups command to configure the
chassis cluster mana... | [
{
"name": "cluster-id cluster-id",
"desc": "Identifies the cluster within the Layer 2 domain. Range: 0 through 255"
},
{
"name": "node node",
"desc": "Identifies a node within a cluster. Range: 0 through 1"
},
{
"name": "reboot",
"desc": "reboot the specified devices to configure t... | maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request. | Support for extended cluster identifiers (more than 15 identifiers) added in Junos OS Release 12.1X45-
D10. | [
"Example: Setting the Chassis Cluster Node ID and Cluster ID",
"Understanding the Interconnect Logical System and Logical Tunnel Interfaces",
"Example: Configuring Logical Systems in an Active/Passive Chassis Cluster (Primary Administrators",
"Only)",
"Disabling a Chassis Cluster",
"set chassis cluster di... | |
set chassis cluster disable reboot | set chassis cluster disable <reboot> | After defining chassis cluster configuration, you can disable or remove a chassis cluster and change the
SRX Series Firewalls to standalone devices by running the set chassis cluster disable reboot command
from the operational mode.
After the chassis cluster is disabled using this CLI command, you do not have a similar... | [
{
"name": "reboot",
"desc": "You can disable the chassis cluster and run the reboot command. When the reboot is completed, you can view the SRX device functioning in standalone mode."
}
] | maintenance
Output Fields
Sample Output
set chassis cluster disable reboot
user@host> set chassis cluster disable reboot
Successfully disabled chassis cluster. Going to reboot now. | Statement introduced in Junos OS Release 9.0. | [
"Disabling a Chassis Cluster"
] | |
set chassis display message | set chassis display message “message ” (fpc-slot slot-number | lcc number | sfc number)
<permanent> | Display or stop a text message on the craft interface display, which is on the front of the router, or on
the LCD panel display on the switch. The craft interface alternates the display of text messages with
standard craft interface messages three times, switching between messages every 60 seconds.
NOTE: On T Series ro... | [
{
"name": "\"message\"",
"desc": "Message to display. On the craft interface display, if the message is longer than 20 characters, it wraps onto the next line. If a word does not fit on one line, the entire word moves down to the next line. Any portion of the message that does not fit on the display is trun... | clear
Output Fields
See show chassis craft-interface for an explanation of output fields.
Sample Output
set chassis display message (Creating)
The following example shows how to set the display message and verify the result:
user@host> set chassis display message "NOC
contact Dusty (888) 555-1234"
message sent
user@h... | Command introduced before Junos OS Release 7.4.
sfc option for TX Matrix Plus router introduced in Junos OS Release 9.6. | [
"Configuring the LCD Panel on EX Series Switches (CLI Procedure)",
"clear chassis display message",
"show chassis craft-interface"
] | |
set chassis virtual-chassis | set chassis virtual-chassis
<disable>
<local> | Set the EX8200 switch into Virtual Chassis mode.
An EX8200 switch cannot be a member switch in an EX8200 Virtual Chassis until the switch is in Virtual
Chassis mode.
This command is not needed when configuring an EX3300 Virtual Chassis, EX4200 Virtual Chassis,
EX4500 Virtual Chassis, or a mixed EX4200 and EX4500 Virtua... | [
{
"name": "none",
"desc": "Set the internal Routing Engines into Virtual Chassis mode."
},
{
"name": "disable",
"desc": "Disable Virtual Chassis mode for all internal REs on the switch."
},
{
"name": "local",
"desc": "Set the Routing Engine that you are currently logged in to into Vi... | view
Sample Output
set chassis virtual-chassis
user@switch> set chassis virtual-chassis
This will reboot the RE(s)
Do you want to continue ? [yes,no] (no) yes | Command introduced in Junos OS Release 10.4. | [
"Configuring an EX8200 Virtual Chassis (CLI Procedure)"
] | |
set cli complete-on-space | set cli complete-on-space (off | on) | Set the command-line interface (CLI) to complete a partial command entry when you type a space or a
tab. This is the default behavior of the CLI. | [
{
"name": "off",
"desc": "Turn off command completion."
},
{
"name": "on",
"desc": "Allow either a space or a tab to be used for command completion."
}
] | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
set cli complete-on-space
In the following example, pressing the Spacebar changes the partial command entry from com to
complete-on-space. The example shows how adding the keyword off at the end of the... | Command introduced before Junos OS Release 7.4. | [
"CLI User Interface Overview"
] | |
set cli directory | set cli directory directory | Set the current working directory. | [
{
"name": "directory",
"desc": "Pathname of the working directory."
}
] | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
set cli directory
user@host> set cli directory /var/tmp
Current directory: /var/tmp | Command introduced before Junos OS Release 7.4. | [
"CLI User Interface Overview"
] | |
set cli idle-timeout | set cli idle-timeout <minutes> | Set the maximum time that an individual session can be idle before the user is logged off the router or
switch. set cli idle-timeout holds good only for the session in use when you enter it. If you need to
configure the idle timeout permanently for all the CLI sessions, then configure the idle-timeout statement
at the ... | [
{
"name": "minutes",
"desc": "(Optional) Maximum idle time. The range of values, in minutes, is 0 through 100,000. If you do not issue this command, and the user’s login class does not specify this value, the user is never forced off the system after extended idle times. Setting the value to 0 disables the ... | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
set cli idle-timeout
user@host> set cli idle-timeout 60
Idle timeout set to 60 minutes | Command introduced before Junos OS Release 7.4. | [
"CLI User Interface Overview"
] | |
set cli logical-system | set cli logical-system logical-system | Set the CLI to the specified logical system view. | [
{
"name": "logical-system",
"desc": "logical system name."
}
] | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
set cli logical-system
user@host> set cli logical-system log-router-A
logical system: log-router-A
user@host:log-router-A> | Command introduced before Junos OS Release 7.4. | [
"Logical Systems User Guide for Routers and Switches"
] | |
set cli prompt | set cli prompt string | Set the prompt so that it is displayed within the CLI. | [
{
"name": "string",
"desc": "CLI prompt string. To include spaces in the prompt, enclose the string in quotation marks. By default, the string is username@hostname."
}
] | view
Output Fields
When you enter this command, the new CLI prompt is displayed.
Sample Output
set cli prompt
user@host> set cli prompt lab1-router>
lab1-router> | Command introduced before Junos OS Release 7.4. | [
"CLI User Interface Overview"
] | |
set cli restart-on-upgrade | set cli restart-on-upgrade string (off | on) | For an individual session, set the CLI to prompt you to restart the router or switch after upgrading the
software. | [
{
"name": "off",
"desc": "Disables the prompt."
},
{
"name": "on",
"desc": "Enables the prompt."
}
] | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
set cli restart-on-upgrade
user@host> set cli restart-on-upgrade on
Enabling restart-on-upgrade | Command introduced before Junos OS Release 7.4. | [
"CLI User Interface Overview"
] | |
set cli screen-length | set cli screen-length length | Set terminal screen length.
user@host> set cli screen-length 75
Screen length set to 75 | [
{
"name": "length",
"desc": "Number of lines of text that the terminal screen displays. The range of values, in an integer"
}
] | view | Command introduced before Junos OS Release 7.4. | [
"Setting the Junos OS CLI Screen Length and Width"
] | |
set cli screen-width | set cli screen-width width | Set the terminal screen width.
user@host> set cli screen-width
Screen width set to 132 | [
{
"name": "width",
"desc": "Number of characters in a line. The value is 0 or in the range of 40 through 1024. The default value"
}
] | view | Command introduced before Junos OS Release 7.4. | [
"Setting the Junos OS CLI Screen Length and Width"
] | |
set cli terminal | set cli terminal terminal-type | Set the terminal type.
user@host> set cli terminal xterm | [
{
"name": "terminal-type",
"desc": "Type of terminal that is connected to the Ethernet management port:"
},
{
"name": "ansi",
"desc": "ANSI-compatible terminal"
},
{
"name": "pc",
"desc": "PC screen command-prompt window"
},
{
"name": "small-xterm",
"desc": "Small xterm w... | view | Command introduced before Junos OS Release 7.4. | [
"CLI Environment Settings"
] | |
set cli timestamp | set cli timestamp (format timestamp-format | disable) | Set a timestamp for CLI output. | [
{
"name": "format",
"desc": ""
},
{
"name": "timestamp-format",
"desc": "Set the date and time format for the timestamp. The timestamp format you specify can include the following placeholders in any order:"
},
{
"name": "%m",
"desc": "Two-digit month"
},
{
"name": "%d",
... | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
set cli timestamp
user@host> set cli timestamp format '%m-%d-%T'
'04-21-17:39:13'
CLI timestamp set to: '%m-%d-%T' | Command introduced before Junos OS Release 7.4. | [
"CLI User Interface Overview"
] | |
set date ntp | set date ntp <servers | force | key key | node node-number | routing-instance routing-instance-
name | source-address source-address> | Set the date and local time. If reject mode is enabled and the system rejected the update from the NTP
server because it exceeds the configured threshold value, an administrator has two options to overrule
the reject mode action: manually set the date and time in YYYYMMDDhhmm.ss format, or force
synchronization of devi... | [
{
"name": "servers",
"desc": "Specify the IP address of one or more NTP servers."
},
{
"name": "force",
"desc": "Force system date and time to update to NTP server values. The device date and time are synchronized with the NTP proposed date and time even if reject is set as the action and the di... | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
set date ntp force
user@host> set date ntp force
18 Jul 16:52:43 ntpdate[3319]: NTP update request has been accepted, The time offset is
147605840.624994 sec from the time server 66.129.255.62 which ... | Command introduced in Junos OS Release 15.1X49-D70. | [
"NTP Time Synchronization on SRX Series Devices"
] | |
set date | set date (date-time | ntp <ntp-server> <key authentication-key number> <servers> <source-address
source-address>) | Set the date and time.
user@host> set date ntp
21 Apr 17:22:02 ntpdate[3867]: step time server 172.17.27.46 offset 8.759252 sec | [
{
"name": "date-time",
"desc": "Specify date and time in one of the following formats:"
},
{
"name": "YYYYMMDDHHMM.SS",
"desc": ""
},
{
"name": "“month DD, YYYY HH:MM(am | pm)”",
"desc": "NOTE: In Junos OS Evolved, the date and time will be set only on the node where the command is i... | view
Sample Output
set date ntp (Junos OS)
user@host> set date ntp
22 Jun 10:07:48 ntpdate[51123]: step time server 66.129.255.62 offset -0.013200 sec
set date ntp (Junos OS Evolved)
user@host> set date ntp
-------------------------------
node: re0
-------------------------------
error: ntpd is already running | Command introduced before Junos OS Release 7.4.
key option introduced in Junos OS Release 12.1R2 | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.