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 |
|---|---|---|---|---|---|---|---|
ike | ike {
proposal proposal-name {
authentication-algorithm (sha1 | sha-256 | sha-384);
authentication-method (ecdsa-signatures-256 | ecdsa-signatures-384 | pre-shared-keys | rsa-
signatures);
description description;
dh-group (group1 | group2 | group5 |group14 | group15 | group16 | gro... | [edit services ipsec-vpn] | Configure IKE.
The remaining statements are explained separately.
NOTE: In Junos FIPS mode, the aggressive option of the "mode" on page 11246 statement
is not supported.
NOTE: In Junos FIPS mode, ECDSA options of the authentication-method statement are not
supported in Junos OS Release 17.3R1. Starting in Junos OS Rele... | [] | 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. | [
"Configuring IKE Proposals",
"Configuring IKE Policies"
] |
ike-access-profile | ike-access-profile profile-name; | [edit services service-set service-set-name ipsec-vpn-options] | Define the access profile for the IPsec traffic on dynamic tunnels. | [
{
"name": "profile-name",
"desc": "Identifier for access profile, which must match the name configured at the [edit access"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring Dynamic Endpoints for IPsec Tunnels",
"Configuring IPsec Service Sets"
] |
ike-esp-nat | ike-esp-nat {
enable;
esp-gate-timeout seconds;
esp-session-timeout seconds;
state-timeout seconds;
traceoptions {
flag {
all {
extensive
}
}
}
} | [edit logical-systems name security alg],
[edit logical-systems name tenants name security alg],
[edit security alg],
[edit services alg],
[edit tenants name security alg] | 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": "Enable",
"desc": "Enable the IKE-ESP ALG."
},
{
"name": "esp-gate-timeout seconds",
"desc": "Set the timeout for the ESP gates created after an IKE Phase 2 exchange has"
},
{
"name": "esp-session-timeout seconds",
"desc": "Set the idle timeout for the ESP sessions created ... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5.
Statement supported at hierarchy [edit logical-systems name tenants name security alg tenant] in Junos OS
Release 18.3R1. | [
"Understanding the IKE and ESP ALG"
] |
ike-log | ike-log {
filename filename;
level level;
} | [edit security host-vpn] | Configure IKE logging details. | [
{
"name": "filename",
"desc": ""
},
{
"name": "filename",
"desc": ""
},
{
"name": "Specify the filename for logging",
"desc": "for example, /var/log/filename.log."
},
{
"name": "level level",
"desc": "Specify the logging level (how much detail is included) of the IKE daem... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 18.3R1. | [] |
ike-phase1-failures | ike-phase1-failures {
threshold value;
} | [edit security alarms potential-violation] | Raise a security alarm after exceeding a specified number of Internet Key Exchange (IKE) Phase 1
failures.
Default
Multiple IKE phase 1 failures do not cause an alarm to be raised. | [
{
"name": "failures",
"desc": "Number of IKE phase 1 failures up to which an alarm is not raised. When the configured"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"IPsec Overview",
"Monitoring VPN Traffic"
] |
ike-phase2-failures | ike-phase2-failures {
threshold value;
} | [edit security alarms potential-violation] | Raise a security alarm after exceeding a specified number of Internet Key Exchange (IKE) phase 2
failures.
Default
Multiple IKE phase 2 failures do not cause an alarm to be raised. | [
{
"name": "failures",
"desc": "Number of IKE phase 2 failures up to which an alarm is not raised. When the configured"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"IPsec Overview",
"Monitoring VPN Traffic"
] |
ike-secrets | ike-secrets {
ike-secret {
id id;
secret (ascii-text ascii-text | hexadecimal hexadecimal);
}
} | [edit security host-vpn] | Configure IKE shared secret details. If the shared secret passed between devices does not match, a
session is not set up.
NOTE: To configure a host-to-host VPN connection, you must configure the ike-secrets
statement. | [
{
"name": "ike-secret",
"desc": "Specify the name of the IKE secret."
},
{
"name": "id id",
"desc": ""
},
{
"name": "Specify the identity that the secret belongs to",
"desc": "for example, an IP address, a"
},
{
"name": "secret (ascii-text",
"desc": ""
},
{
"name"... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 18.3R1. | [] |
ila-options | ila-options {
edfa-a-b (tca-input-power-high | tca-input-power-low | tca-output-power-high | tca-output-power-
low | tca-pump0-current-high | tca-pump0-current-low | tca-pump0-temperature-high | tca-pump0-
temperature-low | tca-pump1-current-high | tca-pump1-current-low | tca-pump1-temperature-high |
tca-pump1-tempera... | [edit chassis fpc fpc-slot optical-options amplifier-chain ila ila-number] | tca-attenuation-high
Attenuation high TCA
tca-attenuation-low
Attenuation low TCA | [
{
"name": "ila-ipv4-address",
"desc": ""
},
{
"name": "ila-ipv4-address",
"desc": "Specify the IPv4 address of the optical ILA in the format: w.x.y.z/a. To enable OSC communication to and from the specified optical ILA, you must configure the IP address of the optical ILA. TIP: All communication... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1R1. | [
"Understanding Optical Supervisory Channel Communication in the Amplifier Chain",
"Configuring the Optical Supervisory Channel Across the Amplifier Chain of the PTX3000 Integrated",
"Photonic Line System",
"Configuring the IP Address of an Optical Inline Amplifier",
"Enabling and Configuring Thresholds on t... |
image | image {
file-path;
bus-type [ide | virtio];
driver-cache {
default-cache;
directsync;
none;
unsafe;
writeback;
writethrough;
}
image-type [qcow2 | raw];
} | [edit virtual-network-functions] | Specify the VNF image source file. VNF image is virtual hard disk, which contains the bootable file-
system for the VNF. | [
{
"name": "file-path",
"desc": "Path of the image source file"
},
{
"name": "image-type",
"desc": "Format of the image. Default value is qcow2."
},
{
"name": "bus-type",
"desc": "Type of the system bus. Default value is virtio."
},
{
"name": "driver-cache",
"desc": "Type ... | 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"
] |
imap-profile (Security Content Security Policy Antivirus) | imap-profile profile-name; | [edit security utm default-configuration]
[edit security utm utm-policy policy-name anti-virus] | Configure a Content Security policy for the antivirus IMAP protocol and attach this policy to a security
profile to implement it. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
imap-profile (Security Content Security Policy Content Filtering) | imap-profile profile-name; | [edit security utm default-configuration]
[edit security utm utm-policy policy-name content-filtering] | Configure a Content Security policy for the content-filtering IMAP protocol and attach this policy to a
security profile to implement it. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Content Filtering Overview"
] |
immediate-accounting-response | immediate-accounting-response (enabled | disabled); | [edit unified-edge gateways tdf gateway-name domains domain-name ip-subscriber] | Enable or disable the sending of an immediate RADIUS response message to the accounting start
message received from a GGSN, PGW, or BNG RADIUS client.
Default
If you do not specify an option, disabled is the default. | [
{
"name": "enabled",
"desc": "Enable immediate response."
},
{
"name": "disabled",
"desc": "Disable immediate response. The response is sent after TDF subscriber creation is complete."
}
] | 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",
"Understanding the Definition of a Set of IP-Based Subscriber Properties with a TDF Domain",
"IP-Based Subscriber Setup Overview"
] |
immediate-leave (Dynamic IGMP Interface) | immediate-leave; | [edit dynamic-profiles profile-name protocols igmp interface interface-name] | Enable the routing device to leave the multicast group immediately after the last host leaves the
multicast group. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Dynamic IGMP Configuration Overview",
"Configuring Dynamic DHCP Client Access to a Multicast Network",
"Specifying Immediate-Leave Host Removal for IGMP"
] |
immediate-leave (Dynamic MLD Interface) | immediate-leave; | [edit dynamic-profiles profile-name protocols mld interface interface-name] | The immediate leave setting is useful for minimizing the leave latency of MLD memberships. When this
setting is enabled, the routing device leaves the multicast group immediately after the last host leaves
the multicast group.
The immediate-leave setting enables host tracking, meaning that the device keeps track of 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. | [
"Dynamic MLD Configuration Overview",
"Specifying Immediate-Leave Host Removal for MLD"
] |
immediate-leave | immediate-leave; | [edit logical-systems logical-system-name protocols igmp interface interface-name],
[edit protocols igmp interface interface-name],
[edit bridge-domains bridge-domain-name protocols igmp-snooping],
[edit bridge-domains bridge-domain-name protocols igmp-snooping interface interface-name],
[edit bridge-domains bridge-dom... | Enable host tracking to allow the device to track the hosts that send membership reports, determine
when the last host sends a leave message for the multicast group, and immediately stop forwarding
traffic for the multicast group after the last host leaves the group. This setting helps to minimize IGMP
or MLD membershi... | [] | 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. | [
"Specifying Immediate-Leave Host Removal for IGMP",
"Configuring IGMP Snooping on Switches",
"Example: Configuring IGMP Snooping on Switches",
"Example: Configuring IGMP Snooping on SRX Series Devices",
"IGMP Snooping Overview",
"Specifying Immediate-Leave Host Removal for MLD",
"Understanding MLD Snoop... |
immediate-leave-on-host-interface (IGMP Snooping) | immediate-leave-on-host-interface; | [edit protocols igmp-snooping vlan vlan-name],
[edit routing-instances routing-instance-name protocols igmp-snooping vlan vlan-name],
[edit routing-instances routing-instance-name bridge-domains bd-name protocols igmp-snooping],
[edit bridge-domains bd-name protocols igmp-snooping] | Enable automatic immediate-leave on all host links without receiving IGMP leave reports. This can be
configured on a vlan or bridge-domains level.
Default
This configuration is disabled by default. | [] | Statement introduced in Junos OS Release 25.2R1. | [
"No Link Title"
] | |
immediate-leave-on-host-interface (MLD Snooping) | immediate-leave-on-host-interface; | [edit protocols mld-snooping vlan vlan-name],
[edit routing-instances routing-instance-name protocols mld-snooping vlan vlan-name],
[edit routing-instances routing-instance-name bridge-domains bd-name protocols mld-snooping],
[edit bridge-domains bd-name protocols mld-snooping] | Enable automatic immediate leave on all host links without receiving MLD leave reports. This can be
configured on a vlan or bridge-domains level.
Default
This configuration is disabled by default. | [] | Statement introduced in Junos OS Release 25.2R1. | [
"No Link Title"
] | |
immediate-update | immediate-update; | [edit access profile profile-name accounting] | Configure the router or switch to send an Acct-Update message to the RADIUS accounting server on
receipt of a response (for example, an ACK or timeout) to the Acct-Start message. | [] | 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. | [
"RADIUS Servers and Parameters for Subscriber Access",
"RADIUS Accounting for Subscriber Access"
] |
import (BGP) | import [ policy-names ]; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Apply one or more routing policies to routes being imported into the Junos OS routing table from BGP.
If you specify more than one policy, they are evaluated in the order specified, from left to right, and the
first matching filter is applied to the route. If no match is found, BGP places into the routing table only
th... | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring BGP Interactions with IGPs",
"Configuring Routing Policies to Control BGP Route Advertisements",
"Understanding Routing Policies"
] |
import (Classifiers) | import (classifier-name | default); | [edit class-of-service classifiers type classifier-name] | Specify a default or previously defined classifier. | [
{
"name": "classifier-name",
"desc": "Name of the classifier mapping configured at the [edit class-of-service classifiers]"
},
{
"name": "default",
"desc": "The default classifier mapping."
}
] | 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"
] |
import (CoS) | import (import | default); | [edit class-of-service classifiers (dscp | dscp-ipv6 | ieee-802.1 | exp) classifier-name],
[edit class-of-service rewrite-rules (dscp | dscp-ipv6 | ieee-802.1 | exp) classifier-name] | Specify a default or previously defined classifier. | [
{
"name": "import",
"desc": "Name of the classifier mapping configured at the [edit class-of-service classifiers] hierarchy"
},
{
"name": "default",
"desc": "Default classifier mapping."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Example: Configuring Unicast Classifiers",
"Defining CoS BA Classifiers (DSCP, DSCP IPv6, IEEE 802.1p)",
"Defining CoS Rewrite Rules",
"Understanding CoS Classifiers",
"Understanding CoS Classifiers",
"Understanding CoS Classifiers",
"Understanding CoS Rewrite Rules",
"Example: Configuring CoS on EX ... |
import (MPLS Traffic Engineering Database) | import {
bgp-ls-identifier domain-identifier;
identifier identifier;
ipv6;
l3-unicast-topology {
bgp-link-state;
}
policy policy-name;
igp-topology{
bgp-link-state;
} | [edit logical-systems logical-system-name protocols mpls traffic-engineering database],
[edit protocols mpls traffic-engineering database] | Configure the traffic engineering database import parameters. | [
{
"name": "bgp-ls-identifier",
"desc": ""
},
{
"name": "domain-identifier",
"desc": "BGP-TE domain identifier."
},
{
"name": "identifier",
"desc": ""
},
{
"name": "identifier",
"desc": "BGP-TE identifier. Range: 2 through 18446744073709551615"
},
{
"name": "ipv6"... | 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.
ipv6 option introduced in Junos OS Release 20.4R1. | [] |
import (Protocols DVMRP) | import [ policy-names ]; | [edit logical-systems logical-system-name protocols dvmrp],
[edit protocols dvmrp] | Apply one or more policies to routes being imported into the routing table from DVMRP. If you specify
more than one policy, they are evaluated in the order specified, from first to last, and the first matching
policy is applied to the route. If no match is found, DVMRP shares with the routing table only those
routes th... | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | NOTE: Distance Vector Multicast Routing Protocol (DVMRP) was deprecated in Junos
OS Release 16.1. Although DVMRP commands continue to be available and configurable
in the CLI, they are no longer visible and are scheduled for removal in a subsequent
release.
Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring DVMRP to Announce Unicast Routes"
] |
import (Protocols IS-IS) | import [ policy-names ]; | [edit logical-systems logical-system-name protocols isis],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
isis],
[edit protocols isis],
[edit routing-instances routing-instance-name protocols isis] | Apply one or more routing policies to routes being imported into the Junos OS routing table from IS-IS.
You can import a routing policy to filter or restrict routes. | [
{
"name": "policy-names",
"desc": "Name of one or more routing policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Example: Configuring a Routing Policy to Prioritize IS-IS Routes",
"Understanding Routing Policies"
] |
import (Protocols LDP) | import [ policy-names ]; | [edit logical-systems logical-system-name protocols ldp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp],
[edit protocols ldp],
[edit routing-instances routing-instance-name protocols ldp] | Apply policy filters to received LDP label bindings. Filters are applied to all label bindings from all
neighbors. | [
{
"name": "policy-names",
"desc": "Name of one or more routing policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Filtering Inbound LDP Label Bindings"
] |
import (Protocols MSDP) | import [ policy-names ]; | [edit logical-systems logical-system-name protocols msdp],
[edit logical-systems logical-system-name protocols msdp group group-name],
[edit logical-systems logical-system-name protocols msdp group group-name peer address],
[edit logical-systems logical-system-name protocols msdp peer address],
[edit logical-systems lo... | Apply one or more policies to routes being imported into the routing table from MSDP. | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring MSDP in a Routing Instance"
] |
import (Protocols OSPF) | import [ policy-names ]; | [edit logical-systems logical-system-name protocols (ospf | ospf3)],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(ospf | ospf3)],
[edit logical-systems log... | Filter OSPF routes from being added to the routing table. | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for the realm statement introduced in Junos OS Release 9.2.
Support for the realm statement introduced in Junos OS Release 9.2 for EX Series switches. | [
"Understanding OSPF Routing Policy",
"Import and Export Policies for Network Summaries Overview"
] |
import (Protocols PIM Bootstrap) | import [ policy-names ]; | [edit logical-systems logical-system-name protocols pim rp bootstrap (inet | inet6)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp bootstrap (inet | inet6)],
[edit protocols pim rp bootstrap (inet | inet6)],
[edit routing-instances routing-instance-name protocols p... | Apply one or more import policies to control incoming PIM bootstrap messages. | [
{
"name": "policy-names",
"desc": "Name of one or more import policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring PIM Bootstrap Properties for IPv4",
"Configuring PIM Bootstrap Properties for IPv4 or IPv6"
] |
import (Protocols PIM) | import [ policy-names ]; | [edit logical-systems logical-system-name protocols pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit protocols pim],
[edit routing-instances routing-instance-name protocols pim] | Apply one or more policies to routes being imported into the routing table from PIM. Use the import
statement to filter PIM join messages and prevent them from entering the network. | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Filtering Incoming PIM Join Messages"
] |
import (Protocols RIP) | import [ policy-names ]; | [edit logical-systems logical-system-name protocols rip],
[edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip],
[edit logical-systems logical-system-name routing-instances routin... | Apply one or more policies to routes being imported by the local routing device from neighbors. | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Applying Policies to RIP Routes Imported from Neighbors",
"Junos OS Routing Policies, Firewall Filters, and Traffic Policers User Guide for Routing Devices"
] |
import (Protocols RIPng) | import [ policy-names ]; | [edit logical-systems logical-system-name protocols ripng],
[edit logical-systems logical-system-name protocols ripng group group-name neighbor neighbor-
name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ripng],
[edit logical-systems logical-system-name routing-instanc... | Apply one or more policies to routes being imported into the local routing device from its neighbors. | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for routing instances introduced in Junos OS Release 9.0. | [
"Example: Applying Policies to RIPng Routes Imported from Neighbors"
] |
import (Rewrite Rules) | import (rewrite-name | default); | [edit class-of-service rewrite-rules type rewrite-name] | Specify a default or previously defined rewrite-rules mapping to import. | [
{
"name": "rewrite-name",
"desc": "Name of a rewrite-rules mapping configured at the [edit class-of-service rewrite-rules]"
},
{
"name": "default",
"desc": "The default rewrite-rules mapping."
}
] | 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"
] |
import (Routing Options) | import [ policy-names ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options resolution rib],
[edit logical-systems logical-system-name routing-options resolution rib],
[edit routing-instances routing-instance-name routing-options resolution rib],
[edit routing-options resolution rib] | Specify one or more import policies to use for route resolution. | [
{
"name": "policy-names",
"desc": "Name of one or more import policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring Route Resolution on PE Routers"
] |
import-labeled-routes (Routing Instances VPLS) | import-labeled-routes [ routing-instance-name ] | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls],
[edit routing-instances routing-instance-name protocols vpls ] | (MX Series routers with MPCs and MIC interfaces only) Specify one or more routing instances where
MPLS paths (pseudowire labeled routes) are leaked from the mpls.0 routing table in the primary routing
instance to the local routing-instance-name.mpls.0 routing table.
This capability is useful in an L2VPN/VPLS configurat... | [
{
"name": "routing-instance-name",
"desc": "Name of a nondefault routing instance where you want routes leaked from the primary MPLS routing table."
}
] | 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 VPLS Routing Instances"
] |
import-policy | import-policy [ policy-names ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib-groups group-name],
[edit logical-systems logical-system-name routing-options rib-groups group-name],
[edit routing-instances routing-instance-name routing-options rib-groups group-name],
[edit routing-options rib-gro... | Apply one or more policies to routes imported into the routing table group. The import-policy statement
complements the import-rib statement and cannot be used unless you first specify the routing tables to
which routes are being imported.
NOTE: On EX Series switches, only dynamically learned routes can be imported fr... | [
{
"name": "policy-names",
"desc": "Name of one or more policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Exporting Specific Routes from One Routing Table Into Another Routing Table"
] |
import-rib | import-rib [ routing-table-names ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib-groups group-name],
[edit logical-systems logical-system-name routing-options rib-groups group-name],
[edit routing-instances routing-instance-name routing-options rib-groups group-name],
[edit routing-options rib-gro... | Specify the name of the routing table into which Junos OS should import routing information. The first
routing table name you enter is the primary routing table. Any additional names you enter identify
secondary routing tables. When a protocol imports routes, it imports them into the primary and any
secondary routing t... | [
{
"name": "routing-table-names",
"desc": "Name of one or more routing tables."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Exporting Specific Routes from One Routing Table Into Another Routing Table"
] |
import-target | import-target {
target {
target-value;
receiver target-value;
sender target-value;
}
unicast {
receiver;
sender;
}
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols mvpn
route-target],
[edit routing-instances routing-instance-name protocols mvpn route-target] | Enable you to override the Layer 3 VPN import and export route targets used for importing and
exporting routes for the MBGP MVPN NLRI. | [] | 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. | [] |
imsi-prefix | imsi-prefix imsi-prefix-digits {
action (APN GTP) {
drop;
pass;
selection (ms|net|vrf);
}
} | [edit security gtp profile profile-name apn pattern-string] | Use the imsi-prefix option to specify an International Mobile Station Identity (IMSI) prefix for filtering
GTP packets. You can also filter GTP packets based on the combination of an IMSI prefix and an access
point name (APN).
From Junos OS Release 20.4R1 onwards, the [edit security gprs gtp profile profile-name apn pa... | [
{
"name": "imsi-prefix-digits",
"desc": "To specify an IMSI prefix."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. Support. | [
"Understanding GTP APN Filtering",
"Understanding GTPv2 IMSI Prefix and APN Filtering",
"Example: Setting a GTP APN and a Selection Mode"
] |
in-place-lsp-bandwidth-update (Protocols MPLS) | in-place-lsp-bandwidth-update; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name] | Enable the ingress label edge routers (LER) to re-use the LSP-ID when performing bandwidth change on
an intra-domain LSP. The LSP-ID re-use mechanism described in this document will not be applicable for
inter-domain LSPs.
NOTE: commit fails if you have configured either of the following:
•
"no-cspf" on page 11904 at t... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [
"Configuring Optimized Auto-bandwidth Adjustments for MPLS LSPs"
] |
in-service | in-service; | [edit services monitoring rfc2544 tests test-name test-name] | Runs the test in the in-service mode. In this mode, while the test is running, the rest of the data traffic
sent to and from the UNI port under test on the service are not interrupted. Control protocol packets
and control protocol peering are not interrupted.
If this mode is not configured, the test runs in the default... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X53.
Statement introduced in Junos OS Evolved Release 22.4R1. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers",
"Configuring an RFC 2544-Based Benchmarking Test"
] |
inactive-media-timeout (Security MGCP) | inactive-media-timeout value-in-seconds; | [edit logical-systems name security alg mgcp],
[edit logical-systems name tenants name security alg mgcp],
[edit security alg mgcp],
[edit services alg mgcp],
[edit tenants name security alg mgcp] | Configure inactive-media-timeout parameter to specify the maximum amount of time that the
temporary openings in the firewall (pinholes) remain open for media if no activity is detected. | [
{
"name": "value-in-seconds",
"desc": "Maximum amount of time that the pinholes remain open."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
inactive-media-timeout (Security SCCP) | inactive-media-timeout value-in-seconds; | [edit logical-systems name security alg sccp],
[edit logical-systems name tenants name security alg sccp],
[edit security alg sccp],
[edit services alg sccp],
[edit tenants name security alg sccp] | Configure inactive-media-timeout parameter to specify the maximum amount of time that the
temporary openings in the firewall (pinholes) remain open for media if no activity is detected. | [
{
"name": "value-in-seconds",
"desc": "Maximum amount of time that the pinholes remain open."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
inactive-media-timeout (Security SIP) | inactive-media-timeout value-in-seconds; | [edit logical-systems name security alg sip (Security)],
[edit logical-systems name tenants name security alg sip (Security)],
[edit security alg sip (Security)],
[edit services alg sip (Security)],
[edit tenants name security alg sip (Security)] | Configure inactive-media-timeout parameter to specify the maximum amount of time that the
temporary openings in the firewall (pinholes) remain open for media if no activity is detected. | [
{
"name": "value-in-seconds",
"desc": "Maximum amount of time that the pinholes remain open."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
inactivity-asymm-tcp-timeout (Service Set Next Gen Services) | inactivity-asymm-tcp-timeout seconds; | [edit services service-set service-set-name service-set-options tcp-session] | Configure the number of seconds that a unidirectional TCP session can be inactive before it is closed.
Valid settings: 4 through 86400 seconds. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [] |
inactivity-interval (Fabric Load Balance) | inactivity-interval interval; | [edit forwarding-options enhanced-hash-key fabric-load-balance flowlet] | Set the inactivity interval for adaptive load balancing (ALB) using flowlets within a VCF.
NOTE: Starting in Junos OS Release 14.1X53-D46, 15.1R7, 16.1R6, 17.1R3, 17.2R2,
17.3R2, and 17.4R1, the ALB feature is deprecated. If fabric-load-balance is enabled in the
configuration and inactivity-interval is set, delete thes... | [
{
"name": "interval",
"desc": "The amount of time that occurs between packet bursts on a sending interface before a traffic flow is spliced into flowets. Range: 16 microseconds (16us) to 32 milliseconds(32ms)."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10.
Statement deprecated starting in Junos OS Releases 14.1X53-D46, 15.1R7, 16.1R6, 17.1R3, 17.2R2,
17.3R2, and 17.4R1. | [
"Understanding Traffic Flow Through a Virtual Chassis Fabric"
] |
inactivity-non-tcp-timeout | inactivity-non-tcp-timeout seconds; | [edit interfaces interface-name services-options] | Define the inactivity timeout period for non-TCP established sessions in seconds. | [
{
"name": "seconds",
"desc": "Timeout period."
}
] | 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. | [
"Defining an Application Identification"
] |
inactivity-probe-duration | inactivity-probe-duration milliseconds; | [edit protocols ovsdb controller] | Configure the maximum amount of time, in milliseconds, that the connection between a Juniper
Networks device that supports the Open vSwitch Database (OVSDB) management protocol and a
software-defined networking (SDN) controller can be inactive before an inactivity probe is sent. | [
{
"name": "milliseconds",
"desc": "Number of milliseconds that the connection can be inactive before an inactivity probe is"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1R2. | [
"Understanding How to Set Up OVSDB Connections on a Juniper Networks Device"
] |
inactivity-tcp-timeout | inactivity-tcp-timeout seconds; | [edit interfaces interface-name services-options] | Define the inactivity timeout period for TCP established sessions in seconds. | [
{
"name": "seconds",
"desc": "Timeout period."
}
] | 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. | [
"Defining an Application Identification"
] |
inactivity-timeout (Applications) | inactivity-timeout (seconds | never) ; | [edit applications application application-name ]
[edit applications application application-name term term-name] | Application-specific inactivity timeout period, in seconds. | [
{
"name": "seconds",
"desc": "Specify the amount of time the application is inactive before it times out in seconds."
},
{
"name": "never",
"desc": "Disables the inactivity-timeout period. If you do not want an application to time out, use the never"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement modified in Junos OS Release 8.5. | [
"Security Policy Application Sets Overview"
] |
inactivity-timeout (Security Persistent NAT) | inactivity-timeout seconds; | [edit security nat source rule-set ruleset rule rule then source-nat interface persistent-nat]
[edit security nat source rule-set ruleset rule rule then source-nat pool persistent-nat] | The amount of time, in seconds, that the persistent NAT binding remains in the Juniper Networks
device’s memory when all the sessions of the binding entry are gone. When the configured timeout is
reached, the binding is removed from memory. | [
{
"name": "seconds",
"desc": "Number of seconds."
}
] | 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. | [] |
inactivity-timeout (Services RPM) | inactivity-timeout seconds; | [edit services rpm twamp server] | Inactivity timeout period, in seconds. | [
{
"name": "seconds",
"desc": "Length of time the session is inactive before it times out."
}
] | system—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Configuring TWAMP on MX, M, T, and PTX Series Routers and EX4300 Series Switches"
] |
inactivity-timeout (services) | inactivity-timeout seconds; | [edit interfaces interface-name services-options]
[edit services service-set-name service-set-options] | Configure the inactivity timeout period for established flows. The timeout value configured in the
application protocol definition overrides this value. | [
{
"name": "seconds",
"desc": "Timeout period."
}
] | 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 added in Junos OS Release 19.3R2 for MX-SPC3 services card on MX240, MX480 and MX960
routers. | [
"Configuring Default Timeout Settings for Services Interfaces"
] |
inactivity-timeout | inactivity-timeout ( seconds | never ); | [edit applications application application-name] | Configure the inactivity timeout period, in seconds. | [
{
"name": "seconds",
"desc": "Length of time the application is inactive before it times out."
},
{
"name": "never",
"desc": "Disables the inactivity-timeout period. Use this option if you do not want an application to time"
}
] | 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. | [
"ALG Descriptions",
"Configuring Application Sets",
"Configuring the Inactivity Timeout Period",
"Examples: Configuring Application Protocols",
"Verifying the Output of ALG Sessions"
] |
inband-flow-telemetry | inband-flow-telemetry {
clock-source (ntp | ptp);
device-id {
(id-number | auto);
}
flow-type (l3 | vxlan);
hop-limit value;
meta-data-stack-length value;
mode (live | probe);
no-ipv6-address-match;
profile {
ifa-profile-name {
sample-rate value;
collector {
... | [edit services] | Configure Inband Flow Analyzer 2.0 (IFA 2.0). IFA 2.0 provides insights about complex networks by
collecting per-hop flow data on the data plane. IFA uses probe packets to collect network-wide flow
data. IFA generates probe packets by sampling the traffic flow of interest. IFA probe packets are
representative packets o... | [
{
"name": "clock-source",
"desc": ""
},
{
"name": "(ntp |",
"desc": ""
},
{
"name": "ptp)",
"desc": "Configure the clock source protocol to enable more accurate timestamping. The QFX5120-48YM switch supports PTP as well as NTP; all of the other QFX5120 switch models support NTP only.... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.4R1.
clock-source, maximum-clip-length, mtu, and no-ipv6-address-match options introduced in Junos OS Release
22.2R1.
Statement introduced in Junos OS Evolved Release 22.4R1.
mode option introduced in Junos OS Evolved Release 25.4R1. | [
"Inband Flow Analyzer (IFA) 2.0 Probe for Real-Time Performance Monitoring"
] |
inband-ztp | inband-ztp {
management-vlan-id management-vlan-id;
name-server [ name-server ... ];
}
} | [edit system services] | Enable in-band ZTP.
In-band ZTP enables your already-provisioned Day 1 upstream devices in your IP fabric to monitor for
newly connected Day 0 downstream devices. In-band ZTP invokes an autonomous Python daemon,
which uses Link-Level Discovery Protocol (LLDP) telemetry data, to monitor for any new downstream
interfaces... | [
{
"name": "management-vlan-id",
"desc": "Provide the management VLAN ID. The management VLAN enables in-band ZTP for a particular VLAN. An upstream device can belong to multiple VLANs, and the management VLAN enables in-band ZTP to monitor for interfaces in those VLANs."
},
{
"name": "name-server",
... | None. | Statement introduced in Junos OS Release 24.2R1 | [
"In-band Zero Touch Provisioning"
] |
include (Diameter Gx Profiles) | include {
gx-capability-list;
rule-suggestion;
} | [edit unified-edge diameter-profiles gx-profile profile-name attributes] | Configure the attribute-value pairs (AVPs) to be included in the credit control request (CCR) messages
between the MX Series router and the policy and charging enforcement function (PCEF). | [
{
"name": "gx-capability-list",
"desc": "Include the Gx-Capability list AVP."
},
{
"name": "rule-suggestion",
"desc": "Include the Rule-suggestion AVP."
}
] | 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. | [] |
include-all (for Administrative Groups) | include-all [ group-names ]; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name admin-
group],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name (primary |
secondary) path-name admin-group],
[edit protocols mpls label-switched-path lsp-name admin-group],
[edit protocols mpls l... | Require the LSP to traverse links that include all of the defined administrative groups. | [
{
"name": "group-names",
"desc": "One or more names of groups defined with the admin-groups statement."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Administrative Groups for LSPs"
] |
include-all (for Fast Reroute) | (include-all [ group-names ] | no-include-all); | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name fast-
reroute],
[edit protocols mpls label-switched-path lsp-name fast-reroute] | Control inclusion of administrative groups:
•
include-all—Define the administrative groups that must all be included for fast reroute.
•
no-include-all—Disable administrative group inclusion. | [
{
"name": "group-names",
"desc": "One or more names of groups defined with the admin-groups statement."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Fast Reroute"
] |
include-any (for Administrative Groups) | include-any [ group-names ]; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name admin-
group],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name (primary |
secondary) path-name admin-group],
[edit protocols mpls label-switched-path lsp-name admin-group],
[edit protocols mpls l... | Define the administrative groups to include for an LSP or for a path’s primary and secondary paths. | [
{
"name": "group-names",
"desc": "One or more names of groups defined with the admin-groups statement."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Administrative Groups for LSPs"
] |
include-any (for Fast Reroute) | (include-any [ group-names ] | no-include-any); | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name fast-
reroute],
[edit protocols mpls label-switched-path lsp-name fast-reroute] | Control inclusion of administrative groups:
•
include-any—Define the administrative groups to include for fast reroute.
•
no-include-any—Disable administrative group inclusion. | [
{
"name": "group-names",
"desc": "One or more names of groups defined with the admin-groups statement."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Fast Reroute"
] |
include-igp-metric | include-igp-metric; | [edit protocols rsvp route] | RSVP adds the actual IGP metric of the installed routes to the existing metrics in the RSVP LSP route
created with conditional-metric.
Default
include-igp-metric is disabled by default. If you do not include the include-igp-metric statement, RSVP
continues to use the currently configured metrics in which the RSVP route... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.1R1 | [
"Configuring RSVP-signaled MPLS Label-Switched Path (LSP) Metrics"
] |
include-ipv6 (Gx-Plus) | include-ipv6; | [edit access gx-plus global] | Include IPv6 subscribers in Gx-Plus provisioning requests.
Default
By default, IPv6 subscribers are not included. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring Gx-Plus Global Attributes",
"Configuring Gx-Plus"
] |
include-irb-and-l2 | include-irb-and-l2; | [edit forwarding-options dhcp-relay dhcpv6 (relay-agent-interface-id | relay-agent-remote-id)],
[edit forwarding-options dhcp-relay dhcpv6 group group-name (relay-agent-interface-id | relay-agent-
remote-id)],
[edit forwarding-options dhcp-relay relay-option-82 (circuit-id | remote-id)],
[edit forwarding-options dhcp-r... | Include both the integrated routing and bridging (IRB) interface name and Layer 2 interface name in the
circuit-id or remote-id value in the DHCP option 82 information. VLAN tags are global.
For leasequery and bulk leasequery operations that involve integrated routing and bridging (IRB)
interfaces, you must configure D... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1.
NOTE: The EX Series switches that support the include-irb-and-l2 statement are the
EX4300, EX4600, and EX9200 switches. | [
"Including a Textual Description in DHCP Options",
"Using DHCP Relay Agent Option 82 Information",
"Configuring DHCPv6 Relay Agent Options"
] |
include-mp-next-hop | include-mp-next-hop; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Enable multiprotocol updates to contain next-hop reachability information. | [] | 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 IPv6 BGP Routes over IPv4 Transport",
"Enabling Layer 2 VPN and VPLS Signaling",
"Understanding Multiprotocol BGP"
] |
include-option-82 (DHCP Local Server) | include-option-82 {
forcerenew;
nak;
} | [edit system services dhcp-local-server overrides],
[edit system services dhcp-local-server dhcpv6 overrides],
[edit system services dhcp-local-server dhcpv6 group group-name overrides],
[edit system services dhcp-local-server dhcpv6 group group-name interface interface-name
overrides],
[edit logical-systems logical-s... | Specify that the DHCP server include option 82 information in NAK and forcerenew messages when
you configure secure communications between the DHCP server and DHCP clients that are in different
VRFs. You can configure support globally, for a group of interfaces, or for a specific interface. | [
{
"name": "forcerenew",
"desc": "Include option 82 in DHCP forcerenew messages."
},
{
"name": "nak",
"desc": "Include option 82 in DHCP NAK messages."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Releases 13.3R3, 14.1R2, and 14.2R1. | [
"DHCP Message Exchange Between DHCP Clients and DHCP Server in Different VRFs",
"Configuring DHCP Message Exchange Between DHCP Server and Clients in Different Virtual Routing",
"Instances"
] |
include-sci (MACsec for MX Series) | include-sci; | [edit security macsec connectivity-association connectivity-association-name] | Specifies that the SCI tag should be appended to each packet on a link that has enabled MACsec.
This option is used only when connecting a router to a host device that requires SCI tagging. SCI tags
are eight octets long, so appending an SCI tag to all traffic on the link adds a significant amount of
unneeded overhead.... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Media Access Control Security (MACsec) on Routers"
] |
include-sci | include-sci; | [edit security macsec connectivity-association connectivity-association-name] | Specifies that the SCI tag should be appended to each packet on a link that has enabled MACsec.
You must enable SCI tagging on a switch that is enabling MACsec on an Ethernet link connecting to an
EX4300 or EX4600 switch.
SCI tags are automatically appended to packets leaving a MACsec-enabled interface on EX4300 or
EX4... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D15.
Statement introduced for SRX Series Firewalls in Junos OS Release 15.1X49-D60. | [
"Configuring MACsec on EX, QFX and SRX Devices",
"Understanding Media Access Control Security (MACsec)",
"Configuring Media Access Control Security (MACsec)"
] |
includes (Dynamic Access-Line-Identifier VLANs) | includes {
accept-no-ids {
mac-address;
}
circuit-id;
remote-id;
} | [edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit auto-configure line-identity],
[edit interfaces interface-name unit logical-unit-number auto-configure line-identity] | Configure the access-line identifier received in DHCP or PPPoE discovery packets that is a trusted
option. Trusted options are accepted for dynamically creating a VLAN on a static or dynamic underlying
VLAN interface. These VLANs are known as access-line-identifier-based VLANs. | [
{
"name": "accept-no-ids",
"desc": "(Optional) Enables creation of a VLAN in the absence of the ACI and the ARI string in the received DHCP or PPPoE packet. This VLAN serves an a default VLAN to collect all subscribers for which no sub-option is received. For PPPoE subscribers you can configure the accept-n... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS 17.1.
mac-address option introduced in Junos OS 25.2R1. | [
"Configuring Dynamic Underlying VLAN Interfaces to Use Access-Line Identifiers",
"Configuring Dynamic VLAN Subscriber Interfaces Based on Access-Line Identifiers"
] |
inclusive | inclusive; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols mvpn
family (inet | inet6) autodiscovery-only intra-as],
[edit routing-instances routing-instance-name protocols mvpn family (inet | inet6) autodiscovery-
only intra-as] | For Rosen 7, enable the MVPN control plane for autodiscovery only, using intra-AS autodiscovery routes
over an inclusive provider multicast service interface (PMSI). | [] | 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 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"
] |
incoming-map | incoming-map {
caller caller-number | accept-all;
} | [edit interfaces dln unit logical-unit-number dialer-options],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number dialer-options] | On J Series Services Routers with interfaces configured for ISDN, specify the dialer to accept incoming
calls.
The remaining statements are explained separately. See CLI Explorer.
NOTE: The incoming-map statement is mandatory for the router to accept any incoming
ISDN calls. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [] |
incoming-queue | incoming-queue {
size size;
} | [edit access diameter peer peer-name] | Configure the incoming queue properties of this peer. | [
{
"name": "size size",
"desc": "Size of the queue. The default is 6000. Range: 1 through 65,535 packets"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [] |
independent-domain | independent-domain <no-attrset>; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options autonomous-system autonomous-system],
[edit routing-instances routing-instance-name routing-options autonomous-system autonomous-
system] | Configure an independent AS domain.
The independent domain uses transitive path attribute 128 (attribute set) messages to tunnel the
independent domain’s BGP attributes through the internal BGP (IBGP) core.
This improves the transparency of Layer 3 VPN services for customer networks by preventing the IBGP
routes that ... | [
{
"name": "no-attrset",
"desc": "(Optional) Disables attribute set messages on the independent AS domain."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
no-attrset option introduced in Junos OS Release 10.4. | [
"Example: Tunneling Layer 3 VPN IPv6 Islands over an IPv4 Core Using IBGP and Independent",
"Domains",
"Configuring Layer 3 VPNs to Carry IBGP Traffic",
"autonomous-system",
"Disabling Attribute Set Messages on Independent AS Domains for BGP Loop Detection"
] |
index (Applications) | index number; | [edit services application-identification application application-name],
[edit services application-identification application-group group-name] | Assign an application or application-group index number. This is a mandatory value. | [
{
"name": "number",
"desc": "Index number; must be a unique, unsigned value."
}
] | 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. | [
"Defining an Application Identification",
"Configuring Application Groups"
] |
index (Nested Applications) | index number; | [edit services application-identification nested-application name] | Set a number that is a one-to-one mapping to the application name. The application name is used to
ensure that each signature definition is unique. | [
{
"name": "number",
"desc": "Numeric value associated with an application name. The index range for predefined applications is from 1 through 32,767. The index range for custom applications and custom nested applications is from 32,768 through 65,534."
}
] | system—To view this statement in the configuration.
system control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Application Identification for Nested Applications"
] |
indexed-load-balance | indexed-load-balance; | [edit forwarding-options load-balance],
[edit logical-systems logical-system-name forwarding-options load-balance],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options load-balance],
[edit routing-instances routing-instance-name forwarding-options load-balance] | The indexed-load-balance statement causes the creation of a nexthop structure that is both a function of
the hash, and a function of the low-order bits of the IP address. Include this statement if you notice
issues with load-balance distribution for IPv4 or IPv6 traffic to improve load-balance distribution for
unicast ... | [] | 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.
Starting with Junos OS Release 12.1, the indexed-next-hop statement has been renamed as the
indexed-load-balance statement. | [
"Understanding the Algorithm Used to Load Balance Traffic on MX Series Routers",
"Configuring Per-Prefix Load Balancing"
] |
indication | indication (ignore | normal | require); | [edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options] | For X.21 interfaces only, configure the from-DCE signal indication. | [
{
"name": "ignore",
"desc": "The from-DCE signal is ignored."
},
{
"name": "normal",
"desc": "Normal indication signal handling as defined by ITU-T Recommendation X.21."
},
{
"name": "require",
"desc": "The from-DCE signal must be asserted."
}
] | 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 Serial Signal Handling"
] |
indication-polarity | indication-polarity (negative | positive); | [edit interfaces interface-name serial-options] | For X.21 interfaces only, configure the indication signal polarity. | [
{
"name": "positive",
"desc": "Positive signal polarity."
},
{
"name": "negative",
"desc": "Negative signal polarity."
}
] | 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 Serial Signal Polarities"
] |
indirect-next-hop | (indirect-next-hop | no-indirect-next-hop); | [edit logical-systems logical-system-name routing-options forwarding-table],
[edit routing-options forwarding-table] | Enable indirectly connected next hops for route convergence. This statement is implemented on the
Packet Forward Engine to speed up forwarding information base (FIB) updates. Configuring this
statement significantly speeds convergence times. The only downside of configuring this statement is
that some additional FIB me... | [
{
"name": "indirect-next-hop",
"desc": "Enable indirectly connected next hops."
},
{
"name": "no-indirect-next-hop",
"desc": "Explicitly disable indirect next hops."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the Packet Forwarding",
"Engine"
] |
indirect-next-hop-change-acknowledgements | (indirect-next-hop-change-acknowledgements | no-indirect-next-hop-change-acknowledgements); | [edit logical-systems logical-system-name routing-options forwarding-table],
[edit routing-options forwarding-table] | Configure the routing protocol process (rpd) to request an acknowledgement when creating a new
forwarding next hop.
During an indirect next-hop change sequence, the routing device might create a new forwarding next
hop that is referenced by the indirect next hop. If the indirect-next-hop-change-acknowledgements stateme... | [
{
"name": "indirect-next-hop-change-acknowledgements",
"desc": "Enable acknowledgements."
},
{
"name": "no-indirect-next-hop-change-acknowledgements",
"desc": "Explicitly disable acknowledgements."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the Packet Forwarding",
"Engine"
] |
ineligible | ineligible; | [edit logical-systems logical-system-name protocols router-discovery address address],
[edit protocols router-discovery address address] | Specify that the address can never become the default router. | [] | routing—To view this statement in the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Understanding the ICMP Protocol for Discovering Gateways to Other Networks",
"Example: Configuring the ICMP Protocol for Discovering Gateways to Other Networks"
] |
inet (AMT Protocol) | inet {
anycast-prefix ip-prefix/<prefix-length>;
local-address ip-address;
} | [edit logical-systems logical-system-name protocols amt relay family],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols amt
relay family],
[edit protocols amt relay family],
[edit routing-instances routing-instance-name protocols amt relay family] | Specify the IPv4 local address and anycast prefix for Automatic Multicast Tunneling (AMT) relay
functions.
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 10.2. | [
"Configuring the AMT Protocol"
] |
inet (chassis) | inet {
layer-3;
layer-4;
symmetric-hash {
complement;
}
} | [edit chassis fpc slot-number pic pic-number hash-key family] | (MX Series 5G Universal Routing Platforms only) Configure data used in a hash key for the inet protocol
family when configuring PIC-level symmetrical load balancing on an 802.3ad Link Aggregation Group. | [
{
"name": "layer-3",
"desc": "Include Layer 3 IP data in the hash key."
},
{
"name": "layer-4",
"desc": "Include Layer 4 IP data in the hash key."
},
{
"name": "symmetric-hash",
"desc": "Configure symmetric hash key with source and destination ports."
}
] | 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 PIC-Level Symmetrical Hashing for Load Balancing on 802.3ad LAGs for MX Series",
"Routers"
] |
inet (CoS) | inet {
classifiers {
(dscp | inet-precedence) classifier-name ;
}
} | [edit class-of-service multi-destination family] | Specify the IP multicast family.
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. | Option inet introduced in Junos OS Release 9.5 for EX Series switches.
The remaining statements are explained separately. See CLI Explorer. | [
"Understanding CoS Schedulers",
"Understanding CoS Forwarding Classes",
"Understanding CoS Classifiers"
] |
inet (enhanced-hash-key) | inet {
gtp-tunnel-endpoint-identifier;
no-ipv4-destination-address;
no-ipv4-source-address;
no-l4-destination-port;
no-l4-source-port;
no-incoming-port;
} | [edit forwarding-options enhanced-hash-key family] | Select the payload fields in IPv4 traffic used by the hashing algorithm to make hashing decisions.
When IPv4 traffic enters a LAG and the hash mode is set to Layer 2 payload, the hashing algorithm
checks the fields configured using the inet statement and uses the information in the fields to decide
how to place traffic... | [
{
"name": "no-ipv4-destination-address",
"desc": "Exclude the IPv4 destination address field from the hashing algorithm."
},
{
"name": "no-ipv4-source-address",
"desc": "Exclude the IPv4 source address field from the hashing algorithm."
},
{
"name": "no-l4-destination-port",
"desc": ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51-D15. | [
"Configuring the Fields in the Algorithm Used To Hash LAG Bundle and ECMP Traffic (CLI Procedure)",
"Understanding the Algorithm Used to Hash LAG Bundle and Egress Next-Hop ECMP Traffic",
"Understanding the Algorithm Used to Hash LAG Bundle and Egress Next-Hop ECMP Traffic (QFX",
"10002 and QFX 10008 Switches... |
inet (forwarding options) | inet {
mode(drop | flow-based | packet-based);
} | [edit security forwarding-options family] | The default mode for inet is flow mode.
Family IPv4 | [
{
"name": "mode",
"desc": "Forwarding mode"
},
{
"name": "drop",
"desc": "Disable forwarding"
},
{
"name": "flow-based",
"desc": "Enable flow-based forwarding"
},
{
"name": "packet-based",
"desc": "Enable packet-based forwarding"
}
] | [none specified] | Statement supported in Junos 24.2R1 for SRX Series Firewalls | [] |
inet (interfaces (QFX Series)) | inet {
address address {
primary;
filter input filter-name;
filter output filter-name;
targeted-broadcast;
}
} | [edit interfaces interface-name unit logical-unit-number family],
[edit interfaces interface-range interface-name unit logical-unit-number family] | Configure the primary IP address for the logical interface.
Junos will no longer accept duplicate IPs between different logical interfaces in the same routing
instance. It is applicable to both inet and inet6. The below table lists the duplicate addresses found
between different interfaces.
Table 63: Allowed Duplicate... | [] | 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. | [
"Configuring Gigabit and 10-Gigabit Ethernet Interfaces for EX4600 and QFX Series Switches"
] |
inet (Interfaces) | inet {
address source;
auto-configure {
address-ranges {
authentication {
password password-string;
username-include {
auth-server-realm realm-string;
delimiter delimiter-character;
domain-name domain... | [edit interfaces interface-name unit unit-number demux] | Specify the inet family for the demultiplexing (demux) interface options. | [
{
"name": "address-source",
"desc": ""
},
{
"name": "address",
"desc": "Specify the source IPv4 or IPv6 address or prefix value from which to inherit configuration data for the demultiplexing (demux) interface options."
}
] | 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. | [
"IP Demultiplexing Interfaces on Packet-Triggered Subscribers Services Overview",
"Configuring Packet Triggered Subscribers Using IP Demux Interfaces in Dynamic Profiles"
] |
inet (Port Mirroring) | inet {
output {
ip-addressaddress {
}
routing-instance instance-name {
ip-address address {
}
} | [edit forwarding-options port-mirroring [instance name] family] | Specify that the output interface will be of type inet. Use this statement so that you can send the
mirrored packets to the IP address of the device running an analyzer application. The device can be on a
remote network. When you use this feature, the mirrored packets are GRE-encapsulated. The analyzer
device must be a... | [] | 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. | [] |
inet (Routing Policy Condition) | inet {
address;
table table-name;
} | [edit logical-systems logical-system-name policy-options condition if-route-exists address-
family],
[edit policy-options condition if-route-exists address-family] | Specify that the route must correspond to a IPv4 prefix to be considered a match. | [
{
"name": "(Optional) address",
"desc": "Specify the IP address that the route must have to be considered a match."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Example: Configuring Pseudowire Redundancy in a Mobile Backhaul Scenario"
] |
inet (Security Static NAT) | inet {
routing-instance (routing-instance-name| default);
} | [edit security nat static rule-set rule-set-name rule rule-name then static-nat] | Specify the automatic translation of IPv6 addresses to IPv4 addresses (and vice versa).
NOTE: If you use this option, you do not need to use the prefix option because with this
option, the first 96 most significant bits are automatically stripped from the 128-bit IPv6
address. | [
{
"name": "routing-instance routing-instance-name",
"desc": "Use the user-defined static NAT routing-instance to perform"
},
{
"name": "default",
"desc": "Use the default routing-instance to perform static NAT. When a routing-instance-name is not"
}
] | 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. | [] |
inet (Subscriber Secure Policy) | inet {
drop-policy rule-name {
from {
apply-groups group-name;
apply-groups-except group-name;
destination-address address;
destination-port port-number;
dscp dscp-value;
protocol protocol;
source-address address;
... | [edit services radius-flow-tap policy policy-name] | Specify the inet family for the policy that is applied to mirrored packets sent to a mediation device.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | flow-tap—To view this statement in the configuration.
flow-tap-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Subscriber Secure Policy Overview",
"Configuring RADIUS-Initiated Subscriber Secure Policy Mirroring Overview"
] |
inet (TDF Subscriber Address) | inet {
apply-groups [group-names];
apply-groups-except [group-names];
pool pool-name;
} | [edit unified-edge gateways tdf gateway-name domains domain-name ip-subscriber subscriber-
address] | Specify IP version 4 (IPv4) for the address pool that contains the source IP addresses for IP-based
subscriber packets that undergo TDF processing.
The remaining statements are 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",
"Understanding the Definition of a Set of IP-Based Subscriber Properties with a TDF Domain",
"IP-Based Subscriber Setup Overview"
] |
inet (TDF Subscriber Exclude Prefix) | inet {
network address mask;
} | [edit unified-edge gateways tdf gateway-name domains domain-name subscriber-exclude-prefix
family] | Specify IP version 4 (IPv4) 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 (CoS Multidestination) | inet6 {
classifiers {
dscp-ipv6 classifier-name;
}
} | [edit class-of-service multi-destination family] | Specify the IPv6 multicast family.
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. | Option inet6 introduced in before Junos OS 11.4 for EX Series switches. | [
"Understanding CoS Schedulers",
"Understanding CoS Forwarding Classes",
"Understanding CoS Classifiers"
] |
inet6 (enhanced-hash-key) | inet6 {
gtp-tunnel-endpoint-identifier;
ipv6-flow-label;
no-ipv6-destination-address;
no-ipv6-source-address;
no-l4-destination-port;
no-l4-source-port;
no-incoming-port;
} | [edit forwarding-options enhanced-hash-key family] | Select the payload fields in an IPv6 packet used by the hashing algorithm to make hashing decisions.
When IPv6 traffic enters a LAG and the hash mode is set to Layer 2 payload, the hashing algorithm
checks the fields configured using this statement and uses the information in the fields to decide how to
place traffic o... | [
{
"name": "no-ipv6-destination-address",
"desc": "Exclude the IPv6 destination address field from the hashing algorithm."
},
{
"name": "no-ipv6-source-address",
"desc": "Exclude the IPv6 source address field from the hashing algorithm."
},
{
"name": "no-l4-destination-port",
"desc": ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51-D15. | [
"Configuring the Fields in the Algorithm Used To Hash LAG Bundle and ECMP Traffic (CLI Procedure)",
"Understanding the Algorithm Used to Hash LAG Bundle and Egress Next-Hop ECMP Traffic",
"Understanding the Algorithm Used to Hash LAG Bundle and Egress Next-Hop ECMP Traffic (QFX",
"10002 and QFX 10008 Switches... |
inet6 (forwarding options) | inet6 {
mode(drop | flow-based | packet-based);
} | [edit security forwarding-options family] | The default mode for inet6 is flow mode.
Family IPv6 | [
{
"name": "mode",
"desc": "Forwarding mode"
},
{
"name": "drop",
"desc": "Disable forwarding"
},
{
"name": "flow-based",
"desc": "Enable flow-based forwarding"
},
{
"name": "packet-based",
"desc": "Enable packet-based forwarding"
}
] | [none specified] | Statement supported in Junos 24.2R1 for SRX Series Firewalls | [] |
inet6 (interfaces (QFX Series)) | inet6 {
address address {
eui-64
preferred
primary;
filter input filter-name;
filter output filter-name;
}
} | [edit interfaces interface-name unit logical-unit-number family],
[edit interfaces interface-range interface-name unit logical-unit-number family] | Configure the primary IP address for the logical interface.
Default
You must configure a logical interface to be able to use the physical device. | [] | 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 Gigabit and 10-Gigabit Ethernet Interfaces for EX4600 and QFX Series Switches",
"Configuring Gigabit and 10-Gigabit Ethernet Interfaces for OCX Series Switches"
] |
inet6 (Interfaces) | inet6 {
address source;
auto-configure {
address-ranges {
authentication {
password password-string;
username-include {
auth-server-realm realm-string;
delimiter delimiter-character;
domain-name domai... | [edit interfaces interface-name unit unit-number demux] | Specify the inet6 family for the demultiplexing (demux) interface options. | [
{
"name": "address-source",
"desc": ""
},
{
"name": "address",
"desc": "Specify the source IPv4 or IPv6 address or prefix value from which to inherit configuration data for the demultiplexing (demux) interface options."
}
] | 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. | [
"IP Demultiplexing Interfaces on Packet-Triggered Subscribers Services Overview",
"Configuring Packet Triggered Subscribers Using IP Demux Interfaces in Dynamic Profiles"
] |
inet6 (Subscriber Secure Policy) | inet6 {
drop-policy rule-name {
from {
apply-groups group-name;
apply-groups-except group-name;
destination-address address;
destination-port port-number;
dscp dscp-value;
protocol protocol;
source-address address;
... | [edit services radius-flow-tap policy policy-name] | Specify the inet6 family for the policy that is applied to mirrored packets sent to a mediation device.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | flow-tap—To view this statement in the configuration.
flow-tap-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Subscriber Secure Policy Overview",
"Configuring RADIUS-Initiated Subscriber Secure Policy Mirroring Overview"
] |
inet6 (TDF Subscriber Address) | inet6 {
pool pool-name;
} | [edit unified-edge gateways tdf gateway-name domains domain-name ip-subscriber subscriber-
address] | Specify IP version 6 (IPv6) for the address pool that contains the source IP addresses for IP-based
subscriber packets that undergo TDF processing.
The remaining statements are 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",
"Understanding the Definition of a Set of IP-Based Subscriber Properties with a TDF Domain",
"IP-Based Subscriber Setup Overview"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.