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 |
|---|---|---|---|---|---|---|---|
version-ipfix (Forwarding Options) | version-ipfix {
template template-name;
} | [edit forwarding-options sampling instance instance-name family (inet | inet6 | mpls | vpls)
output flow-server hostname] | Specify flow monitoring version IPFIX properties to apply to output sampling records.
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 10.2. | [
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250",
"Configuring Inline J-Flow to Use IPFIX Flow Templates on MX, vMX and T Series Routers, EX Series",
"Switches, NFX Series Devices, and SRX Devices"
] |
versioning | versioning; | [edit system dynamic-profile-options] | Enable version support for dynamic profiles on the system. This means that you can create new versions
of dynamic profiles that are currently in use by subscribers. Each new version of the profile is stored as a
new profile. The profile name is in the format base-profile-name$$number, where number varies sequentially
f... | [] | 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. | [
"Versioning for Dynamic Profiles"
] |
video (Application Profile) | video {
dscp (alias | bits);
forwarding-class class-name;
} | [edit services cos application-profileprofile-name sip] | Set the appropriate dscp and forwarding-class values for SIP video traffic.
Default
By default, the system will not alter the DSCP or forwarding class for SIP video traffic. | [] | 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. | [] |
video | video {
dscp (Services CoS) (alias | bits);
forwarding-class (Services PIC Classifiers) class-name;
} | [edit services cos application-profile profile-name sip] | Set the appropriate dscp and forwarding-class values for SIP video traffic.
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 9.3. | [
"Configuring Application Profiles for Use as CoS Rule Actions"
] |
video-monitoring | video-monitoring {
interfaces {
interface-name {
family {
inet {
input-flows {
input-flow-name {
destination-address [ address ];
destination-port [ port ];
... | [edit services] | Define the options for video monitoring using media delivery index options for metrics.
The remaining statements are explained separately. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Configuring Inline Video Monitoring on MX Series Routers"
] |
view (Configuring a MIB View) | view view-name {
oid object-identifier <include | exclude>;
} | [edit snmp] | Define a MIB view. A MIB view identifies a group of MIB objects. Each MIB object in a view has a
common OID prefix. Each object identifier represents a subtree of the MIB object hierarchy. The view
statement uses a view to specify a group of MIB objects on which to define access. To enable a view,
you must associate th... | [
{
"name": "view-name",
"desc": "Name of the view."
}
] | 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. | [] |
view (SNMP Community) | view view-name; | [edit snmp community community-name] | Associate a view with a community. A view represents a group of MIB objects. | [
{
"name": "view-name",
"desc": "Name of the view. You must use a view name already configured in the view statement at"
}
] | 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. | [] |
violation-action (DHCP Local Server and DHCP Relay Agent) | violation-action action; | [edit forwarding-options dhcp-relay lease-time-validation],
[edit forwarding-options dhcp-relay dhcpv6 lease-time-validation],
[edit forwarding-options dhcp-relay group group-name lease-time-validation],
[edit forwarding-options dhcp-relay dhcpv6 group group-name lease-time-validation],
[edit logical-systems logical-sy... | Configure the action that the router performs when a DHCP lease-time violation occurs. The violation
occurs when a third-party DHCP server or address-assignment pool offers a DHCP lease time that is
less than the threshold specified by the lease-time-threshold statement. | [
{
"name": "action",
"desc": "Action taken by the router when a lease-time violation occurs."
},
{
"name": "drop",
"desc": "(Optional) For DHCPv4 and DHCPv6 relay agent, the third-party lease is dropped and"
},
{
"name": "override-lease",
"desc": "(Optional) For DHCPv4 and DHCPv6 loca... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"DHCP Lease Times for IP Addresses"
] |
violation-report-rate (DDoS Flow Detection) | violation-report-rate report-rate; | [edit system ddos-protection global] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches) Limit
the rate at which bandwidth violations (violation reports) are reported from an FPC to the Routing
Engine, for all protocol groups and packet types on all line cards. | [
{
"name": "report-rate",
"desc": "Number of violations per second. Range: 1 through 50,000 Default: 100"
}
] | 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.
Support for Enhanced Subscriber Management added in Junos OS Release 17.3R1. | [
"Configuring the Violation Reporting Rate for All Protocol Groups and Packet Types",
"Setting Up and Using Flow Detection"
] |
virtual-address | virtual-address [ addresses ]; | [edit interfaces interface-name unit logical-unit-number family inet address address vrrp-
group group-id],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet address address vrrp-group group-id] | Configure the addresses of the devices in a Virtual Router Redundancy Protocol (VRRP) IPv4 or IPv6
group. You can configure up to eight addresses. | [
{
"name": "addresses",
"desc": "Addresses of one or more devices. Do not include a prefix length. If the address is the same as the interface’s physical address, the interface becomes the primary device for the 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. | [
"Configuring Basic VRRP Support",
"Understanding VRRP on SRX Series Devices",
"Example: Configuring VRRP/VRRPv3 on Chassis Cluster Redundant Ethernet Interfaces"
] |
virtual-channel-group (CoS Interfaces) | virtual-channel-group group-name; | [edit class-of-service interfaces interface-name unit logical-unit-number] | Assign a virtual channel group to a logical interface.
If you apply a virtual channel group to multiple logical interfaces, separate queues are created on each of
the interfaces. The same virtual channel names are used on all the interfaces. You can specify the
scheduler and shaping rates in the virtual channels in per... | [
{
"name": "group-name",
"desc": "Name of the virtual channel group."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [] |
virtual-channel-groups | virtual-channel-groups {
virtual-channel-group-name {
virtual-channel-name {
scheduler-map map-name;
shaping-rate (percent percentage | rate);
default;
}
}
} | [edit class-of-service] | Associate a virtual channel with a scheduler map and a shaping rate. Virtual channels and virtual channel
groups enable you to direct traffic into a virtual channel and apply bandwidth limits to the channel. | [
{
"name": "group-name",
"desc": "Name of the virtual channel group."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [] |
virtual-channels | virtual-channels {
virtual-channel-name;
} | [edit class-of-service] | Specify a list of virtual channels.
Each virtual channel has eight transmission queues. | [
{
"name": "virtual-channel-name",
"desc": "Name of the virtual channel."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [] |
virtual-chassis (MX Series Virtual Chassis) | virtual-chassis {
aliases {
serial-number serial-number;
}
graceful-restart {
disable;
}
heartbeat-address (ip-address | ipv6-address);
heartbeat-timeout seconds;
heartbeat-tos seconds;
heartbeat-tos value;
locality-bias;
member member-id {
role (... | [edit] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Example: Configuring Interchassis Redundancy for MX Series 5G Universal Routing Platforms Using a",
"Virtual Chassis",
"Example: Determining Member Health Using an MX Series Virtual Chassis Heartbeat Connection",
"with Member Routers in the Same Subnet",
"Example: Determining Member Health Using an MX Seri... |
virtual-chassis | virtual-chassis {
aliases {
serial-number serial-number {
alias-name alias-name;
}
}
auto-conversion;
auto-provisioned;
auto-sw-update {
(ex-4200 | ex-4300 | ex-4500 | ex-4600 | qfx-3 | qfx-5)
package-name package-name;
}
fast-failover (ge | vcp di... | [edit] | 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... | [] | 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 for EX Series switches.
Statement introduced in Junos OS Release 13.2X50-D15. | [
"Autoprovisioning a Virtual Chassis Fabric",
"Preprovisioning a Virtual Chassis Fabric",
"Adding a Device to a Virtual Chassis Fabric",
"Configuring an EX4650 or a QFX Series Virtual Chassis",
"Configuring an EX2300, EX3400, or EX4300 Virtual Chassis",
"Configuring EX4600 Switches in a Mixed or Non-Mixed ... |
virtual-circuit-id | virtual-circuit-id identifier; | [edit logical-systems logical-system-name protocols l2circuit local-switching interface
interface-name backup-neighbor address],
[edit logical-systems logical-system-name protocols l2circuit neighbor address
interface interface-name],
[edit logical-systems logical-system-name protocols l2circuit neighbor address inte... | Uniquely identify a Layer 2 circuit for either a standard pseudowire or a redundant pseudowire. | [
{
"name": "identifier",
"desc": "1 through 4,294,967,295"
}
] | 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.
Hierarchy levels for backup-neighbor (pseudowire redundancy) added in Junos OS Release 9.2. | [
"Configuring the Virtual Circuit ID",
"Configuring Pseudowire Redundancy on the PE Router",
"Example: Configuring Layer 2 Circuit Switching Protection"
] |
virtual-control-channel | virtual-control-channel channel-name {
west-interface name;
east-interface name;
} | [edit protocols protection-group ethernet-ring name (east-interface | west-interface)] | Specify virtual control channels which are logical interfaces on the east and west interfaces of the major
ring. | [
{
"name": "west-interface name",
"desc": "Logical interface on the major ring’s west port."
},
{
"name": "east-interface name",
"desc": "Logical interface on the major ring’s east port."
}
] | 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)"
] |
virtual-cpu | virtual-cpu {
virtual-cpu-number {
physical-cpu number | range;
}
count number;
features {
hardware-virtualization;
}
} | [edit virtual-network-functions] | Specify the number of virtual CPUs the VNF can use. By default, a VNF is assigned one virtual CPU,
which is independent of any specific physical CPU. | [
{
"name": "virtual-cpu count number",
"desc": "Number of virtual CPUs. For example, 2."
},
{
"name": "virtual-cpu features",
"desc": "Features of the virtual cpu. For example, hardware-virtualization."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D40. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
virtual-gateway-address | virtual-gateway-address address; | [edit interfaces interface-name unit logical-unit-number family family address address] | Set the default IPv4 or IPv6 address for the gateway for end hosts. You eliminate the need to proxy for
remote gateway IP addresses because you must configure the virtual gateway address using the same IP
address as on all of the provider edge (PE) devices. This configuration internally generates the same
Virtual Route... | [
{
"name": "address",
"desc": "virtual gateway address. You can't specify the addresses 0.0.0.0 (default route address) or"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"EVPN with IRB Solution Overview",
"Example: Configuring EVPN with IRB Solution",
"Configuring the Interface Address"
] |
virtual-gateway-v4-mac | virtual-gateway-v4-mac ipv4-mac-address | [edit dynamic-profiles name interfaces name unit logical-unit-number],
[edit dynamic-profiles name logical-systems name interfaces name unit logical-unit-number],
[edit interfaces name unit logical-unit-number] | Explicitly configure an IPv4 media access control (MAC) address for a default virtual gateway.
A Juniper Networks device creates a default virtual gateway when you specify a virtual gateway address
(VGA) for an integrated routing and bridging (IRB) interface on the device. You use this option on a
device that functions... | [
{
"name": "ipv4-mac-address",
"desc": "IPv4 MAC address for the default virtual gateway."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R5. | [] |
virtual-gateway-v6-mac | virtual-gateway-v6-mac ipv6-mac-address | [edit dynamic-profiles name interfaces name unit logical-unit-number],
[edit dynamic-profiles name logical-systems name interfaces name unit logical-unit-number],
[edit interfaces name unit logical-unit-number] | Explicitly configure an IPv6 media access control (MAC) address for a default virtual gateway.
A Juniper Networks device creates a default virtual gateway when you specify a virtual gateway address
(VGA) for an integrated routing and bridging (IRB) interface on the device. You use this option on a
device that functions... | [
{
"name": "ipv6-mac-address",
"desc": "IPv6 MAC address for the default virtual gateway."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R5. | [] |
virtual-inet6-address | virtual-inet6-address [ addresses ]; | [edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-
group group-id],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet6 address address vrrp-inet6-group group-id] | Configure the addresses of the virtual routers in a Virtual Router Redundancy Protocol (VRRP) IPv6
group. You can configure up to eight addresses. | [
{
"name": "addresses",
"desc": "Addresses of one or more virtual routers. Do not include a prefix length. If the address is the"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Basic VRRP Support"
] |
virtual-ip | virtual-ip name {
interface interface;
ip ip;
use-virtual-mac;
} | [edit chassis high-availability services-redundancy-group] | Specify IP address used for activeness determination and enforcement on the switching side of
Multinode High Availability deployments. Required for hybrid and default gateway deployments. | [
{
"name": "name",
"desc": "Virtual IP Identifier."
},
{
"name": "interface",
"desc": "Name of the interface for virtual IP."
},
{
"name": "ip",
"desc": "IPV4/IPV6 prefix, should be in the same subnet as the interface IP"
},
{
"name": "use-virtual-mac",
"desc": "Use virtua... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.3R1. | [
"Multinode High Availability",
"Example: Configure Multinode High Availability in a Default Gateway Deployment"
] |
virtual-link | virtual-link neighbor-id router-id transit-area area-id {
disable;
authentication key <key-id identifier>;
dead-interval seconds;
hello-interval seconds;
ipsec-sa name;
retransmit-interval seconds;
transit-delay seconds
keychain keychain-name;
} | [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf
area area-id],
[edit protocols (ospf | ospf3) area area-id],
[edit routing-instances routing-instance-name protocols ospf area area-id] | For backbone areas only, create a virtual link to use in place of an actual physical link. All area border
routers and other routing devices on the backbone must be contiguous. If this is not possible and there
is a break in OSPF connectivity, use virtual links to create connectivity to the OSPF backbone. When
configur... | [
{
"name": "neighbor-id router-id",
"desc": "IP address of the routing device at the remote end of the virtual link."
},
{
"name": "transit-area area-id",
"desc": "Area identifier of the area through which the virtual link transits. Virtual links are not allowed to transit the backbone area."
}... | 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 option keychain keychain-name introduced in Junos OS and Junos OS Evolved Release 24.2R1. | [
"Understanding OSPF Areas",
"Example: Configuring OSPF Virtual Links to Connect Noncontiguous Areas"
] |
virtual-link-local-address | virtual-link-local-address ipv6-address; | [edit interfaces interface-name unit logical-unit-number family inet6 address address vrrp-inet6-
group group-id],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet6 address address vrrp-inet6-group group-id] | Used to explicitly configure a virtual link-local address for a Virtual Router Redundancy Protocol (VRRP)
IPv6 group. The virtual link-local address must be configured to be on a fe80::/64 subnet for proper
operation. Early versions of the Junos OS required manual configuration of this parameter. In current
Junos relea... | [
{
"name": "ipv6-address",
"desc": "virtual link-local IPv6 address for VRRP for an IPv6 group."
}
] | 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 Basic VRRP Support",
"Junos OS Support for VRRPv3"
] |
virtual-mac | virtual-mac mac-address/mask; | [edit protocols l2-learning global-mac-move] | Configure MAC addresses that are not to be considered in the VPLS loop prevention algorithm.
NOTE: Starting in Junos OS Release 17.4R1, this statement has been replaced with the
exclusive-mac statement. | [
{
"name": "mac-address/mask",
"desc": ""
},
{
"name": "MAC address",
"desc": "Values: 00:00:5e:00:01:00/8, 00:00:0c:07:ac:00/8, and 02:bf:00:00:00:00/32"
}
] | 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. | [
"Example: Configuring Loop Prevention in VPLS Network Due to MAC Moves"
] |
virtual-network-functions (Junos node slicing) | virtual-network-functions vnf-name {
base-config base-config ;
chassis-type chassis-type;
id id;
resource-template resource-template;
} | [edit ] | Associate a GNF ID, base configuration, chassis type and resource template with the VNF.
The GNFs that are configured and committed will appear as auto-complete options in operational
commands. | [
{
"name": "vnf-name",
"desc": "Name of the VNF."
},
{
"name": "base-config base-config",
"desc": "Choose a base configuration for the VNF."
},
{
"name": "chassis-type",
"desc": ""
},
{
"name": "chassis-type",
"desc": "Applicable only to Junos node slicing set up using ext... | root | Statement introduced in Junos OS Release 17.2R1. | [] |
virtual-network-functions | virtual-network-functions vnf-name; | virtual-network-functions {
ipsec-nm {
interfaces {
heth1 | heth2 {
mapping {
vlan {
members vlan-name;
}
}
}
}
}
vjunos0 {
interfaces {
em1 {
... | Create an instance of a virtual network function (VNF) on platforms that run disaggregated Junos OS
software.
NOTE:
•
Creating a VNF instance fails if the resources required by the VNF are not available in
the system.
•
If you use init-descriptor to define a VNF by specifying and setting different values
for the virtu... | [
{
"name": "virtual-network-functions vnf-name",
"desc": "Name of the VNF instance. It is mandatory to provide one of the options: init-descriptor or image."
},
{
"name": "file-path",
"desc": "Path of the source file."
},
{
"name": "number | range",
"desc": "Number or a range of physi... | 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-D45. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
virtual-offload (CSDS) | virtual-offload {
interface name {
remote-ip ip-address;
source-identity profile-name;
}
source-identity-profile name {
family {
inet {
local-ip local-ip;
local-virtual... | [edit security forwarding-options services-offload] | Enable the firewall to process the control traffic on interfaces that carry real services. Use the statement
on the firewall for the Connected Security Distributed Services (CSDS) architecture Express Path
solution.
The interface on the router that connects to the firewall holds the load-balancing information required
... | [
{
"name": "virtual-offload",
"desc": "Specify the option to use the virtual service-offload feature on the firewall."
},
{
"name": "interface name",
"desc": "Specify the virtual service-offload interface to associate with the source identity profile."
},
{
"name": "remote-ip ip-address",... | 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. | [
"Express Path in CSDS Architecture"
] |
virtual-service (Traffic Load Balancer) | virtual-service virtual-service-name {
address virtual-ip–address;
group group-name;
load-balance-method {
hash {
hash-key method;
}
random;
}
mode ( layer2-direct-server-return | direct-server-return | translated );
<routing-instance routing-instance-name>;
... | [edit services traffic-load-balance instance instance-name] | Configure a TLB virtual service. | [
{
"name": "address virtual-ip-address",
"desc": "Address of the virtual service."
},
{
"name": "group group-name",
"desc": "Server group for the virtual service."
},
{
"name": "load-balance method",
"desc": ""
},
{
"name": "hash hash-key method",
"desc": "Use a combinatio... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1.
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. | [
"Traffic Load Balancer Overview",
"Configuring TLB"
] |
virtual-switch | virtual-switch name bridge-domain name vlan-id [vlan-ids ]; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name default-
x] | Specify the routing-instance type as a virtual switch, under which bridge-domain MIPs must be 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.6. | [
"Configuring Maintenance Intermediate Points (MIPs)"
] |
virus-detection (Security Antivirus) | virus-detection {
custom-message message;
custom-message-subject message-subject;
(notify-mail-sender | no-notify-mail-sender);
type (message | protocol-only);
} | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name
notification-options]
[edit security utm feature-profile anti-virus avira-engine profile profile-name notification-
options]
[edit security utm feature-profile anti-virus sophos-engine p... | 15.1X49-D10
The Express and Kaspersky Antivirus features are not supported from Junos OS Release 15.1X49-
D10 onwards. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
The Express and Kaspersky Antivirus features are 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 ... | [] |
vjunos0 | vjunos0 {
interfaces {
em1 {
mapping {
vlan {
members vlan-name;
}
}
}
}
} | [edit virtual-network-functions] | An option that enables or disables the vjunos virtual network function if the vjunos0 option is
configured in the system. | [
{
"name": "interfaces",
"desc": "Name of the interface. For example, em1."
},
{
"name": "vlan members vlan-name",
"desc": "Name of the VLAN members."
}
] | 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-D45. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
vlan (Access Port Security) | vlan (all | vlan-name) {
(arp-inspection | no-arp-inspection) {
forwarding-class class-name;
}
dhcp-option82 {
circuit-id {
prefix hostname;
use-interface-description;
use-vlan-id;
}
remote-id {
prefix hostname | mac | none;
... | [edit ethernet-switching-options secure-access-port] | Apply any of the following security options to a VLAN:
•
DHCP snooping
•
DHCPv6 snooping with DHCP option 37
•
DHCP option 82
•
Dynamic ARP inspection (DAI)
•
IPv6 neighbor discovery inspection
•
FIP snooping
•
IP source guard
•
IPv6 source guard
•
MAC move limiting
The remaining statements are explained separately. Se... | [
{
"name": "all",
"desc": "Apply the feature to all VLANs."
},
{
"name": "vlan-name",
"desc": "Apply the feature to the specified VLAN."
}
] | 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.
Support for the examine-dhcpv6, no-option37, neighbor-discovery-inspection, and ipv6-source-guard statements
introduced in Junos OS Release 14.1x53-D10 for EX Series switches. | [
"Example: Configuring Port Security (non-ELS)",
"Example: Configuring IP Source Guard with Other EX Series Switch Features to Mitigate Address-",
"Spoofing Attacks on Untrusted Access Interfaces",
"Example: Setting Up DHCP Option 82 Using the Same VLAN",
"Example: Configuring an FCoE Transit Switch"
] |
vlan (Bridge Domains) | vlan vlan-id {
all
immediate-leave;
interface interface-name {
group-limit limit;
host-only-interface;
multicast-router-interface;
static {
group multicast-group-address {
source ip-address;
}
}
}
proxy {
source... | [edit bridge-domains bridge-domain-name protocols igmp-snooping],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-
snooping] | Configure IGMP snooping parameters for a particular VLAN.
Default
By default, IGMP snooping options apply to all VLANs. | [
{
"name": "vlan-id",
"desc": "Apply the parameters to this VLAN."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring VLAN-Specific IGMP Snooping Parameters"
] |
vlan (DHCP Bindings on Access Ports) | vlan vlan-name; | [edit ethernet-switching-options secure-access-port interface (all | interface-name) static-ip ip-
address] | Associate the static IP address with the specified VLAN associated with the specified interface. | [
{
"name": "vlan-name",
"desc": "Name of a specific VLAN associated with the specified interface."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Configuring Static DHCP IP Addresses for DHCP snooping (non-ELS)"
] |
vlan (IGMP Snooping) | vlan vlan-name {
immediate-leave;
interface interface-name {
group-limit limit;
host-only-interface;
multicast-router-interface;
static {
group multicast-group-address {
source ip-address;
}
}
}
(l2-querier | igmp-querier (... | [edit protocols igmp-snooping] | Configure IGMP snooping parameters for a VLAN (or all VLANs if you use the all option, where
supported).
On legacy EX Series switches, which do not support the Enhanced Layer 2 Software (ELS) configuration
style, IGMP snooping is enabled by default on all VLANs, and this statement includes a disable option if
you want ... | [
{
"name": "all",
"desc": "All VLANs on the switch. This option is available only on EX Series switches that do not support"
},
{
"name": "disable",
"desc": "Disable IGMP snooping on all or specified VLANs. This option is available only on EX Series"
},
{
"name": "vlan-name",
"desc": ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5.
Statement updated with enhanced ? (CLI completion feature) functionality in Junos OS Release 9.5 for
EX Series switches. | [
"Configuring IGMP Snooping",
"Configuring IGMP Snooping on Switches",
"Example: Configuring IGMP Snooping on Switches",
"Example: Configuring IGMP Snooping on EX Series Switches",
"Configuring VLAN-Specific IGMP Snooping Parameters"
] |
vlan (Mirroring) | vlan (vlan-id | vlan-name); | [edit forwarding-options analyzer analyzer-name input ingress],
[edit forwarding-options analyzer analyzer-name input ingress routing-instance instance-name],
[edit forwarding-options analyzer analyzer-name output],
[edit forwarding-options analyzer analyzer-name output routing-instance instance-name] | Configure mirrored traffic to be sent to a VLAN for remote monitoring. | [
{
"name": "vlan-id",
"desc": "Numeric VLAN identifier."
},
{
"name": "vlan-name",
"desc": "Name of the VLAN."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10 (ELS). | [
"Example: Configuring Mirroring for Remote Monitoring of Employee Resource Use Through a Transit",
"Switch on EX9200 Switches",
"Example: Configuring Port Mirroring for Remote Monitoring of Employee Resource Use"
] |
vlan (MLD Snooping) | vlan (all | vlan-name) {
disable;
immediate-leave;
interface ( all | interface-name) {
group-limit limit;
host-only-interface;
immediate-leave;
multicast-router-interface;
static {
group ip-address {
source ip-address;
}
... | [edit protocols mld-snooping]
[edit routing-instances instance-name protocols mld-snooping] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "all",
"desc": "(All EX Series switches except EX9200) Configure MLD snooping parameters for all VLANs on the switch."
},
{
"name": "vlan-name",
"desc": "Configure MLD snooping parameters for the specified VLAN. TIP: When you configure MLD snooping parameters using the vlan all stateme... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1.
Support at the [edit routing-instances instance-name protocols mld-snooping] hierarchy introduced in Junos
OS Release 13.3 for EX Series switches.
Support for the qualified-vlan, query-interval, query-last-member-interval, query-response-interval, and
traceoptions statemen... | [
"Configuring MLD Snooping on an EX Series Switch VLAN (CLI Procedure)"
] |
vlan (MSTP) | vlan vlan-id;
EX Series
vlan (all | vlan-id | vlan-name) {
bridge-priority priority;
forward-delay seconds;
hello-time seconds;
interface interface-name {
bpdu-timeout-action {
block;
log;
}
cost cost;
disable;
edge;
mod... | [edit logical-systems logical-system-name protocols mstp msti msti-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name
protocols mstp msti msti-id]
[edit protocols mstp msti msti-id],
[edit protocols mstp msti msti-id]
[edit protocols vstp]
[edit routing-instances routing-instance-na... | Configure the VLANs for a Multiple Spanning Tree Instance (MSTI) or VSTP instance.
NOTE: When you configure VSTP with the set prototocol vstp vlan all command, vlan-id
1 is excluded to be compatible with Cisco PVST+. If you want vlan-id 1 to be included in
VSTP, you must set it separately with the set protocol vstp vla... | [
{
"name": "vlan-name",
"desc": "Name of the VLAN."
},
{
"name": "vlan-id",
"desc": "The VLAN identifier associated with the MSTI."
},
{
"name": "vlan-id-range",
"desc": "Range of VLAN identifiers associated with the MSTI in the form minimum-vlan-id-maximum-vlan-id. VLAN identifier ra... | 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.
Statement updated with enhanced ? (CLI completion feature) functionality in Junos OS Release 9.5 for
EX Series switches.
Support for logical systems added in Junos OS Release 9.6. | [
"Understanding MSTP",
"Understanding VSTP",
"Example: Configuring Network Regions for VLANs with MSTP on Switches"
] |
vlan (PIM Snooping) | vlan <vlan-id>{
no-dr-flood;
} | [edit routing-instances <instance-name> protocols pim-snooping],
[edit logical-systems <logical-system-name> routing-instances <instance-name> protocols pim-
snooping] | Configure PIM snooping parameters for a VLAN. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"PIM Overview",
"Configuring Basic PIM Settings"
] |
vlan (Port Mirroring) | vlan (vlan-id | vlan-name) {
No Link Title; | For platforms without ELS:
[edit ethernet-switching-options analyzer name input ingress],
[edit ethernet-switching-options analyzer name output]
For platforms with ELS:
[edit forwarding-options analyzer name input (egress | ingress)],
[edit forwarding-options analyzer name output],
[edit forwarding-options port-mirrori... | When used in an input statement, specifies that traffic entering or exiting a VLAN should be mirrored.
(You can include this statement in an ingress statement or egress statement within the input statement. It
is not supported in an egress statement on all switches) When used in an output statement, specifies that
mir... | [
{
"name": "vlan-id",
"desc": "Numeric VLAN identifer."
},
{
"name": "vlan-name",
"desc": "Name of the VLAN."
},
{
"name": "no-tag",
"desc": "Specifies that remote mirrored packets are not tagged with the tag of the output (analyzer)"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
Optionoutput vlan added in Junos OS Release 12.1 for the QFX Series.
Optionno-tag added in Junos OS Release 15.1X53-D10 for QFX10000 switches. | [
"Understanding Port Mirroring and Analyzers",
"Configuring Port Mirroring Local and Remote Analysis"
] |
vlan (Port Mirroring) | vlan (vlan-name | vlan-ID); | [edit forwarding-options port-mirroring family ethernet-switching output]
[edit forwarding-options port-mirroring instance instance-name family ethernet-switching output] | Specify the VLAN name or ID for sending copies of packets to an analyzer. This configuration enables
remote VLAN port mirroring on EX Series switches. | [
{
"name": "vlan-name",
"desc": "Name of remote mirroring VLAN."
},
{
"name": "vlan-ID",
"desc": "ID of the remote mirroring VLAN."
}
] | 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. | [
"Example: Configuring Layer 2 Port Mirroring to Remote VLAN",
"Layer 2 Port Mirroring to Remote Destination by Using Destination as VLAN"
] |
vlan (Secure Access Port) | vlan (all | vlan-name) {
examine-fip {
examine-vn2vn {
beacon-period milliseconds;
}
fc-map fc-map-value;
no-fip-snooping-scaling;
}
dhcp-option82
circuit-id {
prefix (Circuit ID for Option 82) hostname;
use-interface-description;
... | [edit ethernet-switching-options secure-access-port] | Apply DHCP snooping, dynamic ARP inspection (DAI), DHCP option 82, and MAC move limiting.
TIP: To display a list of all configured VLANs on the system, including VLANs that are
configured but not committed, type ? after vlan or vlans in your configuration mode
command line. Note that only one VLAN is displayed for a V... | [
{
"name": "all",
"desc": "Apply DHCP snooping, DAI, DHCP option 82, and MAC move limiting to all VLANs."
},
{
"name": "vlan-name",
"desc": "Apply DHCP snooping, DAI, DHCP option 82, and MAC move limiting to the specified"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Understanding How to Protect Access Ports from Common Attacks",
"Understanding MAC Limiting and MAC Move Limiting for Port Security",
"Understanding and Using Trusted DHCP Servers",
"Configuring MAC Limiting (QFX Switches)",
"Understanding and Using Trusted DHCP Servers"
] |
vlan (Static IP) | vlan vlan-name; | [edit ethernet-switching-options secure-access-port interface (all | interface-name) static-ip ip-
address] | Associate a static IP address with the specified VLAN. | [
{
"name": "vlan-name",
"desc": "Name of a VLAN associated with the specified interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Configuring Static DHCP IP Addresses for DHCP snooping (non-ELS)"
] |
vlan (Unknown Unicast Forwarding) | vlan (all | vlan-name) {
interface (Unknown Unicast Forwarding) interface-name;
} | [edit ethernet-switching-options unknown-unicast-forwarding] | Specify a VLAN from which unknown unicast packets will be forwarded or specify that the packets will
be forwarded from all VLANS. Unknown unicast packets are forwarded from a VLAN to a specific trunk
interface.
The interface statement is explained separately.
TIP: To display a list of all configured VLANs on the system... | [
{
"name": "all",
"desc": "All VLANs."
},
{
"name": "vlan-name",
"desc": "Name of a VLAN."
}
] | 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.
Statement updated with enhanced ? (CLI completion feature) functionality in Junos OS Release 9.5 for
EX Series switches. | [
"show vlans",
"Configuring Unknown Unicast Forwarding (CLI Procedure)"
] |
vlan (VSTP) | vlan vlan-id {
bridge-priority priority;
forward-delay seconds;
hello-time seconds;
max-age seconds;
interface interface-name {
cost cost;
edge;
mode (p2p | shared);
no-root-port;
priority interface-priority;
}
}
EX Series
vlan (al... | [edit logical-systems logical-system-name protocols vstp],
[edit protocols vstp] | Configure VSTP VLAN parameters.
TIP: To display a list of all configured VLANs on the system, including VLANs that are
configured but not committed, type ? after vlan or vlans in your configuration mode
command line. Note that only one VLAN is displayed for a VLAN range. | [
{
"name": "all",
"desc": "All VLANs."
},
{
"name": "vlan-id",
"desc": "Numeric VLAN identifier."
},
{
"name": "vlan-range",
"desc": "Name of the VLAN range."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Support for logical systems added in Junos OS Release 9.6. | [
"Understanding VSTP",
"Configuring VLAN Spanning Tree Protocol"
] |
vlan members (VLANs) | vlan members [vlan-id]; | [edit vlans vlan-name] | Specify multiple VLAN identifiers to create a VLAN for each VLAN identifier. | [
{
"name": "vlan-id",
"desc": "A list of valid VLAN identifiers. A VLAN is created for each VLAN identifier in the list."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.5. | [
"Example: Configuring VLANs on Security Devices"
] |
vlan | vlan (all | vlan-name) {
interface interface-name;
} | [edit ethernet-switching-options unknown-unicast-forwarding] | For both Gigabit Ethernet and aggregated Ethernet interfaces and 802.1Q Tagging, assign an 802.1Q
VLAN tag ID to a logical interface.
For Static MAC-based VLANs, specify the name of a VLAN to add to the Ethernet switching table.
For unknown unicast, specify a VLAN from which unknown unicast packets will be forwarded, o... | [
{
"name": "all",
"desc": "All VLANs."
},
{
"name": "vlan-name",
"desc": "Name of the VLAN to add to the Ethernet switching table."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
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 t... | Statement introduced in Junos OS Release 9.0. | [
"Bridging and VLANs",
"MAC Addresses",
"Bridging and VLANs",
"Configuring Routed VLAN Interfaces on Switches (CLI Procedure)",
"Integrated Routing and Bridging",
"Bridging and VLANs",
"Junos OS Network Interfaces Configuration Guide"
] |
vlan-group | vlan-group group group-name {
vlan (vlan-id |vlan-group |all) {
} | [edit protocols vstp] | Configure VLAN group for Spanning Tree Protocol (VSTP). VSTP is used to prevent loops in Layer 2
networks on a per-VLAN basis.
BEST PRACTICE: Configure RSTP when you configure VSTP. RSTP overhead is minimal
and this configuration ensures that a spanning-tree protocol is running on all VLANs on
your switch, even when y... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [] |
vlan-groups | vlan-groups vlan_group_name{
vlan-id-list vlan_id_ist
} | [edit vlans] | Configure VLAN group on EX series switches. The 802.1X VLAN group feature uses a single wireless
local area network (WLAN) that can support multiple VLANs. The client gets assigned to one of the
configured VLANs.
The VLAN group name is added within the Tunnel-Private-Group-ID (defined as RADIUS attribute type
81, RFC 2... | [
{
"name": "vlan-id-list",
"desc": "Specify the associated VLAN id."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [
"802.1X Authentication"
] |
vlan-id (Dynamic Profiles) | vlan-id (number | none); | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number] | For VLAN demux, Fast Ethernet, Gigabit Ethernet, and Aggregated Ethernet interfaces only, bind a
802.1Q VLAN tag ID to a logical interface. | [
{
"name": "number",
"desc": "A valid VLAN identifier. When used in the dynamic-profiles hierarchy, specify the $junos-vlan-id"
},
{
"name": "none",
"desc": "Enable the use of untagged pseudo-wire frames on dynamic interfaces."
}
] | 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.
VLAN demux interface support introduced in Junos OS Release 10.2. | [
"Configuring Dynamic Subscriber Interfaces Using VLAN Demux Interfaces in Dynamic Profiles"
] |
vlan-id (Dynamic VLANs) | vlan-id number; | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number input-vlan-
map],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number output-vlan-
map] | For dynamic VLAN interfaces, specify the line VLAN identifiers to be rewritten at the input or output
interface.
You cannot include the vlan-id statement with the swap statement, swap-push statement, push-push
statement, or push-swap statement at the [edit dynamic-profiles profile-name interfaces interface-name unit
lo... | [
{
"name": "number",
"desc": "A valid VLAN identifier. When used for input VLAN maps, you can specify the $junos-vlan-map-id predefined variable to dynamically obtain the VLAN identifier."
}
] | 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. | [
"Rewriting the VLAN Tag on Tagged Frames",
"Binding VLAN IDs to Logical Interfaces"
] |
vlan-id (Fast Ethernet) | vlan-id number; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | For Fast Ethernet and Gigabit Ethernet interfaces only, bind an 802.1Q VLAN tag ID to a logical
interface. | [
{
"name": "number",
"desc": "A valid VLAN identifier."
}
] | 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 Interfaces for VPLS Routing"
] |
vlan-id (Logical Port in Bridge Domain) | vlan-id number; | [edit interfaces interface-name unit logical-unit-number family bridge],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family bridge] | The VLAN ID configured on the logical port. Received packets with no VLAN tags are forwarded within
the bridge domain with the matching VLAN ID. | [
{
"name": "number",
"desc": "The VLAN ID."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Statement introduced in Junos OS Release 15.1. | [
"Configuring Access Mode on a Logical Interface",
"Tunnel Services Overview",
"Tunnel Interface Configuration on MX Series Routers Overview"
] |
vlan-id (routing instance) | vlan-id (vlan-id | all | none); | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name]
[edit routing-instances routing-instance-name instance-type] | Specify 802.1Q VLAN tag IDs to a routing instance. | [
{
"name": "vlan-id",
"desc": "A valid VLAN identifier."
},
{
"name": "all",
"desc": "Include all VLAN identifiers specified on the logical interfaces included in the routing instance."
},
{
"name": "none",
"desc": "Include no VLAN identifiers for the 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 13.2. | [
"Configuring EVPN Routing Instances",
"Configuring EVPN Routing Instances on EX9200 Switches"
] |
vlan-id (VLAN ID to Be Bound to a Logical Interface) | vlan-id number; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | For Fast Ethernet, Gigabit Ethernet, and Aggregated Ethernet interfaces only, bind a 802.1Q VLAN tag
ID to a logical interface. | [
{
"name": "number",
"desc": "A valid VLAN identifier."
}
] | 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. | [
"Enabling VLAN Tagging"
] |
vlan-id inner-all | vlan-id inner-all; | [edit routing-instances instance_name] | Enable qualified MAC learning on the second (inner) VLAN tag of an ingress 2-tagged packet, without
removing the first (outer) tag implicitly. For a single vlan-tagged packet, qualified MAC learning happens
on VLAN 4096. If the ingress packet has more than two tags, all tags beyond the second tag are treated
as part of... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Command introduced in Junos OS Release 17.4R1. | [
"Understanding Qualified MAC Learning"
] |
vlan-id | vlan-id (all | none | number); | For platforms without ELS:
[edit vlans vlan-name vlan-range]
For platforms without ELS and with ELS:
[edit vlans vlan-name]
For ELS platforms only:
[edit interfaces interface-name unit number],
[edit vlans vlan-name vlan-id-list],
[edit vlans vlan-name],
[edit logical-systems logical-system-name vlansvlan-name],
[edit... | For VLANs, specify a VLAN identifier (VID) to include in the packets sent to and from the VLAN, or a
VPLS routing instance.
NOTE: When configuring a VLAN identifier for provider backbone bridge (PBB) routing
instances, dual-tagged VIDs and the none option are not permitted.
For 10-Gigabit Ethernet and aggregated Ethern... | [
{
"name": "number",
"desc": "A valid VLAN identifier. If you configure multiple VLANs with a valid VLAN identifier, you must"
},
{
"name": "all",
"desc": "Specify that the VLAN spans all the VLAN identifiers configured on the member logical interfaces."
},
{
"name": "none",
"desc": "... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
interface—To view this statement in the configuration.
interface-control—To add this statement t... | Statement introduced before Junos OS Release 7.4.
Support for Layer 2 trunk ports added in Junos OS Release 9.2.
Support for SRX 5600, and SRX 5800 devices added in Junos OS Release 9.6.
Support for logical systems added in Junos OS Release 9.6. | [
"Example: Connecting Access Switches with ELS Support to a Distribution Switch with ELS Support",
"Example: Configuring a Private VLAN on a Single Switch with ELS Support",
"Creating a Private VLAN on a Single Switch with ELS Support (CLI Procedure)",
"Creating a Private VLAN Spanning Multiple EX Series Switc... |
vlan-id-list (Ethernet VLAN Circuit) | vlan-id-list [vlan-id vlan-id–vlan-id]; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Binds a single-tag logical interface to a list of VLAN IDs. Configures a logical interface to receive and
forward any tag frame whose VLAN ID tag matches the list of VLAN IDs you specify.
NOTE: When you create a circuit cross-connect (CCC) using VLAN-bundled single-tag
logical interfaces on Layer 2 VPN routing instance... | [
{
"name": "[vlan-id vlan-id–vlan-id]",
"desc": "A list of valid VLAN ID numbers. Specify the VLAN IDs individually by using a"
},
{
"name": "1. Inefficient",
"desc": ""
},
{
"name": "[edit interfaces interface-name]",
"desc": ""
},
{
"name": "vlan-tagging;",
"desc": ""
... | 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. | [
"Binding VLAN IDs to Logical Interfaces",
"Junos OS VPNs Library for Routing Devices"
] |
vlan-id-list (Interface in Bridge Domain) | vlan-id-list [ number number-number ]; | [edit interfaces interface-name unit logical-unit-number family bridge],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family bridge] | Configure a logical interface to forward packets and learn MAC addresses within each bridge domain
configured with a VLAN ID that matches a VLAN ID specified in the list. VLAN IDs can be entered
individually using a space to separate each ID, entered as an inclusive list separating the starting VLAN
ID and ending VLAN ... | [
{
"name": "number number",
"desc": "Individual VLAN IDs separated by a space."
},
{
"name": "number-number",
"desc": "Starting VLAN ID and ending VLAN ID in an inclusive range."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Statement introduced in Junos OS Release 15.1. | [
"Configuring a Logical Interface for Trunk Mode",
"Configuring the VLAN ID List for a Trunk Interface",
"Tunnel Services Overview",
"Tunnel Interface Configuration on MX Series Routers Overview"
] |
vlan-id-list (Interface in VPLS) | vlan-id-list [ numbers number–number ]; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Configure a logical interface to forward packets and learn MAC addresses within each VPLS routing
instance configured with a VLAN ID that matches a VLAN ID specified in the list. VLAN IDs can be
entered individually using a space to separate each ID, entered as an inclusive list separating the starting
VLAN ID and endi... | [
{
"name": "number number",
"desc": "Individual VLAN IDs separated by a space."
},
{
"name": "number-number",
"desc": "Starting VLAN ID and ending VLAN ID in an inclusive range."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced for VPLS in Junos OS Release 10.2. | [
"Configuring Interfaces for VPLS Routing",
"Configuring Interfaces for VPLS Routing"
] |
vlan-id-list | vlan-id-list [ vlan-id-numbers ]; | [edit bridge-domains bridge-domain-name],
[edit logical-systems logical-system-name bridge-domains bridge-domain-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name bridge-domains
bridge-domain-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name],... | Specify a VLAN identifier list to use for a bridge domain or VLAN in trunk mode. VLAN identifier list can
be used on C-VLAN interfaces in Q–in–Q tunneling for EX and QFX Series switches.
Specify the trunk option in the interface-mode statement to accept packets with a VLAN ID that matches
the list of VLAN IDs specified... | [
{
"name": "vlan-id-numbers",
"desc": "Valid VLAN identifiers. You can combine individual numbers with range lists by including"
}
] | 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 a Bridge Domain",
"Configuring a VLAN",
"Configuring VLAN Identifiers for Bridge Domains and VPLS Routing Instances",
"Configuring VLAN Identifiers for VLANs and VPLS Routing Instances",
"Configuring Q-in-Q Tunneling and VLAN Q-in-Q Tunneling and VLAN Translation"
] |
vlan-id-range | vlan-id-range vlan-id–vlan-id | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Bind a range of VLAN IDs to a logical interface.
NOTE: The total number or count of configured VLAN IDs for vlan-id-range and vlan-id-
list must be less than or equal to 32 on the logical interface. | [
{
"name": "number",
"desc": "The first number is the lowest VLAN ID in the range the second number is the highest VLAN ID"
},
{
"name": "1. Inefficient",
"desc": ""
},
{
"name": "[edit interfaces interface-name]",
"desc": ""
},
{
"name": "vlan-tagging;",
"desc": ""
},
... | 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.
Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Statement introduced in Junos OS Release 25.2R1-EVO for ACX Series switches. | [
"Understanding VLANs"
] |
vlan-id-start | vlan-id-start S-VLAN-ID; | [edit vlans vlan-name interfaces interface-name mapping-range C-VLAN-range (push | swap)] | Configure an access interface to map a range of C-VLANs to a range of S-VLANs. Use this statement
instead of using multiple set vlans VLAN-name interface interface-name mapping (push | swap) statements to
configure Q-in-Q tunneling or VLAN translation on a per-VLAN basis. This statement sets the start of
the S-VLAN ran... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [] |
vlan-isolation | vlan-isolation; | [edit chassis network-slices] | Configure VLAN isolation. For the VLAN isolation configuration to take effect, you must configure the
set chassis network-slices vlan-isolation CLI configuration statement on all the Routing Engines of the
BSYS and GNFs, and then reboot the router.
On an MX without Junos Node Slicing enabled, all control traffic betwee... | [] | system | Statement introduced in Junos OS Release 21.2R1. | [
"Setting Up Junos Node Slicing"
] |
vlan-model | vlan-model one-to-one; | [edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | Define the network VLAN model. | [
{
"name": "one-to-one",
"desc": "Specify that any received, dual-tagged VLAN packet triggers the provisioning process in a"
}
] | 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 Separate Access Routing Instances for Layer 2 Wholesale Service Retailers",
"Configuring Separate NNI Routing Instances for Layer 2 Wholesale Service Retailers"
] |
vlan-prune | vlan-prune; | [edit vlans vlan-name] | Prune the Virtual Chassis port (VCP) paths in a Virtual Chassis to ensure received broadcast, multicast,
and unknown unicast traffic in a VLAN uses the shortest possible path through the Virtual Chassis to the
egress VLAN interface.
By default, all broadcast, multicast, and unknown unicast traffic in a VLAN on an EX Se... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring VLANs for EX Series Switches"
] |
vlan-range | vlan-range vlan-id-low-vlan-id-high; | [edit vlans vlan-name] | Configure multiple VLANs. Each VLAN is assigned a VLAN ID number from the range.
Default
None. | [
{
"name": "vlan-id-low-vlan-id-high",
"desc": "Specify the first and last VLAN ID number for the group of VLANs."
}
] | 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.2. | [
"Configuring VLANs on Switches",
"Configuring VLANs for EX Series Switches",
"Configuring VLANs for EX Series Switches (J-Web Procedure)",
"Configuring Routed VLAN Interfaces on Switches (CLI Procedure)",
"Understanding Bridging and VLANs on Switches",
"Configuring IRB Interfaces on Switches"
] |
vlan-ranges (RADIUS Options) | vlan-ranges (any | low-tag–high-tag); | [edit interfaces interface-name radius-options nas-port-options nas-port-options-name] | Configure the VLAN range of subscribers to which the named NAS-Port options definition applies.
NOTE: You can configure a maximum of 16 NAS-Port options definitions per physical
interface. Each definition can include a maximum of 32 VLAN ranges or 32 S-VLAN
ranges, but cannot include a combination of VLAN ranges and S-... | [
{
"name": "any",
"desc": "Entire VLAN range representing all VLAN IDs."
},
{
"name": "low-tag",
"desc": "VLAN ID tag representing the lower limit of the VLAN range. Range: 1 through 4094"
},
{
"name": "high-tag",
"desc": "VLAN ID tag representing the upper limit of the VLAN range. ... | 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. | [
"RADIUS NAS Port Attributes and Options",
"RADIUS NAS Port Attributes and Options"
] |
vlan-ranges | vlan-ranges {
access-profile profile-name;
authentication {
packet-types [packet-types];
password password-string;
username-include {
circuit-type;
circuit-id;
delimiter delimiter-character;
domain-name domain-name-string;
inte... | [edit interfaces interface-name auto-configure] | Configure multiple VLANs. Each VLAN is assigned a VLAN ID number from the range.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | routing—To view this statement in the configuration.
routing–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring an Interface to Use the Dynamic Profile Configured to Create Single-Tag VLANs",
"Configuring Interfaces to Support Both Single and Stacked VLANs"
] |
vlan-rewrite | vlan-rewrite {
translate from-vlan-id to-vlan-id;
} | [edit interfaces interface-name unit number family bridge ]
[edit interfaces interface-name unit number family ethernet-switching] | Translate a VLAN ID (the from-vlan-id) in an incoming packet to another VLAN ID (the to-vlan-id) that
you have configured on an interface. The device does the corresponding translation in reverse at egress.
You can configure VLAN translation with the vlan-rewrite translate statement as follows:
•
Only on trunk mode int... | [] | 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. | [
"Rewriting a VLAN Tag and Adding a New Tag",
"Overlapping VLAN Support Using VLAN Translation in EVPN-VXLAN Networks"
] |
vlan-rule (100-Gigabit Ethernet Type 4 PIC with CFP) | vlan-rule (high-low | odd-even); | [edit chassis fpc slot pic slot forwarding-mode vlan-steering] | Configure the interoperation mode of the 100-Gigabit Ethernet Type 4 PIC with CFP (PD-1CE-CFP-
FPC4) when interoperating with 100 gigabit Ethernet interfaces from other vendors.
If no VLAN rule is configured, all tagged packets are distributed to PFE0. | [
{
"name": "high-low",
"desc": "VLAN IDs 1 through 2047 are distributed to PFE0 and VLAN IDs 2048 through 4096 are distributed to PFE1."
},
{
"name": "odd-even",
"desc": "Odd number VLAN IDs are distributed to PFE1 and even number VLAN IDs are distributed to PFE0."
}
] | 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. | [
"Configuring VLAN Steering Mode for 100-Gigabit Ethernet Type 4 PIC with CFP"
] |
vlan-steering (100-Gigabit Ethernet Type 4 PIC with CFP) | vlan-steering {
vlan-rule (high-low | odd-even);
} | [edit chassis fpc slot pic slot forwarding-mode] | Configure the 100-Gigabit Ethernet Type 4 PIC with CFP (PD-1CE-CFP-FPC4) to interoperate with 100
gigabit Ethernet interfaces from other vendors.
The other statement is explained separately. | [] | 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. | [
"Configuring VLAN Steering Mode for 100-Gigabit Ethernet Type 4 PIC with CFP"
] |
vlan-tag (Dynamic Classifiers) | vlan-tag (inner | outer); | [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-
number classifiers ieee-802.1] | Apply this IEEE-802.1 classifier to the inner or outer VLAN tags in a dynamic profile.
Default
If you do not include this statement, the classifier applies to the outer VLAN tag only. | [
{
"name": "inner",
"desc": "Apply the classifier to the inner VLAN tag only."
},
{
"name": "outer",
"desc": "Apply the classifier to the outer VLAN tag only."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Applying a Classifier to a Subscriber Interface in a Dynamic Profile",
"classifiers (Definition)"
] |
vlan-tag (Dynamic Rewrite Rules) | vlan-tag (outer | outer-and-inner); | [edit dynamic-profiles profile-name class-of-service interfaces interface-name unit logical-unit-
number rewrite-rules ieee-802.1] | Apply this IEEE-802.1 rewrite rule to the outer or outer and inner VLAN tags in a dynamic profile.
Default
If you do not include this statement, the rewrite rule applies to the outer VLAN tag only. | [
{
"name": "outer",
"desc": "Apply the rewrite rule to the outer VLAN tag only."
},
{
"name": "outer-and-inner",
"desc": "Apply the rewrite rule to both the outer and inner VLAN tags."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Applying a Rewrite Rule Definition to a Subscriber Interface in a Dynamic Profile",
"rewrite-rules"
] |
vlan-tag | vlan-tag (outer | outer-and-inner); | [edit class-of-service interfaces interface-name unit logical-unit-number rewrite-rules
ieee-802.1 (rewrite-name | default)] | Apply this IEEE-802.1 rewrite rule to the outer VLAN tag or, if available, both outer and inner VLAN
tags.
Default
If you do not include this statement, the rewrite rule applies to the outer VLAN tag only. | [
{
"name": "outer",
"desc": "Apply the rewrite rule to the outer VLAN tag only."
},
{
"name": "outer-and-inner",
"desc": "Apply the rewrite rule to both the outer and inner VLAN tags."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Applying IEEE 802.1p Rewrite Rules to Dual VLAN Tags"
] |
vlan-tagging (Dynamic) | vlan-tagging; | [edit dynamic-profiles profile-name interfaces interface-name],
[edit interfaces interface-name] | For Fast Ethernet and Gigabit Ethernet interfaces and aggregated Ethernet interfaces configured for
VPLS, enable the reception and transmission of 802.1Q VLAN-tagged frames on the interface.
NOTE: For Ethernet, Fast Ethernet, Tri-Rate Ethernet copper, Gigabit Ethernet, 10-
Gigabit Ethernet, and aggregated Ethernet int... | [] | 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. | [
"Configuring an Interface to Use the Dynamic Profile Configured to Create Stacked VLANs",
"Configuring an Interface to Use the Dynamic Profile Configured to Create Single-Tag VLANs",
"Configuring the L2TP LNS Peer Interface"
] |
vlan-tagging | vlan-tagging native-vlan-id vlan-id; | [edit interfaces interface-name],
[edit logical-systems logical-system-name interfaces interface-name]
QFX Series, NFX Series, and EX4600 Interfaces
[edit interfaces (QFX Series) interface-name ]
[edit interfaces (QFX Series) interface-range interface-range-name ]
SRX Series Interfaces
[edit interfaces interface ] | For Fast Ethernet and Gigabit Ethernet interfaces, aggregated Ethernet interfaces configured for VPLS,
and pseudowire subscriber interfaces, enable the reception and transmission of 802.1Q VLAN-tagged
frames on the interface.
NOTE: For QFX Series configure VLAN identifier for untagged packets received on the
physical i... | [
{
"name": "native-vlan-id",
"desc": "(SRX Series)Configures a VLAN identifier for untagged packets. Enter a number from 0"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Metro Routers. | [
"802.1Q VLANs Overview",
"Configuring a Layer 3 Subinterface (CLI Procedure)",
"Configuring Tagged Aggregated Ethernet Interfaces",
"Example: Configuring Layer 3 Subinterfaces for a Distribution Switch and an Access Switch",
"vlan-id",
"Configuring a Layer 3 Logical Interface",
"Configuring VLAN Tagging... |
vlan-tags (Dual-Tagged Logical Interface) | vlan-tags inner-list [vlan-id vlan-id–vlan-id ] outer <tpid.>vlan-id; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | (MX Series routers only) Binds a dual-tag logical interface to a list of VLAN IDs. Configures the logical
interface to receive and forward any dual-tag frame whose inner VLAN ID tag matches the list of VLAN
IDs you specify.
NOTE: To create a circuit cross-connect (CCC) using VLAN-bundled dual-tag logical
interfaces on ... | [
{
"name": "inner-list [vlan-id vlan-id vlan-id-vlan-id]",
"desc": "A list of valid VLAN ID numbers. Specify the VLAN IDs"
},
{
"name": "outer <tpid.>vlan-id",
"desc": "An optional Tag Protocol ID (TPID) and a valid VLAN ID."
},
{
"name": "1. Inefficient",
"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.5. | [
"Binding VLAN IDs to Logical Interfaces",
"Junos OS VPNs Library for Routing Devices"
] |
vlan-tags (Dynamic Profiles) | vlan-tags outer [tpid].vlan-id [inner [tpid].vlan-id]; | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number] | For Gigabit Ethernet IQ and IQE interfaces only, binds TPIDs and 802.1Q VLAN tag IDs to a logical
interface. You must include the stacked-vlan-tagging statement at the [edit interfaces interface-name]
hierarchy level.
NOTE: The inner-range vid1–vid2 option is supported on IQE PICs only. | [
{
"name": "inner",
"desc": ""
},
{
"name": "[tpid].vlan-id",
"desc": "A TPID (optional) and a valid VLAN identifier in the format tpid.vlan-id. When used in the dynamic-profiles hierarchy, specify the $junos-vlan-id predefined variable to dynamically obtain the VLAN ID. NOTE: On the network-to-n... | 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.
VLAN demux interface support introduced in Junos OS Release 10.2. | [
"Configuring Dual VLAN Tags"
] |
vlan-tags (Stacked VLAN Tags) | vlan-tags inner tpid.vlan-id inner-list value inner-range vid1—vid2 outer tpid.vlan-id; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Bind TPIDs and 802.1Q VLAN tag IDs to a logical interface. TPID fields are used to identify the frame as
an IEEE 802.1Q-tagged frame. | [
{
"name": "inner",
"desc": ""
},
{
"name": "tpid.vlan-id",
"desc": "A TPID and a valid VLAN identifier. TPID is a 16-bit field set to a value of 0x8100 in order to identify the frame as an IEEE 802.1Q-tagged frame. Range: (most routers) For VLAN ID, 1 through 4094. VLAN ID 0 is reserved for tag... | 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 Dual VLAN Tags",
"Configuring Flexible VLAN Tagging on PTX Series Packet Transport Routers",
"stacked-vlan-tagging"
] |
vlan-tags | vlan-tags outer number inner number; | [edit bridge-domains bridge-domain-name],
[edit logical-systems logical-system-name bridge-domains bridge-domain-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name bridge-domains
bridge-domain-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name]... | Specify dual VLAN identifier tags for a bridge domain, VLAN, or VPLS routing instance. | [
{
"name": "outer number",
"desc": "A valid VLAN identifier."
},
{
"name": "inner number",
"desc": "A valid VLAN identifier."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Support for logical systems added in Junos OS Release 9.6. | [
"Configuring a Bridge Domain",
"Configuring a VLAN",
"Configuring VLAN Identifiers for Bridge Domains and VPLS Routing Instances",
"Configuring VLAN Identifiers for VLANs and VPLS Routing Instances",
"Configuring a Layer 2 Virtual Switch",
"Configuring a Layer 2 Virtual Switch on an EX Series Switch"
] |
vlan-tags-outer | vlan-tags-outer vlan-tag; | [edit interfaces interface-set interface-set-name interface interface-name] | The S-VLAN outer tag that belongs to a set of interfaces used to configure hierarchical CoS schedulers. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Junos OS Class of Service User Guide for Routing Devices"
] |
vlans (RA Guard) | vlans (vlan-name | all) {
policy policy-name (stateful | stateless);
} | [edit forwarding-options access-security router-advertisement-guard] | Configure IPv6 Router Advertisement (RA) guard on a VLAN. In an IPv6 deployment, RA guard protects
against rogue RA messages generated either maliciously or unintentionally by unauthorized or
improperly configured routers connecting to the network segment. An RA guard policy is used to
validate incoming RA messages on ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D55. | [
"Understanding IPv6 Router Advertisement Guard",
"Configuring Stateful IPv6 Router Advertisement Guard"
] |
vlans | vlans {
vlan name {
(vlan-id (all | none | number) | vlan-id-list [ vlan-id-numbers] | vlan-tags <inner number>
outer number);
description;
forwarding-options {
dhcp-security {
arp-inspection;
dhcpv6-options {
option-16 {
... | [edit]
[edit routing-instances routing-instance-name] | 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": "vlan-name",
"desc": "Name of the VLAN. The name can include letters, numbers, hyphens (-), and periods (.) and"
}
] | routing—To view this statement in the configuration.
routing–control—To add this statement to the configuration.
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.
Statements for private VLANs and Q-in-Q tunneling introduced in Junos OS Release 12.1 for the QFX
Series switches. | [
"Integrated Routing and Bridging",
"Bridging and VLANs",
"Bridging and VLANs",
"Configuring VLANs for EX Series Switches with ELS Support (CLI Procedure)",
"Configuring Q-in-Q Tunneling and VLAN Q-in-Q Tunneling and VLAN Translation",
"Configuring Q-in-Q Tunneling on Security Devices",
"Integrated Routi... |
vmhost management-if disable | vmhost management-if disable | [edit vmhost] | Disable the host interface eth0, which serves as the management port. You can the disable the interface
if there are any issues associated with security or any hardware failures either at the local end or the
remote end of the interface. if you disable the interface, the transmitter is turned off and the link partner
e... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F6.
NOTE: The command is supported on the routers with RE-MX-X6, RE-MX-X8, and RE-
PTX-X8 Routing Engines only. | [] |
vmhost management-if link-mode | vmhost management-if link-mode (automatic | half-duplex | full-duplex) | [edit vmhost] | Configure the link mode of the host interface eth0, which serves as the management port as half-duplex
or full-duplex. You can also manually select the link mode option as either half-duplex or full-duplex.
Default
The link partners auto-negotiate the speed and duplex link mode and select the highest common
capability. | [
{
"name": "automatic",
"desc": "Autonegotiate the link mode of the management interface. if you set the link mode to automatic, you must also set the link speed to automatic."
},
{
"name": "half-duplex",
"desc": "Set the link mode of the management interface to half-duplex."
},
{
"name":... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F6.
NOTE: The command is supported on the routers with RE-MX-X6, RE-MX-X8, and RE-
PTX-X8 Routing Engines only. | [] |
vmhost management-if speed | vmhost management-if speed { automatic | 10m | 100m | 1g } | [edit vmhost] | Configure the link speed of the host interface eth0, which serves as the management port. If you set the
link speed as 10m or 100m, autonegotiation is turned off and the link speed is the speed that you specify.
Default
The link partners auto-negotiate the speed and duplex link mode and select the highest common
capabi... | [
{
"name": "automatic",
"desc": "Autonegotiate the link speed of the management interface. If you set the link speed as automatic, speed and link mode are auto-negotiated with the link partner."
},
{
"name": "10m",
"desc": "Set the link speed of the management interface to 10Mbps."
},
{
"... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F6.
NOTE: The command is supported on the routers with RE-MX-X6, RE-MX-X8, and RE-
PTX-X8 Routing Engines only. | [] |
vmhost resize vjunos compact | vmhost resize vjunos compact | [edit] | Reduce the routing engine resource footprint on MX Series router to accommodate GNF VMs within the
Routing Engine in in-chassis Junos node slicing. Configuring the vmhost resize vjunos compact statement
enables hyperthreading in Routing Engine CPU. The in-chassis Junos node slicing requires that
hyperthreading be enabl... | [] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1R1. | [] |
vmhost | vmhost {
interfaces name {
family {
(inet | inet6) {
address name {
master-only;
}
gateway gateway;
}
}
}
external interface {
in-band {... | [edit] | Configure VM host management properties. Set values in the edit vmhost hierarchy of the configuration. | [
{
"name": "interfaces",
"desc": "Configure interface properties of the host."
},
{
"name": "management-if0 | management-if1",
"desc": "Configure the host's side management"
},
{
"name": "family (inet|inet6) address",
"desc": "Configure IPv4 or IPv6 parameters."
},
{
"name": "... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F3.
in-band and out-of-band options introduced for NFX devices in Junos OS Release 24.2R1.
NOTE: PTX3000 router supports the Routing and Control Board, RCBPTX. | [
"VM Host Overview",
"Disabling Autorecovery on Routing Engines with VM Host Support"
] |
vnf-license-supplement | vnf-license-supplement {
vnf-id gnf-id
license-supplement-string augmented-ssrn
} | [edit system] | Allocate a MAC address to a licensed guest network function (GNF). For more details, see Assigning
MAC Addresses to GNF. | [
{
"name": "vnf-id gnf-id",
"desc": "Specify the GNF ID that will be assigned the licensed MAC address range. Each license can only be assigned to a single GNF."
},
{
"name": "license-supplement-string augmented-ssrn",
"desc": "Specify the augmented software support reference number (SSRN) string... | Statement introduced in Junos OS Release 19.2R1. | [] | |
vnf-name | vnf-name {
type {
linux-container | virtual-machine;
}
image {
file-path;
bus-type [ide | virtio];
image-type [qcow2 | raw];
}
init-descriptor file-path;
memory {
size size;
features {
hugepages;
}
}
no-autostart;
st... | [edit virtual-network-functions] | Name of the virtual network function. | [
{
"name": "interfaces",
"desc": "Name of the interface. For example, em1."
},
{
"name": "no-autostart",
"desc": "An option to disable auto-start of VNF on the VNF configuration commit."
},
{
"name": "pci-address",
"desc": "An option to specify PCI address for the VNF interfaces."
}... | 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-D45. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
vni | vni [0–16777214] | [edit routing-instances routing-instance-name vlans vlan-name vxlan]
[edit vlans vlan-name vxlan] | Assign a numeric value to identify a Virtual Extensible LAN (VXLAN). All members of a VXLAN must use
the same VNI. | [
{
"name": "vni",
"desc": "Value to specify in the vni attribute. Range: 0 through 16,777,215 NOTE: Starting in Junos OS Release 17.3R3-3, 18.1R3-S3, and 19.1R1, Junos OS supports a VNI value of 0."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1R2. | [
"Understanding VXLANs",
"Manually Configuring VXLANs on QFX Series and EX4600 Switches",
"Examples: Manually Configuring VXLANs on QFX Series and EX4600 Switches"
] |
vni(Interfaces) | vni [0–16777214] | [edit interfaces name unit name tunnel encapsulation vxlan-gpe] | Assign a numeric value to identify a Virtual Extensible LAN (VXLAN). All members of a VXLAN must use
the same virtual network identifier (VNI). | [
{
"name": "vni",
"desc": "Value to specify in the vni attribute. Range: For flexible tunnel interfaces, the range supported is 0 through 16,777,214 for all MX Series routers (except MX80)."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1. | [
"Understanding VXLANs",
"Flexible Tunnel Interfaces Overview",
"Configuring Flexible Tunnel Interfaces",
"Example: Configuring Flexible Tunnel Interfaces on MX Series Routers"
] |
vni-options | vni-options vni vxlan-network-identifier {
designated-forwarder-election-hold-time seconds;
vrf-target {
community;
auto;
import community-name;
export community-name;
}
} | [edit protocols evpn]
[edit routing-instances routing-instance-name protocols evpn] | Configure a designated forwarder election hold time and specific route targets (RTs) for each VXLAN
network identifier (VNI). | [] | 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-D30 . | [
"EVPN Multihoming Overview",
"Understanding EVPN with VXLAN Data Plane Encapsulation",
"Example: Configuring an EVPN Control Plane and VXLAN Data Plane"
] |
vnid (EVPN) | vnid; | [edit routing-instances routing-instance-name] | Enables having the same MAC frames across multiple VXLAN segments without traffic crossover.
Multicast in VXLAN is implemented as Layer 3 multicast, in which endpoints subscribe to groups. VNID
is a 24-bit virtual network identifier that uniquely identifies the VXLAN segment. | [] | 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. | [
"Understanding EVPN with VXLAN Data Plane Encapsulation",
"Example: Configuring an EVPN Control Plane and VXLAN Data Plane",
"EVPN Type-5 Route with MPLS encapsulation for EVPN-MPLS",
"EVPN Type-5 Route with VXLAN encapsulation for EVPN-VXLAN"
] |
voice (Application Profile) | voice {
dscp (alias | bits);
forwarding-class class-name;
} | [edit services cos application-profileprofile-name sip] | Set the appropriate dscp and forwarding-class values for SIP voice traffic.
Default
By default, the system will not alter the DSCP or forwarding class for SIP voice traffic. | [] | 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 CoS Rules on Services PICs"
] |
voice | voice {
dscp (Services CoS) (alias | bits);
forwarding-class (Services PIC Classifiers) class-name;
} | [edit services cos application-profile profile-name sip] | Set the appropriate dscp and forwarding-class values for SIP voice traffic.
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 9.3. | [
"Configuring Application Profiles for Use as CoS Rule Actions"
] |
voip | voip {
interface (all | [interface-name | access-ports]) {
forwarding-class forwarding-class;
vlan vlan-name );
voip-mac-exclusive;
}
} | For platforms with ELS:
[edit switch-options voip]
For platforms without ELS:
[edit ethernet-switching-options voip] | Configure voice over IP (VoIP) on interfaces.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | 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.
Hierarchy level [edit switch-options] introduced in Junos OS Release 13.2X50-D10. (See Using the
Enhanced Layer 2 Software CLI for information about ELS.)
Configuration option voip-mac-exclusive introduced in Junos OS Release 13.2X50-D10. | [
"Example: Setting Up VoIP with 802.1X and LLDP-MED on an EX Series Switch",
"Example: Configuring VoIP on an EX Series Switch Without Including 802.1X Authentication",
"Example: Configuring VoIP on an EX Series Switch Without Including LLDP-MED Support"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.