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 |
|---|---|---|---|---|---|---|---|
unified-access-control (Services) | unified-access-control {
captive-portal redirect-policy-name{
redirect-traffic (all | unauthenticated);
redirect-url redirect-url;
}
certificate-verification [ optional | required | warning ];
infranet-contoller host-name {
address ip-address;
ca-profile [ca-profile];
... | [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... | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [] |
unified-access-policy (Protocols) | unified-access-policy {
interface name [inter-switch-link];
key key;
mac multicast-mac-address;
robust-count count;
source-mac source-mac-address;
} | [edit protocols] | Configure unified access policy. Unified access policy extends Group-Based Policy (GBP) support to Mist
access points (APs). This allows wireless clients to participate in GBP microsegmentation alongside wired
clients in a network. | [
{
"name": "interface",
"desc": "Name of the interface to enable for unified access policy. The named interface receives and transmits GBP messages from and to Mist APs."
},
{
"name": "interface inter-switch link",
"desc": "Configures the specified interface to be a unified access policy inter-sw... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [
"Microsegmentation Using Group-Based Policies"
] |
unified-policy max-lookups | unified-policy max-lookups max-lookups-number; | [edit logical-systems name security policies],
[edit logical-systems name tenants name security policies],
[edit security policies]
[edit tenants tenant-name security policies] | Configure maximum number of policy lookups, when micro-applications reach the transaction final
state, during the dynamic application classification process.
Application classification with micro-applications does not reach the final match state because the
micro-application keeps changing for the session. When the mic... | [] | flow-tap | Statement introduced in Junos OS Release 19.2R1. | [
"Unified Security Policies"
] |
unified-policy-explicit-match | unified-policy-explicit-match; | [edit security policies] | Enable explicit match in a unified policy.
•
In a unified policy, when you enable explicit match, the session is dropped if a dependent application
does not have any matching policy.
•
In a unified policy, when explicit match is not configured, then implicit match is applied. That is, if the
dependent application does... | [] | security— To view this statement in the configuration.
security-control— To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Unified Security Policies"
] |
unique-nas-port (Access) | unique-nas-port {
chassis-id chassis-id;
chassis-id-width chassis-id-width;
} | [edit access radius-options] | Configure the router to provide a unique value for the NAS-Port attribute (RADIUS attribute 5) of each
subscriber. You can configure a NAS-Port value that is unique within the router only, or unique across
the different MX routers in the network. | [
{
"name": "chassis-id",
"desc": "Value for the chassis-id part of NAS-Port attribute. To ensure that NAS-Port values are unique across all MX series routers in the network, you must specify a unique chassis-id for each MX router. Range: 0-127 bits"
},
{
"name": "chassis-id-width",
"desc": "Numb... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"RADIUS NAS Port Attributes and Options",
"RADIUS Servers and Parameters for Subscriber Access"
] |
unit (Aggregated Multiservices) | unit interface-unit-number {
family family;
} | [edit interfaces interface-name] | Configure the logical interface on the physical device. You must configure a logical interface to be able to
use the physical device.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "interface-unit-number",
"desc": "Number of the logical unit."
}
] | 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. | [
"Understanding Aggregated Multiservices Interfaces",
"Example: Configuring an Aggregated Multiservices Interface (AMS)"
] |
unit (CoS Interfaces) | unit logical-unit-number {
classifiers {
type (classifier-name | default) family (mpls | all);
}
forwarding-class class-name;
fragmentation-map map-name;
input-traffic-control-profile profile-name shared-instance instance-name;
output-traffic-control-profile profile-name shared-instance ... | [edit class-of-service interfaces interface-name] | Configure class of service properties on a logical interface on a physical port.
NOTE: Available options can vary by platform and software release (Junos OS or Junos
OS Evolved). Use Feature Explorer to confirm platform and release support for specific
features. | [
{
"name": "logical-unit-number",
"desc": "Number of the logical unit."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Understanding How Behavior Aggregate Classifiers Prioritize Trusted Traffic",
"Configuring Rewrite Rules",
"Assigning CoS Components to Interfaces"
] |
unit (CoS Interfaces) | unit logical-unit-number {
classifiers {
(dscp | dscp-ipv6 | ieee-802.1 | exp) (classifier-name | default);
}
forwarding-class class-name;
rewrite-rules {
(dscp | dscp-ipv6 | ieee-802.1 | exp) (classifier-name | default);
}
} | [edit class-of-service interfaces interface-name] | Configure a logical interface on the physical device. You must configure a logical interface to use the
physical device. | [
{
"name": "logical-unit-number",
"desc": "Number of the logical unit."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Assigning CoS Components to Interfaces"
] |
unit (Dynamic Demux Interface) | unit logical-unit-number {
demux-options {
underlying-interface interface-name
}
family family {
access-concentrator name;
address address;
demux-source {
source-address;
}
direct-connect;
duplicate-protection;
dynamic-profile prof... | [edit dynamic-profiles profile-name interfaces demux0] | Configure a dynamic logical interface on the physical device. You must configure a logical interface to be
able to use the physical device. | [
{
"name": "logical-unit-number",
"desc": "Either the specific unit number of the interface or the unit number variable ($junos-interface-unit). The variable is used to specify the unit of the interface when a new demux interface is"
}
] | 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 Dynamic Subscriber Interfaces Using IP Demux Interfaces in Dynamic Profiles"
] |
unit (Dynamic Interface Sets) | unit logical-unit-number {
advisory-options {
downstream-rate rate;
upstream-rate rate;
}
} | [edit dynamic-profiles profile-name interfaces interface-set interface-set-name interface interface-
name] | Apply the logical interface unit to the interface set. | [
{
"name": "logical-unit-number",
"desc": "One of the following options:"
},
{
"name": "$junos-underlying-interface-unit",
"desc": "For static VLANs, the unit number variable. The static unit number"
},
{
"name": "$junos-interface-unit",
"desc": "For dynamic demux and dynamic PPPoE in... | 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 Dynamic VLAN Subscriber Interfaces Based on Agent Circuit Identifier Information",
"Applying Traffic Shaping and Scheduling to a Subscriber Interface in a Dynamic Profile",
"Configuring an Interface Set of Subscribers in a Dynamic Profile",
"Agent Circuit Identifier-Based Dynamic VLANs Overview",... |
unit (Dynamic PPPoE) | unit logical-unit-number {
keepalives interval seconds;
no-keepalives;
pppoe-options {
underlying-interface interface-name;
server;
}
ppp-options {
aaa-options aaa-options-name;
authentication [ authentication-protocols ];
mru size;
mtu (size | use-low... | [edit dynamic-profiles profile-name interfaces pp0] | In a dynamic profile, configure a logical unit number for the dynamic PPPoE logical interface. You must
configure a logical interface to be able to use the router. | [
{
"name": "logical-unit-number",
"desc": "Variable used to specify the unit number when the PPPoE logical interface is"
}
] | 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. | [
"Configuring a PPPoE Dynamic Profile",
"Dynamic PPPoE Subscriber Interfaces over Static Underlying Interfaces Overview"
] |
unit (Dynamic Profiles Standard Interface) | unit logical-unit-number {
actual-transit-statistics;
auto-configure {
agent-circuit-identifier {
dynamic-profile profile-name;
}
line-identity {
includes {
accept-no-ids {
mac-address;
}
circuit-id;... | [edit dynamic-profiles profile-name interfaces interface-name] | Configure a logical interface on the physical device. You must configure a logical interface to be able to
use the physical device. | [
{
"name": "logical-unit-number",
"desc": "The specific unit number of the interface you want to assign to the dynamic"
},
{
"name": "$junos-underlying-interface-unit",
"desc": "For static VLANs, the unit number variable. The static unit number"
},
{
"name": "$junos-interface-unit",
"... | 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 Dynamic Underlying VLAN Interfaces to Use Agent Circuit Identifier Information",
"Configuring Static Underlying VLAN Interfaces to Use Agent Circuit Identifier Information",
"Agent Circuit Identifier-Based Dynamic VLANs Overview"
] |
unit (Dynamic Traffic Shaping) | unit logical-unit-number {
classifiers {
type (classifier-name | default);
}
output-traffic-control-profile (profile-name | $junos-cos-traffic-control-profile);
report-ingress-shaping-rate bps;
rewrite-rules {
dscp (rewrite-name | default);
dscp-ipv6 (rewrite-name | default);... | [edit dynamic-profiles profile-name class-of-service interfaces interface-name],
[edit dynamic-profiles profile-name interfaces interface-set interface-set-name interface interface-
name] | Configure a logical interface on the physical device. You must configure a logical interface to be able to
use the physical device. | [
{
"name": "logical-unit-number",
"desc": "One of the following options:"
},
{
"name": "$junos-underlying-interface-unit",
"desc": "For static VLANs, the unit number variable. The static unit number"
},
{
"name": "$junos-interface-unit",
"desc": "For dynamic demux and dynamic PPPoE in... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Support at the [edit dynamic-profiles profile-name class-of-service interfaces interface-set interface-set-name]
hierarchy level introduced in Junos OS Release 10.4. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Applying Traffic Shaping and Scheduling to a Subscriber Interface in a Dynamic Profile",
"Configuring an Interface Set of Subscribers in a Dynamic Profile"
] |
unit (Interfaces Services) | unit logical-unit-number {
family inet {
address address {
}
service {
input {
[ service-set service-set-name <service-filter filter-name> ];
post-service-filter filter-name;
}
output {
[ service-set service-... | [edit interfaces interface-name ] | Configure a logical interface on the physical device. You must configure a logical interface to be able to
use the physical device. | [
{
"name": "logical-unit-number",
"desc": "Number of the logical unit."
}
] | 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. | [
"Junos OS Network Interfaces Library for Routing Devices"
] |
unit (interfaces) | unit logical-unit-number {
accept-source-mac {
mac-address mac-address {
policer {
input cos-policer-name;
output cos-policer-name;
}
}
}
accounting-profile name;
advisory-options {
downstream-rate rate;
upstream-rat... | [edit interfaces interface-name],
[edit logical-systems logical-system-name interfaces interface-name],
[edit interfaces interface-set interface-set-name interface interface-name] | Configure a logical interface on the physical device. You must configure a logical interface to be able to
use the physical device. | [
{
"name": "logical-unit-number",
"desc": "Number of the logical unit. Range: 0 through 1,073,741,823 for demux, PPPoE, and pseudowire static interfaces. 0 through 16,385 for all other static interface types."
},
{
"name": "interface-tag",
"desc": ""
},
{
"name": "name",
"desc": "(Jun... | 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.
Range increased for static pseudowire interfaces to 1,073,741,823 in Junos OS Release 18.3R1. | [
"Configuring Logical Interface Properties",
"Junos OS Services Interfaces Library for Routing Devices"
] |
unit (Interfaces) | unit logical-unit-number {
family inet {
ipsec-sa sa-name;
}
tunnel {
backup-destination destination-address;
destination destination-address;
routing-instance {
destination routing-instance-name;
}
source source-address;
ttl number;
}
... | [edit interfaces interface-name] | Configure a logical interface on the physical device. You must configure a logical interface to be able to
use the physical device. | [
{
"name": "logical-unit-number",
"desc": "Number of the logical unit."
}
] | 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 Encryption Interfaces",
"Junos OS Network Interfaces Library for Routing Devices",
"Junos OS Network Interfaces Library for Routing Devices"
] |
unit (Link-Multilink) | unit logical-unit-number {
disable-mlppp-inner-ppp-pfc;
dlci dlci-identifier;
drop-timeout milliseconds;
encapsulation type;
fragment-threshold bytes;
interleave-fragments;
minimum-links number;
mrru bytes;
multicast-dlci dlci-identifier;
short-sequence;
family family {
... | [edit interfaces interface-name] | Configure a logical interface on the physical device. You must configure a logical interface to be able to
use the physical device. | [
{
"name": "logical-unit-number",
"desc": "Number of the logical unit."
}
] | 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. | [
"Link and Multilink Services Interfaces User Guide for Routing Devices",
"Junos OS Network Interfaces Library for Routing Devices"
] |
unit (QFX Series) | The ethernet-switching and fibre-channel statements and all of their substatements are not supported on
OCX Series switches.
unit logical-unit-number {
family {
ethernet-switching {
filter input filter-name;
filter output filter-name;
native-vlan-id vlan-id;
... | [edit interfaces interface-name],
[edit interfaces interface-range interface-range-name] | NOTE: The ethernet-switching and fibre-channel statements and all of their substatements
are not supported on OCX Series switches.
Configure a logical interface on the physical device. You must configure a logical interface to be able to
use the physical device.
Default
You must configure a logical interface to be able... | [
{
"name": "logical-unit-number",
"desc": "Number of the logical unit."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring Gigabit and 10-Gigabit Ethernet Interfaces for EX4600 and QFX Series Switches",
"Configuring Link Aggregation",
"Junos OS Network Interfaces Library for Routing Devices"
] |
unit (Sampling) | unit logical-unit-number {
family inet {
address address {
destination destination-address;
}
filter {
group filter-group-number;
input filter-name;
output filter-name;
}
sampling direction;
}
} | [edit interfaces interface-name] | Configure a logical interface on the physical device. You must configure a logical interface to be able to
use the physical device. | [
{
"name": "logical-unit-number",
"desc": "Number of the logical unit."
}
] | 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. | [
"Monitoring, Sampling, and Collection Services Interfaces User Guide"
] |
unit (TDF Interface) | unit interface-unit-number {
family family-name;
} | [edit interfaces mif] | Configure the logical interface on the TDF interface. You must configure a logical interface to be able to
use the TDF interface. | [
{
"name": "interface-unit-number",
"desc": "Number of the logical unit. Range: 0 through 16,384 The remaining statement is explained separately. See CLI Explorer."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring a TDF Logical Interface"
] |
unit (Tunnel) | unit logical-unit-number {
peer-unit unit-number;
reassemble-packets;
tunnel {
allow-fragmentation;
backup-destination address;
destination destination-address;
do-not-fragment;
key number;
routing-instance {
destination routing-instance-name;
... | [edit interfaces interface-name],
[edit logical-systems logical-system-name interfaces interface-name] | Configure a logical interface on the physical device. You must configure a logical interface to be able to
use the physical device. | [
{
"name": "logical-unit-number",
"desc": "Number of the logical unit."
}
] | 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. | [
"Junos OS Network Interfaces Library for Routing Devices"
] |
unit (Voice Services) | unit logical-unit-number {
compression {
rtp {
f-max-period number;
maximum-contexts number <force>;
port {
minimum port-number;
maximum port-number;
}
queues [ queue-numbers ];
}
}
compression-device... | [edit interfaces interface-name ] | Configure a logical interface on the physical device. You must configure a logical interface to be able to
use the physical device. | [
{
"name": "logical-unit-number",
"desc": "Number of the logical unit."
}
] | 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. | [
"Junos OS Network Interfaces Library for Routing Devices",
"Configuring Services Interfaces for Voice Services"
] |
unknown-message (Security H323 ALG) | unknown-message {
permit-nat-applied;
permit-routed;
} | [edit logical-systems name security alg h323 application-screen],
[edit logical-systems name tenants name security alg h323 application-screen],
[edit security alg h323 application-screen],
[edit services alg h323 application-screen],
[edit tenants name security alg h323 application-screen] | Specify how the SRX Series Firewall handles the unidentified H.323 messages. By default, SRX Series
Firewall drops unknown messages. Permitting unknown messages can compromise security and is not
recommended. However, in a secure test or production environment, this statement is useful to resolve
interoperability issue... | [
{
"name": "permit-nat-applied",
"desc": "Permits unknown messages to pass if the session is in NAT mode."
},
{
"name": "permit-routed",
"desc": "Permit unknown messages on routed packets. Sessions in Transparent mode are treated"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
unknown-message (Security MGCP ALG) | unknown-message {
permit-nat-applied;
permit-routed;
} | [edit logical-systems name security alg mgcp application-screen],
[edit logical-systems name tenants name security alg mgcp application-screen],
[edit security alg mgcp application-screen],
[edit services alg mgcp application-screen],
[edit tenants name security alg mgcp application-screen] | Specify how SRX Series Firewall handles unidentified Media Gateway Control Protocol (MGCP)
messages. The default is to drop unknown (unsupported) messages. Permitting unknown messages can
compromise security and is not recommended. However, in a secure test or production environment,
this statement is useful to resolve... | [
{
"name": "permit-nat-applied",
"desc": "Permits unknown messages to pass if the session is in NAT mode."
},
{
"name": "permit-routed",
"desc": "Permit unknown messages on routed packets. Sessions in Transparent mode are treated"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
unknown-message (Security SCCP ALG) | unknown-message {
permit-nat-applied;
permit-routed;
} | [edit logical-systems name security alg sccp application-screen],
[edit logical-systems name tenants name security alg sccp application-screen],
[edit security alg sccp application-screen],
[edit services alg sccp application-screen],
[edit tenants name security alg sccp application-screen] | Specify how SRX Series Firewall handles unidentified Skinny Client Control Protocol (SCCP) messages.
The default is to drop unknown (unsupported) messages. Permitting unknown messages can
compromise security and is not recommended. However, in a secure test or production environment,
this statement is useful to resolve... | [
{
"name": "permit-nat-applied",
"desc": "Permits unknown messages to pass if the session is in NAT mode."
},
{
"name": "permit-routed",
"desc": "Permit unknown messages on routed packets. Sessions in Transparent mode are treated"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
unknown-message (Security SIP ALG) | unknown-message {
permit-nat-applied;
permit-routed;
} | [edit logical-systems name security alg sip (Security) application-screen (Security SIP)],
[edit logical-systems name tenants name security alg sip (Security) application-screen (Security
SIP)],
[edit security alg sip (Security) application-screen (Security SIP)],
[edit services alg sip (Security) application-scree... | Specify how SRX Series Firewall handles unidentified Session Initiation Protocol (SIP) messages. The
default is to drop unknown (unsupported) messages. Permitting unknown messages can compromise
security and is not recommended. However, in a secure test or production environment, this statement
is useful for resolving ... | [
{
"name": "permit-nat-applied",
"desc": "Permits unknown messages to pass if the session is in NAT mode."
},
{
"name": "permit-routed",
"desc": "Permit unknown messages on routed packets. Sessions in Transparent mode are treated"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
unknown-protocol (IDS Screen Next Gen Services) | unknown-protocol; | [edit services screen ids-option screen-name ip] | Identify and drop IP frames with protocol numbers greater than 137 for IPv4 and 139 for IPv6, which
protects against IP unknown protocol attacks. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
unknown-unicast-forwarding | unknown-unicast-forwarding {
vlan (all | vlan-name){
interface interface-name;
}
} | [edit ethernet-switching-options],
[edit switch-options] | Configure the switch to forward all unknown unicast packets in a VLAN or on all VLANs to a particular
interface.
NOTE: Before you can configure unknown unicast forwarding within a VLAN, you must
first configure that VLAN.
The remaining statements are explained separately. See CLI Explorer.
Default
Unknown unicast packe... | [] | 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. | [] |
unnumbered-address (Demux) | unnumbered-address interface-name <preferred-source-address address>; | [edit interfaces interface-name unit logical-unit-number family inet],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family
inet] | For IP demultiplexing interfaces, enable the local address to be derived from the specified interface.
Configuring an unnumbered interface enables IP processing on the interface without assigning an
explicit IP address to the interface. | [
{
"name": "interface-name",
"desc": "Name of the interface from which the local address is derived. The specified interface"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2.
preferred-source-address option introduced in Junos OS Release 9.0.
IP demultiplexing interfaces supported in Junos OS Release 9.2. | [
"Configuring an Unnumbered Interface"
] |
unnumbered-address (Dynamic PPPoE) | unnumbered-address interface-name; | [edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit family family] | For dynamic PPPoE interfaces, enable the local address to be derived from the specified interface.
Configuring unnumbered Ethernet interfaces enables IP processing on the interface without assigning an
explicit IP address to the interface. | [
{
"name": "interface-name",
"desc": "Interface from which the local address is derived. The interface name must include a"
}
] | 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. | [
"Configuring a PPPoE Dynamic Profile",
"Dynamic PPPoE Subscriber Interfaces over Static Underlying Interfaces Overview"
] |
unnumbered-address (Dynamic Profiles) | unnumbered-address interface-name <preferred-source-address address>; | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family],
[edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family family] | For Ethernet interfaces, enable the local address to be derived from the specified interface. Configuring
unnumbered Ethernet interfaces enables IP processing on the interface without assigning an explicit IP
address to the interface. To configure unnumbered address dynamically, include the $junos-loopback-
interface-a... | [
{
"name": "interface-name",
"desc": "Name of the interface from which the local address is derived. The specified interface must have a logical unit number, a configured IP address, and must not be an unnumbered interface. This value can be a specific interface name or the $junos-loopback-interface predefin... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2.
Support for the $junos-preferred-source-address and $junos-preferred-source-ipv6-address predefined variables
introduced in Junos OS Release 9.6.
Support for the $junos-loopback-interface predefined variable introduced in Junos OS Release 9.6. | [
"Dynamic Profiles Overview"
] |
unnumbered-address (Ethernet) | unnumbered-address interface-name <preferred-source-address address>; | [edit interfaces interface-name unit logical-unit-number family family],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family
family] | For Ethernet interfaces, enable the local address to be derived from the specified interface. Configuring
an unnumbered Ethernet interface enables IP processing on the interface without assigning an explicit
IP address to the interface. | [
{
"name": "interface-name",
"desc": "Name of the interface from which the local address is derived. The specified interface"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2.
preferred-source-address option introduced in Junos OS Release 9.0. | [
"Configuring an Unnumbered Interfaceaddress",
"address",
"Overview for Junos OS"
] |
unnumbered-address (PPP) | unnumbered-address interface-name destination address destination-profile profile-name; | [edit interfaces interface-name unit logical-unit-number family inet],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet] | For interfaces with PPP encapsulation, enable the local address to be derived from the specified
interface. | [
{
"name": "interface-name",
"desc": "Interface from which the local address is derived. The interface name must include a"
}
] | 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 IPCP Options for Interfaces with PPP Encapsulation"
] |
unprotect | unprotect (hierarchy | statement | identifier) | Unprotect a protected hierarchy, configuration statement, or an identifier, so that it can be modified or
deleted. | [
{
"name": "hierarchy",
"desc": "(Optional) Unprotect a specific protected hierarchy."
},
{
"name": "statement",
"desc": "(Optional) Unprotect a specific protected statement."
},
{
"name": "identifier",
"desc": "(Optional) Unprotect a specific protected identifier."
}
] | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy. | Command introduced in Junos OS Release 11.2. | [
"Displaying the Current Configuration",
"Example: Protecting the Configuration from Modification or Deletion"
] | |
unreachable-vtep-aging-timer | unreachable-vtep-aging-timer [300–1800]; | [edit vlans vlan-name vxlan] | Configure the system to age out the address for the remote virtual tunnel endpoint (VTEP) if all the
MAC addresses learned from that VTEP age out. The address for the remote VTEP expires the
configured number of seconds after the last learned media access control (MAC) address expires. | [] | 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"
] |
untagged | untagged; | [edit interfaces ps0] | Specify that the router supports untagged traffic on pseudowire subscriber interfaces. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1. | [
"MPLS Pseudowire Subscriber Logical Interfaces"
] |
untrusted (VLAN) | untrusted; | [edit vlans vlan-name forwarding-options dhcp-security group group-name overrides] | Configure a trunk interface as untrusted for DHCP security. Trunk interfaces are trusted by default and
all packets are allowed. You can override this default behavior and set a trunk interface as untrusted in
order to support DHCP security features on the interface. DHCP snooping, DHCPv6 snooping, dynamic
ARP inspecti... | [] | 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. | [
"Understanding and Using Trusted DHCP Servers",
"Configuring a Trunk Interface as Untrusted for DHCP Security (CLI Procedure)"
] |
untrusted | untrusted; | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security group group-name overrides] | Allow DHCP responses from the specified interface. | [] | 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. | [
"Enabling a Trusted DHCP Server (MX Series Routers)",
"Understanding and Using Trusted DHCP Servers"
] |
Unused | unused; | [edit chassis fpc slot-number pic pic-number port port-number]
[edit interface interface-name] | (PTX10003-80C and PTX10003-160C routers) While setting port 0 to 400-Gigabit Ethernet mode
(using QSFP56-DD-400GBASE-LR8 optics), the total bandwidth (speed x number-of-subports) of port 1 has
to be less than 100G and port 2 has to configured as 'unused'. When using port 4 as 400G, port 3 has to
be configured with tota... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 19.3R1.
Hierarchy introduced in Junos OS Evolved Release 20.1R1 for JNP10K-LC1201 line card on PTX10008
routers. | [
"PTX10003 Port Panel",
"Port Speed on PTX10003"
] |
up | up <number> <configuration-command> | Move up one level in the statement hierarchy. | [
{
"name": "none",
"desc": "Move up one level in the configuration hierarchy."
},
{
"name": "configuration-command",
"desc": "(Optional) Issue configuration mode commands from a location higher in the hierarchy."
},
{
"name": "number",
"desc": "(Optional) Move up the specified number ... | configure—To enter configuration mode. | Command introduced before Junos OS Release 7.4. | [
"Displaying the Current Configuration"
] | |
update | update | Update private candidate configuration with a copy of the most recently committed configuration,
including your private changes.
NOTE: The update command is available only when you are in configure private mode. | [] | configure—To enter configuration mode. | Command introduced in Junos OS Release 7.5. | [
"Updating the configure private Configuration"
] | |
update-interval (Protocols RIP) | update-interval seconds; | [edit logical-systems logical-system-name protocols rip],
[edit logical-systems logical-system-name protocols rip group group-name],
[edit logical-systems logical-system-name protocols rip group group-name neighbor neighbor-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protoco... | Configure the interval at which routes learned by RIP are sent to neighbors. This timer controls the
interval between routing updates. This timer is set to 30 seconds, by default, with a small random
amount of time added when the timer is reset. This added time prevents congestion that can happen if
all routing devices... | [
{
"name": "seconds",
"desc": "Estimated time to wait before making updates to the routing table."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Example: Configuring RIP Timers"
] |
update-interval (Protocols RIPng) | update-interval seconds; | [edit logical-systems logical-system-name protocols ripng],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ripng],
[edit protocols ripng],
[edit routing-instances routing-instance-name protocols ripng] | Configure the interval at which routes learned by RIPng are sent to neighbors. | [
{
"name": "seconds",
"desc": "Estimated time to wait before making updates to the routing table."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6.
Support for routing instances introduced in Junos OS Release 9.0. | [
"Example: Configuring RIP Timers"
] |
update-interval (Service Accounting) | update-interval minutes; | [edit access profile profile-name service accounting] | Enable service interim accounting updates and configure the amount of time that the router waits
before sending a new service accounting update.
NOTE: An update interval value configured in the RADIUS attribute, Service-Interim-
Acct-Interval (VSA 26-140), takes precedence over the value configured with this
statement.... | [
{
"name": "minutes",
"desc": "Amount of time between updates, in minutes. All values are rounded up to the next higher"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R1. | [
"RADIUS Accounting for Subscriber Access",
"RADIUS Accounting for Subscriber Access",
"RADIUS Accounting for Subscriber Access",
"Configuring Service Accounting in Local Flat Files"
] |
update-interval | update-interval minutes; | [edit access profile profile-name accounting] | Enable interim accounting updates and configure the amount of time that the router or switch waits
before sending a new accounting update.
Interim accounting updates are included in the exchange of messages between the client and the
accounting server. In RADIUS accounting, the client is the network access server (NAS)... | [
{
"name": "minutes",
"desc": "Amount of time between updates, in minutes. All values are rounded to the next higher multiple"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1. | [
"RADIUS Servers and Parameters for Subscriber Access",
"ANCP Agent and AAA"
] |
update-rate-limit | update-rate-limit updates-per-minute; | [edit protocols pcep] | Specify the number of updates per minute that the Path Computation Client (PCC) can receive at
maximum. Updates above this limit are ignored by the PCC. | [
{
"name": "updates-per-minute",
"desc": "Number of updates per minute that the PCC can receive at maximum. Range: 1 through 16384 Default: 0 (disabled or no limit)"
}
] | 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.
Support for PTX Series added in Junos OS Release 14.2.
Support for QFX Series switches added in Junos OS Release 16.1R3.
Support for ACX Series added in Junos OS Release 17.1R1. | [] |
update-response-timeout (PCRF Partition) | update-response-timeout seconds; | [edit access pcrf partition partition-name] | Configure the amount of time in seconds before a Policy and Charging Rule Function (PCRF) partition
stops attempting to send an updated rule report response using a CCR-GX-U message. Use this
statement if you added or deleted rules in either the subscriber login using a CCA-GX-I message, or the
reauthorization request ... | [
{
"name": "seconds",
"desc": "Number of seconds to wait before a PCRF partition stops attempting to send an updated rule report response using a CCR-GX-U message. Default: 300 Range: 0 through 86,400 seconds (24 hours)"
}
] | 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",
... |
update-router-advertisement | update-router-advertisement (interface interface-name); | [edit interfaces interface-name unit logical-unit-number family family dhcpv6-client]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet6 dhcpv6-client]
[edit tenants tenant-name interfaces interface-name unit logical-unit-number family inet6 dhcpv6-
client] | Specify the interface used to delegate prefixes. | [
{
"name": "interface interface-name",
"desc": "Interface on which to delegate prefixes"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10.
The logical-systems and tenant options are introduced in Junos OS Release 18.4R1. | [] |
update-server (dhcp-client) | update-server; | [edit interfaces interface-name unit logical-unit-number family family dhcp-client] | Propagate DHCP options to a local DHCP server. | [] | 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... | [] |
update-server (dhcpv6-client) | update-server; | [edit interfaces interface-name unit logical-unit-number family family dhcpv6-client] | Propagate TCP/IP settings to the DHCPv6 server. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10. | [] |
update-server | update-server; | [edit interfaces interface-name unit logical-unit-number family inet dhcp] | Propagate TCP/IP settings learned from an external DHCP server to the DHCP server running on the
switch, router, or device. | [] | 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. | [
"Configuring a DHCP Client",
"Example: Configuring the Device as a DHCP Client",
"unit",
"family"
] |
update-threading | update-threading {
number-of-threads;
group-split-size;
}
} | [edit system processes routing bgp] | Enables BGP update thread. If you configure update-threading on a Routing Engine, RPD creates update
threads.
NOTE:
•
Sharding requires Update/IO thread. If rib-sharding is configured and update-threading is
not configured, the commit check fails.
•
RPD would restart automatically when rib-sharding or update-threadin... | [
{
"name": "number of",
"desc": ""
},
{
"name": "threads",
"desc": ""
},
{
"name": "number of threads",
"desc": "the number of update threads created. If you configure update-threading"
},
{
"name": "group-split-size",
"desc": ""
},
{
"name": "group-split-size",
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4R1.
group-split-size statement introduced in Junos OS Release 21.4R1.
Support for NSR with sharding introduced in Junos OS Release 22.2. | [] |
update-threshold | update-threshold {
threshold-percent;
adaptive
threshold-value threshold-value;
} | [edit logical-systems logical-system-name protocols rsvp interface interface-name],
[edit protocols rsvp interface interface-name] | Adjust the threshold at which a change in bandwidth triggers an interior gateway protocol (IGP) update. | [
{
"name": "threshold-percent",
"desc": "Specify the percentage change in reserved bandwidth to trigger IGP update. Default: 10 percent Range: 0.001 through 20 percent"
},
{
"name": "threshold-value",
"desc": ""
},
{
"name": "threshold-value",
"desc": "Specify the change in reserved... | 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.
threshold-value option introduced in Junos OS Release 19.4R1 on all platforms. | [
"Configuring the RSVP Update Threshold on an Interface"
] |
update-threshold-max-reservable | update-threshold-max-reservable update-threshold-max-reservable; | [edit logical-systems name protocols rsvp interface],
[edit logical-systems name routing-instances name protocols rsvp interface],
[edit protocols rsvp interface],
[edit routing-instances name protocols rsvp interface] | Configure a threshold in bits per second. When SPRING bandwidth utilization exceeds this threshold,
Resource Reservation Protocol (RSVP) reports this event to IGP and preempts the labeled switched
paths (LSPs). If this threshold is not exceeded, RSVP does not make any changes to the bandwidth
allocation.
However, if t... | [
{
"name": "update-threshold-max-",
"desc": ""
},
{
"name": "reservable",
"desc": "Specify a threshold value for maximum SPRING bandwidth utilization in bits per second. Range: 0 through 100000"
},
{
"name": "percent percent",
"desc": "Specify a bandwidth utilization change threshold... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R1.
percent option introduced in Junos OS Release 17.4R1 for MX Series and PTX Series. | [] |
upgrade-group | upgrade-group group-name {
fpcs (slot-number | [list-of-slot-numbers]);
member member-id {
fpcs (slot-number | [list-of-slot-numbers]);
}
} | [edit chassis nssu] | Assign a name to a line-card upgrade group being created for nonstop software upgrade (NSSU).
To reduce the time an NSSU takes, you can configure line-card upgrade groups on an EX6200 or
EX8200 switch with redundant Routing Engines; EX8200 Virtual Chassis; EX4650 Virtual Chassis;
QFX3500, QFX3600, and QFX5100 Virtual C... | [
{
"name": "group-name",
"desc": "Name of the upgrade group."
}
] | 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 Line-Card Upgrade Groups for Nonstop Software Upgrade",
"Example: Configuring Line-Card Upgrade Groups for Nonstop Software Upgrade on EX Series",
"Switches",
"Upgrading Software on a Virtual Chassis Fabric Using Nonstop Software Upgrade"
] |
upgrade-groups (Junos Fusion) | upgrade-groups upgrade-group-name {
satellite [slot-id | range | all];
} | [edit chassis satellite-management] | Create and name a satellite software upgrade group for a Junos Fusion, or specify an existing satellite
software upgrade group to configure.
A satellite software upgrade group is a group of satellite devices that are designated to upgrade to the
same satellite software version using the same satellite software package.... | [
{
"name": "upgrade-group-name",
"desc": "Specifies the user-defined name for the satellite software upgrade group. The remaining statements are explained separately."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3.
Statement introdcued in Junos OS Release 16.1R1 for Junos Fusion Enterprise. | [
"Configuring or Expanding a Junos Fusion Enterprise",
"Configuring Junos Fusion Provider Edge"
] |
upgrade-mode | upgrade-mode (3d-fabric | default | t4000); | [edit chassis fabric],
[edit chassis member name fabric] | Configures upgrade mode for SIBs and forces them to operate in the same mode until the upgrade is
complete. Upgrade mode is used so that two different types of SIBs can be installed in an operational
router or routing matrix. After you upgrade the SIBs delete the upgrade-mode statement from the
configuration. See the h... | [
{
"name": "3d-fabric",
"desc": "Enables the TX Matrix Plus router to upgrade to a TX Matrix Plus router with 3D SIBs. On the SFC, enables setting proper support for mixed SIBs (TXP-F13 SIB and TXP-F13-3D SIB). On the T640 or T1600 or T4000 routers in a routing matrix enables support for mixed SIBs (TXP-T160... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [
"TX Matrix Router and T640 Router Configuration Overview",
"Configuring Junos OS to Upgrade a T4000 Router to LCC 0 of a TX Matrix Plus Router with 3D SIBs",
"Configuring Junos OS to Upgrade the T1600 Router Chassis to LCC 0 of a TX Matrix Plus Router",
"with 3D SIBs",
"Upgrading an Operational Standalone R... |
uplink-failure-detection (Junos Fusion) | uplink-failure-detection {
<candidate-uplink-policy policy-name>;
} | [edit chassis satellite-management]
[edit chassis satellite-management fpc slot-id] | Enables uplink failure detection in a Junos Fusion.
The uplink failure detection feature on a Junos Fusion enables satellite devices to detect link failures on
the uplink interfaces used to connect to aggregation devices. When uplink failure detection detects
uplink failure on a satellite device, all of the device’s ex... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring Junos Fusion Provider Edge",
"Configuring or Expanding a Junos Fusion Enterprise"
] |
uplink-failure-detection | uplink-failure-detection {
action {
log;
}
group group-name {
debounce-interval seconds;
link-to-monitor interface-name;
link-to-disable interface-name;
}
traceoptions {
file filename <files number> <no-stamp> <replace> <size size> <world-readable | no-world... | [edit protocols] | Configure uplink and downlink interfaces in a group to monitor uplink failures and to propagate uplink
failures to the downlink interfaces.
The remaining statements are explained separately. See CLI Explorer. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configure Interfaces for Uplink Failure Detection"
] |
uplink-port-group (Junos Fusion) | uplink-port-group group-name; | [edit policy-options satellite-policies candidate-uplink-port-profile profile-name]
[edit policy-options satellite-policies candidate-uplink-port-profile profile-name term term-
name from] | In Junos Fusion configuration, assign an uplink port group to a candidate uplink port policy.
An uplink port group defines a set of candidate uplink ports that are assigned to satellite devices to
which the candidate uplink port group is assigned.
CAUTION: The physically connected uplink ports on a satellite device mu... | [
{
"name": "group-name",
"desc": "The name of the port group to assign."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring Junos Fusion Provider Edge",
"Configuring or Expanding a Junos Fusion Enterprise"
] |
upload (Event Policy) | upload filename (filename | committed) destination destination-name {
retry-count count retry-interval seconds;
transfer-delay seconds;
user-name username;
} | [edit event-options policy policy-name then] | Configure an event policy to upload the committed configuration file or other specified files to a
destination when triggered. | [
{
"name": "destination",
"desc": ""
},
{
"name": "destination-name",
"desc": "Name of the destination for the uploaded file. The destination must be defined in the destinations statement at the [edit event-options] hierarchy level."
},
{
"name": "filename (filename |",
"desc": ""
}... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5.
committed option for filename statement introduced in Junos OS Release 8.1. | [
"Configure an Event Policy to Upload Files"
] |
upload-profile (Security Antivirus FTP) | upload-profile profile-name; | [edit security utm default-configuration]
[edit security utm utm-policy policy-name anti-virus ftp] | Configure a Content Security policy for the antivirus FTP (upload) protocol and attach this policy to a
security profile to implement it. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
upload-profile (Security Content Filtering FTP) | upload-profile profile-name; | [edit security utm default-configuration]
[edit security utm utm-policy policy-name content-filtering ftp] | Configure a Content Security policy for the content-filtering FTP (upload) protocol and attach this policy
to a security profile to implement it. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
upstream-interface | upstream-interface [ interface-names ]; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast pim-to-igmp-proxy],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast pim-to-mld-proxy],
[edit logical-systems logical-system-name routing-options multi... | Configure at least one, but not more than two, upstream interfaces on the rendezvous point (RP) routing
device that resides between a customer edge–facing Protocol Independent Multicast (PIM) domain and
a core-facing PIM domain. The RP routing device translates PIM join or prune messages into
corresponding IGMP report ... | [
{
"name": "interface-names",
"desc": "Names of one or two upstream interfaces to which the RP routing device proxies"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.6. | [
"Configuring PIM-to-IGMP Message Translation",
"Configuring PIM-to-MLD Message Translation"
] |
upstream-label | upstream-label {
vlan-id vlan-id;
} | [edit protocols mpls label-switched-path lsp-name lsp-attributes] | Specify the upstream label for the bidirectional label-switched path (LSP). | [
{
"name": "vlan-id vlan-id",
"desc": "VLAN ID to be used for the Generalized MPLS (GMPLS) VLAN LSP at the ingress provider edge (PE) to customer edge (CE) link."
}
] | 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. | [
"Configuring MPLS LSPs for GMPLS"
] |
upstream-mode | upstream-mode; | [edit logical-systems name protocols router-advertisement interface],
[edit protocols router-advertisement interface] | Configure the interface as upstream interface for RA proxy. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.1R1 | [] |
upstream-rate (Traffic Shaping) | upstream-rate rate; | [edit dynamic-profiles profile-name interfaces $junos-interface-ifd-name unit $junos-interface-
unit advisory-options],
[edit dynamic-profiles profile-name interfaces interface-set $junos-interface-set-name interface
$junos-interface-ifd-name advisory-options],
[edit interfaces demux0 unit logical-unit-number advisory... | Specify a recommended shaping rate to be applied to upstream traffic on an interface.
For ANCP interfaces, this configured rate is used as the default value for the Juniper VSA Upstream-
Calculated-Qos-Rate (26-142) when the router has not received and processed the attributes from the
access node.
For L2TP, the rate ... | [
{
"name": "rate",
"desc": "Traffic rate in bits per second."
}
] | 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.
Support at the [edit interfaces demux0 ...] hierarchy level introduced in Junos OS Release 12.2.
Support at the [edit dynamic-profiles ...] hierarchy level introduced in Junos OS Release 13.1. | [
"ANCP Agent Traffic Shaping and CoS",
"ANCP Agent Neighbors and Operations",
"Configuring the Method to Derive the LAC Connection Speeds Sent to the LNS"
] |
upstream-rewrite | upstream-rewrite {
dscp dscp;
dscp-n3 dscp-n3;
forwarding-class forwarding-class;
loss-priority(high | low);
} | [edit services agf fiveqi-map] | Rewrite QoS attributes for upstream traffic in AGF in the 5QI table. | [
{
"name": "dscp",
"desc": "Differentiated services code point (DSCP) value on the IP packet containing user data sent to the UPF on N3 Interface. DSCP is a 6-bit value represented by decimal value between 0 to 63. Range: 0 through 63"
},
{
"name": "dscp-n3",
"desc": "DSCP value of the GTP-U enc... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Command introduced in Junos OS Release 23.2R1. | [
"CoS for Subscriber Access Overview"
] |
urgent-pointer | urgent-pointer {
match (equal | greater-than | less-than | not-equal);
value urgent-pointer;
} | [edit security idp custom-attack attack-name attack-type signature protocol tcp] | Specify the data in the packet is urgent; the URG flag must be set to activate this field. | [
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value urgent-pointer",
"desc": "Match the value of the urgent pointer."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
uri-check | uri-check; | [edit security utm default-configuration anti-virus scan-options] | Perform Sophos antivirus Uniform Resource Identifier (URI) checking. URI checking is a way of analyzing
URI content in HTTP traffic against a remote Sophos database to identify malware or malicious content.
URI checking is on by default.
NOTE: Starting in Junos OS release 18.4R1, the URI checking is off by default.
Yo... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
url (Security Antivirus) | url url; | [edit security utm feature-profile anti-virus juniper-express-engine pattern-update]
[edit security utm feature-profile anti-virus kaspersky-lab-engine pattern-update]
[edit security utm feature-profile anti-virus sophos-engine pattern-update]
[edit security utm default-configuration anti-virus avira-engine pattern-upd... | 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 9.5 for Juniper Express
engine and Kaspersky Lab engine. Support for Sophos engine added in Junos OS Release 11.1.
The [edit security utm default-config... | [] |
url (Security IDP) | url url-name; | [edit security idp security-package] | Specify the URL to automatically download the updated signature database. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
url (Security) | url url; | [edit security dynamic-address feed-server feed-server-name] | URL of the bundle file for feed server configuration. Use a browser to verify the URL validity. Examples
of URLs are shown below:
•
example.url.com/my_file.tgz
•
example.url.com/my_file.bundle | [] | security | Statement introduced in Junos OS Release 19.3R1. | [
"Dynamic Address Groups in Security Policies"
] |
url (Security) | url url-name; | [edit security pki ca-profile ca-profile-name enrollment],
[edit security pki ca-profile ca-profile-name revocation-check crl] | (Supported on Adaptive Services (AS) and MultiServices PICs only.) Specify the certificate authority (CA)
URL to use in requesting digital certificates or the URL for the Lightweight Directory Access Protocol
(LDAP) location from which the certificate revocation list (CRL) is retrieved. | [
{
"name": "url-name",
"desc": "Location of the CA to which enrollment requests are sent or LDAP location of the CRL. With"
}
] | admin—To view the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Enroll a Certificate"
] |
url | url url-name; | [edit unified-edge pcef pcc-action-profiles profile-name redirect],
[edit services pcef pcc-action-profiles profile-name redirect] | Specify the URL name that you want a PCC action profile to use for performing HTTP redirection. If you
configure this, the PCC action profile can only be used in PCC rules that match only HTTP-based
applications and all flows.
If you are using Junos OS Subscriber Aware, specify the URL name at the [edit unified-edge pc... | [
{
"name": "url-name",
"desc": "URL for the HTTP redirect."
}
] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef pcc-action-profiles profile-name redirect] hierarchy level introduced for
Junos OS Broadband Subscriber Management in Junos OS Release 17.2 on MX Series.
Support for Next Gen Services for Junos OS Broadband Subscriber Management introduce... | [
"Configuring Policy and Charging Control Action Profiles For Junos OS Subscriber Aware",
"Configuring Policy and Charging Control Action Profiles for Subscriber Management"
] |
url | url url; | [edit services application-identification download] | Define the URL for application package downloads. | [
{
"name": "url",
"desc": "Download URL."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring Automatic Download of Application Package Updates"
] |
url-blacklist | url-blacklist listname; | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering] | This is a global blocklist category, blocking content for Web filtering. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
url-feed | url-feed name {
interval interval;
no-autoupdate;
proxy-profile proxy-profile;
routing-instance routing-instance;
url url;
} | [edit logical-systems name security utm custom-objects],
[edit logical-systems name tenants name security utm custom-objects],
[edit security utm custom-objects],
[edit tenants name security utm custom-objects] | Configure URL feed object. The URL feed object reduces your effort to add multiple URLs into a single
URL pattern. The URL feed enables you to create a URL pattern automatically.
To create a URL pattern automatically, you need to create a URL feed file on the HTTP server. You
should add the URLs that need to be added i... | [
{
"name": "url-feed name",
"desc": "Configure the name of the URL feed object"
},
{
"name": "interval",
"desc": "Interval in hours for auto-updating list Default: 24 Range: 1 through 168"
},
{
"name": "no-autoupdate",
"desc": "Disable automatic update for URL feed pattern"
},
{... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [] |
url-filter | url-filter {
profile profile-name {
template template-name {
client-interfaces [ client-interface-name1 client-interface-name2 ];
disable-url-filtering;
dns-resolution-interval minutes;
dns-resolution-rate seconds;
dns-retries number;
... | [edit services] | Configure URL filtering service.
NOTE: Starting in Junos OS Release 18.3R1, the url-filter statement is deprecated and
has been replaced by the web-filter statement. The url-filter statement is supported for
backward compatibility. | [
{
"name": "url-filter-database filename",
"desc": "Specify the filename of the URL filter database. This option is mandatory. The remaining statements are explained separately."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2. | [
"Configuring URL Filtering",
"URL Filtering Overview"
] |
url-filter-profile | url-filter-profile profile-name; | [edit services service-set service-set-name] | Specify the URL filter profile that the service set uses. The URL filter profile specifies how to filter access
to disallowed URLs, and is configured at the [edit services url-filter] hierarchy level.
NOTE: You must also configure the next-hop-service statement with this statement.
NOTE: Starting in Junos OS Release 18... | [
{
"name": "profile-name",
"desc": "Name of the URL filter profile."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2. | [
"Configuring URL Filtering",
"URL Filtering Overview"
] |
url-filter-template | url-filter-template template-name {
client-interfaces [ client-interface-name1 client-interface-name2 ];
disable-url-filtering;
dns-resolution-interval minutes;
dns-resolution-rate seconds;
dns-retries number;
dns-routing-instance dns-routing-instance-name;
dns-server [ ip-address1 ip-addres... | [edit services web-filter profile profile-name] | Configure a URL filter template. | [
{
"name": "template-name",
"desc": "Name of the URL filter template. client-interfaces [ client-interface-name1 client-"
},
{
"name": "interface-name2 ]",
"desc": "The list of client-facing logical interfaces (uplink) on which the URL filtering is configured. This option is mandatory."
},
{
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1 on MX Series.
Statement introduced in Junos OS Release 20.1R1. | [
"Configuring URL Filtering"
] |
url-pattern | Pattern Format | [edit security utm custom-objects] | Example
Asterisk (*) in
domain name
Pattern = [*].sub-
domain..sub-domain
Asterisk should be at the head
only.
Match 0-N words in domain
name.
*.juniper.net
*.net
Caret (^) in domain
name
Pattern = [^]..[^].sub-
domain.[^]..[^].sub-domain.
[^]..[^]
Caret could be at any place.
Match one word in domain
name.
^.google.^.... | [
{
"name": "object-name",
"desc": "Name of the URL list object."
},
{
"name": "value value",
"desc": "Value of the URL list object. You can configure multiple values separated by spaces and"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Security Policies User Guide for Security Devices"
] |
url-whitelist | url-whitelist listname; | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering] | A URL allowlist is a unique custom list that you define in which all the URLs or IP addresses in that list
for a specified category are always bypassed for filtering | [] | 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. | [] |
url-whitelist | url-whitelist listname; | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus] | A URL allowlist is a unique custom list that you define in which all the URLs or IP addresses in that list
for a specified category are always bypassed for scanning. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
usb | usb {
disable;
} | [edit system autoinstallation]
[edit chassis] | Disable the USB autoinstallation process. | [
{
"name": "disable",
"desc": "Disable the process."
}
] | 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. | [
"Configuring Autoinstallation of Configuration Files"
] |
usb-control | usb-control {
command binary-file-path;
disable;
} | [edit system processes] | Specify the universal serial bus (USB) supervise process. | [
{
"name": "command binary-file-path",
"desc": "Path to the binary process."
},
{
"name": "disable",
"desc": "Disable the universal serial bus (USB) supervise process."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
use-active-child-mac-on-reth | use-active-child-mac-on-reth; | [edit chassis cluster] | Copy child's physical MAC address on RETH parent's current MAC address on KVM based systems.
NOTE: The commands use-active-child-mac-on-reth and use-actual-mac-on-physical-interfaces
need to be configured together and the device rebooted for the feature to work. | [] | interface | Statement introduced in Junos OS Release 19.4R1. | [] |
use-actual-mac-on-physical-interfaces | use-actual-mac-on-physical-interfaces; | [edit chassis cluster] | Configure this command so that SR-IOV uses hypervisor’s provided MAC address for physical interfaces
on KVM based systems.
NOTE: The commands use-active-child-mac-on-reth and use-actual-mac-on-physical-interfaces
need to be configured together and the device rebooted for the feature to work. | [] | interface | Statement introduced in Junos OS Release 19.4R1. | [] |
use-class (Class Attribute) | use-class {
regex “value”;
pattern “pattern”;
subscription-id-type (imsi | msisdn | nai | private | sip-uri);
} | [edit unified-edge gateways tdf gateway-name domains domain-name subscription-id] | Configure a regular expression to parse the Class attribute contents, specify characters to insert
between the resulting regular expression groups, and specify the subscription ID type if you configured
subscription-id-options entry-name use-class under [edit unified-edge gateways tdf gateway-name domains domain-
name ... | [] | 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 Set of IP-Based TDF Subscriber Properties with a TDF Domain"
] |
use-extended-flow-memory | use-extended-flow-memory; | [edit chassis fpc slot-number inline-services] | Configure the service to extended flow memory. This service provides more scale in flows for inline
services sampling.
The new configuration set chassis fpc slot slot-number inline-services use-extended-flow-memory allows you to
configure table to operate in side band mode with side band memory. This configuration is a... | [] | 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. | [
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250",
"Including Fragmentation Identifier and IPv6 Extension Header Elements in IPFIX Templates on MX",
"Series Routers"
] |
use-for-post-convergence-lfa | use-for-post-convergence-lfa; | [edit logical-systems name routing-instances name routing-options fate-sharing group group-name],
[edit logical-systems name routing-options fate-sharing group group-name],
[edit routing-instances name routing-options fate-sharing group group-name],
[edit routing-options fate-sharing group group-name] | Use this fate-sharing group as a constraint for the backup path computed by topology-independent
loop-free alternate (TI-LFA). | [] | system | 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-imported-time-zones | use-imported-time-zones; | [edit system] | Configure a custom time zone from a locally generated time-zone database. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Updating the IANA Time Zone Database on Junos OS Devices"
] |
use-ingress-routes-as-transit | use-ingress-routes-as-transit; | [edit logical-systems name protocols source-packet-routing srv6],
[edit protocols source-packet-routing srv6] | Download all ingress routes with transit behavior | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [] |
use-interface | use-interface-description {logical |device}; | [edit interfaces interface-name unit logical-unit-number family family dhcp-client client-
identifier] | The description configured at the physical or logical interface level is used for client identification. | [] | 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. | [] |
use-interface-description (MX) | use-interface-description (device | logical);
Hierarchy Level (For Platforms with Enhanced Layer 2 Software (ELS))
[edit vlans vlan-name forwarding-options dhcp-security option-82 circuit-id] | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security option-82circuit-id] | Use the interface description rather than the interface name (which is the default value) in the circuit ID
or remote ID value in the DHCP option 82 information.
The textual description is configured using the description statement at the [edit interfaces interface-name]
hierarchy level. If you specify that the textual... | [
{
"name": "device",
"desc": "Use the device interface description. Only available for MX Series platform configuration."
},
{
"name": "logical",
"desc": "Use the logical interface description. Only available for MX Series platform 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.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... | [
"Example: Setting Up DHCP Option 82 Using the Same VLAN",
"Example: Setting Up DHCP Option 82",
"http://tools.ietf.org/html/rfc3046"
] |
use-interface-description | use-interface-description (logical | device); | [edit forwarding-options dhcp-relay dhcpv6 (relay-agent-interface-id | relay-agent-remote-id)],
[edit forwarding-options dhcp-relay dhcpv6 group group-name (relay-agent-interface-id | relay-
agent-remote-id)],
[edit forwarding-options dhcp-relay relay-option-82 (circuit-id | remote-id)],
[edit forwarding-options dhcp-r... | Use the textual interface description instead of the interface identifier in the DHCP base option 82
Agent Circuit ID (suboption 1) or Agent Remote ID (suboption 2) information, or in the DHCPv6 option
18 (Relay Agent Interface ID) or option 37 (Relay Agent Remote ID) information in DHCP packets that
the DHCP relay age... | [
{
"name": "logical",
"desc": "Use the textual description that is configured for the logical interface."
},
{
"name": "device",
"desc": "Use the textual description that is configured for the device interface."
}
] | 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.
Support at the [edit ... dhcpv6] hierarchy levels introduced in Junos OS Release 11.4.
Support at the [edit ... relay-agent-remote-id] and [edit ... remote-id] hierarchy levels introduced in Junos
OS Release 14.1.
Support at the [edit vlans vlan-name dhcp-security dhcpv6-op... | [
"Using DHCP Option 82 Information",
"Using DHCP Relay Agent Option 82 Information",
"Configuring DHCPv6 Relay Agent Options"
] |
use-interface-index | use-interface-index (logical | device); | [edit vlans vlan-name forwarding-options dhcp-security dhcpv6-options option-18],
[edit vlans vlan-name forwarding-options dhcp-security dhcpv6-options option-37] | Use the index number of the interface instead of the interface name in the DHCPv6 option 18 (Relay
Agent Interface-ID) or option 37 (Relay Agent Remote-ID). These options are used by a relay agent to
insert information in DHCPv6 requests before the relay agent forwards them to a DHCPv6 server. | [
{
"name": "logical",
"desc": "Use the textual description that is configured for the logical interface."
},
{
"name": "device",
"desc": "Use the textual description that is configured for the device interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10. | [
"Including a Textual Description in DHCP Options",
"Using DHCP Relay Agent Option 82 Information",
"Configuring DHCPv6 Relay Agent Options"
] |
use-interface-name | use-interface-name (logical | device); | [edit vlans vlan-name forwarding-options dhcp-security dhcpv6-options option-18],
[edit vlans vlan-name forwarding-options dhcp-security dhcpv6-options option-37] | Configure DHCPv6 option 18 (Relay Agent Interface-ID) or option 37 (Relay Agent Remote-ID) to use
the interface name to identify the port identity of the DHCP client to the DHCP server. | [
{
"name": "logical",
"desc": "Use the name that is configured for the logical interface."
},
{
"name": "device",
"desc": "Use the name that is configured for the device interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10. | [
"Including a Textual Description in DHCP Options",
"Using DHCP Relay Agent Option 82 Information",
"Configuring DHCPv6 Relay Agent Options"
] |
use-option-82 | use-option-82 <strict>; | [edit forwarding-options dhcp-relay dhcpv6 (relay-agent-interface-id | relay-agent-remote-id)],
[edit forwarding-options dhcp-relay dhcpv6 group group-name (relay-agent-interface-id | relay-agent-
remote-id)],
[edit logical-systems logical-system-name forwarding-options dhcp-relay dhcpv6 ... (relay-agent-
interface-id ... | For the relay-agent-interface-id statement, specify that in dual-stack environments, the DHCPv6 relay
agent uses an Interface-ID option (option 18) that is based on the DHCPv4 relay agent information
option (option 82). When you include this statement, the DHCPv6 relay agent checks for the option 82
Agent Circuit-ID su... | [
{
"name": "strict",
"desc": "(Optional) The router drops Solicit messages that do not include a DHCPv4 Remote-ID (option 82 suboption 2). If you do not specify the strict keyword, the router sends the RELAY-FORW message without adding 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 13.2.
Support at the [...relay-agent-remote-id] hierarchy level introduced in Junos OS Release 15.1. | [
"Using DHCP Relay Agent Option 82 Information",
"Inserting DHCPv6 Interface-ID Option (Option 18) In DHCPv6 Packets"
] |
use-p2mp-lsp | igmp-snooping-options {
use-p2mp-lsp;
}
} | [edit routing-instances instance name igmp-snooping-options] | Point-to-multipoint LSP for IGMP snooping enables multicast data traffic in the core to take the point-
to-multipoint path. The effect is a reduction in the amount of traffic generated on the PE router when
sending multicast packets for multiple VPLS sessions because it avoids the need to send multiple parallel
streams... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Configuring Point-to-Multipoint LSP with IGMP Snooping"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.