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 |
|---|---|---|---|---|---|---|---|
alarm-without-drop (IDS Screen Next Gen Services) | alarm-without-drop; | [edit services screen ids-option screen-name]
[edit logical-systems name security screen ids-option],
[edit logical-systems name tenants name security screen ids-option],
[edit security screen ids-option],
[edit tenants name security screen ids-option] | Use the ids-option to prevent DDoS attack from interface. Configure the IDS screen to log an alarm for
an offending packet, but not drop the packet. The screen skips the rest of the screen checks. The packet
is not counted as a dropped packet.
IDS screen logs an alarm when packets exceed the session limit. To prevent p... | [
{
"name": "alarm-without-drop",
"desc": "Do not drop packet, only generate alarm"
}
] | 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. | [
"No Link Title"
] |
alarm-without-drop (Security) | alarm-without-drop; | [edit security screen ids-option screen-name] | Direct the SRX device to generate an alarm when detecting an attack but not block the attack. Use this
statement to allow an attack to enter a segment of your network that you have previously prepared to
receive it (for example, a honeynet, which is a decoy network with extensive monitoring capabilities). | [] | 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"
] |
alarm-without-drop | alarm-without-drop; | [edit logical-systems name security screen ids-option],
[edit logical-systems name tenants name security screen ids-option],
[edit services screen ids-option],
[edit tenants name security screen ids-option] | Do not drop packet, only generate alarm | [] | [none specified]
Release Information | [] | |
alarms (Security) | alarms {
audible {
continuous;
}
potential-violation {
authentication failures;
cryptographic-self-test;
decryption-failures {
threshold value;
}
encryption-failures {
threshold value;
}
idp;
ike-phase1-failures... | [edit security] | Configures security alarms. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Security Policies Overview"
] |
alarms (Video Monitoring) | alarms {
delay-factor {
no-syslog-generation;
generate-snmp-traps;
storm-control {
count number;
interval number;
}
alarm-mode {
mdi-records-count number;
average;
}
}
media-rate-variation {
no-syslog-gen... | [edit services video-monitoring] | Configure the alarm to monitor and report active alarms. SNMP is used to monitor alarms raised by the
inline video monitoring feature. The alarms are monitored in the network management system either to
troubleshoot the problem or to diagnose degradation in video quality.
The remaining statements are explained separate... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding Inline Video Monitoring on MX Series Routers"
] |
alarms | alarms; | [edit interfaces interface-name optics-options] | For 10-Gigabit Ethernet DPCs, configure the DPC to drop the interface link when the receive power falls
below the alarm threshold. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in JUNOS Release 10.1. | [
"Ethernet DWDM Interface Wavelength Overview"
] |
alg (Applications) | alg (dns |ftp | ftp-data | gprs-gtp-c | gprs-gtp-u | gprs-gtp-v0 | gprs-sctp | http | https |
realaudio | rsh | rtsp | sccp | sip | smtp | sqlnet-v2 | ssh | sun-rpc | talk | telnet | tftp |
twamp); | [edit applications application application-name term term-name] | Define individual Application Layer Gateway (ALG).
The twamp application protocol is introduced Junos OS Release 18.2R1. | [
{
"name": "dns",
"desc": "Domain Name Service"
},
{
"name": "ftp",
"desc": "File Transfer Protocol"
},
{
"name": "ftp-data",
"desc": "Trace FTP Data Session"
},
{
"name": "gprs-gtp-c",
"desc": "GPRS Tunneling Control Plane"
},
{
"name": "gprs-gtp-u",
"desc": "... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
alg | alg {
alg-manager {
traceoptions {
flag {
all <extensive>;
}
}
}
alg-support-lib {
traceoptions {
flag {
all <extensive>;
}
}
}
dns {
disable;
doctoring (none | sanity-chec... | [edit security],
[edit tenants tenant-name security],
[edit services],
[edit logical-systems 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": "bytes",
"desc": "Maximum length in bytes of a single DNS message."
},
{
"name": "c-timeout value-in-minutes",
"desc": "Specifies the timeout interval for Session Initiation Protocol (SIP) transactions"
},
{
"name": "endpoint-registration-timeout value-in-seconds",
"desc": ... | 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.
Statement supported in Junos OS Release 18.3R1 for tenant systems.
maximum-message-lengthbytes option introduced in Junos OS Release 10.1.
twamp option introduced in Junos OS Release 18.2R1. | [] |
alg-manager | alg-manager {
clear-dont-frag-bit {
traceoptions {
flag {
all {
extensive
}
}
}
}
} | [edit security alg] | 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": "clear-dont-frag-bit",
"desc": "Starting in Junos OS Release 15.1X49-D200, we’ve introduced the clear-dont-frag-bit option to disable the do not fragment flag from the packet IP header, which allows to split the packet after the NAT translation."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | [] | |
alg-support-lib | alg-support-lib {
traceoptions {
flag {
all {
extensive
}
}
}
} | [edit logical-systems name security alg],
[edit logical-systems name tenants name security alg],
[edit security alg],
[edit services alg],
[edit tenants name security alg] | 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... | [] | 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. | [] |
algorithm (Junos FIPS) | algorithm 3des-cbc; | [edit security ipsec internal security-association manual direction encryption] | Select the encryption algorithm for the internal Routing-Engine–to–Routing-Engine IPsec security
association (SA) configuration. | [] | Crypto Officer—To add and view this statement in the configuration. | Statement introduced before Junos OS Release 7.4. | [] |
algorithm | algorithm algorithm-name; | [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 the algorithm to use for BFD authentication. | [
{
"name": "algorithm-name",
"desc": "Name of algorithm to use for BFD authentication:"
},
{
"name": "simple-password",
"desc": "Plain-text password. One to 16 bytes of plain text. One or more passwords can be"
},
{
"name": "keyed-md5",
"desc": "Keyed Message Digest 5 hash algorithm f... | 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. | [
"Understanding Bidirectional Forwarding Detection Authentication for PIM",
"Configuring BFD Authentication for PIM"
] |
alias (Interfaces) | alias alias-name; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Configure a textual description of a physical interface or the logical unit of an interface to be the alias of
an interface name. The alias name can be a single line of text. If the text contains spaces, enclose it in
quotation marks. If you configure an alias name, the alias name is displayed instead of the interface
... | [
{
"name": "alias-name",
"desc": "Text to denote an easily identifiable, meaningful alias name for the interface. If the text includes spaces, enclose the entire text in quotation marks."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Example: Adding an Interface Alias Name",
"Junos OS Network Interfaces Library for Routing Devices"
] |
alias (Junos Fusion Satellite Device Clustering) | alias alias; | [edit chassis satellite-management cluster cluster-name fpc slot-id ] | Configure an alias to label a satellite device in a satellite device cluster.
Satellite device alias configuration is optional, but recommended. In a Junos Fusion, satellite device
aliases assist with administration tasks, such as monitoring satellite devices using show command
outputs, as well as with some configurati... | [
{
"name": "alias",
"desc": "The user-defined text name of the alias."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1. | [
"Configuring or Expanding an Junos Fusion Enterprise",
"Configuring Junos Fusion Provider Edge"
] |
alias (Junos Fusion) | alias alias; | [edit chassis satellite-management fpc slot-id] | Configure an alias to label a satellite device.
Satellite device alias configuration is optional, but recommended. In a Junos Fusion, satellite device
aliases assist with administration tasks, such as monitoring satellite devices using show command
outputs, as well as with some configuration tasks that provide an optio... | [
{
"name": "alias",
"desc": "The user-defined text name of the alias."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring or Expanding a Junos Fusion Enterprise",
"Configuring Junos Fusion Provider Edge"
] |
aliases (Virtual Chassis) | aliases {
serial-number serial-number {
alias-name alias-name;
}
} | [edit virtual-chassis] | Optionally create an alias for a member switch in a Virtual Chassis or Virtual Chassis Fabric (VCF). You
can more clearly identify the member switches in your Virtual Chassis or VCF by assigning text labels
(alias names) to them, associating the alias name with member switch serial numbers. Aliases are for
administrati... | [
{
"name": "serial-number",
"desc": "The permanent serial number for the member switch in the Virtual Chassis or VCF that you want to label with an alias name. Serial number values are case-sensitive. The show virtual-chassis command displays the serial number for all members in the Virtual Chassis or VCF in... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10. | [
"Autoprovisioning a Virtual Chassis Fabric",
"Preprovisioning a Virtual Chassis Fabric",
"Configuring an EX4650 or a QFX Series Virtual Chassis",
"Understanding Virtual Chassis Fabric Components",
"Understanding Virtual Chassis Components"
] |
aliases | aliases {
director-device director-device-name {
assigned-director-device-name;
}
interconnect-device interconnect-device-name {
assigned-interconnect-device-name;
}
node-device node-device-name {
assigned-node-device-name;
} | [edit fabric] | (QFabric systems only) Specify the mapping of user defined names to QFabric system components. You
can reassign names for Director devices, Interconnect devices, and Node devices.
The remaining statements are explained separately. See CLI Explorer.
NOTE: The following rules apply to QFabric component alias naming:
•
Al... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.3.
Options director-group and interconnect-device introduced in Junos OS Release 12.2 for the QFX Series. | [
"Configuring Aliases for the QFabric System",
"Understanding Node Devices"
] |
all-defects | all-defects; | [edit protocols oam ethernet connectivity-fault-management action-profile action-profile-name
event ais-trigger-condition] | Configure the defect condition that raises an alarm indication signal when any or all possible defects
occur in the maintenance domain level. | [] | 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"
] |
all-regions | all-regions {
incoming;
ingress-replication {
create-new-ucast-tunnel;
label-switched-path {
label-switched-path-template (Multicast) {
(default-template | lsp-template-name);
}
}
}
ldp-p2mp;
rsvp-te {
label-switched-path-templ... | [edit protocols mvpn inter-region-template template template-name] | Specify the tunnel support for all regions that are not defined in the more specific regions. The all-
regions statement supports different tunnel types such as incoming, ingress replication, ldp-p2mp, or
rsvp-te. The incoming tunnel indicates that the tunnel type across the area boundary router (ABR) is not
changed. | [
{
"name": "incoming",
"desc": "Specify the tunnel type to be the same across the ABR."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Segmented Inter-Area Point-to-Multipoint Label-Switched Paths Overview",
"Example: Configuring Segmented Inter-Area P2MP LSP",
"Configuring Segmented Inter-Area P2MP LSP"
] |
all-tcp | all-tcp mss value; | [edit security flow tcp-mss] | Set the TCP maximum segment size (MSS) value to enable MSS override for all TCP packets in network
traffic. | [
{
"name": "mss value",
"desc": "TCP MSS value."
}
] | 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"
] |
allow | allow (all | [ network/mask-length ]); | [edit logical-systems name protocols bgp group name],
[edit logical-systems name routing-instances name protocols bgp group name],
[edit protocols bgp group name],
[edit routing-instances name protocols bgp group name],
[edit logical-systems name protocols bgp group name dynamic-neighbor dyn-name],
[edit logical-system... | Implicitly configure BGP peers, allowing peer connections from any of the specified networks or hosts.
To configure multiple BGP peers, configure one or more networks and hosts within a single allow
statement or include multiple allow statements.
You can configure authentication for all implicitly configured peers at [... | [
{
"name": "all",
"desc": "Allow all addresses, which is equivalent to 0.0.0.0/0 (or ::/0)."
},
{
"name": "network/mask-length",
"desc": "IPv6 or IPv4 network number of a single address or a range of allowable"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced under [edit protocols bgp group group-name dynamic-neighbor dyn-name] hierarchy in
Junos OS Release 19.1. | [] |
allow-6pe-traceroute | allow-6pe-traceroute; | [edit system] | Allow IPv4-mapped IPv6 source addresses in an ICMPv6 echo request TTL expired packets.
In a dual-stack IPv6 network connected over an IPv4 MPLS network, the P routers in the IPv4 MPLS
backbone do not have an IPv6 family. Consequently, the transit P routers are not shown in the output
when you do an IPv6 traceroute. To ... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | [
"Configure IPv6 Features"
] | |
allow-active-leasequery (DHCP Local Server) | allow-active-leasequery {
idle-timeout seconds;
timeout seconds;
} | [edit system services dhcp-local-server],
[edit system services dhcp-local-server dhcpv6],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services],
[edit logical-systems logical-system-name system services],
[edit routing-instances routing-instance-name system services] | Enable a DHCPv4 or DHCPv6 local server to listen for, process, and respond to active leasequery
requests received on TCP connections on TCP port 67 for DHCPv4 and on TCP port 547 for DHCPv6.
NOTE: Because active leasequery is an extension of bulk leasequery, you must also
configure bulk leasequery before you configure ... | [
{
"name": "idle-timeout",
"desc": ""
},
{
"name": "seconds",
"desc": "(Optional) Specify the number of seconds that pass with no activity before the TCP connection is terminated and restarted. Range: 10 through 3600 Default: 60"
},
{
"name": "timeout",
"desc": ""
},
{
"name... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1R1. | [
"DHCP Leasequery Methods"
] |
allow-bulk-leasequery (DHCP Local Server) | allow-bulk-leasequery {
max-connections number-of-connections;
max-empty-replies number-of-replies;
restricted-requestor;
timeout seconds;
} | [edit system services dhcp-local-server],
[edit system services dhcp-local-server dhcpv6],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services],
[edit logical-systems logical-system-name system services],
[edit routing-instances routing-instance-name system services] | Enable a DHCPv4 or DHCPv6 local server to listen for, process, and respond to bulk leasequery requests
received on TCP connections on TCP port 67 for DHCPv4 and on TCP port 547 for DHCPv6. | [
{
"name": "max-connections",
"desc": ""
},
{
"name": "number-of-connections",
"desc": "Specify the maximum number of concurrent TCP connections allowed in the logical system/routing instance. This setting helps you manage the resources that the jdhcpd daemon uses for bulk leasequery operations i... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring and Using DHCP Bulk Leasequery"
] |
allow-clear (Accounting Options) | allow-clear; | [edit accounting-options interface-profile profile-name] | Reports accounting statistics values cleared by the clear interfaces statistics command on a logical
interface configured with accounting options to the accounting options flat file associated with the
interface. By default, this statement is disabled and the cleared statistics are not reported to the flat file,
althou... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R1. | [
"Configure the Interface Profile",
"Accounting Options Configuration"
] |
allow-commands (Op Scripts) | allow-commands “regular-expression”; | [edit system scripts op file filename] | Specify a regular expression that defines which operational mode commands to explicitly allow during
execution of a local op script.
By default, when a user executes a script, the system does not permit the user to execute operational
mode commands within a script for which their login class does not normally have perm... | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Define Operational Mode Commands to Allow in an Op Script",
"Enable an Op Script and Define a Script Alias",
"Disable an Op Script",
"Regular Expressions for Allowing and Denying Junos OS Operational Mode Commands,",
"Configuration Statements, and Hierarchies"
] |
allow-distinct-port-pools | allow-distinct-port-pools; | [edit services nat source] | Allow NAT allocation for same subscriber with same NAT IP with different ports based on PCP and
DSLite traffic. | [] | Configure—To enter configuration mode. | Command introduced in Junos OS Release 24.4R1. | [] |
allow-dns-reply | allow-dns-reply; | [edit security flow] | Allow an incoming Domain Name Service (DNS) reply packet without a matched request. By default, if
an incoming UDP first-packet has dst-port 53, the device checks the DNS message packet header to
verify that the query bit (QR) is 0, which denotes a query message. If the QR bit is 1, which denotes a
response message, th... | [] | 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"
] |
allow-duplicates | allow-duplicates; | [edit logical-systems logical-system-name system syslog],
[edit logical-systems logical-system-name system syslog file file-name],
[edit logical-systems logical-system-name system syslog host host-name],
[edit logical-systems logical-system-name system syslog user user-name],
[edit system syslog],
[edit system syslog f... | Specify whether to allow the repeated messages in the system log output files. This can be set either at
global configuration level or for individual file, host, or user. By default, this parameter is set to disable. | [
{
"name": "file",
"desc": "Name of the file to log messages"
},
{
"name": "host",
"desc": "Host to receive the messages"
},
{
"name": "user",
"desc": "User to receive the notification of the event"
}
] | 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.
Logical systems support introduced in Junos OS Release 11.4. | [] |
allow-dynamic-requests (RADIUS Server) | allow-dynamic-requests; | [edit access radius servers name] | Allow dynamic requests from the RADIUS server so that change of authorization requests can be
received. | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring RADIUS Servers",
"Understanding Network Elements",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules"
] |
allow-email (Security Fallback Block) | allow-email; | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name
notification-options fallback-block]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name
notification-options fallback-block]
[edit security utm featu... | Enable e-mail notification to notify a specified administrator when a fallback-block occurs. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5. Support for Sophos
engine added in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS R... | [] |
allow-email (Security Virus Detection) | allow–email; | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus profile notification-options virus-detect] | Enable e-mail notification to notify a specified administrator when a virus is detected. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
allow-embedded-icmp | allow-embedded-icmp; | [edit security flow] | Allow ICMP error packets to pass through the device even when there is no session match for the
embedded packet. Once enabled, all packets encapsulated in ICMP pass through and no policy affects
this behavior. This feature is useful when you have asymmetric routing in your network and you want to
use traceroute and oth... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.3X48-D10. | [
"Understanding Traffic Processing on Security Devices"
] |
allow-fragmentation (fti) | allow-fragmentaion; | [edit interfaces fti number unit logical-unit-number tunnel encapsulation (gre|udp|ipip)] | For an encapsulated (UDP/GRE/IP-in-IP) tunnel, enable fragmentation of GRE-encapsulated packets
whose size exceeds the maximum transmission unit (MTU) value of a link that the packet passes
through. The don’t-fragment (DF) bit is not set in the outer IP header of encapsulated packets.
Default
Don't Fragment (DF) bit is... | [] | interface | Statement introduced in Junos OS Evolved Release 23.2R1. | [
"encapsulation"
] |
allow-fragmentation (protocols mpls) | allow-fragmentation; | [edit logical-systems logical-system-name protocols mpls path-mtu],
[edit protocols mpls path-mtu] | Allow IP packets to be fragmented before they are encapsulated in MPLS. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Enabling Packet Fragmentation"
] |
allow-fragmentation | allow-fragmentation; | [edit interfaces gr-fpc/pic/port unit logical-unit-number tunnel],
[edit logical-systems logical-system-name interfaces gr-fpc/pic/port unit logical-unit-number
tunnel] | For a generic routing encapsulation (GRE) tunnel, enable fragmentation of GRE-encapsulated packets
whose size exceeds the maximum transmission unit (MTU) value of a link that the packet passes
through. The don’t-fragment (DF) bit is not set in the outer IP header of GRE-encapsulated packets.
To enable the reassembly of... | [] | 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.
Statement introduced in Junos OS Release 19.3 for MPC10E line card. | [
"Enabling Fragmentation and Reassembly on Packets After GRE-Encapsulation",
"Junos OS Services Interfaces Library for Routing Devices"
] |
allow-icmp-without-flow | (allow-icmp-without-flow | no-allow-icmp-without-flow); | [edit security idp sensor-configuration flow] | Allow an ICMP packet without matched request. By default the ICMP flow is enabled. | [] | 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. | [] |
allow-ip-options (IDS MS-MPC) | allow-ip-options {
any;
loose-source-route;
route-alert;
route-record;
security;
stream-id;
strict-source-route;
timestamp;
} | [edit services ids rule rule-name term term-name then] | Specify the type of IPv4 options that the IDS rule permits in the IP header of a packet. If the packet
includes an option that is not configured, the packet is blocked. If the packet includes a configured
option whose length is an illegal value, the packet is dropped. This IDS rule can only be assigned to a
service set... | [
{
"name": "any",
"desc": "Allow all IPv4 options."
},
{
"name": "loose-source-route",
"desc": "Allow the Loose Source Route option."
},
{
"name": "route-alert",
"desc": "Allow the Router Alert option."
},
{
"name": "route-record",
"desc": "Allow the Record Route option."
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
allow-ip-options (Services Stateful Firewall) | allow-ip-options values; | [edit services stateful-firewall rule (Services Stateful Firewall) rule-name term (Services Stateful
Firewall) term-name then (Services Stateful Firewall) ] | Configure how the stateful firewall handles IP header information. This statement is optional. | [
{
"name": "value",
"desc": "Can be a set or range of numeric values, or one or more of the following predefined option types."
},
{
"name": "any",
"desc": ""
},
{
"name": "(Continued)",
"desc": "Option Name Numeric Value"
},
{
"name": "ip-security",
"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. | [
"Configuring Stateful Firewall Rules"
] |
allow-ipv6-extension-header (IDS MS-MPC) | allow-ipv6-extension-header {
ah;
any;
dstopts;
esp;
fragment;
hop-by-hop;
mobility;
routing;
} | [edit services ids rule rule-name term term-name then] | Specify the type of IPv6 extension headers that the IDS rule permits in a packet. If the packet includes
an extension header that is not configured, the packet is blocked. If the packet includes configured
extension headers that are incorrect, the packet is dropped. This IDS rule can only be assigned to a
service set ... | [
{
"name": "ah",
"desc": "Allow Authentication Header extension header."
},
{
"name": "any",
"desc": "Allow all IPv6 extension headers."
},
{
"name": "dstopts",
"desc": "Allow Destination Options extension header."
},
{
"name": "esp",
"desc": "Allow Encapsulating Security ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
allow-l3vpn-traceroute-src-select | allow-l3vpn-traceroute-src-select; | [edit system] | Select best source address for ICMP time-to-live (TTL) expiry error in case of Layer 3 VPNs. When a
traceroute occurs over Layer 3 VPN and the TTL expired traffic is generated, the traceroute returns to
the source through the routing instance. allow-l3vpn-traceroute-src-select determines the correct IP source
address b... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R1. | [
"Pinging a Layer 3 VPN"
] |
allow-leasequery (DHCP Local Server) | allow-leasequery {
restricted-requestor;
} | [edit system services dhcp-local-server],
[edit system services dhcp-local-server dhcpv6],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services],
[edit logical-systems logical-system-name system services],
[edit routing-instances routing-instance-name system services] | Enable a DHCPv4 or DHCPv6 local server to support individual leasequery operations by listening on
the UDP socket and responding to leasequery requests received on UDP connections. | [
{
"name": "restricted-requestor",
"desc": "Specify that the DHCP local server responds to an individual leasequery request by sending the binding information to restricted requestors only. This ensures that the requestor is the originator of the binding. Restricted requestors are determined as follows: For... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring and Using DHCP Individual Leasequery",
"Configuring and Using DHCP Bulk Leasequery"
] |
allow-maximum (Multicast) | allow-maximum; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast forwarding-cache],
[edit logical-systems logical-system-name routing-options multicast forwarding-cache],
[edit routing-instances routing-instance-name routing-options multicast forwarding-cache],
[edit routing-... | Allow the larger of global and family-level threshold values to take effect.
This statement is optional when you configure a forwarding cache or PIM state limits. When this
statement is included in the configuration and both a family-specific and a global configuration are
present, the higher limits take precedence.
F... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Example: Configuring the Multicast Forwarding Cache",
"Example: Configuring PIM State Limits"
] |
allow-multicast | allow-multicast; | [edit services service-set service-set-name] | Allow multicast traffic to be sent to the Adaptive Services or Multiservices PIC. | [] | 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. | [
"Enabling Services PICs to Accept Multicast Traffic"
] |
allow-no-end-option (DHCP Relay Agent) | allow-no-end-option; | [edit forwarding-options dhcp-relay overrides],
[edit forwarding-options dhcp-relay group group-name overrides],
[edit forwarding-options dhcp-relay group group-name interface interface-name overrides],
[edit routing-instances routing-instance-name forwarding-options dhcp-relay] | Enable a DHCP relay agent to process packets sent from clients without DHCP Option-255 (end-of-
options).
The default behavior in Junos OS is to drop packets that do not include Option 255. To override this
default behavior, configure the allow-no-end-option CLI statement at the [edit forwarding-options dhcp-relay
over... | [] | 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. | [
"Extended DHCP Relay Agent Overview",
"Overriding the Default DHCP Relay Configuration Settings",
"DHCP Snooping Support"
] |
allow-overlapping-nat-pools | allow-overlapping-nat-pools; | [edit services nat] | Specify that NAT source or destination pools can be shared between multiple service sets. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced with Junos OS Release 12.1. | [
"Configuring Service Sets for Network Address Translation"
] |
allow-overlapping-pools (NAT Next Gen Services) | allow-overlapping-pools; | [edit services nat] | Specify that NAT source or destination pools can have IP addresses that overlap with IP addresses in
pools used in other service sets. However, pools that configure port-block allocation must not overlap
with other pools. | [] | 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. | [] |
allow-remote-loopback | allow-remote-loopback; | [edit protocols oam link-fault-management interface interface-name negotiation-options] | Enable the remote loopback on IQ2 and IQ2-E Gigabit Ethernet interfaces, and Ethernet interfaces on
the MX Series routers and EX Series switches. Advertise that the interface is capable of getting into
loopback mode. Enable remote loopback in Ethernet OAM link fault management (LFM) on all Ethernet
interfaces or the sp... | [] | 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. | [
"Enabling Remote Loopback Support on the Local Interface"
] |
allow-reverse-ecmp | allow-reverse-ecmp | [edit security flow] | Enable ECMP support for reverse traffic. In this case, Junos OS for SRX Series Firewalls and vSRX Virtual
Firewall instances use a hash algorithm to determine the interface to use for reverse traffic in a flow.
This process is similar to asymmetric routing in which a packet traverses from a source to a destination
in o... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 17.3. | [
"Understanding ECMP Flow-Based Forwarding",
"Understanding ECMP Flow-Based Forwarding for Reverse Traffic on SRX Series Devices and vSRX",
"Instances"
] |
allow-route-leaking | allow-route-leaking; | [edit logical-systems name protocols ospf overload],
[edit logical-systems name routing-instances name protocols ospf overload],
[edit protocols ospf overload],
[edit routing-instances name protocols ospf overload],
[edit protocols ospf3 overload] | Allow routes to be leaked when OSPF overload is configured and advertise the external prefixes with
normal cost. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2. | [
"Understanding OSPF Overload Function"
] |
allow-snooped-clients | allow-snooped-clients; | [edit forwarding-options dhcp-relay dhcpv6 group group-name interface interface-name overrides],
[edit forwarding-options dhcp-relay dhcpv6 group group-name overrides],
[edit forwarding-options dhcp-relay dhcpv6 overrides],
[edit forwarding-options dhcp-relay group group-name interface interface-name overrides],
[edit ... | Explicitly enable DHCP snooping support on the DHCP relay agent.
Use the statement at the [edit ... dhcpv6] hierarchy levels to explicitly enable snooping support on the
router for DHCPv6 relay agent.
Default
DHCP snooping is disabled by default.
NOTE: On EX4300 and EX9200 switches, the allow-snooped-clients statement ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 12.1. | [
"Extended DHCP Relay Agent Overview",
"Overriding the Default DHCP Relay Configuration Settings",
"DHCP Snooping Support",
"Configuring DHCP Snooped Packets Forwarding Support for DHCP Relay Agent"
] |
allow-sram-parity-errors | allow-sram-parity-errors; | [edit chassis fpc slot-number] | (T Series routers only) Allow SRAM parity errors to occur without restarting the FPC. | [] | 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. | [] |
allow-subnet-mismatch | allow-subnet-mismatch; | [edit logical-systems logical-system-name protocols ldp interface interface-name],
[edit protocols ldp interface interface-name] | Ignore the LDP subnet check. For Junos OS Release 8.4 and later releases, an LDP source address
subnet check was added for the neighbor establishment procedure. The source address in the LDP link
hello packet is matched against the interface address.
Default
The source address in the LDP link hello packet is matched ag... | [] | 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. | [
"Ignoring the LDP Subnet Check"
] |
allow-transients | allow-transients; | [edit system scripts commit],
[edit system scripts commit file filename] | Enable commit scripts to commit transient configuration changes. Transient changes are made in the
checkout configuration but not in the candidate configuration.
Default
Transient changes are disabled by default. If you do not include the allow-transients statement, and an
enabled commit script generates transient chan... | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.4.
Support at the [edit system scripts commit file filename] hierarchy level introduced in Junos OS Release
24.2R1. | [
"Generating a Persistent or Transient Configuration Change in SLAX and XSLT Commit Scripts",
"Creating a Commit Script Macro to Read the Custom Syntax and Generate Related Configuration",
"Statements"
] |
allow-url-for-python (Op Scripts) | allow-url-for-python; | [edit system scripts op] | Enable the execution of Python op scripts from a remote site.
When you configure the language python or language python3 statement at the [edit system scripts] hierarchy
level, you can execute local Python scripts on a device running Junos OS. In order to execute Python op
scripts from a remote site, you must also conf... | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 16.1R1. | [
"Execute an Op Script from a Remote Site"
] |
allow-v4mapped-packets | allow-v4mapped-packets; | [edit system] | Enable the processing of IPv4-mapped IPv6 packets. | [] | 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. | [
"Configure IPv6 Features"
] |
allowed-destinations | allowed-destinations [ destinations ]; | [edit services dynamic-flow-capture capture-group client-name control-source identifier] | Identify flow capture destinations that are allowed in messages sent from this control source. | [
{
"name": "destinations",
"desc": "Allowed content destination 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.4. | [
"Configuring the Control Source"
] |
allowed-mac | allowed-mac {
mac-address-list;
} | [edit ethernet-switching-options secure-access-port interface (all | interface-name)] | Specify particular MAC addresses to be added to the MAC address cache.
NOTE: Although this configuration restricts the addresses that can be added to the MAC
address cache, it does not block the switch from receiving Layer 2 control packets—such
as Link Layer Discovery Protocol (LLDP) packets—transmitted from MAC addre... | [
{
"name": "mac-address-list",
"desc": "One or more MAC addresses configured as allowed MAC addresses for a specified"
}
] | system—To view this statement in the configuration.
system–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Example: Configuring Port Security (non-ELS)",
"Example: Protecting Against DHCP Snooping Database Attacks",
"Example: Protecting against Ethernet Switching Table Overflow Attacks",
"Example: Protecting against DHCP Starvation Attacks",
"Configuring MAC Limiting (non-ELS)",
"Configuring MAC Limiting (J-W... |
allowed-sources (REST API) | allowed-sources [ value-list ]; | [edit system services rest control] | Specify the allowed source IP addresses for the REST API process. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
alt-name (Application Identification) | alt-name alt-name | [edit services application-identification application application-name] | Provide an alternate name for the application. | [
{
"name": "alt-name",
"desc": "Alternate name for the application. Range: 1 through 255 characters"
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
alternative-partition-name (OCS Partition) | alternative-partition-name; | [edit access ocs partition alternative-partition-name alternative-partition-name] | Configure alternative partition name for OCS/GY. When configured, the specific partition name is used
to forward diameter data along alternative data path in the specific cases. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3. | [
"Configuring the OCS Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interactions Between the PCRF, PCEF, and OCS"
] |
always-mark-connection-protection-tlv | always-mark-connection-protection-tlv; | [edit logical-systems logical-systems-name protocols mpls interface interface-name],
[edit protocols mpls interface interface-name] | (MX Series routers only) Enable you to switch an LSP away from a network node using a bypass LSP.
This feature could be used in maintenance of active networks when a network device needs to be
replaced without interrupting traffic passing through the network. The LSPs can be either static or
dynamic.
This statement mar... | [] | 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. | [
"Switching LSPs Away from a Network Node"
] |
always-process-option-request-option | always-process-option-request-option; | [edit logical-systems name system services dhcp-local-server dhcpv6 group name interface name
overrides],
[edit logical-systems name system services dhcp-local-server dhcpv6 group name interface-tag
name overrides],
[edit logical-systems name system services dhcp-local-server dhcpv6 group name overrides],
[edit logic... | Always process the Option Request option even after address allocation failure. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | — | [
"Understanding Differences Between Legacy DHCP and Extended DHCP",
"Configuring a DHCP Server on Switches",
"Overriding the Default DHCP Local Server Configuration Settings"
] |
always-write-giaddr | always-write-giaddr; | [edit forwarding-options dhcp-relay overrides],
[edit forwarding-options dhcp-relay group group-name overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay group group-name
overrides],
[edit logical-systems... | Overwrite the gateway IP address (giaddr) of every DHCP packet with the giaddr of the DHCP relay
agent before forwarding the packet to the DHCP server. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Extended DHCP Relay Agent Overview"
] |
always-write-option-82 | always-write-option-82; | [edit forwarding-options dhcp-relay overrides],
[edit forwarding-options dhcp-relay group group-name overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay group group-name
overrides],
[edit logical-systems... | Override the DHCP relay agent information option (option 82) in DHCP packets destined for a DHCP
server. The use of this option causes the DHCP relay agent to perform one of the following actions,
depending on how it is configured:
•
If the DHCP relay agent is configured to add option 82 information to DHCP packets, it... | [] | 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. | [
"Using DHCP Relay Agent Option 82 Information",
"Extended DHCP Relay Agent Overview"
] |
ambient-temperature | chassis ambient-temperature (25C|40C|55C); | [edit chassis] | Set the chassis ambient temperature and instruct the power manager to allocate power to the line cards
according to the ambient temperature value.
On system initialization in a PTX Series router, the power manager reads the ambient temperature and
allocates power to the line cards according to the power budget policy a... | [
{
"name": "25C",
"desc": "Set the ambient temperature of the chassis to 25°C"
},
{
"name": "40C",
"desc": "Set the ambient temperature of the chassis to 40°C"
},
{
"name": "55C",
"desc": "Set the ambient temperature of the chassis to 55°C NOTE: Starting in Junos OS Evolved Release 19... | chassis—To view this statement in the configuration.
chassis-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Managing Power Allocated to PTX5000 FPCs on the Basis of Chassis Ambient Temperature",
"Configuration",
"Monitoring the Power Consumption of PTX5000 FPCs by Configuring the Ambient Temperature",
"Understanding How Configuring Ambient Temperature Helps Optimize Power Utilization"
] |
amf | amf name {
<default-amf>;
ip-address ip-address;
local-endpoint {
<initial-tnla-weight-factor initial-tnla-weight-factor>;
ip-address address;
<port port-number>;
}
}
node-id node-id;
<offline>;
<port port-number>;
<routing-instance routing-instance>;
tracking-area name;
} | [edit services agf] | Configure the parameters that the AGF uses to connect to the Access and Mobility Management
Function (AMF). | [
{
"name": "name",
"desc": "Specifies the name of the Access and Mobility Management Function (AMF)."
},
{
"name": "default-amf",
"desc": "(Optional) Identifies the AMF as the default AMF."
},
{
"name": "ip-address address",
"desc": "Specifies the AMF IP address that AGF uses to estab... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.3R1. | [] |
amplifier-chain (IPLC) | amplifier-chain {
anchor-iplc ;
ila ila-number {
ila-options ;
no-anchor-iplc ;
osc-ip ip-address/CIDR ;
osc-mac osc-mac;
}
} | [edit chassis fpc fpc-slot optical-options] | Configure the optical supervisory channel (OSC) for the PTX3000 integrated photonic line system and
optical ILAs in the amplifier chain. This command includes parameters that enable IP connectivity for the
OSC in the line system and amplifier chain.
Default | [
{
"name": "OS CLI:",
"desc": ""
},
{
"name": "anchor-iplc",
"desc": "Configure the specified IPLC as the anchor IPLC for the optical supervisory channel (OSC). Use this option to specify one of the IPLC modules in the amplifier chain as the anchor of the chain. You can only have one IPLC anchor ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1R1. | [
"Configuring the Optical Supervisory Channel Across the Amplifier Chain of the PTX3000 Integrated",
"Photonic Line System",
"Example: Configuring the Optical Supervisory Channel for the Integrated Photonic Line System and",
"Optical Inline Amplifier",
"Configuring the Anchor IPLC of the Amplifier Chain",
... |
amt (IGMP) | amt {
relay {
defaults {
(accounting | no-accounting);
group-policy [ policy-names ];
query-interval seconds;
query-response-interval seconds;
robust-count number;
ssm-map ssm-map-name;
version version;
}
}
} | [edit logical-systems logical-system-name protocols igmp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
igmp],
[edit protocols igmp],
[edit routing-instances routing-instance-name protocols igmp] | Configure Automatic Multicast Tunneling (AMT) relay attributes.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Default IGMP Parameters for AMT Interfaces"
] |
amt (Protocols) | amt {
relay {
accounting;
family {
inet {
anycast-prefix ip-prefix</prefix-length>;
local-address ip-address;
}
}
secret-key-timeout minutes;
tunnel-limit number;
}
traceoptions {
file filename <... | [edit logical-systems logical-system-name protocols],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit protocols],
[edit routing-instances routing-instance-name protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | 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"
] |
analytics | analytics {
agent {
service-agents {
agent-name {
inputs {
analytics {
parameters {
generate-tags value;
sample-frequency value;
sensors file-path;
... | [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 13.2. | [
"Network Analytics Overview",
"Configuring the BNG as an IPFIX Mediator to Collect and Export IPFIX Data",
"Configuring NTF Agent",
"IPFIX Mediation on the BNG",
"Configuring the Collection and Export of Local Telemetry Data on the IPFIX Mediator",
"Telemetry Data Collection on the IPFIX Mediator for Expo... |
analyzer | Routing
analyzer {
analyzer-name {
input {
egress {
interface (all | interface-name);
vlan (vlan-id | vlan-name);
}
ingress {
interface (all | interface-name);
vlan (vlan-id | vlan-name);
... | For platforms without ELS:
[edit ethernet-switching-options]
For platforms with ELS:
[edit forwarding-options] | Configure port mirroring. You can create a total of four port-mirroring configurations on the QFX Series,
subject to the following limits:
•
There can be no more than two configurations that mirror ingress traffic.
•
There can be no more than two configurations that mirror egress traffic.
Default
Port mirroring is dis... | [
{
"name": "all",
"desc": "Mirror all the access interfaces. Using this option does not cause the QSFP+ or management"
},
{
"name": "analyzer-name",
"desc": "Name of the analyzer. The name can include as many as 125 characters; must begin with a"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
Option output vlan added in Junos OS Release 12.1 for the QFX Series.
Option output ip-address added in Junos OS Release 12.3 for the QFX Series for non-ELS platforms and
added in 14.1X53-D10 for ELS platforms.
Statement introduced for the “Interface Privilege Level” in Ju... | [
"Understanding Port Mirroring and Analyzers",
"Configuring Port Mirroring",
"Examples: Configuring Port Mirroring for Local Analysis",
"Example: Configuring Port Mirroring Analyzers for Local Monitoring of Employee Resource Use",
"Example: Configuring Port Mirroring for Remote Monitoring of Employee Resourc... |
analyzer-address | analyzer-address address; | [edit services flow-collector] | Configure an IP address for the packet analyzer that overrides the default value. | [
{
"name": "address",
"desc": "IP address for packet analyzer."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring a Packet Analyzer"
] |
analyzer-id | analyzer-id name; | [edit services flow-collector] | Configure an identifier for the packet analyzer that overrides the default value. | [
{
"name": "name",
"desc": "Identifier for packet analyzer."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring a Packet Analyzer"
] |
anchor-point (Pseudowire Subscriber Interfaces) | anchor-point {
lt-device;
aex;
} | [edit interfaces ps0] | Specify the anchor-point. The anchor point can either be an aggregated ethernet interface or a logical
tunnel (lt) interface.
On a logical tunnel interface that terminates the MPLS pseudowire tunnel at the access node, the other
end of the tunnel terminates on the pseudowire subscriber logical interface. The subscriber... | [
{
"name": "lt-device",
"desc": "An lt device in the format lt-fpc/pic/port"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1. | [
"MPLS Pseudowire Subscriber Logical Interfaces",
"MPLS Pseudowire Subscriber Logical Interfaces",
"MPLS Pseudowire Subscriber Logical Interfaces",
"MPLS Pseudowire Subscriber Logical Interfaces"
] |
ancp (Adjustment Control Profiles) | ancp {
priority priority;
algorithm algorithm;
} | [edit class-of-service adjustment-control-profiles profile-name application] | Configure the shaping rate adjustment controls for the ANCP application. | [
{
"name": "priority",
"desc": "Priority of the ANCP application in the adjustment control profile. Range: 1 through 10; 1 being the highest priority. Default: 1"
},
{
"name": "algorithm",
"desc": "Rate adjustment algorithm used by the ANCP application. Values:"
},
{
"name": "adjust-ne... | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1. | [
"CoS Adjustment Control Profiles Overview",
"Configuring CoS Adjustment Control Profiles",
"Verifying the CoS Adjustment Control Profile Configuration"
] |
ancp | ancp {
adjacency-loss-hold-time seconds;
adjacency-timer seconds;
gsmp-syn-timeout seconds;
gsmp-syn-wait;
interfaces {
interface-set interface-set-name {
access-identifier identifier-string;
underlying-interface underlying-interface-name;
}
interface... | [edit protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Configuring the ANCP Agent"
] |
ancp-speed-change-immediate-update (ANCP) | ancp-speed-change-immediate-update; | [edit access profile profile-name accounting] | Configure AAA to generate immediate interim accounting updates to the RADIUS server in response to
ANCP agent notifications of rate changes on subscriber access lines. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Configuring Immediate Interim Accounting Updates to RADIUS in Response to ANCP Notifications",
"Configuring Per-Subscriber Session Accounting",
"Configuring the ANCP Agent"
] |
annotate | annotate <statement> <comment string> | Add comments to a configuration. You can add comments only at the current hierarchy level.
Any comments you add appear only when you view the configuration by entering the "show" on page
28980 command in configuration mode or the show configuration command in operational mode.
NOTE: The software supports annotation up... | [
{
"name": "statement",
"desc": "Statement to which you are attaching the comment."
},
{
"name": "comment-string",
"desc": "Text of the comment. You must enclose it in quotation marks. In the comment string, you can include the comment delimiters /* */ or #. If you do not specify any, the comment... | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy. | Command introduced before Junos OS Release 7.4. | [
"Adding Comments in a Device Configuration"
] | |
anomaly | anomaly {
direction (Security Custom Attack) (any | client-to-server | server-to-client);
service service-name;
shellcode (all | intel | no-shellcode | sparc);
test test-condition;
} | [edit security idp custom-attack attack-name attack-type] | Protocol anomaly attack objects detect abnormal or ambiguous messages within a connection according
to the set of rules for the particular protocol being used. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
anti-replay-window-size (Services IPsec VPN) | anti-replay-window-size bits; | [edit services ipsec-vpn rule rule-name term term-name then] | Specify the size of the IPsec antireplay window. | [
{
"name": "bits",
"desc": "Size of the antireplay window, in bits."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [] |
anti-replay-window-size (Services Service Set) | anti-replay-window-size bits; | [edit services service-set service-set-name ipsec-vpn-options] | Specify the size of the IPsec antireplay window. This statement is useful for dynamic endpoint tunnels
for which you cannot configure the anti-replay-window-size statement at the [edit services ipsec-vpn rule
rule-name term term-name then] hierarchy level.
For static IPsec tunnels, this statement sets the antireplay wi... | [
{
"name": "bits",
"desc": "Size of the antireplay window, in bits."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Configuring IPsec Service Sets",
"Configuring IPsec Rules"
] |
anti-replay-window-size | anti-replay-window-size anti-replay-window-size; | [edit security ipsec],
[edit tenants name security ipsec] | To enable the anti-replay-window-size option, you first need to configure the option for each VPN object or
at the global level. You can configure the anti-replay window size in the range of 64 to 8192 (power of
2). If the anti-replay window size is not configured, the window size is 64 by default. If anti-replay-windo... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1. | [
"Anti-Replay Window"
] |
anti-spam (Logical Systems) | anti-spam {
sbl {
profile (Security Antispam SBL) name {
address-blacklist address-blacklist;
address-whitelist address-whitelist;
custom-tag-string custom-tag-string;
(sbl-default-server | no-sbl-default-server);
spam-action (block | tag-header | ... | [edit logical-systems logical-system-name security utm feature-profile]
[edit tenants tenant-name security utm feature-profile] | Configures the Content Security antispam feature for logical systems. The antispam feature examines
transmitted e-mail messages to identify e-mail spam. When the device detects a message deemed to be
spam, it blocks the e-mail message or tags the e-mail message header or subject with a preprogrammed
string. Antispam fi... | [
{
"name": "anti-spam",
"desc": "Configures the Content Security antispam feature for logical system."
},
{
"name": "address-blacklist",
"desc": "Enter an address blocklist custom object for local list spam filtering."
},
{
"name": "address-whitelist",
"desc": "Enter an address allowl... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1.
Support for configuration in tenant systems introduced in Junos OS Release 19.2R1. | [
"Antispam Filtering Overview"
] |
anti-spam (Security Content Security Policy) | anti-spam {
smtp-profile profile-name;
} | [edit security utm default-configuration]
[edit security utm utm-policy policy-name]
[edit logical-systems logical-system-name security utm utm-policy policy-name]
[edit tenants tenant-name security utm utm-policy policy-name] | Configures a Content Security policy for the antispam SMTP protocol and attach this policy to a security
profile to implement it. The device can block and drop detected spam at either the connection level or
the e-mail level. When the SMTP sender is identified as a spam sender based on its IP address, the
SMTP connecti... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Support for configuration in logical systems introduced in Junos OS Release 18.3R1.
Support for configuration in tenant systems introduced in Junos OS Release 19.2R1. | [
"Antispam Filtering Overview"
] |
anti-spam | anti-spam {
address-blacklist address-blacklist;
address-whitelist address-whitelist;
sbl {
custom-tag-string custom-tag-string;
(sbl-default-server | no-sbl-default-server);
server {
ip;
routing-instance routing-instance;
source-address source-address;
}
spam-action(block |... | [edit security utm feature-profile]
[edit security utm default-configuration] | 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": "anti-spam",
"desc": "Configure antispam feature."
},
{
"name": "address-blacklist",
"desc": "Enter an address blocklist custom object for local list spam filtering."
},
{
"name": "address-whitelist",
"desc": "Enter an address-allowlist custom-object for local list spam fil... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
The server option introduced in Junos OS Release 23.1R1. | [] |
anti-virus (Content Security Policy) | anti-virus {
ftp {
download-profile profile-name;
upload-profile profile-name;
}
http-profile profile-name;
imap-profile profile-name;
pop3-profile profile-name;
smtp-profile profile-name;
} | [edit security utm default-configuration]
[edit security utm utm-policy policy-name]
[edit logical-systems logical-systems-name security utm utm-policy policy-name]
[edit tenants tenant-name security utm utm-policy policy-name] | Configures a Content Security policy for the antivirus protocols and attaches this policy to a security
profile to implement it. The internal antivirus scan engine supports scanning for specific Application
Layer transactions allowing you to select the content (HTTP, FTP, SMTP, POP3, or IMAP traffic) to scan. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Support for configuration in logical systems introduced in Junos OS Release 18.3R1.
Support for configuration in tenant systems introduced in Junos OS Release 19.2R1. | [
"Unified Threat Management Overview"
] |
anti-virus (Content Security) | anti-virus {
mime-whitelist {
exception;
list;
}
sophos-engine {
fallback-options {
content-size (block | log-and-permit | permit);
default (block | log-and-permit | permit);
engine-not-ready (block | log-and-permit | permit);
out-of-r... | [edit security utm feature-profile]
[edit security utm default-configuration] | 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": "anti-virus",
"desc": "Configure antivirus feature."
},
{
"name": "mime-whitelist",
"desc": "This is the comprehensive list for those MIME types that can bypass antivirus scanning."
},
{
"name": "sophos-engine",
"desc": "The antivirus engine that is used on the device. You ... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
anti-virus (Logical Systems) | anti-virus {
profile name {
fallback-options (Security Antivirus Sophos Engine) {
content-size (Security Antivirus Sophos Engine) (block | log-and-permit | permit);
decompress-err (block | log-and-permit | permit);
default (Security Antivirus Sophos Engine) (block | log-... | [edit logical-systems logical-systems-name security utm feature-profile]
[edit tenants tenant-name security utm feature-profile] | Configures the Content Security Sophos Antivirus feature for logical systems. You can also configure the
default Content Security configuration for antivirus feature profile. If you do not configure any option in
the antivirus feature profile, the values configured in the default Content Security configuration are
appl... | [
{
"name": "anti-virus",
"desc": "Configures the Content Security antivirus feature for logical systems."
},
{
"name": "mime-whitelist",
"desc": "This is the comprehensive list for those MIME types that can bypass antivirus scanning."
},
{
"name": "sophos-engine",
"desc": "The antivir... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1.
Support for configuration in tenant systems introduced in Junos OS Release 19.2R1. | [
"Unified Threat Management Overview"
] |
anti-virus (Services) | anti-virus {
policy policy-name {
action(block | permit);
default-notification {
log;
}
fallback-options {
action(block | permit);
notification {
log;
}
}
http-client-notify {
(file file-name | message message | redirect-url redirect-URL);
}
notification {
log;
}
machine-l... | [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": "policy",
"desc": "Configure the antivirus policy details."
},
{
"name": "policy-name",
"desc": "Name of the antivirus policy."
},
{
"name": "action",
"desc": "Action taken when file meets verdict threshold."
},
{
"name": "default-notification",
"desc": "Notific... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1.
The machine-learning-scan option is introduced in Junos OS Release 24.2R1. | [] |
any (VPLS Multihoming) | any; | [edit logical-systems logical-system-name routing-instances instance-name protocols vpls multi-
homing active-interface],
[edit logical-systems logical-system-name routing-instances instance-name protocols vpls multi-
homing site site-name active-interface],
[edit routing-instances instance-name protocols vpls multi-ho... | Specify that any multihomed interface can be used as the primary interface by the VPLS site. Depending
on the order in which interfaces are listed in the PE router’s configuration, the first operational interface
in the set of configured interfaces is chosen to be the primary interface.
NOTE: In the VPLS documentation... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Specifying an Interface as the Active Interface"
] |
any-sender | any-sender; | [edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip
group group-name neighbor neighbor-name],
[edit protocols rip group group-name neighbor neighbor-name],
[edit routing-instanc... | Disable strict sender address checks. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0. | [] |
anycast-pim | anycast-pim {
rp-set {
address address <forward-msdp-sa>;
} | [edit logical-systems logical-system-name protocols pim rp local family (inet | inet6)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp local family (inet | inet6)],
[edit protocols pim rp local family (inet | inet6)],
[edit routing-instances routing-instance-name pr... | Configure properties for anycast RP using PIM.
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 7.4. | [
"Example: Configuring PIM Anycast With or Without MSDP"
] |
anycast-prefix | anycast-prefix ip-prefix/<prefix-length>; | [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 an IP address prefix to use for the Automatic Multicast Tunneling (AMT) relay anycast address.
The prefix is advertised by unicast routing protocols to route AMT discovery messages to the router
from nearby AMT gateways. The IP address that the prefix is derived from can be configured on any
interface in the s... | [
{
"name": "ip-prefix/<prefix-length>",
"desc": "IP address prefix."
}
] | 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"
] |
apn | apn pattern-string {
imsi-prefix imsi-prefix-digits {
action (APN GTP) {
drop;
pass;
selection (ms|net|vrf);
}
}
} | [edit security gtp profile profile-name] | Use the APN function to allow or deny access to specific access point names (APNs). By default, the
device permits all APNs. To enable APN filtering, you must specify one or more APNs. To specify an
APN, you need to know the domain name of the network (for example, example.com) and, the operator
ID. Because the domain ... | [
{
"name": "pattern-string",
"desc": "To specify APN pattern string, such as “example.net.mcc123.mnc456.gprs”."
},
{
"name": "imsi-prefix-digits",
"desc": "To specify an IMSI prefix."
}
] | 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. | [
"Understanding GTP APN Filtering",
"Example: Setting a GTP APN and a Selection Mode",
"Understanding GTPv2 IMSI Prefix and APN Filtering"
] |
apn-control (Security GTP) | apn-control apn-ctrl-name
{ apn apn-string}
{rate-limit
{alarm-threshold threshold}
{drop-threshold threshold}
{ message <v0msg-list-name|v1msg-list-name|v3msg-list-name>}
} | [edit security gtp] | Use this command to configure APN control profile using APN string. You can apply the APN control
profile to GTP profile for ARL. | [
{
"name": "Apnapn-string",
"desc": "You can specify APN using APN string. APN string consists of Network Identifier (NI)"
},
{
"name": "<NI>: for example internet, internet.public",
"desc": "<NI>.<OI>: for example internet.mnc005.mcc244.gprs, internet.public.mnc005.mcc244.gprs APN string configu... | Statement introduced in Junos OS Release 21.2R1. | [] | |
apn-control-group (Security GTP) | apn-control-group <apn-ctrl-grp-name> | [edit security gtp] | Use this configuration to group all the APNs with the same rate limiting requirements and apply the
group to the GTP profile. | [] | Statement introduced in Junos OS Release 21.2R1. | [
"Understanding GTP APN Filtering"
] | |
apn-services (control plane services) | apn-services {
apns name {
mobile-interface mobile-interface;
}
} | [edit services mobile-edge gateways saegw name control-plane-peers] | The access point name (APN) is sent by the control plane over PFCP to place a subscriber in a specific
network instance. | [
{
"name": "apn name",
"desc": "At least one access point name."
}
] | system | Statement introduced in Junos OS Release 19.4R1. | [] |
app-mapping-timeout | app-mapping-timeout app-mapping-timeout; | [edit services nat pool nat-pool-name] | Specify the duration for address pooling paired (AP-P) mappings that use the specified NAT pool. If this
option is not configured and a timeout value is configured for "mapping-timeout" on page 10782, the
timeout value configured for "mapping-timeout" on page 10782 is used. If neither option is specified, the
default ... | [
{
"name": "app-mapping-timeout",
"desc": "Lifetime of AP-P mappings in seconds."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | mapping-timeout statement introduced in JUNOS Release 12.3. | [
"Configuring Source and Destination Addresses Network Address Translation Overview"
] |
appfw-profile (System) | appfw-profile {
maximum amount;
reserved amount;
} | [edit security application-firewall profile profile-name]
[edit tenants tenant-name security application-firewall] | Specify the application firewall profile quota of a logical system and tenant systems.
As a primary administrator, you can create a security profile and specify the kinds and amounts of
resources that are to be allocated to a logical system to which the security profile is bound. A security
profile is used for share th... | [
{
"name": "maximum amount",
"desc": "Specify the maximum allowed quota value."
},
{
"name": "reserved amount",
"desc": "Specify a reserved quota value that guarantees that the resource amount specified is"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
The edit tenant tenant-name security application-firewall level is introduced in Junos OS Release 18.4R1. | [
"Application Firewall Overview"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.