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 |
|---|---|---|---|---|---|---|---|
protocol (Dynamic Schedulers) | protocol (any | non-tcp | tcp); | [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name drop-profile-map] | Specify the protocol type for the specified scheduler in a dynamic profile. | [
{
"name": "any",
"desc": "Accept any protocol type."
},
{
"name": "non-tcp",
"desc": "Accept any protocol type other than TCP/IP."
},
{
"name": "tcp",
"desc": "Accept only TCP/IP protocol."
}
] | 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. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Schedulers in a Dynamic Profile for Subscriber Access"
] |
protocol (early-aging) | protocol name {
cutoff-time {
(percent percent | seconds seconds);
}
} | [edit security flow aging early-aging] | Set of attributes that define early-ageout by-protocol. | [
{
"name": "name",
"desc": "Match IP protocol type"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | This statement is introduced in Junos OS Release 23.4R1. | [] |
protocol (Firewall Filter) | protocol (tcp|udp); | [edit firewall family family-name filter filter-name term term-name from ip-version ip-version] | Configure the protocol field of IPv4 or the next-header field of the IPv6 address. | [
{
"name": "tcp",
"desc": "Transmission Control Protocol."
},
{
"name": "udp",
"desc": "User Datagram Protocol."
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1R1. | [
"Firewall Filter Match Conditions for MPLS-Tagged IPv4 or IPv6 Traffic"
] |
protocol (Flow Descriptions) | protocol number; | [edit unified-edge pcef flow-description flow-identifier],
[edit services pcef flow-description flow-identifier] | Specify a protocol type to identify the subscriber traffic that you want the service data flow (SDF) filter
to detect. If you specify the protocol statement, you must specify a protocol number.
If you are using Junos OS Subscriber Aware, specify the protocol type at the [edit unified-edge pcef flow-
description flow-id... | [
{
"name": "number",
"desc": "Number that specifies the IP protocol type. Range: 1 through 255"
}
] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef flow-description flow-identifier] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series. | [
"Configuring Service Data Flow Filters",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Understanding Application-Aware Policy Control for Subscriber Management"
] |
protocol (Host Outbound Traffic) | protocol {
isis-over-gre {
dscp-code-point dscp-code-point;
}
} | [edit class-of-service host-outbound-traffic],
[edit dynamic-profiles name class-of-service host-outbound-traffic] | Set the DSCP code point for IS-IS traffic originating on the host and being sent over a GRE tunnel. By
default, this DSCP code point is 000000, which is normally mapped to best-effort forwarding class and can
lead to packet drops during congestion. Set this DSCP code point to enable traffic prioritization for IS-IS
tra... | [] | interface | Statement introduced in Junos OS Release 17.3. | [] |
protocol (IPsec) | protocol (ah | esp | bundle); | [edit services ipsec-vpn ipsec proposal proposal-name],
[edit services ipsec-vpn rule rule-name term term-name then manual direction direction] | Define an IPsec protocol for a dynamic or manual SA. | [
{
"name": "ah",
"desc": "(Not supported on MS-MPCs and MS-MICs on MX Series routers) Use the Authentication Header"
},
{
"name": "esp",
"desc": "Use the Encapsulating Security Payload protocol."
},
{
"name": "bundle",
"desc": "(Not supported on MS-MPCs and MS-MICs on MX Series router... | 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 Security Associations"
] |
protocol (Junos OS) | protocol (ah | esp | bundle); | [edit security ipsec proposal ipsec-proposal-name],
[edit security ipsec security-association sa-name manual direction (inbound | outbound |
bidirectional)] | Define the IPsec protocol for a manual or dynamic SA.
NOTE: The Junos OS supports only encapsulating security payload (ESP) when you use
tunnel mode.
In transport mode, the Junos OS does not support authentication header (AH) and ESP
header bundles.
In transport mode, the Junos OS supports only Border Gateway Protocol... | [
{
"name": "ah",
"desc": "Authentication Header protocol"
},
{
"name": "bundle",
"desc": "AH and ESP protocols"
},
{
"name": "esp",
"desc": "ESP protocol (the tunnel statement must be included at the [edit security ipsec security-association"
},
{
"name": "sa-name mode hierarc... | 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. | [
"Example: Using IPsec to Protect BGP Traffic",
"Configuring Manual IPsec Security Associations for an ES PIC",
"Configuring the Protocol for a Dynamic IPsec SA"
] |
protocol (Junos-FIPS Software) | protocol esp; | [edit security ipsec internal security-association manual direction] | The protocol used for the internal Routing-Engine–to–Routing-Engine IPsec security association (SA)
configuration. | [] | Crypto Officer—To add and view this statement in the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IPsec for Enabling Internal Communications Between Routing Engines for Junos OS in",
"FIPS Mode"
] |
protocol (OVSDB) | protocol protocol {
port number;
} | [edit protocols ovsdb controller] | Configure the security protocol that protects the connection between a Juniper Networks device that
supports the Open vSwitch Database (OVSDB) management protocol and a software-defined
networking (SDN) controller.
The Secure Sockets Layer (SSL) connection requires a private key and certificates, which must be stored
i... | [
{
"name": "protocol",
"desc": "Establish a secure connection to the SDN controller, using SSL or TCP. NOTE: SSL is the only supported connection protocol. Default: ssl The remaining statement is explained separately. See CLI Explorer."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1R2. | [
"Understanding How to Set Up OVSDB Connections on a Juniper Networks Device"
] |
protocol (Protocols OpenFlow) | protocol tcp {
port port;
} | [edit protocols openflow switch switch-name controller] | Specify the connection protocol that the OpenFlow virtual switch uses to connect to the OpenFlow
controller. | [
{
"name": "tcp",
"desc": "Establish a TCP connection to the controller. The remaining statement is explained separately. See CLI Explorer."
}
] | 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. | [
"Understanding Support for OpenFlow on Devices Running Junos OS"
] |
protocol (Rewrite Rules) | protocol protocol-types; | [edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules exp
rewrite-name],
[edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules dscp
rewrite-name],
[edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules dscp-
ipv6 rewr... | Apply a rewrite rule to MPLS packets only, and write the CoS value to MPLS headers only; or apply a
rewrite rule to MPLS and IPv4 or IPv6 packets, and write the CoS value to MPLS and IPv4 or IPv6
headers.
On segment routing LSPs, applying an EXP rewrite rule to the egress interface on the ingress (provider
edge) route... | [
{
"name": "protocol-types can be one of the following:",
"desc": ""
},
{
"name": "mpls-any",
"desc": "Apply a rewrite rule to MPLS packets and write the CoS value to MPLS headers only."
},
{
"name": "mpls-inet-both",
"desc": "Applies the CoS value to the MPLS and IPv4 headers of VPN ... | 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.
Option for dscp and inet-prec introduced in Junos OS Release 8.4.
Option for dscp-ipv6 introduced in Junos OS Release 10.4R2. | [
"Rewriting MPLS and IPv4 Packet Headers"
] |
protocol (Schedulers) | protocol (any | non-tcp | tcp); | [edit class-of-service schedulers scheduler-name drop-profile-map] | Specify the protocol type for the specified scheduler. | [
{
"name": "any",
"desc": "Accept any protocol type."
},
{
"name": "non-tcp",
"desc": "Accept any protocol type other than TCP/IP."
},
{
"name": "tcp",
"desc": "Accept TCP/IP protocol type."
}
] | 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 Schedulers"
] |
protocol (Security Destination NAT) | protocol [protocol-name-or-number]; | [edit security nat destination rule-set rule-set-name rule rule-name match] | Specify an IP protocol to match the rule. You can configure multiple protocol names or protocol
numbers. | [
{
"name": "protocol-name-or-number",
"desc": "Name or number of the specific protocol."
}
] | 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. | [] |
protocol (Security Forwarding Options) | protocol protocol; | [edit security forwarding-options mirror-filter filter-name] | Specify the networking protocol name or number to be matched for mirroring. | [
{
"name": "protocol-name",
"desc": "Networking protocol name or number. The following text values are supported. For a complete list of possible numeric values, see RFC 1700, Assigned Numbers (for the Internet Protocol Suite)."
},
{
"name": "ah",
"desc": ""
},
{
"name": "IP Security Auth... | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [] |
protocol (Security IDP Signature Attack) | protocol {
icmp (Security IDP Signature Attack) {
checksum-validate {
match (equal | greater-than | less-than | not-equal);
value checksum-value;
}
code {
match (equal | greater-than | less-than | not-equal);
value code-value;
}
... | [edit security idp custom-attack attack-name attack-type signature] | Specify a protocol to match the header information for the signature attack. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. Statement modified in Junos OS Release 12.3X48-D25
to add ICMPv6 protocol support. | [] |
protocol (Security Source NAT) | protocol [protocol-name-or-number]; | [edit security nat source rule-set rule-set-name rule rule-name match] | Specify an IP protocol to match the rule. You can configure multiple protocol names or protocol
numbers. | [
{
"name": "protocol-name-or-number",
"desc": "Name or number of the specific protocol."
}
] | 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. | [] |
protocol (Server MEP) | protocol (l2circuit | l2vpn | ethernet) {
interface interface-name;
} | [edit protocols oam ethernet connectivity-fault-management] | Configure the protocol as Layer 2 circuit, Layer 2 VPN, or Ethernet and associate the interface to the
protocol that needs to be monitored for ETH-AIS. | [
{
"name": "l2circuit",
"desc": "Configure the protocol for the server MEP as Layer 2 circuit."
},
{
"name": "l2vpn",
"desc": "Configure the protocol for the server MEP as Layer 2 VPN."
},
{
"name": "ethernet",
"desc": "Configure the protocol for the server MEP as Ethernet."
},
{
... | 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"
] |
protocol (Subscriber Secure Policy) | protocol protocol; | [edit services radius-flow-tap policy policy-name inet drop-policy rule-name from],
[edit services radius-flow-tap policy policy-name inet6 drop-policy rule-name from] | Specify the match IP protocol type for the radius-flow-tap policy. | [
{
"name": "protocol",
"desc": "Protocol for the IPv4 or IPv6 address for the radius-flow-tap policy."
}
] | flow-tap—To view this statement in the configuration.
flow-tap-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Subscriber Secure Policy Overview",
"Configuring RADIUS-Initiated Subscriber Secure Policy Mirroring Overview"
] |
protocol | protocol protocol; | [edit services application-identification nested-application name] | Identify the protocol that is monitored to identify nested applications. HTTP is supported. | [
{
"name": "protocol",
"desc": "An agreed-upon or standardized method for transmitting data and establishing communications between different devices. The value http is supported."
}
] | system—To view this statement in the configuration.
system control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Application Identification for Nested Applications"
] |
protocol | protocol (cdp | elmi | gvrp | ieee8021x | ieee8023ah | lacp | lldp | mmrp | mvrp | pvstp | stp |
udld | vtp); | [edit logical-systems name protocols layer2-control mac-rewrite interface interface-
name],
[edit protocols layer2-control mac-rewrite interface interface-name] | Configure the protocol to be tunneled on an interface using Layer 2 protocol tunneling (L2PT). To enable
tunneling multiple protocols, include multiple protocol statements.
You can tunnel different protocols listed in the Options section on different types of devices. The Syntax
and Release Information sections list th... | [
{
"name": "all",
"desc": "Tunnel all supported Layer 2 control protocols."
},
{
"name": "cdp",
"desc": "Tunnel the Cisco Discovery Protocol (CDP)."
},
{
"name": "elmi",
"desc": "Tunnel Ethernet Local Management Interface (E-LMI) packets."
},
{
"name": "gvrp",
"desc": "Tun... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
Support for PVST/PVST+ introduced in Junos OS Release 13.3 for MX Series routers and EX9200
switches.
Support for E-LMI, IEEE 802.1X, MMRP, and UDLD introduced in Junos OS Release 17.3R1 for EX4300
switches.
Support for E-LMI, GVRP, IEEE 802.1x, IEEE 802.3AH, LACP, LLDP, MM... | [
"Understanding Layer 2 Protocol Tunneling",
"Configuring Layer 2 Protocol Tunneling"
] |
protocol-binding | protocol-binding {
application application-name;
icmp;
icmpv6;
ip (Security IDP Custom Attack) {
protocol-number transport-layer-protocol-number;
}
ipv6 {
protocol-number transport-layer-protocol-number;
}
rpc {
program-number rpc-program-number;
}
tcp (Se... | [edit security idp custom-attack attack-name attack-type chain],
[edit security idp custom-attack attack-name attack-type signature] | Select a protocol that the attack uses to enter your network. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
protocol-command | protocol-command object-name {
value [value];
} | [edit security utm default-configuration]
[edit security utm custom-objects] | Different protocols use different commands to communicate between servers and clients. By blocking or
allowing certain commands, traffic can be controlled on the protocol command level. | [
{
"name": "object-name",
"desc": "Name of the command-list object."
},
{
"name": "value value",
"desc": "Value of the command-list object. You can configure multiple values separated by spaces"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Unified Threat Management Overview"
] |
protocol-down | protocol-down; | [edit protocols oam ethernet link-fault-management event] | Configure the upper layer indication of a protocol down event. When the protocol-down statement is
included, the protocol down event triggers the action specified under the action statement. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in JUNOS Release 9.4 . | [
"Example: Configure Ethernet OAM Link Fault Management",
"Configure Ethernet OAM Link Fault Management"
] |
protocol-master | protocol-master (inet | inet6); | [edit bridge-domains name forwarding-options dhcp-relay dhcpv6 group group-name dual-stack-group
dual-stack-group-name],
[edit bridge-domains name forwarding-options dhcp-relay dual-stack-group dual-stack-group-name],
[edit forwarding-options dhcp-relay dhcpv6 group name dual-stack-group dual-stack-group-name],
[edit ... | Select family as protocol primary. In some customer use cases, CPE devices have reachability to multiple
BNG routers for load sharing. The CPE’s DHCP client broadcasts a DHCP protocol handshake to the
reachable routers; more than one router may respond. In a DHCP dual-stack environment, the DHCPv4
and DHCPv6 protocol h... | [
{
"name": "inet",
"desc": "INET family has protocol primary behavior."
},
{
"name": "inet6",
"desc": "INET6 family has protocol primary behavior."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3. | [
"Configuring Access Profile Options for Interactions with RADIUS Servers",
"Attaching Access Profiles to DHCP Subscriber Interfaces or DHCP Client Interfaces",
"Configuring Access Components for the DHCP Layer 3 Wholesale Network Solution",
"Configuring Access Components for the PPPoE Wholesale Network Soluti... |
protocol-name | protocol-name protocol-name {
tunable-name tunable-name {
tunable-value protocol-value;
}
} | [edit security idp sensor-configuration detector] | Specify the name of the protocol to be used to configure each of the protocol detector engines. | [
{
"name": "protocol-name",
"desc": "Name of the specific protocol."
}
] | 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. Support. | [] |
protocol-origin | protocol-origin {
bgp;
cli;
pcep;
} | [edit policy-options policy-statement name from traffic-engineering spring-te] | Specify protocol originating the SPRING-TE policy candidate path. | [
{
"name": "bgp",
"desc": "SPRING-TE policy candidate path originated by BGP"
},
{
"name": "cli",
"desc": "SPRING-TE policy candidate path originated by cli"
},
{
"name": "pcep",
"desc": "SPRING-TE policy candidate path originated by PCEP"
}
] | routing | [
"Link-State Distribution using BGP"
] | |
protocol-version | protocol-version (all | tls1 | tls11 | tls12 | tls12-and-lower | tls13); | [edit services ssl termination profile profile-name]
[edit services ssl initiation profile profile-name] | Specify the accepted SSL protocol version.
You can specify the SSL/TLS protocol version the SRX Series Firewall uses to negotiate in SSL
connections. | [
{
"name": "all",
"desc": "Accept all versions of TLS. This is enabled by default."
},
{
"name": "TLS version 1.0",
"desc": "Accept TLS version 1.0. It provides secure communication over networks by"
},
{
"name": "TLS version 1.1",
"desc": "Accept TLS version 1.1. This enhanced versio... | 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. The tls11 and tls12 options are introduced in
15.1X49-D30. Starting in Junos OS Release 21.2R1, on SRX Series Firewalls, SSL proxy supports TLS
version 1.3. | [
"Firewall User Authentication Overview",
"SSL Proxy Overview"
] |
protocols (DDoS) (ACX Series, PTX Series, and QFX Series) | protocols{
arp;
bfd;
bfdv6;
bgp;
custom;
sample;
dhcpv4;
dhcpv6;
dhcpv4v6;
l2tp;
ppp;
pppoe;
} | [edit system ddos-protection] | arp or
Configure ARP traffic
bfd
Configure BFD traffic
bfdv6
BFDv6 traffic
bgp
Configure BGP traffic
custom
Configure CUSTOM traffic
sample
Configure Sampling traffic
dhcpv4
Configure DHCPv4 traffic
dhcpv6
Configure DHCPv6 traffic
dhcpv4v6
Configure DHCPv4/v6 traffic
l2tp
Configure L2TP traffic.
ppp
Configure PPP traff... | [
{
"name": "aggregate",
"desc": "Configure parameters for the policer that polices all control packets belonging to the specified protocol as a combined group. An aggregate policer exists for all protocol groups. NOTE: ACX Series routers support only the aggregate policer for the supported protocol groups."
... | 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. | [
"Control Plane Distributed Denial-of-Service (DDoS) Protection Overview",
"Configuring Control Plane DDoS Protection"
] |
protocols (DDoS) | protocols protocol-group (aggregate | packet-type) {
bandwidth packets-per-second;
burst size;
bypass-aggregate;
disable-fpc;
disable-logging;
disable-routing-engine;
flow-detection-mode (automatic | off | on);
flow-detect-time seconds;
flow-level-bandwidth {
logical-interfac... | [edit system ddos-protection] | (MX Series routers with only MPCs or LC9600 or LC4800, T4000 Core Routers with only FPC5s, or
EX9200 switches) Configure control plane DDoS protection policers for all supported packet types
within a protocol group or for a particular supported packet type within a protocol group.
Starting in Junos OS Release 22.2R1, w... | [
{
"name": "aggregate",
"desc": "Configure the policer to monitor all control packets within the protocol group. You can configure an aggregate policer for any protocol group."
},
{
"name": "packet-type",
"desc": "(Optional) Name of the control packet type to be policed. You can configure a speci... | 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.
Support for Enhanced Subscriber Management added in Junos OS Release 17.3R1. | [
"Control Plane Distributed Denial-of-Service (DDoS) Protection Overview",
"Configuring Control Plane DDoS Protection Aggregate or Individual Packet Type Policers"
] |
protocols (Dynamic Profiles) | protocols {
igmp {
interface interface-name {
accounting;
disable;
group-limit limit;
group-policy;
group-threshold value;
immediate-leave
log-interval seconds;
no-accounting;
oif-map;
p... | [edit dynamic-profiles profile-name] | Enable Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) Protocol on
the router and configure interface-specific values on dynamic interfaces for each protocol.
PIM and MLD manage multicast groups by establishing, maintaining, and removing groups on a subnet.
Multicast routing devices use... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Support at the [edit dynamic-profiles profile-name protocols mld] and [edit dynamic-profiles profile-name
protocols router-advertisement] hierarchy levels introduced in Junos OS Release 10.1. | [
"Configuring IGMP",
"Configuring MLD"
] |
protocols (Fabric) | protocols {
fabric-control {
graceful-restart {
restart-timeseconds;
stale-routes-time seconds;
}
}
} | [edit fabric] | Specify attributes for the fabric control protocol.
The remaining statements are explained separately. See CLI Explorer. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X52-D10. | [
"Understanding Routing Engines in the QFabric System"
] |
protocols (FIP) | protocols {
fip {
fcoe-trusted;
fc-map fc-map-value;
fka-adv-period milliseconds;
interface {
interface-name {
fka-adv-period milliseconds;
priority priority;
}
}
max-sessions-per-enode max-sessions-per-enode;
... | [edit fc-fabrics fc-fabric-name] | 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... | [] | 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. | [
"Configuring FIP on an FCoE-FC Gateway",
"Overview of FIP"
] |
protocols (Security Zones Host Inbound Traffic) | protocols {
(protocol-name | all <protocol-name except>);
} | [edit security zones security-zone zone-name host-inbound-traffic] | Specify the types of protocol traffic that can reach the device for all interfaces in a zone. You can do this
in one of several ways:
•
You can enable traffic from each protocol individually.
•
You can enable traffic from all protocols.
•
You can enable traffic from all but some protocols. | [
{
"name": "protocol-name",
"desc": "Protocol for which traffic is allowed. The following protocols are supported:"
},
{
"name": "all",
"desc": "Enable traffic from all possible protocols available. Use the except option to"
},
{
"name": "bfd",
"desc": "Enable incoming Bidirectional F... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Security Zones Overview",
"Understanding Functional Zones"
] |
protocols (Security Zones Interfaces) | protocols protocol-name {
except;
} | [edit security zones security-zone zone-name interfaces interface-name host-inbound-traffic] | Specify the types of routing protocol traffic that can reach the device on a per-interface basis. | [
{
"name": "protocol-name",
"desc": "Protocol for which traffic is allowed. The following protocols are supported:"
},
{
"name": "all",
"desc": "Enable traffic from all possible protocols available."
},
{
"name": "bfd",
"desc": "Enable incoming Bidirectional Forwarding Detection (BFD)... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Security Zones Overview",
"Understanding Functional Zones"
] |
protocols (STP Type) | protocols {
mstp { ... }
rstp { ... }
vstp { ... }
} | [edit],
[edit logical-systems logical-system-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | Configure the Spanning Tree Protocol type as MSTP, RSTP, or VSTP. | [
{
"name": "mstp",
"desc": "Configure the protocol as Multiple Spanning Tree."
},
{
"name": "rstp",
"desc": "Configure the protocol as Rapid Spanning Tree."
},
{
"name": "vstp",
"desc": "Configure the protocol as VLAN Spanning Tree."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Support for logical systems added in Junos OS Release 9.6. | [
"Configuring RSTP on EX Series Switches (CLI Procedure)",
"Configuring MSTP on Switches",
"Configuring MSTP Instances on a Physical Interface",
"Configuring Rapid Spanning Tree Protocol",
"Configuring Multiple Spanning Tree Protocol",
"Configuring VLAN Spanning Tree Protocol",
"Understanding MSTP"
] |
protocols (Tenant Systems) | protocols (bgp | ospf | ospf3); | edit tenants tenant-name routing-instances instance_name | Specify the types of routing protocol traffic that can reach a tenant system supported device. | [
{
"name": "bgp",
"desc": "Enable incoming BGP traffic."
},
{
"name": "ospf",
"desc": "Enable incoming OSPF traffic."
},
{
"name": "ospf3",
"desc": "Enable incoming OSPF version 3 traffic."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1. | [
"Tenant Systems Overview"
] |
protocols rsvp expand-flood-reflector-hop | protocols rsvp expand-flood-reflector-hop | Expands the flood reflector hops in the Explicit Route Objects (EROs) to enable the Level 1-Level 2 (L1-
L2) routers to signal RSVP over ISIS non-forwarding adjacency. | [] | routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2. | [] | |
protocols | protocols {
all-fiber-channel-enode {
aggregate {
bandwidth packets per second;
burst packets;
disable-fpc;
disable-logging;
disable-routing-engine;
flow-detection-mode(automatic | off | on);
flow-detect-time seconds;
flow-level-bandwidth {
logical-interface packets per second;... | [edit system ddos-protection] | DDOS protocol parameters | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | [] | |
protocols | protocols {
bgp {
... bgp-configuration ...
}
evpn {
... evpn-configuration ...
isis {
... isis-configuration ...
}
ldp {
... ldp-configuration ...
}
mpls {
... mpls -configuration ...
}
msdp {
... msdp-configuration ...
}
m... | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | Specify the protocol for a routing instance. You can configure multiple instances of many protocol types.
Not all protocols are supported on the switches. See the switch CLI. | [
{
"name": "bgp",
"desc": "Specify BGP as the protocol for a routing instance."
},
{
"name": "isis",
"desc": "Specify IS-IS as the protocol for a routing instance."
},
{
"name": "l2iw",
"desc": "Specify Layer 2 interworking."
},
{
"name": "l2vpn",
"desc": "Specify Layer 2 ... | 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 RIPng introduced in Junos OS Release 9.0.
mpls and rsvp options added in Junos OS Release 15.1. | [
"Example: Configuring Multiple Routing Instances of OSPF"
] |
provider-tunnel | provider-tunnel {
external-controller pccd;
family {
inet {
ingress-replication {
create-new-ucast-tunnel;
label-switched-path-template {
(default-template | lsp-template-name);
}
}
l... | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | Configure virtual private LAN service (VPLS) flooding of unknown unicast, broadcast, and multicast
traffic using point-to-multipoint LSPs. Also configure point-to-multipoint LSPs for MBGP MVPNs.
Starting in Junos OS Release 21.1R1, following provider tunnel types are supported on QFX10002,
QFX10008, and QFX10016 Switch... | [
{
"name": "external-controller",
"desc": ""
},
{
"name": "pccd",
"desc": "(Optional) Specifies that point-to-multipoint LSP and (S,G) for MVPN can be provided by an external controller. This option enables an external controller to dynamically configure (S,G) and point-to-multipoint LSP for MVPN... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3.
The selective statement and substatements added in Junos OS Release 8.5.
The ingress-replication statement and substatements added in Junos OS Release 10.4.
In Junos OS Release 17.3R1, the mdt hierarchy was moved from provider-tunnel to the provider-tunnel family
inet and p... | [
"Flooding Unknown Traffic Using Point-to-Multipoint LSPs in VPLS",
"Configuring Point-to-Multipoint LSPs for an MBGP MVPN",
"Example: Configuring Data MDTs and Provider Tunnels Operating in Source-Specific Multicast Mode"
] |
providers | providers {
provider-id {
license-type license deployment-scope [ deployments ];
}
} | [edit system extensions] | Activate the certificate of the provider of the application and enable the PIC for loading of the
application. | [
{
"name": "provider-id",
"desc": "Provider ID for the application package. The provider ID identifies the provider of the application to the system. The provider ID must be activated on the device to allow the application to be deployed on the device and run."
},
{
"name": "license-type",
"desc"... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
license-type option introduced in Junos OS Release 10.2. | [] |
provisioning-method (Remote Device Management) | provisioning-method {
netconf {
bulk-interval milliseconds;
bulk-limit number;
connection-retry-interval seconds;
password password;
port port-number;
reconfigure-bulk-limit number;
response-timeout seconds;
response-timeout-count number;
user-... | [edit routing-instances routing-instance-name system services remote-device-management service-
device device-name],
[edit system services remote-device-management service-device device-name] | Configure the method for provisioning and deprovisioning services on the remote device. The
NETCONF XML management protocol is currently the only supported method.
The remaining statement is explained separately. Search for a statement in CLI Explorer or click a linked
statement in the Syntax section for details. | [] | system—To view this statement in the configuration. | Statement introduced in Junos OS Release 18.3R1. | [
"Configuring Remote Device Management for Service Provisioning",
"Remote Device Services Manager (RDSM) Overview"
] |
provisioning-order (Diameter Applications) | provisioning-order (gx-plus | jsrc | pcrf); | [edit access profile profile-name] | Configure AAA to use the specified application for subscriber service provisioning. | [
{
"name": "gx-plus",
"desc": "Specify Gx-Plus as the application used to communicate with a PCRF server for subscriber"
},
{
"name": "jsrc",
"desc": "Specify JSRC as the application used to communicate with the SAE for subscriber service"
},
{
"name": "pcrf",
"desc": "Specify Policy ... | 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.
Support for Gx-Plus introduced in Junos OS Release 11.2.
pcrf option added in Junos OS Release 16.2. | [
"JSRC Configuration Overview",
"Provisioning Subscribers with JSRC",
"Configuring Gx-Plus",
"Provisioning Subscribers with Gx-Plus",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Interactions Between the PCRF, PCEF, and OCS"
] |
proxy (Bridge Domains) | proxy {
source-address ip-address;
} | [edit bridge-domains bridge-domain-name protocols igmp-snooping],
[edit bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-
snooping],
[edit routing-instances routing-instance-name bridge-domains bridge-... | Configure proxy mode and options, including source address. All the queries generated by IGMP
snooping are sent using 0.0.0.0 as the source address in order to avoid participating in IGMP querier
election. Also, all reports generated by IGMP snooping are sent with 0.0.0.0 as the source address
unless there is a configu... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Example: Configuring IGMP Snooping"
] |
proxy (Fibre Channel) | proxy {
auto-load-rebalance
load-balance-algorithm (simple | enode-based | flog-based);
no-fabric-wwn-verify;
traceoptions {
file filename <replace> <size size> <files number> <no-stamp>
<world-readable | no-world-readable>;
flag flag <flag-modifier> <disable>;
}
} | [edit fc-fabrics fabric-name] | 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... | [] | storage—To view this statement in the configuration.
storage-control—To add this statement to the configuration. | [
"Understanding FCoE-FC Gateway Functions"
] | |
proxy (interfaces) | proxy inet-address address; | [edit interfaces interface-name unit logical-unit-number family tcc],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family tcc] | 20.1R1
Starting in Junos OS Release 20.1R1, aggregated ethernet interfaces supports VLAN TCC (Translational
cross-connect) encapsulation on MX series platforms. | [
{
"name": "inet-address",
"desc": "Configure the IP address of the neighbor to the TCC router."
}
] | 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.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Configuring TCC Interface Switching",
"Configuring TCC Interface Switching",
"remote",
"Junos OS VPNs Library for Routing Devices"
] |
proxy (Interfaces) | proxy inet-address address; | [edit interfaces interface-name unit logical-unit-number family tcc],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family tcc] | For Layer 2.5 VPNs using an Ethernet interface as the TCC router, configure the IP address for which the
TCC router is proxying. Ethernet TCC is supported on interfaces that carry IPv4 traffic only. Ethernet
TCC encapsulation is supported on 1-port Gigabit Ethernet, 2-port Gigabit Ethernet, 4-port Gigabit
Ethernet, and... | [
{
"name": "inet-address address",
"desc": "IP address for which the TCC router is acting as a proxy."
}
] | 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 TCC Encapsulation for Layer 2 VPNs and Layer 2 Circuits"
] |
proxy (Multicast VLAN Registration) | proxy source-address ip-address; | [edit protocols igmp-snooping vlan (all | vlan-name)] | Specify that a VLAN operate in IGMP snooping proxy mode.
On EX Series switches that do not use the Enhanced Layer 2 Software (ELS) configuration style, this
statement is used only to set proxy mode for multicast VLAN registration (MVR) on a VLAN acting as a
data-forwarding source (an MVLAN).
On ELS EX Series switches,... | [
{
"name": "source-address ip-address",
"desc": "IP address of the source VLAN to act as proxy."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Example: Configuring Multicast VLAN Registration on EX Series Switches Without ELS",
"Configuring Multicast VLAN Registration on EX Series Switches"
] |
proxy (Security Antivirus) | proxy {
password password-string;
port port-number;
server address-or-url;
username name;
} | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine pattern-update]
[edit security utm feature-profile anti-virus kaspersky-lab-engine pattern-update]
[edit security utm feature-profile anti-virus sophos-engine pattern-update] | Update the pattern file on the proxy server. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 11.2.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
proxy (Services) | proxy {
global-config {
session-cache-timeout seconds;
}
profile profile-name {
actions {
crl {
disable;
if-not-present (allow | drop);
ignore-hold-instruction-code;
}
disable-session-resumption;
... | [edit services ssl] | Specify the configuration for Secure Socket Layer (SSL) proxy support service. | [] | 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. The crl statement is supported from 15.1X49-
D30. | [
"SSL Proxy Overview",
"Configuring SSL Forward Proxy",
"Enabling Debugging and Tracing for SSL Proxy"
] |
proxy (snmp) | proxy proxy-name{
device-name device-name;
logical-system logical-system {
routing-instance routing-instance;
}
routing-instance routing-instance;
(version-v1 | version-v2c) {
snmp-community community-name;
no-default... | [edit snmp] | Configure a device to act as a proxy SNMP agent, and specify a name for the proxy. | [
{
"name": "context context-name",
"desc": "Specify the SNMPv3 context name as configured on the device specified at edit snmp proxy proxy-name device-name device-name. For more information about this statement, see \"context\" on page 4850."
},
{
"name": "device-name",
"desc": ""
},
{
"n... | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [] |
proxy (System) | proxy {
server (hostname | ip-address);
port port-number;
username username;
password password;
} | [edit system] | Configure the proxy server properties for a device. | [
{
"name": "server",
"desc": "Configure the server by hostname or IP address."
},
{
"name": "port",
"desc": "Set the port number for the proxy server ranging from 0 through 65535."
},
{
"name": "username",
"desc": "Specify the user name configured in the proxy server."
},
{
"n... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Example: Configuring a Proxy Server for License Updates"
] |
proxy-arp (Dynamic Profiles) | proxy-arp; | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number] | For Ethernet interfaces only, configure the router to respond to any ARP request, as long as the router
has an active route to the target address of the ARP request. | [] | 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. | [
"Configuring Restricted and Unrestricted Proxy ARP",
"Configuring Gratuitous ARP"
] |
proxy-arp (Security NAT) | proxy-arp {
interface interface-name {
address ip-address {
to ip-address;
}
}
} | [edit security nat] | Configure Address Resolution Protocol (ARP) proxy. | [] | 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. | [] |
proxy-arp | proxy-arp (restricted | unrestricted); | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | For Ethernet interfaces only, configure the router or switch to respond to any ARP request, as long as
the router or switch has an active route to the ARP request’s target address.
NOTE: You must configure the IP address and the inet family for the interface when you
enable proxy ARP.
Default
Proxy ARP is not enabled.... | [
{
"name": "none",
"desc": "The router or switch responds to any ARP request for a local or remote address if the router or"
},
{
"name": "restricted",
"desc": "(Optional) The router or switch responds to ARP requests in which the physical networks"
},
{
"name": "unrestricted",
"desc"... | 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.
restricted added in Junos OS Release 10.0 for EX Series switches. | [
"Configuring Restricted and Unrestricted Proxy ARP",
"Configuring Proxy ARP on Switches",
"Example: Configuring Proxy ARP on an EX Series Switch",
"Configuring Gratuitous ARP"
] |
proxy-generate | proxy-generate <route-target-policy route-target-policy-name>; | [edit logical-systems logical-system-name protocols bgp group group-name family route-target],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address family
route-target],
[edit protocols bgp group group-name family route-target],
[edit protocols bgp group group-name neighbor addre... | Enable proxy BGP route target filtering (also known as proxy route target constrain, or proxy RTC). This
feature is useful if you have a network environment where route target filtering is not widely deployed
or fully supported. When configured for proxy BGP route target filtering, the device creates route target
membe... | [
{
"name": "route-target-policy route-",
"desc": ""
},
{
"name": "target-policy-name",
"desc": "(Optional) Apply a routing policy that defines a subset of VPN routes to be used in your proxy BGP route target filter. The subset of VPN routes control which proxy BGP route targets are used to create... | 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. | [
"Example: Configuring Proxy BGP Route Target Filtering for VPNs",
"Example: Configuring an Export Policy for BGP Route Target Filtering for VPNs",
"Configuring BGP Route Target Filtering for VPNs",
"rtf-prefix-list"
] |
proxy-mac | proxy-mac {
irb |proxy-mac-address;
} | [edit routing-instances name protocols evpn],
[edit routing-instances name bridge-domains] | Specifies the proxy MAC address.
When CE devices connect directly to gateway devices, configure the MAC proxy on the gateway
devices with the irb option. Junos OS will use the virtual gateway MAC address or the MAC address of
the IRB interface.
In a spine-and-leaf network where the routing is performed on the spine dev... | [
{
"name": "irb",
"desc": "Reply with the manually configured virtual gateway, automatically derived virtual gateway, or IRB MAC address. The virtual gateway MAC address takes precedence over a IRB MAC address. If the MAC address of the IRB interface is not configured, Junos OS uses a MAC address derived fro... | routing | Statement introduced in Junos OS Release 19.1R1. | [
"ARP and NDP Request with a proxy MAC address"
] |
proxy-macip-advertisement | proxy-macip-advertisement; | [edit interfaces irb unit logical-unit-number ] | Enable the proxy advertisement feature on a QFX Series switch that can function as a Layer 3 (L3)
gateway. With this feature enabled, the L3 gateway advertises the MAC and IP routes (EVPN Type 2
MAC-IP routes) on behalf of Layer 2 (L2) Virtual Extensible LAN (VXLAN) gateways.
In an Ethernet VPN-VXLAN (EVPN-VXLAN) cent... | [] | 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-D60. | [] |
proxy-mode | proxy-mode; | [edit forwarding-options dhcp-relay overrides],
[edit forwarding-options dhcp-relay group group-name overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay group group-name
overrides],
[edit logical-syst... | Enable DHCP relay proxy mode on the extended DHCP relay. Proxy mode supports all extended DHCP
relay functionality.
You cannot configure both the DHCP relay proxy and the extended DHCP local server on the same
interface. | [] | 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. | [
"DHCP Relay Proxy Overview",
"Extended DHCP Relay Agent Overview",
"Enabling DHCP Relay Proxy Mode"
] |
proxy-ndp (Security NAT) | proxy-ndp {
interface interface-name {
address ip-address {
to ip-address;
}
}
} | [edit security nat] | Configure Neighbor Discovery Protocol (NDP) proxy. | [] | 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. | [] |
proxy-profile | proxy-profile proxy profile name | [edit security utm default-configuration anti-virus avira-engine pattern-update],
[edit security utm default-configuration anti-virus sophos-engine pattern-update],
[edit security utm feature-profile anti-virus sophos-engine pattern-update],
[edit logical-systems name security utm default-configuration anti-virus avira... | Specify the proxy profile name and is used for configuring the explicit proxy.
For logical system and tenant you can configure the proxy profile only in root system at device level. You
cannot configure the proxy profile in the logical system or tenant level. | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1. | [] |
ps0 (Pseudowire Subscriber Interfaces) | ps0 {
anchor-point lt-device;
mtu bytes;
mac mac-address;
no-gratuitous-arp-request;
(flexible-vlan-tagging | stacked-vlan-tagging | untagged | vlan-tagging);
} | [edit logical-systems transport-ls interfaces] | Configure the pseudowire logical device.
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 13.1. | [
"MPLS Pseudowire Subscriber Logical Interfaces",
"MPLS Pseudowire Subscriber Logical Interfaces",
"MPLS Pseudowire Subscriber Logical Interfaces",
"MPLS Pseudowire Subscriber Logical Interfaces",
"MPLS Pseudowire Subscriber Logical Interfaces"
] |
pseudowire-service (Pseudowire Subscriber Interfaces) | pseudowire-service {
device-count number;
} | [edit chassis] | Configure properties for the pseudowire devices on the router.
The remaining statement is 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 13.1. | [
"MPLS Pseudowire Subscriber Logical Interfaces",
"MPLS Pseudowire Subscriber Logical Interfaces",
"MPLS Pseudowire Subscriber Logical Interfaces"
] |
pseudowire-status-tlv | pseudowire-status-tlv hot-standby-vc-on; | [edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name],
[edit protocols l2circuit neighbor address interface interface-name] | Enables the pseudowire type length variable (TLV). The pseudowire status TLV is used to communicate
the status of a pseudowire back and forth between two PE routers. The pseudowire status TLV is
configurable for each pseudowire connection and is disabled by default.
The remaining statement is explained separately. See ... | [] | 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. | [
"Configuring the Pseudowire Status TLV",
"Example: Configuring Pseudowire Redundancy in a Mobile Backhaul Scenario"
] |
psn-tunnel-endpoint | psn-tunnel-endpoint address; | [edit logical-systems logical-system-name protocols l2circuit neighbor address
interface interface-name],
[edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name backup-neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name ... | Specify the endpoint of the packet switched network (PSN) tunnel on the remote PE router. | [
{
"name": "address",
"desc": "Address for the tunnel endpoint."
}
] | 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.
Hierarchy levels associated with the backup-neighbor statement added in Junos OS Release 9.2. | [
"Configuring Layer 2 Circuits over Both RSVP and LDP LSPs",
"Configuring Pseudowire Redundancy on the PE Router"
] |
psu (satellite-management) | psu {
redundancy {
n-plus-n;
}
} | [edit chassis satellite-management] | Configure N+N power supply redundancy for the satellite devices in a Junos Fusion.
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 16.1R1. | [
"Understanding Power over Ethernet in a Junos Fusion"
] |
psu | psu {
redundancy {
n-plus-n (Power Management);
}
} | [edit chassis] | Configure N+N power supply redundancy for power management on an EX6200 or EX8200 switch or
SRX380 device.
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 10.2. | [
"Configuring Power Supply Redundancy (CLI Procedure)"
] |
ptp | ptp {
clock-mode(boundary | ordinary);
delay-comp {...}
disable-lag-revertive-switchover;
domain domain;
local-priority local-priority;
master {
announce-interval announce-interval;
}
path-trace;
performance-monitor {...}
phase-adjust-threshold phase-... | [edit logical-systems name protocols],
[edit protocols] | Configure PTP on the device. PTP, also known as IEEE 1588v2, is a packet-based technology that
enables the operator to deliver synchronization services on packet-based mobile backhaul networks.
IEEE 1588 PTP (Version 2) clock synchronization standard is a highly precise protocol for time
synchronization that synchroniz... | [
{
"name": "acquiring-state-announce-",
"desc": ""
},
{
"name": "grandmaster",
"desc": "Use grandmaster data set for announce messages when in acquiring state."
},
{
"name": "afts",
"desc": "Enable assisted full timing support (AFTS) mode of operation. See, No Link Title."
},
{
... | routing-To view this statement in the configuration. | Statement introduced in Junos OS Release 12.2R1
frequency-lock-threshold, phase-adjust-threshold, and phase-lock-threshold options introduced in Junos OS
Release 23.4R1 for MX10008 routers.
frequency-lock-threshold, phase-adjust-threshold, and phase-lock-threshold options supported on
ACX7100-32C, ACX7100-48L, and ACX7... | [
"Precision Time Protocol (PTP) Overview",
"PTP Passive Port Performance Monitoring"
] |
ptp-mode | ptp-mode; | [edit chassis fpc name pic name] | Configure the PTP mode to enable PTP boundary or ordinary clock functionality.
When you enable PTP mode, one of the port that is used for data traffic gets disabled. For more
information about valid port configurations on ACX7100-32C, ACX7100-48L, and ACX7024 routers,
see Port Speed. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 21.1R1. | [] |
ptsp-rules | (ptsp-rules rule-name | ptsp-rules-sets rule-set-name); | [edit services service-set service-set-name] | Specify the PTSP rules or rule set included in this service set. You can configure multiple rules but only
one rule set for each service. | [
{
"name": "rule-name",
"desc": "Identifier for the collection of terms that constitute this rule."
},
{
"name": "rule-set-name",
"desc": "Identifier for the set of rules to be included."
}
] | interface—To view this statement in the configuration.
interface–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Service Sets to be Applied to Services Interfaces"
] |
pulse-per-second-enable | pulse-per-second-enable; | [edit chassis synchronization interfaces external],
[edit chassis synchronization interfaces (external-0/0 | external-1/0)] | Configure the external interface to receive the pulse per second (PPS) signal on the GPS interface of the
router. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [] |
purge-flow-timer (Protocols OpenFlow) | purge-flow-timer seconds; | [edit protocols openflow switch switch-name] | For an OpenFlow virtual switch, specify the number of seconds after which an invalid OpenFlow flow
entry is deleted from the flow table.
If you do not configure the purge-flow-timer statement, the device purges invalid flows from hardware, but
indefinitely retains the corresponding flow entries in the flow table. If yo... | [
{
"name": "seconds",
"desc": "Number of seconds after which an invalid flow entry is deleted from the flow table. Range: 0 through 300"
}
] | 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. | [
"Understanding Support for OpenFlow on Devices Running Junos OS",
"Understanding OpenFlow Flow Entry Timers on Devices Running Junos OS"
] |
purge-timeout (programmable-rpd) | purge-timeout {
never;
timeout <seconds>;
} | [edit routing-options programmable-rpd] | Set the time, in seconds, after which a disconnected client times out. Upon disconnect, the client state
remains available but no operations occur. If the disconnected client reconnects before the set time has
elapsed, the states are restored on the router. If it does not, all client operations are reverted and the
pro... | [
{
"name": "never",
"desc": "When this option is configured, the purge timeout is infinite for the BGP route service. Client-added routes never time out. The prpd-client-added routes are not deleted when the client disconnects and does not reconnect back. The routes are deleted only when the client explicitl... | routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2.
never option introduced in Junos OS Release 18.4R1. | [] |
purging | purging; | [edit system arp] | Purge obsolete ARP entries from the cache when an interface or link goes offline. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [] |
push (Dynamic VLANs) | push; | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number input-vlan-
map] | For dynamic VLAN interfaces, specify the VLAN rewrite operation to add a new VLAN tag to the top of
the VLAN stack. An outer VLAN tag is pushed in front of the existing VLAN tag. If you include the push
statement in the configuration, you must also include the pop statement at the [edit dynamic-profiles
profile-name in... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Stacking and Rewriting VLAN Tags for the Layer 2 Wholesale Solution"
] |
push (protocols mpls) | push out-label; | [edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
bypass],
[edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
ingress],
[edit protocols mpls static-label-switched-path lsp-name bypass],
[edit protocols mpls static-label-switched-path... | Add a new label to the top of the label stack. This statement is used to configure static LSPs at ingress
routers and to configure bypass LSPs for static LSPs. | [
{
"name": "out-label",
"desc": "Manually assigned outgoing label value."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Ingress Router for Static LSPs"
] |
push | push; | [edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interfa... | NOTE: On EX4300 switches, push is not supported at the [edit interfaces interface-name
unit logical-unit-number output-vlan-map] hierarchy level.
Specify the VLAN rewrite operation to add a new VLAN tag to the top of the VLAN stack. An outer
VLAN tag is pushed in front of the existing VLAN tag.
You can use this stateme... | [] | 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. | [
"Stacking a VLAN Tag",
"Configuring Q-in-Q Tunneling on EX Series Switches with ELS Support"
] |
push-backup-to-master (Accounting Options) | push-backup-to-master; | [edit accounting-options file filename] | Configure the router to save the accounting files from the new backup Routing Engine to the new
primary Routing Engine when a change in primary role occurs. The files are saved to the /var/log/
pfedBackup directory on the router. The primary Routing Engine includes these accounting files with its
own current accounting... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R4. | [
"Configuring Accounting-Data Log Files",
"Configuring Flat-File Accounting for Layer 2 Wholesale",
"Configuring Flat-File Accounting for Extensible Subscriber Services Management",
"Flat-File Accounting Overview"
] |
push-push | push-push; | [edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interfa... | Specify the VLAN rewrite operation to push two VLAN tags in front of the frame.
You can use this statement on Gigabit Ethernet IQ, IQ2 and IQ2-E interfaces, 10-Gigabit Ethernet
LAN/WAN PIC, on aggregated Ethernet interfaces using Gigabit Ethernet IQ2 and IQ2-E or 10-Gigabit
Ethernet PICs on MX Series routers, and 100-G... | [] | 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. | [
"Stacking Two VLAN Tags"
] |
push-to-identity-management | push-to-identity-management; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
firewall-authentication] | Configure JIMS with SRX Series Firewall to push the authentication entries with a successful
authentication state to the Juniper Identity Management Service server. Configure JIMS with SRX Series
Firewall to view the JIMS status online. For more information, see Configuration of JIMS with SRX
Series Firewall. You use t... | [] | 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. | [] |
pvlan | pvlan; | [edit vlans vlan-name] | Specify that the VLAN is private and access ports in the VLAN do not forward packets to each other.
You use this statement with primary VLANs and isolated secondary VLANs. | [
{
"name": "none",
"desc": ""
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Creating a Private VLAN on a Single QFX Switch without ELS Support",
"Creating a Private VLAN Spanning Multiple QFX Series Switches without ELS Support"
] |
pvlan-trunk | pvlan-trunk; | [edit vlans vlan-name vlan-id number interface interface-name] | Configure an interface to be the trunk port, connecting switches that are configured with a private
VLAN (PVLAN) across these switches. | [] | routing—To view this statement in the configuration.
routing–control—To add this statement to the configuration.
system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Creating a Private VLAN Spanning Multiple EX Series Switches (CLI Procedure)",
"Creating a Private VLAN on a Single QFX Switch",
"Creating a Private VLAN Spanning Multiple QFX Series Switches"
] |
python-script-user (Event and SNMP Scripts) | python-script-user username; | [edit event-options event-script file filename],
[edit system scripts snmp file filename] | Define the user under whose access privileges the local Python event script or Python SNMP script
executes. If you do not associate a user with the script, then by default, Junos OS executes the script
with the privileges of the *nix user and group nobody, which is the generic, unprivileged system account.
NOTE: You ca... | [
{
"name": "username",
"desc": "Username that is configured at the [edit system login] hierarchy level."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 16.1R3. | [
"Requirements for Executing Python Automation Scripts on Devices Running Junos OS",
"Understanding Python Automation Scripts for Devices Running Junos OS",
"Q"
] |
qos-adjust | [edit protocols ancp] | Specify that the ANCP agent reports data rates for downstream traffic to CoS. When this statement is
not configured, the ANCP agent does not report traffic rates to CoS.
For Junos OS Release 17.3 and earlier releases, configure the values by which the actual downstream
data rates are adjusted. The remaining statements ... | [] | 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.
Subordinate statements deprecated in Junos OS Release 17.4. | [
"Configuring the ANCP Agent to Report Traffic Rates to CoS",
"Traffic Rate Reporting and Adjustment by the ANCP Agent",
"Configuring the ANCP Agent"
] | |
qos-adjust-adsl2 | qos-adjust-adsl2 adjustment-factor; | [edit protocols ancp] | 17.4R1
Starting in Junos OS Release 17.4R1, this statement is deprecated and replaced by the adsl2-total-
adjust option of the access-line statement at the [edit system] hierarchy level. | [
{
"name": "adjustment-factor",
"desc": "Adjustment factor applied to upstream and downstream data rates for the DSL type."
}
] | 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.
Statement deprecated in Junos OS Release 17.4R1.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Setting a Global Adjustment Factor per DSL Subscriber Line for ANCP Agent-Reported Traffic Rates",
"Configuring the ANCP Agent"
] |
qos-adjust-adsl2-plus | qos-adjust-adsl2-plus adjustment-factor; | [edit protocols ancp] | 17.4R1
Starting in Junos OS Release 17.4R1, this statement is deprecated and replaced by the adsl2-plus-total-
adjust option of the access-line statement at the [edit system] hierarchy level. | [
{
"name": "adjustment-factor",
"desc": "Adjustment factor applied to upstream and downstream data rates for the DSL type."
}
] | 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.
Statement deprecated in Junos OS Release 17.4R1.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Setting a Global Adjustment Factor per DSL Subscriber Line for ANCP Agent-Reported Traffic Rates",
"Configuring the ANCP Agent"
] |
qos-adjust-adsl | qos-adjust-adsl adjustment-factor; | [edit protocols ancp] | 17.4R1
Starting in Junos OS Release 17.4R1, this statement is deprecated and replaced by the adsl-total-adjust
option of the access-line statement at the [edit system] hierarchy level. | [
{
"name": "adjustment-factor",
"desc": "Adjustment factor applied to upstream and downstream data rates for the DSL type."
}
] | 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.
Statement deprecated in Junos OS Release 17.4R1.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Setting a Global Adjustment Factor per DSL Subscriber Line for ANCP Agent-Reported Traffic Rates",
"Configuring the ANCP Agent"
] |
qos-adjust-hierarchical | qos-adjust-hierarchical [interface-set]; | [edit dynamic-profiles dynamic-profile-name access-cac interface $junos-interface-name] | Specify that multicast QoS adjustments received on the subscriber contribute to hierarchical QoS
adjustments. | [
{
"name": "interface-set",
"desc": "(Optional) Specify that the immediate parent interface-set receive QoS adjustments."
}
] | 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. | [
"Configuring the Minimum Adjusted Shaping Rate on Scheduler Nodes for Subscribers"
] |
qos-adjust-other | qos-adjust-other adjustment-factor; | [edit protocols ancp] | 17.4R1
Starting in Junos OS Release 17.4R1, this statement is deprecated and replaced by the other-total-
adjust option of the access-line statement at the [edit system] hierarchy level. | [
{
"name": "adjustment-factor",
"desc": "Adjustment factor applied to upstream and downstream data rates for the DSL type."
}
] | 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.
Statement deprecated in Junos OS Release 17.4R1.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Setting a Global Adjustment Factor per DSL Subscriber Line for ANCP Agent-Reported Traffic Rates",
"Configuring the ANCP Agent"
] |
qos-adjust-sdsl | qos-adjust-sdsl adjustment-factor; | [edit protocols ancp] | 17.4R1
Starting in Junos OS Release 17.4R1, this statement is deprecated and replaced by the sdsl-total-adjust
option of the access-line statement at the [edit system] hierarchy level. | [
{
"name": "adjustment-factor",
"desc": "Adjustment factor applied to upstream and downstream data rates for the DSL type."
}
] | 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.
Statement deprecated in Junos OS Release 17.4R1.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Setting a Global Adjustment Factor per DSL Subscriber Line for ANCP Agent-Reported Traffic Rates",
"Configuring the ANCP Agent"
] |
qos-adjust-vdsl2 | qos-adjust-vdsl2 adjustment-factor; | [edit protocols ancp] | 17.4R1
Starting in Junos OS Release 17.4R1, this statement is deprecated and replaced by the vdsl2-total-
adjust option of the access-line statement at the [edit system] hierarchy level. | [
{
"name": "adjustment-factor",
"desc": "Adjustment factor applied to upstream and downstream data rates for the DSL type."
}
] | 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.
Statement deprecated in Junos OS Release 17.4R1.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Setting a Global Adjustment Factor per DSL Subscriber Line for ANCP Agent-Reported Traffic Rates",
"Configuring the ANCP Agent"
] |
qos-adjust-vdsl | qos-adjust-vdsl adjustment-factor; | [edit protocols ancp] | 17.4R1
Starting in Junos OS Release 17.4R1, this statement is deprecated and replaced by the vdsl-total-adjust
option of the access-line statement at the [edit system] hierarchy level. | [
{
"name": "adjustment-factor",
"desc": "Adjustment factor applied to upstream and downstream data rates for the DSL type."
}
] | 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.
Statement deprecated in Junos OS Release 17.4R1.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Setting a Global Adjustment Factor per DSL Subscriber Line for ANCP Agent-Reported Traffic Rates",
"Configuring the ANCP Agent"
] |
qualified-bum-pruning-mode | qualified-bum-pruning-mode; | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | For Junos OS Layer 2 Wholesale configurations, prune (constrain) distribution of broadcast, unicast, and
multicast (BUM) packets of unknown origin to only those interfaces that match the traffic from a specific
VLAN pair. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Configuring Separate NNI Routing Instances for Layer 2 Wholesale Service Retailers",
"Layer 2 and Layer 3 Wholesale Overview",
"Support of Inner VLAN List and Inner VLAN Range for Qualified BUM Pruning on a Dual-Tagged",
"Interface for a VPLS Routing Instance Overview"
] |
qualified-next-hop (Access) | qualified-next-hop next-hop; | [edit routing-options access route ip-prefix</prefix-length>] | Configure the qualified next-hop address for an access route. | [
{
"name": "next-hop",
"desc": "Specific qualified next-hop address 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. | [] |
qualified-next-hop (Access-Internal) | qualified-next-hop next-hop; | [edit routing-options access-internal route ip-prefix</prefix-length>] | Configure the qualified next-hop address for an internal access route. | [
{
"name": "next-hop",
"desc": "Specific qualified next-hop address you want to assign to the internal 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. | [] |
qualified-next-hop (Dynamic Access-Internal Routes) | qualified-next-hop interface-name {
mac-address address;
} | [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
access-internal route subscriber-ip-address],
[edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
rib routing-table-name access-internal route subscriber-ip-address],
[edit dynamic-p... | Dynamically configure the qualified next-hop and the MAC address for an access-internal route for
DHCP and PPP subscriber interfaces. | [
{
"name": "interface-name",
"desc": "Either the specific interface you want to assign to the access route or the variable, or the"
}
] | 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 the [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
route subscriber-ip-address] and [edit dynamic-profiles profile-name routing-instances $junos-routing-instance
routing-options rib routing-table-name route subscribe... | [
"Routes for DHCP and PPP Subscriber Access Networks"
] |
qualified-next-hop (Static Routes) | qualified-next-hop (address | interface-name) {
bfd-liveness-detection {
authentication {
algorithm (keyed-md5 | keyed-sha-1 | meticulous-keyed-md5 | meticulous-keyed-sha-1 |
simple-password);
key-chain key-chain-name;
loose-check;
}
detection-time {
... | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options
static route destination-prefix],
[edit logical-systems logical-system-name routing-options rib inet6.0 static route destination-
prefix],
[edit logical-systems logical-system-name routing-options static route destination... | Configure a static route with multiple possible next hops, each of which can have its own preference
value, IGP metric that is used when the route is exported into an IGP, and Bidirectional Forwarding
Detection (BFD) settings. If multiple links are operational, the one with the most preferred next hop is
used. The most... | [
{
"name": "address",
"desc": "IPv4, IPv6, or ISO network address of the next hop."
},
{
"name": "interface-name",
"desc": "Name of the interface on which to configure an independent metric or preference for 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. | [
"Example: Enabling BFD on Qualified Next Hops in Static Routes for Route Selection"
] |
qualified-vlan | qualified-vlan vlan-id; | [edit protocols mld-snooping vlan vlan-name]
[edit routing-instances instance-name protocols mld-snooping vlan vlan-name]
[edit protocols igmp-snooping vlan vlan-name] | Configure VLAN options for qualified learning. | [
{
"name": "vlan-id",
"desc": "VLAN ID of the learning domain."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Example: Configuring IGMP Snooping on SRX Series Devices",
"Configuring MLD Snooping on a Switch VLAN with ELS Support (CLI Procedure)",
"Configuring IGMP Snooping on Switches",
"IGMP Snooping Overview"
] |
quality (Interfaces) | quality <value>; | [edit interfaces interface-name unit logical-unit-number radio-router] | This option controls relative link quality weight (value 0–100). | [] | 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. | [
"PPPoE-Based Radio-to-Router Protocols Overview"
] |
quality-level (Clock Synchronization) | quality-level (prc | prs | sec | smc | ssu-a | ssu-b | st2 | st3 | st3e | st4 | stu | tnc); | [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 quality level for a timing source so that the router knows the best available source with
which to synchronize. The quality level specifies the accuracy level of the clock and is transmitted across
the network through Synchronization Status Messages (SSMs) over the Ethernet Synchronization
Messaging Chann... | [
{
"name": "prs",
"desc": "Primary reference source—Stratum 1"
},
{
"name": "st2",
"desc": "Stratum 2"
},
{
"name": "tnc",
"desc": "Transit node clock"
},
{
"name": "st3e",
"desc": "Stratum 3E"
},
{
"name": "st3",
"desc": "Stratum 3"
},
{
"name": "smc",... | 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. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.