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 |
|---|---|---|---|---|---|---|---|
interface (Protocols RSVP) | interface interface-name {
disable;
(aggregate | no-aggregate);
authentication-key key;
bandwidth bps;
hello-interval seconds;
link-protection {
disable;
admin-group {
exclude [ group-names ];
include-all [ group-names ];
include-any [ group-... | [edit logical-systems logical-system-name protocols rsvp],
[edit protocols rsvp] | Enable RSVP on one or more router interfaces.
Default
RSVP is disabled on all interfaces. | [
{
"name": "interface-name",
"desc": "Name of an interface. To configure all interfaces, specify all. For details about specifying"
}
] | 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. | [
"Minimum RSVP Configuration"
] |
interface (RA Guard) | interface interface-name {
mark-interface (trusted | block);
policy policy-name (stateful | stateless);
} | [edit forwarding-options access-security router-advertisement-guard] | Configure IPv6 Router Advertisement (RA) guard on an interface. In an IPv6 deployment, RA guard
protects against rogue RA messages generated either maliciously or unintentionally by unauthorized or
improperly configured routers connecting to the network segment. An RA guard policy is used to
validate incoming RA messag... | [
{
"name": "interface-name",
"desc": "Configure RA guard parameters on the specified interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D55. | [
"Understanding IPv6 Router Advertisement Guard",
"Configuring Stateful IPv6 Router Advertisement Guard"
] |
interface (Redundant Trunk Groups) | interface interface-name <primary>;
interface interface-name; | For platforms with ELS:
[edit switch-options redundant-trunk-group group name]
For platforms without ELS:
[edit ethernet-switching-options redundant-trunk-group group name] | Configure a primary link and secondary link on trunk ports. If the primary link fails, the secondary link
automatically takes over as the primary link without waiting for normal STP convergence. | [
{
"name": "interface interface-name",
"desc": "A logical interface or an aggregated interface containing multiple ports."
},
{
"name": "primary",
"desc": "(Optional) Specify one of the interfaces in the redundant group as the primary link. The"
}
] | system—To view this statement in the configuration.
system–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Hierarchy level [edit switch-options] introduced in Junos OS Release 13.2X50-D10 (ELS). (See Using the
Enhanced Layer 2 Software CLI for information about ELS.) | [
"Example: Configuring Redundant Trunk Links for Faster Recovery on EX Series Switches",
"Example: Configuring Redundant Trunk Links for Faster Recovery on Devices with ELS Support",
"Understanding Redundant Trunk Links (Legacy RTG Configuration)"
] |
interface (Routing Instances) | interface interface-name {
description text;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | Specify the interface over which the VPN traffic travels between the PE device and CE device. You
configure the interface on the PE device. If the value vrf is specified for the instance-type statement
included in the routing instance configuration, this statement is required. | [
{
"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 before Junos OS Release 7.4. | [
"Configuring EVPN Routing Instances",
"Configuring EVPN Routing Instances on EX9200 Switches"
] |
interface (Routing Options) | interface interface-names {
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.
TIP: You cannot enable multicast traffic on an interface by using the routing-options
multicast interface statement and configure PIM on the interface. | [
{
"name": "interface-name",
"desc": "Names of the physical or logical interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Example: Defining Interface Bandwidth Maximums",
"Example: Configuring Multicast with Subscriber VLANs"
] |
interface (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 to scope. Specify the full interface name, including the"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring Multicast Snooping"
] |
interface (Secure Access Port) | interface (all | interface-name) {
allowed-mac mac-address-list;
(dhcp-trusted | no-dhcp-trusted);
mac-limit limit action action;
no-allowed-mac-log;
static-ip ip-address {
vlan vlan-name;
mac mac-address;
}
} | [edit ethernet-switching-options secure-access-port] | Apply port security features to all interfaces or to the specified interface.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "all",
"desc": "Apply port security features to all interfaces. Does not apply to QFabric systems."
},
{
"name": "interface-name",
"desc": "Apply port security features to the specified 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. | [
"Understanding How to Protect Access Ports from Common Attacks",
"Understanding MAC Limiting and MAC Move Limiting for Port Security",
"Understanding and Using Trusted DHCP Servers",
"Configuring MAC Limiting (QFX Switches)"
] |
interface (Security NAT ARP Proxy) | interface interface-name {
address ip-address {
to ip-address;
}
} | [edit security nat proxy-arp] | Specify the interface on which the ARP proxy is to be configured. It should be a logical interface. | [
{
"name": "interface-name",
"desc": "Name of the logical interface."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. | [] |
interface (Security NAT NDP Proxy) | interface interface-name {
address ip-address {
to ip-address;
}
} | [edit security nat proxy-ndp] | Specify the interface on which the NDP proxy is to be configured. It should be a logical interface. | [
{
"name": "interface-name",
"desc": "Name of the logical interface."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. | [] |
interface (Security Source NAT Rule Set) | interface {
persistent-nat {
address-mapping;
inactivity-timeout seconds;
max-session-number value;
permit (any-remote-host | target-host | target-host-port);
}
} | [edit security nat source rule-set rule-set-name rule rule-name then source-nat] | Enable interface NAT with or without port overloading. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [] |
interface (Security Source NAT) | interface (port-overloading off | port-overloading-factor number); | [edit security nat source] | Enable interface NAT with or without port overloading. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. Statement modified in Junos OS Release 12.1X45-D10. | [] |
interface (Service Interfaces) | interface service-interface-name; | [edit services service-device-pools pool pool-name] | Assign a service interface to a service interface pool. You specify more than one interface for each pool.
The interfaces are used to balance traffic loads. For an L2TP tunnel group, the interfaces must be inline
service interfaces (si). For a hybrid access tunnel group, the interfaces must be pseudowire service
interf... | [
{
"name": "service-interface-name",
"desc": "Name of the service interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
Support for ps service interfaces added in Junos OS Release 19.3R1. | [
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces"
] |
interface (Service Redundancy Group Monitor) | interface {
interface-name name {
weight weight;
}
threshold threshold;
} | [edit chassis high-availability services-redundancy-group name monitor],
[edit chassis high-availability services-redundancy-group name monitor monitor-object name ] | Configure interface monitoring for a service redundancy group. | [
{
"name": "interface",
"desc": ""
},
{
"name": "interface-name",
"desc": "Name of the physical interface to monitor."
},
{
"name": "weight",
"desc": ""
},
{
"name": "threshold",
"desc": ""
},
{
"name": "(monitor-object)",
"desc": ""
},
{
"name": "monit... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [] |
interface (Services Flow Tap) | interface sp-fpc/pic/port.logical-unit-number; | [edit services flow-tap] | Specify the AS PIC interface used with the flow-tap application. Any AS PIC available in the router can
be assigned, and any logical interface on the AS PIC can be used. | [
{
"name": "sp-fpc/pic/port.logical-unit-number",
"desc": "Use the specified services interface for flow-tap service. You cannot configure flow-tap services on channelized interfaces."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Configuring the Flow-Tap Interface"
] |
interface (Services PIC) | [interface interface-name]; | [edit unified-edge gateways tdf gateway-name system service-pics] | Specify one or more of the MS-MPC service interfaces that represent the service PICs used for
anchoring subscriber-aware services in the MX Series router. The following conditions are applicable to
the services PIC interfaces configured here:
•
If an aggregated multiservices interface (ams) is specified in this stateme... | [
{
"name": "interface-name",
"desc": "Name of the interface representing the services PIC. Syntax: The interface must be a valid multiservices interface (amsn or ms-a/b/0, where n is the ams number, a is the Flexible PIC Concentrator [FPC] slot number, and b is the PIC slot number); for example, ams0 or ms-... | 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 17.1. | [
"Configuring Service PICs",
"TDF Gateway Service PICs and Session PICs for Subscriber-Aware Traffic Treatment"
] |
interface (services) | interface interface-name.unit-number; | [edit services service-interface-pools pool pool-name] | Add logical service interfaces to the pool of service interfaces. | [
{
"name": "interface-name.unit-number",
"desc": "Name and logical unit number of the service 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.3. | [] |
interface (Services) | interface interface-name; | [edit services unified-access-control infranet-controller hostname] | Specify the SRX Series interface through which the IC Series device should connect.
This statement is required when you are configuring the SRX Series Firewall to act as a Junos OS
Enforcer in a Unified Access Control (UAC) deployment. When deployed as a Junos OS Enforcer, the
SRX Series Firewall enforces the policies ... | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [] |
interface (Session PICs) | [interface interface-name]; | [edit unified-edge gateways tdf gateway-name system session-pics] | Specify one or more of the MS-MPC service interfaces that represent the session PICs used for the
control plane in the TDF gateway. The following conditions are applicable to the session PIC interfaces
configured here:
•
If an aggregated multiservices interface (ams) is specified in this statement, the ams must already... | [
{
"name": "interface-name",
"desc": "Name of the interface representing the services PIC. Syntax: The interface must be a valid multiservices interface (amsn or ms-a/b/0, where n is the ams number, a is the Flexible PIC Concentrator [FPC] slot number, and b is the PIC slot number); for example, ams0 or ms-... | 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 17.1. | [
"Configuring Session PICs",
"TDF Gateway Service PICs and Session PICs for Subscriber-Aware Traffic Treatment"
] |
interface (SLAAC Snooping) | interface (interface-name | all) {
auto-dad {
retries retry-count;
retrans-interval seconds;
}
mark-interface trusted;
maximum-allowed-contentions {
count integer;
duration seconds;
}
} | [edit forwarding-options access-security slaac-snooping] | Configure interface-level parameters for IPv6 stateless address auto-configuration (SLAAC) snooping.
SLAAC enables an IPv6 client to generate its own local and global addresses using a combination of
locally-available information and information advertised by routers through Neighbor Discovery
Protocol (NDP). NDP messa... | [
{
"name": "(interface-name",
"desc": ""
},
{
"name": "| all)",
"desc": "Configure SLAAC snooping parameters on the specified interface or on all interfaces."
},
{
"name": "mark-interface",
"desc": ""
},
{
"name": "trusted",
"desc": "Configure the interface as trusted. The... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1. | [
"IPv6 Stateless Address Auto-configuration (SLAAC) Snooping"
] |
interface (SNMP RMON History) | interface interface-name; | [edit snmp rmon history history-index] | Specify the interface to be monitored in the specified RMON history entry.
Only one interface can be specified for a particular RMON history index. There is a one-to-one
relationship between the interface and the history index. The interface must be specified in order for the
RMON history to be created. | [
{
"name": "interface-name",
"desc": "Specify the interface to be monitored within the specified entry of the RMON history"
}
] | snmp—To view this statement in the configuration.
snmp–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Understanding RMON",
"RMON MIB Event, Alarm, Log, and History Control Tables",
"Configuring RMON History Sampling",
"Monitoring RMON MIB Tables",
"Junos OS Network Management Configuration Guide"
] |
interface (SNMP) | interface [ interface-names ]; | [edit snmp] | Configure the interfaces on which SNMP requests can be accepted.
Default
If you omit this statement, SNMP requests entering the router or switch through any interface are
accepted. | [
{
"name": "interface-names",
"desc": "Names of one or more logical interfaces."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Interfaces on Which SNMP Requests Can Be Accepted"
] |
interface (Spanning Tree) | interface interface-name {
arp-on-stp;
bpdu-timeout-action
block;
log;
cost cost;
disable;
edge;
mode mode;
no-root-port;
priority priority;
} | [edit logical-systems logical-system-name protocols (mstp | rstp | vstp)],
[edit logical-systems logical-system-name protocols vstp vlan vlan-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(mstp | rstp | vstp)],
[edit logical-systems logical-system-name routing-instanc... | Configures the interface to participate in the RSTP, MSTP, or VSTP instance.
The edge, mode, and no-root-port options are not available at the [edit protocols mstp msti msti-id]
hierarchy level. | [
{
"name": "interface-name",
"desc": "Name of a Gigabit Ethernet or 10-Gigabit Ethernet interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Statement updated in Junos OS Release 9.4 for EX Series switches to add VSTP support.
Support for logical systems added in Junos OS Release 9.6.
Statement updated in Junos OS Release 15.1 for EX Series switches to support configuration of
spanning tree parameters globally o... | [
"Understanding Spanning-Tree Instance Interfaces",
"Understanding RSTP",
"Understanding MSTP",
"Understanding VSTP",
"Configuring RSTP on EX Series Switches (CLI Procedure)",
"Configuring MSTP on Switches",
"Example: Configuring Network Regions for VLANs with MSTP on Switches",
"Example: Faster Conver... |
interface (Static MAC Bypass) | interface [interface-names]; | [edit protocols authentication-access-control] | Configure interfaces on which the specified MAC addresses are allowed to bypass RADIUS
authentication and allowed to connect to the LAN without authentication. | [
{
"name": "interface-names",
"desc": "List of interfaces."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
interface (Static Subscriber Group) | interface interface-name <exclude> <upto upto-interface-name>; | [edit logical-systems logical-system-name system services static-subscribers group group-name],
[edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers group group-name],
[edit routing-instances routing-instances-name system services static-subscribers grou... | Specify one or more interfaces, or a range of interfaces, that are within a specified group on which static
subscribers are created. You can repeat the interface interface-name statement to specify multiple
interfaces within a group. You must configure each interface in only one group.
NOTE: The logical system and rou... | [
{
"name": "exclude",
"desc": "(Optional) Exclude an interface or a range of interfaces from the group."
},
{
"name": "interface-name",
"desc": "Name of the interface on which static subscribers are created. If you do not specify a unit"
},
{
"name": "upto-interface-name",
"desc": "(O... | 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.
Support for IPv6 and IPv4 demux static interfaces introduced in Junos OS Release 11.2.
Support for pseudowire interfaces over logical tunnels introduced in Junos OS Release 18.3R1. | [
"Subscribers over Static Interfaces Configuration Overview",
"Creating a Static Subscriber Group"
] |
interface (Static Subscriber Username) | interface; | [edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers authentication username-include],
[edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers group group-name authentication username-inclu... | Specify that a modified version of the interface name is included as part of the username created for all
static subscribers or for the static subscribers in a specified group. The group version of the statement
takes precedence over the global version. The username is also sent to RADIUS in the Access-Request
message.... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Subscribers over Static Interfaces Configuration Overview",
"Configuring the Static Subscriber Global Username",
"Configuring the Static Subscriber Group Username"
] |
interface (Storm Control) | interface (all | interface-name) {
bandwidth bandwidth;
level level;
multicast;
no-broadcast;
no-multicast;
no-registered-multicast;
no-unknown-unicast;
no-unregistered-multicast;
} | [edit ethernet-switching-options storm-control] | Configure storm control on all interfaces or on the specified interface.
Default
•
On EX2200, EX3200, EX3300, EX4200, and EX6200 switches—Storm control does not apply by
default to multicast traffic. The factory default configuration enables storm control for broadcast and
unknown unicast traffic on all switch interfac... | [
{
"name": "all",
"desc": "All interfaces. The storm control settings configured with the all option affect only those interfaces"
},
{
"name": "interface-name",
"desc": "Name of an interface. The storm control settings configured with the interface-name"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Configuring Autorecovery for Port Security Events",
"Enabling and Disabling Storm Control (non-ELS)"
] |
interface (Switching Options) | interface interface-name {
encapsulation-type;
ignore-encapsulation-mismatch;
pseudowire-status-tlv;
static-mac mac-address {
vlan-id vlan-id;
}
} | [edit vlans vlans-name switch-options] | Specify the logical interfaces to include in the VLAN. | [
{
"name": "interface-name",
"desc": "Name of a logical interface."
},
{
"name": "encapsulation-type",
"desc": "Encapsulation type for VPN."
},
{
"name": "ignore-encapsulation-mismatch",
"desc": "Allow different encapsulation types on local and remote devices."
},
{
"name": "p... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.5. | [] |
interface (System Services DHCP) | interface interface-name {
exclude;
overrides {
interface-client-limit number;
}
trace;
upto upto-interface-name;
} | [edit system services dhcp-local-server dhcpv6 group group-name] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and rest... | [
{
"name": "interface-name",
"desc": "Name of the interface."
},
{
"name": "trace",
"desc": "Enable tracing of the interface specified by the interface-name argument."
},
{
"name": "upto upto-interface-name",
"desc": "The upper end of the range of interfaces; the lower end of the rang... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"DHCP Server Configuration",
"DHCP Server Options"
] |
interface (Unknown Unicast Forwarding) | interface interface-name; | For platforms with ELS:
[edit switch-options unknown-unicast-forwarding vlan vlan-name]
For platforms without ELS:
[edit ethernet-switching-options unknown-unicast-forwarding vlan vlan-name] | Specify the interface to which unknown unicast packets will be forwarded. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3.
Hierarchy level [edit switch-options] introduced in Junos OS Release 13.2X50-D10. (See Using the
Enhanced Layer 2 Software CLI for information about ELS.) | [
"show vlans",
"Understanding and Preventing Unknown Unicast Forwarding"
] |
interface (Virtual Tunnel in Routing Instances) | interface vt-fpc/pic/port.unit-number {
multicast;
primary;
unicast;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | In a multiprotocol BGP (MBGP) multicast VPN (MVPN), configure a virtual tunnel (VT) interface.
VT interfaces are needed for multicast traffic on routing devices that function as combined provider
edge (PE) and provider core (P) routers to optimize bandwidth usage on core links. VT interfaces prevent
traffic replication... | [
{
"name": "vt-fpc/pic/port.unit-number",
"desc": "Name of the VT 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.4. | [
"Example: Configuring Redundant Virtual Tunnel Interfaces in MBGP MVPNs",
"Example: Configuring MBGP MVPN Extranets"
] |
interface (VoIP) | interface (all | [interface-name] | access-ports) {
forwarding-class forwarding-class;
vlan (vlan-id | vlan-name | untagged));
} | For platforms with ELS:
[edit switch-options voip]
For platforms without ELS:
[edit ethernet-switching-options voip] | (Required) Enable voice over IP (VoIP) on interfaces. | [
{
"name": "all",
"desc": "Enable VoIP on all interfaces."
},
{
"name": "interface-name",
"desc": "Enable VoIP on a specific interface."
},
{
"name": "access-ports",
"desc": "(Switches without ELS only) Enable VoIP on all access ports."
},
{
"name": "forwarding-class",
"de... | 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.
Hierarchy level [edit switch-options] introduced in Junos OS Release 13.2X50-D10. (See Using the
Enhanced Layer 2 Software CLI for information about ELS.) | [
"Example: Setting Up VoIP with 802.1X and LLDP-MED on an EX Series Switch",
"Example: Configuring VoIP on an EX Series Switch Without Including 802.1X Authentication",
"Example: Configuring VoIP on an EX Series Switch Without Including LLDP-MED Support"
] |
interface (VPLS Mesh-Group) | interface interface-name; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
mesh-group mesh-group-name],
[edit routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name] | Specify one or more interfaces belonging to the virtual private LAN service (VPLS) flood mesh-group. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.2. | [
"Configuring VPLS Routing Instances"
] |
interface (VPLS Multihoming for FEC 129) | interface interface-name {
preference preference-value;
} | [edit logical-systems logical-system-name routing-instances instance-name protocols vpls multi-
homing site site-name],
[edit routing-instances instance-name protocols vpls multi-homing site site-name] | Configure the interface that connects this site to the VPN.
The remaining statement is explained separately. See CLI Explorer. | [
{
"name": "interface-name",
"desc": "Name of the interface (for example, ge-0/1/0.1)."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Example: Configuring VPLS Multihoming (FEC 129)"
] |
interface (VPLS Routing Instances) | interface interface-name {
mac-pinning;
interface-mac-limit limit;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
site site-name],
[edit routing-instances routing-instance-name protocols vpls],
[edit routing-instances routing-instance-n... | Configure the interface for a pseudowire to the VPLS customer site. To complete the configuration of
interfaces for a VPLS routing instance, you must also configure the interfaces specified for a VPLS site at
the [edit routing-instances routing-instance-name] hierarchy level as described in Configuring Routing
Instance... | [
{
"name": "interface-name",
"desc": "Specify the name of the interface used by the VPLS site."
}
] | 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 VPLS Site Interfaces",
"Configuring Routing Instances on PE Routers in VPNs"
] |
interface (VRRP) | interface interface-name {
bandwidth-threshold bits-per-second priority-cost priority;
priority-cost priority;
} | [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-
group group-id track],
[edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-
group group-id track],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit... | Enable logical interface tracking for a Virtual Router Redundancy Protocol (VRRP) group. | [
{
"name": "interface-name",
"desc": "Interface to be tracked for this VRRP group."
}
] | 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.
bandwidth-threshold statement added in Junos OS Release 8.1. | [
"Configuring a Logical Interface to Be Tracked for a VRRP Group",
"Junos OS Services Interfaces Library for Routing Devices"
] |
interface-client-limit (DHCP Local Server) | interface-client-limit number; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server overrides],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 overrides],
[edit logical-systems logical-system-name routing-insta... | Set the maximum number of DHCP subscribers or DHCP clients per interface allowed for a specific
group or for all groups. A group specification takes precedence over a global specification for the
members of that group.
NOTE: Do not use this statement for dual-stack subscribers. Instead, use the "dual-
stack-interface-c... | [
{
"name": "number",
"desc": "Maximum number of clients allowed."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Specifying the Maximum Number of DHCP Clients Per Interface",
"Overriding the Default DHCP Local Server Configuration Settings"
] |
interface-client-limit (DHCP Relay Agent) | interface-client-limit number; | [edit forwarding-options dhcp-relay dhcpv6 overrides],
[edit forwarding-options dhcp-relay overrides],
[edit forwarding-options dhcp-relay dhcpv6 group group-name overrides],
[edit forwarding-options dhcp-relay group group-name overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6 o... | Set the maximum number of DHCP (or DHCPv6) subscribers or clients per interface allowed for a
specific group or for all groups. A group specification takes precedence over a global specification for
the members of that group. Use the statement at the [edit ... dhcpv6] hierarchy levels to configure
DHCPv6 support.
M120 ... | [
{
"name": "number",
"desc": "Maximum number of clients allowed."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4. | [
"Extended DHCP Relay Agent Overview",
"Configuring Group-Specific DHCP Relay Options",
"Overriding the Default DHCP Relay Configuration Settings"
] |
interface-delete (Subscriber Management or DHCP Client Management) | interface-delete; | [edit system services subscriber-management maintain-subscriber] | On router—Configure the router to maintain, rather than log out, subscribers when the subscriber
interface is deleted. By default, the router logs out subscribers when the subscriber interface is deleted.
On switch—Configure the switch to maintain rather than log out DHCP clients when the client interface
is deleted. ... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring the Router to Maintain DHCP Subscribers During Interface Delete Events"
] |
interface-description (DHCP Local Server) | interface-description (device-interface | logical-interface); | [edit system services dhcp-local-server authentication username-include],
[edit system services dhcp-local-server dhcpv6 authentication username-include],
[edit system services dhcp-local-server dhcpv6 group group-name authentication username-include],
[edit system services dhcp-local-server group group-name authentica... | Specify that the interface description for the device (physical) interface or the logical interface is
concatenated with the username during the subscriber authentication or DHCP client authentication
process. Use the statement at the [edit ... dhcpv6] hierarchy levels to configure DHCPv6 support.
The interface descrip... | [
{
"name": "device-interface",
"desc": "Use the text description configured for the device (physical) interface."
},
{
"name": "logical-interface",
"desc": "Use the text description configured for the logical interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Creating Unique Usernames for DHCP Clients"
] |
interface-description (DHCP Relay Agent) | interface-description (device-interface | logical-interface); | [edit forwarding-options dhcp-relay authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 group group-name authentication username-include],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name auth... | Specify that the interface description for the device (physical) interface or the logical interface is
concatenated with the username during the subscriber authentication or DHCP client authentication
process. Use the statement at the [edit ... dhcpv6] hierarchy levels to configure DHCPv6 support.
The interface descrip... | [
{
"name": "device-interface",
"desc": "Description of the physical interface."
},
{
"name": "logical-interface",
"desc": "Description of the logical interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Creating Unique Usernames for DHCP Clients"
] |
interface-description-format | interface-description-format {
exclude-adapter;
exclude-channel;
exclude-sub-interface;
} | [edit access profile profile-name radius options] | Specify the information that is excluded from the interface description that the device passes to
RADIUS for inclusion in the RADIUS attributes such as NAS-Port-ID (87) or Calling-Station-ID (31).
The default format for nonchannelized interfaces is as follows:
interface-type-slot/adapter/port.subinterface[:svlan-vlan]
... | [
{
"name": "exclude-adapter",
"desc": ""
},
{
"name": "exclude-channel",
"desc": "(Optional) Exclude the channel information from the interface description."
},
{
"name": "exclude-sub-interface",
"desc": ""
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
exclude-adapter and exclude-sub-interface options added in Junos OS Release 10.4.
exclude-channel option added in Junos OS Release 17.3R1. | [
"RADIUS Servers and Parameters for Subscriber Access",
"Standard and Vendor-Specific RADIUS Attributes"
] |
interface-down | interface-down; | [edit protocols oam ethernet connectivity-fault-management action-profile profile-name default-actions] | Bring the interface down when a remote MEP connectivity failure is detected. | [] | 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. | [
"Configuring a CFM Action Profile to Specify CFM Actions for CFM Events"
] |
interface-group (Decapsulate GRE) | interface-group (0 -255) | [edit firewall family family-name filter filter-name term term-name then decapsulate gre] | Allows you to explicitly specify and add an interface group to packets after they have undergone GRE
decapsulation. In releases prior to Junos OS Release 14.1, the interface group upon decapsulation was
always 0 and could not be changed.
In Junos OS Release 14.1 and later, you can assign any arbitrary value in the ran... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1 . | [
"Example: Configuring a Stateless Firewall Filter on an Interface Group",
"Applying Forwarding Table Filters"
] |
interface-group (Routing Options) | interface-group group-id exclude; | [edit routing-options flow] | Exclude applying flowspec filter to traffic received on specific interfaces. Use exclude to specify the
interface group where you do not want to receive the traffic.
CAUTION:
Do not use this statement with BGP flowspec on the QFX10K or Junos based PTX
platforms as this might result in erratic behavior. Junos OS does no... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring MPLS-Signaled LSPs to Use GRE Tunnels",
"Understanding BGP Flow Routes for Traffic Filtering"
] |
interface-group | interface-group {
interface-device-name
unit-list
} | [edit protocols oam ethernet connectivity-fault-management maintenance-domain md-name maintenance-
association ma-name mep mep-id remote-mep mep-id ] | Mark the interface group down for the action profile configured with the action interface-group-down.
Provides information for the interface-group on which the configured action will be taken when the
configured event occur for a specific remote MEP ID. | [
{
"name": "interface-device",
"desc": ""
},
{
"name": "name",
"desc": "Name of the interface device. Only Ethernet devices are allowed. The device interface name includes ge, ae, xe and et. ."
},
{
"name": "unit-list",
"desc": "One or more logical interface unit numbers. Range: A st... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"Configuring a CFM Action Profile to Bring Down a Group of Logical Interfaces"
] |
interface-group-down | interface-group-down | [edit protocols oam ethernet connectivity-fault-management action-profile action-profile-name
action] | Mark the interface group down. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"Configuring a CFM Action Profile to Bring Down a Group of Logical Interfaces"
] |
interface-id | interface-id interface-id; | [edit access group-profile profile-name l2tp],
[edit access group-profile profile-name ppp],
[edit access profile profile-name client client-name ike],
[edit access profile profile-name client client-name l2tp],
[edit access profile profile-name client client-name ppp] | Configure the interface identifier. | [
{
"name": "interface-id",
"desc": "Identifier for the interface representing a Layer 2 Tunneling Protocol (L2TP) session"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Point-to-Point Protocol (PPP)",
"Layer 2 Tunneling Protocol (L2TP)",
"L2TP LNS Inline Service Interfaces",
"Configuring an IKE Access Profile"
] |
interface-in (Security Forwarding Options) | interface-in interface-name; | [edit security forwarding-options mirror-filter filter-name] | Specify the incoming logical interface to be matched for mirroring. | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [] |
interface-mac-ip-limit | interface-mac-ip-limit number; | [edit logical-systems logical-system-name routing-instances routing-instance-name vlans vlan-name
switch-options],
[edit logical-systems logical-system-name vlans vlan-name switch-options],
[edit routing-instances routing-instance-name protocols evpn],
[edit routing-instances routing-instance-name bridge-domains bridg... | Limit the number of entries that can be learned on an interface through the MAC-IP bindings database.
Depending on the Juniper Networks device, this limit can be applied to EVPN instances, bridge domains
configured in a virtual-switch routing instance, or VLANs configured in a virtual-switch routing instance.
To apply ... | [
{
"name": "number",
"desc": "Specify the maximum number of MAC-IP bindings per interface. After that maximum is reached, no additional MAC-IP entries are added to the database. Range: 1 through 1024. Default: 1024"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R2. | [
"EVPN Proxy ARP and ARP Suppression, and Proxy NDP and NDP Suppression"
] |
interface-mac-limit (VPLS) | interface-mac-limit limit {
packet-action drop;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
site site-name interfaces interface-name],
[edit routing-instances routing-instance-name protocols evpn],
[edit routing-instances routing-instance-name protocols evpn interface interface-name],
[edit routing-instances rout... | Specify the maximum number of media access control (MAC) addresses that can be learned by the
EVPN or VPLS routing instance. You can configure the same limit for all interfaces configured for a
routing instance. You can also configure a limit for a specific interface.
Starting with Junos OS Release 12.3R4, if you do no... | [
{
"name": "limit",
"desc": "Number of MAC addresses that can be learned from each 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.
Support for EVPNs introduced in Junos OS Release 13.2 on MX 3D Series routers.
Support for EVPNs introduced in Junos OS Release 14.2 on EX Series switches. | [
"Configuring EVPN Routing Instances",
"Configuring EVPN Routing Instances on EX9200 Switches",
"Limiting the Number of MAC Addresses Learned from an Interface"
] |
interface-mac-limit | interface-mac-limit {
limit;
disable;
packet-action;
} | [edit bridge-domains bridge-domain-name bridge-options],
[edit bridge-domains bridge-domain-name bridge-options interface interface-name],
[edit logical-systems logical-system-name bridge-domains bridge-domain-name bridge-options],
[edit logical-systems logical-system-name bridge-domains bridge-domain-name bridge-optio... | Configure a limit to the number of MAC addresses that can be learned from a bridge domain, VLAN,
virtual switch, or set of bridge domains or VLANs.
NOTE: For multichassis link aggregation (MC-LAG) peers in active-active mode,
configuring the interface-mac-limit statement or changing the interface-mac-limit
configuratio... | [
{
"name": "disable",
"desc": "Disables the global interface-mac-limit configuration on an interface and sets the maximum"
},
{
"name": "limit",
"desc": "Sets the maximum number of MAC addresses learned from an interface."
}
] | 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 the switch-options statement added in Junos OS Release 9.2.
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
sta... | [
"Understanding Layer 2 Learning and Forwarding for Bridge Domains",
"Layer 2 Learning and Forwarding for VLANs Overview",
"Understanding Layer 2 Learning and Forwarding for Bridge Domains Functioning as Switches with",
"Layer 2 Trunk Ports",
"Layer 2 Learning and Forwarding for VLANs Acting as a Switch for ... |
interface-map | interface-map {
collector interface-name;
file-specification variant-number;
interface-name {
collector interface-name;
file-specification variant-number;
}
} | [edit services flow-collector] | Match an input interface with a flow collector interface and apply the preset file specifications to the
input interface.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Interface Mappings"
] |
interface-mib (Enhanced Subscriber Management) | interface-mib; | [edit dynamic-profiles profile-name interfaces interface-name] | Enable representation of the Interfaces MIB for the specified dynamic interface.
To achieve maximum performance with enhanced subscriber management, we recommend that you not
enable representation of the Interfaces MIB on all dynamic subscriber interfaces.
Default
If you do not include the interface-mib statement, rep... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1R3.
Support for the interface-mib-oids.sh script added in 18.1R1. | [
"Configuring Junos OS Enhanced Subscriber Management",
"Junos OS Enhanced Subscriber Management Overview"
] |
interface-mode | interface-mode (access | trunk <inter-switch-link>); | [edit interfaces interface-name unit logical-unit-number family bridge],
[edit interfaces interface-name unit logical-unit-number family ethernet-switching],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family bridge] | NOTE: This statement supports the Enhanced Layer 2 Software (ELS) configuration style.
If your switch runs software that does not support ELS, see port-mode. For ELS details,
see Using the Enhanced Layer 2 Software CLI.
QFX3500 and QFX3600 standalone switches—Determine whether the logical interface accepts or
discards ... | [
{
"name": "access",
"desc": "Configure a logical interface to accept untagged packets. Specify the VLAN to which this"
},
{
"name": "trunk",
"desc": "Configure a single logical interface to accept packets tagged with any VLAN ID specified with the"
},
{
"name": "trunk inter-switch-link",... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
inter-switch-link option introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers in
enhanced LAN mode. | [
"Configuring Access Mode on a Logical Interface",
"Configuring a Logical Interface for Trunk Mode",
"Example: Connecting Access Switches with ELS Support to a Distribution Switch with ELS Support",
"Tunnel Services Overview",
"Tunnel Interface Configuration on MX Series Routers Overview"
] |
interface-monitor | interface-monitor interface-name {
weight number;
} | [edit chassis cluster redundancy-group group-number ] | Specify a redundancy group interface to be monitored for failover and the relative weight of the
interface.
For a redundancy group to automatically failover to another node, its interfaces must be monitored.
Interface monitoring monitors the physical status of an interface.
When you configure a redundancy group, you ca... | [
{
"name": "name",
"desc": "Name of the interface to monitor"
},
{
"name": "weight",
"desc": "Weight assigned to this interface that influences failover Range: 0-255"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [] |
interface-name (DHCP Local Server) | interface-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-server ...],
[edit routing-instances routing-instance-name system services dhcp-local-server ...],
[edit system services dhcp-lo... | Specify that the interface name is concatenated with the username during the subscriber authentication
or DHCP client authentication process. Use the statement at the [edit ... dhcpv6] hierarchy levels to
configure DHCPv6 support. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Creating Unique Usernames for DHCP Clients"
] |
interface-name (DHCP Relay Agent) | interface-name; | [edit forwarding-options dhcp-relay authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 group group-name authentication username-include],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name auth... | Specify that the interface name is concatenated with the username during the subscriber authentication
or client authentication process. Use the statement at the [edit ... dhcpv6] hierarchy levels to configure
DHCPv6 support. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4
Support at the [edit ... dual-stack-group dual-stack-group-name] hierarchy level introduced in Junos OS
Release 15.1. | [
"Creating Unique Usernames for DHCP Clients"
] |
interface-name | interface-name interface-name; | [edit logical-systems logical-system-name protocols pim default-vpn-source],
[edit protocols pim default-vpn-source] | Specify the primary loopback address configured in the default routing instance to use as the source
address when PIM hello messages, join messages, and prune messages are sent over multicast tunnel
interfaces for interoperability with other vendors’ routers. | [
{
"name": "interface-name",
"desc": "Primary loopback address configured in the default routing instance to use as the"
}
] | 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. | [] |
interface-name | interface-name; | [edit interfaces interface-name auto-configure vlan-ranges authentication username-include],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication username-include] | Append the interface name and VLAN ID or stacked VLAN ID to the username string used for
authentication. The appended information takes the following format:
•
For single VLAN—<interface-name>:<4-digit-vlan-id>
•
For stack VLANs—<interface-name>:<4-digit-svlan-id>-<4-digit-vlan-id> | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Configuring VLAN Interface Username Information for AAA Authentication"
] |
interface-none | interface-none; | [edit protocols protection-group ethernet-ring ring-name east-interface]
[edit protocols protection-group ethernet-ring ring-name west-interface] | Designates port as not used for Ethernet ring protection. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"Ethernet Ring Protection Switching Overview",
"Ethernet Ring Protection Using Ring Instances for Load Balancing",
"Example: Configuring Ethernet Ring Protection Switching on EX Series Switches",
"Configuring Ethernet Ring Protection Switching on Switches (CLI Procedure)"
] | |
interface-notification (programmable-rpd) | interface-notification name; | [edit logical-systems name routing-options programmable-rpd client id],
[edit routing-options programmable-rpd client id] | Restrict interface event notifications from the programmable routing protocol process (prpd) to specified
JET clients and interfaces. The prpd provides public APIs to program routing systems, making it possible
for users to directly access the APIs to customize, create, and modify behavior of their network.
Default
By... | [
{
"name": "name",
"desc": "Interface name."
}
] | routing | Statement introduced in Junos OS Release 17.4R1. | [] |
interface-num | interface-num integer; | [edit forwarding-options vxlan-routing] | Configure the maximum number of physical interfaces reserved for use in an Ethernet VPN-Virtual
Extensible LAN (EVPN-VXLAN) overlay network.
Juniper Networks switches support a maximum number of physical interfaces for use in either an
underlay network or an EVPN-VXLAN overlay network. By default, a switch allocates 40... | [
{
"name": "integer",
"desc": "Maximum number of physical interfaces reserved for use in an EVPN-VXLAN overlay network on a switch. Range: QFX5110 switches: 0 through 12288. QFX5120 switches: 0 through 14336. The specified"
},
{
"name": "value must be a multiple of 2048",
"desc": "for example, 2... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R1. | [] |
interface-out (Security Forwarding Options) | interface-out interface-name; | [edit security forwarding-options mirror-filter filter-name] | Specify the outgoing logical interface to be matched for mirroring. | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [] |
interface-profile | interface-profile profile-name {
allow-clear;
fields {
field-name;
}
file filename;
interval minutes;
start-time time;
} | [edit accounting-options] | Create a profile to filter and collect error and packet statistics and write them to a file in the /var/log
directory. You can specify an interface profile for either a physical or a logical interface. | [
{
"name": "profile-name",
"desc": "Name of the interface profile."
},
{
"name": "start-time",
"desc": ""
},
{
"name": "time",
"desc": "(Optional) Specify the start time in yyyy-mm-dd.hh:mm local time format for the accounting profile. Sometimes, if the time at which the records are w... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Interface Profile",
"Accounting Options Configuration"
] |
interface-range (QFX Series) | The vlan-id statement is not supported on OCX Series switches.
interface-range interface-range-name {
disable;
description text;
ether-options {
802.3ad aex {
lacp {
force-up;
}
}
(auto-negotiation| no-auto-negotiation);
(flow-contro... | [edit interfaces] | NOTE: The vlan-id statement and Fibre Channel interfaces are not supported on OCX
Series switches.
NOTE: The interface range definition is supported only for Gigabit Ethernet, 10-Gigabit
Ethernet, and Fibre Channel interfaces. Interface ranges are not supported on
channelized interfaces.
Group interfaces that share a c... | [
{
"name": "interface-range-name",
"desc": "Name of the interface range."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Understanding Interface Ranges for Switches",
"Interfaces Overview for Switches",
"Configuring Gigabit and 10-Gigabit Ethernet Interfaces for EX4600 and QFX Series Switches",
"Junos OS Network Interfaces Library for Routing Devices"
] |
interface-range | interface-range name {
member-range interface-name-fpc/pic/port to interface-name-fpc/pic/port;
member interface-name-fpc/pic/port;
member interface-name-fpc/[low-high]/*;
member interface-name-fpc/[pic1,pic2,pic3...picN]/port
/*Common config is added as part of interface-range definition, as f... | edit interfaces (QFX Series, EX Series) | Specify a set of identical interfaces as an interface group, to which you can apply a common
configuration to the entire set of interfaces. This group can consist of both lexical member ranges of
interfaces specified using the member-range interface-type-fpc/pic/port to xx-fpc/pic/port option (regex not
supported), and... | [
{
"name": "member-range",
"desc": "Adds interfaces in lexical order. Regex is not supported. Format:"
},
{
"name": "member-range <start-range> to <end-range>",
"desc": "Example:"
},
{
"name": "member-range ge-0/0/0 to ge-4/0/40;",
"desc": ""
},
{
"name": "member",
"desc":... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Interface Ranges"
] |
interface-routes | interface-routes {
family (inet | inet6) {
export {
lan;
point-to-point;
}
}
rib-group group-name;
} | [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] | Associate a routing table group with the routing device’s interfaces, and specify routing table groups
into which interface routes are imported.
By default, IPv4 interface routes (also called direct routes) are imported into routing table inet.0, and
IPv6 interface routes are imported into routing table inet6.0. If you... | [
{
"name": "inet",
"desc": "Specify the IPv4 address family."
},
{
"name": "inet6",
"desc": "Specify the IPv6 address family."
},
{
"name": "lan",
"desc": "Export LAN routes."
},
{
"name": "point-to-point",
"desc": "Export point-to-point routes."
}
] | 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.
NOTE: On EX Series switches, only dynamically learned routes can be imported from
one routing table group to another. | [
"Example: Populating a Routing Table Created by Virtual Router Configuration",
"Example: Configuring Multiple Routing Instances of OSPF"
] |
interface-service (Services Interfaces) | interface-service {
load-balancing-options {
hash-keys {
egress-key (destination-ip | source-ip);
ingress-key (destination-ip | source-ip);
}
}
service-interface name;
} | [edit services service-set service-set-name] | Specify the device name for the interface service Physical Interface Card (PIC). | [
{
"name": "service-interface name",
"desc": "Name of the service device associated with the interface-wide service set."
}
] | 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 Service Sets to be Applied to Services Interfaces"
] |
interface-set (ANCP) | interface-set interface-set-name {
access-identifier identifier-string;
underlying-interface underlying-interface-name;
} | [edit protocols ancp interfaces] | Identify a group of VLANs on which traffic is sent to a subscriber identified by the access-loop circuit
identifier. | [
{
"name": "interface-set-name",
"desc": "Name of a group of VLANs that carry traffic to the subscriber identified by the access"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Configuring the ANCP Agent",
"Associating an Access Node with Subscribers for ANCP Agent Operations"
] |
interface-set (Dynamic Profiles) | interface-set interface-set-name {
interface interface-name {
unit logical-unit-number;
}
} | [edit dynamic-profiles profile-name interfaces] | For MX Series routers with enhanced queuing DPCs or MPC/MIC modules, configure an interface set
for dynamic CoS. | [
{
"name": "interface-set-name",
"desc": "Name of the interface set to be configured or one of the following Junos OS"
},
{
"name": "predefined variables:",
"desc": ""
},
{
"name": "$junos-interface-set-name",
"desc": "Predefined variable that, when used, is replaced with the interfac... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
$junos-phy-ifd-interface-set-name option added in Junos OS Release 16.1.
$junos-pon-id-interface-set-name option added in Junos OS Release 17.2R1.
Statement introduced for dynamic profile on user plane in Junos OS Evolved Release 25.2R1. | [
"CoS for Interface Sets of Subscribers Overview",
"Configuring an Interface Set of Subscribers in a Dynamic Profile",
"Configuring an Interface Set of Subscribers in a Dynamic Profile",
"Extracting an Option 82 or Option 37 Substring to Create an Interface Set"
] |
interface-set (Dynamic VLAN Interface Sets Association) | interface-set interface-set-name {
interface interface-name {
unit logical-unit-number {
advisory-options {
downstream-rate rate;
upstream-rate rate;
}
}
}
} | [edit dynamic-profiles profile-name interfaces] | For MX Series routers with MPC/MIC modules that face the access side of the network, associate an
agent circuit identifier (ACI) or access-line-identifier (ALI) interface set with a dynamic VLAN subscriber
interface for DHCP or PPPoE subscribers. To associate the interface set with a dynamic subscriber
interface, you m... | [
{
"name": "interface-set-name",
"desc": "Name of the ACI interface set, which is represented in a dynamic profile for a"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring Dynamic VLAN Subscriber Interfaces Based on Agent Circuit Identifier Information",
"Agent Circuit Identifier-Based Dynamic VLANs Overview",
"Configuring Dynamic VLAN Subscriber Interfaces Based on Access-Line Identifiers",
"Access-Line-Identifier-Based Dynamic VLANs Overview"
] |
interface-set (Dynamic VLAN Interface Sets Definition) | interface-set interface-set-name {
interface interface-name;
pppoe-underlying-options {
max-sessions number;
}
} | [edit dynamic-profiles profile-name interfaces] | For MX Series routers with MPC/MIC modules that face the access side of the network, configure an
agent circuit identifier (ACI) or access-line-identifier (ALI) interface set for the creation of dynamic VLAN
subscriber interfaces for DHCP or PPPoE subscribers based on information about the subscriber access
line receiv... | [
{
"name": "interface-set-name",
"desc": "Name of the ACI interface set, which is represented in a dynamic profile by the"
}
] | 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",
"Clearing Agent Circuit Identifier Interface Sets",
"Agent Circuit Identifier-Based Dynamic VLANs Overview",
"Verifying and Managing Configurations for Dynamic VLANs Based on Access-Line Identifiers",
"Clearing Access-Line-Identifier Interface Sets",
"Access-Line-Identifier-... |
interface-set (Ethernet Interfaces) | interface-set interface-set-name {
interface ethernet-interface-name {
(unit unit-number | vlan-tags-outer vlan-tag);
}
} | [edit interfaces] | The set of interfaces used to configure hierarchical CoS schedulers on Ethernet interfaces on the MX
Series router and IQ2E PIC on M Series and T Series routers.
The remaining statements are described separately. | [] | 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. | [] |
interface-set (Hierarchical Schedulers) | interface-set interface-set-name {
excess-bandwidth-share (proportional value | equal);
internal-node;
output-traffic-control-profile profile-name;
output-traffic-control-profile-remaining profile-name;
} | [edit class-of-service interfaces] | Configure hierarchical schedulers for an interface set. | [
{
"name": "interface-set-name",
"desc": "Name of the interface set."
}
] | 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. | [
"Configuring Interface Sets",
"Configuring Hierarchical Schedulers for CoS"
] |
interface-set (IP Demux Interfaces) | interface-set interface-set-name {
interface interface-name {
unit unit-number;
}
} | [edit interfaces] | The set of interfaces used to configure hierarchical CoS schedulers for subscribers on IP demux
interfaces on the MX Series router.
The remaining statements are described separately. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Interfaces Fundamentals"
] |
interface-set | interface-set interface-set-name {
interface-name;
} | [edit firewall],
[edit logical-systems logical-system-name firewall] | Configure an interface set. | [
{
"name": "interface-name",
"desc": "Names of each interface to include in the interface set. You must specify more than one"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Logical systems support introduced in Junos OS Release 9.3. | [
"Filtering Packets Received on an Interface Set Overview"
] |
interface-shared | interface-shared; | [edit dynamic-profiles profile-name firewall family family-name filter filter-name],
[edit firewall family family-name filter filter-name] | Set the interface-shared attribute for a firewall filter.
NOTE: A firewall filter cannot be both interface-specific and interface-shared. | [] | 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. | [
"Interface-Shared Filters Overview",
"Understanding Dynamic Firewall Filters",
"Classic Filters Overview",
"Basic Classic Filter Syntax"
] |
interface-shared | interface-shared; | [edit dynamic-profiles profile-name firewall family family-name filter filter-name],
[edit firewall family family-name filter filter-name] | Set the interface-shared attribute for a firewall filter.
NOTE: A firewall filter cannot be both interface-specific and interface-shared. | [] | 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.
Statement supported for BNG-CUPS in Junos OS Evolved Release 25.2R1. | [
"Interface-Shared Filters Overview",
"Understanding Dynamic Firewall Filters",
"Classic Filters Overview",
"Basic Classic Filter Syntax"
] |
interface-shared-with | interface-shared-with psdn; | [edit interfaces ge-fpc/pic/slot unit logical-unit-number],
[edit interfaces so-fpc/pic/slot unit logical-unit-number],
[edit interfaces xe-fpc/pic/slot unit logical-unit-number] | Assign a logical interface under a shared physical interface to a Protected System Domain (PSD). | [
{
"name": "n",
"desc": "PSD identification as a numeric value."
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
interface-shutdown-action | interface-shutdown-action [soft-shutdown | hard-shutdown] | [edit switch-options] | Configure device to shut down interfaces or temporarily disable interfaces. This action can be done in
addition to the default switching device action for storm control (dropping packets).
Storm control enables the switching device to monitor traffic levels and to drop broadcast, multicast, and
unknown unicast packets ... | [
{
"name": "hard-shutdown",
"desc": "When the storm control level threshold is exceeded, restricts all packets, port will not"
},
{
"name": "soft-shutdown",
"desc": "When the storm control level threshold is exceeded, restricts data packets while control"
}
] | 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-D40. | [
"Example: Configuring Storm Control to Prevent Network Outages on EX Series Switches",
"Understanding Storm Control"
] |
interface-specific (Dynamic Firewalls) | interface-specific; | [edit dynamic-profiles profile-name firewall family family fast-update-filter filter-name]
[edit dynamic-profiles profile-name firewall family family-name filter filter-name] | Configure interface-specific names for firewall counters that are based on fast update filters. | [] | 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. | [
"Configuring Fast Update Filters",
"Interface-Specific Firewall Filter Instances Overview"
] |
interface-specific (Firewall Filters) | interface-specific; | [edit dynamic-profiles profile-name firewall family family-name filter filter-name],
[edit No Link Title family family-name filter filter-name],
[edit logical-systems logical-system-name firewall family family-name filter filter-name] | Configure interface-specific names for firewall counters.
NOTE: A firewall filter cannot be both interface-specific and interface-shared. | [] | 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.
Logical systems support introduced in Junos OS Release 9.3. | [
"Configuring Firewall Filters and Policers for VPLS",
"Interface-Specific Firewall Filter Instances Overview"
] |
interface-specific | interface-specific; | [edit firewall family family-name filter filter-name] | Configure separate counters for each interface to which a filter is applied. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Firewall Filter Match Conditions and Actions (QFX5100, QFX5110, QFX5120, QFX5200, EX4600,",
"EX4650)",
"Configuring Firewall Filters",
"Overview of Firewall Filters (QFX Series)"
] |
interface-state | interface-state {
hold-time {
down seconds;
up seconds;
}
(local | local-interface local-interface | local-remote | remote);
local-count local-count;
vtep-count vtep-count;
} | [edit interfaces name unit num] | Consider other local or remote interface state changes when evaluating the state (up or down) of the
named interface. | [
{
"name": "hold-time",
"desc": ""
},
{
"name": "(down | up)",
"desc": ""
},
{
"name": "seconds",
"desc": "Time to wait in seconds after other interface or remote reachability states change before considering those changes to evaluate the state of the named interface."
},
{
"n... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.3R1. | [] |
interface-status-send-rdi | interface-status-send-rdi interface-status-send-rdi; | [edit logical-systems name protocols oam ethernet connectivity-fault-
management maintenance-domain name maintenance-
association name continuity-check],
[edit protocols oam ethernet connectivity-fault-m... | Configure CFM to propagate the status of the provider edge device via the remote defect indication
(RDI) bit in the CC messages when the interface is down. When the status of the EVPN provider edge
device is standby, the EVPN VPWS service is notified and it sets the interface status to CCC-down.
When the interface stat... | [] | routing—To view this statement in the configuration. | Statement introduced in Junos OS Release 17.3R1. | [
"Configuring Port Status TLV and Interface Status TLV",
"Understanding CFM Monitoring between CE and PE Devices"
] |
interface-status-tlv | interface-status-tlv [ down lower-layer-down ]; | [edit protocols oam ethernet connectivity-fault-management action-profile profile-name event]
[edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name continuity-check] | Defines an action-profile consisting of various events and the action. Based on values of interface-status-
tlv in the received CCM packets, specific action such as interface-down can be taken using "action-
profile" on page 1943 options. | [
{
"name": "down",
"desc": "When the incoming CCM packet contains interface status TLV with value down, the action will be triggered for this action-profile."
},
{
"name": "lower-layer-down",
"desc": "When the incoming CCM packet contains interface status TLV with value lower-layer-down, the acti... | 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. | [
"Configuring Port Status TLV and Interface Status TLV"
] |
interface-switch | interface-switch connection-name {
interface interface-name.unit-number;
} | [edit logical-systems logical-system-name protocols connections],
[edit protocols connections] | Configure Layer 2 switching cross-connects. The cross-connect is bidirectional, so packets received on
the first interface are transmitted out the second interface, and those received on the second interface
are transmitted out the first.
For Layer 2 switching cross-connects to work, you must also configure MPLS. | [
{
"name": "connection-name",
"desc": "Connection name (up to 128 characters in Junos 12.3 and later)."
},
{
"name": "interface interface-name.unit-number",
"desc": "Interface name. Include the logical portion of the name, which"
}
] | 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 CCC Connection for Layer 2 Switching Cross-Connects",
"Defining the Connection for Switching Cross-Connects",
"MPLS Applications User Guide"
] |
interface-tag (DHCP Local Server) | interface-tag name {
access-profile;
dynamic-profile (DHCP Local Server);
overrides (DHCP Local Server);
service-profile (DHCP Local Server);
short-cycle-protection (DHCP Local Server and Relay Agent);;
} | [edit logical-systems name routing-instances name system services dhcp-local-server group],
[edit logical-systems name system services dhcp-local-server group],
[edit logical-systems name tenants name routing-instances name system services dhcp-local-server
group],
[edit routing-instances name system services dhcp-loc... | Configure the interface tag name to map auto-configured dynamic VLANs to DHCP groups. Specify an
interface tag with a dynamic. You can then use the dynamic profile to map to a subset of incoming VLAN
IDs. The maximum number of interface-tags supported is 32. This is also the maximum number of
supported auto-configurabl... | [
{
"name": "name",
"desc": "Interface tag name. The length of the interface tag name cannot exceed 64 characters. The only supported special characters are ^_-*$. The remaining statements are explained separately. Click the linked statement in the Syntax section for details or search for the statement in CLI... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1. | [] |
interface-tag (DHCP Relay Server) | interface-tag name {
access-profile;
dynamic-profile (DHCP Relay Agent);
overrides (DHCP Relay Agent);
service-profile (DHCP Relay Agent);
short-cycle-protection (DHCP Local Server and Relay Agent);
} | [edit bridge-domains name forwarding-options dhcp-relay group],
[edit forwarding-options dhcp-relay group],
[edit logical-systems name bridge-domains name forwarding-options dhcp-relay group],
[edit logical-systems name forwarding-options dhcp-relay group],
[edit logical-systems name routing-instances name bridge-domai... | Configure the interface tag name to map auto-configured dynamic VLANs to DHCP groups. Specify an
interface tag with a dynamic. You can then use the dynamic profile to map to a subset of incoming VLAN
IDs. The maximum number of interface-tags supported is 32. This is also the maximum number of
supported auto-configurabl... | [
{
"name": "name",
"desc": "Interface tag name. The length of the interface tag name cannot exceed 64 characters. The only supported special characters are ^_-*$. The remaining statements are explained separately. Click the linked statement in the Syntax section for details or search for the statement in CLI... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1. | [] |
interface-traceoptions (DHCP) | interface-traceoptions {
file filename <files number> <match regular-expression > <size maximum-file-size> <world-
readable | no-world-readable>;
flag flag;
level (all | error | info | notice | verbose | warning);
no-remote-trace;
} | [edit system processes dhcp-service] | Configure extended DHCP tracing operations that can be enabled on a specific interface or group of
interfaces.
Replaces deprecated interface-traceoptions statements at the [edit forwarding-options dhcp-relay] and [edit
system services dhcp-local-server] hierarchy levels.
To enable the tracing operation on the specific ... | [
{
"name": "file filename",
"desc": "Name of the file to receive the output of the tracing operation. Enclose the name within"
},
{
"name": "files number",
"desc": "(Optional) Maximum number of trace files to create before overwriting the oldest one. If"
},
{
"name": "flag flag",
"des... | trace—To view this statement in the configuration.
trace-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Tracing Extended DHCP Operations for Specific Interfaces"
] |
interface-traceoptions (System Services DHCP) | interface-traceoptions {
file {
filename ;
files number;
match regular-expression;
size maximum-file-size;
(world-readable | no-world-readable);
}
flag flag;
level (all | error | info | notice | verbose | warning);
no-remote-trace;
} | [edit routing-instances routing-instance-name system services dhcp-local-server],
[edit system services dhcp-local-server] | Configure extended DHCP local server tracing operations that can be enabled on a specific interface or
group of interfaces. You use the interface interface-name trace statement at the [edit system services group
group-name] hierarchy level to enable the tracing operation on the specific interfaces. | [
{
"name": "file-name",
"desc": "Name of the file to receive the output of the tracing operation. Enclose the name in quotation"
},
{
"name": "files number",
"desc": "(Optional) Maximum number of trace files. When a trace file named trace-file reaches its"
},
{
"name": "flag flag",
"d... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"DHCP Server Configuration",
"DHCP Server Options"
] |
interface-transmit-statistics | interface-transmit-statistics; | [edit interfaces {interface-name}] | Configure the interface to report the transmitted load statistics. If this statement is not included in the
configuration, the interface statistics show the offered load on the interface, and not the actual
transmitted load.
Aggregated Ethernet interfaces do not support reporting of the transmitted load statistics. You... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4R3. | [
"Improvements to Interface Transmit Statistics Reporting"
] |
interface-type (Protocols OSPF) | interface-type (nbma | p2mp | p2mp-over-lan | p2p) {
ipsec-sa;
ipv4-adjacency-segment;
lan-neighbor;
ldp-synchronization {
(disable | enable);
hold-time;
}
metric;
mtu;
neighbor address {
eligible;
}
no-advertise-adjacency-segment;
no-eligible-backup;
... | [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface
interface-name],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-multicast | ipv4-unicast |
ipv6-multicast) area area-id interface interface-name],
[edit logical-systems logical-system-name routing-instance... | Specify the type of interface.
By default, the software chooses the correct interface type based on the type of physical interface.
Therefore, you should never have to set the interface type. The exception to this is for NBMA
interfaces, which default to an interface type of point-to-multipoint. To have these interface... | [
{
"name": "nbma (OSPFv2 only)",
"desc": "Nonbroadcast multiaccess (NBMA) interface"
},
{
"name": "p2mp",
"desc": "Point-to-multipoint interface"
},
{
"name": "p2mp-over-lan",
"desc": "Point-to-multipoint over LAN mode"
},
{
"name": "p2p",
"desc": "Point-to-point 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.
Support for OSPFv3 for interface type p2p only introduced in Junos OS Release 9.4. You cannot
configure other interface types for OSPFv3.
Support for OSPFv3 for interface type p2mp is introduced in Junos OS Release 18.1R1.
Support for OSPFv3 for interface type p2p only ... | [
"About OSPF Interfaces",
"Example: Configuring an OSPFv2 Interface on a Nonbroadcast Multiaccess Network"
] |
interface-type (Protocols RIP) | interface-type p2mp; | [edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name],
[edit protocols rip group group-name neighbor neighbor-name] | Configure the type of interface in a RIP network.
This statement enables a RIP device to have single or multiple peers through an interface. | [
{
"name": "p2mp",
"desc": "Configure an interface in a RIP network as a point-to-multipoint interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Example: Configuring Point-to-Multipoint RIP Networks"
] |
interfaces (Aggregated Multiservices) | interfaces interface-name {
load-balancing-options {
hash-keys {
egress-key (source-ip | destination-ip);
ingress-key (source-ip | destination-ip);
}
high-availability-options {
(many-to-one | one-to-one) {
preferred-backup preferred-back... | [edit] | Configure the aggregated Multiservices (AMS) interface. The AMS interface provides the infrastructure
for load balancing and high availability (HA). | [
{
"name": "interface-name",
"desc": ""
},
{
"name": "Name of a valid aggregated multiservices interface (ams)",
"desc": "for example, ams0 or ams1."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Configuring Load Balancing on AMS Infrastructure",
"Understanding Aggregated Multiservices Interfaces",
"Example: Configuring an Aggregated Multiservices Interface (AMS)"
] |
interfaces (Analytics Resource) | interfaces {
interface-name {
resource-profile profile-name;
}
} | [edit services analytics resource] | Apply the network analytics resource profile to an interface for which you wish to enable queue or
traffic statistics monitoring. The resource profile is a template that specifies the parameters for queue
and traffic monitoring, as well as for the depth and latency thresholds.
NOTE: The interfaces statement in the [ed... | [
{
"name": "interface-name",
"desc": "Name of the interface for which a resource profile has been configured."
},
{
"name": "resource-profile",
"desc": ""
},
{
"name": "profile-name",
"desc": "Name of a resource profile containing the analytics parameters that have been specified for ... | 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"
] |
interfaces (Analytics) | interfaces {
all {
depth-threshold high number low number;
latency-threshold high number low number;
queue-statistics;
no-queue-statistics;
traffic-statistics;
no-traffic-statistics;
}
interface-name {
depth-threshold high number low number;
la... | [edit services analytics] | Configure physical interfaces for monitoring traffic and queue statistics by the network analytics
processes running on the Packet Forwarding Engine and Routing Engine. You may specify one interface
or all interfaces in your configuration.
NOTE: The configuration for a specific interface supersedes the global configur... | [
{
"name": "all",
"desc": "Configure all interfaces on the device for high-frequency monitoring."
},
{
"name": "interface-name",
"desc": "Name of the interface to configure for high-frequency monitoring."
},
{
"name": "no-queue-statistics",
"desc": "Disable the collection of queue sta... | 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"
] |
interfaces (ANCP) | interfaces {
interface-set interface-set-name {
access-identifier identifier-string;
underlying-interface underlying-interface-name;
}
interface-name {
access-identifier identifier-string
}
} | [edit protocols ancp] | Identify the subscribers whose traffic is reported and shaped by the ANCP agent. | [
{
"name": "interface-name",
"desc": "Name of a logical interface supporting a single VLAN that carries traffic to the subscriber"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Configuring the ANCP Agent",
"Associating an Access Node with Subscribers for ANCP Agent Operations"
] |
interfaces (Autoinstallation) | interfaces {
interface-name {
bootp;
rarp;
}
} | [edit system autoinstallation] | Configure the interface on which to perform autoinstallation. A request for an IP address is sent from
the interface. Specify the IP address procurement protocol.
NOTE: When you run the system autoinstallation command, the command will configure
unit 0 logical interface for all the active state physical interfaces. How... | [
{
"name": "bootp",
"desc": "Enables BOOTP or DHCP during autoinstallation."
},
{
"name": "rarp",
"desc": "Enables RARP during autoinstallation."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Autoinstallation Overview",
"Configuring Autoinstallation of Configuration Files"
] |
interfaces (Chassis Synchronization Source) | interfaces interface-name {
priority number;
quality-level (prc | prs |sec | smc | ssu-a | ssu-b | st2 | st3 | st3e | st4 | stu | tnc);
request request (force-switch | lockout);
wait-to-restore minutes;
} | [edit chassis synchronization source] | Configure an interface with an upstream clock source to be considered one of the candidate sources for
the chassis synchronization by the clock source selection algorithm. | [
{
"name": "interface-name",
"desc": "Consider the specified interface as a candidate source. Additional Information A maximum of 8 clock sources can be configured."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"External Clock Synchronization Overview for ACX Series Routers",
"Configuring External Clock Synchronization for ACX Series Routers",
"Synchronous Ethernet Overview",
"show chassis synchronization"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.