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 |
|---|---|---|---|---|---|---|---|
pcc-action-profile (PCC Rules) | pcc-action-profile profile-name; | [edit unified-edge pcef pcc-rules rules-name then],
[edit services pcef pcc-rules rules-name then] | Specify the name of the action profile to include in a policy and charging control (PCC) rule
configuration. The action profile defines the treatment to be applied to specific service data flows or to
packets associated with specific applications.
If you are using Junos OS Subscriber Aware, specify the name of the acti... | [
{
"name": "profile-name",
"desc": "Name of the PCC action profile that the PCC rule references. The referenced action profile must be configured. Range: 1 through 63 characters."
}
] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef pcc-rules rules-name then] 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 Junos OS
R... | [
"Configuring Policy and Charging Control Rules",
"Configuring Policy and Charging Control Action Profiles For Junos OS Subscriber Aware",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Configuring Policy and Charging Control Action Profiles for Subscriber... |
pcc-action-profiles | pcc-action-profiles profile-name {
forwarding-class class-name;
gate-status (uplink | downlink | uplink-downlink | disable-both);
hcm-profile hcm-profile-name;
logging-rule lrf-rule-name;
maximum-bit-rate uplink mbr-uplink-value downlink mbr-downlink-value;
monitoring-key key_string;
redire... | [edit unified-edge pcef],
[edit services pcef] | Configure a PCC action profile. A PCC action profile defines the treatment to be applied to specific
service data flows or to packets associated with specific applications. A PCC action profile is specified in
the then clause of a PCC rule.
If you are using Junos OS Subscriber Aware, configure the PCC action profile at... | [
{
"name": "profile-name",
"desc": "Name of the PCC action profile. Range: 1 through 63 characters. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef] 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 Junos OS
Release 19.3R2 on MX Series. | [
"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 TDF Subscriber Usage Monitoring for... |
pcc-context | pcc-context {
input-service-filter-name filter-name;
input-service-set-name service-set-name;
ipv6-input-service-filter-name filter-name;
ipv6-input-service-set-name service-set-name;
ipv6-output-service-filter-name filter-name;
ipv6-output-service-set-name service-set-name;
output-service-f... | [edit access profile profile-name session-options] | Specify the PCEF profile that contains the policy and charging control (PCC) rules that a PCRF can
directly activate for a subscriber, and specify the input and output service sets that process the PCC
rules. You can optionally specify service filters for the service sets. PCC rules specify the policies to
apply to tr... | [
{
"name": "input-service-filter-name",
"desc": ""
},
{
"name": "filter-name",
"desc": "(Optional) Input IPv4 service filter name. The service filter identifies conditions for which you want to skip application-aware policy control."
},
{
"name": "input-service-set-name",
"desc": ""
... | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1 on MX Series. | [
"Enabling Direct PCC Rule Activation by a PCRF for Subscriber Management"
] |
pcc-rule | [pcc-rule rule-name precedence number]; | [edit unified-edge pcef pcc-rule-bases rulebase-name],
[edit services pcef pcc-rule-bases rulebase-name] | Specify one or more policy and charging control (PCC) rules and the rules precedence in a PCC rulebase.
If you are using Junos OS Subscriber Aware, configure the PCC rules at the [edit unified-edge pcef pcc-
rule-bases rulebase-name] hierarchy level.
If you are using Junos OS Broadband Subscriber Management, configure ... | [
{
"name": "rule-name",
"desc": "Name of the PCC rule. The referenced PCC rule must be configured. Range: 1 through 63 characters."
},
{
"name": "number",
"desc": "Precedence value assigned to the PCC rule. The precedence assigned must be unique among the configured PCC rules. Range: 1 through ... | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef pcc-rule-bases rulebase-name] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series. | [
"Configuring a Policy and Charging Control Rulebase",
"Configuring Policy and Charging Control Rules"
] |
pcc-rulebases (PCEF Profile) | [pcc-rulebases rulebase-name <time-of-day-profile profile-name>]; | [edit unified-edge pcef profiles profile-name aaa-policy-control],
[edit unified-edge pcef profiles profile-name dynamic-policy-control],
[edit unified-edge pcef profiles profile-name static-policy-control],
[edit services pcef profiles profile-name static-policy-control],
[edit services pcef profiles profile-name dyna... | Specify a policy and charging control (PCC) rulebase for a policy control profile.
If you are using Junos OS Subscriber Aware, specify the PCC rulebase at the [edit unified-edge pcef
profiles profile-name (aaa-policy-control | dynamic-policy-control | static-policy-control) hierarchy level.
If you are using Junos OS Br... | [
{
"name": "rulebase-name",
"desc": "Name of the PCC rulebase. The referenced PCC rulebase must be configured."
},
{
"name": "time-of-day-profile profile-",
"desc": ""
},
{
"name": "name",
"desc": "(Optional; only applies to rulebases in static PCEF profiles for Junos OS Subscriber Aw... | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef profiles profile-name static-policy-control] hierarchy level introduced for
Junos OS Broadband Subscriber Management in Junos OS Release 17.2 on MX Series.
Support at the [edit services pcef profiles profile-name dynamic-policy-control] h... | [
"Configuring a Policy and Charging Enforcement Function Profile for Junos OS Subscriber Aware",
"Dynamic Policies",
"Configuring a Policy and Charging Enforcement Function Profile for Junos OS Subscriber Aware",
"Static Policies",
"Configuring a Policy and Charging Enforcement Function Profile for Junos OS ... |
pcc-rulebases (PCEF) | pcc-rulebases rulebase-name {
[pcc-rule rule-name precedence number];
} | [edit unified-edge pcef],
[edit services pcef] | Configure a policy and charging control (PCC) rulebase. You can specify from 1 through 4000 rules in a
rulebase.
If you are using Junos OS Subscriber Aware, configure the PCC rulebase at the [edit unified-edge pcef]
hierarchy level.
If you are using Junos OS Broadband Subscriber Management, configure the PCC rulebase ... | [
{
"name": "rulebase-name",
"desc": "Name of the PCC rulebase. Range: 1 through 63 characters. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef] hierarchy level introduced for Junos OS Broadband Subscriber
Management in Junos OS Release 17.2 on MX Series. | [
"Configuring a Policy and Charging Control Rulebase"
] |
pcc-rules (PCEF Profile) | pcc-rules [rule-name precedence number <time-of-day-profile profile-name>]; | [edit unified-edge pcef profiles profile-name aaa-policy-control],
[edit unified-edge pcef profiles profile-name dynamic-policy-control],
[edit unified-edge pcef profiles profile-name static-policy-control],
[edit services pcef profiles profile-name static-policy-control],
[edit services pcef profiles profile-name dyna... | Specify the policy and charging control (PCC) rules for a policy and charging enforcement function
(PCEF) profile and assign a precedence to each PCC rule. You can configure up to 32 PCC rules in a
PCEF profile.
If you are using Junos OS Subscriber Aware, specify the PCC rules at the [edit unified-edge pcef profiles
pr... | [
{
"name": "rule-name",
"desc": "Name of the PCC rule. The referenced PCC rule must be configured."
},
{
"name": "precedence",
"desc": ""
},
{
"name": "number",
"desc": "Use the specified precedence value assigned to a PCC rule. A lower precedence value indicates a higher precedence. ... | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef profiles profile-name static-policy-control] hierarchy level introduced for
Junos OS Broadband Subscriber Management in Junos OS Release 17.2 on MX Series.
Support at the [edit services pcef profiles profile-name dynamic-policy-control] h... | [
"Configuring a Policy and Charging Enforcement Function Profile for Junos OS Subscriber Aware",
"Dynamic Policies",
"Configuring a Policy and Charging Enforcement Function Profile for Junos OS Subscriber Aware",
"Static Policies",
"Configuring a Policy and Charging Enforcement Function Profile for Junos OS ... |
pcc-rules (PCEF) | pcc-rules rule-name {
from {
<application-groups [application-group-name]>;
<applications [application-name]>;
flows ([flow-identifier | any)];
}
then {
pcc-action-profile profile-name;
}
} | [edit unified-edge pcef],
[edit services pcef] | Configure the PCC rules. A PCC rule identifies the subscriber IP packets that are associated with a
service data flow (SDF) or application and defines the treatment to be applied to the packets.
If you are using Junos OS Subscriber Aware, configure the PCC rule at the [edit unified-edge pcef]
hierarchy level.
If you ar... | [
{
"name": "rule-name",
"desc": "Name of the PCC rule. Range: 1 through 63 characters. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef] 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 Junos OS
Release 19.3R2 on MX Series... | [
"Configuring Policy and Charging Control Rules",
"Configuring TDF Subscriber Usage Monitoring for Traffic That Matches Predefined PCC Rules"
] |
pcc-time-of-day-profiles | pcc-time-of-day-profiles profile-name {
rule-activation-time {
<day-of-week | day-of-month month>;
<hour:min>;
}
rule-deactivation-time {
<day-of-week | day-of-month month>;
<hour:min>;
}
} | [edit unified-edge pcef] | Configure a PCC time-of-day profile to specify the time of day, day of the week, or day of the month to
activate and deactivate a PCC rule or rulebase. A PCC time-of-day profile is applied to a PCC rule or
PCC rulebase within a static PCEF profile. If a time zone is configured on the router, the time-of-day
settings ap... | [
{
"name": "profile-name",
"desc": "Name of the PCC time-of-day profile. Range: 1 through 63 characters. The remaining statements are explained separately."
}
] | 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 Static Time-of-Day PCC Rule Activation and Deactivation in a Junos OS Subscriber",
"Aware PCEF Profile",
"Understanding Static Time-of-Day PCC Rule Activation and Deactivation"
] |
pce | pce pce-id {
authentication-key key;
authentication-key-chain key-chain;
delegation-cleanup-timeout seconds;
delegation-priority priority-number;
destination-ipv4-address ipv4-address;
destination-port port-number;
local-address ip-address;
lsp-cleanup-timer seconds;
lsp-provisioning... | [edit protocols pcep] | 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": "pce-id",
"desc": "IP address of the PCE."
},
{
"name": "authentication-key key",
"desc": "(Optional) Authentication password. It can be up to 126 characters. Characters can include any ASCII strings. If you include spaces, enclose all characters in quotation marks (“ ”). It is recomme... | 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.
Support for PTX Series added in Junos OS Release 14.2.
Support for QFX Series switches added in Junos OS Release 16.1R3.
Support for ACX Series added in Junos OS Release 17.1R1.
lsp-cleanup-timer, lsp-provisioning, max-unknown-requests, request-timer, and request-priority... | [
"PCEP Configuration"
] |
pce-group (PCE) | pce-group pce-group-name; | [edit protocols pcep pce pce-id] | Specify the Path Computation Element (PCE) group to which the configured PCE belongs. | [
{
"name": "pce-group-name",
"desc": "Name of the PCE group."
}
] | 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.
Support for PTX Series added in Junos OS Release 14.2.
Support for QFX Series switches added in Junos OS Release 16.1R3.
Support for ACX Series added in Junos OS Release 17.1R1. | [] |
pce-group (Protocols PCEP) | pce-group pce-group-id {
delegation-cleanup-timeout seconds;
max-unknown-messages messages-per-minute;
pce-type {
active stateful;
srv6-capability;
}
traceoptions {
file filename <files number> <size size> <world-readable | no-world-readable>;
flag (all | pcep);
... | [edit protocols pcep] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support for PTX Series added in Junos OS Release 14.2.
Support for QFX Series switches added in Junos OS Release 16.1R3.
Support for ACX Series added in Junos OS Release 17.1R1. | [] |
pce-type | pce-type {
active stateful;
} | [edit protocols pcep pce pce-id] | Configure the path computation element (PCE) type:
•
active—Uses LSP state information learned from PCCs to optimize path computations, and actively
updates LSP parameters in those PCCs that delegated control over their LSPs to the PCE.
•
stateful—Uses LSP state information learned from PCCs to optimize path computatio... | [] | 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.
Support for PTX Series added in Junos OS Release 14.2.
Support for QFX Series switches added in Junos OS Release 16.1R3.
Support for ACX Series added in Junos OS Release 17.1R1. | [] |
pcef (Dynamic Profiles) | pcef pcef-profile-name {
activate rule-name | activate-all;
} | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number service] | Assign a policy and charging enforcement function (PCEF profile) to the dynamic profile. The PCEF
profile specifies a set of PCC rules and rulebases to assign to a subscriber for application-aware policy
control, and assigns a precedence value to each predefined rule. Also specify which of the PCC rules to
activate for... | [
{
"name": "activate rule-name",
"desc": "Name of the PCC rule to activate or the predefined dynamic interface variable $junos-pcef-rule. To specify more than one rules, include this line multiple times."
},
{
"name": "activate-all",
"desc": "Activates all of the PCC rules."
},
{
"name": ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2. | [
"Configuring Application-Aware Policy Control for Subscriber Management"
] |
pcef | pcef {
flow-descriptions flow-identifier {
direction (uplink | downlink | both);
local-port-range {
low low-value high high-value;
}
local-ports number;
no-send-to-ue;
protocol number;
remote-address (ipv4-address ipv4-address | ipv6-address ipv6-a... | [edit unified-edge] | Set up the overall policy and control enforcement function (PCEF) configuration.
The remaining statements are explained separately. See CLI Explorer. | [] | 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. | [
"Understanding Junos Subscriber Aware Policy and Charging Enforcement Function (PCEF)",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment"
] |
pcef-profile (Service Set) | pcef-profile pcef-profile-name; | [edit services service-set service-set-name] | Specify the dummy PCEF profile that you configured at the [edit services pcef] hierarchy level. This
profile is a placeholder profile with no configuration options, but it must be specified to enable PCEF
functionality on the services plane. | [
{
"name": "pcef-profile-name",
"desc": "Name of the PCEF profile."
}
] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Applying Services to Subscriber-Aware Traffic with a Service Set",
"Identifying the Service Interface That Handles Subscriber Management Application-Aware Policy",
"Control",
"Configuring a Policy and Charging Enforcement Function Profile for Subscriber Management"
] |
pcef-profile (TDF Domain Selection) | pcef-profile pcef-profile-name; | [edit unified-edge gateways tdf gateway-name domain-selection term term-name then] | Specify the policy and charging enforcement function (PCEF) profile to be selected for the IP-based TDF
subscriber when the criteria specified in the domain-selection term term-name from statement are matched.
This PCEF profile is required if the TDF domain selected for a subscriber does not specify a PCEF profile
or y... | [
{
"name": "pcef-profile-name",
"desc": "Name of the PCEF profile. NOTE: The PCEF profile must have been previously configured at the [edit unified-edge pcef] hierarchy level."
}
] | 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 Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
] |
pcef-profile (TDF Domain) | pcef-profile name; | [edit unified-edge gateways tdf gateway-name domains domain-name] | Specify the policy and charging enforcement function (PCEF) profile to be applied to subscribers in the
TDF domain. This is required for IFL-based subscribers, and optional for IP-based subscribers. If you do
not identify a PCEF profile, then the PCEF profile must be assigned under the [edit unified-edge gateways
tdf g... | [
{
"name": "name",
"desc": "Name of the PCEF profile. NOTE: The PCEF profile must have been previously configured at the [edit unified-edge pcef] hierarchy level."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring a Set of IP-Based TDF Subscriber Properties with a TDF Domain",
"Configuring IFL-Based TDF Subscribers and Properties with a TDF Domain",
"Understanding the Definition of a Set of IP-Based Subscriber Properties with a TDF Domain",
"IP-Based and IFL-Based TDF Subscribers Overview",
"IP-Based Sub... |
pcep | pcep {
message-rate-limit messages-per-minute;
pce pce-id;
pce-group pce-group-id;
traceoptions;
update-rate-limit updates-per-minute;
maximum-srmpls-segment-list-depth maximum-srmpls-segment-list-depth;
maximum-srv6-segment-list-depth
propagate-lsp-max-segment-list-depth
} | [edit protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and rest... | [] | 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.
Support for ACX Series added in Junos OS Release 17.1R1. | [
"Support of the Path Computation Element Protocol for RSVP-TE Overview",
"Example: Configuring the Path Computation Element Protocol for MPLS RSVP-TE",
"Example: Configuring Path Computation Element Protocol for MPLS RSVP-TE with Support of PCE-",
"Initiated Point-to-Point LSPs",
"Example: Configuring Path ... |
pci-address | pci-address pci-address; | [edit virtual-network-functions] | PCI address for the VNF interfaces. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D50. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
pcp-rules | pcp-rules rule-name; | [edit services service-set service-set-name] | Specify the PCP rule to apply to the service set. A PCP rule assigns the PCP server that handles selected
traffic.
PCP is supported on the MS-DPC, MS-100, MS-400, and MS-500 MultiServices PICS. Starting in Junos
OS Release 17.4R1, PCP is also supported on the MS-MPC and MS-MIC. Starting in Junos OS Release
20.1R1, PCP ... | [
{
"name": "rule-name",
"desc": "The PCP rule to apply to the service set."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R1. | [] |
pcp-server | pcp-server server-name; | [edit services pcp rule rule-name term term-name then] | Specify the PCP server that handles the traffic that matches the PCP rule term.
PCP is supported on the MS-DPC, MS-100, MS-400, and MS-500 MultiServices PICS. Starting in Junos
OS Release 17.4R1, PCP is also supported on the MS-MPC and MS-MIC. | [
{
"name": "server-name",
"desc": "Name of the PCP server."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R1. | [
"Configuring Port Control Protocol"
] |
pcrf (Diameter Applications) | pcrf {
global {
rule-param avp-code;
}
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 {
... | [edit access] | Configure the Policy and Charging Rules Function (PCRF) global attributes, rules, parameters, and
partition to authorize and provision subscribers. PCRF is a centralized policy decision point that deploys
business policy and charging rules to allocate broadband network resources and manages flow-based
charges for subsc... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the PCRF Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Interactions Between the PCRF, PCEF, and OCS",
"Understanding Upstream and Downstream Messages for the PCR... |
pdu-interval | pdu-interval interval; | [edit protocols oam ethernet link-fault-management interface interface-name] | For Ethernet interfaces on EX Series switches and M320, M120, MX Series, and T Series routers, specify
the periodic OAM PDU sending interval for fault detection. Used for IEEE 802.3ah Operation,
Administration, and Management (OAM) support. | [
{
"name": "interval",
"desc": "Periodic OAM PDU sending interval."
},
{
"name": "1000 milliseconds",
"desc": "Default: 1000 milliseconds"
}
] | 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 8.2. | [
"Configuring the OAM PDU Interval",
"Example: Configuring Ethernet OAM Link Fault Management",
"Configuring Ethernet OAM Link Fault Management"
] |
pdu-threshold | pdu-threshold threshold-value; | [edit protocols oam ethernet link-fault-management interface interface-name] | Configure how many protocol data units (PDUs) are missed before declaring the peer lost in Ethernet
OAM link fault management (LFM) for all interfaces or for specific interfaces.
For Ethernet interfaces on EX Series switches and M320, M120, MX Series, and T Series routers, specify
the number of OAM PDUs to miss before ... | [
{
"name": "threshold-value",
"desc": "The number of PDUs missed before declaring the peer lost."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Configuring the OAM PDU Threshold",
"Configuring Ethernet OAM Link Fault Management"
] |
peak-burst-size (QFX) | peak-burst-size bytes; | [edit firewall three-color-policer policer-name two-rate] | Configure the maximum number of bytes allowed for incoming packets to burst above the peak
information rate (PIR) and still be marked with medium-high packet loss priority (yellow). Packets that
exceed the peak burst size (PBS) are marked with high packet loss priority (red).
NOTE: When you include the peak-burst-size ... | [
{
"name": "bytes",
"desc": "Number of bytes. You can specify a value in bytes either as a complete decimal number or as a"
}
] | 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",
"Overview of Policers"
] |
peak-burst-size | peak-burst-size bytes; | [edit dynamic-profiles profile-name firewall three-color-policer name two-rate],
[edit firewall three-color-policer policer-name two-rate] | For a two-rate three-color policer, configure the peak burst size (PBS) as a number of bytes. The PBS
defines the maximum number of bytes of unused peak bandwidth capacity that can be accumulated.
The accumulated bandwidth allows for moderate periods of bursting traffic that exceeds the peak
information rate (PIR) and ... | [
{
"name": "bytes",
"desc": "Number of bytes. You can specify a value in bytes either as a complete decimal number or as a"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4.
Support at the [edit dynamic-profiles ... two-rate] hierarchy level introduced in Junos OS Release 11.4. | [
"Three-Color Policer Configuration Overview",
"Policer Bandwidth and Burst-Size Limits",
"Policer Color-Marking and Actions",
"Dual Token Bucket Algorithms",
"Determining Proper Burst Size for Traffic Policers"
] |
peak-information-rate (QFX) | peak-information-rate bits-per-second; | [edit firewall three-color-policer policer-name two-rate] | Configure the maximum achievable rate. Packets that exceed the committed information rate (CIR) but
are below the peak information rate (PIR) are marked with medium-high packet loss priority (yellow).
Packets that exceed the PIR are marked with high packet loss priority (red). You can configure a discard
action for pac... | [
{
"name": "bits-per-second",
"desc": "Number of bits per second. You can specify a value in bits per second either as a"
}
] | 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",
"Overview of Policers"
] |
peak-information-rate | peak-information-rate bps; | [edit dynamic-profiles profile-name firewall three-color-policer name two-rate],
[edit firewall three-color-policer policer-name two-rate] | For a two-rate three-color policer, configure the peak information rate (PIR) as a number of bits per
second. The PIR is the maximum rate for traffic arriving at or departing from the interface under peak
line conditions. Traffic that exceeds the committed information rate (CIR) and the committed burst size
(CBS) is me... | [
{
"name": "bps",
"desc": "Number of bits per second. You can specify a value in bits per second either as a complete decimal"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4.
Support at the [edit dynamic-profiles ... two-rate] hierarchy level introduced in Junos OS Release 11.4. | [
"Three-Color Policer Configuration Overview",
"Policer Bandwidth and Burst-Size Limits",
"Policer Color-Marking and Actions",
"Dual Token Bucket Algorithms",
"Determining Proper Burst Size for Traffic Policers"
] |
peak-rate | peak-rate rate; | [edit class-of-service traffic-control-profiles traffic-control-profile-name] | (MX Series routers) Define ATM peak cell rate on ATM MICs in cells per second by entering a decimal
number followed by the abbreviation c; where 1 cps = 384 bps. | [
{
"name": "rate",
"desc": "ATM peak rate in cells per second."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [] |
peer (Diameter Base Protocol) | peer peer-name {
address ip-address;
connect-actively {
<capabilities-exchange-timeout seconds>;
<port port-number>;
<repeat-timeout seconds>;
<retry-timeout seconds>;
<timeout seconds>;
transport transport-name;
}
<disconnect-peer-timeout seconds>;
<i... | [edit access diameter] | Configure a remote peer for the Diameter instance. You can configure up to 31 peers. | [
{
"name": "peer-name",
"desc": "Name of the peer."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [] |
peer (Diameter Base Protocol) | peer peer-name {
address ip-address;
connect-actively {
port port-number;
transport transport-name;
}
logical-system logical-system-name <routing-instance routing-instance-name>;
peer-origin realm realm-name host hostname;
routing-instance routing-instance-name;
send-origin... | [edit diameter] | Configure peer-specific Origin-Realm and Origin-Name AVP values to include in the CER, DWR, DWA,
DPR, and DPA messages of this peer. | [
{
"name": "peer-name",
"desc": "Name of the peer."
}
] | 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. | [
"Configuring Diameter",
"Configuring Diameter Peers"
] |
peer (Diameter Network Element) | peer peer-name {
priority priority-value;
<timeout seconds>;
} | [edit access diameter network-element element-name] | Define and prioritize a peer associated with a Diameter network element. You must prioritize the
associated peer by including the priority statement. | [
{
"name": "peer-name",
"desc": "Name of the peer."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [] |
peer (Diameter Network Element) | peer peer-name {
priority priority-value;
} | [edit diameter network-element element-name] | Assigns a peer to a Diameter network element and sets a priority value for that peer within the DNE. | [
{
"name": "peer-name",
"desc": "Name of the peer."
}
] | 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. | [
"Configuring Diameter",
"Configuring Diameter Network Elements"
] |
peer (ICCP) | peer ip-address {
authentication-key string;
backup-liveness-detection {
backup-peer-ip ip-address;
}
liveness-detection {
detection-time {
threshold milliseconds;
}
minimum-intervalmilliseconds;
minimum-receive-interval milliseconds;
multipli... | [edit protocols iccp] | Configure the peers that host a multichassis link aggregation group (MC-LAG). You must configure Inter-
Chassis Control Protocol (ICCP) for both peers that host the MC-LAG.
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 10.0. | [] |
peer (Multichassis) | peer ip-address {
interface interface-name;
} | [edit multi-chassis] | Configure the IP address of the peer that is part of the interchassis link-protection link (ICL-PL). If Inter-
Chassis Control Protocol (ICCP) is up and the interchassis link (ICL) comes up, the peer configured as
standby will bring up the multichassis aggregated Ethernet interfaces shared with the active peer
specifie... | [] | 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. | [] |
peer (Protocols LMP) | peer peer-name {
address ip-address;
control-channel control-channel-interface;
lmp-control-channel control-channel-interface;
lmp-protocol {
hello-dead-interval milliseconds;
hello-interval milliseconds;
passive;
retransmission-interval milliseconds;
retry-limit ... | [edit logical-systems logical-system-name protocols link-management],
[edit protocols link-management] | Configure a network peer. | [
{
"name": "peer-name",
"desc": "Name of the network peer."
}
] | 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.
lmp-protocol statement and substatements added in Junos OS Release 8.1. | [
"Configuring LMP Peers"
] |
peer (Protocols MSDP) | peer address {
disable;
active-source-limit {
maximum number;
threshold number;
}
authentication-key peer-key;
default-peer;
export [ policy-names ];
import [ policy-names ];
local-address address;
traceoptions {
file filename <files number> <size size> <worl... | [edit logical-systems logical-system-name protocols msdp],
[edit logical-systems logical-system-name protocols msdp group group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
msdp],
[edit logical-systems logical-system-name routing-instances routing-instance-name pro... | 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": "address",
"desc": "Name of the MSDP peer."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring MSDP in a Routing Instance"
] |
peer (Protocols RIP) | peer IP address; | [edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name],
[edit protocols rip group group-name neighbor neighbor-name] | Configure a static peer for an interface in a point-to-multipoint RIP network. | [
{
"name": "address",
"desc": "IP address of the static peer to be configured."
}
] | 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. | [
"Example: Configuring Point-to-Multipoint RIP Networks"
] |
peer | peer a.b.c.d {
interface interface-name;
} | [edit interfaces interface-name multi-chassis-protection] | For MX Series routers with multichassis aggregated Ethernet (MC-AE) interfaces, use the multi-chassis-
protection statement under the physical interface level to reduce the configuration at the logical interface
level. If the interchassis control protocol connection (ICCP) is UP and the interchassis data link (ICL)
com... | [
{
"name": "a.b.c.d",
"desc": "Specify the IP address of the peer."
},
{
"name": "interface interface-name",
"desc": "Specify the peer’s physical interface: interface interface-name-fpc/pic/port"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring Active-Active Bridging and VRRP over IRB in Multichassis Link Aggregation on MX",
"Series Routers and QFX Series Switches",
"Configuring Aggregated Ethernet Link Protection",
"Example: Configuring Aggregated Ethernet Link Protection"
] |
peer-active (VPLS Multihoming for FEC 129) | peer-active; | [edit logical-systems logical-system-name routing-instances instance-name protocols vpls multi-
homing],
[edit logical-systems logical-system-name routing-instances instance-name protocols vpls multi-
homing site site-name],
[edit routing-instances instance-name protocols vpls multi-homing],
[edit routing-instances ins... | Keep customer edge (CE) interfaces in the up state when all BGP peers go down.
NOTE: In the VPLS documentation, the word router in terms such as PE router is used to
refer to any device that provides routing functions.
Consider a scenario in which two provider edge (PE) routers are sharing two multihomed sites under on... | [] | 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. | [
"Example: Configuring VPLS Multihoming (FEC 129)"
] |
peer-as (Protocols BGP) | peer-as autonomous-system; | [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... | Specify the neighbor (peer) autonomous system (AS) number.
For EBGP, the peer is in another AS, so the AS number you specify in the peer-as statement must be
different from the local router’s AS number, which you specify in the autonomous-system statement. For
IBGP, the peer is in the same AS, so the two AS numbers tha... | [
{
"name": "autonomous-system",
"desc": "AS number."
}
] | 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. | [] |
peer-as (VPLS) | peer-as {
all;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
mesh-group mesh-group-name],
[edit routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name] | Enable the autonomous system border router (ASBR) to establish a single pseudowire to each of the
other ASBRs interconnected using inter-AS VPLS with MAC processing at the ASBR.
NOTE: In the VPLS documentation, the word router in terms such as PE router is used to
refer to any device that provides routing functions. | [
{
"name": "all",
"desc": "This option is required. All peer routers, the ASBRs, are placed within the same VPLS mesh group."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Configuring Inter-AS VPLS with MAC Processing at the ASBR"
] |
peer-as-billing-template | peer-as-billing-template; | [edit services flow-monitoring version9 template template-name] | Enables the extraction of bandwidth usage information for billing purposes in PIC-based sampling
configurations. This capability is supported on routers and applies only to IPv4 and IPv6 traffic. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9",
"Flow Templates"
] |
peer-as-list | peer-as-list peer-as-list; | [edit fabric protocols bgp group],
[edit logical-systems name protocols bgp group],
[edit logical-systems name routing-instances name protocols bgp group],
[edit logical-systems name tenants name routing-instances name protocols bgp group],
[edit protocols bgp group],
[edit routing-instances name protocols bgp group],
... | Specify a list of peer autonomous systems for neighbors whose IP addresses are not known. This
supports dynamic peering and allows you to control BGP peering when the neighbor’s exact IP address
is not known. | [] | routing | Statement introduced in Junos OS Release 20.2R1. | [] |
peer-certificate-type | peer-certificate-type (pkcs7 | x509-signature); | [edit services ipsec-vpn ike policy policy-name] | (MX Series routers only) Specify a preferred type of certificate (PKCS7 or X509). By default, X509
encoding format is used. With the flexibility to configure the encoding format in which certificate
requests are sent to the peer, you can determine the type of certificate to be used depending on the
type supported by th... | [
{
"name": "pkcs7",
"desc": "Public-Key Cryptography Standard #7."
},
{
"name": "x509-signature",
"desc": "X509 is an ITU-T standard for public key infrastructure."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Release 15.1. | [
"Configuring IKE Policies"
] |
peer-domain-id | peer-domain-id name {
domain-size domain-size;
peer-id name {
desc desc;
interface interface;
liveness-detection {
no-adaptation;
detection-time {
threshold milliseconds;
}
minimum-int... | [edit chassis high-availability] | Peer domain related information | [
{
"name": "ID",
"desc": "Peer domain identifier Range:1 through 2"
},
{
"name": "domain-size",
"desc": "Peer domain size Default: 2 Range: 1 through 2"
},
{
"name": "peer-id",
"desc": "Peer node identifier in a peer domain."
}
] | [none specified] | Statement introduced in Junos OS Release 25.4R1 | [] |
peer-forwarding-ip | peer-forwarding-ip loopback-address {
interface interface-name;
liveness-detection {
no-adaptation;
detection-time {
threshold milliseconds;
}
minimum-interval milliseconds;
minimum-receive-interv... | [edit chassis high-availability peer-id] | Configure peer node for managing asymmetric traffic handling. | [
{
"name": "IP-address",
"desc": "Specify peer forwarding IP. This forwarding address used to forward data packet over ICD link. Interface Specify interface for forwarding data packets for ICD."
},
{
"name": "\"liveness-detection\" on page",
"desc": "Specify BFD failure detection time."
}
] | interface | Statement introduced in Junos OS Release 20.4R1. | [
"Multinode High Availability",
"Example: Configure Multinode High Availability in a Layer 3 Network"
] |
peer-gnf | peer-gnf {
id peer-gnf-id;
remote-af-name;
} | [edit chassis network-slices guest-network-functions gnf id af-name] | Configure the details of the GNF peer connected using the abstracted fabric (af) interface. | [
{
"name": "idpeer-gnf -id",
"desc": "Name of the GNF peer connected using the abstracted fabric (af) interface. Range: 1 through 10"
},
{
"name": "remote-af-name",
"desc": "Name of the af interface on the peer GNF."
}
] | system | Statement introduced in Junos OS Release 17.4R1. | [
"Setting Up Junos Node Slicing"
] |
peer-groups (access network peers) | peer-groups name {
peer {
address [ address ... ];
hostname hostname;
}
routing-instance routing-instance;
} | [edit services mobile-edge gateways saegw name access-network-peers] | Define a group of eNodeBs for an SAEGW-U or SGW-U. | [
{
"name": "name",
"desc": "Peer group name."
},
{
"name": "peer",
"desc": "IPv4 address or prefix value (required) of the GTP-U peer and hostname (optional) of the GTP-U peer. NOTE: The maximum number of peers that can appear in a peer group is 4000."
},
{
"name": "routing-instance",
... | system | Statement introduced in Junos OS Release 19.4R1. | [] |
peer-groups (control plane peers) | peer-groups name {
heartbeat-interval seconds;
n3-requests n3-requests;
path-management (disable | enable);
peer {
address [ address ... ];
hostname hostname;
}
routing-instance routing-instance;
t3-response seconds;
} | [edit services mobile-edge gateways saegw name control-plane-peers] | If at least one peer group is configured, PFCP packets from control plane peers matching this address/
prefix alone are accepted. The control plane peers are bound to the routing instance defined within this
peer group, if configured. Otherwise the control plane function is bound to the routing instance listed
under "... | [
{
"name": "name",
"desc": "Peer group name"
},
{
"name": "heartbeat-interval",
"desc": "Time between origination of two successive heartbeat requests (seconds). Range: 60 through 255 Default: 60"
},
{
"name": "n3-requests",
"desc": "Maximim number of retries of PFCP request message... | system | Statement introduced in Junos OS Release 19.4R1. | [] |
peer-groups (core network peers) | peer-groups name {
peer {
address [ address ... ];
hostname hostname;
}
routing-instance routing-instance;
} | [edit services mobile-edge gateways saegw name core-network-peers] | Define a peer group of PGW-Us for an SGW-U or a group of SGW-Us for a PGW-U. | [
{
"name": "name",
"desc": "Peer group name."
},
{
"name": "peer",
"desc": "IPv4 address or prefix value (required) of the GTP-U peer and hostname (optional) of the GTP-U peer. NOTE: The maximum number of peers that can appear in a peer group is 4000."
},
{
"name": "routing-instance",
... | system | Statement introduced in Junos OS Release 20.4R1. | [] |
peer-id | peer-id name {
desc desc;
interface interface;
liveness-detection {
no-adaptation;
detection-time {
threshold milliseconds;
}
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier multiplier;
transmit-interval {
... | [edit chassis high-availability] | Configure the other node related information in a Multinode High Availability setup. | [
{
"name": "ID",
"desc": "Peer node identifier."
},
{
"name": "desc",
"desc": "Peer node description."
},
{
"name": "interface",
"desc": "Name of the interface used for communicating with the peer node using the interchassis link (ICL."
},
{
"name": "\"liveness-detection\" on"... | interface | Statement introduced in Junos OS Release 20.4R1. | [
"Multinode High Availability",
"Example: Configure Multinode High Availability in a Layer 3 Network"
] |
peer-interface (Protocols OSPF) | peer-interface interface-name {
disable;
dead-interval seconds;
hello-interval seconds;
retransmit-interval seconds;
transit-delay seconds;
} | [edit logical-systems logical-system-name protocols ospf area area-id],
[edit protocols ospf area area-id] | Configure a peer interface. | [
{
"name": "interface-name",
"desc": "Name of the peer interface. To configure all interfaces, you can specify all."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring OSPFv2 Peer interfaces",
"Configuring RSVP and OSPF for LMP Peer Interfaces",
"Configuring a Hierarchy of RSVP LSPs to Tunnel Multiple RSVP LSPs Over a Single RSVP LSP"
] |
peer-interface (Protocols RSVP) | peer-interface peer-interface-name {
disable;
(aggregate | no-aggregate);
authentication-key key;
dynamic-bidirectional-transport template template;
hello-interval seconds;
(reliable | no-reliable);
} | [edit protocols rsvp] | Configure the name of the LMP peer device.
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.
dynamic-bidirectional-transport template template option introduced in Junos OS Release 14.2. | [
"Configuring RSVP and OSPF for LMP Peer Interfaces"
] |
peer-ip-address-optional | peer-ip-address-optional; | [edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit ppp-options],
[edit interfaces interface-name pp0 unit unit-number ppp-options],
[edit access group-profile profile-name ppp ppp-options] | Enable the Internet Protocol Control Protocol (IPCP) negotiation to succeed even though the peer does
not include the IP address option in an IPCP configuration request for static and dynamic, and
terminated and tunneled, Point-to-Point Protocol over Ethernet (PPPoE) subscribers. By default, this
statement 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 15.1. | [
"IPCP Negotiation with Optional Peer IP Address",
"Dynamic Profiles Overview"
] |
peer-limit | peer-limit peer-limit; | [edit fabric protocols bgp group name dynamic-neighbor],
[edit logical-systems name protocols bgp group name dynamic-neighbor],
[edit logical-systems name routing-instances name protocols bgp group name dynamic-neighbor],
[edit logical-systems name tenants name routing-instances name protocols bgp group name dynamic-
n... | Limit the number of peers for each subnet configured via dynamic-neighbor | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4. | [] |
peer-origin (Diameter Peer) | peer-origin realm realm-name host hostname; | [edit diameter peer peer-name] | Specify values of Origin-Realm-AVP and Origin-Host-AVP used in messages sent for the specified peer
by the Diameter instance.
NOTE: Both the host and realm are mandatory for the peer origin. | [
{
"name": "host hostname",
"desc": "Name of the message origin host that is supplied as the value of the Origin-Host AVP for Diameter messages to the peer."
},
{
"name": "realm realm-name",
"desc": "Name of the message origin realm, that is supplied as the value of the Origin-Realm AVP for Diame... | 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 Diameter Peers",
"Configuring Diameter"
] |
peer-selection-service | peer-selection-service {
command binary-file-path;
disable;
failover (alternate-media | other-routing-engine);
} | [edit system processes] | Enable the peer selection service process. | [
{
"name": "command binary-file-path",
"desc": "Path to the binary process."
},
{
"name": "disable",
"desc": "Disable the peer selection service 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. | [
"Interfaces User Guide for Security Devices"
] |
peer-subnet (Easy EVPN LAG Configuration) | peer-subnet {
inet inet-address;
inet6 inet6-address;
interface-name [interface-name ... ];
} | [edit services evpn device-attribute peer-to-peer] | Specify interface parameters for the peer-to-peer connections between Ethernet VPN (EVPN) fabric
provider edge (PE) devices as part of a generated EVPN fabric configuration.
You use the statements in the [edit services evpn] hierarchy level to simplify configuring an EVPN fabric
with Ethernet segment identifier (ESI) ... | [
{
"name": "inet inet-address",
"desc": "The IPv4 subnet address for the interfaces or aggregated Ethernet interfaces that connect the PE device to a peer PE device. You should configure the same subnet address for this option on both peer PE devices."
},
{
"name": "inet6 inet6-address",
"desc": ... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.2R1. | [
"Easy EVPN LAG (EZ-LAG) Configuration"
] |
peer-to-peer (Easy EVPN LAG Configuration) | peer-to-peer {
overlay-connectivity {
ibgp;
}
peer-subnet {
inet inet-address;
inet6 inet6-address;
interface-name [ interface-name ... ];
}
underlay-connectivity {
ospf;
}
} | [edit services evpn device-attribute] | Specify parameters for the peer-to-peer interface connections between Ethernet VPN (EVPN) fabric
provider edge (PE) devices as part of a generated EVPN fabric configuration.
You use the statements in the [edit services evpn] hierarchy level to simplify configuring an EVPN fabric
with Ethernet segment identifier (ESI) l... | [
{
"name": "overlay-connectivity",
"desc": "Use the specified protocol for the EVPN fabric overlay peering instead of EBGP, which is the default overlay protocol the [edit services evpn] commit script configures. Available options:"
},
{
"name": "ibgp",
"desc": "Use IBGP for the overlay peering i... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.2R1. | [
"Easy EVPN LAG (EZ-LAG) Configuration"
] |
peer-unit (Routing Policy Condition) | peer-unit unit-number; | [edit logical-systems logical-system-name policy-options condition if-route-exists address-family
ccc],
[edit policy-options condition if-route-exists address-family ccc] | Specify the associated logical tunnel interface’s peer-unit. This is required for logical-tunnel-based
routes. | [
{
"name": "unit-number",
"desc": "Logical unit number of the logical tunnel peer interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Example: Configuring Pseudowire Redundancy in a Mobile Backhaul Scenario"
] |
peer-unit | peer-unit unit-number; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Configure a peer relationship between two logical systems. | [
{
"name": "unit-number",
"desc": "Peering logical system unit number."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Evolved Release 24.1R1 for ACX7K Series Routers. | [
"Configuring Logical Tunnel Interfaces"
] |
peers (Commit) | peers {
name of peer {
user name of user;
authentication string;
routing-instance name ;
}
} | [edit system commit] | Configure options for the peers participating in commit synchronization.
NOTE: In configuration sync across SRX Series Firewalls, routing instance need be
specified and configured to let local node reach peer nodes through a configurable
routing instance instead of default routing instance. | [
{
"name": "name of peer",
"desc": "Hostname or IP address of the peer participating in commit synchronization."
},
{
"name": "user",
"desc": "Name of administrator configuring commit synchronization."
},
{
"name": "authentication",
"desc": "Plain-text password string that is stored a... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 14.2R6. | [] |
peers-synchronize | peers-synchronize; | [edit system commit] | Configure the commit command to automatically perform a peers-synchronize action between peers. The
local peer (or requesting peer) on which you enable the peers-synchronize statement copies and loads its
configuration to the remote (or responding) peer. Each peer then performs a syntax check on the
configuration file ... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R6. | [] |
peg-df-election | peg-df-election {
delay-time seconds;
mod;
preference {
use-least;
value value;
}
} | [edit protocols evpn oism pim-evpn-gateway],
[edit routing-instances name protocols evpn oism pim-evpn-gateway] | Use one of the available PIM EVPN gateway (PEG) designated forwarder (DF) election methods with
optimized intersubnet multicast (OISM) for a Layer 3 (L3) virtual routing and forwarding (VRF) instance
or for the default L3 routing instance on an EVPN fabric device.
Otherwise, if you don't enable PEG DF election, by defa... | [
{
"name": "delay-time",
"desc": ""
},
{
"name": "seconds",
"desc": "Time to wait (in seconds) before applying the selected method to elect a PEG DF. Range: 1 through 1800"
},
{
"name": "mod",
"desc": "Use mod-based PEG DF election. This method is the default if you enable PEG DF ele... | 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 and Junos OS Evolved Release 23.4R1.
Support in the default L3 routing instance introduced in Junos OS Evolved Release 25.4R1. | [
"PEG DF Election"
] |
pem (MX Series Devices, ACX7024 Devices) | pem {
minimum number
redundancy;
} | [edit chassis] | Configure the minimum number of Power Entry Modules (PEMs) on an M320, MX10004, MX10008 and
ACX7024 devices. With this configuration, PEM absent alarms are generated only if the PEM count falls
below the minimum specified. | [
{
"name": "minimum number",
"desc": "Minimum number of PEMs on the router. ACX7024 device supports dual PSU (1+1"
},
{
"name": "redundancy",
"desc": "Specify power redundancy. This option is only applicable on the MX10004 and MX10008"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring the Junos OS to Support Entry-Level Configuration on an M320 Router with a Minimum",
"Number of SIBs and PIMs"
] |
pem (T640, T1600, and T4000 Routers with Six-Input DC Power Supply) | pem {
feeds number-of-input-feeds;
input-current amps-in-each-feed;
} | [edit chassis],
[edit chassis lcc lcc-number] | Configure the power supply parameters of the six-input DC power supply on T640, T1600, or T4000
routers. | [
{
"name": "feeds number-of-input-feeds",
"desc": "Number of input feeds connected to the six-input DC power supply."
},
{
"name": "(For T4000 routers only) input-current amps-in-each-feed",
"desc": "Input current (in amperes) in each feed."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1.
Option feeds introduced in Junos OS Release 12.1.
Option input-current introduced for T4000 routers in Junos OS Release 12.3. | [
"Configuring the Six-Input DC Power Supply on T Series Routers"
] |
pem-absence | pem-absence ignore; | [edit chassis alarm] | Configure pem-absence ignore to ignore the red alarm of missing power supply unit. To delete the
configuration use [# delete chassis alarm pem-absence] command. | [
{
"name": "ignore",
"desc": "Ignores the power supply module absence alarm."
}
] | Statement introduced in Junos OS Release 20.3R1 for SRX4100 and SRX4200.
Statement introduced in Junos OS Release 20.4R1 for SRX1500 and SRX4600. | [
"Understanding Chassis Alarms"
] | |
pending-queue-watermark | pending-queue-watermark watermark; | [edit access radius network-element name] | Configure the pending-request queue high watermark for the network element. This is a percentage of
the maximum number of requests that can be queued to the network element, which is configured in
the maximum-pending-reqs-limit number statement at the [edit access radius network-element name] hierarchy
level. When the ... | [
{
"name": "watermark",
"desc": "High watermark for the network element pending request queue. Range: 1 through 100 percent."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring RADIUS Network Elements",
"Understanding Network Elements",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules"
] |
pending-queue-watermark-abate | pending-queue-watermark-abate abate-watermark; | [edit access radius network-element name] | Configure the low watermark of the pending-request queue for the network element. This is a
percentage of the maximum size of the pending-request queue, which is configured in the maximum-
pending-reqs-limit watermark statement at the [edit access radius network-element name] hierarchy level. When
the number of pending... | [
{
"name": "abate-watermark",
"desc": "Low watermark for the network element pending request queue. Range: 1 through 100 percent."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring RADIUS Network Elements",
"Understanding Network Elements",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules"
] |
pending-sess-queue-length | pending-sess-queue-length (high | moderate | normal); | [edit security flow] | Configure the maximum queued length per pending session. | [
{
"name": "high",
"desc": "Allow the maximum number of queued sessions."
},
{
"name": "moderate",
"desc": "Allow more queued sessions than the normal number."
},
{
"name": "normal",
"desc": "Allow the normal number of queued session."
}
] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Understanding Traffic Processing on Security Devices"
] |
per-esi | per-esi {
lacp-oos-on-ndf;
} | [edit interfaces name esi df-election-granularity] | Ensure that all the member links in an aggregated Ethernet (AE) interface between a multihomed
customer edge (CE) device and its multihoming peer provider edge (PE) devices take the same
designated forwarder (DF) election role per Ethernet segment (ES). The behavior with this option is
called port-based DF election wit... | [
{
"name": "lacp-oos-on-",
"desc": ""
},
{
"name": "ndf",
"desc": "In an EVPN single-active configuration, the PE device that is the non-DF will send LACP out-of-sync packets to the multihomed CE device. As a result, LACP goes down on the CE device, and the CE device does not send traffic on the ... | interface | Statement introduced in Junos OS Release 20.4R1 | [] |
per-esi-vlan | per-esi-vlan; | [edit interfaces name esi df-election-granularity] | Enable aggregated Ethernet interface member links between a multihomed CE device and its
multihoming peer provider edge (PE) devices to take different designated forwarder (DF) election roles
per Ethernet segment (ES) and per VLAN. This is the default behavior with EVPN multihoming.
If you want to ensure all the member... | [] | interface | Statement introduced in Junos OS Release 20.4R1 | [] |
per-evi | per-evi; | [edit interfaces interface-name esi df-election-granularity],
[edit interfaces interface-name unit logical-unit-number esi df-election-granularity] | Enable the designated forwarder (DF) election granularity to support Ethernet segment ID (ESI) at the
EVPN instance (EVI) level.
You can configure multiple access interfaces to support ESI at the EVI level between a multihomed
customer edge (CE) device and its multihoming provider edge (PE) peer. When you configure the... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.2R1 | [
"EVPN Multihoming Overview"
] |
per-flow (Aggregated Ethernet Interfaces) | per-flow; | [edit interfaces aeX unit logical-unit-number forwarding-options load-balance-stateful] | Enable the mechanism to perform an even, effective distribution of traffic flows across member links of
an aggregated Ethernet interface (ae) bundle on MX Series routers with MPCs, except MPC3Es and
MPC4Es. When multiple flows are transmitted out of an ae interface, the flows must be distributed
across the different me... | [
{
"name": "per-flow",
"desc": "Enable the stateful load-distribution mechanism per traffic flow on an aggregated Ethernet interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R1. | [
"Configuring Stateful Load Balancing on Aggregated Ethernet Interfaces"
] |
per-flow | per-flow {
hash-seed;
} | [edit forwarding-options load-balance],
[edit logical-systems logical-system-name forwarding-options load-balance],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options load-balance],
[edit routing-instances routing-instance-name forwarding-options load-balance] | Enable per-flow load balancing based on hash values. | [
{
"name": "hash-seed",
"desc": "Configure the hash value. Junos OS automatically chooses a value for the hashing algorithm"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3 (M120, M320, and MX Series routers only). | [
"Configuring Per-Flow Load Balancing Based on Hash Values"
] |
per-group-label | per-group-label; | [edit logical-systems logical-system-name protocols bgp family inet labeled-unicast],
[edit logical-systems logical-system-name protocols bgp group group-name family inet labeled-
unicast],
[edit protocols bgp family inet labeled-unicast],
[edit protocols bgp group group-name family inet labeled-unicast] | Account for traffic from each customer separately by advertising separate labels for the same prefix to
the peer routers in the BGP groups. | [] | 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 BGP to Gather Interprovider and Carrier-of-Carriers VPNs Statistics",
"Understanding Interprovider and Carrier-of-Carriers VPNs"
] |
per-prefix | per-prefix {
hash-seed number;
} | [edit forwarding-options load-balance],
[edit logical-systems logical-system-name forwarding-options load-balance],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options load-balance],
[edit routing-instances routing-instance-name forwarding-options load-balance] | Configure the hash parameter for per-prefix load balancing. | [
{
"name": "hash-seed",
"desc": "Per-prefix load-balancing hash function."
},
{
"name": "number",
"desc": "Hash value."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Configuring Per-Prefix Load Balancing"
] |
per-prefix-label | per-prefix-label; | [edit logical-systems logical-system-name protocols bgp family inet labeled-unicast],
[edit logical-systems logical-system-name protocols bgp group group-name family inet labeled-
unicast],
[edit protocols bgp family inet labeled-unicast],
[edit protocols bgp group group-name family inet labeled-unicast],
[edit routing... | Allocate a unique label for each prefix. The per-prefix-label statement helps minimize packet loss in most
deployments.
Although allocating a label for each prefix is not generally ideal for scaling, it is assumed that a small
number of labels are used for BGP labeled-unicast. When labeled BGP is used to set up transp... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1x48. | [
"MPLS Label Allocation"
] |
per-route-accounting | (per-route-accounting | no-per-route-accounting); | [edit logical-systems name routing-instances name routing-options flow],
[edit logical-systems name routing-options flow],
[edit logical-systems name tenants name routing-instances name routing-options flow],
[edit routing-instances name routing-options flow],
[edit routing-options flow],
[edit tenants name routing-ins... | Typically, in the BGP FlowSpec filter, an individual counter was added for each FlowSpec term
configured. As part of optimization to FlowSpec, starting from Junos OS Evolved Release 21.1R1 this
behavior is changed, and counter action is not added by default. We now support a higher scale of flows
in BGP FlowSpec filter... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 21.1R1. | [] |
per-session-scheduler | per-session-scheduler; | [edit interfaces interface-name unit logical-unit-number] | Enable session-aware CoS shaping on this L2TP interface. | [] | 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. | [] |
per-unit-scheduler | per-unit-scheduler; | [edit interfaces interface-name] | Enable the association of scheduler maps or traffic control profiles with logical interfaces.
CAUTION: Turning on per-unit scheduling causes the interface to reinitialize, which
means all logical interfaces (units) on the interface are deleted and recreated.
When including the per-unit-scheduler statement, you must als... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Applying Scheduler Maps and Shaping Rate to DLCIs and VLANs",
"Example: Applying Scheduling and Shaping to VLANs",
"Configuring Virtual LAN Queuing and Shaping on PTX Series Routers",
"Providing a Guaranteed Minimum Rate"
] |
perfect-forward-secrecy (Security) | perfect-forward-secrecy {
keys (group1 | group2);
} | [edit security ipsec policy ipsec-policy-name] | Define the Perfect Forward Secrecy (PFS) protocol. Create single-use keys. | [
{
"name": "keys",
"desc": "Type of Diffie-Hellman prime modulus group that IKE uses when performing the new Diffie-Hellman exchange."
},
{
"name": "group1",
"desc": "768-bit."
},
{
"name": "group2",
"desc": "1024-bit."
}
] | 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 IPsec Policy for an ES PIC"
] |
perfect-forward-secrecy (Services) | perfect-forward-secrecy {
keys (group1 | group2 |group5 |group14 |group15 | group16 | group24);
} | [edit services ipsec-vpn ipsec policy policy-name] | Define Perfect Forward Secrecy (PFS). Creates single-use keys. This statement is optional. | [
{
"name": "keys",
"desc": "Type of Diffie-Hellman prime modulus group that IKE uses when performing the new Diffie-Hellman exchange. The key can be one of the following:"
},
{
"name": "group1",
"desc": "768-bit."
},
{
"name": "group2",
"desc": "1024-bit."
},
{
"name": "group5... | 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.
group15, group16, and group24 options added in Junos OS Release 17.4R1. | [
"Configuring IPsec Policies"
] |
performance | performance {
values [fast normal slow unknown];
} | [edit security idp dynamic-attack-group dynamic-attack-group-name filters] | Specify a performance filter to add attack objects based on the performance level that is vulnerable to
the attack. | [
{
"name": "values",
"desc": "Name of the performance filter. You can select from the following performance levels:"
},
{
"name": "fast",
"desc": "Fast track performance level."
},
{
"name": "normal",
"desc": "Normal track performance level."
},
{
"name": "slow",
"desc": "... | 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. | [] |
performance-monitor | performance-monitor {
passive-port {
delay-request-rate delay-request-rate;
}
slave-port;
} | [edit logical-systems name protocols ptp],
[edit protocols ptp] | PTP packet delay metrics | [
{
"name": "passive-port",
"desc": "Enable PTP performance monitoring for passive ports"
},
{
"name": "slave-port",
"desc": "Enable IEEE 1588v2.1 (2019) Annex J1 & J3 performance monitoring"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.4R1. | [] |
performance-monitoring (OAM LFM) | performance-monitoring {
sla-iterator-profiles {
profile-name {
calculation-weight {
delay delay-value;
delay-variation delay-variation-value;
}
cycle-time cycle-time-value;
iteration-period iteration-period-value;
... | [edit protocols oam ethernet connectivity-fault-management] | Specify performance monitoring support for Ethernet frame delay measurement.
The remaining statements are explained separately. See CLI Explorer. | [] | Configure—To enter configuration mode.
Control—To modify any configuration. | Statement introduced in Junos OS Release 11.4. | [
"Configure MEP Interfaces on Switches to Support Ethernet Frame Delay Measurements (CLI",
"Procedure)",
"Configure One-Way Ethernet Frame Delay Measurements on Switches (CLI Procedure)",
"Configure Two-Way Ethernet Frame Delay Measurements on Switches (CLI Procedure)"
] |
performance-monitoring (Protocols MPLS) | performance-monitoring {
querier {
delay {
traffic-class tc-value {
average-sample-size sample size;
padding-size size;
query-interval milliseconds;
rtt-delay-threshold rtt threshold value;
twcd-delay-threshold twcd ... | [edit protocols mpls oam],
[edit protocols mpls label-switched-path lsp-name oam],
[edit protocols mpls label-switched-path lsp-name primary path-name oam],
[edit protocols mpls label-switched-path lsp-name secondary path-name oam] | Configure performance monitoring options.
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 15.1. | [] |
performance-monitoring | performance-monitoring {
delegate-server-processing;
hardware-assisted-timestamping;
hardware-assisted-keepalives;
sla-iterator-profiles {
profile-name {
avg-fd-twoway-threshold;
avg-ifdv-twoway-threshold;
avg-flr-forward-threshold;
avg-flr-backwar... | [edit protocols oam ethernet connectivity-fault-management] | Specify performance monitoring support for Ethernet frame delay measurement.
The remaining statements are explained separately. See CLI Explorer. | [] | Configure—To enter configuration mode.
Control—To modify any configuration. | Statement introduced in Junos OS Release 9.5. | [
"ITU-T Y.1731 Ethernet Service OAM Overview",
"Configuring Ethernet Frame Delay Measurement Sessions"
] |
periodic (Chassis) | periodic {
ch-power-check-interval seconds;
no-sib-asic-stats;
one-sib-per-check;
re-check-interval seconds;
slow-fpc-check;
yield-cpu;
} | [edit chassis] | Chassisd periodic options | [
{
"name": "ch-power-check-interval",
"desc": "Chassis power check interval, 0=default (seconds) Default: 0 Range: 0 through 60"
},
{
"name": "no-sib-asic-stats",
"desc": "Disable asic statis for all SIBs in periodic"
},
{
"name": "one-sib-per-check",
"desc": "Check one SIB per peri... | [none specified] | Statement introduced in Junos OS Release 16.2R1. | [] |
periodic (Interfaces) | periodic (fast | slow); | [edit interfaces interface-name redundant-ether-options lacp] | For redundant Ethernet interfaces in a chassis cluster only, configure the interval at which the interfaces
on the remote side of the link transmit link aggregation control protocol data units (PDUs) by configuring
the periodic statement on the interfaces on the local side. It is the configuration on the local side tha... | [
{
"name": "fast",
"desc": "Transmit link aggregation control PDUs every second."
},
{
"name": "slow",
"desc": "Transmit link aggregation control PDUs every 30 seconds."
}
] | 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. | [
"Understanding Ethernet Interfaces"
] |
periodic | periodic (fast | slow); | [edit interfaces aex aggregated-ether-options lacp],
[edit interfaces interface-range name aggregated-ether-options lacp] | For aggregated Ethernet interfaces only, configure the interval for periodic transmission of LACP
packets. | [
{
"name": "fast",
"desc": "Transmit packets every second."
},
{
"name": "slow",
"desc": "Transmit packets every 30 seconds."
}
] | 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 LACP for Aggregated Ethernet Interfaces",
"Configuring Aggregated Ethernet LACP (CLI Procedure)",
"Example: Configuring Aggregated Ethernet High-Speed Uplinks Between an EX4200 Virtual Chassis",
"Access Switch and an EX4200 Virtual Chassis Distribution Switch",
"Configuring Aggregated Ethernet ... |
periodic-traceroute | periodic-traceroute {
disable;
exp exp-value;
fanout fanout-value;
frequency minutes;
paths number-of-paths;
retries retry-attempts;
source address;
ttl ttl-value;
wait seconds;
} | [edit logical-systems logical-system-name protocols ldp oam],
[edit logical-systems logical-system-name protocols ldp oam fec fec-address],
[edit protocols ldp oam],
[edit protocols ldp oam fec fec-address] | Enable tracing of forwarding equivalence classes (FECs) for LDP LSPs. | [
{
"name": "disable",
"desc": "(Optional) Disable tracing for a specific FEC. This option is available at the [edit protocols ldp oam"
},
{
"name": "exp exp-value",
"desc": "(Optional) Specify the class of service to use when sending probes."
},
{
"name": "fanout fanout-value",
"desc"... | 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 added at the [edit protocols ldp oam] and [edit logical-systems logical-system-name protocols ldp oam]
hierarchy levels in Junos OS Release 9.0. | [
"Configuring LDP LSP Traceroute"
] |
permit (Security Persistent NAT) | permit ( any-remote-host | target-host | target-host-port ); | [edit security nat source rule-set ruleset rule rule then source-nat interface persistent-nat]
[edit security nat source rule-set ruleset rule rule then source-nat pool persistent-nat] | Configure persistent NAT mappings. | [
{
"name": "any-remote-host",
"desc": "All requests from a specific internal IP address and port are mapped to the same"
},
{
"name": "target-host",
"desc": "All requests from a specific internal IP address and port are mapped to the same reflexive"
},
{
"name": "target-host-port",
"d... | 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. | [] |
permit (Security Policies) | permit {
advanced-connection-tracking;
application-services (Security Policies) {
application-firewall {
rule-set rule-set-name;
}
application-traffic-control {
rule-set rule-set-name;
}
gprs-gtp-profile profile-name;
gprs-sctp-profile prof... | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then] | Specify the policy action to perform when packets match the defined criteria. | [] | 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 tcp-options added in Junos OS Release
10.4. Support for the services-offload option added in Junos OS Release 11.4. Support for the ssl-
termination-profile and web-redirect-to-https options added in Junos OS Release 12.1X44-D10. Support for
the user-firewal... | [] |
permit (Security SCTP) | permit {
payload-protocol name;
} | [edit security sctp profile profile-name] | Use the permit option to display information about the configuration of the current Stream Control
Transmission Protocol (SCTP) inspection.
From Junos OS Release 20.4R1 onwards, the [edit security gprs sctp profile profile-name] hierarchy level
is replaced by [edit security sctp profile profile-name]. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [
"Understanding Stream Control Transmission Protocol",
"Example: Configuring a GPRS SCTP Profile for Policy-Based Inspection to Reduce Security Risks"
] |
permit-command | permit-command protocol-command-list; | [edit security utm default-configuration]
[edit security utm feature-profile content-filtering profile profile-name] | Apply protocol permit command custom-objects to the content-filtering 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. | [
"Content Filtering Overview"
] |
perpetual-poe | perpetual-poe; | [edit poe] | Configure perpetual power over Ethernet (PoE) to prevent interruptions to power during a reboot of the
power sourcing equipment (PSE). The PSE is a switch that provides PoE to connected powered devices. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.1R1. | [
"Perpetual PoE and Fast PoE"
] |
persistent-learning | persistent-learning; | For platforms without ELS:
[edit ethernet-switching-options secure-access-port interface (all | interface-name)]
For platforms with ELS:
[edit switch-options interface interface-name] | Specify that learned MAC addresses persist on the specified interfaces across restarts of the switch and
link-down conditions. This feature is also known as sticky MAC. | [] | system—To view this statement in the configuration.
system–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
Hierarchy level [edit switch-options interface interface-name] introduced in Junos OS Release 13.2X50-
D10 | [
"Example: Configuring Port Security (non-ELS)",
"Configuring Persistent MAC Learning (non-ELS)",
"Configuring Persistent MAC Learning (ELS)"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.