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 |
|---|---|---|---|---|---|---|---|
persistent-nat | persistent-nat {
address-mapping;
inactivity-timeout seconds;
max-session-number value;
permit (any-remote-host | target-host | target-host-port);
} | [edit security nat source rule-set ruleset rule rule then source-nat interface]
[edit security nat source rule-set ruleset rule rule then source-nat pool] | Use the persistent-nat feature to ensure that all requests from the same internal transport address are
mapped to the same reflexive transport address (the public IP address and port created by the NAT
device closest to the STUN server). The source NAT rule action can use a source NAT pool (with or
without port transla... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration | Statement introduced in Junos OS Release 9.6. Support. | [
"Understanding Persistent NAT and NAT64"
] |
persistent-results | persistent-results; | [edit services rpm twamp client control-connection control-client-name] | When enabled, allows to display the old and current tests’ results after a network recovery or after
TWAMP server reachability when you execute the show services rpm twamp client probe-results command.
By default, the option is disabled. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1. | [
"Configuring TWAMP on MX, M, T, and PTX Series Routers and EX4300 Series Switches",
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
pfc (Input Congestion Notification) | pfc {
mru mru-value;
} | [edit class-of-service congestion-notification-profile profile-name input dscp code-point code-point-
bits],
[edit class-of-service congestion-notification-profile profile-name input ieee-802.1 code-point
code-point-bits] | Enable and configure ingress interface priority-based flow control (PFC) for a configured IEEE 802.1p
code point in the VLAN-tagged packet header at Layer 2, or on a DSCP value from the Layer 3 IP header
to support PFC with untagged traffic. | [] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support for DSCP-based PFC introduced in Junos OS Release 17.4R1 for the QFX Series. | [
"Configuring CoS PFC (Congestion Notification Profiles)",
"Example: Configuring Two or More Lossless FCoE IEEE 802.1p Priorities on Different FCoE Transit",
"Switch Interfaces",
"Example: Configuring Two or More Lossless FCoE Priorities on the Same FCoE Transit Switch",
"Interface",
"Example: Configuring ... |
pfc | pfc; | [edit interfaces interface-name ppp-options compression],
[edit interfaces interface-name unit logical-unit-number ppp-options compression],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number ppp-
options compression] | For interfaces with PPP encapsulation, configure the router to compress the protocol field to one byte. | [] | 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 PPP"
] |
pfc-account | pfc-account {
name;
pfc-priority pfc-priority;
xoff xoff;
xon xon;
} | [edit class-of-service congestion-notification-profile name input] | Define a PFC account for a congestion notification profile (CNP). | [
{
"name": "name",
"desc": ""
},
{
"name": "PFC account name",
"desc": ""
},
{
"name": "pfc-priority",
"desc": ""
},
{
"name": "PFC priorities (set of priorities)",
"desc": "Range: 0 through 7"
},
{
"name": "xoff",
"desc": "(Optional) Specifies account threshol... | [none specified] | Statement introduced in Junos OS Evolved Release 20.4R1. | [] |
pfc-priority | pfc-priority pfc-priority; | [edit class-of-service forwarding-classes class class-name] | Explicitly map a forwarding class to a priority-based flow control (PFC) priority value.
To support lossless behavior for untagged traffic across Layer 3 connections to Layer 2 subnetworks,
you can configure PFC to be invoked based on a configured 6-bit Distributed Services code point (DSCP)
value in the Layer 3 IP hea... | [
{
"name": "pfc-priority",
"desc": "3-bit PFC priority value in decimal form (0-7)."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1. | [
"Understanding PFC Using DSCP at Layer 3 for Untagged Traffic",
"Configuring DSCP-based PFC for Layer 3 Untagged Traffic",
"Understanding CoS Flow Control (Ethernet PAUSE and PFC)"
] |
pfe power off | pfe pfe-instance power (off | on); | [edit chassis fpc slot-number] | Configure a Packet Forwarding Engine (PFE) to remain powered off when an FPC comes online or power
off or power on a PFE during runtime. Click here to see the platforms supporting pfe configuration
options.
Default
on | [
{
"name": "pfe pfe-id",
"desc": "The ID of the Packet Forwarding Engine to be powered off. NOTE: Powering off a supported PFE using this configuration command triggers an automatic FPC restart on an MX series router. For the MPC10E-15C-MRATE line card, only the Packet Forwarding Engine 2 is applicable."
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1R1. | [
"Packet Forwarding Engine Power Management",
"MPC10E-15C-MRATE"
] |
pfe | pfe pfe-instance {
exception-reporting {
category category-name; {
inline-monitoring-instance inline-monitoring-instance;
}
}
forwarding-packages {
mobility;
}
power (off | on);
temp-perf-throttle-disable;
temp-volt-reduction-disable;
tunnel-services;
} | [edit chassis fpc slot-number],
[edit chassis lcc name fpc slot-number],
[edit chassis member name fpc slot-number] | Configure options for the Packet Forwarding Engine (PFE). Click here to see the platforms supporting pfe
configuration options. | [
{
"name": "pfe-instance or",
"desc": ""
},
{
"name": "pfe-id",
"desc": "PFE identifier or PFE number that represents the PFE ASIC ID ranges from 0-4 for PTX10004 and 0-7 for PTX10008 devices. PFE identifier or PFE number that represents the PFE ASIC ID. The value is 0 for ACX7024, and ACX7024X d... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | exception-reporting option added in Junos OS Release 21.2R1.
temp-perf-throttle-disable option added in Junos OS Evolved Release 21.4R1.
temp-volt-reduction-disable option added in Junos OS Evolved Release 22.2R1.
exception-reporting option added in Junos OS Evolved Release 22.2R1.
Statement introduced in Junos OS Evol... | [] |
pgcp | pgcp {
hint [ hint-strings ];
ports-per-session ports;
remotely-controlled;
transport [ transport-protocols ];
} | [edit services nat pool nat-pool-name] | Specify that the NAT pool is used exclusively by the BGF. | [] | 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.
remotely-controlled and ports-per-session statements added in Junos OS Release 8.5.
hint statement added in Junos OS Release 9.0. | [] |
pgcp-rules | (pgcp-rules rule-name | pgcp-rules-sets rule-set-name); | [edit services service-set service-set-name] | Specify the Packet Gateway Control Protocol (PGCP) rules or rule set included in this service set. You
can configure multiple rules but only one rule set for each service. | [
{
"name": "rule-name",
"desc": "Identifier for the collection of terms that constitute this rule."
},
{
"name": "rule-set-name",
"desc": "Identifier for the set of rules to be included."
}
] | 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 Service Sets to be Applied to Services Interfaces"
] |
pgcp-service | pgcp-service {
command binary-file-path;
disable;
failover (alternate-media | other-routing-engine);
} | [edit system processes] | Specify the Packet Gateway Control Protocol (PGCP) that is required for the border gateway function
(BGF) feature. | [
{
"name": "command binary-file-path",
"desc": "Path to the binary process."
},
{
"name": "disable",
"desc": "Disable the Packet Gateway Control Protocol (PGCP) process."
},
{
"name": "failover",
"desc": "Configure the device to reboot if the software process fails four times within 3... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
phase-adjust-threshold | phase-adjust-threshold phase-offset | [edit protocols ptp] | The phase adjust threshold option is the maximum phase offset that will be adjusted by the G.8275.2
enhanced servo in a phase-aligned state. A higher phase adjust threshold permits a clock to tolerate
phase offset changes because of higher network packet delay variation (PDV). This option can be used
for PTP applicatio... | [
{
"name": "phase-offset",
"desc": "The maximum phase offset value in nanoseconds (ns). Range: 1100 ns through 100000 ns Default: 1100 ns"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1 for MX10008.
Supported on ACX7100-32C, ACX7100-48L, and ACX7024 in Junos OS Evolved Release 24.2R1. | [
"Configuring Precision Time Protocol",
"Example: Configuring Precision Time Protocol",
"Precision Time Protocol Overview",
"Configuring the Precision Time Protocol G.8275.2 Enhanced Profile (Telecom Profile)"
] |
phase-error-limit | phase-error-limit {
force-synce-holdover;
max-holdover-time max-holdover-time;
relative-threshold relative-threshold;
} | [edit logical-systems name protocols ptp],
[edit protocols ptp] | Parameters for configuring a phase-error threshold. | [
{
"name": "force-synce-holdover",
"desc": "Force SyncE into holdover after phase threshold is exceeded."
},
{
"name": "max-holdover-time",
"desc": "Holdover time limit (in minutes) after phase threshold is exceeded. Range: 5 through 10080"
},
{
"name": "relative-threshold",
"desc": ... | routing-To view this statement in the configuration. | Statement introduced in Junos OS Release 25.4R1. | [
"No Link Title"
] |
phase-lock-threshold | phase-lock-threshold phase-offset | [edit protocols ptp] | The phase lock threshold option controls the maximum phase offset with which G.8275.2 enhanced
servo enters the phase-aligned state. Phase locking with a higher phase lock threshold leads to the servo
and time receiver getting into the phase-aligned state quickly. This higher offset is subsequently
adjusted in the phas... | [
{
"name": "phase-offset",
"desc": "The maximum phase offset value in nanoseconds (ns). Range: 100 ns through 1000 ns Default: 200 ns"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1 for MX10008.
Supported on ACX7100-32C, ACX7100-48L, and ACX7024 in Junos OS Evolved Release 24.2R1. | [
"Configuring Precision Time Protocol",
"Example: Configuring Precision Time Protocol",
"Precision Time Protocol Overview",
"Configuring the Precision Time Protocol G.8275.2 Enhanced Profile (Telecom Profile)"
] |
phy-timestamping | phy-timestamping | [edit protocols ptp] | Configure timestamping of the IEEE 1588 event packets at the physical layer. Timestamping the packet
at the physical layer, also known as PHY timestamping, eliminates the noise or the packet delay variation
(PDV) that is introduced by the Packet Forwarding Engine.
By default PHY timestamping is disabled.
On Junos EVO p... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1R1. | [
"Precision Time Protocol Overview"
] |
physical-interface (DDoS Flow Detection) | physical-interface (flow-bandwidth | flow-control-mode | flow-detection-mode) | [edit system ddos-protection protocols protocol-group packet-type flow-level-bandwidth],
[edit system ddos-protection protocols protocol-group packet-type flow-level-control],
[edit system ddos-protection protocols protocol-group packet-type flow-level-detection] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches)
Configure flow bandwidth, flow control mode, or flow detection mode at the physical interface flow
aggregation level for the packet type. | [
{
"name": "flow-bandwidth",
"desc": "Bandwidth for the flow at the physical interface level. Available only at the [edit system"
},
{
"name": "flow-control-mode",
"desc": "Mode for how traffic in the detected flow is controlled at the physical interface level."
},
{
"name": "drop",
"... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support for Enhanced Subscriber Management added in Junos OS Release 17.3R1. | [
"Configuring the Maximum Flow Bandwidth at Each Flow Aggregation Level",
"Configuring How Traffic in a Culprit Flow Is Controlled at Each Flow Aggregation Level",
"Configuring How Flow Detection Operates at Each Flow Aggregation Level",
"Setting Up and Using Flow Detection"
] |
physical-interface-filter | physical-interface-filter; | [edit firewall family family-name filter filter-name],
[edit logical-systems logical-system-name firewall family family-name filter filter-name],
[edit routing-instances routing-instance-name firewall family family-name filter filter-name],
[edit logical-systems logical-system-name routing-instances routing-instance-na... | Configure a physical interface filter. Use this statement to reference a physical interface policer for the
specified protocol family.
For PTX series routers running Junos OS Release 18.3R1 or later, you can use this command to
configure separate firewall filters for different family address types (IPv4 and IPv6) that ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6.
Support for PTX series routers with third-generation FPCs added in Junos OS Release 18.3R1. | [
"Two-Color and Three-Color Physical Interface Policers"
] |
physical-interface-policer | physical-interface-policer; | [edit dynamic-profiles profile-name firewall policer policer-name],
[edit firewall policer policer-name],
[edit firewall three-color-policer policer-name],
[edit logical-systems logical-system-name firewall policer policer-name],
[edit logical-systems logical-system-name three-color-policer policer-name],
[edit routing... | Configure an aggregate policer for a physical interface.
A physical interface policer can be a two-color or three-color policer. When you apply physical interface
policer, to different protocol families on the same logical interface, the protocol families share the same
policer instance. This means that rate limiting i... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6.
Support at the [edit dynamic-profiles ... policer policer-name] hierarchy level introduced in Junos Release
OS 11.4.
Support for PTX series routers with third-generation FPCs added in Junos OS Release 18.3R1. | [
"Two-Color and Three-Color Physical Interface Policers",
"physical-interface-filter"
] |
pic (M Series and T Series Routers) | pic pic-number {
ce1 {
e1 port-number {
channel-group group-number timeslots slot-number;
}
}
ct3 {
port port-number {
t1 link-number {
channel-group group-number timeslots slot-number;
}
}
}
framing (sdh | sonet);
... | [edit chassis fpc slot-number] | Configure properties for an individual PIC. | [
{
"name": "pic-number",
"desc": "Slot number in which the PIC is installed."
}
] | 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 Junos OS to Enable SONET/SDH Framing for SONET/SDH PICs",
"Configuring the Junos OS to Enable a SONET PIC to Operate in Channelized (Multiplexed) Mode",
"Configuring the Junos OS to Support Channelized DS3-to-DS0 Naming for Channel Groups and Time",
"Slots",
"Configuring the Junos OS to Sup... |
pic (MX Series Routers) | pic pic-number {
account-layer2-overhead;
adaptive-services {
(layer-2 | layer-3);
}
aggregate-ports;
ce1 {
e1 port-number {
channel-group group-number timeslots slot-number;
}
}
channelization;
ct3 {
port port-number {
t1 link-numb... | [edit chassis fpc slot-number] | Configure properties for an individual PIC. | [
{
"name": "pic-number",
"desc": "Slot number in which the PIC is installed."
}
] | 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.
multi-link-layer-2-inline and mlfr-uni-nni-bundles-inline options introduced in Junos OS Release 14.1. | [
"Configuring the Junos OS to Enable SONET/SDH Framing for SONET/SDH PICs",
"Configuring the Junos OS to Enable a SONET PIC to Operate in Channelized (Multiplexed) Mode",
"Configuring the Junos OS to Support Channelized DS3-to-DS0 Naming for Channel Groups and Time",
"Slots",
"Configuring the Junos OS to Sup... |
pic (Port) | pic pic-number {
fte {
(port port-number | port-range port-range-low port-range-high);
}
xe {
(port port-number | port-range port-range-low port-range-high);
}
} | [edit chassis interconnect-device name fpc slot] | (QFX3600 Node device only) Configure port types on QFX3600 Node devices.
CAUTION: The Packet Forwarding Engine on the QFX3600 Node device is restarted
when you commit the port type configuration changes. As a result, you might experience
packet loss on the Node device. | [
{
"name": "pic pic-number",
"desc": "Number of the physical interface card (PIC) on which you want to configure port types. Specify 0 to configure xe (10-Gigabit Ethernet) type ports. Specify 1 to configure fte (40-gigabit data plane uplink) type ports."
},
{
"name": "fte",
"desc": "Configure a ... | 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. | [
"Configuring the Port Type on QFX3600 Node Devices"
] |
pic (PTX Series Routers) | pic
{
ce1 {
e1 port-number
{
channel-group group-number timeslots slot-number;
}
ct3 {
port port-number {
t1 link-number {
channel-group group-number timeslots slot-number;
... | [edit chassis fpc slot-number] | Configure properties for an individual PIC. | [
{
"name": "pic-number",
"desc": "Slot number in which the PIC is installed."
}
] | 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 Junos OS to Enable SONET/SDH Framing for SONET/SDH PICs",
"Configuring the Junos OS to Enable a SONET PIC to Operate in Channelized (Multiplexed) Mode",
"Configuring the Junos OS to Support Channelized DS3-to-DS0 Naming for Channel Groups and Time",
"Slots"
] |
pic (satellite-policies port-group-alias) | pic pic-number {
port [port-number | port-number-range | all];
} | [edit policy-options satellite-policies port-group-alias port-group-alias-name] | Specify the PIC number to apply a port group alias for satellite policies in a Junos Fusion.
You must also specify the ports on the PIC when you use this statement. | [
{
"name": "pic-number",
"desc": "The PIC number on the satellite device. The remaining statements are explained separately."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring Junos Fusion Provider Edge",
"Configuring or Expanding a Junos Fusion Enterprise"
] |
pic (Subscriber Limits) | pic number {
limit limit;
port number {
limit limit;
}
} | [edit system services resource-monitor subscribers-limit client-type name fpc slot-number] | Configure the maximum number of subscribers of a client type allowed to be logged in on the specified
MIC. When that number is reached, subsequent logins on the MIC are denied until the current number
of subscribers drops below the maximum allowed. You can also specify the maximum number of
subscribers of a client type... | [
{
"name": "number",
"desc": "MIC number. Range: 0 through 3"
},
{
"name": "limit",
"desc": "Maximum number of subscribers. Range: 1 through 256,000 The remaining statement is explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for deta... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R1. | [
"Limiting Subscribers by Client Type and Hardware Element with Resource Monitor",
"Resource Monitoring for Subscriber Management and Services"
] |
pic | pic pic-number {
fibre-channel {
port-range {
port-range-low port-range-high;
}
}
fte{
port port-number;
(port-range port-range-low | port-range-high);
}
xe {
(port port-number | port-range port-range-low port-range-high);
}
xle {
... | [edit chassis fpc slot]
[edit chassis node-group name node-device name] | (QFX3500, QFX3600, and QFX5100 standalone switches running Enhanced Layer 2 Software only)—
Configure a specific port or a range of ports to operate as 10-Gigabit Ethernet ports or 40-Gigabit
Ethernet ports.
Enable the specified port on the Physical Interface Card (PIC) to perform in the specified operating
mode. | [
{
"name": "pic pic-number",
"desc": "(QFX3500 standalone switch only) Number of the physical interface card (PIC) on which you want to configure port types. Specify 1 to configure 10-Gigabit Ethernet or 40-Gigabit Ethernet type ports. (QFX3600 standalone switch only) Number of the physical interface card (P... | 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.
Options xe and xle introduced in Junos OS 12.2X50-D20 for the QFX Series.
Option channel-speed introduced in Junos OS Release 13.2 for the QFX Series. | [
"Channelizing Interfaces on QFX3500, QFX3600, QFX5100, QFX10002, QFX10008, QFX10016, and",
"EX4600 Switches",
"Configuring the QSFP+ Port Type on QFX3500 Standalone Switches",
"Configuring the Port Type on QFX3600 Standalone Switches",
"Configuring the QSFP+ Port Type on QFX5100 Devices"
] |
pic-boot-timeout | pic-boot-timeout (240 | 300); | [edit interfaces interface-name multiservice-options] | Set the service PIC boot timeout value to 240 or 300 seconds for every services PIC on the MX Series
router if you are configuring more than 24 members in an aggregated multiservices (AMS) interface. We
recommend setting the boot timeout value to 240. Starting with Junos OS Release 16.2, an AMS
interface can have up to... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring Aggregated Multiservices Interfaces"
] |
pic-console-authentication | pic-console authentication {
(encrypted-password "password");
} | [edit system] | Configure console access to Physical Interface Cards (PICs).
Default
Disabled. By default, there is no password setting for console access. | [
{
"name": "encrypted-password \"",
"desc": ""
},
{
"name": "password\"",
"desc": "Use MD5 or other encrypted authentication. Specify the MD5 or other password. You can specify only one encrypted password. You cannot configure a blank password for encrypted-password using blank quotation marks (\... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Junos OS to Set Console and Auxiliary Port Properties",
"Configuring Password Authentication for Console Access to PICs"
] |
pic-memory-threshold | pic-memory-threshold percentage percentage; | [edit services dynamic-flow-capture capture-group client-name] | Specify a PIC memory usage percentage that triggers a system log warning message. | [
{
"name": "percentage",
"desc": "PIC memory threshold value."
}
] | 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 Thresholds"
] |
pic-mode (Chassis T1 Mode) | pic-mode (clear-channel); | [edit chassis fpc slot-number pic pic-number ethernet] | Configure normal T1 mode or channelized T1 mode. | [
{
"name": "clear-channel",
"desc": "(default) Normal T1 mode."
},
{
"name": "ct1",
"desc": "Channelized T1 mode."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement added in Junos OS Release 10.2. | [
"Understanding Interfaces"
] |
pic-mode (MX Series) | pic-mode pic-speed; | [edit chassis fpc slot pic pic-number ] | Configure the operating speed of all ports on the MPC7E-MRATE MPC, MIC-MRATE MIC, MX10003
MPC, and MX204 routers.
(MX240, MX480, MX960, MX2010, and MX2020 routers with MPC7E-MRATE) To configure 100 Gbps,
10 Gbps, and 40 Gbps speed on all supported ports, specify 100G, 10G, or 40G, respectively, as the speed
for the spe... | [
{
"name": "pic-speed",
"desc": "Operating speed of the interfaces configured on the ports of an MPC7E-MRATE MPC."
},
{
"name": "100G",
"desc": "Supported ports operate at 100 Gbps speed."
},
{
"name": "40G",
"desc": "Supported ports operate at 40 Gbps speed."
},
{
"name": "10... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F4.
Statement introduced in Junos OS Release 17.3R1 for MX10003 routers with the MX10003 MPC. | [
"Port Speed"
] |
pic-mode | pic-mode mode; | [edit chassis fpc slot pic pic-number sfpplus] | Configure the operating mode for the specified port on the SFP+ uplink module on an EX3200 or
EX4200 switch.
On a switch using the SFP+ or SFP+ MACSec uplink module, the pic-mode setting defines the speeds of
the SFP+ interfaces. When the PIC mode is set to 10g on the SFP+ or SFP+ MACSec uplink module,
uplink ports 0 a... | [
{
"name": "mode",
"desc": "Operating mode of the SFP+ uplink module:"
},
{
"name": "1G",
"desc": "1-gigabit operating mode"
},
{
"name": "10G",
"desc": "10-gigabit operating mode"
}
] | 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"
] |
pic-services-logging | pic-services-logging {
command binary-file-path;
disable;
failover (alternate-media | other-routing-engine);
} | [edit system processes] | Enable PICs to send special logging information to the Routing Engine for archiving on a hard disk. | [
{
"name": "command binary-file-path",
"desc": "Path to the binary process."
},
{
"name": "disable",
"desc": "Disable the PIC services logging process."
},
{
"name": "failover",
"desc": "Configure the device to reboot if the software process fails four times within 30 seconds,"
},
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
pim | pim {
disable;
assert-timeout seconds;
dense-groups {
addresses;
}
dr-election-on-p2p;
export;
family (inet | inet6) {
disable;
}
graceful-restart {
disable;
no-bidirectional-mode;
restart-duration seconds;
}
import [ policy-names ];
... | [edit logical-systems logical-system-name protocols],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit protocols],
[edit routing-instances routing-instance-name 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 before Junos OS Release 7.4.
family statement introduced in Junos OS Release 9.6. | [
"Example: Configuring Data MDTs and Provider Tunnels Operating in Any-Source Multicast Mode",
"Configuring PIM Dense Mode Properties",
"Configuring PIM Sparse-Dense Mode Properties"
] |
pim-asm | pim-asm {
group-address (Routing Instances) address;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel],
[edit routing-instances routing-instance-name provider-tunnel] | Specify a Protocol Independent Multicast (PIM) sparse mode provider tunnel for an MBGP MVPN or for
a draft-rosen MVPN.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [] |
pim-evpn-gateway | pim-evpn-gateway {
external-irb irb-interface-name;
peg-df-election {
delay-time seconds;
mod;
preference {
use-least;
value value;
}
}
} | [edit protocols evpn oism],
[edit routing-instances name protocols evpn oism] | Configure a border leaf device to act as a PIM EVPN gateway (PEG) for optimized intersubnet multicast
(OISM).
The PEG device connects an EVPN fabric to an external PIM domain to route multicast traffic:
•
From external sources to receivers in the EVPN fabric.
•
From sources in the EVPN fabric to external receivers.
You... | [
{
"name": "external-irb",
"desc": ""
},
{
"name": "irb-interface-",
"desc": ""
},
{
"name": "name",
"desc": "Specify an IRB interface the device uses in PEG mode to route multicast traffic to and from the external PIM domain. Include this option on OISM border leaf devices that use t... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1 and Junos OS Evolved Release 22.1R1.
Support in the default L3 routing instance introduced in Junos OS Evolved Release 25.4R1. | [
"Optimized Inter-Subnet Multicast in EVPN Networks",
"PEG DF Election"
] |
pim-snooping | pim-snooping {
no-dr-flood;
traceoptions{
file [filename files | no-word-readable | size | word-readable];
flag [all | general | hello | join | normal | packets | policy | prune | route |
state | task | timer];
}
vlan<vlan-id>{
no-dr-flood;
}
} | [edit logical-systems logical-system-name routing-instances instance-name instance-type vpls
protocols],
[edit logical-systems logical-system-name routing-instances instance-name protocols],
[edit routing-instances instance-name 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... | [
{
"name": "no-dr-flood",
"desc": "Disable default flooding of multicast data on the PIM-designated router port."
},
{
"name": "traceoptions",
"desc": "Configure tracing options for PIM snooping."
},
{
"name": "vlan <vlan-id>",
"desc": "Configure PIM snooping parameters for a VLAN."
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"PIM Snooping for VPLS"
] |
pim-ssm (Provider Tunnel) | pim-ssm {
group-address (Routing Instances) address;
tunnel-source address;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel family inet | inet6],
[edit routing-instances routing-instance-name provider-tunnel family inet | inet6] | Configure the PIM source-specific multicast (SSM) provider tunnel. Use family inet6 pim-ssm for Rosen 7
running on IPv6 . For Rosen 7 on IPv4, use family inet pim-ssm. The customer data-MDT can be
configured on IPv4 or IPv6, but not both (the provider space always runs on IPv4). Enable Rosen IPv4
before enabling Rosen ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
In Junos OS Release 17.3R1, the pim-ssm hierarchy was moved from provider-tunnel to the provider-tunnel
family inet and provider-tunnel family inet6 hierarchies as part of an upgrade to add IPv6 support for
default multicast distribution tree (MDT) in Rosen 7, and data MDT ... | [
"Example: Configuring Source-Specific Multicast for Draft-Rosen Multicast VPNs"
] |
pim-ssm (Selective Tunnel) | pim-ssm {
group-range multicast-prefix;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel selective group group-address source source-address],
[edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel selective group group-address wildcard-source],
[edit logical-system... | Establish the multicast group address range to use for creating MBGP MVPN source-specific multicast
selective PMSI tunnels. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [] |
pim-to-igmp-proxy | pim-to-igmp-proxy {
upstream-interface [ interface-names ];
} | [edit logical-systems logical-system-name routing-options multicast],
[edit routing-options multicast] | Use the pim-to-igmp-proxy statement to have Internet Group Management Protocol (IGMP) forward
IPv4 multicast traffic across Protocol Independent Multicast (PIM) sparse mode domains.
Configure the rendezvous point (RP) routing device that resides between a customer edge-facing PIM
domain and a core-facing PIM domain to ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configuring PIM-to-IGMP Message Translation"
] |
pim-to-mld-proxy | pim-to-mld-proxy {
upstream-interface [ interface-names ];
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options multicast] | Configure the rendezvous point (RP) routing device that resides between a customer edge–facing
Protocol Independent Multicast (PIM) domain and a core-facing PIM domain to translate PIM join or
prune messages into corresponding Multicast Listener Discovery (MLD) report or leave messages. The
routing device then transmit... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configuring PIM-to-MLD Message Translation"
] |
ping clns | ping clns host
<brief>
<count requests>
<detail>
<do-not-fragment>
<interval seconds>
<logical-system logical-system-name>
<no-resolve>
<pattern string>
<rapid>
<routing-instance routing-instance-name>
<size bytes>
<source source-address>
<ttl value>
<verbose>
<wait seconds> | Check the reachability of a remote Connectionless Network Service (CLNS) node. Enter Ctrl+c to
interrupt a ping clns command. | [
{
"name": "host",
"desc": "IP address or hostname of the remote system to ping."
},
{
"name": "brief",
"desc": "(Optional) Display brief information."
},
{
"name": "count requests",
"desc": "(Optional) Number of ping requests to send. The range of values is 1 through 2,000,000,000. T... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request. An
exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply
was not received within the timeout period. An x indicates that an echo reply was received with an err... | Command introduced before Junos OS Release 7.4. | [] | |
ping fabric multicast-flow | ping fabric multicast-flow source-fmep-id source-fmep-id fma-name fma-name flow-spec-name flow-
specification-name
<verbose> | Send a fabric multicast ping command to the multicast group destination fabric maintenance endpoints
(FMEPs) configured in the flow specification. Send a single PDU with a timeout after 1 second. | [
{
"name": "flow-spec-name flow-specification-name",
"desc": "Name of the flow specification that defines the protocol parameters (unicast or multicast) for the fabric ping operation."
},
{
"name": "fma-name fma-name",
"desc": "Name of the FMA."
},
{
"name": "source-fmep-id source-fmep-id... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Output Fields
Table 109 on page 13042 lists the output fields for the ping fabric-multicast-flow command. Output fields
are listed in the approximate order in which they appear.
Table 109: ping fabric mu... | Command introduced in Junos OS Release 12.2. | [
"Overview of Internal Fabric Monitoring",
"Configuring a Fabric Maintenance Association",
"Configuring Flow Specifications"
] | |
ping fabric unicast-flow | ping fabric unicast-flow fma-name fma-name source-fmep-id source-fmep-id dest-fmep-id dest-fmep-
id flow-spec-name flow-specification-name
<count count>
<forced-fte-interface fte-interface>
<verbose> | Send a unicast fabric ping command to the destination fabric maintenance endpoints (FMEPs) specified. | [
{
"name": "count count",
"desc": "(Optional) Number of fabric ping PDUs to send. The maximum PDU count is 5. The default PDU count is 1."
},
{
"name": "dest-fmep-id destination-fmep-id",
"desc": "ID of the destination FMEP of the fabric ping operation."
},
{
"name": "flow-spec-name flow-... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Output Fields
Table 110 on page 13045 lists the output fields for the ping fabric-unicast-flow command. Output fields
are listed in the approximate order in which they appear.
Table 110: ping fabric unic... | Command introduced in Junos OS Release 12.2. | [
"Overview of Internal Fabric Monitoring",
"Configuring a Fabric Maintenance Association",
"Configuring Flow Specifications"
] | |
ping mpls bgp | ping mpls bgp fec
<bottom-label-ttl>
<count count>
<destination address>
<detail>
<exp forwarding-class>
<instance routing-instance-name>
<logical-system (all | logical-system-name)>
<size bytes>
<source source-address>
<sweep> | Check the operability of MPLS BGP-signaled label-switched path (LSP) connections. Press Ctrl+c to
interrupt a ping mpls bgp command.
NOTE: The ping mpls bgp fec command only supports single paths. | [
{
"name": "bottom-label-ttl",
"desc": "(Optional) Time-to-live (TTL) value for the bottom label in the label stack. The range of values is 1 through 255. The default value is 255."
},
{
"name": "count count",
"desc": "(Optional) Number of ping requests to send. If count is not specified, five pi... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request. An
exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply
was not received within the timeout period. An x indicates that an echo reply was received with an err... | Command introduced in Junos OS Release 11.1. | [] | |
ping mpls l2circuit | ping mpls l2circuit (interface interface-name | virtual-circuit virtual-circuit-id
neighbor address)
<count count>
<destination address>
<detail>
<exp forwarding-class>
<logical-system (all | logical-system-name)>
reply-mode (application-level-control-channel | ip-udp | no-reply)
<size bytes>
<source source-address>... | Check the operability of the MPLS Layer 2 circuit connections. Type Ctrl+c to interrupt a ping mpls
l2circuit command.
NOTE: This command is not supported on EX4500 and EX4550 switches. | [
{
"name": "count count",
"desc": "(Optional) Number of ping requests to send. If count is not specified, five ping requests are sent. The range of values is 1 through 1,000,000. The default value is 5."
},
{
"name": "destination address",
"desc": "(Optional) Specify an address other than the def... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request. An
exclamation point (!) indicates that an echo reply was received. A period ( .) indicates that an echo reply
was not received within the timeout period. An x indicates that an echo reply was received with an er... | Command introduced before Junos OS Release 7.4.
The size and sweep options were introduced in Junos OS Release 9.6.
The reply-mode option and its suboptions are introduced in Junos OS Release 10.4R1. | [] | |
ping mpls l2vpn | ping mpls l2vpn (instance instance-name local-site-id local-site-id-number remote-site-id
remote-site-id-number | interface interface-name)
<bottom-label-ttl>
<count count>
<destination address>
<detail>
<exp forwarding-class>
<logical-system (all | logical-system-name)>
reply-mode (application-level-control-channe... | Check the operability of MPLS Layer 2 virtual private network (VPN) connections. Type Ctrl+c to
interrupt a ping mpls l2vpn command. | [
{
"name": "bottom-label-ttl",
"desc": "(Optional) Display the time-to-live value for the bottom label in the label stack."
},
{
"name": "count count",
"desc": "(Optional) Number of ping requests to send. If count is not specified, five ping requests are sent. The range of values is 1 through 1,0... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request. An
exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply
was not received within the timeout period. An x indicates that an echo reply was received with an err... | Command introduced before Junos OS Release 7.4.
The size and sweep options were introduced in Junos OS Release 9.6.
The reply-mode option and its suboptions are introduced in Junos OS Release 10.4R1. | [] | |
ping mpls l3vpn | ping mpls l3vpn prefix prefix-name
<l3vpn-name>
<bottom-label-ttl>
<count count>
<destination address>
<detail>
<exp forwarding-class>
<logical-system (all | logical-system-name)>
<size bytes>
<source source-address>
<sweep> | Check the operability of a MPLS Layer 3 virtual private network (VPN) connection. Type Ctrl+c to
interrupt a ping mpls l3vpn command. | [
{
"name": "bottom-label-ttl",
"desc": "(Optional) Display the time-to-live value for the bottom label in the label stack."
},
{
"name": "count count",
"desc": "(Optional) Number of ping requests to send. If count is not specified, five ping requests are sent. The range of values is 1 through 1,0... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request. An
exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply
was not received within the timeout period. An x indicates that an echo reply was received with an err... | Command introduced before Junos OS Release 7.4.
The size and sweep options were introduced in Junos OS Release 9.6. | [] | |
ping mpls ldp | ping mpls ldp fec
<count count>
<destination address>
<detail>
<exp forwarding-class>
<instance routing-instance-name>
<logical-system (all | logical-system-name)>
<p2mp root-addr ip-address lsp-id identifier>
<size bytes>
<source source-address>
<stitched-protocol>
<sweep> | Check the operability of MPLS LDP-signaled label-switched path (LSP) connections. Type Ctrl+c to
interrupt a ping mpls command. | [
{
"name": "count count",
"desc": "(Optional) Number of ping requests to send. If count is not specified, five ping requests are sent. The range of values is 1 through 1,000,000. The default value is 5."
},
{
"name": "destination address",
"desc": "(Optional) Specify an address other than the def... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request. An
exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply
was not received within the timeout period. An x indicates that an echo reply was received with an er... | Command introduced before Junos OS Release 7.4.
size and sweep options introduced in Junos OS Release 9.6.
instance option introduced in Junos OS Release 10.0.
p2mp, root-address, and lsp-id options introduced in Junos OS Release 11.2. | [] | |
ping mpls lsp-end-point | ping mpls lsp-end-point prefix-name
<count count>
<destination address>
<detail>
<exp forwarding-class>
<instance routing-instance-name>
<logical-system (all | logical-system-name)>
<size bytes>
<source source-address>
<sweep> | Check the operability of MPLS label-switched path (LSP) endpoint connections. Type Ctrl+c to interrupt
a ping mpls command. | [
{
"name": "count count",
"desc": "(Optional) Number of ping requests to send. If count is not specified, five ping requests are sent. The range of values is 1 through 1,000,000. The default value is 5."
},
{
"name": "destination address",
"desc": "(Optional) Specify an address other than the def... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request. An
exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply
was not received within the timeout period. An x indicates that an echo reply was received with an err... | Command introduced before Junos OS Release 7.4.
The size and sweep options were introduced in Junos OS Release 9.6.
The instance option was introduced in Junos OS Release 10.0. | [] | |
ping mpls rsvp | ping mpls rsvp
<lsp-name>
<count count>
<destination address>
<detail>
<dynamic-bypass>
<egress egress-address>
<exp forwarding-class>
<interface interface-name>
<logical-system (all | logical-system-name)>
<manual-bypass>
<multipoint>
<size bytes>
<source source-address>
<standby standby-path-name>
<sweep> | Check the operability of MPLS RSVP-signaled label-switched path (LSP) connections. Type Ctrl+c to
interrupt a ping mpls command. | [
{
"name": "count count",
"desc": "(Optional) Number of ping requests to send. If count is not specified, five ping requests are sent. The range of values is 1 through 1,000,000. The default value is 5."
},
{
"name": "destination address",
"desc": "(Optional) Specify an address other than the def... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request. An
exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply
was not received within the timeout period. An x indicates that an echo reply was received with an err... | Command introduced before Junos OS Release 7.4.
The egress and multipoint options were introduced in Junos OS Release 9.2.
The size and sweep options were introduced in Junos OS Release 9.6.
The dynamic-bypass and manual-bypass options were introduced in Junos OS Release 10.2. | [] | |
ping mpls segment routing isis | ping mpls segment routing isis fec
<algorithm algorithm-id>
<count count>
<destination address>
<detail>
<exp forwarding-class>
<instance routing-instance-name>
<logical-system (all | logical-system-name)>
<p2mp root-addr ip-address lsp-id identifier>
<size bytes>
<source source-address>
<stitched-protocol>
<sweep> | Check the operability of MPLS segment routing label-switched path (LSP) connections added by ISIS
protocol. Type Ctrl+c to interrupt a ping mpls segment routing isis command. | [
{
"name": "algorithm",
"desc": ""
},
{
"name": "algorithm-id",
"desc": "(Optional) Specify the flexible algorithm identifier. The range of values is 0 through 255. The default value is 0 which means no algorithm is configured. The algorithm-id in conjunction with the prefix is used to distinguis... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request. An
exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply
was not received within the timeout period. An x indicates that an echo reply was received with an err... | Command introduced in Junos OS Release 19.1R1
algorithm option introduced in Junos OS Release 23.1R1 and Junos OS Evolved Release 23.1R1. | [] | |
ping mpls segment routing ospf | ping mpls segment routing ospf fec
algorithm algorithm-id
<count count>
<destination address>
<detail>
<exp forwarding-class>
<instance routing-instance-name>
<logical-system (all | logical-system-name)>
<p2mp root-addr ip-address lsp-id identifier>
<size bytes>
<source source-address>
<stitched-protocol>
<sweep> | Check the operability of MPLS segment routing label-switched path (LSP) connections added by ospf
protocol. Type Ctrl+c to interrupt a ping mpls segment routing ospf command. | [
{
"name": "algorithm",
"desc": ""
},
{
"name": "algorithm-id",
"desc": "(Optional) Specify the flexible algorithm identifier. The range of values is 0 through 255. The default value is 0 which means no algorithm is configured. The algorithm-id in conjunction with the prefix is used to distinguis... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request. An
exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply
was not received within the timeout period. An x indicates that an echo reply was received with an err... | Command introduced in Junos OS Release 19.1R1
algorithm option introduced in Junos OS Release 23.1R1 and Junos OS Evolved Release 23.1R1. | [] | |
ping mpls segment-routing spring-te | ping mpls segment-routing spring-te
<egress-ip (active | color | count | detail | exp | instance | logical-system | secondary |
segment-list | size | skip-fec-validation | source | sweep | tunnel-source) >
<label-stack ( detail | egress | labels | logical-system | nexthop-address | nexthop-interface )
>
<source-rou... | Check the operability of MPLS segment routing label-switched path (LSP) connections added by
segment routing traffic-engineered (SPRING-TE) protocol. Type Ctrl+c to interrupt a ping mpls segment
routing spring-te command. | [
{
"name": "egress-ip",
"desc": "Specify to ping to or install IP address to use when sending probes."
},
{
"name": "active",
"desc": "Specify to use the forwarding path or nexthops from the RIB table."
},
{
"name": "color",
"desc": "Specify the color identifier for the tunnel end-poi... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request. An
exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply
was not received within the timeout period. An x indicates that an echo reply was received with an err... | Command introduced in Junos OS Release 20.2R1. | [] | |
ping mpls segment routing static egress-ip | ping mpls segment-routing static egress-ip
<egress-ip (fec | count | destination | detail | exp | instance | logical-system | size | source
| sweep) >
ping mpls segment-routing spring-te label-stack
<label-stack (count | destination | detail | egress | exp | labels | logical-system | nexthop-
address | nexthop-interfa... | Use ping mpls segment-routing static to check the MPLS segment routing label-switched path (LSP)
connections on the prpd programmed static routes. Type Ctrl+c to interrupt a ping mpls segment-routing
static command. | [
{
"name": "egress-ip",
"desc": "Specify to ping PRPD-programmed labelled switched paths (LSP)."
},
{
"name": "<fec>",
"desc": "Specify to use the IP prefix/length of forwarding equivalence class."
},
{
"name": "count count",
"desc": "(Optional) Specify number of ping requests to send... | Network
Output Fields
When you enter ping mpls segment-routing static command, you can see the feedback on the status of
your request. An exclamation point (!) indicates that an echo reply. A period (.) indicates that an echo
reply is not received within the timeout period. An x indicates that an echo reply with an err... | Command introduced in Junos OS Release 22.4R1. | [] | |
ping overlay | ping overlay
<tunnel-type>
vni vni
tunnel-src ip-source-address
tunnel-dst ip-destination-address
<mac mac-address>
<count requests>
<ttl value>
<hash source-udp-port>
<hash-source-mac source-mac-address>
<hash-destination-mac destination-mac-address>
<hash-source-address source-IP-address>
<hash-destination-address de... | Verify the presence of the Virtual Extensible LAN (VXLAN) tunnel endpoints (VTEPs), which can
originate and terminate VXLAN tunnels, and service connectivity within the context of the overlay
VXLAN segment. Use ping overlay as a fault detection tool to determine failure within an overlay VXLAN
tunnel. Type Ctrl+c to in... | [
{
"name": "tunnel-type",
"desc": "(Optional) Specify the overlay tunnel type used in a virtualized environment such as: VXLAN, Network Virtualization using Generic Routing Encapsulation (NVGRE), MPLS over User Datagram Protocol (UDP), and MPLS over General Routing Encapsulation (GRE) tunnels. NOTE: Only VXL... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request. An
exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply
was not received within the timeout period. An x indicates that an echo reply was received with an er... | Command introduced in Junos OS Release 14.1X53-D30. | [
"Understanding Overlay ping and traceroute Packet Support",
"Example: Troubleshoot a VXLAN Overlay Network with Overlay Ping and Overlay Traceroute on QFX",
"Series Switches"
] | |
ping srv6 spring-te micro-sids-stack | ping srv6 spring-te micro-sids-stack usids ipv6addr nexthop-interface nexthop-interface nexthop-
address ipv6addr
<count>
<source ipv6addr>
<detail>
<size>
<ttl>
<instance instance>
<pattern pattern>
<tos>
<interval>
<sweep>
<logical-system> | Sends ICMP Echo Requests (ping) along a Segment Routing over IPv6 (SRv6) path defined by a user-
configured micro Segment ID (uSID) stack. This allows reachability testing for SRv6 micro segment paths
using SPRING-TE.
Use this command to validate that each micro-segment in the SRv6 stack is reachable and programmed
cor... | [
{
"name": "count",
"desc": "(Optional) Number of ping requests to send."
},
{
"name": "source",
"desc": "(Optional) Source address of echo request."
},
{
"name": "detail",
"desc": "(Optional) Display detailed output."
},
{
"name": "size",
"desc": "(Optional) Size of reque... | network | Command introduced in Junos OS Release 23.4R1. | [] | |
ping srv6 | ping srv6 spring-te sids-stack
<count requests>
<detail>
<instance routing-instance-name>
<interval seconds>
<logical-system logical-system-name>
<nexthop-address IPv6-address>
<nexthop interface interface-name>
<pattern hex-string>
<sids value>
<size bytes>
<source source-address>
<sweep>
<tos type-of-service>
<ttl ... | Check the reachability of a Segment Routing with IPv6 data plane (SRv6) network. | [
{
"name": "host",
"desc": "IPv6 loopback address or SRv6 Segment Identifier (SID) of the remote system to ping."
},
{
"name": "count requests",
"desc": "(Optional) Number of ping requests to send. The range of values is 1 through 1,000,000. The default value is 5."
},
{
"name": "detail",... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request. An
exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply
was not received within the timeout period. An x indicates that an echo reply was received with an err... | Command introduced in Junos OS Release 21.2. | [] | |
ping vpls instance | ping vpls instance instance-name destination-mac address source-ip address
<bd-name name>
<control-plane-response>
<count number>
<detail>
<learning-vlan-id number>
<logical-system logical-system-name> | Check the operability of virtual private LAN service (VPLS) connections. Type Ctrl+c to interrupt a ping
vpls instance command.
When you issue a ping vpls instance command, a chassis MAC address is drawn from the ingress PE
router's pool of MAC addresses and used to create the VPLS ping packet. The ping packet is then
... | [
{
"name": "instance instance-name",
"desc": "Specify the name of the VPLS routing instance."
},
{
"name": "destination-mac address",
"desc": "Specify a destination MAC address for the ping echo requests."
},
{
"name": "source ip address",
"desc": "IP address of the outgoing interface... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request. An
exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply
was not received within the timeout period. An x indicates that an echo reply was received with an err... | Command introduced in Junos OS Release 9.1. | [] | |
ping | ping host
<bypass-routing>
<ce-ip destination-ip-address instance routing-instance-name source-ip source-ip-address>
<count requests>
<do-not-fragment>
<inet | inet6>
<interface source-interface>
<interval seconds>
<no-resolve>
<pattern string>
<rapid>
<record-route>
<routing-instance routing-instance-name>
<size by... | Check host reachability and network connectivity. The ping command sends Internet Control Message
Protocol (ICMP) ECHO_REQUEST messages to elicit ICMP ECHO_RESPONSE messages from the
specified host. Press Ctrl+c to interrupt a ping command. | [
{
"name": "host",
"desc": "IP address or hostname of the remote system to ping."
},
{
"name": "bypass-routing",
"desc": "(Optional) Bypass the normal routing tables and send ping requests directly to a system on an attached network. If the system is not on a directly attached network, an error i... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request. An
exclamation point (!) indicates that an echo reply was received. A period (.) indicates that an echo reply
was not received within the timeout period. An x indicates that an echo reply was received with an er... | Command introduced before Junos OS Release 7.4.
ce-ip option introduced in Junos OS Release 17.3 for MX Series routers with MPC and MIC interfaces.
The following options are deprecated for Junos OS Evolved Release 18.3R1: detail, logical-system, loose-
source, mac-address, strict, strict-source, and vpls.
The command t... | [
"Rate Limit ICMPv4 and ICMPv6 Traffic",
"Pinging Customer Edge Device IP Address"
] | |
ping-death (IDS Screen Next Gen Services) | ping-death; | [edit services screen ids-option screen-name icmp] | Identify and drop oversized and irregular ICMP packets, which protects against the ping of death attack.
In the ping of death attack, the attacker sends the target ping packets whose IP datagram length (ip_len)
exceeds the maximum legal length (65,535 bytes) for IP packets, and the packets are fragmented. When
the targ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
ping-death | ping-death; | [edit security screen ids-option screen-name icmp] | Configure the device to detect and reject oversized and irregular ICMP packets. Although the TCP/IP
specification requires a specific packet size, many ping implementations allow larger packet sizes. Larger
packets can trigger a range of adverse system reactions, including crashing, freezing, and restarting. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
ping-interval | ping-interval seconds; | [edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name oam],
[edit logical-systems logical-system-name routing-instances instance-name protocols l2vpn oam],
[edit logical-systems logical-system-name routing-instances instance-name protocols vpls
neighbor address oam], ... | Configure the time interval between ping messages for bidirectional forwarding detection (BFD)
sessions enabled over pseudowires inside a VPN. | [
{
"name": "seconds",
"desc": "Time interval between ping messages."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
Support for FEC 129 VPLS added in Junos OS Release 12.2. | [
"Configuring BFD for VCCV for Layer 2 VPNs, Layer 2 Circuits, and VPLS",
"Junos OS VPNs Library for Routing Devices"
] |
pki (Services) | pki {
auto-re-enrollment {
certificate-id {
ca-profile ca-profile-name;
challenge-password password;
re-enroll-trigger-time-percentage percentage;
re-generate-keypair;
validity-period days;
}
}
ca-profile ca-profile-name {
c... | [edit security] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5.
revocation-check and crl statements added in Junos OS Release 8.1. | [
"Enroll a Certificate"
] |
pki | pki {
auto-re-enrollment;
ca-profile ca-profile-name;
default-trusted-ca-certs (Security);
traceoptions;
trusted-ca-group trusted-ca-group-name {
ca-profiles ca-profiles;
}
} | [edit security] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and rest... | [
{
"name": "auto-re-enrollment",
"desc": "Configure the automatic reenrollment of a local end-entity (EE) certificate."
},
{
"name": "ca-profile ca-profile-name",
"desc": "Configure certificate authority (CA) profile."
},
{
"name": "default-trusted-ca-certs",
"desc": "Configure automa... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 8.5.
default-trusted-ca-certs option is added in Junos OS Release 23.2R1. | [
"Basic Elements of PKI in Junos OS"
] |
platform-parameters | platform-parameters {
no-mac-flush-on-aa-ae-down (disable | enable);
} | [edit protocols l2-learning] | Set platform-specific options for Layer 2 (L2) address learning features.
The options are explained separately. You can also see CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.3R2 and Junos OS Release 21.4R1. | [] |
plmn | plmn name {
mcc mcc;
mnc mnc;
} | [edit services agf] | Configure the public land mobile networks (PLMNs) that the Access Gateway Function (AGF) supports. | [
{
"name": "name",
"desc": "Public land mobile network (PLMN) name"
},
{
"name": "mcc mcc",
"desc": "Mobile country code"
},
{
"name": "mnc mnc",
"desc": "Mobile network code"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.3R1. | [] |
poe | For switches other than EX6200 and EX8200 switches:
poe {
guard-band watts;
interface (all | interface-name) {
disable;
maximum-power watts;
priority (high | low);
telemetries {
disable;
duration hours;
interval minutes;
}
}
lld... | [edit] | Configure PoE options. PoE ports on Juniper network switches provide power to PoE-enabled devices
only when straight-through cables are used. Power is not provided when crossover cables are used.
The remaining statements are explained separately. See CLI Explorer. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge. | [
"Configuring PoE Interfaces on EX Series Switches",
"Configuring Power over Ethernet in a Junos Fusion"
] |
point-to-point (MVRP) | point-to-point; | [edit logical-systems logical-system-name protocols mvrp interface (all | interface-name)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols mvrp
interface (all | interface-name)],
[edit protocols mvrp interface (all | interface-name)],
[edit routing-instances routing-instanc... | (Optional) For Multiple VLAN Registration Protocol (MVRP) configurations, configure an interface to be
recognized as a point-to-point connection. If specified, a point-to-point subset of the MRP state
machine is used to provide a simpler and more efficient method to accelerate convergence on the
network. Point-to-point... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Example: Configuring Automatic VLAN Administration Using MVRP on MX Series Routers",
"Configuring Multiple VLAN Registration Protocol (MVRP) to Manage Dynamic VLAN Registration",
"Verifying That MVRP Is Working Correctly",
"Understanding Multiple VLAN Registration Protocol (MVRP) for Dynamic VLAN Registratio... |
point-to-point | point-to-point; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | For all interfaces except aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet, configure the
interface unit as a point-to-point connection. This is the default connection type.
Default
If you omit this statement, the interface unit is configured as a point-to-point connection. | [] | 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 a Point-to-Point Connection"
] |
policer (Applying to a Logical Interface) | policer {
input policer-name;
output policer-name;
} | [edit interfaces interface-name unit unit-number],
[edit interfaces interface-name unit unit-number family family],
[edit logical-systems logical-system-name interfaces interface-name unit unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit unit-number
family family] | Apply a single-rate two-color policer—except for a physical interface policer—to Layer 3 input or output
traffic at a logical interface.
•
To rate-limit all traffic types, regardless of the protocol family, you can apply a logical interface policer
at the logical unit level of a supported interface.
•
To rate-limit tra... | [
{
"name": "input policer-name",
"desc": "Name of one policer to evaluate packets received on the interface."
},
{
"name": "output policer-name",
"desc": "Name of one policer to evaluate packets transmitted on the interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"Single-Rate Two-Color Policer Overview",
"Bandwidth Policer Overview",
"Logical Interface (Aggregate) Policer Overview"
] | |
policer (CFM Firewall) | policer cfm-policer {
if-exceeding {
bandwidth-limit 8k;
burst-size-limit 2k;
}
then discard;
} | [edit firewall] | Attach an explicit policer to CFM sessions. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Configuring Rate Limiting of Ethernet OAM Messages"
] |
policer (CFM Global) | policer {
all cfm-policer-name;
continuity-check cfm-policer-name;
other cfm-policer-name;
}
} | [edit protocols oam ethernet connectivity-fault-management] | Specify a policer at the global level to police the CFM traffic belonging to all sessions. | [
{
"name": "continuity-check cfm-policer-name",
"desc": "Police all continuity check packets with the policer specified."
},
{
"name": "other cfm-policer-name",
"desc": "Police all non-continuity check packets with the policer specified."
},
{
"name": "all cfm-policer-name",
"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.0. | [
"Configuring Connectivity Fault Management (CFM)"
] |
policer (CFM Session) | policer {
all cfm-policer-name;
continuity-check cfm-policer-name;
other cfm-policer-name;
}
} | [edit protocols oam ethernet connectivity-fault-management maintenance-domain name level number
maintenance-association name] | Specify a separate policer to rate-limit packets specific to that session. | [
{
"name": "continuity-check cfm-policer-name",
"desc": "Police continuity check packets belonging to this session."
},
{
"name": "other cfm-policer-name",
"desc": "Police all non-continuity check packets belonging to this session."
},
{
"name": "all cfm-policer-name",
"desc": "Police... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Configuring Connectivity Fault Management (CFM)"
] |
policer (Configuring) | policer policer-name {
filter-specific;
counter {
counter-id counter-index;}
if-exceeding {
bandwidth-limit bps;
bandwidth-percent number;
burst-size-limit bytes;
}
logical-bandwidth-policer;
logical-interface-policer;
physical-interface-policer;
shared-ba... | [edit dynamic-profiles profile-name firewall],
[edit firewall],
[edit logical-systems logical-system-name firewall] | Configure policer rate limits and actions. When included at the [edit firewall] hierarchy level, the policer
statement creates a template, and you do not have to configure a policer individually for every firewall
filter or interface. To activate a policer, you must include the policer-action modifier in the then state... | [
{
"name": "policer-action",
"desc": "One or more actions to take:"
},
{
"name": "discard",
"desc": "Discard traffic that exceeds the rate limits."
},
{
"name": "forwarding-class class-name",
"desc": "Specify the particular forwarding class."
},
{
"name": "loss-priority",
... | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
The out-of-profile policer action added in Junos OS Release 8.1.
The logical-bandwidth-policer statement added in Junos OS Release 8.2.
Logical systems support introduced in Junos OS Release 9.3.
The physical-interface-policer statement introduced in Junos OS Release 9.... | [
"Bandwidth Policer Overview",
"Configuring Firewall Filters and Policers for VPLS",
"Configuring Multifield Classifiers",
"Logical Interface (Aggregate) Policer Overview",
"Physical Interface Policer Overview",
"Single-Rate Two-Color Policer Overview",
"Using Multifield Classifiers to Set Packet Loss Pr... |
policer (CoS) | policer cos-policer-name {
aggregate {
bandwidth-limit bps;
burst-size-limit bytes;
}
premium {
bandwidth-limit bps;
burst-size-limit bytes;
}
} | [edit interfaces interface-name gigether-options ethernet-switch-profile ethernet-policer-profile] | For Gigabit Ethernet IQ , Gigabit Ethernet PICs with SFPs (except the 10-port Gigabit Ethernet PIC and
the built-in Gigabit Ethernet port on the M7i router), and 100-Gigabit Ethernet Type 5 PIC with CFP,
define a CoS policer template to specify the premium bandwidth and burst-size limits, and the aggregate
bandwidth an... | [
{
"name": "cos-policer-name",
"desc": "Name of one policer to specify the premium bandwidth and burst-size limits, and the"
}
] | 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 Gigabit Ethernet Policers"
] |
policer (Firewall Filter Action) | policer policer-name; | [edit firewall family family-name filter filter-name term term-name then],
[edit logical-systems logical-system-name firewall family family-name filter filter-name term term-
name then] | For T Series routers and M320 routers with Enhanced II Flexible PIC Concentrators (FPCs) and the T640
Core Router with Enhanced Scaling FPC4, apply a tricolor marking policer. | [
{
"name": "policer-name",
"desc": "Name of a single-rate two-color policer to use to rate-limit traffic."
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Logical systems support introduced in Junos OS Release 9.3. | [
"Firewall Filter Nonterminating Actions",
"Two-Color Policer Configuration Overview"
] |
policer (Interface) | policer {
arp policer-template-name;
input policer-template-name;
output policer-template-name;
} | [edit interfaces irb unit logical-unit-number family inet],
[edit interfaces interface-name unit logical-unit-number family family],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family inet] | Apply a policer to an interface. | [
{
"name": "arp policer-template-name",
"desc": "For inet family only, name of one policer to evaluate when ARP packets are"
},
{
"name": "input policer-template-name",
"desc": "Name of one policer to evaluate when packets are received on the interface."
},
{
"name": "output policer-templ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for MX Series routers added in Junos OS Release 20.2R1 | [
"Applying Policers",
"Configuring Firewall Filters and Policers for VPLS",
"Routing Policies, Firewall Filters, and Traffic Policers User Guide",
"Junos OS Services Interfaces Library for Routing Devices"
] |
policer (Layer 2 VPN) | policer {
input policer-template-name;
output policer-template-name;
} | [edit interfaces interface-name unit logical-unit-number family (ccc | inet | tcc)],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family (ccc | inet | tcc)] | Use policing to control the amount of traffic flowing over the interfaces servicing a Layer 2 VPN. | [
{
"name": "input policer-template-name",
"desc": "Name of one policer to evaluate when packets are received on the interface."
},
{
"name": "output policer-template-name",
"desc": "Name of one policer to evaluate when packets are transmitted on the"
}
] | 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 Traffic Policing in Layer 2 VPNs",
"Routing Policies, Firewall Filters, and Traffic Policers User Guide",
"Junos OS Network Interfaces Library for Routing Devices"
] |
policer (MAC) | policer {
input cos-policer-name;
output cos-policer-name;
} | [edit interfaces interface-name unit logical-unit-number accept-source-mac mac-address mac-address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
accept-source-mac mac-address mac-address] | For Gigabit Ethernet IQ and Gigabit Ethernet PICs with SFPs (except the 10-port Gigabit Ethernet PIC
and the built-in Gigabit Ethernet port on the M7i router), and 100-Gigabit Ethernet Type 5 PIC with CFP,
configure MAC policing.
NOTE: On MX Series routers with Gigabit Ethernet or Fast Ethernet PICs, the following
cons... | [
{
"name": "input cos-policer-name",
"desc": "Name of one policer to specify the premium bandwidth and aggregate bandwidth."
},
{
"name": "output cos-policer-name",
"desc": "Name of one policer to specify the premium bandwidth and aggregate"
}
] | 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 Gigabit Ethernet Policers"
] |
policer | policer policer-name {
filter-specific;
if-exceeding {
bandwidth-limit bps;
burst-size-limit bytes;
}
then {
policer-action;
}
} | [edit firewall] | Configure policer rate limits and actions. To activate a policer, you must include the policer action
modifier in the then statement in a firewall filter term.
Each policer that you configure includes an implicit counter that counts the number of packets that
exceed the rate limits that are specified for the policer. I... | [
{
"name": "policer-name",
"desc": "Name that identifies the policer. The name can contain letters, numbers, hyphens (-), and"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring Two-Color and Three-Color Policers to Control Traffic Rates",
"Configuring Firewall Filters",
"Overview of Policers"
] |
policer-charge | policer-charge | [edit firewall family firewall filter family filter filter name term term name then] | Hierarchical policers support policing of premium and non-premium traffic. The former is policed by a
premium policer and the latter by an aggregate policer. Premium traffic is subject to expedited
forwarding. Non-premium traffic is subject to non-expedited forwarding. Out of the aggregate
bandwidth available to both t... | [] | firewall—To view this statement in the configuration.
firewall -control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.4R1 | [] |
policer-drop-probability-low | policer-drop-probability-low; | [edit chassis] | Reduces the possibility that policers configured on the router might drop packets. For some Juniper
Networks routers, policers can mark packets as out-of-specification in accordance with TCP. By default,
these policers begin to randomly drop packets when the current credit exceeds the credit limit. In the
context of TC... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4R1. | [
"show pfe cfeb",
"show pfe feb",
"show pfe fpc"
] |
policer-overhead | policer-overhead {
egress bytes;
ingress bytes;
policer-overhead-value;
} | [edit interfaces interface-name unit number] | Policer overhead adjustment for the logical interface. The adjustment can be made to ingress policers,
egress policers, or both.
NOTE: The policer overhead adjustment only works on the "logical-interface-policer" on
page 10491. | [
{
"name": "egress",
"desc": "Optional. Egress overhead adjustment in bytes. Range: -64 through 64"
},
{
"name": "ingress",
"desc": "Optional. Ingress overhead adjustment in bytes. Range: -64 through 64"
},
{
"name": "policer-overhead-value",
"desc": "Policer overhead adjustment to ... | interface | Statement introduced in Junos OS Release 18.2R1. | [] |
policer-overhead-adjustment | interfaces interface-name
unit unit-number
policer-overhead <ingress | egress> <adjustment in-bytes>
policer-overhead <adjustment in-bytes> | [edit interfaces interface-name unit logical-unit-number] | Add the configured number of bytes to the length of a packet entering the interface or leaving the
interface. The policer overhead adjustment at per IFL or direction granularity is in the range of -64 bytes
to +64 bytes.
NOTE: If you configure the policer-overhead adjustment statement without the ingress or
egress opti... | [
{
"name": "adjustment-in-bytes",
"desc": "Policer overhead bytes to be accounted in ingress and egress. Number of bytes used"
}
] | 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. | [
"Accounting of the Policer Overhead Attribute at the Interface Level",
"Configuring the Accounting of Policer Overhead in Interface Statistics"
] |
policies (Security) | policies {
default-policy (deny-all | permit-all);
from-zone from-zone-name {
to-zone;
policy name {
description description;
match (Security Policies Global) {
source-address (Security Policies);
destination-address (Security Policies);
... | [edit security] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "default-policy",
"desc": "Configure a default action when no user-defined policy match. Values:"
},
{
"name": "deny-all",
"desc": "Deny all traffic if no policy match"
},
{
"name": "permit-all",
"desc": "Permit all traffic if no policy match"
},
{
"name": "policy-... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5.
Support for the services-offload option added in Junos OS Release 11.4.
Support for the source-identitiy option added in Junos OS Release 12.1.
Support for the description option added in Junos OS Release 12.1.
Support for the ssl-termination-profile and web-redirect-to-htt... | [
"Security Policies Overview"
] |
policing (Protocols LDP) | policing {
fec fec-address {
ingress-traffic filter-name;
transit-traffic filter-name;
}
} | [edit logical-systems logical-system-name protocols ldp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp],
[edit protocols ldp],
[edit routing-instances routing-instance-name protocols ldp] | Enable policing of forwarding equivalence classes (FECs) for LDP. | [
{
"name": "fec fec-address",
"desc": "Specify the address for the FEC."
},
{
"name": "ingress-traffic filter-name",
"desc": "Specify the name of the filter for policing ingress FEC traffic."
},
{
"name": "transit-traffic filter-name",
"desc": "Specify the name of the filter for polic... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Policers for LDP FECs"
] |
policing (Protocols MPLS) | policing {
filter filter-name;
no-auto-policing;
} | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
ingress],
[edit protocols mpls label-switched-path lsp-name],
[edit protocols mpls static-label-switched-path lsp-name ingress] | Specify the policing filter for the LSP. | [
{
"name": "filter filter-name",
"desc": "Specify the name of the policing filter."
},
{
"name": "no-auto-policing",
"desc": "Disable automatic policing on this LSP."
}
] | 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.
NOTE: Filter based LSP policing is not supported for point-to-multipont LSPs. | [
"Configuring Policers for LSPs"
] |
policing | policing (filter filter-name | no-automatic-policing); | [edit protocols mpls label-switched-path lsp-name]
[edit interfaces interface-id unit number-of-logical-unit family inet address ip-address] | Apply a rate-limiting policer as the specified policing filter:
•
To the LSP for MPLS over CCC.
•
To the customer-edge interface for IP over MPLS. | [
{
"name": "filter filter-name",
"desc": "Specify the name of the policing filter."
},
{
"name": "no-automatic-policing",
"desc": "Disable automatic policing on this LSP."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1 . | [
"Configuring Policers to Control Traffic Rates (CLI Procedure)",
"Configuring CoS on an MPLS Provider Edge Switch Using Circuit Cross-Connect",
"Configuring CoS on an MPLS Provider Edge Switch Using IP Over MPLS"
] |
policy (advanced-policy-based-routing) | policy name {
description description;
match {
source-address;
destination-address;
application [ application ... ];
source-identity;
destination-address-excluded;
source-address-excluded;
}
scheduler-name scheduler-name;
then {
application-services {
advance... | [edit security advance-policy-based-routing from-zone name],
[edit logical-systems name security advance-policy-based-routing from-zone],
[edit logical-systems name tenants name security advance-policy-based-routing from-zone],
[edit tenants name security advance-policy-based-routing from-zone] | Configure advanced policy-based routing (APBR) policies.
You can create APBR policies for a security zone and apply advanced policy-based routing (APBR)
profiles on the traffic that matches the policy.
In the APBR policy, you can define source addresses, destination addresses, and applications as match
conditions; and ... | [
{
"name": "policy policy-name",
"desc": "Specify the name of the APBR policy."
},
{
"name": "description",
"desc": "Specify descriptive text for the APBR policy."
},
{
"name": "match",
"desc": "Specify an APBR policy match-criteria."
},
{
"name": "source-address",
"desc":... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1 | [
"Advanced Policy-Based Routing"
] |
policy (Aggregate and Generated Routes) | policy policy-name; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options (aggregate | generate) (defaults | route)],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name (aggregate | generate) (defaults | route)],
[edit logic... | Associate a routing policy when configuring an aggregate or generated route’s destination prefix in the
routes part of the aggregate or generate statement. This provides the equivalent of an import routing
policy filter for the destination prefix. That is, each potential contributor to an aggregate route, along
with an... | [
{
"name": "policy-name",
"desc": "Name of a routing policy."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Summarizing Static Routes Through Route Aggregation"
] |
policy (Event Policy) | policy policy-name {
attributes-match {
event1.attribute-name equals event2.attribute-name;
event.attribute-name matches regular-expression;
event1.attribute-name starts-with event2.attribute-name;
}
events [ events ];
then {
... the then subhierarchy appears at the end o... | [edit event-options] | Define an event policy to be processed by the eventd process. If you configure a policy, the events and
then statements are mandatory.
You can configure multiple policies to be processed for an event. The policies are executed in the order
in which they appear in the configuration. If you configure more than one policy... | [
{
"name": "policy-name",
"desc": "Name of an event policy."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5. | [] |
policy (Explicit-Proxy) | policy name {
description description;
match {
destination-address;
destination-address-excluded;
destination-identity-feed [ destination-identity-feed ... ];
dynamic-application;
application;
source-address;
source-address-excluded;
source-identity;
source-iden... | [edit security policies explicit-proxy profile] | Define a explicit proxy profiles policies. | [
{
"name": "name",
"desc": "Security policy name. Range: 1 through 63 characters"
},
{
"name": "description",
"desc": "Text description of policy. The descriptive text should not include characters “<”, “>”, “&”, or “\\n”. The upper limit of the description text range is related to character enco... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [] |
policy (Flow Maps) | policy [ policy-names ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast flow-map flow-map-name],
[edit logical-systems logical-system-name routing-options multicast flow-map flow-map-name],
[edit routing-instances routing-instance-name routing-options multicast flow-map flow-map-nam... | Configure a flow map policy. | [
{
"name": "policy-names",
"desc": "Name of one or more policies for flow mapping."
}
] | routing—To view this statement in the configuration. | Statement introduced in Junos OS Release 8.2. | [] |
policy (IPsec) | policy policy-name {
description description;
perfect-forward-secrecy {
keys (group1 | group2 |group5 |group14 |group15 | group16 | group24);
}
proposals [ proposal-names ];
} | [edit services ipsec-vpn ipsec] | Define an IPsec policy. | [
{
"name": "policy-name",
"desc": "IPsec policy name."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IPsec Policies"
] |
policy (Multicast-Only Fast Reroute) | policy policy-name; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast stream-protection],
[edit logical-systems logical-system-name routing-options multicast stream-protection],
[edit routing-instances routing-instance-name routing-options multicast stream-protection],
[edit rout... | When you configure multicast-only fast reroute (MoFRR), apply a routing policy that filters for a
restricted set of multicast streams to be affected by your MoFRR configuration. You can apply filters
that are based on source or group addresses.
For example:
routing-options {
multicast {
stream-protection {
... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Understanding Multicast-Only Fast Reroute",
"Example: Configuring Multicast-Only Fast Reroute in a PIM Domain",
"Example: Configuring Multicast-Only Fast Reroute in a PIM Domain on Switches",
"Example: Configuring Multicast-Only Fast Reroute in a Multipoint LDP Domain"
] |
policy (PIM rpf-vector) | policy [policy-name]; | [edit dynamic-profiles name protocols pim rp rpf-vector],
[edit logical-systems name protocols pim rprpf-vector],
[edit logical-systems name routing-instances name protocols pim rp rpf-vector],
[edit protocols pim rp rpf-vector],
[edit routing-instances name protocols pim rp rpf-vector] | Create a filter policy. The configured device checks the policy configuration to determine whether or not
to apply "rpf-vector" on page 16609 to (S,G).
RPF Vector Policy Example
This example policy shows Source and Group, using Source, using Group.
policy-statement pim-rpf-vector-example {
term A {
... | [] | routing | Statement introduced in Junos OS Release 17.3R1. | [] |
policy (Protocols Multipoint LDP) | policy policy-name; | [edit logical-systems logical-system-name protocols pim mldp-inband-signalling],
[edit protocols pim mldp-inband-signalling] | Multipoint LDP (M-LDP) in-band signaling enables you to carry multicast traffic across an existing IP/
MPLS backbone, while avoiding the use of PIM in the provider core.
On the egress nodes of the point-to-multipoint LSP, specify an M-LDP join translation filter policy where
PIM messages are translated into M-LDP FEC b... | [
{
"name": "policy-name",
"desc": "Name of a policy configured at the [edit policy-options] hierarchy level."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"No Link Title"
] |
policy (Security Alarms) | policy {
application {
duration interval;
size count;
threshold value;
}
destination-ip {
duration interval;
size count;
threshold value;
}
policy match {
duration interval;
size count;
threshold value;
}
source-ip {
... | [edit security alarms potential-violation] | Configure alarms for policy violation, based on source IP, destination IP, application, and policy rule. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Security Policies Overview"
] |
policy (Security Group VPN IKE) | policy policy-name {
description description;
mode2 (aggressive | main);
pre-shared-key (ascii-text key | hexadecimal key);
proposals proposal-name;
} | [edit security group-vpn member ike]
[edit security group-vpn server ike] | Configure an IKE policy. An IKE policy defines a combination of security parameters (IKE proposals) to
be used during IKE negotiation. It defines a peer address, the preshared key for the given peer, and the
proposals needed for that connection. During the IKE negotiation, IKE looks for an IKE policy that is the
same o... | [
{
"name": "policy policy-name",
"desc": "Name of the IKE policy. The policy name can be up to 32 alphanumeric characters long."
},
{
"name": "description",
"desc": ""
},
{
"name": "description",
"desc": "Specify descriptive text for an IKE policy."
},
{
"name": "mode",
"d... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Group VPNv2 Overview"
] |
policy (Security IKE) | policy policy-name {
blocklist blocklist-name;
certificate {
local-certificate certificate-id;
peer-certificate-type (pkcs7 | x509-signature);
policy-oids [ oid ];
trusted-ca {
ca-profile ca-profile-name;
trusted-ca-group trusted-ca-group-name;
}
... | [edit security ike] | IKE policies define a combination of security parameters (IKE proposals) to be used during IKE
negotiation, including peer address, the preshared key for the given peer, and the proposals needed for
that connection. During the IKE negotiation, IKE looks for an IKE policy that is the same on both peers.
The peer that in... | [
{
"name": "policy-name",
"desc": "Name of the IKE policy. The policy name can be up to 32 alphanumeric characters long."
},
{
"name": "blocklist blocklist-name",
"desc": "Specify the name of the corresponding remote peer's IKE identity blocklist. The"
},
{
"name": "certificate",
"des... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 8.5.
Support for suiteb-gcm-128 and suiteb-gcm-256 options added in Junos OS Release 12.1X45-D10.
Support for policy-oids option added in Junos OS Release 12.3X48-D10.
Support for trusted-ca option added in Junos OS Release 18.1R1.
Support for reauth-frequency option added in Juno... | [
"IPsec Overview",
"Example: Configuring AutoVPN with Pre-Shared Key"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.