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 |
|---|---|---|---|---|---|---|---|
port_list | port-list port-list-name | [edit firewall port-list port-list-name] | You create a port-list to conveniently group together multiple ports (source ports or destination ports)
so that they can be referenced easily in firewall configurations as port-list, source-port-list and/or
destination-port-list match conditions. You can create a port list and associate a port number with this
port li... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1 | [] |
port-mapping | port-mapping {
disable;
port-range {
tcp [ ports-and-port-ranges ];
udp [ ports-and-port-ranges ];
}
} | [edit services application-identification application application-name] | Define port-mapping properties for application identification.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Defining an Application Identification"
] |
port-mirroring | [edit forwarding-options] | 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... | [] | 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 before Junos OS Release 7.4.
family vpls statement introduced in Junos OS Release 9.3.
instance instance-name statement introduced in Junos OS Release 9.3 .
mirror-once statement introduced in Junos OS Release 9.3 .
family ccc statement introduced in Junos OS Release 9.6.
family inet6 and next-hop-... | [
"Configuring Port Mirroring",
"Configuring Port Mirroring",
"Configuring Active Flow Monitoring on PTX Series Packet Transport Routers",
"Understanding Port Mirroring and Analyzers",
"Understanding Port Mirroring",
"Examples: Configuring Port Mirroring for Local Analysis",
"Example: Mirroring Employee W... | |
port-mode (Fibre Channel Interfaces) | port-mode (f-port | np-port); | [edit interfaces vlan unit unit family fibre-channel],
[edit interfaces interface-name unit logical-unit-number family fibre-channel] | Configure the FCoE VLAN interface port mode to F_Port to connect the switch to FCoE initiators, or
configure the native FC interface port mode to proxy N_Port (NP_Port) to connect the switch to an FC
switch fabric port (F_Port). | [
{
"name": "f-port",
"desc": "Configure an FCoE VLAN interface to connect to FCoE initiator Virtual N_Ports (VN_Ports)."
},
{
"name": "np-port",
"desc": "Configure a native FC port to connect to an FC switch F_Port."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Example: Setting Up Fibre Channel and FCoE VLAN Interfaces in an FCoE-FC Gateway Fabric",
"Configuring an FCoE VLAN Interface on an FCoE-FC Gateway",
"Converting an Ethernet Interface To a Fibre Channel Interface",
"Understanding Interfaces on an FCoE-FC Gateway"
] |
port-mode | port-mode (access | tagged-access | trunk); | [edit interfaces interface-name unit logical-unit-number family ethernet-switching] | NOTE: This statement does not support the Enhanced Layer 2 Software (ELS)
configuration style. If your switch runs software that supports ELS, see "interface-mode"
on page 9438. For ELS details, see Using the Enhanced Layer 2 Software CLI.
Configure whether an interface on the switch operates in access, tagged access, ... | [
{
"name": "access",
"desc": "Have the interface operate in access mode. In this mode, the interface can be in a single VLAN"
},
{
"name": "tagged-access",
"desc": "Have the interface operate in tagged-access mode. In this mode, the interface can be in"
},
{
"name": "trunk",
"desc": "... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Example: Connecting an EX Series Access Switch to a Distribution Switch",
"Configuring Gigabit Ethernet Interfaces (CLI Procedure)",
"Configuring VLANs for EX Series Switches",
"Junos OS Ethernet Interfaces Configuration Guide"
] |
port-overloading (Security Source NAT Interface) | port-overloading off | [edit security nat source interface] | Enable interface NAT with or without port overloading. | [
{
"name": "off",
"desc": "Specify off to disable interface port overloading. NOTE: The port-overloading option should not be used in conjunction with the port-overloading-factor option because they can override each other. For example, if port- overloading has been set to off to disable interface port overl... | 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. | [] |
port-overloading-factor (Security Source NAT Interface) | port-overloading-factor number; | [edit security nat source interface] | Configure the port overloading capacity for the source NAT interface. If port-overloading-factor is set to
x(1 up to the maximum port capacity), then x times the maximum port capacity is allocated for interface-
based NAT.
NOTE: There is also a port-overloading option, but it is not supported for logical systems,
and s... | [
{
"name": "number",
"desc": "A number ranging from 1 through the maximum port capacity. For example, if port-overloading-factor is set to 2, and it is multiplied by a maximum port capacity of 63,486, the port overloading threshold is 126,972. If the configured port-overloading-factor setting exceeds the max... | 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. | [] |
port-overloading-factor (Security Source NAT Pool) | port-overloading-factor | [edit security nat source pool source-pool-name port] | Configures the port overloading capacity in source NAT. If the port-overloading-factor is set to x, each
translated IP address will have x number of ports available.
NOTE: The port-overloading-factor statement cannot be configured with port no-
translation (source NAT pool without PAT). | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2 | [] |
port-priority | port-priority priority; | [edit interfaces interface-name gigether-options 802.3ad lacp] | Define LACP port priority at the interface level. | [
{
"name": "priority",
"desc": "Priority for being elected to be the active port and both collect and distribute traffic. A smaller"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Configuring LACP Link Protection of Aggregated Ethernet Interfaces for Switches",
"Configuring Aggregated Ethernet LACP (CLI Procedure)"
] |
port-randomization | port-randomization disable; | [edit security nat source] | Disable random port allocation for pool-based and interface source NAT. | [
{
"name": "disable",
"desc": "Disables random port allocation for pool-based and interface source NAT. For pool-based"
}
] | 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. | [] |
port-range (Address Mapping) | port-range {
tcp [port];
udp [port];
} | []
edit services application-identification application application-name address-mapping address-name filter | Specify a port to match a TCP or UDP destination port for Layer 3 and Layer 4 address-based custom
applications.
.
Layer 3 and Layer 4 address-based custom applications, you can match the IP address and port range to
destination IP address and port. When both IP address and port are configured, both should match
destin... | [
{
"name": "tcp [port]",
"desc": "Define the TCP port range for the application."
},
{
"name": "udp [port]",
"desc": "Define the UDP port range for the application."
}
] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D40. | [
"Understanding Junos OS Application Identification Custom Application Signatures"
] |
port-range (Application Identification) | port-range {
tcp [port-range];
udp [port-range];
} | [edit services application-identification application application-name over protocol-type
signature l4-l7-signature-name] | Define TCP or UDP port number range. | [
{
"name": "port-range",
"desc": "Numeric port ranges. The format for numeric port ranges is in the format minimum-value– maximum-value."
}
] | view-level—To view this statement in the configuration.
control-level—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"
] |
port-range | port-range {
tcp [ ports-and-port-ranges ];
udp [ ports-and-port-ranges ];
} | [edit services application-identification application application-name port-mapping],
[edit services application-identification rule rule-name address destination],
[edit services application-identification rule rule-name address source] | Define TCP and UDP port numbers or numeric ranges. For port-mapping configurations, this entry is
required if the parent node exists. | [
{
"name": "ports-and-port-ranges",
"desc": "Individual port numbers, numeric port ranges, or both. Separate the values with"
}
] | 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. | [
"Defining an Application Identification",
"Configuring APPID Rules"
] |
port-range | port-range port-range-low port-range-high; | [edit chassis fpc fpc-id pic pic-id fibre-channel] | Configure a contiguous block of ports as FC ports. You can configure the FC-capable ports xe-0/0/0
through xe-0/0/5 as fc-0/0/0 through fc-0/0/5, and ports xe-0/0/42 through xe-0/0/47 as fc-0/0/42
through fc-0/0/47 to create blocks of native FC interfaces. You cannot individually configure a single
port as a native FC ... | [
{
"name": "port-range-low",
"desc": "Lowest-numbered port in the block of native FC interfaces, either 0 or 42."
},
{
"name": "port-range-high",
"desc": "Highest-numbered port in the block of native FC interfaces. The value is 5 if the port-range-low value is 0. The value is 47 if the port-range... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Example: Setting Up Fibre Channel and FCoE VLAN Interfaces in an FCoE-FC Gateway Fabric",
"Configuring a Physical Fibre Channel Interface",
"Understanding Interfaces on an FCoE-FC Gateway"
] |
port-round-robin (Source NAT Next Gen Services) | port-round-robin {
disable;
} | [edit services nat source] | Disable round-robin port allocation for any NAT pools that do not specify an automatic (random-allocation |
round-robin) setting at the [edit services nat source pool nat-pool-name port] hierarchy level. The automatic
(random-allocation | round-robin) setting for a pool overrides the port-round-robin disable setting. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [] |
port-round-robin | port-round-robin disable; | [edit security nat source] | Disable round-robin port allocation for pool-based and interface source NAT on SRX5400, SRX5600,
and SRX5800 devices. | [
{
"name": "disable",
"desc": "Disables round-robin port allocation for pool-based and interface source NAT."
}
] | 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-D30. | [] |
port-scaling-enlargement | port-scaling-enlargement; | [edit security nat source] | Increase the source NAT port capacity on SRX5400, SRX5600, and SRX5800 devices with next-
generation Services Processing Cards (SPCs). | [] | 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-D60. | [] |
port-scan | port-scan {
threshold number;
} | [edit security screen ids-option screen-name tcp]
[edit security screen ids-option screen-name udp] | Prevent port scan attacks. A port scan attack occurs when an attacker sends packets with different port
numbers to scan available services. The attack succeeds if a port responds. To prevent this attack, the
device internally logs the number of different ports scanned from a single remote source. For example, if
a rem... | [
{
"name": "threshold number",
"desc": "Number of microseconds during which the device accepts packets from the same"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
port-status-tlv | port-status-tlv blocked; | [edit protocols oam ethernet connectivity-fault-management action-profile tlv-action event]
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name continuity-check] | Define an action-profile consisting of various events and the action. Based on values of port-status-tlv in
the received CCM packets, specific action such as interface-down can be taken using "action-profile" on
page 1943 options. | [
{
"name": "blocked",
"desc": "When the incoming CCM packet contains port status TLV with value blocked, the action will be triggered for this action-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.6. | [
"CFM Monitoring between CE and PE Devices"
] |
ports (System) | ports {
auxiliary {
disable;
insecure;
type terminal-type;
port-type (mini-usb | rj45);
}
console {
disable;
insecure;
log-out-on-disconnect;
type terminal-type;
}
} | [edit system] | Configure the properties of the console and auxiliary ports.
The ports are located on the device’s craft interface. See the device’s hardware documentation for port
locations. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Junos OS to Set Console and Auxiliary Port Properties"
] |
ports-per-session | ports-per-session ports; | [edit services nat pool nat-pool-name pgcp] | Configure the number of ports required to support Real-Time Transport Protocol (RTP), Real-Time
Control Protocol (RTCP), Real-Time Streaming Protocol (RTSP), and forward error correction (FEC) for
voice and video flows on the Multiservices PIC. | [
{
"name": "number-of-ports",
"desc": "Number of ports to enable: 2 or 4 for combined voice and video services."
}
] | interface—To view this statement in the configuration.
interface–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [] |
post-attack | post-attack number; | [edit security idp idp-policy policy-name rulebase-ips rule rule-name then notification packet-
log] | Specify the number of packets received after an attack that should be captured for further analysis of
attacker behavior. If post-attack packets are not significant to your analysis or the configured attack
response ends packet transfer, you can set the post-attack option to 0. | [
{
"name": "number",
"desc": "Number of post-attack packets to be captured."
}
] | 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. | [] |
post-attack-timeout | post-attack-timeout seconds; | [edit security idp idp-policy policy-name rulebase-ips rule rule-name then notification packet-
log] | Specify a time limit for capturing post-attack packets for a session. No packet capture is conducted after
the timeout has expired. | [
{
"name": "seconds",
"desc": "Maximum number of seconds for post-attack packet capture."
}
] | 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. | [] |
post-cli-implicit-firewall | post-cli-implicit-firewall; | [edit services rpm twamp] | Ensure that the CLI configured (explicit firewall) takes precedence over the implicit firewall. The inline
TWAMP client or server uses implicit firewall to achieve its functionality.
NOTE: Wrong configuration of CLI firewall can lead to improper functioning of inline
TWAMP client or server. After you enable or disable ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
post-convergence-lfa (Protocols OSPF) | post-convergence-lfa <fate-sharing-protection fate-sharing-protection<node-protection <cost
cost> <srlg-protection>; | [edit logical-systems name protocols ospf area interface interface-name ],
[edit logical-systems name routing-instances name protocols ospf area interface interface-name],
[edit protocols ospf area interface interface-name ],
[edit routing-instances name protocols ospf area interface interface-name] | Configure the installation of backup-paths that follow the post-convergence paths corresponding to the
failure of this interface. | [
{
"name": "fate-sharing-",
"desc": ""
},
{
"name": "protection",
"desc": "Enable fate-sharing protection. A list of fate-sharing groups are configured on each point of local repair (PLR) with the links in each fate-sharing group identified by their respective IP addresses. The PLR associates a c... | routing | Statement introduced in Junos OS Release 18.2R1 for MX Series, PTX Series, and QFX Series.
fate-sharing-protection option introduced in Junos OS release 20.3R1 for MX Series and PTX Series.
srlg-protection option introduced in Junos OS release 20.3R1 for MX Series and PTX Series. | [
"Topology-Independent Loop-Free Alternate with Segment Routing for OSPF"
] |
post-convergence-lfa | post-convergence-lfa <fate-sharing-protection fate-sharing-protection> <node-protection <cost
cost> <srlg-protection>; | [edit logical-systems name protocols isis interface name level number],
[edit logical-systems name routing-instances name protocols isis interface name level number],
[edit protocols isis interface name level number ],
[edit routing-instances name protocols isis interface name level number] | Configure backup paths along post-convergence on this interface. | [
{
"name": "fate-sharing-",
"desc": ""
},
{
"name": "protection",
"desc": "Enable fate-sharing protection. A list of fate-sharing groups are configured on each point of local repair (PLR) with the links in each fate-sharing group identified by their respective IP addresses. The PLR associates a c... | routing | Statement introduced in Junos OS Release 17.4R1.
srlg-protection option introduced in Junos OS release 20.2R1 for MX Series and PTX Series. | [
"Understanding Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS",
"Configuring Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS"
] |
post-policy | post-policy {
exclude-non-eligible;
} | [edit protocols bgp bmp route-monitoring],
[edit protocols bgp group group-name bmp route-monitoring],
[edit protocols bgp group neighbor group-name neighbor address bmp route-monitoring],
[edit routing-options bmp route-monitoring],
[edit routing-options bmp station station-name route-monitoring] | For BMP route monitoring, allows you to excludes routes that are non-eligible for the decision process
(for example, protocol nexthop not resolved). This represents the view of the BGP routes after running
the import policy. If the import policy has rejected the BGP route, the route does not exist in the post
policy vi... | [
{
"name": "exclude-non-eligible",
"desc": "Exclude routes that are non-eligible for the decision process."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51-D15 for the QFX Series.
Statement introduced in Junos OS Release 13.3.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series. | [
"BGP Monitoring Protocol"
] |
post-service-filter (Dynamic Service Sets) | post-service-filter filter-name; | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family service input],
[edit dynamic-profiles profile-name interfaces pp0 unit $junos–interface–unit family family service
input] | Define the filter to be applied to traffic after service processing. The filter is applied only if a service set
is configured and selected. You can configure a post-service filter on the input side of the interface only. | [
{
"name": "filter-name",
"desc": "Identifier for the post-service filter."
}
] | 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 pp0 unit “$junos-interface-unit” family family
service input] hierarchy level introduced in Junos OS Release 10.1. | [
"Dynamic Service Sets Overview",
"Associating Service Sets with Interfaces in a Dynamic Profile"
] |
post-service-filter | post-service-filter filter-name; | [edit interfaces interface-name unit logical-unit-number family inet service input],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet service input] | Define the filter to be applied to traffic after service processing. The filter is applied only if a service set
is configured and selected. You can configure a postservice filter on the input side of the interface only.
The post-service-filter statement is not supported when the service interface is on an MS-MIC or MS... | [
{
"name": "filter-name",
"desc": "Identifier for the post-service filter."
}
] | 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 Filters and Services to Interfaces"
] |
potential-violation | potential-violation {
authentication failures;
cryptographic-self-test;
decryption-failures {
threshold value;
}
encryption-failures {
threshold value;
}
idp;
ike-phase1-failures {
threshold value;
}
ike-phase2-failures {
threshold value;
}
... | [edit security alarms] | Configure alarms for potential violation. | [
{
"name": "authentication",
"desc": "Raise a security alarm when the device or switch detects a specified number of authentication failures (bad password attempts) before an alarm is raised."
},
{
"name": "cryptographic-self-test",
"desc": "Raise a security alarm when the device or switch detect... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [] |
power | power (off | on); | [edit chassis fpc slot-number]
[edit chassis fpc slot pic],
[edit chassis lcc name fpc name pic slot],
[edit chassis member name fpc slot pic],
[edit chassis fpc slot slc slc-id]
[edit chassis feb slot slot-number]
[edit chassis sib slot slot-number] | Turn a Flexible PIC Concentrator (FPC), a Physical Interface Card (PIC) in the specified FPC, a sub line
card (SLC), a Forwarding Engine Board (FEB), or a Switch Interface Board (SIB) on or off.
The power (off | on) command at the edit chassis fpc slot-number hierarchy configures the Flexible PIC
Concentrator (FPC) to ... | [
{
"name": "off",
"desc": "Take the FPC (or a PIC in the specified FPC), or SLC offline, and configure it to stay offline, as, for"
},
{
"name": "on",
"desc": "Bring the FPC (or a PIC in the specified FPC) online, and configure it to come online automatically,"
},
{
"name": "slc slc-id",
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | The edit chassis fpc slot-number power (off | on) statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.4.
The edit chassis fpc slot-number pic pic-number power off introduced in Junos OS Release 13.3R2.
The edit chassis fpc slot-number pfe slot-number power (off | on) statement i... | [
"Managing Power",
"Removing a Line Card from an EX6200 Switch",
"EX8208 Switch Hardware and CLI Terminology Mapping",
"EX8216 Switch Hardware and CLI Terminology Mapping",
"EX6210 Switch Hardware and CLI Terminology Mapping"
] |
power-budget-priority | power-budget-priority priority; | [edit chassis fpc slot] | Assign a power priority to the specified line card slot on an EX6200 or EX8200 switch.
NOTE: On an EX6200 switch, you cannot change the power priority of a slot containing
a Switch Fabric and Routing Engine (SRE) module. Although the CLI allows you to set a
different power priority for the slot, your change does not go... | [
{
"name": "priority",
"desc": "Assigned power priority for the slot, with 0 being the highest priority:"
},
{
"name": "0 through 9 for an EX6200 switch",
"desc": ""
},
{
"name": "0 through 7 for an EX8208 switch",
"desc": ""
},
{
"name": "0 through 15 for an EX8216 switch",
... | 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 the Power Priority of Line Cards (CLI Procedure)"
] |
power-mode-disable | power-mode-disable; | [edit security flow] | PowerMode is enabled by default. To disable the feature, use power-mode-disable statement at the [edit
security flow] hierarchy level. | [] | security | Statement introduced in Junos OS Release 21.3R1. | [
"PowerMode"
] |
power-mode-ipsec | power-mode-ipsec; | [edit security flow (Security Flow)] | Enable PowerMode IPsec. processing. PMI is a new mode of operation that provides IPsec performance
improvements.
For SRX4100, SRX4200 devices running Junos OS Release 18.4R1, SRX4600 devices running Junos OS
Release 20.4R1, and vSRX Virtual Firewall instances running Junos OS Release 18.3R1, you can enable
or disable t... | [] | flow-tap | Statement introduced in Junos OS Release 18.3R1. | [
"Improving IPsec Performance with PowerMode IPsec"
] |
power-mode-ipsec-qat | power-mode-ipsec-qat; | [edit security flow] | Enable QuickAssist (QAT) for encryption of cryptographic operation.
PowerMode IPsec (PMI) uses AES-NI and QAT for encryption and FPGA for decryption of cryptographic
operation to enhance IPSec VPN performance.
PMI with QAT is supported on SRX5400, SRX5600, and SRX5800 with SPC3 cards. | [] | flow-tap | Statement introduced in Junos OS Release 20.4R1. | [
"Improving IPsec Performance with PowerMode IPsec",
"application-services (Security Forwarding Process)",
"show security flow status"
] |
pp0 (Dynamic PPPoE) | pp0 {
unit logical-unit-number {
actual-transit-statistics;
keepalives interval seconds;
no-keepalives;
pppoe-options {
underlying-interface interface-name;
server;
}
ppp-options {
aaa-options aaa-options-name;
authentic... | [edit dynamic-profiles profile-name interfaces] | Configure the dynamic PPPoE logical interface in a dynamic profile. When the router creates a dynamic
PPPoE logical interface on an underlying Ethernet interface configured with PPPoE (ppp-over-ether)
encapsulation, it uses the information in the dynamic profile to determine the properties of the dynamic
PPPoE logical ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Configuring a PPPoE Dynamic Profile",
"Configuring Dynamic Authentication for PPP Subscribers",
"Configuring PPPoE"
] |
ppm (Ethernet Switching) | ppm {
centralized | distributed | inline;
} | [edit protocols lacp] | Configure PPM processing options for Link Aggregation Control Protocol (LACP) packets.
This command configures the PPM processing options for LACP packets only. You can disable
distributed PPM processing for all packets that use PPM and run all PPM processing on the Routing
Engine by configuring the no-delegate-proces... | [
{
"name": "distributed",
"desc": "Specifies distributed non-inline PPM processing."
},
{
"name": "inline",
"desc": "Specifies distributed inline PPM processing."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Configuring Distributed Periodic Packet Management on an EX Series Switch (CLI Procedure)",
"Configuring Distributed Periodic Packet Management"
] |
ppm | ppm {
no-delegate-processing;
inline-processing-enable;
} | [edit routing-options] | Disable distributed periodic packet management (PPM) to the Packet Forwarding Engine (on routers), to
access ports (on EX3200 and EX4200 switches, and QFX Series), or to line cards (on EX6200 and
EX8200 switches).
After you disable PPM, PPM processing continues to run on the Routing Engine.
In Junos OS Release 8.2, PPM... | [
{
"name": "no-delegate-processing",
"desc": "Disable PPM to the Packet Forwarding Engine, access ports, or line cards. Distributed PPM is enabled by default."
},
{
"name": "redistribution-timer",
"desc": "Ensures that link aggregation and spanning tree protocols work seamlessly on chassis or vir... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
inline-processing-enable option introduced in Junos OS Release 19.4R1. | [
"Ensuring That Distributed ppm Is Not Disabled"
] |
ppp (Group Profile) | ppp {
cell-overhead;
encapsulation-overhead bytes;
framed-pool framed-pool;
idle-timeout seconds;
interface-id interface-id;
keepalive seconds;
ppp-options {
aaa-options aaa-options-name;
chap;
ignore-magic-number-mismatch;
initiate-ncp (ip | ipv6 | dual-stack... | [edit access group-profile profile-name] | Configure PPP properties for a group profile. | [
{
"name": "cell-overhead",
"desc": "Configure the session to use Asynchronous Transfer Mode (ATM)-aware egress shaping on the IQ2 PIC."
},
{
"name": "encapsulation-overhead",
"desc": "Configure the encapsulation overhead for class-of-service calculations."
},
{
"name": "Values: bytes",
... | 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. | [
"Point-to-Point Protocol (PPP)",
"L2TP LNS Inline Service Interfaces"
] |
ppp (Profile) | ppp {
cell-overhead;
encapsulation-overhead bytes;
framed-ip-address address;
framed-pool framed-pool;
idle-timeout seconds;
interface-id interface-id;
keepalive seconds;
primary-dns primary-dns;
primary-wins primary-wins;
secondary-dns secondary-dns;
secondary-wins secondar... | [edit access profile profile-name client client-name] | Configure PPP properties for a client profile. | [
{
"name": "framed-ip-address",
"desc": "(SRX Series, T Series only) Specify a framed IP address."
},
{
"name": "Values: address",
"desc": "The IP version 4 (IPv4) prefix."
}
] | 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.
Statement idle-timeout introduced in Junos OS Release 11.1 for the QFX Series.
Statement idle-timeout introduced in Junos OS Release 14.1X53-D20 for OCX Series switches. | [
"Point-to-Point Protocol (PPP)"
] |
ppp | ppp {
aggregate {
bandwidth packets per second;
burst packets;
disable-fpc;
disable-logging;
disable-routing-engine;
fpc name {
bandwidth-scale percent;
burst-scale percent;
disable-fpc;
}
recover-time seconds;
}
authentication {
bandwidth packets per second;... | [edit system ddos-protection protocols] | Configure PPP control traffic. | [
{
"name": "> aggregate",
"desc": "Configure aggregate for all PPP control traffic"
},
{
"name": "+ apply-groups",
"desc": "Groups from which to inherit configuration data"
},
{
"name": "+ apply-groups-except",
"desc": "Don't inherit configuration data from these groups"
},
{
... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos Evolved OS Release 23.4R1. | [] |
ppp-access-profile | ppp-access-profile profile-name; | [edit services l2tp tunnel-group name] | Specify the profile used to validate all Point-to-Point Protocol (PPP) session requests through L2TP
tunnels established to the local gateway address.
NOTE: This statement is not supported for L2TP LNS on MX Series routers. | [
{
"name": "profile-name",
"desc": "Identifier for the PPP profile."
}
] | 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 Access Profiles for L2TP Tunnel Groups"
] |
ppp-options (Dynamic PPP) | ppp-options {
aaa-options aaa-options-name;
authentication [ authentication-protocols ];
chap {
challenge-length minimum minimum-length maximum maximum-length;
local-name name;
}
ignore-magic-number-mismatch;
initiate-ncp (dual-stack-passive | ipv6 | ip)
ipcp-suggest-dns-opti... | [edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit],
[edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit] | Configure PPP-specific interface properties in a dynamic profile.
NOTE: PPP options can also be configured in a group profile with the ppp-options (L2TP)
statement. The following behavior determines the interaction between the PPP options
configured in a group profile and the PPP options configured in a dynamic profile... | [
{
"name": "lcp-connection-",
"desc": ""
},
{
"name": "update",
"desc": "Enable PPP to act on a Connection-Status-Message VSA (26–218) received by authd in either a RADIUS Access-Accept message or a CoA message. PPP conveys the contents of the VSA in an LCP Connection-Update-Request message to th... | 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”] hierarchy level introduced in Junos OS Release 12.2.
lcp-connection-update option added in Junos OS Release 20.2R1. | [
"Dynamic Profiles Overview",
"Configuring a PPPoE Dynamic Profile",
"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",
"How to Configure RADIUS-Sourced C... |
ppp-options (L2TP) | ppp-options {
aaa-options aaa-options-name;
chap;
ignore-magic-number-mismatch;
initiate-ncp (ip | ipv6 | dual-stack-passive)
ipcp-suggest-dns-option;
mru;
mtu;
pap;
peer-ip-address-optional;
} | [edit access group-profile profile-name ppp] | Configure PPP-specific properties in a group profile that applies to tunneled PPP subscribers at the LNS.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details.
NOTE: PPP options can also be configured for an inline servic... | [] | 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.
mtu statement introduced in Junos OS Release 14.2 | [
"Configuring the PPP Attributes for a Group Profile",
"L2TP LNS Inline Service Interfaces"
] |
ppp-options | ppp-options {
authentication [ authentication-protocols ];
mru size;
mtu (size | use-lower-layer);
chap {
access-profile name;
challenge-length minimum minimum-length maximum maximum-length;
default-chap-secret name;
local-name name;
passive;
}
compres... | [edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | On interfaces with PPP encapsulation, configure PPP-specific interface properties.
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 types:
•
atm-ppp-llc—PPP over AAL5 LLC encapsulation.
•
atm-ppp... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the PPP Challenge Handshake Authentication Protocol",
"Applying PPP Attributes to L2TP LNS Subscribers per Inline Service Interface"
] |
ppp-over-ether | ppp-over-ether; | [edit interfaces interface-name unit logical-unit-number encapsulation] | This encapsulation is used for underlying interfaces of pp0 interfaces. This encapsulation is supported
on Fast Ethernet interface, Gigabit Ethernet interface, and Redundant Ethernet interface. When
Redundant Ethernet interface is used as underlying interface, an existing pppoe session can be
continued in case of failo... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 11.2.
This encapsulation is supported for Redundant Ethernet interface in Junos OS Release 11.2. | [
"Understanding Ethernet Interfaces"
] |
ppp-subscriber-services | ppp-subscriber-services (disable | enable); | [edit chassis] | Enable dynamic PPP subscriber services on non-PPPoE interfaces on certain PICs.
NOTE: When you include this statement, the relevant PICs restart. This action disrupts
subscribers already logged in through those PICs. You can confirm completion of the
restart by issuing the show chassis pic fpc-slot slot-number pic-slo... | [
{
"name": "disable",
"desc": "Disable subscriber services."
},
{
"name": "enable",
"desc": "Enable subscriber services."
}
] | 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. | [
"Attaching Dynamic Profiles to MLPPP Bundles",
"Hardware Requirements for PPP Subscriber Services on Non-Ethernet Interfaces"
] |
pppoe (DDoS Protection) | pppoe {
aggregate {
bandwidth packets per second;
burst packets;
disable-fpc;
disable-logging;
disable-routing-engine;
fpc name {
bandwidth-scale percent;
burst-scale percent;
disable-fpc;
}
recover-time seconds;
}
padi {
bandwidth packets per second;
bur... | [edit system ddos-protection protocols] | Configure PPPoE control traffic. | [
{
"name": "> aggregate",
"desc": "Configure aggregate for all PPPoE control traffic"
},
{
"name": "+ apply-groups",
"desc": "Groups from which to inherit configuration data"
},
{
"name": "+ apply-groups-except",
"desc": "Don't inherit configuration data from these groups"
},
{
... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos Evolved OS Release 23.4R1. | [] |
pppoe (System Processes) | pppoe {
command binary-file-path;
disable;
failover (alternate-media | other-routing-engine);
} | [edit system processes] | Enable users to connect to a network of hosts over a bridge or access concentrator. | [
{
"name": "command binary-file-path",
"desc": "Path to the binary process."
},
{
"name": "disable",
"desc": "Disable the Point-to-Point Protocol over Ethernet process."
},
{
"name": "failover",
"desc": "Configure the device to reboot if the software process fails four times within 30... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Understanding Ethernet Interfaces"
] |
pppoe-options (Dynamic PPPoE) | pppoe-options {
underlying-interface interface-name;
server;
} | [edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit] | Configure the underlying interface and PPPoE server mode for a dynamic PPPoE logical interface in a
dynamic profile.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Configuring a PPPoE Dynamic Profile",
"Configuring Dynamic PPPoE Subscriber Interfaces"
] |
pppoe-options (SRX Series) | pppoe-options {
access-concentrator name ;
auto-reconnect seconds;
(client | server);
ignore-eol-tag;
service-name name;
underlying-interface interface-name;
} | [edit interfaces pp0 unit logical-unit-number],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number] | Configure PPP over Ethernet-specific interface properties. | [
{
"name": "access-concentrator name",
"desc": "(SRX Series devices with Point-to-Point Protocol over Ethernet (PPPoE) interfaces) Configure the name of the access concentrator. If you configure a specific access concentrator name on the client and the same access concentrator name server is available, then ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement modified in Junos OS Release 12.3X48 to include ignore-eol-tag statement. | [
"Example: Configuring PPPoE Interfaces"
] |
pppoe-options | pppoe-options {
access-concentrator name;
auto-reconnect seconds;
(client | server);
service-name name;
underlying-interface interface-name;
ppp-max-payload ppp-max-payload
} | [edit interfaces pp0 unit logical-unit-number],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number],
[edit interface ppp interface unit logical-unit-number ppp-max-payload ppp-max-payload] | Configure PPP over Ethernet-specific interface properties.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details.
The maximum payload allowed on an Ethernet frame is 1500 bytes. For a PPPoE interface, the PPPoE
header use... | [] | 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.
client Statement introduced in Junos OS Release 8.5.
server Statement introduced in Junos OS Release 8.5.
ppp-max-payload Statement introduced in Junos OS Release 15.1X49-D100. | [
"Configuring a PPPoE Interface"
] |
pppoe-tags (Adjustment Control Profiles) | pppoe-tags {
priority priority;
algorithm algorithm;
} | [edit class-of-service adjustment-control-profiles profile-name application] | Configure the shaping rate adjustment controls for the Point-to-Point Protocol over Ethernet (PPPoE)
Tags application. | [
{
"name": "priority",
"desc": "Priority of the Point to Point Protocol over Ethernet IA Tags application in the adjustment control profile. Range: 1 through 10; 1 being the highest priority. Default: 2"
},
{
"name": "algorithm",
"desc": "Rate adjustment algorithm used by the Point to Point Pro... | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1. | [
"CoS Adjustment Control Profiles Overview",
"Configuring CoS Adjustment Control Profiles",
"Verifying the CoS Adjustment Control Profile Configuration"
] |
pppoe-underlying-options (Dynamic VLAN Interface Sets) | pppoe-underlying-options {
max-sessions number;
} | [edit dynamic-profiles profile-name interfaces interface-set $junos-interface-set-name] | Configure PPPoE-specific interface properties in the dynamic profile that defines the agent circuit
identifier (ACI) interface set. An ACI interface set is a logical collection of subscriber interfaces that
originate at the same household or on the same access-loop port. Configuring PPPoE-specific interface
properties ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring Dynamic VLANs Based on Agent Circuit Identifier Information",
"Agent Circuit Identifier-Based Dynamic VLANs Overview"
] |
pppoe-underlying-options (Static and Dynamic Subscribers) | pppoe-underlying-options {
access-concentrator name;
dynamic-profile profile-name;
direct-connect
duplicate-protection;
max-sessions number;
max-sessions-vsa-ignore;
service-name-table table-name;
short-cycle-protection <lockout-time-min minimum-seconds> <lockout-time-max maximum-second... | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Configure PPPoE-specific interface properties for the underlying interface on which the router creates a
static or dynamic PPPoE logical interface. The underlying interface must be configured with PPPoE (ppp-
over-ether) encapsulation.
The remaining statements are explained separately. Search for a statement in CLI Exp... | [] | 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 PPPoE",
"Configuring an Underlying Interface for Dynamic PPPoE Subscriber Interfaces",
"Assigning a Service Name Table to a PPPoE Underlying Interface"
] |
pps-limit (Hierarchical Policer) | pps-limit pps; | [edit dynamic-profiles profile-name firewall hierarchical-policer hierarchical-policer-name aggregate
if-exceeding],
[edit dynamic-profiles profile-name firewall hierarchical-policer hierarchical-policer-name premium
if-exceeding],
[edit No Link Title hierarchical-policer hierarchical-policer-name aggregate if-excee... | Configure the maximum bandwidth in packets per second (pps) for premium or aggregate traffic in a
hierarchical policer.
Hierarchical policing is a form of two-color policing that applies different policing actions based on
whether the packets are classified for expedited forwarding (EF) or for a lower priority. You app... | [
{
"name": "pps",
"desc": "Specify the number of packets per second either as a decimal number or 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 Bandwidth and Burst-Size Limits",
"Policer Color-Marking and Actions",
"Single Token Bucket Algorithm",
"Determining Proper Burst Size for Traffic Policers"
] |
pps-limit (Policer) | pps-limit pps; | [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 firewallpolicer policer-name if-exceeding-pps] | For a single-rate two-color policer, configure the packets-per-second (pps) limit as a number of packets
per second. 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 cat... | [
{
"name": "pps",
"desc": "Specify the number of packets per second either as a decimal number or 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. | [
"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"
] |
pptp | pptp {
disable;
traceoptions {
flag {
all {
extensive
}
}
}
} | [edit logical-systems name security alg],
[edit logical-systems name tenants name security alg],
[edit security alg],
[edit services alg],
[edit tenants name security alg] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "disable",
"desc": "Disable the PPTP ALG. By default, the PPTP ALG is enabled."
},
{
"name": "traceoptions",
"desc": "Configure PPTP ALG tracing options."
},
{
"name": "flag",
"desc": "Trace operation to perform."
},
{
"name": "all",
"desc": "Trace all events."
... | 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.
The tenant option is introduced in Junos OS Release 18.3R1. | [
"Security Policies User Guide for Security Devices"
] |
prbs | (prbs | no-prbs); | [edit interfaces interface-name otn-options] | Specify whether OTN payload Pseudo-Random Binary Sequence (PBRS) is enabled or disabled.
Default
By default, OTN payload prbs is disabled. | [
{
"name": "prbs",
"desc": "Enable OTN payload PBRS."
},
{
"name": "no-prbs",
"desc": "Disable OTN payload PBRS."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
prbs-test-start | test interfaces ifd-name prbs-test-start pattern-type type direction 0/1 flip 0/1 | You can check the physical link connectivity by issuing this command that starts collecting the Pseudo
Random Binary Sequence (PRBS) statistics. The PRBS pattern generation and verification validates the
physical link connectivity in a routers. If the PRBS test passes with PRBS31 pattern type consistently, it
indicate... | [
{
"name": "ifd-name",
"desc": "Name of the interface."
},
{
"name": "type",
"desc": "Specifies the pattern type, that is in the range from 7 to 58."
},
{
"name": "PRBS7",
"desc": ""
},
{
"name": "PRBS9",
"desc": ""
},
{
"name": "PRBS11",
"desc": ""
},
{
... | view | Command introduced in Junos OS Release 19.2R1. | [
"Verifying Link and Transceivers using Pseudo Random Binary Sequence (PRBS) Test"
] | |
prbs-test-stop | test interfaces ifd-name prbs-test-stop direction (0|1) | Use this command to stop collecting the Pseudo Random Binary Sequence (PRBS) statistics that is
initiated using "prbs-test-start" on page 13512 command. This command only disables the statistics
collection and does not clear the statistics collected. To clear the collected statistics, issue the clear
interfaces statist... | [
{
"name": "ifd-name",
"desc": "Name of the interface."
},
{
"name": "direction",
"desc": "Direction to transmit or receive PRBS pattern."
}
] | view
Sample Output
Stopping PRBS test statistics collection
user@host> test interface et-0/1/2 prbs-test-stop direction 1 | Command introduced in Junos OS Release 19.2R1. | [
"Verifying Link and Transceivers using Pseudo Random Binary Sequence (PRBS) Test"
] | |
pre-attack | pre-attack number; | [edit security idp idp-policy policy-name rulebase-ips rule rule-name then notification packet-
log] | Specify the number of packets received before an attack that should be captured for further analysis of
attacker behavior. | [
{
"name": "number",
"desc": "Number of pre-attack packets."
}
] | 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. | [] |
pre-filter-shellcode | pre-filter-shellcode; | [edit security idp sensor-configuration ips] | Enable to pre-filter the shell code and protects it from buffer overflow attacks. By default this setting is
enabled. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
pre-id-default-policy | pre-id-default-policy {
then {
log {
session-init;
session-close;
}
session-timeout {
icmp seconds;
icmp6 seconds;
ospf seconds;
others seconds;
tcp seconds;
udp seconds;
}
}
} | [edit security policies] | Configure pre-ID default policy settings.
Starting in Junos OS Release 23.4R1, the flow process is optimized to deny the traffic (without AppID)
when all the potential policies (including the default policy) would deny the traffic.
The flow does not proceed to the Pre-ID default policy (pre-id-default-policy) but is in... | [
{
"name": "then",
"desc": "Specifies the policy action that has to be taken when the packet matches the criteria."
},
{
"name": "log",
"desc": "Specifies the log details at session close time and session initialization time. Values:"
},
{
"name": "session-init",
"desc": "Log at the ... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Understanding Advanced Policy-Based Routing"
] |
pre-ietf-mode | pre-ietf-mode | [edit protocols ancp],
[edit protocols ancp neighbor ip-address] | Configure the ANCP agent to run in a mode that is backward compatible with Internet draft draft-
wadhwa-gsmp-l2control-configuration-00.txt, GSMP extensions for layer2 control (L2C) for all
neighbors or for a specific neighbor. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Configuring the ANCP Agent",
"Configuring the ANCP Agent for Backward Compatibility",
"Configuring ANCP Neighbors"
] |
pre-rewrite-tos | pre-rewrite-tos; | [edit forwarding-options sampling] | Preserve prenormalized type-of-service (ToS) value for egress sampled or mirrored packets. This
configuration preserves the prerewrite ToS value for all forms of sampling, such as Routing Engine-based
sampling, port mirroring, flow monitoring, and so on. This statement is effective for egress sampling
only. | [] | 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 Traffic Sampling on MX, M and T Series Routers"
] |
pre-shared-key (MX Series) | pre-shared-key {
cak hexadecimal-number;
ckn hexadecimal-number;
} | [edit security macsec connectivity-association connectivity-association-name] | Specifies the pre-shared key used to enable MACsec using static connectivity association key (CAK)
security mode.
A pre-shared key includes a connectivity association key name (CKN) and a connectivity association key
(CAK). A pre-shared key is exchanged between two devices at each end of a point-to-point link to
enable... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Media Access Control Security (MACsec) on Routers"
] |
pre-shared-key (Security) | pre-shared-key (ascii-text key | hexadecimal key); | [edit security ike policy ike-peer-address] | Configure the key used to authenticate a dynamic peer during IKE phase 1 negotiation. Specify the key
in either ASCII or hexadecimal format. | [
{
"name": "ascii-text key",
"desc": "Authentication key in ASCII format."
},
{
"name": "hexadecimal key",
"desc": "Authentication key in hexadecimal format."
}
] | 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 an IKE Policy for Preshared Keys"
] |
pre-shared-key (Services IKE) | pre-shared-key (ascii-text key | hexadecimal key); | [edit services ike policy policy-name] | Define a preshared key for an IKE policy. | [
{
"name": "key",
"desc": "Value of preshared key. The key can be one of the following:"
},
{
"name": "ascii-text",
"desc": "ASCII text key."
},
{
"name": "hexadecimal",
"desc": "Hexadecimal key."
}
] | 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 IKE Policies"
] |
pre-shared-key | pre-shared-key {
cak hexadecimal-number;
ckn hexadecimal-number;
} | [edit security macsec connectivity-association connectivity-association-name] | Specifies the pre-shared key used to enable MACsec using static connectivity association key (CAK)
security mode.
A pre-shared key includes a connectivity association key name (CKN) and a connectivity association key
(CAK). A pre-shared key is exchanged between two devices at each end of a point-to-point link to
enable... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D15.
Statement introduced on SRX Series Firewalls in Junos OS Release 15.1X49-D60. | [
"Configuring MACsec on EX, QFX and SRX Devices",
"Understanding Media Access Control Security (MACsec)",
"Configuring Media Access Control Security (MACsec)"
] |
preauthentication-order (Access Profile) | preauthentication-order [ preauthentication-method ]; | [edit access profile profile-name] | Set the order in which the Junos OS uses preauthentication methods for the LLID service when multiple
methods are configured. Junos OS supports only the radius method.
NOTE: You cannot configure this statement if the Calling-Station-ID attribute is excluded
from RADIUS Access-Request messages by the exclude statement. | [
{
"name": "preauthentication-method",
"desc": ""
},
{
"name": "radius",
"desc": "Verify the client using RADIUS."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"RADIUS Logical Line Identifier (LLID) Overview",
"Configuring Logical Line Identification (LLID) Preauthentication"
] |
precedence | precedence precedence; | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family filter input filter-name],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family filter output filter-name],
[edit dynamic-profiles profile-name interfaces interface-name... | Apply a precedence to a dynamic filter. You can configure filter processing to occur in a particular order.
You specify a precedence for input and output filters within a dynamic profile at the [edit dynamic-profiles
profile-name interfaces (interface-name | demux0) unit logical-unit-number family family] hierarchy lev... | [
{
"name": "precedence",
"desc": "Precedence value for the filter. The lower the precedence value, the higher the precedence."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3.
The [edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit” family inet filter input
filter-name] hierarchy level and [edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit”
family inet filter output filter-name] hierarchy lev... | [
"Firewall Filters Overview",
"Understanding Dynamic Firewall Filters",
"Classic Filters Overview",
"Fast Update Filters Overview",
"Basic Classic Filter Syntax",
"Basic Fast Update Filter Syntax",
"No Link Title"
] |
precision-timers | precision-timers; | [edit protocols bgp] | NOTE: The precision-timers statement is not applicable to Junos OS Evolved.
Enable BGP sessions to send frequent keepalive messages with a hold time as short as 10 seconds.
NOTE: The hold time is three times the interval at which keepalive messages are sent,
and the hold time is the maximum number of seconds allowed t... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [] |
precision-timers-max-period | precision-timers-max-period precision-timers-max-period; | [edit routing-options nonstop-routing-options] | Support of precision-timers in the kernel is a feature where the kernel takes over auto-generation of
BGP keepalives right after the switchover from standby to primary event occurs. The kernel in the RE
continues this auto-generation until the BGP protocol is able to take over the session or until a
maximum period has ... | [] | 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. | [] |
predefined-attack-groups | predefined-attack-groups [attack-group-name]; | [edit security idp idp-policy policy-name rulebase-exempt rule rule-name match attacks],
[edit security idp idp-policy policy-name rulebase-ips rule rule-name match attacks] | Specify predefined attack groups that you can use to match the traffic against known attack objects. You
can update only the list of attack objects. | [
{
"name": "attack-name",
"desc": "Name of the predefined attack object group."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
predefined-attacks | predefined-attacks [attack-name]; | [edit security idp idp-policy policy-name rulebase-exempt rule rule-name match attacks],
[edit security idp idp-policy policy-name rulebase-ips rule rule-name match attacks] | Specify predefined attack objects that you can use to match the traffic against known attacks. You can
update only the list of attack objects. | [
{
"name": "attack-name",
"desc": "Name of the predefined attack objects."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
predefined-variable-defaults (Dynamic Client Profiles) | predefined-variable-defaults {
cos-excess-rate <percent percentage> <proportion number>;
cos-excess-rate-low <percent percentage> <proportion number>;
cos-excess-rate-high <percent percentage> <proportion number>;
cos-scheduler-bs <percent percentage> <temporal microseconds>;
cos-scheduler-shaping-r... | [edit dynamic-profiles profile-name] | Configure default values for the predefined variables that are configured in a dynamic client profile.
These default values are used when RADIUS does not supply a value. Omit the predefined variable
prefix, $junos-, when you configure a default. Most predefined variables support only a single default
value; these prede... | [
{
"name": "cos-excess-rate percent",
"desc": ""
},
{
"name": "percentage",
"desc": "Specify the percentage of excess bandwidth to share from all traffic. Range: 1 through 100"
},
{
"name": "cos-excess-rate proportion",
"desc": ""
},
{
"name": "number",
"desc": "Specify t... | 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.
Support for the $junos-interface-mtu predefined variable (interface-mtu) introduced in Junos OS Release
18.1R1 on MX Series. | [
"Configuring Default Values for Predefined Variables in a Dynamic Profile",
"Per-Subscriber Support of Maximum Transmission Unit for Dynamic Profiles"
] |
preempt (Chassis Cluster) | preempt {
delay seconds;
limit limit;
period seconds;
} | [edit chassis cluster redundancy-group group-number] | Allow preemption of the primary system based on the priority within a redundancy group.
Configuring preemption for RG0 is not allowed and is blocked when committed.
By configuring the preemptive delay timer and failover limit, you can limit the flapping of the
redundancy group state between the secondary and the primar... | [
{
"name": "delay",
"desc": "Time to wait before the node in secondary state transitions to primary state in a preemptive failover. Range: 1 to 21,600 seconds Default: 1"
},
{
"name": "limit",
"desc": "Maximum number of preemptive failovers allowed in a configured preemptive period. Range: 1 t... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. Support for delay, limit, and period options are added in
Junos OS Release 17.4R1. | [
"Understanding Chassis Cluster Redundancy Group Failover"
] |
preempt (VRRP) | (preempt | no-preempt) {
hold-time seconds;
} | [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-
group group-id],
[edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-
group group-id],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
fam... | In a Virtual Router Redundancy Protocol (VRRP) configuration, determine whether or not a backup
router can preempt a primary router:
•
preempt—Allow the primary router to be preempted.
NOTE: By default, a higher-priority backup router can preempt a lower-priority primary
router.
•
no-preempt—Prohibit the preemption of ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring a Backup Router to Preempt the VRRP Primary Router",
"Configuring VRRP Preemption and Hold Time"
] |
preempt | (preempt | no-preempt) {
hold-time seconds;
} | [edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-
group group-id] | Configure whether a backup router can preempt a primary router:
•
preempt—Allow the primary router to be preempted.
•
no-preempt—Prohibit the preemption of the primary router.
The remaining statement is explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Configuring VRRP for IPv6 (CLI Procedure)"
] |
preempt-cutover-timer | preempt-cutover-timer seconds; | For platforms with ELS:
[edit switch-options redundant-trunk-group group name],
[edit interfaces name aggregated-ether-options lacp link-protection rtg-config],
[edit interfaces name aggregated-ether-options link-protection rtg-config]
For platforms without ELS:
[edit ethernet-switching-options redundant-trunk-group gr... | Change the length of time that a re-enabled primary link waits to take over from an active secondary
link in a redundant trunk group (RTG).
Default
If you do not change the time with the preempt-cutover-timer statement, a re-enabled primary link takes
over from the active secondary link after 1 second. | [
{
"name": "seconds",
"desc": "Number of seconds that the primary link waits to take over from the active secondary link."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
Hierarchy level [edit switch-options] introduced in Junos OS Release 13.2X50-D10 (ELS). (See Using the
Enhanced Layer 2 Software CLI for information about ELS.) | [
"Example: Configuring Redundant Trunk Links for Faster Recovery on EX Series Switches",
"Example: Configuring Redundant Trunk Links for Faster Recovery on Devices with ELS Support",
"Q-in-Q Support on Redundant Trunk Links Using LAGs with Link Protection"
] |
preemption | preemption {
(aggressive | disabled | normal);
soft-preemption {
cleanup-timer seconds;
}
} | [edit logical-systems logical-system-name protocols rsvp],
[edit protocols rsvp] | Control RSVP session preemption.
Default
normal | [
{
"name": "aggressive",
"desc": "Preempt RSVP sessions whenever bandwidth is insufficient to handle all sessions. A session is"
},
{
"name": "disabled",
"desc": "Do not preempt RSVP sessions."
},
{
"name": "normal",
"desc": "Preempt RSVP sessions to accommodate new higher-priority se... | 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. | [
"Preempting RSVP Sessions"
] |
preemptive-fast-reroute | preemptive-fast-reroute {
(backward-frr-enable | no-backward-frr-enable);
(signal-degrade-monitor-enable | no-signal-degrade-monitor-enable);
(odu-backward-frr-enable | no-odu-backward-frr-enable);
(odu-signal-degrade-monitor-enable |no-odu-signal-degrade-monitor-enable);
} | [edit interfaces interface-name otn-options] | Enable or disable preemptive fast reroute options.
Default
By default, backward fast reroute insertion and signal degradation monitoring are disabled. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1. | [
"10-Gigabit Ethernet OTN Options Configuration Overview",
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
prefer-framed-ip-address (RADIUS Clients) | prefer-framed-ip-address; | [edit access radius clients client-name] | Specify that the framed-ip-address is used for subscriber creation when both the framed-route and
framed-ip-address attributes are in the RADIUS accounting request from the RADIUS client. The
framed-ip-netmask is also used for subscriber creation if it is in the request.
By default, the framed-route attribute is used f... | [] | 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 Clients That Send Accounting Requests for IP-Based Subscribers"
] |
prefer-framed-ipv6-prefix (RADIUS Clients) | prefer-framed-ipv6-prefix; | [edit access radius clients client-name] | Specify that the framed-ipv6-prefix is used for subscriber creation when both the delegated-ipv6-prefix
and framed-ipv6-prefix attributes are in the RADIUS accounting request from the RADIUS client.
By default, the delegated-ipv6-prefix attribute is used for subscriber creation when both the delegated-
ipv6-prefix and ... | [] | 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 Clients That Send Accounting Requests for IP-Based Subscribers"
] |
preference (Access) | preference route-distance; | [edit routing-options access route ip-prefix</prefix-length>] | Configure the distance for an access route. | [
{
"name": "route-distance",
"desc": "Specific distance you want to assign to the access route."
}
] | 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. | [] |
preference (DF Election) | preference {
least;
non-revertive;
value value;
} | [edit dynamic-profiles name interfaces name esi df-election-type],
[edit dynamic-profiles name logical-systems name interfaces name esi df-election-type],
[edit interfaces name esi df-election-type] | Configure the preference-based election algorithm for the designated forwarder (DF) for an Ethernet
segment among the multihoming provider edge (PE) devices in an Ethernet VPN (EVPN) network.
NOTE: Configure all the candidate devices within the Ethernet segment with the same
election algorithm. In the event of a mismat... | [
{
"name": "least",
"desc": "Enable the DF election for the ESI based on the lowest configured preference value."
},
{
"name": "non-revertive",
"desc": "Don't allow DF Election preemption after a DF failure. This option does not prevent role changes due to administrative actions such as changing ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3 for MX Series Routers with MPC and MIC interfaces.
least and non-revertive statements introduced in Junos OS Release 24.2R1. | [
"EVPN Multihoming Overview",
"preference (Interface-Level Preference for VPLS Multihoming for FEC"
] |
129) | preference preference-value; | [edit logical-systems logical-system-name routing-instances instance-name protocols vpls multi-
homing site site-name interface interface-name],
[edit routing-instances instance-name protocols vpls multi-homing site site-name interface
interface-name] | Specify a preference for the interface to become the designated forwarder (DF) for a multihomed VPLS
site. This preference statement can be useful when you want the interface preference for a site to change
dynamically so that the DF election can be influenced depending on the interface state. Among the list
of interfa... | [
{
"name": "preference-value",
"desc": "Preference value for the interface. Range: 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 12.3. | [
"Example: Configuring VPLS Multihoming (FEC 129)"
] |
preference (IPv6 Router Advertisement) | preference (high | low | medium); | [edit logical-systems logical-system-name protocols router-advertisement interface interface-
name],
[edit protocols router-advertisement interface interface-name] | Specify the router preference that is communicated to IPv6 hosts through router advertisements. The
preference value in the router advertisements enables IPv6 hosts to select a default router to reach a
remote destination.
The preference can be configured when there are multiple devices that route to distinct sets of p... | [
{
"name": "high",
"desc": "Specify a high preference for a device."
},
{
"name": "low",
"desc": "Specify a low preference for a device."
},
{
"name": "medium",
"desc": "Specify a medium preference for a device. This is the default preference."
}
] | 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. | [
"Example: Configuring IPv6 Interfaces and Enabling Neighbor Discovery"
] |
preference (PEG DF Election) | preference {
use-least;
value value;
} | [edit protocols evpn oism pim-evpn-gateway peg-df-election,
[edit routing-instances name protocols evpn oism pim-evpn-gateway peg-df-election] | Use preference-based PIM EVPN gateway (PEG) designated forwarder (DF) election with optimized
intersubnet multicast (OISM) for a virtual routing and forwarding (VRF) instance or the default L3
routing instance on an EVPN fabric device.
See Feature Explorer for the devices that support this statement in the default L3 r... | [
{
"name": "use-least",
"desc": "Elect the OISM PEG DF based on the lowest preference value. By default, the DF election preference-based algorithm uses the highest preference value."
},
{
"name": "value value",
"desc": "Preference value for OISM PEG DF election. Default: 32767 Range: 0 through... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 23.4R1.
Support in the default L3 routing instance introduced in Junos OS Evolved Release 25.4R1. | [
"PEG DF Election"
] |
preference (Protocols BGP) | preference preference; | [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 preference for routes learned from BGP.
At the BGP global level, the preference statement sets the preference for routes learned from BGP. You
can override this preference in a BGP group or peer preference statement.
At the group or peer level, the preference statement sets the preference for routes learned... | [
{
"name": "preference",
"desc": "Preference to assign to routes learned from BGP or from the group or 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 the Preference Value for BGP Routes"
] |
preference (Protocols LDP) | preference preference; | [edit logical-systems logical-system-name protocols ldp],
[edit protocols ldp interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp],
[edit protocols ldp],
[edit protocols ldp interface interface-name],
[edit routing-instances routing-instance-name p... | Set the route preference level for LDP routes. | [
{
"name": "preference",
"desc": "Preferred value."
}
] | 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 LDP Route Preferences"
] |
preference (Protocols MPLS) | preference preference; | [edit logical-systems logical-system-name protocols mpls],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name (primary |
secondary) path-name],
[edit logical-systems logical-system-name protocols ... | Preference for the route.
You can optionally configure multiple LSPs between the same pair of ingress and egress routers. This is
useful for balancing the load among the LSPs because all LSPs, by default, have the same preference
level. To prefer one LSP over another, set different preference levels for individual LSPs... | [
{
"name": "preference",
"desc": "Preference to assign to the route. A route with a lower preference value is preferred."
}
] | 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 Preference Values for LSPs",
"Configuring the Ingress Router for Static LSPs",
"Configuring the Intermediate (Transit) and Egress Routers for Static LSPs"
] |
preference (Protocols RIP) | preference preference; | [edit logical-systems logical-system-name protocols rip group group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip
group group-name],
[edit protocols rip group group-name],
[edit routing-instances routing-instance-name protocols rip group group-name] | Specify the preference of external routes learned by RIP as compared to those learned from other
routing protocols.
By default, Junos OS assigns a preference of 100 to routes that originate from RIP. When Junos OS
determines a route’s preference to become the active route, the software selects the route with the
lowest... | [
{
"name": "preference",
"desc": "Preference value. A lower value indicates a more preferred route."
}
] | 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. | [
"Route Preferences Overview"
] |
preference (Protocols RIPng) | preference preference; | [edit logical-systems logical-system-name protocols ripng group group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ripng group group-name],
[edit protocols ripng group group-name],
[edit routing-instances routing-instance-name protocols ripng group group-name] | Specify the preference of external routes learned by RIPng as compared to those learned from other
routing protocols.
By default, Junos OS assigns a preference of 100 to routes that originate from RIPng. When Junos OS
determines that a route is to become the active route, the software selects the route with the lowest
... | [
{
"name": "preference",
"desc": "Preference value. A lower value indicates a more preferred route."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for routing instances introduced in Junos OS Release 9.0. | [] |
preference (Routing Options) | preference {
metric-value;
<type metric_type>
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options (aggregate | generate | static) (defaults | route)],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name (aggregate | generate | static) (defaults | ro... | Preference value for a static, aggregate, or generated route. You also can specify a secondary preference
value, as well as color values, which are even finer-grained preference values.
You can specify a primary route preference (by including the preference statement in the configuration),
and a secondary preference th... | [
{
"name": "metric_value",
"desc": "The metric value for an aggregate, a generated, or a static route to determine the best"
},
{
"name": "route among multiple routes to a destination",
"desc": "Range: 0 through 4,294,967,295 (232 – 1) Default: 5 (for static routes), 130 (for aggregate and gener... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Summarizing Static Routes Through Route Aggregation"
] |
preference (Site-Level Preference for VPLS Multihoming for FEC 129) | preference (preference-value | backup | primary); | [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 site site-name] | Influence the designated forwarder (DF) selection for a multihomed VPLS site. Configure the preference
in terms of keywords primary and backup, or configure the preference value explicitly.
Default
If this statement is omitted, the default preference value for the site is 100. | [
{
"name": "preference-value",
"desc": "Preference value for the DF. Range: 1 through 65535"
},
{
"name": "backup",
"desc": "Less likely to become the DF."
},
{
"name": "primary",
"desc": "Most likely to become the DF."
}
] | 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)"
] |
preference (Subscriber Management) | preference route-distance; | [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
access route prefix],
[edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
rib routing-table-name access route prefix],
[edit dynamic-profiles profile-name routing-options access rout... | Dynamically configure the distance for an access route. | [
{
"name": "route-distance",
"desc": "Either the specific distance you want to assign to the access route or either of the"
},
{
"name": "following distance variables:",
"desc": ""
},
{
"name": "$junos-framed-route-distance",
"desc": "Distance of an IPv4 access route; the variable is ... | 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.
Support at [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options access
route prefix] and [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
rib routing-table-name access route prefix] hierar... | [
"Configuring Dynamic Access Routes for Subscriber Management"
] |
preference (Tunnel Profile) | preference number; | [edit access tunnel-profile profile-name tunnel tunnel-id] | Specify the preference for a tunnel. You can specify up to 8 levels of preference, and you can assign the
same preference to a maximum of 31 tunnels. When you define multiple preferences for a destination,
you increase the probability of a successful connection.
This value can be overridden by RADIUS attribute Tunnel-P... | [
{
"name": "number",
"desc": "Number that indicates the order in which the router attempts to connect to the destination. Zero"
}
] | 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. | [
"L2TP LAC Tunneling for Subscribers"
] |
preferred | preferred; | [edit interfaces interface-name unit logical-unit-number family family address address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family address address] | Configure this address to be the preferred address on the interface. If you configure more than one
address on the same subnet, the preferred source address is chosen by default as the source address
when you initiate frame transfers to destinations on the subnet.
NOTE: The edit logical-systems hierarchy is not availab... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Interface Address"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.