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 |
|---|---|---|---|---|---|---|---|
netconf (Remote Device Management) | netconf {
bulk-interval milliseconds;
bulk-limit number;
connection-retry-interval seconds;
password password;
port port-number;
reconfigure-bulk-limit number;
response-timeout seconds;
response-timeout-count number;
user-name name;
} | [edit routing-instances routing-instance-name system services remote-device-management service-
device device-name provisioning-method],
[edit system services remote-device-management service-device device-name provisioning-method] | Configure the NETCONF XML management protocol as the method for provisioning and deprovisioning
services on the remote device. | [
{
"name": "bulk-interval",
"desc": ""
},
{
"name": "milliseconds",
"desc": "(Optional) Interval during which multiple services are provisioned or deprovisioned based on the assigned dictionary before the configuration is committed to the service device. When the interval times out, the service a... | system—To view this statement in the configuration. | Statement introduced in Junos OS Release 18.3R1. | [
"Configuring Remote Device Management for Service Provisioning",
"Remote Device Services Manager (RDSM) Overview"
] |
netconf | netconf {
flatten-commit-results;
hello-message {
yang-module-capabilities {
advertise-native-yang-modules;
advertise-custom-yang-modules;
advertise-standard-yang-modules;
}
}
netconf-monitoring {
netconf-state-schemas {
retrieve-cu... | [edit system 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 rest... | [
{
"name": "flatten-commit-results",
"desc": "Suppress the <commit-results> XML subtree in the NETCONF server's response for <commit> operations. This statement must be configured in conjunction with the rfc-compliant statement. NOTE: You should configure the flatten-commit-results statement outside of a NET... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5.
flatten-commit-results option added in Junos OS Release 21.2R1.
version-1.1 statement added in Junos OS Release 24.4R1 and Junos OS Evolved Release 24.4R1. | [] |
netconf-monitoring (NETCONF) | netconf-monitoring {
netconf-state-schemas {
retrieve-custom-yang-modules;
retrieve-standard-yang-modules;
}
} | [edit system services netconf] | Configure NETCONF monitoring options. | [
{
"name": "netconf-state-",
"desc": ""
},
{
"name": "schemas",
"desc": "Specify the schemas that the NETCONF server should return when a client application retrieves the list of supported schemas, which by default includes only the Junos OS native schema. The following statements are supported:"... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1 and Junos OS Evolved Release 21.1R1. | [] |
network (Access) | network | [edit access address-assignment pool name family (inet | inet6)] | Specify the network address for the pool. This attribute is mandatory. For an IPv6 pool, you will set the
IPv6 network prefix. | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 10.4 of Junos OS. | [
"Understanding Pass-Through Authentication"
] |
network (Address Pools) | network {
[network-prefix] {
external-assigned;
}
} | [edit access address-assignment address-pools name family inet],
[edit access address-assignment address-pools name family inet6] | Specify the network prefix for the address pool for IPv4 or IPv6 addresses.
NOTE: At least one network prefix must be configured but you can configure more than
one prefix. | [
{
"name": "network-prefix",
"desc": "Network prefix (IPv4 or IPv6). The remaining statement is explained separately. See CLI Explorer."
}
] | 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. | [
"Understanding Source IP Filtering with Address Pools in TDF Domains for IP-Based Subscribers",
"Configuring Address Pools for Source-IP Filtering of IP-Based Subscribers"
] |
network (TDF Domain) | network address net-mask; | [edit unified-edge gateways tdf gateway-name domains domain-name subscriber-exclude-prefix
family inet],
[edit unified-edge gateways tdf gateway-name domains domain-name subscriber-exclude-prefix
family inet6] | Specify the network prefix of source IP addresses for uplink packets and destination IP addresses for
downlink packets that do not undergo TDF processing. | [
{
"name": "address",
"desc": "Network address for the network prefix to exclude."
},
{
"name": "net-mask",
"desc": "Netmask for the network prefix."
}
] | 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 a Set of IP-Based TDF Subscriber Properties with a TDF Domain",
"Configuring IFL-Based TDF Subscribers and Properties with a TDF Domain",
"Understanding the Definition of a Set of IP-Based Subscriber Properties with a TDF Domain",
"IP-Based and IFL-Based TDF Subscribers Overview",
"IP-Based Sub... |
network | network ip-prefix</prefix-length>; | [edit access address-assignment pool pool-name family inet] | Configure subnet information for an IPv4 address-assignment pool. | [
{
"name": "ip-prefix",
"desc": "IP version 4 address or prefix value."
},
{
"name": "prefix-length",
"desc": "(Optional) Subnet mask."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Address-Assignment Pools for Subscriber Management"
] |
network-domain | network-domain; | [edit fabric resources node-group node-group-name] | (QFabric systems only) Designate a Node group to become a network Node group, which is used to
route traffic between a QFabric system and external networks. The absence of the network-domain
configuration statement implies that the Node group is a server Node group, which is used to group sets
of Node devices that are ... | [] | 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. | [
"Configuring Node Groups for the QFabric System",
"Understanding Node Groups"
] |
network-element (AAA Profile) | network-element network-element-name; | [edit unified-edge aaa profiles aaa-profile-name radius authentication],
[edit unified-edge aaa profiles aaa-profile-name radius accounting] | Specify the network element providing policy management for TDF subscribers. The network element
must already be defined at the [edit access radius] hierarchy level. | [
{
"name": "network-element-name",
"desc": "Name of the network element."
}
] | 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 17.1. | [
"Configuring an AAA Profile",
"Understanding AAA Profiles",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules",
"Configuring RADIUS Network Elements"
] |
network-element (Diameter Base Protocol) | network-element element-name {
function function-name;
peer peer-name {
priority priority-value;
<timeout seconds>;
}
} | [edit access diameter] | Configure the Diameter network element, which is similar to a peer group that provides function-
specific features including failover and load balancing. Specify the associated function that the network
element supports. You can prioritize the peers to support failover or load balancing.
Default
By default, all network... | [
{
"name": "element-name",
"desc": "Name of the network element."
}
] | 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. | [] |
network-element (Diameter Base Protocol) | network-element element-name {
dne-origin realm realm-name <host hostname>
forwarding {
route dne-route-name {
destination realm realm-name <host hostname> ;
function [function-name] <partition partition-name>;
metric route-metric;
}
}
function functio... | [edit diameter] | Specify the transport layer Diameter configuration. The Diameter network element includes a list of
routes reachable through the Diameter instance, associated functions, and prioritized Diameter peers. | [
{
"name": "element-name",
"desc": "Name of the network element."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configuring Diameter",
"Configuring Diameter Network Elements"
] |
network-element (Subscriber Aware Policy Control) | network-element {
element-name {
session-pics {
group {
group-name {
[session-pic interface-name];
}
}
}
}
} | [edit unified-edge tdf gateway-name diameter] | Configure the Diameter network element associated with Diameter bindings for this TDF gateway.
NOTE: If you want to set up Diameter bindings for session PICs on the TDF gateway,
contact Juniper Networks Professional Services for assistance. | [
{
"name": "element-name",
"desc": "Name of the network element. Range: Up to 32 alphanumeric characters NOTE: The specified network element must already be configured on the TDF gateway at the [edit access diameter network-element] hierarchy level."
}
] | 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 17.1. | [] |
network-elements (RADIUS) | network-elements name {
server name {
priority priority;
}
maximum-pending-reqs-limit number;
pending-queue-watermark watermark;
pending-queue-watermark-abate abate-watermark;
} | [edit access radius] | Configure a network element, which is a load-balanced group of RADIUS servers providing policy
management for TDF subscribers. | [
{
"name": "name",
"desc": "Name of the network element. Range: Up to 31 alphanumeric characters. The remaining statements are described separately."
}
] | 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 Network Elements",
"Understanding Network Elements",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules"
] |
network-isolation | network-isolation {
group name {
detection {
hold-time <down milliseconds><up milliseconds>;
link-tracking {
failure-type link;
interface name;
minimum-links minimum-links;
}
service-tracking {
core-isolation;
}
}
service-tracking-action (lacp-... | [edit protocols] | Configure a network isolation group in an EVPN network to define the parameters the device uses to
determine network isolation condition changes and act upon them.
A network isolation condition means a bridge domain or EVPN instance (EVI) becomes isolated from the
EVPN core network, usually for one or more of the follo... | [
{
"name": "group name",
"desc": "(Required) Network isolation group name. You can define up to 64 network isolation groups."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 23.1R1.
service-tracking and service-tracking-action options added in Junos OS and Junos OS Evolved Release
23.2R1. | [] |
network-isolation-profile | network-isolation-profile {
group name;
} | [edit bridge-domains name bridge-options],
[edit interfaces name],
[edit routing-instances name bridge-domains name bridge-options],
[edit routing-instances name switch-options],
[edit routing-instances name vlans name switch-options],
[edit switch-options],
[edit vlans name switch-options] | On a provider edge (PE) device in an EVPN network, assign a network isolation group profile to an EVPN
instance (EVI), to a particular bridge domain or VLAN in an EVI, or to an interface.
A network isolation group encompasses the parameters that the device uses to:
•
Detect when an EVPN instance. a bridge domain, or a ... | [
{
"name": "group",
"desc": ""
},
{
"name": "name",
"desc": "Group name of the network isolation profile you want to assign to the desired EVI, bridge domain, VLAN, or interface (depending on the configuration hierarchy level you use with this statement)."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 23.1R1. | [
"Determine IRB Interface State Changes from Local L2 Interface or Remote Connectivity Status in",
"EVPN Fabrics",
"Layer 2 Interface Status Tracking and Shutdown Actions for EVPN Core Isolation Conditions"
] |
network-management | network-management {
cluster-master;
} | [edit chassis cluster] | Define parameters for network management. To manage an SRX Series Services Gateway cluster
through a non-fxp0 interface, use this command to define the node as a virtual chassis in NSM. This
command establishes a single DMI connection from the primary node to the NSM server. This
connection is used to manage both nodes... | [
{
"name": "cluster-master",
"desc": "Enable in-band management on the primary cluster node through NSM."
}
] | 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. | [] |
network-option | network-option (option-1 | option-2); | [edit chassis synchronization] | Configure the Ethernet equipment clock (EEC) synchronization networking type.
NOTE: For SCB, this option is set with the set chassis synchronization network-type (option-1
| option-2) configuration command at the [edit] hierarchy level.
NOTE: For Junos OS releases 11.2R4 through 13.3R3 for MX240, MX480, and MX960
with ... | [
{
"name": "option-1",
"desc": "Maps to the G.813 option 1 (EEC1)."
},
{
"name": "option-2",
"desc": "Maps to the G.812 type IV clock (EEC1)."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2R4. | [] |
network-services | network-services (ethernet | enhanced-ethernet | ip | enhanced-ip | lan); | [edit chassis] | Set the router’s network services to a specific mode of operation. On MX240, MX480, and MX960
routers, MPC5E and MPC7E power on only if the network services mode configured is enhanced-ip or
enhanced-ethernet.
MX2010 and MX2020 support only enhanced-ip and enhanced-ethernet network services modes.
Default
•
MX80, MX104... | [
{
"name": "ethernet",
"desc": "Set the router’s network services to Ethernet and use standard, compiled firewall filter format."
},
{
"name": "enhanced-ethernet",
"desc": "Set the router’s network services to enhanced Ethernet and use enhanced mode"
},
{
"name": "ip",
"desc": "Set th... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 8.5.
enhanced-ethernet and enhanced-ip options introduced in Junos OS Release 11.4.
limited-ifl-scaling option introduced in Junos OS Release 15.1R3 for MX Series routers. | [
"Network Services Mode Overview",
"Firewall Filters and Enhanced Network Services Mode Overview",
"Configuring Junos OS to Run a Specific Network Services Mode in MX Series Routers",
"Configuring Enhanced IP Network Services for a Virtual Chassis",
"Limiting the Maximum Number of Logical Interfaces on MX Se... |
network-slices | network-slices {
guest-network-functions{
gnf id {
control-plane-bandwidth-percent percent;
description description;
fpcs fpcs;
af-name
collapsed-forward
}
}
} | [edit chassis] | Configure Junos node slicing.
Junos node slicing enables a single MX Series router to be partitioned to appear as multiple,
independent routers. Each partition has its own Junos control plane, which runs as a virtual machine
(VM), and a dedicated set of line cards. Each partition is called a guest network function (GNF... | [] | 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.2. | [
"Understanding Junos Node Slicing",
"Setting Up Junos Node Slicing",
"Setting Up Junos Node Slicing"
] |
network-slicing | network-slicing {
slice slice-name;
} | [edit services] | Specify the network slice(s) on the device.
Network slicing is the partitioning of a physical network into multiple logical networks. Each logical
network is called a slice. By virtue of being a logical network, a slice is a designated set of network
resources, such as interfaces, firewall filters, policers, virtual ou... | [] | •
interface—To view this statement in the configuration
•
interface-control—To add this statement to the configuration | Statement introduced in Junos OS Release 22.2R1. | [
"Hierarchical Class of Service for Network Slicing"
] |
network-summary-export | network-summary-export policy-name; | [edit logical-systems logical-system-name protocols ospf area area-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf
area area-id],
[edit protocols ospf area area-id],
[edit routing-instances routing-instance-name protocols ospf area area-id] | Apply an export policy that specifies which network-summary link-state advertisements (LSAs) are
flooded into an OSPFv2 area. | [
{
"name": "policy-name",
"desc": "Name of a policy configured at the [edit policy-options policy-statement policy-name term term-name] hierarchy level."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Import and Export Policies for Network Summaries Overview",
"Example: Configuring an OSPF Export Policy for Network Summaries",
"Routing Policies, Firewall Filters, and Traffic Policers User Guide"
] |
network-summary-import | network-summary-import policy-name; | [edit logical-systems logical-system-name protocols ospf area area-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf
area area-id],
[edit protocols ospf area area-id],
[edit routing-instances routing-instance-name protocols ospf area area-id] | Apply an import policy that specifies which routes learned from an OSPFv2 area are used to generate
network-summary link-state advertisements to other areas. | [
{
"name": "policy-name",
"desc": "Name of a policy configured at the [edit policy-options policy-statement policy-name term term-name] hierarchy level."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Import and Export Policies for Network Summaries Overview",
"Example: Configuring an OSPF Import Policy for Network Summaries",
"Routing Policies, Firewall Filters, and Traffic Policers User Guide"
] |
next-hop (Access Internal) | next-hop next-hop; | [edit routing-options access-internal route ip-prefix</prefix-length>] | Configure the next-hop address for an internal access route. Access routes are typically unnumbered
interfaces.
NOTE: Starting in Junos OS Release 15.1R4, the router no longer supports a
configuration where a static route points to a next hop that is tied to a subscriber.
Typically, this might occur when RADIUS assigns... | [
{
"name": "next-hop",
"desc": "Specific next-hop address you want to assign to the internal access route."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [] |
next-hop (Access) | next-hop next-hop; | [edit routing-options access route ip-prefix</prefix-length>] | Configure the next-hop address for an access route. Access routes are typically unnumbered interfaces. | [
{
"name": "next-hop",
"desc": "Specific next-hop address you want to assign to the access route."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [] |
next-hop (Class-Of-Service) | next-hop [ next-hop-name ]; | [edit class-of-service forwarding-policy next-hop-map map-name forwarding-class class-name] | Specify the next-hop name or address to which to map forwarded traffic. | [
{
"name": "next-hop-name",
"desc": "Next-hop alias or IP address."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring CoS-Based Forwarding"
] |
next-hop (Dynamic Access Routes) | next-hop next-hop; | [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
access route prefix],
[edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
rib routing-table-name access route prefix],
[edit dynamic-profiles profile-name routing-options access rout... | Dynamically configure the next-hop address for an access route. Access routes are typically unnumbered
interfaces.
The next-hop gateway can be specified explicitly in the framed route, as either the subscriber’s fixed
address (common for business subscribers) or 0.0.0.0. Alternatively, the absence of the gateway addres... | [
{
"name": "next-hop",
"desc": "Either the specific next-hop address you want to assign to the access route or one of the"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Support at the [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
access route prefix] and [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-
options rib routing-table-name access route prefix] h... | [
"Configuring Dynamic Access Routes for Subscriber Management"
] |
next-hop (Forwarding Options) | next-hop address; | [edit forwarding-options port-mirroring family (inet | inet6) output interface interface-name] | Specify the next-hop address for sending copies of packets to an analyzer.
NOTE: You need not configure the option for QFX5220-128C and QFX5220-32CD
routers. | [
{
"name": "address",
"desc": "IP address of the next-hop router."
}
] | 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 Port Mirroring on M, T MX, ACX, and PTX Series Routers",
"Configuring Port Mirroring"
] |
next-hop (PIM RPF Selection) | next-hop next-hop-address; | [edit routing-instances routing-instance-name protocols pim rpf-selection group group-address
source source-address],
[edit routing-instances routing-instance-name protocols pim rpf-selection group group-address
wildcard-source],
[edit routing-instances routing-instance-name protocols pim rpf-selection prefix-list pr... | Configure the specific next-hop address for the PIM group source. | [
{
"name": "next-hop-address",
"desc": "Specific next-hop address for the PIM group source."
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in JUNOS Release 10.4. | [
"Example: Configuring PIM RPF Selection"
] |
next-hop (Protocols MPLS) | next-hop (address | interface-name | address/interface-name); | [edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
bypass],
[edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
ingress],
[edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
transit incoming-la... | Location of the next hop to the destination, specified as the IPv4 or IPv6 address of the next hop, the
interface name (for point-to-point interfaces only), or the address/interface-name to specify an IP address
on an operational interface. | [
{
"name": "address",
"desc": "IPv4 or IPv6 address of the next-hop router."
},
{
"name": "interface-name",
"desc": "IP address of the outgoing interface. It must be a point-to-point interface. The name can"
}
] | 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 IPv6 addresses in static LSP configurations on the egress router added in Junos OS Release
17.2R1.
Support for IPv4 or IPv6 lookup after poping the label added in Junos OS Release 17.4R1. | [
"Configuring the Ingress Router for Static LSPs"
] |
next-hop (RPM) | next-hop next-hop; | [edit services rpm probe owner test test-name] | Specify the next-hop address to which the probe should be sent. | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [] |
next-hop (Static MAC-Based VLANs) | next-hop interface-name; | [edit ethernet-switching-options static vlan vlan-name mac mac-address] | Specify the next hop for the indicated Ethernet node. | [
{
"name": "interface-name",
"desc": "Name of the next-hop interface."
}
] | 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. | [
"Adding a Static MAC Address Entry to the Ethernet Switching Table"
] |
next-hop (VXLAN Routing) | next-hop integer; | [edit forwarding-options vxlan-routing] | Configure the maximum number of next hops reserved for use in an Ethernet VPN-Virtual Extensible
LAN (EVPN-VXLAN) overlay network.
Juniper Networks switches can store a maximum number of next hops for use in either an underlay
network or an EVPN-VXLAN overlay network. By default, a switch allocates 8192 next hops for u... | [
{
"name": "integer",
"desc": "Maximum number of next hops reserved for use in an EVPN-VXLAN overlay network on a switch. Range: QFX5110 switches: 0 through 45056. QFX5120 switches: 0 through 61440. The integer you"
},
{
"name": "specify must be a multiple of 4096",
"desc": "for example, 4096, 8... | 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. | [] |
next-hop-based-tunnel (Routing Options) | next-hop-based-tunnel; | [edit logical-systems logical-system-name routing-options dynamic-tunnels gre next-hop-based-
tunnel],
[edit routing-options dynamic-tunnels gre next-hop-based-tunnel] | Enable dynamic next hop based GRE tunnels.
Create a tunnel composite next hop for every dynamic GRE tunnel configured. The tunnel composite
next hop includes the dynamic tunnel’s encapsulation data and a VPN label (when chained composite
next hop is not enabled). When this option is not configured, the default interfac... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring MPLS-Signaled LSPs to Use GRE Tunnels"
] |
next-hop-group (Analyzer) | next-hop-group next-hop-group-name {
vlan vlan-id ;
} | [edit forwarding-options analyzer analyzer-name output] | Configure next-hop group through which the port-mirrored traffic is sent. | [
{
"name": "next-hop-group-name",
"desc": "Name of the next-hop group through which the port-mirrored traffic is sent."
},
{
"name": "vlan vlan-id",
"desc": "ID of the VLAN that contains multiple next-hop groups."
}
] | interface—To view this statement in the configuration.interface-control—To add this statement to the
configuration. | Statement introduced in Junos OS Release 14.1.
Option vlan vlan-id introduced in Junos OS Release 25.2. | [
"Example: Configuring Mirroring to Multiple Interfaces for Remote Monitoring of Employee Resource",
"Use on EX9200 Switches",
"1:N Port Mirroring to Multiple Destinations on Switches"
] |
next-hop-group (Forwarding Options) | [edit forwarding-options] | Specify the next-hop address for sending copies of packets to an analyzer.
(This paragraph applies only to routers.) The commit operation fails when a next-hop group has only one
interface configured. It is implicitly assumed that a subgroup is up only if more than one interface in the
subgroup is up.
NOTE: (This Note ... | [
{
"name": "interface",
"desc": ""
},
{
"name": "interface-name",
"desc": "Name of interface used to reach the next-hop destination."
},
{
"name": "group-type",
"desc": ""
},
{
"name": "layer-2",
"desc": "(Applies only to EX switches) Group type of the next-hop group. The ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 22.4R1 for EX3400, EX4100, EX4100-F, EX4300-MP, and
EX4400 switches. | [
"Configuring Next-Hop Groups to Use Multiple Interfaces to Forward Packets Used in Port Mirroring",
"Configuring Port Mirroring for Multiple Destinations",
"1:N Port Mirroring to Multiple Destinations on Switches"
] | |
next-hop-group (Port Mirroring) | next-hop-group group-name {
vlan vlan-id ;
} | [edit forwarding-options port-mirroring family (inet | vpls) output],
[edit forwarding-options port-mirroring instance instance-name family (inet | vpls) output] | Specify the next-hop address for sending copies of packets to an analyzer.
NOTE: This configuration enables multipacket port mirroring on MX Series routers and
EX Series switches without the use of a Tunnel PIC.
The commit operation fails when a next-hop group has only one interface configured. It is implicitly
assumed... | [
{
"name": "group-name",
"desc": "Name of next-hop group."
},
{
"name": "vlan vlan-id",
"desc": "ID of the VLAN that contains multiple next-hop groups."
}
] | 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.
Option vlan vlan-id introduced in Junos OS Release 25.2. | [
"Understanding Layer 2 Port Mirroring to Multiple Destinations Using Next-Hop Groups",
"1:N Port Mirroring to Multiple Destinations on Switches"
] |
next-hop-group (Unknown Unicast Forwarding) | next-hop-group group-name {
group-type {
layer-2;
}
interface interface-name {
next-hop address;
}
next-hop-subgroup subgroup-name {
interface interface-name;
}
}
} | [edit forwarding-options] | Configure a next-hop group to forward unknown unicast packets to a specific interface or interfaces. | [
{
"name": "group-name",
"desc": "Name of the next-hop group."
}
] | 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. | [
"Configuring Unknown Unicast Forwarding (ELS)",
"Configuring Mirroring on EX9200 Switches to Analyze Traffic (CLI Procedure)"
] |
next-hop-group | next-hop-group group-name{
group-type inet6;
interface interface-name {
next-hop ipv6-address;
}
next-hop-subgroup group-name{
interface interface-name {
next-hop ipv6-address;
}
}
} | [edit forwarding-options port-mirroring family inet6 output] | Specify the next-hop group through which to send port-mirror traffic to an analyzer. This configuration
enables multipacket port mirroring on MX Series routers with or without the use of a Tunnel PIC. It is
implicitly assumed that a subgroup is up only if more than one interface in the subgroup is up. | [
{
"name": "group-name",
"desc": "Name of the next-hop group. Up to 30 next-hop groups are supported for the router. Each"
},
{
"name": "interface-name",
"desc": "Name of the interface used to reach the next-hop destination."
},
{
"name": "ipv6-address",
"desc": "IPv6 address of the n... | 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. | [
"Configuring Port Mirroring on M, T MX, ACX, and PTX Series Routers"
] |
next-hop-map | next-hop-map map-name {
forwarding-class class-name {
discard;
lsp-next-hop [ lsp-regular-expression ];
next-hop [next-hop-name];
non-lsp-next-hop;
}
forwarding-class-default {
discard;
lsp-next-hop [ lsp-regular-expression ];
next-hop [next-hop-name];... | [edit class-of-service forwarding-policy] | Specify the map for CoS forwarding routes. | [
{
"name": "map-name",
"desc": "Map that defines next-hop routes."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced for QFX10000 Series switches in Junos OS Release 17.1R1. | [
"Configuring CoS-Based Forwarding"
] |
next-hop-service | next-hop-service {
inside-service-interface interface-name.unit-number;
outside-service-interface interface-name.unit-number;
outside-service-interface-type interface-type;
service-interface-pool name;
} | [edit services service-set service-set-name] | Specify interface names or a service interface pool for the forwarding next-hop service set. You cannot
specify both a service interface pool and an inside or outside interface. | [
{
"name": "inside-service-interface interface-name.unit-number",
"desc": "Name and logical unit number of the service interface"
},
{
"name": "outside-service-interface interface-name.unit-number",
"desc": "Name and logical unit number of the service interface"
},
{
"name": "outside-serv... | 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.
service-interface-pool option added in Junos OS Release 9.3.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Configuring Service Sets to be Applied to Services Interfaces"
] |
next-hop-tunnel | next-hop-tunnel gateway-address ipsec-
vpn vpn-name; | [edit interfaces interface-name unit
logical-unit-number family family-name] | For the secure tunnel (st) interface, create entries in the Next-Hop Tunnel Binding (NHTB) table, which is
used to map the next-hop gateway IP address to a particular IP Security (IPsec) Virtual Private Network
(VPN) tunnel. NHTB allows the binding of multiple IPsec VPN tunnels to a single IPsec tunnel interface. | [
{
"name": "gateway-address",
"desc": "Next-hop gateway IP address."
},
{
"name": "ipsec-vpn vpn-name",
"desc": "VPN to which the next-hop gateway IP address is mapped."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Understanding Interfaces"
] |
next-server | next-server next-server; | [edit system services dhcp],
[edit system services dhcp pool pool-id],
[edit system services dhcp static-binding mac-address] | (J Series Services Routers only) Specify the IP address for the next DHCP server used for communication
after a DHCP boot client establishes initial contact. | [
{
"name": "next-server",
"desc": "The IP address of the DHCP server that is used as the “siaddr” in a DHCP protocol packet."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [] |
next-table | next-table table-name; | [edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
bypass],
[edit protocols mpls static-label-switched-path lsp-name bypass] | Specify the routing table used to resolve the IPv4 or IPv6 next hop for a bypass LSP.
NOTE:
•
The transit LSP that's associated with a bypass LSP that uses next-table must use a
label in the range of 1000000-1048575
•
The transit LSP that's associated with a bypass LSP that uses next-table must be
configured with a po... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2. | [
"Configuring the Ingress Router for Static LSPs"
] |
nextboot | nextboot {
media-device;
} | [edit] | You can use the nextboot function to check the current bootup device. This function lists the available
boot device choice for the media devices and current settings. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.3R1. | [
"Veriexec Overview"
] |
nexthop-ecmp | nexthop-ecmp (value | equal | greater-than | greater-than-equal | less-than | less-than-equal); | [edit logical-systems name policy-options policy-statement name from],
[edit policy-options policy-statement name from] | Qualify nexthop equal cost multipath gateways. The BGP export policy compares the number of ECMP
next hops for the BGP route against the value you configure with the from nexthop-ecmp statement at
either of these hierarchies: [edit policy-options policy-statement policy-name] or [edit policy-options policy-
statement p... | [
{
"name": "value",
"desc": "The exact number of ECMP gateways (1 through 512) required to meet the condition."
},
{
"name": "equal",
"desc": "The number of gateways must be equal to the configured value."
},
{
"name": "greater-than",
"desc": "The number of gateways must be greater th... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.4. | [
"No Link Title"
] |
nexthop-hold-time | nexthop-hold-time milliseconds; | [edit routing-instances routing-instance-name multicast-snooping-options] | Accumulate outgoing interface changes in order to perform bulk updates to the forwarding table and the
routing table. Delete the statement to turn off bulk updates. | [
{
"name": "milliseconds",
"desc": "Set the hold time duration from 1 through 1000 milliseconds."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Enabling Bulk Updates for Multicast Snooping"
] |
nexthop-learning | nexthop-learning (disable | enable); | [edit services flow-monitoring (version-ipfix |version9) template template-name] | Enable learning of next-hop addresses to correctly report the next hop address, output SNMP,
destination IP address, destination IP mask values, the packet loss priority, and the first two characters
of the configured forwarding class name in the flow records when a destination is reachable through
multiple paths. By d... | [
{
"name": "disable",
"desc": "Disable the learning of next-hop information required for inline active flow monitoring."
},
{
"name": "enable",
"desc": "Enable the learning of next-hop information required for inline active flow monitoring."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F2.
nexthop-learning is supported for the bridge-template statement in Junos OS Release 18.2R1 for MX Series
routers.
Support introduced in Junos OS Release 20.3R1 to correctly report the packet loss priority and the first
two characters of the configured forwarding class in... | [
"Configuring Next-Hop Address Learning on MX Series and PTX Series Routers for Destinations",
"Accessible Over Multiple Paths"
] |
ng-juniper | ng-juniper {
base-filter {
base-filter;
ng-default-filter;
}
category category-name {
action (block | log-and-permit | permit | quarantine);
custom-message... | [edit security utm default-configuration web-filtering]
[edit security utm feature-profile web-filtering ng-juniper profile name] | Configure the Juniper NextGen Web filtering engine. Juniper NextGen Web filtering acts as a gateway
for the SRX Series devices seeking URL reputation or category from the Juniper NextGen Web Filtering
(NGWF) cloud.
NOTE: You must configure SSL initiation profile for NGWF to communicate through
HTTPS connections.
The fo... | [
{
"name": "base-filter",
"desc": "Juniper base filter."
},
{
"name": "ng-default-filter",
"desc": "Juniper default base filter."
},
{
"name": "category name",
"desc": "Juniper NextGen category name."
},
{
"name": "action",
"desc": "Action to perform when web traffic match... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [] |
ngfw | ngfw {
default-profile {
application-traffic-control {
rule-set rule-set;
}
ssl-proxy {
profile-name profile-name;
}
}
} | [edit security],
[edit security logical-systems logical-system-name] | Specify a default profile to manage conflicts when a security policy lookup returns a list of policies
before the final application is identified.
The initial policy lookup phase occurs prior to identifying a dynamic application. If there are multiple
policies present in the potential policy list that contain different... | [
{
"name": "application-traffic-control",
"desc": "Specify the application traffic control rule as the default rule."
},
{
"name": "rule-set rule-set",
"desc": "Rule set name of the application traffic control."
},
{
"name": "ssl-proxy",
"desc": "Specify the SSL forward proxy profile ... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1 | [
"Configuring SSL Forward Proxy",
"Firewall User Authentication Overview"
] |
niso-maintenance | niso-maintenance {
down (all | group-name);
} | [edit logical-systems name protocols l2-learning],
[edit protocols l2-learning] | The network isolation maintenance knob enables you to shut down all L2 interfaces or just those
associated with a particular network isolation group.
You use this statement to facilitate controlled and efficient maintenance operations by configuring it to
shut down the desired interfaces then removing it after the main... | [
{
"name": "down",
"desc": "Network isolation maintenance down knob"
},
{
"name": "all",
"desc": "Bring down all L2 interfaces associated with all network isolation groups."
},
{
"name": "group-name",
"desc": "Bring down all L2 interfaces associated with a specific network isolation g... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1 | [
"Uplink Protection for Network Isolation"
] |
no advertise-peer-as | no-advertise-peer-as; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Enable the default behavior of suppressing AS routes. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring BGP Route Advertisement",
"Configuring Routing Policies to Control BGP Route Advertisements"
] |
no-accounting | no-accounting; | [edit dynamic-profiles profile-name protocols igmp interface interface-name] | Disable the collection of IGMP join and leave event statistics on a per-interface basis. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Dynamic IGMP Configuration Overview",
"Configuring Dynamic DHCP Client Access to a Multicast Network",
"Recording IGMP Join and Leave Events"
] |
no-adaptation (BFD Liveness Detection) | no-adaptation; | [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 BFD sessions not to adapt to changing network conditions. We recommend that you do not
disable BFD adaptation unless it is preferable to have BFD adaptation disabled in your network.
The BFD failure detection timers are adaptive and can be adjusted to be faster or slower. The lower the
BFD failure detection t... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0
Support for 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"
] |
no-adaptation (Liveness Detection) | no-adaptation; | [edit protocols iccp peer liveness-detection] | Configure Bidirectional Forwarding Detection (BFD) sessions to not adapt to changing network
conditions. | [] | 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. | [] |
no-adaptation (PIM BFD Liveness Detection) | no-adaptation; | [edit protocols pim interface interface-name bfd-liveness-detection],
[edit routing-instances routing-instance-name protocols pim interface interface-name bfd-
liveness-detection] | Configure BFD sessions not to adapt to changing network conditions. We recommend that you do not
disable BFD adaptation unless it is preferable to have BFD adaptation disabled in your network. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0
Support for BFD authentication introduced in Junos OS Release 9.6. | [
"Configuring BFD for PIM"
] |
no-adaptation | no-adaptation; | [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 Bidirectional Forwarding Detection (BFD) sessions to not adapt to changing network
conditions. | [] | 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"
] |
no-adaptive | no-adaptive; | [edit dynamic-profiles name interfaces name aggregated-ether-options load-balance],
[edit dynamic-profiles name interfaces name logical-tunnel-options load-balance],
[edit dynamic-profiles name interfaces interface-range name aggregated-ether-options load-
balance],
[edit dynamic-profiles name interfaces interface-rang... | Disables the adaptive load-balancing solution configured on the aggregated Ethernet bundle to
distribute traffic by using a feedback mechanism. | [] | interface - To view statement in the configuration.
interface-control - To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R3. | [
"Understanding Aggregated Ethernet Load Balancing"
] |
no-adjacency-down-notification (Protocols IS-IS) | no-adjacency-down-notification; | [edit logical-systems logical-system-name protocols isis interface interface-name],
[edit protocols isis interface interface-name] | Disable adjacency down notification for IS-IS to allow for migration from IS-IS to OSPF without
disruption of the RSVP neighbors and associated RSVP-signaled label-switched paths (LSPs).
Whenever IS-IS is deactivated, the IS-IS adjacencies are brought down. IS-IS signals to RSVP to bring
down any RSVP neighbors associa... | [] | 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. | [] |
no-advertise-adjacency-segment (Protocols IS-IS) | no-advertise-adjacency-segment; | [edit logical-systems logical-system-name protocols isis interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols isis
interface interface-name],
[edit protocols isis interface interface-name],
[edit routing-instances routing-instance-name protocols isis in... | Disable advertising of the adjacency segment on all levels for the specified interface.
Default
Enabled | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [] |
no-advertise-adjacency-segment (Protocols OSPF) | no-advertise-adjacency-segment; | [edit logical-systems logical-system-name protocols ospf area name interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf
area name interface interface-name],
[edit protocols ospf area name interface interface-name],
[edit routing-instances routing-i... | Disable advertising of the adjacency segment for the specified interface.
Default
Enabled | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"OSPF Overview",
"source-packet-routing"
] |
no-aggregate-delegate-processing | no-aggregate-delegate-processing; | [edit protocols oam ethernet connectivity-fault-management] | Disable distribution of connectivity fault management (CFM) sessions on aggregated Ethernet
interfaces.
Default
CFM sessions on aggregated Ethernet interfaces are distributed by default. | [] | Configure—To enter configuration mode.
Control—To modify any configuration. | Statement introduced in Junos OS Release 14.1. | [
"IEEE 802.1ag OAM Connectivity Fault Management Overview"
] |
no-aggregator-id | no-aggregator-id; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Prevent different routing devices within an AS from creating aggregate routes that contain different AS
paths.
Junos OS performs route aggregation, which is the process of combining the characteristics of different
routes so that only a single route is advertised. Aggregation reduces the amount of information that
BGP ... | [] | 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 Messages Overview"
] |
no-allow-link-events | no-allow-link-events; | [edit protocols oam ethernet link-fault-management
interface interface-name negotiation-options] | Disable the sending of link event TLVs. | [] | 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"
] |
no-allow-snooped-clients | no-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 disable DHCP snooping support on DHCP relay agent.
Use the statement at the [edit ... dhcpv6] hierarchy levels to explicitly disable snooping support for
DHCPv6 relay agent.
NOTE: In Junos OS Release 10.0 and earlier, DHCP snooping is enabled by default. In
Release 10.1 and later, DHCP snooping is disabled b... | [] | 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"
] |
no-allow-url (Op Scripts) | no-allow-url; | [edit system scripts op] | Prohibit the remote execution of Junos OS op scripts. When you include this configuration statement,
the op url operational mode command does not support executing op scripts from a remote site and
generates an error.
Default
If you do not include the no-allow-url statement, authorized users can issue the op url comman... | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Executing an Op Script from a Remote Site"
] |
no-allowed-mac-log | no-allowed-mac-log; | [edit ethernet-switching-options secure-access-port interface (all | interface-name)] | Specify that the switch does not log messages when it receives packets from invalid MAC addresses on
an interface that has been configured for particular (allowed) MAC addresses.
Default
The switch logs messages when it receives packets from invalid MAC addresses on an interface that has
been configured for particular ... | [] | system—To view this statement in the configuration.
system–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Example: Configuring Port Security (non-ELS)",
"Example: Protecting Against DHCP Snooping Database Attacks",
"Example: Protecting against DHCP Starvation Attacks",
"Configuring MAC Limiting (non-ELS)"
] |
no-anti-replay (Services Service Set) | no-anti-replay; | [edit services service-set service-set-name ipsec-vpn-options] | Disable IPsec antireplay service for this service set, which occasionally causes interoperability issues for
security associations. This statement is useful for dynamic endpoint tunnels for which you cannot
configure the no-anti-reply statement at the [edit services ipsec-vpn rule rule-name term term-name then]
hierarc... | [] | 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"
] |
no-anti-replay | no-anti-replay; | [edit services ipsec-vpn rule rule-name term term-name then] | Disable IPsec antireplay service, which occasionally causes interoperability issues for security
associations. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring IPsec Rules"
] |
no-application-identification (Services) | no-application-identification; | [edit services application-identification] | Disable the application identification of applications running on nonstandard ports. By default,
application identification is enabled on the device. You can disable application identification by using the
following command:
user@host# set services application-identification no-application-identification
If you want to... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Disabling and Reenabling Junos OS Application Identification"
] |
no-application-identification | no-application-identification; | [edit services application-identification] | Disable all application identification methods. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring Global APPID Properties"
] |
no-application-system-cache | no-application-system-cache; | [edit services application-identification],
[edit services application-identification nested-application-settings] | Application identification information is saved in the application system cache to improve performance.
This cache is updated when a different application is identified. This caching is turned on by default. Use
the no-application-system-cache statement to turn it off.
ASC is enabled by default when a session is create... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Support for Next Gen Services introduced in Junos OS Release 19.3R2 and 19.4R1 on MX Series routers
MX240, MX480 and MX960.
Statement deprecated in Junos OS Release 12.3X48-D10 at the [edit services application-identification
nested-application-settings] hierarchy level. | [
"Configuring Global APPID Properties",
"Application Identification for Nested Applications"
] |
no-attribute-length-in-pdu | no-attribute-length-in-pdu; | [edit protocols mvrp] | Include an extra byte in protocol data units (PDUs) sent by the Multiple VLAN Registration Protocol
(MVRP). You can disable the extra byte to address a compatibility issue between MVRP in Junos OS
Releases 13.2 and later for EX Series switches with support for the Enhanced Layer 2 Software (ELS),
which includes the ext... | [] | routing—To view this statement in the configuration.
routing control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10. | [
"Configuring Multiple VLAN Registration Protocol (MVRP) on Switches",
"Understanding Multiple VLAN Registration Protocol (MVRP)",
"Understanding Multiple VLAN Registration Protocol (MVRP) for Dynamic VLAN Registration"
] |
no-authentication-check (Protocols RSVP) | no-authentication-check; | [edit protocols rsvp] | Skip authentication check for received messages. | [] | routing | Statement introduced in Junos OS Release 18.4R1. | [
"RSVP Authentication"
] |
no-auto-conversion | no-auto-conversion; | [edit virtual-chassis] | Disable automatic Virtual Chassis port (VCP) conversion in a Virtual Chassis.
NOTE: This statement is available as of Junos OS Releases 14.1X53-D47, 17.4R2,
18.1R3, 18.2R2, and 18.3R1 only on EX Series and QFX Series switches in a Virtual
Chassis that have automatic VCP conversion enabled by default, which include all
... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Releases 14.1X53-D47, 17.4R2, 18.1R3, 18.2R2, and 18.3R1. | [
"Understanding Virtual Chassis Components",
"Setting an Uplink Port on an EX Series or QFX Series Switch as a Virtual Chassis Port",
"Adding a New Switch to an Existing EX2300, EX3400, or EX4300 Virtual Chassis",
"Adding an EX4600 Switch to a Mixed or Non-mixed Virtual Chassis",
"Adding a New Switch to an E... |
no-auto-failover | no-auto-failover; | [edit chassis redundancy feb redundancy-group group-name] | Disable automatic failover to a backup FEB when an active FEB in a redundancy group fails.
Default
Automatic failover is enabled by default. | [] | 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 FEB Redundancy on the M120 Router"
] |
no-auto-iccp-provisioning (Junos Fusion Redundancy Group) | no-auto-iccp-provisioning; | [edit chassis satellite-management redundancy-groups redundancy-group-name peer-chassis-id peer-
chassis-id-number] | Disable automatic ICCP provisioning of an interchassis link (ICL) for the redundancy group used to
configure dual aggregation devices in a Junos Fusion topology.
Automatic ICCP provisioning of an interchassis link (ICL) simplifies configuration of a Junos Fusion with
dual aggregation devices by automatically provisioni... | [] | 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 a Junos Fusion Enterprise"
] |
no-auto-mdix | no-auto-mdix; | [edit interface interface-name gigether-options] | Disable the Auto MDI/MDIX feature.
MX Series routers with Gigabit Ethernet interfaces automatically detect MDI and MDIX port
connections. Use this statement to override the default setting. Remove this statement to return to the
default setting.
The show interfaces interface-name command displays incorrect auto MDI-X ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Metro Routers. | [
"Ethernet Interfaces Overview"
] |
no-auto-virtual-gateway-esi | no-auto-virtual-gateway-esi; | [edit dynamic-profiles name interfaces name unit],
[edit dynamic-profiles name logical-systems name interfaces name unit],
[edit interfaces name unit] | Disable auto ESI generation for virtual gateway address. Automatic ESI generation is enabled by default
on devices in EVPN-VXLAN networks with EVPN multihoming for virtual gateway redundancy (see
Understanding the Redundant Default Gateway).
Starting in Junos OS Release 22.1R1, MX960, MX2020, and MX10008 routers also e... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.2R1. | [] |
no-autostart | no-autostart; | [edit virtual-network-functions] | Disable auto-start of VNF on the VNF configuration commit. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D40. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
no-autoupdate | no-autoupdate; | [edit security utm feature-profile anti-virus juniper-express-engine pattern-update]
[edit security utm feature-profile anti-virus kaspersky-lab-engine pattern-update]
[edit security utm feature-profile anti-virus sophos-engine pattern-update]
[edit security utm default-configuration anti-virus avira-engine pattern-upd... | Turn off automatic data file (pattern file) update for the Kaspersky Lab, Juniper Express, or Sophos
engines.
NOTE: The data files used with Sophos are not typical virus pattern files; they are small
files that help guide virus scanning logic. The full virus pattern database is stored on an
external Sophos server call... | [] | 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 for Juniper Express
engine and Kaspersky Lab engine. Support for Sophos engine added in Junos OS Release 11.1.
The [edit security utm default-config... | [] |
no-backup | no-backup; | [edit logical-systems name policy-options policy-statement name term name then],
[edit policy-options policy-statement name term name then] | This prefix should not have backup. You can selectively enable backup paths for specific prefixes to
optimize redundancy and resource utilization. By default, a configured backup path applies to all
prefixes. To exclude specific prefixes or ranges, create an OSPF import policy and configure the no-backup
option in the ... | [] | routing—To view this statement in the configuration.
routing—To view this statement in the configuration. | Statement introduced in Junos OS and Junos OS Evolved 25.4R1. | [] |
no-bfd-triggered-local-repair | no-bfd-triggered-local-repair; | [edit logical-systems logical-system-name routing-options],
[edit routing-options] | Disable Bidirectional Forwarding Detection (BFD) sessions to trigger fast reroute (FRR) using MPLS-FRR
and loop-free alternates (LFAs). When this statement is configured, no BFD-triggered local repair is
supported. However, logical interface down-based local repair is in force.
When using this statement to disable loca... | [] | 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. | [
"BFD-Triggered Local Repair for Rapid Convergence"
] |
no-bidirectional-mode | no-birectional-mode; | [edit logical-systems logical-system-name protocols pim graceful-restart],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
graceful-restart],
[edit protocols pim graceful-restart],
[edit routing-instances routing-instance-name protocols pim graceful-restart] | Disable forwarding for bidirectional PIM routes during graceful restart recovery, both in cases of a
routing protocol process (rpd) restart and graceful Routing Engine switchover.
Bidirectional PIM accepts packets for a bidirectional route on multiple interfaces. This means that some
topologies might develop multicast ... | [] | 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. | [
"Configuring PIM Sparse Mode Graceful Restart",
"Understanding Bidirectional PIM",
"Example: Configuring Bidirectional PIM"
] |
no-bind-on-request (DHCP Relay Agent) | no-bind-on-request; | [edit forwarding-options dhcp-relay dhcpv6 overrides],
[edit forwarding-options dhcp-relay overrides],
[edit forwarding-options dhcp-relay dhcpv6 group group-name overrides],
[edit forwarding-options dhcp-relay group group-name overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6 o... | Explicitly disable automatic binding of received DHCP request messages that have no entry in the
database (stray requests). Use the statement at the [edit ... dhcpv6] hierarchy levels to configure
DHCPv6 support.
M120 and M320 routers do not support DHCPv6.
NOTE: Beginning with Junos OS Release 10.4, automatic binding ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4. | [
"Extended DHCP Relay Agent Overview",
"Overriding the Default DHCP Relay Configuration Settings",
"Disabling Automatic Binding of Stray DHCP Requests"
] |
no-broadcast | no-broadcast; | For platforms with Enhanced Layer 2 Software (ELS)
(EX Series switches and MX Series routers):
[edit forwarding-options storm-control-profiles profile-name all] | Disable storm control for broadcast traffic for the specified interface or for all interfaces.
Default
•
On EX2200, EX3200, EX3300, and EX4200 switches—Storm control does not apply to multicast
traffic by default. The factory default configuration enables storm control on all interfaces at 80
percent of the available b... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
Hierarchy level [edit forwarding-options] introduced in Junos OS Release 13.2X50-D10. (See Using the
Enhanced Layer 2 Software CLI for information about ELS.) | [
"Configuring Autorecovery for Port Security Events",
"Example: Configuring Storm Control to Prevent Network Outages on EX Series Switches",
"Example: Using Storm Control to Prevent Network (MX Routers)",
"Enabling and Disabling Storm Control (non-ELS)",
"Enabling and Disabling Storm Control (ELS)"
] |
no-bundle-flap | no-bundle-flap; | [edit dynamic-profiles name interfaces name load-balancing-options] | When you add a new member to an existing AMS bundle, all the existing members and the newly added
member of the AMS bundle go for reboot and disrupts the traffic. To overcome this problem for IPsec
services, configure the no-bundle-flap statement before adding a new member to the AMS bundle. When
you configure no-bundl... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1 | [] |
no-certificate-chain-in-ike | no-certificate-chain-in-ike; | [edit services service-set name ipsec-vpn-options] | To avoid IKE fragmentation, send only the end-entity certificate for certificate-based IKE authentication
instead of the full certificate chain. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Configuring IPsec Service Sets"
] |
no-clear-application-system-cache | no-clear-application-system-cache; | [edit services application-identification] | Disable clearing the application system cache. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring Global APPID Properties"
] |
no-client-reflect | no-client-reflect; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Disable intracluster route redistribution by the system acting as the route reflector. Include this
statement when the client cluster is fully meshed to prevent the sending of redundant route
advertisements. Route reflection provides a way to decrease BGP control traffic and minimizing the
number of update messages sen... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring BGP Route Reflectors"
] |
no-control-word (Protocols Layer 2 VPN) | no-control-word; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
l2vpn],
[edit routing-instances routing-instance-name protocols l2vpn] | Disable the control word. This might be necessary on networks with equipment that does not support
the control word.
NOTE: The following configuration statements are ignored for time-division multiplexing
pseudowires at the [edit protocols l2vpn] hierarchy level:
•
control-word
•
no-control-word
Default
The control wor... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Disabling the Control Word for Layer 2 VPNs"
] |
no-control-word | no-control-word; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
evpn],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
mesh-group mesh-group-... | Set no-control-word to request that other routers not insert a control word between the label stack and
the MPLS payload. This is the default setting for BGP VPLS. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1.
Statement introduced for static pseudowires in mesh-group and in VPLS instance in Junos OS Release
20.3R1. | [
"Control Word for BGP VPLS Overview",
"Configuring a Control Word for BGP VPLS"
] |
no-cspf (Protocols RSVP) | no-cspf; | [edit logical-systems logical-system-name protocols rsvp interface interface-name link-
protection],
[edit logical-systems logical-system-name protocols rsvp interface interface-name link-
protection bypass bypass-name],
[edit protocols rsvp interface interface-name link-protection],
[edit protocols rsvp interface inte... | Disable CSPF computation on all bypass LSPs or on a specific bypass LSP. You need to disable CSPF for
link protection to function properly on interarea paths.
Default
CSPF is enabled. | [] | 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. | [
"Disabling CSPF for Bypass LSPs"
] |
no-cspf | no-cspf; | [edit logical-systems logical-system-name protocols mpls],
[edit logical-systems logical-system-name protocols mplslabel-switched-path lsp-name],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name (primary |
secondary) path-name],
[edit protocols mpls],
[edit protocols mpls label-swi... | Disable constrained-path LSP computation.
An explicit-path LSP is completely configured through operator action. Once configured, it is initiated
only along the explicitly specified path.
A constrained-path LSP relies on an ingress router to compute the complete path. The ingress router
takes into account the followin... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Disabling Constrained-Path LSP Computation",
"Configuring Explicit-Path LSPs"
] |
no-decrement-ttl | no-decrement-ttl; | [edit logical-systems logical-system-name protocols mpls],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name (primary |
secondary) path-name],
[edit protocols mpls],
[edit protocols mpls label-sw... | Disable normal time-to-live (TTL) decrementing, which decrements the TTL field in the IP header by 1.
This statement decrements the IP TTL by 1 before encapsulating the IP packet within an MPLS packet.
When the penultimate router pops off the top label, it does not use the standard write-back procedure
of writing the M... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Evolved Release 20.1R1 on PTX10008. | [
"Disabling Normal TTL Decrementing"
] |
no-default-gateway-ext-comm | no-default-gateway-ext-comm; | [edit routing-instances name protocols evpn] | Configure a routing instance to suppress the advertisement of the extended community on the default
gateway. An extended community is an 8-octet community used by Ethernet VPNs (EVPNs). | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Implementing EVPN-VXLAN for Data Centers",
"EVPN Multihoming Overview"
] |
no-delegate-processing | no-delegate-processing; | [edit routing-options ppm] | Disable distributed periodic packet management (PPM) processing and run all PPM processing on the
Routing Engine.
PPM processing cannot be completely disabled on EX Series switches. You can only configure whether
PPM processing is distributed between the access ports (EX3200 and EX4200 switches) or the line
cards (EX82... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [] |
no-dhcp-flood | no-dhcp-flood; | [edit interfaces name unit] | In an EVPN-VXLAN fabric where DHCP relay is configured with integrated routing and bridging (IRB)
interfaces on leaf devices, it is possible for DHCP Discover packets to be flooded across a VXLAN
attached to an IRB. This scenario leads to multiple copies of DHCP packets flooded across the fabric. To
counter this behav... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.4R1 and Junos OS Evolved Release 22.4R1 for the
QFX5xxx Series switches, EX4100 Series switches, and EX4400 Series switches. | [
"DHCP Relay Agent over EVPN-VXLAN"
] |
no-dhcp-snooping | no-dhcp-snooping; | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security] | Disable DHCP snooping for the specified VLAN or bridge domain.
NOTE: Explicitly disabling DHCP snooping also disables any other port security features
that you have enabled under [edit vlans vlan-name forwarding-options dhcp-security],
including dynamic ARP inspection (DAI) and IP source guard for the specified VLAN or... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10.
Hierarchy level [edit bridge-domains bridge-domain-name forwarding-options dhcp-security] introduced in Junos
OS Release 14.1 for the MX Series. | [
"Understanding DHCP Snooping (non-ELS)"
] |
no-dhcp-trusted | (dhcp-trusted | no-dhcp-trusted); | [edit ethernet-switching-options secure-access-port interface (Access Port Security) (all | interface-
name)] | Port security features, such as DHCP snooping and dynamic ARP inspection inspect packets only on
untrusted interfaces.
Allow or deny DHCP responses from the specified interfaces (ports) or all interfaces.
•
dhcp-trusted—Allow DHCP responses.
•
no-dhcp-trusted—Deny DHCP responses.
Default
Trusted for trunk ports, untrus... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Understanding How to Protect Access Ports from Common Attacks",
"Understanding and Using Trusted DHCP Servers"
] |
no-dhcpv6-options | no-dhcpv6-options; | [edit vlans vlan-name forwarding-options dhcp-security group group-name overrides] | Configure a specific group of one or more access interfaces within the VLAN not to add any DHCPv6
options, even if the VLAN is configured to perform DHCPv6 snooping. DHCPv6 options include option
16, option 18, and option 37. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10. | [
"Understanding DHCP Snooping (ELS)",
"Understanding DHCP Option 82"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.