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 |
|---|---|---|---|---|---|---|---|
exclude (Dynamic MLD Interface) | exclude; | [edit dynamic-profiles profile-name protocols mld interface interface-name static group multicast-
group-address] | Configure the group to operate in exclude mode on the dynamic interface. In exclude mode all sources
except the address configured are accepted for the group. By default, the group operates in include
mode. | [] | 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.1. | [
"Dynamic MLD Configuration Overview",
"Enabling MLD Static Group Membership"
] |
exclude (for Administrative Groups) | exclude [ group-names ]; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name admin-group],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name (primary |
secondary) path-name admin-group],
[edit protocols mpls label-switched-path lsp-name admin-group],
[edit protocols mpls la... | Define the administrative groups to exclude for an LSP or for a path’s primary and secondary paths. | [
{
"name": "group-names",
"desc": "Names of one or more groups defined with the \"admin-groups\" on page 2149 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 Administrative Groups for LSPs"
] |
exclude (for Fast Reroute) | (exclude [ group-names ] | no-exclude); | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name fast-
reroute],
[edit protocols mpls label-switched-path lsp-name fast-reroute] | Control exclusion of administrative groups:
•
exclude—Define the administrative groups to exclude for fast reroute.
•
no-exclude—Disable administrative group exclusion. | [
{
"name": "group-names",
"desc": "Names of one or more groups defined with the admin-groups 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 Fast Reroute"
] |
exclude (JSRC Attributes) | exclude {
user-name [ authorization-request | provisioning-request ];
} | [edit access profile profile-name jsrc attributes] | Configure the router to exclude the specified attribute-value pair (AVP) from the specified Diameter
message for JSRC. | [
{
"name": "user-name",
"desc": "User-Name AVP (1). Diameter AVP name and number."
},
{
"name": "authorization-request",
"desc": "address-authorization request in AAR message sent from JSRC to the SAE."
},
{
"name": "provisioning-request",
"desc": "provisioning-request in AAR message ... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Excluding AVPs from Diameter Messages for JSRC",
"Understanding JSRC-SAE Interactions"
] |
exclude (Protocols IGMP) | exclude; | [edit logical-systems logical-system-name protocols igmp interface interface-name static group
multicast-group-address],
[edit protocols igmp interface interface-name static group multicast-group-address] | Configure the static group to operate in exclude mode. In exclude mode all sources except the address
configured are accepted for the group. If this statement is not included, the group operates in include
mode. | [] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Enabling IGMP Static Group Membership"
] |
exclude (Protocols MLD) | exclude; | [edit logical-systems logical-system-name protocols mld interface interface-name static group
multicast-group-address],
[edit protocols mld interface interface-name static group multicast-group-address] | Configure the static group to operate in exclude mode. In exclude mode all sources except the address
configured are accepted for the group. By default, the group operates in include mode. | [] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Enabling MLD Static Group Membership"
] |
exclude (RADIUS Attributes) | exclude {
acc-aggr-cir-id-asc [ access-request | accounting-start | accounting-stop ];
acc-aggr-cir-id-bin [ access-request | accounting-start | accounting-stop ];
acc-loop-cir-id [ access-request | accounting-start | accounting-stop ];
acc-loop-encap [ access-request | accounting-start | accounting-sto... | [edit access profile profile-name radius attributes] | Configure the router or switch to exclude the specified attributes from being sent in the specified type
of RADIUS message. Exclusion can be useful, for example, for attributes that do not change values over
the lifetime of a subscriber. By not sending these attributes, you reduce the packet size without losing
informa... | [
{
"name": "RADIUS attribute",
"desc": "RADIUS standard attribute or VSA:"
},
{
"name": "acc-aggr-cir-id-asc",
"desc": "Exclude Juniper Networks VSA 26-112, Acc-Aggr-Cir-Id-Asc."
},
{
"name": "acc-aggr-cir-id-bin",
"desc": "Exclude Juniper Networks VSA 26-111, Acc-Aggr-Cir-Id-Bin."
... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
downstream-calculated-qos-rate, dsl-forum-attributes, and upstream-calculated-qos-rate options added in Junos
OS Release 11.4.
cos-shaping-rate and filter-id options added in Junos OS Release 13.2.
pppoe-description option added in Junos OS Release 14.2.
virtual-router opt... | [
"RADIUS Servers and Parameters for Subscriber Access",
"Standard and Vendor-Specific RADIUS Attributes"
] |
exclude (Schedulers) | exclude; | [edit schedulers scheduler scheduler-name daily],
[edit schedulers scheduler scheduler-name friday],
[edit schedulers scheduler scheduler-name monday],
[edit schedulers scheduler scheduler-name saturday],
[edit schedulers scheduler scheduler-name sunday],
[edit schedulers scheduler scheduler-name tuesday],
... | Exclude a specified day from the schedule.
Use the exclude statement to exclude a day from a daily schedule created with the daily statement. You
cannot use the exclude statement for a particular day unless it is in conjunction with the daily statement
in a schedule. | [] | 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 Policy Schedulers Overview"
] |
exclude (Security Log) | exclude exlude-name {
destination-address destination-address;
destination-port destination-port;
event-id event-id;
failure;
interface-name interface-name;
policy-name policy-name;
process process-name;
protocol protocol;
source-address source-address;
source-port source-port;
... | [edit security log cache]
[edit logical-systems name security log cache]
[edit tenants tenant-name security log cache] | Configure a list of auditable events that can be excluded from the audit log. | [
{
"name": "destination-ip destination-address",
"desc": "Destination IP address."
},
{
"name": "destination-port destination-port",
"desc": "Destination port number."
},
{
"name": "event-id event-id",
"desc": "Error message identification number."
},
{
"name": "failure",
... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2.
The [edit logical-systems name security log cache] and [edit tenants tenant-name security log cache]
hierarchy levels introduced in Junos OS Release 19.1R1. | [] |
exclude-hostname | exclude-hostname; | [edit system syslog host hostname] | Disable logging of hostname in the message directed to remote host. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2 | [] |
exclude-protocol (MX Series) | exclude-protocol protocol-name; | [edit security macsec connectivity-association connectivity-association-name] | Specifies protocols whose packets are not secured using Media Access Control Security (MACsec) when
MACsec is enabled on a link using static connectivity association key (CAK) security mode.
When this option is enabled in a connectivity association that is attached to an interface, MACsec is not
enabled for all packets... | [
{
"name": "protocol-name",
"desc": "Specifies the name of the protocol that should not be MACsec-secured. Options include:"
},
{
"name": "cdp",
"desc": "Cisco Discovery Protocol."
},
{
"name": "lacp",
"desc": "Link Aggregation Control Protocol."
},
{
"name": "lldp",
"desc... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Media Access Control Security (MACsec) on Routers"
] |
exclude-protocol | exclude-protocol protocol-name; | [edit security macsec connectivity-association connectivity-association-name] | Specifies protocols whose packets are not secured using Media Access Control Security (MACsec) when
MACsec is enabled on a link using static connectivity association key (CAK) security mode.
When this option is enabled in a connectivity association that is attached to an interface, MACsec is not
enabled for all packets... | [
{
"name": "protocol-name",
"desc": "Specifies the name of the protocol that should not be MACsec-secured. Options include:"
},
{
"name": "cdp",
"desc": "Cisco Discovery Protocol."
},
{
"name": "lacp",
"desc": "Link Aggregation Control Protocol."
},
{
"name": "lldp",
"desc... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D15.
Statement introduced for SRX Series Firewalls in Junos OS Release 15.1X49-D60. | [
"Configuring MACsec on EX, QFX and SRX Devices",
"Understanding Media Access Control Security (MACsec)",
"Configuring Media Access Control Security (MACsec)"
] |
exclude-queue-overhead-bytes | exclude-queue-overhead-bytes {
include-hierarchy;
} | [edit class-of-service interfaces interface-name] | By default, the Layer 2 header bytes applied to upper-level logical interfaces are included in CoS per-
queue statistics at the physical interface, which can provide inaccurate results. This options enables you
to exclude the counting of overhead bytes from aggregate queue statistics. | [
{
"name": "include-hierarchy",
"desc": "Exclude the counting of overhead bytes from aggregate queue statistics of all child interfaces, including logical interfaces and interface sets, as well."
}
] | interface | Statement introduced in Junos OS Release 18.2R1. | [] |
exclude-srlg | exclude-srlg; | [edit protocols mpls],
[edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls label-switched-path path-name],
[edit logical-systems logical-system-name protocols mpls label-switched-path path-name],
[edit protocols rsvp interface interface-name link-protection],
[edit logical-systems logical-sy... | Exclude Shared Risk Link Group (SRLG) links for the secondary path for critical links where it is
imperative to keep the secondary and primary label-switched paths completely disjoint from any
common SRLG.
When specified, the Constrained Shortest Path First (CSPF) algorithm excludes any link belonging to the
set of SR... | [] | 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. | [
"Example: Excluding SRLG Links Completely for the Secondary LSP"
] |
excluded-address (Address-Assignment Pools) | excluded-address ip-address; | [edit access address-assignment pool] | Allows you to exclude select IPv4 or IPv6 addresses from a DHCP address pool. Within a configured
address pool, you can specifically exclude up to 20 addresses. Junos OS will not assign these excluded
addresses to any clients. If you configure an excluded address that has already been assigned to a DHCP
client, that ex... | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D20. | [
"Preventing Addresses from Being Allocated from an Address Pool"
] |
excluded-range (Address-Assignment Pools) | excluded-range name low minimum-value high maximum-value; | [edit access address-assignment pool name family (inet | inet6)],
[edit logical-systems name access address-assignment pool name family (inet | inet6)],
[edit logical-systems name routing-instances name access address-assignment pool name family (inet
| inet6)],
[edit routing-instances name access address-assignment p... | Specify a range of consecutive addresses to exclude from consideration when addresses are allocated
from the corresponding address pool. For example, you might want to reserve certain addresses or
ranges to be used only for static subscribers. If a range you configure for exclusion includes an address
that has already ... | [
{
"name": "high",
"desc": "Upper limit of excluded range of addresses."
},
{
"name": "low",
"desc": "Lower limit of range of addresses."
},
{
"name": "name",
"desc": "Name of a range of addresses to exclude from the address pool for the specified family."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"Preventing Addresses from Being Allocated from an Address Pool",
"Address-Assignment Pools Overview",
"Address-Assignment Pool Configuration Overview"
] |
exclusive-mac | exclusive-mac virtual-mac-mac-address/mask; | [edit protocols l2-learning global-mac-move] | Exclude MAC addresses from the MAC move limit algorithm.
The global MAC move feature is used to track MAC addresses when they appear on a different physical
interface or within a different unit of the same physical interface. When you configure the exclusive-mac
virtual-mac-mac-address/mask parameter at the [edit proto... | [
{
"name": "virtual-mac-mac-address/mask",
"desc": "Specify a MAC address and a mask. If the mask is 48, only the exact MAC address is excluded. If the mask is 40, all the MAC addresses that have the same first 5 bytes are excluded."
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D45. | [
"Configuring MAC Move Parameters"
] |
execute-commands (Event Policy) | execute-commands {
commands {
"command";
}
destination destination-name {
retry-count count retry-interval seconds;
transfer-delay seconds;
}
output-filename filename;
output-format (text | xml);
user-name username;
} | [edit event-options policy policy-name then] | Specify the operational mode commands to be issued when the corresponding event policy is triggered.
You can also specify the format of the command output and the filename identifier and destination for
the output file.
The remaining statements are explained separately. See CLI Explorer. | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Configure an Event Policy to Execute Operational Mode Commands"
] |
exercise | request protection-group ethernet-aps exercise md <md> ma <ma> | [edit protocols protection-group ethernet-aps] | This configuration statement is used to test if APS is operating correctly, it does not interrupt regular
APS operations. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"Ethernet Automatic Protection Switching Overview"
] | |
exit | exit <configuration-mode> | Exit the current level of the statement hierarchy, returning to the level prior to the last edit command, or
exit from configuration mode. The quit and exit commands are synonyms. | [
{
"name": "none",
"desc": "Return to the previous edit level. If you are at the top of the statement hierarchy, exit configuration mode."
},
{
"name": "configuration-mode",
"desc": "(Optional) Exit from configuration mode."
}
] | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy. | Command introduced before Junos OS Release 7.4. | [
"Displaying the Current Configuration"
] | |
exp (Class of Service) | Classifier Configuration
exp classifier-name {
import (classifier-name | default);
forwarding-class class-name {
loss-priority level {
code-points [ aliases ] [ bit-patterns ];
}
}
}
Rewrite Rule Configuration
exp rewrite-name {
import (rewrite-name | default);
forwarding... | [edit class-of-service classifiers]
[edit class-of-service code-point-aliases],
[edit class-of-service rewrite-rules]
[edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules],
[edit class-of-service system-defaults classifiers] | Define the EXP code point mapping that is applied to MPLS packets. EXP classifiers are not applied to
any traffic except MPLS traffic. EXP classifiers are applied only to interfaces that are configured as family
mpls (for example, set interfaces xe-0/0/35 unit 0 family mpls.)
There are no default EXP classifiers. You c... | [
{
"name": "classifier-name",
"desc": "Name of the EXP classifier."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X50. | [
"Configuring Rewrite Rules for MPLS EXP Classifiers",
"Understanding CoS MPLS EXP Classifiers and Rewrite Rules",
"Understanding Applying CoS Classifiers and Rewrite Rules to Interfaces",
"Understanding Using CoS with MPLS Networks on EX Series Switches",
"MPLS on Provider and Provider Edge Devices Configur... |
exp (Rewrite rules) | exp (rewrite-name | default) protocol protocol-types; | [edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules] | Apply an MPLS experimental (EXP) rewrite rule.
On segment routing LSPs, applying an EXP rewrite rule to the egress interface on the ingress (provider
edge) router of a segment-routing network imposes the rewrite rule to all transport labels in the stack.
As a result, you don't need to configure rewrite rules on every s... | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules exp] hierarchy level."
},
{
"name": "default",
"desc": "The default mapping. By default, IP precedence rewrite rules alter the first three bits on the type-of-service (ToS) b... | 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.
Support for PTX platforms running Junos OS Evolved added with Junos OS Evolved Release 22.4. | [
"Configuring Rewrite Rules",
"Rewriting the EXP Bits of All Three Labels of an Outgoing Packet",
"Applying Rewrite Rules to Output Logical Interfaces"
] |
exp-push-push-push | exp-push-push-push default; | [edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules] | Rewrite the EXP bits of all three labels of an outgoing packet, thereby maintaining CoS of an incoming
non-MPLS packet. | [
{
"name": "default",
"desc": "Apply the default MPLS EXP rewrite table."
}
] | 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. | [
"Rewriting the EXP Bits of All Three Labels of an Outgoing Packet"
] |
exp-swap-push-push | exp-swap-push-push default; | [edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules] | Rewrite the EXP bits of all three labels of an outgoing packet, thereby maintaining CoS of an incoming
MPLS packet. | [
{
"name": "default",
"desc": "Apply the default MPLS EXP rewrite table."
}
] | 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. | [
"Rewriting the EXP Bits of All Three Labels of an Outgoing Packet"
] |
expand-loose-hop | expand-loose-hop; | [edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls] | Allow an LSP to traverse multiple OSPF areas within a service provider’s network.
Allows a point-to-multipoint LSP to span multiple domains in a network. Effectively, this allows you to
configure one or more sub-LSPs (branches) in separate network domains. Examples of such domains
include OSPF areas and autonomous syst... | [] | 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.
Point-to-multipoint LSP support introduced in Junos OS Release 11.2. | [
"Enabling Interarea Traffic Engineering",
"Configuring Inter-Domain Point-to-Multipoint LSPs"
] |
expansion-card (IPLC) | expansion-card {
fpc fpc-slot;
} | [edit chassis fpc fpc-slot optical-options] | Create a logical association between the specified IPLC base module and IPLC expansion module. The
IPLC base module can accept and multiplex (add) and demultiplex (drop) up to 32 individual wavelengths
into a single fiber pair. If you require the IPLC to support more than 32 channels, you can configure it to
support an... | [
{
"name": "fpc-slot",
"desc": "Specify the slot in which the IPLC expansion module resides. Range: 0 through 15 Default: None Example If the IPLC base module resides in slot 1 and the IPLC expansion module resides in slot 2:"
},
{
"name": "[edit]",
"desc": "user@host# set chassis fpc 1 optical... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Releases 15.1F6 and 17.1R1. | [
"Integrated Photonic Line Card Base and Expansion Module Overview",
"Understanding the Integrated Photonic Line Card Architecture",
"Increasing the Channel Capacity of the Node",
"Configuring a Two-Degree Node for Express Traffic"
] |
explicit-congestion-notification | explicit-congestion-notification; | [edit class-of-service schedulers scheduler-name] | Enable explicit congestion notification (ECN) on the output queue (forwarding class) or output queues
(forwarding classes) mapped to the scheduler. ECN enables end-to-end congestion notification between
two endpoints on TCP/IP based networks. The two endpoints are an ECN-enabled sender and an ECN-
enabled receiver. ECN... | [] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51.
Statement supported on SRX380, SRX300, SRX320, SRX340, SRX345, vSRX3.0, and NFX devices in
Junos OS Release 22.2R1. | [
"Example: Configuring ECN",
"Understanding CoS Explicit Congestion Notification"
] |
explicit-null (Protocols BGP) | explicit-null; | [edit logical-systems logical-system-name protocols mpls],
[edit logical-systems logical-system-name protocols bgp family inet labeled-unicast],
[edit logical-systems logical-system-name protocols bgp family inet6 labeled-unicast],
[edit logical-systems logical-system-name protocols bgp group group-name family inet lab... | Advertise label 0 to the egress routing device of an LSP.
Default
If you do not include the explicit-null statement in the configuration, label 3 (implicit null) is advertised. | [] | 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. | [
"Advertising Explicit Null Labels to BGP Peers"
] |
explicit-null (Protocols LDP) | explicit-null; | [edit logical-systems logical-system-name protocols ldp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp],
[edit protocols ldp],
[edit routing-instances routing-instance-name protocols ldp] | Advertise label 0 to the egress router of a label-switched path (LSP).
Default
If you do not include the explicit-null statement in the MPLS configuration, label 3 (implicit null) is
advertised. | [] | 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 MPLS and LDP to Pop the Label on the Ultimate-Hop Router"
] |
explicit-null (Protocols MPLS) | explicit-null; | [edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls] | Advertise label 0 to the egress router of an LSP.
Default
If you do not include the explicit-null statement in the MPLS configuration, label 3 (implicit null) is
advertised.
NOTE: Junos OS does not support explicit null routes with next hops to virtual tunnel
(vt-) interfaces. | [] | 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 RSVP to Pop the Label on the Ultimate-Hop Router"
] |
explicit-null-cos | explicit-null-cos {
inet;
inet6;
} | [edit forwarding-options] | The default classification for explicit-null packets is based on the payload (IPv4 or IPv6 DSCP bits).
Configure this to make the packet classification based on the MPLS EXP value rather than on the
payload, thus preserving the MPLS classification of the packet. | [
{
"name": "inet",
"desc": "Use the MPLS EXP value for classification when the payload is an IPv4 packet."
},
{
"name": "inet6",
"desc": "Use the MPLS EXP value for classification when the payload is an IPv6 packet."
}
] | interface | Statement introduced in Junos OS Release 18.1. | [
"Applying MPLS EXP Classifiers for Explicit-Null Labels"
] |
explicit-priority | explicit-priority; | [edit logical-systems logical-system-name system syslog file filename],
[edit logical-systems logical-system-name system syslog host],
[edit system syslog file filename],
[edit system syslog host] | Record the priority (facility and severity level) in each standard-format system log message directed to a
file or remote destination.
When the structured-data statement is also included at the [edit system syslog file filename] hierarchy level,
this statement is ignored for the file. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Including Priority Information in System Log Messages",
"System Log Explorer"
] |
export (Bootstrap) | export [ policy-names ]; | [edit logical-systems logical-system-name protocols pim rp bootstrap family (inet | inet6)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp bootstrap family (inet | inet6)],
[edit protocols pim rp bootstrap family (inet | inet6)],
[edit routing-instances routing-inst... | Apply one or more export policies to control outgoing PIM bootstrap messages. | [
{
"name": "policy-names",
"desc": "Name of one or more import policies."
}
] | 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"
] |
export (ISIS) | export [ policy-names ]; | [edit logical-systems logical-system-name protocols isis],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
isis],
[edit protocols isis],
[edit routing-instances routing-instance-name protocols isis] | Apply one or more policies to routes being exported from the routing table into IS-IS.
All routing protocols store the routes that they learn in the routing table. The routing table uses this
collected route information to determine the active routes to destinations. The routing table then
installs the active routes in... | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | 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. | [] |
export (MPLS Traffic engineering database) | export {
credibility;
policy policy-name;
} | [edit logical-systems logical-system-name protocols mpls traffic-engineering database],
[edit protocols mpls traffic-engineering database] | Configure the traffic engineering database export-related parameters. | [
{
"name": "policy policy-name",
"desc": "Name of the export policy. The remaining statement is explained separately. See CLI Explorer."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
export (OSPF) | export [ policy-names ]; | [edit logical-systems logical-system-name protocols (ospf | ospf3)],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(ospf | ospf3)],
[edit logical-systems log... | Apply one or more policies to routes being exported from the routing table into OSPF. | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | 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 the realm statement introduced in Junos OS Release 9.2.
Support for the realm statement introduced in Junos OS Release 9.2 for EX Series switches. | [
"Understanding OSPF Routing Policy",
"Import and Export Policies for Network Summaries Overview"
] |
export (Protocols BGP) | export [ policy-names ]; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Apply one or more policies to routes being exported from the routing table into BGP.
If you specify more than one policy, they are evaluated in the order specified, from left to right, and the
first matching filter is applied to the route. If no routes match the filters, the routing table exports into
BGP only the rout... | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | 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 Routing Policies to Control BGP Route Advertisements",
"Routing Policies, Firewall Filters, and Traffic Policers User Guide"
] |
export (Protocols DVMRP) | export [ policy-names ]; | [edit logical-systems logical-system-name protocols dvmrp],
[edit protocols dvmrp] | Apply one or more policies to routes being exported from the routing table into DVMRP. If you specify
more than one policy, they are evaluated in the order specified, from first to last, and the first matching
policy is applied to the route. If no match is found, the routing table exports into DVMRP only the routes
tha... | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | NOTE: Distance Vector Multicast Routing Protocol (DVMRP) was deprecated in Junos
OS Release 16.1. Although DVMRP commands continue to be available and configurable
in the CLI, they are no longer visible and are scheduled for removal in a subsequent
release.
Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring DVMRP to Announce Unicast Routes"
] |
export (Protocols LDP) | export [ policy-names ]; | [edit logical-systems logical-system-name protocols ldp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp],
[edit protocols ldp],
[edit routing-instances routing-instance-name protocols ldp] | Apply policy filters to outbound LDP label bindings. Filters are applied to all label bindings from all
neighbors. | [
{
"name": "policy-names",
"desc": "Name of one or more routing policies."
}
] | 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. | [
"Filtering Outbound LDP Label Bindings"
] |
export (Protocols MSDP) | export [ policy-names ]; | [edit logical-systems logical-system-name protocols msdp],
[edit logical-systems logical-system-name protocols msdp group group-name],
[edit logical-systems logical-system-name protocols msdp group group-name peer address],
[edit logical-systems logical-system-name protocols msdp peer address],
[edit logical-systems lo... | Apply one or more policies to routes being exported from the routing table into MSDP. | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring MSDP in a Routing Instance"
] |
export (Protocols PIM) | export [ policy-names ]; | [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim] | Apply one or more export policies to control outgoing PIM join and prune messages. PIM join and prune
filters can be applied to PIM-SM and PIM-SSM messages. PIM join and prune filters cannot be applied
to PIM-DM messages. | [] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Filtering Outgoing PIM Join Messages"
] |
export (Protocols RIFT) | export {
northbound {
policy;
}
southbound {
policy;
allow-rift-routes;
}
} | [edit protocols rift] | Enable exporting of routes from other protocols into the RIFT protocol. | [
{
"name": "northbound",
"desc": "(Optional) Policy to advertise routes from other protocols using north external prefix topology information elements (TIEs)."
},
{
"name": "southbound",
"desc": "(Optional) Policy to advertise routes from other protocols using south external prefix TIEs."
},
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4R1. | [
"Understanding Junos Implementation of Routing in Fat Tree (RIFT) Protocol"
] |
export (Protocols RIPng) | export [ policy-names ]; | [edit logical-systems logical-system-name protocols ripng group group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ripng group group-name],
[edit protocols ripng group group-name],
[edit routing-instances routing-instance-name protocols ripng group group-name] | Apply a policy or list of policies to routes being exported to the neighbors.
By default, RIPng does not export routes it has learned to its neighbors. To have RIPng export routes,
apply one or more export policies. To apply export policies and to filter routes being exported from the
local routing device to its neighb... | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for routing instances introduced in Junos OS Release 9.0. | [] |
export (RIP) | export [ policy-names ]; | [edit logical-systems logical-system-name protocols rip group group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip
group group-name],
[edit protocols rip group group-name],
[edit routing-instances routing-instance-name protocols rip group group-name] | Apply a policy to routes being exported to the neighbors.
By default, RIP does not export routes it has learned to its neighbors. To enable RIP to export routes,
apply one or more export policies.
If no routes match the policies, the local routing device does not export any routes to its neighbors.
Export policies over... | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | 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. | [] |
export (Routing Options) | export [ policy-name ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options forwarding-table],
[edit logical-systems logical-system-name routing-options forwarding-table],
[edit routing-instances routing-instance-name routing-options forwarding-table],
[edit routing-options forwarding-table] | Apply one or more policies to routes being exported from the routing table into the forwarding table.
In the export statement, list the name of the routing policy to be evaluated when routes are being
exported from the routing table into the forwarding table. Only active routes are exported from the
routing table.
You ... | [
{
"name": "policy-name",
"desc": "Name of one or more policies."
}
] | 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: Load Balancing BGP Traffic"
] |
export-by-asic | export-by-asic; | [edit services inline-monitoring instance] | For those line cards that support the BX ASIC, configure this statement to export IPFIX packets using
the ASIC, for Inline Monitoring Services (IMON). Both the Packet Forwarding Engine on the sampling
line card and the Packet Forwarding Engine on the export line card must be running in BX-v2 mode to
support this featur... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 24.4R1. | [] |
export-extension | export-extension (app-id | flow-dir); | [edit services flow-monitoring version9 template name ipv4-template]
[edit services flow-monitoring version9 template name ipv6-template]
[edit services flow-monitoring version-ipfix template name ipv4-template]
[edit services flow-monitoring version-ipfix template name ipv6-template] | (SRX Firewalls only) Add additional fields to the template. | [
{
"name": "app-id",
"desc": "Add the application ID field."
},
{
"name": "flow-dir",
"desc": "Add the flow direction field."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | [] | |
export-format (Flow Monitoring) | export-format format; | [edit forwarding-options monitoring name output] | Flow monitoring export format. | [
{
"name": "format",
"desc": "Format of the flows."
}
] | 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. | [
"Exporting Flows",
"Configuring Passive Flow Monitoring"
] |
export-format (JSON) | export-format {
json {
ietf;
verbose;
}
state-data {
json {
compact;
}
}
} | [edit system] | Specify the default implementation of the serialization to use for exported data in the given format. This
statement affects configuration data and command output that is displayed in the requested format. | [
{
"name": "json",
"desc": "Define which implementation of the serialization to use for configuration data emitted in JavaScript Object Notation (JSON) format. Acceptable values include:"
},
{
"name": "ietf",
"desc": "Emit JSON data according to the encoding rules defined in Internet drafts draft... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 16.1.
state-data json compact statement added in Junos OS Release 17.3R1.
state-data json compact statement deprecated in Junos OS Release 24.4R1 and Junos OS Evolved Release
24.4R1. | [
"Map Junos OS Configuration Statements to JSON",
"Map Junos OS Command Output to JSON in the CLI"
] |
export-profile (Junos Telemetry Interface) | export-profile name {
dscp value;
forwarding-class (assured-forwarding | best-effort | expedited-forwarding | network-
control);
local-address ip-address;
local-port source-port-number;
loss-priority (high | low | medium-high | medium-low);
<payload-size bytes>;
reporting-rate seconds;
... | [edit services analytics] | Configure the parameters of the export process for data generated through Junos Telemetry sensors.
You can create one or more export profiles. Each profile can be associated with one or more sensors that
define the system resource to monitor and stream data. You can associate only one export profile with a
specific sen... | [
{
"name": "name",
"desc": "Name of export profile. NOTE: To associate this export profile with a configured sensor, include the name you configure for the export-profile statement at the [edit services analytics sensor sensor-name export-name] hierarchy level."
},
{
"name": "dscp value",
"desc":... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F3.
payload-size bytes option introduced in Junos OS Release 16.1R3.
loss-priority option introduced in Junos OS Release 17.3R1 for MX Series routers only.
Statement introduced in Junos OS Release 17.4R1 for virtual MX Series (vMX) routers.
dialout-type option introduced in ... | [] |
export-profiles | export-profiles {
profile-name {
interface {
information;
statistics {
queue;
traffic;
}
status {
link;
queue;
traffic;
}
}
stream-format format;
... | [edit services analytics] | Configure an profile to specify the network analytics data being streamed to remote servers. Each profile
is a template that defines the type of data being streamed.
NOTE: The export-profile statement is not available in Junos OS Releases prior to
13.2X51-D15. | [
{
"name": "profile-name",
"desc": "Name of the export profile containing the configuration of the data being streamed."
},
{
"name": "stream-format",
"desc": ""
},
{
"name": "format",
"desc": "Format of the streaming data being sent to a server. Only one format can be sent to each po... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Network Analytics Overview"
] |
export-rib | export-rib routing-table-name; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib-groups group-name],
[edit logical-systems logical-system-name routing-options rib-groups group-name],
[edit routing-instances routing-instance-name routing-options rib-groups group-name],
[edit routing-options rib-gro... | Specify the name of the routing table from which Junos OS should export routing information. For any
individual RIB group, only one table can be specified in the export-rib statement.
The export-rib statement specifies the source table from which routing information is advertised.
One common use of the export-rib state... | [
{
"name": "routing-table-name",
"desc": "Routing table group 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: Exporting Specific Routes from One Routing Table Into Another Routing Table",
"Example: Configuring a PIM RPF Routing Table",
"Example: Configuring DVMRP to Announce Unicast Routes",
"Example: Configuring a Dedicated PIM RPF Routing Table",
"Example: Configuring Any-Source Multicast for Draft-Rose... |
export-target | export-target {
target target-community;
unicast;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols mvpn
route-target],
[edit routing-instances routing-instance-name protocols mvpn route-target] | Enable you to override the Layer 3 VPN import and export route targets used for importing and
exporting routes for the MBGP MVPN network layer reachability information (NLRI). | [
{
"name": "target target-community",
"desc": "Specify the export target community."
},
{
"name": "unicast",
"desc": "Use the same target community as specified for unicast."
}
] | 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. | [] |
express-in (IPLC) | express-in {
fpc fpc-slot;
} | [edit chassis fpc fpc-slot optical-options] | Create a logical connection for between two IPLC base modules to form a two-degree IPLC node. By
using this statement, along with connecting two IPLC base modules together through the front panel,
you create a two-degree IPLC node that can communicate either east-west or north-south. You can use
this option for express... | [
{
"name": "fpc-slot",
"desc": "Specify the location of the IPLC base module. Default: None Example To create a logical connection between the IPLC base modules in slots 1 and 2:"
},
{
"name": "[edit]",
"desc": "user@host# set chassis fpc 1 optical-options express-in fpc 2"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Releases 15.1F6 and 17.1R1. | [
"Bypassing a Wavelength",
"Integrated Photonic Line Card Base and Expansion Module Overview",
"Understanding the Integrated Photonic Line Card Architecture",
"Configuring the Integrated Photonic Line Card to Switch Wavelengths to Local or Remote Optical",
"Interfaces"
] |
expression | expression boolean-expression; | [edit security idp custom-attack attack-name attack-type chain] | Configure the Boolean expression. The Boolean expression defines the condition for the individual
members of a chain attack that will decide if the chain attack is hit.
For standalone IDP devices, expression overrides order function.
For SRX Series Firewalls, expression and order cannot be configured together. Only one... | [
{
"name": "boolean-expression",
"desc": "Boolean operators:"
},
{
"name": "or",
"desc": "If either of the member name patterns match, the expression matches."
},
{
"name": "and",
"desc": "If both of the member name patterns match, the expression matches. It does not matter which"
}... | 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. | [] |
extend-secondary-vlan-id | extend-secondary-vlan-id number; | [edit vlans vlan-name pvlan] | Configure traffic that egresses from a secondary VLAN trunk port to retain its secondary VLAN tag
instead of getting the tag of the primary VLAN that the secondary port is a member of. | [] | 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 PVLANs with Secondary VLAN Trunk Ports and Promiscuous Access Ports on a",
"QFX Series Switch"
] |
extended-echo | extended-echo; | [edit system] | Configure ICMP extended echo to enable the probe command. On enabling this statement on the proxy
node, you can query for the status of the probed interface. The ICMP extended echo and ICMP
extended reply messages are used for the communication between the probing interface and the probed
interface through the proxy in... | [] | system-To view this statement in the configuration. | Statement introduced in Junos OS Release 20.3R1. | [
"How to Use the Probe Command"
] |
extended-gateway (sFlow) | extended-gateway {
communities {
count count;
}
destination-as-path {
count count;
}
} | [edit protocols sflow family inet structure-list] | Configure extended-gateway to export the extended gateway structure in sFlow records. By default, it
exports the following fields:
•
next-hop
•
local AS number
•
source autonomous system (src-as)
•
src_peer_as
•
localpref
To export additional fields, such as dst_as_path and communities, configure the destination-as-pat... | [
{
"name": "communities",
"desc": "Configure communities to export community entries in the extended gateway structure. If you configure communities with count option, the number of community entries exported is equal to the configured count and if you do not configure count option, the number of communities... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.2R1. | [] |
extended-isid-list | extended-isid-list (single-isid | isid-list |isid-range | all); | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols]
[edit routing-instances routing-instance-name protocol evpn] | Specify the service identifiers (ISIDs) that are being extended over the Ethernet VPN (EVPN) core.
NOTE: When you deactivate the extended-isid-list statement, with or without
configuring the automatic derivation of the BGP route target (auto-RT) for advertised
prefixes, both Type 2 and Type 3 routes are retained. | [
{
"name": "single-isid",
"desc": "Specify a single ISID."
},
{
"name": "isid-list",
"desc": "Specify a list of multiple ISIDs."
},
{
"name": "isid-range",
"desc": "Specify a range of ISIDs."
},
{
"name": "all",
"desc": "Specify that all ISIDs are being extended over the E... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1.
Support for logical systems on MX Series routers added in Junos OS Release 17.4R1. | [] |
extended-nexthop | extended-nexthop; | [edit logical-systems name protocols bgp family inet unicast],
[edit logical-systems name protocols bgp family inet inet6 unicast],
[edit logical-systems name protocols bgp group name family inet unicast],
[edit logical-systems name protocols bgp group name family inet inet6 unicast],
[edit logical-systems name protoco... | Configure extended next-hop encoding for BGP groups with IPv6 peers to route IPv4 address families
over an IPv6 session. Configure dynamic IPv4-over-IPv6 tunnels and define their attributes to forward
IPv4 traffic over an IPv6-only network. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R1. | [
"Understanding Redistribution of IPv4 Routes with IPv6 Next Hop into BGP"
] |
extended-nexthop-color | extended-nexthop-color; | [edit logical-systems name protocols bgp family (inet | inet6) unicast],
[edit logical-systems name protocols bgp group name family (inet | inet6) unicast],
[edit logical-systems name protocols bgp group name neighbor name family (inet |inet6) unicast],
[edit protocols bgp family (inet | inet6) unicast],
[edit protocol... | Enable this option to steer a packet using a segment routing traffic engineering policy. Configure a color
attribute for a BGP family or group to resolve the path. This option is disabled by default and prefixes
with color community are resolved over the standard BGP tables. However, with this option configured,
prefi... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1 on the MX Series and PTX Series with FPC-PTX-P1-
A. | [
"segment-list",
"BGP Egress Traffic Engineering"
] |
extended-nexthop-tunnel | extended-nexthop-tunnel; | [edit protocols bgp group group-name family inet unicast],
[edit protocols bgp group group-name family inet6 unicast] | Configure the tunnel attribute to transition the BGP signaling of MPLS-over-UDP dynamic nexthop
tunnels to IP-over-IP tunnels. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.3R1. | [
"Overview of Next-Hop-Based Dynamic Tunneling Using IP-Over-IP Encapsulation"
] |
extended-space | extended-space; | [edit logical-systems logical-system-name routing-options forwarding-table chained-composite-
next-hop ingress l3vpn],
[edit routing-options forwarding-table chained-composite-next-hop ingress l3vpn] | Accept more than one million Layer 3 VPN BGP updates with unique inner VPN labels. The neighboring
PE routers are typically from other vendors and configured to assign a unique inner label to each Layer 3
VPN BGP route.
NOTE: This statement is supported on Juniper Networks routers containing only MPCs
and MICs and with... | [] | 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. | [
"Accepting Route Updates with Unique Inner VPN Labels in Layer 3 VPNs"
] |
extended-statistics | extended-statistics; | [edit chassis] | (MX Series routers only) Enable accounting of system statistics for IPv4 and IPv6 traffic.
Default
Accounting of system statistics is disabled. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"show system statistics"
] |
extended-system-id | extended-system-id identifier; | [edit logical-systems logical-system-name protocols rstp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
rstp],
[edit protocols rstp],
[edit routing-instances routing-instance-name protocols rstp] | The extended system ID is used to specify different bridge identifiers for different RSTP or STP routing
instances. | [
{
"name": "identifier",
"desc": "Specify the system identifier to use for the RSTP or STP instance."
}
] | 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.
Support for logical systems added in Junos OS Release 9.6. | [
"Configuring Rapid Spanning Tree Protocol",
"Configuring RSTP on EX Series Switches (CLI Procedure)",
"Example: Configuring Faster Convergence and Network Stability on ELS Switches with RSTP",
"Understanding RSTP"
] |
extended-vlan-list | extended-vlan-list vlan-id | [vlan-id set]; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols]
[edit routing-instances routing-instance-name instance-type virtual-switch protocols evpn] | Specify the VLAN or range of VLANs that are extended over the WAN, wherein all the single VLAN
bridge domains corresponding to these VLANs are stretched.
NOTE: The extended-vni-list statement is an exclusive command. You cannot configure
the extended-vni-list statement with either the extended-vlan-list or extended-vni... | [
{
"name": "vlan-id",
"desc": "VLAN ID to be EVPN extended."
},
{
"name": "vlan-id set",
"desc": "List of VLAN IDs to be EVPN extended. Range: 1 through 4094 VLANs"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1.
Support for logical systems on MX Series routers added in Junos OS Release 17.4R1. | [] |
extended-vni-all | extended-vni-all; | For QFX5100 and EX4600 switches:
{edit protocols evpn]
For MX Series routers:
[edit routing-instances routing-instance-name protocols evpn] | Include all VXLAN Network Identifiers (VNIs) as part of the Virtual Switch (VS) instance. By specifying
all, you bypass the commit check process and all configured bridge domains (BDs) in the Ethernet Virtual
Private Network (EVPN) are considered extended.
NOTE: The extended-vni-list statement is an exclusive command.... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D30. | [
"Example: Configuring an EVPN Control Plane and VXLAN Data Plane",
"Understanding EVPN with VXLAN Data Plane Encapsulation",
"EVPN Over VXLAN Encapsulation Configuration Overview for QFX Series and EX4600 Switches"
] |
extended-vni-list | extended-vni-list [list of VNIs | all]; | For MX Series routers, EX9200, and QFX Series switches:
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit routing-instances routing-instance-name protocols evpn] | Establishes which VXLAN Network Identifiers (VNI) will be part of the Virtual Switch (VS) instance.
When you issue the commit check command to verify the candidate configuration syntax without
committing it, it also checks if the specified VNI(s) is associated with a bridge domain (BD) (bridge-domain
name vxlan vni).
T... | [
{
"name": "list of",
"desc": ""
},
{
"name": "VNIs",
"desc": "Specify a single VNI or list of VNIs as part of the VS instance, for example extended-vni-list [ 10-50 60 70]."
},
{
"name": "all",
"desc": "Include all VNIs as part of the VS instance. By specifying all, you bypass the co... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D15.
Support for logical systems on MX Series routers added in Junos OS Release 17.4R1. | [
"Example: Configuring an EVPN Control Plane and VXLAN Data Plane",
"Understanding EVPN with VXLAN Data Plane Encapsulation",
"EVPN Over VXLAN Encapsulation Configuration Overview for QFX Series and EX4600 Switches",
"show configuration protocols evpn",
"Implementing EVPN-VXLAN for Data Centers"
] |
Extensible Subscriber Services | extensible-subscribe-services {
access-profile access-profile-name;
commit-interval interval;
dictionary dictionary-path;
flat-file-profile flat-file-profile;
logical-interface-init-range {
high;
low;
}
maximum-subscribers limit;
} | [edit system services] | Configure the extensible subscriber services manager. Extensible Subscriber Services Manager (ESSM) is
a background process that is part of the Intelligent Customer Extendable authentication, authorization,
and accounting (ICE-AAA) framework, which supports customer extensible services for both business
and residential... | [
{
"name": "access-profile",
"desc": "Access profile name for time-accounting specified using this configuration. In most cases access-profile radius server information is same as control session access-profile. It is a mandatory configuration."
},
{
"name": "commit-interval",
"desc": "The ESSM d... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1R1. | [] |
extension-header | extension-header {
destination-option {
home-address {
match (equal | greater-than | less-than | not-equal);
value header-value;
}
option-type {
match (equal | greater-than | less-than | not-equal);
value header-value;
}... | [edit set security idp custom-attack attack-name attack-type signature protocol ipv6] | Specify the IPv6 extension header. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
extension-provider | extension-provider {
control-cores control-number;
data-cores data-number;
data-flow-affinity {
hash-key (layer-3 | layer-4);
}
forwarding-db-size size;
object-cache-size size;
package package-name;
policy-db-size size;
syslog {
facility {
severity;
... | [edit chassis fpc slot-number pic pic-number adaptive-services service-package] | Configure an application on a PIC.
CAUTION: Do not configure these settings unless it is specified you should do so. The
default settings work under most normal scenarios. Unneeded settings can cause
negative effects.
NOTE: The PICs of MS-MPC and MS-MIC support only extension-provider service-
package.
When the extensi... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [] |
extension-service (System Extensions) | extension-service {
application {
file script-name {
arguments arguments;
cert-file path;
checksum (md5 | sha-256 | sha1) hash;
daemonize;
interpreter (bash | python | python3);
optional;
refresh;
refresh-from... | [edit system extensions] | 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... | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 16.1. | [] |
extension-service (System Services) | extension-service {
request-response {
grpc {
max-connections max-connections;
routing-instance routing-instance;
ssl {
address ip-address;
hot-reloading;
local-certificate local-certificate;
mutual-authentic... | [edit system services] | 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... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1.
grpc option introduced in Junos OS Release 16.2. | [] |
extensions | extensions {
extension-service {
application {
file script-name {
arguments arguments;
cert-file path;
checksum hash-algorithm hash-value;
daemonize;
interpreter (bash | python | python3);
optional; ... | [edit system] | 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... | [] | 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.
extension-service option introduced in Junos OS Release 16.1. | [] |
external-assigned (Address Pools) | external-assigned; | [edit access address-assignment address-pools name family inet network network-prefix],
[edit access address-assignment address-pools name family inet6 network network-prefix] | Assign addresses in network prefixes statically. | [] | 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. | [
"Understanding Source IP Filtering with Address Pools in TDF Domains for IP-Based Subscribers",
"Configuring Address Pools for Source-IP Filtering of IP-Based Subscribers"
] |
external-authority | external-authority; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server pool-match-order],
[edit logical-systems logical-system-name system services dhcp-local-server pool-match-order],
[edit routing-instances routing-instance-name system services dhcp-local-server pool-matc... | Specify that an external authority (for example, RADIUS or Diameter) provides the address assignment.
When RADIUS is the external authority, the router uses the Framed-IPv6-Pool attribute (RADIUS
attribute 100) to select the pool. When Diameter is the external authority, the router uses the Diameter
counterpart of RADI... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Configuring How the Extended DHCP Local Server Determines Which Address-Assignment Pool to",
"Use",
"Understanding Differences Between Legacy DHCP and Extended DHCP",
"Address-Assignment Pools Overview",
"F"
] |
f-max-period (rtp) | f-max-period number; | [edit interfaces interface-name unit logical-unit-number compression rtp],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
compression rtp] | Specify the maximum number of compressed packets allowed between the transmission of full headers
in a compressed Real-time Transport Protocol (RTP) traffic stream. | [
{
"name": "number",
"desc": "Maximum number of packets."
}
] | 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 Compression of Voice Traffic"
] |
f-max-period | f-max-period number; | [edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-name unit logical-unit-number rtp] | For all adaptive services interfaces and for ISDN interfaces on J Series Services Routers. Specify the
maximum number of compressed packets allowed between the transmission of full headers in a
compressed Real-Time Transport Protocol (RTP) traffic stream. | [
{
"name": "number",
"desc": "Maximum number of packets. The value can be from 1 through 65535."
}
] | 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 Bandwidth on Demand",
"Junos OS Services Interfaces Library for Routing Devices"
] |
fabric (Class-of-Service) | fabric {
scheduler-map {
priority (high | low) scheduler scheduler-name;
}
} | [edit class-of-service] | Define CoS parameters of the switch fabric. For M320 routers, MX Series routers, T Series routers and
EX Series switches only, associate a scheduler with a fabric priority.
On EX Series switches, this statement is supported only on EX8200 standalone switches and EX8200
Virtual Chassis.
The remaining statements are expl... | [] | 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"
] |
fabric (OAM) | fabric {
fabric-maintenance-associations {
fma-name {
description string;
fabric-maintenance-end-points {
fmep-id {
description string;
fmep-interface interface-name;
fmep-name name;
}
... | [edit protocols oam] | Configure the fabric maintenance association (FMA) and flow specification parameters for internal fabric
monitoring.
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 12.2. | [
"Overview of Internal Fabric Monitoring",
"Configuring a Fabric Maintenance Association",
"Configuring Flow Specifications"
] |
fabric loopback wan | fabric loopback wan (off | on); | [edit chassis fpc slot-number] | Allow the fabric bound packets to take new fabric loopback path, freeing up the WAN bandwidth thus
improving the sampling and tunneling performance of the router.
You can configure fabric side loopback by using the fabric loopback wan off option or switch to WAN side
by using the fabric loopback wan on option. By defau... | [
{
"name": "off",
"desc": "Configure fabric bound packets to take fabric loopback path."
},
{
"name": "on",
"desc": "Configure fabric bound packets to take the WAN loopback path."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.3. | [] |
fabric | fabric
aliases {
director-device director-device-name {
assigned-director-device-name;
}
interconnect-device interconnect-device-name {
assigned-interconnect-device-name;
}
node-device node-device-name {
assigned-node-device-name;
}... | [edit] | (QFabric systems only) Define resources, routing options, fabric control protocol settings, and the
mapping of user-defined names to QFabric system components.
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 11.3. | [
"Understanding QFabric System Administration Tasks and Utilities"
] |
fabric-advertise | fabric-advertise {
route destination {
backup-color backup-color;
color color;
}
} | [edit logical-systems name protocols bgp],
[edit protocols bgp], | Advertise routes assigned with specific fabric colors. BGP advertises the routes based on the color
configuration without relying on a routing policy. When a neighbor is colored, only routes with the same
color or uncolored routes are allowed to be advertised via this neighbor. If there is a color mismatch on
the rece... | [
{
"name": "route destination",
"desc": "Specify a route that you want to advertise."
},
{
"name": "backup-color",
"desc": ""
},
{
"name": "backup-color",
"desc": "(Optional) Configure route advertisement with a backup color. The route is advertised over the primary and backup colored... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1 | [
"BGP Deterministic Path Forwarding in a CLOS Network"
] |
fabric-color | fabric-color fabric-color; | [edit logical-systems name protocols bgp],
[edit logical-systems name protocols bgp group group-name],
[edit logical-systems name protocols bgp group group-name neighbor address],
[edit protocols bgp],
[edit protocols bgp group group-name],
[edit protocols bgp group group-name neighbor address] | Specify a fabric color to a single-hop external BGP (EBGP) neighbor at the global, group or neighbor
level. When a neighbor is colored, only routes with the same color or uncolored routes are allowed to be
advertised via this neighbor. A route with no color community assigned can be advertised over any
colored or uncol... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [
"BGP Deterministic Path Forwarding in a CLOS Network"
] |
fabric-control | fabric-control {
graceful-restart {
restart-timeseconds;
stale-routes-time seconds;
}
} | [edit fabric protocols] | 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"
] |
fabric-id | fabric-id fc-fabric-id; | [edit fc-fabrics fc-fabric-name] | Configure a unique identifier for the FC fabric.
NOTE: Changing the ID of an FC fabric causes all logins to drop and forces the ENodes
to log in again. | [
{
"name": "fc-fabric-id",
"desc": "Unique identifier of the FC fabric."
}
] | 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 an FCoE-FC Gateway Fibre Channel Fabric",
"Understanding an FCoE-FC Gateway"
] |
fabric-interfaces | fabric-interfaces {
node-group (node-group-name | all) {
oxid (enable | disable);
}
} | [edit forwarding-options hash-key family fcoe] | Specify that you are enabling or disabling OxID hash control on the fabric ports of a QFabric system
Node group. OxID hash control is enabled or disabled on the fabric ports that face an FCoE forwarder
(FCF). | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X52-D10. | [
"Enabling and Disabling CoS OxID Hash Control for FCoE Traffic on QFabric Systems",
"Understanding OxID Hash Control for FCoE Traffic Load Balancing on QFabric Systems"
] |
fabric-load-balance | fabric-load-balance {
flowlet {
inactivity-interval interval;
}
per-packet;
} | [edit forwarding-options enhanced-hash-key] | Enable adaptive load balancing (ALB) for a VCF, and specify how ALB is implemented.
NOTE: Starting in Junos OS Release 14.1X53-D46, 15.1R7, 16.1R6, 17.1R3, 17.2R2,
17.3R2, and 17.4R1, the ALB feature is deprecated. If fabric-load-balance is enabled in the
configuration, delete the configuration item upon upgrading Juno... | [
{
"name": "flowlet",
"desc": "Implement ALB by using flowlets. When ALB is implemented using flowlets, traffic flows that enter the VCF are spliced into"
},
{
"name": "smaller flows",
"desc": "flowlets—and individually forwarded across the VCF to the same destination"
},
{
"name": "exper... | 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.
Statement deprecated starting in Junos OS Releases 14.1X53-D46, 15.1R7, 16.1R6, 17.1R3, 17.2R2,
17.3R2, and 17.4R1. | [
"Understanding Traffic Flow Through a Virtual Chassis Fabric"
] |
fabric-maintenance-associations | fabric-maintenance-associations {
fma-name {
description string;
fabric-maintenance-end-points {
fmep-id {
description string;
fmep-interface interface-name;
fmep-name name;
}
}
vlan-name vlan-name;
}
} | [edit protocols oam fabric] | Configure the fabric maintenance association (FMA) parameters for internal fabric monitoring. The FMA
defines a set of QFabric system interfaces (fabric maintenance endpoints [FMEPs]) that are members of
a given VLAN which are used in internal fabric monitoring operations. The FMA associates the set of
FMEPs with a VLA... | [
{
"name": "description string",
"desc": "Description of the FMA. Syntax: 1 to 128 alphanumeric characters"
},
{
"name": "fma-name",
"desc": "Name of the FMA. Syntax: 1 to 20 alphanumeric characters"
},
{
"name": "vlan-name vlan-name",
"desc": "Name of the VLAN for which the FMA is ... | 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. | [
"Overview of Internal Fabric Monitoring",
"Configuring a Fabric Maintenance Association",
"Configuring Flow Specifications"
] |
fabric-maintenance-end-points | fabric-maintenance-end-points {
fmep-id {
description string;
fmep-interface interface-name;
fmep-name name;
}
} | [edit protocols oam fabric fabric-maintenance-associations fma-name] | Configure the fabric maintenance association endpoint (FMEP) parameters within a fabric maintenance
association (FMA). The FMA associates the FMEP with a VLAN for purposes of internal fabric
monitoring. | [
{
"name": "description string",
"desc": "Description of the FMEP. Syntax: 1 to 128 alphanumeric characters"
},
{
"name": "fmep-id",
"desc": "32-bit integer that is used to identify an FMEP. Range: 1 to 64,000"
},
{
"name": "fmep-name name",
"desc": "Name of the fabric maintenance a... | 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. | [
"Overview of Internal Fabric Monitoring",
"Configuring a Fabric Maintenance Association",
"Configuring Flow Specifications"
] |
fabric-options | fabric-options {
member-interfaces member-interface-name;
} | [edit interfaces interface-name] | Configure fabric interface specific options in chassis clusters.
The fabric is the data link between the nodes and is used to forward traffic between the chassis. Each
node in the chassis requires a fabric interface configured. To create a fabric link between the two chassis
requires the creation of a special interfac... | [
{
"name": "member-interface-name",
"desc": "Member interface name."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Example: Configuring the Chassis Cluster Fabric Interfaces"
] |
fabric-tree-root | fabric-tree-root; | [edit virtual-chassis member member-id] | Optionally specify a member of a VCF to be a root node for creating the shared multicast distribution
trees (MDTs) used in forwarding broadcast, unknown unicast, and multicast (BUM) traffic within the VCF.
To configure this option, the VCF must be configured as "auto-provisioned" on page 2923 or
"preprovisioned" on pag... | [] | 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-D35. | [
"Autoprovisioning a Virtual Chassis Fabric",
"Preprovisioning a Virtual Chassis Fabric",
"Adding a Device to a Virtual Chassis Fabric"
] |
fabric-type | fabric-type proxy; | [edit fc-fabrics fc-fabric-name] | Specify that the FC fabric be an FCoE-FC gateway fabric. | [
{
"name": "proxy",
"desc": "Specify that the switch be an FCoE-FC gateway fabric."
}
] | 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 an FCoE-FC Gateway Fibre Channel Fabric",
"Understanding an FCoE-FC Gateway"
] |
facility | facility facility-type; | [edit event-options policy policy-name then priority-override] | Within an event policy, override the default facility type of the triggering event so that the event is
logged based on the configured facility type. | [] | 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"
] |
facility-override (Security) | facility-override facility; | [edit security log]
[edit logical-systems name security log]
[edit tenants tenant-name security log] | Alternate facility for logging to remote host.
System log server is set up to use a facility-override value to filter or write log files received by a system
log agent. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D35.
The [edit logical-systems name security log] and [edit tenants tenant-name security log] hierarchy levels
introduced in Junos OS Release 19.1R1. | [] |
facility-override (Service Sets) | facility-override facility-name; | [edit services service-set service-set-name syslog host hostname] | Override the default facility for system log reporting. | [
{
"name": "facility-name",
"desc": "Name of the facility that overrides the default assignment. Valid entries are:"
},
{
"name": "1. authorization",
"desc": ""
},
{
"name": "2. daemon",
"desc": ""
},
{
"name": "3. ftp",
"desc": ""
},
{
"name": "4. kernel",
"de... | 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 System Logging for Service Sets"
] |
facility-override (System Log Reporting) | facility-override facility-name; | [edit services l2tp tunnel-group group-name syslog host hostname] | Override the default facility for system log reporting. | [
{
"name": "facility-name",
"desc": "Name of the facility that overrides the default assignment. Valid entries include:"
},
{
"name": "1. authorization",
"desc": ""
},
{
"name": "2. daemon",
"desc": ""
},
{
"name": "3. ftp",
"desc": ""
},
{
"name": "4. kernel",
... | 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 System Logging of L2TP Tunnel Activity"
] |
facility-override | facility-override facility-name; | [edit interfaces interface-name services-options sysloghost hostname] | Override default facility for system log reporting. | [
{
"name": "facility-name",
"desc": "Name of facility that overrides the default assignment."
}
] | 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. | [
"Junos OS Services Interfaces Library for Routing Devices"
] |
fail | fail string; | [edit access firewall-authentication pass-through (ftp | http | telnet) banner],
[edit access firewall-authentication web-authentication banner] | Specify the banner that a client sees if the authentication process fails. | [
{
"name": "string",
"desc": "Banner text. Maximum length of the message text is 250 characters. Enclose the banner text"
},
{
"name": "within spaces or special characters",
"desc": "for example, quotation marks (” “)."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [
"External Authentication Servers",
"Configure a Custom Logo and Banner Messages"
] |
fail-filter (Dynamic Profiles) | fail-filter filter-name; | [edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family family rpf-
check],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family rpf-check] | Specify a filter that evaluates packets that fail a unicast RPF check. The filter determines what action to
take with the failed packets. If the fail filter is not configured, the failed packets are silently discarded. | [
{
"name": "filter-name",
"desc": "Name of the filter that evaluates packets that fail the RPF check."
}
] | 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. | [
"Unicast RPF in Dynamic Profiles for Subscriber Interfaces",
"Unicast RPF in Dynamic Profiles for Subscriber Interfaces",
"Understanding Unicast RPF (Routers)"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.