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 |
|---|---|---|---|---|---|---|---|
use-post-convergence-lfa (Protocols OSPF) | use-post-convergence-lfa <maximum-backup-paths maximum-backup-paths> <maximum-labels maximum-
labels> ; | [edit logical-systems name protocols ospf backup-spf-options],
[edit logical-systems name routing-instances name protocols ospf backup-spf-options],
[edit protocols ospf backup-spf-options],
[edit routing-instances name protocols ospf backup-spf-options] | Calculate post-convergence MPLS fast reroute (FRR) backup next hops for the OSPF protocol using
segment routing (SR). Junos OS allows you to control the maximum number of equal-cost multipath
(ECMP) backup paths installed for a given destination. Junos OS also allows you to control the maximum
number of labels in the i... | [
{
"name": "maximum-backup-paths",
"desc": "Set the maximum number of equal-cost post-convergence backup paths to be installed. Default: 1 Range: 1-8"
},
{
"name": "maximum-labels",
"desc": "Set the maximum number of labels used to construct a post-convergence backup path. If the backup path fo... | routing | Statement introduced in Junos OS Release 18.2R1 for MX Series, PTX Series, and QFX Series. | [
"Topology-Independent Loop-Free Alternate with Segment Routing for OSPF"
] |
use-post-convergence-lfa | use-post-convergence-lfa <maximum-backup-paths maximum-backup-paths> <maximum-labels maximum-
labels> ; | [edit logical-systems name protocols isis backup-spf-options],
[edit logical-systems name routing-instances name protocols isis backup-spf-options],
[edit protocols isis backup-spf-options],
[edit routing-instances name protocols isis backup-spf-options] | Calculate post-convergence MPLS fast reroute (FRR) backup next hops for the IS-IS protocol using
segment routing (SR). Topology-independent loop-free alternate (TI-LFA) provides protection against link
failure, node failure, and fate-sharing failures. By default, Junos OS provides link protection. Junos OS
allows you t... | [
{
"name": "maximum-backup-",
"desc": ""
},
{
"name": "paths",
"desc": "Set the maximum number of equal-cost post-convergence backup paths to be installed. For remote LFA, the IS-IS protocol installs only one backup path. The maximum backup path range allows you to install multiple backup paths ... | routing | Statement introduced in Junos OS Release 17.4R1 for MX Series, PTX Series, and QFX Series. | [
"Understanding Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS",
"Configuring Topology-Independent Loop-Free Alternate with Segment Routing for IS-IS"
] |
use-primary (DHCP Local Server) | use-primary primary-profile-name; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dynamic-profile profile-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server group group-name dynamic-profile profile-name],
[edit l... | Specify the dynamic profile to configure as the primary dynamic profile. The primary dynamic profile is
instantiated when the first subscriber or DHCP client logs in. Subsequent subscribers (or clients) are not
assigned the primary dynamic profile; instead, they are assigned the dynamic profile specified for the
interf... | [
{
"name": "primary-profile-name",
"desc": "Name of the dynamic profile to configure as the primary dynamic profile"
}
] | 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. | [
"Attaching Dynamic Profiles to DHCP Subscriber Interfaces or DHCP Client Interfaces"
] |
use-primary (DHCP Relay Agent) | use-primary primary-profile-name; | [edit forwarding-options dhcp-relay dhcpv6 dynamic-profile profile-name],
[edit forwarding-options dhcp-relay dynamic-profile profile-name],
[edit forwarding-options dhcp-relay dhcpv6 group group-name dynamic-profile profile-name],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name dynamic-prof... | Specify the dynamic profile to configure as the primary dynamic profile. The primary dynamic profile is
instantiated when the first subscriber logs in. Subsequent subscribers are not assigned the primary
dynamic profile; instead, they are assigned the dynamic profile specified for the interface. When the first
subscrib... | [
{
"name": "primary-profile-name",
"desc": "Name of the dynamic profile to configure as the primary dynamic profile"
}
] | 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.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4.
Support at the [edit ... dual-stack-group dual-stack-group-name] hierarchy level introduced in Junos OS
Release 15.1. | [
"Attaching Dynamic Profiles to DHCP Subscriber Interfaces or DHCP Client Interfaces"
] |
use-string | use-string string;
Hierarchy Level (For Platforms with Enhanced Layer 2 Software (ELS))
[edit vlans vlan-name forwarding-options dhcp-security option-82 remote-id] | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security option-82 circuit-id] | Use a string rather than the MAC address of the host system (the default) in the remote ID value in the
DHCP option 82 information. | [
{
"name": "string",
"desc": "Character string used as the remote ID value."
}
] | 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.
Hierarchy level [edit vlans vlan-name forwarding-options dhcp-security] introduced in Junos OS Release
13.2X50-D10. (See Using the Enhanced Layer 2 Software CLI for information about ELS.)
Hierarchy level [edit bridge-domains bridge-domain-name forwarding-options dhcp-secur... | [
"Configuring DHCP Option 82 on a Router with Bridge Domain",
"Example: Setting Up DHCP Option 82",
"http://tools.ietf.org/html/rfc3046"
] |
use-transport-class | use-transport-class {
fib-install;
inet3-install;
} | [edit logical-systems name protocols source-packet-routing],
[edit logical-systems name routing-instances name routing-options flex-algorithm],
[edit logical-systems name routing-options flex-algorithm],
[edit logical-systems name tenants name routing-instances name routing-options flex-algorithm],
[edit protocols sour... | Enable transport class on SR-TE colored policies to Install ingress routes via transport class RIBs | [
{
"name": "fib-install",
"desc": "Install SR-TE routes in FIB"
},
{
"name": "inet3-install",
"desc": "Install SR-TE routes in inet{6}.3 table"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1. | [
"BGP Classful Transport Planes Overview",
"Color-Based Traffic Engineering Configuration"
] |
use-underlying-interface-mac | use-underlying-interface-mac | [edit system demux-options] | Configure the software to use the same link-local address for both interfaces when you are using Router
Advertisement for IPv6 subscribers on dynamic demux interfaces that run over underlying static demux
interfaces. In this case, the link-local address for the underlying interface should be based the MAC
address of th... | [] | 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. | [
"Dual Stack for PPPoE Access Networks Using NDRA"
] |
use-vlan-id (DHCP Relay Agent) | use-vlan-id; | [edit forwarding-options dhcp-relay dhcpv6],
[edit forwarding-options dhcp-relay dhcpv6 group group-name],
[edit forwarding-options dhcp-relay dual-stack-group dual-stack-group-name],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6 ...],
[edit logical-systems logical-system-name forwardin... | Specify that the VLAN is identified by the VLAN ID, rather than the VLAN name, when you configure
the DHCPv6 relay agent to include either of the following in packets it sends to a DHCPv6 server:
•
DHCPv6 Interface-ID (option 18)
•
DHCPv6 Remote-ID (option 37) | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"DHCPv6 Relay Agent",
"Extended DHCP Relay Agent Overview"
] |
use-vlan-id | use-vlan-id;
Hierarchy Level (For Platforms with Enhanced Layer 2 Software (ELS))
[edit forwarding-options helpers bootp dhcp-option82-circuit-id],
[edit forwarding-options helpers bootp interface interface-name dhcp-option82-circuit-id] | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security option-82 circuit-id] | Use the VLAN ID rather than the VLAN name (the default) in the circuit ID or remote ID value in the
DHCP option 82 information.
NOTE: The use-vlan-id statement is mutually exclusive with the use-interface-description
and no-vlan-interface-name statements.
The use-vlan-id statement only applies to interfaces in a bridge... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3.
Hierarchy level [edit vlans vlan-name forwarding-options dhcp-security] introduced in Junos OS Release
13.2X50-D10. (See Using the Enhanced Layer 2 Software CLI for information about ELS.)
Hierarchy level [edit bridge-domains bridge-domain-name forwarding-options dhcp-secu... | [
"Example: Setting Up DHCP Option 82 Using the Same VLAN",
"Example: Setting Up DHCP Option 82",
"http://tools.ietf.org/html/rfc3046."
] |
user (Access) | user user-name {
authentication {
(encrypted-password encrypted-password | plain-text-password);
load-key-file filename;
no-public-keys;
ssh-ecdsa name {
from host-list;
}
ssh-ed25519 name {
from host-list;
}
ssh-rsa name {
... | [edit system login] | Configure access permission for individual users. Starting in Junos OS Release 18.3, the ssh-dsa hostkey
algorithm is deprecated— rather than immediately removed—to provide backward compatibility and a
chance to bring your configuration into compliance with the new configuration. | [
{
"name": "authentication",
"desc": "Specify one or more authentication methods that a user can use to log in to the router or switch. You can assign multiple authentication methods to a single user."
},
{
"name": "encrypted-password",
"desc": "Message Digest 5 (MD5) or other encrypted authentic... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement no-public-keys introduced in Junos OS Release 15.1.
Statement cli introduced in Junos OS 17.3. | [
"Configuring Junos OS User Accounts by Using a Configuration Group",
"root-authentication"
] |
user (SNMP v3) | user username; | [edit snmp v3 usm local-engine],
[edit snmp v3 usm remote-engine engine-id] | Specify a user associated with an SNMPv3 group on a local or remote SNMP engine. | [
{
"name": "username",
"desc": "SNMPv3 user-based security model (USM) username."
}
] | 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. | [] |
user (System Logging) | user (username | *) {
facility severity;
match "regular-expression";
match-strings string-name;
} | [edit system syslog] | Configure the logging of system messages to user terminals. | [
{
"name": "* (the asterisk)",
"desc": "Log messages to the terminal sessions of all users who are currently logged in."
},
{
"name": "facility",
"desc": "Class of messages to log. To specify multiple classes, include multiple facility severity"
},
{
"name": "severity",
"desc": "Sever... | 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. | [
"Direct System Log Messages to a User Terminal",
"System Logging Facilities and Message Severity Levels"
] |
user (System Services) | user {
user-name;
password password;
} | [edit system services webapi (System Services)] | Configure the Web API process (webapi) username and password for the account.
The Web API process, acting as an HTTP server, allows the Aruba ClearPass Policy Manager (CPPM),
acting as a client, to send POST request messages to HTTP server. The CPPM, which is the
authentication source for this feature, sends to the SRX... | [
{
"name": "user-name",
"desc": "Specify the user name for the integrated ClearPass authentication and enforcement feature Web API process (webapi) user."
},
{
"name": "password",
"desc": "Specify the password for the integrated ClearPass authentication and enforcement feature Web API process (we... | 1. system—To view this statement in the configuration.
2. system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [] |
user-defined-option-82 | user-defined-option-82 string; | [edit forwarding-options dhcp-relay group group-name interface interface-name overrides user-
defined-option82 string],
[edit forwarding-options dhcp-relay group group-name overrides user-defined-option82 string],
[edit forwarding-options dhcp-relay overrides user-defined-option82 string] | 21.2R1
Starting with Junos OS Release 21.2R1, QFX Series switches support the user-defined-option-82 CLI
statement in a stateless DHCP relay configuration. You can configure stateless DHCP relay using the
forward-only CLI statement at the [edit forwarding-options dhcp-relay] hierarchy level. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Including a Textual Description in DHCP Options",
"Using DHCP Relay Agent Option 82 Information"
] |
user-firewall (Access Firewall-Authentication) | user-firewall {
default-ssl-termination-profile default-ssl-termination-profile;
} | [edit access firewall-authentication] | Enable the command default-ssl-termination-profile to set a default SSL termination profile. Enable this
configuration to enforce security for all access profiles. | [
{
"name": "default-ssl-termination-profile",
"desc": "Use default-ssl-termination-profile if no ssl-termination-profile is configured."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1. | [
"[edit access firewall-authentication]",
"user-firewall",
"SAML Authentication in Juniper Secure Connect"
] |
user-firewall | user-firewall {
access-profile profile-name;
auth-only-browser;
auth-user-agent;
domain domain-name;
ssl-termination-profile profile-name;
web-redirect;
web-redirect-to-https;
} | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
firewall-authentication] | Configure user role firewall authentication, and map the source IP address to the username and its
associated roles (groups). The mapped data is written to the firewall authentication table for later
retrieval by the user role firewall. The user role firewall uses the username and role information to
determine whether ... | [
{
"name": "access-profile profile-name",
"desc": "Specify the name of the access profile to be used for authentication."
},
{
"name": "domain domain-name",
"desc": "Specify the name of the domain where firewall authentication occurs in the event that the Windows Management Instrumentation client... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10. Support for the domain keyword added in
Junos OS Release 12.1X47-D10. | [
"Active Directory as Identity Source",
"Configure Active Directory as Identity Source on Firewall",
"Understanding User Role Firewalls",
"Example: Configuring a User Role Firewall on an SRX Series Device"
] |
user-group-mapping | user-group-mapping {
ldap {
address ip-address {
port port;
}
authentication-algorithm {
simple;
}
base base;
ssl;
user username {
password password;
}
}
} | [edit services user-identification active-directory-access domain] | Configure the SRX Series Firewall to connect to an LDAP server, so that the server can provide the SRX
Series with user-to-group mappings. These mappings are used to implement the integrated user firewall
feature. The domain controller acts as the LDAP server in typical customer scenarios.
Most of this statement is opt... | [
{
"name": "ldap",
"desc": "Required. LDAP is the protocol used to access the LDAP server to get user-to-group mappings."
},
{
"name": "address ip-address",
"desc": "Optional. Specify the IP address of the LDAP server. If no address is specified, the system uses one of the configured Active Direc... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X47-D10. | [
"LDAP Functionality in Integrated User Firewall"
] |
user-id | user-id {ascii ascii hexadecimal hexadecimal}; | [edit interfaces interface-name unit logical-unit-number family family dhcp-client client-
identifier] | Specify an ASCII or hexadecimal user ID for the Dynamic Host Configuration Protocol (DHCP) client. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. | [] |
user-identification (Services) | user-identification {
active-directory-access {
domain domain-name {
user username;
password password;
domain-controller domain-controller-name {
address domain-controller-address;
}
ip-user-mapping {
discovery-m... | [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... | [
{
"name": "authentication-entry-timeout",
"desc": ""
},
{
"name": "minutes",
"desc": "Timeout interval starting from the Active Directory/domain controller login time, the last active session, or the last successful probe. A setting of 0 means the authentication does not need a timeout. We recom... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X47-D10.
logical-domain-identity-management option introduced in Junos OS Release 19.3R1. | [] |
user-identification | user-identification {
authentication-source {
firewall-authentication (disable | priority priority);
local-authentication-table (disable | priority priority);
unified-access-control (disable | priority priority);
}
traceoptions {
file {
filename;
files... | [edit security] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | 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. Statement updated in Junos OS Release 12.1X45-D10. | [
"Understanding User Role Firewalls",
"Understanding the User Identification Table"
] |
user-name (Event Policy) | user-name username; | [edit event-options policy policy-name then change-configuration],
[edit event-options policy policy-name then event-script filename],
[edit event-options policy policy-name then execute-commands],
[edit event-options policy policy-name then upload filename (filename | committed) destination
destination-name] | Associate a user with an action in an event policy. The event policy action is executed under the
privileges of the associated user. You can configure the user-name statement for the following actions:
•
Changing the configuration
•
Executing a SLAX or XSLT event script
•
Executing commands
•
Uploading a file
NOTE: Whe... | [
{
"name": "username",
"desc": "Username that is configured at the [edit system login] hierarchy level."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 8.4.
Support at the [edit event-options policy policy-name then change-configuration] hierarchy level introduced in
Junos OS Release 12.1. | [
"Change the User Privilege Level for an Event Policy Action"
] |
user-name | user-name {
equals value;
has-prefix value;
has-suffix value;
matches value;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from] | Specify the RADIUS AVP User-Name for the incoming RADIUS request from the subscriber.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selected.
The remaining statements are explained separately. See CL... | [] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
user-name-include (OCS Partition) | user-name-include{
base-interface-name;
delimiter delimiter-character;
domain-name my-domain;
interface-name;
mac-address;
nas-port-id;
origin-host;
origin-realm;
user-name;
user-prefix pref;
} | [edit access ocs partition partition-name] | Configure the username identification to be used in an Online Charging Function (OCS) partition. You
can configure a data string to include the following options. | [
{
"name": "base-interface-",
"desc": ""
},
{
"name": "name",
"desc": "Use the physical or underlying interface name. If both the underlying interface and the client application perform authentication, authorization, and provisioning, the identification attributes in the server requests enable th... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"3GPP Policy and Charging Control for Wireline Provisioning and Accounting",
"3GPP Policy and Charging Control for Wireline Provisioning and Accounting",
"3GPP Policy and Charging Control for Wireline Provisioning and Accounting",
"3GPP Policy and Charging Control for Wireline Provisioning and Accounting",
... |
user-password (PCEF Profile) | user-password password; | [edit unified-edge pcef profiles profile-name aaa-policy-control] | Configure the user password for subscribers assigned to the parent PCEF profile. | [
{
"name": "password",
"desc": "Password for access requests to the RADIUS server. Range: 1 through 32 characters"
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring a Policy and Charging Enforcement Function Profile for Junos OS Subscriber Aware",
"Policies That a RADIUS Server Controls",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules"
] |
user-planes | user-planes name {
colocated-user-plane {
ip-endpoint-address ip-endpoint-address;
}
data-network-name data-network-name;
ip-address ip-address;
routing-instance routing-instance;
} | [edit services agf] | Configure a tunnel to the User Plane Function (UPF). | [
{
"name": "name",
"desc": "User plane name"
},
{
"name": "colocated-user-plane",
"desc": "Specify there is a colocated UPF. The ip-endpoint-address ip-endpoint-address is the IP address of the UPF."
},
{
"name": "data-network-name",
"desc": "Data network name Name of the data network... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.3R1. | [] |
user-prefix (DHCP Local Server) | user-prefix user-prefix-string; | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server authentication username-include],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 authentication ],
[edit logical-systems logic... | Specify the user prefix that is concatenated with the username during the subscriber authentication or
DHCP client authentication process. | [
{
"name": "user-prefix-string",
"desc": "User prefix string."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"Specifying Authentication Support"
] |
user-prefix (DHCP Relay Agent) | user-prefix user-prefix-string; | [edit forwarding-options dhcp-relay authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 authentication username-include],
[edit forwarding-options dhcp-relay dhcpv6 group group-name authentication username-include],
[edit forwarding-options dhcp-relay dual-stack-grouop dual-stack-group-name aut... | Specify the user prefix that is concatenated with the username during the subscriber authentication or
client authentication process. Use the statement at the [edit ... dhcpv6] hierarchy levels to configure
DHCPv6 support. | [
{
"name": "user-prefix-string",
"desc": "User prefix string."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4.
Support at the [edit ... dual-stack-group dual-stack-group-name] hierarchy level introduced in Junos OS
Release 15.1. | [
"DHCP with External Authentication Server"
] |
user-prefix (Static Subscribers) | user-prefix user-prefix-string; | [edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers authentication username-include],
[edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers group group-name authentication username-inclu... | Specify that a string is included as the beginning of the username created for all static subscribers or for
the static subscribers in a specified group. The group version of the statement takes precedence over
the global version. The username is also sent to RADIUS in the Access-Request message. | [
{
"name": "user-prefix-string",
"desc": "String that begins the username. The string can include the following characters: a"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"JSRC and Subscribers on Static Interfaces",
"JSRC and Subscribers on Static Interfaces",
"JSRC and Subscribers on Static Interfaces"
] |
user-prefix | user-prefix user-prefix-string; | [edit interfaces interface-name auto-configure vlan-ranges authentication username-include],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication username-include] | Specify the user prefix that is concatenated with the username during the subscriber authentication
process. | [
{
"name": "user-prefix-string",
"desc": "The user prefix string."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"Configuring VLAN Interface Username Information for AAA Authentication"
] |
user-query (Services User Identification) | user-query {
ca-certificate ca-certificate;
client-id client-id;
client-secret client-secret;
delay-query-time seconds;
query-api query-api;
token-api token-api;
web-server (Services) {
server-name;
address address;
connect-method (http | https);
port port;
... | [edit services user-identification authentication-source (Services User Identification ClearPass)
aruba-clearpass] | ca-certificate- Configures the Integrated ClearPass Authentication and Enforcement feature user query
function configuration. User query enables the SRX Series Firewall to query the ClearPass Policy
Manager (CPPM) for authentication and identity information for an individual user under certain
circumstance when it does... | [
{
"name": "ca-certificate",
"desc": "Specify the certificate file that the SRX Series Firewall uses to verify the Clearpass server’s certificate for the SSL connection that is used for the user query function. As the ClearPass administrator, you must export the server’s certificate from the CPPM and import ... | services
To view this statement in the configuration.
services-control
To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D30. | [
"Configure Integrated ClearPass Authentication and Enforcement"
] |
user-route-proxy | user-route-proxy; | [edit logical-systems name protocols neighbor-discovery ndp-proxy],
[edit protocols neighbor-discovery ndp-proxy] | Enable ND proxy for user routes. This is a global configuration and is applicable to all interfaces where
unrestricted proxy mode is enabled. To disable this configuration use the delete protocols neighbor-
discovery ndp-proxy user-route-proxy. | [] | Statement introduced in Junos OS Release 25.2R1. | [] | |
username (Security Antivirus) | username name; | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine pattern-update proxy]
[edit security utm feature-profile anti-virus kaspersky-lab-engine pattern-update proxy]
[edit security utm feature-profile anti-virus sophos-engine pattern-update proxy] | 15.1X49-D10
The Express and Kaspersky Antivirus feature is 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 Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 11.2.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Change History Table
Feature support is de... | [] |
username (Services) | username user-name; | [edit services flow-collector transfer-log-archive archive-sites] | Specify the username for the transfer log server. | [
{
"name": "user-name",
"desc": "FTP server username."
}
] | 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 Transfer Logs"
] |
username-include (Demux) | username-include {
auth-server-realm realm-string;
delimiter delimiter-character;
domain-name domain-name;
interface-name;
source-address;
user-prefix user-prefix-string;
} | [edit interfaces interface-name unit unit-number demux inet auto-configure address-ranges
authentication]
[edit interfaces interface-name unit unit-number demux inet6 auto-configure address-ranges
authentication] | Specify the information included in the username created for the demultiplexing (demux) interface
options. The remaining statement is explained separately. | [
{
"name": "auth-server-realm",
"desc": ""
},
{
"name": "auth-server-realm-string",
"desc": "Specify the authentication server name string used for the demultiplexing (demux) interface options."
},
{
"name": "delimiter delimiter-character",
"desc": "Specify the character used as the d... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"IP Demultiplexing Interfaces on Packet-Triggered Subscriber Services"
] |
username-include (DHCP Local Server) | username-include {
circuit-type;
client-id <exclude-headers> <use-automatic-ascii-hex-encoding>;
delimiter delimiter-character;
domain-name domain-name-string;
interfaces-description (device-interface | logical-interface);
interface-name ;
logical-system-name;
mac-address;
option-60;... | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server ...],
[edit logical-systems logical-system-name system services dhcp-local-server ...],
[edit routing-instances routing-instance-name system services dhcp-local-server ...],
[edit system services dhcp-lo... | Configure the username that the router or switch passes to the external AAA server. You must include at
least one of the optional statements for the username to be valid. If you do not configure a username,
the router (or switch) accesses the local authentication service only and does not use external
authentication se... | [
{
"name": "vlan-tags",
"desc": "Include the subscriber session VLAN tags in the username for interactions with an external authority. Both single-tagged and double-tagged VLANs are supported: The tags are added in the format outer-vlan-tag-inner-vlan-tag. The outer tag is always included; the inner tag is i... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
vlan-tags option added in Junos OS Release 18.3R1 on MX Series routers. | [
"Specifying Authentication Support",
"Creating Unique Usernames for DHCP Clients"
] |
username-include (DHCP Relay Agent) | username-include {
circuit-type;
client-id <exclude-headers> <use-automatic-ascii-hex-encoding>;
delimiter delimiter-character;
domain-name domain-name-string;
interface-description (device-interface | logical-interface);
interface-name;
logical-system-name;
mac-address;
option-60;
... | [edit forwarding-options dhcp-relay authentication],
[edit forwarding-options dhcp-relay group group-name authentication],
[edit forwarding-options dhcp-relay dhcpv6 authentication],
[edit forwarding-options dhcp-relay dhcpv6 group group-name authentication],
[edit forwarding-options dhcp-relay dual-stack-group dual-st... | Configure the username that the router (or switch) passes to the external AAA server. You must include
at least one of the optional statements for the username to be valid. If you do not configure a username,
the router (or switch) accesses the local authentication service only and does not use external
authentication ... | [
{
"name": "vlan-tags",
"desc": "Include the subscriber session VLAN tags in the username for interactions with an external authority. Both single-tagged and double-tagged VLANs are supported: The tags are added in the format outer-vlan-tag-inner-vlan-tag. The outer tag is always included; the inner tag is i... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4.
Support at the [edit ... dual-stack-group dual-stack-group-name] hierarchy level introduced in Junos OS
Release 15.1.
vlan-tags option added in Junos OS Release 18.3R1 on MX Series router... | [
"Creating Unique Usernames for DHCP Clients",
"Specifying Authentication Support"
] |
username-include (Interfaces) | username-include {
circuit-id;
circuit-type;
delimiter delimiter-character;
domain-name domain-name-string;
interface-name;
mac-address;
option-18;
option-37;
option-82 <circuit-id> <remote-id>;
radius-realm radius-realm-string;
remote-id;
user-prefix user-prefix-string;
... | [edit interfaces interface-name auto-configure vlan-ranges authentication],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication] | Configure the username that the router passes to the external AAA server. You must include at least one
of the optional statements for the username to be valid. If you do not configure a username, the router
accesses the local authentication service only and does not use external authentication services, such as
RADIUS... | [
{
"name": "vlan-tags",
"desc": "Include the subscriber session VLAN tags in the username for interactions with an external authority. Both single-tagged and double-tagged VLANs are supported: The tags are added in the format outer-vlan-tag-inner-vlan-tag. The outer tag is always included; the inner tag is i... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
vlan-tags option added in Junos OS Release 18.3R1 on MX Series routers. | [
"Configuring VLAN Interface Username Information for AAA Authentication",
"Using DHCP Option 82 Suboptions in Authentication Usernames for Autosense VLANs",
"Using DHCP Option 18 and Option 37 in Authentication Usernames for DHCPv6 Autosense VLANs",
"Configuring a Username for Authentication of Out-of-Band Tr... |
username-include (Local Authentication) | username-include {
circuit-id;
delimiter character;
domain-name name;
mac-address;
remote-id;
} | [edit dynamic-profiles name interfaces $junos-interface-ifd-name unit $junos-interface-unit ppp-
options local-authentication] | Configure a local username that authd can use to request authentication for terminated PPP
subscribers. This enables the external RADIUS server to pass implementation-specific configuration for
successfully authenticated subscribers. Local authentication supports CPEs that do not negotiate
authentication protocols in t... | [
{
"name": "circuit-id",
"desc": "Include the agent circuit identifier (ACI) in the local username."
},
{
"name": "delimiter",
"desc": ""
},
{
"name": "character",
"desc": "Specify the character that separates components that make up the concatenated username. Default: Period (.)"
... | interface | Statement introduced in Junos OS Release 18.2R1. | [
"PPP Subscriber Access Networks Overview"
] |
username-include (Static Subscribers) | username-include {
delimiter delimiter-character;
domain-name domain-name;
interface;
logical-system-name;
routing-instance-name;
user-prefix user-prefix-string;
vlan-tags;
} | [edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers authentication],
[edit logical-systems logical-system-name routing-instances routing-instances-name system
services static-subscribers group group-name authentication],
[edit logical-systems logical... | Specify the information included in the username created for all static subscribers or for static
subscribers in a specified group. The group version of the statement takes precedence over the global
version. The username is also sent to RADIUS in the Access-Request message. | [
{
"name": "delimiter",
"desc": ""
},
{
"name": "delimiter-character",
"desc": "Specify the delimiter character that separates the different fields configured for the username. You can specify only a single character as the delimiter. Default: The default delimiter is a period (.)."
},
{
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6.
delimiter and vlan-tags options added in Junos OS Release 18.3R1. | [
"JSRC and Subscribers on Static Interfaces",
"JSRC and Subscribers on Static Interfaces",
"JSRC and Subscribers on Static Interfaces"
] |
using-user-password | using-user-password password; | [edit access domain map] | Enable the use of an override CHAP password. The override CHAP password replaces the CHAP
challenge response that the PPP client sends to the server for authentication.
You must configure the override CHAP password using the override-chap-password statement at the [edit
access domain map] hierarchy level. | [] | access—To view this statement in the configuration.
access-control—To add this statement in the configuration. | Statement introduced in Junos OS Release 21.3R1. | [
"Changing the Username and Password to Simplify Off-Chassis Provisioning"
] |
usm | usm {
local-engine {
user username {
authentication-md5 {
authentication-password authentication-password;
}
authentication-none;
authentication-sha {
authentication-password authentication-password;
}
p... | [edit snmp v3] | Configure user-based security model (USM) information.
The remaining statements are explained separately. See CLI Explorer. | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [] |
utc-timestamp | utc-timestamp; | For routers with the MX-SPC3 services card, you can configure the statement at the following hierarchy
levels:
[edit services service-set service-set-name syslog],
[edit interfaces vms-interface\ams-interface services-options] | Display the system timestamp in the syslog by overriding the default local system timestamp in syslog to
UTC format.
Default
When the statement is not enabled, the syslog displays the local system timestamp in syslog. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced for routers with MX-SPC3 cards in Junos OS Release 21.1.
NOTE: In Junos OS Release 21.1R1, the statement is implemented at the at the
[edit interfaces vms-interface\ams-interface services-options
hierarchy level. | [] |
utm default-configuration | utm {
default-configuration {
anti-spam {
address-blacklist;
address-whitelist;
sbl {
custom-tag-string;
(sbl-default-server | no-sbl-default-server);
spam-action (block | tag-header | tag-subject);
}
... | [edit security utm] | 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": "default-configuration",
"desc": "Global default Content Security configurations."
},
{
"name": "anti-spam",
"desc": "Configure the default Content Security configuration for antispam feature profile."
},
{
"name": "anti-virus",
"desc": "Configure the default Content Securi... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Starting in Junos OS Release 21.4R1, the rule-set and rules configurations introduced under the [edit
security utm utm-policy <utm-policy-name> content-filtering] hierarchy level can be used from [edit security
utm default-configuration content-filtering hierarchy.
Content filtering options based on mime-type, content-... | [] |
uuid (Applications) | uuid hex-value; | [edit applications application application-name term term-name] | Specify the Universal Unique Identifier (UUID) for objects. DCE RPC services are mainly used by
Microsoft applications. The ALG uses well-known TCP port 135 for port mapping services and uses the
Universal Unique Identifier (UUID) instead of the program number to identify protocols. The main
application-based DCE RPC i... | [
{
"name": "uuid hex-value",
"desc": "Specify the universal unique identifier (UUID) for objects."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement modified in Junos OS Release 8.5. | [] |
uuid | uuid hex-value; | [edit applications application application-name] | Specify the Universal Unique Identifier (UUID) for DCE RPC objects. | [
{
"name": "hex-value",
"desc": "Hexadecimal value."
}
] | 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. | [
"ALG Descriptions",
"Configuring a Universal Unique Identifier",
"Examples: Configuring Application Protocols",
"Verifying the Output of ALG Sessions",
"V"
] |
v3 | v3 {
notify name {
tag tag-name;
type trap;
}
notify-filter profile-name {
oid object-identifier (include | exclude);
}
snmp-community community-index {
community-name community-name;
security-name security-name;
tag tag-name;
}
target-address... | [edit snmp] | Configure SNMPv3.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "must configure the parameters as follows:",
"desc": "Message-processing model: v3 Security level: privacy Security model: usm target-address-name is the string that identifies the target address. tag-name defines the target addresses to which this notification is sent. This notification is sent... | 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. | [] |
v4address | v4address {
equals;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from attribute name
format] | Specify the custom AVP attribute’s format as an IPv4 address and the value to match for the incoming
RADIUS request from the IP-based subscriber.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selecte... | [] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
v4ov6 | v4ov6 ipv6-anycast-source-duplication; | [edit logical-systems name routing-instances name routing-options dynamic-tunnels],
[edit logical-systems name routing-options dynamic-tunnels],
[edit logical-systems name tenants name routing-instances name routing-options dynamic-tunnels],
[edit routing-instances name routing-options dynamic-tunnels],
[edit routing-o... | Enable dynamic tunnel V4oV6 mode | [
{
"name": "ipv6-anycast-source-duplication",
"desc": "Enable full resolved nh base source-tunnel"
}
] | routing | [] | |
v6address | v6address {
equals;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from attribute name
format] | Specify the custom AVP attribute’s format as an IPv6 address and the value to match for the incoming
RADIUS request from the IP-based subscriber.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selecte... | [] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
v6prefix | v6prefix {
apply-groups [group-names];
apply-groups-except [group-names];
equals;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from attribute name
format] | Specify the custom AVP attribute’s format as an IPv6 address prefix and the value to match for the
incoming RADIUS request from the IP-based subscriber.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is ... | [] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
v6rd | v6rd v6rd-softwire-concentator {
ipv4-prefix ipv4-prefix;
v6rd-prefix ipv6-prefix;
mtu-v4 mtu-v4;
softwire-address ipv4-address;
} | [edit services softwire softwire-concentrator]
[edit services softwires softwire-types | Configure settings for a 6rd concentrator used to process IPv6 packets encapsulated in IPv4 packets.
The v6rd statement is supported only on the MS-DPC, MS-100, MS-400, and MS-500 line cards. The v6rd
statement is not supported on MS-MPCs and MS-MICs. | [
{
"name": "ipv4-prefix",
"desc": "IPv4 prefix of the customer edge (CE) network"
},
{
"name": "ipv6-prefix",
"desc": "IPv6 prefix of the 6rd domain."
},
{
"name": "mtu-v4",
"desc": "Maximum transmission unit (MTU), in bytes (576 through 9192), for IPv6 packets"
},
{
"name": "... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
Support added in Junos OS release 20.2R1 for the v6rd concentrator at the [edit services softwires
softwire-types edit hierarchy for Next Gen Services on MX240, MX480, and MX860 routers. | [
"Configuring a 6rd Softwire Concentrator"
] |
vacm | vacm {
access {
group group-name {
(default-context-prefix | context-prefix context-prefix){
security-model (any | usm | v1 | v2c) {
security-level (authentication | none | privacy) {
notify-view view-name;
read-... | [edit snmp v3] | Configure view-based access control model (VACM) information.
The remaining statements are explained separately. See CLI Explorer. | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [] |
valid-lifetime (Dynamic Router Advertisement) | valid-lifetime seconds; | [edit dynamic-profiles profile-name protocols router-advertisement interface interface-name
prefix prefix] | Specify how long the prefix remains valid for onlink determination. | [
{
"name": "seconds",
"desc": "Valid lifetime, in seconds. If you set the valid lifetime to 0xffffffff, the lifetime is infinite."
}
] | 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. | [
"IPv6 WAN Link Addressing with NDRA",
"Dynamic Router Advertisement Configuration Overview"
] |
valid-lifetime | valid-lifetime seconds; | [edit logical-systems logical-system-name protocols router-advertisement interface interface-
name prefix prefix],
[edit protocols router-advertisement interface interface-name prefix prefix] | Specify how long the prefix remains valid for onlink determination. | [
{
"name": "seconds",
"desc": "Valid lifetime, in seconds. If you set the valid lifetime to 0xffffffff, the lifetime is infinite."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring IPv6 Interfaces and Enabling Neighbor Discovery"
] |
validation (Origin Validation for BGP) | validation {
traceoptions {
file filename <files number> <size size> <(world-readable | no-world-readable)>;
flag flag flag-modifier;
}
notification-rib test;
group group-name {
max-sessions number;
session server-ip-address {
traceoptions {
... | [edit logical-systems logical-system-name routing-instances instance-name routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances instance-name routing-options],
[edit routing-options] | 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": "notification-rib [ notification-rib ... ];",
"desc": "Specify the routing tables that are notified when the validation state changes. When validation policies are used for BGP peers in routing instances, the policy engine tries to lookup within the local Validated Route Payload (VRP) database of ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Use Case and Benefit of Origin Validation for BGP",
"Understanding Origin Validation for BGP",
"Example: Configuring Origin Validation for BGP"
] |
validity-period | validity-period days; | [edit security pki auto-re-enrollment certificate-id] | Certificate validity period, in days, from the enrollment start date. If not specified, the issuing certificate
authority (CA) sets this time as per its own policy. The start time is when auto-reenrollment is initiated. | [
{
"name": "days",
"desc": "Number of days that the certificate is valid."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring Auto-Reenrollment of a Router Certificate"
] |
variable (SNMP RMON) | variable oid-variable; | [edit snmp rmon alarm index] | Set the object identifier (OID) of the MIB object (also called variable) to be monitored when you
configure an SNMP RMON alarm. If the value of the monitored variable exceeds the configured rising
threshold or falling threshold, an alarm is triggered and a corresponding event may be generated. | [
{
"name": "oid-variable",
"desc": "OID of the MIB variable that is being monitored. The OID can be a dotted decimal (for"
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"RMON MIB Event, Alarm, Log, and History Control Tables",
"RMON Overview",
"Junos OS Network Management Configuration Guide"
] |
variables (Dynamic Service Profiles) | variables variable-name {
default-value default-value;
equals expression;
mandatory;
uid;
uid-reference;
} | [edit dynamic-profiles profile-name] | Configure user-defined variables in a dynamic service profile. The values that the system uses for these
variables are provided by the RADIUS server and applied when the subscriber authenticates. You can
configure default values that are used when RADIUS does not return a value. Alternatively, you can
specify that the ... | [
{
"name": "variable-name",
"desc": "Name of the variable."
}
] | 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. | [
"Dynamic Variables Overview",
"User-Defined Variables in Dynamic Profiles"
] |
variant | variant variant-number {
data-format format;
name-format format;
transfer {
record-level number;
timeout seconds;
}
} | [edit services flow-collector file-specification] | Configure a variant of the file format.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring File Formats"
] |
vbr rate | vbr rate; | [edit interfaces interface-name atm-options vpi vpi-identifier shaping] | For ATM encapsulation only, define a variable bit rate bandwidth utilization in the traffic-shaping profile. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Junos OS Release 9.5. | [
"Understanding Interfaces"
] |
vc-port | vc-port {
lag-hash (packet-based | source-port-based);
} | [edit virtual-chassis] | Enable hashing of link aggregation group (LAG) network traffic over a dedicated trunk port within a
Virtual Chassis, and select how the traffic within the dedicated trunk port is hashed.
BEST PRACTICE: Do not configure this statement unless you have a compelling reason
to configure it. Configuration of this statement i... | [
{
"name": "lag-hash",
"desc": "Select how to direct LAG traffic through the dedicated trunk port using either of the following"
},
{
"name": "options:",
"desc": ""
},
{
"name": "packet-based",
"desc": "Hashes all incoming LAG network traffic on the dedicated trunk port based on the p... | 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. | [] |
vci | vci vpi-identifier.vci-identifier; | [edit interfaces at-fpc/pic/port unit logical-unit-number],
[edit interfaces at-fpc/pic/port unit logical-unit-number family family address address
multipoint-destination address],
[edit logical-systems logical-system-name interfaces at-fpc/pic/port unit logical-unit-number],
[edit logical-systems logical-system-name ... | For ATM point-to-point logical interfaces only, configure the virtual circuit identifier (VCI) and virtual
path identifier (VPI).
To configure a VPI for a point-to-multipoint interface, specify the VPI in the multipoint-destination
statement.
VCIs 0 through 31 are reserved for specific ATM values designated by the ATM ... | [
{
"name": "vci-identifier",
"desc": "ATM virtual circuit identifier. Unless you configure the interface to use promiscuous"
},
{
"name": "vpi-identifier",
"desc": "ATM virtual path 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 a Point-to-Point ATM1 or ATM2 IQ Connection",
"Applying Scheduler Maps to Logical ATM Interfaces"
] |
vcp-no-hold-time | vcp-no-hold-time; | [edit virtual-chassis] | Disable the Virtual Chassis port (VCP) holddown timer for all VCPs in the Virtual Chassis or Virtual
Chassis Fabric (VCF).
The VCP holddown timer is an internal mechanism that delays a Virtual Chassis reconvergence for
several seconds when a VCP becomes inactive. The purpose of this delay is to provide the VCP time to
... | [] | 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. | [
"Understanding EX Series Virtual Chassis",
"Understanding QFX Series Virtual Chassis",
"Understanding Virtual Chassis Components"
] |
vcp-snmp-statistics | vcp-snmp-statistics; | [edit virtual-chassis] | Enable SNMP monitoring of the Virtual Chassis ports (VCPs) for all VCPs in the Virtual Chassis or Virtual
Chassis Fabric (VCF).
When this statement is enabled, SNMP gathers statistics on the Junos VCP MIBs. You can retrieve the
statistics gathered by SNMP for these MIBs by using the show snmp mib command with the walk ... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D40 and 15.1R5 only.
Statement deprecated in Junos OS Releases after 14.1X53 and 15.1. | [
"Understanding EX Series Virtual Chassis",
"Understanding QFX Series Virtual Chassis",
"Understanding Virtual Chassis Components"
] |
vdsl2-bytes | vdsl2-bytes bytes; | [edit protocols ancp qos-adjust] | 17.4R1
Starting in Junos OS Release 17.4R1, this statement is deprecated and replaced by the vdsl2-overhead-
bytes option of the access-line statement at the [edit system] hierarchy level. | [
{
"name": "bytes",
"desc": "Number of bytes added to or subtracted from the actual downstream frame overhead. Range: -100 through 100 bytes Default: 0 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.2.
Statement deprecated in Junos OS Release 17.4R1.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Neighbors and Operations"
] |
vdsl2-overhead-adjust | vdsl2-overhead-adjust percentage; | [edit protocols ancp qos-adjust] | 17.4R1
Starting in Junos OS Release 17.4R1, this statement is deprecated and replaced by the vdsl2-overhead-
adjust option of the access-line statement at the [edit system] hierarchy level. | [
{
"name": "percentage",
"desc": "Percentage by which to multiply the rate. Range: 80 through 100 percent Default: 100 percent"
}
] | 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 deprecated in Junos OS Release 17.4R1.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Neighbors and Operations"
] |
vdsl-bytes | vdsl-bytes bytes; | [edit protocols ancp qos-adjust] | 17.4R1
Starting in Junos OS Release 17.4R1, this statement is deprecated and replaced by the vdsl-overhead-
bytes option of the access-line statement at the [edit system] hierarchy level. | [
{
"name": "bytes",
"desc": "Number of bytes added to or subtracted from the actual downstream frame overhead. Range: -100 through 100 bytes Default: 0 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.2.
Statement deprecated in Junos OS Release 17.4R1.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Neighbors and Operations"
] |
vdsl-overhead-adjust | vdsl-overhead-adjust percentage; | [edit protocols ancp qos-adjust] | 17.4R1
Starting in Junos OS Release 17.4R1, this statement is deprecated and replaced by the vdsl-overhead-
adjust option of the access-line statement at the [edit system] hierarchy level. | [
{
"name": "percentage",
"desc": "Percentage by which to multiply the rate. Range: 80 through 100 percent Default: 100 percent"
}
] | 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 deprecated in Junos OS Release 17.4R1.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Neighbors and Operations"
] |
vdsl-profile | vdsl-profile | [edit interfaces interface-name vdsl-options] | Configure the type of VDSL2 profiles. A profile is a table that contains a list of preconfigured VDSL2
settings. | [
{
"name": "8a",
"desc": ""
},
{
"name": "8b",
"desc": ""
},
{
"name": "8c",
"desc": ""
},
{
"name": "8d",
"desc": ""
},
{
"name": "12a",
"desc": ""
},
{
"name": "12b",
"desc": ""
},
{
"name": "17a",
"desc": ""
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Junos OS Release 10.1. | [
"VDSL2 Interface Support on SRX Series Devices"
] |
vendor | vendor name {
product-name product-name;
} | [edit security idp dynamic-attack-group name filters] | A vendor has single or multiple products. An attack can be applicable to some of the products of
vendors. This filter can be used to group attacks specific to the product of a vendor. | [
{
"name": "name",
"desc": "Values for vendor field"
},
{
"name": "product-name",
"desc": "Values for product field"
}
] | security | Statement introduced in Junos OS Release 18.2R1. | [] |
vendor-id (AAA Profile) | vendor-id vendor-id; | [edit unified-edge aaa profiles aaa-profile-name radius policy activation-attribute],
[edit unified-edge aaa profiles aaa-profile-name radius policy deactivation-attribute] | Configure the vendor identification when a vendor-specific RADIUS attribute is used to carry the policy
and charging control (PCC) rulebase name for rulebase activations or deactivations. By default, the
rulebase name is carried in the ERX-Service-Activate Juniper vendor-specific attribute (VSA) for
activations and in ... | [
{
"name": "vendor-id",
"desc": "Vendor identification number for the RADIUS AVP."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring an AAA Profile",
"Understanding AAA Profiles",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules"
] |
vendor-id (DHCP Client) | vendor-id vendor-id; | [edit interfaces interface-name unit logical-unit-number family family dhcp-client] | Configure a vendor class ID for the Dynamic Host Configuration Protocol (DHCP) client. | [
{
"name": "vendor-id",
"desc": "Vendor class ID."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10.
Starting with Junos OS Release 17.3R1, on all SRX Series Firewalls and vSRX Virtual Firewall instances,
the CLI option dhcp-clinet at [edit interfaces interface-name unit logical-unit-number family inet] hierarchy is
changed to dhcp to keep consistent with other Jun... | [] |
vendor-id (dhcp-option82) | vendor-id <string>;
Hierarchy Level (For Platforms with Enhanced Layer 2 Software (ELS))
[edit vlans vlan-name forwarding-options dhcp-security option-82] | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security option-82] | Insert a vendor ID in the DHCP option 82 information in a DHCP request packet header before
forwarding or relaying the request to a DHCP server.
Default
If vendor-id is not explicitly configured for DHCP option 82, then no vendor ID is set. | [
{
"name": "string",
"desc": "(Optional) A single string that designates the vendor ID."
}
] | 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.
Hierarchy level [edit vlans vlan-name forwarding-options dhcp-security] introduced in Junos OS Release
13.2X50-D10. (See Using the Enhanced Layer 2 Software CLI for information about ELS.)
Hierarchy level [edit bridge-domains bridge-domain-name forwarding-options dhcp-secur... | [
"Configuring DHCP Option 82 on a Router with Bridge Domain",
"Example: Setting Up DHCP Option 82 Using the Same VLAN",
"Example: Setting Up DHCP Option 82 on a VLAN",
"Setting Up DHCP Option 82 on the Switch with No Relay (ELS)"
] |
vendor-id (Interfaces) | vendor-id vendor-id ; | [edit interfaces interface-name unit logical-unit-number family family-name dhcp] | Configure a vendor class ID for the Dynamic Host Configuration Protocol (DHCP) client. | [
{
"name": "vendor-id",
"desc": "vendor class 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. | [
"Understanding Interfaces"
] |
vendor-id (Unified Edge) | vendor-id vendor-id; | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from attribute name] | Specify the custom attribute’s AVP vendor identification number for the incoming RADIUS request from
the subscriber.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selected. | [
{
"name": "vendor-id",
"desc": "AVP vendor identification number. Range: 0 through 65,534."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
vendor-option | vendor-option {
(default-relay-server-group server-group-name | default-local-server-group local-server-
group-name | drop);
(equals | starts-with) (ascii match-string | hexadecimal match-hex) {
(drop | local-server-group local-server-group-name | relay-server-group server-group-
name);
}
} | [edit forwarding-options dhcp-relay relay-option-60],
[edit forwarding-options dhcp-relay group group-name relay-option-60],
[edit logical-systems logical-system-name forwarding-options dhcp-relay relay-option-60],
[edit logical-systems logical-system-name forwarding-options dhcp-relay group group-name relay-
option-60... | Configure the match criteria when you use the DHCP vendor class identifier option (option 60) in DHCP
client packets to forward client traffic to specific DHCP servers. The extended DHCP relay agent
compares the option 60 vendor-specific strings received in DHCP client packets against the match
criteria that you specif... | [
{
"name": "equals",
"desc": "Exact, left-to-right match of the ASCII or hexadecimal match string with the option 60 string."
},
{
"name": "starts-with",
"desc": "Partial match of the ASCII or hexadecimal match string with the option 60 string. The"
},
{
"name": "ascii match-string",
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in JUNOS Release 9.0. | [] |
vendor-specific (DHCP Relay Agent) | vendor-specific {
host-name;
location;
} | [edit forwarding-options dhcp-relay relay-option-82],
[edit forwarding-options dhcp-relay group group-name relay-option-82] | Add vendor-specific information to the option-82, suboption 9 field of DHCPv4 control messages on
server-facing interfaces. The vendor-specific information can be a hostname, a location (such as a
unique connection identifier), or both. The hostname can be a string of characters such as Juniper-AB-1.
The location shoul... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Junos OS Release 16.2. | [] |
vendor-support | vendor-support ibm; | [edit services lrf profile profile-name] | Configure support for any vendor-specific template types. Currently, the only vendor-specific template
type is ipflow-tcp-ts, for which you configure vendor-specific ibm.
If you do not configure vendor-specific ibm, a warning appears when you commit the configuration. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2.
Support for Next Gen Services introduced in Junos OS Release 19.3R1 on MX Series. | [
"Configuring an LRF Profile for Subscribers",
"Configuring Logging and Reporting for Junos OS Subscriber Aware",
"Configuring Logging and Reporting for Subscriber Management",
"Logging and Reporting Function for Subscribers"
] |
verify-path | verify-path {
destination-ip ip-address;
packet-size bytes;
} | [edit security ipsec vpn vpn-name vpn-monitor] | Verify the IPsec datapath before the secure tunnel (st0) interface is activated and route(s) associated
with the interface are installed in the Junos OS forwarding table. This configuration is useful in network
topologies where there is a transit firewall located between the VPN tunnel endpoints, and where IPsec
data t... | [
{
"name": "destination-ip",
"desc": ""
},
{
"name": "ip-address",
"desc": "Original, untranslated IP address of the peer tunnel endpoint that is behind a NAT device. This IP address must not be the NAT translated IP address. This option is required if the peer tunnel endpoint is behind a NAT dev... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D70.
packet-size option added in Junos OS Release 15.1X49-D120.
Support for verify-path option with IPsec VPN running IKED process is introduced in Junos OS Release
23.4R1. | [] |
version (BFD Liveness Detection) | version (1 | automatic); | [edit logical-systems name routing-instances name protocols (evpn | l2vpn | vpls) oam bfd-liveness-
detection],
[edit logical-systems name routing-instances name protocols (evpn | l2vpn | vpls) neighbor neighbor-
id oam bfd-liveness-detection],
[edit logical-systems name routing-instances name protocols (evpn | l2vpn |... | Specify the BFD version for detection. You can explicitly configure BFD version 1 or the routing device
can automatically detect the BFD version. By default, the routing device automatically detects the BFD
version. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1 | [
"Configuring BFD for Layer 2 VPN and VPLS",
"Example: Configuring BFD Authentication for BGP",
"Example: Configuring BFD on Internal BGP Peer Sessions",
"Understanding BFD Authentication for BGP"
] |
version (BFD) | version (0 | 1 | automatic); | [edit logical-systems logical-system-name protocols ldp oam bfd-liveness-detection],
[edit logical-systems logical-system-name protocols ldp oam fec address bfd-liveness-detection],
[edit system services dhcp-local-server liveness-detection method bfd],
[edit system services dhcp-local-server dhcpv6 liveness-detection ... | Configure the BFD protocol version to detect. | [
{
"name": "automatic",
"desc": "Autodetect the BFD protocol version. Default: automatic"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Example: Configuring Group Liveness Detection with BFD for DHCP Local Server Clients",
"Example: Configuring Global Liveness Detection with BFD for DHCP Relay Agent Clients",
"Configuring BFD for LDP LSPs"
] |
version (Dynamic IGMP Interface) | version version; | [edit dynamic-profiles profile-name protocols igmpinterface interface-name] | Specify the version of IGMP. | [
{
"name": "version",
"desc": "IGMP version number."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Dynamic IGMP Configuration Overview",
"Configuring Dynamic DHCP Client Access to a Multicast Network",
"Changing the IGMP Version"
] |
version (Dynamic MLD Interface) | version version; | [edit dynamic-profiles profile-name protocols mld interface interface-name] | Configure the MLD version explicitly on the dynamic interface. MLD version 2 (MLDv2) is used only to
support source-specific multicast (SSM). | [
{
"name": "version",
"desc": "MLD version to run on the interface."
}
] | routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Dynamic MLD Configuration Overview",
"Modifying the MLD Version"
] |
version (Flow Aggregation) | version format; | [edit forwarding-options accounting name output flow-server hostname],
[edit forwarding-options sampling instance instance-name family (inet |inet6 |mpls) output flow-server
hostname],
[edit forwarding-options sampling family (inet |inet6 |mpls) output flow-server hostname] | Specify the version format of the aggregated flows exported to a cflowd server. | [
{
"name": "format",
"desc": "Format of the flows."
}
] | 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 Flow Aggregation",
"Directing Traffic Sampling Output to a Server Running the cflowd Application"
] |
version (Flow Monitoring Logs for NAT) | version (ipfix | v9); | [edit services jflow-log template-profile template–profile-name] | Specify the flow template format, such as IPFIX or version 9, to be used for generating flow monitoring
records for NAT events and for transmitting them to the collector. | [
{
"name": "ipfix",
"desc": "Use the IPFIX flow template format for flow monitoring logs for NAT events."
},
{
"name": "v9",
"desc": "Use the version 9 flow template format for flow monitoring logs for NAT events."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding NAT Event Logging in Flow Monitoring Format on an MX Series Router or NFX250",
"Configuring Log Generation of NAT Events in Flow Monitoring Record Format on an MX Series",
"Router or NFX250",
"Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats",
"Exa... |
version (IGMP Snooping) | version version; | [edit bridge-domains bridge-domain-name protocols igmp-snooping],
[edit routing-instances routing-instance-name protocols igmp-snooping],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-
snooping],
[edit routing-instances routing-instance-name protocols igmp-snooping vlan ... | Specify the IGMP version for the IGMP general query that the snooping device sends to hosts when an
interface comes up or a new member is added to a VLAN or bridge domain. If the L2 querier is
configured for a VLAN/bridge-domain, periodic queries are sent to all members with the specified
version of IGMP-snooping.
To c... | [
{
"name": "version",
"desc": "IGMP version number."
}
] | 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 | [
"Configuring IGMP or MLD Snooping Version"
] |
version (IKE) | version ( 1 | 2); | [edit services ipsec-vpn ike policy policy-name] | Configure the Internet Key Exchange (IKE) version that is used to negotiate dynamic SAs for IPSec. | [
{
"name": "1",
"desc": "Uses IKEv1."
},
{
"name": "2",
"desc": "Uses IKEv2."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Configuring IKE Policies"
] |
version (Liveness Detection) | version (1 | automatic); | [edit protocols iccp peer liveness-detection] | Configure the Bidirectional Forwarding Detection (BFD) protocol version to detect. | [
{
"name": "automatic",
"desc": "Autodetect the BFD protocol version."
}
] | 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. | [] |
version (MLD Snooping) | version version; | [edit bridge-domains bridge-domain-name protocols mld-snooping],
[edit routing-instances routing-instance-name protocols mld-snooping],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols mld-
snooping],
[edit routing-instances routing-instance-name protocols mld-snooping vlan vlan... | Specify the MLD version for the MLD general query that the snooping device sends to hosts when an
interface comes up or a new member is added to a VLAN or bridge domain. If the L2 querier is
configured for a VLAN/bridge-domain, periodic queries are sent to all members with the specified
version of MLD-snooping.
To conf... | [
{
"name": "version",
"desc": "MLD version number."
}
] | 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 | [
"Configuring IGMP or MLD Snooping Version"
] |
version (Protocols BFD) | version (0 | 1 | automatic); | [edit protocols pim interface (Protocols PIM) interface-name bfd-liveness-detection],
[edit routing-instances routing-instance-name protocols pim interface (Protocols PIM) interface-
name bfd-liveness-detection] | Specify the bidirectional forwarding detection (BFD) protocol version that you want to detect. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Configuring BFD for PIM"
] |
version (Protocols IGMP AMT) | version version; | [edit logical-systems logical-system-name protocols igmp amt relay defaults],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols igmp
amt relay defaults],
[edit protocols igmp amt relay defaults],
[edit routing-instances routing-instance-name protocols igmp amt relay defaults] | Specify the version of IGMP used through an Automatic Multicast Tunneling (AMT) interface. | [
{
"name": "version",
"desc": "IGMP version number."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Default IGMP Parameters for AMT Interfaces"
] |
version (Protocols IGMP) | version version; | [edit logical-systems logical-system-name protocols igmp interface interface-name],
[edit protocols igmp interface interface-name],
[edit protocols igmp-snooping vlan (all | vlan-name)] | Specify the version of IGMP. | [
{
"name": "version",
"desc": "IGMP version number."
}
] | 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. | [
"Changing the IGMP Version"
] |
version (Protocols MLD) | version version; | [edit logical-systems logical-system-name protocols mld interface interface-name],
[edit protocols mld interface interface-name] | Configure the MLD version explicitly. MLD version 2 (MLDv2) is used only to support source-specific
multicast (SSM). | [
{
"name": "version",
"desc": "MLD version to run on the interface."
}
] | routing and trace—To view this statement in the configuration.
routing-control and trace-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Modifying the MLD Version"
] |
version (Protocols PIM) | version version; | [edit logical-systems logical-system-name protocols pim interface (Protocols PIM) interface-name],
[edit logical-systems logical-system-name protocols pim rp static address address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
interface (Protocols PIM) interface-name... | Starting in Junos OS Release 16.1, it is no longer necessary to specify a PIM version. PIMv1 is being
obsoleted so the version choice is moot. | [
{
"name": "version",
"desc": "PIM version number."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement deprecated (hidden) in Junos OS Release 16.1 for later removal. | [
"Enabling PIM Sparse Mode",
"Configuring PIM Dense Mode Properties",
"Configuring PIM Sparse-Dense Mode Properties"
] |
version (SNMP) | version (all | v1 | v2); | [edit snmp trap-group group-name] | Specify the version number of SNMP traps.
Default
all—Send an SNMPv1 and SNMPv2 trap for every trap condition. | [
{
"name": "all",
"desc": "Send an SNMPv1 and SNMPv2 trap for every trap condition."
},
{
"name": "v1",
"desc": "Send SNMPv1 traps only."
},
{
"name": "v2",
"desc": "Send SNMPv2 traps only."
}
] | 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. | [] |
version9 (Flow Monitoring) | version9 {
template template-name {
flow-active-timeout seconds;
flow-inactive-timeout seconds;
flow-key {
flow-direction;
vlan-id;
output-interface;
}
(ipv4-template | ipv6-template | mpls-template label-position [ positions ] | mpls-ipv4-... | [edit services flow-monitoring] | Specify the version 9 output template properties to support flow monitoring.
The remaining statements are explained separately. See CLI Explorer. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3.
Statement introduced in Junos OS Release 19.2R1 for MX Series routers with MPC10E-15C-MRATE
line card to define a flow record template suitable for IPv4 or IPv6 traffic only.
multi-bgp-path option added in Junos OS Release 24.2R1. | [
"Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9",
"Flow Templates",
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250"
] |
version9 (Forwarding Options) | version9 {
template template-name;
} | [edit forwarding-options sampling instance instance-name family (bridge | inet |inet6 |mpls vpls)
output flow-server hostname],
[edit forwarding-options sampling family (inet |inet6 |mpls| vpls |bridge) output flow-server
hostname] | Specify flow monitoring version 9 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 8.3.
Support at the following hierarchy levels introduced in Junos OS Release 18.2R1: [edit forwarding-options
sampling instance instance-name family bridge], [edit forwarding-options sampling instance instance-name family
vpls], [edit forwarding-options sampling family bridge],... | [
"Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9",
"Flow Templates"
] |
version-3 | version-3; | [edit protocols vrrp] | Enable Virtual Router Redundancy Protocol version 3 (VRRPv3).
NOTE:
•
Even though the version-3 statement can be configured only at the [edit protocols vrrp]
hierarchy level, VRRPv3 is enabled on all the configured logical systems as well.
•
When enabling VRRPv3, you must ensure that VRRPv3 is enabled on all the VRRP... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Junos OS Support for VRRPv3"
] |
version-alias (Dynamic Profiles) | version-alias version-alias-string; | [edit dynamic-profiles profile-name] | Configure an alias to identify a specific configuration variant of a base dynamic client profile. The version
alias is a text description that lets you decide how to name different profile variants, so they have an
identifier independent of the dynamic version name that is automatically created by the BNG.
The need for... | [
{
"name": "version-alias-string",
"desc": "String that identifies a particular version of a dynamic profile. The maximum size of the string is 64 bytes."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.2R1. | [
"Versioning for Dynamic Profiles"
] |
version-ipfix (Flow Monitoring) | version-ipfix {
template template-name {
data-record-fields {
include-policy-map-name;
source-prefix-as-path count;
destination-prefix-as-path count;
bgp-source-standard-community count;
bgp-destination-standard-community count;
bgp-... | [edit services flow-monitoring] | Specify the IPFIX output template properties to support flow monitoring.
The remaining statements are explained separately. See CLI Explorer. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2.
data-record-fields option introduced in Junos OS Evolved Release 21.4R1.
multi-bgp-path option added in Junos OS Release 24.2R1.
include-policy-map-name option added in Junos OS Evolved 24.4R1. | [
"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",
"Configuring Inline Active Flow Monitoring on PTX Series Routers"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.