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 |
|---|---|---|---|---|---|---|---|
lldp-priority | lldp-priority; | [edit poe],
[edit poe fpc (all | slot-number)] | Configure the switch to assign interfaces the power priority provided by the powered device by using
Link Layer Discovery Protocol (LLDP) power negotiation rather than the power priority configured on
the switch 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. | [
"Configuring PoE Interfaces on EX Series Switches"
] |
lmi (Ethernet OAM) | lmi {
status-counter count;
polling-verification-timer value;
interface name {
uni-id uni-name;
status-counter number;
polling-verification-timer value;
evc-map-type (all-to-one-bundling | bundling | service-multiplexing);
evc evc-name {
default-evc;
... | [edit protocols oam ethernet] | On routers with ge, xe, or ae interfaces, configure an OAM Ethernet Local Management Interface (E-LMI).
NOTE: On MX Series routers, E-LMI is supported on Gigabit Ethernet (ge), 10-Gigabit
Ethernet (xe), and Aggregated Ethernet (ae) interfaces configured on MX Series routers
with DPC only. | [
{
"name": "status-counter count",
"desc": "Status counter (N393), defaults to 4."
},
{
"name": "interface name",
"desc": "Polling verification timer (T392), defaults to 15 seconds."
},
{
"name": "uni-id uni-name",
"desc": "(Optional) Defaults to the physical interface name."
},
{... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring Ethernet Local Management Interface"
] |
lmi-type | lmi-type (ansi | itu); | [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options] | Set the Frame Relay Local Management Interface (LMI) type. | [
{
"name": "ansi",
"desc": "Use American National Standards Institute (ANSI) T1.167 Annex D LMIs."
},
{
"name": "itu",
"desc": "Use ITU Q933 Annex A LMIs."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Keepalives on Link Services Physical Interfaces"
] |
lmp-control-channel | lmp-control-channel control-channel-interface {
remote-address ip-address;
} | [edit logical-systems logical-system-name protocols link-management peer peer-name],
[edit protocols link-management peer peer-name] | Specify the Link Management Protocol (LMP) control channel interface for the peer. | [
{
"name": "control-channel-interface",
"desc": "Name of the control channel interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Configuring the LMP Control Channel Interface for the Peer"
] |
lmp-protocol | lmp-protocol {
hello-dead-interval milliseconds;
hello-interval milliseconds;
passive;
retransmission-interval milliseconds;
retry-limit number;
} | [edit logical-systems logical-system-name protocols link-management peer peer-name],
[edit protocols link-management peer peer-name] | Configure attributes of Link Management Protocol (LMP) to establish and maintain the LMP control
channel for the peer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Configuring LMP Peers"
] |
load access-security slaac-snooping persistent-file | load access-security slaac-snooping persistent-file (local_pathname | remote_URL) | Load a SLAAC snooping database file to ensure that IPv6-MAC bindings persist through the device
reboots by specifying a local pathname or a remote URL. | [
{
"name": "(local_pathname | remote_URL)",
"desc": "Specify either a local pathname or a remote URL for the SLAAC snooping database file."
}
] | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy.
Output Fields
This command produces no output.
Sample Output
load access-security slaac-snooping persistent-file
user@switch> load access-security slaac-snooping persisten... | Command introduced in Junos OS Release 19.2R1. | [] | |
load | load ((dhcp-security-snoop | dhcpv6-security-snoop) filename | ssl-certificate (file filename |
path pathname)) | Load and update the operational state from an ASCII file, or load an SSL certificate to enable secure
authentication and ensure data encryption.
For information on valid filename and URL formats, see Format for Specifying Filenames and URLs in
Junos OS CLI Commands. | [
{
"name": "dhcp-security-snoop",
"desc": "Load DHCPv4 snooping entries from a file and create or populate the DHCPv4"
},
{
"name": "dhcpv6-security-snoop",
"desc": "Load DHCPv6 snooping entries from a file and create or populate the DHCPv6"
},
{
"name": "filename",
"desc": "Name of t... | NOTE: The load commands for dhcp-security-snoop and dhcpv6-security-snoop are restricted to
admin only.
NOTE: The load command with dhcp-security-snoop and dhcpv6-security-snoop options does
not produce any output unless an execution error occurs, in which case relevant error
message is displayed on the console.
view | Command introduced before Junos OS Release 7.4.
dhcp-security-snooping option introduced in Junos OS Release 13.1R1.
dhcpv6-security-snooping option introduced in Junos OS Release 14.1R1. | [
"Loading a Configuration from a File or the Terminal"
] | |
load-balance (ecmp) | load-balance {
adaptive;
consistent-hash;
destination-ip-only;
per-packet;
profile1;
profile2;
random;
source-ip-onl... | [edit policy-options policy-statement policy-name then] | Specify the type of load balancing of an equal-cost multipath (ECMP) in the forwarding table.
By default, Junos OS uses a hashing method based only on the destination address to elect a forwarding
next hop when multiple equal-cost paths are available. As a result, when multiple routers or switches
share the same set of... | [
{
"name": "adaptive",
"desc": "Adaptive load balancing. Dynamically manages and distributes traffic loads across multiple ECMP paths by monitoring packet and byte counts for each hash bucket and employing a feedback mechanism to detect and correct overload conditions."
},
{
"name": "consistent-hash"... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
load-balance (Forwarding Options) | load-balance {
indexed-load-balance;
per-flow {
hash-seed;
}
per-prefix {
hash-seed number;
}
} | [edit forwarding-options],
[edit logical-systems logical-system-name forwarding-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-
options],
[edit routing-instances routing-instance-name forwarding-options] | Enable per-prefix or per-flow load balancing so that the router or switch elects a next hop independently
of the route selected by other routers or switches.
For the active route, when there are multiple equal-cost paths to the same destination, by default, Junos
OS chooses in a random fashion one of the next-hop addre... | [] | 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.
Support for per-flow load balancing introduced in Junos OS Release 9.3. | [
"Example: Load Balancing BGP Traffic",
"Configuring Per-Flow Load Balancing Based on Hash Values",
"Configuring Per-Prefix Load Balancing"
] |
load-balance (Protocols RSVP) | load-balance {
bandwidth;
} | [edit logical-systems logical-system-name protocols rsvp],
[edit protocols rsvp] | Load-balance traffic between RSVP LSPs. | [
{
"name": "bandwidth",
"desc": "Load-balance traffic between RSVP LSPs based on the bandwidth configured for each LSP."
}
] | 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 Load Balancing Across RSVP LSPs"
] |
load-balance profile1/profile2 | load-balance profile1/profile2 | [edit policy-options policy-statement policy name then] | Apply any one of two predefined load balance profiles (profile1 or profile2) for the matching route.
Default
•
Default profile or global profile - a route without a policy-options specified load-balance profile will
be grouped to the default profile or global profile. | [
{
"name": "profile1",
"desc": ""
},
{
"name": "profile2",
"desc": ""
}
] | •
routing—To view this statement in the configuration.
•
routing-control—To add this statement to the configuration. | Statement introduced in Junos 23.2 | [
"enhanced-hash-key profile1/profile2",
"hash-seed (profile)"
] |
load-balance | load-balance {
adaptive{
pps;
scan-interval multiple;
tolerance percentage;
}
no-adaptive;
per-packet;
} | [edit dynamic-profiles name interfaces name aggregated-ether-options],
[edit dynamic-profiles name interfaces name logical-tunnel-options],
[edit dynamic-profiles name interfaces interface-range name aggregated-ether-options],
[edit dynamic-profiles name interfaces interface-range name logical-tunnel-options],
[edit dy... | Load-balances the received traffic across all the available paths of aggregated Ethernet bundles for
better link utilization. | [
{
"name": "adaptive",
"desc": "(MX Series and PTX Series) Corrects a genuine traffic imbalance by using a feedback mechanism to distribute the traffic across the links of an Aggregated Ethernet bundle."
},
{
"name": "no-adaptive",
"desc": "(MX Series and PTX Series) Disables the adaptive load-ba... | interface - To view statement in the configuration.
interface-control - To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Understanding Aggregated Ethernet Load Balancing",
"Example: Configuring Aggregated Ethernet Load Balancing"
] |
load-balance-algorithm | load-balance-algorithm (simple | enode-based | flogi-based); | [edit fc-fabrics fabric-name proxy] | Set the load-balancing algorithm that the QFX Series uses to distribute FCoE sessions (FLOGI and FDISC
sessions from the FCoE devices in the Ethernet network) among the NP_Port links to the FC switch.
NOTE: Changing the load-balancing algorithm when FCoE sessions are running forces
the FCoE sessions to log out, then lo... | [
{
"name": "simple",
"desc": "Load balancing is based on the weighted utilization (load) of the NP_Ports connected to an FC"
},
{
"name": "enode-based",
"desc": "Load balancing is based on the ENode FLOGI. When an ENode logs in to the fabric, all"
},
{
"name": "flogi-based",
"desc": "... | storage—To view this statement in the configuration.
storage-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Defining the Proxy Load-Balancing Algorithm",
"Example: Configuring Automated Fibre Channel Interface Load Rebalancing",
"Simulating On-Demand Fibre Channel Link Load Rebalancing (Dry Run Test)",
"Monitoring Fibre Channel Interface Load Balancing",
"Understanding Load Balancing in an FCoE-FC Gateway Proxy ... |
load-balance-group | load-balance-group group-name {
next-hop-group [ group-names ];
} | [edit firewall] | Configure a load-balance group. | [
{
"name": "group-name",
"desc": "Name of load-balance group."
},
{
"name": "group-names",
"desc": "Name of next-hop groups to include in the load-balance group set."
}
] | 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. | [
"Configuring Load-Balance Groups",
"Routing Policies, Firewall Filters, and Traffic Policers User Guide"
] |
load-balance-label-capability | load-balance-label-capability; | [edit forwarding-options] | Enables the router to push and pop the load balancing label and causes LDP and RSVP to advertise the
entropy label TLV to neighboring routers.
The load-balance-label-capability and no-load-balance-label-capability statements at the [edit forwarding-
options] hierarchy level are mutually exclusive, and at a given point ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Configuring the Entropy Label for LSPs"
] |
load-balance-stateful (Aggregated Ethernet Interfaces) | load-balance-stateful {
per-flow;
rebalance interval;
load-type (low | medium | large);
} | [edit interfaces aeX unit logical-unit-number forwarding-options] | Define the capability to perform uniform load balancing and also perform rebalancing is introduced on
MX Series routers with MPCs, except MPC3Es and MPC4Es. Rebalancing is not supported when load-
balancing is skewed or distorted owing to a change in the number of flows. The mechanism to record
and retain states for th... | [
{
"name": "stateful",
"desc": "Define the stateful load-distribution mechanism for traffic flows on aggregated Ethernet interfaces."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R1. | [
"Configuring Stateful Load Balancing on Aggregated Ethernet Interfaces"
] |
load-balancing-options (Aggregated Multiservices) | load-balancing-options {
high-availability-options {
(many-to-one | one-to-one) {
preferred-backup preferred-backup;
}
}
member-failure-options {
drop-member-traffic {
rejoin-timeout rejoin-timeout;
}
redistribute-all-traffic {
enab... | [edit interfaces interface-name] | Configure the high availability (HA) options for the aggregated multiservices (AMS) interface.
Many-to-one (N:1) high availability mode for service applications like Network Address Translation
(NAT) is supported. In the case of N:1 high availability mode, one services PIC is the backup (in hot
standby mode) for one or... | [] | 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.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Understanding Aggregated Multiservices Interfaces",
"Example: Configuring an Aggregated Multiservices Interface (AMS)"
] |
load-balancing-options (Service Set) | load-balancing-options {
hash-keys {
egress-key (destination-ip | source-ip);
ingress-key (destination-ip | source-ip);
}
} | [edit services service-set service-set-name interface-service] | Configure the load-balancing options for aggregated multiservices (AMS) in service applications
(Network Address Translation [NAT], stateful firewall, application-level gateway [ALG], HTTP header
enrichment, and mobility). AMS for service applications can be used for load balancing with or without
high availability (HA... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS 11.4. | [
"Understanding Aggregated Multiservices Interfaces",
"Example: Configuring an Aggregated Multiservices Interface (AMS)"
] |
load-interval | load-interval seconds; | [edit interfaces dln unit logical-unit-number dialer-options],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number dialer-options] | On J Series Services Routers with ISDN logical interfaces, specify the interval used to calculate the
average load on the network. By default, the average interface load is calculated every 60 seconds. | [
{
"name": "seconds",
"desc": "Number of seconds at which the average load calculation is triggered."
}
] | 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. | [] |
load-scripts-from-flash (Scripts) | load-scripts-from-flash; | [edit system scripts] | Load commit, event, op, SNMP, and library scripts from the device’s flash memory instead of the hard
disk.
When you configure this statement, all commit, event, op, SNMP, and script library scripts are loaded
from the /config/scripts directory in flash memory under the subdirectory appropriate to the script type.
To en... | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Storing Scripts in Flash Memory"
] |
load-threshold | load-threshold percent; | [edit interfaces dln unit logical-unit-number dialer-options],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number dialer-options] | On J Series Services Routers with ISDN logical interfaces, specify the bandwidth threshold percentage
used for adding interfaces. Another link is added to the multilink bundle when the load reaches the
threshold value you set. Specify a percentage between 0 and 100. | [
{
"name": "percent",
"desc": "Bandwidth threshold percentage used for adding interfaces. When set to 0, all available"
}
] | 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. | [] |
load-type (Aggregated Ethernet Interfaces) | load-type (low | medium | large); | [edit interfaces aeX unit logical-unit-number forwarding-options load-balance-stateful] | Define the load-balancing type to inform the Packet Forwarding Engine regarding the appropriate
memory pattern to be used for traffic flows. The approximate number of flows for effective load-
balancing for each keyword is a derivative. | [
{
"name": "low",
"desc": "Define a low load-balancing method if the number of flows that flow on the specified aggregated Ethernet interface is less or minimal (between 1 and 100 flows)."
},
{
"name": "medium",
"desc": "Define a medium or moderate load-balancing method if the number of flows tha... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R1. | [
"Configuring Stateful Load Balancing on Aggregated Ethernet Interfaces"
] |
loc-rib | loc-rib {
rib-filter <X>
route-filter <Y>
} | [edit logical-systems name routing-instancesname routing-options bmp route-monitoring],
[edit logical-systems name routing-options bmp route-monitoring],
[edit logical-systems name tenants name routing-instances name routing-options bmp route-monitoring],
[edit routing-instances name routing-options bmp route-monitorin... | Enable local routing information base (RIB) route monitoring messages. | [
{
"name": "rib-filter x",
"desc": "Specify a policy to accept or reject a set of RIBs. You can specify multiple rib lists to filter in or filter them out."
},
{
"name": "route-filter y",
"desc": "Specify a policy with a set of match conditions for route filtering such as neighbor, prefixes etc. ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.4R1. | [] |
local (Analytics Collector) | local {
file filename {
size size;
files number;
}
} | [edit services analytics collector] | Configure a local file for logging network analytics (queue and traffic) statistics.
NOTE: The local statement is not available in Junos OS Releases prior to 13.2X51-D15.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Network Analytics Overview"
] |
local (certificates) | local certificate-name {
certificate-key-string;
load-key-file URL filename;
} | [edit security certificates] | Import a paired X.509 private key and authentication certificate, to enable Junos XML protocol client
applications to establish Secure Sockets Layer (SSL) connections to the router or switch.
NOTE: For FIPS mode, the digital security certificates must be compliant with the
National Institute of Standards and Technology... | [
{
"name": "certificate-key-string",
"desc": "String of alphanumeric characters that constitute the private key and certificate."
},
{
"name": "certificate-name",
"desc": "Name that uniquely identifies the certificate."
},
{
"name": "load-key-file URL",
"desc": ""
},
{
"name":... | 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. | [
"Importing SSL Certificates for Junos XML Protocol Support"
] |
local (Flat-File Access Profile) | local {
flat-file-profile profile-name;
} | [edit access profile profile-name] | Configure local reporting of service accounting statistics according to the specified flat-file profile, which
determines the accounting statistics and nonstatistical parameters that are collected and reported in the
local flat file. This configuration collects the running total service statistics per interface family.... | [
{
"name": "profile-name",
"desc": "Name of the flat-file profile."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
This statement is no longer supported as of Junos OS Release 18.4R1 | [
"Configuring Service Accounting in Local Flat Files",
"Flat-File Accounting Overview"
] |
local | local {
address address;
disable;
family (inet | inet6) anycast-pim;
}
group-ranges {
destination-ip-prefix</prefix-length>;
}
hold-time seconds;
override;
priority number;
process-non-null-as-null-register ;
} | [edit logical-systems logical-system-name protocols pim rp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp],
[edit protocols pim rp],
[edit routing-instances routing-instance-name protocols pim rp] | Configure the routing device’s RP properties.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Local PIM RPs",
"Example: Configuring PIM Anycast With or Without MSDP"
] |
local-address (Junos Telemetry Interface) | local-address local-address; | [edit services analytics export-profile export-profile-name] | For legacy gRPC dialout connections, configure the local IPv4 or IPv6 address in an export profile.
Configuring the local address lets you bypass the current default way of addressing, which is that the
outgoing interface IP address is used as the source address. You can configure the local address to be
your router's ... | [
{
"name": "local-address",
"desc": "An IPv4 or IPv6 address."
}
] | Edit | Statement introduced in Junos OS Evolved 24.2R1 (for IPv6) on ACX7024, ACX7024X, ACX7100-32C,
ACX7100-48L, ACX7332, ACX7348, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008,
PTX10016, QFX5130E-32CD, QFX5130-48C, QFX5130-48CM, QFX5220, and QFX5700E. | [
"Using gRPC Dial-Out for Secure Telemetry Collection"
] |
local-address (Protocols AMT) | local-address ip-address; | [edit logical-systems logical-system-name protocols amt relay family inet],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols amt
relay family inet],
[edit protocols amt relay family inet],
[edit routing-instances routing-instance-name protocols amt relay family inet] | Specify the local unique IP address to send in Automatic Multicast Tunneling (AMT) relay advertisement
messages, for use as the IP source of AMT control messages, and as the source of the data tunnel
encapsulation. The address can be configured on any interface in the system. Typically, the router’s lo0.0
loopback addr... | [
{
"name": "ip-address",
"desc": "Unique unicast IP address."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring the AMT Protocol"
] |
local-address (Protocols BGP) | local-address address; | [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 the address of the local end of a BGP session. This address is used to accept incoming
connections to the peer and to establish connections to the remote peer. When none of the operational
interfaces are configured with the specified local address, a session with a BGP peer is placed in the idle
state.
You gene... | [
{
"name": "address",
"desc": "IPv6 or IPv4 address of the local end of the connection."
}
] | 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 Internal BGP Peering Sessions on Logical Systems",
"Example: Configuring Internal BGP Peer Sessions",
"Understanding Internal BGP Peering Sessions"
] |
local-address (Protocols Link Management) | local-address ip-address; | [edit logical-systems logical-system-name protocols link-management te-link te-link-name],
[edit logical-systems logical-system-name protocols link-management te-link te-link-name
interface interface-name],
[edit protocols link-management te-link te-link-name],
[edit protocols link-management te-link te-link-name inte... | Specify the local IP address associated with the traffic engineering link. If you configure the local IP
address, you must also configure the "remote-address" on page 14859 statement. | [
{
"name": "local-address",
"desc": "Local IP address of the traffic engineering link."
}
] | 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 Local IP Address for Traffic Engineering Links",
"Configuring the Local IP Address for Forwarding Adjacencies"
] |
local-address (Protocols MSDP) | local-address address; | [edit logical-systems logical-system-name protocols msdp],
[edit logical-systems logical-system-name protocols msdp group group-name],
[edit logical-systems logical-system-name protocols msdp group group-name peer address],
[edit logical-systems logical-system-name protocols msdp peer address],
[edit logical-systems lo... | Configure the local end of an MSDP session. You must configure at least one peer for MSDP to function.
When configuring a peer, you must include this statement. This address is used to accept incoming
connections to the peer and to establish connections to the remote peer. | [
{
"name": "address",
"desc": "IP address of the local end of the connection."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring MSDP in a Routing Instance"
] |
local-address (Protocols PIM) | local-address address; | [edit logical-systems logical-system-name protocols pim rp local family (inet | inet6) anycast-pim],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp local family (inet | inet6) anycast-pim],
[edit protocols pim rp local family (inet | inet6) anycast-pim],
[edit routin... | Configure the routing device local address for the anycast rendezvous point (RP). If this statement is
omitted, the router ID is used as this address. | [
{
"name": "address",
"desc": "Anycast RP IPv4 or IPv6 address, depending on family configuration."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Example: Configuring PIM Anycast With or Without MSDP"
] |
local-address (Routing Options) | local-address address; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast backup-pe-group group-name],
[edit logical-systems logical-system-name routing-options multicast backup-pe-group group-name],
[edit routing-instances routing-instance-name routing-options multicast backup-pe-gro... | Configure the address of the local PE for ingress PE redundancy when point-to-multipoint LSPs are used
for multicast distribution. | [
{
"name": "address",
"desc": "Address of local PEs in the backup group."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Statement added to the multicast hierarchy in Junos OS Release 13.2. | [
"Example: Configuring Ingress PE Redundancy"
] |
local-as | local-as autonomous-system <loops number> <private | alias> <no-prepend-global-as>; | [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 the BGP local autonomous system (AS) number for a BGP neighbors. This local AS may differ
from the global AS configured under the routing-options autonomous system statement.
An AS is a set of routing devices that are under a single technical administration and generally use a
single interior gateway protocol (... | [
{
"name": "alias",
"desc": "(Optional) Configure the local AS as an alias of the global AS number configured for the router under [edit routing-options] autonomous-system. As a result, a BGP peer considers any local AS to which it is assigned as equivalent to the primary AS number configured for the routing... | 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.
alias option introduced in Junos OS Release 9.5.
loops and no-prepend-global-as options introduced in Junos OS Release 9.6. | [
"Examples: Configuring BGP Local AS",
"Example: Configuring a Local AS for EBGP Sessions",
"Mastering Local AS - Default mode",
"Mastering Local AS - Alias Mode",
"Mastering Local AS - Private Mode",
"Mastering Local AS - No-Prepend-Global-AS",
"Mastering Local AS - Private No-Prepend-Global-AS"
] |
local-authentication (Dynamic PPP Options) | local-authentication {
password password;
username-include {
circuit-id;
delimiter character;
domain-name name;
mac-address;
remote-id;
}
} | [edit dynamic-profiles name interfaces $junos-interface-ifd-name unit $junos-interface-unit ppp-
options] | Configure local authentication for terminated PPP subscribers. This enables the external RADIUS server
to pass implementation-specific configuration for successfully authenticated subscribers. Local
authentication enables the same dynamic profile to support both CPEs that do not negotiate
authentication protocols and C... | [
{
"name": "password password",
"desc": "Specify the local authentication password The remaining statement is explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | interface | Statement introduced in Junos OS Release 18.2R1. | [
"PPP Subscriber Access Networks Overview"
] |
local-bias (ae load-balance) | local-bias percent bias; | [edit interfaces aex aggregated-ether-options load-balance] | Next hop addresses may be local or remote, and traffic can be expected to be more-or-less evenly
distributed among the available next-hop addresses whether they are local or remote. You can skew
distribution to favor local addresses, however, by setting a value for local bias (local relative to the
packet forwarding en... | [] | interface - To view statement in the configuration.
interface-control - To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1. | [
"Understanding Aggregated Ethernet Load Balancing",
"Example: Configuring Aggregated Ethernet Load Balancing"
] |
local-bias (ae) | local-bias; | [edit interfaces aex aggregated-ether-options] | Enable local link bias for all links in the aggregated Ethernet interface.
Local link bias conserves bandwidth on Virtual Chassis ports (VCPs) by using local links to forward
unicast traffic exiting a Virtual Chassis or Virtual Chassis Fabric (VCF) that has a Link Aggregation group
(LAG) bundle composed of member links... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51-D20. | [
"Configuring Local Link Bias",
"Understanding Local Link Bias"
] |
local-bias | local-bias percent bias; | [edit interfaces rlt x logical-tunnel-options load-balance] | Next hop addresses may be local or remote, and absent any other load balancing scheme (except
adaptive load balancing), traffic can be expected to be more-or-less evenly distributed among the
available next-hop addresses whether they are local or remote. You can skew distribution to favor local
addresses, however, by s... | [] | interface - To view statement in the configuration.
interface-control - To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1. | [] |
local-bw-override-threshold | local-bw-override-threshold; | [edit logical-systems name protocols rsvp interface name non-rsvp-bandwdith],
[edit logical-systems name routing-instances name protocols rsvp interface name non-rsvp-bandwdith],
[edit protocols rsvp interface name non-rsvp-bandwdith],
[edit routing-instances name protocols rsvp interface name non-rsvp-bandwdith] | RSVP local unreserved bandwidth is updated irrespective of the threshold configured on the update-
threshold-max-reservable is crossed or not. As this statement only changes RSVP local bandwidth behavior,
IGP bandwidth update behavior using the update-threshold-max-reservable statement remains same. | [] | 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 and Junos OS Evolved Release 21.3R1. | [] |
local-category (Next Gen Services Service-Set Local System Logging) | local-category category, category....category; | [edit services service-set name syslog | Specify the category for which you want to collect local logs. | [
{
"name": "all",
"desc": "All events are logged"
},
{
"name": "content-security",
"desc": "Content security events are logged"
},
{
"name": "fw-auth",
"desc": "Fw-auth events are logged"
},
{
"name": "screen",
"desc": "Screen events are logged"
},
{
"name": "alg",... | system | Statement introduced in Junos OS Release 19.3R2. | [
"Understanding Next Gen Services CGNAT Global System Logging",
"Enabling Global System Logging for Next Gen Services",
"Configuring System Logging to One or More Remote Servers for Next Gen Services",
"Configuring Local System Logging for Next Gen Services"
] |
local-certificate (Security) | local-certificate certificate-filename; | [edit security ike policy ike-peer-address] | Configure the certificate filename from which to read the local certificate. | [
{
"name": "certificate-filename",
"desc": "File from which to read the local certificate."
}
] | 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 an IKE Policy for Digital Certificates for an ES PIC"
] |
local-certificate (System) | local-certificate name; | [edit system ntp nts],
[edit system services extension-service request-response grpc ssl],
[edit system services http servers server name tls],
[edit system services service-deployment] | Specify the SSL or TLS certificate to use to authenticate the local device for system services, gRPC
Remote Procedure Calls (gRPC), and Network Time Security (NTS) using Network Time Protocol (NTP).
Specify the name of a local certificate. There is no default for local-certificate. The value for local-
certificate shou... | [] | 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.
Support at the [edit system services extension-service request-response thrift] hierarchy level introduced in
Junos OS Release 16.1.
Support at the [edit system services http servers server name tls] hierarchy level introduced in Junos OS
Release 25.2R1 and Junos OS Evo... | [
"Configuring clear-text or SSL Service for Junos XML Protocol Client Applications",
"Importing SSL Certificates for Junos XML Protocol Support",
"local"
] |
local-certificate | local-certificate identifier; | [edit services ipsec-vpn ike policy policy-name] | Name of the certificate that needs to be sent to the peer during the IKE authentication phase. | [
{
"name": "identifier",
"desc": "Name of certificate."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Configuring IKE Policies"
] |
local-chap | local-chap; | [edit access group-profile profile-name l2tp],
[edit access profile profile-name client client-name l2tp] | Configure the Junos OS so that the LNS ignores proxy authentication attribute-value pairs (AVPs) from
the L2TP access concentrator (LAC) and reauthenticates the PPP client using a Challenge Handshake
Authentication Protocol (CHAP) challenge. When you do this, the LNS directly authenticates the PPP
client.
NOTE: This st... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Layer 2 Tunneling Protocol (L2TP)"
] |
local-decision (PCRF Partition) | local-decision {
deny;
grant;
reinit-on-failure;
reinit-on-rar;
reinit-timeout seconds;
timeout seconds;
} | [edit access pcrf partition partition-name] | Configure a non-standard extension that allows the subscriber login to proceed even if the Policy and
Charging Rule Function (PCRF) is not available or if the PCRF does not respond within the
corresponding logout response timeout. This statement determines how long to wait before using the
local decision to log in.
Yo... | [
{
"name": "deny",
"desc": "(Optional) Prevent subscriber logins from occurring when the PCRF is not available or not responding."
},
{
"name": "grant",
"desc": "(Optional) Allow subscriber logins to occur when the PCRF is not available or not responding. Default: deny"
},
{
"name": "rei... | 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.
reinit-on-failure, reinit-on-rar, and reinit timeout options added in Junos OS Release 20.1R1. | [
"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... |
local-domain-id | local-domain-id id <domain-size domain-size>; | [edit chassis high-availability] | Local domain identifier for four-node multinode high availability setup. | [
{
"name": "id",
"desc": "Local domain identifier number. Range: 1 through 2"
},
{
"name": "domain-size",
"desc": "Local domain size. Default: 2 Range: 1 through 2"
}
] | [none specified] | Statement introduced in Junos OS Release 25.4R1. | [] |
local-dump (Flow Aggregation) | (local-dump | no-local-dump); | [edit forwarding-options sampling instance instance-name family (inet |inet6 |mpls) output flow-
server hostname],
[edit forwarding-options sampling family (inet |inet6 |mpls) output flow-server hostname] | Enable collection of cflowd records in a log file. | [
{
"name": "no-local-dump",
"desc": "Do not dump cflowd records to a log file before exporting."
},
{
"name": "local-dump",
"desc": "Dump cflowd records to a log file before exporting."
}
] | 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. | [
"Enabling Flow Aggregation",
"Debugging cflowd Flow Aggregation"
] |
local-endpoint | local-endpoint {
<initial-tnla-weight-factor initial-tnla-weight-factor>;
ip-address address;
<port port-number>;
} | [edit services agf amf] | Configure the local endpoint.options on the AGF. AGF uses the local endpoint values to initiate an initial
static TNLA with the AMF. | [
{
"name": "initial-tnla-weight-factor",
"desc": "(Optional) Specify the initial weight factor that AGF assigns to the static TNLA with the AMF. Default: 128 Range: 1 through 255"
},
{
"name": "ip-address address",
"desc": "Specify the IP address that the AGF uses as the local SCTP endpoint"
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS 22.3R1. | [] |
local-engine | local-engine {
user username {
authentication-md5 {
(authentication-key authentication-key | authentication-password authentication-
password);
}
authentication-none;
authentication-sha {
(authentication-key authentication-key | authentication-password authent... | [edit snmp v3 usm] | Configure local engine information for the user-based security model (USM).
The remaining statements are explained separately. See CLI Explorer. | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Creating SNMPv3 Users"
] |
local-gateway (IPSec) | local-gateway address <gw-interface interface-name.logical-unit-number>; | [edit services service-set service-set-name ipsec-vpn-options] | Define the local IPv4 or IPv6 address for the IPsec traffic.
NOTE: You cannot use a VRRP "virtual-address" on page 31924 for defining the local-
gateway address. | [
{
"name": "address",
"desc": "Local address. The remaining statement is explained separately."
}
] | 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. | [
"Configuring Service Rules"
] |
local-gateway (L2TP LNS) | local-gateway {
address address;
gateway-name gateway-name;
} | [edit services l2tp tunnel-group name] | Specify the IP address or name for the local (LNS) gateway for L2TP tunnel.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [
{
"name": "address",
"desc": "Local IP address; corresponds to the IP address that is used by LACs to identify the LNS. When"
}
] | 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 Local Gateway Address and PIC",
"Configuring L2TP Tunnel Groups",
"Configuring an L2TP Tunnel Group for LNS Sessions with Inline Services Interfaces"
] |
local-id (High Availability) | local-id id-number {
local-forwarding-ip loopback-address;
local-ip local-ip-address;
} | [edit chassis high-availability] | Configure the local node identifier for Multinode High Availability. | [
{
"name": "id",
"desc": "Local identifier number Range: 1 through 10"
},
{
"name": "local-ip",
"desc": "Local IPv4 address"
},
{
"name": "local-forwarding-ip",
"desc": "IP address used for local forwarding IP. This IP address must be associated to loopback interface only. You must c... | interface | Statement introduced in Junos OS Release 20.4R1. | [
"Multinode High Availability",
"Example: Configure Multinode High Availability in a Layer 3 Network"
] |
local-id | local-id (distinguished-name container container-string-values |wildcard wildcard-string-values
ipv4_addr ipv4-address | ipv6-addr ipv6-address | key-id identifier fqdn fqdn); | [edit services ipsec-vpn ike policy policy-name] | Specify local identifiers for IKE Phase 1 negotiation. This statement is optional. | [
{
"name": "ipv4_addr ipv4-address",
"desc": "IPv4 address identification value."
},
{
"name": "ipv6_addr ipv6-address",
"desc": "IPv6 address identification value."
},
{
"name": "key_id identifier",
"desc": "Key identification value."
},
{
"name": "fqdn fqdn",
"desc": "Fu... | 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.
ipv6_addr option added in Junos OS Release 7.6. | [
"Configuring Security Associations"
] |
local-identity | local-identity (distinguished-name | hostname identity-hostname | inet identity-ipv4 | inet6
identity-ipv6 | key-id | user-at-hostname identity-user); | [edit security ike gateway gateway-name] | Specify the local IKE identity to send in the exchange with the destination peer to establish
communication. If you do not configure a local-identity, the device uses the IPv4 or IPv6 address
corresponding to the local endpoint by default.
For Network Address Translation Traversal (NAT-T), both local identity and remot... | [
{
"name": "distinguished-name distinguished name",
"desc": "Specify a distinguished name as the identifier for the remote"
},
{
"name": "hostname hostname",
"desc": "Specify identity as a fully qualified domain name (FQDN)."
},
{
"name": "inet ip-address",
"desc": "Specify identity a... | 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. The inet6 option added in Junos OS Release 11.1. | [
"IPsec Overview"
] |
local-interface (IPv6) | local-interface interface-name; | [edit logical-systems logical-system-name protocols bgp group group-name neighbor ipv6-link-local-
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp
group group-name neighbor ipv6-link-local-address],
[edit protocols bgp group group-name neighbor ipv6-link-local-... | Specify the interface name of the EBGP peer that uses IPv6 link-local addresses. This peer is link-local in
scope.
TIP: Configure a local interface only if you need to use the IPv6 link-local addresses as
BGP endpoints for an IPv6 BGP session.
NOTE: The local interface option does not work if you have configured the al... | [
{
"name": "interface-name",
"desc": "Interface name of the EBGP IPv6 peer."
}
] | 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 Internal BGP Peering Sessions on Logical Systems",
"Example: Configuring Internal BGP Peer Sessions",
"Example: Configuring External BGP on Logical Systems with IPv6 Interfaces",
"Understanding Internal BGP Peering Sessions"
] |
local-ip-addr (ICCP) | local-ip-addr local-ip-address; | [edit protocols iccp],
[edit protocols iccp peer peer-IP-address] | Specify the local IP address of the interchassis link (ICL) interface that Inter-Chassis Control Protocol
(ICCP) uses to communicate to the peers that host a multichassis link aggregation group (MC-LAG). | [
{
"name": "local-ip-address",
"desc": "Default local IP address to be used by all peers."
}
] | 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. | [] |
local-ipv4-address | local-ipv4-address local ipv4 address; | [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 family a... | Specify the local IPv4 address of a device that is also configured with an IPv6 address in a dual-stack
environment. This enables BGP to advertise IPv4 unicast reachability with IPv4 next hop to remote IPv4
hosts over an IPv6 BGP session.
BGP advertises IPv4 unicast reachability with IPv4 next hop over an IPv6 BGP sess... | [] | 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. | [
"Advertising IPv4 Routes over BGP IPv6 Sessions Overview",
"Example: Advertising IPv4 Routes over IPv6 BGP Sessions"
] |
local-ipv6-address | local-ipv6-address local-ipv6-address; | [edit logical-systems name protocols pcep pce],
[edit protocols pcep pce] | Specify the IPv6 address of the local end of Path Computation Element Protocol (PCEP) session. | [] | 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. | [] |
local-key-pair | local-key-pair private-public-key-file; | [edit security ike policy ike-peer-address] | Specify private and public keys. | [
{
"name": "private-public-key-file",
"desc": "Specify the file from which to read the private and public key pair."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos 7.4. | [
"Configuring an IKE Policy for Digital Certificates for an ES PIC"
] |
local-log-tag (Next Gen Services) | local-log-tag tag-stamp; | [edit services service-set name syslog stream stream-name] | Each log message is stamped with this tag. Supported for sw, session, session-open, and session-close
categories only. | [] | system | Statement introduced in Junos OS Release 19.3R2. | [
"Understanding Next Gen Services CGNAT Global System Logging",
"Enabling Global System Logging for Next Gen Services",
"Configuring System Logging to One or More Remote Servers for Next Gen Services",
"Configuring Local System Logging for Next Gen Services"
] |
local-loopback | (local-loopback-enable | no-local-loopback); | [edit interfaces interface-name otn-options] | Specify whether local-loopback is enabled or disabled.
Default
If you omit the local-loopbback-enable statement, local-loopback is disabled. | [
{
"name": "local-loopback-enable",
"desc": "Enable local-loopback."
},
{
"name": "no-local-loopback",
"desc": "Disable local-loopback."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
local-minimum-links-threshold | local-minimum-links-threshold threshold-value | [edit interfaces aex aggregated-ether-options] | For an aggregated Ethernet interface (LAG bundle) with member links spanning multiple chassis
(member switches) in a Virtual Chassis or Virtual Chassis Fabric (VCF), set a threshold for the percentage
of member links local to any particular chassis that must be up for that chassis to continue to be active
in the aggreg... | [
{
"name": "threshold-value",
"desc": "Percentage of member links in an aggregated Ethernet bundle local to a chassis that"
},
{
"name": "Default: none",
"desc": "This option is not enabled by default."
}
] | 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-D40. | [] |
local-name | local-name name; | [edit interfaces interface-name ppp-options chap],
[edit interfaces interface-name ppp-options pap],
[edit interfaces interface-name unit logical-unit-number ppp-options chap],
[edit interfaces interface-name unit logical-unit-number ppp-options pap],
[edit logical-systems logical-system-name interfaces interface-name... | Specify the name of the interface used for CHAP or PAP authentication. Dynamic interfaces are
supported only for CHAP authentication.
For ATM2 IQ interfaces only, you can configure a CHAP local name on the logical interface unit if the
logical interface is configured with one of the following PPP over ATM encapsulation... | [
{
"name": "name",
"desc": "Name of the interface used as an identifier in CHAP challenge and response packets or PAP request and response packets. Default: When you do not include the local-name statement in the configuration, the interface sends the router’s system hostname in CHAP challenge and response ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for PAP added in Junos OS Release 8.3.
Support at the [edit dynamic-profiles profile-name interfaces "$junos-interface-ifd-name" unit “$junos-
interface-unit” ppp-options] hierarchy level introduced in Junos OS Release 14.2. | [
"Configuring the PPP Challenge Handshake Authentication Protocol",
"Configuring the PPP Password Authentication Protocol On a Physical Interface"
] |
local-password | local-password password; | [edit interfaces interface-name ppp-options pap],
[edit interfaces interface-name unit logical-unit-number ppp-options pap],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number ppp-
options pap] | Configure the host password for sending PAP requests. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Configuring the PPP Password Authentication Protocol"
] |
local-port-range | local-port-range {
low low-value;
high high-value;
} | [edit unified-edge pcef flow-descriptions flow-identifier],
[edit services pcef flow-descriptions flow-identifier] | Specify the port range to identify the subscriber traffic that you want the service data flow (SDF) filter
to detect.
NOTE: You can specify either local-port-range or a list of ports with local-ports, but not
both.
If you are using Junos OS Subscriber Aware, specify the port range at the [edit unified-edge pcef flow-
d... | [
{
"name": "low-value",
"desc": "Lower boundary for the port range. Range: 1 through 65,535"
},
{
"name": "high-value",
"desc": "Upper boundary for the port range. Range: 1 through 65,535"
}
] | 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 flow-descriptions flow-identifier] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series. | [
"Configuring Service Data Flow Filters",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Understanding Application-Aware Policy Control for Subscriber Management"
] |
local-ports | local-ports [number]; | [edit unified-edge pcef flow-description flow-identifier],
[edit services pcef flow-description flow-identifier] | Specify a port number or list of port numbers to identify the subscriber traffic that you want the service
data flow (SDF) filter to detect.
NOTE: You can specify either a list of ports or a port range, but not both.
If you are using Junos OS Subscriber Aware, specify the port numbers at the [edit unified-edge pcef flo... | [
{
"name": "number",
"desc": "Number of a port or list of port numbers. You can specify a maximum of three port numbers (separated by a space) in a list. Range: 1 through 65,535"
}
] | 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 flow-description flow-identifier] hierarchy level introduced for Junos OS
Broadband Subscriber Management in Junos OS Release 17.2 on MX Series. | [
"Configuring Service Data Flow Filters",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment",
"Understanding Application-Aware Policy Control for Subscriber Management"
] |
local-preference | local-preference local-preference; | [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... | Modify the value of the LOCAL_PREF path attribute, which is a metric used by IBGP sessions to indicate the
degree of preference for an external route. The route with the highest local preference value is
preferred.
The LOCAL_PREF path attribute always is advertised to internal BGP peers and to neighboring
confederation... | [
{
"name": "local-preference",
"desc": "Preference to assign to routes that are advertised to the group or peer."
}
] | 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 Local Preference Value for BGP Routes",
"Understanding Internal BGP Peering Sessions"
] |
local-priority | local-priority local-priority; | For MX Series:
[edit protocols ptp]
[edit protocols ptp master interface interface-name multicast-mode]
[edit protocols ptp master interface interface-name unicast-mode]
[edit protocols ptp slave interface interface-name multicast-mode]
[edit protocols ptp slave interface interface-name unicast-mode]
[edit protocols pt... | Priority assigned to the local clock.
NOTE: The stateful statement is not supported on QFX Series switches that support
PTP
Configure a clock’s local priority to be used as a tie-breaker in the dataset comparison algorithm, in the
event that all other previous attributes of the datasets being compared are equal. The da... | [
{
"name": "local-priority value",
"desc": "The priority value of the clock. Range: 1 through 255 Default: 128"
}
] | routing | Statement introduced in Junos OS Release 20.4 | [] |
local-replication | local-replication | [edit forwarding-options satellite] | Enables multicast replication on all the satellite devices that are connected to the aggregation device.
You cannot selectively enable local replication for specific satellite devices, bridge domains, or route
prefixes. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Egress (Local) Replication on a Junos Fusion"
] |
local-server-group (DHCP Relay Agent Option) | local-server-group local-server-group; | [edit forwarding-options dhcp-relay relay-option (default-action | equals | starts-with)],
[edit forwarding-options dhcp-relay group group-name relay-option (default-action | equals | starts-
with)],
[edit logical-systems logical-system-name forwarding-options dhcp-relay ...],
[edit logical-systems logical-system-name ... | Forward DHCP client packets to the specified group of DHCP local servers when you use the DHCP
relay selective processing feature. You can configure the forwarding operation globally or for a group of
interfaces.
The local-server-group option is not supported for DHCPv6 relay agent. | [
{
"name": "local-server-group",
"desc": "Name of DHCP local server group."
}
] | 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. | [
"Using DHCP Option Information to Selectively Process DHCP Client Traffic"
] |
local-switching (Layer 2 Circuits) | local-switching {
interface interface-name {
description text;
encapsulation-type;
end-interface {
interface interface-name;
no-revert;
protect-interface interface-name;
}
ignore-encapsulation-mismatch;
ignore-mtu-mismatch;
... | [edit logical-systems logical-system-name protocols l2circuit],
[edit protocols l2circuit] | Configure a local switching interface. A local switching interface allows you to terminate a virtual circuit
on the local router.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Local Interface Switching in Layer 2 Circuits"
] |
local-switching (VPLS) | local-switching; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
mesh-group mesh-group-name],
[edit routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name] | Allows you to terminate multiple Layer 2 circuit pseudowires at a single VPLS mesh group. Note that
when using vpls-id-list, you can enable local-switching to allow local switching of traffic (including BUM
traffic) between multiple pseudo wires. Enabling local-switching also eliminates the need to have a
dedicated mes... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Configuring Switching Between Pseudowires Using VPLS Mesh Groups"
] |
local-traffic-selector | local-traffic-selector {
(ipv4-prefix ipv4-prefix | ipv6-prefix ipv6-prefix);
port port;
protocol protocol;
} | [edit security host-vpn connections connection-name children child-name] | Configure the local IPsec traffic to be protected by the child security association. A traffic selector is a
traffic filter that defines and identifies the traffic flow permitted between two systems (a specified pair
of local and remote addresses) that have IPsec protection. | [
{
"name": "(ipv4-prefix ipv4-prefix | ipv6-prefix",
"desc": ""
},
{
"name": "ipv6-prefix)",
"desc": "Specify traffic to be protected by the child security association using either IPv4 or IPv6 with a prefix. The prefix allows for specifying more general traffic."
},
{
"name": "port port"... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 18.3R1. | [] |
locality-bias (MX Series Virtual Chassis) | locality-bias; | [edit virtual-chassis] | Configure unicast transit traffic for equal-cost multipath (ECMP) groups and aggregated Ethernet
bundles to egress links in the same (local) member router in an MX Series Virtual Chassis rather than to
egress links in the remote member router, provided that the local member router has an equal or larger
number of avail... | [] | 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 Locality Bias for a Virtual Chassis",
"Locality Bias in a Virtual Chassis",
"Guidelines for Configuring Locality Bias in a Virtual Chassis"
] |
localized-fib | localized-fib {
fpc-slot fpc-slot-number;
} | [edit routing-instances instance-name routing-options] | Localize the VRF routing instance routes to a specific FPC of CE-facing physical interfaces, or specify an
FPC slot number if the CE-facing interfaces are logical interfaces like AE or RSQL or IRB. | [
{
"name": "fpc-slot fpc-slot-number",
"desc": "Specify the FPC slot number to localize the VRF routing instance for logical interfaces like AE or RSQL or IRB."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Understanding VRF Localization in Layer 3 VPNs",
"Example: Improving Scalability Using VRF Localization for Layer 3 VPNs"
] |
location (DHCP Relay Agent) | location name; | [edit forwarding-options dhcp-relay relay-option-82 vendor-specific],
[edit forwarding-options dhcp-relay group group-name relay-option-82 vendor-specific] | Supports the addition of a vendor-specific location in the option 82, suboption 9 field of DHCPv4
control messages on server-facing interfaces. The location should be specified as interface, vlan ID, and
if applicable, svlan ID. For example, <ifd-name>:<vlan> (ae0:100) or <ifd-name>:<svlan> -<vlan>
(ae0:100-10).
Junos... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Junos OS Release 16.2. | [] |
location (DHCP Snooping Database) | location local_pathname | remote_URL; | [edit ethernet-switching-options secure-access-port dhcp-snooping-file] | Specify either a local pathname or a remote URL as the location in which to store the DHCP snooping
database. | [
{
"name": "local_pathname | remote_URL",
"desc": "Location for storing the DHCP snooping database."
},
{
"name": "local_pathname",
"desc": "Use /path to store the database on a local switch."
},
{
"name": "remote_URL",
"desc": "Use ftp://ip-address or ftp:// hostname/path to store th... | 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. | [] |
location (DHCP Snooping Database) | location (local_pathname | remote_url);
timeout seconds;
write-interval seconds;
} | [edit ethernet-switching-options secure-access-port dhcp-snooping-file],
[edit ethernet-switching-options secure-access-port dhcpv6-snooping-file] | Configure IP-MAC address bindings to persist through switch reboots by specifying a location in which
to store the DHCP snooping database. When specifying the location for the DHCP snooping database,
you must also specify how frequently the switch writes (write-interval) the database entries into the
DHCP snooping data... | [
{
"name": "local_pathname | remote_url",
"desc": ""
},
{
"name": "local_pathname",
"desc": "Use /path to store the database file on the local switch."
},
{
"name": "remote_url",
"desc": "Use ftp://ip-address or ftp:// hostname/path to store the database on a remote FTP site."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
Support at the [edit ethernet-switching-options secure-access-port dhcpv6-snooping-file] hierarchy level
introduced in Junos OS Release 14.1X53-D10 for EX Series switches. | [
"Configuring Persistent Bindings in the DHCP or DHCPv6 (non-ELS)",
"Understanding DHCP Snooping (non-ELS)"
] |
location (DHCPv6 Relay Agent) | location name; | [edit forwarding-options dhcp-relay dhcpv6 relay-option-vendor-specific],
[edit forwarding-options dhcp-relay group group-name dhcpv6 relay-option-vendor-specific] | Supports the addition of a vendor-specific location in the vendor-specific option (17) of DHCPv6 control
messages on server-facing interfaces. The location should be specified as interface, vlan ID, and if
applicable, svlan ID. For example, <ifd-name>:<vlan> (ae0:100) or <ifd-name>:<svlan> -<vlan>
(ae0:100-10).
Junos a... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Junos OS Release 16.2. | [] |
location (LLDP-MED) | location {
civic-based {
ca-type type {
ca-value value;
}
country-code country-code;
what what;
}
co-ordinate {
lattitude latitude;
longitude longitude;
}
elin elin;
} | [edit protocols lldp-med interface (all | interface-name)] | For Link Layer Discovery Protocol–Media Endpoint Discovery (LLDP-MED), configure the location
information. Location information is advertised from the switch to the MED. This information is used
during emergency calls to identify the location of the MED.
The remaining statements are explained separately. See CLI Explor... | [
{
"name": "co-ordinate",
"desc": "Geographical coordinates for the location of the MED. Values: Specify these values:"
},
{
"name": "lattitude latitude",
"desc": "Latitude value for the location."
},
{
"name": "longitude longitude",
"desc": "Longitude value for the location."
},
... | 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)"
] |
location (SNMP) | location location; | [edit snmp] | Define the value of the MIB II sysLocation object, which is the physical location of the managed system. | [
{
"name": "location",
"desc": "Location of the local system. You must enclose the name within quotation marks (\" \")."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the System Location for a Device Running Junos OS"
] |
location (System) | location {
altitude feet;
building name;
country-code code;
floor number;
hcoord horizontal-coordinate;
lata transport-area;
latitude degrees;
longitude degrees;
npa-nxx number;
postal-code postal-code;
rack number;
vcoord vertical-coordinate;
} | [edit system] | Configure the system location in various formats. | [
{
"name": "altitude feet",
"desc": "Number of feet above sea level."
},
{
"name": "building name",
"desc": "Name of the building. The name of the building can be 1 to 28 characters in length. If the string contains spaces, enclose it in quotation marks (\" \")."
},
{
"name": "country-cod... | 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. | [
"System Settings"
] |
location (Virtual Chassis) | location location; | [edit virtual-chassis member member-id] | Set a description of the location of the Virtual Chassis or VCF member switch or external Routing
Engine.
The Location field is visible to users who enter the show virtual-chassis status detail command.
Setting this description has no effect on the operation of the member device. | [
{
"name": "location",
"desc": "Location of the current member switch or external Routing Engine. The location can be any"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Autoprovisioning a Virtual Chassis Fabric",
"Preprovisioning a Virtual Chassis Fabric",
"Configuring an EX4650 or a QFX Series Virtual Chassis",
"Configuring an EX2300, EX3400, or EX4300 Virtual Chassis",
"Configuring EX4600 Switches in a Mixed or Non-Mixed Virtual Chassis"
] |
locator | locator name {
static-sid;
no-reduced-srh;
} | [edit logical-systems name protocols source-packet-routing source-routing-path name micro-srv6-
binding-sid],
[edit logical-systems name protocols source-packet-routing source-routing-path name srv6-binding-
sid],
[edit protocols source-packet-routing source-routing-path name micro-srv6-binding-sid],
[edit protocols so... | Configure the SRv6 locator from where the operating system allocates binding SIDs. | [
{
"name": "name",
"desc": "Specify the name of the SRv6 binding SID locator."
},
{
"name": "static-sid",
"desc": "Specify static SRv6 binding SID function."
},
{
"name": "no-reduced-srh",
"desc": "Configure SRv6 binding SID in non-reduced mode"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.2R1. | [
"No Link Title"
] |
locator | locator name {
anycast
end-sid sid | dynamic-end-sid
flavor {
psp;
usp;
usd;
}
algorithm algorithm
}
micro-sid
} | [edit logical-systems name routing-instances name routing-options source-packet-routing srv6],
[edit logical-systems name routing-options source-packet-routing srv6],
[edit logical-systems name tenants name routing-instances name routing-options source-packet-
routing srv6],
[edit routing-instances name routing-options... | Configure the locator for an SRv6 node in an IPv6 domain to indicate the SRv6 capability of the router.
A Segment Identifier (SID) is a 128-bit IPv6 address that represents a specific segment in a segment
routing domain. A SID consists of two parts, the first part is called the locator and consists of the most
signific... | [
{
"name": "name",
"desc": "Specify the locator entry name."
},
{
"name": "anycast",
"desc": "Set A flag in the prefix-attribute sub-TLV through a policy to enable anycast locators. By default, the A flag is preserved while leaking IS-IS routes."
},
{
"name": "end-sid",
"desc": "Confi... | routing | Statement introduced in Junos OS Release 20.3R1.
micro-sid option introduced in Junos OS Release 23.4R1. | [
"How to Enable SRv6 Network Programming in IS-IS Networks",
"Example: Configuring SRv6 Network Programming in IS-IS Networks",
"Configuring Flexible Algorithm for Segment Routing"
] |
lockout | request protection-group ethernet-aps lockout md <md> ma <ma> | [edit protocols protection-group ethernet-aps] | Configure a lockout of the protection path, forcing the use of the working path and locking out the
protect path regardless of anything else. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"Ethernet Automatic Protection Switching Overview"
] | |
lockout-timeout (L2TP Destination Lockout) | lockout-timeout seconds; | [edit services l2tp destination lockout-result-code lockout-result-code-name lockout-error-code
lockout-error-code- name] | Set the duration of the timeout period for which all future destinations are locked out, meaning that
they are not considered for selection when a new tunnel is created. Destinations are locked out when
L2TP cannot connect to the destination during the tunnel selection process. This statement does not
affect destinatio... | [
{
"name": "seconds",
"desc": "Length of the period during which the destination is locked out. Range: 60 through 3600 seconds Default: 300 seconds"
}
] | 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. | [
"L2TP Tunnel Switching For Multiple-Domain Networks",
"L2TP LNS Inline Service Interfaces"
] |
log (aacl) | log event-type | [edit services aacl rule rule-name No Link Title term-name No Link Title ] | Enable AACL logging of flows for known or unknown applications. | [
{
"name": "event-type",
"desc": "Enable logging of the specified event-type:"
},
{
"name": "session-start",
"desc": ""
},
{
"name": "session-end",
"desc": ""
},
{
"name": "session-start-end-no-stats",
"desc": ""
},
{
"name": "session-start-interim-end",
"desc"... | 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. | [] |
log (Logical Systems and Tenant Systems) | log {
disable;
facility-override (authorization | daemon | ftp | kernel | local0 | local1 | local2
| local3 | local4 | local5 | local6 | local7 | user);
mode (event | stream);
format (binary | sd-syslog | syslog);
source-address;
source-interface;... | [edit logical-systems name security]
[edit tenants name security] | Configure security log for logical systems and tenant systems. Set the mode of logging (event for
traditional system logging or stream for streaming security logs through a revenue port to a server). You
can also specify all the other parameters for security logging. | [
{
"name": "disable",
"desc": "Disable the security logging for the device."
},
{
"name": "facility-override",
"desc": "Alternate facility for logging to remote host. Values:"
},
{
"name": "authorization",
"desc": "Authorization system"
},
{
"name": "daemon",
"desc": "Var... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1.
Statement introduced in Junos OS Release 18.3R1 for tenant systems.
The routing-instance option introduced in Junos OS Release 18.3R1 for tenant systems. | [
"Troubleshooting Logical Systems"
] |
log (Security GTP) | log {
forwarded (basic | detail);
gtp-u name;
prohibited (basic | detail);
rate-limited (basic | detail);
event (basic | detail);
} | [edit security gtp profile profile-name] | Use the console or syslog to view GPRS tunneling protocol version 2 (GTPv2) traffic logs. You can
configure the device to log GTPv2 packets based on their status. You can use the log configuration
statement to enable GTPv2 logging on the device. By default, all logs are disabled on the device.
From Junos OS Release 20.... | [
{
"name": "forwarded",
"desc": "A packet that the security device transmitted because it was valid."
},
{
"name": "GTP-U",
"desc": "A packet that the security devices have for gtp-u."
},
{
"name": "prohibited",
"desc": "A packet that the security device dropped because it was invalid... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. Support. The state-invalid (basic | detail) option is
replaced by event (basic | detail) in Junos OS Release 20.4R1. | [
"Understanding GTPv2 Traffic Logging",
"Example: Enabling GTPv2 Traffic Logging"
] |
log (Security IDP Sensor Configuration) | log {
cache-size size;
suppression {
disable;
(include-destination-address | no-include-destination-address);
max-logs-operate value;
max-time-report value;
start-log value;
}
} | [edit security idp sensor-configuration] | Configure IDP security policy logs. | [
{
"name": "cache-size",
"desc": "Specify the size in bytes for each user’s log cache."
},
{
"name": "Syntax: size",
"desc": "Cache size."
}
] | 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 (Security Policies) | log (session-close | session-init); | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then] | Log traffic information for a specific policy. Traffic information is logged when a session begins (session-
init) or closes (session-close).
NOTE: You must configure security policy for the session using the set security policies
from-zone zone-name to-zone zone-name policy policy-name then log session-close command t... | [
{
"name": "session-close",
"desc": "Start logging traffic when the session ends."
},
{
"name": "session-init",
"desc": "Start logging traffic when the session begins."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Security Policies Overview",
"Understanding On-Box Logging and Reporting",
"Example: Configuring Application Tracking"
] |
log (Security SCTP) | log name; | [edit security sctp] | Use the console or syslog to view Stream Control Transmission Protocol (SCTP) logs.
From Junos OS Release 20.4R1 onwards, the [edit security gprs sctp] hierarchy level is replaced by [edit
security sctp]. | [
{
"name": "association",
"desc": "To log association events."
},
{
"name": "configuration",
"desc": "To log the CLI configuration."
},
{
"name": "control-message-all",
"desc": "To log both dropped and passed control messages."
},
{
"name": "control-message-drop",
"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. The options association, control-message-all, control-
message-drop, and data-message-drop added in Junos OS Release 12.1X45-D10. | [
"Understanding Stream Control Transmission Protocol",
"SCTP Packet Structure Overview"
] |
log (Security) | log {
(source-address source-address | source-interface source-interface);
cache {
exclude name {
destination-address destination-address;
destination-port destination-port;
event-id event-id;
failure;
interface-name interface-name;
... | [edit security]
[edit logical-systems name security]
[edit tenants tenant-name security] | 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": "cache",
"desc": "Cache security log events in the audit log buffer."
},
{
"name": "disable",
"desc": "Disable the security logging for the device."
},
{
"name": "escape",
"desc": "Escapes the stream log forwarding to avoid parsing errors. Stream mode supports escape in sd-... | 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.
The [edit logical-systems name security] and [edit tenants tenant-name security] hierarchy levels
introduced in Junos OS Release 19.1R1.
escape option added in Junos OS Release 20.2R1.
root-streaming option added in Junos OS Release 20.3R1.
protobuf option is introduced in ... | [] |
log (Services) | log {
all;
errors;
info;
sessions-allowed;
sessions-dropped;
sessions-ignored;
sessions-whitelisted;
warning;
} | [edit services ssl proxy profile profile-name actions] | Specify the logging actions. When configuring SSL proxy, you can choose to set the option to receive
some or all of the logs.
SSL proxy logs contain the logical system name, SSL proxy allowlists, policy information, SSL proxy
information, and other information that helps you troubleshoot when there is an error.
You can... | [
{
"name": "all",
"desc": "Log all events."
},
{
"name": "errors",
"desc": "Log all error events."
},
{
"name": "info",
"desc": "Log all information events."
},
{
"name": "sessions-allowed",
"desc": "Log SSL session allowed events after an error."
},
{
"name": "ses... | 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"
] |
log (Spanning Trees) | log; | [edit protocols mstp interface (all | interface-name) bpdu-timeout-action],
[edit protocols rstp interface (all | interface-name) bpdu-timeout-action],
[edit protocols stp interface (all | interface-name) bpdu-timeout-action],
[edit protocols vstp vlan vlan-id interface (all | interface-name) bpdu-timeout-action] | For interfaces configured for loop protection, configure the software to generate a message to be sent
to the system log file /var/log/messages to record the loop-protection event. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
Statement updated in Junos OS Release 9.4 for EX Series switches to add VSTP support. | [
"Example: Configuring Network Regions for VLANs with MSTP on Switches",
"Example: Faster Convergence and Improved Network Stability with RSTP on EX Series Switches",
"Example: Configuring Loop Protection to Prevent Interfaces from Transitioning from Blocking to",
"Forwarding in a Spanning Tree on non-ELS EX S... |
log | log {
session {
client;
all;
dhcpv6 {
client;
server;
relay;
dynamic-server;
all;
}
server;
relay;
}
} | [edit system processes dhcp-service] | Enable DHCP session log on the device. Session logs include the information on the session creation,
deletion and renew events. You can use the session logs for monitoring and troubleshooting purposes.
DHCP logs are written to system syslog that you define using the following command:
set system syslog ( file filename ... | [
{
"name": "session",
"desc": "Logs of the DHCP sessions."
},
{
"name": "client",
"desc": "Log sessions of the DHCP client."
},
{
"name": "all",
"desc": "Log sessions of the DHCP client, server and relay."
},
{
"name": "dhcpv6",
"desc": "Log sessions of the DHCPv6."
},
... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1R1. | [] |
log-and-generate-ais | log-and-generate-ais {
interval (1m | 1s);
level level;
priority level;
} | [edit protocols oam ethernet connectivity-fault-management action-profile action-profile-name
action] | Configure the action be taken when an AIS alarm is detected. The action includes generating and logging
the AIS statistics along with the interval between AIS messages, the server maintenance domain level,
and the priority of the AIS message. | [] | 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"
] |
log-attacks (rulebase-exempt) | 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 exempt rule logging in the IDP system, which can be used to monitor and analyze traffic patterns,
detect potential security threats, and troubleshoot network issues. | [
{
"name": "alert",
"desc": "Set alert flag in attack log"
}
] | 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. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.