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 |
|---|---|---|---|---|---|---|---|
log-attacks | log-attacks {
alert;
} | [edit security idp idp-policy policy-name rulebase-ips rule rule-name then notification] | Enable the log attacks to create a log record that appears in the log viewer.
In addition to the regular system log messages, IDP generates event logs for attacks. IDP generates
event logs when an event matches an IDP policy rule in which logging is enabled. When you configure a
rule for logging, the device creates a l... | [
{
"name": "alert",
"desc": "Set an alert flag in the Alert column of the Log Viewer for the matching log record."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
log-attacks | log-attacks {
alert;
} | [edit logical-systems name security idp idp-policy name rulebase-exempt rule name then
notification],
[edit logical-systems name tenants name security idp idp-policy name rulebase-exempt rule name
then notification],
[edit security idp idp-policy name rulebase-exempt rule name then notification],
[edit tenants name s... | Enable attack logging | [
{
"name": "alert",
"desc": "Set alert flag in attack log"
}
] | [none specified]
Release Information | [] | |
log-interval (IGMP Interface) | log-interval seconds; | [edit dynamic-profiles profile-name protocols igmp interface interface-name]
[edit logical-systems logical-system-name protocols igmp interface interface-name],
[edit protocols igmp interface interface-name] | Specify the minimum time interval (in seconds) between sending consecutive log messages to the
system log for multicast groups on static or dynamic IGMP interfaces. To configure the time interval, you
must specify the maximum number of multicast groups allowed on the interface. You must configure the
group-limit statem... | [
{
"name": "seconds",
"desc": "Minimum time interval (in seconds) between log messages. You must explicitly configure the"
}
] | 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. | [
"Limiting the Number of IGMP Multicast Group Joins on Logical Interfaces"
] |
log-interval (MLD Interface) | log-interval seconds; | [edit dynamic-profiles profile-name protocols mld interface interface-name]
[edit logical-systems logical-system-name protocols mld interface interface-name],
[edit protocols mld interface interface-name] | Specify the minimum time interval (in seconds) between sending consecutive log messages to the
system log for multicast groups on static or dynamic MLD interfaces. To configure the time interval, you
must specify the maximum number of multicast groups allowed on the interface.
To confirm the configured log interval on ... | [
{
"name": "seconds",
"desc": "Minimum time interval (in seconds) between log messages. You must explicitly configure the"
}
] | 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. | [
"Configuring the Number of MLD Multicast Group Joins on Logical Interfaces"
] |
log-interval (PIM Entries) | log-interval value; | [edit logical-systems logical-system-name protocols pim sglimit],
[edit logical-systems logical-system-name protocols pim sglimit family],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
sglimit],
[edit logical-systems logical-system-name routing-instances routing-instan... | Configure the amount of time between log messages. | [
{
"name": "seconds",
"desc": "Minimum time interval (in seconds) between log messages. To configure the time interval, you"
}
] | 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. | [] |
log-interval (Protocols MSDP) | log-interval seconds; | [edit logical-systems logical-system-name protocols msdp active-source-limit],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols msdp
active-source-limit],
[edit protocols msdp active-source-limit],
[edit routing-instances routing-instance-name protocols msdp active-source-lim... | Specify the minimum time interval (in seconds) between sending consecutive log messages to the
system log for MSDP active source messages. To configure the time interval, you must specify the
maximum number of MSDP active source messages received by the device.
To confirm the configured log interval, use the show msdp ... | [
{
"name": "seconds",
"desc": "Minimum time interval (in seconds) between log messages. You must explicitly configure the"
}
] | 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 MSDP with Active Source Limits and Mesh Groups"
] |
log-prefix (Interfaces) | log-prefix prefix-value; | [edit interfaces interface-name services-options syslog host hostname] | Set the system logging prefix value. | [
{
"name": "prefix-value",
"desc": "System logging prefix value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Junos OS Services Interfaces Library for Routing Devices",
"Configuring System Logging for Services Interfaces"
] |
log-prefix (L2TP) | log-prefix prefix-value; | [edit services l2tp tunnel-group group-name syslog host hostname] | Set the system logging prefix value. | [
{
"name": "prefix-value",
"desc": "System logging prefix value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring System Logging of L2TP Tunnel Activity"
] |
log-prefix (Services) | log-prefix prefix-value; | [edit services service-set service-set-name syslog host hostname] | Set the system logging prefix value. | [
{
"name": "prefix-value",
"desc": "System logging prefix value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring System Logging for Service Sets"
] |
log-prefix (System) | log-prefix string; | [edit system syslog host] | Include a text string in each message directed to a remote destination. | [
{
"name": "string",
"desc": "Text string to include in each message."
}
] | 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. | [
"Adding a Text String to System Log Messages Directed to a Remote Destination"
] |
log-rotate-frequency | log-rotate-frequency frequency; | [edit system syslog] | Configure the system log file rotation frequency by configuring the time interval for checking the log file
size.
When the log file size has exceeded the configured limit, the old log file is archived and a new log file is
created. | [
{
"name": "frequency",
"desc": "Frequency of rotation of the system log file. Range: 1 minute through 59 minutes Default: 15 minutes"
}
] | 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. | [
"Specifying Log File Size, Number, and Archiving Properties"
] |
log-updown (Protocols LDP) | log-updown {
trap disable;
} | [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] | Disable LDP traps on the router, logical system, or routing instance. | [
{
"name": "trap disable",
"desc": "Disable LDP traps."
}
] | 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. | [
"Disabling SNMP Traps for LDP"
] |
log-updown (Protocols MPLS) | log-updown {
no-trap {
mpls-lsp-traps;
rfc3812-traps;
}
(syslog | no-syslog);
trap;
trap-path-down;
trap-path-up;
} | [edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls] | Log a message or send an SNMP trap whenever an LSP makes a transition from up to down, or vice
versa, and whenever an LSP switches from one active path to another. Only the ingress router performs
these operations.
NOTE: System log messages for LSPs are generated by default. To disable the default
logging of messages f... | [
{
"name": "no-syslog",
"desc": "Do not log a message to the system log file."
},
{
"name": "no-trap",
"desc": "Do not send an SNMP trap."
},
{
"name": "syslog",
"desc": "Log a message to the system log file."
},
{
"name": "trap",
"desc": "Send an SNMP trap."
},
{
... | 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.
The mpls-lsp-traps and rfc-3812-traps options added in Junos OS Release 9.0. | [
"System Log Messages and SNMP Traps for MPLS",
"Junos OS Network Management Administration Guide for Routing Devices"
] |
log-updown | log-updown; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Specify to generate a log message whenever a BGP peer makes a state transition. Messages are logged
using the system logging mechanism located at the [edit system syslog] hierarchy level. | [] | 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: Preventing BGP Session Resets"
] |
log-warning (Multicast Forwarding Cache) | log-warning value; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast forwarding-cache threshold],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast forwarding-cache family (inet | inet6) threshold],
[edit logical-systems ... | Specify the threshold at which the device logs a warning message in the system log for multicast
forwarding cache entries. This threshold is a percentage of the maximum number of multicast
forwarding cache entries received by the device. Configuring the threshold statement globally for the
multicast forwarding cache or... | [
{
"name": "value",
"desc": "Percentage of the number of multicast forwarding cache entries that can be added to the cache"
}
] | 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 the Multicast Forwarding Cache"
] |
log-warning (Protocols MSDP) | log-warning value; | [edit logical-systems logical-system-name protocols msdp active-source-limit],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols msdp
active-source-limit],
[edit protocols msdp active-source-limit],
[edit routing-instances routing-instance-name protocols msdp active-source-lim... | Specify the threshold at which the device logs a warning message in the system log for received MSDP
active source messages. This threshold is a percentage of the maximum number of MSDP active source
messages received by the device.
To confirm the configured warning threshold, use the show msdp source-active command. | [
{
"name": "value",
"desc": "Percentage of the number of active source messages that starts triggering the warnings. You"
}
] | 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 MSDP with Active Source Limits and Mesh Groups"
] |
logging (IDS MS-DPC) | logging {
syslog;
threshold rate;
} | [edit services ids rule rule-name term term-name then] | Set logging values for this IDS term when using the MS-DPC. | [] | 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 Actions in IDS Rules"
] |
logging (Services) | logging {
traceoptions {
file filename <files number> <match regular-expression> <size size> <world-readable | no-
world-readable>;
flag flag;
no-remote-trace;
}
} | [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 in Junos OS Release 8.0. | [
"Tracing Services PIC Operations"
] |
logging-rule (PCC Action Profile) | logging-rule lrf-rule-name; | [edit unified-edge pcef pcc-action-profiles profile-name],
[edit services pcef pcc-action-profiles profile-name] | Assign the LRF rule to the PCC action profile of a static PCC rule. When the matching conditions in the
PCC rule are met, the LRF rule is activated.
If you are using Junos OS Subscriber Aware, specify the name of the LRF rule at the [edit unified-edge
pcef pcc-action-profiles profile-name] hierarchy level.
If you are u... | [
{
"name": "lrf-rule-name",
"desc": "LRF rule name. The referenced LRF rule must be configured in an LRF profile."
}
] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef pcc-action-profiles profile-name] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series.
Support for Next Gen Services for Junos OS Broadband Subscriber Management introduced in Juno... | [
"Configuring the Activation of an LRF Rule by a PCC Rule",
"Configuring Logging and Reporting for Junos OS Subscriber Aware",
"Configuring Logging and Reporting for Subscriber Management",
"Configuring an LRF Profile for Subscribers"
] |
logical-bandwidth-policer | logical-bandwidth-policer; | [edit dynamic-profiles profile-name firewall policer policer-name],
[edit firewall policer policer-name],
[edit logical-systems logical-system-name firewall policer policer-name] | For a policer with a bandwidth limit configured as a percentage (using the bandwidth-percent statement),
specify that the percentage be based on the shaping rate defined on the logical interface, rather than on
the media rate of the physical interface. | [] | 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.
Logical systems support introduced in Junos OS Release 9.3.
Support at the [edit dynamic-profiles ... policer policer-name] hierarchy level introduced in Junos OS
Release 11.4. | [
"Bandwidth Policers",
"Configuring Policers Based on Logical Interface Bandwidth",
"interface-specific"
] |
logical-domain-identity-management | logical-domain-identity-management {
active {
authentication-entry-timeout minutes;
filter {
domain name;
exclude-ip {
address-book book-name;
address-set address-set;
}
include-ip {
address-book book-nam... | [edit services] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "active",
"desc": "Displays the active mode for logical domain identity management module."
},
{
"name": "traceoptions",
"desc": "Displays the tracing options."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R1. | [
"User Authentication for Logical Systems",
"Understanding Integrated User Firewall Support in a Tenant System"
] |
logical-interface (DDoS Flow Detection) | logical-interface (flow-bandwidth | flow-control-mode | flow-detection-mode) | [edit system ddos-protection protocols protocol-group packet-type flow-level-bandwidth],
[edit system ddos-protection protocols protocol-group packet-type flow-level-control],
[edit system ddos-protection protocols protocol-group packet-type flow-level-detection] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches)
Configure flow bandwidth, flow control mode, or flow detection mode for flow detection at the logical
interface flow aggregation level for the packet type. | [
{
"name": "flow-bandwidth",
"desc": "Bandwidth for the flow at the logical interface level. Available only at the [edit system ddos-protection protocols protocol-group packet-type flow-level-bandwidth] hierarchy level."
},
{
"name": "flow-control-mode",
"desc": "Mode for how traffic in the detec... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support for Enhanced Subscriber Management added in Junos OS Release 17.3R1. | [
"Configuring the Maximum Flow Bandwidth at Each Flow Aggregation Level",
"Configuring How Traffic in a Culprit Flow Is Controlled at Each Flow Aggregation Level",
"Configuring How Flow Detection Operates at Each Flow Aggregation Level",
"Setting Up and Using Flow Detection"
] |
logical-interface-aggregate-statistics | logical-interface-aggregate-statistics; | [edit class-of-service interfaces interface-name] | Enable the collection of aggregate queue statistics for all underlying logical interfaces on a particular
physical or aggregate (for example, ae0) interface. By default to preserve memory resources, aggregate
queue statistics are not collected for underlying logical interfaces (Level 2 interfaces); queue statistics
are... | [] | interface | Statement introduced in Junos OS Release 18.2R1. | [
"Hierarchical Class of Service Overview"
] |
logical-interface-chassis-redundancy (MX Series Virtual Chassis) | logical-interface-chassis-redundancy; | [edit interfaces aenumber aggregated-ether-options] | For member routers in an MX Series Virtual Chassis, provide chassis redundancy for IP demultiplexing
(demux) and VLAN demux subscriber interfaces in aggregated Ethernet bundles configured with
targeted distribution. With chassis redundancy, the router assigns the backup link in the aggregated
Ethernet bundle to an MPC/... | [] | 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. | [
"Configuring Chassis Redundancy for a Virtual Chassis",
"logical-interface-fpc-redundancy (Aggregated Ethernet Subscriber"
] |
Interfaces) | logical-interface-fpc-redundancy; | [edit interfaces aenumber aggregated-ether-options] | Provide module redundancy for demux subscribers on aggregated Ethernet bundles configured with
targeted distribution. Backup links for a subscriber are chosen on a different EQ DPC or MPC from the
primary link, based on the link with the fewest number of subscribers among the links on different
modules. If all links ar... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Link and Module Redundancy for Demux Subscribers in an Aggregated Ethernet",
"Interface",
"Configuring Module Redundancy for a Virtual Chassis"
] |
logical-interface-fpc-redundancy (PS Interface) | logical-interface-fpc-redundancy; | [edit interfaces ps number targeted-options] | Provide module redundancy for demux subscribers on redundant logical tunnel (RLT) bundles configured
with targeted distribution. Backup links for a subscriber are chosen on a different Packet Forwarding
Engine from the primary link, based on the link with the fewest number of subscribers among the links
on different mo... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.4R1. | [
"MPLS Pseudowire Subscriber Logical Interfaces"
] |
logical-interface-policer | logical-interface-policer; | [edit dynamic-profiles profile-name firewall policer policer-name],
[edit dynamic-profiles profile-name firewall three-color-policer name],
[edit firewall atm-policeratm-policer-name],
[edit firewall policer policer-name],
[edit firewall policer policer-template-name],
[edit firewall three-color-policer policer-name],
... | Configure a logical interface policer. For PTX series routers running Junos OS Release 18.3R1 or later,
you can use this command to configure separate firewall filters for different family address types (IPv4
and IPv6) that share the same interface, and configure the same policer as an action for the filter.
To configu... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support at the [edit firewall three-color-policer policer-name] hierarchy level introduced in Junos OS
Release 8.2.
Logical systems support introduced in Junos OS Release 9.3.
Support at the [edit dynamic-profiles ... policer policer-name] and [edit dynamic-profiles ...... | [
"Two-Color and Three-Color Logical Interface Policers",
"Traffic Policer Types",
"Configuring and Applying Tricolor Marking Policers",
"Configuring Gigabit Ethernet Two-Color and Tricolor Policers",
"action"
] |
logical-interface-unit-range | logical-interface-unit-range (high | low) | [edit system services extensible-subscriber-services] | Configure the range from which the unit number is selected for the logical interface service that is
created by Extensible Subscriber Services Manager by using an op script. Extensible Subscriber Services
Manager assigns the first available unit number in the specified range. | [
{
"name": "high",
"desc": "Upper limit of the logical interface unit range. Range: 1 through 16,385 Default: 16,385"
},
{
"name": "low",
"desc": "Lower limit of the logical interface unit range. Range: 1 through 16,385 Default: 1"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [] |
logical-system (Diameter Peer) | logical-system logical-system-name <routing-instance routing-instance-name > ; | [edit diameter peer peer-name] | Specify a logical system and optionally a routing instance for a Diameter peer. Alternatively, you can
include the routing-instance statement at the [edit diameter peer peer-name] hierarchy level to configure only
a routing instance. | [
{
"name": "logical-system-name",
"desc": "Name of the logical system."
},
{
"name": "routing-instance routing-instance-name",
"desc": "(Optional) Name of the routing instance."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configuring Diameter",
"Configuring Diameter Peers"
] |
logical-system (Diameter Transport) | logical-system logical-system-name <routing-instance routing-instance-name >; | [edit diameter transport transport-name] | Specify a logical system and optionally a routing instance for the transport layer connection.
NOTE: The logical system and routing instance must match that for the peer or a
configuration error is reported. | [
{
"name": "logical-system-name",
"desc": "Name of the logical system."
},
{
"name": "routing-instance routing-instance-name",
"desc": "(Optional) Name of the routing instance."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Diameter",
"Configuring the Diameter Transport"
] |
logical-system (SNMP) | logical-system logical-system-name {
routing-instance routing-instance-name {
source-address address;
}
} | [edit snmp community community-name],
[edit snmp trap-group],
[edit snmp trap-options]
[edit snmp v3target-address target-address-name] | Specify a logical system name for SNMP v1 and v2c clients.
Include at the [edit snmp trap-options] hierarchy level to specify a logical-system address as the source
address of an SNMP trap.
Include at the [edit snmp v3 target-address] hierarchy level to specify a logical-system name as the
destination address for an SN... | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3
NOTE: The logical-system statement replaces the logical-router statement, and is
backward-compatible with Junos OS Release 8.3 and later. | [
"Specifying a Routing Instance in an SNMPv1 or SNMPv2c Community",
"Configuring the Trap Target Address"
] |
logical-system (System Security Profile) | logical-system logical-system; | [edit system security-profile] | Specify the user logical system to bind the security profile.
The primary administrator uses security profiles to provision logical systems with resources. You can
bind security profiles to user logical systems and the primary logical system. The primary administrator
can configure more than one security profile alloca... | [] | 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. | [
"Understanding Logical Systems for SRX Series Services Gateways"
] |
logical-system (Tunnel Profile) | logical-system logical-system-name; | [edit access tunnel-profile profile-name tunnel tunnel-id] | Specify a logical system for a tunnel. When you specify a logical system, you must also specify a routing
instance. | [
{
"name": "logical-system-name",
"desc": "Name of the logical system."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"L2TP LAC Tunneling for Subscribers"
] |
logical-system | logical-system logical-system-name {
[ routing-instances instance-name ];
} | [edit services rpm bgp] | Specify the logical system used by the probes. | [
{
"name": "logical-system-name",
"desc": "Logical system name."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring BGP Neighbor Discovery Through RPM"
] |
logical-system-mux | logical-system-mux {
traceoptions {
file {
<file name>;
files;
no-world-readable;
size;
world-readable;
}
flag {
all;
debug;
general;
normal;
parse;
... | [edit routing-options] | 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": "<filename>",
"desc": "Specify the filename, in which trace information should be written."
},
{
"name": "files",
"desc": "Specify the maximum number of trace files. Range being from 2 to 1000."
},
{
"name": "no-world-readable",
"desc": "Do not allow any user to read the lo... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | [] | |
logical-system-name (DHCP Local Server) | logical-system-name; | [edit system services dhcp-local-server authentication username-include],
[edit system services dhcp-local-server dhcpv6 authentication username-include],
[edit system services dhcp-local-server dhcpv6 group group-name authentication username-include],
[edit system services dhcp-local-server group group-name authentica... | Specify that the logical system name be concatenated with the username during the subscriber
authentication or DHCP client process. No logical system name is concatenated if the configuration is in
the default logical system. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Specifying Authentication Support"
] |
logical-system-name (DHCP Relay Agent) | logical-system-name; | [edit forwarding-options dhcp-relay authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 group group-name authentication username-include],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name auth... | Specify that the logical system name is concatenated with the username during the subscriber
authentication or client authentication process. No logical system name is concatenated if the
configuration is in the default logical system. Use the statement at the [edit ... dhcpv6] hierarchy levels
to configure DHCPv6 supp... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4.
Support at the [edit ... dual-stack-group dual-stack-group-name] hierarchy level introduced in Junos OS
Release 15.1. | [
"Specifying Authentication Support",
"Creating Unique Usernames for DHCP Clients"
] |
logical-system-name (Static Subscribers) | logical-system-name; | [edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers authentication username-include],
[edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers group group-name authentication username-inclu... | Specify that the name of the logical system is included as part of the username created for all static
subscribers or for the static subscribers in a specified group. The group version of the statement takes
precedence over the global version. The username is also sent to RADIUS in the Access-Request
message. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Subscribers over Static Interfaces Configuration Overview",
"Configuring the Static Subscriber Global Username",
"Configuring the Static Subscriber Group Username"
] |
logical-system-trap-filter | logical-system-trap-filter; | [edit snmp] | Restrict the routing instances from receiving traps that are not related to the logical system networks to
which they belong. | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [
"SNMP Traps Supported for Routing Instances"
] |
logical-systems (All) | logical-systems {
logical-system-name {
...logical-system-configuration...
}
} | [edit] | Configure a logical system. Only the primary administrator can configure a logical system at [edit]
hierarchy level.
You can include several of the hierarchies that can be included at the [edit] hierarchy level. For
descriptions of the applicable statements, see the appropriate hierarchies.
NOTE: The logical-systems co... | [
{
"name": "logical-system-name",
"desc": "Name of the logical system."
}
] | all—To view this statement in the configuration.
all—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Understanding Logical Systems for SRX Series Services Gateways"
] |
logical-systems | logical-systems {
logical-system-name {
...logical-system-configuration...
}
} | [edit] | Configure a logical system. | [
{
"name": "logical-system-name",
"desc": "Name of the logical system."
}
] | 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 name changed from logical-routers in Junos OS Release 9.3. | [
"Logical Systems User Guide for Routers and Switches"
] |
logical-tunnel-options | logical-tunnel-options {
link-protection {
non-revertive;
revertive;
}
load-balance{
adaptive{
pps;
scan-interval scan-interval;
tolerance percent;
}
no-adaptive;
per-packet;
local-biaspercent;
}
per-unit-mac... | [edit dynamic-profiles name interfaces],
[edit dynamic-profiles name logical-systems name interfaces],
[edit interfaces] | For redundant logical tunnels, specifies the logical tunnel interface-specific options for load balancing
and link protection. The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "link-protection",
"desc": "Enables link protection for redundant logical tunnel interfaces. In addition to enabling static link protection, you must configure a primary and secondary (backup) link for egress traffic. Values:"
},
{
"name": "non-revertive",
"desc": "Do not revert back ... | interface | Statement introduced in Junos OS Release 19.2R1. | [] |
login (Access) | login string; | [edit access firewall-authentication pass-through (ftp | http | telnet) banner] | Specify the login banner for users using FTP, HTTP, and Telnet during the authentication process. | [
{
"name": "string",
"desc": "Banner text. Maximum length of the message text is 250 characters. Enclose the banner text"
},
{
"name": "within spaces or special characters",
"desc": "for example quotation marks (” “)."
}
] | 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. | [
"[edit access firewall-authentication]",
"SRX Firewall Users",
"Obtaining Username and Role Information Through Firewall Authentication"
] |
login | login {
announcement text;
class class-name {
allow-hidden-commands;
no-hidden-commands {
except [“regular expression or command 1” “regular expression or command
2” ...];
}
access-end hh:mm;
access-start hh:mm;
( allow-commands ”(reg... | [edit system] | Configure user access to the device. | [
{
"name": "announcement",
"desc": ""
},
{
"name": "text",
"desc": "Configure a system login announcement. This announcement appears after a user logs in. Sometimes you want to make announcements to authorized users only after they have logged in. For example, you might want to announce an upcomi... | 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.
deny-sources option introduced in Junos OS Release 11.2.
All of the statements and options introduced previously were introduced in Junos OS Release 14.1X53-
D20 for the OCX Series. | [
"Defining Junos OS Login Classes",
"Configuring Junos OS to Display a System Login Announcement"
] |
logo (Access) | logo file path; | [edit access firewall-authentication web-authentication] | Set custom logo using captive portal authentication. | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [
"[edit access firewall-authentication]",
"Configure a Custom Logo and Banner Messages",
"SRX Firewall Users"
] |
logout (Access) | logout string; | [edit access firewall-authentication web-authentication banner] | Specify the logout banner for users using the logout button displayed in the captive portal. | [
{
"name": "string",
"desc": "Banner text. Maximum length of the message text is 250 characters. Enclose the banner text"
},
{
"name": "within spaces or special characters",
"desc": "for example quotation marks (” “)."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [
"[edit access firewall-authentication]",
"SRX Firewall Users"
] |
logout-response-timeout (PCRF Partition) | logout-response-timeout seconds; | [edit access pcrf partition partition-name] | Configure the amount of time in seconds before a Policy and Charging Rule Function (PCRF) partition
stops attempting to send a subscriber logout.
If you set draining and the draining-response-timeout statements for the PCRF partition, any new subscriber
logins are denied, and the time limit you set in the draining-resp... | [
{
"name": "seconds",
"desc": "Number of seconds to wait before a PCRF partition stops attempting to send a subscriber logout. Default: 7200 Range: 0 through 86,400 seconds (24 hours)"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the PCRF Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gx Interactions Between the Router and the PCRF",
"Understanding Interactions Between the PCRF, PCEF, and OCS",
"Understanding Upstream and Downstream Messages for the PCR... |
long-lived (Graceful Restart for BGP Helper) | long-lived {
receiver {
enable:
disable;
}
advertise-to-non-llgr-neighbor {
omit-no-export;
}
} | [edit logical-systems logical-system-name protocols bgp graceful-restart],
[edit logical-systems logical-system-name protocols bgp group group-name graceful-restart],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address
graceful-restart],
[edit logical-systems logical-system-name r... | Configure the long-lived graceful restart mechanism to preserve BGP routing details for a longer period
from a failed BGP peer than the duration for which such routing information is maintained using the
BGP graceful restart functionality. Long-lived graceful restart receiver or helper mode is enabled by
default, unles... | [] | 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. | [
"Configuring Graceful Restart Options for BGP",
"Junos OS High Availability User Guide"
] |
long-lived (Graceful Restart for BGP Restarter) | long-lived {
restarter {
disable;
stale-time interval;
}
} | [edit logical-systems logical-system-name protocols bgp family inet (labeled-unicast | unicast |
multicast) graceful-restart],
[edit logical-systems logical-system-name protocols bgp group group-name family inet (labeled-
unicast | unicast | multicast) graceful-restart],
[edit logical-systems logical-system-name proto... | Configure the long-lived graceful restart mechanism on the restarter router to preserve BGP routing
details for a longer period from a failed BGP peer than the duration for which such routing information
is maintained using the BGP graceful restart functionality. Long-lived graceful restart restarter mode is
enabled by... | [] | 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. | [
"Configuring Graceful Restart Options for BGP",
"Junos OS High Availability User Guide"
] |
longest-match (Static Routes) | longest-match; | [edit logical-systems logical-system-name routing-options static route destination-prefix next-hop
address resolve]
[edit routing-instances routing-instance-name routing-options static route destination-prefix next-
hop address resolve],
[edit routing-options static route destination-prefix next-hop address resolve] | Specify the static route on the device to resolve and determine the packet’s next-hop interface using the
Longest Match Routing Rule (most specific entry), sometimes referred to as the longest prefix match or
maximum prefix length match. The Longest Match Routing Rule is an algorithm used by IP routers to
select an ent... | [] | 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. | [
"Understanding Static Route Preferences and Qualified Next Hops"
] |
longest-match | longest-match {
policy value |(expression) | [values ];
} | [edit protocols ldp] | Enable longest match to allow LDP to learn the routes aggregated or summarized across OSPF areas or
IS-IS levels in inter-domain. | [
{
"name": "policy value |(expression) | [values ]",
"desc": "Specify policy to provide per prefix granularity."
}
] | 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. | [
"Longest Match Support for LDP Overview",
"Example: Configuring Longest Match for LDP",
"Configuring Longest Match for LDP"
] |
lookup-intact-on-commit | lookup-intact-on-commit; | [edit security policies] | Activate to prevent interruptions in the session flow due to modifications in the security policy. Once
you commit the configuration, restart the forwarding plane to activate the functionality.
Use the following command to check the status and eligibility of the device before enabling the lookup-
intact-on-commit optio... | [] | security—To view this statement in the configuration
security-control—To add this statement to the configuration | Statement introduced in Junos OS Release 24.4R1 | [] |
loop-detect | loop-detect {
enhanced {
interface (name | all) {
loop-detect-action (interface-down | laser-off);
revert-interval seconds;
transmit-interval (10m | 1m | 10s | 1s);
vlan-id (all | vlan-id);
}
}
} | [edit logical-systems name protocols],
[edit protocols] | Configure lightweight provider edge (PE) to customer edge (CE) loop detection on server-facing logical
interfaces in a Layer 2 (L2) network. We also call this feature lightweight leaf to server loop detect,
lightweight PE-CE loop detect, or enhanced loop detect.
This feature can detect the following types of Ethernet l... | [
{
"name": "interface",
"desc": ""
},
{
"name": "(name | all)",
"desc": "Specify the name of a server-facing L2 logical interface on which you want to enable lightweight loop detect, or use the all keyword to enable this feature on all such logical interfaces."
},
{
"name": "loop-detect-a... | routing | Statement introduced in Junos OS Release 20.4R1.
Statement support added to ACX-Series (ACX7100-32C, ACX7100-48L) devices in Junos OS Evolved
Release 22.4R1.
vlan-id all option introduced in Junos OS Release 24.4R1. | [
"EVPN-VXLAN Lightweight Leaf to Server Loop Detection"
] |
loopback (Aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet) | (loopback | no-loopback); | [edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name ether-options],
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options],
[edit interfaces interface-range name ether-options]
For QFX Series and EX Series:
[edit interfaces interf... | For aggregated Ethernet, Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet interfaces, enable or
disable loopback mode.
NOTE:
•
By default, local aggregated Ethernet, Fast Ethernet, Tri-Rate Ethernet copper, Gigabit
Ethernet, and 10-Gigabit Ethernet interfaces connect to a remote system.
•
IPv6 Neighbor Discove... | [] | 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.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Metro Routers.
Statement modified in Junos OS Release 9.2 for the SRX Series. | [
"Configuring Ethernet Loopback Capability",
"Understanding Interfaces"
] |
loopback (Fibre Channel Interface) | (loopback | no-loopback); | [edit interfaces interface-name fibrechannel-options] | Enable or disable loopback mode for FC interfaces.
Default
By default, loopback mode is disabled on FC interfaces. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Converting an Ethernet Interface To a Fibre Channel Interface"
] |
loopback (Local and Remote) | loopback (local | remote); | [edit interfaces interface-name gigether-options] | Enables local loopback and enables remote loopback. This allows you to test the transceiver cable
connection from the far end to the retimer interface without changing the cable. | [
{
"name": "local",
"desc": "Enables local loopback"
},
{
"name": "remote",
"desc": "Enables remote loopback"
}
] | 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. | [
"Configuring Ethernet Loopback Capability"
] |
loopback (Serial) | loopback mode; | [edit interfaces interface-name serial-options] | Configure a loopback connection.
Default
If you do not include this statement, there is no loopback connection. | [
{
"name": "mode",
"desc": "You can specify the one of the following loopback modes:"
},
{
"name": "dce-local",
"desc": "For EIA-530 interfaces only, loop packets back on the local DCE."
},
{
"name": "dce-remote",
"desc": "For EIA-530 interfaces only, loop packets back on the remote D... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Serial Loopback Capability"
] |
loopback-clear-timer | loopback-clear-timer seconds; | [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 loop detection clear timer for the Link Control Protocol (LCP) component of
a PPP session. | [
{
"name": "seconds",
"desc": "The time in seconds to wait before the loop detection flag is cleared if it is not cleared by the"
}
] | 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 PPP"
] |
loopback-firewall-optimization | loopback-firewall-optimization; | [edit chassis] | Enable this setting to increase the system limit for the number of loopback filter terms that can be
configured. When enabled, you can configure up to 768 loopback filter terms for IPv6, and up to 1152
terms for IPv4. The packet forwarding engine (PFE) will restart upon commit for the new system limits to
take effect.
... | [] | interface | Statement introduced in Junos OS Release 20.3R1. | [
"Planning the Number of Firewall Filters to Create"
] |
loopback-firewall-per-vrf | loopback-firewall-per-vrf | [edit chassis loopback-firewall-per-vrf] | After setting this configuration, the system allows you to apply firewall filters to loopback address logical
interfaces on a per VRF basis.
In the following example, two logical interfaces on the loopback address are configured. Two logical
interfaces on an ethernet interface are configured. Two VRFs are configured, a... | [] | interface | Statement introduced in Junos OS Release 25.4R1 | [] |
loopback-firewallv6-optimization | loopback-firewallv6-optimization | [edit chassis] | Move IPv6 loopback filters to a separate single wide group and IPv6 address match to VFP. Can be used
to increase IPv6 loopback filter scale when scale of IPv4 loopback filters are used in EVPN VXLAN
deployments.
With EVPN/VXLAN, we can scale either 512 terms for IPv4 loopback filter or 512 terms for IPv6
loopback filt... | [] | interface | Statement introduced in Junos 23.2 | [] |
loopback-port | loopback-port loopback-port; | [edit forwarding-options vxlan-routing ] | Define the global loopback aggregated Ethernet interface for VXLAN routing on QFX5210 leaf devices
in EVPN-VXLAN edge-routed bridging (ERB) overlay fabrics.
Specify loopback-port using its physical interface name, without a specific unit number (such as ae0
rather than ae0.100, for example).
NOTE: The Packet Forwarding... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.3R1 for QFX5210 switches. | [
"Using a RIOT Loopback Port to Route Traffic in an EVPN Network"
] |
loopback-remote | loopback-remote; | [edit dynamic-profiles name interfaces name gigether-options],
[edit dynamic-profiles name logical-systems name interfaces name gigether-options],
[edit interfaces name gigether-options] | Configure loopback-remote on the remote end of the link. When you configure on an interface loopback-
remote, the local end goes down and remote end goes up.
NOTE: The loopback-remote option is supported on MX routers, starting from the MPC7E,
MPC8E, and MPC9E linecards. | [] | interface | [
"Verifying Link and Transceivers using Pseudo Random Binary Sequence (PRBS) Test"
] | |
loopback-tracking | loopback-tracking; | [edit protocols oam ethernet link-fault-management] | Enables loopback tracking on Ethernet interfaces. When loopback tracking is enabled and the Ethernet
Operation, Administration, and Management (OAM) link-fault management process (lfmd) detects its
own generated packets on an interface, it marks the interface as down. When the loopback issue
resolves, the interface is ... | [] | 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. | [
"IEEE 802.3ah OAM Link-Fault Management Overview",
"Enabling IEEE 802.3ah OAM Support"
] |
loops (Autonomous System) | loops number; | [edit logical-systems logical-system-name protocols bgp local-as],
[edit logical-systems logical-system-name protocols bgp group group-name local-as],
[edit logical-systems logical-system-nameprotocols bgp group group-name neighbor address local-
as],
[edit logical-systems logical-system-name routing-options autonomo... | Globally, for the local-AS BGP attribute, allow the local device’s AS number to be in the received AS
paths, and specify the number of times detection of the local device’s AS number in the AS_PATH
attribute causes the route to hidden. For example, if you configure loops 1, the route is hidden if the local
device’s AS ... | [
{
"name": "number",
"desc": "Number of times detection of the AS number in the AS_PATH attribute causes the route to be"
}
] | 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. | [
"Example: Enabling BGP Route Advertisements"
] |
loops (BGP Address Family) | loops number; | [edit logical-systems logical-system-name protocols bgp family address-family],
[edit logical-systems logical-system-name protocols bgp group group-name family address-
family],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address family
address-family],
[edit protocols bgp fam... | For the specified BGP address family, allow the local device’s AS number in the received AS paths and
specify the number of times the detection of the local device’s AS in the AS_PATH attribute is allowed.
If the count exceeds the specified loop count, the system discards this route. For example, if you
configure loops... | [
{
"name": "number",
"desc": "Maximum number of times that the local device’s AS number is allowed in the AS_PATH"
}
] | 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. | [
"Example: Enabling BGP Route Advertisements"
] |
loose-authentication-check | loose-authentication-check; | [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] | Allow the use of MD5 authentication without requiring network-wide deployment. | [] | 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 Hitless Authentication Key Rollover for IS-IS",
"Example: Configuring Hitless Authentication Key Rollover for IS-IS"
] |
loose-check | loose-check; | [edit protocols pim interface interface-name bfd-liveness-detection authentication],
[edit routing-instances routing-instance-name protocols pim interface interface-name bfd-
liveness-detection authentication] | Specify loose authentication checking on the BFD session. Use loose authentication for transitional
periods only when authentication might not be configured at both ends of the BFD session.
By default, strict authentication is enabled and authentication is checked at both ends of each BFD
session. Optionally, to smooth... | [] | 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. | [
"Configuring BFD Authentication for PIM",
"Understanding Bidirectional Forwarding Detection Authentication for PIM"
] |
loose-source-route-option (IDS Screen Next Gen Services) | loose-source-route-option; | [edit services screen ids-option screen-name ip] | Identify and drop IPv4 packets that have the IP option of 3 (Loose Source Routing). | [] | 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"
] |
loss (querier) | loss {
traffic-class tc-value {
average-sample-size sample size;
loss-threshold loss threshold value;
loss-threshold-window number of samples for loss threshold;
measurement-quantity bytes|packets;
query-interval milliseconds;
}
} | [edit protocols mpls oam performance-monitoring querier],
[edit protocols mpls label-switched-path lsp-name oam performance-monitoring querier],
[edit protocols mpls label-switched-path lsp-name primary path-name oam performance-monitoring
querier],
[edit protocols mpls label-switched-path lsp-name secondary path-nam... | Configure loss measurement options.
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 15.1. | [
"Configuring Pro-Active Loss and Delay Measurements",
"On-Demand Packet Loss and Delay Measurement for UHP LSPs Overview"
] |
loss (responder) | loss {
min-query-interval milliseconds;
} | [edit protocols mpls oam performance-monitoring responder],
[edit protocols mpls label-switched-path lsp-name oam performance-monitoring responder],
[edit protocols mpls label-switched-path lsp-name primary path-name oam performance-monitoring
responder],
[edit protocols mpls label-switched-path lsp-name secondary pat... | Configure loss measurement options. | [
{
"name": "min-query-interval",
"desc": ""
},
{
"name": "milliseconds",
"desc": "(Optional) Specify the minimum query interval that the responder supports. If the minimum query interval of the responder is greater than the query interval configured at the querier, the effective message query rat... | 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. | [
"Configuring Pro-Active Loss and Delay Measurements",
"On-Demand Packet Loss and Delay Measurement for UHP LSPs Overview"
] |
loss-delay (querier) | loss-delay {
traffic-class tc-value {
average-sample-size sample size;
loss-threshold loss threshold value;
loss-threshold-window number of samples for loss threshold;
measurement-quantity bytes|packets;
padding-size size;
query-interval milliseconds;
rtt-dela... | [edit protocols mpls oam performance-monitoring querier],
[edit protocols mpls label-switched-path lsp-name oam performance-monitoring querier],
[edit protocols mpls label-switched-path lsp-name primary path-name oam performance-monitoring
querier],
[edit protocols mpls label-switched-path lsp-name secondary path-name... | Configure combined loss-delay measurement options.
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 15.1. | [
"Configuring Pro-Active Loss and Delay Measurements",
"On-Demand Packet Loss and Delay Measurement for UHP LSPs Overview"
] |
loss-priority (Classifiers) | loss-priority level {
code-points [aliases] [bit-patterns];
} | [edit class-of-service classifiers type classifier-name forwarding-class class-name] | Specify packet loss priority value for a specific set of code-point aliases and bit patterns. | [
{
"name": "level can be one of the following:",
"desc": ""
},
{
"name": "high",
"desc": "Packet has high loss priority."
},
{
"name": "medium-high",
"desc": "Packet has medium-high loss priority."
},
{
"name": "medium-low",
"desc": "Packet has medium-low loss priority."
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Understanding How Behavior Aggregate Classifiers Prioritize Trusted Traffic",
"Configuring and Applying Tricolor Marking Policers",
"Example: Configuring CoS on EX Series Switches",
"Defining CoS Classifiers (CLI Procedure)",
"Defining CoS Classifiers (J-Web Procedure)",
"Understanding CoS Classifiers",
... |
loss-priority (Drop Profiles) | loss-priority level protocol protocol drop-profile profile-name; | [edit class-of-service schedulers scheduler-name drop-profile-map] | Configure packet loss priority value for a weighted random early detection (WRED) drop profile mapped
to a system drop profile. | [
{
"name": "level",
"desc": "Can be one of the following:"
},
{
"name": "low",
"desc": "Packet has low loss priority."
},
{
"name": "medium-high",
"desc": "Packet has medium-high loss priority."
},
{
"name": "high",
"desc": "Packet has high loss priority."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [] |
loss-priority (Dynamic Schedulers) | loss-priority (any | low | medium-low | medium-high | high); | [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name drop-profile-map] | Specify a loss priority to which to apply a drop profile in a dynamic profile. The drop profile map sets the
drop profile for a specific PLP and protocol type. The inputs for the map are the PLP designation and the
protocol type. The output is the drop profile. | [
{
"name": "any",
"desc": "The drop profile applies to packets with any PLP."
},
{
"name": "high",
"desc": "The drop profile applies to packets with high PLP."
},
{
"name": "medium-high",
"desc": "The drop profile applies to packets with medium-high PLP."
},
{
"name": "medium-... | 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. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Schedulers in a Dynamic Profile for Subscriber Access"
] |
loss-priority (Firewall Filter Action) | loss-priority (high | low); | [edit firewall family family-name filter filter-name term term-name then],
[edit logical-systems logical-system-name firewall family family-name filter filter-name term term-
name then] | Set the loss priority of incoming packets. | [] | 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. | [
"Firewall Filter Nonterminating Actions",
"Policer Color-Marking and Actions",
"Multifield Classification Overview"
] |
loss-priority (Firewall Filter) | loss-priority (high | low | medium-high | medium-low); | [edit dynamic-profiles name firewall family inet filter name term name from],
[edit dynamic-profiles name firewall filter name term name from],
[edit firewall family inet filter name term name from],
[edit firewall filter name term name from],
[edit logical-systems name firewall family inet filter name term name from],... | Set the loss priority of incoming packets, which governs the likelihood of the system dropping packets in
the event of congestion. For example, to ensure delivery of critical traffic, you might want to set the loss
priority of non-critical flows to high or medium-high to intentionally sacrifice those packets in favor o... | [
{
"name": "high",
"desc": "Highest probability of being dropped at times of congestion"
},
{
"name": "medium-high",
"desc": "Second highest probability of being dropped at times of congestion"
},
{
"name": "medium-low",
"desc": "Third highest probability of being dropped at times of ... | firewall | Statement introduced before Junos OS Release 7.4.
For EX9200 series switches, support for medium-high and medium-low loss priorities was added in Junos OS
and Junos OS Evolved releases 19.x and 20.x for the ethernet-switching firewall family. | [
"Configuring Multifield Classifiers"
] |
loss-priority (Frame Relay Loss Priority) | loss-priority level code-points [values ]; | [edit class-of-service loss-priority-maps frame-relay-de map-name] | Map CoS values to a packet loss priority (PLP). In Junos OS, classifiers associate incoming packets with a
forwarding class (FC) and PLP. PLPs allow you to set the priority for dropping packets. Typically, you
mark packets exceeding some service level with a high loss priority—that is, a greater likelihood of being
dro... | [
{
"name": "level can be one of the following:",
"desc": ""
},
{
"name": "high",
"desc": "Packet has high loss priority."
},
{
"name": "medium-high",
"desc": "Packet has medium-high loss priority."
},
{
"name": "medium-low",
"desc": "Packet has medium-low loss priority."
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Understanding Interfaces",
"Understanding Packet Loss Priorities"
] |
loss-priority (Rewrite Rules) | loss-priority level {
code-point (alias | bit-pattern);
} | [edit class-of-service rewrite-rules type rewrite-name forwarding-class class-name] | Specify a loss priority to which to apply a rewrite rule. The rewrite rule sets the code-point aliases and
bit patterns for a specific forwarding class and loss priority. Packets that match the forwarding class and
loss priority are rewritten with the rewrite code-point alias or bit pattern. | [
{
"name": "level can be one of the following:",
"desc": ""
},
{
"name": "high",
"desc": "The rewrite rule applies to packets with high loss priority."
},
{
"name": "low",
"desc": "The rewrite rule applies to packets with low loss priority."
},
{
"name": "medium-high",
"de... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Rewrite Rules",
"Understanding How Behavior Aggregate Classifiers Prioritize Trusted Traffic",
"Defining CoS Rewrite Rules (CLI Procedure)",
"Defining CoS Rewrite Rules (J-Web Procedure)",
"Understanding CoS Rewrite Rules"
] |
loss-priority (Scheduler Drop Profiles) | loss-priority (any | high | low | medium-high | medium-low); | [edit class-of-service schedulers scheduler-name drop-profile-map] | Specify a loss priority to which to apply a drop profile. The drop profile map sets the drop profile for a
specific PLP and protocol type. The inputs for the map are the PLP designation and the protocol type.
The output is the drop profile. | [
{
"name": "any",
"desc": "The drop profile applies to packets with any PLP."
},
{
"name": "high",
"desc": "The drop profile applies to packets with high PLP."
},
{
"name": "low",
"desc": "The drop profile applies to packets with low PLP."
},
{
"name": "medium-high",
"desc... | 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. | [
"Default Schedulers Overview",
"Determining Packet Drop Behavior by Configuring Drop Profile Maps for Schedulers",
"Configuring Schedulers for Priority Scheduling",
"Configuring and Applying Tricolor Marking Policers"
] |
loss-priority (Simple Firewall Filter) | loss-priority (high | low | medium); | [edit firewall family family-name simple-filter filter-name term term-name then] | Set the loss priority of incoming packets. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configuring Multifield Classifiers"
] |
loss-priority high then discard (Three-Color Policer) | loss-priority high then discard; | [edit dynamic-profiles profile-name firewall three-color-policer name action],
[edit firewall three-color-policer policer-name action],
[edit logical-systems logical-system-name firewall three-color-policer policer-name action] | For packets with high loss priority, discard the packets. The loss priority setting is implicit and is not
configurable. Include this statement if you do not want the local router to forward packets that have
high packet loss priority.
For single-rate three-color policers, the Junos OS assigns high loss priority to pac... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 8.2.
Logical systems support introduced in Junos OS Release 9.3.
Support at the [edit dynamic-profiles ... action] hierarchy level introduced in Junos OS Release 11.4. | [
"Three-Color Policer Configuration Overview",
"Basic Single-Rate Three-Color Policers",
"Basic Two-Rate Three-Color Policers",
"Two-Color and Three-Color Logical Interface Policers",
"Two-Color and Three-Color Physical Interface Policers",
"Two-Color and Three-Color Policers at Layer 2"
] |
loss-priority | loss-priority (high | low); | [edit interfaces interface-name gigether-options ethernet-switch-profile ethernet-policer-profile
output-priority-map classifier premium forwarding-class class-name] | Specify the packet loss priority value. | [
{
"name": "high",
"desc": "Packet has high loss priority."
},
{
"name": "low",
"desc": "Packet has low loss priority."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Gigabit Ethernet Policers"
] |
loss-priority-maps (Assigning to an Interface) | loss-priority-maps {
frame-relay-de (loss-priority-rewrite-name | default);
} | [edit class-of-service interfaces interface-name unit logical-unit-number] | Assign the loss priority map to a logical interface. | [
{
"name": "default",
"desc": "Apply the default loss priority map. The default map includes the following configuration:"
},
{
"name": "loss-priority low code-point 0;",
"desc": ""
},
{
"name": "loss-priority high code-point 1;",
"desc": ""
},
{
"name": "map-name",
"desc"... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in JUNOS Release 11.4. | [
"Assigning the Default Frame Relay Discard Eligibility Loss Priority Map to an Interface"
] |
loss-priority-maps (CoS Interfaces) | loss-priority-maps {
frame-relay-de (map-name | default);
} | [edit class-of-service interfaces interface-name unit logical-unit-number] | Assign the loss priority map to a logical interface. | [
{
"name": "default",
"desc": "Apply default loss priority map. The default map contains the following:"
},
{
"name": "loss-priority low code-point 0;",
"desc": ""
},
{
"name": "loss-priority high code-point 1;",
"desc": ""
},
{
"name": "map-name",
"desc": "Name of loss pr... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Understanding Interfaces"
] |
loss-priority-maps (CoS) | loss-priority-maps {
frame-relay-de loss-priority-map-name {
loss-priority (high | low | medium-high | medium-low) {
code-points [bit-string];
}
}
} | [edit class-of-service] | Map the loss priority of incoming packets based on CoS values. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Understanding Interfaces"
] |
loss-priority-maps | loss-priority-maps {
frame-relay-de rewrite-name {
loss-priority level {
code-points [ aliases] [ bit-patterns ];
}
}
} | [edit class-of-service] | Map the loss priority of incoming packets based on the CoS values. | [
{
"name": "frame-relay-de rewrite-name",
"desc": "Name of the Frame Relay DE bit loss priority map."
},
{
"name": "loss-priority level",
"desc": "The loss priority level can be one of the following:"
},
{
"name": "high",
"desc": "Packet has high loss priority."
},
{
"name": "... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in JUNOS Release 11.4. | [
"Assigning the Default Frame Relay Discard Eligibility Loss Priority Map to an Interface"
] |
loss-priority-rewrites (Assigning to an Interface) | loss-priority-rewrites {
frame-relay-de (loss-priority-rewrite-name | default);
} | [edit class-of-service interfaces interface-name unit logical-unit-number] | Associate the loss priority rewrites to an outgoing packet. | [
{
"name": "loss-priority-rewrite-name",
"desc": "Name of the loss priority rewrite to be applied to an interface."
},
{
"name": "default",
"desc": "Default loss priority rewrite to be applied to an interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [] |
loss-priority-rewrites | loss-priority-rewrites {
frame-relay-de rewrite-name {
loss-priority level {
code-points [ bit-patterns ];
}
}
} | [edit class-of-service] | Specify the Frame Relay discard eligibility (DE) bit rewrite rule on the enhanced IQ PIC. | [
{
"name": "frame-relay-de rewrite-name",
"desc": "Name of the Frame Relay DE bit loss priority rewrite rule."
},
{
"name": "loss-priority level",
"desc": "The loss priority level can be one of the following:"
},
{
"name": "high",
"desc": "Packet has high loss priority."
},
{
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [] |
loss-threshold | loss-threshold number; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name continuity-check] | Specify the number of continuity check messages lost before marking the remote MEP as down. The
value can be from 3 to 256 protocol data units (PDUs). The default value is 3 PDUs. | [
{
"name": "number",
"desc": "The number of continuity check messages that can be lost before the remote MEP is considered"
}
] | 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. | [
"Continuity Check Protocol Parameters Overview",
"Configuring Continuity Check Protocol Parameters for Fault Detection"
] |
low-latency | low-latency | [edit chassis fpc fpc-slot-number pic pic-slot-number services-offload] | Enables the low-latency mode on the selected NP-IOC. Low-latency is not enabled by default. The low
latency allows you to configure the mode of the network processor’s traffic manager (TM) on the egress
path. If low latency is enabled, the network processor is initialized without the traffic manager, thus
reducing the ... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. | [
"Understanding Traffic Processing on Security Devices"
] |
low-watermark | low-watermark percent; | [edit security flow aging] | Set the point at which the aggressive aging-out process ends. | [
{
"name": "percent",
"desc": "Percentage of session-table capacity at which aggressive aging-out ends."
}
] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Understanding Traffic Processing on Security Devices"
] |
lowest-priority-defect | lowest-priority-defect (all-defects | err-xcon | mac-rem-err-xcon | no-defect | rem-err-xcon |
xcon) | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name mep mep-id] | Specify the lowest priority defect that is allowed to generate a Fault Alarm whenever CFM detects a
defect. This configuration is done at the MEP level. | [
{
"name": "all-defects",
"desc": "Allows all defects."
},
{
"name": "err-xcon",
"desc": "Allows only erroneous CCM and cross-connect CCM defects."
},
{
"name": "mac-rem-err-xcon",
"desc": "Allows only MAC, not receiving CCM, erroneous CCM, and cross-connect defects."
},
{
"na... | 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. | [
"Configuring a MEP to Generate and Respond to CFM Protocol Messages"
] |
lrf-profile (Service Set) | lrf-profile profile-name; | [edit services service-set service-set-name] | Assign the LRF profile to the service set that is configured for application-aware policy control. | [
{
"name": "profile-name",
"desc": "LRF profile name. The referenced LRF profile must be configured."
}
] | 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. | [
"Assigning an LRF Profile to Subscribers",
"Configuring an LRF Profile for Subscribers",
"Configuring Logging and Reporting for Junos OS Subscriber Aware",
"Applying Logging and Reporting Configuration to a Subscriber Management Service Set",
"Configuring Logging and Reporting for Subscriber Management"
] |
lsa-refresh-interval | lsa-refresh-interval minutes; | [edit logical-systems logical-system-name protocols (ospf | ospf3)],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(ospf | ospf3)],
[edit logical-systems log... | Configure the refresh interval for all self-generated link-state advertisement (LSAs). The OSPF standard
requires that every LSA be refreshed every 30 minutes. The Juniper Networks implementation refreshes
LSAs every 50 minutes. By default, any LSA that is not refreshed expires after 60 minutes. By using this
configur... | [
{
"name": "minutes",
"desc": "Time between an LSA refresh, in minutes."
}
] | 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. | [
"Configuring OSPF Refresh and Flooding Reduction in Stable Topologies"
] |
lsp-attributes | lsp-attributes {
encoding-type (ethernet | packet | pdh | sonet-sdh);
gpid (ethernet | hdlc | ipv4 | pos-scrambling-crc-16 | pos-no-scrambling-crc-16 | pos-
scrambling-crc-32 | pos-no-scrambling-crc-32 | ppp);
signal-bandwidth type;
switching-type (fiber | lambda | psc-1 | tdm);
} | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name] | Define the parameters signaled during LSP setup. These usually determine the nature of the resource
(label) allocated for the LSP.
The remaining statements are explained separately. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
pos-scrambling-crc-16, pos-no-scrambling-crc-16, pos-scrambling-crc-32, and pos-no-scrambling-crc-32 options
added in Junos OS Release 8.0. | [
"Configuring MPLS LSPs for GMPLS"
] |
lsp-cleanup-timer | lsp-cleanup-timer seconds; | [edit protocols pcep pce pce-id]
[edit protocols pcep pce-group group-id] | Specify the amount of time (in seconds) that the Path Computation Client (PCC) must wait before
deleting any non-delegated Path Computation Element (PCE)-initiated LSPs from the failed PCE after a
PCEP session terminates.
NOTE: In compliance with draft-ietf-pce-stateful-pce-09, revoking of PCE-initiated LSP
delegations... | [
{
"name": "seconds",
"desc": "Time (in seconds) that the PCC must wait before deleting any non-delegated PCE-initiated LSPs from the failed PCE after a PCEP session terminates. Non-delegated PCE-initiated LSPs are deleted immediately. Range: 0 through 2147483647 seconds Default: 60"
}
] | 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. | [] |
lsp-external-controller | lsp-external-controller controller-name{
(delay-metric-bound | igp-metric-bound | te-metric-bound);
} | [edit protocols mpls],
[edit protocols mpls label-switched-path lsp-name]
[edit protocols spring-traffic-engineering] | Enable external path computing capability for the device. | [
{
"name": "controller-name",
"desc": "Name of the external path computing entity. By default, pccd is the only allowed LSP external controller. Values: pccd"
},
{
"name": "delay-metric-bound",
"desc": "Indicates the maximum metric value, a path can have, for the metric-type delay variation. Va... | 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.
Support for ACX Series added in Junos OS Release 17.1.
Support at the [edit protocols spring-traffic-engineering] hierarchy level introduced in Junos OS Release
17.2.
Support at the following hierarchy levels introduced in Junos OS Release 20.1R1: [edit protocols source-
p... | [
"PCEP Configuration"
] |
lsp-lifetime | lsp-lifetime seconds; | [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] | Specify how long a link-state PDU originating from the routing device should persist in the network. The
routing device sends link-state PDUs often enough so that the link-state PDU lifetime never expires.
Because link-state PDUs have a maximum lifetime, they need to be refreshed. Refreshing means that a
routing device... | [
{
"name": "seconds",
"desc": "link-state PDU lifetime, in seconds."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring the Transmission Frequency for CSNP Packets on IS-IS Interfaces",
"Example: Configuring the Transmission Frequency for Link-State PDUs on IS-IS Interfaces",
"Understanding Link-State PDU Throttling for IS-IS Interfaces",
"Understanding the Transmission Frequency for CSNPs on IS-IS Interf... |
lsp-next-hop (CoS-Based Forwarding) | lsp-next-hop [ lsp-regular-expression ]; | [edit class-of-service forwarding-policy next-hop-map map-name forwarding-class class-name] | Specify the LSP regular expression to which to map forwarded traffic. | [
{
"name": "lsp-regular-expression",
"desc": "Next-hop LSP label."
}
] | 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-Based Forwarding"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.