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 |
|---|---|---|---|---|---|---|---|
key (MACsec for MX Series) | key key-string; | [edit security macsec connectivity-association connectivity-association-name secure-channel
secure-channel-name security-association security-association-number] | Specifies the static security key to exchange to enable MACsec using static secure association key (SAK)
security mode.
The key string is a 32-digit hexadecimal number. The key string and the security association must match
on both sides of an Ethernet connection to secure traffic using MACsec when enabling MACsec usin... | [
{
"name": "key-string",
"desc": "Specifies the key to exchange with the other end of the link on the secure channel. The key-string is a 32-digit hexadecimal string that is created by the user."
}
] | 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"
] |
key (MACsec) | key key-string; | [edit security macsec connectivity-association connectivity-association-name secure-channel secure-
channel-name security-association security-association-number] | Specifies the static security key to exchange to enable MACsec using static secure association key (SAK)
security mode.
The key string is a 32-digit hexadecimal number. The key string and the security association must match
on both sides of an Ethernet connection to secure traffic using MACsec when enabling MACsec usin... | [
{
"name": "key-string",
"desc": "Specifies the key to exchange with the other end of the link on the secure channel. The key-string is a 32-digit hexadecimal string that is created by the user."
}
] | 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. | [
"Configuring MACsec on EX, QFX and SRX Devices"
] |
key | key number; | [edit interfaces ftinumber unit logical-unit-number tunnel encapsulation ( gre | ipip | udp )] | Key for configuring the tunnel. Identifies an individual traffic flow within a tunnel. | [
{
"name": "number",
"desc": "An identifier for a individual traffic flow within a GRE tunnel. Range: 1 through 65535."
}
] | interface | Statement introduced in Junos OS Evolved Release 20.2R1.
Statement introduced for IPIP tunnels in Junos OS Evolved Release 20.4R1.
Statement introduced for UDP tunnels in Junos OS Evolved Release 21.1R1. | [] |
key-chain (Authentication Keychain) | key-chain key-chain-name {
description text-string;
key key {
algorithm (md5 | hmac-sha-1);
options (basic | isis-enhanced);
key-name authentication-key-name;
secret secret-data;
start-time yyyy-mm-dd.hh:mm:ss;
}
tolerance seconds;
} | [edit security authentication-key-chains] | Create the key-chain configuration for the Border Gateway Protocol (BGP) and the Label Distribution
Protocol (LDP) routing protocols, the Bidirectional Forwarding Detection (BFD) protocol, and the
Intermediate System-to-Intermediate System (IS-IS) protocol. | [
{
"name": "key-chain-name",
"desc": "Authentication keychain name. It can be up to 32 characters. Characters can include any ASCII strings. If you include spaces, enclose all characters in quotation marks (“ ”)."
},
{
"name": "description text-string",
"desc": "Configure the description for this... | security—To view this statement in the configuration.
security-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 the BFD protocol introduced in Junos OS Release 9.6 for EX Series switches.
Support for IS-IS introduced in Junos OS Release 11.2. | [
"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",
"Configuring Media Access Control Security (MACsec) on Routers"
] |
key-chain (Protocols PIM) | key-chain key-chain-name; | [edit protocols pim interface interface-name family {inet | inet6} bfd-liveness-detection
authentication],
[edit routing-instances routing-instance-name protocols pim interface interface-name family
{inet | inet6} bfd-liveness-detection authentication] | Specify the security keychain to use for BFD authentication. | [
{
"name": "key-chain-name",
"desc": "Name of the security keychain to use for BFD authentication. The name is a unique"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6.
Statement modified in Junos OS Release 12.2 to include family in the hierarchy level. | [
"Configuring BFD Authentication for PIM",
"Understanding Bidirectional Forwarding Detection Authentication for PIM"
] |
key-exchange | key-exchange [algorithm1 algorithm2...]; | [edit system services ssh] | Specify the set of Diffie-Hellman key exchange methods that the SSH server can use. | [
{
"name": "curve25519-sha256",
"desc": "The EC Diffie-Hellman key exchange method on Curve25519 with SHA2-256."
},
{
"name": "dh-group1-sha1",
"desc": "The Diffie-Hellman group1 algorithm using SHA-1."
},
{
"name": "dh-group14-sha1",
"desc": "The Diffie-Hellman group14 algorithm usin... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. Support for the curve25519-sha256 option added in
Junos OS Release 12.1X47-D10.
dh-group16-sha, dh-group18-sha512, and 512sntrup761x25519-sha512 options added in Junos OS Evolved Release
25.4R1. | [
"Configuring SSH Service for Remote Access to the Router or Switch",
"Quantum Buffer for SSH"
] |
key-length | key-length number; | [edit protocols neighbor-discovery secure cryptographic-address] | Specify the length of the RSA key used to generate the public-private key pair for the cryptographic
address.
Default | [
{
"name": "number",
"desc": "RSA key length."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Secure IPv6 Neighbor Discovery"
] |
key-pair | key-pair pathname; | [edit protocols neighbor-discovery secure cryptographic-address] | Specify the directory path of the public-private key file generated for the cryptographic address.
A cryptographic address is dynamically generated based on a public key and a subnet prefix.
Default
The default location of the file is the /var/etc/rsa_key directory. | [
{
"name": "pathname",
"desc": "Directory path of the public-private key file."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Secure IPv6 Neighbor Discovery"
] |
key-server-priority (MACsec for MX Series) | key-server-priority priority-number; | [edit security macsec connectivity-association connectivity-association-name mka] | Specifies the key server priority used by the MACsec Key Agreement (MKA) protocol to select the key
server when MACsec is enabled using static connectivity association key (CAK) security mode.
The switch with the lower priority-number is selected as the key server.
If the priority-number is identical on both sides of a... | [
{
"name": "priority-number",
"desc": "Specifies the MKA server election priority number. The priority-number can be any number between 0 and 255. The lower the number, the higher the priority."
}
] | 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"
] |
key-server-priority (MACsec) | key-server-priority priority-number; | [edit security macsec connectivity-association connectivity-association-name mka] | Specifies the key server priority used by the MACsec Key Agreement (MKA) protocol to select the key
server when MACsec is enabled using static connectivity association key (CAK) security mode.
The switch with the lower priority-number is selected as the key server.
If the priority-number is identical on both sides of a... | [
{
"name": "priority-number",
"desc": "Specifies the MKA server election priority number. The priority-number can be any number between 0 and 255. The lower the number, the higher the priority."
}
] | 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)"
] |
krt-nexthop-ack | krt-nexthop-ack; | [edit logical-systems logical-system-name routing-options forwarding-table],
[edit routing-options forwarding-table] | When you configure this option, the routing protocol process (rpd) waits for the next hop to get
acknowledged by PFE before using it for a route.
Currently, only BGP-labeled routes and RSVP routes support this option. All other routes will ignore this
option. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.1. | [
"Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the Packet Forwarding",
"Engine"
] |
krt-nexthop-ack-timeout | krt-nexthop-ack-timeout interval; | [edit logical-systems logical-system-name routing-options forwarding-table],
[edit routing-options forwarding-table] | For indirect next-hop and multicast next-hop change acknowledgements, configure the time interval for
which to wait for the next-hop acknowledgement. The routing protocol process (rpd) waits for the
specified time period before changing the route to point to the new next hop.
If the acknowledgement is received before t... | [
{
"name": "interval",
"desc": "Kernel next-hop acknowledgement timeout 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.2. | [
"Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the Packet Forwarding",
"Engine",
"L"
] |
l2-channel-error-threshold (chassis) | l2-channel-error-threshold threshold; {
l2-channel-errors (ignore |red | yellow);
} | [edit chassis alarm l2-chan-err-ethernet] | Use this command to specify the threshold limit for the L2 error count. Range is 1 through 4294967295
per hour and default value is 50,000 per hour. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1. | [
"Chassis Conditions That Trigger Alarms"
] |
l2-channel-errors (chassis) | l2-channel-errors (ignore |red | yellow); | [edit chassis alarm l2-chan-err-ethernet] | Configure chassis alarm for L2 channel error. When you configure this statement, chassis raises an alarm
when the L2 channel error count crosses 50,000 per hour. If you do not configure this statement,
chassis do not raise any alarm for L2 channel errors. | [
{
"name": "ignore",
"desc": "This configuration does not raise any alarm for L2 channel error. This is the default configuration."
},
{
"name": "red",
"desc": "This configuration raises a red alarm for L2 channel error."
},
{
"name": "yellow",
"desc": "This configuration raises a red... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1. | [
"Chassis Conditions That Trigger Alarms"
] |
l2-domain-id-for-l3 | l2-domain-id-for-l3 id; | [edit routing-instances instance-name] | Specify a Layer 2 domain ID within a routing instance. | [
{
"name": "id",
"desc": "Layer 2 identification number."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3R2. | [
"Configuring a Layer 2 Virtual Switch on an EX Series Switch"
] |
l2-learning | l2-learning {
global-mac-limit limit {
packet-action-drop;
}
global-mac-table-aging-time seconds;
global-mode (switching | transparent-bridge) ;
global-no-mac-learning;
} | [edit protocols] | Configure Layer 2 (L2) address learning and forwarding properties globally.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "crb-proxy-mac",
"desc": "Configure proxy MAC address to be used in MAC-IP refresh. In the case of central routing and bridging deployments, you need to configure the crb-proxy-mac statement on all the leaf nodes. Use the following configuration to configure crb-"
},
{
"name": "proxy-mac C... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Statement modified in Junos OS Release 9.5. Support for global mode added in Junos OS Release
15.1X49-D40.
global-le-bridge-domain-aging-time option introduced in Junos OS Release 14.2R5 for the MX Series.
global-mac-ip-limit and global-mac-ip-table-aging-time options intro... | [
"Understanding Layer 2 Learning and Forwarding",
"global-mac-table-aging-time",
"global-mac-limit (Protocols)",
"global-no-mac-learning",
"global-mode (Protocols)"
] |
l2-querier | l2-querier {
source-address ip-address;
} | [edit protocols igmp-snooping vlan] | Configure the device to be an IGMP querier. IGMP querier allows the device to proxy for a multicast
router and send out periodic IGMP queries in the network. This action causes the device to consider
itself an multicast router port. The remaining devices in the network simply define their respective
multicast router po... | [
{
"name": "seconds",
"desc": "Time interval."
}
] | 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 IGMP Snooping on SRX Series Devices",
"IGMP Snooping Overview"
] |
l2-smart-policy | l2-smart-policy; | [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] | Prevent LDP from exporting IPv4 FECs over sessions with Layer 2 neighbors only. IPv4 FECs received
over such sessions are filtered out. | [] | 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. | [
"Configuring LDP IPv4 FEC Filtering"
] |
l2-stats (Flat-File Accounting Options) | l2-stats {
all-fields;
input-mcast-bytes;
input-mcast-packets;
} | [edit accounting-options flat-file-profile profile-name fields] | Specify the statistics to collect for the named flat-file-profile field. | [
{
"name": "all-fields",
"desc": "Collect all Layer 2 statistics for the named flat-file profile."
},
{
"name": "input-mcast-bytes",
"desc": "Collect multicast bytes from the input side for the named flat-file profile."
},
{
"name": "input-mcast-packets",
"desc": "Collect multicast pa... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R4. | [
"Configuring Flat-File Accounting for Layer 2 Wholesale",
"Configuring Flat-File Accounting for Extensible Subscriber Services Management",
"Flat-File Accounting Overview"
] |
l2circuit | l2circuit {
auto-sensing{
password password;
}
local-switching {
interface interface-name {
description text;
end-interface {
interface interface-name;
protect-interface interface-name;
}
ignore-mtu-mismatch;... | [edit logical-systems logical-system-name protocols],
[edit protocols] | 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... | [] | 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 ATM Trunking on Layer 2 Circuits",
"Configuring Bandwidth Allocation and Call Admission Control in Layer 2 Circuits",
"Configuring Interfaces for Layer 2 Circuits",
"Configuring LDP for Layer 2 Circuits",
"Configuring Policies for Layer 2 Circuits",
"Configuring Static Layer 2 Circuits",
"T... |
l2circuit-control-passthrough | l2circuit-control-passthrough; | [edit forwarding-options] | Configure the device to allow LACP, LLDP, OAM LFM, and OAM CFM packets to cross the Layer 2
circuit. If the l2circuit-control-passthrough statement is not configured, LACP, LLDP, OAM LFM, and OAM
CFM packets are classified as control packets and are not transmitted across the Layer 2 circuit.
NOTE: For MX Series router... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R1. | [
"Configuring Layer 2 Switching Cross-Connects Using CCC",
"Configuring an MPLS-Based VLAN CCC with Pop, Push, and Swap and Control Passthrough"
] |
l2ckt | l2ckt {
l2vpn;
l3vpn;
labeled-bgp;
no-l2vpn;
} | [edit logical-systems logical-system-name routing-options forwarding-table chained-composite-
next-hop ingress],
[edit routing-options forwarding-table chained-composite-next-hop ingress] | Enable composite chained next hop for ingress Layer 2 circuit label-switched paths (LSPs).
The remaining statements are explained separately. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [] |
l2iw | l2iw {
dynamic-peer-discovery;
traceoptions {
file filename <files number> <size size> <world-readable | no-world-readable>;
flag flag <flag-modifier>;
}
} | [edit logical-systems name protocols],
[edit protocols] | Enable Layer 2 interworking on a device. | [
{
"name": "dynamic-peer-",
"desc": ""
},
{
"name": "discovery",
"desc": "Create Layer 2 interwork peers dynamically. When you enable this feature, you do not need to configure a logical peer unit manually. Dynamic peer discovery matches the"
},
{
"name": "following configured settings as... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.2R1
dynamic-peer-discovery introduced in Junos OS Evolved Release 25.4 on UFISPACE-S9600-32X,
UFISPACE-S9600-72XC, and UFISPACE-S9600-102XC. | [] |
l2pt (Destination Tunnels) | l2pt {
interface name {
destination {
vxlan-tunnel;
}
enable-all-ifl;
protocol {
all;
cdp;
elmi;
gvrp;
ieee8021x;
ieee8023ah;
lacp;
lldp;
mmrp;
mvrp;
... | [edit protocols layer2-control] | Enable Layer 2 (L2) protocol tunneling (L2PT) across the encapsulation tunnels in an EVPN network.
Use this statement to enable a device to receive protocol control frames coming in on an access
interface and tunnel those frames across the encapsulation tunnels on the device. Configure this
statement with the interface... | [
{
"name": "interface name",
"desc": "(Required) Interface name on which to enable L2PT across a destination tunnel type on the device. The interface can be a physical interface or an aggregated Ethernet (AE) interface."
},
{
"name": "destination",
"desc": ""
},
{
"name": "tunnel-type",
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.2R1. | [
"Layer 2 Protocol Tunneling over VXLAN Tunnels in EVPN-VXLAN Bridged Overlay Networks"
] |
l2tp (DDoS Protection) | l2tp {
aggregate {
bandwidth packets per second;
burst packets;
disable-fpc;
disable-logging;
disable-routing-engine;
flow-detection-mode(automatic | off | on);
flow-detect-time seconds;
flow-level-bandwidth {
logical-interface packets per second;
physical-interface packets ... | [edit system ddos-protection protocols] | Configure L2TP traffic. | [
{
"name": "> aggregate",
"desc": "Configure aggregate for all L2TP control traffic"
},
{
"name": "+ apply-groups",
"desc": "Groups from which to inherit configuration data"
},
{
"name": "+ apply-groups-except",
"desc": "Don't inherit configuration data from these groups"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos Evolved OS Release 23.4R1. | [] |
l2tp (Group Profile) | l2tp {
interface-id interface-id;
lcp-renegotiation;
local-chap;
maximum-sessions-per-tunnel number;
} | [edit access group-profile profile-name] | Configure the Layer 2 Tunneling Protocol for a group profile.
NOTE: This statement is not supported for L2TP LNS on MX Series routers. | [] | 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"
] |
l2tp (Profile) | l2tp {
interface-id interface-id;
lcp-renegotiation;
local-chap;
maximum-sessions number;
maximum-sessions-per-tunnel number;
multilink {
drop-timeout milliseconds;
fragment-threshold bytes;
}
override-result-code session-out-of-resource;
ppp-authentication (chap | pa... | [edit access profile profile-name client client-name] | Configure the L2TP properties for a profile.
NOTE: Only the interface-id, lcp-renegotiation, maximum-sessions, maximum-sessions-per-tunnel,
sessions-limit-group and shared-secret statements are supported for L2TP LNS on MX
Series routers. | [
{
"name": "interface-id",
"desc": "Configure the interface identifier. Values:"
},
{
"name": "interface-id",
"desc": "Identifier for the interface representing a Layer 2 Tunneling"
},
{
"name": "lcp-renegotiation",
"desc": "Configure the L2TP network server (LNS) so it renegotiates ... | 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",
"L2TP for Subscriber Access Overview"
] |
l2tp | l2tp {
access-line-information <connection-speed-update>;
destination {
address ip-address {
access-line-information <connection-speed-update>;
drain;
routing-instance routing-instance-name {
drain;
}
}
lockout-timeout secon... | [edit services] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for LAC on MX Series routers introduced in Junos OS Release 10.4.
Support for LNS on MX Series routers introduced in Junos OS Release 11.4. | [
"Layer 2 Tunneling Protocol Overview",
"L2TP for Subscriber Access Overview"
] |
l2tp-access-profile | l2tp-access-profile profile-name; | [edit services l2tp tunnel-group name] | Specify the profile used to validate all L2TP connection requests to the local gateway address. | [
{
"name": "profile-name",
"desc": "Identifier for the L2TP connection profile."
}
] | 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 Access Profiles for L2TP Tunnel Groups",
"Configuring an L2TP Access Profile on the LNS"
] |
l2tp-interface-id | l2tp-interface-id name;
(dedicated | shared); | [edit interfaces sp-fpc/pic/port unit logical-unit-number interface],
[edit logical-systems logical-system-name interfaces sp-fpc/pic/port unit logical-unit-number
interface] | Specify the L2TP options for configuring logical interfaces for group and user sessions. | [
{
"name": "(dedicated | shared)",
"desc": "Specifies whether a logical interface can host one (dedicated) or multiple (shared)"
},
{
"name": "name",
"desc": "Interface identifier that must be replicated at the [edit access profile name] hierarchy level."
}
] | 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"
] |
l2tp-maximum-session (Service Interfaces) | l2tp-maximum-session number; | [edit interfaces si-slot/pic/port],
[edit interfaces asinumber] | Specify the maximum number of L2TP sessions allowed on a physical service interface (si) or aggregated
service interface (asi).
New session requests on an interface are accepted only when the session count is less than the
maximum session limit. If the limit has been reached, subsequent requests are dropped and the LNS... | [
{
"name": "number",
"desc": "Maximum number of L2TP sessions allowed for the interface. A value of 0 prevents the interface from being considered. Default: 64,000 Range: 0 through 64,000"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"L2TP LAC Tunneling for Subscribers",
"L2TP LNS Inline Service Interfaces",
"L2TP LAC Subscriber Configuration",
"L2TP LNS Inline Service Interfaces",
"L2TP LNS Inline Service Interfaces",
"L2TP for Subscriber Access Overview"
] |
l2tp-tunnel-session-identifier | l2tp-tunnel-session-identifier | [edit forwarding-options enhanced-hash-key family inet],
[edit forwarding-options enhanced-hash-key family inet6] | For better distribution in load balancing for L2TP tunneled traffic, enable l2tp-tunnel-session-identifier to
have the hash calculation of IPv4 or IPv6 packets include L2TP header parameters (tunnel ID and
session ID). With this option enabled, Junos OS generates different hashes for packets from different
tunnels. It... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2.
inet6 hierarchy introduced in Junos OS Release 25.2R1. | [
"Understanding Per-Packet Load Balancing",
"Configuring Per-Packet Load Balancing",
"No Link Title"
] |
l2vpn (routing-options) | l2vpn {
l2ckt;
l3vpn;
labeled-bgp;
no-l2ckt;
} | [edit logical-systems logical-system-name routing-options forwarding-table chained-composite-
next-hop ingress],
[edit routing-options forwarding-table chained-composite-next-hop ingress] | Enable composite chained next hop for ingress Layer 2 virtual private network (VPN) label-switched
paths (LSPs).
The remaining statements are explained separately. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [] |
l2vpn | l2vpn {
(control-word | no-control-word);
encapsulation-type type;
oam {
bfd-liveness-detection {
detection-time {
threshold milliseconds;
}
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier nu... | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit routing-instances routing-instance-name protocols] | 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... | [] | 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 a Layer 2 VPN Routing Instance",
"Configuring an MPLS-Based Layer 2 VPN (CLI Procedure)"
] |
l2vpn-id | l2vpn-id (as-number:id | ip-address:id); | [edit logical-systems logical-system-name routing-instances instance-name],
[edit routing-instances instance-name] | Specify a globally unique Layer 2 VPN community identifier for the instance. | [
{
"name": "as-number:id",
"desc": "Autonomous system number (l2vpn-id:as-number:2-byte-number. For example: l2vpn-id l2vpn-id:100:200. The AS number can be in the range from 1 through 65,535."
},
{
"name": "ip-address:id",
"desc": "IP address (l2vpn-id:ip-address:2-byte-number. For example: l2vp... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4R2. | [
"Example: Configuring BGP Autodiscovery for LDP VPLS",
"Example: Configuring BGP Autodiscovery for LDP VPLS with User-Defined Mesh Groups",
"Example: Configuring FEC 129 BGP Autodiscovery for VPWS"
] |
l2vpn-use-bgp-rules-edit-protocols-bgp | l2vpn-use-bgp-rules; | [edit logical-systems logical-system-name protocols bgp path-selection],
[edit protocols bgp path-selection] | Enable routers to use both the BGP path selection algorithm and the designated forwarder path
selection algorithm when selecting the preferred path to each destination in a Layer 2 VPN or VPLS
network.When the BGP path selection algorithm is enabled, it is used by all of the Provider routers. The
designated forwarder p... | [] | 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.
Statement introduced in Junos OS Release 12.3 for ACX Series routers. | [
"Enabling BGP Path Selection for Layer 2 VPNs and VPLS"
] |
l3-interface (VLAN) | l3-interface (vlan logical-interface-number | irb logical-interface-number);
l3-interface l3-interface-name logical-interface-number {
l3-interface-ingress-counting;
}
l3-interface interface-name-logical-unit-number; | [edit vlans vlan-name]
[edit interfaces ge-chassis/slot/port unit logical-unit-number family ethernet-
switching]
[edit vlans vlan-name] | Associate a Layer 3 interface with the VLAN. Configure Layer 3 interfaces on trunk ports to allow the
interface to transfer traffic between VLANs. Within a VLAN, traffic is bridged, while across VLANs,
traffic is routed. Because traffic between VLANs must be routed, a common Layer 3 interface is
required.
Default
No La... | [
{
"name": "interface-name–logical-unit-number",
"desc": "Name of a logical interface."
},
{
"name": "vlan.logical-interface-number",
"desc": "Number of the logical interface. Use the unit number that you used when"
},
{
"name": "irb.logical-interface-number",
"desc": "Logical interfa... | 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.
[edit vlans vlan-name] hierarchy level introduced in Junos OS Release 12.3R2 for EX Series switches and
MX Series routers.
irb option introduced in Junos OS Release 13.2 for the QFX Series. | [
"Configuring Routed VLAN Interfaces on Switches (CLI Procedure)",
"Configuring Integrated Routing and Bridging Interfaces on Switches (CLI Procedure)"
] |
l3-interface-ingress-counting | l3-interface-ingress-counting layer-3-interface-name; | [edit vlans vlan-name] | (EX8200 standalone switch and EX8200 Virtual Chassis) Enable routed VLAN interface (RVI) input
counters on an EX8200 switch to collect RVI source statistics for tracking or billing purposes. The input
counter is maintained by a firewall filter. The switch can maintain a limited number of firewall filter
counters—these ... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.3. | [
"Configuring Firewall Filters (CLI Procedure)",
"Configuring Routed VLAN Interfaces on Switches (CLI Procedure)"
] |
l3vpn (ingress) | l3vpn {
extended-space;
} | [edit logical-systems logical-system-name routing-options forwarding-table chained-composite-
next-hop ingress],
[edit routing-options forwarding-table chained-composite-next-hop ingress] | (M120 routers, M320 routers with Enhanced III FPCs, and MX Series routers only) Accept larger
numbers of Layer 3 VPN BGP updates with unique inner VPN labels (up to one million). The neighboring
provider edge (PE) routers are typically from other vendors and are configured to assign a unique inner
label to each Layer 3... | [] | 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. | [
"Accepting Route Updates with Unique Inner VPN Labels in Layer 3 VPNs"
] |
l3vpn (transit) | transit
l3vpn; | [edit logical-systems logical-system-name routing-options forwarding-table chained-composite-
next-hop transit]
[edit routing-options forwarding-table chained-composite-next-hop transit] | Configure Layer 3 VPN settings on the transit router.
This statement and the associated functionality is available on PTX Packet Transport Routers and
QFX10000 switches.
NOTE: You can configure transit l3vpn only after configuring the enhanced-ip operation
mode. See "network-services" on page 11789 to configure the enh... | [] | 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. | [] |
label | label {
allocation label-allocation-policy;
substitution label-substitution-policy;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options]
[edit routing-instances routing-instance-name routing-options] | Specify label allocation and substitution policies on a per-route basis. | [
{
"name": "allocation label-allocation-policy",
"desc": "Specify a policy to generate labels on a per-route basis."
},
{
"name": "substitution label-substituion-policy",
"desc": "Specify a policy to substitute labels on a per-route basis. The label"
}
] | 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. | [
"Configuring a Label Allocation and Substitution Policy for VPNs"
] |
label-allocation | label-allocation per-instance | per-bridge-domain; | [edit routing-instances routing-instance-name protocols evpn] | Specifies the MPLS label allocation setting for the EVPN routing instance. | [
{
"name": "per-instance",
"desc": "Allocates a single MPLS label for the EVPN routing instance."
},
{
"name": "per-bridge-domain",
"desc": "Allocates a single MPLS label for each bridge domain. By default, per-bridge-domain is"
}
] | 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. | [
"Configuring EVPN Routing Instances"
] |
label-block-size | label-block-size size; | [edit logical-systems profile-name routing-instances instance-name protocols vpls],
[edit routing-instances instance-name protocols vpls] | Configure the label block size for VPLS labels.
Default | [
{
"name": "2",
"desc": "Allocate the label blocks in increments of 2. For a VPLS domain that has only two sites with no"
},
{
"name": "4",
"desc": "Allocate the label blocks in increments of 4."
},
{
"name": "8 (default)",
"desc": "Allocate the label blocks in increments of 8."
},
... | 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. | [
"Configuring the Label Block Size for VPLS"
] |
label-position | label-position [ positions ]; | [edit services flow-monitoring version9 template template-name mpls-ipv4-template],
[edit services flow-monitoring version9 template template-name mpls-template] | Specify positions for up to three labels in the active flow monitoring version 9 template.
Default
[1 2 3] | [
{
"name": "positions",
"desc": "Numbered positions for the labels."
}
] | 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. | [
"Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9",
"Flow Templates"
] |
label-switched-path (Protocols IS-IS) | label-switched-path name level level-number metric metric; | [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] | Advertise label-switched paths (LSPs) into IS-IS as point-to-point links. The LSP is advertised in the
appropriate IS-IS levels as a point-to-point link and contains a local address and a remote address.
When you advertise LSPs into IS-IS as point-to-point links, the LSPs are used in SPF calculations. The
advertisement... | [
{
"name": "name",
"desc": "Identifies the LSP."
},
{
"name": "level-number",
"desc": "IS-IS level number."
},
{
"name": "metric",
"desc": "Metric 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. | [
"Example: Advertising Label-Switched Paths into IS-IS",
"Understanding Forwarding Adjacencies"
] |
label-switched-path (Protocols Link Management) | label-switched-path lsp-name; | [edit logical-systems logical-system-name protocols link-management te-link te-link-name],
[edit protocols link-management te-link te-link-name] | Specify the label-switched path (LSP) to be used by the forwarding adjacency. | [
{
"name": "lsp-name",
"desc": "Name of the LSP."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring Forwarding Adjacencies"
] |
label-switched-path (Protocols MPLS) | label-switched-path lsp-name {
disable;
adaptive;
admin-down;
admin-group {
exclude [ group-names ];
include-all [ group-names ];
include-any [ group-names ];
}
auto-bandwidth {
adjust-interval seconds;
adjust-threshold percentage;
maximum-band... | [edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and rest... | [
{
"name": "lsp-name",
"desc": "Name that identifies the LSP. The name can be up to 64 characters and can contain letters, digits, periods, and hyphens. To include other characters, enclose the name in quotation marks. The name must be unique within the ingress router."
},
{
"name": "cross-credibilit... | 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.
cross-credibility-cspf option introduced in Junos OS Release 14.2.
self-ping-duration and no-self-ping options introduced in Junos OS Release 16.1. | [
"Configuring the Ingress and Egress Router Addresses for LSPs",
"Configuring Primary and Secondary LSPs"
] |
label-switched-path (Protocols MVPN) | label-switched-path {
label-switched-path-template (Multicast){
(default-template | lsp-template-name);
}
} | [edit protocols mvpn inter-region-template template template-name region region-name ingress-
replication]
[edit protocols mvpn inter-region-template template template-name all-regions ingress-
replication] | Specify point-to-point LSP unicast tunnel at the ABRs. Optionally, you can specify a label-switched path
template. If you configure ingress-replication label-switched-path and do not include label-switched-path-
template, ingress replication works with existing LDP or RSVP tunnels. If you include label-switched-path-
t... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Segmented Inter-Area Point-to-Multipoint Label-Switched Paths Overview",
"Example: Configuring Segmented Inter-Area P2MP LSP",
"Configuring Segmented Inter-Area P2MP LSP"
] |
label-switched-path (Protocols OSPF) | label-switched-path name metric metric; | [edit logical-systems logical-system-name protocols ospf area area-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf
area area-id],
[edit protocols ospf area area-id],
[edit routing-instances routing-instance-name protocols ospf area area-id] | Advertise label-switched paths into OSPF as point-to-point links.
The label-switched path is advertised in the appropriate OSPF levels as a point-to-point link and
contains a local address and a remote address. | [
{
"name": "name",
"desc": "Name of the label-switched path."
},
{
"name": "metric",
"desc": "Metric 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. | [
"Example: Advertising Label-Switched Paths into OSPFv2"
] |
label-switched-path | label-switched-path lsp-name to remote-provider-edge-switch; | [edit protocols mpls] | Define a label-switched path (LSP) to the remote provider edge switch to use for MPLS traffic. You must
specify this statement on the provider edge switch. | [
{
"name": "lsp-name",
"desc": "Name that identifies the LSP. The name can be up to 32 characters and can contain letters,"
},
{
"name": "remote-provider-edge-switch",
"desc": "Either the loopback address or the switch address."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Example: Configuring MPLS on EX8200 and EX4500 Switches",
"Configuring CoS on an MPLS Provider Edge Switch Using IP Over MPLS",
"Configuring CoS on an MPLS Provider Edge Switch Using Circuit Cross-Connect"
] |
label-switched-path-template (Container LSP) | label-switched-path-template {
(default-template | lsp-template-name);
} | [edit protocols mpls container-label-switched-path lsp-name]
[edit routing-instances instance-name provider-tunnel] | Specify the LSP template. An LSP template is used as the basis for other dynamically generated LSPs. | [
{
"name": "default-template",
"desc": "Specify that the default LSP template be used for the dynamically generated LSPs."
},
{
"name": "lsp-template-name",
"desc": "Specify the name of an LSP to be used as a template for the dynamically generated LSPs."
}
] | 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.
Statement introduced for QFX Switches in Junos OS Release 15.1X53-D30. | [] |
label-switched-path-template (Multicast) | label-switched-path-template {
(default-template | lsp-template-name);
} | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel rsvp-te],
[edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel ingress-replication label-switched-path],
[edit logical-systems logical-system-name routing-instances routing-in... | Specify the LSP template. An LSP template is used as the basis for other dynamically generated LSPs.
This feature can be used for a number of applications, including point-to-multipoint LSPs, flooding VPLS
traffic, configuring ingress replication for IP multicast using MBGP MVPNs, and to enable RSVP
automatic mesh. The... | [
{
"name": "default-template",
"desc": "Specify that the default LSP template be used for the dynamically generated LSPs."
},
{
"name": "lsp-template-name",
"desc": "Specify the name of an LSP to be used as a template for the dynamically generated"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Example: Configuring Ingress Replication for IP Multicast Using MBGP MVPNs",
"Configuring Point-to-Multipoint LSPs for an MBGP MVPN",
"Configuring Dynamic Point-to-Multipoint Flooding LSPs",
"Configuring RSVP Automatic Mesh"
] |
label-switched-path-template | label-switched-path-template {
(default-template | lsp-template-name);
} | [edit protocols mpls lsp-external-controller lsp-external-controller] | Specify the LSP template with parameters for setting up the PCE-initiated LSPs when the PCE initiating
the LSP does not provide the PCE-initiated parameters. When label-switched-path-template is not
configured, the default LSP parameters are used. | [
{
"name": "default-template",
"desc": "Specify that the default LSP template be used for the dynamically generated PCE-initiated LSPs."
},
{
"name": "lsp-template-name",
"desc": "Specify the name of the LSP template to be used for setting up PCE-initated LSPs."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [] |
label-withdrawal-delay | label-withdrawal-delay 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] | Delay the withdrawal of labels to reduce router workload during IGP convergence. | [
{
"name": "seconds",
"desc": "Configure the number of seconds to wait before withdrawing labels for the LDP LSPs."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Configuring the Label Withdrawal Timer"
] |
labeled-bgp | labeled-bgp {
inet6;
inet;
} | [edit logical-systems logical-system-name routing-options forwarding-table chained-composite-
next-hop ingress],
[edit routing-options forwarding-table chained-composite-next-hop ingress] | Allows you to configure chained composite next hops for IPv4 and IPv6 labeled-unicast routes.
The other statement is explained separately. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | This statement was introduced in Junos OS Release 12.3. | [
"Accepting Route Updates with Unique Inner VPN Labels in Layer 3 VPNs"
] |
labeled-unicast (Protocols BGP) | labeled-unicast {
accepted-prefix-limit {
maximum number;
teardown <percentage> <idle-timeout (forever | minutes)>;
drop-excess <percentage>;
hide-excess <percentage>;
}
aggregate-label {
community community-name;
}
entropy-label {
elc-v2-compatible;... | [edit logical-systems logical-system-name protocols bgp family (inet | inet6)],
[edit logical-systems logical-system-name protocols bgp group group-name family (inet | inet6)],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address family
(inet | inet6)],
[edit logical-systems logica... | Configure the family type to be labeled-unicast.
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 before Junos OS Release 7.4.
Support for EVPN E-LAN introduced in Junos OS Evolved Release 25.2R1. | [
"Example: Configuring IPv6 BGP Routes over IPv4 Transport",
"Enabling Layer 2 VPN and VPLS Signaling",
"Understanding Multiprotocol BGP"
] |
labeled-unicast | labeled-unicast {
aggregate-label {
community community-name:
}
explicit-null {
connected-only;
}
per-group-label;
resolve-vpn;
traffic-statistics {
file filename <world-readable | no-world-readable>;
interval seconds;
}
} | [edit logical-systems logical-system-name protocols bgp family inet],
[edit logical-systems logical-system-name protocols bgp group group-name family inet],
[edit protocols bgp family inet],
[edit protocols bgp group group-name family inet] | Advertise labeled routes from the inet.0 VPN, and place labeled routes into the inet.0 VPN. When the
labeled-unicast statement is used, the local router automatically performs a next hop to self on all routes
advertised into EBGP from IBGP and into IBGP from EBGP. | [
{
"name": "resolve-vpn",
"desc": "(Optional) Store labeled routes in the inet.3 or inet6.3 routing table to resolve routes for a"
}
] | 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 Carrier-of-Carriers VPNs for Customers That Provide Internet Service",
"Configuring Carrier-of-Carriers VPNs for Customers That Provide VPN Service",
"Configuring Inter-AS VPLS with MAC Processing at the ASBR"
] |
lacp (IEEE 802.1AX) (MX Series) | lacp {
port-priority port-priority;
} | [edit interfaces interface-name fastether-options 802.3ad],
[edit interfaces interface-name gigether-options 802.3ad] | Configure the Link Aggregation Control Protocol (LACP) port priority for Ethernet interfaces. | [
{
"name": "port-priority",
"desc": "Priority for being elected as the active port to collect and distribute traffic. A smaller 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.3. | [
"Configuring LACP for Aggregated Ethernet Interfaces"
] |
lacp (IEEE 802.1AX) | lacp {
force-up;
(primary | backup);
} | [edit interfaces interface-name ether-options 802.3ad] | Configure the Link Aggregation Control Protocol (LACP) parameters for aggregated Ethernet interfaces
on the global level (for all the aggregated Ethernet interfaces on the switch) or for a specific aggregated
Ethernet interface.
Configure the Link Aggregation Control Protocol (LACP) parameters for interfaces. The remai... | [
{
"name": "primary",
"desc": "Designate the interface as the primary interface for link-protection mode."
},
{
"name": "backup",
"desc": "Designate the interface as the backup interface for link-protection mode."
}
] | 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.
Support for LACP link protection introduced in Junos OS Release 11.4 for EX Series switches. | [
"Example: Configuring Aggregated Ethernet High-Speed Uplinks Between an EX4200 Virtual Chassis",
"Access Switch and an EX4200 Virtual Chassis Distribution Switch",
"Example: Configuring Aggregated Ethernet High-Speed Uplinks with LACP Between an EX4200",
"Virtual Chassis Access Switch and an EX4200 Virtual Ch... |
lacp (Aggregated Ethernet) | lacp {
(active | passive);
admin-key key;
accept-data;
fast-failover;
link-protection {
disable;
(revertive |non-revertive);
}
periodic interval;
system-id mac-address;
system-priority priority;
} | [edit interfaces interface-name aggregated-ether-options] | Configure the Link Aggregation Control Protocol (LACP) parameters for interfaces. The remaining
statement is explained separately.
For EX Series, when you configure the accept-data statement at the [edit interfaces aeX aggregated-ether-
options lacp] hierarchy level, the router processes packets received on a member li... | [
{
"name": "active",
"desc": "Initiate transmission of LACP packets."
},
{
"name": "admin-key",
"desc": ""
},
{
"name": "number",
"desc": "Specify an administrative key for the router or switch. NOTE: You must also configure multichassis link aggregation (MC-LAG) when you configure th... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Configuring Link Aggregation",
"Configuring Aggregated Ethernet LACP (CLI Procedure)",
"Understanding Aggregated Ethernet Interfaces and LACP for Switches",
"Configuring LACP for Aggregated Ethernet Interfaces"
] |
lacp (Interfaces) | lacp {
(active | passive);
periodic (fast | slow);
} | [edit interfaces interface-name redundant-ether-options] | For redundant Ethernet interfaces in a chassis cluster only, configure Link Aggregation Control Protocol
(LACP). | [
{
"name": "active",
"desc": "Initiate transmission of LACP packets."
},
{
"name": "passive",
"desc": "Respond to LACP packets."
},
{
"name": "Default",
"desc": "If you do not specify lacp as either active or passive, LACP remains off (the default)."
},
{
"name": "periodic",
... | 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. | [
"Understanding LACP on Standalone Devices",
"periodic (Interfaces)"
] |
lacp (Protocols) | lacp {
traceoptions {
file <filename> <files number> <size size> <world-readable | no-world-readable>;
flag flag;
no-remote-trace;
}
fast-hello-issu;
ppm (Ethernet Switching) centralized | distributed | inline;
} | [edit protocols] | 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": "ppm",
"desc": "Specify the type of PPM processing. Possible values: Centralized, distributed, and inline."
},
{
"name": "fast-hello-issu",
"desc": "Enable LACP with fast hellos during unified ISSU."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3.
The ppm centralized option introduced in Junos OS Release 9.4.
The fast-hello-issu option introduced in Junos OS Release 14.1. | [
"Configuring LACP for Aggregated Ethernet Interfaces",
"Unified ISSU System Requirements"
] |
lacp | lacp {
link-protection {
non-revertive;
}
system-priority priority;
} | [edit chassis aggregated-devices ethernet] | For aggregated Ethernet interfaces only, configure Link Aggregation Control Protocol (LACP) parameters
at the global level for use by LACP at the interface level. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Configuring Junos OS for Supporting Aggregated Devices"
] |
lag-heap-optimization | lag-heap-optimization; | [edit forwarding-options] | Improve heap memory utilization in link aggregation group (LAG) interfaces in large-scale configurations.
If you have a configuration with many interfaces in a large number of VLANs, and you've configured
those interfaces as part of a logical aggregated Ethernet interface bundle, the device can approach 100%
of its hea... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [] |
land (IDS Screen Next Gen Services) | land; | [edit services screen ids-option screen-name tcp] | Identify and drop SYN packets that have the same source and destination address or port, which
protects against land attacks. In a land attack, the target using up its resources as it repeatedly replies to
itself. | [] | 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"
] |
land | land; | [edit security screen ids-option screen-name tcp] | Enable prevention of Land attacks by combining the SYN flood defense with IP spoofing protection.
Land attacks occur when an attacker sends spoofed IP packets with headers containing the target’s IP
address for the source and destination IP addresses. The attacker sends these packets with the SYN flag
set to any avail... | [] | 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. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
land-attack-check (IDS MS-MPC) | land-attack-check (ip-only | ip-port); | [edit services ids rule rule-name term term-name then] | Identify and drop SYN packets that have the same source and destination address or port, which
provides protection against land attacks. This statement can only be used in IDS rules assigned to a
service set on an MS-MPC. | [
{
"name": "ip-only",
"desc": "Identify and drop SYN packets that have the same source and destination address."
},
{
"name": "ip-port",
"desc": "Identify and drop SYN packets that have the same source and destination address and port."
}
] | 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 Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
land-attack-check | land-attack-check (ip-only | ip-port ); | [edit services service-set service-set-name nat-options] | Enable land attack checks based on either IP address only or both IP address and IP port number.
NOTE: If you do not configure this statement, there is no land attack check for
hairpinning NAT packets. | [
{
"name": "ip-only",
"desc": "Land attack check is based on IP address only."
},
{
"name": "ip-port",
"desc": "Land attack check is based on IP address and IP port number."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced with Junos OS Release 12.3. | [
"Configuring Service Rules"
] |
lane | lane [lane-number] {
rx-cdr (off | on);
rx-output (off | on);
rx-output-amplitude (1200mV | 400mV | 600mV | 800mV);
rx-output-emphasis rx-output-e;
rx-rate-select rx-rate-select;
rx-squelch (off | on);
tx-cdr (off| no);
tx-input-equalization-adaptive (o... | [edit interfaces interface-name optics-options] | Configure the optical module parameters of QSFP (Quad Small Form-Factor Pluggable) modules for a
specific media lane number. The following QSFP modules are supported:
•
QSFP+ : 4 host lanes, supports 10g per lane, total bandwidth of 40g
•
QSFP28 : 4 host lanes, supports 25g per lane, total bandwidth of 100g
•
QSFP56 : ... | [
{
"name": "lane-number",
"desc": "Specifies the media lane number. Range: 0 through 7"
},
{
"name": "rx-cdr",
"desc": "Controls receive clock and data recovery block of the optics."
},
{
"name": "Off",
"desc": "Receive clock and data recovery is disabled."
},
{
"name": "On",... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 21.1R1. | [] |
lane-all | lane-all {
rx-cdr (off | on);
rx-output (off | on);
rx-output-amplitude (1200mV | 400mV | 600mV | 800mV);
rx-output-emphasis rx-output-e;
rx-rate-select rx-rate-select;
rx-squelch (off | on);
tx-cdr (off | no);
tx-input-equalization-adaptive (off | on);... | [edit interfaces interface-name optics-options] | Configure the optical module parameters of QSFP (Quad Small Form-Factor Pluggable) modules for all
the media lanes. The following QSFP modules are supported:
•
QSFP+ : 4 host lanes, supports 10g per lane, total bandwidth of 40g
•
QSFP28 : 4 host lanes, supports 25g per lane, total bandwidth of 100g
•
QSFP56 : 4 host l... | [
{
"name": "rx-cdr",
"desc": "Controls receive clock and data recovery block of the optics."
},
{
"name": "Off",
"desc": "Receive clock and data recovery is disabled."
},
{
"name": "On",
"desc": "Receive clock and data recovery is enabled."
},
{
"name": "rx-output",
"desc"... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 21.1R1. | [] |
language (Scripts) | language (python | python3); | [edit system scripts] | Enable the execution of unsigned Python scripts on Junos devices, and specify the version of Python
used to execute the scripts.
Configuring this statement enables you to execute unsigned Python commit, event, op, and SNMP
automation scripts; unsigned Python action and translation scripts for custom YANG modules; and
u... | [
{
"name": "(python |",
"desc": ""
},
{
"name": "python3)",
"desc": "Specify the Python version used to execute Python scripts. Configure python to use Python 2.7, or configure python3 to use Python 3. If you configure the language python3 statement, the device uses Python 3 to execute scripts th... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 16.1R1.
python3 option added in Junos OS Release 19.4R1 for commit, event, op, and SNMP scripts.
python3 option support for JET and YANG scripts added in Junos OS Release 20.2R1.
python3 option added in Junos OS Evolved Release 21.1R1.
python option deprecated in Junos OS Releas... | [
"Understanding Python Automation Scripts for Devices Running Junos OS"
] |
large (IDS Screen Next Gen Services) | large; | [edit services screen ids-option screen-name icmp] | Identify and drop any ICMP frame with an IP length greater than 1024 bytes, which protects against
ICMP large packet attacks. | [] | 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"
] |
large | large; | [edit security screen ids-option screen-name icmp] | Configure the device to detect and drop any ICMP frame with an IP length greater than 1024 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. | [] |
large-community-count | large-community-count | [edit policy-options policy-statement <statement-name>],
[edit policy-options policy-statement <statement-name> term <term-name>] | Count number of BGP large communities (RFC 8092). | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.3R1. | [] |
laser-enable | (laser-enable | no-laser-enable); | [edit interfaces interface-name otn-options] | Specify whether lasers are enabled or disabled.
Default
If you omit the laser-enable statement, lasers are disabled. | [
{
"name": "laser-enable",
"desc": "Enable lasers."
},
{
"name": "no-laser-enable",
"desc": "Do not enable lasers."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
last-block-recycle-timeout | last-block-recycle-timeout timeout-inteval; | [edit security nat source pool port block-allocation] | Specify the amount of time before the last active port block is released. This option is used with the
active-block-timeout option at [edit security nat source pool port block-allocation] hierarchy level. When the
active-block-timeout option is set to 0 (zero), port blocks are filled completely before a new port block ... | [
{
"name": "timeout-interval",
"desc": "Number of seconds before the active block is released."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D60. | [] |
latency (Interfaces) | latency number; | [edit interfaces interface-name unit logical-unit-number radio-router] | This option controls the latency weight (value 0–100). | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"PPPoE-Based Radio-to-Router Protocols Overview"
] |
latency-threshold | latency-threshold {
high number;
low number;
} | [edit services analytics interfaces]
[edit services analytics resource-profiles] | If network analytics queue statistics monitoring is enabled, specify the high and low values (in
microseconds) of the latency threshold of the queue. If you configure a latency threshold, you cannot
configure the depth threshold. You can configure the latency threshold for one interface or all interfaces.
Specify the h... | [
{
"name": "high",
"desc": ""
},
{
"name": "number",
"desc": "Specify the maximum value for the latency threshold. Range:"
},
{
"name": "Junos OS Release 13.2X51-D15 or later",
"desc": "1 to 100,000,000 nanoseconds (0.001 to"
},
{
"name": "100,000 microseconds)",
"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.2.
Statement in the [edit services analytics resource-profiles] hierarchy level introduced in Junos OS Release
13.2X51-D15. | [
"Network Analytics Overview"
] |
layer2 (enhanced-hash-key) | layer2 {
no-incoming-port;
no-destination-mac-address;
no-ether-type;
no-source-mac-address;
source-mac-address;
vlan-id;
no-vlan-id;
inner-vlan-id;
} | [edit forwarding-options enhanced-hash-key] | Select the fields in the Layer 2 header that are used by the hashing algorithm to make hashing decisions.
When traffic enters a link aggregation group (LAG) bundle, the hashing algorithm checks the fields
configured using this statement and uses the information in the fields to decide how to place traffic onto
the LAG ... | [
{
"name": "no-destination-mac-address",
"desc": "Exclude the destination MAC address field from the hashing algorithm."
},
{
"name": "no-ether-type",
"desc": "Exclude the Ethertype field from the hashing algorithm."
},
{
"name": "no-source-mac-address",
"desc": "Exclude the source MA... | 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"
] |
layer2-control | layer2-control {
bpdu-block {
disable-timeout seconds;
interface interface-name;
}
ephemeral-db-support;
l2pt {
interface name {
destination {
vxlan-tunnel;
}
enable-all-ifl;
protocol {
(all | prot... | [edit protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and rest... | [
{
"name": "ephemeral-db-support",
"desc": "(Junos OS only) Enable users to configure Multiple Spanning Tree Protocol (MSTP), Rapid Spanning Tree Protocol (RSTP), or VLAN Spanning Tree Protocol (VSTP) in the ephemeral configuration database."
},
{
"name": "nonstop-bridging",
"desc": "For details ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
bpdu-block statement added in Junos OS Release 9.4.
Statement introduced in Junos OS Release 14.1X53-D10 for EX4300 switches.
tunnel-destination-mac statement added in Junos OS Evolved Release 21.3R1.
ephemeral-db-support statement added in Junos OS Release 23.4R1. | [
"Understanding Layer 2 Protocol Tunneling",
"Configuring Layer 2 Protocol Tunneling",
"Layer 2 Protocol Tunneling over VXLAN Tunnels in EVPN-VXLAN Bridged Overlay Networks"
] |
layer2-liveness-detection (Receive) | layer2-liveness-detection; | [edit system services subscriber-management overrides interfaces family (inet | inet6)] | Enable a DHCP client host to determine the state of the DHCPv4 or DHCPv6 client session from the
perspective of a router acting as a broadband network gateway (BNG). This statement causes the BNG
to conduct a host connectivity check on its directly connected DHCPv4 and DHCPv6 clients when it
receives ARP or Neighbor Di... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1. | [
"DHCP Liveness Detection Using ARP and Neighbor Discovery Packets",
"DHCP Liveness Detection Overview",
"Configuring Junos OS Enhanced Subscriber Management"
] |
layer2-liveness-detection (Send) | layer2-liveness-detection {
max-consecutive-retries number;
transmit-interval seconds;
} | [edit forwarding-options dhcp-relay dhcpv6 group group-name liveness-detection method],
[edit forwarding-options dhcp-relay dhcpv6 liveness-detection method],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name liveness-detection
method],
[edit forwarding-options dhcp-relay group group-name live... | Configure a router acting as a broadband network gateway (BNG) to conduct a host connectivity check
on its directly connected DHCPv4 and DHCPv6 clients to determine the validity and state of the DHCP
client session, and to clean up inactive sessions.
The BNG sends ARP or ND request packets to the each DHCP client at a ... | [
{
"name": "max-consecutive-retries number",
"desc": "Maximum number of consecutive times that the router sends an ARP request packet in the absence of an ARP response packet. Range: 3 through 6 retries Default: 3 retries"
},
{
"name": "transmit-interval",
"desc": ""
},
{
"name": "secon... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4R1. | [
"DHCP Liveness Detection Using ARP and Neighbor Discovery Packets",
"DHCP Liveness Detection Overview"
] |
layer2-map | layer2-map; | [edit logical-systems logical-system-name protocols isis],
[edit logical-systems logical-system-name protocols isis interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
isis],
[edit protocols isis],
[edit protocols isis interface interface-name],
[edit ... | Enable Layer 2 mapping of ARP or neighbor discovery next hops in the kernel for the specified instance
or interface. IS-IS Layer 2 mapping ensures that forwarding next-hop resolution is topology-driven
rather than traffic-driven, which results in minimal traffic loss while activating an Ethernet link.
IS-IS LAN and poi... | [] | 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. | [
"Layer 2 Mapping for IS-IS",
"Example: Configuring Layer 2 Mapping for IS-IS"
] |
layer2-policer (EX) | layer2-policer {
input-policer policer-name;
input-three-color policer-name;
output-policer policer-name;
output-three-color policer-name;
} | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | For 1-Gigabit Ethernet and 10-Gigabit Ethernet IQ2 and IQ2-E interfaces on M Series, MX Series, and T
Series routers, and for aggregated Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet interfaces on EX
Series switches, apply Layer 2 logical interface policers. The following policers are supported:
•
Two-color
•
Sin... | [
{
"name": "input-policer policer-name",
"desc": "Two-color input policer to associate with the interface. This statement is"
},
{
"name": "input-three-color policer-name",
"desc": "Tricolor input policer to associate with the interface. This statement is"
},
{
"name": "output-policer pol... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Applying Layer 2 Policers to Gigabit Ethernet Interfaces",
"Configuring Gigabit Ethernet Two-Color and Tricolor Policers"
] |
layer2-policer (firewall) | layer2-policer | [edit firewall family <firewall filter family> filter <firewall filter name>] | By default, a packet gets policed by a policer on the packet's layer 3 header length along with the
packet's payload length. Applying the layer2-policer configuration on a firewall filter allows the policer to
account layer 2 overhead, which changes the policer behavior as well as the firewall filter counter
behavior a... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration | Statement introduced in Junos OS Evolved Release 24.3R1
Supported on:
•
PTX10001-36MR
•
PTX10003
•
PTX10004 - LC1201 & LC1202
•
PTX10008 - LC1201 & LC1201
•
PTX10016 - LC1201 & LC1201
•
PTX10002-36QDD | [] |
layer2-policer (Hierarchical Policer) | layer2-policer {
input-hierarchical-policer policer-name
} | [edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number] | Apply a hierarchical policer to the Layer 2 input traffic for all protocol families at the physical or logical
interface. The following interfaces are supported:
•
SONET interfaces hosted on M40e, M120, and M320 edge routers with incoming Flexible PIC
Concentrators (FPCs) as SFPC and outgoing FPCs as FFPC
•
Interfaces ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Hierarchical Policers",
"Two-Color and Three-Color Policers at Layer 2"
] |
layer2-policer | layer2-policer {
output-policer policer-name;
output-three-color policer-name;
} | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number] | Specify the output policers to be used in the dynamic profile. | [
{
"name": "output-policer policer-name",
"desc": "Two-color output policer to associate with the interface. You define this"
},
{
"name": "output-three-color policer-name",
"desc": "Tricolor output policer to associate with the interface. You define this"
}
] | 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. | [
"Applying the Policers to Dynamic Profile Interfaces",
"Creating a Dynamic Profile for the Complex Configuration"
] |
layer2-protocol-tunneling | layer2-protocol-tunneling all | protocol-name {
drop-threshold number;
shutdown-threshold number;
} | [edit vlans vlan-name dot1q-tunneling] | Enable Layer 2 protocol tunneling (L2PT) on a VLAN on switches that do not use the the Enhanced
Layer 2 Software (ELS) configuration style (which includes EX2200, EX3300, EX4200, EX4500, and
EX4450 switches).
NOTE: This command is not available on switches that use ELS configuration style
(including EX2300, EX3400, EX4... | [
{
"name": "all",
"desc": "Enable all supported Layer 2 protocols."
},
{
"name": "protocol-name",
"desc": "Name of the Layer 2 protocol. Values are:"
},
{
"name": "802.1x",
"desc": "IEEE 802.1X authentication"
},
{
"name": "802.3ah",
"desc": "IEEE 802.3ah Operation, Admini... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0 for EX Series switches. | [
"Example: Configuring Layer 2 Protocol Tunneling on EX Series Switches Without ELS Support",
"Configuring Layer 2 Protocol Tunneling on EX Series Switches Without ELS Support"
] |
layer2-unicast-replies | layer2-unicast-replies; | [edit forwarding-options dhcp-relay overrides],
[edit forwarding-options dhcp-relay group group-name overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay group group-name
overrides],
[edit logical-systems... | Override the setting of the broadcast bit in DHCP request packets and instead use the Layer 2 unicast
transmission method to transmit DHCP Offer reply packets and DHCP ACK reply packets from the
DHCP server to DHCP clients during the discovery process. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Extended DHCP Relay Agent Overview"
] |
layer3-domain-identifier | layer3-domain-identifier identifier; | [edit routing-instances instance-name] | Specify a Layer 3 domain ID within a routing instance. | [
{
"name": "id",
"desc": "Layer 3 identification number."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3R2. | [
"Configuring a Layer 2 Virtual Switch on an EX Series Switch"
] |
lcd-menu | EX3200, EX3300, EX4200, or EX4500 switch:
lcd-menu fpc slot-number {
menu-item (menu-name | menu-option) <disable>;
}
EX6200 or EX8200 switch or XRE200 External Routing Engine:
lcd-menu {
menu-item (menu-name | menu-option) <disable>;
} | [edit chassis] | Disable or enable the Maintenance menu or the Status menu in the LCD panel. | [
{
"name": "none",
"desc": "(EX6200 and EX8200 switches and XRE200 External Routing Engines only) Disable or enable the"
},
{
"name": "fpc slot-number",
"desc": "(EX3200, EX3300, EX4200, and EX4500 switches only) Disable or enable the"
},
{
"name": "0",
"desc": "On standalone switches... | interface—To view this statement in the configuration.
interface-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring the LCD Panel on EX Series Switches (CLI Procedure)",
"LCD Panel in EX3200 Switches",
"LCD Panel in EX3300 Switches",
"LCD Panel in EX4200 Switches",
"LCD Panel in EX4500 Switches",
"LCD Panel in an EX6200 Switch",
"LCD Panel in an EX8200 Switch",
"LCD Panel in an XRE200 External Routing ... |
lcp-max-conf-req | lcp-max-conf-req number | [edit interfaces so-fpc/pic/port unit number ppp-options] | Set the maximum number of LCP Configure-Requests to be sent, after which the router goes to LCP
down state. | [
{
"name": "number",
"desc": "From 0 to 65,535, where 0 means send infinite LCP Configure-Requests, and any other value specifies the maximum number LCP Configure-Requests to send and then stop sending. Default"
}
] | 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 PPP"
] |
lcp-renegotiation | lcp-renegotiation; | [edit access group-profile profile-name l2tp],
[edit access profile profile-name client client-name l2tp] | Configure the L2TP network server (LNS) so it renegotiates the link control protocol (LCP) with the PPP
client. When LCP renegotiation is disabled, LNS uses the pre-negotiated LCP parameters between the
L2TP access concentrator (LAC) and PPP client to set up the session. When LCP renegotiation is
enabled, authenticatio... | [] | 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"
] |
lcp-restart-timer | lcp-restart-timer milliseconds; | [edit interfaces interface-name unit logical-unit-number ppp-options],
[edit logical-systems logical-system-name interfaces interface-nameunit logical-unit-number ppp-
options] | For interfaces with PPP, PPP TCC, PPP over Ethernet, PPP over ATM, and PPP over Frame Relay
encapsulations, configure a restart timer for the Link Control Protocol (LCP) component of a PPP
session. | [
{
"name": "milliseconds",
"desc": "The time, in milliseconds, between successive LCP configuration requests."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Configuring PPP"
] |
ldap-options | ldap-options {
revert-interval seconds;
base-distinguished-name base-distinguished-name;
search {
admin-search;
}
allowed-groups {
group-name {
address-assignment {
pool pool-name;
}
}
}
... | [edit access],
[edit access profile profile-name authentication-order ldap] | Configure LDAP authentication options.
You can configure user groups using ldap-options command for the user groups that are user
authenticated. You can authenticate users that are assigned roles according to their LDAP group
memberships. The allowed-groups attribute authenticates users that are assigned according to t... | [
{
"name": "allowed-groups",
"desc": "Allow members of only specific groups to sign in. Group lists are limited to 255 bytes. The order in which the membership attribute is received from the LDAP server determines how a user is associated with the configured (allowed) groups. To match the user, the first gro... | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS.
allowed-groups option introduced in Release 21.4R1 of Junos OS. | [] |
ldap-server | ldap-server server-address {
port port-number;
retry attempts;
routing-instance routing-instance-name;
source-address source-address;
timeout seconds;
no-tls-certificate-check;
tls-min-version (v1.1 | v1.2);
tls-peer-name;
tls-timeout;
tls-type {
start-tls;
}
} | [edit access]
[edit access profile profile-name] | Specify that the device uses a Lightweight Directory Access Protocol (LDAP) server for authentication. | [
{
"name": "server-address",
"desc": "Address of the LDAP authentication server."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [
"Firewall User Authentication Overview",
"Obtaining Username and Role Information Through Firewall Authentication",
"LDAP Functionality in Integrated User Firewall"
] |
ldap-url | <ldap-url url-name>; | [edit security certificates certification-authority ca-profile-name] | (Encryption interface on M Series and T Series routers and EX Series switches only) (Optional) Specify
the Lightweight Directory Access Protocol (LDAP) URL for digital certificates. | [
{
"name": "url-name",
"desc": "Name of the LDAP URL."
}
] | 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. | [
"Specifying an LDAP URL"
] |
ldp | ldp {
auto-targeted-session {
maximum-sessions;
no-dynamic-tunnels;
no-rlfa;
teardown-delay;
{
color-import-policy [ policy-names ]
(deaggregate | no-deaggregate);
dod-request-policy
dual-transport {
inet-lsr-id ;
inet6-lsr-id;
... | [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] | 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": "transport-preference ipv4 |",
"desc": ""
},
{
"name": "ipv6",
"desc": "Select the preferred transport for TCP connection when both IPv4 and IPv6 are enabled. If transport-preference ipv4 is configured, LDP will attempt to establish the TCP connection using IPv4. If transport-preferenc... | 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.
dual-transport statement introduced in Junos OS Release 16.1 for the M320 Series, MX Series, and PTX
Series.
family statement introduced in Junos OS Release 16.1 for the M320 Series, MX Series, and PTX Series.
transport-preference option introduced in Junos OS Release 1... | [
"Minimum LDP Configuration",
"Enabling and Disabling LDP"
] |
ldp-p2mp | ldp-p2mp; | [edit logical-systems logical-system-name routing-instances instance-name provider-tunnel],
[edit logical-systems logical-system-name routing-instances instance-name provider-tunnel
selective wildcard-group-inet wildcard-source],
[edit logical-systems logical-system-name routing-instances instance-name provider-tunnel... | Specify a point-to-multipoint provider tunnel with LDP signalling for an MBGP MVPN. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Example: Configuring Point-to-Multipoint LDP LSPs as the Data Plane for Intra-AS MBGP MVPNs"
] |
ldp-stitching (Protocols OSPF) | ldp-stitching; | [edit protocols ospf source-packet-routing],
[edit routing-instances name protocols ospf source-packet-routing] | Enable segment routing to LDP stitching. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1. | [
"LDP Mapping Server for Interoperability of Segment Routing with LDP Overview"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.