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 |
|---|---|---|---|---|---|---|---|
voip-mac-exclusive | voip-mac-exclusive; | [edit ethernet-switching-options secure-access-port interface (all | interface-name)],
[edit switch-options voip interface (all | interface-name)] | NOTE: [edit switch-options voip interface (all | interface-name)] is not supported on ELS on
switches that use Enhanced Layer 2 Software (ELS).
Restrict a VoIP client MAC address to be learned only in a configured VoIP VLAN.
If the voip-exclusive-mac statement is configured at the [edit ethernet-switching-options secu... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in JUNOS Release 13.2X50-D10. | [
"Overview of Port Security"
] |
volume-limit (LRF Rule) | volume-limit volume; | [edit services lrf profile profile-name rule lrf-rule-name then report] | Configure the data volume limit to be used for reporting. The template that the LRF rule is using must
have trigger-type volume configured. | [
{
"name": "volume",
"desc": "Data volume, in megabytes. Range: 1 through 1024"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support for Next Gen Services introduced in Junos OS Release 19.3R1 on MX Series. | [
"Configuring Logging and Reporting for Junos OS Subscriber Aware",
"Configuring an LRF Profile for Subscribers",
"Configuring Logging and Reporting for Subscriber Management"
] |
vpi (Define Virtual Path) | vpi vpi-identifier {
maximum-vcs maximum-vcs;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (disable | seconds);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate
burst length);
queue-length number;
}... | [edit interfaces at-fpc/pic/port atm-options] | For ATM interfaces, configure the virtual path (VP).
NOTE: Certain options apply only to specific platforms. | [
{
"name": "vpi-identifier",
"desc": "ATM virtual path identifier. This is one of the VPIs that you define in the \"vci\" on page"
},
{
"name": "page 31843.)",
"desc": "Range: 0 through 255 The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Maximum Number of ATM1 VCs on a VP"
] |
vpls (Interfaces) | vpls; | [edit interfaces interface-name unit logical-unit-number family],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family] | Specify the VPLS protocol family information for the logical interface. | [] | 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 Interfaces for VPLS Routing"
] |
vpls (Routing Instance) | vpls {
mac-pinning;
active-interface {
any;
primary interface-name;
}
community COMM;
connectivity-type (ce | irb);
control-word;
encapsulation-type ethernet;
ignore-encapsulation-mismatch;
ignore-mtu-mismatch;
import-labeled-routes [ routing-instance-name ];
... | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit routing-instances routing-instance-name protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "service-type single",
"desc": "Allows one vlan per routing instance."
}
] | 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.
mac-flush option introduced in Junos OS Release 10.0.
hot-standby-vc-on, import-labeled-routes [ routing-instance-name ], and interface interface options introduced in
Junos OS Release 15.1R2. | [
"Configuring VPLS Routing Instances"
] |
vpls-flow-table-size | vpls-flow-table-size units; | [edit chassis fpc slot-number inline-services flow-table-size] | Configure the size of the VPLS flow table in units of 256K entries.
NOTE: Any change in the configured size of the flow table size initiates an automatic
reboot of the FPC.
NOTE: Starting with Junos OS Release 17.3R1, the maximum number of 256K flow
entries that you can configure for IPv4 flow tables and IPv6 flow tab... | [
{
"name": "units",
"desc": "Number of 256K flow entries available for the VPLS flow table. Range: 1 through 245 Default: 15 (3840K)"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250"
] |
vpls-flush-on-topology-change | vpls-flush-on-topology-change; | [edit logical-systems logical-system-name protocols (mstp | rstp)],
[edit logical-systems logical-system-name protocols vstp vlan vlan-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(mstp | rstp)],
[edit logical-systems logical-system-name routing-instances routing-ins... | Determine the action the bridge should take when the topology of a multihomed Layer 2 ring with
MPLS infrastructure changes: flush the media access control (MAC) cache or not. By default, the bridge
does not flush the cache when the topology changes. | [] | 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. | [] |
vpls-id | vpls-id vpls-id; | [edit logical-systems logical-system-name routing-instances instance-name protocols l2vpn],
[edit logical-systems logical-system-name routing-instances instance-name protocols l2vpn mesh-
group mesh-group-name],
[edit logical-systems logical-system-name routing-instances instance-name protocols vpls],
[edit logical-sys... | Identify the virtual circuit identifier used for the VPLS routing instance or mesh group. This statement is
a part of the configuration to enable LDP signaling for VPLS. | [
{
"name": "vpls-id",
"desc": "Specify a valid identifier for the VPLS routing instance."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [
"Configuring LDP Signaling for VPLS"
] |
vpls-id-list (protocols vpls mesh-group) | vpls-id-list vc-id-numbers; | [edit routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name neighbor
address] | The vpls-id-list option allows you to configure multiple pseudowires under LDP-VPLS neighbor by
creating one pseudowire per virtual circuit id. This combination of neighbor and virtual circuit ID must
be unique across the l2circuit and all local LDP-VPLS instances. The pseudowire will terminate in the
specified mesh-gr... | [
{
"name": "vc-id-numbers",
"desc": "The virtual circuit ID for the PE pair. This ID can be any number in the range of 1 to"
}
] | 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 . | [] |
vpls-mac-move | vpls-mac-move{
cooloff-time seconds;
interface-recovery-time seconds;
statistical-approach-wait-time seconds;
virtual-mac mac-address /mask;
} | [edit protocols l2-learning] | Configure VPLS MAC move parameters to prevent loop creation in the network. | [
{
"name": "cooloff-time",
"desc": ""
},
{
"name": "seconds",
"desc": "Time interval, in seconds, during which no additional interface is disabled by the PE after a MAC move is detected. By default, it is 30 seconds."
},
{
"name": "interface-recovery-time seconds",
"desc": "Time inter... | 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.
Statement changed to global-mac-move in Junos OS Release 17.4R1 | [
"MAC Moves Loop Prevention in VPLS Network Overview",
"Example: Configuring Loop Prevention in VPLS Network Due to MAC Moves"
] |
vpls-template | vpls-template; | [edit services flow-monitoring version-ipfix template] | Specify that the IPFIX template is used only for VPLS records. Starting in Junos OS Release 18.2R1, the
vpls-template option is deprecated; use the bridge-template option instead. The bridge-template option
supports both VPLS and bridge records. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13 .2. | [
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250"
] |
vpn (Security) | vpn vpn-name {
bind-interface interface-name;
no-hw-offload;
df-bit (clear | copy | set);
distribution-profile (default-spc2-profile | default-spc3-profile | distribution-profile-name);
copy-outer-dscp;
establish-tunnels (immediately | on-traffic | responder-only | responder-only-no-rekey);
... | [edit security ipsec] | Configure an IPsec VPN. A VPN provides a means by which remote computers communicate securely
across a public WAN suchas the Internet. A VPN connection can link two LANs (site-to-site VPN) or a
remote dial-up user and a LAN. The trafficthat flows between these two points passes through shared
resources such as routers,... | [
{
"name": "vpn-name",
"desc": "Name of the VPN."
},
{
"name": "bind-interface",
"desc": "Configure the tunnel interface to which the route-based virtual private network (VPN) is bound."
},
{
"name": "copy-outer-dscp",
"desc": "Enable copying of Differentiated Services Code Point (DSC... | 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.
Support for IPv6 addresses added in Junos OS Release 11.1.
Support for copy-outer-dscp added in Junos OS Release 15.1X49-D30.
verify-path keyword and destination-ip added in Junos OS Release 15.1X49-D70.
packet-size option added in Junos OS Release 15.1X49-D120.
Support for... | [
"IPsec Overview"
] |
vpn-apply-export | vpn-apply-export; | [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 neighbor],
[edit protocols bgp],
[edit protocols bgp group group-name],
[edit protocols bgp group group-... | Apply both the VRF export and BGP group or neighbor export policies (VRF first, then BGP) before
routes from the vrf or l2vpn routing tables are advertised to other PE routers. | [] | 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"
] |
vpn-global-import | vpn-global-import [ vpn-global-import ... ]; | [edit logical-systems name routing-instances name routing-options rib],
[edit logical-systems name routing-options rib],
[edit logical-systems name tenants name routing-instances name routing-options rib],
[edit routing-instances name routing-options rib],
[edit routing-options rib] | Enable leaking of BGP VPN routes to global RIBs to provide service providers the flexibility to allow
internet access to VPN customers. Leaking routes of a customer VPN into master global Internet RIBs
like inet.0and inet6.0 is for customer route prefixes that come from global Internet namespace and are
not private add... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.2R1. | [] |
vpn-group-address | Use group-address in place of vpn-group-address.
vpn-group-address address; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim],
[edit routing-instances routing-instance-name protocols pim] | Configure the group address for the Layer 3 VPN in the service provider’s network. | [
{
"name": "address",
"desc": "Address for the Layer 3 VPN in the service provider’s network."
}
] | 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.
Starting with Junos OS Release 11.4, to provide consistency with draft-rosen 7 and next-generation
BGP-based multicast VPNs, configure the provider tunnels for draft-rosen 6 anysource multicast VPNs
at the [edit routing-instances routing-instance-name provider-tunnel] h... | [
"Configuring Multicast Layer 3 VPNs",
"Junos OS Multicast Protocols User Guide"
] |
vpn-label | vpn-label; | [edit chassis memory-enhanced] | Allocate more jtree memory for Layer 3 VPN labels. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement added in Junos OS Release 10.4. | [
"Allocating More Memory for Routing Tables, Firewall Filters, and Layer 3 VPN Labels"
] |
vpn-localization | vpn-localization {
vpn-core-facing-default;
vpn-core-facing-only;
} | [edit chassis fpc fpc-slot-number] | Configure FPC as either core-facing default or core-facing only in order to localize the routes. | [
{
"name": "vpn-core-facing-default",
"desc": "The core-facing FPC installs all the routes and next hops of the CE-facing interfaces."
},
{
"name": "vpn-core-facing-only",
"desc": "The core-facing FPC installs all the routes and does not store next hops of the CE-facing interfaces."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Understanding VRF Localization in Layer 3 VPNs",
"Example: Improving Scalability Using VRF Localization for Layer 3 VPNs"
] |
vpn-monitor | vpn-monitor {
destination-ip ip-address;
optimized;
source-interface interface-name;
verify-path {
destination-ip ip-address;
packet-size bytes;
}
} | [edit security ipsec vpn vpn-name] | Configure settings for VPN monitoring. | [
{
"name": "destination-ip",
"desc": "Specify the destination of the Internet Control Message Protocol (ICMP) pings. If this statement is used, the device uses the peer's gateway address by default."
},
{
"name": "optimized",
"desc": "Enables VPN monitoring optimization for the specific VPN tunne... | 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.
Support for verify-path keyword and destination-ip added in Junos OS Release 15.1X49-D70.
Support for packet-size option added in Junos OS Release 15.1X49-D120.
Support for vpn-monitor and verify-path options with IPsec VPN running iked process is introduced in
Junos OS Re... | [
"IPsec Overview"
] |
vpn-unequal-cost | vpn-unequal-cost {
equal-external-internal;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multipath],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name multipath],
[edit routing-instances routing-instance-name routing-options multipath],
... | When the vpn-unequal-cost statement is configured, protocol-independent load balancing is applied to
VPN routes that are equal to interior gateway protocol (IGP) metrics. If the vpn-unequal-cost statement is
not configured, then protocol-independent load balancing is applied to VPN routes that are equal to the
router i... | [
{
"name": "equal-external-internal",
"desc": "Specifies that both external and internal BGP paths can be selected for multipath."
}
] | 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 equal-external-internal option was added for
Junos OS Release 8.4. | [
"Configuring Protocol-Independent Load Balancing in Layer 3 VPNs",
"Load Balancing and IP Header Filtering for Layer 3 VPNs"
] |
vpws-service-id | vpws-service-id {
local service-id;
remote serivce-id;
source-packet-routing {
srv6;
locator locator-name {
end-dx2-sid end-dx2-sid;
micro-dx2-sid micro-sid-value;
}
}
} | [edit routing-instances instance-name protocols evpn interface interface-name] | Specify the local and remote Ethernet VPN (EVPN)-Virtual Private Wire Service (VPWS) service
identifiers. These service identifiers are unique to an EVPN and are used to identify the endpoints of the
EVPN-VPWS network. These endpoints are auto-discovered by BGP and are used to exchange the
service labels (learned from ... | [
{
"name": "local",
"desc": "Unique local VPWS service identifier of the EVPN-VPWS network. This identifies the logical interface of the PE router forwarding traffic to the PE router with a remote VPWS service identifier in the EVPN-VPWS network. Range: 1 through 16,777,215"
},
{
"name": "remote",
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
source-packet-routing statement introduced in Junos OS Release 22.4R1.
locator statement introduced in Junos OS Release 22.4R1.
end-dx2-sid statement introduced in Junos OS Release 22.4R1.
micro-dx2-sid statement introduced in Junos OS Evolved Release 24.2R1 | [
"Overview of VPWS with EVPN Signaling Mechanisms",
"EVPN Multihoming Overview",
"Configuring VPWS with EVPN Signaling Mechanisms",
"Example: Configuring VPWS with EVPN Signaling Mechanisms",
"Configuring EVPN-VPWS over SRv6"
] |
vrf | vrf [ vrf ... ]; | [edit security zones security-zone] | VRF in this zone | [] | Security—To view this statement in the configuration.
Security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1 | [
"Configuring Security Policies for a VRF Routing Instance"
] |
vrf-advertise-selective | vrf-advertise-selective {
family {
inet-mvpn;
inet6-mvpn;
}
} | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | Explicitly enable IPv4 or IPv6 MVPN routes to be advertised from the VRF instance while preventing all
other route types from being advertised.
If you configure the vrf-advertise-selective statement without any of its options, the router or switch has
the same behavior as if you configured the no-vrf-advertise statemen... | [] | 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. | [
"Limiting Routes to Be Advertised by an MVPN VRF Instance"
] |
vrf-export | vrf-export [ policy-names ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
mesh-group mesh-group-name]
[edit protocols evpn interconnect]
[edit routing-instances routing-instance-name]
[edit routing-instances rou... | Specify how the device exports routes from the routing table routing-instance-name.inet.0 to other
devices. If the instance-type in the routing instance configuration is vrf, you must either:
•
Include this statement to apply a routing export policy in the routing instance.
•
Use the vrf-target statement with a commun... | [
{
"name": "policy-names",
"desc": "Names for the export policies."
}
] | 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 at the following hierarchy levels introduced in Junos OS Release 20.3R1 on QFX Series
switches: [edit protocols evpn interconnect] and [edit routing-instances routing-instance-name protocols evpn
interconnect]. | [
"Implementing EVPN-VXLAN for Data Centers",
"Configuring Policies for the VRF Table on PE Routers in VPNs"
] |
vrf-import | vrf-import [ policy-names ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls mesh-group mesh-group-name]
[edit protocols evpn interconnect]
[edit routing-instances routing-instance-name]
[edit routing-instances ro... | Specify how routes are imported into the routing table (routing-instance-name.inet.0) of the local device
from the remote device.
You can configure multiple import policies on the device.
One of the following statements is required for importing routes:
•
vrf-target - When you configure the vrf-target community statem... | [
{
"name": "policy-names",
"desc": "Names for the import policies."
}
] | 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 at the following hierarchy levels introduced in Junos OS Release 20.3R1 on QFX Series
switches: [edit protocols evpn interconnect] and [edit routing-instances routing-instance-name protocols evpn
interconnect]. | [
"Implementing EVPN-VXLAN for Data Centers",
"Configuring Policies for the VRF Table on PE Routers in VPNs"
] |
vrf-mtu-check | vrf-mtu-check; | [edit chassis] | On M Series routers (except the M120 and M320 router) and on EX Series 8200 switches, configure
path maximum transmission unit (MTU) checks on the outgoing interface for unicast traffic routed on a
virtual private network (VPN) routing and forwarding (VRF) instance.
Default
Disabled. | [] | 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 Path MTU Checks for VPN Routing Instances",
"Configure Path MTU Discovery"
] |
vrf-name (Duplicate Accounting) | vrf-name vrf-name; | [edit access profile profile-name accounting duplication-vrf] | Specify a nondefault VRF (LS:RI combination) to which duplicate accounting information is sent. Up to
five access profiles can be defined in this VRF; the profiles point to the RADIUS accounting servers that
receive the accounting information. | [
{
"name": "vrf-name",
"desc": "Name of a nondefault VRF to receive duplicate accounting reports."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3R3 and supported in later 12.3Rx releases.
Statement supported in Junos OS Release 13.2 and later releases. (Not supported in Junos OS Release
13.1.) | [
"RADIUS Accounting for Subscriber Access",
"RADIUS Authentication and Accounting Basic Configuration"
] |
vrf-propagate-ttl | vrf-propagate-ttl; | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | Enable 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 copies the TTL value
from the IP packe... | [] | 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"
] |
vrf-table-label | vrf-table-label {
source-class-usage;
static;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | Map the inner label of a packet to a specific VPN routing and forwarding (VRF) instance. This allows the
examination of the encapsulated IP header. The first lookup is done on the VPN label to determine
which VRF instance to refer to, and the second lookup is done on the IP header to determine how to
forward packets to... | [] | 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 source-class-usage statement added in Junos OS Release 9.3.
Support for the static statement added in Junos OS Release 17.2. | [
"Filtering Packets in Layer 3 VPNs Based on IP Headers",
"Configuring EXP-Based Traffic Classification for VPLS",
"Load Balancing and IP Header Filtering for Layer 3 VPNs"
] |
vrf-target | vrf-target {
community;
auto;
import community;
export community;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
l2vpn mesh-group mesh-group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
mesh-group... | Specify a virtual routing and forwarding (VRF) target community. This value is a route target extended
community.
The vrf-target statement simplifies configuring a route target by enabling you to configure the
statements for route sharing in a routing instance at the [edit routing-instances] hierarchy level. In effect,... | [
{
"name": "community",
"desc": "Community name in the format target:community-id, where target is a required keyword"
},
{
"name": "auto",
"desc": "Automatically derives the route target. The auto-derived route targets have higher precedence"
},
{
"name": "import community",
"desc": ... | 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.
auto option added in Junos OS Release 19.1R1 for MX series.
Support at the following hierarchy levels introduced in Junos OS Release 20.3R1 on QFX Series
switches: [edit protocols evpn interconnect] and [edit routing-instances routing-instance-name protocols evpn
interc... | [
"Auto-derived Route targets",
"Configuring Policies for the VRF Table on PE Routers in VPNs",
"Example: Configuring FEC 129 BGP Autodiscovery for VPWS"
] |
vrrp | vrrp {
command binary-file-path;
disable;
failover (alternate-media | other-routing-engine);
} | [edit system processes] | Specify the Virtual Router Redundancy Protocol (VRRP) process. | [
{
"name": "command binary-file-path",
"desc": "Path to the binary process."
},
{
"name": "disable",
"desc": "Disable the VRRP process."
},
{
"name": "failover",
"desc": "Configure the device to reboot if the software process fails four times within 30 seconds,"
},
{
"name": "... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
vrrp-group | vrrp-group group-id {
(accept-data | no-accept-data);
advertise-interval seconds;
advertisements-threshold number;
authentication-key key;
authentication-type (md5 | simple);
fast-interval milliseconds;
no-accept-data;
no-preempt;
preempt {
hold-time seconds;
}
preferred... | [edit interfaces name unit name family inet address],
[edit interfaces name unit name family inet inet6 address]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet address address] | The Routing Engine performs one-by-one state change for subsequent VRRP groups. Every time there is
a state change, and the new state for a particular VRRP group is primary, the Routing Engine generates
appropriate VRRP announcement messages. When the first VRRP group detected by the Routing Engine
changes state, and t... | [
{
"name": "group-id",
"desc": "VRRP group identifier. If you enable MAC source address filtering on the interface, you must include the virtual MAC address in the list of source MAC addresses that you specify in the source-address-filter statement. MAC addresses ranging from 00:00:5e:00:53:00 through 00:00:... | interface | Statement introduced before Junos OS Release 18.1R1. | [
"Understanding VRRP on SRX Series Devices",
"Example: Configuring VRRP/VRRPv3 on Chassis Cluster Redundant Ethernet Interfaces"
] |
vrrp-inet6-group | vrrp-inet6-group group-id {
(accept-data | no-accept-data);
advertisements-threshold number;
fast-interval milliseconds;
inet6-advertise-interval seconds;
(preempt | no-preempt) {
hold-time seconds;
}
priority number;
track {
interface interface-name {
bandwid... | [edit interfaces interface-name unit logical-unit-number family inet6 address address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet6 address address] | Configure a Virtual Router Redundancy Protocol (VRRP) IPv6 group.
NOTE: The group identifier that you enter must be different from any other group
identifiers that you configured for logical units of this same physical interface. | [
{
"name": "group-id",
"desc": "VRRP group identifier. If you enable MAC source address filtering on the interface, you must"
}
] | 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 Basic VRRP Support"
] |
vrrp-inherit-from | vrrp-inherit-from {
active-group group-index;
active-interface active-interface-name;
} | [edit interfaces interface-name unit logical-unit-number family inet6 vrrp-inet6-group group-id]
[edit interfaces interface-name unit logical-unit-number family inet No Link Title group-id] | VRRP group to follow for the vrrp-group or vrrp-inet6-group. | [
{
"name": "group-index",
"desc": "Identifier for VRRP active group."
},
{
"name": "active-interface-name",
"desc": "Interface name of VRRP active group."
}
] | 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. | [
"Understanding VRRP"
] |
vsi-discovery | vsi-discovery {
interface interface-name
vsi-policy vsi-policy-name
} | [edit protocols edge-virtual-bridging] | Configure Virtual Station Interface (VSI) Discovery and Configuration Protocol (VDP). VDP is used to
program policies for each individual station interface (VSI).
Default
VDP is disabled by default. | [
{
"name": "interface-name",
"desc": "Name of the interface on which VDP is configured. The remaining statement is explained separately."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | [
"Example: Configuring Edge Virtual Bridging for Use with VEPA Technology on an EX Series Switch",
"Configuring Edge Virtual Bridging on an EX Series Switch"
] | |
vsi-policy | vsi-policy vsi-policy-namefrom vsi-manager vsi-manager-id vsi-type vsi-type vsi-version vsi-
version vsi-instance instance-number; | [edit policy-options] | Define and apply the named VSI policy to the edge virtual bridging (EVB) configuration. For use with
edge virtual bridging, each virtual machine (VM) on the server is uniquely identified by following four
parameters, which are contained in a VSI policy:
•
vsi-manager-id
•
vsi-type
•
vsi-version
•
vsi-instance-id
The vs... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | [
"Example: Configuring Edge Virtual Bridging for Use with VEPA Technology on an EX Series Switch",
"Configuring Edge Virtual Bridging on an EX Series Switch"
] | |
vstp | [edit protocols]
[edit logical-systems logical-system-name protocols],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit protocols],
[edit routing-instances routing-instance-name protocols] | Configures VLAN Spanning Tree Protocol (VSTP). VSTP is used to prevent loops in Layer 2 networks on
a per-VLAN basis.
You can have a maximum of 253 VSTP VLANs per switch.
If the number of VLANs on your switch exceeds the VSTP VLAN limit, you must use the vlan statement
to specify which VLANs or VLAN groups use VSTP. Yo... | [] | 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.
bpdu-block-on-edge statement added in Junos OS Release 9.4.
bpdu-timeout-action statement added in Junos OS Release 9.4.
Support for logical systems added in Junos OS Release 9.6.
Statement updated in Junos OS Release 15.1 for EX Series switches to support configuration of
... | [
"Understanding VSTP",
"Configuring VLAN Spanning Tree Protocol",
"Configuring VSTP (CLI Procedure)",
"Example: Configuring VSTP on QFX Series Switches and EX4600 Switches"
] | |
vtep-source-interface | vtep-source-interface
interface-name (inet | inet6 ); | [edit switch-options]
[edit routing-instances routing-instance-name] | Configure a source interface for a Virtual Extensible LAN (VXLAN) tunnel. You must provide the name of
a logical interface configured on the loopback interface.
If you specify an IPv4 address (inet option) as the VTEP source address, the VXLAN tunnel endpoint
(VTEP) encapsulates VXLAN packets with an IPv4 outer header ... | [
{
"name": "interface-name",
"desc": "Loopback interface name."
},
{
"name": "inet",
"desc": "IPv4 source address."
},
{
"name": "colored-tunnel-address",
"desc": "Specify an IPv4 address as the VXLAN tunnel endpoint (VTEP)"
},
{
"name": "inet6",
"desc": "IPv6 source addre... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10.
Support at the [edit routing-instances routing-instance-name] hierarchy level introduced in Junos OS Release
17.3. | [
"Understanding VXLANs",
"EVPN-VXLAN with an IPv6 Underlay",
"Manually Configuring VXLANs on QFX Series and EX4600 Switches",
"Examples: Manually Configuring VXLANs on QFX Series and EX4600 Switches"
] |
vulnerability-type | vulnerability-type {
values [ values ];
} | [edit security idp (Security) dynamic-attack-group name filters] | Vulnerability type of attack.
Vulnerabilities are the intersection of three elements: a system susceptibility or flaw, attacker access to
the flaw, and attacker capability to exploit the flaw. A security risk is often incorrectly classified as a
vulnerability.
Using this field you can perform vulnerability scanning. Vu... | [
{
"name": "values",
"desc": "Values for vulnerability-type field (for example: buffer overflow, injection, use after free, Cross-site scripting (XSS), Remote Code Execution (RCE), and so on. Specifying the vulnerability type for IDP will indicate which applications are weak and therefore can be manipulated.... | security | Statement introduced in Junos OS Release 18.2R1. | [] |
vxlan | vxlan {
encapsulate-inner-vlan;
ingress-node-replication;
mtu mtu;
multicast-group multicast-group-address;
ovsdb-managed;
riot-loopback;
unreachable-vtep-aging-timer;
vni;
} | [edit vlans name],
[edit bridge-domains bridge-domain-name] | Configure support for Virtual Extensible LANs (VXLANs) on a Juniper Networks device. | [
{
"name": "mtu mtu",
"desc": "(cRPD only) Specify the maximum transmission unit (MTU) size for a VXLAN packet. Range: 100 to 65535 bytes."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10.
ingress-node-replication option added for EVPN VXLAN on QFX5100 switches in Junos OS
Release 14.1X53-D30.
multicast-group multicast-group option added for MX series routers with MPC and MIC interfaces in Junos
OS Release 17.2.
mtu option added for cRPD in Junos OS R... | [
"Understanding VXLANs",
"Using a RIOT Loopback Port to Route Traffic in an EVPN Network",
"Manually Configuring VXLANs on QFX Series and EX4600 Switches",
"Examples: Manually Configuring VXLANs on QFX Series and EX4600 Switches"
] |
vxlan-disable-copy-tos-decap | vxlan-disable-copy-tos-decap | [edit forwarding-options] | Disable copying the Type of Service (ToS) field from the outer IP header in a Virtual Extensible LAN
(VXLAN) packet to the inner IP header when de-encapsulating the original packet. The ToS field includes
values for differentiated services code points (DSCP) and explicit congestion notification (ECN).
In networks where... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to a configuration. | Statement introduced in Junos OS Release 18.4R2 to disable copying the DSCP bits in the ToS field
during VXLAN de-encapsulation.
Support added in Junos OS Release 21.1R1 for copying and disabling copy of ECN bits in the ToS field
during VXLAN de-encapsulation. | [
"Understanding VXLANs"
] |
vxlan-disable-copy-tos-encap | vxlan-disable-copy-tos-encap | [edit forwarding-options] | Disable copying the Type of Service (ToS) field from the IP header of a packet to the outer IP header of a
Virtual Extensible LAN (VXLAN) packet when encapsulating the packet. The ToS field includes values for
differentiated services code points (DSCP) and explicit congestion notification (ECN).
In networks where you c... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R2 to disable copying the DSCP bits in the ToS field
during VXLAN encapsulation.
Support added in Junos OS Release 21.1R1 for copying and disabling copy of ECN bits in the ToS field
during VXLAN encapsulation. | [
"Understanding VXLANs"
] |
vxlan-extended | vxlan-extended; | [edit system packet-forwarding-options system-profile] | On ACX7100-32C, ACX7100-48L, and ACX7024 devices, you can use either an IPv4 or IPv6 underlay
for a VXLAN configuration. To use an IPv6 underlay, enable the vxlan-extended system profile.
Before you enable the vxlan-extended system profile, remove any existing VXLAN configurations. After
you enable the vxlan-extended s... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.4R1. | [] |
vxlan-gbp-l2-profile | vxlan-gbp-l2-profile; | [edit chassis forwarding-options] | Enable vxlan-gbp-l2-profile on the tunnel termination endpoint in your EVPN-VXLAN deployment to
support group-based policies. This setting tells the switch to allocate a share of its resources for L2/L3
group-based policies, whereas otherwise the resources would remain committed for use by all other
flows.
The vxlan-gb... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 for supported EX4400, EX4650, and QFX5120 Series
switches. | [
"GBP Profiles"
] |
vxlan-gbp-l3-profile | vxlan-gbp-l3-profile; | [edit chassis forwarding-options] | Enable vxlan-gbp-l3-profile on the tunnel termination endpoint in your EVPN-VXLAN deployment to
support group-based policies. This setting tells the switch to allocate a share of its resources for L2/L3
group-based policies, whereas otherwise the resources would remain committed for use by all other
flows.
The vxlan-gb... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 for supported EX4400, EX4650, and QFX5120 Series
switches. | [
"GBP Profiles"
] |
vxlan-gbp-mc-profile | vxlan-gbp-mc-profile; | [edit chassis forwarding-options] | Enable the vxlan-gbp-mc-profile unified forwarding table (UFT) profile on the tunnel termination endpoint
in your EVPN-VXLAN deployment to support multicast traffic flows and group-based policy (GBP)
unicast traffic flows together.
GBP makes use of existing Layer 3 (L3) VXLAN network identifiers (VNI) and firewall filt... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.2R2-S2. | [
"GBP Profiles",
"Optimized Inter-Subnet Multicast in EVPN Networks"
] |
vxlan-gbp-profile | vxlan-gbp-profile | [edit chassis forwarding-options] | Enable vxlan-gbp-profile on the tunnel termination endpoint in your EVPN-VXLAN deployment to
support group-based policies. This setting tells the switch to allocate a share of its resources for L2/L3
group-based policies, whereas otherwise the resources would remain committed for use by all other
flows. Note that for s... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1 for EX4400 Series switches. | [
"GBP Profiles"
] |
vxlan-gpe (FTI) | vxlan-gpe {
destination {
address address;
}
destination-udp-port destination-udp-port;
source {
address address;
interface interface;
}
source-udp-port-range {
(min min-port-number| max max-port-number)
}
tunnel-endpoint vxlan;
vni vni;
} | [edit dynamic-profiles name interfaces name unit name tunnel encapsulation],
[edit interfaces name unit name tunnel encapsulation] | Virtual Extensible LAN (VXLAN) is defined as an encapsulation format that encapsulates Ethernet
frames in an outer UDP/IP transport. The vxlan-gpe encapsulation refers to the header gpe added to the
encapsulation vxlan to extend the existing VXLAN protocol to provide support for multiprotocol
encapsulation. | [
{
"name": "destination-udp-port",
"desc": "Value to write to the destination-udp-port field. Range: 1 through 65,535"
},
{
"name": "source-udp-port-range",
"desc": "Value to write to the source-udp-port-range field. min min-port-number : 1 through 65,535."
},
{
"name": "max max-port-nu... | interface | Statement introduced in Junos OS Release 18.3R1. | [
"Flexible Tunnel Interfaces Overview",
"Configuring Flexible Tunnel Interfaces",
"Example: Configuring Flexible Tunnel Interfaces on MX Series Routers"
] |
vxlan-routing | vxlan-routing {
interface-num integer;
loopback-port;
next-hop integer;
overlay-ecmp;
} | [edit forwarding-options] | Configure Virtual Extensible LAN (VXLAN) routing options on a device.
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 17.3R1.
overlay-ecmp statement introduced in Junos OS Release 17.4R1.
loopback-port statement introduced in Junos OS Release 21.3R1 for QFX5210 switches. | [] |
vxlan-stitching | vxlan-stitching {
control-word;
} | [edit system packet-forwarding-options system-profile] | You must configure vxlan-stitching on ACX devices to support Virtual Extensible LAN (VXLAN) data
center interconnect (DCI) stitching features.
NOTE: The PFE will restart once this statement is applied. | [
{
"name": "control-word",
"desc": "Enable this option on an ACX device operating as a DCI gateway (GW) when both of the"
},
{
"name": "following are true:",
"desc": "Your MPLS network is using Ethernet VPN (EVPN-MPLS) for the overlay fabric. Your ACX DCI GW's peer device is using control-word. ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.2R1.
control-word option introduced in Junos OS Evolved Release 23.4R1. | [
"EVPN-VXLAN Data Center Interconnect Through EVPN-MPLS WAN Overview"
] |
vxlan-tos-copy-filter | vxlan-tos-copy-filter | [edit forwarding-options] | Copy the Type of Service (ToS) field from the IP header of a packet to the outer IP header of a Virtual
Extensible LAN (VXLAN) packet when encapsulating the packet. The ToS field includes values for
differentiated services code points (DSCP) and explicit congestion notification (ECN).
Default
For QFX5000 Series switche... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved 22.1R3, 22.2R2, 22.3R1. | [
"Understanding VXLANs",
"W"
] |
wait-for-acct-on-ack (Access Profile) | wait-for-acct-on-ack; | [edit access profile profile-name accounting] | Configure the router’s authd process to wait for an Acct-On-Ack response message from RADIUS before
sending new authentication and accounting updates to the RADIUS server. This configuration ensures
that when a new subscriber session starts, the authentication and accounting information for the new
session does not get... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"RADIUS Accounting for Subscriber Access",
"RADIUS Servers and Parameters for Subscriber Access"
] |
wait-to-block-interval | wait-to-block-interval number; | [edit protocols protection-group ethernet-ring ring-name] | Enable the Wait to Block (WTB) timer interval when clearing force switch and manual switch commands. | [
{
"name": "number",
"desc": "Wait-to-block interval, in seconds."
}
] | 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)"
] |
wait-to-restore | wait-to-restore minutes; | [edit chassis source interfaces (external-a | external-b | interface interface-name)],
[edit chassis source interfaces (external | interface interface-name)],
[edit chassis source interfaces (external-0/0 | external-1/0 | interface interface-name)] | Configure the time in minutes for each port to be up before opening the Ethernet Synchronization
Message Channel (ESMC) for messages. When a port’s signal transitions out of the signal fail state, it
must be fault-free for the wait-to-restore time before it is again considered by the clock selection
process.
NOTE: When... | [
{
"name": "minutes",
"desc": "Set the time for the port signal to be up before the port is opened to receive and transmit ESMC messages. Range: 0 through 12 minutes Default: 5 minutes"
}
] | 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. | [] |
walkup | 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],
[edit policy-options defaults route-filter],
[edit policy-options policy-statement policy-statement-name defaults rout... | Enable 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, no route filter... | [] | 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"
] |
wander-filter-disable | wander-filter-disable; | [edit chassis synchronization output interfaces external],
[edit chassis synchronization output interfaces (external-0/0 | external-1/0)] | Disable the wander filter on the output interface. | [] | 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. | [] |
warm-standby (Interfaces) | warm-standby; | [edit interfaces rlsqnumber redundancy-options] | For AS or Multiservices PIC redundancy configurations, specify that the failure detection and recovery
involves one backup PIC supporting multiple working PICs. Recovery time is not guaranteed. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0. | [
"Configuring LSQ Interface Redundancy in a Single Router Using Virtual Interfaces"
] |
warm-standby | warm-standby; | [edit routing-options] | Set the routing protocols process (rpd) mode to warm standby. Warm standby mode helps the backup
RE stay synchronized with the primary RE, allowing for faster RE switchover during GRES. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1.
Statement introduced in Junos OS Evolved Release 21.2R1. | [
"Understanding Graceful Routing Engine Switchover"
] |
warning | warning low-light-warning {
(link-down | syslog);
} | [edit interfaces interface-name optics-options] | Specifies the action to take if the receiving optics signal is below the optics low-light warning threshold.
Starting in Junos OS Release 15.1, for all QSFP-based interfaces, you need not explicitly configure the
syslog option. The syslog option is enabled by default. | [
{
"name": "link-down",
"desc": "Drop the 10-Gigabit Ethernet link and marks link as down."
},
{
"name": "syslog",
"desc": "Write the optics information to the system log."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1. | [
"Configuring Link Down Notification for Optics Options Alarm or Warning",
"100-Gigabit Ethernet OTN Options Configuration Overview"
] |
watch-list | watch-list {
[ routes ];
} | [edit interfaces dln unit logical-unit-number dialer-options] | On J Series Services Routers with ISDN interfaces, configure an ISDN list of routes to watch. Used only
for dialer watch. | [
{
"name": "routes",
"desc": "IP prefix of a route. Specify one or more. The primary interface is considered up if there is at least"
}
] | 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. | [] |
watchdog (PSM) | watchdog {
timeout value;
pat-frequency value;
} | [edit chassis psm]
[edit chassis pem] | Enable the power supply module (PSM) watchdog feature. Generally, Junos detects the thermal event
health events and takes the required action as per user configuration. However, if a thermal health event
causes Junos to go down, the PSM watchdog feature detects it and shuts down the router.
NOTE: The PSM watchdog featu... | [
{
"name": "timeout",
"desc": ""
},
{
"name": "value",
"desc": "Specify the watchdog timer in seconds. After the specified duration, the watchdog expires. Range: 600 through 900 seconds Default: 900 seconds On Junos OS, timeout value is not significant since this value is programmed to watchdog... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Platform-Specific Watchdog Behavior
Use Feature Explorer to confirm platform, and release support for specific features.
Use the following table to review platform-specific behaviors for your platform:
... | Statement introduced in Junos OS Release 20.1R1. | [
"Handle Thermal Health Events Using Thermal Health Check and PSM Watchdog"
] |
watchdog | watchdog {
disable;
enable;
timeout value;
} | [edit system processes] | Enable or disable the watchdog timer when Junos OS encounters a problem. | [
{
"name": "disable",
"desc": "Disable the watchdog timer."
},
{
"name": "enable",
"desc": "Enable the watchdog timer."
},
{
"name": "timeout value",
"desc": "Specify amount of time to wait in seconds."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
watchdog-timeout | watchdog-timeout seconds; | [edit access diameter peer peer-name] | Configure the amount of time to wait for a Device-Watchdog-Answer message. | [
{
"name": "seconds",
"desc": "Amount of time to wait. Range: 1 through 65,535 seconds Default: 30 seconds"
}
] | 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. | [] |
wavelength (IPLC) | wavelength nm;
wss-express-in fpc-slot;
}
switch interface-name;
} | [edit chassis fpc fpc-slot optical-options] | Specify the wavelength in nanometers (nm) that you want to configure on the IPLC port.
Default | [
{
"name": "nm",
"desc": "Wavelength in nanometers. It can be one of the following listed for the central wavelength in Table"
},
{
"name": "1:",
"desc": "Table 1932: IPLC Port Number, Wavelength, and Frequency Mapping Frequency"
},
{
"name": "[THz]",
"desc": "Central Wavelength"
},... | Statement introduced in Junos OS Releases 15.1F6 and 17.1R1. | [
"switch (IPLC)",
"wss-express-in (IPLC)"
] | |
wavelength | wavelength nm; | [edit interfaces interface-name optics-options] | For 10-Gigabit, 100-Gigabit, 400-Gigabit ZR, and 400-Gigabit ZR+ Ethernet DWDM interfaces only,
configure full C-band ITU-Grid tunable optics. | [
{
"name": "nm",
"desc": "Wavelength value. It can be one of the following:"
},
{
"name": "1528.38",
"desc": "1528.38 nanometers (nm), corresponds to a 50-GHz grid"
},
{
"name": "1528.77",
"desc": "1528.77 nm, corresponds to 50-GHz and 100-GHz grids"
},
{
"name": "1529.16",
... | 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. | [] |
web-authentication (Access Firewall-Authentication) | web-authentication {
banner {
fail string;
logout string;
success string;
}
default-profile profile-name;
logo file path;
timeout seconds;
} | [edit access firewall-authentication],
[edit logical-systems name tenants name access firewall-authentication],
[edit tenants name access firewall-authentication] | Specify that users go through the Web authentication process. The user uses HTTP or HTTPS to access
an IP address on the device that is enabled for Web authentication. In this scenario, the user does not
use HTTP or HTTPS to access the IP address of the protected resource. The user is prompted for a
username and passwo... | [
{
"name": "banner",
"desc": ""
},
{
"name": "success;",
"desc": "Configure the banner that appears to users during the Web authentication process. The banner appears during login, after successful authentication, and after failed authentication."
},
{
"name": "default-profile",
"desc... | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5.
HTTPS for Web authentication is supported on SRX5400, SRX5600, and SRX5800 devices starting from
Junos OS Release 12.1X44-D10 and on vSRX Virtual Firewall, SRX300, SRX320, SRX340, SRX345,
SRX380, and SRX1500 Services Gateways starting from Junos OS Release 15.1X49-D40.
Opti... | [
"Captive Portal Authentication",
"Example: Configure Captive Portal Authentication"
] |
web-authentication (Interfaces) | web-authentication {
http;
https;
redirect-to-https;
} | [edit interfaces interface-name unit logical-unit-number family family-name address] | Enable the Web authentication process for firewall user authentication. | [
{
"name": "http",
"desc": "Enable HTTP service."
},
{
"name": "https",
"desc": "Enable authentication through HTTPS."
},
{
"name": "redirect-to-https",
"desc": "Redirect Web authentication to HTTPS."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Support for https and redirect-to-https introduced for SRX5400, SRX5600, and SRX5800 Services
Gateways starting from Junos OS Release 12.1X44-D10 and on vSRX Virtual Firewall, SRX300, SRX320,
SRX340, SRX345, SRX380, SRX550, and SRX1500 Services Gateways starting from Junos ... | [
"Understanding Interfaces"
] |
web-authentication | web-authentication {
client-match user-or-group-name;
} | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
firewall-authentication] | Specify that the policy allows access to users who have previously been authenticated by Web
authentication. Web authentication must be enabled on one of the addresses on the interface to which
the HTTP or HTTPS request is redirected. | [
{
"name": "client-match user-or-group",
"desc": "(Optional) Username or user group name."
}
] | 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.
HTTPS for Web authentication is supported on SRX5400, SRX5600, and SRX5800 devices starting from
Junos OS Release 12.1X44-D10 and on vSRX Virtual Firewall, SRX300, SRX320, SRX340, SRX345,
SRX380, SRX550M, and SRX1500 Services Gateways starting from Junos OS Release 15.1X49-... | [
"Understanding User Role Firewalls"
] |
web-filter | web-filter {
profile (Web Filter) profile-name {
dns-filter {
database-file filename;
dns-resp-ttl seconds;
dns-server [ ip-address ];
hash-key key-string;
hash-method hash-method-name;
statistics-log-timer minutes;
wildcar... | [edit services] | Configure filtering of DNS requests for disallowed website domains. Filtering can result in either:
•
Blocking access to the site by sending the client a DNS response that includes an IP address or
domain name of a sinkhole server instead of the disallowed domain.
•
Logging the DNS request and allowing access.
The rema... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1 on MX Series.
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. | [
"DNS Request Filtering for Disallowed Website Domains"
] |
web-filter-profile | web-filter-profile profile-name; | [edit services service-set service-set-name] | Specify the DNS filter profile or the URL filter profile that the service set uses. The filter profile is
configured at the [edit services web-filter] hierarchy level, and specifies how to filter DNS requests for
disallowed website domains or how to filter access to disallowed URLs. | [
{
"name": "profile-name",
"desc": "Name of the DNS filter profile."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1.
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. | [
"DNS Request Filtering for Disallowed Website Domains"
] |
web-filtering (Logical System Security Feature Profile) | web-filtering {
juniper-enhanced {
profile name {
base-filter base-filter;
block-message {
type custom-redirect-url;
url url;
}
category name {
action (block | log-and-permit | permit | quarantine);
... | [edit logical-systems logical-systems-name security utm feature-profile]
[edit tenants tenant-name security utm feature-profile] | Configures the Content Security Web filtering feature for logical systems. The Web filtering allows you
to manage Internet usage by preventing access to inappropriate Web content. The potential policies
conflict check of the Web filtering feature is independent of the content filtering, antivirus, and
antispam features... | [
{
"name": "juniper-enhanced",
"desc": "Enables Enhanced Web Filtering (EWF) on the device."
},
{
"name": "base-filter",
"desc": "A base filter is an object that contains a category-action pair for all categories defined in the category file."
},
{
"name": "block-message",
"desc": "Ju... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1.
Support for configuration in tenant systems introduced in Junos OS Release 19.2R1. | [
"Unified Threat Management Overview"
] |
web-filtering (Security Content Security Policy) | web-filtering {
http-profile http-profile;
} | [edit security utm default-configuration]
[edit security utm utm-policy policy-name]
[edit logical-systems logical-systems-name security utm utm-policy policy-name]
[edit tenants tenant-name security utm utm-policy policy-name] | Configures a Content Security policy for the Web filtering protocols and attach this policy to a security
profile to implement it. Web filtering allows you to manage Internet usage by preventing access to
inappropriate Web content. | [] | 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.
Support in default configuration introduced in Junos OS Release 18.2R1.
Support for configuration in logical systems introduced in Junos OS Release 18.3R1.
Support for configuration in tenant systems introduced in Junos OS Release 19.2R1. | [
"Web Filtering Overview"
] |
web-filtering | web-filtering {
http-persist;
http-reassemble;
juniper-enhanced {
base-filter;
block-message {
type custom-redirect-url;
url;
}
cache {
size kilobytes;
timeout minutes;
}
category name {
action (block... | [edit security utm feature-profile]
[edit security utm default-configuration] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "http-persist",
"desc": "Check all HTTP request in a connection. If http-persist option is enabled for clear text HTTP traffic, then Web filtering checks every HTTP request packet in the same session."
},
{
"name": "http-reassemble",
"desc": "Reassemble HTTP request segments. If http-r... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The surf-control-integrated feature is not supported from Junos OS Release 15.1X49-D10 onwards. For
previous releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level introduced in Junos OS Release 18.2R1.
The performance-mode statement introduced in Junos OS ... | [
"Understanding Local Web Filtering",
"Monitoring Web Filtering Configurations"
] |
web-management (System Processes) | web-management {
disable;
failover (alternate-media | other-routing-engine);
} | [edit system processes] | Specify the Web management process. | [
{
"name": "disable",
"desc": "Disable the Web management process."
},
{
"name": "failover",
"desc": "Configure the device to reboot if the software process fails four times within 30 seconds,"
},
{
"name": "alternate-media",
"desc": "Configure the device to switch to backup media tha... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
web-management (System Services) | web-management {
control max-threads max-threads;
http {
interface [interface-names] ;
port port;
}
https {
interface [interface-names];
( local-certificate name | pki-local-certificate name | system-generated-certificate );
port port;
virtual-domain virtu... | [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 resto... | [
{
"name": "control max-threads max-",
"desc": ""
},
{
"name": "threads",
"desc": "Configure the maximum number of simultaneous threads to handle access requests. Range: 0 through 16"
},
{
"name": "https",
"desc": "Configure the secure version of the HTTP service, HTTPS, which is enc... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for https introduced for SRX5400, SRX5600, and SRX5800 devices starting from Junos OS
Release 12.1X44-D10 and on vSRX Virtual Firewall, SRX300, SRX320, SRX340, SRX345, SRX380,
SRX550M, and SRX1500 devices starting from Junos OS Release 15.1X49-D40.
virtual-domai... | [
"Secure Management Access Configuration Summary",
"Firewall User Authentication Overview",
"Dynamic VPN Overview"
] |
web-proxy | web-proxy {
explicit-proxy {
profile name {
add-forwarded-header {
add-client-ipaddr-in-forwarded-for-info;
add-forwarded-proto-info;
add-proxy-ipaddr-in-forwarded-by-info;
obfuscated-forwarded-by-info obfuscated-forwarded-by-info;
... | [edit services] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | 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. | [] |
web-redirect | web-redirect; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
firewall-authentication pass-through]
[edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
firewall-authentication user-firewall] | Optionally, redirect HTTP requests to the device’s internal webserver by sending a redirect HTTP
response to the client system to reconnect to the webserver for user authentication. The interface on
which the client’s request arrived is the interface to which the request is redirected. | [] | 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.
Starting with Junos OS Release 15.1X49-D70 and Junos OS Release 17.3R1, support for user-firewall
added on SRX300, SRX320, SRX340, SRX345, SRX380, SRX1500, SRX4100, SRX4200, SRX5400,
SRX5600, and SRX5800 devices and vSRX Virtual Firewall Services Gateways. | [
"Understanding User Role Firewalls"
] |
web-redirect-to-https | web-redirect-to-https; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
firewall-authentication pass-through]
[edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
firewall-authentication user-firewall] | Redirect unauthenticated HTTP requests to the internal HTTPS webserver of the device. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced on SRX5600 and SRX5800 Services Gateways starting from Junos OS Release
12.1X44-D10, and on vSRX Virtual Firewall, SRX300, SRX320, SRX340, SRX345, SRX380, and SRX1500
Services Gateways starting from Junos OS Release 15.1X49-D40.
Starting with Junos OS Release 15.1X49-D70 and Junos OS Release 17.3R1... | [
"Unified Threat Management User Guide",
"SRX Firewall Users"
] |
web-server (Services) | web-server {
server-name;
address address;
connect-method (http | https);
port port;
} | [edit services user-identification authentication-source (Services User Identification ClearPass)
aruba-clearpass user-query (Services User Identification)] | Specify the name of the webserver configuration on the SRX Series Firewall used for the user query
integrated ClearPass authentication and enforcement function. The webserver is the ClearPass server to
which the SRX Series Firewall connects to request authentication and identity information for an
individual user.
When... | [
{
"name": "server-name",
"desc": "Specify the Web server name."
},
{
"name": "address",
"desc": "Specify the IP address or hostname of web server."
},
{
"name": "http",
"desc": "Configure HTTP as the connection protocol to use for the SRX Series integrated ClearPass authentication an... | 1. services—To view this statement in the configuration.
2. services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
webapi (System Services) | webapi {
client (System Services) name;
debug-level (System Services) (alert | crit | emerg | error | info | notice | warn);
debug-log (System Services) file;
http (System Services) {
port port;
}
https (System Services) {
certificate certificate;
certificate-key certific... | [edit system services] | Configure Web API (webapi) to facilitate efficient transmission of user authentication and identity
information from the CPPM to the SRX Series Firewall. The CPPM, which is the client in this
relationship, initiates a session with the SRX Series Firewall Web API process, which is the server in this
relationship. Howeve... | [
{
"name": "client",
"desc": "Address of permitted HTTP/HTTPS request originator."
},
{
"name": "debug-level",
"desc": "Debug level for webapi process. Values:"
},
{
"name": "alert",
"desc": "Match alert messages"
},
{
"name": "crit",
"desc": "Match critical messages"
}... | 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-D30. | [] |
webapi-clear-text (Security) | web-api-cleartext | [edit security zones security-zone zone host-inbound-traffic system-services] | Enable the Web API (webapi) service over HTTP host inbound traffic on TCP port 8080 for unencrypted
data. | [] | 1. security—To view this statement in the configuration.
2. security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
webapi-ssl (Security) | webapi-ssl | [edit security zones security-zone zone host-inbound-traffic system-services] | Enable the Web API service over HTTPS host inbound traffic on TCP port 8443. | [] | 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-D30. | [] |
websense-redirect | websense-redirect {
profile profile-name {
account value;
custom-block-message value;
fallback-settings {
default (block | log-and-permit);
server-connectivity (block | log-and-permit);
timeout (block | log-and-permit);
too-many-requests (block... | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering] | Configure the Websense redirect engine features.
Starting with Junos OS Release 17.4R1, you can download and dynamically load new Enhanced Web
Filtering (EWF) categories. The downloading and dynamic loading of the new EWF categories do not
require a software upgrade. Websense occasionally releases new EWF categories. E... | [
{
"name": "no-safe-search",
"desc": "Disable the safe search function."
}
] | 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.
no-safe-search option added in Junos OS Release 20.2R1. | [
"Example: Enhancing Security by Configuring Redirect Web Filtering Using Custom Objects"
] |
weight (Security) | weight (equal | firewall | idp); | [edit security forwarding-process application-services maximize-idp-sessions] | If you are deploying IDP policies, you can tune the device to increase IDP session capacity. By using the
provided commands to change the way the system allocates resources, you can achieve a higher IDP
session capacity.
Devices ship with an implicit default session capacity setting. This default value gives more weigh... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Understanding Traffic Processing on Security Devices"
] |
weight (Targeted Subscribers) | weight ($junos-interface-set-target-weight | weight-value); | [edit interfaces interface-set interface-set-name targeted-options] | Configure weight for targeted subscribers like PPPoe, demux, and conventional VLANs. The weight
assigned is based on factors such as customer preference, CoS, or bandwidth requirement. The member
links are then assigned based on the value of the weight. The value of the weight can range from 1
through 1000. | [
{
"name": "weight",
"desc": ""
},
{
"name": "($junos-interface-",
"desc": ""
},
{
"name": "set-target-weight |",
"desc": ""
},
{
"name": "weight-value)",
"desc": "Specify the weight for targeted subscribers. Member links for logical interfaces of aggregated Ethernet logic... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3.
$junos-interface-set target-weight option added in Junos OS Release 18.4R1. | [
"Understanding Support for Targeted Distribution of Logical Interface Sets of Static VLANs over",
"Aggregated Ethernet Logical Interfaces",
"Using RADIUS-Sourced Weights for Interface and Interface Set Targeted Distribution",
"RADIUS-Sourced Weights for Interface and Interface Set Targeted Distribution"
] |
weight | weight number; | [edit chassis cluster redundancy-group group-number interface-
monitor interface ]
[edit chassis cluster redundancy-group group-number ip-monitoring IP–
address] | Specify the relative importance of the object to the operation of the redundancy group. This statement
is primarily used with interface monitoring and IP address monitoring objects. The failure of an object—
such as an interface—with a greater weight brings the group closer to failover. Every monitored object is
assign... | [
{
"name": "number",
"desc": "Weight assigned to the interface or monitored IP address. A higher weight value indicates a"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement modified in Junos OS Release 10.1. | [] |
weighted-load-balancing (L2TP LAC) | weighted-load-balancing; | [edit services l2tp] | Specify that the router considers tunnel weight when selecting from among multiple tunnels that share
the same preference level. A higher maximum session limit on a tunnel corresponds to a higher tunnel
weight. A tunnel with a higher weight is more likely to be selected than a tunnel with a lower weight.
The distributi... | [] | 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. | [
"L2TP LAC Tunneling for Subscribers",
"L2TP LAC Tunneling for Subscribers"
] |
west-interface | west-interface {
node-id mac-address;
control-channel channel-name {
vlan number;
interface name interface-name
}
interface-none
ring-protection-link-end;
virtual-control-channel {
west-interface name;
east-interface name;
}
} | [edit protocols protection-group ethernet-ring ring-name] | Define one of the two interface ports for Ethernet ring protection, the other being defined by the east-
interface statement at the same hierarchy level. The interface must use the control channel's logical
interface name. The control channel is a dedicated VLAN channel for the ring port.
NOTE: Always configure this po... | [] | 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. | [
"Ethernet Ring Protection Switching Overview",
"Ethernet Ring Protection Using Ring Instances for Load Balancing",
"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"... |
when | when
<chassis chassis-id | member member of vc | model model | node node | peer peer | routing-engine
routing-engine | time time> | Display inherited data for a specified parameter that is defined as conditions under the configuration
"groups" on page 8279. | [
{
"name": "chassis chassis-id",
"desc": "Specify the chassis type of the device."
},
{
"name": "member member of vc",
"desc": "Specify the name of the member of the virtual chassis."
},
{
"name": "model model",
"desc": "Specify the model name of the device."
},
{
"name": "nod... | view
Sample Output
show | display inheritance when
user@host# show | display inheritance when
## Last changed: 2023-01-05 03:44:28 PST
version 22.4I-20220921.0.1158;
login {
##
## 'wheel' was inherited from group 'global'
##
class wheel {
##
## 'snmp' was inhe... | when option introduced in Junos OS Release 11.3.
peers option added in Junos OS Release 14.2R6 for the MX Series.
peers option added in Junos OS Release 16.1R1 for the EX Series. | [
"Example: Configure Conditions for Applying Configuration Groups"
] | |
white-list (Security Screen) | white-list name {
address [address...];
} | [edit logical-systems logical-system-name security screen],
[edit security screen],
[edit tenants tenant-name security screen]
[edit logical-systems logical-system-name security screen ids-option screen-name udp flood],
[edit security screen ids-option screen-name udp flood],
[edit tenants tenant-name security screen i... | Configure a list of IP addresses that are exempted from UDP flood detection, which occur during the
UDP flood screen protection process. This list of exempted addresses is called an allowlist.
You can use this statement to configure an allowlist of IP addresses that bypass UDP flood detection.
NOTE: This statement is n... | [
{
"name": "name White-list name",
"desc": "The name of the allowlist."
},
{
"name": "address address",
"desc": "The list of IP addresses. You can specify multiple addresses or address prefixes as a"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1.
Support for UDP flood screen allowlist introduced in Junos OS Release 17.4.
tenant option added in Junos OS Release 18.3R1.
Support for UDP and TCP flood screen allowlists added in Junos OS Release 20.3R1 for Next Gen
Services on MX240, MX480 and MX960 routers. | [
"Understanding Allowlists for SYN Flood Screens",
"Understanding Allowlist for UDP Flood Screens"
] |
white-list (Security-Zone) | white-list [ white-list ... ]; | [edit logical-systems name security zones security-zone],
[edit logical-systems name tenants name security zones security-zone],
[edit security zones security-zone],
[edit tenants name security zones security-zone] | Configure allowlist for all IP screen options in a security zone.
You can use this statement to configure allowlist for all IP screen options at zone level to bypass IP
packet screening check. Both IPv4 and IPv6 allowlists are supported. Addresses in an allowlist must be
all IPv4 or all IPv6. In each allowlist, there c... | [
{
"name": "White-list name",
"desc": "The name of the allowlist."
}
] | 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. | [] |
white-list | white-list {
IP-address-list IP-address-list-name;
file-name file-name;
} | [edit services web-filter profile profile-name security-intelligence-policy] | Configure a global allowlist of IP addresses to allow packets to the destined countries. | [
{
"name": "IP-address-list ip-address-list-name",
"desc": "Contains the list of IP addresses that must be allowed. ip-address-list-name is the name of the IP address-list specified at the [edit services web-filter]"
},
{
"name": "file-name file-name",
"desc": "Name of the file which contains the... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.4R1 on MX Series routers with Juniper Advanced Threat
Prevention Cloud (Juniper ATP Cloud) . | [
"Global Allowlist and Global Blocklist"
] |
whitelist | whitelist [global-address-book-addresses]; | [edit services ssl proxy profile profile-name]
[edit services ssl termination profile profile-name] | Specify the addresses exempted from the SSL proxy. This statement is supported on the SRX1500,
SRX4100, SRX4200, SRX5400, SRX5600, and SRX5800 devices and vSRX Virtual Firewall.
You can selectively bypass SSL proxy processing for some sessions by configuring a allowlist. Typically,
you might configure the allowlist to ... | [
{
"name": "allowlist-address",
"desc": "Specify address from the global address book."
}
] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. | [
"Configuring SSL Forward Proxy",
"Firewall User Authentication Overview"
] |
whitelist-url-categories | whitelist-url-categories url-category-list; | [edit services ssl proxy profile profile-name] | Configure the predefined URL categories in SSL proxy profile to exempt from SSL inspection. The URL
category identification is leveraged from the Web filtering categories obtained from the Content
Security module.
Before you specify URL category list, you must create a web filtering profile with custom objects using
cu... | [
{
"name": "url-category-",
"desc": ""
},
{
"name": "list",
"desc": "List of predefined or custom URL category. The limits for URL categories in SSL forward proxy and SSL reverse proxy configurations is 800. NOTE: In the reverse proxy configuration, ensure combined size of server certificates and... | 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-D80. | [
"Creating an Allowlist of Exempted URL Categories for SSL Proxy"
] |
wildcard delete | wildcard delete <statement-path> <identifier> <regular-expression> | Delete a statement or identifier. All subordinate statements and identifiers contained within the
specified statement path are deleted with it.
Deleting a statement or an identifier effectively “unconfigures” or disables the functionality associated
with that statement or identifier.
If you do not specify statement-pat... | [
{
"name": "identifier",
"desc": "(Optional) Name of the statement or identifier to delete."
},
{
"name": "regular-expression",
"desc": "(Optional) The pattern based on which you want to delete multiple items. When you use the wildcard command to delete related configuration items, the regular-ex... | configure—To enter configuration mode. Other required privilege levels depend on where the statement
is located in the configuration hierarchy. | Command introduced before Junos OS Release 7.4. | [
"Example: Using Global Replace in a Device Configuration—Using the upto Option",
"Example: Use the Wildcard Command with the Range Option"
] | |
wildcard-group-inet6 | wildcard-group-inet6 {
wildcard-source {
inter-region-segmented{
fan-out fan-out value;
}
ldp-p2mp;
pim-ssm {
group-range multicast-prefix;
}
rsvp-te {
label-switched-path-template {
(default-template | lsp-template-... | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel selective],
[edit routing-instances routing-instance-name provider-tunnel selective] | Configure a wildcard group matching any group IPv6 address.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
The inter-region-segmented statement added in Junos OS Release 15.1. | [
"Example: Configuring Selective Provider Tunnels Using Wildcards",
"Understanding Wildcards to Configure Selective Point-to-Multipoint LSPs for an MBGP MVPN",
"Configuring a Selective Provider Tunnel Using Wildcards"
] |
wildcard-group-inet | wildcard-group-inet {
wildcard-source {
inter-region-segmented{
fan-out fan-out value;
}
ldp-p2mp;
pim-ssm {
group-range multicast-prefix;
}
rsvp-te {
label-switched-path-template {
(default-template | lsp-template-n... | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel selective],
[edit routing-instances routing-instance-name provider-tunnel selective] | Configure a wildcard group matching any group IPv4 address.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
The inter-region-segmented statement added in Junos OS Release 15.1. | [
"Example: Configuring Selective Provider Tunnels Using Wildcards",
"Understanding Wildcards to Configure Selective Point-to-Multipoint LSPs for an MBGP MVPN",
"Configuring a Selective Provider Tunnel Using Wildcards"
] |
wildcard-source (PIM RPF Selection) | wildcard-source {
next-hop next-hop-address;
} | [edit routing-instances routing-instance-name protocols pim rpf-selection group group-address],
[edit routing-instances routing-instance-name protocols pim rpf-selection prefix-list prefix-
list-addresses] | Use a wildcard for the multicast source instead of (or in addition to) a specific multicast source.
The remaining statements are explained separately. See CLI Explorer. | [] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Example: Configuring PIM RPF Selection"
] |
wildcard-source (Selective Provider Tunnels) | wildcard-source {
inter-region-segmented {
fan-out fan-out value;
}
ldp-p2mp;
pim-ssm {
group-range multicast-prefix;
}
rsvp-te {
label-switched-path-template {
(default-template | lsp-template-name);
}
static-lsp lsp-name;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel selective group group-prefix],
[edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel selective wildcard-group-inet],
[edit logical-systems logical-system-name routing-instances... | Configure a selective provider tunnel for a shared tree using a wildcard source.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
The inter-region-segmented statement added in Junos OS Release 15.1. | [
"Example: Configuring Selective Provider Tunnels Using Wildcards",
"Understanding Wildcards to Configure Selective Point-to-Multipoint LSPs for an MBGP MVPN",
"Configuring a Selective Provider Tunnel Using Wildcards"
] |
window-scale | window-scale {
match (equal | greater-than | less-than | not-equal);
value window-scale-factor;
} | [edit security idp custom-attack attack-name attack-type signature protocol tcp] | Specify the scale factor that the session of the attack will use. The window scale extension expands the
definition of the TCP window to 32 bits and then uses a scale factor to carry this 32-bit value in the 16-
bit window field of the TCP header. | [
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value window-scale-factor",
"desc": "Match the number of bytes."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
window-size | window-size {
match (equal | greater-than | less-than | not-equal);
value window-size;
} | [edit security idp custom-attack attack-name attack-type signature protocol tcp] | Specify the number of bytes in the TCP window size. | [
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value window-size",
"desc": "Match the number of bytes."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.