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 |
|---|---|---|---|---|---|---|---|
preferred-ciphers | preferred-ciphers (custom | medium | strong | weak); | [edit services ssl proxy profile profile-name ]
[edit services ssl termination profile profile-name ]
[edit services ssl initiation profile profile-name] | Select preferred ciphers. Preferred ciphers allow you to define an SSL cipher that can be used with
acceptable key strength. Ciphers are divided in three categories depending on their key strength: strong,
medium, or weak.
Custom ciphers allow you to define your own cipher list. If you do not want to use one of the thr... | [
{
"name": "custom",
"desc": "Configure custom cipher suite and order of preference."
},
{
"name": "medium",
"desc": "Use ciphers with key strength of 128 bits or greater."
},
{
"name": "strong",
"desc": "Use ciphers with key strength of 168 bits or greater."
},
{
"name": "wea... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. | [
"Firewall User Authentication Overview",
"SSL Proxy Overview"
] |
preferred-lifetime (Dynamic Router Advertisement) | preferred-lifetime seconds; | [edit dynamic-profiles profile-name protocols router-advertisement interface interface-
nameprefix prefix] | Specify how long the prefix generated by stateless autoconfiguration remains preferred. | [
{
"name": "seconds",
"desc": "Preferred lifetime, in seconds. If you set the preferred lifetime to 0xffffffff, the lifetime is"
}
] | 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. | [
"IPv6 WAN Link Addressing with NDRA",
"Dynamic Router Advertisement Configuration Overview"
] |
preferred-lifetime | preferred-lifetime seconds; | [edit logical-systems logical-system-name protocols router-advertisement interface interface-
name prefix prefix],
[edit protocols router-advertisement interface interface-name prefix prefix] | Specify how long the prefix generated by stateless autoconfiguration remains preferred. | [
{
"name": "seconds",
"desc": "Preferred lifetime, in seconds. If you set the preferred lifetime to 0xffffffff, the lifetime is"
}
] | 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 IPv6 Interfaces and Enabling Neighbor Discovery",
"Secure IPv6 Neighbor Discovery"
] |
preferred-prefix-length | preferred-prefix-length preferred-prefix-length; | [edit interfaces interface-name unit logical-unit-number family family dhcpv6-client prefix-
delegating]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet6 dhcpv6-client prefix-delegating]
[edit tenants tenant-name interfaces interface-name unit logical-unit-numbe... | Allows you to configure DHCPv6 client preferred prefix length. If preferred-prefix-length is configured,
the DHCPv6 client checks the prefix length in the ADVERTISE packet and if the check fails, a sysolg is
created. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30 and in Junos OS Release 15.1X49-D100.
The logical-systems and tenants options are introduced in Junos OS Release 18.4R1. | [] |
preferred-source-address | preferred-source-address address; | [edit dynamic-profiles interfaces interface-name unit logical-unit-number family family unnumbered-
address interface-name],
[edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family family] | For unnumbered Ethernet interfaces configured with a loopback interface as the donor interface, specify
one of the loopback interface’s secondary addresses as the preferred source address for the
unnumbered Ethernet interface. Configuring the preferred source address enables you to use an IP
address other than the prim... | [
{
"name": "address",
"desc": "Secondary IP address of the donor loopback interface. Alternatively, use the $junos-preferred-source-address or the $junos-preferred-source-ipv6-address predefined variable to dynamically apply a"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Support for the $junos-preferred-source-address and $junos-preferred-source-ipv6-address predefined variables
introduced in Junos OS Release 9.6. | [
"Configuring an Unnumbered Interface",
"Junos OS Network Interfaces Library for Routing Devices",
"Junos OS Administration Library for Routing Devices"
] |
prefix (Access IPv6) | prefix IPv6-network prefix; | [edit access address-assignment pool pool-name family inet6] | Specify the IPv6 prefix for the IPv6 address-assignment pool. This statement is mandatory for IPv6
address-assignment pools. | [
{
"name": "IPv6-network-prefix",
"desc": "IPv6 prefix."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 10.4 of Junos OS. | [
"Firewall User Authentication Overview"
] |
prefix (Address-Assignment Pools) | prefix ipv6-prefix; | [edit access address-assignment pool pool-name family inet6] | Specify the IPv6 prefix for the IPv6 address-assignment pool. This statement is mandatory for IPv6
address-assignment pools. | [
{
"name": "ipv6-prefix",
"desc": "The IPv6 prefix."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Address-Assignment Pools Overview",
"Address-Assignment Pool Configuration Overview"
] |
prefix (Circuit ID for Option 82) | prefix {
host-name;
logical-system-name;
routing-instance-name;
} | For platforms with enhanced Layer 2 software (ELS):
[edit vlans forwarding-options dhcp-security option-82 circuit-id]
For platforms without ELS:
[edit ethernet-switching-options secure-access-port vlan (all | vlan-name) dhcp-option82 circuit-id],
[edit forwarding-options helpers bootp dhcp-option82 circuit-id],
[edit ... | Configure an optional prefix for the circuit ID suboption in the DHCP option 82 information that is
inserted by the switch or router into the packet header of a DHCP request before it forwards or relays
the request to a DHCP server.
Default
If the prefix statement is not explicitly specified, no prefix is prepended to ... | [
{
"name": "host-name",
"desc": "Add router host name to DHCP option 82 circuit ID."
},
{
"name": "logical-system-name",
"desc": "Add logical system name to DHCP option-82 circuit ID. This option is not used for the prefix statement at any of the above hierarchy levels."
},
{
"name": "rou... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3.
Hierarchy level [edit vlans vlan-name forwarding-options dhcp-security option-82 circuit-id] introduced in
Junos OS Release 13.2X50-D10. (See Using the Enhanced Layer 2 Software CLI for information about
ELS.) | [
"Example: Setting Up DHCP Option 82 Using the Same VLAN",
"Example: Setting Up DHCP Option 82",
"http://tools.ietf.org/html/rfc3046."
] |
prefix (DHCP Client) | prefix {
host-name;
logical-system-name;
routing-instance-name;
} | [edit interfaces interface-name unit logical-unit-number family family dhcp-client client-
identifier] | Specify a prefix as a client identifier. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. | [] |
prefix (DHCP Relay Agent) | prefix prefix; | [edit forwarding-options dhcp-relay dhcpv6 (relay-agent-interface-id | relay-agent-remote-id)],
[edit forwarding-options dhcp-relay dhcpv6 group group-name (relay-agent-interface-id | relay-agent-
remote-id)],
[edit forwarding-options dhcp-relay relay-option-82 (circuit-id | remote-id)],
[edit forwarding-options dhcp-r... | Add a prefix to the DHCP base option 82 Agent Circuit ID (suboption 1) or Agent Remote ID (suboption
2) information, or to the DHCPv6 option 18 (Relay Agent Interface-ID) or option 37 (Relay Agent
Remote-ID) information in DHCP packets that DHCP relay agent sends to a DHCP server. The prefix can
consist of any combinat... | [
{
"name": "prefix",
"desc": "Any of the following:"
},
{
"name": "host-name",
"desc": "Prepend the hostname of the router configured with the host-name statement at the [edit"
},
{
"name": "logical-system-name",
"desc": "Prepend the name of the logical system to the option informatio... | 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.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4.
Support at the [edit ... relay-agent-remote-id] and [edit ... remote-id] hierarchy levels introduced in Junos
OS Release 14.1. | [
"Including a Prefix in DHCP Options",
"Using DHCP Relay Agent Option 82 Information",
"Configuring DHCPv6 Relay Agent Options"
] |
prefix (DHCPv6 Options) | prefix {
host-name;
logical-system-name;
routing-instance-name;
vlan-id;
vlan-name;
} | [edit vlans forwarding-options dhcp-security dhcpv6-options option-18]
[edit vlans forwarding-options dhcp-security dhcpv6-options option-37] | Configure a prefix for DHCPv6 option 18 (Interface ID) or option 37 (Remote ID). When configured, the
prefix is inserted into DHCPv6 packets during the DHCPv6 snooping process.
Default
If the prefix statement is not explicitly specified, no prefix is inserted in DHCPv6 packets. | [
{
"name": "host-name",
"desc": "Add the host name of the switch to DHCPv6 options."
},
{
"name": "logical-system-name",
"desc": "Add the logical system name to the DHCPv6 options."
},
{
"name": "routing-instance-name",
"desc": "Add the routing instance name to the DHCPv6 options."
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10. | [] |
prefix (Dynamic Router Advertisement) | prefix prefix {
(autonomous | no-autonomous);
(on-link | no-on-link);
preferred-lifetime seconds;
valid-lifetime seconds;
} | [edit dynamic-profiles protocols router-advertisement interface interface-name] | Configure the prefix name in router advertisement messages. | [
{
"name": "prefix",
"desc": "Prefix name. For dynamic configuration, specify the $junos-ipv6–ndra-prefix dynamic variable."
}
] | 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. | [
"IPv6 WAN Link Addressing with NDRA",
"Dynamic Router Advertisement Configuration Overview"
] |
prefix (Protocols IPv6 Neighbor Discovery) | prefix prefix {
(autonomous | no-autonomous);
(on-link | no-on-link);
preferred-lifetime seconds;
valid-lifetime seconds;
} | [edit logical-systems logical-system-name protocols router-advertisement interface interface-
name],
[edit protocols router-advertisement interface interface-name] | Configure prefix properties in router advertisement messages. | [
{
"name": "prefix",
"desc": "Prefix name."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring IPv6 Interfaces and Enabling Neighbor Discovery"
] |
prefix (Remote ID for Option 82) | prefix (hostname | mac | none); | [edit ethernet-switching-options secure-access-port vlan (all | vlan-name) dhcp-
option82 remote-id],
[edit forwarding-options helpers bootp dhcp-option82 remote-id],
[edit forwarding-options helpers bootp interface interface-name dhcp-option82 remote-id] | Configure an optional prefix for the remote ID suboption in the DHCP option 82 information that is
inserted by the switch into the packet header of a DHCP request before it forwards or relays the request
to a DHCP server.
Default
If prefix is not explicitly specified, no prefix is appended to the remote ID. | [
{
"name": "hostname",
"desc": "Name of the host system (the switch) that is forwarding or relaying the DHCP request from"
},
{
"name": "mac",
"desc": "MAC address of the host system (the switch) that is forwarding or relaying the DHCP request from"
},
{
"name": "none",
"desc": "No pr... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Example: Setting Up DHCP Option 82 Using the Same VLAN",
"Example: Setting Up DHCP Option 82",
"http://tools.ietf.org/html/rfc3046."
] |
prefix (Security Static NAT) | prefix {
address-prefix;
mapped-port lower-port-range to upper-port-range;
routing-instance (routing-instance-name| default);
} | [edit security nat static rule-set rule-set-name rule rule-name then static-nat] | Specify a static IP address prefix.
NOTE: If you use the inet option for translation of IPv6 to IPv4 addresses (and vice
versa), you do not need to specify a prefix because the inet option automatically strips
the first 96 most significant bits from the 128-bit IPv6 address. | [
{
"name": "address-prefix",
"desc": "Specify address prefix."
},
{
"name": "mapped-port lower-port-range to upper-port-range",
"desc": "Specify a destination port or port range to allow static"
},
{
"name": "routing-instance",
"desc": "Specify routing instance type:"
},
{
"na... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. | [] |
prefix | prefix destination-prefix; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast scope scope-name],
[edit logical-systems logical-system-name routing-options multicast scope scope-name],
[edit routing-instances routing-instance-name routing-options multicast scope scope-name],
[edit routing-... | Configure the prefix for multicast scopes. | [
{
"name": "destination-prefix",
"desc": "Address range for the multicast scope."
}
] | 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. | [
"Examples: Configuring Administrative Scoping",
"Example: Creating a Named Scope for Multicast Scoping"
] |
prefix-65-127-disable | prefix-65-127-disable; | [edit chassis forwarding-options lpm-profile] | For the Unified Forwarding Table (UFT) feature, specify not to allocate any memory for IPv6 prefixes
with lengths in the range /65 through /127 for longest-prefix-match (LPM) entries. Doing so increases
the memory available for LPM entries for IPv4 unicast prefixes and IPv6 prefixes with lengths equal to
or less than 6... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51-D15.
Support introduced in Junos OS Release 15.1X53-D30 for QFX5200 Series switches.
Support introduced in Junos OS Release 18.1R1 for QFX5200-48C and QFX5210 switches. | [
"Configuring the Unified Forwarding Table on Switches",
"Understanding the Unified Forwarding Table"
] |
prefix-action (Configuring) | prefix-action prefix-action-name {
count;
destination-prefix-length prefix-length;
filter-specific;
policer policer-name;
source-prefix-length prefix-length;
subnet-prefix-length prefix-length;
} | [edit firewall family inet],
[edit logical-systems logical-system-name firewall family inet] | Configure a prefix-specific action. | [
{
"name": "count",
"desc": "Enable counter."
},
{
"name": "destination-prefix-length prefix-length",
"desc": "Destination prefix length."
},
{
"name": "filter-specific",
"desc": "Create the prefix-specific set of policers and counters as a filter-specific set. If this option"
},
... | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Logical systems support introduced in Junos OS Release 9.3. | [
"Prefix-Specific Counting and Policing Actions"
] |
prefix-action (Firewall Filter Action) | prefix-action prefix-action-name; | [edit firewall family inet filter filter-name term term-name then],
[edit logical-systems logical-system-name firewall family inet filter filter-name term term-name
then] | Reference a prefix-specific action. | [
{
"name": "prefix-action-name",
"desc": "Name of a prefix-specific action to use to rate-limit traffic."
}
] | Statement introduced before Junos OS Release 7.4.
Logical systems support introduced in Junos OS Release 9.3. | [
"Firewall Filter Nonterminating Actions",
"Prefix-Specific Counting and Policing Actions"
] | |
prefix-attribute-flags | prefix-attribute-flags [node-segment-flag | external-prefix-flag] | [edit policy-options policy-statement <policy-name> then] | When the prefix attribute flags CLI is configured, the originating router will include the prefix attributes
sub TLV. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.4R1. | [] |
prefix-export-limit (Protocols IS-IS) | prefix-export-limit number; | [edit logical-systems logical-system-name protocols isis level level-number],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis
level level-number],
[edit protocols isis level level-number],
[edit routing-instances routing-instance-name protocols isis level level-number] | Configure a limit to the number of prefixes exported into IS-IS.
By default, there is no limit to the number of prefixes that can be exported into IS-IS. To configure a limit
to the number of prefixes that can be exported into IS-IS, include the prefix-export-limit statement. The
prefix-export-limit statement protects ... | [
{
"name": "number",
"desc": "Prefix limit."
}
] | 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: Redistributing OSPF Routes into IS-IS",
"Example: Configuring a Routing Policy to Redistribute BGP Routes with a Specific Community Tag",
"into IS-IS",
"Understanding BGP Communities, Extended Communities, and Large Communities as Routing Policy",
"Match Conditions",
"Understanding Routing Polic... |
prefix-export-limit (Protocols OSPF) | prefix-export-limit number; | [edit logical-systems logical-system-name protocols (ospf | ospf3)],
[edit logical-systems logical-system-name protocols ospf topology (default | ipv4-multicast |
name)],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast)],
[edit logical-systems logical-sy... | Configure a limit to the number of prefixes exported into OSPF. | [
{
"name": "number",
"desc": "Prefix limit."
}
] | 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 Multitopology Routing introduced in Junos OS Release 9.0.
Support for Multitopology Routing introduced in Junos OS Release 9.0 for EX Series switches.
Support for the realm statement introduced in Junos OS Release 9.2.
Support for the realm statement introdu... | [
"Example: Limiting the Number of Prefixes Exported to OSPF",
"Example: Configuring Multitopology Routing to Provide Redundancy for Multicast Traffic over",
"Separate Network Paths",
"Example: Configuring Multitopology Routing for Class-Based Forwarding of Voice, Video, and Data",
"Traffic",
"Understanding... |
prefix-limit | prefix-limit {
maximum number;
teardown <percentage> <idle-timeout (forever | minutes)>;
drop-excess <percentage>;
hide-excess <percentage>;
} | [edit logical-systems logical-system-name protocols bgp family (inet | inet6) (any | flow |
labeled-unicast | multicast | unicast)],
[edit logical-systems logical-system-name protocols bgp group group-name family (inet | inet6)
(any | flow | labeled-unicast | multicast | unicast)],
[edit logical-systems logical-syste... | Limit the number of prefixes received on a BGP peer session and a rate-limit logging when injected
prefixes exceed a set limit.
This functionality is identical to the accepted-prefix-limit functionality except that it operates against
received prefixes rather than accepted prefixes. | [
{
"name": "maximum number",
"desc": "When you set the maximum number of prefixes, a message is logged when that number is exceeded. Range: 1 through 4,294,967,295 (232 – 1)"
},
{
"name": "teardown",
"desc": ""
},
{
"name": "<percentage>",
"desc": "(Optional) If you include the teard... | 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.
drop-excess <percentage> and hide-excess <percentage> options introduced in Junos OS Release 21.2.
drop-excess <percentage> and hide-excess <percentage> options introduced in Junos OS Evolved
Release 21.3R1. | [
"Understanding Multiprotocol BGP"
] |
prefix-list (Junos Telemetry Interface) | prefix-list {
table table-name {
family {
inet {
prefix [ prefix ... ];
}
inet6 {
prefix [ prefix ... ];
}
}
}
} | [edit system fib-streaming] | Enable specific prefix addresses to be periodically streamed from the target (source) to a collector. Only
interfaces with those prefixes and their corresponding next-hop and next-hop group containers are
exported to the IP OpenConfig Abstract Forwarding Table (oc-aft) collector. Reducing the set of
interfaces to only ... | [
{
"name": "table-name",
"desc": "A forwarding information base (FIB) table."
},
{
"name": "prefix",
"desc": "An IPv4 (inet) or IPv6 inet6 address prefix."
}
] | edit | Statement introduced in Junos OS 24.2R1 for MX2020 routers. | [
"Configuring IP-AFT Prefix Filtering"
] |
prefix-list (PIM RPF Selection) | prefix-list prefix-list-addresses {
source source-address {
next-hop next-hop-address;
}
wildcard-source {
next-hop next-hop-address;
}
} | [edit routing-instances routing-instance-name protocols pim rpf-selection group group-address
source source-address],
[edit routing-instances routing-instance-name protocols pim rpf-selection group group-address
wildcard-source],
[edit routing-instances routing-instance-name protocols pim rpf-selection prefix-list pr... | (Optional) Configure a list of prefixes (addresses) for multiple PIM groups. | [
{
"name": "prefix-list-addresses",
"desc": "List of prefixes (addresses) for multiple PIM groups."
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Example: Configuring PIM RPF Selection"
] |
prefix-list | prefix-list name {
ip-addresses;
apply-path path;
} | [edit dynamic policy-options],
[edit logical-systems logical-system-name policy-options],
[edit policy-options] | Define a list of IPv4 or IPv6 address prefixes for use in a routing policy statement or firewall filter
statement, or a list of IPv6 addresses or address prefixes for use in an IPv6 RA guard policy.
You can configure up to 85,325 prefixes in each prefix list. To configure more than 85,325 prefixes,
configure multiple p... | [
{
"name": "name",
"desc": "Name that identifies the list of IPv4 or IPv6 addresses or address prefixes."
},
{
"name": "ip-addresses",
"desc": "These are the IPv4 or IPv6 prefixes specified as prefix/prefix-length. If you omit prefix-length for an IPv4 prefix, the default is /32prefix-length. If ... | 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 configuration in the dynamic database introduced in Junos OS Release 9.5.
Support for configuration in the dynamic database introduced in Junos OS Release 9.5 for EX Series
switches.
Support for the vpls protocol family introduced in Junos OS Release 10.2.
... | [
"Understanding Prefix Lists for Use in Routing Policy Match Conditions",
"Firewall Filter Match Conditions Based on Address Fields",
"Junos OS Routing Policies, Firewall Filters and Traffic Policers User Guide for Routing Devices",
"Example: Configuring a Filter to Limit TCP Access to a Port Based On a Prefix... |
prefix-list-filter | prefix-list-filter prefix-list-name match-type <actions>; | [edit logical-systems logical-system-name policy-options policy-statement policy-statement-name
term term--name from],
[edit policy-options policy-statement policy-statement-name term term--name from] | Evaluate a list of prefixes within a prefix list using specified qualifiers. | [
{
"name": "prefix-list-name",
"desc": "Name of the prefix list to evaluate."
},
{
"name": "exact",
"desc": "The prefix-length component of the match prefix is equal to the route’s prefix length"
},
{
"name": "longer",
"desc": "The route’s prefix length is greater than the prefix-leng... | 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. | [
"Understanding Prefix Lists for Use in Routing Policy Match Conditions"
] |
prefix-list-name | prefix-list-name prefix-list-name; | [edit forwarding-options access-security router-advertisement-guard policy policy-name discard
(forwarding-options)],
[edit forwarding-options access-security router-advertisement-guard policy policy-name accept (Router
Advertisement Guard Policy) match-list] | Configure a list of IPv6 address prefixes for an IPv6 Router Advertisement (RA) guard policy. The policy
is used to validate the source IPv6 address prefix of an incoming RA message against the IPv6 address
prefixes in this list. RA guard protects against rogue RA messages generated either maliciously or
unintentionall... | [
{
"name": "prefix-list-name",
"desc": "Configure a list of IPv6 address prefixes for an RA guard policy. The policy is used to validate the source of an incoming RA message by comparing the IPv6 address prefix of the RA message to the IPv6 address prefixes contained in the list."
}
] | 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-D55. | [
"Understanding IPv6 Router Advertisement Guard",
"Configuring Stateful IPv6 Router Advertisement Guard"
] |
prefix-name (Security Static NAT) | prefix-name {
address-prefix-name;
mapped-port lower-port-range to upper-port-range;
routing-instance (routing-instance-name| default);
} | [edit security nat static rule-set rule-set-name rule rule-name then static-nat] | Specify an address from the address book. | [
{
"name": "address-prefix-name",
"desc": "Specify address prefix name from address book."
},
{
"name": "mapped-port lower-port-range to upper-port-range",
"desc": "Specify a destination port or port range to allow static"
},
{
"name": "routing-instance",
"desc": "Specify routing inst... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. | [] |
prefix-scale-mode | prefix-scale-mode | [edit firewall family <inet/inet6> filter <filter-name>] | Allows you to configure significantly higher number of prefixes, of upto 225,000 prefixes per term, and
in total up to 1 million prefixes (IPv4), 512,000 prefixes (IPv6 64-bit), 256,000 prefixes (IPv6 128-bit) as
match conditions in an ingress firewall filter. Without this configuration, the scale is limited to a total... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.4 R1 | [] |
prefix-segment (Routing Options) | prefix-segment prefix-segment {
index index;
} | [edit logical-systems name routing-instances name routing-options source-packet-routing mapping-
server-entry],
[edit logical-systems name routing-options source-packet-routing mapping-server-entry],
[edit routing-instances name routing-options source-packet-routing mapping-server-entry],
[edit routing-options source-p... | Configure the IP address and index number of the prefix segment for the LDP mapping server. | [
{
"name": "prefix-segment",
"desc": "IP address of the prefix segment."
},
{
"name": "index index",
"desc": "Prefix segment index. Range: 0 through 199999"
}
] | routing | Statement introduced in Junos OS Release 18.2R1. | [
"LDP Mapping Server for Interoperability of Segment Routing with LDP Overview"
] |
prefix-segment | prefix-segment {
algorithm name {
index index;
node-segment;
redistribute;
}
} | [edit logical-systems name policy-options policy-statement name from],
[edit logical-systems name policy-options policy-statement name then],
[edit policy-options policy-statement policy-name term term-name from],
[edit policy-options policy-statement polic-name term term-name then],
[edit protocols ospf source-packet-... | Configure prefix segment attributes such as index and node segment. Prefix segment index is the index
assigned to a specific prefix. This is used by all other remote routers in the network to index the prefix
into respective segment routing global blocks (SRGB) to derive the segment identifier and to forward the
traffi... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2.
Statement introduced under [edit protocols ospf source-packet-routing] hierarchy in Junos OS Release
19.1R1 for MX Series.
reuse-allocated-sid option introduced in Junos OS Release 20.4R1.
redistribute option introduced in Junos OS Release 22.2R1. | [
"Understanding Adjacency Segments, Anycast Segments, and Configurable SRGB in SPRING",
"Configuring Anycast and Prefix segments in SPRING for IS-IS Protocol"
] |
prefix-segment-range | prefix-segment-range prefix-segment-range-name {
attached;
domain-wide-flooding;
no-node-segment;
size size;
start-index start-index;
start-prefix start-prefix;
} | [edit logical-systems name routing-instances name routing-options source-packet-routing mapping-
server-entry],
[edit logical-systems name routing-options source-packet-routing mapping-server-entry],
[edit routing-instances name routing-options source-packet-routing mapping-server-entry],
[edit routing-options source-p... | Configure the prefix segment range for the LDP mapping server. | [
{
"name": "prefix-segment-range-name",
"desc": "Name of the prefix segment range."
},
{
"name": "attached",
"desc": "(Optional) Set the flag in IS-IS mapping server advertisement to indicate that the prefixes and SIDs advertised in the SID or Label Binding TLV are directly connected to their ori... | •
routing—To view this statement in the configuration.
•
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1.
attached, domain-wide-flooding, and no-node-segment options introduced in Junos OS Release 19.1R1. | [
"LDP Mapping Server for Interoperability of Segment Routing with LDP Overview"
] |
prefix-unreachable | prefix-unreachable {
originator {
max-advertisements max-advertisements;
metric metric;
unplanned-lifetime seconds;
}
use-only-for-leaking;
} | [edit logical-systems name protocols isis],
[edit logical-systems name routing-instances name protocols isis],
[edit logical-systems name tenants name routing-instances name protocols isis],
[edit protocols isis],
[edit routing-instances name protocols isis],
[edit tenants name routing-instances name protocols isis] | Configure unreachable prefix advertisement parameters. | [
{
"name": "use-only-for-leaking",
"desc": "Do not use this UPA route for resolution."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1. | [] |
prelogon compliance (Juniper Secure Connect) | pre-logon name {
banner {
(file file | message message);
}
term term-name {
match {
platform {
(android | ios | ipados | macos | windows) {
(app-version | os-version) {
(equa... | [edit security remote-access compliance] | The statement defines Juniper Secure Connect remote-access prelogon compliance policies. You
associate a single compliance rule object per remote-access connection profile. This means, a remote-
access connection profile can have one associated compliance policy. The Juniper Secure Connect
application sends details to ... | [
{
"name": "pre-logon",
"desc": "Define pre-login compliance rule; specify the compliance rule name. Values: Format: String beginning with a number or letter and consisting of letters, numbers, dashes and underscores. Range: Supports up to 255 prelogon compliance rules."
},
{
"name": "term",
"... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.1R1.
Support for ipados added in Junos OS Release 24.4R1.
Support for banner added in Junos OS Release 24.4R1. | [
"Juniper Secure Connect User Guide"
] |
premium (Hierarchical Policer) | premium {
if-exceeding {
bandwidth-limit bandwidth;
burst-size-limit burst;
}
then {
discard;
}
} | [edit dynamic-profiles profile-name firewall hierarchical-policer],
[edit firewall hierarchical-policer] | On M40e, M120, and M320 edge routers with FPC input as FFPC and FPC output as SFPC, and on
MX Series, T320, T640, and T1600 edge routers with Enhanced Intelligent Queuing (IQE) PICs, T4000
routers with Type 5 FPC and Enhanced Scaling Type 4 FPC, specify a premium level for a hierarchical
policer. | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Support at the [edit dynamic-profiles ... hierarchical-policer name] hierarchy level introduced in Junos OS
Release 11.4. | [
"Applying Policers",
"Guidelines for Applying Traffic Policers",
"Hierarchical Policer Configuration Overview",
"Hierarchical Policers",
"bandwidth-limit (Hierarchical Policer)"
] |
premium (Output Priority Map) | premium {
forwarding-class class-name {
loss-priority (high | low);
}
} | [edit interfaces interface-name gigether-options ethernet-switch-profile ethernet-policer-profile
output-priority-map classifier] | For Gigabit Ethernet IQ interfaces only, define the classifier for egress premium traffic.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Gigabit Ethernet Policers"
] |
premium (Policer) | premium {
bandwidth-limit bps;
burst-size-limit bytes;
} | [edit interfaces interface-name gigether-options ethernet-switch-profile ethernet-policer-profile
policer cos-policer-name] | Define a policer to apply to nonpremium traffic.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Gigabit Ethernet Policers"
] |
preprovisioned (MX Series Virtual Chassis) | preprovisioned; | [edit virtual-chassis] | Enable creation of a Virtual Chassis by means of a preprovisioned configuration.
To configure a Virtual Chassis consisting of MX Series routers, you must create a preprovisioned
configuration on the primary router in the Virtual Chassis by specifying the serial number, member ID,
and role for each router (member chassi... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Preprovisioned Member Information for a Virtual Chassis",
"Example: Configuring Interchassis Redundancy for MX Series 5G Universal Routing Platforms Using a",
"Virtual Chassis"
] |
preprovisioned | preprovisioned; | [edit virtual-chassis] | Enable the preprovisioned configuration mode for a Virtual Chassis or Virtual Chassis Fabric (VCF)
configuration.
When the preprovisioned configuration mode is enabled, you cannot use the CLI or the J-Web interface
to change the primary-role priority or member ID of member switches.
You must use this statement to confi... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Preprovisioning a Virtual Chassis Fabric",
"Example: Configuring an EX4200 Virtual Chassis Using a Preprovisioned Configuration File",
"Example: Setting Up a Full Mesh EX8200 Virtual Chassis with Two EX8200 Switches and Redundant",
"XRE200 External Routing Engines",
"Configuring an EX4200, EX4500, or EX455... |
preserve-fpc-poweron-sequence | preserve-fpc-poweron-sequence; | [edit chassis] | Preserve the sequence in which the line cards—specifically, MPCs on MX series routers—on a router or
switch are powered on when the device is restarted. During a system reboot, the line cards are brought
online in the sequence specified in the system log file /var/log/fpc_poweron_seq.log. When a line card
goes offline,... | [] | chassis—To view this statement in the configuration.
chassis-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding How Dynamic Power Management Enables Better Utilization of Power"
] |
preserve-incoming-fragment-size | preserve-incoming-fragment-size; | [edit security flow] ] | Enable the preserve incoming fragment size feature that allows the SRX Series Firewall to preserve the
size of incoming fragments to be used in determining the best maximum transmission unit (MTU) size for
the egress interface.
When data is sent from one host to another, it is transmitted as a series of packets. Perfor... | [] | 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-D100. | [
"Understanding How Preserving Incoming Fragmentation Characteristics Can Improve Throughput"
] |
preserve-interface | preserve-interface; | [edit interfaces interface-name sonet-options aps] | Provide link PIC replication, providing MLPPP link redundancy at the port level. This feature is supported
with SONET APS and the following link PICs:
•
Channelized OC3 IQ PIC
•
Channelized OC12 IQ PIC
•
Channelized STM1 IQ PIC
Link PIC replication provides the ability to add two sets of links, one from the active SONE... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring Link State Replication for Redundant Link PICs"
] |
preserve-nexthop-hierarchy (SRv6 TE) | preserve-nexthop-hierarchy {
(sr-mpls | srv6);
} | [edit protocols source-packet-routing] | Enable preserve-nexthop hierarchy support for source packet routing. When you enable preserve-nexthop-
hierarchy, SRv6 TE transport is populated correctly so that service resolution is performed properly. The
preserve-nexthop-hierarchy statement at the [edit protocols source-packet-routing] hierarchy level is a
prerequ... | [
{
"name": "sr-mpls",
"desc": "Disable preserve-nexthop-hierarchy for sr-mpls."
},
{
"name": "srv6",
"desc": "Disable preserve-nexthop-hierarchy for srv6."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.3R1. | [
"Understanding SR-TE Policy for SRv6 Tunnel"
] |
preserve-parity (Source NAT Next Gen Services) | preserve-parity; | [edit services nat source pool nat-pool-name port] | Assign a port with the same parity (even or odd) as the incoming source port. This feature is not
available if you configure port-block allocation, and is not available for deterministic NAT. | [] | 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. | [] |
preserve-range (Source NAT Next Gen Services) | preserve-range; | [edit services nat source pool nat-pool-name port] | For source NAT with port translation, except for deterministic NAT, assign a port within the same range
as the incoming port—either 0 through 1023 or 1024 through 65,535. This feature is not available if you
configure port block allocation. | [] | 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. | [] |
primary (Adaptive Services Interfaces) | primary interface-name; | [edit interfaces (rsp0 | rsp1) redundancy-options] | Specify the primary adaptive services interface. | [
{
"name": "interface-name",
"desc": "The identifier for the AS or Multiservices PIC interface, which must be of the form sp-fpc/pic/port."
}
] | 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 AS or Multiservices PIC Redundancy"
] |
primary (Address on Interface) | primary; | [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 primary address of the protocol on the interface. If the logical unit has
more than one address, the primary address is used by default as the source address when packet
transfer originates from the interface and the destination address does not indicate the subnet.
NOTE: The edit logic... | [] | 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"
] |
primary (Interface for Router) | primary; | [edit interfaces interface-name unit logical-unit-number family family]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family] | Configure the primary interface for a device. By default, the multicast-capable interface with the lowest-
index address is chosen as the primary interface. If there is no such interface, the point-to-point
interface with the lowest-index address is chosen. Otherwise, any interface with an address can be
picked. In pra... | [] | 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 Default, Primary, and Preferred Addresses and Interfaces"
] |
primary (Link Services IQ PIC Interfaces) | primary interface-name; | [edit interfaces rlsqnumber redundancy-options] | Specify the primary Link Services IQ PIC interface. | [
{
"name": "interface-name",
"desc": "The identifier for the Link Services IQ PIC interface, which must be of the form lsq-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 7.6. | [
"Configuring LSQ Interface Redundancy in a Single Router Using Virtual Interfaces"
] |
primary (MBGP MVPN) | primary address; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols mvpn
static-umh],
[edit routing-instances routing-instance-name protocols mvpn static-umh] | Statically set the primary upstream multicast hop (UMH) for type 7 (S,G) routes.
If the primary UMH is unavailable, the backup UMH is used. | [
{
"name": "address",
"desc": "Address of the primary UMH."
}
] | 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. | [
"Understanding Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider",
"Tunnels",
"Example: Configuring Sender-Based RPF in a BGP MVPN with RSVP-TE Point-to-Multipoint Provider",
"Tunnels"
] |
primary (Protocols MPLS) | primary path-name {
adaptive;
admin-group {
exclude [ group-names ];
include-all [ group-names ];
include-any [ group-names ];
}
bandwidth bps;
class-of-service cos-value;
hop-limit number;
no-cspf;
no-decrement-ttl;
optimize-timer seconds;
preference... | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name] | Specify the primary path to use for an LSP. You can configure only one primary path.
You can optionally specify preference, CoS, and bandwidth values for the primary path, which override
any equivalent values that you configure for the LSP (at the [edit mpls label-switched-path lsp-name]
hierarchy level). | [
{
"name": "path-name",
"desc": "Name of a path that you created with the path statement."
}
] | 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 Primary and Secondary LSPs"
] |
primary (Virtual Tunnel in Routing Instances) | primary; | [edit logical-systems logical-system-name routing-instances routing-instance-name interface vt-
fpc/pic/port.unit-number],
[edit routing-instances routing-instance-name interface vt-fpc/pic/port.unit-number] | In a multiprotocol BGP (MBGP) multicast VPN (MVPN), configure the virtual tunnel (VT) interface to be
used as the primary interface for multicast traffic.
Junos OS supports up to eight VT interfaces configured for multicast in a routing instance to provide
redundancy for MBGP (next-generation) MVPNs. This support is fo... | [] | 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 Redundant Virtual Tunnel Interfaces in MBGP MVPNs",
"Example: Configuring MBGP MVPN Extranets"
] |
primary (VPLS Multihoming) | primary interface-name; | [edit logical-systems logical-system-name routing-instances instance-name protocols vpls multi-
homing active-interface],
[edit logical-systems logical-system-name routing-instances instance-name protocols vpls multi-
homing site site-name active-interface],
[edit routing-instances instance-name protocols vpls multi-ho... | Specify the name of the multihomed interface to be used as the primary interface by the VPLS site.
For FEC 128, use the [edit routing-instances instance-name protocols vpls multi-homing active-interface]
hierarchy level.
Default
If you omit this statement, depending on the order in which interfaces are listed in the P... | [
{
"name": "interface-name",
"desc": "Name of the interface (for example, ge-0/1/0.1)."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Specifying an Interface as the Active Interface"
] |
primary connection (Identity Management Advanced Query) | primary {
address address;
ca-profile ca-profile;
client-id client-id;
client-secret client-secret;
interface interface-name;
routing-instance routing-instance -name;
source source-address;
} | [edit services user-identification identity-management connection] | Configure parameters that the SRX Series Firewall uses to connect to the Juniper Identity Management
Service (JIMS) primary server and authenticate to it to obtain an access token. JIMS requires that the
SRX Series Firewall use OAuth2 to authenticate to it before the SRX Series Firewall can query the JIMS
server for us... | [
{
"name": "address",
"desc": "IP address of the primary server."
},
{
"name": "ca-profile",
"desc": ""
},
{
"name": "CA profile name",
"desc": ""
},
{
"name": "client-id",
"desc": "Client ID for OAuth2 grant"
},
{
"name": "client-secret",
"desc": "Client secre... | 1. services—To view this statement in the configuration.
2. services-control—To add this statement to the configuration.
The remaining statements are explained separately. See CLI Explorer. | Statement introduced in Junos OS Release 15.1X49-D100.
IPv6 address support introduced in Junos OS Release 18.3R1.
Source, interface, and routing-instance options are introduced in Junos OS Release 21.1R1.
Option ca-profile introduced in Junos OS Release 23.2R1. | [
"Understanding Advanced Query Feature for Obtaining User Identity Information from JIMS"
] |
primary | primary path-name; | [edit protocols mpls label-switched-path lsp-name] | Specify the primary path to use for a label switched path (LSP). You can configure only one primary path. | [
{
"name": "path-name",
"desc": "Name of the primary path that you created with the path statement."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring Path Protection in an MPLS Network (CLI Procedure)"
] |
primary | primary interface name; | [edit protocols ptp client interface interface-name],
[edit protocols ptp master interface interface-name] | Configure the primary member link in an aggregated Ethernet bundle to enable Precision Time Protocol
(PTP) over a link aggregation group. PTP primary streams are created on the FPC on which the primary
interface is present. Announce and sync packets are transmitted on this primary PTP Aggregated
Ethernet link. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1. | [
"Configuring Precision Time Protocol",
"Example: Configuring Precision Time Protocol",
"Precision Time Protocol Overview"
] |
primary-data-record-fields | primary-data-record-fields {
name;
} | [edit services inline-monitoring template template-name] | Configure which IPFIX information elements (IEs) to include in the primary data record, which is
exported by the data path and contains the specific properties seen by the data path, either from the
sampled packet or the packet notification header or context. With this statement, each inline-monitoring
instance can exp... | [
{
"name": "name",
"desc": "Configure which IPFIX information elements (IEs) to include in the primary data record. Per RFC 5102, the Common Properties ID (CPID) is an identifier of a set of common properties that is locally unique per observation domain and transport session."
},
{
"name": "cpid-sta... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1.
Statement introduced in Junos Evolved OS Release 22.2R1.
cpid-state-byte, auxiliary_egnh_id, timestamp_low, timestamp_high, cpid-lookup-type-trapcode, cpid-layer3-vpn, cpid-
egress-nexthop-id, and observation-time-nano-sec options introduced in Junos OS Evolved Release 2... | [
"Juniper Resiliency Interface"
] |
primary-dns | primary-dns primary-dns; | [edit access group-profile profile-name client client-name ppp],
[edit access profile profile-name ppp] | Configure the primary Domain Name System (DNS) server. | [
{
"name": "primary-dns",
"desc": "An IPv4 address."
}
] | 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)"
] |
primary-interface (Aggregated Inline Services) | primary-interface interface-name; | [edit interfaces asix aggregated-inline-services-options] | Specify the primary (active) inline services member link in the asi bundle. You must also configure a
secondary (backup) member link on a different MPC with the secondary-interface statement. The
secondary member provides 1:1 redundancy for subscriber service sessions on the primary member link.
The bandwidth configure... | [
{
"name": "interface-name",
"desc": "Name of an inline services physical interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces"
] |
primary-server | primary-server {
address ipv4-address;
login sender-email-address {
password password;
}
} | [edit smtp] | Configure Simple Mail Transfer Protocol (SMTP) primary server for access authorization for SMTP
requests. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement added in Junos OS Release 10.0. | [] |
primary-vlan | primary-vlan vlan-name; | [edit vlans vlan-name] | For a private VLAN (PVLAN), configure the primary VLAN. The primary VLAN is always tagged.
•
If the PVLAN is configured on a single switch, do not assign a tag to the community VLANs.
•
If the PVLAN is configured to span multiple switches, you must assign tags to the community VLANs
also.
For a community VLAN, configur... | [] | system—To view this statement in the configuration.
system–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 9.3.
Statement updated with enhanced ? (CLI completion feature) functionality in Junos OS Release 9.5 for
EX Series switches. | [
"Creating a Private VLAN on a Single QFX Switch without ELS Support",
"Creating a Private VLAN on a Single EX Series Switch without ELS Support (CLI Procedure)",
"Creating a Private VLAN Spanning Multiple QFX Series Switches without ELS Support",
"Example: Configuring a Private VLAN Spanning Multiple EX Serie... |
primary-wins | primary-wins primary-wins; | [edit access group-profile profile-name client client-name ppp],
[edit access profile profile-name ppp] | Configure the primary Windows Internet name server. | [
{
"name": "primary-wins",
"desc": "An IPv4 address."
}
] | 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)"
] |
prioritization | prioritization {
high-priority-inline;
policy [policy-stanza];
} | [edit logical-systems logical -system-name protocols bgp multipath],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp
multipath],
[edit routing-instances routing-instance-name protocols bgp multipath] | Prioritization in multipath BGP involves selecting and load-sharing traffic across multiple equal-cost BGP
paths, including both EBGP and IBGP routes. Prioritization can be used to prioritize critical routes in
BGP multipath computations with low-, medium-, and high-priority queues. Doing so reduces multipath-
calculat... | [
{
"name": "high-priority-",
"desc": ""
},
{
"name": "inline",
"desc": "Routes that have high priority, either from route prioritization, or overridden using multipath priority policy, will have their equal-cost multipath computed immediately rather than being subject queueing for service."
},
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1. | [
"multipath (Protocols BGP)"
] |
priority (Application Identification With Next Gen Services) | priority (high | low); | [edit services application-identification application application-name] | Define the priority of signatures when both a custom signature and predefined signature apply to a
protocol bundle. This statement is valid only if you are running Next Gen Services. If you are not running
Next Gen Services, use the order-priority statement. | [
{
"name": "high",
"desc": "Custom signatures have priority over predefined signatures."
},
{
"name": "low",
"desc": "Predefined signatures have priority over custom signatures. Default: high"
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Releases 19.3R2 and 19.4R1. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
priority (Bootstrap) | priority number; | [edit logical-systems logical-system-name protocols pim rp bootstrap (inet | inet6)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp bootstrap (inet | inet6)],
[edit protocols pim rp bootstrap (inet | inet6)],
[edit routing-instances routing-instance-name protocols p... | Configure the routing device’s likelihood to be elected as the bootstrap router. | [
{
"name": "number",
"desc": "Routing device’s priority for becoming the bootstrap router. A higher value corresponds to a"
},
{
"name": "packets with a priority of 0.)",
"desc": ""
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring PIM Bootstrap Properties for IPv4",
"Configuring PIM Bootstrap Properties for IPv4 or IPv6"
] |
priority (CFM MEP) | priority value; | [edit protocols oam ethernet connectivity-fault-management action-profile action-profile-name
action log-generate-ais] | Configure the 802.1p priority of the AIS packet. | [
{
"name": "value",
"desc": "Priority level. Range: 0 through 7"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Ethernet Alarm Indication",
"Ethernet Alarm Indication"
] |
priority (Chassis Synchronization Source) | priority number; | [edit chassis synchronization source (bits | gps)],
[edit chassis synchronization source interfaces] | Configure a priority level for the interface specified as a candidate source. When not specified, gps has
higher default priority than bits, and bits has higher default priority than other Gigabit Ethernet, 10-
Gigabit Ethernet, T1, or E1 clock sources, which have the lowest default priority. | [
{
"name": "number",
"desc": "Priority level between 1 and 5."
}
] | 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. | [
"External Clock Synchronization Overview for ACX Series Routers",
"Configuring External Clock Synchronization for ACX Series Routers",
"Synchronous Ethernet Overview",
"show chassis synchronization"
] |
priority (Clock Synchronization) | priority number; | [edit chassis synchronization source interfaces (external-a | external-b | interface interface-
name)],
[edit chassis synchronization source interfaces (external | interface interface-name)],
[edit chassis synchronization source interfaces (external-0/0 | external-1/0 | interface
interface-name)] | Configure the priority of a clock source in relationship to other clock sources to define a network
synchronization flow and to help prevent timing loops.
When the priority is not specified, the external-a interface has higher default priority than the external-b
interface, and the external-b interface has higher defau... | [
{
"name": "number",
"desc": "Set the priority level of the clock source. Range: 1 through 5"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2R4. | [] |
priority (DDoS) | priority level; | For MX Series routers, T4000 routers, and EX9200 switches:
[edit system ddos-protection protocols protocol-group packet-type]
For ACX Series routers, PTX Series routers, and QFX Series switches:
[edit system ddos-protection protocols protocol-group packet-type] | Configure the priority for the packet type within the parent protocol group. In the event of downstream
traffic congestion, high priority packets are provided bandwidth before medium priority packets. In turn,
medium priority packets are provided bandwidth before low priority packets. Packets are dropped when
there is ... | [
{
"name": "level",
"desc": "Priority of the packet type, low, medium, or high."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Control Plane DDoS Protection Aggregate or Individual Packet Type Policers"
] |
priority (Diameter Network Element) | priority priority-value; | [edit access diameter network-element element-name peer peer-name] | Set the priority for a peer within a Diameter network element. A peer with a lower number has a higher
priority. For load balancing, configure the peers with the same priority. | [
{
"name": "priority-value",
"desc": "Priority for the peer within the network element. Range: 1 through 65,535"
}
] | 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. | [] |
priority (Diameter Peer) | priority priority-value; | [edit diameter network-element element-name peer peer-name] | Set the priority for a peer within a Diameter network element. A peer with a higher number has a higher
priority. | [
{
"name": "priority-value",
"desc": "Priority for the peer within the network element."
}
] | 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"
] |
priority (Dynamic Schedulers) | priority (priority-level | $junos-cos-scheduler-priority); | [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] | Specify packet-scheduling priority value in a dynamic profile. | [
{
"name": "priority-level",
"desc": "one of the following packet-scheduling priority values:"
},
{
"name": "low",
"desc": "Scheduler has low priority."
},
{
"name": "medium-low",
"desc": "Scheduler has medium-low priority."
},
{
"name": "medium-high",
"desc": "Scheduler h... | 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 $junos-cos-scheduler-priority predefined variable introduced in Junos OS Release 9.4. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Schedulers in a Dynamic Profile for Subscriber Access",
"Dynamic Variables Overview"
] |
priority (Fabric Priority) | priority (high | low); | [edit class-of-service forwarding-classes class class-name queue-num queue-number],
[edit class-of-service forwarding-classes queue queue-number class-name] | For M320 routers, MX Series routers, T Series routers and EX Series switches only, specify a fabric
priority value.
The two hierarchy levels are mutually exclusive. To configure up to eight forwarding classes with one-to-
one mapping between forwarding classes and output queues, include this statement at the [edit clas... | [
{
"name": "low",
"desc": "Forwarding class’s fabric queuing has low priority."
},
{
"name": "high",
"desc": "Forwarding class’s fabric queuing has high priority."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
[edit class-of-service forwarding-classes class class-name queue-num queue-number] hierarchy level added in
Junos OS Release 8.1. | [
"Forwarding Classes and Fabric Priority Queues",
"Configuring Up to 16 Custom Forwarding Classes"
] |
priority (Fabric Queues, Schedulers) | priority (high | low)scheduler scheduler-name; | [edit class-of-service fabric scheduler-map] | Define Fabric traffic priority. For M320, MX Series, T Series routers and EX Series switches only, specify
the fabric priority with which a scheduler is associated.
For a scheduler that you associate with a fabric priority, you cannot include the buffer-size, transmit-rate,
or priority statements at the [edit class-of-... | [
{
"name": "high",
"desc": "Scheduler has high priority."
},
{
"name": "low",
"desc": "Scheduler has low priority."
}
] | 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. | [
"Associating Schedulers with Fabric Priorities"
] |
priority (FIP) | priority priority; | [edit fc-fabrics fc-fabric-name protocols fip],
[edit fc-fabrics fc-fabric-name protocols fip interface interface-name] | Sets the global or interface-specific priority value associated with the switch FCF-MAC. CNAs use the
priority value to determine the switch with which they will perform FIP FLOGI. The lower the value, the
higher the priority. The switch advertises this value to the server ENodes on the FCoE network. A
priority value s... | [
{
"name": "priority",
"desc": "Value that determines the FCF an ENode selects to perform FIP FLOGI. The lower the priority"
}
] | storage—To view this statement in the configuration.
storage-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Overview of FIP",
"Configuring FIP on an FCoE-FC Gateway"
] |
priority (Management Traffic) | priority (low | medium | high) | [edit system management-traffic protocol protocol-name | You can prioritize the internal traffic between the Routing Engine and the Packet Forwarding Engine or
other Routing Engine based on the packet classification. This enhancement increases the internal and
management traffic performance and provides better packet processing. In addition, this enhancement
can introduce mo... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.4R1. | [] |
priority (OAM Connectivity-Fault Management) | priority number; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain md-namemaintenance-
association ma-name mep mep-id]
For EX Series Switches:
[edit protocols oam ethernet connectivity-fault-management maintenance-domaindomain-namemaintenance-
association ma-name mepmep-id] | IEEE 802.1p priority bits used by the continuity check messages. | [
{
"name": "number",
"desc": "Configure the IEEE 802.1p priority bits to be used in the VLAN header of the CFM packets."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [
"Configuring Connectivity Fault Management (CFM)"
] |
priority (PIM Interfaces) | priority number; | [edit logical-systems logical-system-name protocols pim interface (Protocols PIM) interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
interface (Protocols PIM) interface-name],
[edit protocols pim interface (Protocols PIM) interface-name],
[edit routing-ins... | Configure the routing device’s likelihood to be elected as the designated router. DR priority is specific to
PIM sparse mode; as per RFC 3973, PIM DR priority cannot be configured explicitly in PIM Dense Mode
(PIM-DM) in IGMPv2 – PIM-DM only support DRs with IGMPv1. | [
{
"name": "number",
"desc": "Routing device’s priority for becoming the designated router. A higher value corresponds to a"
}
] | 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 Interface Priority for PIM Designated Router Selection"
] |
priority (PIM RPs) | priority number; | [edit logical-systems logical-system-name protocols pim rp bidirectional address address],
[edit logical-systems logical-system-name routing-instances instance-name protocols pim rp
bidirectional address address],
[edit protocols pim rp bidirectional address address],
[edit protocols pim rp local family (inet | inet6)... | For PIM-SM, configure this routing device’s priority for becoming an RP.
For bidirectional PIM, configure this RP address’ priority for becoming an RP.
The bootstrap router uses this field when selecting the list of candidate rendezvous points to send in the
bootstrap message. A smaller number increases the likelihood ... | [
{
"name": "number",
"desc": "Priority for becoming an RP. A lower value corresponds to a higher priority."
}
] | 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 bidirectional RP addresses introduced in Junos OS Release 12.1. | [
"Configuring Local PIM RPs",
"Example: Configuring Bidirectional PIM"
] |
priority (PoE) | priority (high | low); | [edit poe interface (all | interface-name)] | Sets the priority of individual ports. When it is not possible to maintain power to all connected ports,
lower-priority ports are powered off before higher priority ports. When a new device is connected on a
higher-priority port, a lower-priority port will be powered off automatically if available power is
insufficient... | [
{
"name": "value",
"desc": "high or low:"
},
{
"name": "high",
"desc": "Specify that this port is to be treated as high priority in terms of power allocation"
},
{
"name": "low",
"desc": "Specify that this port is to be treated as low priority in terms of power allocation."
}
] | 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. | [] |
priority (policy-options) | policy-options {
policy-statement policy-name {
term term-name {
from {
match-conditions;
route-filter destination-prefix match-type;
}
then {
priority high | low;
}
}
} | [edit logical-systems name policy-options policy-statementpolicy-name term term-name then],
[edit logical-systems name policy-options policy-statementpolicy-name then],
[edit policy-options policy-statementpolicy-name term term-name then],
[edit policy-options policy-statementpolicy-name then] | Sets the priority for route installation. You can choose a relative priority of high, low , or medium to ensure
that high priority IGP and LDP routes are updated in the FIB (forwarding table) before medium and low
priority routes. Routes are placed in different priority queues according to the priority. Any routes that... | [
{
"name": "high",
"desc": "Set priority to high."
},
{
"name": "low",
"desc": "Set priority to low."
},
{
"name": "medium",
"desc": "Set priority to medium."
}
] | 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. | [
"Prefix Prioritization Overview",
"Example: Configuring the Priority for Route Prefixes in the RPD Infrastructure"
] |
priority (Power over Ethernet) | priority (low | high); | [edit poe interface (interface-name | all | all-extended)] | Set the power priority for individual interfaces when there is insufficient power for all PoE interfaces. If
the switch needs to shut down powered devices because PoE demand exceeds the PoE budget, low-
priority devices are shut down before high-priority devices. Among interfaces that have the same
assigned priority, p... | [
{
"name": "high",
"desc": "Specifies that this interface is to be treated as high-priority in terms of power allocation. If the"
},
{
"name": "low",
"desc": "Specifies that this interface is to be treated as low-priority in terms of power allocation. If the"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge. | [
"Example: Configuring PoE Interfaces with Different Priorities on an EX Series Switch",
"Configuring PoE Interfaces on EX Series Switches",
"Configuring Power over Ethernet in a Junos Fusion"
] |
priority (Protocols MPLS) | priority setup-priority reservation-priority; | [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 protocols mpls],
[edit protocols mpls label-sw... | Configure the setup priority and reservation priority for an LSP. If insufficient link bandwidth is available
during session establishment, the setup priority is compared with other setup priorities for established
sessions on the link to determine whether some of them should be preempted to accommodate the new
sessio... | [
{
"name": "reservation-priority",
"desc": "Reservation priority, used to keep a reservation after it has been set up. A smaller"
},
{
"name": "setup-priority",
"desc": "Setup priority."
}
] | 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 Priority and Preemption for LSPs"
] |
priority (Protocols OAM) | priority priority-value; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain md-name maintenance-
association ma-name mep mep-id remote-mep remote-mep-id sla-iterator-profile profile-namesla-
iterator-profile] | Configure the priority of the iterator profile, which is the vlan-pcp value that is sent in the Y.1731 data
frames. | [
{
"name": "priority-value",
"desc": "Priority value, which is the vlan-pcp value that is sent in the Y.1731 data frames."
}
] | Configure—To enter configuration mode.
Control—To modify any configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configure a Remote MEP with an Iterator Profile"
] |
priority (Protocols Router Discovery) | priority number; | [edit logical-systems logical-system-name protocols router-discovery address address],
[edit protocols router-discovery address address] | Specify the preference of the address to become a default router. This preference is set relative to the
preferences of other router addresses on the same subnet. | [
{
"name": "number",
"desc": "Preference of the addresses for becoming the default router. A higher value indicates that the"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Understanding the ICMP Protocol for Discovering Gateways to Other Networks",
"Example: Configuring the ICMP Protocol for Discovering Gateways to Other Networks"
] |
priority (Protocols RSVP) | priority setup-priority reservation-priority; | [edit logical-systems logical-system-name protocols rsvp interface interface-name link-
protection],
[edit logical-systems logical-system-name protocols rsvp interface interface-name link-
protection bypass bypass-name],
[edit protocols rsvp interface interface-name link-protection],
[edit protocols rsvp interface inte... | Configure the setup priority and reservation priority for a bypass LSP. If insufficient link bandwidth is
available during session establishment, the setup priority is compared with other setup priorities for
established sessions on the link to determine whether some of them should be preempted to
accommodate the new s... | [
{
"name": "reservation-priority",
"desc": "Reservation priority, used to keep a reservation after it has been set up. A smaller"
},
{
"name": "setup-priority",
"desc": "Setup priority."
}
] | 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. | [] |
priority (Protocols STP) | priority interface-priority; | [edit logical-systems logical-system-name protocols (mstp | rstp | vstp) interface interface-name],
[edit logical-systems logical-system-name protocols mstp msti msti-id interface interface-name],
[edit logical-systems logical-system-name protocols vstp vlan vlan-id interface interface-name],
[edit logical-systems log... | For Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol
(VSTP), or Multiple Spanning Tree Protocol (MSTP), specifies the interface priority to control which
interface is elected as the root port. The interface priority must be set in increments of 16.
Default
The default value... | [
{
"name": "priority",
"desc": "(Optional) Interface priority. The interface priority must be set in increments of 16."
}
] | 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.
Statement updated in Junos OS Release 9.4 for EX Series switches to add VSTP support.
Support for logical systems added in Junos OS Release 9.6. | [
"Understanding STP"
] |
priority (Protocols VRRP) | priority priority; | [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... | Configure a Virtual Router Redundancy Protocol (VRRP) device’s priority for becoming the primary
default device. The device with the highest priority within the group becomes the primary. VRRP is
designed to eliminate the single point of failure inherent in the static default routed environment. VRRP
specifies an elect... | [
{
"name": "priority",
"desc": "Device’s priority for being elected to be the primary device in the VRRP group. A larger value indicates a higher priority for being elected. Range: 0 through 255 Default: 100. If two or more devices have the highest priority in the VRRP group, the device with the VRRP inter... | 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 Basic VRRP Support",
"Understanding VRRP on SRX Series Devices",
"Example: Configuring VRRP/VRRPv3 on Chassis Cluster Redundant Ethernet Interfaces"
] |
priority (RADIUS Network Elements) | priority priority; | [edit access radius network-element name server name] | Configure a priority for each RADIUS server in the network element. You can have multiple servers with
the same priority in a network element. All access requests are load balanced among the highest priority
servers. If all the servers with the highest priority in the network element fail, then requests are load
balanc... | [
{
"name": "priority",
"desc": "Relative priority for a RADIUS server. Range: 1 through 16."
}
] | 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"
] |
priority (Redundant Power System) | priority (0|1|2|3|4|5|6); | [edit redundant-power-system member]
[edit redundant-power-system member member-number] | Configure the backup of any switch connected to the Redundant Power System (RPS) using the CLI on
each switch. The determines the order in which the RPS supplies backup power to the switches
connected to the RPS. 6 is the highest priority and 1 is lowest. Zero means off or no RPS backup.
If the switch is not reconfigur... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [] |
priority (Schedulers) | priority priority-level; | [edit class-of-service schedulers scheduler-name] | Specify the packet-scheduling priority value. | [
{
"name": "priority-level can be one of the following:",
"desc": ""
},
{
"name": "low",
"desc": "Scheduler has low priority."
},
{
"name": "low-medium",
"desc": "Scheduler has low-medium priority."
},
{
"name": "low-high",
"desc": "Scheduler has low-high priority."
},
... | 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.
low-latency support introduced for Junos OS Evolved Release 23.4R1.
low-high and low-mediumsupport introduced for Junos OS Evolved Release 24.4R1.
Platform-Specific Behavior
Use Feature Explorer to confirm platform and release support for scheduling priority.
Use the f... | [
"Configuring Schedulers for Priority Scheduling"
] |
priority1 | priority1 priority1-value; | [edit protocols ptp] | Configure the priority as one of the following:
•
In the timeReceiver, the priority value is set to select the best timeTransmitter clock. Note that in
order to select a particular timeTransmitter clock, the priority value in the timeTransmitter clock’s
announce message must be equal to or lower than the configured pri... | [
{
"name": "priority1-value",
"desc": "The priority value of the clock."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring Precision Time Protocol",
"Precision Time Protocol Overview",
"IEEE 1588v2 Precision Timing Protocol (PTP)"
] |
priority2 | priority2 priority2-value; | [edit protocols ptp] | Configure the priority2 value. This value is used to differentiate and prioritize the timeTransmitter clocks
to avoid confusion when the priority1-value is the same for different timeTransmitter clocks in a network.
Note that the lower value takes precedence. | [
{
"name": "priority2-value",
"desc": "The priority value of the clock."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring Precision Time Protocol",
"Example: Configuring Precision Time Protocol",
"Precision Time Protocol Overview",
"IEEE 1588v2 Precision Timing Protocol (PTP)"
] |
priority | priority number; | [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] | Configure a switch’s priority for becoming the primary default routing platform. The routing platform
with the highest priority within the group becomes the primary. | [
{
"name": "number",
"desc": "Routing platform’s priority for being elected to be the primary router in the VRRP group. A"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Configuring VRRP for IPv6 (CLI Procedure)"
] |
priority-cost (VRRP) | priority-cost priority; | [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-
group group-id track interface interface-name],
[edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-
group group-id track interface interface-name],
[edit logical-systems logical-syste... | Configure a Virtual Router Redundancy Protocol (VRRP) router’s priority cost for becoming the primary
default router. The router with the highest priority within the group becomes the primary. | [
{
"name": "priority",
"desc": "The value subtracted from the configured VRRP priority when the tracked interface or route is"
}
] | 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 Release 12.2 for ACX2000 Universal Metro Routers. | [
"Configuring a Logical Interface to Be Tracked for a VRRP Group"
] |
priority-flow-control | priority-flow-control {
no-auto-negotiation;
} | [edit protocols dcbx interface (all | interface-name)] | Disable auto-negotiation of priority-based flow control (PFC) on one or more Ethernet interfaces.
DCBX controls the operational state of PFC on each interfaces where PFC is enabled by configuration.
Auto-negotiation enables PFC on an interface only if the switch and the peer device connected to the
switch both support ... | [
{
"name": "no-auto-negotiation",
"desc": "Disable automatic negotiation of PFC."
}
] | 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. | [
"Configuring CoS PFC (Congestion Notification Profiles)",
"Configuring Priority-Based Flow Control for an EX Series Switch (CLI Procedure)",
"Configuring DCBX Autonegotiation",
"Example: Configuring CoS PFC for FCoE Traffic",
"Understanding Data Center Bridging Capability Exchange Protocol for EX Series Swi... |
priority-hold-time | priority-hold-time seconds; | [edit logical-systems logical-system-name protocols (mstp | rstp)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(mstp | rstp)],
[edit protocols (mstp | rstp)],
[edit routing-instances routing-instance-name protocols (mstp | rstp)] | Specify the number of seconds to hold before switching to the primary priority when the first core
domain comes up. | [
{
"name": "seconds",
"desc": "Number of seconds to hold before switching to primary priority."
}
] | 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. | [] |
priority-hold-time | priority-hold-time seconds; | [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-
group group-id track],
[edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-
group group-id track],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit... | Configure a Virtual Router Redundancy Protocol (VRRP) router’s priority hold time to define the
minimum length of time that must elapse between dynamic priority changes. If the dynamic priority
changes because of a tracking event, the priority hold timer begins running. If another tracking event or
manual configuration... | [
{
"name": "seconds",
"desc": "Minimum length of time that must elapse between dynamic priority changes."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Configuring a Logical Interface to Be Tracked for a VRRP Group"
] |
priority-override (Event Policy) | priority-override {
facility facility-type;
severity severity-level;
} | [edit event-options policy policy-name then] | Configure an event policy to override the default system log priority of the triggering event so that the
system logs the event with a different facility type, severity level, or both. If you configure multiple event
policies to override the priority of the same event, the event is logged based on the priority set by t... | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 12.1. | [
"System Log Priority for Events in Event Policies"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.