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 |
|---|---|---|---|---|---|---|---|
install | install {
ignore-version-check;
ignore-appid-failure;
} | [edit security idp security-package] | Configures the install command with ignore options. | [
{
"name": "ignore-version-check",
"desc": "Ignores version check during the installation of security packages."
},
{
"name": "ignore-appid-failure",
"desc": "Ignores application ID failure during the installation of security packages."
}
] | 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. | [] |
install-nexthop | install-nexthop (except | fallback | lsp lsp-name | lsp-regex lsp-regular-expression | non-
labelled-nexthop | non-lsp-nexthop | overlay-vxlan-interfaces | static-lsp lsp-name | static-
lsp-regex lsp-regular-expression) | strict | strict-named-lsp; | [edit logical-systems logical-system-name policy-options policy-statement policy-name term term-
name then],
[edit policy-options policy-statement policy-name term term-name then] | Select a specific label-switched path (LSP), or select an LSP from a set of similarly named LSPs as the
traffic destination for the configured community. Also can prevent the installation of any matching next
hops. | [
{
"name": "except",
"desc": "Prevent the installation of any matching next hops."
},
{
"name": "fallback",
"desc": "Backup option"
},
{
"name": "lsp lsp-name",
"desc": "Configure a specific LSP."
},
{
"name": "lsp-regex lsp-regular-expression",
"desc": "Configure a range ... | 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.
overlay-vxlan-interfaces statement introduced in Junos OS Release 22.4R1.
overlay-vxlan-interfaces statement introduced in Junos OS Evolved Release 22.4R1. | [
"Configuring the Policy Statement for the Layer 2 Circuit Community"
] |
instance (CASB) | instance instance-name {
application application-name;
domain domain-name;
instance-id instance-id;
tag tag-value;
type type;
} | [edit security casb] | Configure Cloud Access Security Broker (CASB) instance.
Configuring the CASB instance with specific parameters such as the application, instance ID, domain,
and type allows controlled access by differentiating between corporate and non-corporate usage of
cloud applications. | [
{
"name": "instance",
"desc": ""
},
{
"name": "instance-name",
"desc": "CASB instance name."
},
{
"name": "application",
"desc": ""
},
{
"name": "application-name",
"desc": "Application name."
},
{
"name": "domain",
"desc": ""
},
{
"name": "domain-name... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.2R1. | [] |
instance (Ephemeral Database) | instance instance-name {
cyclic-version version;
resize {
database-size-diff size MB;
database-size-on-disk size MB;
}
} | [edit system configuration-database ephemeral] | Enable an instance of the ephemeral configuration database.
The order in which the configuration lists the instances determines their priority when merging
conflicting configuration statements from different instances into the configuration. The instances are
listed in order from highest to lowest priority. In additio... | [
{
"name": "cyclic-version",
"desc": ""
},
{
"name": "version",
"desc": "Number of versions of the ephemeral instance's database for which the system stores deleted configuration objects. After each commit, the device reclaims the space occupied by objects deleted in the previous database version... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 16.2R2 and Junos OS Evolved Release 22.1R1.
cyclic-version statement introduced in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.2R1. | [
"Enabling and Configuring Instances of the Ephemeral Configuration Database",
"Example: Configuring the Ephemeral Configuration Database Using NETCONF",
"Understanding the Ephemeral Configuration Database"
] |
instance (Inline Monitoring) | instance name {
collector name;
controller name;
export-by-asic;
maximum-clip-length maximum-clip-length;
sampling-rate sampling-rate;
template-name template-name;
} | [edit services inline-monitoring] | Configure inline-monitoring instance parameters. You can use these instances along with firewall filters
to monitor different streams of traffic at different sampling rates from the same interface.
You can configure a maximum of sixteen (Junos OS) or seven (Junos OS Evolved) inline-monitoring
instances with four collec... | [
{
"name": "name",
"desc": "Name of instance."
},
{
"name": "collector name",
"desc": "Configure an collector for the inline-monitoring instance. See \"collector\" on page 4647 for more information."
},
{
"name": "controller",
"desc": "(Junos OS Evolved only) Configure inline-monitori... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS 19.4R1.
Statement introduced in Junos OS Evolved Release 22.2R1.
export-by-asic option introduced in Junos OS Evolved 24.4R1. | [
"Inline Monitoring Services Configuration"
] |
instance (OAM) | instance vpls-instance-name; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain name] | Specify the VPLS instance of the default maintenance domain. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Configuring Maintenance Intermediate Points (MIPs)"
] |
instance (Port Mirroring) | [edit forwarding-options port-mirroring] | Specify a port-mirroring configuration (instance). You do not specify an input for this instance. Instead,
you, create a firewall filter that specifies the required traffic and directs it to the mirror. This is useful for
controlling which types of traffic should be mirrored.
The remaining statements are explained sepa... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Understanding Port Mirroring and Analyzers",
"Configuring Port Mirroring",
"Examples: Configuring Port Mirroring for Local Analysis",
"Example: Mirroring Employee Web Traffic with a Firewall Filter"
] | |
instance (Sampling) | instance instance-name {
disable;
family (bridge | inet | inet6 | mpls | vpls) {
disable;
output {
aggregate-export-interval seconds;
flow-active-timeout seconds;
flow-inactive-timeout seconds;
flow-server hostname {
aggregation {
... | [edit forwarding-options sampling] | Configure a sampling instance.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 17.2R1 for QFX10002 switches.
Support for IPv6 addresses for the flow-server address and source-address address statements within
sampling instances introduced in Junos OS Evolved Release 23.1R1. | [
"Configuring Sampling Instance on MX, M and T Series Routers or QFX Series Switches"
] |
instance (Traffic Load Balancer) | instance instance-name {
client-interface client-interface;
client-vrf client-vrf;
group group-name {
health-check-interface-subunit health-check-interface-subunit;
network-monitoring-profile profile-name;
real-service-rejoin-options no-auto-rejoin;
real-services [ server-lis... | [edit services traffic-load-balance] | Configure a Traffic Load Balancer instance. | [
{
"name": "client-interface",
"desc": ""
},
{
"name": "client-interface",
"desc": ""
},
{
"name": "client-vrf client-vrf",
"desc": "Use the specified name of the routing instance in which the data traffic in the reverse direction is routed to the clients."
},
{
"name": "insta... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Traffic Load Balancer Overview",
"Configuring TLB"
] |
instance | instance {
instance-name {
input {
maximum-packet-length bytes;
rate number;
run-length number;
}
family (any | ccc| inet | inet6 | mpls | vpls) {
output {
interface interface-name {
next-hop address;
... | [edit forwarding-options port-mirroring],
[edit routing-instances routing-instance-name forwarding-options port-mirroring] | Configure a port-mirroring instance. | [
{
"name": "port-mirroring-instance-name",
"desc": "Name of the port-mirroring instance."
}
] | interface—To view this statement in the configuration.
interface-control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3 (MX Series routers only).
Support extended to M120 and M320 routers in Junos OS Release 9.5.
maximum-packet-length and ccc options introduced in Junos OS Release 9.6 for M120 and M320
routers only.
server-profile option introduced in Junos OS Release 13.2 for PTX Series Pack... | [
"Configuring Port Mirroring",
"Configuring Active Flow Monitoring on PTX Series Packet Transport Routers"
] |
instance-export | instance-export [ policy-names ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options] | Apply one or more policies to routes being exported from a routing instance. | [
{
"name": "policy-names",
"desc": "Name of one or more export 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. | [
"Routing Policies, Firewall Filters, and Traffic Policers User Guide"
] |
instance-id | instance-id instance-id-value itid-disable; | [edit logical-systems name protocols isis-instance],
[edit protocols isis-instance] | Configure the attributes of a specific instance identifier. | [
{
"name": "instance-id-value",
"desc": "Instance Identifier Range: 1 through 65535"
},
{
"name": "itid-disable",
"desc": "Disable transmission of instance id in IID TLV and its receive validation"
}
] | 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. | [] |
instance-import | instance-import [ policy-names ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options] | Apply one or more policies to routes being imported into a routing instance. | [
{
"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 before Junos OS Release 7.4. | [
"Routing Policies, Firewall Filters, and Traffic Policers User Guide"
] |
instance-role | instance-role (access | nni); | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | Define the role of the routing instance in a Layer 2 Wholesale network. | [
{
"name": "access",
"desc": "Defines the connectivity role of the routing instance in a Layer 2 Wholesale network as an access"
},
{
"name": "nni",
"desc": "Defines the connectivity role of the routing instance in a Layer 2 Wholesale network as a network"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Separate Access Routing Instances for Layer 2 Wholesale Service Retailers",
"Configuring Separate NNI Routing Instances for Layer 2 Wholesale Service Retailers",
"Subscriber Management Overview"
] |
instance-shared | instance-shared; | [edit firewall family protocol-family-name filter filter-name],
[edit logical-systems logical-system-name firewall family protocol-family-name filter filter-
name] | Specify to share the firewall filter across multiple routing instances. By default, firewall filters are not
automatically shared across multiple instances. You can configure both shared and nonshared firewall
filters on the same routing device. This statement can be used only when network services for the
device are c... | [] | 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. | [
"Guidelines for Configuring Firewall Filters"
] |
instance-type | instance-type type; | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | Define the type of routing instance.
CAUTION: We strongly recommend that if you change an instance-type referenced under
a firewall filter, for example, from virtual-router to forwarding, make the change during a
maintenance window, as follows:
1. Deactivate the routing instance.
2. Change the instance-type.
3. Activa... | [
{
"name": "type",
"desc": "Can be one of the following:"
},
{
"name": "evpn",
"desc": "Enable an Ethernet VPN (EVPN) on the routing instance."
},
{
"name": "evpn-vpws",
"desc": "Enable an Ethernet VPN (EVPN) Virtual Private Wire Service (VPWS) on the routing"
},
{
"name": "fo... | 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.
virtual-switch and layer2-control options introduced in Junos OS Release 8.4.
mpls-internet-multicast option introduced in Junos OS Release 11.1 for the EX Series, M Series, MX Series,
and T Series.
evpn option introduced in Junos OS Release 13.2 for MX 3D Series router... | [
"Configuring EVPN Routing Instances",
"Configuring EVPN Routing Instances on EX9200 Switches",
"Configuring Virtual Router Routing Instances",
"Example: Configuring Filter-Based Forwarding on the Source Address",
"Example: Configuring Filter-Based Forwarding on Logical Systems",
"MAC-VRF Routing Instance ... |
integer | integer {
equals value;
greater-than value;
less-than value;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from attribute name
format] | Specify the custom AVP attribute’s format as an integer and the value to match for the incoming
RADIUS request from the IP-based subscriber.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selected.
Th... | [] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
intelligent-offload-tunable (IDP) | service name {
offload-limit bytes;
} | [edit logical-systems name security idp sensor-configuration global intelligent-offload-tunable],
[edit logical-systems name tenants name security idp sensor-configuration global intelligent-
offload-tunable],
[edit security idp sensor-configuration global intelligent-offload-tunable],
[edit tenants name security idp s... | Protocol-Specific Intelligent-Offload Configuration feature in Intrusion Detection and Prevention (IDP)
systems allows you to tailor inspection depth limits for different protocols, enhancing both performance
and security. By configuring individual offload limits for protocols such as SSH and FTP, you can optimize
reso... | [
{
"name": "name",
"desc": "Service name"
},
{
"name": "offload-limit",
"desc": "Service offload limit in bytes (bytes) Range: 0 through 4294967295."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.4R1. | [] |
intelligent-prescreening | intelligent-prescreening; | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name scan-
options]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name scan-
options] | 15.1X49-D10
The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1x49-
D10 onwards. | [] | 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 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Change History Table
Feature support is det... | [] |
inter-area-prefix-export | inter-area-prefix-export [ policy-names ]; | [edit logical-systems logical-system-name protocols ospf3 area area-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ospf3 area area-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ospf3 realm (ip4-unicast | ipv4-multicas... | Apply an export policy for OSPFv3 to specify which interarea prefix link-state advertisements (LSAs) are
flooded into an area. | [
{
"name": "policy-name",
"desc": "Name of a policy configured at the [edit policy-options policy-statement policy-name term term-name] hierarchy level."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
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. | [
"Import and Export Policies for Network Summaries Overview",
"Routing Policies, Firewall Filters, and Traffic Policers User Guide"
] |
inter-area-prefix-import | inter-area-prefix-import [ policy-names ]; | [edit logical-systems logical-system-name protocols ospf3 area area-id],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast) area area-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ospf3 area area-id],
[edi... | Apply an import policy for OSPFv3 to specify which routes learned from an area are used to generate
interarea prefixes into other areas. | [
{
"name": "policy-name",
"desc": "Name of a policy configured at the [edit policy-options policy-statement policy-name term term-name] hierarchy level."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
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. | [
"Import and Export Policies for Network Summaries Overview",
"Routing Policies, Firewall Filters, and Traffic Policers User Guide"
] |
inter-as (Routing Instances) | inter-as{
ingress-replication {
create-new-ucast-tunnel;
label-switched-path-template {
(default-template lsp-template-name);
}
}
inter-region-segmented {
fan-out <leaf-AD routes>);
threshold <kilobits>);
}
ldp-p2mp;
rsvp-te {
label... | [edit routing-instances routing-instance-name provider-tunnel] | These statements add Junos support for segmented RSVP-TE provider tunnels with next-generation
Layer 3 multicast VPNs (MVPN), that is, Inter-AS Option B. Inter-AS (autonomous-systems) support is
required when an L3VPN spans multiple ASes, which can be under the same or different administrative
authority (such as in an ... | [
{
"name": "ingress-replication",
"desc": "Select the ingress replication tunnel for further configuration. Choose create-new-ucast-tunnel to create a new unicast tunnel for ingress replication. Choose label-switched-path to create a point-to-point LSP unicast tunnel, and then choose label-switched-path-te... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1R1. | [
"BGP-MVPN Inter-AS Option B Overview"
] |
inter-domain | inter-domain; | [edit logical-systems logical-system-name protocols mpls label-switched-path label-switched-path-
name],
[edit protocols mpls label-switched-path label-switched-path-name] | Allows the router to search for routes in the IGP database. You need to configure this statement on
routers that might be unable to locate a path using intra-domain CSPF (by looking in the traffic
engineering database (TED). When you configure inter-area or inter-AS LSPs, the inter-domain statement
is required. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring an LSP Across ASs"
] |
inter-region | inter-region [
template template-name;
no-inter-region-segmentation;
} | [edit routing-instances instance-name provider-tunnel] | Specify template to be used in inter-region segmentation. The tunnels types used will be based on the
template mentioned. If a virtual routing and forwarding (VRF) in the area boundary router (ABR) does
not want to participate in the inter-region segmentation then no-inter-region-segmentation can be specified. | [
{
"name": "no-inter-region-segmentation",
"desc": "Specify to avoid the template mapping an ABR that is not involved in the inter-region segmentation."
},
{
"name": "template template-name",
"desc": "Specify the template to be used in the inter-region segmentation."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Segmented Inter-Area Point-to-Multipoint Label-Switched Paths Overview",
"Example: Configuring Segmented Inter-Area P2MP LSP",
"Configuring Segmented Inter-Area P2MP LSP"
] |
inter-region-segmented | inter-region-segmented {
fan-out fan-out value;
threshold rate-value;
} | [edit routing-instances instance-name provider-tunnel selective group multicast IP address
source source IP-address],
[edit routing-instances instance-name provider-tunnel selective group multicast IP address
wildcard-source],
[edit routing-instances instance-name provider-tunnel selective wildcard-group-inet wildcar... | Configure segmentation of inter-region on an ingress PE router or transit area boundary routers (ABRs)
by specifying only a fan-out factor or threshold rate or both. The inter-region segmentation allows the
PE router to signal segmented S-PMSI A-D routes. If the segmentation is based on the threshold, then
the MVPN sta... | [
{
"name": "fan-out fan-out-value",
"desc": "Specify the number of remote leaf A-D route values for fan-out. Once the number of leaf A-D routes per S-PMSI meets the configured fan-out value, the inter-region segmentation is triggered and the traffic flow is directed to segmented S-PMSI. Range: 1 through 100... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Segmented Inter-Area Point-to-Multipoint Label-Switched Paths Overview",
"Example: Configuring Segmented Inter-Area P2MP LSP",
"Configuring Segmented Inter-Area P2MP LSP"
] |
inter-region-template | inter-region-template {
template template-name {
all-regions {
incoming;
ingress-replication {
create-new-ucast-tunnel;
label-switched-path {
label-switched-path-template (Multicast) {
(default-template | lsp... | [edit protocols mvpn] | Define MVPN inter-region tunnel mapping template. A template is configured on a transit area boundary
router (ABR) to define the tunnel type to be used for a given region. There are four types of tunnels that
can be used:
•
Incoming — Indicates that the tunnel type used across the ABR remains unchanged.
•
Ingress-repli... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Segmented Inter-Area Point-to-Multipoint Label-Switched Paths Overview",
"Example: Configuring Segmented Inter-Area P2MP LSP",
"Configuring Segmented Inter-Area P2MP LSP"
] |
inter-switch-link | inter-switch-link vlan members primary-vlan-name; | [edit interfaces interface-name unit logical-unit-number family ethernet-switching interface-mode
trunk] | Use this configuration statement when a private VLAN (PVLAN) spans multiple switches. The Inter-
Switch Link protocol (ISL) must be configured on a trunk port of the primary VLAN in order to connect
the switches composing the PVLAN to each other. You do not need to configure an ISL when a PVLAN
is configured on a singl... | [] | 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. | [
"Creating a Private VLAN Spanning Multiple EX Series Switches with ELS Support (CLI Procedure)"
] |
interconnect | interconnect {
domain-path-id
domain-id-string
encapsulation (protocols evpn) {
mpls;
vxlan;
}
esi identifier {
all-active;
df-election-type {
mod;
preference {
value value (0..65535);
}
}
}
inte... | [edit protocols evpn],
[edit routing-instances routing-instance-name protocols evpn] | Use this statement to enable seamless interconnection of:
•
EVPN-VXLAN points of delivery (PODs) in a data center.
•
Different EVPN-VXLAN data centers. This use case is also known as data center interconnect (DCI).
You can use this statement on devices that support seamless EVPN-VXLAN stitching to interconnect
PODs or ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Option interconnected-vni-list introduced in Junos OS Release 20.3R1.
Options interconnected-vlan-list and encapsulation mpls introduced in Junos OS Release 21.4R1. | [] |
interconnect-device (Aliases) | interconnect-device interconnect-device-name {
assigned-interconnect-device-name;
} | [edit fabric aliases] | (QFabric systems only) Specify the mapping of user-defined names to QFabric system Interconnect
devices.
NOTE: The following rules apply to QFabric component alias naming:
•
Alias names must use alphabetic (A through Z and a through z), numeric (0 through 9),
or dash (-) characters.
•
The maximum length of an alias nam... | [
{
"name": "interconnect-device-name",
"desc": "Specify a user-defined name for a QFabric system Interconnect device."
},
{
"name": "assigned-interconnect-device-name",
"desc": "Specify the Interconnect device identifier or name that has been"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring Aliases for the QFabric System",
"Understanding Interconnect Devices"
] |
interconnect-device (Chassis) | interconnect-device {
alarm {
(ethernet (Alarm) | management-ethernet) {
link-down (red | yellow | ignore);
}
}
container-devices {
device-count number;
}
craft-lockout {
alarm {
interface-type {
link-down (red | yellow | ignore... | [edit chassis] | Configure properties specific to a QFabric system Interconnect 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 11.3. | [
"Understanding Interconnect Devices"
] |
interconnect-device (Flow Groups) | interconnect-device interconnect-device-name; | [edit fabric flow-groups flow-group-name] | In a QFabric system, a hash function is used to select an interconnect device to forward traffic between
two Node devices. Since this hash function is performed on all available Interconnect devices, it is
possible for redundant multicast streams to flow through one Interconnect device, making that
Interconnect device ... | [
{
"name": "interconnect-device-name",
"desc": "assigns Interconnect devices to the named flow group"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D15. | [
"Example: Creating a QFabric Flow Group"
] |
interconnect-multihoming-peer-gateways | interconnect-multihoming-peer-gateways (multihoming-peer-gateway-IP-address | [multihoming-peer-
gateway-IP-address ... ]); | [edit logical-systems name protocols evpn],
[edit protocols evpn] | Specify Ethernet VPN (EVPN) provider edge (PE) multihoming peer Data Center Interconnect (DCI)
gateway devices.
When you configure this option, the DCI gateway devices avoid loops during EVPN configuration
changes and can handle control plane routing more simply, which helps optimize forwarding between
the peer DCI gat... | [
{
"name": "(multihoming-peer-gateway-IP-address | [multihoming-peer-gateway-IP-address …])",
"desc": "One or more multihoming"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 22.2R1. | [] |
interconnected-vlan-list | interconnected-vlan-list (vlan-list ); | [edit protocols evpn interconnect]
[edit routing-instances routing-instance-name protocols evpn interconnect] | Configures seamless stitching between EVPN-VXLAN data centers through an EVPN-MPLS fabric. This
interconnect method transfers unicast and BUM traffic using WAN gateways with gateway-redundancy
multihoming support. This feature is VLAN-based, and includes VLAN-aware bundle and VLAN bundle
support using the VLAN list you... | [
{
"name": "vlan-list",
"desc": "Specifies the VLAN identifiers for interconnection. For example:"
},
{
"name": "interconnected-vlan-list [51 52];",
"desc": ""
},
{
"name": "encapsulation mpls;",
"desc": ""
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statements introduced in Junos OS Release 21.4R1. | [] |
interconnected-vni-list | interconnected-vni-list (vni-list | all); | [edit protocols evpn interconnect]
[edit routing-instances routing-instance-name protocols evpn interconnect] | Establishes that a Juniper Networks switch translates all VXLAN network identifiers (VNIs) or just a
specified list of VNIs. This translation occurs when different VNIs are configured for the same VLAN in
EVPN-VXLAN points of delivery (PODs) or data centers, and in the EVPN-VXLAN WAN network that
interconnects them.
Fo... | [
{
"name": "vni-list",
"desc": "Translate only the specified VNIs with values that range from 1 through 16777214. For example, interconnected-vni-list [10-50 60 70]."
},
{
"name": "all",
"desc": "Translate all VNIs."
}
] | 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. | [] |
interface (802.1X) | interface (all | [ interface-names ]) {
authentication-order (captive-portal | dot1x | mac-radius);
disable;
eapol-block {
captive-portal;
mac-radius;
server-fail <block-interval>;
}
guest-bridge-domain guest-bridge-domain;
guest-gbp-tag guest-gbp-tag
guest-v... | [edit logical-systems name protocols dot1x authenticator],
[edit protocols dot1x authenticator] | Configure IEEE 802.1X authentication for Port-Based Network Access Control for all interfaces or for
specific interfaces. | [
{
"name": "(all | [ interface-names ])",
"desc": "Configure either a list of interface names or all interfaces for 802.1x authentication."
},
{
"name": "disable",
"desc": "Disable 802.1X authentication on a specified interface or all interfaces. Default: 802.1X authentication is disabled on all... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
gbp-tag gbp-tag and guest-gbp-tag guest-gbp-tag introduced in Junos OS Release 23.4R1 for EX and QFX
Series switches.
server-reject-vlan introduced in Junos OS Release 9.3 for EX Series switches.
eapol-block introduced in Junos OS Release 11.2.
authentication-order and redi... | [
"Understanding Authentication on Switches",
"Example: Setting Up 802.1X for Single-Supplicant or Multiple-Supplicant Configurations on an EX",
"Series Switch",
"Example: Setting Up 802.1X in Conference Rooms to Provide Internet Access to Corporate Visitors",
"on an EX Series Switch",
"Example: Setting Up ... |
interface (Access Port Security) | interface (all | interface-name) {
allowed-mac {
mac-address-list;
}
(dhcp-trusted | no-dhcp-trusted);
fcoe-trusted;
mac-limit limit action (drop | log | none | shutdown);
no-allowed-mac-log;
persistent-learning;
static-ip ip-address {
vlan vlan-name;
mac mac-a... | [edit ethernet-switching-options secure-access-port] | Apply port security features to all interfaces or to the specified interface. | [
{
"name": "all",
"desc": "Apply port security features to all interfaces."
},
{
"name": "interface-name",
"desc": "Apply port security features to the specified interface."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Support for the ipv6-source-guard statement introduced in Junos OS Release 14.1X53-D10 for EX Series
switches. | [
"Example: Configuring Port Security (non-ELS)",
"Example: Protecting Against DHCP Snooping Database Attacks",
"Example: Protecting against Ethernet Switching Table Overflow Attacks",
"Example: Protecting against DHCP Starvation Attacks",
"Example: Protecting against Rogue DHCP Server Attacks",
"Configurin... |
interface (Accounting or Sampling) | interface interface-name {
engine-id number;
engine-type number;
source-address address;
} | [edit forwarding-options accounting name output],
[edit forwarding-options sampling family (inet | inet6 | mpls) output],
[edit forwarding-options sampling instance instance-name family (inet | inet6 | mpls) output] | Specify the output interface for monitored traffic or for sending copies of packets elsewhere to be
analyzed. | [
{
"name": "interface-name",
"desc": "Name of the interface."
}
] | 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 Discard Accounting",
"Configuring Traffic Sampling on MX, M and T Series Routers",
"Understanding IP-Based Filtering and Selective Port Mirroring of MPLS Traffic",
"Configuring Discard Accounting",
"Collecting Traffic Sampling Output in a File"
] |
interface (advance-policy-based-routing) | underlay-interfaces interface-name {
unit unit-number {
link-type (IP | MPLS)
priority priority-number;
} | [edit security advance-policy-based-routing] | Configure link preference settings for an interface in a APBR profile.
When a list of best paths that meet the SLA requirements are available for the application path, the path
selection mechanism selects a path that matches the configured link preference (link type, bandwidth,
and priority). The application traffic d... | [
{
"name": "link-tag",
"desc": "Configure custom tag for the link selection. You can use the tags such as IP, MPLS, VOIP, DSL and so on as per the requirement. Defining a link-tag along with link-priority allows you to prioritize the link selection. Default: IP"
},
{
"name": "multipath-bandwidth",
... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1 | [
"Firewall User Authentication Overview"
] |
interface (Analyzer) | interface (all | interface-name); | [edit forwarding-options analyzer analyzer-name input egress],
[edit forwarding-options analyzer analyzer-name input ingress],
[edit forwarding-options analyzer analyzer-name output] | Configure the interfaces for which traffic is mirrored. | [
{
"name": "all",
"desc": "Apply mirroring to all interfaces on the network device. Mirroring a high volume of traffic can be performance intensive for the device. Therefore, you should generally select specific input interfaces in preference to using the all keyword, or use the all keyword in combination wi... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10. | [
"Example: Configuring Port Mirroring Analyzers for Local Monitoring of Employee Resource Use",
"Example: Configuring Port Mirroring for Remote Monitoring of Employee Resource Use",
"Understanding Port Mirroring Analyzers"
] |
interface (Backup Selection OSPF) | interface (interface-name | all) {
admin-group {
exclude [ group-name ];
include-all [ group-name ];
include-any [ group-name ];
preference [ group-name ];
}
bandwidth-greater-equal-primary;
dest-metric (highest | lowest);
downstream-paths-only ;
eva... | [edit logical-systems logical-system-name routing-options backup-selection destination prefix],
[edit logical-systems logical-system-name routing-instances instance-name routing-options backup-
selection destination prefix],
[edit routing-instances instance-name routing-options backup-selection prefix],
[edit routing-... | Define the backup selection policy for a specific primary next hop. | [
{
"name": "interface-name",
"desc": "Name of the primary next-hop interface."
},
{
"name": "all",
"desc": "All the interfaces."
},
{
"name": "bandwidth-greater-equal-",
"desc": ""
},
{
"name": "primary",
"desc": "Allow the selection of the backup next hop only if the band... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Example: Configuring Backup Selection Policy for the OSPF or OSPF3 Protocol",
"Configuring Backup Selection Policy for the OSPF Protocol",
"Understanding Backup Selection Policy for OSPF Protocol"
] |
interface (BOOTP) | interface (interface-name | interface-group) {
apply-secondary-as-giaddr;
broadcast;
client-response-ttl number;
description text-description;
maximum-hop-count number;
minimum-wait-time seconds;
no-listen;
server address {
logical-system logical-system-name <routing-instance [ ... | [edit forwarding-options helpers bootp] | Specify the interface for a DHCP and BOOTP relay agent. | [
{
"name": "interface-group",
"desc": "Set a logical interface or group of logical interfaces with a specific DHCP relay configuration."
},
{
"name": "apply-secondary-as-giaddr",
"desc": "Enable DHCP relay to use secondary gateway IP on this interface."
},
{
"name": "broadcast",
"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. | [
"Configuring Routers, Switches, and Interfaces as DHCP and BOOTP Relay Agents"
] |
interface (BPDU Blocking) | interface (all | [interface-name]); | [edit protocols layer2-control bpdu-block]
[edit ethernet-switching-options bpdu-block] | Applies Bridge Protocol Data Unit (BPDU) protection on all interfaces or on one or more specified
interfaces.
Spanning Tree Protocol (STP), Rapid Spanning Tree protocol (RSTP), and Multiple Spanning Tree Protocol
(MSTP) provide Layer 2 loop prevention for EX Series switches. The spanning-tree protocols use BPDU
frames ... | [
{
"name": "all",
"desc": "All interfaces."
},
{
"name": "[interface-name]",
"desc": "One or more Ethernet interface names."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Understanding BPDU Protection for STP, RSTP, and MSTP",
"Understanding BPDU Protection for Spanning-Tree Instance Interfaces",
"Configuring BPDU Protection for Individual Spanning-Tree Instance Interfaces",
"Example: Configuring Network Regions for VLANs with MSTP on Switches",
"Example: Faster Convergence... |
interface (Bridge Domains) | interface interface-name {
group-limit limit;
host-only-interface;
static {
group ip-address {
source 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-... | Enable IGMP snooping on an interface and configure interface-specific properties. | [
{
"name": "interface-name",
"desc": "Name of the interface. Specify the full interface name, including the physical and logical"
}
] | 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"
] |
interface (Captive Portal) | interface (all | [interface-names]) {
quiet-period seconds;
retries number-of-retries;
server-timeout seconds;
session-expiry seconds;
supplicant ( multiple | single | single-secure);
user-keepalive minutes;
} | [edit services captive-portal] | Configure captive portal authentication for all interfaces or for specific interfaces. | [
{
"name": "all",
"desc": "All interfaces to be configured for captive portal authentication."
},
{
"name": "[interface-names]",
"desc": "List of names of interfaces to be configured for captive portal authentication."
},
{
"name": "quiet-period",
"desc": ""
},
{
"name": "seco... | 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.
user-keepalive introduced in Junos OS Release 16.1 for EX Series switches. | [
"Example: Setting Up Captive Portal Authentication on an EX Series Switch",
"Configuring Captive Portal Authentication (CLI Procedure)",
"Access Control and Authentication on Switching Devices"
] |
interface (Chassis Cluster) | logical-interface-name secondary-ip-address; | [edit chassis cluster redundancy-groupgroup-number ip-monitoring family family-name IP–
address] | Specify the redundant Ethernet interface, including its logical-unit-number, through which the
monitored IP address must be reachable. The specified redundant Ethernet interface can be in any
redundancy group. Likewise specify a secondary IP address to be used as a ping source for monitoring
the IP address through the ... | [
{
"name": "logical-interface-name",
"desc": "Redundant Ethernet interface through which the monitored IP address must be"
},
{
"name": "secondary-ip-address IP–address",
"desc": "Specify the IP address that are used as the source IP address of ping"
}
] | 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. | [] |
interface (DCBX) | interface (interface-name | all) {
disable;
application-map application-map-name;
applications {
no-auto-negotiation;
}
enhanced-transmission-selection {
no-auto-negotiation;
no-recommendation-tlv;
recommendation-tlv {
no-auto-negotiation;
}
}
... | [edit protocols dcbx] | Configure DCBX properties on an interface. | [
{
"name": "interface-name",
"desc": "Name of the interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
Mode and recommendation-tlv statements introduced in Junos OS Release 12.2 for the QFX Series. | [
"Configuring DCBX Autonegotiation",
"Example: Configuring DCBX to Support an iSCSI Application",
"Understanding DCB Features and Requirements",
"Understanding DCB Features and Requirements on EX Series Switches",
"Understanding DCBX Application Protocol TLV Exchange on EX Series Switches"
] |
interface (DHCP Local Server) | interface interface-name {
access-profile profile-name;
exclude;
overrides {
asymmetric-lease-time seconds;
asymmetric-prefix-lease-time seconds;
client-discover-match <option60-and-option82 | incoming-interface>;
client-negotiation-match incoming-interface;
delay-ad... | [edit system services dhcp-local-server group group-name],
[edit system services dhcp-local-server dhcpv6 group group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server ...],
[edit logical-systems logical-system-name system services dhcp-local-ser... | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "exclude",
"desc": "Exclude an interface or a range of interfaces from the group. This option and the overrides option"
},
{
"name": "interface-name",
"desc": "Name of the interface. You can repeat this option multiple times."
},
{
"name": "upto-interface-name",
"desc": "Up... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Options upto and exclude introduced in Junos OS Release 9.1. | [
"Understanding Differences Between Legacy DHCP and Extended DHCP",
"Grouping Interfaces with Common DHCP Configurations",
"Specifying Authentication Support"
] |
interface (DHCP Relay Agent) | interface dhcp-interface-name {
access-profile profile-name;
exclude;
overrides {
allow-no-end-option
allow-snooped-clients;
always-write-giaddr;
always-write-option-82;
asymmetric-lease-time seconds;
asymmetric-prefix-lease-time seconds;
client-disc... | [edit forwarding-options dhcp-relay dhcpv6 group group-name],
[edit forwarding-options dhcp-relay group group-name],
[edit logical-systems logical-system-name forwarding-options dhcp-relay ...],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options dhcp-relay ...],
[edit ... | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "exclude",
"desc": "Exclude an interface or a range of interfaces from the group. This option and the overrides option"
},
{
"name": "interface-name",
"desc": "Name of the interface. You can repeat this option multiple times."
},
{
"name": "overrides",
"desc": "Override the... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3.
Options upto and exclude introduced in Junos OS Release 9.1.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4. | [
"Extended DHCP Relay Agent Overview",
"Grouping Interfaces with Common DHCP Configurations",
"Specifying Authentication Support"
] |
interface (DHCP Security for MX Series) | interface interface-name {
static-ip ip-address {
mac mac-address;
}
} | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security group group-name] | Configure an interface for a static IPaddress to MAC address binding (IP-MAC binding) or configure an
interface to belong to a group within the bridge domain that has DHCP security attributes that are
different from the attributes of other interfaces in the bridge domain.
The remaining statements are explained separat... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Configuring Static DHCP IP Addresses for DHCP snooping (MX routers)"
] |
interface (DHCP Spoofing Prevention) | interface interface-name; | [edit routing-instances routing-instance-name bridge-domains bridge-domain-name forwarding-options
dhcp-relay group group-name],
[edit routing-instances routing-instance-name forwarding-options dhcp-relay group group-name] | Configure Dynamic Host Configuration Protocol (DHCP) snooping on the router. When acting as a
snooping agent, the MX Series router typically is located between the client and the DHCP relay agent.
It creates filters by “snooping” DHCP messages and binding DHCP-issued IP addresses with the MAC
address of the client. The... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4 (MX Series routers only). | [
"Preventing DHCP Spoofing on MX Series 5G Universal Routing Platforms"
] |
interface (DNS, Port, and TFTP Packet Forwarding or Relay Agent) | interface interface-name {
broadcast;
description text-description;
no-listen;
server address <logical-system logical-system-name> <routing-instance routing-instance-name>;
} | [edit forwarding-options helpers domain],
[edit forwarding-options helpers port port-number],
[edit forwarding-options helpers tftp] | Specify the interface for monitoring and forwarding DNS or TFTP requests, or for forwarding LAN
broadcast traffic on a custom UDP port to a particular server as unicast traffic.
When configuring port helpers, in releases prior to Junos OS Release 17.2, only one server can be
specified for a given port. For Junos OS Rel... | [
{
"name": "interface-name",
"desc": "Name of the interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced for port helpers in Junos OS Release 17.2R1 for EX4300 switches.
Support for multiple server instances for a given port introduced in Junos OS Release 17.2 for MX Series
routers.
Support for multiple server instances for a given port introduced in J... | [
"Configuring DNS and TFTP Packet Forwarding",
"Configuring Port-based LAN Broadcast Packet Forwarding"
] |
interface (Dynamic IGMP) | interface interface-name {
accounting;
disable;
distributed;
group-limit limit;
group-policy;
group-threshold value;
immediate-leave
log-interval seconds;
no-accounting;
oif-map;
passive;
promiscuous-mode;
ssm-map ssm-map-name;
ssm-map-policy ssm-map-policy-name
... | [edit dynamic-profiles profile-name protocols igmp] | Enable IGMP on an interface and configure interface-specific properties. | [
{
"name": "interface-name",
"desc": "Variable for the interface. Specify the interface variable ($junos-interface-name) to"
}
] | 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. | [
"Dynamic IGMP Configuration Overview",
"Configuring Dynamic DHCP Client Access to a Multicast Network",
"Enabling IGMP"
] |
interface (Dynamic Interface Sets) | interface interface-name {
unit logical unit number {
advisory-options {
downstream-rate rate;
upstream-rate rate;
}
}
} | [edit dynamic-profiles profile-name interfaces interface-set interface-set-name] | Add a subscriber interface to a dynamic interface set.
In a dynamic profile that defines an agent circuit identifier (ACI) interface set, observe the following
guidelines when you use the interface statement:
•
Use the predefined dynamic interface variable $junos-interface-ifd-name to represent the interface
name. Do n... | [] | 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. | [
"Defining ACI Interface Sets",
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring an Interface Set of Subscribers in a Dynamic Profile",
"Agent Circuit Identifier-Based Dynamic VLANs Overview"
] |
interface (Dynamic MLD) | interfaceinterface-name {
(accounting | no-accounting);
disable;
distributed;
group-limit limit;
group-policy;
group-threshold value;
immediate-leave;
log-interval seconds;
oif-map;
passive;
ssm-map ssm-map-name;
ssm-map-policy ssm-map-policy-name;
static {
g... | [edit dynamic-profiles profile-name protocols mld] | Enable MLD on a dynamic interface and configure interface-specific properties. | [
{
"name": "interface-name",
"desc": "Variable for the interface. Specify the interface variable ($junos-interface-name) to"
}
] | 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. | [
"Dynamic MLD Configuration Overview",
"Enabling MLD"
] |
interface (Dynamic Router Advertisement) | interface interface-name {
current-hop-limitnumber;
default-lifetime seconds;
dns-server-address
(managed-configuration | no-managed-configuration);
max-advertisement-interval seconds;
min-advertisement-interval seconds;
(other-stateful-configuration | no-other-stateful-configuration);
... | [edit dynamic-profiles protocols router-advertisement] | Dynamically configure router advertisement properties on an interface. To dynamically configure
interface properties, include the $junos-interface-name dynamic variable for the interface name. | [
{
"name": "interface-name",
"desc": "Name of an interface. Specify the $junos-interface-name dynamic variable or the full, static"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"IPv6 WAN Link Addressing with NDRA",
"Dynamic Router Advertisement Configuration Overview"
] |
interface (Dynamic Routing Instances) | interface interface-name; | [edit dynamic-profiles profile-namerouting-instances routing-instance-name] | Assign the specified interface to the dynamically created routing instance. | [
{
"name": "interface-name",
"desc": "The interface name variable ($junos-interface-name). The interface name variable is"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [] |
interface (Dynamic Routing Options) | interface interface-names {
no-qos-adjust;
} | [edit dynamic-profiles profile-name routing-options multicast],
[edit dynamic-profiles profile-name routing-instances routing-instance-name routing-options
multicast] | Define the maximum bandwidth for a dynamic interface on which you want to apply bandwidth
management. | [
{
"name": "interface-name",
"desc": "Names of the physical or logical interface. For details about specifying interfaces, see"
}
] | 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. | [
"Configuring Dynamic Access Routes for Subscriber Management",
"Configuring Dynamic Access-Internal Routes for DHCP and PPP Subscribers"
] |
interface (EVPN Routing Instances) | interface interface-name {
ignore-encapsulation-mismatch;
interface-mac-limit limit {
packet-action drop;
}
mac-pinning
no-mac-learning;
protect-interface
static-mac mac-address;
vpws-service-id
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols]
[edit routing-instances routing-instance-name protocols evpn] | Specify each interface over which the Ethernet VPN (EVPN) traffic travels between the PE device and
customer edge (CE) device. The interfaces are bound to the EVPN routing instance. | [
{
"name": "interface-name",
"desc": "Name of the interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2.
Statement (mac-pinning) introduced in Junos OS Release 16.2 on MX Series routers.
vpws-service-id statement introduced in Junos OS Release 17.1 on MX Series routers.
Support for logical systems on MX Series routers added in Junos OS Release 17.4R1. | [
"Configuring EVPN Routing Instances",
"Configuring EVPN Routing Instances on EX9200 Switches"
] |
interface (Export Profiles) | interface {
information;
statistics {
queue;
traffic;
}
status {
link;
queue;
traffic;
}
} | [edit services analytics export-profiles] | Configure an export profile for streaming network analytics data for a specific interface to remote
servers. Each profile is a template that defines the type of data being streamed for that interface.
NOTE: The interface statement is not available in Junos OS Releases prior to 13.2X51-
D15. | [
{
"name": "information",
"desc": "Information about the specified interface, including SNMP index, interface index, slot, port number, media type, capability, and port type."
},
{
"name": "statistics",
"desc": "Type of monitoring statistics to be streamed. Values:"
},
{
"name": "queue",... | 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"
] |
interface (Fibre Channel Fabric) | interface {
interface-name {
max-login-sessions max-login-sessions;
}
interface-name {
max-login-sessions max-login-sessions;
}
<...> {
max-login-sessions max-login-sessions;
}
vlan.interface-name;
} | [edit fc-fabrics fc-fabric-name] | Associate one or more native Fibre Channel (FC) interfaces with an FC fabric and one VLAN interface
for FCoE traffic. An FC interface can be associated with only one FC fabric. | [
{
"name": "interface-name",
"desc": "Name of the native FC interface. You can assign one or more FC interfaces to an FC"
},
{
"name": "vlan.vlan-interface-name",
"desc": "Name of the VLAN interface for FCoE traffic. You can assign one VLAN"
}
] | 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. | [
"Example: Setting Up Fibre Channel and FCoE VLAN Interfaces in an FCoE-FC Gateway Fabric",
"Converting an Ethernet Interface To a Fibre Channel Interface",
"Configuring a Physical Fibre Channel Interface",
"Configuring an FCoE VLAN Interface on an FCoE-FC Gateway",
"Understanding Interfaces on an FCoE-FC Ga... |
interface (FIP Snooping) | interface interface-name {
(fcoe-trusted| no-fcoe-trusted);
} | [edit vlans vlan-name forwarding-options fip-security] | NOTE: This statement supports the Enhanced Layer 2 Software (ELS) CLI. If your switch
runs the original (non-ELS) software, see interface (Secure Access Port) for how to
specify an interface to configure as FCoE trusted or FCoE untrusted. For ELS details, see
Using the Enhanced Layer 2 Software CLI.
Specify an interfac... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced for the ELS CLI in Junos OS Release 13.2 for the QFX Series. | [
"Configuring VN2VF_Port FIP Snooping and FCoE Trusted Interfaces on an FCoE Transit Switch",
"Understanding FCoE Transit Switch Functionality"
] |
interface (FIP) | interface {
interface-name {
fka-adv-period milliseconds;
priority priority;
}
} | [edit fc-fabrics fc-fabric-name protocols fip] | Configure FIP options on a per-interface basis. (Override global FIP configuration for a specified
interface.) | [
{
"name": "interface-name",
"desc": "Name of the interface."
}
] | 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"
] |
interface (Hierarchical CoS Schedulers) | interface interface-name; | [edit interfaces interface-set interface-set-name] | Specify an interface that is a member of the interface set. Supported on Ethernet interfaces on an MX
Series router, Ethernet interfaces on IQ2E PIC on M Series and T Series routers, and IP demux interfaces
on an MX Series router. | [] | 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. | [
"Junos OS Class of Service User Guide for Routing Devices"
] |
interface (Host Fast Reroute) | interface interface-name {
arp-prefix-limit number;
link-protection;
supplementary-blackout-timer minutes;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit routing-instances routing-instance-name routing-options] | Configure host fast reroute settings, including link protection for the interface and an ARP prefix limit.
The remaining statements are described separately. | [] | 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 Link Protection with Host Fast Reroute"
] |
interface (IEEE 802.1ag OAM Connectivity-Fault Management) | interface (interface-name | ((ge- | xe-) (fpc/pic/port | fpc/pic/port.unit-number | fpc/pic/
port.unit-number vlan vlan-id))); | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name mep mep-id] | For Ethernet interfaces on M320, MX Series, and T Series routers, configure IEEE 802.1ag Operation,
Administration, and Management (OAM) support.
For Gigabit Ethernet interfaces and 10-Gigabit Ethernet interfaces on MX Series routers, configure IEEE
802.1ag Connectivity Fault Management (CFM) support on trunk interface... | [
{
"name": "interface-name",
"desc": "Interface to which the MEP is attached. It could be a physical Ethernet interface, logical"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [
"Configuring a MEP to Generate and Respond to CFM Protocol Messages"
] |
interface (IGMP Snooping) | interface interface-name {
group-limit limit;
host-only-interface;
immediate-leave;
multicast-router-interface;
static {
group multicast-group-address {
source ip-address;
}
}
} | [edit protocols igmp-snooping vlan (all | vlan-name)] | For IGMP snooping, configure an interface as either a multicast-router interface or as a static member of
a multicast group with optional interface-specific properties. | [
{
"name": "all",
"desc": "All interfaces in the VLAN."
},
{
"name": "interface-name",
"desc": "Name of the interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Example: Configuring IGMP Snooping on SRX Series Devices",
"IGMP Snooping Overview"
] |
interface (Layer 2 Protocol Tunneling) | interface interface-name {
enable-all-ifl;
protocol protocol-name;
} | [edit logical-systems name protocols layer2-control mac-rewrite],
[edit protocols layer2-control mac-rewrite] | Configure an interface for Layer 2 protocol tunneling.
NOTE: The enable-all-ifl option is available on EX9200 switches but not on other EX
Series switches.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
enable-all-if statement added in Junos OS Release 13.3.
Support for PVSTP protocol introduced in Junos OS Release 13.3.
Statement introduced in Junos OS Release 14.1X53-D10 and 17.3R1 for EX4300 switches. | [
"Understanding Layer 2 Protocol Tunneling"
] |
interface (LLDP) | interface (all | [interface-name-list]) {
(disable | enable);
power-negotiation <(disable | enable)>;
(tlv-filter | tlv-select);
trap-notification (disable | enable);
} | [edit protocols lldp],
[edit routing-instances routing-instance-name protocols lldp] | Configure Link Layer Discovery Protocol (LLDP) on all interfaces or on a particular interface.
NOTE: On MX Series and T Series routers, you run LLDP on a physical interface, such as
ge-1/0/0, and not at the logical interface (unit) level.
Starting with Junos OS Release 14.2, on MX Series devices, you can also configure... | [
{
"name": "(all | [interface-name-list])",
"desc": "Configure LLDP on all interfaces or on one or more interfaces."
},
{
"name": "(disable | enable)",
"desc": "Disable or enable LLDP on all interfaces or on the specified interfaces. Default: Disable"
},
{
"name": "power-negotiation",
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
power-negotiation introduced in Junos OS Release 12.2 for EX and QFX Series switches.
trap-notification introduced in Junos OS Release 15.1R7-S3 for EX3300, EX4200, EX4500, EX4550,
EX6200, EX8200 switches. | [
"Configuring LLDP (CLI Procedure)",
"Configuring LLDP",
"Configuring PoE Interfaces on EX Series Switches"
] |
interface (LLDP-MED) | interface name {
(disable | enable);
location {
civic-based {
ca-type type {
ca-value value;
}
country-code country-code;
what what;
}
co-ordinate {
lattitude latitude;
longitude longitude;
}... | [edit protocols lldp-med] | Configure Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED) on all interfaces or on
a specific interface.
Default
Not enabled. | [
{
"name": "all | interface-name",
"desc": "Configure LLDP-MED on all interfaces or on a specific interface."
},
{
"name": "disable | enable",
"desc": "Disable or enable LLDP-MED on all interfaces or on one or more interfaces. Default: If you do not configure LLDP-MED, it is disabled on the devi... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Example: Setting Up VoIP with 802.1X and LLDP-MED on an EX Series Switch",
"Configuring LLDP-MED (CLI Procedure)",
"Understanding LLDP and LLDP-MED on EX Series Switches"
] |
interface (Logical Interfaces) | interface interface-name; | [edit bridge-domains bridge-domain-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name bridge-domains
bridge-domain-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name],
[edit vlans vlan-name] | (MX Series routers and EX Series switches only) Specify the logical interfaces to include in the bridge
domain, VLAN, VPLS instance, or virtual switch. | [
{
"name": "interface-name",
"desc": "Name of a logical interface. For more information about how to configure logical"
}
] | 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 top-level configuration for the virtual-switch type of routing instance added in Junos OS
Release 9.2.
In Junos OS Release 9.1 and earlier, the routing instances hierarchy supported this statement only for a
VPLS instance or a bridge domain configured within a v... | [
"Configuring a Bridge Domain",
"Configuring a Layer 2 Virtual Switch",
"Configuring a Layer 2 Virtual Switch on an EX Series Switch",
"Tunnel Services Overview",
"Tunnel Interface Configuration on MX Series Routers Overview"
] |
interface (MLD Snooping) | interface (all | interface-name) {
group-limit limit;
host-only-interface;
immediate-leave;
multicast-router-interface;
static {
group ip-address {
source ip-address;
}
}
} | [edit protocols mld-snooping vlan (all | vlan-name)],
[edit routing-instances instance-name protocols mld-snooping vlan vlan-name] | For MLD snooping, configure an interface as a static multicast-router interface, a host-side interface, or
a static member of a multicast group. | [
{
"name": "all",
"desc": "(All EX Series switches except EX9200) All interfaces in the VLAN."
},
{
"name": "interface-name",
"desc": "Name of the interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1.
Support at the [edit routing-instances instance-name protocols mld-snooping vlan vlan-name] hierarchy
introduced in Junos OS Release 13.3 for EX Series switches.
Support for the group-limit, host-only-interface, and the immediate-leave statements introduced in Junos OS
Rel... | [
"Example: Configuring MLD Snooping on SRX Series Devices",
"Configuring MLD Snooping on an EX Series Switch VLAN (CLI Procedure)",
"Understanding MLD Snooping"
] |
interface (Monitoring) | interface interface-name {
engine-id number;
engine-type number;
input-interface-index number;
output-interface-index number;
source-address address;
} | [edit forwarding-options monitoring group-name inet output] | Specify the output interface for monitored traffic. | [
{
"name": "interface-name",
"desc": "Name of the interface."
},
{
"name": "engine-id number",
"desc": "Identity of the monitoring interface."
},
{
"name": "engine-type number",
"desc": "Type of the monitoring interface."
},
{
"name": "input-interface-index number",
"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. | [
"Configuring Passive Flow Monitoring"
] |
interface (MPLS) | interface (all | interface-name); | [edit protocols mpls] | Enable MPLS on all interfaces on the switch or on the specified interface.
Default
MPLS is disabled. | [
{
"name": "all",
"desc": "All interfaces on the switch."
},
{
"name": "interface-name",
"desc": "Name of an interface:"
},
{
"name": "Aggregated Ethernet",
"desc": "aex"
},
{
"name": "Gigabit Ethernet",
"desc": "ge-fpc/pic/port"
}
] | 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. | [
"Example: Configuring MPLS on EX8200 and EX4500 Switches",
"Configuring CoS on an MPLS Provider Edge Switch Using IP Over MPLS",
"Configuring CoS on an MPLS Provider Edge Switch Using Circuit Cross-Connect",
"Configuring MPLS on EX8200 and EX4500 Provider Switches"
] |
interface (Multicast Scoping) | interface [ interface-names ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast scope scope-name],
[edit logical-systems logical-system-name routing-options multicast scope scope-name],
[edit routing-instances routing-instance-name routing-options multicast scope scope-name],
[edit routing-... | Configure the set of interfaces for multicast scoping. | [
{
"name": "interface-names",
"desc": "Names of the interfaces on which to configure scoping. Specify the full interface"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Examples: Configuring Administrative Scoping"
] |
interface (Multicast Static Routes) | interface interface-names {
disable;
maximum-bandwidth bps;
no-qos-adjust;
reverse-oif-mapping {
no-qos-adjust;
}
subscriber-leave-timer seconds;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options multicast] | Enable multicast traffic on an interface.
By default, multicast packets are forwarded by enabling Protocol Independent Multicast (PIM) on an
interface. PIM adds multicast routes into the routing table.
You can also configure multicast packets to be forwarded over a static route, such as a static route
associated with a... | [
{
"name": "interface-names",
"desc": "Name of one or more interfaces on which to enable multicast traffic."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Example: Defining Interface Bandwidth Maximums",
"Example: Configuring Multicast with Subscriber VLANs"
] |
interface (Multichassis Protection) | interface interface-name; | [edit multi-chassis multi-chassis-protection peer] | Specify the name of the interface that is being used as an interchassis link-protection link (ICL-PL). The
two switches hosting a multichassis link aggregation group (MC-LAG) use this link to pass Inter-Chassis
Control Protocol (ICCP) and data traffic. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [] |
interface (MVRP) | interface (all | interface-name) {
join-timer milliseconds;
leave-timer milliseconds;
leaveall-timer milliseconds;
point-to-point;
registration (forbidden | normal | restricted);
} | [edit protocols mvrp],
[edit routing-instances routing-instance-name protocols mvrp],
[edit logical-systems logical-system-name protocols mvrp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols mvrp] | Specify interfaces on which to configure Multiple VLAN Registration Protocol (MVRP).
NOTE: On QFX Series switches, you must configure specific interfaces—you cannot
specify interface all. You can enable MVRP on an interface range.
Default
By default, MVRP is disabled. | [
{
"name": "all",
"desc": "All interfaces on the switch."
},
{
"name": "interface-name",
"desc": "Names of interface to be configured for MVRP."
}
] | 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. | [
"Example: Configuring Automatic VLAN Administration Using MVRP on EX Series Switches",
"Configuring Multiple VLAN Registration Protocol (MVRP) on Switches",
"Understanding Multiple VLAN Registration Protocol (MVRP) for Dynamic VLAN Registration",
"Understanding Multiple VLAN Registration Protocol (MVRP) for D... |
interface (Next-Hop Group) | interface interface-name {
next-hop address;
} | [edit forwarding-options next-hop-group group-name] | Specify the output interface for sending copies of packets elsewhere to be analyzed.
The commit operation fails when a next-hop group has only one interface configured. It is implicitly
assumed that a subgroup is up only if more than one interface in the subgroup is up. | [
{
"name": "interface-name",
"desc": "Name of the interface."
}
] | 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 Next-Hop Groups to Use Multiple Interfaces to Forward Packets Used in Port Mirroring"
] |
interface (OAM CFM, for EX Series Switch Only) | interface (interface-name | ((ge- | xe-) (fpc/pic/port | fpc/pic/port.unit-number | fpc/pic/
port.unit-number vlan vlan-id))); | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name mep mep-id] | Configure IEEE 802.1ag Operation, Administration, and Management (OAM) Connectivity Fault
Management (CFM) support for the specified interface. | [
{
"name": "interface-name",
"desc": "Interface to which the MEP is attached. It can be a physical Ethernet interface or a"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Ethernet OAM Connectivity Fault Management (CLI Procedure)",
"Junos OS Network Interfaces Configuration Guide"
] |
interface (OAM Link-Fault Management) | interface interface-name {
apply-action-profile profile-name;
link-discovery (active | passive);
pdu-interval interval;
pdu-threshold threshold-value;
remote-loopback;
event-thresholds {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-per... | [edit protocols oam ethernet link-fault-management] | For Ethernet interfaces on M320, MX Series, and T Series routers, configure IEEE 802.3ah Operation,
Administration, and Management (OAM) support. | [
{
"name": "interface interface-name",
"desc": "Interface to be enabled for IEEE 802.3ah link fault management OAM support."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Enabling IEEE 802.3ah OAM Support"
] |
interface (PIC Bundle) | interface interface-name; | [edit interfaces pic-set pic-set-name] | Sets the PIC bundle and the interface. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Junos OS Release 9.6. | [
"Understanding Interfaces"
] |
interface (PoE) | interface (all | interface-name) {
disable;
maximum-power watts;
priority (high | low);
telemetries {
disable;
duration hours;
interval minutes;
}
} | [edit poe] | Enable a PoE interface for a PoE port. The PoE interface must be enabled in order for the port to provide
power to a connected powered device.
Default
The PoE interface is enabled by default | [
{
"name": "all",
"desc": "Apply the configuration to all interfaces on the SRX Series Firewall that have not been explicitly"
},
{
"name": "interface-name",
"desc": "Explicitly configure a specific 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. | [
"Understanding Power over Ethernet"
] |
interface (Port Mirroring) | interface (all | interface-name); | For platforms without ELS:
[edit ethernet-switching-options analyzer name input (egress | ingress)],
[edit ethernet-switching-options analyzer name output]
For platforms with ELS:
[edit forwarding-options analyzer name input (egress | ingress)]
[edit forwarding-options analyzer name output]
[edit forwarding-options po... | Specify the interfaces for which ingressing traffic is mirrored. Specify the interface that mirrored traffic
should be copied to (the output interface). | [
{
"name": "all",
"desc": "Apply port mirroring to all interfaces on the switch (except the output interface). Mirroring a high"
},
{
"name": "interface-name",
"desc": "Apply port mirroring to the specified interface only."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Understanding Port Mirroring and Analyzers",
"Configuring Port Mirroring",
"Examples: Configuring Port Mirroring for Local Analysis"
] |
interface (Port Mirroring) | interface interface-name {
next-hop address;
} | [edit forwarding-options port-mirroring output],
[edit forwarding-options port-mirroring family (inet | inet6) output] | Specify the output interface for sending copies of packets elsewhere to be analyzed. | [
{
"name": "interface-name",
"desc": "Name of the interface."
}
] | 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 Port Mirroring"
] |
interface (Power over Ethernet) | interface (all | all-extended | interface-name) {
af-mode;
disable;
maximum-power watts;
priority (high | low);
telemetries {
disable;
duration hours;
interval minutes;
}
} | [edit poe] | Specify a PoE interface to be configured. | [
{
"name": "all",
"desc": "All PoE interfaces on the switch that have not been individually configured for PoE. If a PoE"
},
{
"name": "all-extended",
"desc": "(Junos Fusion only) All PoE extended port interfaces in a Junos Fusion that have not been"
},
{
"name": "interface-name",
"de... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge. | [
"Configuring PoE Interfaces on EX Series Switches",
"Configuring Power over Ethernet in a Junos Fusion"
] |
interface (Precision Time Protocol) | interface interface-name {
unicast-mode {
clock-source ip-address {
local-ip-address local-ip-address;
}
}
transport ipv4;
}
} | [edit protocols ptp slave] | The interface on which to respond to the upstream PTP timeTransmitter. | [
{
"name": "unicast-mode",
"desc": "Configure upstream unicast PTP timeTransmitter clock sources"
},
{
"name": "clock-source",
"desc": "Configure the parameters of the PTP."
},
{
"name": "local-ip-address",
"desc": "Configure the IP address of the local interface acting as the timeRec... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | [
"IEEE 1588v2 Precision Timing Protocol (PTP)",
"Precision Time Protocol Overview",
"Configuring the Precision Time Protocol G.8275.2 Enhanced Profile (Telecom Profile)"
] | |
interface (Protocols DVMRP) | interface interface-name {
disable;
hold-time seconds;
metric metric;
mode (forwarding | unicast-routing);
} | [edit logical-systems logical-system-name protocols dvmrp],
[edit protocols dvmrp] | Enable DVMRP on an interface and configure interface-specific properties. | [
{
"name": "interface-name",
"desc": "Name of the interface. Specify the full interface name, including the physical and logical"
}
] | 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"
] |
interface (Protocols IGMP) | interface interface-name {
(accounting | no-accounting);
disable;
distributed;
group-limit limit;
group-policy [ policy-names ];
immediate-leave;
oif-map map-name;
passive;
promiscuous-mode;
ssm-map ssm-map-name;
ssm-map-policy ssm-map-policy-name;
static {
group ... | [edit logical-systems logical-system-name protocols igmp],
[edit protocols igmp] | Enable IGMP on an interface and configure interface-specific properties. | [
{
"name": "interface-name",
"desc": "Name of the interface. Specify the full interface name, including the physical and logical"
}
] | 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. | [
"Enabling IGMP"
] |
interface (Protocols IPv6 Neighbor Discovery) | interface interface-name {
current-hop-limit number;
default-lifetime seconds;
(link-mtu | no-link-mtu);
(managed-configuration | no-managed-configuration);
max-advertisement-interval seconds;
min-advertisement-interval seconds;
(other-stateful-configuration | no-other-stateful-configuration... | [edit logical-systems logical-system-name protocols router-advertisement],
[edit protocols router-advertisement] | Configure router advertisement properties on an interface. To configure more than one interface,
include the interface statement multiple times.
The Junos OS enters the Neighbor Discovery Protocol (NDP) packets into the routing platform cache
even if there is no known route to the source.
If you are using Virtual Route... | [
{
"name": "interface-name",
"desc": "Name of an interface. Specify the full interface name, including the physical and logical"
},
{
"name": "nat-prefix",
"desc": "NAT64 IPv6 address prefix. Specify upto 3 NAT64 IPv6 address prefix per interface for"
},
{
"name": "lifetime",
"desc": ... | 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.
"solicit-router-advertisement-unicast" on page 29202 statement added from 15.1 Release onwards.
The nat-prefix and lifetime options added from Junos OS 22.4R1 Release onwards. | [
"Example: Configuring IPv6 Interfaces and Enabling Neighbor Discovery",
"Secure IPv6 Neighbor Discovery"
] |
interface (Protocols IS-IS) | interface (all | interface-name) {
disable;
bfd-liveness-detection {
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
minimum-interval millisecond... | [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] | Configure interface-specific IS-IS properties. To configure more than one interface, include the interface
statement multiple times.
Enabling IS-IS on an interface (by including the interface statement at the [edit protocols isis] or the [edit
routing-instances routing-instance-name protocols isis] hierarchy level), di... | [
{
"name": "all | interface-name",
"desc": "Select either automatic interfaces or specify the name of an existing interface."
},
{
"name": "all",
"desc": "Have Junos OS create IS-IS interfaces automatically. If you include this"
},
{
"name": "interface-name",
"desc": "Name of an inter... | 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.
no-eligible-remote-backup option introduced in Junos OS Release 14.2 for the MX Series.
interface-group-holddown-delay option introduced in Junos OS Release 15.2 for the MX Series.
max-hello-size option introduced in Junos OS Release 17.1 for the MX Series. | [
"Understanding IS-IS Configuration",
"Example: Configuring IS-IS",
"Understanding IS-IS Areas to Divide an Autonomous System into Smaller Groups",
"Example: Configuring a Multi-Level IS-IS Topology to Control Interarea Flooding"
] |
interface (Protocols Layer 2 Circuit) | interface interface-name {
backup-neighbor address;
bandwidth (bandwidth | ctnumber bandwidth);
community community-name;
connection-protection;
(control-word | no-control-word);
description text;
egress-protection;
encapsulation-type type;
flow-label-receive;
flow-label-receive-... | [edit logical-systems logical-system-name protocols l2circuit local-switching],
[edit logical-systems logical-system-name protocols l2circuit neighbor address],
[edit protocols l2circuit local-switching],
[edit protocols l2circuit neighbor address] | Interface over which Layer 2 circuit traffic travels. | [
{
"name": "interface-name",
"desc": "Name of the interface to configure. NOTE: The commit operation fails, if the same logical interface is configured for both layer 2 circuit and ccc connection."
},
{
"name": "connection-protection",
"desc": "Enable end-to-end protection through OAM failure det... | 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.
flow-label-receive-static and flow-label-transmit-static options introduced in Junos OS Release 14.1. | [
"Configuring the Neighbor Interface for the Layer 2 Circuit"
] |
interface (Protocols Layer 2 VPN) | interface interface-name {
description text;
remote-site-id remote-site-id;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
l2vpn],
[edit routing-instances routing-instance-name protocols l2vpn] | Configure an interface to handle traffic for a circuit configured for the Layer 2 VPN. | [
{
"name": "interface-name",
"desc": "Name of the interface used for the Layer 2 VPN."
}
] | 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 Site",
"Configuring the Remote Site ID"
] |
interface (Protocols LDP) | interface interface-name {
disable;
hello-interval seconds;
hold-time seconds;
transport-address (interface | loopback);
} | [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] | Enable LDP on one or more router interfaces.
Default
LDP is disabled on all interfaces. | [
{
"name": "interface-name",
"desc": "Name of an interface. To configure all interfaces, specify all."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Enabling and Disabling LDP"
] |
interface (Protocols Link Management) | interface interface-name; | [edit logical-systems logical-system-name protocols link-management te-link te-link-name],
[edit protocols link-management te-link te-link-name] | Specify the egress router interface. | [
{
"name": "interface-name",
"desc": "Name of the interface to the egress router."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"LMP Configuration Overview"
] |
interface (Protocols MLD) | interface interface-name {
(accounting | no-accounting);
disable;
distributed;
group-limit limit;
group-policy [ policy-names ];
group-threshold value;
immediate-leave;
log-interval seconds;
oif-map [ map-names ];
passive;
ssm-map ssm-map-name;
ssm-map-policy ssm-map-pol... | [edit logical-systems logical-system-name protocols mld],
[edit protocols mld] | Enable MLD on an interface and configure interface-specific properties. | [
{
"name": "interface-name",
"desc": "Name of the interface. Specify the full interface name, including the physical and logical"
}
] | 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. | [
"Enabling MLD"
] |
interface (Protocols MPLS) | interface (interface-name | all) {
disable;
admin-group [ group-names ];
srlg srlg-name;
} | [edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls] | Enable MPLS on one or more interfaces. | [
{
"name": "interface-name",
"desc": "Name of the interface on which to configure MPLS. To configure all interfaces, specify all."
},
{
"name": "srlg srlg-name",
"desc": "Name of the SRLG to associate with an interface."
}
] | 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 Intermediate (Transit) and Egress Routers for Static LSPs",
"Example: Configuring SRLG"
] |
interface (Protocols OSPF) | interface interface-name {
disable;
authentication key <key-id identifier>;
bfd-liveness-detection {
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}... | [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast) area area-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(ospf | ospf3) a... | Enable OSPF routing on a routing device interface.
You must include at least one interface statement in the configuration to enable OSPF on the routing
device. | [
{
"name": "interface-name",
"desc": "Specify the interface by IP address or interface name for OSPFv2, or only the interface name for OSPFv3. Using both the interface name and IP address of the same interface produces an invalid configuration. To configure all interfaces, you can specify all. Specifying a p... | 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 topology statement introduced in Junos OS Release 9.0.
Support for the topology statement introduced in Junos OS Release 9.0 for EX Series switches.
Support for the realm statement introduced in Junos OS Release 9.2.
Support for the realm statement intr... | [
"Understanding OSPF Configurations",
"Example: Configuring Multiple Address Families for OSPFv3"
] |
interface (Protocols PIM) | interface (Protocols PIM) (all | interface-name) {
accept-join-always-from [ policy-name ... ];
accept-remote-source;
disable;
multiple-triggered-joins {
count number;
interval milliseconds;
}
bfd-liveness-detection {
authentication {
algorithmalgorithm-name;
... | [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]
[edit protocols pim interface interface-name multiple-triggered-joins | Enable PIM on an interface and configure interface-specific properties. | [
{
"name": "interface-name",
"desc": "Name of the interface. Specify the full interface name, including the physical and logical"
}
] | 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. | [
"PIM on Aggregated Interfaces"
] |
interface (Protocols RIFT) | interface interface-name {
allowed-authentication-keys (value | [set of values]);
bfd-liveness-detection {
minimum-interval milliseconds;
multiplier milliseconds;
}
(check-common-instance-name | no-check-instance-name);
(check-common-subnet | no-check-common-subnet);
disable;
... | [edit protocols rift] | Configure the interfaces for the RIFT protocol. | [
{
"name": "interface-name",
"desc": "Name of the interface on which the RIFT protocol should be configured."
},
{
"name": "allowed-authentication-keys",
"desc": ""
},
{
"name": "(value | [set of",
"desc": ""
},
{
"name": "values])",
"desc": "(Optional) Specify a single or... | 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"
] |
interface (Protocols Router Discovery) | interface interface-name {
lifetime seconds;
max-advertisement-interval seconds;
min-advertisement-interval seconds;
} | [edit logical-systems logical-system-name protocols router-discovery],
[edit protocols router-discovery] | Specify physical interfaces on which to configure timers for router advertisement messages. | [
{
"name": "interface-name",
"desc": "Name of an interface. Specify the full interface name, including the physical and logical"
}
] | routing—To view this statement in the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Understanding the ICMP Protocol for Discovering Gateways to Other Networks",
"Example: Configuring the ICMP Protocol for Discovering Gateways to Other Networks"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.