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 |
|---|---|---|---|---|---|---|---|
security-profile | security-profile {
profile name {
address-book (System) {
maximum maximum;
reserved reserved;
}
advanced-anti-malware-policy {
maximum maximum;
reserved reserved;
}
auth-entry {
maximum maximum;
reserved ... | [edit system],
[edit tenants tenant-name] | Create a security profile and specify the kinds and amounts of resources to allocate to a logical system
to which the security profile is bound.
As a primary administrator, you can create a security profile and bind it to more than one logical system
if you want to allocate the same kinds and amounts of resources to th... | [
{
"name": "profile-name",
"desc": "Name of the security profile."
},
{
"name": "resources",
"desc": "Name of the resources."
}
] | 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.
The dslite-softwire-initiator option introduced in Junos OS Release 12.1.
The security-profile option added under the tenants hierarchy in Junos OS Release 18.3R1.
The icap redirect profile option is introduced in Junos OS Release 18.3R1.
secure-wire option introduced in ... | [
"Understanding Logical Systems Security Profiles (Primary Administrators Only)",
"Example: Configuring Logical Systems Security Profiles (Primary Administrators Only)"
] |
security-profile-resources | security-profile-resources {
cpu-control;
cpu-control-target percent;
} | [edit system] | Configure global settings that apply to all logical systems in the device. | [
{
"name": "cpu-control",
"desc": "Enable CPU utilization control."
},
{
"name": "cpu-control-target percent",
"desc": "Specify the upper limit for CPU utilization on the device under normal"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Understanding Logical Systems Security Profiles (Primary Administrators Only)",
"Example: Configuring Logical Systems Security Profiles (Primary Administrators Only)"
] |
security-service (Security Forwarding Options) | security-service (fail-open); | [edit security forwarding-options] | The system resource management guarantees the resources are used according to priorities. the fail-
open/fail-close impacts the new session creation only when the system resource is busy.
•
If system resource is not busy, fail-open/fail-close won't take effect. No impact to traffic.
•
If system resource is busy and the... | [
{
"name": "fail-open",
"desc": "Ignores Layer 7 services with resource requirements, creates a flow session without Layer"
}
] | security—To view this in the configuration.
security-control—To add this to the configuration. | Support on SRX Series Firewalls for flow based security-service in Junos OS Release 20.4R1. | [
"Traffic Processing on SRX Series Devices Overview"
] |
security-to-group | security-to-group {
security-model (usm | v1 | v2c) {
group group-name;
security-name security-name;
}
} | [edit snmp v3 vacm] | Configure the group to which a specific SNMPv3 security name belongs. The security name is used for
messaging security.
The remaining statements are explained separately. See CLI Explorer. | [] | 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-zone | security-zone zone-name {
address-book {
address address-name {
ip-prefix {
description text;
}
description text;
dns-name domain-name {
ipv4-only;
ipv6-only;
}
range-address lower-limit t... | [edit security zones] | Define a security zone, which allows you to divide the network into different segments and apply
different security options to each segment. | [
{
"name": "zone-name",
"desc": "Name of the security zone."
}
] | 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.
Support for wildcard addresses added in Junos OS Release 11.1.
The description option added in Junos OS Release 12.1.
The unidirectional-seesion-refreshing option added in Junos OS Release 20.4R1.
The white-list option added in Junos OS Release 23.4R1. | [
"Security Zones Overview",
"Example: Configuring Application Firewall Rule Sets Within a Security Policy"
] |
segment | segment {
(pop | swap swap);
description description;
next-hop next-hop;
sid-label;
} | [edit logical-systems name protocols mpls static-label-switched-path],
[edit logical-systems name routing-instances name protocols mpls static-label-switched-path],
[edit protocols mpls static-label-switched-path],
[edit routing-instances name protocols mpls static-label-switched-path] | Static segment for segment routing. A static segment is identified by a unique name. This segment type
is assigned a segment identifier (SID) which falls under a default range of 100000 through 1048575. The
segment has label operation such as pop-and-forward for adjacency segment and swap-and-forward for
prefix or node... | [
{
"name": "pop",
"desc": "Pop the SID label"
},
{
"name": "swap",
"desc": "Swap the SID label to this label"
},
{
"name": "description",
"desc": "Text description of label-switched path"
},
{
"name": "next-hop",
"desc": ""
},
{
"name": "IPv4 address or interface o... | routing | Statement introduced in Junos OS Release 18.1R1 for MX Series, PTX Series, and QFX Series. | [
"Static Segment Routing Label Switched Path"
] |
segment-list | segment-list name {
hop-name {
(loose | strict);
ip_address IP address;
label number ;
label-type node
srv6-sid; }
auto-translate {
protected mandatory;
unprotected mandatory;
}
dynamic;
compute;
inherit-label-nexthops;
srv6;
} | [edit logical-systems name protocols source-packet-routing],
[edit protocols source-packet-routing] | Specify an name to identify the segment routing list (used in traffic engineering policy) and the explicit
path for source routing label switched path (LSPs) to traverse through traffic engineering segments. The
segment list is essentially a stack of segment identifiers.
Starting in Junos OS release 19.1R1 for MX and P... | [
{
"name": "name",
"desc": "Specify a name to identify a SR-TE segment-list. NOTE: The combined length of tunnel-name and LSP name must not exceed 53 characters for per-path telemetry to work."
},
{
"name": "<hop-name>",
"desc": "Indicates the next hop in the segment routing traffic engineering p... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1.
ip-address statement introduced in Junos OS Release 18.1R1 on MX Series routers.
inherit-label-nexthops, node-type, and auto-translate statements introduced in Junos OS Release 19.1R1 on
MX Series routers.
dynamic statement introduced in Junos OS Release 19.2R1 on all p... | [
"Static Adjacency Segment Identifier for ISIS",
"Static Segment Routing Label Switched Path",
"Segment Routing Traffic Engineering at BGP Ingress Peer Overview",
"Understanding Static Segment Routing LSP in MPLS Networks",
"extended-nexthop-color",
"sr-preference-override"
] |
select | select (manual | unconditional); | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name (primary |
secondary) path-name],
[edit protocols mpls label-switched-path lsp-name (primary | secondary) path-name] | Specify the conditions under which the path is selected to carry traffic. The manual and unconditional
options are mutually exclusive. | [
{
"name": "manual",
"desc": "The path is selected for carrying traffic if it is up and stable for at least the revert timer window"
},
{
"name": "unconditional",
"desc": "The path is always selected for carrying traffic, even if it is currently down or degraded"
}
] | 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. | [
"Specifying the Conditions for Path Selection"
] |
select-profile | select-profile profile-name | [edit interfaces interface-name cellular-options gsm-options] | Select the active profile to establish a data call with a Global System for Mobile Communications (GSM)
cellular network. | [
{
"name": "profile-name",
"desc": "Name of a configured profile that is to be used to establish a data call."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Understanding Ethernet Interfaces"
] |
selection-mode | selection-mode (configured-quality | received-quality); | [edit chassis synchronization] | Specify whether the clock source selection must use the configured or the received ESMC or SSM
quality level for a qualifying interface. In both the selection modes, the interface qualifies for clock
source selection only when the received ESMC or SSM quality level on the interface is equal to or
greater than the conf... | [
{
"name": "configured-quality",
"desc": "Set this option to let the clock source selection algorithm to use the ESMC or SSM quality level that is configured for a qualifying interface."
},
{
"name": "received-quality",
"desc": "Set this option to let the clock source selection algorithm to use t... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2R4. | [] |
selective | selective {
group multicast-prefix/prefix-length {
source ip-prefix/prefix-length {
ingress-replication {
create-new-ucast-tunnel;
label-switched-path-template {
(default-template | lsp-template-name);
}
... | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel],
[edit routing-instances routing-instance-name provider-tunnel] | Configure selective point-to-multipoint LSPs for an MBGP MVPN. Selective point-to-multipoint LSPs
send traffic only to the receivers configured for the MBGP MVPNs, helping to minimize flooding in the
service provider's network.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5.
The ingress-replication statement and substatements added in Junos OS Release 10.4. | [
"Configuring Point-to-Multipoint LSPs for an MBGP MVPN",
"Configuring PIM-SSM GRE Selective Provider Tunnels"
] |
selective-vlan-switching | selective-vlan-switching {
routing-instance routing-instance;
} | [edit forwarding-options satellite fpc] | Enables local switching for only a select number of VLANs on the satellite device. | [
{
"name": "routing-instance",
"desc": "Configure routing instance."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1. | [
"Configuring Junos Fusion Provider Edge"
] |
send (add-path) | send {
include-backup-path include-backup-path;
multipath;
path-count path-count;
path-selection-mode {
(all-paths | equal-cost-paths);
}
prefix-policy [ policy-names ... ];
} | [edit logical-systems logical-system-name protocols bgp group group-name family family family-
modifier add-path],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address family
family-modifier add-path],
[edit logical-systems logical-system-name routing-instances name protocols bgp g... | Enable advertisement of multiple paths to a destination, instead of advertising only the active path.
NOTE: On PTX1000 devices, the add-path configuration statement is not supported
under routing instances. | [
{
"name": "include-backup-",
"desc": ""
},
{
"name": "path",
"desc": "Configure the number of backup paths that BGP must advertise. Do not configure this option if you have configured all-paths at the [edit protocols bgp group name family name add-path send] hierarchy level. Range: 1 through 2"... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.3.
Support for range from 2 through 20 (for BGP) introduced in Junos OS Release 14.1.
multipath option introduced in Junos OS Release 16.1R2.
Support for 64 BGP add-paths introduced in Junos OS Release 18.4R1 for the MX Series.
include-backup-path and path-selection-mode opti... | [
"Understanding the Advertisement of Multiple Paths to a Single Destination in BGP",
"Example: Advertising Multiple BGP Paths to a Destination"
] |
send (Protocols RIP) | send send-options; | [edit logical-systems logical-system-name protocols rip],
[edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip],
[edit logical-systems logical-system-name routing-instances routin... | Configure RIP send options. | [
{
"name": "send-options",
"desc": "One of the following:"
},
{
"name": "broadcast",
"desc": "Broadcast RIP version 2 packets (RIP version 1 compatible)."
},
{
"name": "multicast",
"desc": "Multicast RIP version 2 packets. This is the default."
},
{
"name": "none",
"desc":... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring the Sending and Receiving of RIPv1 and RIPv2 Packets"
] |
send (Protocols RIPng) | send <none>; | [edit logical-systems logical-system-name protocols ripng],
[edit logical-systems logical-system-name protocols ripng group group-name neighbor neighbor-
name],
[edit logical-systems logical-system-name routing-instances routing-instances-name protocols
ripng],
[edit logical-systems logical-system-name routing-instanc... | Enable or disable sending of update messages. | [
{
"name": "none",
"desc": "(Optional) Disable sending of update messages."
}
] | 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.
Support for routing instances introduced in Junos OS Release 9.0. | [] |
send-acct-status-on-config-change (Access Profile) | send-acct-status-on-config-change; | [edit access profile profile-name accounting] | Configure the router’s authd process to send accounting messages when the RADIUS server status
changes for an access profile. When you include this statement, authd sends an Acct-On message when
the first RADIUS server is added to an access profile, and to send an Acct-Off message when the last
RADIUS server is removed... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1. | [
"Configuring Per-Subscriber Session Accounting",
"RADIUS Servers and Parameters for Subscriber Access"
] |
send-critical-event | send-critical-event; | [edit protocols oam ethernet link-fault-management action-profile action] | Send OAM PDUs with the critical event bit set. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Specifying the Actions to Be Taken for Link-Fault Management Events"
] |
send-dyn-subscription-indicator (PCRF Partition) | send-dyn-subscription-indicator; | [edit access pcrf partition partition-name] | Include the Juniper-Network-Family-Indicator AVP into its message requests. To enable the Policy
Control and Charging Rules Function (PCRF) to dynamically pass subscription-ID parameters, and
support a variety of authentication, authorization, and provisioning configuration, the Juniper attribute-
value pairs (AVPs) i... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the PCRF Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Interactions Between the PCRF, PCEF, and OCS",
"Understanding Upstream and Downstream Messages for the PCR... |
send-network-family-indicator (PCRF Partition) | send-network-family-indicator; | [edit access pcrf partition partition-name] | Include the Juniper-Network-Family-Indicator AVP into its message requests. In many cases, wireline
subscribers support only one IP family, which is required information for both AAA service and Policy
Control and Charging Rules Function (PCRF). To indicate this information, the Juniper-Network-Family-
Indicator AVP h... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the PCRF Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Interactions Between the PCRF, PCEF, and OCS",
"Understanding Upstream and Downstream Messages for the PCR... |
send-oam | send-oam; | [edit protocols l2circuit neighbor address interface interface-name static] | Enable the ability to ping a static pseudowire. If you configure the send-oam statement, it applies to the
backup neighbor as well. Once you have configured this statement, you can ping the static pseudowire
by issuing the ping mpls l2circuit command. | [] | 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 Static Layer 2 Circuits"
] |
send-origin-state-id (Diameter Applications) | send-origin-state-id; | [edit access pcrf partition partition-name],
[edit access ocs partition partition-name],
[edit diameter peer peer-name] | Include the Origin-State AVP for the Diameter peer, OCS partition, or PCRF partition. The AVP is
conveyed in Diameter-level or partition-level messages, respectively. The value of the AVP increases
every time it changes, such as when the system reboots. Sending the Origin-State AVP in messages
enables Diameter entities... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the OCS Partition",
"Configuring the PCRF Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interac... |
send-release-on-delete (DHCP Relay Agent) | send-release-on-delete; | [edit forwarding-options dhcp-relay dhcpv6 overrides],
[edit forwarding-options dhcp-relay overrides],
[edit forwarding-options dhcp-relay dhcpv6 group group-name overrides],
[edit forwarding-options dhcp-relay group group-name overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6 o... | Send a release message to the DHCP (or DHCPv6) server whenever DHCP relay or relay proxy deletes a
client. Use the statement at the [edit ... dhcpv6] hierarchy levels to configure DHCPv6 support.
M120 and M320 routers do not support DHCPv6. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4. | [
"Extended DHCP Relay Agent Overview",
"Overriding the Default DHCP Relay Configuration Settings",
"Sending Release Messages When Clients Are Deleted"
] |
sender-based-rpf (MBGP MVPN) | sender-based-rpf; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
mvpn],
[edit routing-instances routing-instance-name protocols mvpn] | In a BGP multicast VPN (MVPN) with either RSVP-TE point-to-multipoint or MLDP point-to-multipoint
provider tunnels, configure a downstream provider edge (PE) router to forward multicast traffic only
from a selected upstream sender PE router.
Starting in Junos OS Release 21.1R1, you can configure MLDP point-to-multipoin... | [] | 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.
Support for MLDP point-to-multipoint provider tunnel is introduced in Junos OS Release 21.1R1 for MX
Series router. | [
"Understanding Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider",
"Tunnels",
"Example: Configuring Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider",
"Tunnels",
"Example: Configuring Sender-Based RPF in a BGP MVPN with MLDP Point-to-Multipoint Provider",
"Tu... |
sendid-tlv | sendid-tlv {
send-chassis-tlv;
} | [edit protocols oam ethernet connectivity-fault-management][edit protocols oam ethernet connectivity-fault-
management maintenance-domain maintenance-domain-name maintenance-association maintenance-association-name
continuity-check] | Configures Junos OS to send the sender ID TLV along with the packets. The sender ID TLV is an optional
TLV that is sent in continuity check messages (CCMs), loopback messages, and Link Trace Messages
(LTMs), as specified in the IEEE 802.1ag standard. TLVs (type, length, and value) are described in the IEEE
802.1ag stan... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R2. | [
"CFM Monitoring between CE and PE Devices"
] |
sensor (Junos Telemetry Interface) | sensor sensor-name {
export-name export-profile-name;
polling-interval seconds;
resource resource-string;
<resource-filter regular expression>;
server-name [ streaming-server-names ];
} | [edit services analytics] | 19.1R1
Statement introduced in Junos OS Release 19.1R1 for PTX3000 routers and PTX5000 routers with
FPC2. | [
{
"name": "sensor-name",
"desc": "Specify a name that defines the sensor configuration. For example, for a sensor configuration that monitors all LSP events, you might choose the name lsp-mon-global. For a sensor configuration that monitors events only for an LSP named A2B, you might choose the name lsp-mon... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F3.
Support for MPC7E, MPC8E, and MPC9E on MX Series routers added in Junos OS Release 15.1F5.
Support for FPC1 and FPC2 on PTX Series routers added in Junos OS Release 16.1R3.
Statement introduced in Junos OS Release 19.1R1 for PTX3000 routers and PTX5000 routers with
FPC2.... | [] |
sensor-based-stats (Junos Telemetry Interface) | sensor-based-stats; | [edit protocols ldp traffic-statistics],
[edit protocols mpls] | Enable the collection of certain statistics for the Junos telemetry interface. You must configure this
statement when you configure a sensor to monitor and stream data for the following statistics:
•
LDP—Enable the collection of LDP traffic statistics. Use the resource option at the [edit services
analytics sensor sens... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F6.
Support at the [edit protocols mpls] hierarchy level introduced in Junos OS Release 19.2R1 for ACX6360
routers.
Statement supported in Junos OS Evolved Release 19.1R1 on PTX10003 routers and QFX 10003
switches.
Support at the [edit protocols ldp traffic-statistics] hiera... | [
"Understanding the Junos Telemetry Interface Export Format of Collected Data"
] |
sensor-based-stats | sensor-based stats {
per-interface-per-member-link {
egress;
ingress;
}
per-sid {
egress;
ingress;
}
subscribe {
interval interval;
}
} | [edit protocols isis source-packet-routing]
[edit protocols (ospf | ospf3) source-packet-routing] | Enable the collection of aggregate segment routing statistics for the Source Packet Routing in
Networking (SPRING) traffic only, excluding RSVP and LDP-signaled traffic. Family MPLS statistics per
interface are accounted for separately. The SR statistics also include SPRING traffic statistics per link
aggregation group... | [
{
"name": "per-interface-",
"desc": ""
},
{
"name": "per-member-",
"desc": ""
},
{
"name": "link",
"desc": "Configure sensor-based statistics per nexthop. Sensor-based statistics is the traffic statistics in a segment routing (SR) network that can be recorded in an OpenConfig complia... | routing—To view this statement in the configuration. | Statement introduced in Junos OS Release 17.4R1.
Support at the [edit protocols (ospf | ospf3) source-packet-routing] hierarchy level introduced in Junos OS
Release 23.1R1 and Junos OS Evolved Release 23.1R1. | [
"Understanding Source Packet Routing in Networking (SPRING)",
"Understanding the Junos Telemetry Interface Export Format of Collected Data"
] |
sensor-configuration | sensor-configuration {
application-identification {
max-packet-memory-ratio percentage-value;
}
detector {
protocol-name protocol-name {
tunable-name tunable-name { ... | [edit security idp] | Configure various IDP parameters to match the properties of transiting network traffic. | [
{
"name": "ssl-profile-name profile-name",
"desc": "SSL initiation profile name to be used for encrypted packet log"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. Packet memory ratios added in Junos OS Release
12.1X44-D20.
intel-inspect-cpu-usg-threshold, intel-inspect-cpu-usg-tolerance, intel-inspect-disable-content-
decompress, intel-inspect-enable, intel-inspect-free-mem-threshold, intel-inspect-mem-tolerance, intel-
inspect-proto... | [] |
separator | separator special-character; | [edit access profile profile-name client-name-filter client-name] | Specify a character to identify where stripping of characters occurs in a client name. Stripping removes
characters to the right of each instance of the specified character, plus the character itself. The stripping
begins with the rightmost separator character.
Use the separator statement with the count statement to de... | [
{
"name": "special-character",
"desc": "Character used to identify where to start the stripping of characters in a client 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. | [
"Obtaining Username and Role Information Through Firewall Authentication"
] |
seq-number-validated | seq-number-validated; | [edit security gtp profile profile-name] | When the command seq-number-validated is configured, GTP ALG check the sequence number in the
GTP-U packet. If it is not configured, the sequence check is disabled by default.
From Junos OS Release 20.4R1 onwards, the [edit security gprs gtp profile profile-name] hierarchy level is
replaced by [edit security gtp profil... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10. | [] |
sequence-check-required | sequence-check-required; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit tcp-
options] | Enable sequence check per policy. The sequence-check-required value overrides the global value no-
sequence-check. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Security Policies Overview",
"Understanding Security Policy Rules",
"Understanding Security Policy Elements"
] |
sequence-number (Security IDP ICMP Headers) | sequence-number {
match (equal | greater-than | less-than | not-equal);
value sequence-number;
} | [edit security idp custom-attack attack-name attack-type signature protocol icmp],
[edit security idp custom-attack attack-name attack-type signature protocol icmpv6] | Specify the sequence number of the packet. This number identifies the location of the request/reply in
relation to the entire sequence. | [
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value sequence-number",
"desc": "Match a decimal value."
}
] | 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. Statement modified in Junos OS Release 12.3X48-D25
to add ICMPv6 protocol support. | [] |
sequence-number (Security IDP TCP Headers) | sequence-number {
match (equal | greater-than | less-than | not-equal);
value sequence-number;
} | [edit security idp custom-attack attack-name attack-type signature protocol tcp] | Specify the sequence number of the packet. This number identifies the location of the data in relation to
the entire data sequence. | [
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value sequence-number",
"desc": "Match a decimal value."
}
] | 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. | [] |
serial-number (Junos Fusion) | serial-number serial-number; | [edit chassis satellite-management fpc slot-id] | Bind the specified FPC slot ID to a satellite device based on the serial number.
A Junos Fusion provides two methods of assigning an FPC identifier: Unique ID-based FPC
identification and connectivity-based FPC identification. Unique ID-based FPC identification maps an
FPC slot ID to a satellite device’s MAC address or... | [
{
"name": "serial-number",
"desc": "Specifies the serial number of the satellite device."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3.
Statement introdcued in Junos OS Release 16.1R1 for Junos Fusion Enterprise. | [
"Configuring Junos Fusion Provider Edge",
"Configuring or Expanding a Junos Fusion Enterprise"
] |
serial-number (MX Series Virtual Chassis) | serial-number serial-number; | [edit virtual-chassis member member-id] | As part of the preprovisioned configuration for an MX Series Virtual Chassis, specify the chassis serial
number of each MX Series member router in the Virtual Chassis configuration. If you do not correctly
specify a router’s serial number in the preprovisioned configuration, the software does not recognize
that router ... | [
{
"name": "serial-number",
"desc": "Alphanumeric string that represents the chassis serial number of each member router in"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Preprovisioned Member Information for a Virtual Chassis",
"Example: Configuring Interchassis Redundancy for MX Series 5G Universal Routing Platforms Using a",
"Virtual Chassis"
] |
serial-number | serial-number serial-number; | [edit virtual-chassis member member-id] | In a preprovisioned Virtual Chassis or Virtual Chassis Fabric (VCF), specify the serial number of each
member switch to be included in the configuration. If you do not include the serial number within the
configuration, the switch cannot be recognized as a member of a preprovisioned configuration. Serial
number values ... | [
{
"name": "serial-number",
"desc": "Permanent serial number for the external Routing Engine or for the member switch."
}
] | 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. | [
"Autoprovisioning a Virtual Chassis Fabric",
"Preprovisioning a Virtual Chassis Fabric",
"Configuring an EX2300, EX3400, or EX4300 Virtual Chassis",
"Configuring EX4600 Switches in a Mixed or Non-Mixed Virtual Chassis",
"Configuring an EX9200 Virtual Chassis",
"Configuring an EX4650 or a QFX Series Virtua... |
serial-options | serial-options {
clock-rate rate;
clocking-mode (dce | loop);
control-polarity (negative | positive);
cts-polarity (negative | positive);
dcd-polarity (negative | positive);
dce-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd ... | [edit interfaces se-pim/0/port] | Configure serial-specific interface properties.
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 prior to Junos OS Release 7.4. | [
"Serial Interfaces Overview",
"no-concatenate"
] |
server (Batch Commits) | server {
commit-intervalnumber-of-seconds-between-commits;
commit-schedule-profile;
days-to-keep-error-logsdays-to-keep-error-log-entries;
maximum-aggregate-poolmaximum-number-of-commits-to-aggregate;
maximum-entries number-of-entries;
redirect-completion-status;
retry-attempts;
retry-i... | [edit system commit] | 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": "commit-interval",
"desc": "Configure the interval in seconds between commits."
},
{
"name": "days-to-keep-error-logs",
"desc": "Configure the number of days to keep log entries. Valid range is from 1 to 366 days."
},
{
"name": "maximum-aggregate-pool",
"desc": "Configure t... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Example: Configuring Batch Commit Server Properties"
] |
server (DHCP and BOOTP Relay Agent) | server address {
logical-system logical-system-name <routing-instance [ <default> routing-instance-names ]>;
routing-instance [ <default> routing-instance-names ];
} | [edit forwarding-options helpers bootp],
[edit forwarding-options helpers bootp interface (interface-name | interface-group)] | Configure the router or switch to act as a DHCP and BOOTP relay agent. The device forwards all
broacast requests within the configured subnet to all configured servers in parallel. To support clients on
different VRFs, see the "relay-agent-option" on page 14828 statement. | [
{
"name": "address",
"desc": "One or more addresses of the server."
},
{
"name": "logical-system logical-system-name",
"desc": "(Optional) Logical system of the server."
},
{
"name": "routing-instance routing-instance-names",
"desc": "(Optional) Routing instance name that belong to t... | 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 Routers, Switches, and Interfaces as DHCP and BOOTP Relay Agents"
] |
server (DNS, Port, and TFTP Service) | server address <logical-system logical-system-name> <routing-instance routing-instance-name>; | [edit forwarding-options helpers domain],
[edit forwarding-options helpers domain interface interface-name],
[edit forwarding-options helpers port port-number],
[edit forwarding-options helpers port port-number interface interface-name],
[edit forwarding-options helpers tftp],
[edit forwarding-options helpers tftp inte... | Specify the DNS or TFTP server for forwarding DNS or TFTP requests, or specify a destination server
address for forwarding LAN broadcast packets as unicast traffic for a custom-configured UDP port.
When configuring port helpers, in releases prior to Junos OS Release 17.2, only one server can be
specified for a given p... | [
{
"name": "address",
"desc": "IP address of the server."
},
{
"name": "logical-system logical-system-name",
"desc": "(Optional) Logical system name of the server."
},
{
"name": "routing-instance [ routing-instance-names ]",
"desc": "(Optional) Set the routing instance name or names t... | 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 for port helpers in Junos OS Release 17.2R1 for EX4300 switches.
Support for multiple server instances for a given port introduced in Junos OS Release 17.2 for MX Series
routers.
Support for multiple server instances for a given port introduced in J... | [
"Configuring DNS and TFTP Packet Forwarding",
"Configuring Port-based LAN Broadcast Packet Forwarding"
] |
server (Dynamic PPPoE) | server; | [edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit pppoe-options] | In a dynamic profile, configure the router to act as a PPPoE server, also known as a remote access
concentrator, when a PPPoE logical interface is dynamically created. | [] | 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. | [
"Configuring a PPPoE Dynamic Profile",
"Subscriber Interfaces and PPPoE Overview"
] |
server (Easy EVPN LAG Configuration) | server name {
apply-config-groups config-groups;
enable-pxe-boot;
esi-lag-id esi-lag-id;
interface [ interface ... ];
mac-vrf-instance instance-id {
vlan-id-list [ vlan-id-list ... ]
};
single-home-id single-home-id;
vlan-id-list [ vlan-id-list ... ]);
}; | [edit services evpn evpn-vxlan] | Specify parameters to generate the configuration statements for servers connected to a provider edge
(PE) device in an Ethernet VPN (EVPN) fabric with Virtual Extensible LAN (VXLAN) encapsulation.
The server might be a customer edge (CE) device or end server connected to the EVPN PE device, and
can be:
•
Single-homed t... | [
{
"name": "(Required)",
"desc": ""
},
{
"name": "name",
"desc": "Specify a name to identify a server connected to the peer PE device. For example, SERVER_1 or hostA."
},
{
"name": "apply-config-groups config-",
"desc": ""
},
{
"name": "groups",
"desc": "Apply the specifie... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.2R1. | [
"Easy EVPN LAG (EZ-LAG) Configuration"
] |
server (HTTP Servers) | server name {
grpc [service1 service2 ... ];
listen-address address;
max-connections max-connections;
port port;
routing-instance routing-instance;
tls {
local-certificate certificate-id;
mutual-authentication {
authentication-type (dont-request-cert | request-and-req... | [edit system services http servers] | Configure gRPC server settings. You can configure multiple servers that host different sets of services on
unique ports. Distributing services across different ports allows for better allocation of network
resources, reducing the risk of port conflicts and optimizing server performance.
You can optionally customize eac... | [
{
"name": "name",
"desc": "User-defined identifier for the server. You can configure a maximum of 5 servers."
},
{
"name": "grpc service",
"desc": "Specify one or more gRPC services hosted by this server. Configure multiple services as a space-separated list enclosed in square brackets. You can ... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1 and Junos OS Evolved Release 25.2R1. | [
"Configure gRPC Services"
] |
server (icap-redirect profile) | server name {
authorization {
authorization-type authorization-type;
credentials (ascii ascii | base64 base64);
}
host host;
port port;
reqmod-uri reqmod-uri;
respmod-uri respmod-uri;
routing-instance ri-name;
sockets sockets;
... | [edit services icap-redirect profile name],
[edit logical-systems logical-system-name services icap-redirect profile name] | Configure the ICAP server details.
When you configure the ICAP redirect service on SRX Series Firewalls, you must configure the ICAP
server details. ICAP server configuration allows you to define the settings required to process request
messages, response messages, authorization, and so on. You can also specify an SSL ... | [
{
"name": "name",
"desc": "ICAP server name."
},
{
"name": "host",
"desc": "ICAP server hostname or IP address."
},
{
"name": "port",
"desc": "ICAP server listening port, default port is reached according to the protocol defined. Default: 1344 Range: 1025 through 65535"
},
{
... | system | Statement introduced in Junos OS Release 18.1R1.
The logical system option is introduced in Junos OS Release 18.3R1. | [
"ICAP Service Redirect"
] |
server (Junos node slicing) | server {
interfaces {
cb0 cb0-interface;
cb1 cb1-interface;
jdm-management jdm-management-interface;
vnf-management gnf-management-interface;
}
} | [edit ] | Applicable only to Junos node slicing set up using external server model.
Configure the server interfaces for the JDM and GNFs. These include a JDM management interface, a
GNF management interface, and two server interfaces that are connected to the MX Series router. | [
{
"name": "cb0 cb0-interface",
"desc": "The server interface that is connected to the control board 0 of the MX Series router."
},
{
"name": "cb1 cb1-interface",
"desc": "The server interface that is connected to the control board 1 of the MX Series router."
},
{
"name": "jdm-management ... | root | Statement introduced in Junos OS Release 17.2R1. | [] |
server (Junos OS Evolved) | server {
light {
offload-type (none | inline-timestamp | pfe-timestamp);
port number;
stateful sequence cache-size number-of-entries;
}
managed {
client-limit limit;
client-list list-name {
address address <routing-instance [instance-name...]>;
}... | [edit services monitoring twamp] | Configure the Two-Way Active Measurement Protocol (TWAMP) server. The server listens in on all
routing instances. | [
{
"name": "client-limit limit",
"desc": "Maximum number of TWAMP clients Range: 0 to 1000 clients"
},
{
"name": "control-inactivity-timeout seconds",
"desc": "Inactivity timeout on control connection Range: 0 to 86400 seconds"
},
{
"name": "control-maximum-duration seconds",
"desc": ... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved 20.3R1.
offload-type and stateful-sequence options introduced in Junos OS Evolved Release 23.4R1. | [
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
server (Junos OS) | server {
authentication-mode none;
client-list list-name {
address address <routing-instance [instance-name...]>;
}
light {
offload-type (none | inline-timestamp | pfe-timestamp);
port number;
}
max-connection-duration hours;
maximum-connections count;
maximum-con... | [edit services rpm twamp] | Defines the Two-Way Active Measurement Protocol (TWAMP) server configurations. This configuration
describes a TWAMP server on the router that enables a TWAMP client to connect to the server using
any media interface IP address. | [] | 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.
light option added in Junos OS Release 21.1R1.
offload-type option added in Junos OS Release 25.4R1. | [
"Configuring TWAMP on MX, M, T, and PTX Series Routers and EX4300 Series Switches"
] |
server (NTP) | server address {
key key;
nts remote-identity {
hostname hostname;
distinguished-name(container container | wildcard wildcard);
}
prefer;
routing-instance routing-instance;
version version;
} | [edit system ntp] | For NTP, configure the local router or switch to operate in client mode with the remote system at the
specified address. In this mode, the local router or switch can be synchronized with the remote system,
but the remote system can never be synchronized with the local router or switch.
If the NTP client time drifts so ... | [
{
"name": "address",
"desc": "Address of the remote system. You must specify an address, not a hostname."
},
{
"name": "key key-number",
"desc": "(Optional) Use the specified key number to encrypt authentication fields in all packets sent to the specified address. Range: Any unsigned 32-bit int... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the NTP Time Server and Time Services"
] |
server (pcp) | server server-name {
ipv4-address ipv4-address;
ipv6-address ipv6-address;
long-lifetime-error long-lifetime-error;
mapping-lifetime-max mapping-lifetime-max;
mapping-lifetime-min mapping-lifetime-min;
max-mappings-per-client max-mappings-per-client;
nat-options {
pool pool... | [edit services pcp] | Configure PCP server options. PCP enables hosts to operate servers for a long time (as in the case of a
webcam) or a short time (for example, while playing a game or on a phone call) when behind a NAT
device, including when behind a carrier-grade NAT operated by their ISP. PCP enables applications to
create mappings fr... | [
{
"name": "ipv4-address",
"desc": "IPv4 address of the PCP server."
},
{
"name": "ipv6-address",
"desc": "IPv6 address of the PCP server."
},
{
"name": "long-lifetime-error",
"desc": "Time limit for generating long lifetime errors. Default: 1800 seconds Range: 900 through 18,000 se... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R1. | [
"Configuring Port Control Protocol"
] |
server (RADIUS Accounting) | server {
server-address {
accounting-port port-number;
accounting-retry number;
accounting-timeout seconds;
dynamic-request-port number;
max-outstanding-requests value;
port number;
preauthentication-port number;
preauthentication-secret secret;
... | [edit system accounting destination radius] | Configure RADIUS accounting.
To configure multiple RADIUS accounting servers, include multiple server server-address statements. The
servers are tried in order and in a round-robin fashion until a valid response is received from one of the
servers or until all the configured retry limits are reached.
NOTE: The [edit sy... | [
{
"name": "server-address",
"desc": "Specify the IPv4 or IPv6 address of the RADIUS authentication server."
},
{
"name": "accounting-port port-number",
"desc": "Configure the accounting port number on which to contact the RADIUS server. Range: 1 through 65,335 Default: 1813"
},
{
"name... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4.
routing-instance introduced in Junos OS Release 18.1R1. | [
"Configuring RADIUS System Accounting",
"Management Interface in a Non-Default Instance",
"Configuring RADIUS Server Authentication",
"Configuring RADIUS Authentication (QFX Series or OCX Series)"
] |
server (RADIUS Network Elements) | server name {
priority priority;
} | [edit access radius network-element name] | Configure a RADIUS server for the network element, which is a load-balanced group of RADIUS servers
providing policy management for TDF subscribers. The RADIUS server must already be defined at the
[edit access radius] hierarchy level. You can configure multiple RADIUS servers under a network element. | [
{
"name": "name",
"desc": "Name of the RADIUS server. The remaining statement is described separately."
}
] | 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 Network Elements",
"Understanding Network Elements",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules",
"Configuring RADIUS Servers"
] |
server (Security Antivirus) | server address-or-url; | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine pattern-update proxy]
[edit security utm feature-profile anti-virus kaspersky-lab-engine pattern-update proxy]
[edit security utm feature-profile anti-virus sophos-engine pattern-update proxy] | Set the IP address or URL for the proxy server. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 11.2.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
server (Security Group VPN) | server {
group name {
anti-replay-time-window milliseconds;
description description;
group-id number;
ike-gateway [gateway-name];
ipsec-sa name {
match-policy policy-name {
destination ip-address/netmask;
destination-port number;
... | [edit security group-vpn] | 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": "gateway gateway-name",
"desc": "Configure IKE gateway for group VPN server."
},
{
"name": "ike",
"desc": "Configure Phase 1 security association (SA) with a member on the group server."
},
{
"name": "ipsec",
"desc": "Configure an IPsec proposal for Phase 2 exchange on the ... | 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. | [
"Group VPNv2 Overview"
] |
server (Security Sophos Engine Antivirus) | server {
host host;
port port;
routing-instance routing-instance;
source-address source-address;
ssl-profile ssl-profile;
proxy-profile proxy-profile;
} | [edit security utm feature-profile anti-virus sophos-engine],
[edit logical-systems name security utm feature-profile anti-virus sophos-engine],
[edit logical-systems name tenants name security utm feature-profile anti-virus sophos-engine],
[edit tenants name security utm feature-profile anti-virus sophos-engine] | Enable you to configure the server parameters for the device-to-server communication.
Starting in Junos OS Release 23.1R1, The Content Security supports the new antivirus Sophos Live
Protection version 2.0. The new version of Sophos antivirus uses an HTTPS connection for the device-
to-server communication. For the HTT... | [
{
"name": "host",
"desc": "Specify the server host IP address or string host name. Default: 4.sophosxl.net"
},
{
"name": "port",
"desc": "Specify the server port number. Range: 1 through 65535 Default: 443"
},
{
"name": "proxy-profile",
"desc": "Specify the proxy profile name."
... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D90.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
The host, port, and ssl-profile options introduced in Junos OS Release 23.1R1.
The ip option is deprecated in Junos OS Release 23.1R1.
The proxy-profile option in... | [] |
server (Security Web Filtering) | server {
host host-name;
port number;
} | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering surf-control-integrated]
[edit security utm feature-profile web-filtering websense-redirect profile profile-name]
[edit security utm feature-profile web-filtering juniper-enhanced] | 15.1X49-D10
The surf-control 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 surf-control feature is not supported from Junos OS Release 15.1X49-D10 onwards. For previous
releases, statement introduced in Junos OS Release 9.5 .
Statement introduced in Junos OS Release 11.4 .
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Change Histor... | [] |
server (syslog) | server {
routing-instances (routing-instance-name | all | default) {
disable;
}
} | [edit system syslog] | Enable a syslog server for a routing instance on a Junos device. This configuration allows compute nodes
and virtual machines (VMs) in a connected App Engine to send log messages to it. Log messages from all
compute nodes and VMs in the App Engine infrastructure are collected in one place. Note that you can
enable a sy... | [
{
"name": "routing-instances",
"desc": "Enable/disable syslog server on the routing instances."
},
{
"name": "routing-instance-name",
"desc": "Specify the name of the routing instance that the syslog client uses to send syslog messages to the syslog server."
},
{
"name": "all",
"desc... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [] |
server (TACACS+ Accounting) | server {
server-address {
port port-number;
routing-instance routing-instance;
secret password;
single-connection;
source-address address
timeout seconds;
}
} | [edit system accounting destination tacplus] | Configure TACACS+ logging. | [
{
"name": "server-address",
"desc": "Address of the IPv4 or IPv6 TACACS+ authentication server. NOTE: Wildcard characters cannot be used in the TACACS+ server address or source address. This is because the TACACS+ server and source can accept both IPv4 and IPv6 addresses and, if you use wildcard characters ... | 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.
routing-instance option introduced in Junos OS Release 17.4R1. | [
"Configuring TACACS+ System Accounting",
"Configuring TACACS+ Authentication",
"Management Interface in a Non-Default Instance"
] |
server | server; | [edit interfaces pp0 unit logical-unit-number pppoe-options],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number pppoe-options] | Configure the router to operate in the PPPoE server mode. Supported on M120 and M320 Multiservice
Edge Routers and MX Series 5G Universal Routing Platforms operating as access concentrators. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring the PPPoE Server Mode"
] |
server-address (dhcp-client) | server address ip-address; | [edit interfaces interface-name unit logical-unit-number family family dhcp-client] | Specify the preferred DHCP server address that is sent to DHCP clients. | [
{
"name": "ip-address",
"desc": "DHCP server address."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10.
Starting with Junos OS Release 17.3R1, on all SRX Series Firewalls and vSRX Virtual Firewall instances,
the CLI option dhcp-clinet at [edit interfaces interface-name unit logical-unit-number family inet] hierarchy is
changed to dhcp to keep consistent with other Jun... | [] |
server-address (Hosted Services) | server-address ipv4-address; | [edit services hosted-services server-profile server-profile-name] | Configure the server address where sampled packets are sent. | [
{
"name": "ipv4-address",
"desc": "IPv4 address of the server."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Configuring Active Flow Monitoring on PTX Series Packet Transport Routers"
] |
server-address | server-address ip-address; | [edit interfaces interface-name unit logical-unit-number family inet dhcp] | Specify the address of the DHCP server that the client should accept DHCP offers from. If this option is
included in the DHCP configuration, the client accepts offers only from this server and ignores all other
offers.
Default
The client accepts the first offer it receives from any DHCP server. | [
{
"name": "ip-address",
"desc": "DHCP server address."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring a DHCP Client",
"unit",
"family"
] |
server-certificate (REST API) | server-certificate local-certificate-identifier; | [edit system services rest https] | Set the server certificate when configuring SSL/TLS mutual authentication. | [
{
"name": "local-certificate-identifier",
"desc": "The server certificate. This must be set when configuring SSL/TLS mutual authentication."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
server-certificate (Services) | server-certificate server-certificate; | [edit services ssl proxy profile profile-name]
[edit services ssl termination profile profile-name]
[edit services ssl initiation profile profile-name] | Specify the local certificate identifier. | [
{
"name": "server-certificate",
"desc": "Specify the name of the local certificate identifier."
}
] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. This statement is supported. | [] |
server-certificate-subject | server-certificate-subject subject; | [edit services unified-access-control infranet-controller hostname] | Optionally specify the full subject name of the certificate that the SRX Series Firewall should use to
validate the IC Series device’s server certificate.
Use this statement when you are configuring the SRX Series Firewall to act as a Junos OS Enforcer in a
Unified Access Control (UAC) deployment. When deployed as a Ju... | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [] |
server-cluster (Security Group VPN Server) | server-cluster {
ike-gateway gateway-name;
retransmission-period seconds;
server-role (root-server | sub-server);
} | [edit security group-vpn server group name] | Configure the Group Domain of Interpretation (GDOI) group controller/key server (GCKS) cluster for the
specified group. All servers in a group VPN server cluster must be SRX Series Firewalls. | [
{
"name": "ike-gateway",
"desc": ""
},
{
"name": "gateway-name",
"desc": "(Required) Specify the name of the IKE gateway for the local device in the group server cluster. IKE gateways are configured at the [edit security group-vpn server ike] hierarchy level. If the local device is a root-server... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D30. | [
"Group VPNv2 Overview",
"Understanding Group VPNv2 Server Clusters"
] |
server-connectivity | server-connectivity (block | log-and-permit); | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering surf-control-integrated profile profile-name
fallback-settings]
[edit security utm feature-profile web-filtering websense-redirect profile profile-name fallback-
settings]
[edit security utm feature-profile web-filtering junipe... | 15.1X49-D10
The surf-control feature is not supported from Junos OS Release 15.1X49-D10 onwards. | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The surf-control feature is not supported from Junos OS Release 15.1X49-D10 onwards. For previous
releases, statement introduced in Junos OS Release 9.5 .
Statement introduced in Junos OS Release 11.4 .
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Change Histor... | [] |
server-duid-type (DHCP Local Server) | server-duid-type type; | [edit system services dhcp-local-server dhcpv6] | Configure the DHCP Unique Identifier (DUID) type that the DHCPv6 server supports. The server uses
the DUID to identify clients for configuration and to group clients into identity associations.
Use this statement to explicitly configure the DUID-LL type. DUID-LL uses a link-layer network
interface address on the device... | [
{
"name": "type",
"desc": "DUID type to support. The only available option is duid-ll."
}
] | 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. | [
"DHCPv6 Local Server Overview"
] |
server-group | server-group {
server-group-name {
server-ip-address;
}
} | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit logical-systems logical-system-name forwarding-options dhcp-relay],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6],
[edit logical-systems logical-system-name routing-instances routing-instance-name ... | Specify the name of a group of DHCP server addresses for use by the extended DHCP relay agent.
Apply the group with the active-server-group statement globally for all interfaces or for a named group of
interfaces configured with the group statement. This mechanism enables you to apply different DHCP
relay configuration... | [
{
"name": "server-group-",
"desc": ""
},
{
"name": "name",
"desc": "Name of the group of DHCP or DHCPv6 server addresses."
},
{
"name": "server-ip-address",
"desc": "IP address of the DHCP server belonging to this named server group. Use IPv6 addresses when configuring DHCPv6 support... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4. | [
"Extended DHCP Relay Agent Overview",
"Configuring Active Server Groups to Apply a Common DHCP Relay Agent Configuration to Named",
"Server Groups"
] |
server-id-override | server-id-override; | [edit forwarding-options dhcp-relay relay-option-82],
[edit forwarding-options dhcp-relay group group-name relay-option-82],
[edit logical-systems logical-system-name forwarding-options dhcp-relay relay-option-82],
[edit logical-systems logical-system-name forwarding-options dhcp-relay group group-name relay-
option-82... | Add the suboptions link-selection and server-id override to option-82 information for DHCP packets
relayed to the server.
In network configurations where a firewall on the broadband network gateway (BNG) is between the
DHCPv4 relay agent and the DHCP server, only the BNG loopback address passes through the BNG
firewal... | [] | 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. | [
"Configuring the DHCP Relay Agent Source Address to Enable DHCP Packets to Pass Through a",
"Firewall"
] |
server-identifier | server-identifier address; | [edit system services dhcp],
[edit system services dhcp pool],
[edit system services dhcp static-binding] | Configure a server identifier. The identifier can be used to identify a DHCP server in a DHCP message. It
can also be used as a destination address from clients to servers (for example, when the boot file is set,
but not the boot server).
Servers include the server identifier in DHCPOFFER messages so that clients can d... | [
{
"name": "address",
"desc": "IPv4 address of the server. This address must be accessible by all clients served within a"
}
] | 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. | [] |
server-inactivity-timeout | server-inactivity-timeout minutes; | [edit services rpm twamp server] | The maximum time the Two-Way Active Measurement Protocol (TWAMP) server has to finish the
TWAMP control protocol negotiation. | [
{
"name": "minutes",
"desc": "Number of minutes the TWAMP server has to finish the TWAMP control protocol negotiation. Configure 0 to disable. Default: 15 minutes Range: 1 through 30 minutes"
}
] | 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. | [
"Configuring TWAMP on MX, M, T, and PTX Series Routers and EX4300 Series Switches"
] |
server-member-communication (Security Group VPN Server) | server-member-communication {
certificate certificate-id;
communication-type (unicast);
encryption-algorithm (aes-128-cbc | aes-192-cbc | aes-256-cbc);
lifetime-seconds seconds;
number-of-retransmission number;
retransmission-period seconds;
sig-hash-algorithm (sha-256 | sha-384);
} | [edit security group-vpn server group name] | Enable and configure server to member communication. When these options are configured, group
members receive new keys before current keys expire. Starting with Junos OS Release 15.1X49-D80,
the minimum value that you can configure for the lifetime-seconds option is 300 seconds instead of 180
seconds. | [
{
"name": "certificate certificate-id",
"desc": "Specify the certificate identification. Only RSA keys are supported."
},
{
"name": "communication-type",
"desc": "Configure unicast (the default)."
},
{
"name": "encryption-algorithm",
"desc": "Encryption used for communications betwee... | 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 | [
"Group VPNv2 Overview"
] |
server-profile (Active Flow Monitoring) | server-profile server-profile-name; | [edit forwarding-options port-mirroring instance instance-name family (inet | inet6 | mpls)
output] | Specify the name of a server profile. This profile specifies a host where sampled traffic is sent. | [
{
"name": "server-profile-name",
"desc": "Specify the name of a server profile configured at the [edit services hosted-services server-profile server-profile-name] hierarchy level."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"Configuring Active Flow Monitoring on PTX Series Packet Transport Routers"
] | |
server-profile | server-profile server-profile-name {
client-address ipv4-address;
server-address ipv4-address;
} | [edit services hosted-services] | Configure the server profile. | [
{
"name": "server-profile-name",
"desc": "Name to apply to this server profile."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Configuring Active Flow Monitoring on PTX Series Packet Transport Routers"
] |
server-reject-bridge-domain | server-reject-vlan | (server-reject-bridge-domain bridge-domain | server-reject-vlan (vlan-id | vlan-name)) {
block-interval block-interval;
eapol-block;
gbp-tag gbp-tag
} | [edit logical-systems name protocols dot1x authenticator interface (all | [interface-names])],
[edit protocols dot1x authenticator interface (all | [interface-names])] | For a device configured for 802.1X authentication, specify that when the device receives an Extensible
Authentication Protocol Over LAN (EAPoL) Access-Reject message during the authentication process
between the device and the RADIUS authentication server, supplicants attempting to access the LAN
are granted access and... | [
{
"name": "server-reject-bridge-domain",
"desc": ""
},
{
"name": "bridge-domain",
"desc": "(MX Series only) Move the supplicant on the interface to the bridge domain specified by this name or numeric identifier."
},
{
"name": "server-reject-vlan (vlan-id |",
"desc": ""
},
{
"... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | gbp-tag gbp-tag introduced in Junos OS Release 23.4R1 for EX and QFX Series switches.
server-reject-vlan introduced in Junos OS Release 9.3 for EX Series.
block-interval introduced in Junos OS Release 11.2 for EX Series.
server-reject-vlan introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers in
enhan... | [
"Example: Connecting a RADIUS Server for 802.1X to an EX Series Switch",
"Example: Configuring Fallback Options on EX Series Switches for EAP-TTLS Authentication and",
"Odyssey Access Clients",
"Configuring RADIUS Server Fail Fallback (CLI Procedure)",
"Understanding Server Fail Fallback and Authentication ... |
server-response-time (DHCP Relay Agent) | server-response-time seconds; | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit logical-systems logical-system-name forwarding-options dhcp-relay ...],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options dhcp-relay ...],
[edit routing-instances routing-instance... | Configure the timeframe during which the router monitors DHCP server responsiveness within the
routing instance. The router generates a system log message when the DHCP server does not respond
to relayed packets during the specified timeframe. | [
{
"name": "seconds",
"desc": "Number of seconds the DHCP server is monitored. Range: 30 through 4,294,967,295 seconds Default: 0 (no limit)"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Monitoring DHCP Relay Server Responsiveness"
] |
servers (RADIUS) | servers name {
accounting-port port-number;
accounting-secret password;
address server-address;
allow-dynamic-requests;
dead-criteria-retries retry-number interval seconds;
dynamic-requests-secret password;
port port-number;
retry attempts;
revert-interval seconds;
secret passwor... | [edit access radius] | Configure a RADIUS server that provides policy management for TDF subscribers. | [
{
"name": "name",
"desc": "Name of the RADIUS server. Range: 1 through 32 characters"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring RADIUS Servers",
"Understanding Network Elements",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules"
] |
servers (System Services) | servers {
server name {
grpc [service1 service2 ... ];
listen-address address;
max-connections max-connections;
port port;
routing-instance routing-instance;
tls {
local-certificate certificate-id;
mutual-authentication {
authen... | [edit system services http] | Configure servers that serve a custom set of services at the specified IP address and port.
NOTE: The gRPC server configurations at the [edit system services http servers] hierarchy
level and the [edit system services extension-service request-response grpc] hierarchy level are
mutually exclusive.
The remaining stateme... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1 and Junos OS Evolved Release 25.2R1. | [] |
servers | servers server-address {
port port-number;
} | [edit system services service-deployment] | Configure an IPv4 address for the Session and Resource Control (SRC) server. | [
{
"name": "server-address",
"desc": "The TCP port number."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Junos OS to Work with SRC Software"
] |
service (Dynamic Profiles) | service {
pcef pcef-profile-name {
activate rule-name | activate-all;
}
} | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number] | Assign a policy and charging enforcement function (PCEF profile) to the dynamic profile. The PCEF
profile specifies a set of PCC rules and rulebases to assign to a subscriber for application-aware policy
control, and assigns a precedence value to each predefined rule. Also specify which of the PCC rules to
activate for... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2. | [
"Configuring Application-Aware Policy Control for Subscriber Management"
] |
service (Dynamic Service Sets) | service {
input {
service-set service-set-name {
service-filter filter-name;
}
post-service-filter filter-name;
}
output {
service-set service-set-name {
service-filter filter-name;
}
}
} | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family],
[edit dynamic-profiles profile-name interfaces pp0 unit $junos–interface–unit family family] | Define the service sets and filters to be applied to an interface. This statement is not supported for
family inet6.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Support at the [edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit” family family]
hierarchy level introduced in Junos OS Release 10.1. | [
"Dynamic Service Sets Overview",
"Associating Service Sets with Interfaces in a Dynamic Profile",
"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 S... |
service (PPPoE) | 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 {
drop;
delay seconds;
terminate;
... | [edit protocols pppoe service-name-tables table-name] | Specify the action taken by the interface on receipt of a PPPoE Active Discovery Initiation (PADI) control
packet for the specified named service, empty service, or any service in a PPPoE service name table. You
can also specify the dynamic profile and routing instance that the router uses to instantiate a dynamic
PPPo... | [
{
"name": "service-name",
"desc": "Service entry in the PPPoE service name table:"
},
{
"name": "service-name",
"desc": "Named service entry of up to 32 characters; for example, premiumService. You can"
},
{
"name": "empty",
"desc": "Service entry of zero length that represents an un... | 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.
any, dynamic-profile, routing-instance, max-sessions, and static-interface options introduced in Junos OS
Release 10.2. | [
"Configuring PPPoE Service Name Tables",
"Assigning a Service to a Service Name Table and Configuring the Action Taken When the Client",
"Request Includes a Non-zero Service Name Tag",
"Configuring the Action Taken When the Client Request Includes an Empty Service Name Tag",
"Configuring the Action Taken fo... |
service (Security IDP Anomaly Attack) | service service-name; | [edit security idp custom-attack attack-name attack-type anomaly] | Service is the protocol whose anomaly is defined in the attack. IP, TCP, UDP, and ICMP are also valid as
services. (Protocol names must be entered in lowercase.) | [
{
"name": "service-name",
"desc": "Name of the protocol in lowercase."
}
] | 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. | [] |
service (Security IDP Dynamic Attack Group) | service {
values [service-value];
} | [edit security idp dynamic-attack-group dynamic-attack-group-name filters] | Specify a service filter to add attack objects based on the attack service, such as FTP, HTTP, NetBios,
and so on. | [
{
"name": "values",
"desc": "Name of the service filter. You can configure multiple filters separated by spaces and enclosed in"
}
] | 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. | [] |
service (Service Accounting) | service {
accounting-order (activation-protocol | local | radius);
accounting {
statistics (time | volume-time);
update-interval minutes;
}
} | [edit access profile profile-name] | Define the subscriber service accounting configuration.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
accounting, update-interval, and statistics options added in Junos OS Release 14.2R1 for MX Series
routers. | [
"Configuring Service Accounting with JSRC",
"Service Accounting with JSRC",
"Configuring Service Accounting in Local Flat Files",
"Configuring Service Accounting",
"Configuring Per-Subscriber Session Accounting"
] |
service | service {
input {
[ service-set service-set-name <service-filter filter-name> ];
post-service-filter filter-name;
}
output {
[ service-set service-set-name <service-filter filter-name> ];
}
} | [edit interfaces interface-name unit logical-unit-number family inet],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet] | Define the service sets and filters to be applied to an 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. | [
"Applying Filters and Services to Interfaces"
] |
service-agents (Analytics) | service-agents {
agent-name {
inputs {
analytics {
parameters {
generate-tags value;
sample-frequency value;
sensors file-path;
}
}
input-ipfix {
parameters {
... | [edit services analytics agent] | Configure a network analytics service agent that uses input and output plug-ins to collect, transform,
and forward network telemetry data.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | system | Statement introduced in Junos OS Release 18.3R1. | [
"Configuring the BNG as an IPFIX Mediator to Collect and Export IPFIX Data",
"Configuring the Collection and Export of Local Telemetry Data on the IPFIX Mediator",
"Configuring NTF Agent",
"IPFIX Mediation on the BNG",
"Telemetry Data Collection on the IPFIX Mediator for Export to an IPFIX Collector"
] |
service-context-id (OCS) | service-context-id service-context ; | [edit access ocs global] | Configure the service-context-id to globally and uniquely identify the Service-Context-Id AVP (cc-
service-context) and the Service-Identifier AVP (cc-service-identifier), which is part of the Diameter
Credit Control Service charging system. The service provider or operator allocates this identifier. | [
{
"name": "service-context",
"desc": "3rd Generation Partnership Project (3GPP)-specific values."
},
{
"name": "service-context",
"desc": "32251"
},
{
"name": "customer-domain",
"desc": "3gpp.org"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring OCS Global Parameters",
"3GPP Policy and Charging Control Overview for Wireline Provisioning and Accounting",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interactions Betwe... |
service-deployment | service-deployment {
servers server-address {
port port-number;
}
source-address source-address;
} | [edit system services] | Enable Junos OS to work with the Session and Resource Control (SRC) software.
The remaining statements are explained separately. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Junos OS to Work with SRC Software"
] |
service-device (Remote Device Management) | service-device device-name {
access-domain {
vlan-id-list [vlan-id-low-vlan-id-high vlan-id]
}
address ip-address;
dictionary absolute file path;
provisioning-method {
netconf {
bulk-interval milliseconds;
bulk-limit number;
connection-retry-interv... | [edit routing-instances routing-instance-name system services remote-device-management],
[edit system services remote-device-management] | Configure a remote device to provision and deprovision services for subscribers. This configuration is
used when profile-type remote-device-service has been configured in the dynamic service profile.
Provides basic configuration for the remote service device and enables NETCONF TCP session to be
established with the se... | [
{
"name": "address ip-address",
"desc": "Specify the IP address of the remote device used by the BNG to configure the subscriber service. The address must be unique; it is used for all actions performed by the BNG, including service provisioning and deprovisioning. The address must also be unique across all... | system—To view this statement in the configuration. | Statement introduced in Junos OS Release 18.3R1. | [
"Configuring Remote Device Management for Service Provisioning",
"Remote Device Services Manager (RDSM) Overview"
] |
service-device-pool (L2TP) | service-device-pool pool-name; | [edit services l2tp tunnel-group name] | Assign a pool of service interfaces to the tunnel group to balance traffic across.
NOTE: The service interface configuration is required for static LNS sessions. Either the
service interface configuration or the service device pool configuration can be used for
dynamic LNS sessions. | [
{
"name": "pool-name",
"desc": "Name of the service device pool."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Configuring an L2TP Tunnel Group for LNS Sessions with Inline Services Interfaces"
] |
service-device-pools (Service Interfaces) | service-device-pools {
pool pool-name {
interface service-interface-name;
}
} | [edit services] | Configure one or more pools of service interfaces that can be assigned to an L2TP tunnel group for
traffic load-balancing. The interfaces in the pool must be inline service interfaces (si). The service device
pool is required for dynamic LNS sessions. | [
{
"name": "pool-name",
"desc": "Name of the service interface pool. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
Support for ps service interfaces added in Junos OS Release 19.3R1. | [
"L2TP LNS Inline Service Interfaces"
] |
service-domain | service-domain (inside | outside); | [edit interfaces interface-name unit logical-unit-number family inet],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet] | Specify the service interface domain. If you specify this interface using the next-hop-service statement at
the [edit services service-set service-set-name] hierarchy level, the interface domain must match that
specified with the inside-service-interface and outside-service-interface statements. | [
{
"name": "inside",
"desc": "Interface used within the network."
},
{
"name": "outside",
"desc": "Interface used outside the network."
}
] | 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 the Address and Domain for Services Interfaces"
] |
service-filter (Dynamic Service Sets) | service-filter filter-name; | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family service input service-set service-set-name],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family service output service-set service-set-name],
[edit dynamic-profiles pr... | Define the filter to be applied to traffic before it is accepted for service processing. You can use the
predefined dynamic interface variables $junos-input-service-filter, $junos-output-service-filter, $junos-input-
ipv6-service-filter, and $junos-output-ipv6-service-filter. Configuration of a service filter is option... | [
{
"name": "filter-name",
"desc": "Identifies the filter to be applied in service processing."
}
] | 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 service-set service-set-name] and [edit dynamic-profiles profile-name interfaces pp0 unit “$junos-
interface-unit” family family service output service... | [
"Dynamic Service Sets Overview",
"Associating Service Sets with Interfaces in a Dynamic Profile",
"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 S... |
service-filter (Firewall) | service-filter filter-name {
term term-name {
from {
match-conditions;
}
then {
actions;
}
}
} | [edit firewall family (inet | inet6)],
[edit logical-systems logical-system-name firewall family (inet | inet6)] | Configure service filters.
NOTE: ACX Series routers do not support family inet6. | [
{
"name": "filter-name",
"desc": "Name that identifies the service filter. The name can contain letters, numbers, and hyphens"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Logical systems support introduced in Junos OS Release 9.3. | [
"Guidelines for Configuring Service Filters",
"Guidelines for Applying Service Filters"
] |
service-filter (Interfaces) | service-filter filter-name; | [edit interfaces interface-name unit logical-unit-number family inet service (input | output)
service-set service-set-name],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet service (input | output) service-set service-set-name] | Define the filter to be applied to traffic before it is accepted for service processing. Configuration of a
service filter is optional; if you include the service-set statement without a service-filter definition, Junos
OS assumes the match condition is true and selects the service set for processing automatically. | [
{
"name": "filter-name",
"desc": "Identifies the filter to be applied in service processing. You can include special characters,"
}
] | 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 Filters and Services to Interfaces",
"Junos OS Services Interfaces Library for Routing Devices"
] |
service-groups | service-groups {
service-group-name {
pbb-service-options {
default-isid isid-number;
isid isid-number vlan-id-list [ vlan-ids ];
mac-address mac-address;
}
service-type (elan | eline);
source-bmac <mac-address> <length>
}
} | [edit routing-instances routing-instance-name] | For IEEE 802.1ah provider backbone bridge (PBB) configurations, configure the service groups to be
supported in the customer routing instance (I-component).
NOTE: The mac-address statement under pbb-service-options is not supported for PBB-
EVPN.
NOTE: The eline option for the service-type statement is not supported fo... | [
{
"name": "service-group-name",
"desc": "Name of a service group."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in JUNOS Release 10.0. | [] |
service-id (Bridge Domains) | service-id number; | [edit bridge-domains bridge-domain-name] | Specify a service identifier to include in the packets sent to and from the multichassis link aggregation
(MC-LAG) bridge domain when the VLAN identifier is set to none. This configuration facilitates media
access control (MAC) and Address Resolution Protocol (ARP) synchronization among MC-LAG peers.
NOTE: The VLAN id... | [
{
"name": "number",
"desc": "A valid service identifier. You must configure the same service identifier within the bridge"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2 | [
"Configuring a Bridge Domain",
"Configuring VLAN Identifiers for Bridge Domains and VPLS Routing Instances",
"Understanding Layer 2 Learning and Forwarding for Bridge Domains",
"bridge-domains"
] |
service-id (Switch Options) | service-id number; | [edit switch-options]
[edit vlans vlan-name] | Specify a service identifier for each multichassis aggregated Ethernet interface that belongs to a link
aggregation group (LAG). | [
{
"name": "number",
"desc": "A number that identifies a particular service. Range: 1 through 65535"
}
] | system—To view this statement in the configuration.
system control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3R2. | [] |
service-interface (L2TP Processing) | service-interface interface-name; | [edit services l2tp tunnel-group name] | Specify the service interface responsible for handling L2TP processing.
NOTE: On MX Series routers, the service interface configuration is required for static
LNS sessions. Either the service interface configuration or the service device pool
configuration can be used for dynamic LNS sessions. | [
{
"name": "interface-name",
"desc": "Name of the service interface. The ae, si, and sp interface types are supported as follows:"
},
{
"name": "asix",
"desc": "(MPCs on MX Series routers) Aggregated inline services interface."
},
{
"name": "sp-fpc/pic/port",
"desc": "On AS or Multise... | 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.
si-fpc/pic/port option added in Junos OS Release 11.4.
Option asifpc added in Junos OS Release 16.2. | [
"Configuring the Local Gateway Address and PIC",
"Configuring an L2TP Tunnel Group for LNS Sessions with Inline Services Interfaces"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.