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 |
|---|---|---|---|---|---|---|---|
ldp-tunneling | ldp-tunneling; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name]
[edit protocols source-packet-routing source-routing-path lsp-name] | Enable the LSP to be used for LDP tunneling. | [] | 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. | [
"Enabling LDP over RSVP-Established LSPs"
] |
leaf | leaf {
deterministic-ar-policy [ deterministic-ar-policy-name ... ];
replicator-activation-delay seconds;
} | [edit logical-systems name routing-instances name protocols evpn assisted-replication],
[edit routing-instances name protocols evpn assisted-replication],
[edit protocols evpn assisted-replication] | Configure a device in an EVPN network into the assisted replication (AR) leaf role. AR leaf devices might
also be called AR client devices.
AR helps to optimize broadcast, unknown unicast, and multicast (BUM) traffic in EVPN networks. To
enable AR, you configure devices in the EVPN network to operate as AR replicator a... | [
{
"name": "replicator-activation-",
"desc": ""
},
{
"name": "delay",
"desc": "Interval (in seconds) to wait after receiving an AR replicator route from an AR replicator before starting to forward traffic to it. You might want to adjust the delay to make sure AR replicator devices have fully lear... | routing | Statement introduced in Junos OS Release 18.4R2 and 19.4R1.
deterministic-ar-policy option added in Junos OS Release 23.4R2. | [
"Assisted Replication Multicast Optimization in EVPN Networks",
"Deterministic Load Balancing and Traffic Steering to AR Replicators"
] |
leaf-tunnel-limit-inet (MVPN Selective Tunnels) | leaf-tunnel-limit-inet number; | [edit logical-systems logical-system-name routing-instances instance-name provider-tunnel
selective],
[edit routing-instances instance-name provider-tunnel selective] | Configure the maximum number of selective leaf tunnels for IPv4 control-plane routes.
The purpose of the leaf-tunnel-limit-inet statement is to supplement the multicast forwarding-cache limit
when the MVPN rpt-spt mode is configured and when traffic is flowing through selective service
provider multicast service interf... | [
{
"name": "number",
"desc": "Maximum number of selective leaf tunnels for IPv4."
}
] | 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. | [
"Examples: Configuring the Multicast Forwarding Cache",
"Example: Configuring MBGP Multicast VPN Topology Variations"
] |
leaf-tunnel-limit-inet6 (MVPN Selective Tunnels) | leaf-tunnel-limit-inet6 number; | [edit logical-systems logical-system-name routing-instances instance-name provider-tunnel
selective],
[edit routing-instances instance-name provider-tunnel selective] | Configure the maximum number of selective leaf tunnels for IPv6 control-plane routes.
The purpose of the leaf-tunnel-limit-inet6 statement is to supplement the multicast forwarding-cache
limit when the MVPN rpt-spt mode is configured and when traffic is flowing through selective service
provider multicast service inter... | [
{
"name": "number",
"desc": "Maximum number of selective leaf tunnels for IPv6."
}
] | 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. | [
"Examples: Configuring the Multicast Forwarding Cache",
"Example: Configuring MBGP Multicast VPN Topology Variations"
] |
learn-sip-register | learn-sip-register; | [edit applications application application-name] | Learn potential incoming SIP calls by inspecting the SIP register method.
More information: You can enable the router to accept any incoming SIP calls for the endpoint devices
that are behind the NAT firewall. When a device behind the firewall registers with the proxy that is
outside the firewall, the AS or Multiservic... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"ALG Descriptions",
"Configuring Application Sets",
"Configuring SIP",
"Examples: Configuring Application Protocols",
"Verifying the Output of ALG Sessions"
] |
lease-time (dhcp-client) | lease-time seconds; | [edit interfaces interface-name unit logical-unit-number family family dhcp-client] | Specify the time to negotiate and exchange Dynamic Host Configuration Protocol (DHCP) information. | [
{
"name": "seconds",
"desc": "Request time to negotiate and exchange information."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10.
Starting with Junos OS Release 17.3R1, on all SRX Series Firewalls and vSRX Virtual Firewall instances,
the CLI option dhcp-client at [edit interfaces interface-name unit logical-unit-number family inet] hierarchy is
changed to dhcp to keep consistent with other Jun... | [
"DHCP Overview"
] |
lease-time | lease-time (length | infinite); | [edit interfaces interface-name unit logical-unit-
number family inet dhcp] | Request a specific lease time for the IP address. The lease time is the length of time in seconds that a
client holds the lease for an IP address assigned by a DHCP server.
Default
If no lease time is requested by client, then the server sends the lease time. The default lease time on a
Junos OS DHCP server is one day. | [
{
"name": "seconds",
"desc": "Request a lease time of a specific duration. NOTE: Starting in Junos OS Release 23.4R1, the DHCP client silently discards the DHCP OFFER which has a lease-time of less than 15 seconds. Range: 60 through 2147483647 seconds"
},
{
"name": "infinite",
"desc": "Request ... | 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. | [
"DHCP Client",
"DHCPv6 Client"
] |
lease-time-threshold (DHCP Local Server and DHCP Relay Agent) | lease-time-threshold seconds; | [edit forwarding-options dhcp-relay lease-time-validation],
[edit forwarding-options dhcp-relay dhcpv6 lease-time-validation],
[edit forwarding-options dhcp-relay group group-name lease-time-validation],
[edit forwarding-options dhcp-relay dhcpv6 group group-name lease-time-validation],
[edit logical-systems logical-sy... | Configure the minimum DHCP lease time allowed in your subscriber access network. If a third-party
DHCP server or address pool provides a client lease that is less than the configured threshold, the router
performs the action specified by the violation-action statement. | [
{
"name": "seconds",
"desc": "Minimum client lease time allowed. Range: 60 through 2,147,483,647 seconds"
}
] | 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. | [
"Configuring a DHCP Lease-Time Threshold"
] |
lease-time-validation (DHCP Local Server and DHCP Relay Agent) | lease-time-validation {
lease-time-threshold seconds;
violation-action action;
} | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit forwarding-options dhcp-relay group group-name],
[edit forwarding-options dhcp-relay dhcpv6 group group-name],
[edit logical-systems logical-system-name ...],
[edit logical-systems logical-system-name routing-instances routing-ins... | Enable the lease-time validation feature on the router. You can then configure the lease-time threshold
and an optional action to take when a lease-time violation occurs.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for detai... | [] | 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. | [
"Configuring a DHCP Lease-Time Threshold"
] |
leasequery (DHCP Relay Agent) | leasequery {
attempts number-of-attempts;
timeout seconds;
} | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit logical-systems logical-system-name ...],
[edit logical-systems logical-system-name routing-instances routing-instance-name ...],
[edit routing-instances routing-instance-name ...] | Enable support for leasequery on a DHCPv4 or DHCPv6 relay agent. You can also configure parameters
that the DHCP relay agent uses when sending DHCP leasequery messages to obtain lease information
from the DHCP local servers in the logical system/routing instance.
NOTE: You must also configure support on the relevant DH... | [
{
"name": "attempts",
"desc": ""
},
{
"name": "number-of-attempts",
"desc": "Specify the number of times the DHCP relay agent attempts to send DHCP leasequery messages to the configured DHCP servers in the logical system/routing instance. DHCP relay agent resends the query message if the configu... | 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. | [
"Configuring and Using DHCP Individual Leasequery"
] |
least-fill | [] | [] | |||||
leave-timer (MVRP) | leave-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... | For Multiple VLAN Registration Protocol (MVRP), configure the number of milliseconds the switch
retains a VLAN in the Leave state before the VLAN is unregistered. If the interface receives a join
message before this timer expires, the VLAN remains registered.
Maintain default timer settings unless there is a compelling... | [
{
"name": "milliseconds",
"desc": "Interval that the switch retains a VLAN in the Leave state before the VLAN is unregistered."
}
] | 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) on Switches",
"Configuring Multiple VLAN Registration Protocol (MVRP) to Manage D... |
leaveall-timer (MVRP) | leaveall-timer interval; | [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... | For Multiple VLAN Registration Protocol (MVRP), configure the interval at which the LeaveAll state
operates on the interface.
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 operation of MVRP. However, i... | [
{
"name": "EX Series and QFX Series:",
"desc": ""
},
{
"name": "interval",
"desc": "Number of seconds or milliseconds between the sending of Leave All messages."
},
{
"name": "seconds",
"desc": "Interval between the sending of Leave All messages (range from 10 seconds through 60"
}... | 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.
Hierarchy level [edit protocols mvrp] introduced in Junos OS Release 13.2X50-D10 (ELS). (See Using the
Enhanced Layer 2 Software CLI for information about ELS.) | [
"Understanding Multiple VLAN Registration Protocol (MVRP) for Dynamic VLAN Registration",
"Understanding Multiple VLAN Registration Protocol (MVRP) for Dynamic VLAN Registration",
"Configuring Multiple VLAN Registration Protocol (MVRP) to Manage Dynamic VLAN Registration",
"Example: Configuring Automatic VLAN... |
led-beacon | led-beacon | [edit interfaces interface-name (with port number)] | This command causes the LED for the specified port to flash green. You can use the command to
physically locate a specific optic port on the PIC.
NOTE: At the [edit interfaces interface-name (with port number)] hierarchy level, you must
include the port number as part of the interface name. For example, et-x/y/z(:n). | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F3 and 16.1R2. | [] |
legacy-redirect-ip-action | legacy-redirect-ip-action {
send;
receive;
} | [edit protocols bgp group group-name family (inet | inet-vpn) flow],
[edit protocols bgp group group-name neighbor address family (inet | inet-vpn) flow],
[edit routing-instances routing-instance-name protocols bgp group group-name family (inet | inet-
vpn) flow],
[edit routing-instances routing-instance-name protocols... | Configure the legacy redirect to IP action for flow specification routes to provide traffic filtering options
for DDos mitigation in service provider networks. You can choose to accept legacy redirect to IP action
as specified in the Internet draft draft-ietf-idr-flowspec-redirect-ip-00.txt, BGP Flow-Spec Extended
Comm... | [
{
"name": "send",
"desc": "Advertise the redirect action as legacy redirect attribute. Specify this option to encode redirect to IP action as flow spec redirect to IP next-hop attribute and advertise the next-hop attribute with the redirect address."
},
{
"name": "receive",
"desc": "Accept legac... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R1. | [
"Configuring BGP Flow Specification Action Redirect to IP to Filter DDoS Traffic",
"Understanding BGP Flow Routes for Traffic Filtering"
] |
less-than | less-than value; | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from attribute name
format integer],
[edit unified-edge gateways tdf gateway-name domain-selection term term-name from attribute name
format time] | Specify a value for the custom AVP attribute below which the incoming RADIUS request from the
subscriber must match.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selected. | [
{
"name": "value",
"desc": "Value that the attribute must be less than."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
level (App Engine Virtual Machine Management Service) | level (all | error| info | notice | verbose | warning) | [edit system processes app-engine-virtual-machine-management-service traceoptions] | 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": "all",
"desc": "Match all levels."
},
{
"name": "error",
"desc": "Match error conditions."
},
{
"name": "info",
"desc": "Match informational messages."
},
{
"name": "notice",
"desc": "Match conditions that must be handled specially."
},
{
"name": "verbos... | system-control | Statement introduced in Junos OS Release 15.1F3.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [] |
level (CFM MEP) | level value; | [edit protocols oam ethernet connectivity-fault-management action-profile action-profile-name
action log-and-generate-ais] | Configure the server maintenance domain level for the MEP. | [
{
"name": "value",
"desc": "Maintenance domain level. Range: 1 through 7"
}
] | 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. | [
"Ethernet Alarm Indication Signal (ETH-AIS) Function Overview",
"Configuring ETH-AIS on a CFM MEP"
] |
level (Connectivity Fault Management) | level number; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name] | A number used in connectivity fault management (CFM) messages to identify the maintenance
association. The number is embedded in each of the CFM frames. CFM messages within a given level
are processed by maintenance end points (MEPs) at the same level. For example, the operator domain
can be level 0, the provider domai... | [
{
"name": "number",
"desc": "A number used to identify the maintenance domain to which the CFM message belongs."
}
] | 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. | [
"Creating a Maintenance Domain"
] |
level (Disk Partition) | level (full | high)
{
free-space threshold-value (mb | percent);
} | [edit chassis disk-partition partition-name] | Select the desired threshold state for triggering the alarm. | [
{
"name": "state",
"desc": "Select the desired threshold state for triggering the alarm. Note: You cannot monitor more than"
},
{
"name": "full",
"desc": "Set the threshold for indicating that the disk usage is full. Full disk usage is indicated when the"
},
{
"name": "high",
"desc":... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3 for EX Series switches.
RELATED INFORMATION
•
request system partition hard-disk
•
show system storage partitions | [] |
level (EX Series Switch Only) | level number; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name] | Configure a number to be used in CFM messages to identify the maintenance association. | [
{
"name": "number",
"desc": "Number used to identify the maintenance domain to which the CFM message belongs."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Ethernet OAM Connectivity Fault Management (CLI Procedure)",
"Junos OS Network Interfaces Configuration Guide"
] |
level (Global IS-IS) | level level-number {
authentication-key key;
authentication-key-chain (Protocols IS-IS) key-chain-name;
authentication-type type;
disable;
external-preference preference;
no-authentication-check;
no-csnp-authentication;
no-hello-authentication;
no-psnp-authentication;
preference ... | [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] | Configure the global-level properties.
You can administratively divide a single AS into smaller groups called areas. You configure each routing
device interface to be in an area. Any interface can be in any area. The area address applies to the entire
routing device. You cannot specify one interface to be in one area a... | [
{
"name": "level-number",
"desc": "The IS-IS device level number, which can be 1 or 2. The default is for the device to operate as both a Level 1 and 2 device."
},
{
"name": "authentication-key key",
"desc": "Authentication key (password). Neighboring devices use the password to verify the authe... | 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. | [
"Understanding IS-IS Configuration",
"Example: Configuring IS-IS",
"Understanding IS-IS Areas to Divide an Autonomous System into Smaller Groups",
"Example: Configuring a Multi-Level IS-IS Topology to Control Interarea Flooding"
] |
level (IS-IS Interfaces) | level level-number {
application-specific {
attribute-group name {
admin-group name;
advertise-delay-metric
application flex-algorithm;
srlg name1, name2;
te-metric metric;
}
}
hello-authentication-key key;
hello-authentication-key-... | [edit logical-systems logical-system-name protocols isis interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis
interface interface-name],
[edit protocols isis interface interface-name],
[edit routing-instances routing-instance-name protocols isis in... | Configure the IS-IS level. You can configure one instance of Level 1 routing and one instance of Level 2
routing on each interface, and you can configure the two levels differently. | [
{
"name": "level-number",
"desc": "The IS-IS level number, which can be 1 or 2. The default is for the device to operate as both a Level 1 and 2 device."
},
{
"name": "application-specific",
"desc": "Configure and advertise application (flexible algorithm) specific TE attributes such as delay-me... | 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. | [
"Understanding IS-IS Configuration",
"Example: Configuring IS-IS",
"Understanding IS-IS Areas to Divide an Autonomous System into Smaller Groups",
"Example: Configuring a Multi-Level IS-IS Topology to Control Interarea Flooding"
] |
level (OAM) | level level; | [edit ethernet-switching-options storm-control interface (all | interface-name)] | For interfaces that are enabled for storm control, configure the storm control level as a percentage of
the combined traffic streams that are subject to storm control on that interface.
Default
When storm control is enabled on an interface, the default storm control level is 80 percent of the
combined traffic streams t... | [
{
"name": "level",
"desc": "Percentage of the combined traffic streams that are subject to storm control on that interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in JUNOS Release 9.1 .
Statement deprecated in JUNOS Release 9.5 for EX Series switches.
Statement reinstated in JUNOS Release 11.4 for EX Series switches. | [
"Configuring Autorecovery for Port Security Events",
"Understanding Storm Control"
] |
level (Protocols RIFT) | level {
auto;
configured-value value;
leaf;
top-of-fabric;
} | [edit protocols rift] | Configure the level to identify the role of node in the RIFT topology.
If you do not specify any options under the level statement, the default option is auto level. | [
{
"name": "auto",
"desc": "(Optional) Enable zero touch provisioning to identify the level of the node automatically."
},
{
"name": "configured-value",
"desc": ""
},
{
"name": "value",
"desc": "(Optional) Enter the configured value of the level. Range: 1 through 23"
},
{
"na... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4R1. | [
"Understanding Junos Implementation of Routing in Fat Tree (RIFT) Protocol"
] |
level (Services) | level [brief | detail | extensive | verbose]]; | [edit services ssl traceoptions] | 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": "brief",
"desc": "Specify brief debugging output."
},
{
"name": "detail",
"desc": "Specify detailed debugging output."
},
{
"name": "extensive",
"desc": "Specify extensive debugging output."
},
{
"name": "verbose",
"desc": "Specify verbose debugging output."
}... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. | [
"Configuring SSL Forward Proxy"
] |
license | license {
autoupdate {
url url <password password>;
}
keys {
key key
}
renew {
before-expiration number;
interval interval-hours;
}
traceoptions {
file {
filename;
files number;
match regular-expression;
... | [edit system] | 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": "autoupdate",
"desc": "Autoupdate license keys from license servers."
},
{
"name": "before-expiration number",
"desc": "License renewal lead time before expiration, in days. Range: 0 through 60 days"
},
{
"name": "interval interval-hours",
"desc": "License checking interva... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5.
Options keys introduced in Junos OS Release 14.1X53-D10. | [] |
license-mode | license-mode IR | R | [edit chassis fpc slot-number] | Configures the FPC’s license mode. This can be used to track the number of PICs configured for a
specific mode. | [
{
"name": "IR",
"desc": "Sets the PIC to LSR mode."
},
{
"name": "R",
"desc": "Sets the PIC to full IP mode. NOTE: Starting in Junos OS Release 16.1R3 for PTX Series routers, the IR and R options are used. For previous releases (starting in Junos OS Release 15.1F3) the Ip (full IP mode) and lsr ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F3. | [] |
license-server | license-server {
ip-address address;
log-interval seconds;
services (jflow | cgnat | firewall);
} | [edit] | On MX Series routers with MS-MICs and MS-MPCs, configure the capability to transmit the throughput
details per service for the Junos Address Aware, Junos Traffic Vision, and Junos Network Secure services
in the last time interval to an external log collector. | [
{
"name": "ip-address",
"desc": ""
},
{
"name": "address",
"desc": "Use the specified IP address of the license log server."
},
{
"name": "log-interval",
"desc": ""
},
{
"name": "seconds",
"desc": "Use the specified frequency at which throughput data must be sent from the... | 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. | [
"License Server Management for Throughput Data Export on MX Series Routers for NAT, Firewall, and",
"Inline Flow Monitoring Services"
] |
lie-receive-address (Protocols RIFT) | lie-receive-address {
family {
(inet ipv4-address | inet6 ipv6-address);
}
} | [edit protocols rift] | Configure the address on which the link information elements (LIEs) should be received. | [
{
"name": "family",
"desc": "Specify the family type for the RIFT protocol interface on which the LIEs should be received."
},
{
"name": "inet ipv4-address",
"desc": "Specify the IPv4 IP address of the RIFT protocol interface on which the LIEs should be recieved."
},
{
"name": "inet6 ipv... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4R1. | [
"Understanding Junos Implementation of Routing in Fat Tree (RIFT) Protocol"
] |
lie-transmit-address (Protocols RIFT) | lie-transmit-address {
family {
(inet ipv4-address | inet6 ipv6-address);
}
} | [edit protocols rift interface interface-name] | Configure the IPv4 or IPv6 IP address on which the link information elements (LIEs) should be sent to
discover neighbors on the other side of the link. | [
{
"name": "family",
"desc": "Specify the family type for the RIFT protocol interface on which the LIEs should be sent."
},
{
"name": "inet ipv4-address",
"desc": "Specify the IPv4 IP address of the RIFT protocol interface on which the LIEs should be sent."
},
{
"name": "inet6 ipv6-addres... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4R1. | [
"Understanding Junos Implementation of Routing in Fat Tree (RIFT) Protocol"
] |
lifetime (Router Advertisement) | lifetime seconds; | [edit logical-systems logical-system-name protocols router-advertisement interface interface-name
dns-server-address address],
[edit protocols router-advertisement interface interface-name dns-server-address address] | Specify the maximum time in seconds for which the recursive DNS server address remains valid. The
device can use the specified recursive DNS server address for DNS name resolution until the time
specified by this statement.
seconds– Maximum time for which the recursive DNS server address remains valid. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Understanding Recursive DNS Servers for IPv6",
"Example: Configuring Recursive DNS Server Addresses for IPv6 Hosts"
] |
lifetime (Router Discovery) | lifetime seconds; | [edit logical-systems logical-system-name protocols router-discovery interface interface-name],
[edit protocols router-discovery interface interface-name] | Specify how long the addresses sent by the server in its router advertisement packets are valid. This
time must be long enough so that another router advertisement packet is sent before the lifetime has
expired. The lifetime value is placed in the advertisement lifetime field of the router advertisement
packet. If this... | [
{
"name": "seconds",
"desc": "Lifetime value. A value of 0 indicates that one or more addresses are no longer valid."
},
{
"name": "30 minutes (9000 seconds)",
"desc": "Default: 1800 seconds (30 minutes, which is three times the default value for the max-advertisement-interval statement)"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Understanding the ICMP Protocol for Discovering Gateways to Other Networks",
"Example: Configuring the ICMP Protocol for Discovering Gateways to Other Networks"
] |
lifetime-seconds (Security) | <lifetime-seconds seconds>; | [edit security ike proposal ike-proposal-name],
[edit security ipsec proposal ipsec-proposal-name] | (Optional) Configure the lifetime of IKE or IPsec SA. When the SA expires, it is replaced by a new SA
(and SPI) or terminated. | [
{
"name": "seconds",
"desc": "Lifetime, in seconds."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Lifetime for an IKE SA",
"Configuring the Lifetime for an IPsec SA"
] |
lifetime-seconds | lifetime-seconds seconds; | [edit services ipsec-vpn ike proposal proposal-name],
[edit services ipsec-vpn ipsec proposal proposal-name] | Configure the lifetime of an IKE or IPsec SA. This statement is optional. | [
{
"name": "seconds",
"desc": "Lifetime"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IKE Proposals",
"Configuring IPsec Proposals",
"Configuring Security Associations"
] |
light | [edit services monitoring twamp server] | Enable the Two-Way Active Measurement Protocol (TWAMP) server for light control on the UDP port
that reflects the test packets. If you want the default IANA port for TWAMP (862), you do not need to
configure the port option. To complete the configuration for light control, you also need to configure the
control-type li... | [
{
"name": "offload-type",
"desc": ""
},
{
"name": "(none | inline-timestamp |",
"desc": ""
},
{
"name": "pfe-timestamp)",
"desc": "Enable timestamping of TWAMP probe messages in the Routing Engine, inline in the hardware, or Packet Forwarding Engine host processor. Prior to Junos OS ... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved 20.3R1.
Support added in Junos OS Release 21.1R1.
offload-type and stateful-sequence options introduced in Junos OS Evolved Release 23.4R1. | [
"Understanding Two-Way Active Measurement Protocol on Routers"
] | |
light-weight-dhcpv6-relay | lightweight-dhcpv6-relay; | [edit vlans vlan-name forwarding-options dhcp-security dhcpv6-options] | Configure a Lightweight DHCPv6 Relay Agent (LDRA) to insert relay agent information in messages sent
from a DHCPv6 client to a server or other relay agent on the same IPv6 link. The LDRA acts as a relay
agent, but without performing the routing function necessary to forward messages to a server or relay
agent that resi... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R3. | [
"Using Lightweight DHCPv6 Relay Agent (LDRA)"
] |
limit (Content Security Policy) | limit value; | [edit security utm default-configuration]
[edit security utm utm-policy policy-name traffic-options sessions-per-client] | In an attempt to consume all available resources and hinder the ability of the device, a malicious user
might generate a large amount of traffic all at once. To prevent such activity from succeeding, you can
impose a session throttle to limit sessions. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
limit (Security Log) | limit value; | [edit security log cache]
[edit logical-systems name security log cache]
[edit tenants tenant-name security log cache] | Specify the number of security log entries to be kept in memory. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.2.
The [edit logical-systems name security log cache] and [edit tenants tenant-name security log cache]
hierarchy levels introduced in Junos OS Release 19.1R1. | [] |
limit (Security SCTP) | limit {
address name {
payload-protocol (asap | bicc | ddp-segment | ddp-stream | diameter-dtls | diameter-sctp
| dua | enrp | h248 | h323 | id | iua | m2pa | m2ua | m3ua | others | qipc | reserved | s1ap |
simco | sua | tali | v5ua | x2ap) {
rate rate;
}
}
payload-protocol (a... | [edit security sctp profile profile-name] | Use the limit option to set the rate limit per association for local Services Processing Unit (SPU) packets.
You can configure a GPRS SCTP profile by setting the limit rate parameter and the payload protocol
parameter for SCTP inspection.
From Junos OS Release 20.4R1 onwards, the [edit security gprs sctp profile profil... | [
{
"name": "address ip-address",
"desc": "To set Signalling Connection Control Part (SCCP), Subsystem-Prohibited (SSP), and Subsystem Status Test (SST) messages rate limit to an IP address. The IP address can accept either an IPv4 address or an IPv6 address."
},
{
"name": "sccp rate-limit",
"desc... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. Statement is modified in Junos OS Release 12.1X46-
D10. Support for address option accepting both IPv4 and IPv6 formats added in Junos OS Release
12.1X47-D10. | [
"Understanding Stream Control Transmission Protocol",
"SCTP Packet Structure Overview"
] |
limit | limit max-sub-sessions; | [edit services service-set services-set-name subscriber-profile profile-name max-data-sessions-
per-subscriber] | Specify the limit for the maximum number of subscriber sessions. | [
{
"name": "max-sub-sessions",
"desc": "Maximum number of subscriber sessions."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [] |
limit-ports-per-address | limit-ports-per-address number; | [edit services nat pool nat-pool-name] | Specify the limit for number of ports allocated per host (IP address). | [
{
"name": "number",
"desc": "Number of ports allocated per host (IP address). Range: 2 through 65,435"
}
] | 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. | [
"Configuring Pools of Addresses and Ports for Network Address Translation Overview"
] |
limit-session (IDS Screen Next Gen Services) | limit-session {
by-destination{
by-protocol {
icmp {
maximum-sessions number;
packet-rate number;
session-rate number;
}
tcp {
maximum-sessions number;
packet-rate number;
sess... | [edit services screen ids-option screen-name] | Configure session limits for individual destination or source addresses, or for individual destination or
source subnets. This protects against network probing attacks and network flooding attacks. You can
specify limits for specific protocols (ICMP, TCP, and UDP), or specify limits independent of a protocol.
When a se... | [] | 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"
] |
limit-session | limit-session {
destination-ip-based number;
source-ip-based number;
} | [edit security screen ids-option screen-name] | Limit the number of concurrent sessions the device can initiate from a single source IP address or the
number of sessions it can direct to a single destination IP address. | [] | 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"
] |
limited-ifl-scaling | limited-ifl-scaling; | [edit chassis network-services enhanced-ip] | Limits the maximum number of logical interfaces on MX Series routers with MS-DPCs to 64,000 for
enhanced IP network services mode. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Junos OS Release 15.1R3. | [
"Configuring Network Services Mode",
"Configuring Network Services Mode",
"Configuring Enhanced IP Network Services for a Virtual Chassis"
] |
line-encoding (E1 Options) | line-encoding (ami | hdb3); | [edit chassis synchronization interfaces external e1-options],
[edit chassis synchronization interfaces (external-0/0 | external-1/0) e1-options] | Configure the line encoding format on the E1 interface. | [
{
"name": "ami",
"desc": "Set the line encoding format as automatic mark inversion."
},
{
"name": "hdb3",
"desc": "Set the line encoding format as high-density bipolar 3 code."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [] |
line-encoding (T1 Options) | line-encoding (ami | b8zs); | [edit chassis synchronization interfaces external t1-options],
[edit chassis synchronization interfaces (external-0/0 | external-1/0) t1-options] | Configure the line encoding format on the T1 interface. | [
{
"name": "ami",
"desc": "Set the line encoding format as automatic mark inversion."
},
{
"name": "b8zs",
"desc": "Set the line encoding format as 8-bit zero suppression."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [] |
line-identity (Dynamic Access-Line-Identifier VLANs) | line-identity {
dynamic-profile profile-name;
includes {
accept-no-ids {
mac-address;
}
circuit-id;
remote-id;
}
} | [edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit auto-configure],
[edit interfaces interface-name unit logical-unit-number auto-configure] | Configure the access-line identifier received in DHCP or PPPoE discovery packets as a trusted option
that is accepted for dynamically creating a VLAN on a static or dynamic underlying VLAN interface
according to the specified dynamic profile.
The remaining statements are explained separately. Search for a statement in... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS 17.1.
mac-address option introduced in Junos OS 25.2R1. | [
"Configuring Dynamic Underlying VLAN Interfaces to Use Access-Line Identifiers",
"Configuring Dynamic VLAN Subscriber Interfaces Based on Access-Line Identifiers"
] |
line-interval (Dampen Options) | line-interval line-interval; | [edit event-options event-script dampen dampen-options],
[edit event-options event-script file filename dampen dampen-options],
[edit system scripts commit dampen dampen-options],
[edit system scripts op dampen dampen-options],
[edit system scripts op file filename dampen dampen-options] | Specify the number of lines of scripts to execute before pausing.
Script dampening is initiated when CPU use exceeds the value specified using the cpu-factor statement.
Junos OS then executes the number of lines of script specified using the line-interval statement and
then pauses script execution for the time specifie... | [
{
"name": "line-interval",
"desc": "Specify the line interval at which to pause. Range: 1 through 4,294,967,295 Default: 10"
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Dampen Script Execution"
] |
line-loopback | (line-loopback-enable | no-line-loopback); | [edit interfaces interface-name otn-options] | Specify whether line-loopback is enabled or disabled.
Default
If you omit the line-loopbback-enable statement, line-loopback is disabled. | [
{
"name": "line-loopback-enable",
"desc": "Enable line-loopback."
},
{
"name": "no-line-loopback",
"desc": "Disable line-loopback."
}
] | 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"
] |
line-protocol | line-protocol protocol; | [edit interfaces interface-name serial-options] | For serial interfaces only, configure the line protocol. | [
{
"name": "protocol",
"desc": "You can specify the one of the following line protocols:"
},
{
"name": "eia530",
"desc": "Line protocol EIA-530"
},
{
"name": "v.35",
"desc": "Line protocol V.35"
},
{
"name": "x.21",
"desc": "Line protocol X.21"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Serial Line Protocol"
] |
line-rate (Interfaces) | line-rate | [edit interfaces interfaces name shdsl-options] | Specify a line rate for an G.SHDSL interface. | [
{
"name": "auto",
"desc": "Automatically selects a line rate."
},
{
"name": "value",
"desc": "Select the values between 192 kbps and 22784 kbps for the speed of transmission of data on"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Junos OS Release 10.0. | [] |
line-rate | line-rate line-rate; | [edit interfaces interface-name shdsl-options],
[edit logical-systems logical-system-name interfaces interface-name shdsl-options] | For J Series Services Routers only, configure the SHDSL line rate. | [
{
"name": "line-rate",
"desc": "SHDSL line rate, in Kbps. Possible values are:"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [] |
linerate-mode | linerate-mode; | [edit chassis fpc slot-number pic pic-number linerate-mode],
[edit chassis lcc number fpc slot-number pic pic-number linerate-mode] | For 10-port 10-Gigabit Oversubscribed Ethernet (OSE) PICs only, configure the line rate operation. | [] | 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. | [
"Junos OS Network Interfaces Library for Routing Devices"
] |
link (Access) | link pool-name; | [edit access address-assignment pool] | Configure the name of the secondary address-assignment pool that is linked to a primary address-
assignment pool. The secondary pool provides a backup pool for local address assignment. | [
{
"name": "pool-name",
"desc": "Name of the address assignment pool."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 10.4 of Junos OS. | [
"Firewall User Authentication Overview",
"Obtaining Username and Role Information Through Firewall Authentication"
] |
link-adjacency-loss | link-adjacency-loss; | [edit protocols oam ethernet link-fault-management
action-profile event] | Configure loss of adjacency event with the IEEE 802.3ah link fault management (LFM) peer. When
included, the loss of adjacency event triggers the action specified under the "action" on page 1924
statement. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Example: Configuring Ethernet OAM Link Fault Management",
"Configuring Ethernet OAM Link Fault Management"
] |
link-degrade-monitor | link-degrade-monitor {
(link-degrade-monitor-enable | no-link-degrade-monitor-enable);
actions media-based;
recovery {
(auto | manual);
timer timer;
}
thresholds {
clear clear-value;
interval interval-value;
set set-value;
warning-clear warning-clear-... | [edit interfaces interfaces- name] | Configure link degrade monitoring on an interface and when a link degrade event is detected, specify
the corrective action to be triggered. When configured, the feature monitors the quality of physical links
on Ethernet interfaces (10-Gigabit, 25-Gigabit, 40-Gigabit, 50-Gigabit, 100-Gigabit, 200-Gigabit and
400-Gigabit... | [
{
"name": "link-degrade-monitor-enable",
"desc": "Enable link degrade monitoring on an interface."
},
{
"name": "no-link-degrade-monitor-enable",
"desc": "Disable link degrade monitoring on an interface."
},
{
"name": "media-based",
"desc": "Action to be taken when a link degrade eve... | 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.
The options link-degrade-monitor-enable and no-link-degrade-monitor-enable are introduced in Junos OS
Evolved Release 20.1R1. | [
"Link Degrade Monitoring Overview",
"Common Output Fields Description"
] |
link-discovery | link-discovery (active | passive); | [edit protocols oam ethernet link-fault-management interface interface-name] | Specify the discovery mode used for IEEE 802.3ah Operation, Administration, and Maintenance (OAM)
link fault management (LFM) support. The discovery process is triggered automatically when OAM
802.3ah functionality is enabled on an interface. Link monitoring is done when the interface sends
periodic OAM PDUs.
For Ether... | [
{
"name": "active",
"desc": "In active mode, the interface discovers and monitors the peer on the link if the peer also"
},
{
"name": "passive",
"desc": "In passive mode, the peer initiates the discovery process."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Configuring Ethernet OAM Link Fault Management"
] |
link-down (QFX Series) | link-down (red | yellow | ignore); | [edit chassis alarm ethernet (Alarm)],
[edit chassis alarm fibre-channel],
[edit chassis interconnect-device name alarm ethernet (Alarm)],
[edit chassis node-group name alarm fibre-channel] | Specify either red, yellow, or ignore to display when the link is down. | [
{
"name": "red",
"desc": "Indicates that one or more hardware components have failed or exceeded temperature thresholds, or an alarm condition configured on an interface has triggered a critical warning."
},
{
"name": "yellow",
"desc": "Indicates a noncritical condition on the device that, if le... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.3. | [] |
link-down | link-down; | [edit protocols oam ethernet link-fault-management action-profile action] | Mark the interface as down for transit 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.4. | [
"Configuring Ethernet OAM Link Fault Management"
] |
link-event-rate | link-event-rate {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
} | [edit protocols oam ethernet link-fault-management
action-profile event] | Configure the number of link fault management (LFM) events per second.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Configuring Ethernet OAM Link Fault Management"
] |
link-fault-management | link-fault-management {
action-profile profile-name;
action {
syslog;
link-down;
}
event {
link-adjacency-loss;
link-event-rate {
frame-error count;
frame-period count;
frame-period-summary c... | [edit protocols oam ethernet] | Configure Ethernet OAM link fault management (LFM) for all interfaces or for specific interfaces.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Example: Configuring Ethernet OAM Link Fault Management",
"Configuring Ethernet OAM Link Fault Management"
] |
link-group-protection (Protocols IS-IS) | link-group-protection {
minimum-bandwidth rate;
revert-bandwidth rate;
} | [edit logical-systems logical-system-name protocols isis interface-group group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis
interface-group group-name],
[edit protocols isis interface-group group-name],
[edit routing-instances routing-instance-name protocols ... | Configure link group protection. This enables Packet Forwarding Engine-based local repair by pre-
downloading suboptimal backup paths with appropriate weights in the Packet Forwarding Engine. | [
{
"name": "minimum-bandwidth",
"desc": ""
},
{
"name": "rate",
"desc": "Minimum bandwidth to carry traffic. This is the minimum bandwidth at which the outgoing traffic can no longer be carried on this link group. When the bandwidth becomes less than or equal to this bandwidth, traffic will get l... | 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 for the MX Series. | [] |
link-layer-broadcast-inet-check | link-layer-broadcast-inet-check; | [edit forwarding-options] | Enable destination MAC and IP address check to prevent the Router from forwarding IPV4 packets,
which have link layer destination address set to broadcast or multicast, unless it is directed to an IPV4
multicast address. | [] | 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. | [] |
link-layer-overhead | link-layer-overhead percent; | [edit interfaces interface-name mlfr-uni-nni-bundle-options],
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | For link services IQ (lsq) interfaces only, configure the percentage of total bundle bandwidth to be set
aside for link-layer overhead. Link-layer overhead accounts for the bit stuffing on serial links. Bit stuffing
is used to prevent data from being interpreted as control information. Overhead resulting from link-laye... | [
{
"name": "percent",
"desc": "Percentage of total bundle bandwidth to be set aside for link-layer overhead."
}
] | 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 CoS Scheduling Queues on Logical LSQ Interfaces"
] |
link-management | link-management {
peer peer-name {
address ip-address;
control-channel control-channel-interface;
lmp-control-channel control-channel-interface {
remote-address ip-address;
}
lmp-protocol {
hello-dead-interval milliseconds;
hello-interval... | [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 rest... | [] | 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. | [
"LMP Configuration Overview"
] |
link-mode | link-mode mode; | [edit interfaces interface-name ether-options] | Set the device’s link-connection characteristic.
NOTE: Some QFX Series switch interfaces are full-duplex only. In such cases, the CLI
shows only “link-mode full-duplex” or does not include the “link-mode” statement at all.
You cannot configure the link mode on these interfaces; it is set to the full-duplex
default.
Def... | [
{
"name": "mode",
"desc": "Link characteristic:"
},
{
"name": "full-duplex",
"desc": "Connection is full duplex."
},
{
"name": "half-duplex",
"desc": "Connection is half duplex."
},
{
"name": "automatic",
"desc": "Link mode is negotiated."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring Gigabit and 10-Gigabit Ethernet Interfaces for EX4600 and QFX Series Switches",
"Junos OS Network Interfaces Library for Routing Devices"
] |
link-mtu | (link-mtu | no-link-mtu); | [edit logical-systems logical-system-name protocols router-advertisement interface interface-
name],
[edit protocols router-advertisement interface interface-name] | Specify whether to include the maximum transmission unit (MTU) option in router advertisement
messages:
•
link-mtu–Includes the MTU option in router advertisements.
•
no-link-mtu–Does not include the MTU option in router advertisements.
The MTU option included in router advertisement messages ensures that all nodes on ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS 10.3. | [
"Example: Configuring IPv6 Interfaces and Enabling Neighbor Discovery"
] |
link-protection (Chassis Cluster) | link-protection {
non-revertive;
} | [edit chassis aggregated-devices ethernet lacp] | Enable Link Aggregation Control Protocol (LACP) link protection at the global (chassis) level.
By default LACP link protection reverts to a higher-priority (lower-numbered) link when the higher-
priority link becomes operational or when a higher-priority link is added to the aggregated Ethernet
bundle.
You can suppress... | [
{
"name": "non-revertive",
"desc": "Disable the ability to switch to a better priority link (if one is available) after a link is established as active and a collection or distribution is enabled."
}
] | 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. | [
"Example: Configuring Aggregated Ethernet Device with LAG and LACP on a Security Device (CLI",
"Procedure)"
] |
link-protection (Dynamic LSPs) | link-protection; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name] | Enable link protection on the specified LSP, which helps to ensure that traffic sent over a specific
interface to a neighboring router can continue to reach the router if that interface fails. For point-to-
multipoint LSPs, including this statement extends link protection to all of the paths used by the LSP.
To fully e... | [] | 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 Link Protection for Point-to-Multipoint LSPs",
"Configuring Node Protection or Link Protection for LSPs"
] |
link-protection (Host Fast Reroute) | link-protection; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options interface interface-name],
[edit routing-instances routing-instance-name routing-options interface interface-name] | Enable link protection on a specified interface in a routing instance.
Configuring link protection on an interface ensures that traffic is rerouted to the destination device
through alternate loop-free paths that traverse the protected interface. | [] | 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: Configuring Link Protection with Host Fast Reroute"
] |
link-protection (non-LACP) | link-protection {
revertive | non-revertive;
} | [edit interfaces aex aggregated-ether-options] | User can specify the link-protection revertive statement in the link protection configuration at the
aggregated Ethernet interface level to set revertive mode. In revertive mode, adding a higher-priority
link to the aggregated Ethernet bundle results in recalculation of the priorities and traffic will switch
from the c... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R1. | [
"Configuring Aggregated Ethernet Link Protection"
] |
link-protection (Protocols IS-IS) | link-protection; | [edit logical-systems logical-system-name protocols isis interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis
interface interface-name],
[edit protocols isis interface interface-name],
[edit routing-instances routing-instance-name protocols isis in... | Enable link protection on the specified IS-IS interface. Junos OS creates a backup loop-free alternate
path to the primary next hop for all destination routes that traverse the protected interface. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Understanding Loop-Free Alternate Routes for IS-IS",
"Example: Configuring Node-Link Protection for IS-IS Routes in a Layer 3 VPN"
] |
link-protection (Protocols LACP) | link-protection {
non-revertive;
} | [edit chassis aggregated-devices ethernet lacp] | Enable LACP link protection at the global (chassis) 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"
] |
link-protection (Protocols OSPF) | link-protection; | [edit protocols (ospf | ospf3) area area-name interface interface-name],
[edit logical-systems logical-system-name protocols (ospf | ospf3) area area-name interface
interface-name],
[edit routing-instances routing-instance-name protocols (ospf | ospf3) area area-name interface
interface-name],
[edit logical-systems l... | Enable link protection on the specified OSPF interface. Junos OS creates a backup loop-free alternate
path to the primary next hop for all destination routes that traverse the protected interface.
NOTE: This feature calculates alternate next hop paths for unicast routes only.
Therefore, this statement is not supported ... | [] | 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 Link Protection for OSPF"
] |
link-protection (RSVP) | link-protection {
disable;
admin-group {
exclude [ group-names ];
include-all [ group-names ];
include-any [ group-names ];
}
bandwidth bps;
bypass bypass-name {
bandwidth bps {
ct0 bps;
ct1 bps;
ct2 bps;
ct3 bps;
... | [edit logical-systems logical-system-name protocols rsvp interface interface-name],
[edit protocols rsvp interface interface-name] | Enable link protection on the specified interface. Using link protection, you can configure a network to
reroute traffic quickly around broken links. To fully enable link protection, you also need to configure the
link-protection statement at the [edit protocols mpls label-switched-path lsp-name] hierarchy level. You c... | [
{
"name": "no-node-protection",
"desc": "Disable node-link protection on the RSVP interface. Link protection remains active."
}
] | 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.
Statement introduced in Junos OS Release 14.1X53-D10 for the QFX Series and for EX4600 switches. | [
"Configuring Link Protection on Interfaces Used by LSPs"
] |
link-protection (Static LSPs) | link-protection bypass-name name; | [edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
ingress],
[edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
transit incoming-label],
[edit protocols mpls static-label-switched-path lsp-name ingress],
[edit protocols mpls static-la... | Enable link protection on the specified static LSP. Link protection helps to ensure that traffic sent over a
specific interface to a neighboring router can continue to reach the router if that interface fails.
Default
Link protection is disabled. | [
{
"name": "bypass-name name",
"desc": "Bypass LSP name."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Configuring Static LSPs",
"Example: Configuring a Collection of Paths to Create an RSVP-Signaled Point-to-Multipoint LSP"
] |
link-protection | aggregated-ether-options {
lacp {
+ link-protection {
+ revertive | non-revertive;
+ disable
}
}
}
}
link–protection {
disable;
(revertive |non-revertive);
disable
} | [edit interfaces aex aggregated-ether-options]] | On the router, for aggregated Ethernet interfaces only, configure link protection. In addition to enabling
link protection, a primary and a secondary (backup) link must be configured to specify what links egress
traffic should traverse. To configure primary and secondary links on the router, include the primary and
bac... | [] | 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.
Support for disable, revertive, and non-revertive statements added in Junos OS Release 9.3. | [
"Configuring Aggregated Ethernet Link Protection",
"Configuring LACP Link Protection of Aggregated Ethernet Interfaces for Switches"
] |
link-protection-sub-group (802.3ad) | link-protection-sub-group group-name; | [edit interfaces interface-name ether-options 802.3ad] | Add an interface in an aggregated Ethernet bundle into a link-protection subgroup.
A link protection subgroup is created and named using the link-protection-sub-group statement in the [edit
interfaces aex aggregated-ether-options] hierarchy. | [
{
"name": "group-name",
"desc": "Name of the link protection subgroup that will include this interface after this statement is entered. The link protection subgroup is named when it is created using the link-protection-sub-group statement in the [edit interfaces aex aggregated-ether-options] hierarchy."
}... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10. | [
"Configuring Aggregated Ethernet Links (CLI Procedure)",
"Configuring LACP Link Protection of Aggregated Ethernet Interfaces for Switches",
"Q-in-Q Support on Redundant Trunk Links Using LAGs with Link Protection"
] |
link-protection-sub-group (aggregated-ether-options) | link-protection-sub-group group-name {
[primary | backup];
} | [edit interfaces aex aggregated-ether-options] | Create and name a link protection subgroup.
Link protection subgroups allow you to provide link protection to a collection of Ethernet links within a
link aggregation group (LAG). If you need to provide link protection to a single link in a LAG, you do not
need to configure link protection subgroups.
A link protection ... | [
{
"name": "group-name",
"desc": "User-provided name of the link protection subgroup."
},
{
"name": "primary",
"desc": "Subgroup is the primary subgroup."
},
{
"name": "backup",
"desc": "Subgroup is the backup subgroup."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10. | [
"Configuring Aggregated Ethernet Links (CLI Procedure)",
"Configuring LACP Link Protection of Aggregated Ethernet Interfaces for Switches",
"Q-in-Q Support on Redundant Trunk Links Using LAGs with Link Protection"
] |
link-speed (Aggregated Ethernet) | link-speed (100m | 10g| 10m | 1g| 2.5g| 25g| 400g| 40g| 50g| 5g| 80g| 8g| mixed| oc192); | [edit interfaces aex aggregated-ether-options],
[edit interfaces interface-range name aggregated-ether-options],
[edit interfaces interface-range name aggregated-sonet-options] | For aggregated Ethernet interfaces only, set the required link speed. You can specify speed in bits per
second either as a complete decimal number or as a decimal number followed by the abbreviation k
(1000), m (1,000,000), or g (1,000,000,000). By default, the speed of the first aggregated interface that
you add to th... | [
{
"name": "100m",
"desc": "(EX Series, QFX5100, QFX100002, QFX100008, QFX100016 switches, MX Series, PTX Series"
},
{
"name": "10g",
"desc": "(EX Series, QFX5100, QFX100002, QFX100008, QFX100016 switches, MX Series, PTX Series"
},
{
"name": "10m",
"desc": "(EX Series, QFX5100, QFX100... | 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.
mixed option added in Junos OS Release 15.1F3 and 16.1R2 for PTX5000 routers and 15.1F6 and 16.1R2
for PTX3000 routers. | [
"Aggregated Ethernet Interfaces Overview",
"Configuring Aggregated Ethernet Link Speed",
"Configuring Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles",
"Configuring Aggregated Ethernet Links (CLI Procedure)",
"Example: Configuring Aggregated Ethernet High-Speed Uplinks Between an EX4200 Virtual C... |
link-speed (Aggregated SONET/SDH) | link-speed (speed | mixed); | [edit interfaces asx aggregated-sonet-options] | For aggregated SONET/SDH interfaces only, set the required link speed. | [
{
"name": "speed",
"desc": "Aggregated SONET/SDH links can have one of the following speed values."
},
{
"name": "oc3",
"desc": "Links are OC3c or STM1c."
},
{
"name": "oc12",
"desc": "Links are OC12c or STM4c."
},
{
"name": "oc48",
"desc": "Links are OC48c or STM16c."
... | 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.
mixed option added in Release 8.0. | [
"Configuring Aggregated Ethernet Link Speed",
"Configuring Aggregated SONET/SDH Interfaces"
] |
link-speed (Interfaces) | link-speed speed; | [edit interfaces interface-name redundant-ether-options] | For redundant Ethernet interfaces in a chassis cluster only, set the required link speed. | [
{
"name": "speed",
"desc": "For redundant Ethernet links, you can specify speed in bits per second either as a complete"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement modified in Release 9.0 of Junos OS. | [] |
link-speed | link-speed speed; | [edit interfaces aex aggregated-ether-options],
[edit interfaces interface-range name aggregated-ether-options],
[edit interfaces interface-range name aggregated-sonet-options] | For aggregated Ethernet interfaces only, set the required link speed. | [
{
"name": "speed",
"desc": "For aggregated Ethernet links, you can specify speed in bits per second either as a complete"
},
{
"name": "100m",
"desc": "Links are 100 Mbps."
},
{
"name": "10g",
"desc": "Links are 10 Gbps."
},
{
"name": "1g",
"desc": "Links are 1 Gbps."
}... | 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 Links (CLI Procedure)",
"Example: Configuring Aggregated Ethernet High-Speed Uplinks Between an EX4200 Virtual Chassis",
"Access Switch and an EX4200 Virtual Chassis Distribution Switch"
] |
link-to-disable | link-to-disable interface-name; | [edit protocols uplink-failure-detection group group-name] | Configure the downlink interfaces to be disabled when the switch detects an uplink failure. The switch
can monitor a maximum of 48 downlink interfaces in a group.
NOTE: In QFX5120 and QFX5210 Series switches, you can configure a maximum of 128
downlink interfaces. | [
{
"name": "interface-name",
"desc": "Name of the downlink interface or interface range in the group. The interface can be a physical interface or a logical interface."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [] |
link-to-monitor | link-to-monitor interface-name; | [edit protocols uplink-failure-detection group group-name] | Configure the uplink interfaces to be monitored for uplink failure detection. The switch can monitor a
maximum of 48 uplink interfaces in a group.
NOTE: In QFX5120 and QFX5210 Series switches, you can configure a maximum of 128
uplink interfaces.
An interface can be configured as link-to-monitor in multiple groups. | [
{
"name": "interface-name",
"desc": "Name of the uplink interface or interface range in the group. The interface can be a physical interface or a logical interface."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [] |
link-tracking (Network Isolation Groups) | link-tracking {
failure-type <link>;
interface name;
minimum-links count;
} | [edit protocols network-isolation group name detection] | Track the link status of the configured interface or interfaces to detect network isolation conditions. You
configure this statement when you define a network isolation group that you apply to a bridge domain,
VLAN, or EVPN instance (EVI). | [
{
"name": "(Required) failure-type link",
"desc": "Type of failure. The only supported failure type currently is link for link failures, which is also the default failure type."
},
{
"name": "interface",
"desc": ""
},
{
"name": "{interface-name |",
"desc": ""
},
{
"name": "[i... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 23.1R1. | [
"Determine IRB Interface State Changes from Local L2 Interface or Remote Connectivity Status in",
"EVPN Fabrics"
] |
linkdown (satellite-policies alarm) | linkdown [ignore | red | yellow] | [edit policy-options satellite-policies environment-monitoring-policy policy-name alarm] | Configure the alarm behavior when an Ethernet link goes down on a satellite device in a Junos Fusion.
The configured alarm behavior can be applied to any satellite device in the Junos Fusion. The alarm
behavior is applied to satellite devices using environment monitoring policies. | [
{
"name": "ignore",
"desc": "Do not signal an alarm when an Ethernet link-down event occurs."
},
{
"name": "red",
"desc": "Raise a major alarm when an Ethernet link-down event occurs."
},
{
"name": "yellow",
"desc": "Raise a minor alarm when an Ethernet link-down event occurs."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring Satellite Device Alarm Handling Using an Environment Monitoring Satellite Policy in a",
"Junos Fusion",
"Understanding Satellite Policies in a Junos Fusion"
] |
linked-pool-aggregation (Address-Assignment Pools) | linked-pool-aggregation; | [edit access] | Change how the search for an available address is performed. When you include this statement, all
ranges in the matching pool are searched, but only from the last-saved next address to the highest
address in the range. The same search is performed as necessary in a linked pool, through the end of the
chain of pools. Th... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"Configuring Address-Assignment Pool Linking",
"Address Allocation from Linked Address Pools",
"Address-Assignment Pools Overview",
"Address-Assignment Pool Configuration Overview"
] |
linktrace | linktrace {
age (30m | 10m | 1m | 30s | 10s);
path-database-size path-database-size;
} | [edit protocols oam ethernet connectivity-fault-management] | Configure connectivity fault management linktrace parameters. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring Linktrace Protocol in CFM"
] |
LIST (DTCP) | LIST DTCP/0.7
Csource-ID: user-name
Cdest-ID: variable
Flags: BOTH
Seq: sequence-number
Authentication-Info: ssh-authentication-string | Request information that is returned in a LIST response. The response lists triggers only. It does not
return sessions that are being mirrored. This DTCP message is supported for both FlowTapLite and
radius-flow-tap services.
NOTE: Consult the documentation for your mediation device to learn how to configure
DTCP mess... | [
{
"name": "ssh-authentication-string",
"desc": "String used when you are using SSH to connect to the router."
}
] | Not applicable.
Sample Output
LIST DTCP
LIST DTCP/0.7
Csource-ID: dtcp1
Cdest-ID: cd1
Flags: BOTH
Seq: 9
Authentication-Info: f6dd64643021debb167ce2fb2d3c7b6622a87e09
DTCP/0.7 200 OK
SEQ: 9
TIMESTAMP: 2011-02-13 15:57:47.667
CRITERIA-ID: 2
CSOURCE-ID: dtcp1
CDEST-ID: cd1
CSOURCE-ADDRESS: 203.0.113.224
FLAGS: BOTH
AVER... | [
"DTCP Messages Used for Subscriber Secure Policy",
"DTCP-Initiated Subscriber Secure Policy Overview"
] | ||
list (Security Content Filtering Block Mime) | list list-name; | [edit security utm default-configuration]
[edit security utm feature-profile content-filtering profile profile-name block-mime] | Configure the content filter to use MIME block lists (custom objects). | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Content Filtering Overview"
] |
list | list listname {
exception listname;
} | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus mime-whitelist] | Configure the antivirus scanner to use MIME bypass lists (custom objects). If you want to have
exceptions to the allowlist, create a mime-pattern list with the exception statement in addition to the list
statement. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
listen | listen address <port port>; | [edit logical-systems logical-system-name protocols sap],
[edit protocols sap] | Specify an address and optionally a port on which SAP and SDP listen, in addition to the default SAP
address and port on which they always listen, 224.2.127.254:9875. To specify multiple additional
addresses or pairs of address and port, include multiple listen statements. | [
{
"name": "address",
"desc": "(Optional) Address on which SAP listens for session advertisements."
},
{
"name": "port port",
"desc": "(Optional) Port on which SAP listens for session advertisements."
}
] | 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 Session Announcement Protocol"
] |
listening-mode | listening-mode; | [edit security gtp profile profile-name] | Use listening-mode to enable listening-mode for GTP inspection.
The SRX Series firewall enables GPRS tunneling protocol (GTP) listening mode on the S5, S8, or S11
interface. In listening mode, the firewall performs sanity check and stateful inspection on GTP packets.
Any failure in the GTP packet processing will stop t... | [] | security | Statement introduced in Junos OS Release 20.4R1. | [] |
liveness-detection (high availability) | liveness-detection {
no-adaptation;
detection-time {
threshold milliseconds;
}
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier multiplier;
transmit-interval {
minimum-interval milliseconds;
thresh... | [edit chassis high-availability peer-id]
[edit chassis high-availability peer-id peer-forwarding-ip]
[edit chassis high-availability peer-domain-id peer-id] | Configure Bidirectional Forwarding Detection (BFD) options for the peer node. | [
{
"name": "no-adaption",
"desc": "Disable adaptation."
},
{
"name": "detection-time",
"desc": "Specify BFD failure detection time."
},
{
"name": "threshold",
"desc": "Specify the threshold for the adaptation of the BFD session detection"
},
{
"name": "minimum-interval",
"... | interface | Statement introduced in Junos OS Release 20.4R1. | [
"Multinode High Availability",
"Example: Configure Multinode High Availability in a Layer 3 Network"
] |
liveness-detection (iccp-peer) | liveness-detection {
detection-time {
threshold milliseconds;
}
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (1 | a... | [edit protocols iccp peer] | Enable Bidirectional Forwarding Detection (BFD). BFD enables rapid detection of communication
failures between peers.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [] |
liveness-detection | liveness-detection {
failure-action (clear-binding | clear-binding-if-interface-up | log-only);
method {
bfd {
version (0 | 1 | automatic);
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
... | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit forwarding-options dhcp-relay dhcpv6 group group-name],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name ],
[edit forwarding-options dhcp-relay group group-name],
[edit system services dhcp-local-server],... | Configure bidirectional failure detection timers and authentication criteria for static routes.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | 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. | [
"DHCP Liveness Detection Overview",
"Configuring Detection of DHCP Local Server Client Connectivity with BFD",
"Configuring Detection of DHCP Relay or DHCP Relay Proxy Client Connectivity with BFD",
"Example: Configuring Group Liveness Detection with BFD for DHCP Local Server Clients",
"Example: Configuring... |
lldp | lldp {
advertisement-interval seconds;
(disable | enable);
hold-multiplier number;
{
chassis-id (chassis-id-type | chassis-id-value)
}
interface (all | [interface-name]) {
(disable | enable);
power-negotiation <(disable | enable)>;
tlv-filter;
tlv-select;
trap... | [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": "advertisement-interval seconds",
"desc": "Specify the frequency at which LLDP advertisements are sent. This value is also used in combination with the hold-multiplier value to determine the length of time LLDP information is held before it is discarded. The advertisement-interval value must be gr... | 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.
management-address introduced in Junos OS Release 9.5.
netbios-snooping introduced in Junos OS Release 11.1 for EX2200, EX3200, EX3300, EX4200, EX4500,
EX4550, EX6210, EX8208, and EX8216 switches.
port-description-type introduced in Junos OS Release 13.3R5, 14.2R2, 14.1R4, ... | [
"Configuring LLDP",
"Configuring LLDP (CLI Procedure)",
"Understanding LLDP",
"Understanding LLDP and LLDP-MED on EX Series Switches",
"Configuring NetBIOS Snooping (CLI Procedure)"
] |
lldp-med (Ethernet Switching) | lldp-med {
fast-start fast-start;
interface name {
(disable | enable);
location {
civic-based {
ca-type name {
ca-value ca-value;
}
country-code country-code;
what what;
... | [edit protocols] | Configure Link Layer Discovery Protocol–Media Endpoint Discovery. LLDP-MED is an extension of
LLDP. The device uses LLDP-MED to support device discovery of VoIP telephones and to create
location databases for these telephone locations for emergency services. LLDP-MED is defined in the
standard ANSI/TIA-1057 by the Tele... | [
{
"name": "fast-start",
"desc": ""
},
{
"name": "number",
"desc": "Configure the number of LLDP-MED advertisements sent from the device in the first second after it has detected an LLDP-MED device (such as an IP telephone). Range: 1 through 10 advertisements Default: 3 advertisements The remai... | 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: Setting Up VoIP with 802.1X and LLDP-MED on an EX Series Switch",
"Configuring LLDP-MED (CLI Procedure)",
"Understanding LLDP and LLDP-MED on EX Series Switches"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.