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 |
|---|---|---|---|---|---|---|---|
ipsec-vpn (Security Flow) | ipsec-vpn {
mss value;
} | [edit security flow tcp-mss] | Specify the TCP maximum segment size (TCP MSS) for the TCP packets that are about to go into an
IPsec VPN tunnel. This value overrides the value specified in the all-tcp-mss statement. | [
{
"name": "mss value",
"desc": "TCP MSS value for TCP packets entering an IPsec VPN tunnel. Value is optional. Range: 64 through 65,535 bytes"
}
] | 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. | [
"IPsec VPN Overview"
] |
ipsec-vpn (Security Policies) | ipsec-vpn vpn-name; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
tunnel] | Define IPsec name for VPN. | [
{
"name": "vpn-name",
"desc": "Name of the IPsec."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Security Policies Overview"
] |
ipsec-vpn-options | ipsec-vpn-options {
anti-replay-window-size bits;
clear-dont-fragment-bit;
ike-access-profile profile-name;
local-gateway address;
no-certificate-chain-in-ike;
no-anti-replay;
passive-mode-tunneling;
trusted-ca [ ca-profile-names ];
tunnel-mtu bytes;
udp-encapsulation {
<... | [edit services service-set service-set-name] | Specify IP Security (IPsec) service options. | [] | 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 IPsec Service Sets",
"Configuring Service Rules"
] |
ipsec-vpn-rules | (ipsec-vpn-rules rule-name | ipsec-vpn-rule-sets rule-set-name); | [edit services service-set service-set-name] | Specify the IPsec rules or rule set included in this service set. You can configure multiple rules, but only
one rule set for each service. | [
{
"name": "rule-name",
"desc": "Identifier for the collection of terms that constitute this rule."
},
{
"name": "rule-set-name",
"desc": "Identifier for the set of rules to be included."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Service Rules"
] |
ipv4 (Family MPLS) | ipv4 {
destination-address ip-address {
except;
}
destination-prefix-list destination-prefix-list-name {
except;
}
protocol protocol {
(source-port | source-port-except);
(destination-port | destination-port-except);
}
source-address ip-address {
excep... | [edit firewall family mpls filter name term name from ip-version] | Define Layer 3 and Layer 4 match items to match IPv4 packets for IP-based filtering of MPLS traffic. | [
{
"name": "destination-address ip-address",
"desc": "Match MPLS traffic with the specified IPv4 destination address."
},
{
"name": "destination-prefix-list",
"desc": ""
},
{
"name": "destination-prefix-list-name",
"desc": "Match MPLS traffic with the specified IPv4 destination prefix... | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R1. | [
"Understanding IP-Based Filtering and Selective Port Mirroring of MPLS Traffic"
] |
ipv4 (Security IDP Signature Attack) | ipv4 {
checksum-validate {
match (equal | greater-than | less-than | not-equal | validate);
value value;
}
destination (Security IP Headers Attack) {
match (equal | greater-than | less-than | not-equal);
value value;
}
identification (Security ... | [edit security idp custom-attack attack-name attack-type signature protocol] | An IP header is header information at the beginning of an IP packet which contains information about IP
version, source IP address, destination IP address, time-to-live, etc. Allow IDP to match the IP header
information for the signature attack. | [
{
"name": "identification",
"desc": "Specify a unique value used by the destination system to reassemble a fragmented packet. Syntax:"
},
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value identification-value",
"desc": ... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
ipv4-address (Steering Path) | ipv4-address ipv4-address; | [edit unified-edge pcef pcc-action-profiles profile-name steering path]
[edit services pcef pcc-action-profiles profile-name] | Specify the IPv4 address of a third-party server to which the PCC action profile steers HTTP traffic for
applying services. If you configure this, the PCC action profile can only be used in PCC rules that match
only HTTP-based applications and all flows. | [
{
"name": "ipv4-address ipv4-address",
"desc": "Use the specified IPv4 address of the server."
}
] | For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration.
For Junos OS Subscriber Aware:
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.
Support at the [edit services pcef pcc-action-profiles profile-name] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series.
Support for Next Gen Services for Junos OS Broadband Subscriber Management introduced in Juno... | [
"Understanding Application-Aware Policy Control for Subscriber Management",
"Configuring Policy and Charging Control Action Profiles for Subscriber Management",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Configuring Policy and Charging Control Action ... |
ipv4-dscp | ipv4-dscp number | [edit protocols ptp] | Specify the value used as the DiffServ code point (DSCP) value for all Precision Time Protocol (PTP) IPv4
packets originated by the router. | [
{
"name": "number",
"desc": "DiffServ code point (DSCP) value for all PTP IPv4 packets originated by the router."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"IEEE 1588v2 Precision Timing Protocol (PTP)",
"Precision Time Protocol Overview"
] | |
ipv4-flow-table-size | ipv4-flow-table-size units; | [edit chassis fpc slot-number inline-services flow-table-size] | 17.3R1
Starting with Junos OS Release 17.3R1, for LU-based platforms, the maximum number of units is 15. For
XL-based platforms, the maximum is 220. For EA-based platforms, the maximum is 48 for MPC7E and
MPC9E. For MPC8E, the maximum is 97.
16.1R1
Starting with Junos OS Release 16.1R1 and 15.1F2, by default, the softw... | [
{
"name": "units",
"desc": "Number of 256K flow entries available for the IPv4 flow table. 1 unit equals 256K flow entries. Range: 1 through the maximum number of units for the line card. See Table 66 on page 9742 for maximum number of units for line cards."
},
{
"name": "Default: The absolute numb... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250"
] | |
ipv4-mask (HTTP Header Enrichment) | ipv4-mask ipv4-mask; | [edit services hcm tag-rule rule-name term term-number then tag tag-name] | Configure the IPv4 mask to identify a byte of the IPv4 subscriber address that you want to modify in the
HTTP header. You must also set the ipv4-or-value statement at the [edit services hcm tag-rule rule-name term
term-number then tag tag-name] hierarchy level to specify the new value you want to put in the byte. | [
{
"name": "ipv4-mask",
"desc": "IPv4 mask. Specify 255 in the byte you want to modify and specify 0 in the bytes that you do not want to modify."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview",
"Configuring Tag Rules",
"Configuring HCM Profiles and Assigning Tag Rules",
"Junos Web Aware HTTP Header Enrichment Overview"
] |
ipv4-or-value (HTTP Header Enrichment) | ipv4-or-value ipv4-or-value; | [edit services hcm tag-rule rule-name term term-number then tag tag-name] | Configure the new IPv4 value for the byte you want to modify in the IPv4 subscriber address in the
HTTP header. You must also set the ipv4-mask statement at the [edit services hcm tag-rule rule-name term
term-number then tag tag-name] hierarchy level to clear the existing byte value. | [
{
"name": "ipv4-or-value",
"desc": "IPv4 value. Specify the new value in the byte you are modifying and specify 0 in all other bytes."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview",
"Configuring Tag Rules",
"Configuring HCM Profiles and Assigning Tag Rules",
"Junos Web Aware HTTP Header Enrichment Overview"
] |
ipv4-prefix | ipv4-prefix {
as as;
router-id router-id;
prefix prefix;
system-id system-id;
} | [edit logical-systems logical-system-name policy-options policy-statement policy-name term term-
name from traffic-engineering],
[edit policy-options policy-statement policy-name term term-name from traffic-engineering] | Configure filter options for a traffic engineering policy to filter traffic based on IPv4 prefix addresses.
You can specify additional parameters, such as autonomous system (AS), prefix, router ID, and system ID
for filtering IPv4 traffic. If you do not specify the additional parameters, the policy matches all IPv4-
pr... | [
{
"name": "as as",
"desc": "Specify an AS to filter traffic."
},
{
"name": "router-id router-id",
"desc": "Specify an IP prefix to match the router-ID against."
},
{
"name": "prefix",
"desc": "Specify an IPv4 prefix to match against."
},
{
"name": "system-id system-id",
"... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1. | [] |
ipv4-template | ipv4-template; | [edit services flow-monitoring version9 template template-name],
[edit services flow-monitoring version-ipfix template template-name] | Specify the version 9 or IPFIX template properties for one of the following:
•
Template for monitoring IPv4 flows.
•
Template for inline monitoring an MPLS-over-UDP flow that is carried between IPv4 endpoints on
PTX Series routers. This monitoring looks past the tunnel header to report the inner payload of the
packets.... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3.
Support at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level added in
Junos OS Release 10.2. | [
"Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9",
"Flow Templates",
"Configuring Flow Aggregation to Use IPFIX Flow Templates on PTX Series Routers",
"Configuring Inline J-Flow to Use IPFIX Flow Templates on MX, vMX and T Series Routers, EX Series",
"Switches, NF... |
ipv6 (Family MPLS) | ipv6 {
destination-address destination-ip-address {
except;
}
destination-prefix-list prefix-list-name {
except;
}
protocol protocol {
(source-port | source-port-except);
(destination-port | destination-port-except);
}
source-address ip-address {
excep... | [edit firewall family mpls filter name term name from ip-version] | Define Layer 3 and Layer 4 match items to match IPv6 packets for IP-based filtering of MPLS traffic. | [
{
"name": "destination-address ip-address",
"desc": "Match MPLS traffic with the specified IPv6 destination address."
},
{
"name": "destination-prefix-list",
"desc": ""
},
{
"name": "destination-prefix-list-name",
"desc": "Match MPLS traffic with the specified list of IPv6 destinatio... | firewall | Statement introduced in Junos OS Release 18.4R1. | [] |
ipv6-address (Steering Path) | ipv6-address ipv6-address; | [edit unified-edge pcef pcc-action-profiles profile-name steering path]
[edit services pcef pcc-action-profiles profile-name] | Specify the IPv6 address of a third-party server to which the PCC action profile steers HTTP traffic for
applying services. If you configure this, the PCC action profile can only be used in PCC rules that match
only HTTP-based applications and all flows. | [
{
"name": "ipv6-address ipv6-address",
"desc": "Use the specified IPv6 address of the server."
}
] | For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration.
For Junos OS Subscriber Aware:
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.
Support at the [edit services pcef pcc-action-profiles profile-name] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series.
Support for Next Gen Services for Junos OS Broadband Subscriber Management introduced in Juno... | [
"Understanding Application-Aware Policy Control for Subscriber Management",
"Configuring Policy and Charging Control Action Profiles for Subscriber Management",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Configuring Policy and Charging Control Action ... |
ipv6-extended | ipv6-extended:type-and-subtype value:<IPv6 unicast address>:operator-defined local values | [edit policy-options community community-name members] | Defines the extended format of the IPv6 unicast address in a policy match. | [] | policy-options—To view and add this statement in the configuration. | Statement introduced in Junos OS Release and Junos OS Evolved Release 23.1. | [] |
ipv6-extended-attrib | ipv6-extended-attrib; | [edit chassis fpc slot-number inline-services ipv6 flow-table-size] | Enable the inclusion of element ID, 54, fragmentIdentification, and element ID, 64,
ipv6ExtensionHeaders, in IPFIX flow templates that are exported to the flow collector
NOTE: Collection of IPv4 fragmentation IDs occurs automatically without having to
configure this setting explicitly. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250"
] | |
ipv6-extension-header (IDS Screen Next Gen Services) | ipv6-extension-header {
AH-header;
ESP-header;
fragment-header;
hop-by-hop-header {
CALIPSO-option;
jumbo-payload-option;
quick-start-option;
router-alert-option;
RPL-option;
SFM-DPD-option;
user-defined-option-type <type-low> to <type-high>;
... | [edit services screen ids-option screen-name ip] | Identify and drop IP packets that have the configured IPv6 extension header values. | [
{
"name": "ah-header",
"desc": "Authentication Header extension header"
},
{
"name": "esp-header",
"desc": "Encapsulating Security Payload extension header"
},
{
"name": "fragment-header",
"desc": "Fragment Header extension header"
},
{
"name": "hop-by-hop-header",
"desc"... | 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. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
ipv6-extension-header | ipv6-extension-header {
AH-header;
ESP-header
HIP-header;
destination-header {
ILNP-nonce-option;
home-address-option;
line-identification-option;
tunnel-encapsulation-limit-option;
user-defined-option-type low | <to high>;
}
fragment-header;
hop-by-ho... | [edit security screen ids-option screen-name ip] | Define the IPv6 extension header for the intrusion detection service (IDS). | [
{
"name": "AH-header",
"desc": "Enable the IPv6 Authentication Header screen option."
},
{
"name": "ESP-header",
"desc": "Enable the IPv6 Encapsulating Security Payload header screen option."
},
{
"name": "HIP-header",
"desc": "Enable the IPv6 Host Identify Protocol header screen opt... | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [
"Understanding IPv6 Support for Screens"
] |
ipv6-extension-header-limit | ipv6-extension-header-limit limit; | [edit security screen ids-option screen-name ip] | Define the IPv6 extension header number limit for screen options. The screen blocks packets that have
more than the defined number of extension headers. | [
{
"name": "limit",
"desc": "Set the number of IPv6 extension headers that can pass through the screen. Range: 0 through 32."
}
] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [
"Understanding IPv6 Support for Screens"
] |
ipv6-flow-label | ipv6-flow-label; | For PTX Series:
[edit forwarding-options hash-key family inet6 layer-3] | Enable IPv6 packet flow labels for hash calculations and load balancing based on the flow label of the
IPv6 header. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D30 on QFX10002 and 10008 switches.
Statement introduced in Junos OS Release 18.3R1 for PTX series routers. | [
"Understanding the Algorithm Used to Hash LAG Bundle and Egress Next-Hop ECMP Traffic (QFX",
"10002 and QFX 10008 Switches)"
] |
ipv6-flow-table-size | ipv6-flow-table-size units; | [edit chassis fpc slot-number inline-services ipv6 flow-table-size] | Configure the size of the IPv6 flow table in units of 256K entries.
NOTE: Prior to Junos OS Release 15.1F2, any changes in the configured size of the flow
table initiates an automatic reboot of the FPC.
NOTE: The recommended flow table size is 4 so that it can scale up to 4x256K flows,
which is 1M. You can configure mo... | [
{
"name": "units",
"desc": "Number of 256K flow entries available for the IPv6 flow table. Range: 1 through 245 Default: If number of units is not specified, 1024 flow entries are allocated for IPv6."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250"
] | |
ipv6-malformed-header | ipv6-malformed-header; | [edit security screen ids-option screen-name ip] | Enable the IPv6 malformed header intrusion detection service (IDS) option. The screen will not pass any
communication using the subnet 2001:db8 :: / 32. | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [
"Understanding IPv6 Support for Screens"
] |
ipv6-mask (HTTP Header Enrichment) | ipv6-mask ipv6-mask; | [edit services hcm tag-rule rule-name term term-number then tag tag-name] | Configure the IPv6 mask to identify a byte of the IPv6 subscriber address that you want to modify in the
HTTP header. You must also set the ipv6-or-value statement at the [edit services hcm tag-rule rule-name term
term-number then tag tag-name] hierarchy level to specify the new value you want to put in the byte. | [
{
"name": "ipv6-mask",
"desc": "IPv6 mask. Specify ff in the byte you want to modify and specify 0 in the bytes that you do not want to modify."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview",
"Configuring Tag Rules",
"Configuring HCM Profiles and Assigning Tag Rules",
"Junos Web Aware HTTP Header Enrichment Overview"
] |
ipv6-multicast-interfaces | ipv6-multicast-interfaces (all | interface-name) {
disable;
} | [edit services nat],
[edit services softwire] | Enable multicast filters on Ethernet interfaces when IPv6 NAT is used for neighbor discovery. | [
{
"name": "all",
"desc": "Enable filters on all interfaces."
},
{
"name": "disable",
"desc": "Disable filters on the specified interfaces."
},
{
"name": "interface-name",
"desc": "Enable filters on a specific interface only."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Configuring IPv6 Multicast Interfaces"
] |
ipv6-or-value (HTTP Header Enrichment) | ipv6-or-value ipv6-or-value; | [edit services hcm tag-rule rule-name term term-number then tag tag-name] | Configure the new IPv6 value for the byte you want to modify in the IPv6 subscriber address in the
HTTP header. You must also set the ipv6-mask statement at the [edit services hcm tag-rule rule-name term
term-number then tag tag-name] hierarchy level to clear the existing byte value. | [
{
"name": "ipv6-or-value",
"desc": "IPv6 value. Specify the new value in the byte you are modifying and specify 0 in all other bytes."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview",
"Configuring Tag Rules",
"Configuring HCM Profiles and Assigning Tag Rules",
"Junos Web Aware HTTP Header Enrichment Overview"
] |
ipv6-origin | ipv6-origin:<IPv6 unicast address>:operator-defined local values | [edit policy-options community community-name members] | Defines the source of the IPv6 unicast address in a policy match and allow routes of the specified
community to be advertised. | [] | policy-options—To view and add this statement in the configuration. | Statement introduced in Junos OS Release and Junos OS Evolved Release 23.1. | [] |
ipv6-prefix | ipv6-prefix {
as as;
router-id router-id;
prefix prefix;
system-id system-id;
} | [edit logical-systems name policy-options policy-statement name from traffic-engineering],
[edit policy-options policy-statement name from traffic-engineering] | Configure filter options for a traffic engineering policy to filter traffic based on IPv6 prefix addresses.
You can specify additional parameters, such as autonomous system (AS), prefix, router ID, and system ID
for filtering IPv6 traffic. | [
{
"name": "as as",
"desc": "Specify an AS to filter traffic"
},
{
"name": "router-id router-id",
"desc": "Specify an IP prefix to match the router-ID against."
},
{
"name": "prefix",
"desc": "Specify an IPv6 prefix to match against."
},
{
"name": "system-id system-id",
"d... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.2R1. | [
"Link-State Distribution using SRv6"
] |
ipv6-source-guard | ipv6-source-guard; | For platforms with Enhanced Layer 2 Software (ELS):
[edit vlans vlan-name forwarding-options dhcp-security]
For platforms without ELS:
[edit ethernet-switching-options secure-access-port vlan (all | vlan-name)] | Perform IPv6 source guard checking on packets sent from access interfaces. Validate source IP
addresses and source MAC addresses on all VLANs or on the specified VLAN. Forward packets with
valid addresses and drop those with invalid addresses.
NOTE: If you configure the ipv6-source-guard statement at the [edit vlans vl... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51-D20.
Support at the [edit ethernet-switching-options secure-access-port vlan (all | vlan-name)] hierarchy level
introduced in Junos OS Release 14.1X53-D10 for EX Series switches. | [
"Example: Configuring IPv6 Source Guard and Neighbor Discovery Inspection to Protect a Switch from",
"IPv6 Address Spoofing",
"Configuring IP Source Guard (ELS)"
] |
ipv6-source-guard-sessions | ipv6-source-guard-sessions {
max-number max-number;
} | [edit ethernet-switching-options secure-access-port] | Specify the maximum number of IPv6 source guard sessions for TCAM space provisioning.
NOTE: After setting or changing the maximum number of IPv6 source guard sessions
and committing the configuration, you must reboot the switch for the configuration to
take effect.
Default
Disabled. | [
{
"name": "max-number max-number",
"desc": "The maximum number of IPv6 source guard sessions. Range: 50 through 300."
}
] | 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. | [
"Example: Configuring IPv6 Source Guard and Neighbor Discovery Inspection to Protect a Switch from",
"IPv6 Address Spoofing",
"Configuring IP Source Guard (ELS)"
] |
ipv6-target | ipv6-target:<IPv6 unicast address>:operator-defined local values | [edit policy-options community community-name members] | Defines the VPN IPv6 target unicast address used in a policy match and allow routes of the specified
community to be advertised. | [] | policy-options—To view and add this statement in the configuration. | Statement introduced in Junos OS Release and Junos OS Evolved Release 23.1. | [] |
ipv6-template | ipv6-template; | [edit services flow-monitoring version9 template template-name],
[edit services flow-monitoring version-ipfix template template-name] | Specify that the flow aggregation version 9 or IPFIX template is used only for IPv6 records.
The remaining statements are explained separately. See CLI Explorer. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
Support at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level added in
Junos OS Release 10.2. | [
"Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9",
"Flow Templates",
"Configuring Flow Aggregation to Use IPFIX Flow Templates on PTX Series Routers"
] |
ipv6-tunneling | ipv6-tunneling; | [edit logical-systems name protocols mpls],
[edit logical-systems name routing-instances name protocols mpls],
[edit protocols mpls],
[edit routing-instances name protocols mpls] | Allow IPv6 routes to be resolved over an MPLS network by converting LDP and RSVP routes stored in
the inet.3 routing table to IPv4-mapped IPv6 addresses and then copying them into the inet6.3 routing
table. This routing table can be used to resolve next hops for both inet6 and inet6-vpn routes. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Tunneling IPv6 Traffic over MPLS IPv4 Networks"
] |
ipvacl-firewall-l2-profile | ipvacl-firewall-l2-profile | [edit chassis] | IPACL group is used when a filter is attached to the input of an L2 interface. IPACL group has both L2
qualifiers and L3 qualifiers. Set this configuration statement to have only L2 qualifiers for IPACL/IVACL.
NOTE: When this configuration statement is enabled, only L2 match conditions should
be used for IPACL/IVACL fi... | [] | interface-control | Statement introduced in Junos OS Release 22.2R1 | [] |
iq-policing-filter | iq-policing-filter filter-name; | [edit interfaces interface-name unit unit-number family bridge|inet|vpls ] | For devices that support ingress queuing, attaches a filter to an interface that polices traffic before
assigning to ingress queues. This enables rate limiting of traffic before the traffic is assigned to ingress
queues.
The iq-policing-filter statement is available for the following protocol families: bridge, inet, an... | [
{
"name": "filter-name",
"desc": "Name of the iq-policing-filter filter"
}
] | 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. | [] |
ir-mode | ir-mode (IR | R); | [edit chassis fpc slot-number] | Configure the license mode of the specified enhanced MPC in an MPC slot as IR or R. Setting the license
mode enables you to distinguish between an MPC with an IR license and an MPC with an R license after
the MPC is installed on the router.
NOTE: The license mode settings are used only to provide information. You canno... | [
{
"name": "IR",
"desc": "Configure the license mode IR for an MPC installed in a specified MPC slot. Includes the following"
},
{
"name": "features:",
"desc": "All Layer 2, Layer 2.5, and Layer 3 features. Up to 32 Layer 3 routing instances of the virtual routing and forwarding (VRF) instance t... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"License Modes for Enhanced MPCs Overview",
"Configuring the License Mode for Specific Enhanced MPCs on MX Series Routers",
"Viewing the License Mode for MPC Cards on MX Series Routers"
] |
iracl-firewall-ipv4-profile | iracl-firewall-ipv4-profile | [edit chassis] | Optimize fixed QSET profiles.
IRACL group has IPv6 source and destination address qualifiers by default which is used for matching
IPv4 source and destination addresses as well. Set this configuration statement to have IPv4 profile only.
NOTE: When this configuration statement is enabled, source-address and destinatio... | [] | interface-control | Statement introduced in Junos OS Release 22.2R1 | [] |
irb (Easy EVPN LAG Configuration) | irb irb-instance {
apply-config-groups;
instance {
mac-vrf-instance instance-id;
vrf-instance instance-id;
}
no-dhcp-relay;
subnet-address {
inet (inet-addr | [inet-addr1 inet-addr2 ...]);
inet6 (inet6-addr | [inet6-addr1 inet6-addr2 ...]);
no-irb-address-auto-derive;... | [edit services evpn evpn-vxlan] | Specify parameters to generate the configuration statements for the integrated routing and bridging
(IRB) instances on a provider edge (PE) device in an Ethernet VPN (EVPN) fabric with Virtual Extensible
LAN (VXLAN) encapsulation.
You use statements at the [edit services evpn] hierarchy level to simplify configuring an... | [
{
"name": "(Required)",
"desc": ""
},
{
"name": "irb-instance",
"desc": "Specify a string that identifies an IRB instance and the parameters associated with it for commit script processing. Choose irb-instance values that help interpret what you will see in the generated configuration. For examp... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.2R1. | [
"Easy EVPN LAG (EZ-LAG) Configuration"
] |
irb (EVPN Multicast Replication) | irb {
(enhanced-oism | local-only | local-remote | oism);
} | [edit forwarding-options multicast-replication evpn] | Enable one of the supported integrated routing and bridging (IRB) multicast modes in an EVPN-VXLAN
network.
The EVPN IRB multicast mode options are mutually exclusive. You can enable only one of these modes
at a time, and you must configure the same mode on all devices in the network that process multicast
traffic. If ... | [
{
"name": "local-only",
"desc": "Use this mode with an edge-routed bridging (ERB) overlay, also known as a collapsed IP fabric. In this mode, the PFE on the leaf devices in the fabric performs local multicast routing at the fabric edge. The spine devices, also called lean spines, primarily act as IP transit... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | oism option introduced in Junos OS Release 21.2R1.
enhanced-oism option introduced in Junos OS Release 23.4R1. | [
"IPv4 Inter-VLAN Multicast Forwarding Modes for EVPN-VXLAN Overlay Networks",
"Optimized Inter-Subnet Multicast in EVPN Networks"
] |
irb (Interfaces) | irb {
accounting-profile name;
arp-l2-validate;
description text;
(gratuitous-arp-reply | no-gratuitous-arp-reply);
mtu bytes;
no-gratuitous-arp-request;
traceoptions {
flag flag;
}
(traps | no-traps);
unit logical-unit-number {
accounting-profile name;
... | [edit interfaces interface-name] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3R2.
irb option introduced in Junos OS Release 13.2 for the QFX Series. | [] |
irb | irb {
unit logical-unit-number {
classifiers {
type (classifier-name | default);
}
rewrite-rules {
dscp (rewrite-name | default);
dscp-ipv6 (rewrite-name | default);
exp (rewrite-name | default)protocol protocol-types;
ieee-802.1 (... | [edit class-of-service interfaces] | On the MX Series routers and EX Series switches, you can apply classifiers or rewrite rules to an
integrated bridging and routing (IRB) interface. All types of classifiers and rewrite rules are allowed.
These classifiers and rewrite rules are independent of others configured on the MX Series router and on
EX Series swi... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [
"CoS Features and Limitations on MX Series Routers"
] |
irb-enhanced-scale (Bridge Domain) | bridge-domains <domain-name> {
irb-enhanced-scale;
} | [edit bridge-domains domain-name] | Enable the bridge domain to support enhanced scaling of ARP/ND unicast next hop entries. This
configuration allows the bridge domain to handle up to 1.5 million next hop entries for interfaces
configured within it.
Default
No default configuration. | [
{
"name": "domain-name: The name of the bridge",
"desc": "domain. Range: <domain-name> specifies the name of the bridge domain. Default: None Syntax: <domain-name> Values: Any valid bridge domain name."
}
] | admin: To view this statement in the configuration.
admin-control: To add this statement to the configuration. | [] | |
irb-symmetric-routing | irb-symmetric-routing {
vni vni;
} | [edit routing-instances name protocols evpn]
[edit routing-instances name protocols evpn interconnect] | Enable the symmetric IRB model of routing with EVPN Type 2 routes. You must specify the vni option
and a VXLAN network identifier (VNI) with this statement.
We support this statement in Layer 3 virtual routing and forwarding (VRF) instances on EVPN-VXLAN
devices with EVPN instances defined with MAC-VRF routing instance... | [
{
"name": "vni",
"desc": "(Mandatory) VNI used for EVPN Type 2 symmetric routing IP prefixes. Range: 1 through 16777214"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.3R1-S1 and 21.4R1 on QFX5210 switches only. | [
"Symmetric Integrated Routing and Bridging with EVPN Type 2 Routes in EVPN-VXLAN Fabrics"
] |
is-ma | (is-ma | no-is-ma); | [edit interfaces interface-name otn-options]
[edit dynamic-profiles name interfaces name optics-options],
[edit dynamic-profiles name logical-systems name interfaces name optics-options],
[edit interfaces name optics-options] | Specify whether masked alarms are enabled or disabled.
Default
If you omit the is-ma statement, masked alarms are disabled. | [
{
"name": "is-ma",
"desc": "Enable masked alarms."
},
{
"name": "no-is-ma",
"desc": "Do not enable masked alarms."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
isdn-options | isdn-options {
bchannel-allocation (ascending | descending);
calling-number number;
incoming-called-number number <reject>;
spid1 spid-string;
spid2 spid-string;
static-tei-val value;
switch-type (att5e | etsi | ni1 | ntdms100 | ntt);
t310 seconds;
tei-option (first-call | power-up);... | [edit interfaces br-pim/0/port],
[edit interfaces ct1-pim/0/port],
[edit interfaces ce1-pim/0/port] | For J Series Services Routers only. Specify the ISDN options for configuring ISDN interfaces for group
and user sessions.
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.
bchannel-allocation option added in Junos OS Release 8.3. | [
"Configuring ISDN Physical Interface Properties",
"Allocating B-Channels for Dialout"
] |
isid | isid isid-number vlan-id-list vlan-ids {
source-bmac mac-address length
} | [edit routing-instances routing-instance-name service-groups service-group-name] | For IEEE 802.1ah provider backbone bridge (PBB) configurations, configure the service identifier (I-SID)
for the customer routing instance (I-component) service group. | [
{
"name": "isid",
"desc": "Service identifier. Enter an I-SID in the range from 256 through 16777214."
},
{
"name": "vlan-id-list [ vlan-ids ]",
"desc": "List of service VLANs (S-VLANs)."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in JUNOS Release 10.0. | [] |
isid-list | isid-list all-service-groups; | [edit interfaces pseudo-logical-interface-name unit logical-unit-number family bridge] | For IEEE 802.1ah provider backbone bridge (PBB) configurations, map all service identifiers (I-SIDs)
specified for the service groups. | [
{
"name": "all-service-groups",
"desc": "Map all service identifiers (I-SIDs) for the specified service groups."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in JUNOS Release 10.0. | [] |
isis | isis { ... } | [edit logical-systems logical-system-name protocols],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit protocols],
[edit routing-instances routing-instance-name protocols] | Enable IS-IS routing on the routing device or for a routing instance.
The isis statement is the one statement you must include in the configuration to run IS-IS on the routing
device or in a routing instance.
Default
IS-IS is disabled on the routing device. | [] | 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 IS-IS",
"Example: Configuring a Multi-Level IS-IS Topology to Control Interarea Flooding"
] |
isis-instance | isis-instance igpinstance-name{
instance-id instance-id-value itid-disable;
} | [edit logical-systems logical-system-name protocols],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit protocols] | Enable multiple IGP instances of IS-IS routing on the routing device.
The isis-instance statement is the one statement you must include in the configuration to run multiple
IS-IS on the routing device.
Enabling IS-IS on an interface (by including the interface statement at the [edit protocols isis-instance
igpinstance-... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1. | [
"How to Configure Multiple Independent IGP Instances of IS-IS"
] |
iso-vpn | iso-vpn {
unicast {
prefix-limit number;
rib-group group-name;
}
} | [edit protocols bgp family],
[edit protocols bgp group group-name family],
[edit protocols bgp group group-name neighbor address family],
[edit routing-instances routing-instance-name protocols bgp family],
[edit routing-instances routing-instance-name protocols bgp group group-name family],
[edit routing-instances rou... | Enable BGP to carry ISO VPN NLRI messages between PE routes connecting a VPN.
The remaining statements are explained separately in this chapter.
Default
Disabled. | [] | 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 for CLNS VPNs",
"Understanding BGP for CLNS VPNs"
] |
isolated | isolated; | [edit vlans vlan-name interfaces interface-name] | Configure an access or trunk port to be isolated. You configure a trunk port to be isolated so that it can
be a secondary VLAN trunk port–that is, it can carry secondary VLAN traffic. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Creating a Private VLAN on a Single QFX Switch without ELS Support",
"Creating a Private VLAN Spanning Multiple QFX Series Switches without ELS Support",
"Example: Configuring PVLANs with Secondary VLAN Trunk Ports and Promiscuous Access Ports on a",
"QFX Series Switch"
] |
isolated-vlan (MX Series) | isolated-vlan vlan-id; | [edit bridge-domains bridge-domain-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name bridge-domains
bridge-domain-name bridge-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name bridge-domains
bridge-domain-name,
[edit routing-instances ro... | Configure the specified isolated VLAN to be a secondary VLAN of the specified primary VLAN. An
isolated VLAN receives packets only from the primary VLAN and forwards frames upstream to the
primary VLAN.
NOTE: When you specify this configuration statement, the VLAN ID of a logical
interface that you associate with a bri... | [
{
"name": "vlan-id",
"desc": "Individual VLAN IDs separated by a space."
}
] | system—To view this statement in the configuration.
system–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
isolated-vlan | isolated-vlan vlan-name isolated-vlan-name vlan-id isolated-vlan-id; | [edit vlans primary-vlan-name vlan-id primary-vlan-vlan-id] | Configure the specified isolated VLAN to be a secondary VLAN of the specified primary VLAN. An
isolated VLAN receives packets only from the primary VLAN and forwards frames upstream to the
primary VLAN.
NOTE: Before you specify this configuration statement, you must have already
configured an isolated VLAN and assigned... | [] | system—To view this statement in the configuration.
system–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10. | [
"Creating a Private VLAN on a Single Switch with ELS Support (CLI Procedure)",
"Creating a Private VLAN Spanning Multiple EX Series Switches with ELS Support (CLI Procedure)"
] |
isolation-id | isolation-id number; | [edit vlans vlan-name vlan-id number] | Configure an inter-switch isolated VLAN within a private VLAN (PVLAN) that spans multiple switches. | [
{
"name": "number",
"desc": "VLAN tag identifier."
}
] | 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. | [
"Creating a Private VLAN Spanning Multiple EX Series Switches (CLI Procedure)"
] |
isolation-vlan-id | isolation-vlan-id number; | [edit vlans vlan-name pvlan] | Configure an interswitch isolated VLAN within a private VLAN that spans multiple switches. | [
{
"name": "number",
"desc": "VLAN tag identifier."
}
] | routing—To view this statement in the configuration.
routing–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Creating a Private VLAN on a Single QFX Switch without ELS Support",
"Creating a Private VLAN Spanning Multiple QFX Series Switches without ELS Support"
] |
iteration-count | iteration-count count-value; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain md-name maintenance-
association ma-name mep mep-id remote-mep remote-mep-id sla-iterator-profile profile-name] | Configure the number of iterations for which the connection partakes in the iterator for acquiring SLA
measurements. | [
{
"name": "count-value",
"desc": "Number of iterations for which the connection should partake in the iterator for acquiring"
}
] | Configure—To enter configuration mode.
Control—To modify any configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring a Remote MEP with an Iterator Profile"
] |
iteration-period | iteration-period iteration-period-value; | [edit protocols oam ethernet connectivity-fault-management performance-monitoring sla-iterator-profiles
profile-name] | Configure the iteration period, which is the maximum number of cycles per iteration (that is, the number
of connections registered to an iterator cannot exceed this value). | [
{
"name": "iteration-period-value",
"desc": "Maximum number of cycles per iteration."
}
] | Configure—To enter configuration mode.
Control—To modify any configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring an Iterator Profile",
"Configure an Iterator Profile on a Switch (CLI Procedure)"
] |
ivacl-firewall-no-portrange-profile | ivacl-firewall-no-portrange-profile | [edit chassis] | Optimize and merge IVACL VxLAN and IVACL groups.
NOTE: When this configuration statement is enabled, source-port-range-optimize and
destination-port-range-optimize should not be used for IVACL filters. | [] | interface-control | Statement introduced in Junos OS Release 22.2R1 | [] |
ivlan-cfi (RFC 2544 Benchmarking) | ivlan-cfi; | [edit services rpm rfc2544-benchmarkingtests test-name test-name] | CFI bit to be used in the inner VLAN header of the frames generated. | [] | 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. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
ivlan-id (RFC 2544 Benchmarking) | ivlan-id number; | [edit services rpm rfc2544-benchmarkingtests test-name test-name] | Configure the inner VLAN ID for the test frames. This parameter is applicable for dual-tagged packets. | [
{
"name": "number",
"desc": "VLAN ID number. Range: 0 through 4094"
}
] | 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. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
ivlan-priority (RFC 2544 Benchmarking) | ivlan-priority value; | [edit services rpm rfc2544-benchmarking tests test-name test-name] | Configure the priority value for the IEEE 802.1p bit in the inner VLAN tag. This parameter is valid only
for a bridge family for an Ethernet LAN (ELAN) or an Ethernet Line (E-LINE) service. | [
{
"name": "value",
"desc": "IEEE 802.1p priority value in the inner VLAN tag Range: 0 through 7"
}
] | 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. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
iwf-params (tdm-options) | iwf-params {
decap-ecid value;
encap-ecid value;
} | [edit interfaces interface-name tdm-options] | Configure TDM interworking functionality (IWF) parameters. You can configure these parameters to
support multiple streams.
Default
If you do not specify an emulation circuit id, the default emulation circuit id for decapsulation and
encapsulation is 0. You cannot configure multiple streams if the emulation circuit id ... | [
{
"name": "decap-ecid value",
"desc": "Emulation circuit id for de-encapsulation. Possible values: 0 through 1048575."
},
{
"name": "encap-ecid value",
"desc": "Emulation circuit id for encapsulation. Possible values: 0 through 1048575."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4. | [
"J"
] |
jdaf | jdaf {
routing-instances [ routing-instance-names ];
} | [edit services] | Configure Juniper distributed application framework (JDAF).
The remaining statements are explained separately. See CLI Explorer. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [] |
jeb | jeb {
max-seed-size max-seed-size;
port port;
rbg (default-rng | hmac-drbg);
tls {
cert-bundle cert-bundle;
certificate certificate;
key key;
}
} | [edit system services] | Configure a Juniper Entropy Beacon (JEB) server. JEB can be used to feed high quality entropy over the
network from a SRX345 Firewall to entropy-starved clients. | [
{
"name": "max-seed-",
"desc": ""
},
{
"name": "size",
"desc": "Maximum allowed size in bytes for a requested entropy seed Default: 4096 Range: 1 through 65536"
},
{
"name": "port",
"desc": "Port to use for JEB service Default: 57005 Range: 1025 through 65535"
},
{
"name"... | admin | Statement introduced in Junos OS Release 19.1R1. | [] |
jflow-log (Interfaces) | jflow-log {
message-rate-limit messages-per-second;
} | [edit interfaces interface-name services-options] | Configure generation of log messages or template records in flow monitoring format for NAT error
events. These records for NAT error events are generated when addresses for allocation from the NAT
pool are not available, when ports for allocation to a subscriber are not available, or when the allocated
quota is exceede... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding NAT Event Logging in Flow Monitoring Format on an MX Series Router or NFX250",
"Configuring Log Generation of NAT Events in Flow Monitoring Record Format on an MX Series",
"Router or NFX250",
"Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats",
"Exa... |
jflow-log (Services) | jflow-log {
collector collector-name {
source-ip address;
destination-address address;
destination-port port-number;
}
collector-group collector-group-name {
[collector-name1 collector-name2];
}
template-profile template-profile-name {
collector collector-nam... | [edit services] | Enable the mechanism to record logging messages in flow monitoring format for NAT events. For this
transmission of flow monitoring logs to work properly, the services PIC interface must have an IP
address and appropriate logging options configured.
You can configure MX Series routers with MS-MPCs and MS-MICs to log net... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R2. | [
"Understanding NAT Event Logging in Flow Monitoring Format on an MX Series Router or NFX250",
"Configuring Log Generation of NAT Events in Flow Monitoring Record Format on an MX Series",
"Router or NFX250",
"Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats",
"Exa... |
jnu-management | jnu-management {
authentication authentication;
controller controller;
device-group device-group;
device-group-map name {
include-groups [ include-groups ... ];
}
mode(bng-control-plane | feature-rich);
other-controller;
satellite name {
device-group device-group;
... | [edit chassis] | JNU Management configuration. | [
{
"name": "authentication",
"desc": "Authentication string Option not applicable for Connected Security Distributed Services (CSDS)."
},
{
"name": "controller",
"desc": "Controller Name"
},
{
"name": "device-group",
"desc": "Satellite device group Option not applicable for CSDS."
}... | [none specified] | Support for other-controller option is added for CSDS in Junos OS Release 24.4R1.
Statement introduced in Junos OS Release 21.3R1. | [] |
join-load-balance | join-load-balance {
automatic;
} | [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] | Enable load balancing of PIM join messages across interfaces and routing devices. | [
{
"name": "automatic",
"desc": "Enables automatic load balancing of PIM join messages. When a new interface or neighbor is introduced into the network, ECMP joins are redistributed with minimal disruption to traffic."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Example: Configuring PIM Make-Before-Break Join Load Balancing",
"Configuring PIM Join Load Balancing"
] |
join-prune-timeout | join-prune-timeout seconds; | [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] | Configure the timeout for the join state. If the periodic join refresh message is not received before the
timeout expires, the join state is removed. | [
{
"name": "seconds",
"desc": "Number of seconds to wait for the periodic join message to arrive."
}
] | 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. | [
"Modifying the Join State Timeout"
] |
join-timer (MVRP) | join-timer milliseconds; | [edit logical-systems logical-system-name protocols mvrp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols mvrp
interface (all | interface-name)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
mvrp],
[edit logical-systems logica... | Configure the maximum number of milliseconds interfaces must wait before sending Multiple VLAN
Registration Protocol (MVRP) protocol data units (PDUs).
Maintain default timer settings unless there is a compelling reason to change the settings. Modifying
timers to inappropriate values might cause an imbalance in the op... | [
{
"name": "milliseconds",
"desc": "Interval that the interface must wait before sending MVRP PDUs (range from 100"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Example: Configuring Automatic VLAN Administration Using MVRP on MX Series Routers",
"Example: Configuring Automatic VLAN Administration Using MVRP on EX Series Switches",
"Configuring Multiple VLAN Registration Protocol (MVRP) to Manage Dynamic VLAN Registration",
"Configuring Multiple VLAN Registration Pro... |
json | json {
reorder-list-keys;
} | [edit system configuration input format] | Configure parameters for Junos configuration data in JavaScript Object Notation (JSON) format. | [
{
"name": "reorder-list-keys",
"desc": "When you load JSON configuration data on the device, reorder list entries so that list keys precede other siblings and appear in the order required by the schema. Configuring this option enables you to load JSON configuration data that contains unordered list entries,... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.1R1 and Junos OS Evolved Release 22.1R1. | [
"Load JSON Configuration Data With Unordered List Entries"
] |
jsrc (Access Profile) | jsrc {
attributes {
exclude {
user-name [ authorization-request | provisioning-request ];
}
}
}
} | [edit access profile profile-name] | Specify JSRC settings in an access 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. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"JSRC Configuration Overview",
"Authorizing Subscribers with JSRC",
"Understanding JSRC-SAE Interactions",
"Excluding AVPs from Diameter Messages for JSRC"
] |
jsrc (JSRC) | jsrc {
dualstack-support;
partition partition-name {
diameter-instance instance-name;
destination-host hostname;
destination-realm realm-name;
}
} | [edit] | Configure JSRC to interact with an SAE in an SRC environment to authorize and provision subscribers.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"JSRC Configuration Overview"
] |
jsrc-partition | jsrc-partition partition-name; | [edit] | Specify the JSRC partition to use. | [
{
"name": "partition-name",
"desc": "Name of the JSRC partition that you want JSRC to use. The name is defined with the"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"JSRC Configuration Overview",
"Configuring the JSRC Partition"
] |
juniper-enhanced | juniper-enhanced {
cache {
size value;
timeout value;
}
profile profile-name {
category customurl-list name {
action (block | log-and-permit | permit | quarantine);
}
custom-block-message value;
custom-quarantine-message value;
default (b... | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering] | Configure the Content Security Enhanced Web Filtering feature. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
The proxy-profile option is introduced under the security utm default-configuration web-filtering juniper-
enhanced server hierarchy level in Junos OS Release 18.3R1. | [
"Web Filtering Overview"
] |
juniper-express-engine | juniper-express-engine {
pattern-update {
email-notify {
admin-email email-address;
custom-message message;
custom-message-subject message-subject;
}
interval value;
no-autoupdate;
proxy {
password password-string;
p... | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus] | Configure the Content Security express antivirus feature. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express Antivirus feature is not supported from Junos OS Release 15.1X49-D10 onwards. For
previous releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Express Antivirus Configuration Overview"
] |
juniper-local | juniper-local {
profile profile-name {
block-message (Security UTM) value;
default (Security Web Filtering) (block | log-and-permit | permit);
fallback-settings (Security Web Filtering) {
default (Security Web Filtering) (block | log-and-permit);
server-connectivity (... | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering] | Configure the Content Security Web-filtering local feature. | [
{
"name": "no-safe-search",
"desc": "Disable the safe search function."
}
] | 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.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
no-safe-search option added in Junos OS Release 20.2R1.
K
IN THIS SECTION | [] |
kaspersky-lab-engine | kaspersky-lab-engine {
pattern-update {
email-notify {
admin-email email-address;
custom-message message;
custom-message-subject message-subject;
}
interval value;
no-autoupdate;
proxy {
password password-string;
por... | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus] | Configure the Content Security full file-based antivirus feature. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Kaspersky Antivirus feature is not supported from Junos OS Release 15.1x49-D10 onwards. For
previous releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
keep | keep (all | none); | [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 bg... | Control whether or not Junos OS keeps in memory and hides certain routes.
If the keep none statement is used, Junos OS does not retain in memory and hide routes that are rejected
because of a BGP import policy. Nor does BGP keep in memory and hide routes that are declared
unfeasible due to BGP sanity checks. The keep n... | [
{
"name": "all",
"desc": "Retain all routes."
},
{
"name": "none",
"desc": "Discard routes that were received from a peer and that were rejected by import policy or other"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Routing Policies to Control BGP Route Advertisements",
"Interprovider VPN Example—MP-EBGP Between ISP Peer Routers",
"Example: Configuring a Routing Policy for Conditional Advertisement Enabling Conditional",
"Installation of Prefixes in a Routing Table"
] |
keep-address-and-control | keep-address-and-control; | [edit interfaces interface-name unit logical-unit-number family ccc],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family ccc] | For interfaces with encapsulation type PPP CCC, do not remove the address and control bytes before
encapsulating the packet into a tunnel.
Default
If you do not include this statement, address and control bytes are removed before encapsulating the
packet into a tunnel. | [] | 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. | [
"Disabling the Removal of Address and Control Bytes"
] |
keep-alive (Protocols MSDP) | keep-alive seconds; | [edit logical-systems logical-system-name protocols msdp],
[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 logical-system-name routing-instances instance-name protocols msdp],
[edit log... | Specify the keepalive interval to use when maintaining a connection with the MSDP peer. If a keepalive
message is not received for the hold-time period, the MSDP peer connection is terminated. According to
the RFC 3618, Multicast Source Discovery Protocol (MSDP), the recommended value for the keepalive
timer is 60 seco... | [
{
"name": "seconds",
"desc": "Keepalive interval."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Examples: Configuring MSDP"
] |
keep-existing-steering | keep-existing-steering; | [edit unified-edge pcef pcc-action-profiles profile-name steering],
[edit services pcef pcc-action-profiles profile-name] | Specify that the PCC action profile steering attributes that a PCC rule applies at the start of a data flow
will continue to be applied to that data flow when the PCC rule match conditions are modified, deleted,
or added to. | [] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef pcc-action-profiles profile-name] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series.
Support for Next Gen Services for Junos OS Broadband Subscriber Management introduced in Juno... | [
"Understanding Application-Aware Policy Control for Subscriber Management",
"Configuring Policy and Charging Control Action Profiles for Subscriber Management",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Configuring Policy and Charging Control Action ... |
keep-incoming-circuit-id (DHCP Relay Agent) | keep-incoming-circuit-id ; | [edit forwarding-options dhcp-relay relay-option-82 circuit-id],
[edit logical-systems logical-system-name forwarding-options dhcp-relay relay-option-82 circuit-
id],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options dhcp-relay relay-option-82 circuit-id],
[edit routi... | Specify that the jdhcpd process keeps the incoming circuit ID and prepends the ID with the locally
generated ID (in the format, generated-id + incoming-id) before sending the leasequery packet to the DHCP
server.
This configuration is required for leasequery and bulk leasequery operations when subscriber
authentication... | [] | 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. | [
"Using DHCP Relay Agent Option 82 Information"
] |
keep-incoming-interface-id (DHCP Relay Agent) | keep-incoming-interface-id ; | [edit forwarding-options dhcp-relay dhcpv6 relay-agent-interface-id],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6 relay-agent-
interface-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options dhcp-relay dhcpv6 relay-agent-interface-... | Specify that the jdhcpd process keeps the incoming interface ID and prepends the ID with the locally
generated ID (in the format, generated-id + incoming-id) before sending the leasequery packet to the
DHCPv6 server.
This configuration is required for leasequery and bulk leasequery operations when subscriber
authentica... | [] | 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. | [
"Inserting DHCPv6 Interface-ID Option (Option 18) In DHCPv6 Packets"
] |
keep-incoming-remote-id (DHCP Relay Agent) | keep-incoming-remote-id ; | [edit forwarding-options dhcp-relay dhcpv6 relay-agent-remote-id],
[edit forwarding-options dhcp-relay relay-option-82 circuit-id],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6 relay-agent-remote-
id],
[edit logical-systems logical-system-name forwarding-options dhcp-relay relay-option... | Specify that the jdhcpd process keeps the incoming remote ID and prepends the ID with the locally
generated ID (in the format, generated-id + incoming-id) before sending the leasequery packet to the
DHCPv6 server.
This configuration is required for leasequery and bulk leasequery operations when subscriber
authenticatio... | [] | 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. | [
"Using DHCP Relay Agent Option 82 Information",
"Inserting DHCPv6 Interface-ID Option (Option 18) In DHCPv6 Packets"
] |
keep-multiplier | keep-multiplier number; | [edit logical-systems logical-system-name protocols rsvp],
[edit protocols rsvp] | Specify a value used by RSVP to calculate timer values for network outages, and declare that a
reservation or a neighbor is down. It indicates the number of messages that can be lost before a
particular state is declared stale and must be deleted. The keep multiplier directly affects the lifetime of
an RSVP state.
Star... | [
{
"name": "number",
"desc": "Multiplier value."
}
] | 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 Timers for RSVP Refresh Messages"
] |
keepalive | keepalive seconds; | [edit access group-profile profile-name ppp],
[edit access profile profile-name client client-name ppp] | Configure the keepalive interval for an L2TP tunnel. | [
{
"name": "seconds",
"desc": "Time period that must elapse before the Junos OS checks the status of the Point-to-Point"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Layer 2 Tunneling Protocol (L2TP)",
"L2TP LNS Inline Service Interfaces"
] |
keepalive-interval | keepalive-interval seconds; | [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] | Set the keepalive interval value. | [
{
"name": "seconds",
"desc": "Keepalive value."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Interval for LDP Keepalive Messages"
] |
keepalive-retries | keepalive-retries number-of-retries; | [edit access profile profile-name client client-name ppp] | Configure the number of retry attempts for checking the keepalive status of a Point-to-Point (PPP)
protocol session. Configure this setting to reduce the detection time for PPP client session timeouts or
failures if you have configured the keepalive timeout interval (using the keepalive statement). | [
{
"name": "number-of-retries",
"desc": "The maximum number of retries the L2TP network server (LNS) attempts by sending"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Point-to-Point Protocol (PPP)"
] |
keepalive-time (Chassis) | keepalive-time seconds; | [edit chassis redundancy] | Configure the time period that must elapse before the backup router takes primary role when it detects
loss of the keepalive signal.
Default
The on-loss-of-keepalives statement at the [edit chassis redundancy failover] hierarchy level must be
included for failover to occur.
When the on-loss-of-keepalives statement is i... | [
{
"name": "seconds",
"desc": "Time before the backup router takes primary role when it detects loss of the keepalive signal."
}
] | 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. | [
"On Detection of a Loss of Keepalive Signal from the Primary Routing Engine",
"High Availability Features for EX Series Switches Overview"
] |
keepalive-time (Protocols OAM) | keepalive-time seconds; | [edit protocols oam gre-tunnel interface interface-name],
[edit protocols oam gre-tunnel interface interface-name.unit-number] | Time difference between consecutive keepalive packets in a GRE tunnel.
NOTE: Support for GRE keepalive packets on MPC line cards became available as of
Junos OS Release 11.4. | [
{
"name": "seconds",
"desc": "Keepalive time value."
}
] | 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 19.3 for MPC10E line card. | [
"Configuring Tunnel Interfaces on an MX Series Router with a 16x10GE 3D MPC",
"Configuring GRE Keepalive Time"
] |
keepalive-time (Protocols BGP) | keepalive-time keepalive-time; | [edit fabric protocols bgp],
[edit logical-systems name protocols bgp],
[edit logical-systems name routing-instances name protocols bgp],
[edit logical-systems name tenants name routing-instances name protocols bgp],
[edit protocols bgp],
[edit routing-instances name protocols bgp],
[edit tenants name routing-instances... | Override the BGP keepalive time derived from the hold-time. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [] |
keepalive-timeout | keepalive-timeout seconds; | [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] | Set the keepalive timeout value. The keepalive timeout defines the amount of time that the neighbor
LDP node waits before determining that the session has failed. | [
{
"name": "seconds",
"desc": "Keepalive timeout value."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the LDP Keepalive Timeout"
] |
keepalives (Dynamic Profiles) | keepalives {
interval seconds;
} | [edit dynamic-profiles profile-name interfaces pp0 unit logical-unit-number],
[edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit],
[edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit] | Specify the keepalive interval in a PPP dynamic profile.
Starting in Junos OS Release 15.1R5, you can configure the PPP keepalive interval for subscriber
services in the range 1 second through 600 seconds. Subscriber PPP keepalives are handled by the
Packet Forwarding Engine. If you configure a value greater than 600 s... | [
{
"name": "interval seconds",
"desc": "The time in seconds between successive keepalive requests."
}
] | 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”] hierarchy level
introduced in Junos OS Release 10.1.
Support at the [edit dynamic-profiles profile-name interfaces "$junos-interface-ifd-name" unit “$junos-
interface-unit”] hier... | [
"Dynamic Profiles Overview",
"Configuring Dynamic Authentication for PPP Subscribers",
"Applying PPP Attributes to L2TP LNS Subscribers per Inline Service Interface"
] |
keepalives | keepalives <interval seconds> <down-count number> <up-count number>; | [edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Enable the sending of keepalives on a physical interface configured with PPP, Frame Relay, or Cisco
HDLC encapsulation.
For ATM2 IQ interfaces only, you can enable keepalives on a logical interface unit if the logical interface
is configured with one of the following PPP over ATM encapsulation types:
•
atm-ppp-llc—PPP ... | [
{
"name": "down-count number",
"desc": "The number of keepalive packets a destination must fail to receive before the network"
},
{
"name": "interval seconds",
"desc": "The time in seconds between successive keepalive requests."
},
{
"name": "up-count number",
"desc": "The number of ... | 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 Keepalives",
"Configuring Frame Relay Keepalives",
"Applying PPP Attributes to L2TP LNS Subscribers per Inline Service Interface"
] |
kernel-replication | kernel-replication {
no-multithreading;
system-reboot recovery-failure;
} | [edit system] | Configure kernel replication. Use this configuration statement to debug the kernel synchronization
process (ksyncd) and configure automatic recovery from ksyncd initialization errors. | [
{
"name": "no-multithreading",
"desc": "-(Optional) Run ksyncd in single thread mode for debugging purposes."
},
{
"name": "system-reboot recovery-failure",
"desc": "-(Optional) Configure the backup RE to automatically reboot if a ksyncd initialization error is detected."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1. | [
"Understanding Graceful Routing Engine Switchover"
] |
key (Authentication Keychain) | key key-identifier {
algorithm (hmac-sha-1 | md5);
key-name authentication-key-name;
options (basic | isis-enhanced);
secret secret-data;
start-time yyyy-mm-dd.hh:mm:ss;
} | [edit security authentication-key-chains key-chain key-chain-name] | Configure an authentication element (key). You include this statement several times in the configuration,
thereby creating a keychain of authentication keys, each with its own identifier, secret (password), and
start time. You can have up to 64 keys within a keychain. | [
{
"name": "key-identifier",
"desc": "(Required) Each key within a keychain is identified by a unique integer value. Range: 0 through 63"
},
{
"name": "algorithm (hmac-sha-1 | md5)",
"desc": "Configure the authentication algorithm for IS-IS. Values: Configure one of these authentication algorit... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6.
Support for the BFD protocol introduced in Junos OS Release 9.6.
Support for IS-IS introduced in Junos OS Release 11.2.
algorithm and options introduced in Junos OS Release 11.2.
key-name introduced in Junos OS Release 17.4. | [
"Configuring the Authentication Key Update Mechanism for BGP and LDP Routing Protocols",
"Example: Configuring BFD Authentication for Securing Static Routes",
"Example: Configuring Hitless Authentication Key Rollover for IS-IS",
"Understanding Hitless Authentication Key Rollover for IS-IS",
"Configuring Med... |
key (gre) | key number; | [edit interfaces interface-name unit logical-unit-number tunnel],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
tunnel] | Identify an individual traffic flow within a tunnel, as defined in RFC 2890, Key and Sequence Number
Extensions to GRE. On M Series and T Series routers, you can configure the GRE interface on an
Adaptive Services, Multiservices, or Tunnel PIC. On MX Series routers, configure the interface on a
Multiservices DPC. | [
{
"name": "number",
"desc": "Value of the key."
}
] | 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 a Key Number on GRE Tunnels"
] |
key (interfaces) | key number; | [edit interfaces interface-name unit logical-unit-number tunnel],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
tunnel] | For Adaptive Services PICs on M Series routers (except the M320 and M120 routers), identify an
individual traffic flow within a tunnel, as defined in RFC 2890, Key and Sequence Number Extensions to
GRE. | [
{
"name": "number",
"desc": "Value of the key."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Junos OS Services Interfaces Library for Routing Devices"
] |
key (Junos FIPS) | key (ascii-text key | hexadecimal key); | [edit security ipsec internal security-association manual direction encryption] | The key used for the internal Routing-Engine–to–Routing-Engine IPsec security association (SA)
configuration. | [
{
"name": "ascii-text-key",
"desc": "The encrypted ASCII text key."
},
{
"name": "hexadecimal key",
"desc": "The encrypted hexadecimal key."
}
] | Crypto Officer—To add and view this statement in 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.