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 |
|---|---|---|---|---|---|---|---|
inet6 (TDF Subscriber Exclude Prefix) | inet6 {
network address mask;
} | [edit unified-edge gateways tdf gateway-name domains domain-name subscriber-exclude-prefix
family] | Specify IP version 6 (IPv6) for the network prefix of source IP addresses for uplink packets and
destination IP addresses for downlink packets that do not undergo TDF processing.
The remaining statement is explained separately. See CLI Explorer. | [] | 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 a Set of IP-Based TDF Subscriber Properties with a TDF Domain",
"Configuring IFL-Based TDF Subscribers and Properties with a TDF Domain",
"Understanding the Definition of a Set of IP-Based Subscriber Properties with a TDF Domain",
"IP-Based and IFL-Based TDF Subscribers Overview",
"IP-Based Sub... |
inet6 | inet6; | [edit logical-systems logical-system-name routing-options forwarding-table chained-composite-
next-hop ingress labeled-bgp],
[edit routing-options forwarding-table chained-composite-next-hop ingress labeled-bgp] | Allows you to configure chained composite next hops for IPv6 labeled-unicast routes. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | This statement was introduced in Junos OS Release 12.3. | [
"Accepting Route Updates with Unique Inner VPN Labels in Layer 3 VPNs"
] |
inet6-advertise-interval (VRRP) | inet6-advertise-interval milliseconds; | [edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-
group group-id],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet6 address address vrrp-inet6-group group-id] | Configure the interval between Virtual Router Redundancy Protocol (VRRP) IPv6 advertisement packets.
All routers in the VRRP group must use the same advertisement interval.
NOTE: When VRRPv3 is enabled, the inet6-advertise-interval statement cannot be used
to configure advertisement intervals. Instead, use the fast-int... | [
{
"name": "milliseconds",
"desc": "Interval, in milliseconds, between advertisement packets."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4R2. | [
"No title for referred element: topic-map",
"Configuring VRRP for IPv6 (CLI Procedure)"
] |
inet6-backup-router | inet6-backup-router address <destination destination-address>; | [edit system] | Set a default router (running IP version 6 [IPv6]) to use while the local router or switch (running IPv6) is
booting and if the routing protocol processes fail to start. The Junos OS removes the route to this router
or switch as soon as the software starts. | [
{
"name": "address",
"desc": "Address of the default router."
},
{
"name": "destination",
"desc": ""
},
{
"name": "destination-address",
"desc": "(Optional) Destination address that is reachable through the backup router. You can include this option to achieve network reachability wh... | 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. | [] |
inet6-bgpmcast | inet6-bgpmcast {
signaling;
} | [edit protocols bgp family],
[edit protocols bgp group group-name family],
[edit protocols bgp neighbor neighbor-address family] | Enable the inet6-bgpmcast address family to advertise BGP multicast NLRI.
IPv4 and IPv6 can be enabled or disabled separately. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1 | [
"Controller-Based BGP Multicast Signaling"
] |
inet6-mvpn (BGP) | inet6-mvpn {
signaling {
accepted-prefix-limit {
maximum number;
teardown percentage {
idle-timeout (forever | minutes);
}
}
loops number
prefix-limit {
maximum number;
teardown percentage {
... | [edit logical-systems logical-system-name protocols bgp family],
[edit protocols bgp family],
[edit logical-systems logical-system-name protocols bgp group group-name family],
[edit protocols bgp group group-name family] | Enable the inet6-mvpn address family in BGP. | [] | 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. | [
"BGP Configuration Overview"
] |
inet6-mvpn (VRF Advertisement) | inet6-mvpn; | [edit logical-systems logical-system-name routing-instances routing-instance-name vrf-advertise-
selective family],
[edit routing-instances routing-instance-name vrf-advertise-selective family] | Enable IPv6 MVPN routes to be advertised from the VRF instance. | [] | 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. | [] |
inet6-options (Services) | inet6-options {
source-address address;
} | [edit services rpm probe owner test test-name] | Specify the source IPv6 address used for probes. If the source IPv6 address is not one of the devices’
assigned addresses, the packet uses the outgoing interface’s address as its source. | [
{
"name": "inet6-options",
"desc": "Use the specified base IPv6 protocol-related settings to be used for RPM probes"
},
{
"name": "source-address ipv6-address",
"desc": "Specify the base IPv6 address for sending the RPM probes from the client to"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1R4. | [
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches"
] |
inet6-precedence (CoS Rewrite Rules) | inet6-precedence rewrite-name {
protocol mpls;
} | [edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules] | Apply an IPv6 precedence rule to rewrite the first three bits of the IPv6 DSCP value. | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules inet6-precedence] hierarchy level."
},
{
"name": "protocol mpls",
"desc": "(Optional for ingress MPLS tunnel nodes) Rewrite the DSCP value for IPv6 packets entering the MPLS ... | 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 Rewrite Rules",
"Applying Rewrite Rules to Output Logical Interfaces"
] |
inet6-vpn | inet6-vpn (any | multicast | unicast) {
aggregate-label;
prefix-limit maximum;
rib-group rib-group-name;
} | [edit logical-systems logical-system-name protocols bgp family],
[edit logical-systems logical-system-name protocols bgp group group-name family],
[edit protocols bgp family],
[edit protocols bgp group group-name family] | Enable IP version 6 (IPv6) on the provider edge (PE) router for the Layer 3 VPN.
NOTE: The [edit logical-systems] hierarchy level is not applicable in ACX Series routers. | [
{
"name": "any",
"desc": "Configure the family type to be both multicast and unicast."
},
{
"name": "multicast",
"desc": "Configure the family type to be multicast. This means that the BGP peers are being used only"
},
{
"name": "prefix-limit maximum",
"desc": "Maximum prefix limit."... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Layer 3 VPNs to Carry IPv6 Traffic",
"Configuring Aggregate Labels for VPNs",
"Junos OS Routing Protocols Library"
] |
inet | inet; | [edit logical-systems logical-system-name routing-options forwarding-table chained-composite-
next-hop ingress labeled-bgp],
[edit routing-options forwarding-table chained-composite-next-hop ingress labeled-bgp] | Allows you to configure chained composite next hops for IPv4 labeled-unicast routes. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | This statement was introduced in Junos OS Release 22.2. | [
"Accepting Route Updates with Unique Inner VPN Labels in Layer 3 VPNs"
] |
inet-bgpmcast | inet-bgpmcast {
signaling;
} | [edit protocols bgp family],
[edit protocols bgp group group-name family],
[edit protocols bgp neighbor neighbor-address family] | Enable the inet-bgpmcast address family to advertise BGP multicast NLRI.
IPv4 and IPv6 can be enabled or disabled separately. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1 | [
"Controller-Based BGP Multicast Signaling"
] |
inet-mdt (Signaling) | signaling {
accepted-prefix-limit {
maximum number;
teardown <percentage-threshold> idle-timeout (forever | minutes);
drop-excess <percentage>;
hide-excess <percentage>;
}
add-path {
receive;
send {
include-backup-path backup_path_number;
... | [edit logical-systems logical-system-name protocols bgp family],
[edit logical-systems logical-system-name protocols bgp group group-name family],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address
family],
[edit protocols bgp family],
[edit protocols bgp group group-name family]... | For draft-rosen 7, on the provider edge router enable BGP intra-AS auto-discovery using MDT-SAFI. | [] | 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 Source-Specific Multicast for Draft-Rosen Multicast VPNs"
] |
inet-mdt | inet-mdt; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
mvpn family (inet | inet6) autodiscovery],
[edit routing-instances routing-instance-name protocols pim mvpn family (inet | inet6)
autodiscovery] | For Rosen 7, configure the PE router in a VPN to use an SSM multicast distribution tree (MDT)
subsequent address family identifier (SAFI) NLRI . | [] | 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.
Statement moved to [..protocols pim mvpn family inet] from [.. protocols mvpn] in Junos OS Release 13.3.
Support for IPv6 added in Junos OS Release 17.3R1. | [
"Example: Configuring Source-Specific Multicast for Draft-Rosen Multicast VPNs"
] |
inet-mvpn (BGP) | inet-mvpn {
signaling {
accepted-prefix-limit {
maximum number;
teardown percentage {
idle-timeout (forever | minutes);
}
}
damping;
loops number;
prefix-limit {
maximum number;
teardown percentage {
... | [edit logical-systems logical-system-name protocols bgp family],
[edit protocols bgp family],
[edit logical-systems logical-system-name protocols bgp group group-name family],
[edit protocols bgp group group-name family] | Enable the inet-mvpn address family in BGP. | [] | 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. | [] |
inet-mvpn (VRF Advertisement) | inet-mvpn; | [edit logical-systems logical-system-name routing-instances routing-instance-name vrf-advertise-
selective family],
[edit routing-instances routing-instance-name vrf-advertise-selective family] | Enable IPv4 MVPN routes to be advertised from the VRF instance. | [] | 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. | [
"Limiting Routes to Be Advertised by an MVPN VRF Instance"
] |
inet-precedence (Classifier on Physical Interface) | inet-precedence (classifier-name | default); | [edit class-of-service interfaces interface-name classifiers] | On ACX Series Universal Metro routers and EX Series switches, map the inet-precedence field of the
incoming packet to the forwarding class and packet loss priority, based on the specified inet-precedence
classifier. When no classifier is configured on the physical interface, the default ipprec-compatibility
inet-prece... | [
{
"name": "classifier-name",
"desc": "Name of the previously defined inet-precedence behavior aggregate classifier."
},
{
"name": "default",
"desc": "Default inet-precedence behavior aggregate classifier."
}
] | 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. | [] |
inet-precedence (CoS Classifiers) | inet-precedence (classifier-name | default) {
import (classifier-name | default);
forwarding-class class-name {
loss-priority level code-points [ aliases ] [ bit-patterns ]
}
} | [edit class-of-service classifiers] | Define an IPv4 classifier. | [
{
"name": "default",
"desc": "The default mapping. By default, IP precedence rewrite rules alter the first three bits on the type"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Understanding How Behavior Aggregate Classifiers Prioritize Trusted Traffic"
] |
inet-precedence (CoS Rewrite Rules) | inet-precedence (rewrite-name | default) protocol (inet-both | inet-outer | mpls); | [edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules] | Apply an IPv4 precedence rewrite rule. | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules inet-precedence] hierarchy level."
},
{
"name": "default",
"desc": "The default mapping. By default, IP precedence rewrite rules alter the first three bits on the type of ser... | 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 Rewrite Rules",
"Applying Rewrite Rules to Output Logical Interfaces"
] |
inet-precedence (Dynamic Classifiers) | inet-precedence (classifier-name | default); | [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-
number classifiers] | Apply a IPv4 precedence classifier to a subscriber interface in a dynamic profile. | [
{
"name": "classifier-name",
"desc": "Name of a classifier mapping configured at the [edit class-of-service classifiers inet-precedence] hierarchy level."
},
{
"name": "default",
"desc": "The default mapping."
}
] | 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. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Applying a Classifier to a Subscriber Interface in a Dynamic Profile",
"classifiers (Definition)"
] |
inet-precedence (Dynamic Rewrite Rules) | inet-precedence (rewrite-name | default); | [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-
number rewrite-rules] | Apply a IPv4 precedence rewrite rule. | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules inet-precedence] hierarchy level."
},
{
"name": "default",
"desc": "The default mapping. By default, IP precedence rewrite rules alter the first three bits on the type"
}
] | 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. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Applying a Rewrite Rule Definition to a Subscriber Interface in a Dynamic Profile",
"rewrite-rules"
] |
inet-precedence (Rewrite Rules on Physical Interface) | inet-precedence (rewrite-name | default); | [edit class-of-service interfaces interface-name rewrite-rules] | Apply a IPv4 precedence rewrite rule. | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules inet-precedence] hierarchy level."
},
{
"name": "default",
"desc": "The default mapping. By default, IP precedence rewrite rules alter the first three bits on the type"
}
] | 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. | [] |
inet-precedence | inet-precedence classifier-name {
import (classifier-name | default);
forwarding-class class-name {
loss-priority level {
code-points [ aliases ] [ 6–bit-patterns ];
}
}
} | [edit class-of-service classifiers],
[edit class-of-service code-point-aliases],
[edit class-of-service interfaces interface-name unit logical-unit-number classifiers],
[edit class-of-service rewrite-rules] | Apply an IPv4 precedence rewrite rule. | [
{
"name": "classifier-name",
"desc": "Name of the classifier."
}
] | 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. | [
"Example: Configuring CoS on EX Series Switches",
"Defining CoS Classifiers (CLI Procedure)",
"Defining CoS Classifiers (J-Web Procedure)",
"Defining CoS Code-Point Aliases (CLI Procedure)",
"Defining CoS Code-Point Aliases (J-Web Procedure)",
"Defining CoS Rewrite Rules (CLI Procedure)",
"Defining CoS ... |
infinity | infinity [ policy-names ]; | [edit logical-systems logical-system-name protocols pim spt-threshold],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
spt-threshold],
[edit protocols pim spt-threshold],
[edit routing-instances routing-instance-name protocols pim spt-threshold] | Apply one or more policies to set the SPT threshold to infinity for a source-group address pair. Use the
infinity statement to prevent the last-hop routing device from transitioning from the RPT rooted at the
RP to an SPT rooted at the source for that source-group address pair. | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0. | [
"Example: Configuring the PIM SPT Threshold Policy"
] |
infranet-controller | infranet-contoller host-name {
address ip-address;
ca-profile [ca-profile];
interface interface-name;
password password;
port port-number;
server-certificate-subject subject;
} | [edit services unified-access-control ] | To configure an Infranet Controller, specify the hostname of the IC Series device with which the SRX
Series Firewall should communicate. Possible values for this statement range from 1 to 31 characters.
This statement is required when you are configuring the SRX Series Firewall to act as a Junos OS
Enforcer in a Unifie... | [] | 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. | [
"Firewall User Authentication Overview"
] |
ingress (Analyzer) | ingress {
bridge-domain bridge-domain-name;
interface (all | interface-name);
routing-instance {
instance-name {
bridge-domain bridge-domain-name;
}
vlan (vlan-id | vlan-name);
}
vlan (vlan-id | vlan-name);
} | [edit forwarding-options analyzer analyzer-name input] | Configure ports, routing instances, VLANs, or bridge domains for which the entering traffic is mirrored as
part of a mirroring configuration.
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 13.2X50-D10. | [
"Example: Configuring Mirroring for Remote Monitoring of Employee Resource Use Through a Transit",
"Switch on EX9200 Switches"
] |
ingress (Buffer Configuration) | ingress {
buffer-partition (lossless | lossless-headroom | lossy) {
percent percent;
}
percent percent;
} | [edit class-of-service shared-buffer] | Configure the global shared buffer pool allocation for ingress traffic. The system allocates the shared
buffer pool dynamically across its ports as the ports require memory space. Some buffer space is
reserved for buffers such as dedicated buffers (buffers allocated permanently to ports) and headroom
buffers (buffers t... | [
{
"name": "percent percent",
"desc": "Percentage of available ingress buffer space allocated to the shared buffer pool. If the"
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Example: Recommended Configuration of the Shared Buffer Pool for Networks with Mostly Best-",
"Effort Unicast Traffic",
"Example: Recommended Configuration of the Shared Buffer Pool for Networks with Mostly Multicast",
"Traffic",
"Example: Recommended Configuration of the Shared Buffer Pool for Networks wi... |
ingress (Chained Composite Next Hop) | ingress {
(evpn | no-evpn);
(fec129-vpws | no-fec129-vpws);
(l2ckt | no-l2ckt);
(l2vpn | no-l2vpn);
l3vpn ;
labeled-bgp;
} | [edit logical-systems logical-system-name routing-options forwarding-table chained-composite-next-
hop],
[edit routing-options forwarding-table chained-composite-next-hop] | Allows you to configure chained composite next hops for devices handling ingress traffic in the network.
NOTE:
•
On MX Series routers containing both DPC and MPC FPCs, the chassis must be
configured with enhanced-ip option for enabling chained composite next hops. Only the
"l3vpn" on page 9983 option under the ingress... | [
{
"name": "evpn | no-evpn",
"desc": "Enable or disable composite chained next hop for ingress EVPN label-switched paths (LSPs)."
},
{
"name": "fec129-vpws | no-fec129-vpws",
"desc": "Enable or disable composite chained next hop for ingress FEC 129 virtual private wire service (VPWS) LSPs."
},
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | This statement was introduced in Junos OS Release 12.1.
labeled-bgp option was introduced in Junos OS Release 12.3.
l2ckt, l2vpn, no-l2ckt, and no-l2vpn options were introduced in Junos OS Release 13.3.
evpn, fec129-vpws, no-evpn, and no-fec129-vpws options were introduced in Junos OS Release 14.1. | [
"Accepting Route Updates with Unique Inner VPN Labels in Layer 3 VPNs"
] |
ingress (LSP) | ingress {
bandwidth bps;
class-of-service cos-value;
description string;
entropy-label;
install {
destination-prefix <active>;
}
link-protection bypass-name name;
metric metric;
next-hop (address | interface-name | address/interface-name);
node-protection bypass-name nam... | [edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name],
[edit protocols mpls static-label-switched-path lsp-name] | Configure an ingress LSR for a static LSP.
The remaining statements are explained separately | [] | 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.
entropy-label option introduced in Junos OS Release 14.1. | [
"Configuring Static LSPs"
] |
ingress (Port Mirroring) | ingress {
interface (all | interface-name);
vlan (vlan-id | vlan-name);
} | For platforms without ELS:
[edit ethernet-switching-options analyzer name input]
For platforms with ELS:
[edit forwarding-options analyzer name input] | Specify the interfaces or VLANs for which incoming traffic is mirrored as part of a port mirroring
configuration.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.routing-control—To add this statement to the
configuration. | Statement introduced in Junos OS Release 11.1. | [
"Understanding Port Mirroring and Analyzers",
"Configuring Port Mirroring",
"Examples: Configuring Port Mirroring for Local Analysis"
] |
ingress (vlans) | ingress; | [edit vlans vlan-name vlan-id number interface interface-name] | Specify that the member interface of the VLAN allows only ingress traffic. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [] |
ingress-egress-recycle | ingress-egress-recycle; | [edit system packet-forwarding-options mcast-repl-type] | Use this statement to enable ingress and egress recycle replication that helps restarts Packet Forwarding
Engine. If you don’t select the replication type, ingress replication (ingress-only) is considered as the
default replication type. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.4R1. | [] |
ingress-node-replication (EVPN) | ingress-node-replication; | [edit routing-instances routing-instance-name vlans vlan-name vxlan],
[edit vlans vlan-name vxlan] | EVPN all-active mode with VXLAN encapsulation is based on the local bias for traffic coming from the
access layer (redundant Layer 2 gateway function through a pair of top-of-rack switches). Because the
traffic has no MPLS label, the split-horizon filtering rule for multihomed Ethernet segments is modified
to be based ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D30 . | [
"Understanding EVPN with VXLAN Data Plane Encapsulation"
] |
ingress-node-replication | ingress-node-replication; | [edit bridge-domains bridge-domain-name vxlan],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name vxlan],
[edit routing-instances routing-instance-name vlans vlan-name vxlan],
[edit routing-instances routing-instance-name vxlan]
[edit vlans vlan-name vxlan] | Enable ingress node replication for a specified Virtual Extensible LAN (VXLAN) that is managed by the
Open vSwitch Database (OVSDB) management protocol.
With this feature enabled, instead of service nodes, Juniper Networks devices with OVSDB
implemented handle incoming broadcast, unknown unicast, or multicast (BUM) tra... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1R2. | [
"Configuring OVSDB-Managed VXLANs"
] |
ingress-only | ingress-only; | [edit system packet-forwarding-options mcast-repl-type] | Use this statement to to enable full ingress replication model that helps restarts Packet Forwarding
Engine. If you don’t select the replication type, ingress replication (ingress-only) is considered as the
default replication type. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.4R1. | [] |
ingress-policer-overhead | ingress-policer-overhead bytes; | [edit chassis fpc slot-number pic pic-number] | Add the configured number of bytes to the length of a packet entering the interface.
Configure a policer overhead to control the rate of traffic received on an interface. Use this feature to
help prevent denial-of-service (DoS) attacks or to enforce traffic rates to conform to the service-level
agreement (SLA). When yo... | [
{
"name": "bytes",
"desc": "Number of bytes added to a frame entering an interface."
},
{
"name": "[edit chassis fpc 0 pic 0]",
"desc": ""
},
{
"name": "user@host# set ingress-policer-overhead 10;",
"desc": ""
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 11.1. | [
"Policer Overhead to Account for Rate Shaping Overview",
"Example: Configuring Policer Overhead to Account for Rate Shaping",
"Configuring a Policer Overhead",
"CoS on Enhanced IQ2 PICs Overview"
] |
ingress-policy | ingress-policy [ingress-policy-names]; | [edit logical-systems logical-system-name protocols ldp entropy-label],
[edit logical-systems logical-system-name protocols ldp oam],
[edit protocols ldp entropy-label],
[edit protocols ldp oam] | Configure an LDP ingress policy for either the entropy label or Operation, Administration, and
Management (OAM).
For OAM, configure the ingress policy to choose which forwarding equivalence classes (FECs) need to
have OAM enabled. If the FEC passes through the policy or if the FEC is explicitly configured, OAM is
enabl... | [
{
"name": "ingress-policy-names",
"desc": "Specify the names of the ingress policies."
}
] | 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.
Statement introduced at the [edit protocols ldp entropy-label] hierarchy level in Junos OS Release 14.1. | [
"Configuring OAM Ingress Policies for LDP",
"Configuring the Entropy Label for LSPs"
] |
ingress-queuing-filter | ingress-queuing-filter filter-name; | [edit interfaces interface-name unit unit-number family family-name],
[edit logical-systems logical-system-name interfaces interface-name unit unit-number family
family-name] | Use the ingress-queuing-filter statement to set the packet loss priority and forwarding class for the
packet, or drop the packet prior to input queue selection. This assists in traffic shaping.
The ingress-queuing-filter statement is available only for the following protocol families: bridge, ccc, inet,
inet6, mpls, an... | [] | 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. | [
"Example: Configuring a Filter for Use as an Ingress Queuing Filter"
] |
ingress-rate-limit | ingress-rate-limit rate; | [edit interfaces interface-name fastether-options] | Perform port-based rate limiting on ingress traffic arriving on Fast Ethernet 8-port, 12-port, and 48-port
PICs. | [
{
"name": "rate",
"desc": "Traffic rate, in megabits per second (Mbps)."
}
] | 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 Ingress Rate Limit"
] |
ingress-replication | ingress-replication {
create-new-ucast-tunnel;
label-switched-path {
label-switched-path-template {
(template-name | default-template);
}
}
} | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel],
[edit protocols mvpn inter-region-template template template-name all-regions],
[edit protocols mvpn inter-region-template template template-name region region-name],
[edit routing-instances routing-instance-name provid... | A provider tunnel type used for passing multicast traffic between routers through the MPLS cloud, or
between PE routers when using MVPN. The ingress replication provider tunnel uses MPLS point-to-
point LSPs to create the multicast distribution tree.
Optionally, you can specify a label-switched path template. If you co... | [
{
"name": "existing-unicast-tunnel",
"desc": "An existing tunnel to the destination is used for ingress replication. If an"
},
{
"name": "create-new-ucast-tunnel",
"desc": "When specified, a new unicast tunnel to the destination is created and used"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Example: Configuring Ingress Replication for IP Multicast Using MBGP MVPNs"
] |
ingress-shaping-overhead | ingress-shaping-overhead number; | [edit chassis fpc slot-number pic pic-number traffic-manager],
[edit chassis lcc number fpc slot-number pic pic-number traffic-manager] | Number of bytes to add to packet to determine shaped session packet length.
NOTE: Although the ingress queuing filter can be used with EX9200 switches and MX-
Series routers, it is used only on those MX Series routers that have MPCs. An error is
generated at commit if the ingress queuing filter is applied to an interfa... | [
{
"name": "number",
"desc": "When L2TP session shaping is configured, the number of CoS shaping overhead bytes to add to"
}
] | 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. | [] |
ingress-stats (Flat-File Accounting Options) | ingress-stats {
all-fields;
drop-packets;
input-bytes;
input-packets;
output-bytes;
output-packets;
queue-id;
} | [edit accounting-options flat-file-profile profile-name fields] | Specify ingress queue statistics to be collected for the interface. | [
{
"name": "all-fields",
"desc": "Collect all ingress queue statistics available for the interface context, logical or physical."
},
{
"name": "drop-packets",
"desc": "Collect the number of received packets dropped on the Ingress queue."
},
{
"name": "input-bytes",
"desc": "Collect th... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R4. | [
"Configuring Flat-File Accounting for Layer 2 Wholesale",
"Configuring Flat-File Accounting for Extensible Subscriber Services Management",
"Flat-File Accounting Overview"
] |
inherit-advertisement-interval | inherit-advertisement-interval seconds; | [edit protocols vrrp] | Set the time interval for advertisement for inherit sessions. | [
{
"name": "inherit-advertisement-interval seconds",
"desc": "Time interval for inherit sessions advertisements in seconds. The default value is the recommended value. Default: 120 Range: 5 to 120"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [] |
init-command-string | init-command-string initialization-command-string; | [edit interfaces umd0 modem-options] | For J Series Services Routers, configure the command string used to initialize the USB modem.
When you connect the USB modem to the USB port on a Services Router, the router applies the modem
AT commands configured in the init-command-string command to the initialization commands on the
modem.
For example, the initial... | [
{
"name": "initialization-command-string",
"desc": "Specify an initialization command string using the following AT command"
},
{
"name": "values:",
"desc": ""
},
{
"name": "%C0",
"desc": "Disables data compression."
},
{
"name": "&C1",
"desc": "Disables reset of the mode... | 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. | [] |
init-descriptor | init-descriptor file-path; | [edit virtual-network-functions] | Create an XML descriptor file to launch a VNF. You can launch a VNF by configuring the VNF name, and
specifying either the path to the XML descriptor file or to an image. | [
{
"name": "file-path",
"desc": "Path of the init-descriptor XML file."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D45. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
initial-route-check | initial-route-check seconds; | [edit interfaces dln unit logical-unit-number dialer-options] | On J Series Services Routers with ISDN interfaces, allows the router to check whether the primary route
is up after the initial startup of the router is complete and the timer expires. | [
{
"name": "seconds",
"desc": "How long to wait to check if the primary interface is up after the router comes up."
}
] | 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. | [
"ISDN Interfaces Overview"
] |
initial-tcp-mss | initial-tcp-mss mss-value; | [edit security policies from-zone zone-name to-zone zone-name
policy policy-name then permit tcp-options] | Configure the TCP maximum segment size (MSS) for packets that arrive at the ingress interface (initial
direction), match a specific policy, and for which a session is created. The value you configure overrides
the TCP MSS value in the incoming packet when the value in the packet is higher than the one you
specify.
The ... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D20. | [
"tcp-mss (Security Flow)",
"syn-flood-protection-mode"
] |
initiate-dead-peer-detection | initiate-dead-peer-detection; | [edit services ipsec-vpn rule rule-name term term-name then] | Enable triggering of dead peer detection (DPD) hello messages to the remote peer for the specified
tunnel. | [] | 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 .
Support for IKEv2 introduced in Junos OS Release 11.4. | [
"Configuring IPsec Rules"
] |
initiate-ncp (Dynamic and Static PPP) | initiate-ncp (ip | ipv6 | dual-stack-passive); | [edit access group-profile profile-name ppp ppp-options],
[edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit ppp-options],
[edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit ppp-options],
[edit interfaces pp0 unit logical-unit-number ppp-opti... | Configure PPP Network Control Protocol (NCP) negotiation mode (active or passive) for dynamic and
static IPv4 and IPv6 PPP subscriber interfaces. You can also configure PPP NCP negotiation mode for
the PPP server in an IPv4/IPv6 dual-stack configuration. | [
{
"name": "dual-stack-",
"desc": ""
},
{
"name": "passive",
"desc": "Enable passive PPP NCP negotiation for the PPP server in an IPv4/IPv6 dual-stack configuration. The initiate-ncp dual-stack-passive statement overrides the initiate-ncp ip and initiate-ncp ipv6 statements if they are configured... | 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. | [
"PPP Network Control Protocol Negotiation",
"PPP Network Control Protocol Negotiation"
] |
initiation (Services) | initiation{
profile name {
actions {
crl {
disable disable;
if-not-present (allow | drop);
ignore-hold-instruction-code ignore-hold-instruction-code;
}
ignore-server-auth-failure ignore-server-auth-failure;
}
... | [edit services ssl] | Specify the configuration for Secure Socket Layer (SSL) initiation support service. The SRX Series
Firewall, acting as an SSL proxy client, initiates and maintains SSL sessions between itself and an SSL
server. SRX Series Firewall receives un-encrypted data from an HTTP client, and encrypts and transmits
the data as ci... | [
{
"name": "client-certificate",
"desc": "Local certificate."
}
] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. The protocol-version statement is updated to
include tls11 and tls12 from Junos OS Release 15.1X49-D30. | [
"Configuring SSL Forward Proxy",
"Firewall User Authentication Overview"
] |
inline | inline; | [edit protocols lacp ppm] | (MX Series routers with MPC line cards only) To enable the inline Link Aggregation Control Protocol
(LACP) PDU transmission processing.
This statement disables the default distributed periodic packet management (PPM) processing for Link
Aggregation Control Protocol (LACP) packets and run all Link Aggregation Control Pr... | [] | 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. | [
"Disabling or Enabling Inline Periodic Packet Management for LACP Packets",
"Configuring Link Aggregation",
"Configuring Aggregated Ethernet LACP (CLI Procedure)"
] |
inline-fpga-crypto | inline-fpga-crypto (disabled | enabled); | [edit security forwarding-process application-services (Security Forwarding Process)] | Enable or disable Inline FPGA Decryption (IFD) for cryptographic operation.
By default, the inline-fpga-crypto is disabled. To use the feature, enable the option.
Ensure you enable PMI processing when using inline-fpga-crypto option to avoid the risk of traffic loss.
PowerMode IPsec (PMI) uses AES-NI for encryption and... | [
{
"name": "disabled",
"desc": "Disable inline FPGA crypto"
},
{
"name": "enabled",
"desc": "Enable inline FPGA crypto"
}
] | security | Statement introduced in Junos OS Release 20.4R1. | [
"Improving IPsec Performance with PowerMode IPsec",
"application-services (Security Forwarding Process)"
] |
inline-jflow (Forwarding Options) | inline-jflow {
flow-export-rate number;
source-address ip-address;
} | [edit forwarding-options sampling instance instance- name family inet output]
[edit forwarding-options sampling instance instance- name family inet6 output] | Specify Inline processing of sampled packets. | [
{
"name": "flow-export-rate value",
"desc": "Flow export rate of monitored packets in kpps. The range is from 1 through"
},
{
"name": "source-address address",
"desc": "Address to use for generating monitored packets."
}
] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. Support. | [
"Understanding Interfaces"
] |
inline-jflow | inline-jflow {
source-address address;
flow-export-rate rate;
} | [edit forwarding-options sampling instance instance-name family inet output] | Specify inline active flow monitoring for traffic from the designated address.
The remaining statements are explained separately. See CLI Explorer.
NOTE: If you configure inline flow monitoring with inline-jflow then you have to disable
it before performing ISSU. For more information, see Before You Begin a Unified ISS... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2.
Statement introduced in Junos OS Release 17.2R1 for QFX10002 switches.
Support for IPv6 addresses for the source-address address statement introduced in Junos OS Evolved
Release 23.1R1. | [
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250"
] |
inline-monitoring | inline-monitoring {
instance instance-name;
observation-cloud-id observation-cloud-identifier;
template template-name;
traceoptions;
} | [edit services] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "instance",
"desc": ""
},
{
"name": "instance-name",
"desc": "Configure parameters for an inline-monitoring instance. See \"instance\" on page 9149 for more information."
},
{
"name": "observation-cloud-id",
"desc": ""
},
{
"name": "observation-cloud-identifier",
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4R1.
observation-cloud-id option introduced in Junos OS Release 21.2R1.
Statement introduced in Junos OS Evolved Release 22.2R1. | [
"Inline Monitoring Services Configuration",
"Flow-Based Telemetry (EX4100, EX4100-F, and EX4400 Series)"
] |
inline-services (PIC level) | inline-services {
service-port;
bandwidth bandwidth;
} | [edit chassis fpc slot-number pic number] | Enable inline services on PICs residing on MPCs and optionally specify a bandwidth for traffic on the
inline service interface. Bandwidth values can be 1g, 10g, 20g, 30g, 40g, 50g, 60g, 70g, 80g, 90g, 100g,
200g, 300g, or 400g.
NOTE: For an MPC, such as MPC2, always configure inline-services at the [chassis fpc
slot-nu... | [] | 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 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. | [
"Enabling Inline Service Interfaces",
"Configuring an L2TP LNS with Inline Service Interfaces"
] |
inline-services | inline-services {
flex-flow-sizing;
flow-table-size {
bridge-flow-table-size bridge-flow-table-size;
ipv4-flow-table-size ipv4-flow-table-size;
ipv6-extended-attrib;
ipv6-flow-table-size ipv6-flow-table-size;
mpls-flow-table-size mpls-flow-table-size;
}
report-zero-oif-gw-on-discard;
use-... | [edit chassis fpc fpc-number] | (MX Series only) Enable inline services for FPCs.
Default
Disabled. | [] | flow-tap—To view this statement in the configuration.
flow-tap-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4R1. | [] |
inline-tap | inline-tap; | [edit security forwarding-process application-services maximize-idp-sessions] | Enable IDP inline tap mode. The inline tap feature provides passive, inline detection of application layer
threats for traffic matching security policies which have the IDP application service enabled. When a
device is in inline tap mode, packets pass through firewall inspection and are also copied to the
independent I... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Understanding Traffic Processing on Security Devices"
] |
inner-list | inner-list [vlan-id–vlan-id]; | [edit interfaces interface-name unit logical-unit-number] | List or a set of VLAN identifiers. inner-list is used in double-tagged interfaces and doesn't support Tag
Protocol Identifier (TPID) values such as 0x8100, 0x88a8, 0x9100, and 0x9200. You can configure a maximum of
32 unique ranges for VLAN IDs for each IFD and configure a maximum of 1024 VLAN ID lists at the
system l... | [
{
"name": "vlan-id-vlan-id",
"desc": "The first vlan-id is the lowest VLAN ID"
},
{
"name": "reserved for tagging the priority of",
"desc": "frames."
}
] | interface—To view this statement in the configuration. | Statement introduced in Junos OS Evolved Release 24.2R1-EVO for ACX Series Switches. | [
"vlan-id",
"tag-protocol-id TPID (TPIDs Expected to Be Sent or Received)",
"Configuring Dual VLAN Tags",
"Binding VLAN IDs to Logical Interfaces"
] |
inner-range | inner-range tpid.vlan-id–vlan-id; | [edit interfaces interface-name unit logical-unit-number] | Specify a TPID and a range of VLAN IDs. inner-range is used in double-tagged interfaces and supports
all Tag Protocol Identifier (TPID) values such as 0x8100, 0x88a8, 0x9100, and 0x9200. You can configure a
maximum of 32 unique ranges for VLAN IDs for each IFD and configure a maximum of 1024 VLAN ID
lists at the system... | [
{
"name": "tpid",
"desc": "The global tpid used for the tag."
},
{
"name": "vlan-id",
"desc": "The first vlan-id is the start of the range and the"
},
{
"name": "reserved for tagging the priority of",
"desc": "frames."
}
] | interface—To view this statement in the configuration. | Statement introduced in Junos OS Evolved Release 25.2R1-EVO for ACX. | [
"vlan-id",
"tag-protocol-id TPID (TPIDs Expected to Be Sent or Received)",
"Configuring Dual VLAN Tags",
"Binding VLAN IDs to Logical Interfaces"
] |
inner-tag-protocol-id (Dynamic VLANs) | inner-tag-protocol-id tpids; | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-numberinput-vlan-
map],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number output-vlan-
map] | For dynamic VLAN interfaces, configure the IEEE 802.1Q TPID value to rewrite for the inner tag. All
TPIDs you include in input and output VLAN maps must be among those you specify at the [edit
interfaces interface-name gigether-options ethernet-switch-profile tag-protocol-id tpids ] hierarchy level.
Default
If the inne... | [
{
"name": "tpids",
"desc": "TPIDs to be accepted on the VLAN. Specify TPIDs in hexadecimal format."
}
] | 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. | [
"Configuring Inner and Outer TPIDs and VLAN IDs"
] |
inner-tag-protocol-id | inner-tag-protocol-id tpid; | [edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interfa... | Configure the IEEE 802.1Q TPID value to rewrite for the inner tag.
All TPIDs you include in input and output VLAN maps must be among those you specify at the [edit
interfaces interface-name gigether-options ethernet-switch-profile tag-protocol-id [ tpids ]] hierarchy level.
On MX Series routers, you can use this statem... | [] | 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 Inner and Outer TPIDs and VLAN IDs"
] |
inner-vlan-id (Dynamic VLANs) | inner-vlan-id number; | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number input-vlan-
map],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number output-vlan-
map] | For dynamic VLAN interfaces, specify the VLAN ID to rewrite for the inner tag of the final packet.
You cannot include the inner-vlan-id statement with the swap statement, swap-push statement, push-push
statement, or push-swap statement and the inner-vlan-id statement at the [edit logical-systems logical-
system-name in... | [
{
"name": "number",
"desc": "VLAN ID number. When used for input VLAN maps, you can specify the $junos-inner-vlan-map-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.4. | [
"Configuring Inner and Outer TPIDs and VLAN IDs"
] |
inner-vlan-id | inner-vlan-id number; | [edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interfa... | For Gigabit Ethernet IQ, IQ2 and IQ2-E interfaces, and for aggregated Ethernet interfaces using Gigabit
Ethernet IQ2 and IQ2-E or 10-Gigabit Ethernet PICs on MX Series routers or 100-Gigabit Ethernet Type
5 PIC with CFP, or on Ethernet interfaces on EX Series switches, specify the VLAN ID to rewrite for the
inner tag o... | [
{
"name": "number",
"desc": "VLAN ID number."
}
] | 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 Inner and Outer TPIDs and VLAN IDs"
] |
inner-vlan-id-swap-ranges | inner-vlan-id-swap-ranges low-inner-tag–high-inner-tag; | [edit interfaces interface-name unit logical-unit-number] | Define core-facing VLAN ID ranges from which an inner VLAN ID tag can be allocated to replace the
outer VLAN tag that was appended by the access node on the upstream packets to the BNG in a Layer 2
wholesale network. The tag swap occurs before the subscriber traffic is forwarded to the network
service provider (NSP). Y... | [
{
"name": "low-inner-tag",
"desc": "Inner (core-facing) VLAN ID tag representing the lower limit of the swap range. Range: 1 through 4094."
},
{
"name": "high-inner-tag",
"desc": "Inner (core-facing) VLAN ID tag representing the upper limit of the swap range. Range: 1 through 4094."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1. | [
"Configuring Multiple Non-Overlapping VLAN Ranges for Core-Facing Physical Interfaces",
"Layer 2 Wholesale with ANCP-Triggered VLANs Overview"
] |
input (Analyzer) | input {
egress {
bridge-domain bridge-domain-name;
interface (all | interface-name);
routing-instance {
instance-name {
bridge-domain bridge-domain-name;
}
}
}
ingress {
bridge-domain bridge-domain-name;
interface (all... | [edit forwarding-options analyzer analyzer-name] | Define the traffic to be mirrored in a mirroring configuration—the definition can be a combination of:
•
Packets entering or exiting a port
•
Packets entering or exiting a VLAN
•
Packets entering or exiting a bridge domain
The remaining statements are explained separately. See CLI Explorer.
Native analyzer sessions (th... | [] | 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"
] |
input (Congestion Notification) | input {
(dscp | ieee-802.1) {
code-point [code-point-bits] {
pfc {
mru mru-value;
}
xon
}
}
cable-length cable-length-value;
} | [edit class-of-service congestion-notification-profile profile-name] | Configure priority-based flow control (PFC) on incoming traffic based on either IEEE 802.1p priorities in
the Layer 2 VLAN header or Differentiated Services code point (DSCP) values in the Layer 3 IP header.
You cannot configure both DSCP-based PFC and IEEE 802.1p PFC under the same congestion
notification profile. | [] | 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.
Support for DSCP values introduced in Junos OS Release 17.4R1. | [
"Example: Configuring CoS PFC for FCoE Traffic",
"Configuring CoS PFC (Congestion Notification Profiles)",
"Understanding CoS Flow Control (Ethernet PAUSE and PFC)",
"Understanding PFC Using DSCP at Layer 3 for Untagged Traffic",
"Configuring DSCP-based PFC for Layer 3 Untagged Traffic",
"Example: Configu... |
input (Dynamic Service Sets) | input {
service-set service-set-name {
service-filter filter-name;
}
post-service-filter filter-name;
} | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family service],
[edit dynamic-profiles profile-name interfaces pp0 unit $junos–interface–unit family family service] | Define the input service sets and filters to be applied to traffic by a dynamic profile.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Support at the [edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit” family family
service] hierarchy level introduced in Junos OS Release 10.1. | [
"Dynamic Service Sets Overview",
"Associating Service Sets with Interfaces in a Dynamic Profile"
] |
input (Fibre Channel Interfaces) | input {
ieee-802.1{
code-point code-point-bits;
}
} | [edit class-of-service interfaces fibre-channel-interface-name rewrite-value] | Configure the IEEE 802.1p code point value to which all traffic received from the Fibre Channel (FC)
network on the specified FC interface is rewritten. After the code point value is rewritten, the interface
forwards the traffic to the Ethernet (FCoE) network. This works in conjunction with configuring a fixed
classifi... | [] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"Example: Configuring IEEE 802.1p Priority Remapping on an FCoE-FC Gateway",
"Understanding CoS IEEE 802.1p Priority Remapping on an FCoE-FC Gateway",
"Understanding CoS Classifiers"
] | |
input (Forwarding Table) | input filter-name; | [edit forwarding-options family (inet | inet6 | mpls | vpls) filter],
[edit routing-instances routing-instance-name forwarding-options family (inet | inet6 | mpls |
vpls) filter] | Apply a forwarding table filter to ingress traffic of the forwarding table. | [
{
"name": "filter-name",
"desc": "Name of the applied filter."
}
] | 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. | [
"Applying Forwarding Table Filters"
] |
input (Interfaces) | input {
service-set service-set-name <service-filter filter-name>;
post-service-filter filter-name;
} | [edit interface interface-name unit logical-unit-number family inet service],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet service] | Define the input service sets and filters to be applied to traffic. | [] | 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. | [
"Applying Filters and Services to Interfaces"
] |
input (Port Mirroring) | input {
maximum-packet-length bytes;
rate number;
run-length number;
} | [edit forwarding-options port-mirroring],
[edit forwarding-options port-mirroring instance instance-name] | Configure input packet properties for port mirroring.
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.
maximum-packet-length option introduced in Junos OS Release 9.6 for M120 and M320 routers only. | [
"Configuring Port Mirroring"
] |
input (Routing Options RIB) | input filter-name; | [edit logical-systems logical-system-name routing-options rib routing-table-name filter],
[edit routing-options rib routing-table-name filter] | Specify the name of the input filter. | [
{
"name": "filter-name",
"desc": "Name of the input filter."
}
] | 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 Forwarding Table Filters",
"Applying Forwarding Table Filters"
] |
input (Sampling) | input {
max-packets-per-second number;
maximum-packet-length bytes;
rate number;
run-length number;
} | [edit forwarding-options sampling],
[edit forwarding-options sampling instance instance-name] | Configure traffic sampling on a logical 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.
Support for sampling of MPLS traffic introduced in Junos OS Release 8.3. | [
"Configuring Traffic Sampling on MX, M and T Series Routers"
] |
input | input {
ingress {
interface (all | interface-name);
vlan (vlan-id | vlan-name);
}
egress {
interface (all | interface-name);
}
} | For platforms without ELS:
[edit ethernet-switching-options analyzer name]
For platforms with ELS:
[edit forwarding-options analyzer name] | Define the traffic to be mirrored. The definition can be a combination of traffic entering or exiting
specific ports or VLANs.
The remaining statements are explained separately. See CLI Explorer.
Default
No default. | [] | 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"
] |
input-chain | input-chain [ filter-name ] | [edit interfaces interface-name unit logical-unit-number family family filter] | The input-chain command works like the next filter term to allow multiple levels of filtering on the
interface in both the ingress and egress direction. For example, you can implement a combination of
classification and firewall filter rules for evaluation, wherein the first filter performs a generic filter
classificat... | [
{
"name": "[ filter-names ]",
"desc": "Name of each filter in the chain that is to be evaluated when packets are received on"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R1.
Statement introduced in Junos OS Evolved Release 21.4R1 (PTX10001-36MR, PTX10004, PTX10008,
and PTX10016). | [
"Example: Using Firewall Filter Chains",
"Applying a Filter to an Interface"
] |
input-current (T4000 Routers) | input-current amps-in-each-feed; | [edit chassis pem] | Configure the amount of input current received in each feed. The value assigned to the input-current
statement must be equal to the input current capability of each feed.
NOTE: Before configuring input current for your router, see the T4000 Core Router
Hardware Guide for special considerations. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring the Six-Input DC Power Supply on T Series Routers"
] |
input-excess-bandwidth-share | input-excess-bandwidth-share (proportional value | equal); | [edit class-of-service interfaces interface-name],
[edit class-of-service interfaces interface-set interface-set-name] | Determines the method of sharing excess bandwidth on the ingress interface in a hierarchical scheduler
environment. If you do not include this statement, the node shares excess bandwidth proportionally at
32.64 Mbps. | [
{
"name": "proportional value",
"desc": "(Default) Share ingress excess bandwidth proportionally (default value is 32.64 Mbps)."
},
{
"name": "equal",
"desc": "Share ingress excess bandwidth equally."
}
] | 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. | [
"Configuring Ingress Hierarchical CoS on Enhanced Queuing DPCs"
] |
input-firewall-optimized-profile | input-firewall-optimized-profile | [edit chassis] | Optimize IFP DYN group (IFP dynamic group) by removing less frequently used qualifiers.
NOTE: This configuration statement should be used only when FIP snooping, Fibre
Channel over Ethernet (FCoE), and Inband Flow Analyzer (IFA) features are not used. On
EX4400, this configuration statement should be used only when FIP... | [] | interface-control | Statement introduced in Junos OS Release 22.2R1 | [] |
input-hierarchical-policer | input-hierarchical-policer policer-name; | [edit interfaces interface-name layer2-policer],
[edit interfaces interface-name unit logical-unit-number layer2-policer] | Apply a hierarchical policer to the Layer 2 input traffic for all protocol families at the physical or logical
interface. | [
{
"name": "policer-name",
"desc": "Name of the hierarchical policer."
}
] | 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. | [
"Hierarchical Policers",
"layer2-policer (Hierarchical Policer)"
] |
input-interface-index | input-interface-index number; | [edit forwarding-options monitoring name output interface interface-name] | Specify a value for the input interface index that overrides the default supplied by SNMP. | [
{
"name": "number",
"desc": "Input interface index value."
}
] | 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 Flow Monitoring"
] |
input-list | input-list [ filter-names ]; | [edit interfaces interface-name unit logical-unit-number family family filter],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family filter] | Apply a group of filters to evaluate when packets are received on an interface. | [
{
"name": "[ filter-names ]",
"desc": "Name of a filter to evaluate when packets are received on the interface. Up to 16 filters"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Applying a Filter to an Interface",
"Routing Policies, Firewall Filters, and Traffic Policers User Guide",
"Junos OS Administration Library for Routing Devices",
"output-list"
] |
input-native-vlan-push | input-native-vlan-push (disable | enable); | [edit interfaces interface-name] | On EX2300, EX3400, EX4300, EX4300-MP, EX4600, EX4650, and the QFX5000 line of switches
except QFX5220, QFX5130, QFX5230, QFX5240, and QFX5700, for a Q-in-Q tunneling configuration,
enable or disable whether the switch inserts a native VLAN identifier in untagged frames received on
the C-VLAN interface when the configur... | [
{
"name": "disable",
"desc": "Disable input-native-vlan-push."
},
{
"name": "enable",
"desc": "Enable input-native-vlan-push."
}
] | interface | Statement introduced in Junos OS Release 19.3R1 on EX Series and QFX Series switches. | [
"Configuring Q-in-Q Tunneling and VLAN Q-in-Q Tunneling and VLAN Translation"
] |
input-packet-rate-threshold | input-packet-rate-threshold rate; | [edit services dynamic-flow-capture capture-group client-name] | Specify a packet rate threshold value that triggers a system log warning message. | [
{
"name": "rate",
"desc": "Threshold value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring Thresholds"
] |
input-policer | input-policer policer-name; | [edit interfaces interface-name unit logical-unit-number layer2-policer]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
layer2-policer] | Apply a single-rate two-color policer to the Layer 2 input traffic at the logical interface. The input-policer
and input-three-color statements are mutually exclusive. | [
{
"name": "policer-name",
"desc": "Name of the single-rate two-color policer that you define at the [edit firewall] hierarchy"
}
] | 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. | [
"Two-Color and Three-Color Policers at Layer 2",
"Applying Layer 2 Policers to Gigabit Ethernet Interfaces",
"Configuring Gigabit Ethernet Policers"
] |
input-priority-map | input-priority-map {
ieee802.1p premium [ values ];
} | [edit interfaces interface-name gigether-options ethernet-switch-profile ethernet-policer-profile]
[edit interfaces interface-name ether-options ethernet-switch-profile ethernet-policer-profile] | For Gigabit Ethernet IQ and 10-Gigabit Ethernet interfaces only, define the input policer priority map to
be applied to incoming frames on this 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 Gigabit Ethernet Policers"
] |
input-scheduler-map | input-scheduler-map map-name; | [edit class-of-service interfaces interface-name],
[edit class-of-service interfaces interface-name unit logical-unit-number] | Associate a scheduler map with a physical or logical input interface. The input-scheduler-map and input-
traffic-control-profile statements are mutually exclusive at the same hierarchy level.
NOTE: On some devices, CoS queuing and scheduling are enabled on the egress side but
disabled on the ingress side by default. To... | [
{
"name": "map-name",
"desc": "Name of scheduler map that you define at the [edit class-of-service scheduler-maps] hierarchy"
},
{
"name": "default",
"desc": "The default scheduler mapping."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring an Input Scheduler on an Interface",
"Configuring Ingress Hierarchical CoS on Enhanced Queuing DPCs"
] |
input-shaping-rate (Logical Interface) | input-shaping-rate (percent percentage | rate); | [edit class-of-service interfaces interface-name unit logical-unit-number] | Configure input traffic shaping by specifying the amount of bandwidth to be allocated to the logical
interface. You can configure hierarchical shaping, meaning you can apply an input shaping rate to both
the physical interface and the logical interface.
Default
If you do not include this statement, logical interfaces ... | [
{
"name": "percent",
"desc": ""
},
{
"name": "percentage",
"desc": "Shaping rate as a percentage of the available interface bandwidth. Range: 0 through 100 percent"
},
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps). You can specify a value in bits per second either a... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring Ingress Hierarchical CoS on MIC and MPC Interfaces",
"Configuring Input Shaping Rates for Both Physical and Logical Interfaces",
"Configuring Ingress Hierarchical CoS on Enhanced Queuing DPCs"
] |
input-shaping-rate (Physical Interface) | input-shaping-rate rate; | [edit class-of-service interfaces interface-name] | Configure input traffic shaping by specifying the amount of bandwidth to be allocated to the physical
interface. You can configure hierarchical shaping, meaning you can apply an input shaping rate to both
the physical interface and the logical interface. | [
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps). You can specify a value in bits per second either as a complete decimal number or as a decimal number followed by the abbreviation k (1000), m (1,000,000), or g (1,000,000,000). Range: 1000 through 6,400,000,000,000 bps"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring Input Shaping Rates for Both Physical and Logical Interfaces",
"Configuring Ingress Hierarchical CoS on Enhanced Queuing DPCs"
] |
input-three-color | input-three-color policer-name; | [edit interfaces interface-name unit logical-unit-number layer2-policer]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
layer2-policer] | Apply a single-rate or two-rate three-color policer to the Layer 2 input traffic at the logical interface. The
input-three-color and input-policer statements are mutually exclusive. | [
{
"name": "policer-name",
"desc": "Name of the single-rate or two-rate three-color policer."
}
] | 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. | [
"Two-Color and Three-Color Policers at Layer 2",
"Applying Layer 2 Policers to Gigabit Ethernet Interfaces",
"Configuring Gigabit Ethernet Policers"
] |
input-traffic-control-profile | input-traffic-control-profile profile-name shared-instance instance-name; | [edit class-of-service interfaces interface-name],
[edit class-of-service interfaces interface-name unit logical-unit-number] | Apply an input traffic scheduling and shaping profile to the physical or logical interface. The input-traffic-
control-profile and input-scheduler-map statements are mutually exclusive at the same hierarchy level.
NOTE: The shared-instance statement applies only to Gigabit Ethernet IQ2 and IQ2E PICs.
NOTE: On many pla... | [
{
"name": "profile-name",
"desc": "Name of the traffic-control profile to be applied to this interface."
},
{
"name": "instance-name",
"desc": "Name of the shared scheduler and shaper to be applied to this interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring Traffic Control Profiles for Shared Scheduling and Shaping",
"Configuring Ingress Hierarchical CoS on Enhanced Queuing DPCs"
] |
input-traffic-control-profile-remaining | input-traffic-control-profile-remaining profile-name; | [edit class-of-service interfaces interface-name],
[edit class-of-service interfaces interface-name interface-set interface-set-name] | Apply an input traffic scheduling and shaping profile for the remaining traffic to the logical interface or
interface set. | [
{
"name": "profile-name",
"desc": "Name of the traffic-control profile for the remaining traffic to be applied to this interface or"
}
] | 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. | [
"Configuring Ingress Hierarchical CoS on Enhanced Queuing DPCs"
] |
input-vlan-map (Aggregated Ethernet) | input-vlan-map {
(pop | push | swap);
tag-protocol-id tpid;
vlan-id number;
} | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Define the rewrite profile to be applied to incoming frames on this logical interface. On MX Series
routers, this statement only applies to aggregated Ethernet inferfaces using Gigabit Ethernet IQ, 10-
Gigabit Ethernet IQ2 and IQ2-E interfaces and 100-Gigabit Ethernet Type 5 PIC with CFP.
The remaining statements are e... | [] | 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.
Starting in Junos OS Release 17.3R1, input-vlan-map for outer vlan is supported for L2 circuit over
aggregated Ethernet interfaces for QFX10000 Series switches. | [
"Stacking a VLAN Tag"
] |
input-vlan-map (Dynamic Interfaces) | input-vlan-map {
inner-tag-protocol-id tpid;
inner-vlan-id number;
(push | swap);
tag-protocol-id tpid;
vlan-id number;
} | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number] | For dynamic interfaces, define the rewrite profile to be applied to incoming frames on this logical
interface.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Stacking and Rewriting VLAN Tags for the Layer 2 Wholesale Solution"
] |
input-vlan-map | input-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
} | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | For Gigabit Ethernet IQ, 10-Gigabit Ethernet SFPP interfaces, 100-Gigabit Ethernet Type 5 PIC with CFP
only as well as Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit Ethernet, and aggregated Ethernet
interfaces, define the rewrite profile to be applied to incoming frames on this logical interface.
The remaining stat... | [] | 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.
pop-pop, pop-swap, push-push, swap-push, and swap-swap statements introduced in Junos OS Release 8.1. | [
"Stacking a VLAN Tag",
"Configuring Q-in-Q Tunneling on EX Series Switches with ELS Support"
] |
inputs (Analytics) | inputs {
analytics {
parameters {
generate-tags value;
sample-frequency value;
sensors path;
}
}
input-ipfix {
parameters {
maximum-connections number;
tcp-port port-number;
vrf-name name;
}
}
inp... | [edit services analytics agent service-agents agent-name] | Configure parameters for a Network Telemetry Framework (NTF) service agent input plug-in. For each
service agent instance, you can configure more than one input plug-in to push data to the output plug-
in.
NOTE: When you modify the input plug-in configuration of a service agent instance, the
associated service agent da... | [
{
"name": "analytics",
"desc": ""
},
{
"name": "parameters",
"desc": "Configure parameters to collect data from Junos Telemetry Interface (JTI) sensors."
},
{
"name": "generate-tags",
"desc": ""
},
{
"name": "value",
"desc": "(Optional) Enable tag generation. Default: En... | system | Statement introduced in Junos OS Release 18.3R1.
input-jti-ipfix option added in Junos OS Release 18.4R1 on MX Series routers.
analytics option added in Junos OS Release 18.4R1 on MX Series and PTX Series routers. | [
"Configuring the BNG as an IPFIX Mediator to Collect and Export IPFIX Data",
"Configuring the Collection and Export of Local Telemetry Data on the IPFIX Mediator",
"Configuring NTF Agent",
"IPFIX Mediation on the BNG",
"Telemetry Data Collection on the IPFIX Mediator for Export to an IPFIX Collector"
] |
insert | insert <statement-path> identifier1 (before | after) identifier2 | Insert an identifier in to an existing hierarchy. | [
{
"name": "statement-path",
"desc": "(Optional) Path to the existing identifier."
},
{
"name": "identifier1",
"desc": "The new identifier to insert."
},
{
"name": "after",
"desc": "Place identifier1 after identifier2."
},
{
"name": "before",
"desc": "Place identifier1 bef... | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy. | Command introduced before Junos OS Release 7.4. | [
"Inserting a New Identifier in a Device Configuration"
] | |
inspection-profile | inspection-profile name
{
vxlan name
{
policy-set policy-set;
vni vni-name;
}
} | [edit logical-systems name security tunnel-inspection],
[edit logical-systems name tenants name security tunnel-inspection],
[edit security tunnel-inspection],
[edit tenants name security tunnel-inspection] | Configure the tunnel-inspection profile. | [
{
"name": "name",
"desc": "Tunnel-inspection profile name"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [] |
install (Protocols MPLS) | install {
destination-prefix <active>;
} | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
ingress],
[edit protocols mpls label-switched-path lsp-name],
[edit protocols mpls static-label-switched-path lsp-name ingress]
[edit prot... | Associate one or more prefixes with an LSP. When the LSP is up, all the prefixes are installed as entries
into the inet.3 or inet6.3 routing table.
The support of the install statement at the [edit protocols source-packet-routing source-routing-path lsp-
name] is applicable for both colored and non-colored segment rout... | [
{
"name": "active",
"desc": "(Optional) Install the route into the inet.0 or inet6.0 routing table. This allows you to issue a ping or traceroute command on this address. NOTE: The install destination-prefix active statement is not supported on static LSPs. When the install destination-prefix active stateme... | 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 at the [edit protocols source-packet-routing source-routing-path lsp-name] hierarchy level introduced
in Junos OS Release 19.1R1. | [
"Adding LSP-Related Routes to the inet.3 or inet6.3 Routing Table"
] |
install (Routing Options) | (install | no-install); | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options static (defaults | route)],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name static (defaults | route)],
[edit logical-systems logical-system-name r... | Configure whether Junos OS installs all static routes into the forwarding table. Even if you configure a
route so it is not installed in the forwarding table, the route is still eligible to be exported from the
routing table to other protocols. | [
{
"name": "install",
"desc": "Explicitly install all static routes into the forwarding table. Include this statement when"
},
{
"name": "no-install",
"desc": "Do not install the route into the forwarding table, even if it is the route with the lowest"
}
] | 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. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.