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 |
|---|---|---|---|---|---|---|---|
standby (Routing Policy Condition) | standby; | [edit logical-systems logical-system-name policy-options condition if-route-exists address-family
ccc],
[edit policy-options condition if-route-exists address-family ccc] | Specify that the route must be in standby state to be considered a match. | [] | 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. | [
"Example: Configuring Pseudowire Redundancy in a Mobile Backhaul Scenario"
] |
standby | standby; | [edit logical-systems logical-system-name protocols mpls],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
secondary) path-name],
[edit protocols mpls],
[edit protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name (primary | secondary) pa... | Have the path remain up at all times to provide instant switchover if connectivity problems occur. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Hot Standby of Secondary Paths for LSPs"
] |
standby-path-creation-delay | standby-path-creation-delay <seconds>; | [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim] | Configure the time interval after which a standby path is created, when a new ECMP interface or
neighbor is added to the network.
In the absence of this statement, ECMP joins are redistributed as soon as a new ECMP interface or
neighbor is added to the network. | [
{
"name": "<seconds>",
"desc": "Time interval after which a standby path is created, when a new ECMP interface or neighbor is added to the network. Range is from 1 through 300."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Example: Configuring PIM Make-Before-Break Join Load Balancing",
"Configuring PIM Join Load Balancing"
] |
start (Scripts) | start {
start-options {
mem-factor percentage;
}
} | [edit event-options event-script],
[edit event-options event-script file filename],
[edit system extensions extension-service application],
[edit system extensions extension-service application file filename],
[edit system scripts op],
[edit system scripts op file filename],
[edit system scripts snmp],
[edit system sc... | Configure options to control script execution.
NOTE: Junos devices do not enforce script start options for remote op scripts, which are
executed using the op url command. Script start options are enforced only for local op
scripts.
Default
If you do not configure start options for an individual script or script type, t... | [
{
"name": "mem-factor",
"desc": ""
},
{
"name": "percentage",
"desc": "System memory usage threshold, specified as a percentage, above which a script does not execute. You can configure the statement for op, event, SNMP, and Juniper Extension Toolkit (JET) scripts. You can apply the statement to... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 22.4R1.
Statement introduced in Junos OS Evolved Release 23.1R1. | [
"Configure Script Start Options"
] |
start shell | start shell (csh | sh)
<user username> | Exit from the CLI environment and create a UNIX-level shell. To return to the CLI, type exit from the
shell.
Juniper Networks does not provide support for operations in the shell.
NOTE:
•
To issue this command, the user must have the required login access privileges
configured by including the permissions statement a... | [
{
"name": "csh",
"desc": "Create a UNIX C shell."
},
{
"name": "sh",
"desc": "Create a UNIX Bourne shell."
},
{
"name": "user username",
"desc": "(Optional) Start the shell as another user. Additional Information When you are in the shell, the shell prompt has the following format:"
... | shell or maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
start shell csh
user@host> start shell csh
%
exit
%
username@hostname% start shell sh
%
exit
user@host> | Command introduced before Junos OS Release 7.4. | [] | |
start-date | start-date date-time; | [edit schedulers scheduler scheduler-name] | Specify the time, day, month, and year that the schedule starts.
Specifying the year is optional. If no year is specified, the schedule applies to the current year and all
subsequent years. If the year is specified in either the start-date or stop-date statement, that year is used
for both statements. | [
{
"name": "date-time",
"desc": "Use the format [ yyyy -] mm - dd . hh . mm to specify the year, month, day, hour, and minutes."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Security Policies Overview"
] |
start-log | start-log value; | [edit security idp sensor-configuration log suppression] | Specify how many instances of a specific event must occur before log suppression begins. | [
{
"name": "value",
"desc": "Log suppression begins after how many occurrences."
}
] | 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. | [] |
start-measurement | (no-start-measurement | start-measurement); | [edit interfaces interface-name otn-options odu-delay-management] | Start or do not start a delay measurement (DM) session.
Default
By default, do not start a DM session. | [
{
"name": "no-start-measurement",
"desc": "Do not start a DM session."
},
{
"name": "start-measurement",
"desc": "Start a DM session."
}
] | 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. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
start-time (Accounting) | start-time time; | [edit accounting-options file filename] | Specify the start time for transfer of an accounting-data log file. | [
{
"name": "time",
"desc": "Start time for file transfer."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Configuring Accounting Options, Source Class Usage and Destination Class Usage Options"
] |
start-time (Schedulers) | start-time hh:mm; | [edit schedulers scheduler scheduler-name daily],
[edit schedulers scheduler scheduler-name friday],
[edit schedulers scheduler scheduler-name monday],
[edit schedulers scheduler scheduler-name saturday],
[edit schedulers scheduler scheduler-name sunday],
[edit schedulers scheduler scheduler-name tuesday],
... | Specify the time that a schedule starts for a specified day.
If you specify a starting time for a daily schedule with the daily statement and also include the friday,
monday, saturday, sunday, tuesday, thursday, and wednesday statements in the schedule, the starting time
specified for a specific day (for example, Frida... | [
{
"name": "time",
"desc": "Use the 24-hour format (hh:mm:ss ) to specify the hours, minutes, and seconds."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Security Policies Overview"
] |
start-time (Security IDP) | start-time start-time; | [edit security idp security-package automatic] | Specify the time that the device automatically starts downloading the updated signature database from
the specified URL. | [
{
"name": "start-time",
"desc": "Time in MM-DD.hh:mm format."
}
] | 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. | [] |
start-time | start-time start-time; | [edit security utm default-configuration anti-virus avira-engine pattern-update]
[edit security utm default-configuration anti-virus sophos-engine pattern-update] | Specify the time that the device automatically starts downloading the updated signature database from
the specified URL. | [
{
"name": "start-time",
"desc": "Time in MM-DD.hh:mm format."
}
] | security— To view this statement in the configuration.
security-control— To add this statement to the configuration. | The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Support for Avira engine added in Junos OS Release 18.4R1. | [] |
starts-with (DHCP Relay Agent Option) | equals {
ascii name {
drop drop;
forward-only forward-only;
local-server-group local-server-group;
}
hexadecimal name {
drop drop;
forward-only forward-only;
local-server-group local-server-group;
}
} | [edit bridge-domains name forwarding-options dhcp-relay group name relay-option],
[edit bridge-domains name forwarding-options dhcp-relay group name relay-option option-60],
[edit bridge-domains name forwarding-options dhcp-relay group name relay-option option-77],
[edit bridge-domains name forwarding-options dhcp-rela... | Configure a partial match criteria used with the DHCP relay agent selective processing feature. DHCP
relay agent compares the configured partial match string with the option-specific string received in
DHCP client packets. If there is an partial left-to-right match, DHCP performs the action you define for
the match cri... | [
{
"name": "ascii-string",
"desc": "ASCII string of 1 through 255 alphanumeric characters."
},
{
"name": "hexadecimal-string",
"desc": "Hexadecimal string of 1 through 255 hexadecimal characters (0 through 9, a through f, A through F). The remaining statements are explained separately. Search for... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Statement updated in Junos OS Release 17.4. | [
"DHCP Options and Selective Traffic Processing",
"DHCP Options and Selective Traffic Processing"
] |
starts-with (Event Policy) | event1.attribute-name starts-with event2.attribute-name; | [edit event-options policy policy-name attributes-match] | Configure an event policy to trigger only if the event1 attribute value starts with the value of the event2
attribute. The referenced events must be either the trigger event or the correlating events included in
the event policy’s within statements.
An attributes-match statement can include multiple comparison statemen... | [
{
"name": "event1.attribute-name",
"desc": "Attribute of one event."
},
{
"name": "event2.attribute-name",
"desc": "Attribute of another event."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Use Correlated Events to Trigger an Event Policy"
] |
startup-alarm | startup-alarm (falling-alarm | rising-alarm | rising-or-falling-alarm); | [edit snmp rmon alarm index] | Set an initial alarm that is sent after the configured SNMP RMON alarm becomes active. | [
{
"name": "falling-alarm",
"desc": "Generated if the first sample after the alarm entry becomes active is less than or equal to"
},
{
"name": "rising-alarm",
"desc": "Generated if the first sample after the alarm entry becomes active is greater than or equal"
},
{
"name": "rising-or-fall... | 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. | [
"Remote Nework Monitoring (RMON)"
] |
startup-silent-period | startup-silent-period seconds; | [edit protocols vrrp] | Instruct the system to ignore the Primary Down Event when an interface transitions from the down
state to the up state. This statement is used to avoid incorrect error alarms caused by the delay or
interruption of incoming Virtual Router Redundancy Protocol (VRRP) advertisement packets during the
interface startup phas... | [
{
"name": "seconds",
"desc": "Number of seconds for the startup period."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Startup Period for VRRP Operations"
] |
stateful (Precision Time Protocol) | stateful {
interface interface-name {
multicast-mode {
local-priority
transport 802.3 ( link-local ) ;
asymmetry number;
primary-asymmetry number;
secondary-asymmetry number
}
passive-port-monitor {
measure-only;
... | [edit protocols ptp] | Configure the stateful port or bidirectional port with parameters. A stateful port is useful when you
configure PTP over Ethernet for multicast mode of transmission of PTP traffic. A stateful port
configuration for PTP over Ethernet and default profile is supported only on boundary clock mode and
not on ordinary clock ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1R1. | [
"Precision Time Protocol Overview",
"Guidelines for Configuring PTP over Ethernet",
"Configuring PTP Multicast Primary and Member Ports for Ethernet Encapsulation",
"Configuring PTP Dynamic Ports for Ethernet Encapsulation"
] |
stateful (Router Advertisement Guard) | (stateful | stateless); | [edit forwarding-options access-security router-advertisement-guard interface (interface-name |
interface-range-name)],
[edit forwarding-options access-security router-advertisement-guard vlans vlan-name] | Configure stateful IPv6 Router Advertisement (RA) guard. In an IPv6 deployment, RA guard protects
against rogue RA messages generated either maliciously or unintentionally by unauthorized or
improperly configured routers connecting to the network segment. RA guard performs checks on
incoming RA messages to make sure t... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D55. | [
"Understanding IPv6 Router Advertisement Guard",
"Configuring Stateful IPv6 Router Advertisement Guard"
] |
stateful-firewall-rule-set (Next Gen Services) | stateful-firewall-rule-set {
stateful-firewall-rule [rule-name];
] | [edit services policies] | Specify a set of stateful firewall rules, which are processed in the order in which they appear in the rule
set configuration. Once a stateful firewall rule in the rule set matches a flow, that rule is applied and no
other rules in the rule set are processed˙. | [
{
"name": "stateful-firewall-rule [rule-name]",
"desc": "Names of the stateful firewall rules that belong to the rule set. A stateful firewall rule is configured at the [edit services policies] hierarchy level."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Stateful Firewalls for Next Gen Services"
] |
stateful-firewall-rule-sets (Service Set Next Gen Services) | stateful-firewall-rule-sets [rule-set-name]; | [edit services service-set service-set-name] | Specify the stateful firewall rule sets to be used with the service set. A stateful firewall rule set is
configured at the [edit services policies] hierarchy level. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Stateful Firewalls for Next Gen Services"
] |
stateful-firewall-rules (Service Set Next Gen Services) | stateful-firewall-rules [rule-name]; | [edit services service-set service-set-name] | Specify the stateful firewall rules to be used with the service set. A stateful firewall rule is configured at
the [edit services policies] hierarchy level. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Stateful Firewalls for Next Gen Services"
] |
stateful-firewall-rules | (stateful-firewall-rules rule-names | stateful-firewall-rule-sets rule-set-name); | [edit services service-set service-set-name] | Specify the stateful firewall rules or rule set included in this service set. You can configure multiple rules,
but only one rule set for each service. | [
{
"name": "rule-name",
"desc": "Identifier for the collection of terms that make up this rule."
},
{
"name": "rule-set-name",
"desc": "Identifier for the set of rules to be included."
}
] | 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 Service Rules"
] |
stateful-nat64 | stateful-nat64 {
clear-dont-fragment-bit;
disable-h323-ras;
ipv6-mtu;
} | [edit services service-set service-set-name nat-options] | Set parameters for stateful NAT64 operation.
NOTE: These parameters do not change the operation of other types of NAT. | [
{
"name": "clear-dont-fragment-bit",
"desc": "Clear the DF (don't fragment) bit in a translated IPv4 packet if its packet size is less than 1280 bytes. If the packet is greater than or equal to 1280 bytes, the DF bit is not cleared."
},
{
"name": "disable-h323-ras",
"desc": "Disable the H323 and... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced with Junos OS Release 12.1. | [
"Configuring Service Rules"
] |
stateless | (stateful | stateless); | [edit forwarding-options access-security router-advertisement-guard interface (interface-name |
interface-range-name)],
[edit forwarding-options access-security router-advertisement-guard vlans vlan-name] | Configure stateless IPv6 Router Advertisement (RA) guard. In an IPv6 deployment, RA guard protects
against rogue RA messages generated either maliciously or unintentionally by unauthorized or
improperly configured routers connecting to the network segment. An RA guard policy is used to
validate incoming RA messages on ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D55. | [
"Understanding IPv6 Router Advertisement Guard",
"Configuring Stateful IPv6 Router Advertisement Guard"
] |
static (802.1X) | static mac-address {
bridge-domain-assignment bridge-domain-assignment;
interface [interface-names];
vlan-assignment (vlan-id |vlan-name );
} | [edit protocols dot1x authenticator] | Configure MAC addresses to exclude from 802.1X authentication. The static MAC list provides an
authentication bypass mechanism for supplicants connecting to a port, permitting devices such as
printers that are not 802.1X-enabled to be connected to the network on 802.1X-enabled ports.
Using this 802.1X authentication-b... | [
{
"name": "mac-address",
"desc": "The MAC address of the device for which 802.1X authentication should be bypassed and the device permitted access to the port."
},
{
"name": "bridge-domain-assignment bridge-",
"desc": ""
},
{
"name": "domain-assignment",
"desc": "(MX Series only) Spe... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Example: Configuring Static MAC Bypass of 802.1X and MAC RADIUS Authentication on an EX",
"Series Switch",
"Configuring 802.1X Interface Settings (CLI Procedure)",
"Configuring 802.1X Authentication (J-Web Procedure)",
"Understanding Authentication on Switches"
] |
static (Bridge Domains) | static {
group multicast-group-address {
source ip-address;
}
} | [edit bridge-domains bridge-domain-name protocols igmp-snooping interface interface-name],
[edit bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id interface interface-
name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-
snooping interface interface... | Define static multicast groups on an interface.
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. | [
"Example: Configuring IGMP Snooping"
] |
static (Distributed IGMP) | static {
<distributed>;
group multicast-group-address{
<distributed>;
source source- address<distributed>;
}
} | [edit protocols pim] | Configure static source and group (S, G) addresses when distributed IGMP is enabled. Reduces the first
join delay time and brings multicast traffic to the last-hop router. Specified (S, G) addresses join statically
without waiting for the first join. | [
{
"name": "distributed",
"desc": "(Optional) Enable static joins for specified (S,G) addresses and preprovision all of them so that all distributed IGMP Packet Forwarding Engines receive traffic. The remaining statements are explained separately."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X50. | [
"Enabling Distributed IGMP",
"Junos OS Multicast Protocols User Guide",
"Junos OS Multicast Protocols User Guide"
] |
static (Dynamic IGMP Interface) | static {
group group;
group group {
source source;
}
} | [edit dynamic-profiles profile-name protocols igmp interface interface-name] | Test multicast forwarding on an interface without a receiver host. | [] | routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Dynamic IGMP Configuration Overview",
"Configuring Dynamic DHCP Client Access to a Multicast Network",
"Enabling IGMP Static Group Membership"
] |
static (Dynamic MLD Interface) | static {
group multicast-group-address {
exclude;
group-count number;
group-increment increment;
source ip-address {
source-count number;
source-increment increment;
}
}
} | [edit dynamic-profiles profile-name protocols mld interface interface-name] | Test multicast forwarding on an interface.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Dynamic MLD Configuration Overview",
"Enabling MLD Static Group Membership"
] |
static (IGMP Snooping) | static {
group ip-address;
} | [edit protocols igmp-snooping vlan (all | vlan-name) interface interface-name] | Statically define multicast groups for IGMP snooping on a Layer 2 (L2) interface.
You might use this statement to configure an L2 interface to statically join a particular multicast group in
cases such as the following:
•
In a network that doesn't include Layer 3 (L3) multicast. You can't establish a static IGMP state ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [] |
static (Origin Validation for BGP) | static {
record destination {
maximum-length prefix-length {
origin-autonomous-system as-number {
validation-state (invalid | valid);
}
}
}
} | [edit logical-systems logical-system-name routing-instances instance-name routing-options
validation],
[edit logical-systems logical-system-name routing-options validation],
[edit routing-instances instance-name routing-options validation],
[edit routing-options validation] | Configure a static route validation (RV) record.
RV records are received from the RPKI cache server using the protocol defined in Internet draft draft-
ietf-sidr-rpki-rtr-19, The RPKI/Router Protocol, and can also be configured statically, as shown here.
Static records are useful for overwriting the information receiv... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Use Case and Benefit of Origin Validation for BGP",
"Understanding Origin Validation for BGP",
"Example: Configuring Origin Validation for BGP"
] |
static (Protocols IGMP) | static {
group multicast-group-address {
exclude;
group-count number;
group-increment increment;
source ip-address {
source-count number;
source-increment increment;
}
}
} | [edit logical-systems logical-system-name protocols igmp interface interface-name],
[edit protocols igmp interface interface-name] | Test multicast forwarding on an interface without a receiver host.
The static statement simulates IGMP joins on a routing device statically on an interface without any
IGMP hosts. It is supported for both IGMPv2 and IGMPv3 joins. This statement is especially useful for
testing multicast forwarding on an interface witho... | [] | routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Enabling IGMP Static Group Membership"
] |
static (Protocols Layer 2 Circuit) | static {
incoming-label label;
outgoing-label label;
send-oam;
} | [edit logical-systems logical-system-name l2circuit neighbor address interface interface-name],
[edit logical-systems logical-system-name l2circuit neighbor address interface interface-name
backup-neighbor neighbor],
[edit protocols l2circuit neighbor address interface interface-name],
[edit protocols l2circuit neigh... | Configures static Layer 2 circuit pseudowires. Static pseudowires are designed for networks that do not
support LDP or do not have LDP enabled. You configure a static pseudowire by configuring static values
for the in and out labels needed to enable a pseudowire connection. | [
{
"name": "incoming-label",
"desc": "(Optional for PTX Series Packet Transport Routers only) Configure the Layer 2 circuit incoming static pseudowire label. Range: 1000000 through 1048575"
},
{
"name": "outgoing-label",
"desc": "(Optional for PTX Series Packet Transport Routers only) Configure ... | 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"
] |
static (Protocols MLD) | static {
group multicast-group-address {
exclude;
group-count number;
group-increment increment;
source ip-address {
source-count number;
source-increment increment;
}
}
} | [edit logical-systems logical-system-name protocols mld interface interface-name],
[edit protocols mld interface interface-name] | Test multicast forwarding on an interface.
The static statement simulates MLD joins on a routing device statically on an interface without any MLD
hosts. It is supported for both MLDv1 and MLDv2 joins. This statement is especially useful for testing
multicast forwarding on an interface without a receiver host.
NOTE: T... | [] | routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Enabling MLD Static Group Membership"
] |
static (Protocols PIM) | static {
address address {
group-ranges {
destination-ip-prefix</prefix-length>;
}
override;
version version;
}
} | [edit logical-systems logical-system-name protocols pim rp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp],
[edit protocols pim rp],
[edit routing-instances routing-instance-name protocols pim rp] | Configure static RP addresses. The default static RP address is 224.0.0.0/4. To configure other
addresses, include one or more address statements. You can configure a static RP in a logical system only
if the logical system is not directly connected to a source.
For each static RP address, you can optionally specify th... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Static PIM RP Address on the Non-RP Routing Device"
] |
static (Protocols VPLS) | static {
incoming-label label;
outgoing-label label;
control-word;
no-control-word;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
mesh-group mesh-group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
neighbor address],
[edit logical-systems logical-system-name routing-instances... | Specifies a static pseudowire for a VPLS domain. By configuring static pseudowires for the VPLS
domain, you do not need to configure the LDP or BGP protocols that would normally be used for
signaling. Static pseudowires require that you configure a set of in and out labels for each pseudowire
configured for the VPLS do... | [
{
"name": "incoming-label label",
"desc": "You must configure an incoming label for the static pseudowire."
},
{
"name": "outgoing-label label",
"desc": "You must configure an outgoing label for the static pseudowire."
},
{
"name": "control-word",
"desc": "Set control-word to request... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2.
Options control-word and no-control-word are introduced in Junos OS Release 20.3R1.
NOTE: Options control-word and no-control-word are not introduced at the [edit logical-
systems logical-system-name routing-instances routing-instance-name protocols vpls
neighbor address ... | [
"Configuring Static Pseudowires for VPLS"
] |
static (Routing Options) | static {
defaults {
static-options;
}
rib-group group-name;
route route-name {
(discard | mreceive-internal-use-only | next-hop [ next-hop-address ... ] | next-table next-
table-name | receive | reject);
(active | passive);
as-path {
aggregator {
aggregator-addre... | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit logical-systems logical-system-name routing-options],
[edit logical-systems logical-system-name routing-options rib routing-table-name],
[edit routing-instances routing-instance-name routing-options],
[edit routin... | Configure static routes to be installed in the routing table. You can specify any number of routes within
a single static statement, and you can specify any number of static options in the configuration. | [
{
"name": "defaults",
"desc": "(Optional) Specify global static route options. These options only set default attributes"
},
{
"name": "route",
"desc": "Configure individual static routes. In this part of the static statement, you optionally can"
},
{
"name": "destination-prefix/prefix-l... | 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 BFD authentication introduced in Junos 9.6.
Support for BFD authentication introduced in Junos 9.6 for EX Series switches. | [
"Understand Basic Static Routing",
"Example: Configure IPv4 Static Routing for a Stub Network",
"Example: Configure IPv6 Static Routing for a Stub Network"
] |
static (Security NAT) | static {
rule-set rule-set-name {
description text;
from {
interface [interface-name];
routing-instance [routing-instance-name];
zone [zone-name];
}
rule rule-name {
description text;
match {
(destination-add... | [edit security nat] | Configure static NAT. | [] | 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. The description option added in Junos OS Release 12.1.
Statement modified in Junos OS Release 12.1X45-D10. Statement modified in Junos OS Release
12.3X48-D25. | [] |
static-binding | static-binding mac-address {
client-identifier (ascii client-id | hexadecimal client-id);
fixed-address {
address;
}
host-name client-hostname;
} | [edit system services dhcp] | For J Series Services routers and EX Series switches only. Set static bindings for DHCP clients. A static
binding is a mapping between a fixed IP address and the client’s MAC address or client identifier. | [
{
"name": "mac-address",
"desc": "The MAC address of the client. This is a hardware address that uniquely identifies a client on"
},
{
"name": "fixed-address address",
"desc": "Fixed IP address assigned to the client. Typically a client has one address assigned,"
},
{
"name": "host-name ... | 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. | [] |
static-host-mapping | static-host-mapping {
hostname {
alias [ aliases ];
inet [ addresses ];
inet6 [ addresses];
sysid system-identifier;
}
} | [edit system] | (Optional) Statically map a hostname to one or more IP addresses and aliases, and configure an
International Organization for Standardization (ISO) system identifier (system ID).
Default
If you do not statically map the hostname, the mapping is generated dynamically, based on the system
configuration. For instance, if ... | [
{
"name": "alias alias",
"desc": "Alias for the hostname."
},
{
"name": "hostname",
"desc": "Fully qualified hostname."
},
{
"name": "inet address",
"desc": "IP address. You can specify one or more IP addresses for the host."
},
{
"name": "sysid system-identifier",
"desc"... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 11.1. for the QFX Series. | [
"No Link Title"
] |
static-interface | static-interface interface-name; | [edit protocols pppoe service-name-tables table-name service service-name agent-specifier aci
circuit-id-string ari remote-id-string] | Reserve the specified static PPPoE interface for use only by the PPPoE client with matching agent circuit
identifier (ACI) and agent remote identifier (ARI) information. You can specify only one static interface
per ACI/ARI pair configured for a named service entry, empty service entry, or any service entry in the
PPPo... | [
{
"name": "interface-name",
"desc": "Name of the static PPPoE interface reserved for use by the PPPoE client with matching"
}
] | 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. | [
"Configuring PPPoE Service Name Tables",
"Reserving a Static PPPoE Interface for Exclusive Use by a PPPoE Client"
] |
static-ip (MX Series) | static-ip ip-address mac mac-address; | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security group group-name interface
interface-name] | Configure a static IP address to MAC address (IP-MAC) binding record to be added to the DHCP
snooping database. | [
{
"name": "ip-address",
"desc": "Static IP address assigned to a device connected on the specified interface."
},
{
"name": "mac-address",
"desc": "Static MAC address assigned to a device connected on the specified interface."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Configuring Static DHCP IP Addresses for DHCP snooping (MX routers)"
] |
static-ip | static-ip ip-addresses {
vlan vlan-name;
mac mac-address;
} | For platforms with ELS:
[edit vlans vlan-name forwarding-options dhcp-security group group-name interface interface-name]
For platforms without ELS:
[edit ethernet-switching-options secure-access-port interface (all | interface-name)] | Configure a static IP address to MAC address (IP-MAC) binding to be added to the DHCP snooping
database.
NOTE: The VLAN is specified at the higher hierarchy level when static-ip is configured at
[edit vlans vlan-name forwarding-options dhcp-security group group-name interface interface-
name]. | [
{
"name": "ip-address",
"desc": "Static IP address assigned to a device connected on the specified interface."
},
{
"name": "macmac-address",
"desc": "Static MAC address assigned to a device connected on the specified interface."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Hierarchy level [edit vlans vlan-name forwarding-options dhcp-security] introduced in Junos OS Release
13.2X50-D10. (See Using the Enhanced Layer 2 Software CLI for information about ELS.) | [
"Configuring Static DHCP IP Addresses for DHCP snooping (non-ELS)",
"Configuring Static DHCP IP Addresses for DHCP snooping (ELS)"
] |
static-ipv6 | static-ipv6 ip-address {
mac mac-address;
} | [edit vlans vlan-name forwarding-options dhcp-security group group-name interface interface-name],
[edit ethernet-switching-options secure-access-port interface interface-name] | Configure a static IP-MAC binding to be added to the DHCPv6 snooping database. | [
{
"name": "ip-address",
"desc": "Static IPv6 address assigned to a device connected on the specified interface."
},
{
"name": "mac mac-address",
"desc": "Static MAC address assigned to a device connected on the specified interface."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51-D20.
Support at the [edit ethernet-switching-options secure-access-port interface interface-name] hierarchy level
introduced in Junos OS Release 14.1X53-D10 for EX Series switches. | [
"Configuring Static DHCP IP Addresses for DHCP snooping (ELS)"
] |
static-label-switched-path | static-label-switched-path lsp-name {
bypass bypass-name {
bandwidth bps;
description string;
next-hop (address | interface-name | address/interface-name);
next-table string
push out-label;
to address;
}
ingress {
bandwidth bps;
class-of-servic... | [edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls] | Configure a static LSP. | [
{
"name": "lsp-name",
"desc": "Name of the path."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Configuring Static LSPs"
] |
static-lsp | static-lsp lsp-name; | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel rsvp-te],
[edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel selective group address source source-address rsvp-te],
[edit logical-systems logical-system-name routing-instan... | Specify the name of the static point-to-multipoint (P2MP) LSP used for a specific MBGP MVPN; static
P2MP LSP cannot be shared by multiple VPNs. Use this statement to specify the static LSP for both
inclusive and selective point-to-multipoint LSPs.
Use a static P2MP LSP when you know all the egress PE router endpoints ... | [] | 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. | [
"Point-to-Multipoint LSPs Overview",
"Configuring Static LSPs",
"Configuring Point-to-Multipoint LSPs for an MBGP MVPN",
"Example: Configuring an RSVP-Signaled Point-to-Multipoint LSP on Logical Systems"
] |
static-mac | static-mac mac-address;
static-mac mac-address {
vlan-id number;
} | [edit vlans vlan-name switch-options interface interface-name]
[edit bridge-domains bridge-domain-name bridge-options interface interface-name],
[edit logical-systems logical-system-name bridge-domains bridge-domain-name bridge-options
interface interface-name],
[edit logical-systems logical-system-name routing-insta... | Configure a static MAC address for a logical interface in a bridge domain or VLAN.
The vlan-id option can be specified for static-macs only if vlan-id all is configured for the bridging domain
or VLAN. | [
{
"name": "mac-address",
"desc": "MAC address"
},
{
"name": "vlan-id number",
"desc": "(Optional) VLAN identifier to associate with static MAC address."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Statement modified in Junos OS Release 9.5.
Support for logical systems added in Junos OS Release 9.6.
[edit vlans vlan-name switch-options interface interface name] hierarchy level introduced in Junos OS
Release 12.3R2 for EX Series switches.
Support for EVPNs added in Jun... | [
"Configuring EVPN Routing Instances",
"Understanding Layer 2 Learning and Forwarding for Bridge Domains",
"Layer 2 Learning and Forwarding for VLANs Overview",
"Adding a Static MAC Address Entry to the Ethernet Switching Table on a Switch with ELS Support"
] |
static-mac-ip | static-mac-ip ip-address {
mac-address [ mac-address ... ];
router;
} | [edit routing-instances name vlans name switch-options interface],
[edit vlans name switch-options interface],
[edit logical-systems name routing-instances name bridge-domains name bridge-options interface],
[edit routing-instances name bridge-domains name bridge-options interface],
[edit logical-systems name routing-i... | Configure a static IP address to MAC address (MAC-IP) binding. You can configure an IP address to one
or more MAC address entries.
NOTE: You can configure a maximum of eight MAC addresses per static IP address. | [
{
"name": "ip-address",
"desc": "Static IP address assigned to bind to the MAC address of the device."
},
{
"name": "mac-address [ mac-address ... ]",
"desc": "The MAC address of the switch-options interface."
},
{
"name": "router",
"desc": "Router flag for IPv6 addresses."
}
] | [none specified] | Statement introduced in Junos OS Release 23.4R1. | [] |
static-multihoming-peer | static-multihoming-peer (static-multihoming-peer-IP-address | [ static-multihoming-peer-IP-
address ... ]); | [edit logical-systems name protocols evpn],
[edit protocols evpn] | Statically identify a device's multihoming peer leaf devices in an Ethernet VPN (EVPN) network running
enhanced optimized intersubnet multicast (OISM).
OISM leaf devices are multihoming peers when they share an Ethernet segment (ES) for a multihomed
customer edge (CE) device or attached host. When enhanced OISM leaf de... | [
{
"name": "(static-multihoming-peer-IP-address | [ static-multihoming-peer-IP-address ... ])",
"desc": "One or more multihoming"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 24.4R1. | [
"Statically Identify Multihoming Peers With Enhanced OISM To Improve Convergence"
] |
static-nat | static-nat {
inet {
routing-instance (default | routing-instance-name);
}
nptv6-prefix {
address-prefix;
routing-instance routing-instance-name;
nptv6-prefix-name {
address-prefix-name;
routing-instance routing-instance-name;
[
prefix {
add... | [edit security nat static rule-set rule-set-name rule rule-name then] | Specify the translated address of the static NAT rule. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. Statement modified in Junos OS Release 12.1X45-D10.
Statement modified in Junos OS Release 12.3X48-D25. | [] |
static-policy-control | static-policy-control {
pcc-rules {
[rule-name precedence number <time-of-day-profile profile-name>];
}
pcc-rulebases {
[rulebase-name <time-of-day-profile profile-name>];
}
} | [edit unified-edge pcef profiles profile-name],
[edit services pcef profiles profile-name] | Configure static policy control for the policy and charging control (PCC) rules or PCC rulebase in a policy
and charging enforcement function (PCEF) profile. You can configure a maximum of 32 PCC rules in a
PCEF profile. There is no limit to the number of PCC rulebases you can configure in a PCEF profile.
NOTE: For Jun... | [] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef profiles profile-name] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series. | [
"Configuring a Policy and Charging Enforcement Function Profile for Junos OS Subscriber Aware",
"Static Policies",
"Configuring a Policy and Charging Enforcement Function Profile for Subscriber Management"
] |
static-remote-vtep-list | static-remote-vtep-list [ remote-vtep-loopback-address ... ]; | [edit bridge-domains name vxlan],
[edit routing-instances name bridge-domains name vxlan],
[edit routing-instances name vlans name vxlan],
[edit vlans name vxlan] | Statically configure a list of one or more remote virtual tunnel endpoints (VTEPs) on an Layer 2 (L2)
VXLAN gateway device, and map the list to a particular bridge domain or VLAN.
You can configure a static VXLAN configuration at the VLAN level or bridge domain level as follows:
•
In the default switch instance, suppo... | [
{
"name": "static-remote-vtep-list",
"desc": "Specify the loopback address of one or more remote VTEPs in square brackets ([]). You do not need to include a delimiter such as a comma between names."
}
] | routing | Statement introduced in Junos OS Release 20.4R1. | [
"Static VXLAN"
] |
static-subscriber-application | static-subscriber-application; | [edit services service-set name service-set-options] | Apply advanced services, such as deep packet inspection, to static subscribers configured under a
dynamic profile. Static subscribers are supported on GE, AE, and PS logical interfaces over LT interfaces.
To configure advanced services for static subscribers, in addition to the static-subscriber-application
statement, ... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1. | [] |
static-subscribers (Dynamic Service Provisioning) | static-subscribers {
access-profile profile-name;
authentication {
password password-string;
username-include {
delimiter delimiter-character;
domain-name domain-name;
interface;
logical-system-name;
routing-instance-name;
u... | [edit logical-systems logical-system-name system services],
[edit logical-systems logical-system-name routing-instances routing-instances-name system
services],
[edit routing-instances routing-instances-name system services],
[edit system services] | Configure and associate subscribers with statically configured interfaces for dynamic service
provisioning.
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—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"JSRC and Subscribers on Static Interfaces"
] |
static-subscribers | static-subscribers {
disable;
traceoptions {
file filename<files number> <match regular-expression > <size maximum-file-size> <world-
readable | no-world-readable>;
flag flag;
level (all | error | info | notice | verbose | warning);
no-remote-trace;
}
} | [edit system processes] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "disable",
"desc": "Disable the static subscribers process."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
static-tei-val | static-tei-val value; | [edit interfaces br-pim/0/port isdn-options] | For J Series Services Routers only. Statically configure the Terminal Endpoint Identifier (TEI) value. The
TEI value represents any ISDN-capable device attached to an ISDN network that is the terminal
endpoint. TEIs are used to distinguish between several different devices using the same ISDN links. | [
{
"name": "value",
"desc": "Value between 0 through 63."
}
] | 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. | [] |
static-umh (MBGP MVPN) | static-umh {
primary address;
backup address;
source-tree;
} | [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 RSVP-TE point-to-multipoint provider tunnels, statically set the
upstream multicast hop (UMH), instead of using one of the dynamic methods to choose the UMH
routers, such as that described in unicast-umh-election.
The static-umh statement causes all type 7 (S,G) routes to use the conf... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider",
"Tunnels",
"Example: Configuring Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider",
"Tunnels"
] |
interface-tag (Junos OS Evolved) | interface-tag name {
dynamic-profile dynamic-profile;
authentication {
password password;
username-include {
delimiter delimiter;
domain-name domain-name;
interface-name;
radius-realm radius-realm;
unit-number;
user-prefix u... | [edit interfaces interface <varname>name</varname> auto-configure static-vlan-identity] | Configure interface tag for the system to initiate a DHCP relay session over a static IFL (logical
interface). To initiate the session, you must also configure interface tag under the [edit interfaces
interface name unit unit_number] hierarchy. The system uses the tag-name to identify the subscriber
interface and creat... | [
{
"name": "name",
"desc": "Interface tag name. The length of the interface tag name cannot exceed 64 characters. The only supported special characters are ^_-*$."
},
{
"name": "dynamic-profile dynamic-profile",
"desc": "Specify the dynamic profile name to dynamically configure the interface."
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.4R1 | [] |
statistics (Access Profile) | statistics (time | volume-time); | [edit access profile profile-name accounting] | Configure the router or switch to collect time statistics, or both volume and time statistics, for the
sessions being managed by AAA. | [
{
"name": "time",
"desc": "Collect uptime statistics only."
},
{
"name": "volume-time",
"desc": "Collect both volume and uptime statistics."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
volume-time option added in Junos OS Release 9.4. | [
"RADIUS Servers and Parameters for Subscriber Access"
] |
statistics (Protocols MPLS) | statistics {
auto-bandwidth (MPLS Statistics);
file filename <files number> <size size> <world-readable | no-world-readable>;
interval seconds;
no-transit-statistics;
traffic-class-statistics;
transit-statistics-polling;
statistics-query-batch-size <batch-size>;
} | [edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls] | Enable MPLS statistics collection and reporting. | [
{
"name": "file filename",
"desc": "(Optional) Name of the file to receive the output. We recommend that you place MPLS"
},
{
"name": "files number",
"desc": "(Optional) Maximum number of trace files. When a trace file named file reaches its"
},
{
"name": "interval seconds",
"desc": ... | routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
traffic-class-statistics option introduced in Junos OS Release 14.2. | [
"Configuring MPLS to Gather Statistics",
"Configuring Automatic Bandwidth Allocation for LSPs"
] |
statistics (Service Accounting) | statistics (time | volume-time); | [edit access profile profile-name service accounting] | Configure the router to collect time statistics, or both volume and time statistics, for the service
accounting sessions being managed by AAA. | [
{
"name": "time",
"desc": "Collect uptime statistics only."
},
{
"name": "volume-time",
"desc": "Collect both volume and uptime statistics."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R1. | [
"RADIUS Accounting for Subscriber Access",
"RADIUS Accounting for Subscriber Access",
"RADIUS Accounting for Subscriber Access"
] |
statistics (Services) | statistics {
interval interval-number;
} | [edit services application-identification] | Specify the interval, in minutes, for statistics collection. | [
{
"name": "interval interval-number",
"desc": "Length of time, in minutes, that application statistics are collected."
}
] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Onbox Application Identification Statistics"
] |
statistics | statistics {
no-ingress;
no-transit;
} | [edit logical-systems name protocols source-packet-routing telemetry],
[edit protocols source-packet-routing telemetry] | Enable traffic-statistics collection on SR-TE policies through sensors for both SR-TE policy next hop and
binding segment identifier (SID) installed in the forwarding table, by using JVISION traffic sensors in
Junos data plane to stream out traffic statistics on static segment routing policies and their
corresponding b... | [
{
"name": "no-ingress",
"desc": "(Optional) Create sensors for binding SID transit routes only."
},
{
"name": "no-transit",
"desc": "(Optional) Create sensors for SR-TE policy next hops and collect statistics on all steering routes that use the SR-TE policy as nexthop. NOTE: no-ingress and no-tr... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1. | [
"Segment Routing Traffic Engineering at BGP Ingress Peer Overview"
] |
statistics-service | statistics-service {
command binary-file-path;
disable;
} | [edit system processes] | Specify the Packet Forwarding Engine (PFE) statistics service management process. | [
{
"name": "command binary-file-path",
"desc": "Path to the binary process."
},
{
"name": "disable",
"desc": "Disable the Packet Forwarding Engine (PFE) statistics service management process."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
stats-aggregation-interval (programmable-rpd) | stats-aggregation-interval seconds; | [edit routing-options programmable-rpd] | Configure the aggregation window for programmable routing protocol process (prpd) statistics.
If the OpenConfig telemetry collector is receiving periodic streaming every 1 minute, then we
recommend that you configure a 60-second stats-aggregation-interval in order for the collector to not lose
any data. This is because... | [
{
"name": "seconds",
"desc": "Statistics aggregation time in seconds. Range: 60 through 3600 seconds Default: 60 seconds"
}
] | routing | Statement introduced in Junos OS Evolved Release 22.2R1. | [] |
stats-sampling-interval (programmable-rpd) | stats-sampling-interval seconds; | [edit routing-options programmable-rpd] | Configure the sampling interval at which to collect programmable routing protocol process (prpd)
statistics. | [
{
"name": "seconds",
"desc": "Interval in seconds. Range: 30 through 3600 seconds Default: 30 seconds"
}
] | routing | Statement introduced in Junos OS Evolved Release 22.2R1. | [] |
status | status | Display the users currently editing the configuration. | [] | configure—Enters status configuration mode. | Command introduced before Junos OS Release 7.4. | [
"Displaying Users Currently Editing the Configuration"
] | |
status-control | status-control (active | standby); | [edit interfaces aggregated-ether-options mc-ae] | Specify whether a peer hosting a multichassis link aggregation group (MC-LAG) is primary or secondary.
Primary is considered active, and secondary is considered standby. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [] |
steering | steering {
keep-existing-steering;
path {
ipv4-address ipv4-address;
ipv6-address ipv6-address;
}
routing-instance {
downlink downlink-vrf-name;
uplink uplink-vrf-name;
}
} | [edit unified-edge pcef pcc-action-profiles profile-name],
[edit services pcef pcc-action-profiles profile-name] | Specify the method that a PCC action profile uses for steering traffic
If you are using Junos OS Subscriber Aware, configure steering at the [edit unified-edge pcef pcc-action-
profiles profile-name] hierarchy level.
If you are using Junos OS Broadband Subscriber Management, configure the PCC action profile at the
[edi... | [] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef pcc-action-profiles profile-name] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series.
Support for Next Gen Services for Junos OS Broadband Subscriber Management introduced in Jun... | [
"Understanding Application-Aware Policy Control for Subscriber Management",
"Configuring Policy and Charging Control Action Profiles for Subscriber Management",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Configuring Policy and Charging Control Action ... |
step-percent (RFC 2544 Benchmarking) | step-percent percent; | [edit services monitoring rfc2544 test-profile profile-name] | Specify the step percentage for frame-loss tests. This parameter is not applicable for the other types of
tests. If you do not configure this parameter, the default step-percent is 10 percent. | [
{
"name": "percent",
"desc": "Step percent for frame-loss tests. Default: 10 percent Range: 1 through 100 percent"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X53.
Statement introduced in Junos OS Evolved Release 23.4R1. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
stickydr | stickydr | [edit protocols pim interface interface-name]
[edit routing-instances instance-name protocols pim interface interface-name] | The stickydr feature protects against traffic loss as can happen when the designated router (DR) changes
once a new router joins the LAN and/or following an interface down event, or device upgrade. Set
stickydr on all the last hop devices in the LAN, and it will assign one DR special priority (that is, 0xfffffffe,
the ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1. | [
"Understanding Designated Routers",
"Configuring Basic PIM Settings",
"Configuring a Designated Router for PIM"
] |
stop-date | stop-date date-time; | [edit schedulers scheduler scheduler-name] | Specify the time, day, month, and year that the schedule ends.
Specifying the year is optional. If no year is specified, the schedule applies to the current year and all
subsequent years. If the year is specified in either the start-date or stop-date statement, that year is used
for both statements. | [
{
"name": "date-time",
"desc": "Use the format [ yyyy -] mm - dd . hh . mm to specify the year, month, day, hour, and minutes."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Security Policies Overview"
] |
stop-time | stop-time hh:mm; | [edit schedulers scheduler scheduler-name daily],
[edit schedulers scheduler scheduler-name friday],
[edit schedulers scheduler scheduler-name monday],
[edit schedulers scheduler scheduler-name saturday],
[edit schedulers scheduler scheduler-name sunday],
[edit schedulers scheduler scheduler-name tuesday],
... | Specify the time that a schedule stops for a specified day.
If you specify a stop time for a daily schedule with the daily statement and also include the the friday,
monday, saturday, sunday, tuesday, thursday, and wednesday statements in the schedule, the stop time specified
for a specific day (for example, Friday usi... | [
{
"name": "time",
"desc": "Use the 24-hour format (hh:mm:ss ) to specify the hours, minutes, and seconds."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release. | [
"Security Policies Overview"
] |
storage | storage device-name {
type {
cdrom {
source {
file filename;
}
}
disk {
bus-type [ide | virtio];
file-type [qcow2 | raw];
source {
file filename;
}
}
usb {
... | [edit virtual-network-functions] | Configure storage parameters on VNFs. | [
{
"name": "storage",
"desc": ""
},
{
"name": "device-name",
"desc": "Name of the storage device. For example, hda, hdb, sdb, or vdb."
},
{
"name": "type disk-type",
"desc": "Type of disk. For example, cdrom, usb, or disk."
},
{
"name": "source file-name",
"desc": "Path of... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D40. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
store | store {
database;
file name {
files number;
(no-world-readable | world-readable);
size size;
}
fwding-file name {
files number;
(no-world-readable | world-readable);
size size;
}
} | [edit system resiliency] | Store exception data in a file or database.
The on-box collector is disabled by default.
To enable the on-box collector for forwarding exceptions and store the exception data in a file, configure
the following:
user@host# set system resiliency exceptions forwarding
user@host# set system resiliency store fwding-file fi... | [
{
"name": "database",
"desc": "Store exceptions data in the on-box SQLite database, in the /var/db directory. You can copy this database to a remote server and issue SQL commands using the SQLite command line interface. Starting in Release 22.2R1, you can only configure one place to store your exception dat... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1 for MX Series routers.
Statement introduced in Junos Evolved OS Release 22.2R1 for PTX Series routers. | [
"Juniper Resiliency Interface"
] |
storm-control (switch) | storm-control {
action-shutdown;
interface (all | interface-name) {
bandwidth bandwidth;
level level;
multicast;
no-broadcast;
no-multicast;
no-registered-multicast;
no-unknown-unicast;
no-unregistered-multicast;
}
} | [edit ethernet-switching-options] | Configure storm control on the switch.
Apply storm control to all interfaces or to the specified interfaces on switches running non-ELS
software. (For the equivalent statement for switches running ELS software, see "storm-control" on page
29729.
The remaining statements are explained separately. See CLI Explorer.
Defau... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Understanding Storm Control",
"Example: Using Storm Control to Prevent Network Outages (non-ELS)"
] |
storm-control (Video Monitoring) | storm-control {
count number;
interval number;
} | [edit services] | Configure the count and the interval to control the flooding of SNMP traps per flow. | [
{
"name": "count number",
"desc": "Use the specified maximum number of SNMP traps generated in the configured interval."
},
{
"name": "interval number",
"desc": "Use the specified minimum time period, in seconds, between the generation of successive traps. Default: The default count value is 1.... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding Inline Video Monitoring on MX Series Routers"
] |
storm-control | storm-control storm-control-profile; | [edit interfaces interface-name unit number family ethernet-switching],
[edit interfaces interface-name unit number family bridge]
[edit interfaces interface-name ether-options ethernet-switch-profile]
[edit logical-systems name interfaces interface-name unit number family bridge] | Bind a storm control profile to a given interface.
On switches running ELS software, storm control is enabled by default on all switch interfaces at a level
of 80 percent of the combined broadcast and unknown unicast streams. (For the equivalent statement
for platforms running non-ELS software, see "storm-control" on p... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10.
Starting in Junos OS release 17.4R1 for MX Series routers, support for storm control was added for
logical systems. | [
"Example: Configuring Storm Control to Prevent Network Outages on EX Series Switches",
"Understanding Storm Control"
] |
storm-control-profiles | storm-control-profiles profile-name {
action-shutdown;
all {
bandwidth-level;
bandwidth-percentage;
no-broadcast;
no-multicast;
no-registered-multicast;
no-unknown-unicast;
no-unregistered-multicast;
}
} | [edit forwarding-options]
[edit logical-systems name forwarding-options] | Configure a storm control profile on a switch or router. Storm control is used to prevent network
outages that are caused by broadcast traffic storms. Storm control enables the switching device to
monitor traffic levels and to drop broadcast, multicast, and unknown unicast packets when a specified
traffic level—called ... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10.
Starting in Junos OS release 17.4R1 for MX Series routers, support for storm control was added for
logical systems. | [
"Example: Configuring Storm Control to Prevent Network Outages on EX Series Switches",
"Understanding Storm Control"
] |
stp | stp {
bpdu-block-on-edge ;
bridge-priority priority;
disable;
forward-delay seconds;
hello-time seconds;
... | [edit protocols],
[edit protocols rstp force-version] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Overview of Spanning-Tree Protocols",
"Understanding STP",
"Configuring STP on EX Series Switches (CLI Procedure)",
"Configuring STP"
] |
stream (Logical Systems and Tenant Systems) | stream name {
category name;
filter name;
host {
ipaddr;
port port;
routing-instance routing-instance;
}
rate-limit rate;
} | [edit logical-systems name security log]
[edit tenants name security log] | Define security log stream options for a logical and tenant system. When the logging mode is set to
stream, security logs generated in the data plane are streamed out a revenue traffic port directly to a
remote server. All the categories can be configured for sending specific category logs to different log
servers for ... | [
{
"name": "category",
"desc": "Type of logged events. Values:"
},
{
"name": "aamw",
"desc": "AAMW events are logged."
},
{
"name": "alg",
"desc": "Alg events are logged."
},
{
"name": "all",
"desc": "All events are logged."
},
{
"name": "appqos",
"desc": "App... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1 for logical Systems.
Statement introduced in Junos OS Release 18.3R1.
The routing-instance option introduced in Junos OS Release 18.3R1 for tenant systems. | [
"Troubleshooting Logical Systems"
] |
stream (Next Gen Services Service-Set Remote System Logging) | stream stream-name (severity debug | category screen | format sd-syslog | host); | edit services service-set name syslog | Specify the name of the stream to the remote log server.
NOTE: Each remote server requires a unique stream name. | [
{
"name": "severity debug",
"desc": ""
},
{
"name": "category screen",
"desc": ""
},
{
"name": "format sd-syslog",
"desc": ""
},
{
"name": "host",
"desc": ""
}
] | system | 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. | [
"Understanding Next Gen Services CGNAT Global System Logging",
"Enabling Global System Logging for Next Gen Services",
"Configuring System Logging to One or More Remote Servers for Next Gen Services",
"Configuring Local System Logging for Next Gen Services"
] |
stream (Next Gen Services) | stream name {
category name;
format (binary | protobuf | sd-syslog | syslog | welf);
host {
ipaddr;
log-tag log-tag;
port port;
routing-instance routing-instance;
}
severity (alert | critical | d... | [edit services service-set name syslog] | Set UDP based syslog log stream for Next Gen Services (Unified Services). | [
{
"name": "name",
"desc": "Name of security log stream."
},
{
"name": "category",
"desc": "Selects the type of events that may be logged"
},
{
"name": "aamw",
"desc": "AAMW events are logged"
},
{
"name": "alg",
"desc": "Alg events are logged"
},
{
"name": "all",
... | [none specified] | Statement introduced in Junos OS Release 19.1R1 | [] |
stream (Security Log) | stream stream-name {
category (all | content-security | fw-auth | screen | alg | nat | flow | sctp | gtp | ipsec
| idp | rtlog |pst-ds-lite | appqos |secintel |aamw);
file {
allow-duplicates;
name file-name;
size maximum-file-size;
rotation maximum-file-rotation-number;
filt... | [edit security log]
[edit logical-systems name security log]
[edit tenants tenant-name security log] | Define the security log steam settings.
Define security log stream options for a logical and tenant system. When the logging mode is set to
stream, security logs generated in the data plane are streamed out a revenue traffic port directly to a
remote server. All the categories can be configured for sending specific cat... | [
{
"name": "stream",
"desc": "Every stream can configure file or host. Values:"
},
{
"name": "category",
"desc": "Type of events that may be logged."
},
{
"name": "all",
"desc": "All events are logged"
},
{
"name": "content-security",
"desc": "Content security events are ... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.2.
The [edit logical-systems name security log] and [edit tenants tenant-name security log] hierarchy levels
introduced in Junos OS Release 19.1R1.
time-format, source-address, and transport options are introduced in Junos OS Release 20.2R1.
radius option is introduced in Junos ... | [
"Example: Configuring AppTrack"
] |
stream-option (IDS Screen Next Gen Services) | stream-option; | [edit services screen ids-option screen-name ip] | Identify and drop IPv4 packets that have the IP option of 8 (Stream ID). | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
stream-protection (Multicast-Only Fast Reroute) | stream-protection {
mofrr-asm-starg;
mofrr-disjoint-upstream-only;
mofrr-no-backup-join;
mofrr-primary-path-selection-by-routing;
policy policy-name;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options multicast] | Enable multicast-only fast reroute (MoFRR) on a routing or switching device. MoFRR minimizes packet
loss in a network when there is a link failure. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Understanding Multicast-Only Fast Reroute",
"Example: Configuring Multicast-Only Fast Reroute in a PIM Domain",
"Example: Configuring Multicast-Only Fast Reroute in a PIM Domain on Switches",
"Example: Configuring Multicast-Only Fast Reroute in a Multipoint LDP Domain"
] |
streaming-server (Junos Telemetry Interface) | streaming-server streaming-server-name {
remote-address ip-address;
remote-port number;
tls {
certificate-id local-cert-id;
ca-profiles ca-profiles;
}
} | [edit services analytics] | For Junos telemetry interface, configure the parameters of the server that collects exported data
streamed by a monitored system resource. You can configure more than one streaming server. To collect
data, you must associate a configured server with one or more configured sensors. The sensor
configuration defines the p... | [
{
"name": "streaming-server-name",
"desc": "Specify a name for the server configured to collect data streamed through Junos Telemetry Interface. You can configure multiple streaming servers. To associate as many as four server names with a sensor configuration, include each name at the [edit services analyt... | 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. | [] |
streaming-servers | streaming-servers {
address ip-address {
port number {
stream-format format;
stream-type type
}
}
} | [edit services analytics] | Configure remote servers to receive streaming output for the network analytics monitoring of traffic and
queue statistics. The streaming function supports TCP connections only, and sends records separated by
a newline character.
NOTE: Before you use the remote server to receive streaming data, you must set up the
TCP s... | [
{
"name": "address ip-address",
"desc": "IP address of the remote server receiving the streaming data."
},
{
"name": "port number",
"desc": "Port number of the remote server receiving the streaming data."
},
{
"name": "stream-format",
"desc": ""
},
{
"name": "format",
"de... | 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. | [
"Network Analytics Overview"
] |
strict (DHCP Local Server) | strict; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 reconfigure],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 group group-name reconfigure],
[edit logical-systems logi... | Specify whether the server denies a client to bind when the client does not indicate that it accepts
reconfigure messages. This feature is available only for DHCPv6.
Default
Accept solicit messages from clients that do not support reconfiguration and permit them to bind. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Configuring Dynamic Reconfiguration of Extended Local Server Clients Overview",
"Preventing Binding of Clients That Do Not Support Reconfigure Messages"
] |
strict-asla-based-flex-algorithm | strict-asla-based-flex-algorithm; | [edit logical-systems name protocols isis source-packet-routing],
[edit logical-systems name routing-instances name protocols isis source-packet-routing],
[edit logical-systems name tenants name routing-instances name protocols isis source-packet-routing],
[edit protocols isis source-packet-routing],
[edit routing-inst... | Configure IS-IS to ignore links that do not have TE Attributes advertised in Flex-Algo specific
Application-Specific Link Attribute (ASLA) sub-TLVs. This is applicable only to the following TE attribute
sub-TLVs:
•
Min unidirectional link delay
•
TE default metric
•
Administrative group
NOTE: If you do not enable stric... | [] | routing | Statement introduced in Junos OS 21.3R1. | [
"How to Configure Flexible Algorithms in IS-IS for Segment Routing Traffic Engineering"
] |
strict-dual-isis (Protocols IS-IS) | strict-dual-isis {
holddown delay-value;
} | [edit logical-systems logical-system-name protocols isis],
[edit protocols isis] | Configure strict dual stack (IPv4 and IPv6) support for IS-IS.
The strict-dual-isis option was introduced in Junos release 18.RR1-S6. This option avoids protocol flap
when both IPv4 and IPv6 are configured on the same interface or in the same ISIS instance. The option
works by introducing a holdown delay to allow both ... | [
{
"name": "holddown",
"desc": "Specify the delay before ISIS advertises IPv4 and IPv6 reachability, either for the entire ISIS instance or under a specific interface. For details on interface level application, see"
},
{
"name": "\"interface (Protocols IS-IS)\" on page 9316",
"desc": "By default... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 18.4R1-S6. | [] |
strict-priority-scheduler | strict-priority-scheduler; | [edit class-of-service traffic-control-profiles profile-name] | On PTX Series routers only, enable strict-priority scheduling for all scheduler maps within the traffic
control profile.
Physical interfaces on PTX Series routers support two mutually exclusive scheduling processes:
•
normal scheduling (default mode) — A queue’s transmit-rate is used to determine whether it is
operatin... | [] | 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. | [
"Example: Configuring Strict-Priority Scheduling on a PTX Series Router",
"Understanding Scheduling on PTX Series Routers",
"Understanding CoS CLI Configuration Statements on PTX Series Routers",
"How Schedulers Define Output Queue Properties"
] |
strict-source-route-option (IDS Screen Next Gen Services) | strict-source-route-option; | [edit services screen ids-option screen-name ip] | Identify and drop IPv4 packets that have the IP option of 9 (Strict Source Routing). | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
strict-syn-check | strict-syn-check; | [edit security flow tcp-session] | Enable the strict three-way handshake check for the TCP session. It enhances security by dropping data
packets before the three-way handshake is done. By default, strict-syn-check is disabled. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
strict-targeted-hellos | strict-targeted-hellos; | [edit logical-systems logical-system-name protocols ldp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp],
[edit protocols ldp],
[edit routing-instances routing-instance-name protocols ldp] | Prevent LDP sessions from being established with remote neighbors that have not been specifically
configured. LDP peers will not respond to targeted hellos coming from a source that is not one of the
configured remote neighbors. | [] | 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. | [
"Enabling Strict Targeted Hello Messages for LDP"
] |
string | string {
equals;
has-prefix;
has-suffix;
matches;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from attribute name
format] | Specify the custom AVP attribute’s format as a string and the value to match for the incoming RADIUS
request from the IP-based subscriber.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selected.
The ... | [] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
strip-as-path | strip-as-path; | [edit policy-options policy-statement policy-name term term-name then] | Removes the incoming autonomous system (AS) path as part of the import policy for a BGP session and
replaces the received autonomous system (AS) path with the receiving router's local AS number for the
receiving session. Note that the local AS number may be different from the number configured under
autonomous system i... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.3. | [
"Autonomous Systems for BGP Sessions"
] |
strip-domain (Domain Map) | strip-domain; | [edit access domain map domain-map-name] | Remove the domain name from the username before continuing with any AAA services specified in a
domain map. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Mapping Subscriber Domains to Access and Session Options",
"Mapping Subscriber Domains to Access and Session Options"
] |
strip-nexthop | strip-nexthop; | [edit protocols bgp family (inet | inet-vpn | inet6 | inet6-vpn) flow],
[edit protocols bgp group group-name family (inet | inet-vpn | inet6 | inet6-vpn) flow],
[edit protocols bgp group group-name neighbor address family (inet | inet-vpn | inet6 | inet6-
vpn flow)],
[edit routing-instances routing-instance-name protoc... | Prevents BGP from advertising flow route updates with real nexthop address even when the route is
present in the local routing table. When strip-nexthop is not configured, Junos advertises the real next
hop to its neighbors in order to interoperate with devices that have the capability to accept and
advertise real BGP ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2. | [
"Example: Enabling BGP to Carry Flow-Specification Routes"
] |
strip-user-name (Access Profile) | strip-user-name {
delimiter delimiter;
parse-direction (left-to-right | right-to-left);
} | [edit access profile profile-name session-options] | Configure the details of username stripping for a subscriber access profile. This configuration determines
how a portion of a subscriber login string is identified and discarded, leaving the remainder for
subsequent use as a modified username by an external AAA server for session authentication and
accounting. For exam... | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Understanding Session Options for Subscriber Access",
"Configuring Username Modification for Subscriber Sessions",
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.