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 |
|---|---|---|---|---|---|---|---|
ovsdb-managed | ovsdb-managed; | [edit bridge-domains bridge-domain-name vxlan],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name vxlan],
[edit routing-instances routing-instance-name switch-options],
[edit routing-instances routing-instance-name vlans vlan-name vxlan],
[edit routing-instances routing-instance-name v... | Disable a Juniper Networks device from learning about other Juniper Networks devices that function as
hardware virtual tunnel endpoints (VTEPs) in a specified Virtual Extensible LAN (VXLAN) and the media
access control (MAC) addresses learned by the hardware VTEPs. Instead, the Juniper Networks device
uses the Open vS... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1R2. | [
"Understanding Dynamically Configured VXLANs in an OVSDB Environment",
"Configuring OVSDB-Managed VXLANs"
] |
owner (RMON) | owner owner-name; | [edit snmp rmon history] | Specify the user or group responsible for this RMON history configuration. | [
{
"name": "owner-name",
"desc": "The user or group responsible for this configuration."
}
] | snmp—To view this statement in the configuration.
snmp–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"RMON Overview",
"RMON MIB Event, Alarm, Log, and History Control Tables"
] |
owner | owner name {
test test-name {
data-fill data;
data-size size;
destination-port port;
dscp-code-points (RPM) dscp-bits;
history-size size;
moving-average-size number;
offload-type {
none;
pfe-timestamp;
}
probe-count coun... | [edit services monitoring rpm] | Specify an owner name and test options. The owner name combined with the test options for a
particular test name represents a single RPM configuration instance. | [
{
"name": "owner",
"desc": ""
},
{
"name": "name",
"desc": "You can configure any name, up to 32 characters in length, or specify one of the pre-defined owner names:"
},
{
"name": "icmp-evo",
"desc": ""
},
{
"name": "icmp-junos",
"desc": ""
},
{
"name": "udp-evo",... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 20.1R1.
traps option introduced in Junos OS Evolved Release 21.2R1. | [
"Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, and MX Series",
"Routers"
] |
oxid | oxid (enable | disable) | QFX Series Standalone Switches
[edit forwarding-options hash-key family fcoe]
QFabric Systems
[edit forwarding-options hash-key family fcoe ethernet-interfaces node-group (node-group-name |
all)],
[edit forwarding-options hash-key family fcoe fabric-interfaces node-group (node-group-name | all)] | Enable or disable whether the switch uses the originator exchange identifier (OxID) field for hash control
for FCoE traffic load balancing.
Default
OxID hash control is enabled by default. | [
{
"name": "oxid (enable | disable)",
"desc": "Enable or disable whether the switch uses the OxID hash control field for FCoE traffic load balancing."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Enabling and Disabling CoS OxID Hash Control for FCoE Traffic on Standalone Switches",
"Understanding OxID Hash Control for FCoE Traffic Load Balancing on Standalone Switches",
"P"
] |
p2mp (Protocols LDP) | p2mp {
recursive {
fec;
route;
}
}
root-address root-address; ... | [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 point-to-multipoint MPLS LSPs in an LDP-signaled LSP. | [
{
"name": "no-rsvp-tunneling",
"desc": "(Optional) Disable LDP point-to-multipoint LSPs from using RSVP-TE LSPs for tunneling, and use LDP paths instead. NOTE: The no-rsvp-tunneling option is introduced in Junos OS Release 16.1R5, 17.3R1, 17.2R2, 16.2R3, and later releases. Starting in Junos OS Release 12.3... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2.
no-rsvp-tunneling option added in Junos OS Release 16.1R5.
fec option added in Junos OS and Junos OS Evolved Release 23.4R1. | [
"Example: Configuring Point-to-Multipoint LDP LSPs as the Data Plane for Intra-AS MBGP MVPNs",
"Point-to-Multipoint LSPs Overview"
] |
p2mp (Protocols MPLS) | p2mp p2mp-lsp-name; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name] | Specify an LSP as either a point-to-multipoint LSP or as a branch LSP of a point-to-multipoint LSP by
specifying the point-to-multipoint LSP path name. | [
{
"name": "p2mp-lsp-name",
"desc": "Name of the point-to-multipoint LSP path that identifies the sequence of nodes that form"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Primary Point-to-Multipoint LSP"
] |
p2mp-ldp-next-hop | p2mp-ldp-next-hop {
root-address root-address{
lsp-id id;
}
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options
static route destination-prefix],
[edit logical-systems logical-system-name routing-options static route destination-prefix],
[edit routing-instances routing-instance-name routing-options static route destination-prefix],... | Specify a point-to-multipoint LDP label-switched path (LSP) as the next hop for a static route, and
configure a root and provide an lsp-id on that LDP-signalled label-switched path. | [
{
"name": "root-address root address",
"desc": "Specify the root address of the point-to-multipoint LSP."
},
{
"name": "lsp-id id",
"desc": "Specify the generic LSP identifier. The range is 1 through 65535."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [] |
p2mp-lsp-next-hop | p2mp-lsp-next-hop {
metric metric;
preference preference;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options
static route destination-prefix],
[edit logical-systems logical-system-name routing-options static route destination-prefix],
[edit routing-instances routing-instance-name routing-options static route destination-prefix],... | Specify a point-to-multipoint LSP as the next hop for a static route, and configure an independent
metric or preference on that next-hop LSP.
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 before Junos OS Release 7.4. | [
"Configuring Static Unicast Routes for Point-to-Multipoint LSPs",
"Example: Configuring a Collection of Paths to Create an RSVP-Signaled Point-to-Multipoint LSP",
"Example: Configuring an RSVP-Signaled Point-to-Multipoint LSP on Logical Systems"
] |
p2mp-receive-switch | p2mp-receive-switch point-to-multipoint-switch-name {
output-interface [ interface-name.unit-number ];
receive-p2mp-lsp receiving-point-to-multipoint-lsp;
} | [edit logical-systems logical-system-name protocols connections],
[edit protocols connections] | Configure the CCC switch for a point-to-multipoint LSP on the egress PE router. | [
{
"name": "point-to-multipoint-switch-name",
"desc": "Point-to-multipoint CCC receive switch name."
},
{
"name": "output-interface interface-name.unit-number",
"desc": "Name of the egress interfaces for the point-to-multipoint LSP"
},
{
"name": "receive-p2mp-lsp receiving-point-to-multip... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Point-to-Multipoint LSP Switch on Egress PE Routers"
] |
p2mp-transmit-switch | p2mp-transmit-switch point-to-multipoint-transmit-switch-name {
input-interface interface-name.unit-number;
transmit-p2mp-lsp transmitting-point-to-multipoint-lsp;
} | [edit logical-systems logical-system-name protocols connections],
[edit protocols connections] | Configure the CCC switch for the point-to-multipoint LSP on the ingress PE router. | [
{
"name": "point-to-multipoint-transmit-switch-name",
"desc": "Point-to-multipoint CCC transmit switch name."
},
{
"name": "input-interface input-interface-name.unit-number",
"desc": "Specify the name of the interface carrying incoming traffic"
},
{
"name": "transmit-p2mp-lsp transmittin... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Point-to-Multipoint LSP Switch on Ingress PE Routers"
] |
package (Loading on PIC) | package package-name; | [edit chassis fpc slot-number pic pic-number adaptive-services service-package extension-
provider] | Identify a package to be loaded on the PIC. When a package is added or removed, the PIC reboots. | [
{
"name": "package-name",
"desc": "Name of the package to be loaded on the PIC. There can be up to eight packages loaded on"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [] |
packet-action | packet-action action; | [edit bridge-domains bridge-domain-name bridge-options interface interface-name interface-mac-limit
limit],
[edit bridge-domains bridge-domain-name bridge-options interface-mac-limit limit],
[edit logical-systems logical-system-name bridge-domains bridge-domain-name bridge-options
interface interface-name interface-m... | Specify the action taken when packets with new source MAC addresses are received after the MAC
address limit is reached. If this statement is not configured, packets with new source MAC addresses are
forwarded by default.
NOTE: The packet-action statement is not supported on the QFX10002-60C switch.
NOTE: In ACX710 and... | [
{
"name": "drop",
"desc": "(EX Series switches, QFX Series switches, and PTX Series routers in which Junos OS Evolved is installed) Drop packets with new source MAC addresses, and do not learn the new source MAC addresses. NOTE: On QFX10000 switches, if you include the drop option, you cannot configure unic... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Support for the switch-options statement added in Junos OS Release 9.2.
Support for top-level configuration for the virtual-switch type of routing instance added in Junos OS
Release 9.2. In Junos OS Release 9.1 and earlier, the routing instances hierarchy supported this
sta... | [
"Configuring EVPN Routing Instances",
"Configuring EVPN Routing Instances on EX9200 Switches",
"Configuring MAC Limiting (ELS)",
"Configuring Persistent MAC Learning (ELS)",
"Understanding Layer 2 Learning and Forwarding for Bridge Domains",
"Layer 2 Learning and Forwarding for VLANs Overview",
"Underst... |
packet-burst (Hierarchical Policer) | packet-burst packets; | [edit dynamic-profiles profile-name firewall hierarchical-policer hierarchical-policer-name aggregate
if-exceeding-pps],
[edit dynamic-profiles profile-name firewall hierarchical-policer hierarchical-policer-name premium
if-exceeding-pps],
[edit No Link Title hierarchical-policer hierarchical-policer-name aggregate i... | On MPCs hosted on MX Series routers, configure the packet burst limit for premium or aggregate traffic
in a hierarchical policer. When used in combination with the if-exceeding-ppsand "pps-limit" on page
13506 statements, you can control the number of packets that will be allowed over a configured
packets-per-second li... | [
{
"name": "packets",
"desc": "Packet burst limit in packets. You can specify the number of packets either as a decimal number"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Hierarchical Policer Configuration Overview",
"Policer Color-Marking and Actions",
"Single Token Bucket Algorithm",
"Hierarchical Policers"
] |
packet-burst (Policer) | packet-burst packets; | [edit dynamic-profiles profile-name firewall policer policer-name if-exceeding-pps],
[edit firewall policer policer-name if-exceeding-pps],
[edit logical-systems logical-system-name firewall policer policer-name if-exceeding-pps] | For a single-rate two-color policer, configure the packet-burst as a number of packets. Single-rate two-
color policing uses the single token bucket algorithm to measure traffic-flow conformance to a two-color
policer rate limit.
Traffic at the interface that conforms to the pps-limit is categorized green. Traffic that... | [
{
"name": "packets",
"desc": "Specify the number of packets either as a decimal number or as a decimal number followed by"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Two-Color Policer Configuration Overview",
"Policer Bandwidth and Burst-Size Limits",
"Policer Color-Marking and Actions",
"Single Token Bucket Algorithm",
"Determining Proper Burst Size for Traffic Policers"
] |
packet-capture (forwarding-options) | packet-capture {
disable;
file {
filename filename;
files files;
size size;
world-readable | no-world-readable;
}
max-packets-per-second seconds;
maximum-capture-size bytes;
rate;
run-length;
traceoptions {
file;
no... | [edit forwarding-options] | Configure packet-capture that enables capturing real-time network data packets on the device for analysis
and troubleshooting. | [
{
"name": "disable",
"desc": "Disable packet-capture."
},
{
"name": "file",
"desc": "Parameters for file that contains captured packets"
},
{
"name": "filename",
"desc": "Name of the target file."
},
{
"name": "files",
"desc": "Maximum number of files to capture."
},
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"Use Packet Capture to Analyze Network Traffic"
] | |
packet-capture | packet-capture {
aggressive-mode;
buffer-packets-limit bytes;
capture-interval capture-interval;
capture-limit capture-limit;
global;
max-bytes bytes;
max-files max-files;
max-packets max-packets;
no-inconclusive;
storage-limit bytes;
} | [edit services application-identification] | Specify packet capture options to capture unknown application traffic.
You can use the packet capture of unknown applications functionality to gather more details about an
unknown application on your security device. Once you’ve configured packet capture options on your
security device, the unknown application traffic ... | [
{
"name": "aggressive-mode",
"desc": "Capture all traffic before AppID classifies the applications. In this mode, the system captures all application traffic irrespective of the application system cache (ASC) entry. Packet capture starts for the first packet of the first session."
},
{
"name": "buff... | system | Statement introduced in Junos OS Release 20.2R1. | [] |
packet-filter | packet-filter packet-filter-name {
action-profile profile-name {
destination-port (Security Forwarding Options) (port-range | protocol-name);
destination-prefix destination-prefix;
interface logical-interface-name;
protocol (Security Forwarding Options) (protocol-number | protocol-name;
source-... | [edit security datapath-debug] | Set packet filter for taking the datapath-debug action. A filter is defined to filter traffic, then an action
profile is applied to the filtered traffic. Be sure to configure multiple packet filters to capture the traffic.
One packet filter only captures the traffic as specified in it, such as from one source to one de... | [
{
"name": "action-profile profile-name",
"desc": "Identify the action profile to use. You can specify the name of the action"
},
{
"name": "destination-port (port-range | protocol name)",
"desc": "Specify a destination port to match TCP/UDP destination"
},
{
"name": "destination-prefix d... | security—To view this in the configuration
security-control—To add this to the configuration. | Command introduced in Junos OS Release 9.6 ; Support for IPv6 addresses for the destination-prefix and
source-prefix options added in Junos OS Release 10.4. | [] |
packet-format-match | packet-format-match {
(mpls-packet-format-1 | mpls-packet-format-2 | mpls-packet-format-3 | mpls-packet-format-4 |
mpls-packet-format-5 | mpls-packet-format-6 | mpls-packet-format-7 | mpls-packet-format-8);
} | [edit system packet-forwarding-options] | Types of packet formats for MPLS labeled traffic.
NOTE: You must restart the PFE every time you configure this command. A PFE reboot
forces disruptions to the data plane, a hit that can last several minutes while the
component reboots, and is then repopulated with the current routing state.
Default
The default packet ... | [
{
"name": "mpls-packet-format-1",
"desc": "Untagged packet with one or two labels."
},
{
"name": "mpls-packet-format-2",
"desc": "Untagged packet with one label."
},
{
"name": "mpls-packet-format-3",
"desc": "Untagged packet with two labels."
},
{
"name": "mpls-packet-format-... | admin | Statement introduced in Junos OS Release 19.2R1. | [
"Overview of MPLS Firewall Filters on Loopback Interface",
"Configuring MPLS Firewall Filters and Policers on Switches"
] |
packet-forwarding-options | packet-forwarding-options {
eracl-ip6-match {
(srcip6-and-destip6 | srcip6-only);
}
firewall {
eracl-profile {
eracl-scale;
}
profiles {
ethernet-switching {
(profile1 | profile2);
}
inet {
(pro... | [edit system] | Configure packet forwarding options. The packet forwarding option specifies that data is forwarded to
the specified forwarding destination. | [
{
"name": "bpdu-trap-to-cpu",
"desc": "Stop sending Bridge Protocol Data Units (BPDU) packets to the CPU for processing."
},
{
"name": "apply-groups",
"desc": "Groups from which configuration data is inherited."
},
{
"name": "apply-groups-except",
"desc": "Groups from inherited confi... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Platform-Specific packet-forwarding-options Behavior
Use Feature Explorer to confirm platform, and release support for specific features.
Use the following table to review platform-specific behaviors for... | Statement introduced prior to Junos OS Release 21.1R1 and Junos OS Evolved Release 21.1R1.
no-ip-tos-rewrite option introduced in Junos OS Evolved Release 22.1R1.
ipfix-sw-mode option introduced in Junos OS Release 22.2R1.
mef-forwarding-profile option introduced in Junos OS Evolved Release 22.4R1.
vpls-meshgroups opti... | [
"Ingress and Egress Multicast Replication using Recycle Replication Model",
"Flow-Based Telemetry for VXLANs"
] |
packet-log (Security Flow) | packet-log {
enable;
throttle-interval;
packet-filter <filter-name>;
} | [edit security flow ] | Configure flow packet log.
Starting in Junos OS Release 17.3R1, SRX Series Firewalls support logging of unsynchronized out-of-
state TCP packets that are dropped by the flow module.
The logging functionality will allow notifications to the administrators (or automated systems) about any
of TCP out-of-state packets drop... | [
{
"name": "enable",
"desc": "Enable log for dropped packets."
},
{
"name": "packet-filter",
"desc": "Configure packet log filter."
},
{
"name": "throttle-interval",
"desc": "Configure the interval as a power of two (0..32768 milliseconds)."
}
] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 17.3R1. | [] |
packet-log (Security IDP Policy) | packet-log {
post-attack number;
post-attack-timeout seconds;
pre-attack number;
} | [edit security idp idp-policy policy-name rulebase-ips rule rule-name then notification] | In response to a rule match, capture the packets received before and after the attack for further offline
analysis of attacker behavior. You can configure the number of pre-attack and post-attack packets to be
captured for this attack, and limit the duration of post-attack packet capture by specifying a timeout
value.
... | [] | 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. | [] |
packet-log (Security IDP Sensor Configuration) | packet-log {
host (Security IDP Sensor Configuration) <ip-address>;
port <port number>;
source-address (Security IDP Sensor Configuration) <ip-address>;
ssl-profile-name <profile-name>;
threshold-logging-interval <minutes>} | [edit security idp sensor-configuration]
[edit tenants tenant name security idp sensor-configuration]
[edit logical-systems logical system name security idp sensor-configuration] | Configure the sensor for packet capture. This configuration defines the amount of memory to be
allocated for packet capture and the maximum number of sessions that can generate packet capture
data for the device at one time. The configuration also identifies the source address and host address for
transmission of the c... | [
{
"name": "ssl-profile-name profile-name",
"desc": "SSL initiation profile name to be used for encrypted packet log"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"IDP Security Packet Capture"
] |
packet-loss-priority (RFC 2544 Benchmarking) | packet-loss-priority; | [edit services rpm rfc2544-benchmarkingtests test-name test-name] | Specify the packet loss priority (PLP) value to be used for the test frames generated in the packet
forwarding pipeline. If a value is not configured, then the default value of low is used. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X53. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
packet-ordering-mode (Application Services) | packet-ordering-mode {
(hardware | software);
} | [edit security forwarding-process application-services] | Enables or disables the packet-ordering functionality using the Packet Ordering Engine. By default,
packet-ordering functionality using the Packet Ordering Engine (hardware) is enabled.
A system reboot is required when this feature is enabled or disabled, and a warning message is displayed
during the commit.
NOTE: Pack... | [
{
"name": "hardware",
"desc": "Enables packet-ordering functionality using the Packet Ordering Engine."
},
{
"name": "software",
"desc": "Disables packet-ordering functionality using the Packet Ordering Engine."
}
] | •
security—To view this in the configuration.
•
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10. This statement is supported. | [
"Understanding Traffic Processing on Security Devices"
] |
packet-scheduling | (packet-scheduling | no-packet-scheduling); | [edit chassis] | (M 160 routers only) Enable packet-scheduling mode, in which the Packet Director application-specific
integrated circuit (ASIC) schedules packet dispatches to compensate for transport delay differences. This
preserves the interpacket gaps as the packets are distributed from the Packet Director ASIC to the
Packet Forwar... | [
{
"name": "no-packet-scheduling",
"desc": "Do not schedule packets."
},
{
"name": "packet-scheduling",
"desc": "Schedule packets to preserve interpacket gaps."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Enabling an M160 Router to Operate in Packet Scheduling Mode"
] |
packet-size (RFC 2544 Benchmarking) | packet-size [bytes]; | [edit services monitoring rfc2544 test-profile profile-name] | Define up to 10 packet sizes that are used sequentially for the test. | [
{
"name": "bytes",
"desc": "Size of the test packet. If you enter multiple packet sizes, you must separate each number with a space. You should base the test packet size on the configured MTU. Range: 64 through 9136 bytes Minimum Packet Sizes (Junos OS Evolved): Untagged egress logical interface: 64 byte... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X53.
Statement introduced in Junos OS Evolved 23.4R1. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests",
"rfc2544"
] |
packet-timestamp | packet-timestamp {
enable;
} | [edit chassis fpc slot-number traffic-manager] | On MX Series routers, enable timestamping of class-of-service (CoS) queues for a configured Flexible
PIC Concentrator (FPC). | [
{
"name": "enable",
"desc": "Display the last time a packet was enqueued as day, date, time, and year in the format day-of-the-week month day-date hh:mm:ss yyyy; for example, Mon Jul 7 07:36:46 2014. The Packet Forwarding Engine collects the timestamp for all inbound and outbound queue counters for all subs... | 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. | [
"Enabling a Timestamp for Ingress and Egress Queue Packets"
] |
packet-timestamp | packet-timestamp; | [edit forwarding-options port-mirroring] | Apply 64-bit nanosecond EPOCH timestamp on mirrored packets in family any. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.2R1. | [] |
packet-types (Dynamic VLAN Authentication) | packet-types [packet-types] | [edit interfaces interface-name auto-configure vlan-ranges authentication],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication] | Specify one or more packet types to trigger authentication of an auto-configured dynamic VLAN. The
packet types must be a subset of the packet types configured in the VLAN dynamic profile to trigger
creation of the dynamic VLAN. | [
{
"name": "packet-type",
"desc": "One or more of the following packet types that triggers VLAN authentication:"
},
{
"name": "any",
"desc": "Any packet type."
},
{
"name": "dhcp-v4",
"desc": "IPv4 DHCP packet type."
},
{
"name": "dhcp-v6",
"desc": "IPv6 DHCP packet type."... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Configuring Subscriber Packet Types to Trigger VLAN Authentication",
"Subscriber Packet Type Authentication Triggers for Dynamic VLANs"
] |
pado-advertise | pado-advertise; | [edit protocols pppoe] | Enable named services configured in PPPoE service name tables to be advertised in PPPoE Active
Discovery Offer (PADO) control packets. By default, advertisement of named services in PADO packets
is disabled.
NOTE: If you enable advertisement of named services in PADO packets, make sure the
number and length of of all a... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring PPPoE Service Name Tables",
"Enabling Advertisement of Named Services in PADO Control Packets"
] |
pair-policy | pair-policy pair-policy ; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
tunnel] | Link the policy that you are configuring with another policy that references the same VPN tunnel so that
both policies share one proxy ID and one security association (SA). Policy pairing is useful when you
want to allow bidirectional traffic over a policy-based VPN that is using source or destination address
translati... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Security Policies Overview"
] |
pap (Dynamic PPP) | pap; | [edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit ppp-options],
[edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit ppp-options] | Specify PAP authentication in a PPP dynamic profile. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Support at the [edit dynamic-profiles profile-name interfaces "$junos-interface-ifd-name" unit “$junos-
interface-unit” ppp-options] hierarchy level introduced in Junos OS Release 12.2. | [
"Dynamic Profiles Overview",
"Configuring Dynamic Authentication for PPP Subscribers",
"Attaching Dynamic Profiles to Static PPP Subscriber Interfaces",
"Applying PPP Attributes to L2TP LNS Subscribers per Inline Service Interface"
] |
pap (L2TP) | pap; | [edit access group-profile profile-name ppp ppp-options] | (MX Series routers only) Specify PAP authentication for PPP subscribers in an L2TP LNS user group
profile. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"L2TP LNS Inline Service Interfaces"
] |
pap | pap {
access-profile name;
default-pap-password password;
local-name name;
local-password password;
passive;
} | [edit interfaces interface-name ppp-options],
[edit interfaces interface-name unit logical-unit-number ppp-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number ppp-
options] | Configure the Password Authentication Protocol (PAP). Use PAP authentication as a means to provide a
simple method for the peer to establish its identity using a two-way handshake. This is done only upon
initial link establishment.
After the link is established, an ID and password pair is repeatedly sent by the peer to... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Configuring the PPP Challenge Handshake Authentication Protocol",
"Configuring the PPP Password Authentication Protocol",
"Configuring PPP",
"traceoptions (PPP Process)",
"Configuring L2TP",
"Applying PPP Attributes to L2TP LNS Subscribers per Inline Service Interface"
] |
parameter-preference | parameter-preference(configured | proxied); | [edit logical-systems name protocols router-advertisement interface],
[edit protocols router-advertisement interface] | Preference to select configured or proxied parameters for downstream interface. | [
{
"name": "configured",
"desc": "Send configured parameters on downstream interface"
},
{
"name": "proxied",
"desc": "Send proxied parameters on downstream interface"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.1R1 | [] |
parameters | parameters {
message-processing-model (v1 | v2c | v3);
security-level (none | authentication | privacy);
security-model (usm | v1 | v2c);
security-name security-name;
} | [edit snmp v3 target-parameters target-parameters-name] | Configure a set of target parameters for message processing and security.
The remaining statements are explained separately. See CLI Explorer. | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [] |
parse-direction (Access Profile) | parse-direction (left-to-right | right-to-left); | [edit access profile profile-name session-options strip-user-name] | Specify the direction in which a subscriber login string is parsed to identify the first delimiter that
matches one configured with the "delimiter" on page 5537 statement. When subscriber username
stripping is configured in a subscriber access profile, the characters to the right of the identified
delimiter are strippe... | [
{
"name": "left-to-right",
"desc": "Parse the subscriber login string from left to right up to the delimiter. For example, when the direction is left-to-right, the characters /@$%# are configured as the delimiters, and the login string is drgt21@example.com$84, the @ is reached before the $, so the username... | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Understanding Session Options for Subscriber Access",
"Configuring Username Modification for Subscriber Sessions",
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces"
] |
parse-direction (Domain Map) | parse-direction (left-to-right | right-to-left); | [edit access domain] | Specify the direction in which the router searches for the domain name in a username.
Default
left-to-right | [
{
"name": "left-to-right",
"desc": "The router searches starting at the left-most character. When the router reaches a domain"
},
{
"name": "right-to-left",
"desc": "The router searches starting at the right-most character. When the router reaches a"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Specifying the Parsing Direction for Domain and Realm Names",
"Configuring Domain and Realm Name Usage for Domain Maps"
] |
parse-order (Domain Map) | parse-order (domain-first | realm-first); | [edit access domain] | Specify the order in which the router searches for a domain name, either the domain first, or the realm
first.
Default
domain-first | [
{
"name": "domain-first",
"desc": "The router searches for a domain name first. When the router reaches a domain delimiter, it"
},
{
"name": "realm-first",
"desc": "The router searches for a realm name first. When the router reaches a realm delimiter, it"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Specifying the Parsing Direction for Domain and Realm Names",
"Configuring Domain and Realm Name Usage for Domain Maps"
] |
partition (Gx-Plus) | partition partition-name {
diameter-instance instance-name;
destination-host hostname;
destination-realm realm;
} | [edit access gx-plus] | Configure a Gx-Plus partition. | [
{
"name": "partition-name",
"desc": "Name of the Gx-Plus partition."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Gx-Plus",
"Configuring the Gx-Plus Partition"
] |
partition (NASREQ Diameter Application) | partition partition-name {
destination-host hostname;
destination-realm realm-name;
diameter-instance master;
} | [edit access nasreq] | Define the NASREQ partition by specifying the destination host and realm where the application
resides. Only themaster routing instance is supported for the application partition. | [
{
"name": "diameter-instance",
"desc": ""
},
{
"name": "master",
"desc": "Specifies that the master Diameter instance is used. master is the only supported value."
},
{
"name": "hostname",
"desc": "Name of the host where the NASREQ server application resides; generally, this value is... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Diameter Network Access Server Application (NASREQ)",
"Configuring the Diameter Network Access Server Application (NASREQ)"
] |
partition (OCS) | partition partition-name {
called-station-id station-name;
charging-id number;
destination-host ocs-hostname;
destination-realm ocs-realm-name;
diameter-instance;
draining;
draining-response-timeout seconds;
final-response-timeout seconds;
force-continue;
ggsn-address address;
... | [edit access ocs] | Configure an Online Charging System (OCS) partition (a specific logical system:routing instance context)
and its parameters to define user ID information, destination host and realm names, and number of
outstanding requests to the OCS, and control subscriber traffic flow before the first interrogation with
the OCS. The... | [
{
"name": "partition-name",
"desc": "Name of the OCS partition. You can define only one partition for the OCS."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the OCS Partition",
"3GPP Policy and Charging Control Overview for Wireline Provisioning and Accounting",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interactions Between t... |
partition (PCRF) | partition partition-name {
destination-host pcrf-hostname;
destination-realm pcrf-realm-name;
diameter-instance;
draining;
draining-response-timeout seconds;
ip-can-type number;
local-decision {
deny;
grant;
reinit-on-failure;
reinit-on-rar;
reinit-ti... | [edit access pcrf] | Configure a Policy and Charging Rules Function (PCRF) partition (a specific logical system:routing
instance context) and its parameters to define subscription ID information, destination host and realm
names, and reporting for rules and resources. The PCRF is a centralized policy decision point that
deploys business po... | [
{
"name": "partition-name",
"desc": "Name of the PCRF partition. You can define only one partition for the PCRF."
},
{
"name": "use-session-stamp",
"desc": "(Optional) Adds a 32-bit string to the end of the PCRF session ID for new subscribers. Existing subscribers are not affected when you confi... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2.
use-session-stamp option added in Junos OS Release 20.1R1. | [
"Configuring the PCRF Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Interactions Between the PCRF, PCEF, and OCS",
"Understanding Upstream and Downstream Messages for the PCR... |
partition (s6a) | partition name {
destination-host destination-host;
destination-realm destination-realm;
diameter-instance diameter-instance;
max-outstanding-requests max-outstanding-requests;
response-timeout seconds;
} | [edit access s6a] | Define the s6a partition by specifying the destination host and realm where the application resides and
specify the endpoint origin, the remote peers, and the network elements that associate routes with
peers to control diameter forwarding of S6a messages. Only the master routing instance is supported for
the applicat... | [
{
"name": "name",
"desc": "Name of the S6a partition."
},
{
"name": "destination-host",
"desc": "Name of the host where the S6A server application resides; generally, this value is not set unless needed."
},
{
"name": "destination-realm",
"desc": "Name of the realm where the S6a serv... | access | Statement introduced in Junos OS Release 19.3R1. | [
"Example: Configure S6a Application",
"Diameter Base Protocol Overview"
] |
partition | partition partition-name {
diameter-instance instance-name;
destination-host hostname;
destination-realm realm;
} | [edit jsrc] | Configure a JSRC partition. | [
{
"name": "partition-name",
"desc": "Name of the JSRC partition."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"JSRC Configuration Overview",
"Configuring the JSRC Partition"
] |
pass-through (Access Firewall-Authentication) | pass-through {
default-profile profile-name;
ftp {
banner {
fail string;
login string;
success string;
}
}
http {
banner {
fail string;
login string;
success string;
}
}
t... | [edit access firewall-authentication],
[edit logical-systems name tenants name access firewall-authentication],
[edit tenants name access firewall-authentication] | Configure pass-through , when a host or user from one zone needs to access a protected resource in
another zone. A user must use an FTP, Telnet, or HTTP client to access the IP address of the protected
resource and get authenticated by the firewall. The device uses FTP, Telnet, and HTTP to collect
username and password... | [
{
"name": "default-profile",
"desc": "Name of profile to use if not specified in policy"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5.
Statement introduced for logical-systems and tenant in Junos OS Release 18.3R1.
HTTPS for pass-through authentication is supported on SRX5400, SRX5600, and SRX5800 devices
starting from Junos OS Release 12.1X44-D10 and on vSRX Virtual Firewall, SRX300, SRX320, SRX340,
SRX34... | [
"Pass-Through Authentication",
"Example: Configure Pass-Through Authentication",
"Obtaining Username and Role Information Through Firewall Authentication"
] |
pass-through (interfaces) | (pass-through | no-pass-through); | [edit interfaces interface-name otn-options rate] | Enable or disable OTN pass-through mode.
Default
By default, OTN pass-through mode is disabled. | [
{
"name": "no-pass-through",
"desc": "Do not enable OTN pass-through mode."
},
{
"name": "pass-through",
"desc": "Enable OTN pass-through 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. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
pass-through (Security Policy) | pass-through {
access-profile profile-name;
client-match user-or-group-name;
ssl-termination-profile profile-name;
web-redirect;
web-redirect-to-https;
} | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
firewall-authentication] | Configure pass-through firewall user authentication. The user needs to use an FTP, Telnet, or HTTP
client to access the IP address of the protected resource in another zone. Subsequent traffic from the
user or host is allowed or denied based on the result of this authentication. Once authenticated, the
firewall proxies... | [
{
"name": "access-profile profile-name",
"desc": "(Optional) Specify the name of the access profile."
},
{
"name": "client-match user-or-group",
"desc": "(Optional) Specify the name of the users or user groups in a profile who"
},
{
"name": "ssl-termination-profile profile-name",
"de... | 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 ssl-termination-profile and web-redirect-to-https
options added in Junos OS Release 12.1X44-D10. | [
"Security Policies Overview"
] |
passive (CHAP) | passive; | [edit interfaces interface-name ppp-options chap],
[edit interfaces interface-name unit logical-unit-number ppp-options chap],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number ppp-
options chap] | Do not challenge the peer, but respond if challenged. If you omit this statement from the configuration,
the interface always challenges its peer.
For ATM2 IQ interfaces only, you can configure CHAP on the logical interface unit if the logical interface
is configured with one of the following PPP over ATM encapsulation... | [] | 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 Passive Mode"
] |
passive (Dynamic IGMP Interface) | passive <allow-receive> <send-general-query> <send-group-query>; | [edit dynamic-profiles profile-name protocols igmp interface interface-name] | Dynamically specify that IGMP run on the interface and either not send and receive control traffic or
selectively send and receive control traffic such as IGMP reports, queries, and leaves.
NOTE: You can selectively activate up to two out of the three available options for the
passive statement while keeping the other ... | [
{
"name": "allow-receive",
"desc": "Enables IGMP to receive control traffic on the interface."
},
{
"name": "send-general-query",
"desc": "Enables IGMP to send general queries on the interface."
},
{
"name": "send-group-query",
"desc": "Enables IGMP to send group-specific and group-s... | 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.
allow-receive, send-general-query, and send-group-query options were introduced in Junos OS Release 10.0. | [
"Example: Configuring Multicast with Subscriber VLANs",
"Multicast Protocols User Guide"
] |
passive (Dynamic MLD Interface) | passive <allow-receive> <send-general-query> <send-group-query>; | [edit dynamic-profiles profile-name protocols mld interface interface-name] | Specify that MLD run on the interface and either not send and receive control traffic or selectively send
and receive control traffic such as MLD reports, queries, and leaves.
NOTE: You can selectively activate up to two out of the three available options for the
passive statement while keeping the other functions pass... | [
{
"name": "allow-receive",
"desc": "(Optional) Enables MLD to receive control traffic on the interface."
},
{
"name": "send-general-query",
"desc": "(Optional) Enables MLD to send general queries on the interface."
},
{
"name": "send-group-query",
"desc": "(Optional) Enables MLD to s... | 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. | [
"Dynamic MLD Configuration Overview",
"Example: Configuring Multicast with Subscriber VLANs"
] |
passive (IGMP) | passive <allow-receive> <send-general-query> <send-group-query>; | [edit logical-systems logical-system-name protocols igmp interface interface-name],
[edit protocols igmp interface interface-name] | When configured for passive IGMP mode, the interface listens for IGMP reports but it will not send or
receive IGMP control traffic such as IGMP reports, queries and leaves. You can, however, configure
exceptions to allow the interface to receive certain control traffic or queries.
NOTE: When an interface is configured ... | [
{
"name": "allow-receive",
"desc": "Enables IGMP to receive control traffic on the interface."
},
{
"name": "send-general-query",
"desc": "Enables IGMP to send general queries on the interface."
},
{
"name": "send-group-query",
"desc": "Enables IGMP to send group-specific and group-s... | 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.
allow-receive, send-general-query, and send-group-query options were added in Junos OS Release 10.0. | [
"Example: Configuring Multicast with Subscriber VLANs",
"Enabling IGMP"
] |
passive (MLD) | passive <allow-receive> <send-general-query> <send-group-query>; | [edit logical-systems logical-system-name protocols mld interface interface-name],
[edit protocols mld interface interface-name] | Specify that MLD run on the interface and either not send and receive control traffic or selectively send
and receive control traffic such as MLD reports, queries, and leaves.
NOTE: You can selectively activate up to two out of the three available options for the
passive statement while keeping the other functions pas... | [
{
"name": "allow-receive",
"desc": "Enables MLD to receive control traffic on the interface."
},
{
"name": "send-general-query",
"desc": "Enables MLD to send general queries on the interface."
},
{
"name": "send-group-query",
"desc": "Enables MLD to send group-specific and group-sour... | 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.
allow-receive, send-general-query, and send-group-query options added in Junos OS Release 10.0. | [
"Example: Configuring Multicast with Subscriber VLANs"
] |
passive (MVRP) | passive; | [edit protocols mvrp],
[edit protocols mvrp interface(all | interface-name)] | Configure an MVRP interface to not announce its membership in a VLAN or send any VLAN
declarations (updates) unless it receives registration for that VLAN from a peer (server).
Default
Passive mode is disabled by default. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1. | [
"Multiple VLAN Registration Protocol"
] |
passive (PAP) | passive; | [edit interfaces interface-name ppp-options pap],
[edit interfaces interface-name unit logical-unit-number ppp-options pap],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number ppp-
options pap] | Initiate an authentication request when the PAP option is received from a peer. If you omit this
statement from the configuration, the interface requires the peer to initiate an authentication request. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Configuring Passive Mode",
"Junos OS Administration Library for Routing Devices"
] |
passive (Protocols BGP) | passive; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Configure the routing device so that active open messages are not sent to the peer. Once you configure
the routing device to be passive, the routing device will wait for the peer to issue an open request
before a message is sent.
Default
If you omit this statement, all explicitly configured peers are active, and each p... | [] | 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: Preventing BGP Session Flaps When VPN Families Are Configured"
] |
passive (Protocols IS-IS) | passive {
remote-node-id address;
remote-node-iso iso-id;
} | [edit logical-systems logical-system-name protocols isis interface interface-name],
[edit logical-systems logical-system-name protocols isis interface interface-name level level-
number],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis
interface interface-name],
[edit l... | Advertise the direct interface addresses on an interface or into a level on the interface without actually
running IS-IS on that interface or level.
This statement effectively prevents IS-IS from running on the interface. To enable IS-IS on an interface,
include the interface statement at the [edit protocols isis] or t... | [
{
"name": "remote-node-id address",
"desc": "IP address of the remote link."
},
{
"name": "remote-node-iso iso-id",
"desc": "ISO ID of the remote node. NOTE: The options remote-node-id address and remote-node-iso iso-id do not apply under the [edit routing-instances routing-instance-name protoco... | 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.
remote-node-id address option introduced in Junos OS Release 14.2.
remote-node-iso iso-id option introduced in Junos OS Release 14.2. | [
"Example: Configuring a Multi-Level IS-IS Topology to Control Interarea Flooding"
] |
passive (Protocols Link Management) | passive; | [edit logical-systems logical-system-name protocols link-management peer peer-name lmp-protocol],
[edit protocols link-management peer peer-name lmp-protocol] | Specify that the router not configure the Link Management Protocol (LMP) control channels but wait for
the remote peer to configure the LMP control channels. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Preventing the Local Peer from Initiating LMP Negotiation"
] |
passive (Protocols OSPF) | passive {
traffic-engineering {
} | [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface
interface-name],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast) area area-id interface interface-name],
[edit logical-systems logical-system-name routing-instance... | Advertise the direct interface addresses on an interface without actually running OSPF on that interface.
A passive interface is one for which the address information is advertised as an internal route in OSPF,
but on which the protocol does not run.
To configure an interface in OSPF passive traffic engineering mode, i... | [] | 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.
traffic-engineering and remote-node-id address statements introduced in Junos OS Release 8.0.
traffic-engineering and remote-node-id address statements introduced in Junos OS Release 8.0 for EX Series
switches.
Support for the realm statement introduced in Junos OS Rele... | [
"Example: Configuring a Passive OSPF Interface",
"Example: Configuring OSPF Passive Traffic Engineering Mode"
] |
passive (Routing Options) | [] | [] | |||||
passive-mode | passive-mode; | [edit logical-systems name protocols router-advertisement interface],
[edit protocols router-advertisement interface] | Configure passive mode on an interface. When you configure this option on the interface, the interface
only reieves and processes the RA packets and does not send the RAs (receive-only mode). The commit
fails if the interface has both downstream and passive-mode option configured.
Configure RA receive only mode | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.1R1. | [] |
passive-mode-tunneling (Security IPsec) | passive-mode-tunneling; | [edit security ipsec vpn vpn-name] | Allows tunneling of malformed packets. By default, the feature is disabled. When you enable this feature
using the configuration statement set security ipsec vpn vpn-name passive-mode-tunneling:
•
Traffic bypasses the usual active IP checks such as the version, TTL, protocol, options, and address.
•
There is no effect ... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration.
Platform-Specific Passive Mode Tunneling Behavior
Use Feature Explorer to confirm platform and release support for specific features.
Use the following table to review platform-specific behavior for your platfor... | Statement introduced in Junos OS Release 23.1R1. | [
"passive-mode-tunneling"
] |
passive-mode-tunneling | passive-mode-tunneling; | [edit services service-set service-set-name ipsec-vpn-options] | Allows tunneling of malformed packets. When this statement is enabled, traffic bypasses the usual
active IP checks. The IPsec tunnel is not treated as a next hop and TTL is not decremented. If the packet
size exceeds the tunnel MTU value, an ICMP error is not generated. Starting with Junos OS Release
13.3R4 and 14.2R1,... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Configuring IPsec Service Sets"
] |
passive-monitor-mode | passive-monitor-mode; | [edit interfaces ATM, Fast Ethernet, or Gigabit Ethernet interface-name],
[edit interfaces SONET/SDH interface-name unit logical-unit-number] | For Asynchronous Transfer Mode (ATM), SONET/SDH, Fast Ethernet, and Gigabit Ethernet interfaces
only, monitor packet flows from another router. If you include this statement in the configuration, the
SONET/SDH interface does not send keepalives or alarms, and does not participate actively on the
network. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Enabling Passive Flow Monitoring on M Series, MX Series or T Series Routers"
] |
passive-probe-params | passive-probe-params {
sampling-percentage {
percentage;
}
sampling-period {
period;
}
type {
book-ended;
} | [edit security advance-policy-based-routing] | Configure the passive probe parameters with the SLA rule.
Passive probes measure the service quality of an application by inserting a custom probe header in the
live traffic between the spoke and hub points and measuring the RTT, jitter and packet loss between the
points of installation of the probes.
SLA violation is... | [
{
"name": "sampling-percentage",
"desc": ""
},
{
"name": "percentage",
"desc": "Indicates the percentage of sessions that are selected for a book-ended SLA measurement. Example: If 18 sessions are available for a particular application are available, and if"
},
{
"name": "you have config... | 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. | [
"Application Quality of Experience",
"Advanced Policy-Based Routing"
] |
password (Access) | password password; | [edit access ldap-options search admin-search],
[edit access profile profile-name ldap-options search admin-search] | Configure the plain-text password for the administrative user. This password is used in the bind for
performing the LDAP search. | [
{
"name": "password",
"desc": "Administrative user password."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [
"Example: Configuring Integrated User Firewall on SRX Series"
] |
password (DHCP Local Server) | password password-string; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server authentication],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 authentication],
[edit logical-systems logical-system-name rou... | Configure the password that is sent to the external AAA authentication server for subscriber
authentication or DHCP client authentication. | [
{
"name": "password-string",
"desc": "Authentication password."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Specifying Authentication Support"
] |
password (DHCP Relay Agent) | password password-string; | [edit forwarding-options dhcp-relay authentication],
[edit forwarding-options dhcp-relay dhcpv6 authentication],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name authentication],
[edit forwarding-options dhcp-relay group group-name authentication],
[edit forwarding-options dhcp-relay dhcpv6 gr... | Configure the password that is sent to the external AAA authentication server for subscriber
authentication or client authentication. Use the statement at the [edit ... dhcpv6] hierarchy levels to
configure DHCPv6 support. | [
{
"name": "password-string",
"desc": "Authentication password."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4.
Support at the [edit ... dual-stack-group dual-stack-group-name authentication] hierarchy level introduced in
Junos OS Release 15.1. | [
"Specifying Authentication Support",
"Example-Configuring DHCP with External Authentication Server"
] |
password (Flow Collector File Servers) | password "password"; | [edit services flow-collector destination ftp:url] | Specify the primary and secondary destination FTP server password. | [
{
"name": "password",
"desc": "FTP server password."
}
] | 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 Destination FTP Servers for Flow Records"
] |
password (Interfaces) | password password-string; | [edit interfaces interface-name auto-configure vlan-ranges authentication],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication] | Configure the password that is sent to the external AAA authentication server for subscriber VLAN or
stacked VLAN interface authentication. | [
{
"name": "password-string",
"desc": "Authentication password."
}
] | 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 an Authentication Password for VLAN or Stacked VLAN Ranges"
] |
password (Login) | password {
change-type (character-sets | set-transitions);
format (sha256 | sha512);
maximum-length length;
maximum-lifetime days;
minimum-changes number;
minimum-character-changes number;
minimum-length length;
minimum-lifetime days;
minimum-lower-cases number;
minimum-numerics ... | [edit system login] | Configure special requirements such as character length and encryption format for plain-text passwords.
Newly created passwords must meet these requirements.
Using several password minimum requirement options will cause the minimum-length to be reset if the total
sum of the required minimums exceeds the minimum-length ... | [
{
"name": "change-type",
"desc": "Set requirements for using character sets in plain-text passwords. When you combine this statement with the minimum-changes statement, you can check for the total number of character sets included in the password or for the total number of character-set changes in the passw... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4.
Statements minimum-lower-cases, minimum-numerics, minimum-punctuations, and minimum-upper-cases introduced in
Junos OS Release 12.1.
All of the previously mentioned statements were introduced in Junos OS Release 14.1X53-D20 for the
OCX Series.
Statements minimum-reuse and m... | [
"Example: Changing the Requirements for Junos OS Plain-Text Passwords",
"Special Requirements for Junos OS Plain-Text Passwords"
] |
password (MAC RADIUS Authentication) | password password-string; | [edit protocols dot1x authenticator mac-radius] | Configure a global password to be used as the password (instead of the MAC address) for all sessions
that use MAC RADIUS authentication. Use of a global password is supported on all three MAC RADIUS-
based authentication protocols (̌eap-md5, eap-peap, pap).
NOTE: When enabled (or disabled), currently active dot1x sess... | [
{
"name": "password-string",
"desc": "Authentication password. Password can be between 1 and 128 characters in length. Password can include most character classes (uppercase letters, lowercase letters, numbers, punctuation marks, and other special characters), excluding space. If you use any of the followin... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.1R1. | [
"Configuring MAC RADIUS Authentication (CLI Procedure)"
] |
password (Security Antivirus) | password password-string; | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine pattern-update proxy]
[edit security utm feature-profile anti-virus kaspersky-lab-engine pattern-update proxy]
[edit security utm feature-profile anti-virus sophos-engine pattern-update proxy] | Set the password for the proxy server. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Release 11.2.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
password (Services) | password password; | [edit services unified-access-control infranet-controller hostname] | Specify the password that the SRX Series Firewall should send to the IC Series device to establish
communications. The SRX Series Firewall sends the password in its first message to the IC Series device.
This statement is required when you are configuring the SRX Series Firewall to act as a Junos OS
Enforcer in a Unifi... | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [] |
password (Static Subscribers) | password password-string; | [edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers group group-name authentication],
[edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers authentication],
[edit logical-systems logical-... | Specify the password that is sent to AAA for user login for all static subscribers on interfaces configured
at the [edit system services static-subscribers interface] hierarchy level, or for the subscribers in a specified
group. The group version of the statement takes precedence over the global version. | [
{
"name": "password-string",
"desc": "String that defines the password."
}
] | system-level—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Subscribers over Static Interfaces Configuration Overview",
"Configuring the Static Subscriber Global Authentication Password",
"Configuring the Static Subscriber Group Authentication Password"
] |
password (Transfer Log File Servers) | password "password"; | [edit services flow-collector transfer-log-archive archive-sites] | Specify the primary and secondary destination FTP server password. | [
{
"name": "password",
"desc": "FTP server password."
}
] | 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 Transfer Logs"
] |
password-file | password-file (block | (log-and-permit); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name fallback-
options] | Password protected file is the error returned by the scan engine when the scanned file is protected by a
password. The default action is log-and-permit. | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Full Antivirus Configuration Overview"
] |
password-options | password-options {
apply-groups;
apply-groups-except;
tacplus-authorization;
} | [edit system] | Configure options for local authentication.
NOTE: Starting in Junos OS Evolved Release 25.4R1 and Junos OS Release 25.4R1, you
need not configure password under edit system authentication-order to enable password-options. | [
{
"name": "apply-groups",
"desc": "Choose the groups from which to inherit configuration data."
},
{
"name": "apply-groups-except",
"desc": "Choose the groups to be excluded from configuration data being inherited."
},
{
"name": "tacplus-authorization",
"desc": "Configure remote auth... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R1.
Option tacplus-authorization introduced in Junos OS Release 19.3R1 on MX Series routers. | [] |
path (Protocols MPLS) | path path-name {
abstract-hop-name (abstract | loose | loose-link | strict);
(address | hostname) <strict | loose>;
} | [edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls] | Create a named path and optionally specify the sequence of explicit routers that form the path.
You must include this statement when configuring explicit LSPs. | [
{
"name": "abstract-hop-name",
"desc": "Name of the predefined abstract hop. The abstract hop can be used in combination"
},
{
"name": "abstract",
"desc": "Indicate that the next hop configured in the path statement is an abstract hop.."
},
{
"name": "loose-link",
"desc": "Indicate t... | 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.
abstract-hop-name option introduced in Junos OS Release 17.1 for all platforms. | [
"Creating Named Paths",
"abstract-hop"
] |
path (Protocols RSVP) | path address <strict | loose>; | [edit logical-systems logical-system-name protocols rsvp interface interface-name link-
protection],
[edit logical-systems logical-system-name protocols rsvp interface interface-name link-
protection bypass bypass-name],
[edit protocols rsvp interface interface-name link-protection],
[edit protocols rsvp interface inte... | Configure an explicit path (a sequence of strict or loose routes) to control where and how a bypass LSP
is established. If multiple bypasses are configured, they all will use the same explicit path.
Default
No path is configured. CSPF automatically calculates the path the bypass LSP takes. | [
{
"name": "address",
"desc": "IP address of each transit router in the LSP. You must specify the address or hostname of each"
},
{
"name": "loose",
"desc": "(Optional) The next address in the path statement is loose. The LSP can traverse other routers"
},
{
"name": "strict",
"desc": ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring an Explicit Path for Bypass LSPs"
] |
path (Steering) | path {
ipv4-address ipv4-address;
ipv6-address ipv6-address;
} | [edit unified-edge pcef pcc-action-profiles profile-name steering],
[edit services pcef pcc-action-profiles profile-name] | Specify the IP address of a third-party server to which the PCC action profile steers HTTP traffic for
applying services. If you configure this, the PCC action profile can only be used in PCC rules that match
only HTTP-based applications and all flows.
The remaining statements are explained separately. | [] | For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration.
For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef pcc-action-profiles profile-name] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series.
Support for Next Gen Services for Junos OS Broadband Subscriber Management introduced in Juno... | [
"Understanding Application-Aware Policy Control for Subscriber Management",
"Configuring Policy and Charging Control Action Profiles for Subscriber Management",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Configuring Policy and Charging Control Action ... |
path | path destination {
<address | hostname> <strict | loose>
} | [edit protocols mpls] | Configure path protection on your MPLS network. | [
{
"name": "destination",
"desc": "Name of a label switched path (LSP). In addition to specifying the name of the configured"
},
{
"name": "address",
"desc": "(Optional) IP address of each transit switch (or the IP address of the loopback interface on the"
},
{
"name": "hostname",
"de... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring Path Protection in an MPLS Network (CLI Procedure)"
] |
path-database-size (EX Series Switch Only) | path-database-size path-database-size; | [edit protocols oam ethernet connectivity-fault-management linktrace] | Specify the number of linktrace reply entries to be stored per linktrace request. | [
{
"name": "path-database-size",
"desc": "Database size (number of entries stored per request)."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configure Ethernet OAM Connectivity Fault Management (CLI Procedure)",
"Junos OS Network Interfaces Configuration Guide"
] |
path-database-size | path-database-size path-database-size; | [edit protocols oam ethernet connectivity-fault-management linktrace] | Number of linktrace reply entries to be stored per linktrace request. | [
{
"name": "path-database-size",
"desc": "Database size."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring Connectivity Fault Management (CFM)"
] |
path-length | path-length certificate-path-length; | [edit security certificates] | (Encryption interface on M Series and T Series routers and EX Series switches only) Configure the digital
certificate path length. | [
{
"name": "certificate-path-length",
"desc": "Digital certificate path length."
}
] | 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 the Path Length for the Certificate Hierarchy"
] |
path-mtu | path-mtu {
allow-fragmentation;
rsvp {
mtu-signaling;
}
} | [edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls] | Configure MTU options for MPLS paths, including packet fragmentation and MTU signaling.
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 before Junos OS Release 7.4. | [
"Configuring MTU Signaling in RSVP"
] |
path-mtu-discovery (Tunnel) | (path-mtu-discovery | no-path-mtu-discovery); | [edit interfaces ip-fpc/pic/port unit logical-unit-number tunnel],
[edit interfaces gr-fpc/pic/port unit logical-unit-number tunnel] | Configure path MTU discovery for outgoing tunnel connections:
•
path-mtu-discovery—Path MTU discovery is enabled.
•
no-path-mtu-discovery—Path MTU discovery is disabled.
NOTE: Starting in Junos OS Release 17.2R1, the no-path-mtu-discovery configuration
statement in the [edit interfaces ip-fpc/pic/port unit logical-unit... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configure Path MTU Discovery"
] |
path-rate-limit | path-rate-limit {
message-type {
create-req {
alarm-threshold (Security GPRS) {
forward number;
reverse number;
}
drop-threshold (Security GPRS) {
forward number;
reverse number;
}
}
... | [edit security gtp profile profile-name] | Use the path-rate-limit function to control specific GPRS tunneling protocol (GTP) messages in both the
forward and reverse directions. A drop threshold and an alarm threshold parameter can be configured
for each control message in the forward and reverse direction for one path.
From Junos OS Release 20.4R1 onwards, th... | [
{
"name": "message-type",
"desc": "To specific group of control messages"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10. | [
"Understanding Path Rate Limiting for GTP Control Messages",
"Example: Limiting the Message Rate and Path Rate for GTP Control Messages"
] |
path-selection | path-selection {
(always-compare-med | cisco-non-deterministic | external-router-id);
as-path-ignore;
l2vpn-use-bgp-rules;
med-plus-igp {
igp-multiplier number;
med-multiplier number;
}
} | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp],
[edit protocols bgp],
[edit routing-instances routing-instance-name protocols bgp] | Configure BGP path selection.
Default
If the path-selection statement is not included in the configuration, only the multiple exit discriminators
(MEDs) of routes that have the same peer ASs are compared. | [
{
"name": "always-compare-med",
"desc": "Always compare MEDs whether or not the peer ASs of the compared routes are the same. NOTE: We recommend that you configure the always-compare-med option."
},
{
"name": "as-path-ignore",
"desc": "In the best-path algorithm, skip the step that compares the ... | 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.
med-plus-igp option introduced in Junos OS Release 8.1.
as-path-ignore and l2vpn-use-bgp-rules options introduced in Junos OS Release 10.2. | [
"Understanding BGP Path Selection",
"Enabling BGP Path Selection for Layer 2 VPNs and VPLS",
"Example: Ignoring the AS Path Attribute When Selecting the Best Path"
] |
pattern (Application Identification) | pattern pattern; | [edit services application-identification application application-name over protocol-type
signature l4-l7-signature-name member member-name] | Define an attack pattern to be detected. | [
{
"name": "pattern",
"desc": "User-defined pattern of attack to match, using a regular expression."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support for Next Gen Services introduced in Junos OS Releases 19.3R2 and 19.4R1 on MX Series
MX240, MX480 and MX960 using the MX-SPC3 services card. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
pattern (Class Attribute) | pattern “pattern”; | [edit unified-edge gateways tdf gateway-name domains domain-name subscription-id use-class] | Configure characters to insert between the resulting regular expression groups that are generated from
parsing the Class attribute contents of the accounting request from the BNG, PGW, or GGSN. Regular
expression groups are identified with \n for a group number. | [
{
"name": "pattern",
"desc": "Characters to insert between regular expression groups. A regular expression group number “n” is identified as \\n. For example, the following configuration generates \" 000118191129|ALICE:DRAV3:\" out of \" 000118191129#000118191129#ALICE:DRAV3:#7168#nflat#ADSL##\": [edit unif... | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring a Set of IP-Based TDF Subscriber Properties with a TDF Domain"
] |
pattern (Security IDP) | pattern signature-pattern; | [edit security idp custom-attack attack-name attack-type signature] | Specify the pattern IDP should match. You construct the attack pattern just as you would when creating
a new signature attack object. | [
{
"name": "signature-pattern",
"desc": "Specify the signature pattern."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
pattern | pattern dfa-pattern; | [edit services application-identification nested-application name signature name member name] | Define an attack pattern to be detected. | [
{
"name": "dfa-pattern",
"desc": "Pattern of attack to match. Deterministic Finite Automata (DFA) is a powerful pattern matching engine."
}
] | system—To view this statement in the configuration.
system control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Application Identification for Nested Applications"
] |
pattern-pcre (Security IDP) | pattern-pcre signature-pattern-pcre; | [edit security idp custom-attack attack-name attack-type signature] | Specify the pattern in standard PCRE format. You construct the attack pattern in PCRE format just as
you would when creating a new signature attack object. This is an optional field. The pattern field is
unused under this configuration. | [
{
"name": "signature-pattern-pcre",
"desc": "Specify the signature pattern in standard PCRE format."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1x49-D40. | [] |
pattern-update (Security Antivirus) | pattern-update {
email-notify {
admin-email email-address;
custom-message message;
custom-message-subject message-subject;
}
interval value;
no-autoupdate;
proxy-profile proxy profile name;
routing-instance name;
start-time start-time;
url url;
} | [edit security utm feature-profile anti-virus juniper-express-engine]
[edit security utm feature-profile anti-virus kaspersky-lab-engine]
[edit security utm default-configuration anti-virus avira-engine] | Updates to the pattern file are added as new viruses are discovered. You can configure the security
device to regularly update the pattern file automatically, or you can update the file manually.
Starting in Junos OS Release 23.1R1, we've deprecated the pattern-update statement at the [edit security
utm feature-profile... | [] | security— To view this statement in the configuration.
security-control— To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
The proxy-profile option is introduced under the security utm feature-profile anti-virus sophos-engine
hierarchy level in Junos OS Release 18.3R1.
Support for Avira engin... | [] |
pause-computation-during-churn | pause-computation-during-churn; | [edit fabric protocols bgp multipath],
[edit logical-systems name protocols bgp multipath],
[edit logical-systems name routing-instances name protocols bgp multipath],
[edit logical-systems name tenants name routing-instances name protocols bgp multipath],
[edit protocols bgp multipath],
[edit routing-instances name p... | Defer multipath computation for all families during a BGP peering churn. In a very large-scale network,
there is a temporary spike in multipath computation during BGP peering, which takes a toll on the
Packet Forwarding Engine resources. You can pause the multipath computation and resume after the
peering churn settles... | [] | routing | Statement introduced in Junos OS Release 20.3R1. | [] |
payload | payload {
ip {
layer-3;
layer-4;
}
} | [edit chassis fpc slot-number pic pic-number hash-key family multiservice] | (MX Series 5G Universal Routing Platforms only) Include payload data in a hash key for the multiservice
protocol family when configuring PIC-level symmetrical load balancing on an 802.3ad Link Aggregation
Group. | [
{
"name": "ip",
"desc": "Include IPv4 payload data in the hash key. This option has the following suboptions:"
},
{
"name": "layer-3",
"desc": "Include Layer 3 IP information in the hash key."
},
{
"name": "layer-4",
"desc": "Include Layer 4 IP information in the hash key."
}
] | 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. | [
"Configuring PIC-Level Symmetrical Hashing for Load Balancing on 802.3ad LAGs for MX Series",
"Routers"
] |
pba-interim-logging-interval | pba-interim-logging-interval seconds | [edit interfaces interface-name services-options] | Port block allocation (PBA) generates one syslog entry per set of ports allocated to a subscriber. These
logs are UDP based and can be lost in the network,especially for long running flows. Interim logging
resends the above logs at a configured interval for all active blocks that have traffic on at least one
block. For... | [
{
"name": "seconds",
"desc": "Interval, in seconds, for re-sending of session logs"
},
{
"name": "Default: 0",
"desc": "This indicates that interim logging is not used."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Configuring NAT Session Logs"
] |
pbb-evpn-core | pbb-evpn-core; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols]
[edit routing-instances routing-instance-name protocol evpn] | Specify that Ethernet VPN (EVPN) is running for Provider Backbone Bridging (PBB). | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1.
Support for logical systems on MX Series routers added in Junos OS Release 17.4R1. | [] |
pbb-service-options | pbb-service-options {
default-isid isid-number;
isid isid-number vlan-id-list [ vlan-ids ];
mac-address mac-address;
source-bmac <mac-address>
} | [edit routing-instances routing-instance-name service-groups service-group-name] | For IEEE 802.1ah provider backbone bridge (PBB) configurations, configure PBB service options for the
customer routing instance (I-component) service group.
NOTE: The mac-address statement is not supported for PBB-EVPN.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "service-group-name",
"desc": "Name of a service group."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in JUNOS Release 10.0. | [
"Example: Configuring E-LINE and E-LAN Services for a PBB Network on MX Series Routers"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.