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 |
|---|---|---|---|---|---|---|---|
multipath-build-priority | multipath-build-priority {
( low | medium);
} | [edit fabric protocols bgp],
[edit logical-systems name protocols bgp],
[edit logical-systems name routing-instances name protocols bgp],
[edit protocols bgp],
[edit routing-instances name protocols bgp] | Configure a priority for multipath resolution during load balancing. When multipath is enabled on a
route reflector, BGP calculates the multipaths each time a new route is added or whenever an existing
route is changed, which uses up system resources and slows down the BGP RIB resolution. Configure
BGP multipath job pr... | [] | routing | Statement introduced in Junos OS Release 18.1R1. | [
"Understanding BGP Multipath"
] |
multipath-rule | multipath-rule name {
application;
application-group;
bandwidth-limit bandwidth-limit;
enable-reverse-wing;
link-preferences;
link-type (IP | MPLS);
number-of-paths number-of-paths;
} | [edit security advance-policy-based-routing] | Configure application-based multipath routing options.
A multipath rule is attached to an SLA rule. The SLA rule is an action part of the APBR rule in a APBR
profile. So, whenever a traffic matches the APBR profile, the SLA rule and the multipath rule gets applied
and hence multipathing is enabled for that traffic. | [
{
"name": "name",
"desc": "Name of the multipath rule."
},
{
"name": "application",
"desc": "Dynamic application type to match."
},
{
"name": "application-group",
"desc": "Dynamic application group type to match."
},
{
"name": "bandwidth-limit",
"desc": "Bandwidth limit o... | Security | Statement introduced in Junos OS Release 19.2R1. | [] |
multiple-triggered-joins | multiple-triggered-joins {
count (Protocols PIM)number;
interval (Protocols PIM)milliseconds;
} | [edit protocols piminterface (Protocols PIM)interface-name ] | Enable PIM which emits multiple triggered joins between PIM neighbors at configured or default short
intervals.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "interface-name",
"desc": "Name of the interface. Specify the full interface name, including the physical and logical"
},
{
"name": "count",
"desc": "Number of triggered joins."
},
{
"name": "interval",
"desc": "Interval between multiple triggered joins in milliseconds."
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1R1. | [
"PIM on Aggregated Interfaces"
] |
multiplier (BFD Liveness Detection) | multiplier number; | [edit logical-systems name routing-instances name protocols (evpn | l2vpn | vpls) oam bfd-liveness-
detection],
[edit logical-systems name routing-instances name protocols (evpn | l2vpn | vpls) neighbor neighbor-
id oam bfd-liveness-detection],
[edit logical-systems name routing-instances name protocols (evpn | l2vpn ... | Configure the number of hello packets not received by a neighbor that causes the originating interface
to be declared down. | [
{
"name": "number",
"desc": "Number of hello packets."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5.
Support for BFD authentication introduced in Junos OS Release 9.6. | [
"Configuring BFD for Layer 2 VPN and VPLS",
"Example: Configuring BFD for Static Routes for Faster Network Failure Detection"
] |
multiplier (Liveness Detection) | multiplier number; | [edit protocols iccp peer liveness-detection] | Configure the number of liveness detection requests not received by the peer before Bidirectional
Forwarding Detection (BFD) declares the peer is down. | [
{
"name": "number",
"desc": "Maximum allowable number of liveness detection requests missed by the peer. Range: 1 through 255 Default: 3"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [] |
multiplier (Protocols PIM) | multiplier number; | [edit protocols pim interface (Protocols PIM) interface-name bfd-liveness-detection],
[edit routing-instances routing-instance-name protocols pim interface (Protocols PIM) interface-
name bfd-liveness-detection] | Configure the number of hello packets not received by a neighbor that causes the originating interface
to be declared down. | [
{
"name": "number",
"desc": "Number of hello packets."
}
] | 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 BFD for PIM"
] |
multiplier | multiplier number; | [edit system services dhcp-local-server liveness-detection method bfd],
[edit system services dhcp-local-server dhcpv6 liveness-detection method bfd],
[edit forwarding-options dhcp-relay liveness-detection method bfd],
[edit forwarding-options dhcp-relay dhcpv6 liveness-detection method bfd],
[edit system services dhcp... | Configure the number of hello packets not received by the neighbor before Bidirectional Forwarding
Detection (BFD) declares the neighbor down. | [
{
"name": "number",
"desc": "Maximum allowable number of hello packets missed by the neighbor. Range: 1 through 255 Default: 3"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Example: Configuring Group Liveness Detection with BFD for DHCP Local Server Clients",
"Example: Configuring Global Liveness Detection with BFD for DHCP Relay Agent Clients"
] |
multipoint | multipoint; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Configure the interface unit as a multipoint connection.
Default
If you omit this statement, the interface unit is configured as a point-to-point connection. | [] | 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 Multipoint Connection"
] |
multiservice | multiservice {
source-mac;
destination-mac;
payload {
ip {
layer3-only;
layer-3 (source-ip-only | destination-ip-only);
layer-4;
inner-vlan-id;
outer-vlan-id;
}
}
} | [edit chassis fpc slot-number pic pic-number hash-key family] | (MX Series 5G Universal Routing Platforms and QFX10000 switches only) Configure data used in a hash
key for the multiservice protocol family when configuring PIC-level hashing for load balancing on an
802.3ad Link Aggregation Group. | [
{
"name": "destination-mac",
"desc": "Include destination MAC address in the hash key."
},
{
"name": "payload",
"desc": "Include payload data in the hash key. This option has the following suboptions:"
},
{
"name": "ip",
"desc": "Include the IP address of the IPv4 or IPv6 payload int... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D10. | [
"Configuring PIC-Level Symmetrical Hashing for Load Balancing on 802.3ad LAGs for MX Series",
"Routers"
] |
multiservice-options (Flow Monitoring) | multiservice-options {
(core-dump | no-core-dump);
(syslog | no-syslog);
flow-control-options {
down-on-flow-control;
dump-on-flow-control;
reset-on-flow-control;
}
} | [edit interfaces mo-fpc/pic/port] | For flow-monitoring interfaces only, configure multiservice-specific interface properties.
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 before Junos OS Release 7.4. | [
"Configuring Flow Monitoring"
] |
multiservice-options | multiservice-options {
(syslog | no-syslog);
(core-dump | no-core-dump);
(dump-on-flow-control);
flow-control-options {
down-on-flow-control;
dump-on-flow-control;
reset-on-flow-control;
up-on-flow-control;
}
} | [edit interfaces mo-fpc/pic/port] | For monitoring services interfaces only, configure multiservice-specific interface properties.
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 before Junos OS Release 7.4. | [
"Configuring Multiservice Physical Interface Properties",
"Junos OS Services Interfaces Library for Routing Devices"
] |
must-secure | must-secure; | [edit security macsec connectivity-association connectivity-association-name mka] | Specifies that all traffic travelling on the MACsec-secured link must be MACsec-secured to be
forwarded onward.
When the must-secure option is enabled, all traffic that is not MACsec-secured that is received on the
interface is dropped.
When the must-secure option is disabled, all traffic from devices that support MACs... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10. | [
"Configuring MACsec",
"Configuring Advanced MACsec Features"
] |
mutual-authentication (REST API) | mutual-authentication {
certificate-authority certificate-authority-profile-name;
} | [edit system services rest https] | Enable SSL/TLS mutual authentication. The server certificate must be set when configuring mutual
authentication.
The remaining statement is explained separately. See CLI Explorer. | [] | 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. | [] |
mvpn (Draft-Rosen MVPN) | mvpn {
family {
inet {
autodiscovery {
inet-mdt;
}
disable
}
inet6 {
disable
}
}
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit routing-instances routing-instance-name protocols pim] | Configure the control plane to be used for PE routers in the VPN to discover one another automatically.
From here, you can also disable IPv6 draft-rosen multicast VPN at this hierarchy by using the disable
command at the protocols pim mvpn family inet6 hierarchy. | [] | 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.
The autodiscovery statement was moved from [.. protocols pim mvpn] to [..protocols pim mvpn family inet] in
Junos OS Release 13.3. | [
"Example: Configuring Source-Specific Multicast for Draft-Rosen Multicast VPNs"
] |
mvpn (NG-MVPN) | mvpn {
autodiscovery-only {
intra-as {
inclusive;
}
}
receiver-site;
route-target {
export-target {
target target-community;
unicast;
}
import-target {
target {
target <target:number:number> <receiver... | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit routing-instances routing-instance-name protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Example: Configuring Source-Specific Multicast for Draft-Rosen Multicast VPNs"
] |
mvpn | mvpn {
inter-region-template{
template template-name {
all-regions {
incoming;
ingress-replication {
create-new-ucast-tunnel;
label-switched-path {
label-switched-path-template (Multicast) {
... | [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] | Enable next-generation multicast VPNs in a routing instance. | [
{
"name": "receiver-site",
"desc": "Allow sites with multicast receivers."
},
{
"name": "sender-site",
"desc": "Allow sites with multicast senders."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Support for the traceoptions statement at the [edit protocols mvpn] hierarchy level introduced in Junos OS
Release 13.3.
Support for the inter-region-template statement at the [edit protocols mvpn] hierarchy level introduced in
Junos OS Release 15.1. | [
"Configuring Routing Instances for an MBGP MVPN"
] |
mvpn-iana-rt-import | mvpn-iana-rt-import; | [edit logical-systems logical-system-name protocols bgp group group-name],
[edit protocols bgp group group-name] | Enables the use of IANA assigned rt-import type values (0x010b) for mutlicast VPNs. You can configure
this statement on ingress PE routers only.
NOTE: If you configure the mvpn-iana-rt-import statement in Junos OS release 10.4R2 and
later, the Juniper Networks router can inter-operate with other vendors routers for
mul... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS release 10.4R2.
Statement deprecated in Junos OS release 17.3, which means it no longer appears in the CLI but can be
accessed by scripts or by typing the command name until it is finally removed. | [] |
mvpn-mode | mvpn-mode (rpt-spt | spt-only); | [edit logical-systems profile-name routing-instances instance-name protocols mvpn],
[edit routing-instances instance-name protocols mvpn] | Configure the mode for customer PIM (C-PIM) join messages. Mixing MVPN modes within the same
VPN is not supported. For example, you cannot have spt-only mode on a source PE and rpt-spt mode on
the receiver PE.
Default
spt-only | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Configuring Shared-Tree Data Distribution Across Provider Cores for Providers of MBGP MVPNs",
"Configuring SPT-Only Mode for Multiprotocol BGP-Based Multicast VPNs"
] |
mvrp | SRX 320)
mvrp {
bpdu-destination-mac-address provider-bridge-group;
join-timer (MVRP) milliseconds;
leave-timer milliseconds;
leaveall-timer milliseconds;
interface (all | interface-name) {
join-timer (MVRP) milliseconds;
leave-timer milliseconds;
leaveall-timer millisecond... | [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.0. | [
"Example: Configuring Automatic VLAN Administration Using MVRP on MX Series Routers",
"Example: Configuring Automatic VLAN Administration Using MVRP on EX Series Switches",
"Example: Configuring Automatic VLAN Administration Using MVRP on EX Series Switches with ELS",
"Support",
"Configuring Multiple VLAN R... |
n391 | n391 number; | [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options] | For link services interfaces only, set the Frame Relay full status polling interval. | [
{
"name": "number",
"desc": "Polling interval."
}
] | 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"
] |
n392 | n392 number; | [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options] | For link services interfaces only, set the Frame Relay error threshold, in number of errors. | [
{
"name": "number",
"desc": "Error threshold."
}
] | 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"
] |
n393 | n393 number; | [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options] | For link services interfaces only, set the Frame Relay monitored event count. | [
{
"name": "number",
"desc": "Event count."
}
] | 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"
] |
n-plus-n (Power Management) | n-plus-n; | [edit chassis psu redundancy] | Configure N+N power supply redundancy for power management on an EX6200 or EX8200 switch. | [] | 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. | [
"Configuring Power Supply Redundancy (CLI Procedure)"
] |
n-plus-n (satellite-management) | n-plus-n | [edit chassis satellite-management psu redundancy] | Configure N+N power supply redundancy for the satellite devices in a Junos Fusion. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1. | [
"Understanding Power over Ethernet in a Junos Fusion"
] |
name (early-aging) | name; | [edit security flow aging early-aging application] | Application name - Allows configuration cutoff time based on application. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | This statement is introduced in Junos OS Release 23.4R1. | [] |
name (L2TP Destination) | name destination-name {
drain;
} | [edit services l2tp destination] | Specify the name of the L2TP destination for the tunnel. | [
{
"name": "destination-name",
"desc": "Locally assigned name of the tunnel destination."
}
] | 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"
] |
name (L2TP Tunnel Destination) | name name {
address ip-address {
drain;
routing-instance routing-instance-name {
drain;
}
}
drain;
} | [edit services l2tp tunnel] | Specify the local name and other attributes of the L2TP tunnel. | [
{
"name": "name",
"desc": "Locally assigned name of the tunnel; in the format destination-name/tunnel-name or tunnel-name."
}
] | 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"
] |
name (Next Gen Services Global System Logging) | name; | [edit services rtlog traceoptions flag] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "all",
"desc": "Everything"
},
{
"name": "configuration",
"desc": "Reading of configuration"
},
{
"name": "hpl",
"desc": "Trace HPL logging"
},
{
"name": "report",
"desc": "Trace report"
},
{
"name": "source",
"desc": "Communication with security log... | 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"
] |
name (SNMP) | name name; | [edit snmp] | Set the system name from the command-line interface. | [
{
"name": "name",
"desc": "System name override."
}
] | 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 a Different System Name"
] |
name (Transport-class) | nametc-name {
tunnel-egress {
end-point address;
}
} | [edit logical-systems name routing-instances name routing-options transport-class],
[edit logical-systems name routing-options transport-class],
[edit logical-systems name tenants name routing-instances name routing-options transport-class],
[edit routing-instances name routing-options transport-class],
[edit routing-o... | Configure a tunnel end-point to advertise in BGP CT family, which installs a static route in the tc-
<n>.inet.3 RIB routing table. Originating BGP-CT routes at the egress-node allows downstream border
nodes to recognize them as redundant path to the same PE. | [
{
"name": "tunnel-egress",
"desc": "Specify egress tunnel endpoint origination."
},
{
"name": "endpoint-addr",
"desc": "Specify the address of the endpoint of the egress tunnel."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1 | [
"BGP Classful Transport Planes Overview"
] |
name-format (Flow Collection) | name-format “format”; | [edit services flow-collector file-specification variant variant-number] | Specify the name format for a specific file format. The files can include supported macros. Use macros to
organize files on the external machine to which they are exported from the collector PIC. | [
{
"name": "format",
"desc": "Specify the filename format, within quotation marks. The name format can include the following"
},
{
"name": "macros, typed in braces:",
"desc": ""
},
{
"name": "{%D}",
"desc": "Date"
},
{
"name": "{%T)",
"desc": "Time when the file is created... | 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 File Formats"
] |
name-format | name-format (character-string | none | dns | mac+2oct); | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name] | Specify the format of the maintenance domain name. | [
{
"name": "character-string",
"desc": "The name is an ASCII character string."
},
{
"name": "none",
"desc": "The maintenance domain name is not used."
},
{
"name": "dns",
"desc": "The name is in domain name service (DNS) format. For example: www.juniper.net."
},
{
"name": "ma... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [
"Creating a Maintenance Association",
"Creating a Maintenance Domain"
] |
name-server (Access) | name-server address | [edit access address-assignment pool name family (inet | inet6) dhcp-attributes] | Specify the DNS server IP address for an address-assignment pool. | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"address-assignment (Access)"
] |
name-server (System Services) | name-server {
address {
routing-instance mgmt_junos;
}
} | [edit system],
[edit system services dhcp],
[edit system services dhcp pool subnet-address],
[edit system services dhcp static-binding mac-address] | Configure one or more Domain Name System (DNS) name servers. | [
{
"name": "address",
"desc": "Address of the name server. To configure multiple name servers, include a maximum of three address options. The system uses only the first three configured addresses even if you configure additional addresses."
},
{
"name": "routing-instance mgmt_junos",
"desc": "Co... | 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.
routing-instance option introduced in Junos OS Release 19.2R1 and Junos OS Evolved Release 20.1R1
under the [edit system] hierarchy level only. | [
"Configure a DNS Name Server for Resolving Hostnames into Addresses"
] |
nas-ip-address | nas-ip-address {
equals value;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from] | Specify the RADIUS AVP NAS-IP-Address for the incoming RADIUS request from the subscriber.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selected.
The remaining statement is explained separately. See... | [] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
nas-port-extended-format (Interfaces) | nas-port-extended-format {
adapter-width bits;
ae-width bits;
port-width bits;
slot-width bits;
stacked;
stacked-vlan-width bits;
vci-width bits:
vlan-width bits;
vpi-width bits;
} | [edit interfaces interface-name radius-options nas-port-options nas-port-options-name] | Configure the RADIUS client to use the extended format for RADIUS attribute 5 (NAS-Port) and specify
the width in bits of the fields in the NAS-Port attribute. | [
{
"name": "adapter-width width",
"desc": "Number of bits in the adapter field."
},
{
"name": "ae-width width",
"desc": "Number of bits in the aggregated Ethernet identifier field."
},
{
"name": "port-width width",
"desc": "Number of bits in the port field."
},
{
"name": "slot... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Options vci-width and vpi-width introduced in Junos OS Release 12.3R3 and supported in later 12.3Rx
releases.
Options vci-width and vpi-width supported in Junos OS Release 13.2 and later releases. (Not supported in
Junos OS Release 13.1.) | [
"Configuring RADIUS NAS-Port Options for Subscriber Access per Physical Interface, VLAN, or",
"Stacked VLAN",
"Guidelines for Configuring RADIUS NAS-Port Options for Subscriber Access per Physical Interface,",
"VLAN, or Stacked VLAN"
] |
nas-port-extended-format | nas-port-extended-format {
adapter-width bits;
ae-width bits;
atm {
adapter-width bits;
port-width bits;
slot-width bits;
vci-width bits;
vpi-width bits;
}
port-width bits;
pw-width bits;
slot-width bits;
stacked-vlan-width bits;
vlan-width bi... | [edit access profile profile-name radius options] | Configure the RADIUS client to use the extended format for RADIUS attribute 5 (NAS-Port) and specify
the width in bits of the fields in the NAS-Port attribute.
The NAS-Port attribute specifies the physical port number of the NAS that is authenticating the user,
and is formed by a combination of the physical port’s slot... | [
{
"name": "adapter-width width",
"desc": "Number of bits in the adapter field."
},
{
"name": "ae-width width",
"desc": "(Ethernet subscribers only) Number of bits in the aggregated Ethernet identifier field."
},
{
"name": "atm",
"desc": "Specify width for fields for ATM subscribers."... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
ae-width option added in Junos OS Release 12.1.
atm option added in Junos OS Release 12.3R3 and supported in later 12.3Rx releases.
atm option supported in Junos OS Release 13.2 and later releases. (Not supported in Junos OS Release
13.1.)
pw-width option added in Junos OS ... | [
"RADIUS Servers and Parameters for Subscriber Access"
] |
nas-port-id-format (Subscriber Management) | nas-port-id-format {
agent-circuit-id;
agent-remote-id;
concatenated-vlan-tags (fixed-size-inner-tag | fixed-size-outer-tag)
interface-description;
interface-text-description;
nas-identifier;
order (agent-circuit-id | agent-remote-id | interface-description | interface-text-
description | na... | [edit access profile profile-name radius options] | Specify the optional information that the router includes in the NAS-Port-ID (RADIUS attribute 87) that
is passed to the RADIUS server during authentication and accounting. You can include any combination
of the optional values.
When you specify the values for the NAS-Port-ID, you can configure the values to appear in ... | [
{
"name": "agent-circuit-id",
"desc": "Include the agent circuit ID from either DHCP option 82 or the DSL forum VSAs."
},
{
"name": "agent-remote-id",
"desc": "Include the agent remote ID from either DHCP option 82 or the DSL forum VSAs."
},
{
"name": "concatenated-vlan-tags",
"desc"... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
Options interface-text-description, order, and postpend-vlan-tags introduced in Junos OS Release 15.1. | [
"Configuring Access Profile Options for Interactions with RADIUS Servers",
"Configuring a NAS-Port-ID with Additional Options",
"RADIUS Servers and Parameters for Subscriber Access"
] |
nas-port-method (L2TP LAC) | nas-port-method cisco-avp; | [edit services l2tp tunnel] | Globally configure the LAC to interoperate with Cisco LNS devices by including the Cisco NAS Port Info
AVP (100) in the ICRQ to the LNS. This AVP conveys the physical NAS port number identifier and the
type of the physical port, such as Ethernet or ATM.
NOTE: This global configuration can be overridden by the configura... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"L2TP LAC Subscriber Configuration",
"L2TP LAC Tunneling for Subscribers",
"L2TP LAC Subscriber Configuration"
] |
nas-port-method (Tunnel Profile) | nas-port-method cisco-avp; | [edit access tunnel-profile profile-name tunnel tunnel-id] | Configure the LAC to interoperate with Cisco LNS devices by including the Cisco NAS Port Info AVP
(100) in the ICRQ to the LNS. This AVP conveys the physical NAS port number identifier and the type of
the physical port, such as Ethernet or ATM. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"L2TP LAC Tunneling for Subscribers"
] |
nas-port-options (RADIUS Options) | nas-port-options nas-port-options-name {
nas-port-extended-format {
adapter-width width;
ae-width width;
port-width width;
slot-width width;
stacked;
stacked-vlan-width width;
vci-width width:
vlan-width width;
vpi-width width;
}
nas-po... | [edit interfaces interface-name radius-options] | Create a NAS-Port options definition to configure the NAS-Port-Type (61) RADIUS IETF attribute, and
an extended format for the NAS-Port (5) RADIUS IETF attribute, on a per-physical interface, per-VLAN,
or per-stacked VLAN (S-VLAN) basis. Each NAS-Port options definition includes the NAS-Port extended
format, the NAS-Po... | [
{
"name": "nas-port-options-name",
"desc": "Name of the NAS-Port options definition. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring RADIUS NAS-Port Options for Subscriber Access per Physical Interface, VLAN, or",
"Stacked VLAN",
"Guidelines for Configuring RADIUS NAS-Port Options for Subscriber Access per Physical Interface,",
"VLAN, or Stacked VLAN"
] |
nas-port-type (RADIUS Options) | nas-port-type port-type; | [edit interfaces interface-name radius-options nas-port-options nas-port-options-name] | Specify the port type used to authenticate subscribers. The router includes the port type in the NAS-
Port-Type (61) RADIUS IETF attribute.
Default
If you do not include the nas-port-type statement at the [edit interfaces interface-name radius-options nas-
port-options nas-port-options-name] hierarchy level, the global... | [
{
"name": "port-type",
"desc": "One of the following port types:"
},
{
"name": "value",
"desc": "A value from 0 through 65535"
},
{
"name": "adsl-cap",
"desc": "Asymmetric DSL, carrierless amplitude phase (CAP) modulation"
},
{
"name": "adsl-dmt",
"desc": "Asymmetric DSL,... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring RADIUS NAS-Port Options for Subscriber Access per Physical Interface, VLAN, or",
"Stacked VLAN",
"Guidelines for Configuring RADIUS NAS-Port Options for Subscriber Access per Physical Interface,",
"VLAN, or Stacked VLAN"
] |
nas-port-type (Subscriber Management) | nas-port-type {
ethernet {
port-type;
}
} | [edit access profile profile-name radius options] | Specify the port type used to authenticate subscribers. The router includes the port type in RADIUS
attribute 61 (NAS-Port-Type attribute).
NOTE: This statement is ignored if the ethernet-port-type-virtual statement is included in
the same access profile.
Default
The router uses a port type of ethernet. | [
{
"name": "port-type",
"desc": "One of the following port types:"
},
{
"name": "value",
"desc": "A value from 0-65535"
},
{
"name": "adsl-cap",
"desc": "Asymmetric DSL, carrierless amplitude phase (CAP) modulation"
},
{
"name": "adsl-dmt",
"desc": "Asymmetric DSL, discret... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Configuring Access Profile Options for Interactions with RADIUS Servers",
"RADIUS Servers and Parameters for Subscriber Access"
] |
nas-port-type | nas-port-type {
ethernet (ethernet);
} | [edit access profile name radius options] | RADIUS is an authentication method for validating users trying to access the device using Telnet. Using
the nas-port-type configuration statement, you can define the type of physical port to authenticate the
user. | [
{
"name": "ethernet",
"desc": "Translation mechanism for changing the Ethernet value. Values:"
},
{
"name": "ethernet",
"desc": "Configure the NAS port type as Ethernet"
}
] | access—To view this statement in the configuration. | Statement introduced in Junos OS Release 15.1X49-D110. | [] |
nasreq (Diameter Application) | nasreq
max-outstanding-requests number;
partition partition-name {
destination-host hostname;
destination-realm realm-name;
diameter-instance master;
}
request-retry retries;
timeout seconds;
} | [edit access] | Specify the destination and transmission parameters for the Diameter Network Access Server
Requirements (NASREQ) protocol.
NASREQ is a Diameter-based authentication and authorization protocol. The NASREQ client has two
queues, the transmit queue and response queue. The transmit queue stores outbound packets until sent
... | [
{
"name": "number",
"desc": "Maximum number of requests that the NASREQ client sends to Diameter. Range: 20 through 100"
},
{
"name": "retries",
"desc": "Number of times to re-send a timeout request to Diameter after the initial request. This value applies only to requests in the response queue... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Diameter Network Access Server Application (NASREQ)",
"Configuring the Diameter Network Access Server Application (NASREQ)"
] |
nat | nat {
destination {
pool pool-name {
address ip-address {
(port port-number | to ip-address);
}
description text;
routing-instance routing-instance-name;
}
rule-set rule-set-name {
description text;
from ... | [edit 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": "destination",
"desc": "Configure Destination NAT."
},
{
"name": "natv6v4",
"desc": "Configure NAT between IPv6 and IPv4 options."
},
{
"name": "no-v6-frag-header",
"desc": "Configure to disable adding fragment header in non-fragmented IPv6 packets when performing IPv4 to I... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6.
The description option added in Junos OS Release 12.1.
The tenant option is introduced in Junos OS Release 18.3R1.
The radius-accounting and subscriber-extension options are introduced in Junnos OS Release 24.2R1. | [
"Introduction to NAT",
"Understanding Logical Systems Network Address Translation"
] |
nat-cone-binding | nat-cone-binding {
maximum maximum;
reserved reserved;
} | [edit system security-profile] | Specify the number of NAT cone binding configurations that user logical system administrators and
primary logical system administrators can configure for their logical systems if the security profile is
bound to the logical systems.
The primary administrator:
•
uses security profiles to provision logical systems with r... | [
{
"name": "maximum",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its reserved amount allows it can utilize resources configured for the global maximum amount if they are"
},
{
"name": "available",
"desc": "that is, if they are not allocated to other log... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Introduction to NAT"
] |
nat-destination-pool | nat-destination-pool {
maximum maximum;
reserved reserved;
} | [edit system security-profile],
[edit tenants tenant-name security-profile] | Specify the number of NAT destination pool configurations that user logical system administrators and
primary logical system administrators can configure for their logical systems if the security profile is
bound to the logical systems.
The primary administrator:
•
uses security profiles to provision logical systems wi... | [
{
"name": "maximum",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its reserved amount allows it can utilize resources configured for the global maximum amount if they are"
},
{
"name": "available",
"desc": "that is, if they are not allocated to other log... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2.
The tenant option is introduced in Junos OS Release 18.3R1. | [
"Introduction to NAT"
] |
nat-destination-rule | nat-destination-rule {
maximum maximum;
reserved reserved;
} | [edit system security-profile],
[edit tenants tenant-name system security-profile] | Specify the number of NAT destination rule configurations that user logical system administrators and
primary logical system administrators can configure for their logical systems if the security profile is
bound to the logical systems.
The primary administrator:
•
uses security profiles to provision logical systems wi... | [
{
"name": "maximum",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its reserved amount allows it can utilize resources configured for the global maximum amount if they are"
},
{
"name": "available",
"desc": "that is, if they are not allocated to other log... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2.
The tenant option is introduced in Junos OS Release 18.3R1. | [
"Introduction to NAT"
] |
nat-interface-port-ol (System) | nat-interface-port-ol {
maximum maximum;
reserved reserved;
} | [edit system security-profile] | Specify the security NAT interface port overloading the quota of a logical system. | [
{
"name": "maximum amount",
"desc": "Specify the maximum allowed quota value. Range: 0 through 64"
},
{
"name": "reserved amount",
"desc": "Specify a reserved quota value that guarantees that the resource amount specified is always available to the logical system. Default: 0"
}
] | 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. | [
"Introduction to NAT"
] |
nat-keepalive (Services IPsec VPN) | nat-keepalive seconds; | [edit services service-set service-set-name ipsec-vpn-options] | Specify the interval at which NAT keepalive packets can be sent so that NAT translation continues. | [
{
"name": "seconds",
"desc": "Maximum interval in seconds at which NAT keepalive packets can be sent."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.4. | [
"Configuring Junos VPN Site Secure or IPSec VPN"
] |
nat-nopat-address | nat-nopat-address {
maximum maximum;
reserved reserved;
} | [edit system security-profile] | Specify the number of NAT without port address translation configurations that user logical system
administrators and primary logical system administrators can configure for their logical systems if the
security profile is bound to the logical systems.
The primary administrator:
•
uses security profiles to provision lo... | [
{
"name": "maximum",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its reserved amount allows it can utilize resources configured for the global maximum amount if they are"
},
{
"name": "available",
"desc": "that is, if they are not allocated to other log... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Introduction to NAT"
] |
nat-options (Next Gen Services) | nat-options {
nptv6 {
icmpv6-error-messages;
}
} | [edit services service-set service-set-name] | Send ICMP error messages if NPTv6 address translation fails. | [] | 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. | [] |
nat-options | nat-options {
land-attack-check (ip-only | ip-port);
max-sessions-per-subscriber session-number;
stateful-nat64 {
clear-dont-fragment-bit;
}
} | [edit services service-set service-set-name] | Specify parameters for NAT operation. | [] | 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.
land-attack-check and max-sessions-per-subscriber statements added in 13.3. | [
"Configuring Service Rules"
] |
nat-outside-interface | nat-outside-interface; | [edit interfaces name unit name family inet] | Public interface used for NAT. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [] |
nat-pat-address | nat-pat-address {
maximum maximum;
reserved reserved;
} | [edit system security-profile] | Specify the number of NAT with port address translation (PAT) configurations that user logical system
administrators and primary logical system administrators can configure for their logical systems if the
security profile is bound to the logical systems.
The primary administrator:
•
uses security profiles to provision... | [
{
"name": "maximum",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its reserved amount allows it can utilize resources configured for the global maximum amount if they are"
},
{
"name": "available",
"desc": "that is, if they are not allocated to other log... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Understanding Logical Systems Network Address Translation",
"Introduction to NAT"
] |
nat-pat-portnum | nat-pat-portnum {
maximum maximum;
reserved reserved;
} | [edit system security-profile] | Specify the maximum quantity and the reserved quantity of ports for the logical system as part of its
security profile. The total number of PAT pools must not exceed the configured maximum ports for the
logical system. | [
{
"name": "maximum",
"desc": "Specify the maximum number of ports allowed for a logical system. The maximum quantity is not guaranteed and is shared among multiple logical systems. Range: 0 through 134217728"
},
{
"name": "reserved",
"desc": "Specify the number of resources guaranteed for a log... | system—To view this statement in the configuration.
system—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Understanding Logical Systems for SRX Series Services Gateways"
] |
nat-port-ol-ipnumber | nat-port-ol-ipnumber {
maximum maximum;
reserved reserved;
} | [edit system security-profile] | Specify the number of NAT port overloading IP number configurations that user logical system
administrators and primary logical system administrators can configure for their logical systems if the
security profile is bound to the logical systems.
The primary administrator:
•
uses security profiles to provision logical ... | [
{
"name": "maximum",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its reserved amount allows, it can utilize resources configured for the global maximum amount if they are"
},
{
"name": "available",
"desc": "that is, if they are not allocated to other lo... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Understanding Logical Systems for SRX Series Services Gateways"
] |
nat-rule-referenced-prefix (System) | nat-rule-referenced-prefix {
maximum maximum;
reserved reserved;
} | [edit system security-profile] | Specify the security NAT rule referenced IP prefix quota of a logical system. | [
{
"name": "maximum",
"desc": "Specify the maximum allowed quota value. Range: 0 through 1048576"
},
{
"name": "reserved",
"desc": "Specify a reserved quota value that guarantees that the resource amount specified is always available to the logical system. Default: 0"
}
] | 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. | [
"Understanding Logical Systems for SRX Series Services Gateways"
] |
nat-rule-sets (Service Set Next Gen Services) | nat-rule-sets rule-set-name; | [edit services service-set service-set-name] | Specify the NAT rules set included in the service set. | [] | 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. | [] |
nat-rule-sets (Service Set) | nat-rule-sets rule-set-name; | [edit services service-set service-set-name] | Specify the Network Address Translation (NAT) rule set included in the service set. You can configure
only one NAT rule set. If you specify a NAT rule set, you cannot specify a NAT rule. | [
{
"name": "rule-set-name",
"desc": "Name of the NAT rule set."
}
] | 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. | [
"Applying Services to Subscriber-Aware Traffic with a Service Set"
] |
nat-rules | (nat-rules rule-name | nat-rule-sets rule-set-name); | [edit services service-set service-set-name] | Specify the Network Address Translation (NAT) rules or rule set included in this service set. You can
configure multiple rules, but only one rule set for each service. | [
{
"name": "rule-name",
"desc": "Identifier for the collection of terms that constitute this rule."
},
{
"name": "rule-set-name",
"desc": "Identifier for the set of rules to be included."
}
] | 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 Service Rules",
"Applying Services to Subscriber-Aware Traffic with a Service Set"
] |
nat-source-pool | nat-source-pool {
maximum maximum;
reserved reserved;
} | [edit system security-profile],
[edit tenants tenant-name system security-profile] | Specify the NAT source pool configurations that user logical system administrators and primary logical
system administrators can configure for their logical systems if the security profile is bound to the logical
systems.
The primary administrator:
•
uses security profiles to provision logical systems with resources.
... | [
{
"name": "maximum",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its reserved amount allows, it can utilize resources configured for the global maximum amount if they are"
},
{
"name": "available",
"desc": "that is, if they are not allocated to other lo... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2.
The tenant option is introduced in Junos OS Release 18.3R1. | [
"Understanding Logical Systems for SRX Series Services Gateways"
] |
nat-source-rule | nat-source-rule {
maximum maximum;
reserved reserved;
} | [edit system security-profile],
[edit tenants tenant-name system security-profile] | Specify the NAT source rule configurations that user logical system administrators and primary logical
system administrators can configure for their logical systems if the security profile is bound to the logical
systems.
The primary administrator:
•
uses security profiles to provision logical systems with resources.
•... | [
{
"name": "maximum",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its reserved amount allows it can utilize resources configured for the global maximum amount if they are"
},
{
"name": "available",
"desc": "that is, if they are not allocated to other log... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2.
The tenant option is introduced in Junos OS Release 18.3R1. | [
"Understanding Logical Systems for SRX Series Services Gateways"
] |
nat-static-rule | nat-static-rule {
maximum maximum;
reserved reserved;
} | [edit system security-profile],
[edit tenants tenant-name system security-profile] | Specify the number of NAT static rule configurations that user logical system administrators and primary
logical system administrators can configure for their logical systems if the security profile is bound to the
logical systems.
The primary administrator:
•
uses security profiles to provision logical systems with re... | [
{
"name": "maximum",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its reserved amount allows it can utilize resources configured for the global maximum amount if they are"
},
{
"name": "available",
"desc": "that is, if they are not allocated to other log... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2.
The tenant option is introduced in Junos OS Release 18.3R1. | [
"Understanding Logical Systems for SRX Series Services Gateways"
] |
nat-translated-dip | nat-translated-dip nat-translated-dip; | [edit firewall family inet filter name term name then] | IPv4 destination address used for Static NAT | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [] |
nat-translated-dstport | nat-translated-dstport nat-translated-dstport; | [edit firewall family inet filter name term name then] | The UDP or TCP destination port used for static NAT. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [] |
nat-translated-sip | nat-translated-sip nat-translated-sip; | [edit firewall family inet filter name term name then] | IPv4 source address used for Static NAT. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [] |
nat-translated-srcport | nat-translated-srcport nat-translated-srcport; | [edit firewall family inet filter name term name then] | The UDP or TCP source port used for static NAT. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [] |
native-vlan-id | native-vlan-id vlan-id; | For platforms without ELS:
[edit interfaces interface-name unit 0 family ethernet-switching]
For MX Series routers and platforms with ELS:
[edit interfaces interface-name] | Configure the VLAN identifier to associate untagged packets received on a trunk interface.
You must configure a logical interface with the VLAN ID that is same as the native VLAN ID confiured
on the interface, to receive the untagged packets on the interface.
To configure the logical interface, include the vlan-id sta... | [
{
"name": "vlan-id",
"desc": "Numeric identifier of the VLAN."
},
{
"name": "number",
"desc": "VLAN ID number."
}
] | 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 8.3.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Metro Routers. | [
"Configuring Gigabit Ethernet Interfaces (CLI Procedure)",
"Configuring Gigabit Ethernet Interfaces (J-Web Procedure)",
"Understanding Bridging and VLANs on Switches",
"Enabling VLAN Tagging",
"Configuring Access Mode on a Logical Interface",
"Configuring the Native VLAN Identifier on Switches With ELS Su... |
natt-install-interval | natt-install-interval seconds ; | [edit services ipsec-vpn rule rule-name term term-name then dynamic] | Specify the duration of delay in installing IPSec SA in a NAT-T scenario soon after the IPSec SA
negotiation is complete. The default value is 0 seconds. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.2. | [] |
ncp-max-conf-req | ncp-max-conf-req number | [edit interfaces so-fpc/pic/port unit number ppp-options] | Set the maximum number of NCP Configure-Requests to be sent, after which the router goes to NCP
down state. | [
{
"name": "number",
"desc": "Ranges from 0 to 65535, where 0 means send infinite NCP Configure-Requests and any other value specifies the maximum number NCP Configure-Requests to send and then stop sending. Default Range: 0 through 65,535"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configuring PPP"
] |
ncp-restart-timer | ncp-restart-timer milliseconds; | [edit interfaces interface-name unit logical-unit-number ppp-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number ppp-
options] | For interfaces with PPP and PPP TCC encapsulations and on multilink PPP bundle interfaces, configure a
restart timer for the Network Control Protocol (NCP) component of a PPP session. | [
{
"name": "milliseconds",
"desc": "The time in milliseconds between successive NCP configuration requests."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Configuring PPP"
] |
nd6-max-cache | nd6-max-cache nd6-max-cache; | [edit interfaces interface-name unit logical-unit-number family inet6] | Specify the maximum number of entries that can be added to the Neighbor Discovery Protocol (NDP)
IPv6 neighbor discovery cache for an interface. When this maximum is reached, no new entries are
allowed.
Default
•
100,000 for M Series and PTX Series.
•
75,000 for MX Series and QFX Series.
•
20,000 for EX Series. | [
{
"name": "nd6-max-cache",
"desc": "Maximum size of the neighbor discovery next-hop cache for an interface. Range: 1 through 2,000,000 for MX Series, PTX Series or QFX Series. Range: 1 through 700,000 for M Series."
}
] | 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. | [
"Configuring Neighbor Discovery Cache Protection",
"Example: Configuring Neighbor Discovery Cache Protection to Prevent Denial-of-Service Attacks",
"IPv6 Neighbor Discovery Overview"
] |
nd6-new-hold-limit | nd6-new-hold-limit nd6-new-hold-limit; | [edit interfaces interface-name unit logical-unit-number family inet6] | Specify the maximum number of entries for unresolved next-hop addresses that can be added to the
Neighbor Discovery Protocol (NDP) IPv6 neighbor discovery cache for an interface.
Default
•
100,000 for M Series.
•
75,000 for MX Series and QFX Series.
•
20,000 for EX Series. | [
{
"name": "nd6-new-hold-limit",
"desc": "Maximum number of new unresolved next-hop addresses that can be added to the IPv6 neighbor discovery cache. Range: 1 through 2,000,000"
}
] | 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. | [
"Configuring Neighbor Discovery Cache Protection",
"Example: Configuring Neighbor Discovery Cache Protection to Prevent Denial-of-Service Attacks",
"IPv6 Neighbor Discovery Overview",
"nd6-stale-time"
] |
nd6-stale-time | nd6-stale-time seconds; | [edit interfaces interface-name unit logical-unit-number family inet6] | Set the stale timer for IPv6 neighbor reachability confirmation. Reachability of the IPv6 neighbors is
confirmed only after the stale timer has expired. For example, by setting the stale timer to 180 seconds,
users can specify that IPv6 neighbor reachability be confirmed every 180 seconds.
NOTE: When the Routing Engine... | [
{
"name": "seconds",
"desc": "Duration in seconds. Range: 1 to 18000"
}
] | 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. | [
"IPv6 Neighbor Discovery Overview"
] |
nd-maxucast-retry | nd-maxucast-retry count | [edit system] | Configures how many times the device attempts to reach the IPv6 neighbor entries.
Default
The default number of retry attempts is 3. | [
{
"name": "count",
"desc": "Indicates the maximum number of retries for unicast neighbor solicitation."
}
] | admin-control | Statement introduced in Junos OS Evolved Release 19.4R1. | [
"Example: Configuring ARP Cache Protection"
] |
nd-override-preferred-src | nd-override-preferred-src; | [edit system] | Configure the router to override the default configuration and use the appropriate address based on
destination address scope for the source address for Neighbor Solicitation/Neighbor Advertisement
(NS/NA) for unnumbered interfaces.
Default
The router uses the preferred source address, if configured, as source for NS/N... | [] | 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 | [] |
nd-retransmit-timer | nd-retransmit-timer milliseconds; | [edit system] | Set the retransmit timer for neighbor discovery messages. Whenever the state of a neighbor during the
Neighbor Discovery (ND) process changes from stale to probe, the value of the retransmit timer controls
the interval between the neighbor solicitation messages that are sent out. Also, the retransmit timer
controls the... | [
{
"name": "milliseconds",
"desc": "Retransmission frequency."
}
] | 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. | [
"Using NDRA to Provide IPv6 WAN Link Addressing Overview"
] |
nd-system-cache-limit | nd-system-cache-limit number; | [edit system] | Specify the maximum system cache size for IPv6 next-hop addresses. This limit enforces a systemwide
cap on the neighbor discovery cache entries for all interfaces, including the loopback interface for the
internal routing instance, management interfaces, and the public interfaces.
Default
100,000 | [
{
"name": "number",
"desc": "Maximum system cache size for IPv6 next-hop addresses. Range: 200 through 2,000,000"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Example: Configuring Neighbor Discovery Cache Protection to Prevent Denial-of-Service Attacks"
] |
ndp | ndp name {
mac mac;
multicast-mac multicast-mac;
l2-interface l2-interface;
publish (mac mac | multicast-mac multicast-mac;
} | [edit dynamic-profiles name interfaces name unit name family inet6 address],
[edit dynamic-profiles name logical-systems name interfaces name unit name family inet6 address],
[edit interfaces name unit name family inet6 address] | Configures static Neighbor Discovery Protocol (NDP) entries. | [
{
"name": "name",
"desc": "Specify the destination IP address."
},
{
"name": "mac",
"desc": "Specify the MAC address."
},
{
"name": "multicast-mac",
"desc": "Specify the multicast MAC address."
},
{
"name": "l2-interface",
"desc": "Specify the Layer 2 interface name for N... | interface | [] | |
ndp-proxy | ndp-proxy {
interface-restricted;
interface-unrestricted;
} | [edit dynamic-profiles name interfaces name unit name family inet6],
[edit dynamic-profiles name logical-systems name interfaces name unit name family inet6],
[edit interfaces name unit name family inet6] | Enable NDP proxy on interface | [
{
"name": "interface-restricted",
"desc": "Enable NDP interface proxy restricted to interface"
},
{
"name": "interface-unrestricted",
"desc": "Enable NDP interface proxy unrestricted to interface"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1
Option interface-unrestricted introduced in Junos OS Release 22.1R1 (on SRX Series and vSRX Virtual
Firewall 3.0 platform).
NOTE: You cannot configure both interface restricted and interface unrestricted modes
on the same interface simultaneously. | [] |
negate | negate; | [edit security idp custom-attack attack-name attack-type signature] | Select negate to exclude the specified pattern from being matched. | [] | 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. | [] |
negotiate-address | negotiate-address; | [edit interfaces interface-name unit logical-unit-number family inet],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet] | For interfaces with PPP encapsulation, enable the interface to be assigned an IP address by the remote
end. | [] | 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 IPCP Options for Interfaces with PPP Encapsulation",
"Junos OS Administration Library for Routing Devices"
] |
negotiation-options | negotiation-options {
allow-remote-loopback;
no-allow-link-events;
} | [edit protocols oam ethernet link-fault-management
interface interface-name] | Enable and disable IEEE 802.3ah Operation, Administration, and Maintenance (OAM) link fault
management (LFM) features for Ethernet interfaces.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Configuring Ethernet OAM Link Fault Management"
] |
neighbor (Define ANCP) | neighbor ip-address {
adjacency-loss-hold-time seconds;
adjacency-timer;
auto-configure-trigger interface interface-name;
ietf-mode;
maximum-discovery-table-entries entry-number;
pre-ietf-mode;
} | [edit protocols ancp] | Configure an ANCP neighbor with which the ANCP agent on the router forms an adjacency for
reporting and shaping traffic. | [
{
"name": "ip-address",
"desc": "IP address of the ANCP neighbor."
}
] | 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",
"Configuring ANCP Neighbors"
] |
neighbor (Protocols BGP) | neighbor address {
accept-remote-nexthop;
advertise-bgp-static
advertise-external <conditional>;
advertise-inactive;
(advertise-peer-as | no-advertise-peer-as);
as-override;
authentication-algorithm algorithm;
authentication-key key;
authentication-key-chain key-chain;
cluster cl... | [edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp
group group-name],
[edit protocols bgp group group-name],
[edit protocols bgp family prefix-limit (inet | inet6)(any | flow | labeled-unicast | mult... | 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": "address",
"desc": "IPv6 or IPv4 address of a single peer. When you configure the BGP neighbors, use the PPPoE"
}
] | 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. | [
"BGP User Guide"
] |
neighbor (Protocols Layer 2 Circuit) | neighbor address {
interface interface-name {
backup-neighbor address {
community name;
hot-standby;
psn-tunnel-endpoint address;
standby;
virtual-circuit-id number;
}
bandwidth (bandwidth | ctnumber bandwidth);
community c... | [edit logical-systems logical-system-name protocols l2circuit],
[edit protocols l2circuit] | Each Layer 2 circuit is represented by the logical interface connecting the local provider edge (PE) router
or switch to the local customer edge (CE) router or switch. All the Layer 2 circuits using a particular
remote PE router or switch designated for remote CE routers or switches are listed under the neighbor
statem... | [
{
"name": "address",
"desc": "IP address of a neighboring router or switch."
}
] | 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 Neighbor Interface for the Layer 2 Circuit"
] |
neighbor (Protocols LDP) | neighbor neighbor-address; | [edit protocols ldp] | Configure an LDP targeted neighbor.
LDP sends a targeted hello message to the configured remote neighbor with a targeted request-send-
targeted hello message (T) bit set. If the remote neighbor allows receipt of asymmetric hello messages,
or if it is configured with the source address as the targeted neighbor, it respo... | [
{
"name": "neighbor-address",
"desc": "IP address of the remote LDP neighbor."
}
] | routing | Statement introduced before Junos OS Release 14.2R1. | [
"Minimum LDP Configuration",
"Enabling and Disabling LDP"
] |
neighbor (Protocols RIPng) | neighbor neighbor-name {
import [ policy-names ];
metric-in metric;
receive <none>;
route-timeout seconds;
send <none>;
update-interval seconds;
} | [edit logical-systems logical-system-name protocols ripng group group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ripng group group-name],
[edit protocols ripng group group-name],
[edit routing-instances routing-instance-name protocols ripng group group-name] | Configure neighbor-specific RIPng parameters, thereby overriding the defaults set for the routing device. | [
{
"name": "neighbor-name",
"desc": "Name of an interface over which a routing device communicates to its neighbors."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for routing instances introduced in Junos OS Release 9.0. | [] |
neighbor (Protocols VPLS) | neighbor neighbor-id {
mac-pinning;
associate-profile{
dynamic-profile-name;
profile-variable-set profile-variable-set-name;
}
backup-neighbor {...}
community community-name;
connection-protection;
encapsulation-type type;
ignore-encapsulation-mismatch;
oam {
... | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls],
[edit routing-instances routing-instance-name protocols vpls] | Specify each of the PE routers participating in the VPLS domain. Configuring this statement enables LDP
for signaling VPLS.
NOTE: In the VPLS documentation, the word router in terms such as PE router is used to
refer to any device that provides routing functions. | [
{
"name": "neighbor-id",
"desc": "Specify the neighbor identifier for each PE router participating in the VPLS domain."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
The pseudowire-status-tlv option was added in Junos OS Release 10.0.
The vpls-id-list option was added in Junos OS Release 14.2 for MX Series routers to provide support for
multiple pseudowires between the same pair of PEs in LDP-VPLS. | [
"Configuring LDP Signaling for VPLS"
] |
neighbor | neighbor neighbor-name {
authentication-key password;
authentication-type type;
bfd-liveness-detection {
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
... | [edit logical-systems logical-system-name protocols rip group group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols rip
group group-name],
[edit protocols rip group group-name],
[edit routing-instances routing-instance-name protocols rip group group-name] | Configure neighbor-specific RIP parameters, thereby overriding the defaults set for the routing device. | [
{
"name": "neighbor-name",
"desc": "Name of an interface over which a routing device communicates to its neighbors."
}
] | 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. | [] |
neighbor-discovery | neighbor-discovery
dad-proxy {
no-proxy-on-resolve;
}
ndp-proxy {
no-proxy-on-resolve;
proxy-force-resolve;
}
no-dad-on-state-change;
onlink-subnet-only;
secure {
security-level {
(default | secure-messages-only);
}
cryptographic-address {
key-length n... | [edit protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "dad-proxy",
"desc": "Configure DAD proxy behaviour."
},
{
"name": "no-proxy-on-resolve",
"desc": "Disable proxy on unresolved address"
},
{
"name": "ndp-proxy",
"desc": "Configure NDP proxy behaviour."
},
{
"name": "no-proxy-on-resolve",
"desc": "Disable proxy ... | 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.
Option proxy-force-resolve introduced onn SRX Series and vSRX Virtual Firewall 3.0 platforms in Junos OS
Release 22.1R1. | [
"Secure IPv6 Neighbor Discovery"
] |
neighbor-discovery-inspection | neighbor-discovery-inspection; | [edit vlans vlan-name forwarding-options dhcp-security],
[edit ethernet-switching-options secure-access-port vlan (all | vlan-name)] | Perform dynamic IPv6 neighbor discovery inspection on the specified VLAN.
When neighbor discovery inspection is configured, the switch inspects IPv6 packets with neighbor
discovery messages and validates them against the DHCPv6 binding table. The source IP address and
source MAC address of each packet are checked again... | [] | 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.
Support at the [edit ethernet-switching-options secure-access-port vlan (all | vlan-name)] hierarchy level
introduced in Junos OS Release 14.1X53-D10 for EX Series switches.
Starting in Junos OS Release 25.4R1, GBP tagging and enforcement works on ND packets even wh... | [
"Configuring Port Security (ELS)",
"Example: Configuring IPv6 Source Guard and Neighbor Discovery Inspection to Protect a Switch from",
"IPv6 Address Spoofing",
"Microsegmentation Using Group-Based Policies"
] |
neighbor-policy | neighbor-policy [ policy-names ]; | [edit logical-systems logical-system-name protocols pim interface (Protocols PIM) interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
interface (Protocols PIM) interface-name],
[edit protocols pim interface (Protocols PIM) interface-name],
[edit routing-inst... | Apply a PIM interface-level policy to filter neighbor IP addresses. | [
{
"name": "policy-name",
"desc": "Name of the policy that filters neighbor IP addresses."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2. | [
"Configuring Interface-Level PIM Neighbor Policies"
] |
nested-application (Security IDP) | nested-application nested-application-name; | [edit security idp custom-attack attack-name attack-type chain protocol-binding]
[edit security idp custom-attack attack-name attack-type signature protocol-binding] | Specify the nested application name. | [
{
"name": "nested-application-name",
"desc": "Name of the nested application."
}
] | 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. | [] |
nested-application | nested-application name {
index number;
protocol protocol ;
signature name {
chain-order ;
maximum-transactions number;
member name {
context (http-header-content-type | http-header-host | http-url-parsed | http-url-
parsed-param-parsed);
direction (any | clie... | [edit services application-identification] | Configure a custom nested application definition, which is used by the system to identify the nested
application as it passes through the device. Custom nested application definitions can be used for
nested applications that are not part of the Juniper Networks predefined nested application database. | [
{
"name": "name",
"desc": "Name of nested application."
}
] | system—To view this statement in the configuration.
system control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Application Identification for Nested Applications"
] |
nested-application-settings | nested-application-settings {
no-application-system-cache;
no-nested-application;
} | [edit services application-identification] | Configure nested application options for application identification services.
The remaining statements are explained separately. See CLI Explorer. | [] | system—To view this statement in the configuration.
system control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2.
Statement deprecated in Junos OS Release 12.3X48-D10. | [
"Application Identification for Nested Applications"
] |
nested-application-unknown | nested-application-unknown | [edit services aacl rule rule-name No Link Title term-name No Link Title] | Enable AACL logging of flows for unknown nested applications. | [] | 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. | [] |
nested-applications | nested-applications [ nested-application-names ]; | [edit services aacl rule rule-name term (Application Aware Access List) term-name from (Application
Aware Access List)] | Identify one or more nested applications defined in the application identification configuration for
inclusion as a match condition. | [
{
"name": "nested-application-names",
"desc": "Identifiers of the nested applications."
}
] | 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. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.