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 |
|---|---|---|---|---|---|---|---|
set services jinsightd subscribe health-monitor | set services jinsightd subscribe health-monitor | Enables the J-Insight health monitor. Starting in Junos OS Release 18.2R1, J-Insight provides health
monitoring capabilities for FPC FRUs on the MX series routers. The health monitor is disabled by
default. | [] | system | Command introduced in Junos OS Release 18.2R1. | [
"J-Insight Device Monitor Basic Configuration"
] | |
set services jinsightd traceoptions | set services jinsightd traceoptions flag
<all>
<core>
<database>
<rule-engine>
<timer> | 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": "all",
"desc": "All tracing operations."
},
{
"name": "core",
"desc": "J-Insight core events."
},
{
"name": "database",
"desc": "Database events."
},
{
"name": "rule-engine",
"desc": "Rule engine events."
},
{
"name": "timer",
"desc": "Timer events."... | system | Command introduced in Junos OS Release 18.2R1. | [
"J-Insight Device Monitor Basic Configuration"
] | |
set | set <statement-path> identifier | Create a statement hierarchy and set identifier values. This is similar to edit except that your current
level in the hierarchy does not change. | [
{
"name": "identifier",
"desc": "Name of the statement or identifier to set."
},
{
"name": "statement-path",
"desc": "(Optional) Path to an existing statement hierarchy level. If that hierarchy level does not exist, it is created."
}
] | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy. | Command introduced before Junos OS Release 7.4. | [
"Displaying the Current Configuration"
] | |
set-dont-fragment-bit (Services IPsec VPN) | set-dont-fragment-bit; | [edit services ipsec-vpn rule rule-name term term-name then] | Configure the do not fragment (DF) bit in only the outer header of the IPsec packet and leave the inner
header unmodified. If the encapsulated packet size exceeds the tunnel maximum transmission unit
(MTU), the packet is fragmented before encapsulation. These settings apply for static endpoint tunnels
and not for dynam... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Configuring IPsec Rules"
] |
set-dont-fragment-bit (Services Set) | set-dont-fragment-bit; | [edit services service-set service-set-name ipsec-vpn-options] | Configure the do not fragment (DF) bit in only the outer header of the IPsec packet and leave the inner
header unmodified for dynamic endpoint tunnels. If the encapsulated packet size exceeds the tunnel
maximum transmission unit (MTU), the packet is fragmented before encapsulation. These settings apply
for dynamic endp... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Configuring IPsec Service Sets",
"Configuring IPsec Rules"
] |
setup-protection | setup-protection; | [edit logical-systems logical-system-name protocols rsvp],
[edit protocols rsvp] | The facility-backup fast reroute mechanism can provide setup protection for LSPs which are in the
process of being signaled. Both point-to-point LSPs and point-to-multipoint LSPs are supported. You
should configure the setup-protection statement on each of the routers along the LSP path on which you
want to enable LSP ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | [
"Configuring RSVP Setup Protection"
] | |
severity (Event Policy) | severity severity-level; | [edit event-options policy policy-name then priority-override] | emergency
System panic or other conditions that cause the routing platform to stop
functioning
alert
Conditions that require immediate correction, such as a corrupted system
database
critical
Critical conditions, such as hard disk errors
error
Error conditions that generally have less serious consequences than errors i... | [
{
"name": "severity-level",
"desc": "Severity level logged for the triggering event. Table 161 on page 17510 lists the possible severity levels. Table 161: System Log Message Severity Levels Severity Level"
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 12.1. | [
"System Log Priority for Events in Event Policies"
] |
severity (Next Gen Services Service-Set Remote System Logging) | severity severity; | edit services service-set name syslog stream stream-name | Specify the level of severity for the stream.
You can set the following severity levels:
•
ANY — Includes all severity levels
•
ALERT — Action must be taken immediately
•
CRITICAL — Critical conditions
•
EMERGENCY — System is unusable
•
ERROR — Error conditions
•
WARNING — Warning conditions
•
NOTICE — Normal but signi... | [] | system | Statement introduced in Junos OS Release 19.3R2. | [
"Understanding Next Gen Services CGNAT Global System Logging",
"Enabling Global System Logging for Next Gen Services",
"Configuring System Logging to One or More Remote Servers for Next Gen Services",
"Configuring Local System Logging for Next Gen Services"
] |
severity (Security IDP Custom Attack) | severity (critical | info | major | minor | warning); | [edit security idp custom-attack attack-name] | Select the severity that matches the lethality of the attack object on your network. | [
{
"name": "critical",
"desc": "Contains attack objects matching exploits that attempt to evade detection, cause a network"
},
{
"name": "warning",
"desc": "Contains attack objects matching exploits that attempt to obtain noncritical information or"
},
{
"name": "major",
"desc": "Cont... | 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. | [] |
severity (Security IDP Dynamic Attack Group) | severity {
values [critical info major minor warning];
} | [edit security idp dynamic-attack-group dynamic-attack-group-name filters] | Specify a severity filter to add attack objects based on the attack severity levels. | [
{
"name": "values",
"desc": "Name of the severity filter. You can select from the following severity:"
},
{
"name": "critical",
"desc": "The attack is a critical one."
},
{
"name": "info",
"desc": "Provide information of attack when it matches."
},
{
"name": "major",
"des... | 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. | [] |
severity (Security IDP IPS Rulebase) | severity (critical | info | major | minor | warning); | [edit security idp idp-policy policy-name rulebase-ips rule rule-name then] | Set the rule severity levels in logging to support better organization and presentation of log records on
the log server. You can use the default severity settings of the selected attack object, or choose a
specific severity for your rule. The severity you configure in the rules overrides the inherited attack
severity. | [
{
"name": "critical",
"desc": "2"
},
{
"name": "info",
"desc": "3"
},
{
"name": "major",
"desc": "4"
},
{
"name": "minor",
"desc": "5"
},
{
"name": "warning",
"desc": "7"
}
] | 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. | [] |
severity (Security Log) | severity (alert | critical | debug | emergency | error | info | notice | warning) | [edit security log stream stream-name]
[edit logical-systems name security log stream stream-name]
[edit tenants tenant-name security log stream stream-name] | Set severity threshold for security logs. | [
{
"name": "alert",
"desc": "Conditions that require immediate attention."
},
{
"name": "critical",
"desc": "Critical conditions."
},
{
"name": "debug",
"desc": "Information normally used in debugging."
},
{
"name": "emergency",
"desc": "Conditions that cause security func... | 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 stream stream-name] and [edit tenants tenant-name security
log stream stream-name] hierarchy levels introduced in Junos OS Release 19.1R1. | [] |
sflow | and ACX7509)
adaptive-sample-rate rate {
fallback;
sample-limit-threshold sample-limit-threshold;
}
agent-id {
inet ipv4-address;
inet6 ipv6-address;
}
collector ip-v4/v6-address {
dscp dscp;
forwarding-class forwarding-class;
routing-instance rou... | [edit protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3.
dscp and forwarding-class options introduced in Junos OS Release 19.1R1, for PTX routers and QFX
switches (previously introduced for MX Series).
sample-size option introduced in Junos OS Evolved Release 23.1R1, for PTX routers.
inet6 option under agent-id introduced in Juno... | [
"Understanding How to Use sFlow Technology for Network Monitoring",
"Understanding Inline Active Flow Monitoring"
] |
sfm (Chassis Redundancy) | sfm slot-number (always | preferred); | [edit chassis redundancy] | On M40e and M160 routers, configure which Switching and Forwarding Module (SFM) is the primary
and which is the backup.
Default
By default, the SFM in slot 0 is the primary and the SFM in slot 1 is the backup. | [
{
"name": "slot-number",
"desc": "Specify which slot is the primary and which is the backup. On the M40e router, slot-number can be 0 or 1. On the M160 router, slot-number can be 0 through 3."
},
{
"name": "always",
"desc": "Define this SFM as the sole device."
},
{
"name": "preferred",
... | 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 SFM Redundancy on M40e and M160 Routers"
] |
sfm (Chassis) | sfm slot-number power off; | [edit chassis] | For routers with SFMs, configure an SFM to stay offline.
By default, if you use the request chassis sfm CLI command to take an SFM offline, the SFM will attempt
to restart when you enter a commit CLI command. To prevent a restart, configure an SFM to stay offline.
This feature is useful for repair situations. The SFM r... | [
{
"name": "slot-number",
"desc": "Slot number in which the SFM is installed."
},
{
"name": "power off",
"desc": "Take the SFM offline and configure it to remain offline."
}
] | 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 an SFM to Stay Offline",
"High Availability User Guide"
] |
sfp-type | sfp-type (CHAN-STM1 | DS3 | E1 | STM1 | STM16 | STM4 | T1); | [edit interfaces interface name tdm-options],
[edit interfaces interface-range name tdm-options] | Smart SFP type | [
{
"name": "CHAN-STM1",
"desc": "Channelised SFP STM1"
},
{
"name": "DS3",
"desc": ""
},
{
"name": "DS3 smart SFP",
"desc": ""
},
{
"name": "E1",
"desc": ""
},
{
"name": "E1 smart SFP",
"desc": ""
},
{
"name": "STM1",
"desc": ""
},
{
"name":... | [none specified] | Statement introduced in Junos OS Evolved Release 25.4R1 | [] |
sfpplus | sfpplus {
pic-mode mode;
} | [edit chassis fpc slot pic pic-number] | Configure the operating mode for the specified port on the SFP+ uplink module on the EX3200 or
EX4200 switch.
The remaining statement is explained separately. See CLI Explorer.
Default
By default, the SFP+ uplink module operates in the 10-gigabit mode and supports SFP+ transceivers.
NOTE: The SFP+ uplink module provide... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Setting the Mode on an SFP+ or SFP+ MACSec Uplink Module"
] |
sftp-backup (OCS Partition) | sftp-backup {
accumulation-timeout seconds;
accumulation-count messages;
accumulation-size bytes;
logical-system;
retry-interval seconds;
response-timeout seconds;
routing-instance;
address ipv4 | ipv6;
port number;
directory filename;
file-name-prefix filename-prefix;
no... | [edit access ocs partition partition-name] | The data backup for OCS using the SFTP protocol to store data on a remote server. | [
{
"name": "accumulation-timeout",
"desc": ""
},
{
"name": "seconds",
"desc": "The file accumulation time since the first CCR-GY-T was submitted. The maximum time is 30 seconds."
},
{
"name": "accumulation-count",
"desc": ""
},
{
"name": "messages",
"desc": "The number of ... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1. | [
"3GPP Policy and Charging Control for Wireline Provisioning and Accounting",
"3GPP Policy and Charging Control for Wireline Provisioning and Accounting",
"3GPP Policy and Charging Control for Wireline Provisioning and Accounting",
"3GPP Policy and Charging Control for Wireline Provisioning and Accounting",
... |
sg-forwarding-only | sg-forwarding-only; | [edit logical-systems name protocols mvpn mvpn-mode rpt-spt],
[edit logical-systems name routing-instances name protocols mvpn mvpn-mode rpt-spt],
[edit logical-systems name tenants name routing-instances name protocols mvpn mvpn-mode rpt-spt],
[edit protocols mvpn mvpn-mode rpt-spt],
[edit routing-instances name proto... | Create only (S, G) and not (*, G) forwarding entries. | [] | Statement introduced in Junos OS Release 25.1R1. | [
"RPT- SPT Mode with Direct Sources and Receivers"
] | |
sglimit | sglimit {
family (inet | inet6) {
log-interval seconds;
maximum limit;
threshold value;
}
log-interval seconds;
maximum limit;
threshold value;
} | [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 a limit for the number of accepted (*,G) and (S,G) PIM join states.
NOTE: The maximum limit settings that you configure with the maximum and the family
(inet | inet6) maximum statements are mutually exclusive. For example, if you configure a
global maximum PIM join state limit, you cannot configure a limit a... | [
{
"name": "family (inet | inet6)",
"desc": "(Optional) Specify either IPv4 or IPv6 join states to be counted towards the"
}
] | 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 State Limits",
"clear pim join"
] |
sham-link | sham-link {
local address
{
keychain keychain-name;
}
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ospf],
[edit routing-instances routing-instance-name protocols ospf] | Configure the local endpoint of a sham link.
You can create an intra-area link or sham link between two provider edge (PE) routing devices so that
the VPN backbone is preferred over the back-door link. A back-door link is a backup link that connects
customer edge (CE) devices in case the VPN backbone is unavailable. Wh... | [
{
"name": "local address",
"desc": "The address for the local endpoint of the sham link."
},
{
"name": "keychain keychain-name",
"desc": "For each keychain, you must specify a name."
}
] | 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.
The option keychain keychain-name introduced in Junos OS and Junos OS Evolved Release 24.2R1. | [
"Example: Configuring OSPFv2 Sham Links"
] |
sham-link-remote | sham-link-remote address {
demand-circuit;
ipsec-sa name;
metric metric;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf
area area-id],
[edit routing-instances routing-instance-name protocols ospf area area-id] | Configure the remote endpoint of a sham link.
You can create an intra-area link or sham link between two provider edge (PE) routing devices so that
the VPN backbone is preferred over the back-door link. A back-door link is a backup link that connects
customer edge (CE) devices in case the VPN backbone is unavailable. W... | [
{
"name": "address",
"desc": "Address for the remote end point of the sham link."
},
{
"name": "demand-circuit",
"desc": "Configure an interface as a demand circuit."
},
{
"name": "ipsec-sa",
"desc": ""
},
{
"name": "name",
"desc": "Apply the named IPsec authentication to... | 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 ipsec-sa statement added in Junos OS Release 8.3. | [
"Example: Configuring OSPFv2 Sham Links"
] |
shaping | shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate burst
length);
queue-length number;
} | [edit interfaces interface-name atm-options vpi vpi-identifier],
[edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-name unit logical-unit-number address address family family
multipoint-destination address],
[edit logical-systems logical-system-name interfaces interface-name unit lo... | For Circuit Emulation PICs, specify traffic shaping in the ingress and egress directions.
VP tunnels are not supported on multipoint interfaces.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Defining Virtual Path Tunnels"
] |
shaping-rate (Applying to an Interface) | shaping-rate rate; | [edit class-of-service interfaces interface-name],
[edit class-of-service interfaces interface-name unit logical-unit-number] | For logical interfaces on which you configure packet scheduling, configure traffic shaping by specifying
the amount of bandwidth to be allocated to the logical interface. Applying a shaping rate can help
ensure that higher-priority services do not starve lower-priority services.
For physical interfaces, by default, sha... | [
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps). You can specify a value in bits per second either as a complete decimal number or as a decimal number followed by the abbreviation k (1000), m (1,000,000), or g (1,000,000,000). Range: 1000 through 6,400,000,000,000 bps. NOTE: For all MX Serie... | 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.
[edit class-of-service interfaces interface-name] hierarchy level added in Junos OS Release 7.5. | [
"Applying Scheduler Maps Overview",
"Configuring Virtual LAN Queuing and Shaping on PTX Series Routers",
"CoS Port Shaping"
] |
shaping-rate (CoS Adaptive Shapers) | shaping-rate (percent percentage | rate); | [edit class-of-service adaptive-shapers adaptive-shaper-name trigger type] | Define the list of trigger types and associated rates. | [
{
"name": "percent percentage",
"desc": "Shaping rate as a percentage of the available interface bandwidth."
},
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps). You can specify a value in bits per second either as a"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [] |
shaping-rate (CoS Interfaces) | shaping-rate rate <overhead bytes> ; | [edit class-of-service interfaces interface-name],
[edit class-of-service interfaces interface-name unit logical-unit-number] | For logical interfaces on which you configure packet scheduling, configure traffic shaping by specifying
the amount of bandwidth to be allocated to the logical interface.
Logical and physical interface traffic shaping can be configured together. This means you can include the
shaping-rate statement at the [edit class-o... | [
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps). You can specify a value in bits per second either as a complete decimal number or as a decimal number followed by the abbreviation k (1000), m (1,000,000), or g (1,000,000,000). Range: 1000 through 6,400,000,000,000 bps"
},
{
"name": "... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
overhead option introduced in Junos OS Release 18.1.
Platform-Specific Behavior
Use Feature Explorer to confirm platform and release support for specific features.
Use the following table to review platform-specific behavior for your platforms:
Platform
Difference
MX Serie... | [] |
shaping-rate (CoS Virtual Channels) | shaping-rate (percent percentage | rate); | [edit class-of-service virtual-channel-groups group-name virtual-channel-name] | Define the shaping rates to be associated with the virtual channel. | [
{
"name": "percent percentage",
"desc": "Shaping rate as a percentage of the available interface bandwidth."
},
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps). You can specify a value in bits per second either as a"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [] |
shaping-rate (Dynamic Traffic Shaping and Scheduling) | shaping-rate (rate | predefined-variable) <burst-size bytes | $junos-cos-shaping-rate-burst>; | [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name],
[edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] | Configure a shaping rate for a logical interface or a scheduler. The sum of the shaping rates for all logical
interfaces on the physical interface can exceed the physical interface bandwidth. This practice is known
as oversubscription of the peak information rate (PIR). | [
{
"name": "rate",
"desc": "Peak rate in bits per second (bps). You can specify the value as a complete decimal number or as a"
},
{
"name": "predefined-variable",
"desc": "One of the following Junos predefined variables. The variable is replaced with a value"
},
{
"name": "$junos-cos-sha... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
The $junos-cos-shaping-rate variable for traffic-control profiles introduced in Junos OS Release 9.4.
The $junos-cos-scheduler-shaping-rate variable for schedulers introduced in Junos OS Release 10.2.
Option burst-size introduced in Junos OS Release 11.4. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Traffic Scheduling and Shaping for Subscriber Access"
] |
shaping-rate (Oversubscribing an Interface) | shaping-rate (percent percentage | rate) <burst-size bytes>; | [edit class-of-service traffic-control-profiles profile-name] | Configure a shaping rate for a logical interface. On some interfaces, you can also configure an optional
burst size for a logical interface. This can help to ensure that higher-priority services do not starve
lower-priority services.
For physical interfaces on PTX Series routers, configure traffic shaping rate.
The sum... | [
{
"name": "percent",
"desc": ""
},
{
"name": "percentage",
"desc": "Shaping rate as a percentage of the available interface bandwidth. Range: 1 through 100 percent"
},
{
"name": "rate",
"desc": "Peak shaping rate, in bits per second (bps). You can specify a value in bits per second ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6.
Option burst-size introduced in Junos OS Release 9.4.
NOTE: Option burst-size is not supported on MPC5 interfaces. The burst-size
configuration is allowed on these interfaces, but does not take effect.
Statement introduced for PTX Series Packet Transport Routers in Junos O... | [
"Configuring Traffic Control Profiles for Shared Scheduling and Shaping",
"Oversubscribing Interface Bandwidth"
] |
shaping-rate (Schedulers) | shaping-rate (percent percentage | rate) <burst-size bytes>; | [edit class-of-service schedulers scheduler-name] | Define a limit on bandwidth usage for a forwarding class/queue.
The transmit-rate statement at the [edit class-of-service schedulers scheduler-name] hierarchy level
configures the minimum bandwidth allocated to a queue. The transmission bandwidth can be configured
as an exact value or allowed to exceed the configured r... | [
{
"name": "percent",
"desc": ""
},
{
"name": "percentage",
"desc": "Shaping rate as a percentage of the available interface bandwidth. Range: 0 through 100 percent NOTE: If you configure a shaping rate as a percent in a scheduler, the effective shaping rate is calculated based on the following ... | 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.
The burst-size option added in Junos OS Release 11.4. | [
"Applying Scheduler Maps Overview"
] |
shaping-rate (Traffic Control Profiles) | shaping-rate (rate | percent percentage); | [edit class-of-service traffic-control-profiles profile-name]
NOTE: Only devices that support enhanced transmission selection (ETS) or hierarchical
scheduling support the traffic-control-profiles hierarchy. | Configure the shaping rate. The shaping rate throttles the rate of packet transmission by setting a
maximum bandwidth (rate in bits per second) or a maximum percentage of bandwidth for a queue or a
forwarding class set. You specify the maximum bandwidth for a queue by using a scheduler map to
associate a forwarding cla... | [
{
"name": "percent percentage",
"desc": "Shaping rate as a percentage of the available interface bandwidth."
},
{
"name": "rate",
"desc": "Peak (maximum) rate, in bits per second (bps). You can specify a value in bits per second either as a"
}
] | 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. | [
"Example: Configuring CoS Hierarchical Port Scheduling (ETS)",
"Example: Configuring Queue Schedulers",
"Example: Configuring Queue Schedulers for Port Scheduling",
"Example: Configuring Traffic Control Profiles (Priority Group Scheduling)",
"Understanding CoS Output Queue Schedulers",
"Understanding CoS ... |
shaping-rate-excess-high | shaping-rate-excess-high (percent percentage | rate) <burst-size bytes>; | [edit class-of-service traffic-control-profiles profile-name],
[edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | For MIC and MPC interfaces on MX Series routers, configure a shaping rate and optional burst size for
high-priority excess traffic. This can help to make sure higher priority services do not starve lower
priority services.
NOTE: Option burst-size is not supported on MPC5 interfaces. The burst-size
configuration is allo... | [
{
"name": "percent percentage",
"desc": "Specify the shaping rate as a percentage of the overall shaping rate."
},
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps). You can specify a value in bits per second either as a complete"
},
{
"name": "burst-size bytes",
"desc":... | 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.
percent option added in Junos OS Release 19.3R1. | [
"Per-Priority Shaping on MIC and MPC Interfaces Overview",
"Oversubscribing Interface Bandwidth",
"Configuring Traffic Control Profiles for Shared Scheduling and Shaping"
] |
shaping-rate-excess-low | shaping-rate-excess-low (percent percentage | rate) <burst-size bytes>; | [edit class-of-service traffic-control-profiles profile-name],
[edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | For MIC and MPC interfaces on MX Series routers, configure a shaping rate and optional burst size for
low-priority excess traffic. This can help to make sure higher priority services do not starve lower
priority services.
NOTE: Option burst-size is not supported on MPC5 interfaces. The burst-size
configuration is allow... | [
{
"name": "percent percentage",
"desc": "Specify the shaping rate as a percentage of the overall shaping rate."
},
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps). You can specify a value in bits per second either as a complete"
},
{
"name": "burst-size bytes",
"desc":... | 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.
percent option added in Junos OS Release 19.3R1. | [
"Per-Priority Shaping on MIC and MPC Interfaces Overview",
"Oversubscribing Interface Bandwidth",
"Configuring Traffic Control Profiles for Shared Scheduling and Shaping"
] |
shaping-rate-excess-medium-high | shaping-rate-excess-medium-high (percent percentage | rate) <burst-size bytes>; | [edit class-of-service traffic-control-profiles profile-name],
[edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | For MPCs (MPC7E-MRATE, MPC7E-10G, MPC8E, and MPC9E) interfaces on MX Series routers,
configure a shaping rate and optional burst size for medium-high-priority excess traffic. This can help to
make sure higher priority services do not starve lower priority services.
Default
If you do not include this statement, the defa... | [
{
"name": "percent percentage",
"desc": "Specify the shaping rate as a percentage of the overall shaping rate."
},
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps). You can specify a value in bits per second either as a complete"
},
{
"name": "burst-size bytes",
"desc":... | 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.
percent option added in Junos OS Release 19.3R1. | [
"Per-Priority Shaping on MIC and MPC Interfaces Overview",
"Oversubscribing Interface Bandwidth",
"Configuring Traffic Control Profiles for Shared Scheduling and Shaping"
] |
shaping-rate-excess-medium-low | shaping-rate-excess-medium-low (percent percentage | rate) <burst-size bytes>; | [edit class-of-service traffic-control-profiles profile-name],
[edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | For MPC7E-MRATE, MPC7E-10G, MPC8E, and MPC9E interfaces on MX Series routers, configure a
shaping rate and optional burst size for medium-low-priority excess traffic. This can help to make sure
higher priority services do not starve lower priority services.
Default
If you do not include this statement, the default shap... | [
{
"name": "percent percentage",
"desc": "Specify the shaping rate as a percentage of the overall shaping rate."
},
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps). You can specify a value in bits per second either as a complete"
},
{
"name": "burst-size bytes",
"desc":... | 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.
percent option added in Junos OS Release 19.3R1. | [
"Per-Priority Shaping on MIC and MPC Interfaces Overview"
] |
shaping-rate-priority-high | shaping-rate-priority-high (percent percentage | rate) <burst-size bytes>; | [edit class-of-service traffic-control-profiles profile-name],
[edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | For MIC and MPC interfaces on MX Series routers, configure a shaping rate and optional burst size for
high priority traffic. This can help to make sure higher priority services do not starve lower priority
services.
NOTE: Option burst-size is not supported on MPC5 interfaces. The burst-size
configuration is allowed on ... | [
{
"name": "percent percentage",
"desc": "Specify the shaping rate as a percentage of the overall shaping rate."
},
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps). You can specify a value in bits per second either as a complete"
},
{
"name": "burst-size bytes",
"desc":... | 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.
percent option added in Junos OS Release 19.3R1. | [
"Per-Priority Shaping on MIC and MPC Interfaces Overview",
"Oversubscribing Interface Bandwidth",
"Configuring Traffic Control Profiles for Shared Scheduling and Shaping"
] |
shaping-rate-priority-low | shaping-rate-priority-low (percent percentage | rate) <burst-size bytes>; | [edit class-of-service traffic-control-profiles profile-name],
[edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | For MIC and MPC interfaces on MX Series routers, configure a shaping rate and optional burst size for
low priority traffic. This can help to make sure higher priority services do not starve lower priority
services.
NOTE: Option burst-size is not supported on MPC5 interfaces. The burst-size
configuration is allowed on t... | [
{
"name": "percent percentage",
"desc": "Specify the shaping rate as a percentage of the overall shaping rate."
},
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps). You can specify a value in bits per second either as a complete"
},
{
"name": "burst-size bytes",
"desc":... | 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.
percent option added in Junos OS Release 19.3R1. | [
"Per-Priority Shaping on MIC and MPC Interfaces Overview",
"Oversubscribing Interface Bandwidth",
"Configuring Traffic Control Profiles for Shared Scheduling and Shaping"
] |
shaping-rate-priority-medium | shaping-rate-priority-medium (percent percentage | rate) <burst-size bytes>; | [edit class-of-service traffic-control-profiles profile-name],
[edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | For MIC and MPC interfaces on MX Series routers, configure a shaping rate and optional burst size for
medium priority traffic. This can help to make sure higher priority services do not starve lower priority
services.
NOTE: Option burst-size is not supported on MPC5 interfaces. The burst-size
configuration is allowed o... | [
{
"name": "percent percentage",
"desc": "Specify the shaping rate as a percentage of the overall shaping rate."
},
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps). You can specify a value in bits per second either as a complete"
},
{
"name": "burst-size bytes",
"desc":... | 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.
percent option added in Junos OS Release 19.3R1. | [
"Per-Priority Shaping on MIC and MPC Interfaces Overview",
"Oversubscribing Interface Bandwidth",
"Configuring Traffic Control Profiles for Shared Scheduling and Shaping"
] |
shaping-rate-priority-medium-low | shaping-rate-priority-medium-low (percent percentage | rate) <burst-size bytes>; | [edit class-of-service traffic-control-profiles profile-name],
[edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | For MPC7E-MRATE, MPC7E-10G, MPC8E, and MPC9E interfaces on MX Series routers, configure a
shaping rate and optional burst size for medium-low priority traffic. This can help to make sure higher
priority services do not starve lower priority services.
Default
If you do not include this statement, the default shaping rat... | [
{
"name": "percent percentage",
"desc": "Specify the shaping rate as a percentage of the overall shaping rate."
},
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps). You can specify a value in bits per second either as a complete"
},
{
"name": "burst-size bytes",
"desc":... | 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.
percent option added in Junos OS Release 19.3R1. | [
"Per-Priority Shaping on MIC and MPC Interfaces Overview"
] |
shaping-rate-priority-strict-high | shaping-rate-priority-strict-high (percent percentage | rate) <burst-size bytes>; | [edit class-of-service traffic-control-profiles profile-name],
[edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | For MPC7E-MRATE, MPC7E-10G, MPC8E, and MPC9E interfaces on MX Series routers, configure a
shaping rate and optional burst size for strictly high priority traffic. This can help to make sure higher
priority services do not starve lower priority services.
Default
If you do not include this statement, the default shaping ... | [
{
"name": "percent percentage",
"desc": "Specify the shaping rate as a percentage of the overall shaping rate."
},
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps). You can specify a value in bits per second either as a complete"
},
{
"name": "burst-size bytes",
"desc":... | 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.
percent option added in Junos OS Release 19.3R1. | [
"Per-Priority Shaping on MIC and MPC Interfaces Overview"
] |
shared-bandwidth-policer (Configuring) | shared-bandwidth-policer; | [edit firewall policer policer-name],
[edit firewall three-color-policer policer-name],
[edit firewall hierarchical-policer policer-name] | Policer instances share bandwidth. This enables configuration of interface-specific policers applied on an
aggregated Ethernet bundle or an aggregated SONET bundle to match the effective bandwidth and
burst-size to user-configured values. This feature is supported on the following platforms: T Series
routers, M120, M10... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2.
Support for MX Series MPC and MIC interfaces added in Junos OS Release 12.1. | [
"Policer Support for Aggregated Ethernet Interfaces Overview"
] |
shared-buffer | shared-buffer {
egress {
buffer-partition (lossless | lossy | multicast) {
percent percent;
dynamic-threshold threshold-value;
}
percent percent;
}
ingress {
percent percent;
buffer-partition (lossless | lossless-headroom | lossy) {
... | [edit class-of-service] | Configure the global shared buffer pool allocation to ports. Shared buffers are a pool of buffer space that
the system can allocate dynamically across all of its ports as memory space is needed. Some buffer
space is reserved for dedicated buffers (buffers allocated permanently to ports), headroom buffers
(buffers that ... | [] | 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. | [
"Example: Recommended Configuration of the Shared Buffer Pool for Networks with Mostly Best-",
"Effort Unicast Traffic",
"Example: Recommended Configuration of the Shared Buffer Pool for Networks with Mostly Multicast",
"Traffic",
"Example: Recommended Configuration of the Shared Buffer Pool for Networks wi... |
shared-instance | shared-instance instance-name; | [edit class-of-service interfaces interface-name unit logical-unit-number input-traffic-control-
profile],
[edit class-of-service interfaces interface-name unit logical-unit-number output-traffic-control-
profile] | For Gigabit Ethernet IQ2 and IQ2E PICs only, apply a shared traffic scheduling and shaping profile to the
logical interface. | [
{
"name": "instance-name",
"desc": "Name of the shared scheduler and shaper to be applied to this interface"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring Shaping on 10-Gigabit Ethernet IQ2 PICs"
] |
shared-key | shared-key value; | [edit services dynamic-flow-capture capture-group client-name control-source identifier] | Configure the authentication key value. | [
{
"name": "value",
"desc": "Secret authentication value shared between a control source and destination."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring the Control Source"
] |
shared-name | shared-name filter-shared-name; | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family filter input filter-name],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family filter output filter-name],
[edit dynamic-profiles profile-name interfaces interface-name... | Apply a filter shared name to a dynamic filter. | [
{
"name": "filter-shared-name",
"desc": "Name of the specific shared filter or $junos-interface-set-name."
}
] | 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. | [
"Guidelines for Configuring Firewall Filters",
"Understanding Dynamic Firewall Filters",
"Classic Filters Overview",
"Basic Classic Filter Syntax"
] |
shared-scheduler | shared-scheduler; | [edit interfaces interface-name] | For Gigabit Ethernet IQ2 PICs only, enable shared schedulers and shapers on this interface. This
statement and the per-unit-scheduler statement are mutually exclusive. Even so, you can configure one
logical interface for each shared instance. This effectively provides the functionality of per-unit
scheduling.
For Gigab... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring Traffic Control Profiles for Shared Scheduling and Shaping",
"Configuring Shaping on 10-Gigabit Ethernet IQ2 PICs",
"Configuring Shared Scheduling on Aggregated Ethernet Interfaces"
] |
shared-secret (RADIUS Snoop Segment) | shared-secret secret; | [edit access radius snoop-segments segment-name] | Configure a shared secret to be used by the MX Series router and the RADIUS client. If the shared
secrets do not match, the subscriber session is not set up. | [
{
"name": "secret",
"desc": "Shared secret. The maximum length is 64 characters."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring Snooping of RADIUS Accounting Requests for IP-Based Subscribers",
"Snooping RADIUS Accounting Requests for IP-Based Subscribers Overview",
"IP-Based Subscriber Setup Overview"
] |
shdsl-options | shdsl-options {
annex (annex-a | annex-b);
line-rate line-rate;
loopback (local | remote | payload);
snr-margin {
snext margin;
}
} | [edit interfaces interface-name],
[edit logical-systems logical-system-name interfaces interface-name | For J Series Services Routers only, configure symmetric DSL (SHDSL) options.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [] |
shell | shell | [edit system syslog (System)] | Configure the logging of commands executed from the shell.
Additional Information
To log command executed from the shell configure shell logging by including the system syslog shell
statement at the [edit] hierarchy.
[edit]
user@host# set system syslog shell
By default log entries are written to the messages log file.
... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.1R1.
Statement introduced in Junos OS Release 23.4R1. | [] |
shellcode | shellcode (all | intel | no-shellcode | sparc); | [edit security idp custom-attack attack-name attack-type anomaly],
[edit security idp custom-attack attack-name attack-type signature] | Shellcode signifies that the attack is a shellcode attack and is capable of creating its own shell. | [
{
"name": "all",
"desc": "All shellcode checks will be performed if this attack matches."
},
{
"name": "intel",
"desc": "Basic shellcode checks and Intel-specific shellcode checks will be performed."
},
{
"name": "no-shellcode",
"desc": "No shellcode checks will be performed."
},
... | 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. | [] |
shmlog (Shared Memory Log) | shmlog {
disable;
file filename <files maximum-no-files> <size maximum-file-size>;
filtering enable;
log-name {
all;
logname {
<brief | detail | extensive | none | terse>;
<file-logging |no-file-logging>;
}
}
log-type (debug | info | notice);
| | [edit system services subscriber-management overrides] | Junos OS uses a shared memory space to store log entries for subscriber service daemons including
jpppd, jdhcpd, jl2tpd, autoconfd, bbe-smgd, authd, cosd, and dfwd. Shared memory logging is enabled by
default and occurs at the client level. You can view the shmlogs on a per subscriber basis, or use filters
to retrieve ... | [
{
"name": "disable",
"desc": "Name of the command to override the default behavior. Use this option to disable shared memory logging; it is always enabled otherwise."
},
{
"name": "file",
"desc": "Name of the file containing the shmlogs. Use this option to redirect shmlogs to a file for file-bas... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [] |
short-cycle-protection (DHCP Local Server and Relay Agent) | short-cycle-protection <lockout-max-time seconds> <lockout-min-time seconds>; | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit forwarding-options dhcp-relay dhcpv6 group group-name],
[edit forwarding-options dhcp-relay dhcpv6 group group-name interface interface-name],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name],
[edit forwa... | Enable DHCP short-cycle protection to reduce resource usage associated with connection and
authentication processing in highly scaled networks. You must configure both the minimum duration and
the maximum duration for the lockout period.
The router detects short-lived client sessions and clients that repeatedly fail se... | [
{
"name": "lockout-max-time seconds",
"desc": "Maximum length of any lockout period; the upper bound of the lockout range. Range: 1 through 86400"
},
{
"name": "lockout-min-time seconds",
"desc": "Minimum length of any lockout period; the lower bound of the lockout period. The minimum value is ... | interface | Statement introduced in Junos OS Release 18.2R1. | [
"Configuring DHCP Short-Cycle Protection",
"DHCP Short Cycle Protection Against Frequent Brief or Failed Client Sessions"
] |
short-cycle-protection (Static and Dynamic Subscribers) | short-cycle-protection <lockout-time-min minimum-seconds> <lockout-time-max maximum-seconds>
<filter [aci]> ; | [edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family pppoe],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
pppoe],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number pppoe-
underlying-options],
[edit in... | Configure the router to temporarily prevent (lock out) a failed or short-lived (also known as short-cycle)
PPPoE subscriber session from reconnecting for a default or configurable period of time. You can
optionally override the default lockout time, 1 through 300 seconds (5 minutes), by specifying the
minimum lockout t... | [
{
"name": "filter aci",
"desc": "(Optional) Use the agent circuit identifier (ACI) lockout for all subscriber sessions."
},
{
"name": "lockout-time-min minimum-seconds",
"desc": "(Optional) Use the specified minimum lockout time for failed or short-lived PPPoE subscriber sessions. The minimum-se... | 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 Lockout of PPPoE Subscriber Sessions",
"PPPoE Subscriber Session Lockout Overview",
"Understanding the Lockout Period for PPPoE Subscriber Session Lockout",
"Configuring Dynamic PPPoE Subscriber Interfaces",
"Example: Configuring a Static PPPoE Subscriber Interface on a Static Underlying VLAN D... |
short-name-format | short-name-format (character-string | vlan | 2octet | rfc-2685-vpn-id); | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name] | Specify the name format of the maintenance association name. | [
{
"name": "character-string",
"desc": "The name is an ASCII character string."
},
{
"name": "vlan",
"desc": "The primary VLAN identifier."
},
{
"name": "2octet",
"desc": "A number in the range 0 through 65,535."
},
{
"name": "rfc-2685-vpn-id",
"desc": "A VPN identifier th... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [
"Configuring Connectivity Fault Management (CFM)"
] |
short-reach-mode | short-reach-mode (enable | disable); | [edit chassis fpc fpc-slot pic pic-slot],
[edit chassis fpc fpc-slot pic pic-slot port-range port-range-low port-range-high] | Configure short-reach mode for individual as well as a range of copper-based 10-Gigabit Ethernet
interfaces using short cable lengths (less than 10m) on the QFX5100-48T switch. Short-reach mode
reduces power consumption up to 5W on these interfaces.
Default
This feature is disabled by default. | [
{
"name": "enable",
"desc": ""
},
{
"name": "disable",
"desc": ""
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D30. | [
"Physical Interface Properties"
] |
short-sequence | short-sequence; | [edit interfaces (ls-fpc/pic/port | ml-fpc/pic/port) unit logical-unit-number],
[edit logical-systems logical-system-name interfaces (ls-fpc/pic/port | ml-fpc/pic/port) unit
logical-unit-number] | For multilink interfaces only, set the length of the packet sequence identification number to 12 bits.
Default
If not included in the configuration, the length is set to 24 bits. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Sequence Header Format on Multilink and Link Services Logical Interfaces"
] |
shortcuts (Protocols OSPF) | shortcuts {
lsp-metric-into-summary;
} | [edit logical-systems logical-system-name protocols (ospf | ospf3) traffic-engineering],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(ospf | ospf3) traffic-engineering],
[edit protocols (ospf | ospf3) traffic-engineering],
[edit routing-instances routing-instance-name pr... | Configure OSPF to use MPLS label-switched paths (LSPs) as shortcut next hops. By default, shortcut
routes calculated through OSPFv2 are installed in the inet.3 routing table, and shortcut routes calculated
through OSPFv3 are installed in the inet6.3 routing table. | [
{
"name": "lsp-metric-into-summary",
"desc": "Advertise the LSP metric in summary LSAs."
}
] | 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 OSPFv3 (ospf3) introduced in Junos OS Release 9.4.
Support for OSPFv3 (ospf3) introduced in Junos OS Release 9.4 for EX Series switches. | [
"Example: Enabling OSPF Traffic Engineering Support"
] |
should-secure | should-secure; | [edit security macsec connectivity-association connectivity-association-name mka] | Configure the should-secure statement to enable fail open mode for Media Access Control Security
(MACsec). Fail open mode ensures that traffic continues to flow if the MACsec Key Agreement (MKA)
session is not established.
When should-secure is configured:
•
If the MKA session is not established, traffic is still allow... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4. | [
"Configuring Advanced MACsec Features"
] |
show | display commit-scripts | show | display commit-scripts
<no-transients | view> | Show data after commit scripts have been applied. Commit scripts contain instructions that enforce
custom configuration rules and are invoked during the commit process before the standard Junos OS
validity checks are performed. | [
{
"name": "no-transients",
"desc": "Do not display transient changes in the configuration."
},
{
"name": "view",
"desc": "Display commit-script-style xml data. Display XML format of the post-inheritance candidate configuration in the CLI."
}
] | view
Sample Output
show system login | display commit-scripts view
user@host# show system login | display commit-scripts view<rpc-reply xmlns:junos="http://
xml.juniper.net/junos/23.1R0/junos">
<configuration junos:changed-seconds="1682095681" junos:changed-localtime="2023-04-21
09:48:01 PDT" junos:changed="change... | Command introduced in Junos OS Release 7.4. | [
"How Commit Scripts Work"
] | |
show | display inheritance | show | display inheritance
<brief | no-comments | terse>
<defaults>
<when> | Show the inherited configuration data and information about the source group from which the
configuration has been inherited. Show interface ranges configuration data in expanded format and
information about the source interface-range from which the configuration has been expanded. | [
{
"name": "brief",
"desc": "Display brief output for the command."
},
{
"name": "defaults",
"desc": "Display the defaults that have been applied to the configuration."
},
{
"name": "no-comments",
"desc": "Display configuration information without in-line comments marked with ##."
}... | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
show system login class readonly | display inheritance
user@host#show system login class readonly | display inheritance
##
## 'interface' was inherited from group 'global'
## 'network' was inherited fr... | Command introduced before Junos OS Release 7.4. | [
"Using the junos-defaults Configuration Group"
] | |
show | display json | show | display json
<groups | interface-ranges | no-export-path> | Show output in JavaScript Object Notation (JSON) format. Devices running Junos OS support JSON
representation of the operational command output and the Junos OS configuration hierarchy. On the
Junos OS CLI, to display the command output or configuration in JSON instead of in the default
formatted ASCII text, append the... | [
{
"name": "groups",
"desc": "Tag inherited data with the source group name."
},
{
"name": "interface-ranges",
"desc": "Tag inherited data with the source interface-range name"
},
{
"name": "no-export-path",
"desc": "Do not export parent path in the data."
}
] | view
Sample Output
show chassis hardware | display json
user@host# show chassis hardware | display json
{
"chassis-inventory" : [
{
"attributes" : {
"xmlns" : "http://xml.juniper.net/junos/16.1R1/junos-chassis"
},
"chassis" : [
{
"attributes" : {"junos:st... | Command introduced in Junos OS Release 14.2R1 | [
"Map Junos OS Command Output to JSON in the CLI"
] | |
show | display omit | show | display omit | Display configuration statements (including those marked as hidden by the apply-flags omit configuration
statement).
user@host# show | display omit
system {
apply-flags omit;
login {
message lengthy-login-message;
}
}
Following is an example that shows ho... | [] | view | Command introduced in Junos OS Release 8.2. | [] | |
show | display rfc5952 | show | display rfc5952 | Display IPv6 addresses as per RFC 5952 specifications. For RFC information, go to: http://tools.ietf.org/
html/rfc5952. | [] | View
Sample Output
command-name
user@host> show configuration interfaces ge-0/0/0 |display rfc5952
unit 0 {
family inet6 {
address 2012::2:1/64;
address 2001::1111:2222:0:0:1/96;
}
} | Command introduced before Junos OS Release 11.4. | [] | |
show | display set relative | show | display set relative <explicit> | Display the configuration as a series of configuration mode commands required to re-create the
configuration from the current hierarchy level. | [
{
"name": "explicit",
"desc": "Display explicitly, as a series of commands, all the configurations that the system internally creates when you configure certain statements from the current hierarchy level."
}
] | view
Sample Output
Sample output for the show | display set relative <explicit> command:
[edit interfaces fe-0/0/0]
user@host# show
unit 0 {
family inet {
address 192.107.1.230/24;
}
family iso;
family mpls;
}
inactive: unit 1 {
family inet {
address 10.0.0.1/8;
}
}
user@host# show | display set relative
set unit 0 fam... | Command introduced before Junos OS Release 7.4.
Option explicit command introduced in Junos OS Release 20.1R1. | [
"Displaying set Commands from the Device Configuration"
] | |
show | display set | show | display set <explicit> <relative> | Display the configuration as a series of configuration mode commands required to re-create the
configuration from the top level of the hierarchy as set commands. | [
{
"name": "explicit",
"desc": "Display explicitly, as a series of set commands, all the configuration statements that the system internally creates when you configure certain statements from the top level of the hierarchy. For example, assume you issue the set interfaces ge-0/0/0.0 family inet configuration... | view
Sample Output
Sample output for the show | display set and show | display set <explicit> commands:
[edit interfaces ge-0/0/0]
user@host# show | display set
set interfaces ge-0/0/0 unit 0 family inet address 10.0.1.254/24
[edit interfaces ge-0/0/0]
user@host# show | display set explicit
set interfaces ge-0/0/0 un... | Command introduced before Junos OS Release 7.4.
Option explicit command introduced in Junos OS Release 20.1R1. | [
"Displaying set Commands from the Device Configuration"
] | |
show | display translation-scripts | show | display tanslation-scripts
<configured-delta | translated-config | translated-delta> | Show data after translation scripts have been applied. Translation scripts convert the configuration data
corresponding to the nonnative data models into Junos OS syntax and add the translated configuration
data as a transient change in the checkout configuration during the commit operation. | [
{
"name": "configured-delta",
"desc": "Display the input configuration to the translation script."
},
{
"name": "translated-config",
"desc": "Display the translated configuration."
},
{
"name": "translated-delta",
"desc": "Display the output configuration from the translation script.... | view
Sample Output
show display | translation-scripts
The following truncated output displays the complete post-inheritance configuration and includes the
nonnative configuration data as well as the translation of that data.
user@host>show display | translation-scripts
## Last changed: 2016-05-13 16:37:42 PDT
vers... | Command introduced in Junos OS Release 16.1R1 | [
"Committing and Displaying Configuration Data for Nonnative YANG Modules"
] | |
show | display xml | show | display xml <groups | interface-ranges | no-export-path> | Show output as XML tags. On the Junos OS CLI, to display command output as Junos XML tag elements
instead of as the default formatted ASCII text, include the | display xml option after the command. | [
{
"name": "groups",
"desc": "Tag inherited data with the source group name."
},
{
"name": "interface-ranges",
"desc": "Tag inherited data with the source interface-range name"
},
{
"name": "no-export-path",
"desc": "Do not export parent path in the data."
}
] | view
Sample Output
show interfaces | display xml
user@host> show interfaces | display xml
<rpc-reply xmlns:junos="http://xml.juniper.net/junos/23.1R0/junos">
<rpc-reply xmlns:junos=http://xml.juniper.net/junos/21.1R0/junos>
<configuration junos:changed-seconds="1682580061" junos:changed-localtime="2023-04-27
07:21... | Command introduced before Junos OS Release 7.4. | [
"Map Junos OS Commands and Command Output to Junos XML Tag Elements"
] | |
show | display | show | display <changed | commit-scripts |detail | inheritance | json | mark-changed | max-depth
depth | max-version version | omit | set | translation-scripts | xml> | Display the configuration as a series of configuration mode commands required to re-create the
configuration from the top level of the hierarchy. | [
{
"name": "changed",
"desc": "Tag changes with junos:changed attribute (XML only)."
},
{
"name": "commit-scripts",
"desc": "Show data after commit scripts have been applied."
},
{
"name": "detail",
"desc": "Show configuration data detail."
},
{
"name": "inheritance",
"des... | view
Sample Output
show | display max-depth
user@host# show interfaces | display max-depth 3
ge-0/0/0 {
unit 0 {
family inet {
address 10.1.12.1/24;
}
}
}
user@host# show interfaces | display max-depth 2
ge-0/0/0 {
unit 0 {
family inet { ... }
}
}
user@host# show ... | Command introduced before Junos OS Release 7.4. | [] | |
show (ospf | ospf3) backup coverage | show (ospf | ospf3) backup coverage
<instance instance-name>
<topology topology-name> | Display information about the level of backup coverage available for all the nodes and prefixes in the
network. | [
{
"name": "none",
"desc": "Display information about the level backup coverage for all OSPF routing instances in all logical systems."
},
{
"name": "logical-system (all |",
"desc": ""
},
{
"name": "logical-system-name)",
"desc": "(Optional) Display information about the level of back... | view
Output Fields
Table 162 on page 17639 lists the output fields for the show (ospf | ospf3) backup coverage command.
Output fields are listed in the approximate order in which they appear.
Table 162: show (ospf | ospf3) backup coverage Output Fields
Field Name
Field Description
rmorn, June 2020: Uplift
project, gen... | Command introduced in Junos OS Release 10.0. | [] | |
show (ospf | ospf3) backup lsp | show (ospf | ospf3) backup lsp
<logical-system (all | logical-system-name>
<realm (ipv4-unicast | ipv6-unicast)> | Display information about MPLS label-switched-paths (LSPs) designated as backup routes for OSPF
routes.
NOTE: MPLS LSPs can be used as backup routes only for routes in the default OSPFv2
topology and not for any configured topology. Additionally, MPLS LSPs cannot be used
as backup routes for nondefault instances either... | [
{
"name": "none",
"desc": "Display information all MPLS LSPs designated as backup routes."
},
{
"name": "logical-system (all |",
"desc": ""
},
{
"name": "logical-system-name)",
"desc": "(Optional) Display information about MPLS LSPs designated as backup routes for all logical systems... | view
Output Fields
Table 163 on page 17642 lists the output fields for the show (ospf | ospf3) backup lsp command. Output
fields are listed in the approximate order in which they appear.
Table 163: show (ospf | ospf3) backup lsp Output Fields
Field Name
Field Description
MPLS LSP name
Name of each MPLS LSP designated a... | Command introduced in Junos OS Release 10.0. | [] | |
show (ospf | ospf3) backup neighbor | show (ospf | ospf3) backup neighbor
<area area-id>
<instance instance-name>
<topology (default | ipv4-multicast | topology-name)> | Display the neighbors through which direct next hops for the backup paths are available. | [
{
"name": "none",
"desc": "Display all neighbors that have direct next hops for backup paths."
},
{
"name": "area area-id",
"desc": "(Optional) Display the area information."
},
{
"name": "instance (default | instance-name)",
"desc": "(Optional) Display information about the default ... | view
Output Fields
Table 164 on page 17645 lists the output fields for the show (ospf |ospf3) backup neighbor command.
Output fields are listed in the approximate order in which they appear.
Table 164: show (ospf |ospf3) backup neighbor Output Fields
Field Name
Field Description
Level of Output
Neighbor to Self
Metric
... | Command introduced in Junos OS Release 10.0. | [] | |
show (ospf | ospf3) backup spf | show (ospf | ospf3) backup spf
<brief | detail>
<area area-id>
<instance instance-name>
<no-coverage>
<node-id>
<topology (default | ipv4-multicast | topology-name)> | Display information about OSPF shortest-path-first calculations for backup paths. | [
{
"name": "none",
"desc": "Display information about OSPF shortest-path-first (SPF) calculations for all backup paths for all destination nodes."
},
{
"name": "brief | detail",
"desc": "(Optional) Display the specified level of output."
},
{
"name": "area area-id",
"desc": "(Optional... | view
Output Fields
Table 165 on page 17648 lists the output fields for the show (ospf |ospf3) backup spf command. Output
fields are listed in the approximate order in which they appear.
Table 165: show (ospf |ospf3) backup spf Output Fields
Field Name
Field Description
Level of Output
Area area-id
results
Area for whic... | Command introduced in Junos OS Release 10.0. | [] | |
show (ospf | ospf3) bgp-orr | show (ospf | ospf3) bgp-orr
<abr>
<asbr>
<brief | detail | extensive>
<extern>
<group group-name>
<instance instance-name>
<inter>
<intra>
<logical-system (all | logical-system-name)>
<network>
<router>
<topology> | Display information about OSPF BGP-ORR metric (RIB). | [
{
"name": "none",
"desc": "Display group information about all OSPF BGP groups."
},
{
"name": "abr",
"desc": "(Optional) Display OSPF routes to area border routers."
},
{
"name": "asbr",
"desc": "(Optional) Display OSPF routes to autonomous systems border routers."
},
{
"name... | view
Output Fields
Table 166 on page 17652 describes the output fields for the show ospf bgp-orr command. Output fields
are listed in the approximate order in which they appear.
Table 166: show bgp group Output Fields
Field Name
Field Description
Level of
Output
BGP ORR Peer Group
Name of the BGP ORR peer group.
All le... | Command introduced in Junos OS Release 16.2. | [] | |
show (ospf | ospf3) interface | show (ospf | ospf3) interface
<brief | detail | extensive>
<area area-id>
<interface-name>
<instance instance-name> | Display the status of OSPF interfaces. | [
{
"name": "none",
"desc": "Display standard information about the status of all OSPF interfaces for all"
},
{
"name": "routing instances",
"desc": ""
},
{
"name": "brief | detail | extensive",
"desc": "(Optional) Display the specified level of output."
},
{
"name": "area area... | view
Output Fields
Table 167 on page 17656 lists the output fields for the show (ospf | ospf3) interface command. Output
fields are listed in the approximate order in which they appear.
Table 167: show (ospf | ospf3) interface Output Fields
Field Name
Field Description
Level of Output
Interface
Name of the interface r... | Command introduced before Junos OS Release 7.4.
area option introduced in Junos OS Release 9.2.
area option introduced in Junos OS Release 9.2 for EX Series switches.
realm option introduced in Junos OS Release 9.2. | [] | |
show (ospf | ospf3) io-statistics | show (ospf | ospf3) io-statistics | Display Open Shortest Path First (OSPF) input and output statistics. | [
{
"name": "none",
"desc": "Display OSPF input and output statistics."
},
{
"name": "logical-system (all | logical-system-name)",
"desc": "(Optional) Perform this operation on all logical systems or on a particular logical system."
}
] | view
Output Fields
Table 168 on page 17667 lists the output fields for the show ospf io-statistics command. Output fields
are listed in the approximate order in which they appear.
Table 168: show (ospf | ospf3) io-statistics Output Fields
Field Name
Field Description
Packets read
Number of OSPF packets read since the l... | Command introduced before Junos OS Release 7.4. | [] | |
show (ospf | ospf3) log | show (ospf | osfp3) log
<instance instance-name>
<topology topology-name> | Display the entries in the Open Shortest Path First (OSPF) log of SPF calculations. | [
{
"name": "none",
"desc": "Display entries in the OSPF log of SPF calculations for all routing instances."
},
{
"name": "instance instance-name",
"desc": "(Optional) Display entries for the specified routing instance."
},
{
"name": "logical-system (all | logical-system-name)",
"desc"... | view
Output Fields
Table 169 on page 17669 lists the output fields for the show (ospf | ospf3) log command. Output fields
are listed in the approximate order in which they appear.
Table 169: show (ospf | ospf3) log Output Fields
Field Name
Field Description
When
Time, in weeks (w) and days (d), since the SPF calculatio... | Command introduced before Junos OS Release 7.4.
topology option introduced in Junos OS Release 9.0.
topology option introduced in Junos OS Release 9.0 for EX Series switches.
realm option introduced in Junos OS Release 9.2. | [] | |
show (ospf | ospf3) neighbor | show (ospf | ospf3) neighbor
<brief | detail | extensive>
<area area-id>
<instance (all | instance-name)>
<interface interface-name>
<neighbor> | Display information about OSPF neighbors.
CPU utilization might increase while the device learns its OSPF neighbors. We recommend that you use
the show (ospf | ospf3) neighbor command after the device learns and establishes OSPF neighbor
adjacencies. Depending on the size of your network, this might take several minute... | [
{
"name": "none",
"desc": "Display standard information about all OSPF neighbors for all routing instances."
},
{
"name": "brief | detail | extensive",
"desc": "(Optional) Display the specified level of output."
},
{
"name": "area area-id",
"desc": "(Optional) Display information abo... | view
Output Fields
Table 170 on page 17674 lists the output fields for the show (ospf | ospf3) neighbor command. Output
fields are listed in the approximate order in which they appear.
Table 170: show (ospf | ospf3) neighbor Output Fields
Field Name
Field Description
Level of Output
Address
Address of the neighbor.
All... | Command introduced before Junos OS Release 7.4.
instance all option introduced in Junos OS Release 9.1.
instance all option introduced in Junos OS Release 9.1 for EX Series switches.
area, interface, and realm options introduced in Junos OS Release 9.2.
area and interface options introduced in Junos OS Release 9.2 for ... | [] | |
show (ospf | ospf3) overview | show (ospf | ospf3) overview
<brief | extensive>
<instance instance-name> | Display Open Shortest Path First (OSPF) overview information. | [
{
"name": "none",
"desc": "Display standard information about all OSPF neighbors for all routing instances."
},
{
"name": "brief | extensive",
"desc": "(Optional) Display the specified level of output."
},
{
"name": "igp-instance instance-name",
"desc": "(Optional) Specify the isis-i... | view
Output Fields
Table 171 on page 17682 lists the output fields for the show ospf overview command. Output fields are
listed in the approximate order in which they appear.
Table 171: show ospf overview Output Fields
Field name
Field Description
Level of Output
Instance
OSPF routing instance.
All levels
Router ID
Rou... | Command introduced in Junos OS Release 7.4.
realm option introduced in Junos OS Release 9.2.
Database protection introduced in Junos 10.2.
igp-instance option introduced in Junos OS Release 24.1R1 and Junos OS Evolved Release 24.1R1. | [] | |
show (ospf | ospf3) route | show (ospf | ospf3) route
<brief | detail | extensive>
<abr | asbr | extern | inter | intra>
<destination>
<instance instance-name
<network>
<no-backup-coverage>
<router>
<topology (default | ipv4-multicast | topology-name)>
<transit> | Display the entries in the Open Shortest Path First (OSPF) routing table. | [
{
"name": "none",
"desc": "Display standard information about all entries in the OSPF routing table for all routing instances and all topologies."
},
{
"name": "destination",
"desc": "Display routes to the specified IP address (with optional destination prefix length)."
},
{
"name": "bri... | view
Output Fields
Table 172 on page 17691 list the output fields for the show (ospf | ospf3) route command. Output fields
are listed in the approximate order in which they appear.
Table 172: show (ospf | ospf3) route Output Fields
Field Name
Field Description
Output Level
Topology
Name of the topology.
All levels
Pref... | Command introduced before Junos OS Release 7.4.
topology option introduced in Junos OS Release 9.0.
realm option introduced in Junos OS Release 9.2. | [] | |
show (ospf | ospf3) statistics | show (ospf | ospf3) statistics
<instance instance-name> | Display OSPF statistics. | [
{
"name": "none",
"desc": "Display OSPF statistics for all routing instances."
},
{
"name": "instance instance-name",
"desc": "(Optional) Display all statistics for the specified routing instance."
},
{
"name": "logical-system (all | logical-system-name)",
"desc": "(Optional) Perform... | view
Output Fields
Table 173 on page 17697 lists the output fields for the show (ospf | ospf3) statistics command. Output
fields are listed in the approximate order in which they appear.
Table 173: show (ospf | ospf3) statistics Output Fields
Field Name
Field Description
Packet type
Type of OSPF packet.
Total Sent/Tota... | Command introduced before Junos OS Release 7.4.
realm option introduced in Junos OS Release 9.2. | [] | |
show access-cac interface-set | show access-cac interface-set
<interface-set-name | detail> | Display interface-set adjustment information. | [
{
"name": "none",
"desc": "List all interface-set entries with the total aggregate adjustment value for each interface-set."
},
{
"name": "interface-set-name",
"desc": "Restrict the output to a specific interface-set."
},
{
"name": "detail",
"desc": "List all multicast groups, with a... | view
Output Fields
Table 174 on page 17702 describes the output fields for the show show access-cac interface-set command.
Output fields are listed in the approximate order in which they appear.
Table 174: show class-of-service interface-set Output Fields
Field Name
Field Description
Access cac
interface-set
Then name ... | Command introduced in Junos OS Release 17.2. | [
"Using Hierarchical CoS to Adjust Shaping Rates Based on Multicast Traffic"
] | |
show access-security router-advertisement state | show access-security router-advertisement state
<interface interface-name> | Display the IPv6 Router Advertisement (RA) guard state information. Stateful RA guard enables the
switch to learn about the sources of RA messages for a certain period of time. When the learning period
ends, the switch has a record of which interfaces are attached to links with valid IPv6 routers. If there is
no valid ... | [
{
"name": "interface interface-name",
"desc": "(Optional) Display the RA guard entries for the specified interface."
}
] | view
Output Fields
Table 175 on page 17705 lists the output fields for the show access-security router-advertisement state
command. Output fields are listed in the approximate order in which they appear.
Table 175: show access-security router-advertisement state Output Fields
Field Name
Field Description
Interface
Disp... | Command introduced in Junos OS Release 15.1X53-D55. | [] | |
show access-security router-advertisement statistics | show access-security router-advertisement statistics
<interface interface-name> | Display the IPv6 Router Advertisement (RA) guard entries for received RA messages. RA guard enables a
switch to examine incoming RA messages and filter them on the basis of predefined set of criteria. Once
the switch has validated that the sender of the RA message is a legitimate IPv6 router, it forwards the
RA message... | [
{
"name": "interface interface-name",
"desc": "(Optional) Display the RA guard entries for the specified interface."
}
] | view
Output Fields
Table 176 on page 17707 lists the output fields for the show access-security router-advertisement statistics
command. Output fields are listed in the approximate order in which they appear.
Table 176: show access-security router-advertisement statistics Output Fields
Field Name
Field Description
Leve... | Command introduced in Junos OS Release 15.1X53-D55. | [] | |
show access-security slaac-snooping binding | show access-security slaac-snooping binding
<interface (interface-name | all>
<vlan vlan-name>
<vlan vlan-name routing-instance routing-instance-name>
<vlan vlan-name logical-system logical-system-name> | Display the snooping table entries for IPv6 clients using stateless address auto-configuration (SLAAC).
SLAAC snooping extracts address information from Duplicate Address Detection (DAD) packets
exchanged during the SLAAC process to build the SLAAC snooping table. The IPv6-MAC address
bindings in this table are used t... | [
{
"name": "interface (interface-name | all)",
"desc": "Display the SLAAC snooping entries for the specified interface or for all interfaces."
},
{
"name": "vlan vlan-name",
"desc": "Display the SLAAC snooping entries for the specified VLAN."
},
{
"name": "logical-system logical-system-na... | view
Output Fields
Table 177 on page 17709 lists the output fields for the show access-security slaac-snooping binding
command. Output fields are listed in the approximate order in which they appear.
Table 177: show access-security slaac-snooping binding Output Fields
Field Name
Field Description
IPv6 address
IPv6 addr... | Command introduced in Junos OS Release 19.2R1. | [] | |
show access-security slaac-snooping state | show access-security slaac-snooping state
<interface interface-name I all> | Display the SLAAC snooping state information to show interfaces that are blocked. SLAAC snooping
extracts address information from Duplicate Address Detection (DAD) packets exchanged during the
SLAAC process to build the SLAAC snooping table. The IPv6-MAC address bindings in this table are
used to inspect and validate ... | [
{
"name": "interface (interface-name | all)",
"desc": "Display the SLAAC snooping state for the specified interface."
}
] | view
Output Fields
Table 178 on page 17712 lists the output fields for the show access-security slaac-snooping state command.
Output fields are listed in the approximate order in which they appear.
Table 178: show access-security slaac-snooping state Output Fields
Field Name
Field Description
Interface
Displays the in... | Command introduced in Junos OS Release 19.2R1. | [] | |
show access-security slaac-snooping statistics | show access-security slaac-snooping statistics
<interface (interface-name | all> | Display the statistics for IPv6 clients using stateless address auto-configuration (SLAAC). SLAAC
snooping extracts address information from Duplicate Address Detection (DAD) packets exchanged
during the SLAAC process to build the SLAAC snooping table. The IPv6-MAC address bindings in this
table are used to inspect and... | [
{
"name": "interface (interface-name | all)",
"desc": "Display the SLAAC snooping statistics for the specified interface or for all interfaces."
},
{
"name": "logical-system logical-system-name",
"desc": "Display the SLAAC snooping statistics for the specified logical system."
},
{
"name... | view
Output Fields
Table 179 on page 17714 lists the output fields for the show access-security slaac-snooping statistics
command. Output fields are listed in the approximate order in which they appear.
Table 179: show access-security slaac-snooping statistics Output Fields
Field Name
Field Description
Statistics
Stati... | Command introduced in Junos OS Release 19.2R1. | [] | |
show accounting pending-accounting-stops | show accounting pending-accounting-stops
<detail | terse>
<profile-name> | Display all statistics for all pending accounting stop requests, including both service and session
requests. | [
{
"name": "none",
"desc": "Display information for all access profiles."
},
{
"name": "detail | terse",
"desc": "(Optional) Display the specified level of output."
},
{
"name": "profile-name",
"desc": "(Optional) Particular access profile for which you want to display accounting stop... | view
Output Fields
Table 180 on page 17717 lists the output fields for the show accounting pending-accounting-stops command.
Output fields are listed in the approximate order in which they appear.
Table 180: show accounting pending-accounting-stops Output Fields
Field Name
Field Description
Level of Output
Type
Type of... | Command introduced in Junos OS Release 13.1. | [] | |
show accounting profile | show accounting profile profile-name | Display accounting profile information. | [
{
"name": "profile-name",
"desc": "Name of the accounting profile."
}
] | view
Output Fields
Table 181 on page 17722 lists the output fields for the show accounting profile command. Output fields
are listed in the approximate order in which they appear.
Table 181: show accounting profile Output Fields
Field Name
Field Description
Profile
Name of the accounting profile.
Sampling interval
Conf... | Command introduced before Junos OS Release 7.4. | [] | |
show accounting server statistics archival-transfer | show accounting server statistics archival-transfer | Display the statistics of transfer attempted, succeeded, and failed for accounting statistics files and
router configuration archives. | [] | view
Sample Output
show accounting server statistics archival-transfer
user@host> show accounting server statistics archival-transfer
File Name : /var/transfer/config/*
URL :scp://root@ce-bras-nvsrv-a:/var/www/html
Last transfer attempted timestamp :20190603_... | Command introduced in Junos OS Release 19.2. | [] | |
show agent sensors | show agent sensors | Display information about sensors configured for Junos Telemetry Interface.
NOTE: Junos telemetry interface was introduced in Junos OS Release 15.1F3 on MX
Series routers with interfaces configured on MPC1 through MPC6E and on PTX Series
routers with interfaces configured on FPC3. Starting in Junos OS Release 15.1F5, J... | [] | view
Output Fields
Table 182 on page 17730 lists the output fields for the show agent sensors command. Output fields are
listed in the approximate order in which they appear.
Table 182: show agent sensors Output Fields
Field Name
Field Description
Sensor Information
Information about sensors configured to monitor syste... | Statement introduced in Junos OS Release 15.1F3 | [] | |
show amt statistics | show amt statistics
<instance instance-name>
<logical-system (all | logical-system-name)> | Display information about the Automatic Multicast Tunneling (AMT) protocol tunnel statistics. | [
{
"name": "none",
"desc": "Display summary information about all AMT Protocol tunnels."
},
{
"name": "instance instance-name",
"desc": "(Optional) Display information for the specified instance only."
},
{
"name": "logical-system (all | logical-system-name)",
"desc": "(Optional) Perf... | view
Output Fields
Table 183 on page 17740 describes the output fields for the show amt statistics command. Output fields
are listed in the approximate order in which they appear.
Table 183: show amt statistics Output Fields
Field Name
Field Description
AMT receive
message count
Summary of AMT statistics for messages ... | Command introduced in JUNOS Release 10.2. | [
"clear amt statistics"
] | |
show amt summary | show amt summary
<instance instance-name>
<logical-system (all | logical-system-name)> | Display summary information about the Automatic Multicast Tunneling (AMT) protocol. | [
{
"name": "none",
"desc": "Display summary information about all AMT protocol instances."
},
{
"name": "instance instance-name",
"desc": "(Optional) Display information for the specified instance only."
},
{
"name": "logical-system (all | logical-system-name)",
"desc": "(Optional) Pe... | view
Output Fields
Table 184 on page 17744 describes the output fields for the show amt summary command. Output fields are
listed in the approximate order in which they appear.
Table 184: show amt summary Output Fields
Field Name
Field Description
Level of Output
AMT anycast
prefix
Prefix advertised by unicast routing... | Command introduced in Junos OS Release 10.2. | [] | |
show amt tunnel | show amt tunnel
<brief | detail>
<gateway-address gateway-ip-address> <port port-number>
<instance instance-name>
<logical-system (all | logical-system-name)>
<tunnel-interface interface-name> | Display information about the Automatic Multicast Tunneling (AMT) dynamic tunnels. | [
{
"name": "none",
"desc": "Display summary information about all AMT protocol instances."
},
{
"name": "brief | detail",
"desc": "(Optional) Display the specified level of detail. gateway-address gateway-ip-address port port-number (Optional) Display information for the specified AMT gateway onl... | view
Output Fields
Table 185 on page 17746 describes the output fields for the show amt tunnel command. Output fields are
listed in the approximate order in which they appear.
Table 185: show amt tunnel Output Fields
Field Name
Field Description
Level of Output
AMT gateway
address
Address of the AMT gateway that is bei... | Command introduced in Junos OS Release 10.2. | [] | |
show analyzer | show analyzer analyzer-name | Display information about analyzers configured for mirroring. | [
{
"name": "analyzer-name",
"desc": "(Optional) Displays the status of a specific analyzer on the switch."
}
] | view
Output Fields
Table 186 on page 17751 lists the output fields for the command-name command. Output fields are listed in
the approximate order in which they appear.
Table 186: show analyzer Output Fields
Field Name
Field Description
Analyzer name
Displays the name of the analyzer.
Output interface
Specifies a local... | Command introduced in Junos OS Release 9.0. | [] | |
show ancp cos | show ancp cos
<identifier identifier>
<last-update>
<pending-update> | Display information about the CoS state for subscriber traffic. | [
{
"name": "identifier identifier",
"desc": "(Optional) Display information about the local loops for the specified access identifier."
},
{
"name": "last-update",
"desc": "(Optional) Display the most recently updated CoS information."
},
{
"name": "pending-update",
"desc": "(Optional... | view
Output Fields
Table 187 on page 17753 lists the output fields for the show ancp cos command. Output fields are listed in
the approximate order in which they appear.
Table 187: show ancp cos Output Fields
Field Name
Field Description
Per-DSL CoS
adjustment
Adjustment values applied by the ANCP agent to the actual d... | Command introduced in Junos OS Release 9.4. | [] | |
show ancp neighbor | show ancp neighbor
<brief | detail>
<ip-address ip-address
<system-name mac-address> | Display information about all ANCP neighbors or the specified ANCP neighbor, regardless of operational
state. | [
{
"name": "brief | detail",
"desc": "(Optional) Display the specified level of detail."
},
{
"name": "ip-address ip-address",
"desc": "(Optional) Display information about the neighbor (access node) specified by the IP address."
},
{
"name": "system-name mac-address",
"desc": "(Optio... | view
Output Fields
Table 188 on page 17761 lists the output fields for the show ancp neighbor command. Output fields are
listed in the approximate order in which they appear.
Table 188: show ancp neighbor Output Fields
Field Name
Field Description
Level of
Output
Version
Version of the ANCP implementation:
•
0x31—Gener... | Command introduced in Junos OS Release 9.4.
Additional counters added starting Junos OS Release 21.2R1. | [] | |
show ancp statistics | show ancp statistics
<ip-address ip-address>
<system-name mac-address> | Display statistics for all ANCP neighbors (access nodes) or the specified ANCP neighbor. | [
{
"name": "none",
"desc": "Display statistics for all ANCP neighbors, including global statistics not show for individual neighbors."
},
{
"name": "ip-address ip-address",
"desc": "(Optional) Display statistics for only the neighbor with the specified IP address."
},
{
"name": "system-na... | view
Output Fields
Table 189 on page 17773 lists the output fields for the show ancp statistics command. Output fields are
listed in the approximate order in which they appear.
Table 189: show ancp statistics Output Fields
Field Name
Field Description
Number of neighbors
Total count of ANCP neighbors.
Number of subscri... | Command introduced in Junos OS Release 13.3. | [] | |
show ancp subscriber | show ancp subscriber
<brief | detail>
<access-aggregation-circuit-id circuit-identifier>
<identifier identifier>
<ip-address ip-address>
<system-name mac-address> | Display information about active subscribers regardless of the subscriber’s operational state, for all
subscribers (local access loops), the subscriber associated with the access line specified by an ACI, or the
subscriber associated with the specified ANCP neighbor (access node).
After an ancpd restart, this command ... | [
{
"name": "none",
"desc": "Display information about all subscribers."
},
{
"name": "brief | detail",
"desc": "(Optional) Display the specified level of detail."
},
{
"name": "access-aggregation-circuit-id circuit-",
"desc": ""
},
{
"name": "identifier",
"desc": "(Optiona... | view
Output Fields
Table 190 on page 17781 lists the output fields for the show ancp subscriber command. Output fields are
listed in the approximate order in which they appear.
Table 190: show ancp subscriber Output Fields
Field Name
Field Description
Level of Output
Loop Identifier
Access loop identifier as sent by t... | Command introduced in Junos OS Release 9.4.
neighbor option replaced with ip-address in Junos OS Release 16.1.
system-name option introduced in Junos OS Release 16.1.
access-aggregation-circuit-id option introduced in Junos OS Release 18.4R1. | [] | |
show ancp summary neighbor | show ancp summary neighbor
<ip-address ip-address | system-name mac-address> | Display a summary of the counts and states for all ANCP neighbors and of the neighbor’s subscribers
when you specify a particular neighbor. | [
{
"name": "ip-address ip-address",
"desc": "(Optional) IP address of the ANCP neighbor (access node)."
},
{
"name": "system-name mac-address",
"desc": "(Optional) MAC address of the ANCP neighbor (access node)."
}
] | view
Output Fields
Table 191 on page 17791 lists the output fields for the show ancp summary command. Output fields are
listed in the approximate order in which they appear.
Table 191: show ancp summary neighbor Output Fields
Field Name
Field Description
Configured
Number of ANCP neighbors in the Configured state; tha... | Command introduced in Junos OS Release 13.1. | [] | |
show ancp summary subscriber | show ancp summary subscriber | Display a summary of the counts and states for all ANCP subscribers. | [] | view
Output Fields
Table 192 on page 17794 lists the output fields for the show ancp summary subscriber command. Output
fields are listed in the approximate order in which they appear.
Table 192: show ancp summary subscriber Output Fields
Field Name
Field Description
Showtime
Number of DSL lines in Showtime state.
Idl... | Command introduced in Junos OS Release 13.1. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.