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 |
|---|---|---|---|---|---|---|---|
no-revert (Neighbor Interface) | no-revert; | [edit protocols l2circuit neighbor address interfaces interface-name],
[edit logical-systems logical-system-name protocols l2circuit neighbor address interfaces
interface-name] | (Optional) Prevent the protect interface from reverting to the primary interface.
NOTE: The protect interface must be configured prior to configuring the no-revert
statement.
Typically, when the primary interface goes down, the pseudowire starts using the protect interface. By
default, when the primary interface comes ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.3. | [
"Configuring Interfaces for Layer 2 Circuits"
] |
no-rfc-1583 | no-rfc-1583; | [edit logical-systems logical-system-name protocols (ospf | ospf3)],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(ospf | ospf3)],
[edit logical-systems log... | Disable compatibility with RFC 1583, OSPF Version 2. If the same external destination is advertised by
AS boundary routers that belong to different OSPF areas, disabling compatibility with RFC 1583 can
prevent routing loops.
Default
Compatibility with RFC 1583 is enabled by default. | [] | routing—To view this statement in the configuration.
routing-control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5.
Support for the realm statement introduced in Junos OS Release 9.2.
Support for the realm statement introduced in Junos OS Release 9.2 for EX Series switches. | [
"Example: Disabling OSPFv2 Compatibility with RFC 1583"
] |
no-root-port | no-root-port; | [edit logical-systems logical-system-name protocols (mstp | rstp | vstp) interface interface-name],
[edit logical-systems logical-system-name protocols vstp vlan vlan-id interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(mstp | rstp | vstp) interface... | Configures an interface to be a spanning-tree designated port. If the bridge receives superior STP bridge
protocol data units (BPDUs) on a root-protected interface, that interface transitions to a root-prevented
STP state (inconsistency state) and the interface is blocked. This blocking prevents a bridge from being
ele... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
Statement updated in Junos OS Release 9.4 for EX Series switches to add VSTP support.
Support for logical systems added in Junos OS Release 9.6. | [
"Understanding VSTP",
"Understanding Root Protection for Spanning-Tree Instance Interfaces in a Layer 2 Switched Network",
"Enabling Root Protection for a Spanning-Tree Instance Interface",
"Example: Configuring Root Protection to Enforce Root Bridge Placement in Spanning Trees on non-",
"ELS EX Series Swit... |
no-route-localize | no-route-localize; | [edit policy-options policy-statement policy-name term term-name then] | Enforce installation of routes on all FIB-remote Packet Forwarding Engines. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Example: Configuring Packet Forwarding Engine FIB Localization"
] |
no-rpf-fbf-handling | no-rpf-fbf-handling | [edit forwarding-options no-rpf-fbf-handling] | When Unicast Reverse Path Forwarding (uRPF) and filter based forwarding (FBF) are configured on an
interface, the source IP address (SIP) lookup of an incoming packet is done by uRPF in the routing
instance that the interface points to and destination IP addrress lookup is done in the routing instance
specified by the ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.2R1 | [] |
no-sbl-default-server | no-sbl-default-server; | [edit security utm default-configuration]
[edit security utm feature-profile anti-spam sbl profile profile-name] | Disable the default SBL server lookup. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Antispam Filtering Overview"
] |
no-send-pads-ac-info | no-send-pads-ac-info; | [edit protocols pppoe] | Prevent the router from sending the AC-Name and AC-Cookie tags in the PPPoE Active Discovery
Session (PADS) packet. When you configure this statement, it affects PADS packets sent on all PPPoE
interfaces configured on the router after the command is issued; it has no effect on previously created
PPPoE interfaces. By de... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Disabling the Sending of PPPoE Access Concentrator Tags in PADS Packets"
] |
no-send-pads-error | no-send-pads-error; | [edit protocols pppoe] | Discard PADR messages to prevent transmission of PADS control packets with AC-System-Error tags. | [] | 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. | [
"Discarding PADR Messages to Accommodate Abnormal CPE Behavior"
] |
no-send-to-ue | no-send-to-ue; | [edit unified-edge pcef flow-description flow-identifier] | Specify that signaling information about the service data flow (SDF) filter is not sent to the user
equipment.
Default
By default, if this statement is not configured, signaling information about the SDF filter is sent to the
user equipment. | [] | 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 Service Data Flow Filters",
"Understanding Predefined Policy and Charging Control Rules for Subscriber-Aware Traffic Treatment"
] |
no-sequence-check | no-sequence-check; | [edit security flow tcp-session] | Specify that the device does not check sequence numbers in TCP segments during stateful inspection.
By default, the device monitors the sequence numbers in TCP segments. The device detects the window
scale specified by source and destination hosts in a session and adjusts a window for an acceptable
range of sequence nu... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Understanding Traffic Processing on Security Devices"
] |
no-signature-based | no-signature-based; | [edit services application-identification] | Disable the signature-based application identification method. | [] | 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-snoop (DHCP Local Server and Relay Agent) | no-snoop; | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit logical-systems logical-system-name ...],
[edit logical-systems logical-system-name routing-instances routing-instance-name ...],
[edit routing-instances routing-instance-name ...],
[edit system services dhcp-local-server],
[edit s... | Disable DHCP snooping filters.
DHCP snooping provides DHCP security by identifying incoming DHCP packets. In the default DHCP
snooping configuration, all traffic is snooped. You can optionally use the forward-snooped-clients statement
to evaluate the snooped traffic and to determine if the traffic is forwarded or dropp... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1R2. | [
"Configuring DHCP Snooped Packets Forwarding Support for DHCP Relay Agent"
] |
no-source-packet-routing (Protocols OSPF) | no-source-packet-routing; | [edit logical-systems logical-system-name protocols ospf backup-spf-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf
backup-spf-options],
[edit protocols ospf backup-spf-options],
[edit routing-instances routing-instance-name protocols ospf backup-spf-options] | Disables use of source packet routing node segment labels for computing backup paths for normal IPv4
OSPF prefixes and OSPF source packet routing node segments. | [] | 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"
] |
no-split-detection (MX Series Virtual Chassis) | no-split-detection; | [edit virtual-chassis] | As part of the preprovisioned configuration for an MX Series Virtual Chassis, disable detection of a split
in the Virtual Chassis configuration. By default, split detection in the Virtual Chassis is enabled. To
maintain the Virtual Chassis configuration in the event of a failure of one of the two member routers, we
rec... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Preprovisioned Member Information for a Virtual Chassis",
"Disabling Split Detection in a Virtual Chassis Configuration",
"Split Detection Behavior in a Virtual Chassis",
"Global Roles and Local Roles in a Virtual Chassis",
"Example: Configuring Interchassis Redundancy for MX Series 5G Universa... |
no-split-detection | no-split-detection; | [edit virtual-chassis] | Disable the split and merge feature in a Virtual Chassis or VCF configuration.
The split and merge feature is enabled by default when you initially set up a Virtual Chassis. If you have
only two members in your Virtual Chassis, we strongly recommend that you configure no-split-detection
to disable the split and merge f... | [] | 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. | [
"Understanding Split and Merge in a Virtual Chassis",
"Example: Assigning the Virtual Chassis ID to Determine Precedence During an EX4200 Virtual",
"Chassis Merge",
"Disabling Split and Merge in a Virtual Chassis",
"Assigning the Virtual Chassis ID to Determine Precedence During a Virtual Chassis Merge"
] |
no-syn-check | no-syn-check; | [edit security flow tcp-session] | Disable checking of the TCP SYN bit before creating a session. By default, the device checks that the
SYN bit is set in the first packet of a session. If the bit is not set, the device drops the packet. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
no-syn-check-in-tunnel | no-syn-check-in-tunnel; | [edit security flow tcp-session] | Disable checking of the TCP SYN bit before creating a session for tunneled packets. By default, the
device checks that the SYN bit is set in the first packet of a VPN session. If the bit is not set, the device
drops the packet. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
no-syslog | no-syslog; | [edit services dynamic-flow-capture capture-group client-name control-source identifier] | Disable system logging of control protocol requests and responses. By default, these messages are
logged. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring System Logging"
] |
no-syslog-generation | no-syslog-generation; | [edit services] | Disable system log generation.
NOTE: If this statement is not configured, edit services generates a system log with
respective severity level for values not within the configured range. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding Inline Video Monitoring on MX Series Routers"
] |
no-tag | no-tag; | [edit forwarding-options analyzer analyzer-name output vlan (vlan-id | vlan-name)] | Specify that remote mirroring packets are not tagged. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.3.
Hierarchy level [edit forwarding-options] introduced in Junos OS Release 13.2X50-D10 (ELS). | [
"Example: Configuring Mirroring for Remote Monitoring of Employee Resource Use on EX4300",
"Switches"
] |
no-tag | no-tag; | [edit ethernet-switching-options analyzer name output vlan (vlan-id | vlan-name)],
[edit forwarding-options port-mirroring family ethernet-switching output vlan (vlan-name | vlan-
id)],
[edit forwarding-options port-mirroring instance instance-name family ethernet-switching output
vlan (vlan-name | vlan-id)] | Specify that remote port-mirroring packets are not tagged with the tag of the output (analyzer) VLAN. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.3.
Hierarchy [edit forwarding-options port-mirroring family ethernet-switching output vlan] introduced in Junos
OS Release 13.2.
Hierarchy [edit forwarding-options port-mirroring instance instance-name family ethernet-switching output vlan]
introduced in Junos OS Release 13.2... | [
"Example: Configuring Port Mirroring for Local Monitoring of Employee Resource Use on EX Series",
"Switches"
] |
no-temperature-monitoring | no-temperature-monitoring; | [edit chassis fpc fpc_slot pic pic_slot port port_no],
[edit chassis lcc name fpc name pic name port],
[edit chassis member name fpc name pic name port] | Disable EM policy. Disable temperature monitoring to explicitly disable optics temperature sensors for
EM policy monitoring and management, on specific WAN ports.
NOTE: When you enable no-temperature-monitoring and configure set system syslog file
messages any any command to get all relevant outputs, the following mess... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.4R1. | [] |
no-termination-request | no-termination-request; | [edit interfaces interface-name ppp-options],
[edit interfaces lsq-fpc/pic/port lsq-failure-options] | Inhibit PPP termination-request messages to the remote host if the primary circuit fails. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4.
Support at the [edit interfaces interface-name ppp-options] hierarchy level added in Junos OS Release 8.3. | [
"Configuring the Association between LSQ and SONET Interfaces"
] |
no-throttle (Resource Monitor) | no-throttle; | [edit system services resource-monitor] | Disable the throttling of subscriber services and sessions when the utilization of memory resources
exceeds the threshold levels. For the subscriber service management, sessions are throttled based on
line card resources, such as heap, counter memory, expansion memory, and firewall counter memory. If
the resource has b... | [
{
"name": "no-throttle",
"desc": "Disable the throttling of subscriber services and sessions when the utilization of memory resources exceeds the threshold levels. The throttling capability is enabled by default."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [] |
no-tls-certificate-check | no-tls-certificate-check; | [edit access profile profile-name ldap-server ip-address] | Specify validation of the server certificate not required. SRX Series Firewalls support an additional check
on the Lightweight Directory Access Protocol (LDAP) server’s certificate during the Transport Layer
Security (TLS) handshake for LDAP authentication. If the validation of the server certificate is not
required, y... | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D70. | [
"Firewall User Authentication Overview",
"Example: Configuring Integrated User Firewall on SRX Series"
] |
no-transit-statistics | no-transit-statistics; | [edit logical-systems logical-system-name protocols mpls statistics],
[edit protocols mpls statistics] | (PTX Series only) Disables the collection of MPLS statistics for LSPs transiting the router. | [] | routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2 . | [
"Configuring MPLS to Gather Statistics"
] |
no-translation (Source NAT Next Gen Services) | no-translation; | [edit services nat source pool nat-pool-name port] | Disable port translation for NAT. By default, port translation is enabled for NAT. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [] |
no-translation | no-translation; | [edit services nat rule rule-name term term-name then] | Specify that traffic is not to be translated.
The no-translation statement is supported on MX series routers with MS-DPCs and on M Series routers
with MS-100, MS-400, and MS-500 MultiServices PICS. The no-translation statement is supported on
MX series routers with MS-MPCs and MS-MICs starting in Junos OS release 15.1R... | [
{
"name": "none",
"desc": ""
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Network Address Translation Rules Overview"
] |
no-trap | no-trap {
mpls-lsp-traps;
rfc-3812-traps;
} | [edit logical-systems logical-system-name protocols mpls log-updown],
[edit protocols mpls log-updown] | Prevent the transmission of SNMP traps. | [
{
"name": "mpls-lsp-traps",
"desc": "Block the MPLS LSP traps defined in therfc-3812-traps, but allows the rfc3812.mib traps."
},
{
"name": "rfc-3812-traps",
"desc": "Block the traps defined in the rfc3812.mib, but allows the MPLS LSP traps defined in the"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
The mpls-lsp-traps and rfc-3812-traps options added in Junos OS Release 9.0. | [
"System Log Messages and SNMP Traps for MPLS",
"Junos OS Network Management Administration Guide for Routing Devices"
] |
no-tunnel-services | no-tunnel-services; | [edit logical-systems logical-system-name protocols vpls static-vpls],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls],
[edit protocols vpls static-vpls],
[edit routing-instances routing-instance-name protocols vpls] | Configure VPLS on a router without a Tunnel Services PIC. Configuring the no-tunnel-services statement
creates a label-switched interface (LSI) to provide VPLS functionality. An LSI MPLS label is used as the
inner label for VPLS. This label maps to a VPLS routing instance. On the PE router, the LSI label is
stripped an... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6.
Support for static VPLS added in Junos OS Release 10.2. | [
"Configuring VPLS Without a Tunnel Services PIC",
"Configuring Static Pseudowires for VPLS",
"Configuring EXP-Based Traffic Classification for VPLS"
] |
no-unknown-unicast | no-unknown-unicast; | For platforms with Enhanced Layer 2 Software (ELS)
(EX Series switches and MX Series routers):
[edit forwarding-options storm-control-profiles profile-name all]
For platforms without ELS:
[edit ethernet-switching-options storm-control interface (all | interface-name)] | Disable storm control for unknown unicast 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 avail... | [] | 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-unregistered-multicast | no-unregistered-multicast; | For platforms with Enhanced Layer 2 Software (ELS)
(EX Series switches and MX Series routers):
[edit forwarding-options storm-control-profiles profile-name all]
For platforms without ELS:
[edit ethernet-switching-options storm-control interface (all | interface-name)] | (EX8200 switches only) Disable storm control for unregistered multicast traffic for the specified
interface or for all interfaces.
(EX4300 and EX9200 switches only) Exclude storm control for unregistered multicast traffic from a
storm control profile.
(MX Series routers) Exclude storm control for unregistered multicas... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.3.
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.) | [
"Understanding Storm Control",
"Understanding Storm Control"
] |
no-unsolicited-ra (Enhanced Subscriber Management) | no-unsolicited-ra; | [edit system services subscriber-management overrides] | Disable the default transmission and periodic refresh of unsolicited Router Advertisement messages by
the router when the subscriber interface is created, and at configured periodic intervals thereafter.
When you include the no-unsolicited-ra statement, the router sends Router Advertisement messages and
associated peri... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1R3. | [
"Configuring Junos OS Enhanced Subscriber Management"
] |
no-uri-check | no-uri-check; | [edit security utm default-configuration anti-virus scan-options] | Do not perform Sophos antivirus Uniform Resource Identifier (URI) checking. URI checking is performed
by analyzing HTTP traffic URI content against a remote Sophos database server to identify malware or
malicious content. URI checking is on by default.
NOTE: Starting in Junos OS release 18.4R1, the URI checking is off... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
no-user-query (Services User Identification) | no-user-query; | [edit services user-identification authentication-source (Services User Identification ClearPass)
aruba-clearpass] | Disable the integrated ClearPass authentication and enforcement user query function, if it is configured.
You can use the no-user-query statement to turn off the user query function without having to delete
the configuration.
The user query function allows the SRX Series Firewall to query the ClearPass webserver for
au... | [] | services
To view this statement in the configuration.
services-control
To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
no-validate | no-validate policy-name; | [edit protocols bgp group group-name family (inet | inet flow)],
[edit protocols bgp group group-name neighbor address family (inet | inet flow)],
[edit routing-instances routing-instance-name protocols bgp group group-name family (inet | inet
flow)],
[edit routing-instances routing-instance-name protocols bgp group g... | When BGP is carrying flow-specification network layer reachability information (NLRI) messages, the no-
validate statement omits the flow route validation procedure after packets are accepted by a policy.
The receiving BGP-enabled device accepts a flow route if it passes the following criteria:
•
The originator of a fl... | [
{
"name": "policy-name",
"desc": "Import policy to match NLRI messages."
}
] | 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: Enabling BGP to Carry Flow-Specification Routes",
"Understanding BGP Flow Routes for Traffic Filtering"
] |
no-vlan-interface-name | no-vlan-interface-name; | [edit forwarding-options dhcp-relay dhcpv6 (relay-agent-interface-id | relay-agent-remote-id)],
[edit forwarding-options dhcp-relay dhcpv6 group group-name (relay-agent-interface-id | relay-agent-
remote-id)],
[edit forwarding-options dhcp-relay relay-option-82 (circuit-id | remote-id)],
[edit forwarding-options dhcp-r... | When you do not want bridge domain or VLAN tag information, do not include the VLAN ID nor the
VLAN interface name (the default) in the circuit or remote ID value in the DHCP option 82 information.
NOTE: The no-vlan-interface-name statement is mutually exclusive with the use-interface-
description and use-vlan-id state... | [] | 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.
NOTE: The EX Series switches that support the no-vlan-interface-name statement are the
EX4300, EX4600, and EX9200 switches. | [
"Including a Textual Description in DHCP Options",
"Using DHCP Relay Agent Option 82 Information",
"Configuring DHCPv6 Relay Agent Options"
] |
no-vrf-advertise | no-vrf-advertise; | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | Prevent advertising VPN routes from a VRF routing instance to remote PE routers.
Within a hub-and-spoke configuration, you can configure a PE router to not advertise VPN routes from
the primary (hub) routing instance. Instead, these routes are advertised from the secondary
(downstream) routing instance. You can do this... | [] | 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 Policies for the VRF Table on PE Routers in VPNs",
"Configuring Hub-and-Spoke VPN Topologies: One Interface",
"Limiting Routes to Be Advertised by an MVPN VRF Instance"
] |
no-vrf-propagate-ttl | no-vrf-propagate-ttl; | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | Disable normal time-to-live (TTL) decrementing in a VRF routing instance. You configure this statement
once per routing instance, and it affects only RSVP-signaled or LDP-signaled LSPs in the routing
instance. When this router acts as an ingress router for an LSP, it pushes an MPLS header with a TTL
value of 255, regar... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Example: Diagnosing Networking Problems Related to Layer 3 VPNs by Disabling TTL Decrementing",
"Disabling Normal TTL Decrementing"
] |
no-walkup | no-walkup; | [edit logical-systems logical-system-name policy-options defaults route-filter],
[edit logical-systems logical-system-name policy-options policy-statement policy-statement-name
defaults route-filter] | Override route filter walkup globally or locally for a particular policy statement. The walkup feature
examines more than the longest match route filters in a policy statement term with more than one route
filter, allowing consolidation of terms and a potential performance enhancement.
Default
By default, the policy st... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Walkup for Route Filters Overview",
"Configuring Walkup for Route Filters to Improve Operational Efficiency",
"Example: Configuring Walkup for Route Filters Globally to Improve Operational Efficiency",
"Example: Configuring Walkup for Route Filters Locally to Improve Operational Efficiency"
] |
no-world-readable (Next Gen Services Global System Logging) | no-world-readable | [edit services rtlog traceoptions file] | 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": "world-readable",
"desc": "Do not allow any user to read the log file"
}
] | 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",
"world-readable (Next Gen Services Global System ... |
no-zero-suppression | no-zero-suppression | [edit services analytics zero-suppression] | 21.4R1
Statement introduced in Junos OS Release 21.4R1 for MX240, MX280, and MX960 operating with
MPC10E-10-MRATE, MPC10E-10C-MRATE, MPC10E-15C-MRATE line cards and MX2010 and
MX2020 operating with the MX2K-MPC11E line card.
21.1R1
Statement introduced in Junos Evolved OS Release 21.1R1 for PTX10003-80C and PTX10003-16... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [] | |
node (Chassis Cluster Redundancy Group) | node (0 | 1 ) {
priority number;
} | [edit chassis cluster redundancy-group group-number ] | Identify each cluster node in a redundancy group and set its relative priority for primary role.
A redundancy group is collection of objects. A redundancy group contains objects on both nodes. A
redundancy group is primary on one node and backup on the other at any time. When a redundancy
group is said to be primary on... | [
{
"name": "node",
"desc": "Cluster node number, You can set with the set chassis cluster node node-number statement. Values:"
},
{
"name": "0",
"desc": "Node identifier 0"
},
{
"name": "1",
"desc": "Node identifier 1"
},
{
"name": "priority",
"desc": ""
},
{
"nam... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [] |
node (System) | node {
offline node-name;
} | [edit system] | Specify a node by name and set node attributes. A node is a computational resource: it has a general-
purpose CPU and can be used to do useful work. An attribute is a specific detail about a node. | [
{
"name": "offline node-name",
"desc": "Configure a particular node to be offline."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 18.4R1. | [] |
node-detection (EVPN-VXLAN) | node-detection {
action (laser-off | trigger-node-isolation);
bfd-liveness-detection {
no-adaptation;
detection-time {
threshold milliseconds;
}
inline-disable;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier multiplier;
neighbor neighbor;
pdu-size pdu... | [edit logical-systems name protocols evpn],
[edit protocols evpn] | Configure node detection to enable "bfd-liveness-detection" on page 3128 in a multihomed
environment. Node detection monitors the liveness of EVPN BGP peers using Bidirectional Forwarding
Detection (BFD) protocol. Configure one of the peers to take action to forward traffic through the
network based on the status of th... | [
{
"name": "action",
"desc": "Configure the isolation action only on one device and not both. The isolation action determines how to implement the core isolation."
},
{
"name": "laser-off",
"desc": "Will trigger laser-off on core-isolation"
},
{
"name": "trigger-node-isolation",
"desc... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.3R1 and Junos OS Evolved Release 23.3R1. | [
"Backup Liveness Detection on EVPN Dual Homing"
] |
node-device (Aliases) | node-device node-device-name {
assigned-node-device-name;
} | [edit fabric aliases] | (QFabric systems only) Specify the mapping of user-defined names to QFabric system Node devices.
NOTE: The following rules apply to QFabric component alias naming:
•
Alias names must use alphabetic (A through Z and a through z), numeric (0 through 9),
or dash (-) characters.
•
The maximum length of an alias name is 30 ... | [
{
"name": "node-device-name",
"desc": "Specify a user-defined name for a QFabric system Node device."
},
{
"name": "assigned-node-device-name",
"desc": "Specify the Node device identifier or name that has been provided. Identifiers are usually autogenerated by the Director software, and names ar... | 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 Aliases for the QFabric System",
"Understanding Node Devices"
] |
node-device (Chassis) | node-device name {
fibre-channel {
port-range {
port-range-low port-range-high;
}
}
pic pic-number {
fte {
port port-number;
port-range port-range-low port-range-high;
}
xe {
port port-number;
port-range por... | [edit chassis node-group] | Configure properties specific to a Node device in a QFabric system.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.3. | [
"Configuring Link Aggregation"
] |
node-device (Flow Groups) | node-device (node-device-name | serial-ID | alias ); | [edit fabric flow-groups flow-group-name] | In a QFabric system, a hash function is used to select an Interconnect device to forward traffic between
two Node devices. Since this hash function is performed on all available Interconnect devices, it is
possible for redundant multicast streams to flow through one Interconnect device, making that
Interconnect device ... | [
{
"name": "node-device-name (or serial-ID or alias)",
"desc": "selects the indicated ingress Node device switch for a flow"
},
{
"name": "group",
"desc": ""
}
] | 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-D15. | [
"Segregating QFabric Traffic Flows With Flow Groups",
"Example: Creating a QFabric Flow Group",
"Understanding QFabric Multicast Flow Groups"
] |
node-device (Resources) | node-device node-device-name; | [edit fabric resources node-group node-group-name] | (QFabric systems only) Assign Node devices to Node groups within a QFabric system.
NOTE: Ensure that the Node devices you assign to a redundant server Node group are of
the same type, either two QFX3500 Node devices, two QFX3600 Node devices, or two
QFX5100 Node devices. You cannot mix and match different Node device t... | [] | 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"
] |
node-group (Chassis) | node-group name {
aggregated-devices {
ethernet {
device-count number;
}
}
alarm {
interface-type {
link-down (ignore | red | yellow);
}
}
container-devices {
device-count number;
}
node-device name {
fibre-channel {
... | [edit chassis] | Configure properties specific to a Node group.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.3. | [
"Configuring Link Aggregation"
] |
node-group (OxID Hash Control) | node-group (node-group-name | all) {
oxid (enable | disable);
} | [edit forwarding-options hash-key family fcoe ethernet-interfaces]
[edit forwarding-options hash-key family fcoe fabric-interfaces] | Specify a QFabric system Node group on which to enable or disable OxID hash control. OxID hash
control is enabled or disabled on the fabric ports or on the Ethernet (FCoE) LAG ports that face an FCoE
forwarder (FCF). | [
{
"name": "node-group",
"desc": "Name of the Node group on which you want to enable OxID hash control."
},
{
"name": "all",
"desc": "All Node groups on the QFabric system (OxID hash control will be enabled or disabled on all Node groups). The remaining statement is explained separately. See CLI ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X52-D10. | [
"Enabling and Disabling CoS OxID Hash Control for FCoE Traffic on QFabric Systems",
"Understanding OxID Hash Control for FCoE Traffic Load Balancing on QFabric Systems"
] |
node-group (Resources) | node-group node-group-name {
network-domain;
node-device node-device-name;
} | [edit fabric resources] | (QFabric systems only) Define Node groups within a QFabric system.
NOTE: The following rules apply to QFabric Node group naming:
•
The network Node group must use the predefined name NW-NG-0. You must use
this name when adding Node devices to the network Node group. You cannot specify
a different name. Also, you can co... | [] | 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"
] |
node-hello | (node-hello | no-node-hello); | [edit logical-systems logical-system-name protocols rsvp],
[edit protocols rsvp] | Enable node-ID based RSVP hellos globally on all of the RSVP interfaces on the router to allow Juniper
Networks routers to interoperate with the equipment of other vendors. By default, node-ID based RSVP
hellos are enabled. To disable node-id based hello sessions, use the no-node-hello statement. If you have
disabled R... | [] | 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 RSVP Node-ID Hellos"
] |
node-id | node-id mac-address; | [edit protocols protection-group ethernet-ring ring-name] | For EX Series switches and QFX Series switches, node-id is not configurable.
For MX Series routers, optionally specify the MAC address of a node in the protection group. If this
statement is not included, the router assigns the node’s MAC address. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Ethernet Ring Protection Switching Overview",
"Example: Configuring Ethernet Ring Protection Switching on EX Series Switches",
"Example: Configuring Ethernet Ring Protection Switching on QFX Series and EX Series Switches",
"Supporting ELS"
] |
node-link-protection (Protocols MPLS) | node-link-protection; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name] | Enable node and link protection on the specified LSP. To fully enable node and link protection, you also
need to include the link-protection statement at the [edit protocols rsvp interface interface-name] hierarchy
level.
Default
Node and link protection is disabled. | [] | 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 Release 14.1X53-D10 for the QFX Series and for EX4600 switches. | [
"Configuring Node Protection or Link Protection for LSPs",
"MPLS Feature Support on QFX Series and EX4600 Switches",
"Understanding Interprovider and Carrier-of-Carriers VPNs"
] |
node-protection (Static LSP) | node-protection bypass-name name next-next-label label; | [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-label],
[edit protocols mpls static-label-switched-path lsp-name ingress],
[edit protocols mpls static-la... | Enable node protection on the specified static bypass LSP. Node protection ensures that traffic from an
LSP traversing a neighboring router can continue to reach its destination even if the neighboring router
fails.
Default
Node protection is disabled. | [
{
"name": "bypass-name name",
"desc": "Bypass LSP name."
},
{
"name": "next-next-label label",
"desc": "Bypass LSP name."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in JUNOS Release 10.1. | [
"Configuring Static LSPs"
] |
node-protection | node-protection cost cost; | [edit logical-systems name protocols isis interface name level number post-convergence-lfa],
[edit logical-systems name routing-instances name protocols isis interface name level number post-
convergence-lfa],
[edit protocols isis interface name level number post-convergence-lfa],
[edit routing-instances name protocols... | Enable node protection mode for topology-independent loop-free alternate (TI-LFA) routes for IS-IS.
You can configure the cost of all the links used for calculating the TI-LFA post-convergence failure path
cost. If node protection is enabled without configuring a cost value, then the cost is set to the maximum
cost. | [
{
"name": "cost",
"desc": "Cost for node protection. Range: 0 through 16,777,215"
}
] | routing | Statement introduced in Junos OS Release 17.4R1 for MX Series, PTX Series, and QFX Series. | [
"Understanding Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS",
"Configuring Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS"
] |
node-segment (Protocols OSPF) | node-segment {
ipv4-index index;
index-range index range;
} | [edit logical-systems logical-system-name protocols ospf source-packet-routing],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf
source-packet-routing],
[edit protocols ospf source-packet-routing],
[edit routing-instances routing-instance-name protocols ospf source-pack... | Enable source packet routing in networking (SPRING) at all levels. SPRING, or segment routing, is a
control-plane architecture that enables an ingress router to steer a packet through a specific set of
nodes and links in the network without relying on the intermediate nodes in the network to determine
the actual path i... | [
{
"name": "index-range index range",
"desc": "Range of node segment indices allowed. Default: 4096 Range: 32 through 4096"
},
{
"name": "ipv4-index index",
"desc": "IPv4 node segment index. Range: 0 through 4095"
}
] | 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"
] |
non-active-hold-priority | non-active-hold-priority non-active-hold-priority-value; | [edit logical-systems name protocols mpls label-switched-path name secondary name non-active-hold-
priority],
[edit logical-systems name routing-instances name protocols mpls label-switched-path name secondary
name non-active-hold-priority],
[edit logical-systems name tenants name routing-instances name protocols mpls... | Configure the non-active hold priority value for secondary standby path.
Default
There is no default value for non-active-hold-priority.
Range
0 through 7, where 0 is the highest and 7 is the lowest priority. | [] | routing | Statement introduced in Junos OS Release 21.2R1. | [] |
non-lsp-next-hop | non-lsp-next-hop; | [edit class-of-service forwarding-policy next-hop-map map-name forwarding-class class-name] | Use a non-LSP next hop for traffic sent to this forwarding class next-hop map of this forwarding policy. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 9.0. | [
"Configuring CoS-Based Forwarding"
] |
non-revertive (Chassis) | non-revertive; | [edit chassis aggregated-devices ethernet lacp link-protection] | Disable the ability to switch to a better priority link (if one is available) once a link is established as active
and a collection or distribution is enabled.
BEST PRACTICE: (MX Series) By default, Link Aggregation Control Protocol link
protection is revertive. This means that after the current link becomes active, th... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Configuring Junos OS for Supporting Aggregated Devices",
"Configuring LACP Link Protection of Aggregated Ethernet Interfaces for Switches"
] |
non-revertive (Interfaces) | non-revertive; | [edit interfaces aeX aggregated-ether-options lacp link-protection] | Disable the ability to switch to a better priority link (if one is available) once a link is established as active
and collection distribution is enabled. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Configuring Aggregated Ethernet Link Protection",
"Configuring LACP Link Protection of Aggregated Ethernet Interfaces for Switches"
] |
non-revertive | non-revertive; | [edit protocols protection-group ethernet-ring ring-name] | Enable nonrevertive operation where traffic is allowed to use the RPL if it has not failed, even after a
switch condition has cleared. The default mode of operation is revertive. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Ethernet Ring Protection Switching Overview",
"Configuring Ethernet Ring Protection Switching on Switches (CLI Procedure)"
] |
non-strict-priority-scheduling | non-strict-priority-scheduling; | [edit class-of-service],
[edit dynamic-profiles name class-of-service] | Configure non-strict priority scheduling to avoid starvation of lower-priority queues on SRX300,
SRX320, SRX340, SRX345, SRX1500, SRX1600, SRX550M, and vSRX Virtual Firewall 2.0 devices. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D80.
NOTE: This statement is supported only on SRX300, SRX320, SRX340, SRX345,
SRX550M, SRX1500, SRX1600, and vSRX2.0 firewalls. | [
"Example: Configuring CoS Non-Strict Priority Scheduling"
] |
non-subscriber-no-reply | non-subscriber-no-reply; | [edit system arp] | Enable this option to drop ARP requests from non-subscribers when a user route is dynamically added
for a subscriber. Configuring this statement suppresses the ARP response from the kernel when there is
an ARP request for a loopback interface from static DHCP subscribers using a common LAN segment
between two devices. ... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3R9. | [] |
non-vc-mode | non-vc-mode; | [edit protocols protection-group ethernet-ring ring-name] | Configure a node on the sub-ring to operate in non-virtual channel mode. If this option is enabled then
all the nodes in the sub-ring are configured with this option. Also, the non-vc-mode option should be used
with care and only for open rings. Using this option for closed rings creates loops for RAPS control
messages... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Ethernet Ring Protection Switching Overview",
"Configuring Ethernet Ring Protection Switching on Switches (CLI Procedure)"
] |
nonpersistent | nonpersistent; | [edit accounting-options file filename] | Store log files used for accounting data in the mfs/var/log directory (located on DRAM) instead of the
cf/var/log directory (located on the compact flash drive). This feature is useful for minimizing read/write
traffic on the router’s compact flash drive.
NOTE: If log files for accounting data are stored on DRAM, these... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Configuring Accounting Options, Source Class Usage and Destination Class Usage Options"
] |
nonstop-bridging (Ethernet Switching) | nonstop-bridging; | [edit ethernet-switching-options] | For switches with two Routing Engines or for Virtual Chassis, configure a primary Routing Engine to
switch over gracefully to a backup Routing Engine and preserve Layer 2 protocol information for the
Layer 2 protocols that support nonstop bridging (NSB). For a list of the EX Series switches and Layer 2
protocols that s... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.3. | [
"Configuring Nonstop Bridging on EX Series Switches (CLI Procedure)"
] |
nonstop-bridging | nonstop-bridging; | [edit protocols layer2-control] | For platforms with two Routing Engines, configure a primary Routing Engine to switch over gracefully to
a backup Routing Engine and preserve Layer 2 Control Protocol (L2CP) information. | [] | 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. | [
"Synchronizing the Routing Engine Configuration",
"Configuring Nonstop Bridging",
"Configuring Nonstop Bridging on EX Series Switches (CLI Procedure)",
"Configuring Nonstop Bridging on Switches (CLI Procedure)"
] |
nonstop-routing | nonstop-routing; | [edit routing-options]
NOTE: Although nonstop-routing is also a valid keyword at the logical-systems hierarchy
level, it is not supported. | For routing platforms with two Routing Engines, configure a primary Routing Engine to switch over
gracefully to a backup Routing Engine and to preserve routing protocol information.
Default
disabled | [] | 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. | [
"Configuring Nonstop Active Routing"
] |
nonstop-routing-options | nonstop-routing-options {
precision-timers-max-period precision-timers-max-period;
} | [edit routing-options] | For routing platforms with two Routing Engines, a primary Routing Engine is configured to switch over
gracefully to a backup Routing Engine. This allows the routing protocol information to be preserved even
after failover. Support of precision-timers in the kernel is a feature where the kernel takes over
autogeneration... | [
{
"name": "precision-timers-max-period",
"desc": ""
},
{
"name": "precision-timers-max-period",
"desc": "The maximum period for which the kernel auto generates keepalives on behalf of BGP after a switchover event from backup to primary. NOTE: You can verify the precision-timers-max-period using ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.2. | [
"Understanding Maximum Period Configuration for Automatic Generation of BGP Keepalives by",
"Kernel Timers After Switchover"
] |
nonvolatile | nonvolatile {
commit-delay seconds;
} | [edit snmp] | Configure options for SNMP Set requests.
The remaining statement is explained separately. See CLI Explorer. | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
The commit-delay statement introduced in Junos OS Release 9.0 for EX Series switches. | [] |
normalization (Protocols EVPN) | normalization; | [edit routing-instances name protocols evpn] | Enable normalization, which translates ingress or egress VLANs to another VLAN ID.
Default
Routing instances configure as instance-type evpn have normalization enabled by default.
Routing instances configured as instance-type mac-vrf have normalization disabled by default. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 21.3R1 | [] |
normalization | normalization {
failover-normalization;
no-incremental-normalize;
normalization-retry-duration seconds;
normalization-retry-limits number;
normalize-interval seconds;
} | [edit protocols mpls container-label-switched-path lsp-name splitting-merging] | Perform normalization. | [
{
"name": "failover-normalization",
"desc": "Enable the ingress router to pro-actively normalize or re-distribute traffic when a link or node failure happens on a member LSP. A member LSP can go down between two scheduled normalization events because of a link-failure or pre-emption. Default: Disabled"
}... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
not (Event Policy) | not events [ events ]; | [edit event-options policy policy-name within seconds] | Configure an event policy to trigger only if the events in the not statement do not occur within a
specified time interval before one of the trigger events. | [
{
"name": "events [ events ]",
"desc": "List of events. Events can be generated by Junos OS processes, or they can be internally generated."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Use Correlated Events to Trigger an Event Policy"
] |
not-on-disk-underperform | not-on-disk-underperform; | [edit chassis redundancy failover] | Prevent gstatd from causing failovers in dual Routing Engines set for graceful Routing Engine switchover
(GRES). The gstatd log message is still generated. This is an optional configuration.
NOTE: Configure the disk-write-threshold and disk-read-threshold statements to customize
the gstatd timeout threshold. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3R6. | [
"Preventing Graceful Routing Engine Switchover in the Case of Slow Disks"
] |
not-present (DHCP Relay Agent) | not-present {
drop drop;
forward-only forward-only;
local-server-group local-server-group;
} | [edit bridge-domains name forwarding-options dhcp-relay group name relay-option],
[edit bridge-domains name forwarding-options dhcp-relay group name relay-option option-60],
[edit bridge-domains name forwarding-options dhcp-relay group name relay-option option-77],
[edit bridge-domains name forwarding-options dhcp-rela... | Option not present action | [] | 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. | [
"DHCPv4 and DHCPv6 Forward-Only Action for Relay Traffic with Unknown DHCP Server Address"
] |
notification (Commit) | notification; | [edit system commit] | Notify applications upon commit completion. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R3. | [] |
notification (NETCONF) | notification {
interleave;
} | [edit system services netconf] | Enable the NETCONF event notification service. When this service is enabled on supported devices, the
NETCONF server sends asynchronous event notifications to clients that subscribe to notifications
within a NETCONF session.
NOTE: We recommend that you configure and stream only one set of notifications,
either NETCONF ... | [
{
"name": "interleave",
"desc": "Enable the NETCONF client and server to exchange RPCs and RPC replies within a NETCONF session that subscribes to event notifications."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 21.2R1.
interleave statement introduced in Junos OS Evolved Release 23.4R1. | [
"NETCONF Event Notifications"
] |
notification (System Services) | notification {
allow-clients {
address ip-address;
}
broker-socket-send-buffer-size broker-socket-send-buffer-size;
max-connections max-connections;
port port;
} | [edit system services extension-service] | Enable notification services for applications. | [
{
"name": "allow-clients address",
"desc": ""
},
{
"name": "ip-address",
"desc": "(Required) Specify IPv4 or IPv6 addresses (prefix length optional) or host names of clients that are allowed to request notifications from the application. You can specify a set of values using square brackets ([ ]... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [] |
notification | notification {
log-attacks {
alert;
}
packet-log (Security IDP Policy) {
post-attack number;
post-attack-timeout seconds;
pre-attack number;
}
} | [edit security idp idp-policy policy-name rulebase-ips rule rule-name then] | Configure the logging options against the action. When attacks are detected, you can choose to log an
attack and create log records with attack information and send that information to the log server. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. Added packet capture support in Junos OS Release 10.2. | [] |
notification-control | notification-control {
fpc slot-number {
disable;
}
} | [edit poe] | Enable or disable the generation of PoE SNMP traps. If PoE SNMP traps are enabled, an SNMP trap is
sent whenever a PoE interface is enabled or disabled.
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 9.0. | [
"Example: Configuring PoE Interfaces with Different Priorities on an EX Series Switch",
"Configuring PoE Interfaces on EX Series Switches"
] |
notification-interval | notification-interval seconds; | [edit ethernet-switching-options mac-notification]
[edit switch-options mac-notification] | Configure the MAC notification interval for a switch.
The MAC notification interval is the amount of time the switch waits before sending learned or
unlearned MAC address SNMP notifications to the network management server. For instance, if the
MAC notification interval is set to 10, all of the MAC address addition and... | [
{
"name": "seconds",
"desc": "The MAC notification interval, in seconds. Range: 1 through 60 Default: 30"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6.
Hierarchy level [edit switch-options] added in Junos OS Release 14.1X53-D10 for EX Series and QFX
Series. | [
"Configuring Non-ELS MAC Notification",
"Configuring MAC Notification on Switches with ELS Support"
] |
notification-options (Security Antivirus) | notification-options {
fallback-block {
custom-message custom-message;
custom-message-subject custom-message-subject;
(notify-mail-sender | no-notify-mail-sender);
type (message | protocol-only);
}
... | [edit security utm default-configuration anti-virus],
[edit security utm default-configuration anti-virus sophos-engine],
[edit security utm feature-profile anti-virus profile],
[edit security utm feature-profile anti-virus sophos-engine profile],
[edit logical-systems name security utm default-configuration anti-virus... | There are multiple notification options you can configure to trigger when a virus is detected. | [
{
"name": "reputation-block",
"desc": "Specify the Sophos file reputation block notofication."
},
{
"name": "custom-message custom-message",
"desc": "Specify the custom message for the reputation block notication."
},
{
"name": "custom-message-subject custom-message-subject",
"desc":... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5.
Support for Sophos engine added in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS R... | [] |
notification-options (Security Content Filtering) | notification-options {
custom-message message;
(notify-mail-sender | no-notify-mail-sender);
type (message | protocol-only);
} | [edit security utm default-configuration]
[edit security utm feature-profile content-filtering profile profile-name] | You can configure a message notification to trigger when a content filter is 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.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Content Filtering Overview"
] |
notification-targets | notification-targets address port port-number; | [edit services dynamic-flow-capture capture-group client-name control-source identifier] | List the destination IP addresses and User Datagram Protocol (UDP) ports to which DFC PICs log
exception information and control protocol state transitions, such as timeout values. | [
{
"name": "address",
"desc": "Allowed destination IP address."
},
{
"name": "port port-number",
"desc": "Allowed destination UDP port number."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring the Control Source"
] |
notification-time | notification-time seconds; | [edit protocols l2-learning global-mac-move] | (MX Series routers only) Configure the notification time value for MAC move reports that a MAC
address moves before counting against the threshold values.
Default
1 second | [
{
"name": "seconds",
"desc": "Time elapsed before MAC move reports are generated."
}
] | 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.
Support for logical systems added in Junos OS Release 9.6. | [
"Configuring MAC Move Parameters"
] |
notify | notify name {
tag tag-name;
type (trap | inform);
} | [edit snmp v3] | Select management targets for SNMPv3 notifications as well as the type of notifications. Notifications
can be either traps or informs. | [
{
"name": "name",
"desc": "Name assigned to the notification."
},
{
"name": "tag-name",
"desc": "Notifications are sent to all targets configured with this tag."
},
{
"name": "type",
"desc": "Notification type is trap or inform. Traps are unconfirmed notifications. Informs are confir... | 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.
type inform option added in Junos OS Release 7.4. | [] |
notify-filter (Applying to the Management Target) | notify-filter profile-name; | [edit snmp v3 target-parameters target-parameters-name] | Specify the notify filter to be used by a specific set of target parameters. | [
{
"name": "profile-name",
"desc": "Name of the notify filter to apply to notifications."
}
] | 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. | [] |
notify-filter (Configuring the Profile Name) | notify-filter profile-name {
oid oid (include | exclude);
} | [edit snmp v3] | Specify a group of MIB objects for which you define access. The notify filter limits the type of traps or
informs sent to the network management system. | [
{
"name": "profile-name",
"desc": "Name assigned to the notify filter."
}
] | 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. | [] |
notify-mail-recipient | notify-mail-recipient; | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name
notification-options fallback-non-block]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name
notification-options fallback-non-block]
[edit security ... | Notify the e-mail recipient about errors returned by the antivirus scan engine when a fallback
nonblocking action occurs.
You can specify that the e-mail recipient is not to be notified with the no-notify-mail-recipient statement. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5. Support for Sophos
engine added in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS R... | [] |
notify-mail-sender (Security Content Filtering Notification Options) | notify-mail-sender; | [edit security utm default-configuration]
[edit security utm feature-profile content-filtering profile profile-name notification-options] | Notify the e-mail sender. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Content Filtering Overview"
] |
notify-mail-sender (Security Fallback Block) | notify-mail-sender; | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name
notification-options fallback-block]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name
notification-options fallback-block]
[edit security utm featu... | E-mail notification is used to notify the sender or the recipient about the errors returned by either the
scan engine or the scan manager when a fallback action occurs.
You can specify that the sender is not to be notified with the no-notify-mail-sender statement. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5 . Support for Sophos
engine added in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS ... | [] |
notify-mail-sender (Security Virus Detection) | notify-mail-sender; | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name
notification-options virus-detection]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name
notification-options virus-detection]
[edit security utm fea... | E-mail notification is used to notify the sender or the recipient about the detected viruses or the
scanning errors. When a virus is detected, an e-mail is sent to the sender upon virus detection.
You can specify that the sender is not to be notified with the no-notify-mail-sender statement. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5 . Support for Sophos
engine added in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS ... | [] |
notify-view | notify-view view-name; | [edit snmp v3 vacm access group group-name (default-context-prefix | context-prefix context-
prefix) security-model (any | usm | v1 | v2c) security-level (authentication | none | privacy)] | Associate the notify view with a community (for SNMPv1 or SNMPv2c clients) or a group name (for
SNMPv3 clients). | [
{
"name": "view-name",
"desc": "Name of the view to which the SNMP user group has access."
}
] | 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. | [] |
np-cache (Flexible PIC Concentrator) | np-cache; | [edit chassis fpc fpc-slot-number] | Enable session cache table on IOC.
Starting with Junos OS Release 15.1X49-D10 and and Junos OS Release 17.3R1, NP cache is supported
on the SRX5K-MPC (IOC2), SRX5K-MPC3-100G10G (IOC3), and SRX5K-MPC3-40G10G (IOC3) for
SRX5400, SRX5600, and SRX5800 devices.
From Junos OS Release 21.2R1, np-cache is enabled by default.
T... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 15.1X49-D10. | [] |
nptv6-prefix | nptv6-prefix {
address-prefix;
routing-instance routing-instance-name; | [edit security nat static rule-set rule-set-name rule rule-name then static-nat] | Specify a static IPv6 address prefix. The longest prefix supported is /64. | [
{
"name": "address-prefix",
"desc": "Specify the address prefix."
},
{
"name": "routing-instance",
"desc": "Use the user-defined static NAT routing instance to perform 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 12.3X48-D25. | [] |
nptv6-prefix-name | nptv6-prefix-name {
address-prefix-name;
routing-instance routing-instance-name; | [edit security nat static rule-set rule-set-name rule rule-name then static-nat] | Specify an address prefix name from an address book. The longest prefix name supported is /64. | [
{
"name": "address-prefix-name",
"desc": "Specify an address prefix name from an address book."
},
{
"name": "routing-instance",
"desc": "Use the user-defined static NAT routing instance to perform 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 12.3X48-D25. | [] |
nsr-phantom-holdtime | nsr-phantom-holdtime seconds; | [edit routing-options] | Specify to hold phantom IP addresses, that is, prevent these routes from being added to routing tables,
for a specified period of time. During this hold-time interval, these routes are maintained in the kernel.
After the hold time expires, the routes are added to the routing tables.
You use this option with the Gracefu... | [
{
"name": "seconds",
"desc": "Specify the interval of time to prevent phantom IP addresses from being added to the routing tables. After this interval expires, the routes are added to the routing tables. BEST PRACTICE: In an EVPN/VXLAN environment with NSR and GRES enabled, the recommended hold-time value i... | 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-D60. | [
"Understanding Graceful Routing Engine Switchover",
"Preventing Traffic Loss in an EVPN/VXLAN Environment With GRES and NSR",
"Example: Configuring Nonstop Active Routing on Switches"
] |
nssa | nssa {
area-range network/mask-length <restrict> <exact> <override-metric metric>;
default-lsa {
default-metric metric;
metric-type type;
type-7;
}
(no-summaries | summaries);
} | [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(ospf | ospf3) area area-id],... | Configure a not-so-stubby area (NSSA). An NSSA allows external routes to be flooded within the area.
These routes are then leaked into other areas.
You cannot configure an area as being both a stub area and an NSSA.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "summaries |",
"desc": ""
},
{
"name": "no-summaries",
"desc": "Configure whether or not area border routers advertise summary routes into an not-so-stubby area (NSSA):"
},
{
"name": "summaries",
"desc": "Flood summary link-state advertisements (LSAs) into the NSSA."
},
... | 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 the realm statement introduced in Junos OS Release 9.2.
Support for the realm statement introduced in Junos OS Release 9.2 for EX Series switches. | [
"Understanding OSPF Areas",
"Example: Configuring OSPF Not-So-Stubby Areas"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.