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 |
|---|---|---|---|---|---|---|---|
tunnel (Security Screen) | tunnel {
gre {
gre-4in4;
gre-4in6;
gre-6in4;
gre-6in6;
}
ip-in-udp {
teredo;
}
ipip {
ipip-4in4;
ipip-4in6;
ipip-6in4;
ipip-6in6;
ipip-6over4;
ipip-6to4relay;
isatap;
dslite;
}
bad-inner-... | [edit security screen ids-option ids-option-name ip] | Enable IP tunnel IDS options. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D10. | [
"Attack Detection and Prevention Overview"
] |
tunnel (Tunnel Profile) | tunnel tunnel-id {
identification name;
logical-system logical-system-name;
max-sessions number;
medium type;
nas-port-method cisco-avp;
preference number;
remote-gateway {
address server-ip-address;
gateway-name server-name;
}
routing-instance routing-instance-name;
... | [edit access tunnel-profile profile-name] | Define the attributes of a tunnel for the tunnel profile. You can define up to 31 tunnels for each tunnel
profile. | [
{
"name": "tunnel-id",
"desc": "Unique integer that identifies a tunnel defined within a profile. For a subscriber, RADIUS"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"L2TP LAC Tunneling for Subscribers"
] |
tunnel | tunnel {
allow-fragmentation;
backup-destination address;
destination destination-address;
do-not-fragment;
key number;
routing-instance {
destination routing-instance-name;
}
source source-address;
traffic-class traffic-class-value;
ttl number;
} | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Configure a tunnel. You can use the tunnel for unicast and multicast traffic or just for multicast traffic.
You can also use tunnels for encrypted traffic or virtual private networks (VPNs).
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "encapsulation ipip ( source | address)",
"desc": "(Optional) Configure IP-IP encapsulation type. To configure an IP-in-IP tunnel at an FTI, use the encapsulation ipip option at the [edit interfaces interface-name unit logical-"
}
] | 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"
] |
tunnel-attributes | tunnel-attributes name{
dynamic-tunnel-source-prefix dynamic-tunnel-source-prefix;
dynamic-tunnel-type V4oV6;
dynamic-tunnel-mtu dynamic-tunnel-mtu;
dynamic-tunnel-reassembly;
dynamic-tunnel-anchor-pfe dynamic-tunnel-anchor-pfe
dynamic-tunnel-anti-spoof (off | on);
} | [edit logical-systems name routing-instances name routing-options dynamic-tunnels],
[edit logical-systems name routing-options dynamic-tunnels],
[edit routing-instances name routing-options dynamic-tunnels],
[edit routing-options dynamic-tunnels] | Define dynamic tunnel attributes for transporting IPv4 traffic over an IPv6 network. You can configure
multiple tunnels and specify different attributes for each tunnel. Service providers with IPv6
infrastructure can configure individual tunnels for each customer to route IPv4 traffic. | [
{
"name": "name",
"desc": "Specify a dynamic tunnel name. You can have multiple tunnels configured with different attributes."
},
{
"name": "dynamic-tunnel-anchor-pfe",
"desc": "Specify a dynamic tunnel anchor PFE name of format pfe-x/y/z."
},
{
"name": "dynamic-tunnel-anti-spoof",
"... | 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. | [
"Understanding Redistribution of IPv4 Routes with IPv6 Next Hop into BGP"
] |
tunnel-devices (Protocols AMT) | tunnel-devices [ ud-fpc/pic/port ]; | [edit logical-systems logical-system-name protocols amt relay],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols amt
relay],
[edit protocols amt relay],
[edit routing-instances routing-instance-name protocols amt relay] | List one or more tunnel-capable Automatic Multicast Tunneling (AMT) PICs to be used for creating
multicast tunnel (ud) interfaces. Creating an AMT PIC list enables you to control the load-balancing
implementation.
Tunnel-capable PICs include DPC and MPC.
The physical position of the PIC in the routing device determines... | [
{
"name": "ud-fpc/pic/port",
"desc": "Interface that is automatically generated when a tunnel-capable PIC is installed in the"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Configuring the AMT Protocol",
"Example: Configuring the AMT Protocol"
] |
tunnel-devices (Tunnel-Capable PICs) | tunnel-devices [ mt-fpc/pic/port ]; | [edit logical-systems logical-system-name routing-instances instance-name protocols pim],
[edit routing-instances instance-name protocols pim] | List one or more tunnel-capable PICs to be used for creating multicast tunnel (mt) interfaces. Creating a
PIC list enables you to control the load-balancing implementation.
Tunnel-capable PICs include:
•
Adaptive Services PIC
•
Multiservices PIC or Multiservices DPC
•
Tunnel Services PIC
•
On MX Series routers, a PIC ... | [
{
"name": "mt-fpc/pic/port",
"desc": "Interface that is automatically generated when a tunnel-capable PIC is installed in the"
}
] | 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. | [
"Load Balancing Multicast Tunnel Interfaces Among Available PICs"
] |
tunnel-end-point | tunnel-end-point tunnel-name {
gre {
key authentication key;
}
ipv4 {
destination-address destination-host-address;
source-address source-host-address;
}
ipv6 {
destination-address destination-host-address;
source-address source-host-address;
}
} | [edit firewall] | The tunnel-end-point command enables line-rate, filter-based, GRE tunneling of IPv4 and IPv6 payloads
across IPv4 networks for MX Series routers running Trio-based FPCs (including MX80, MX104 and
MX204). Filter-based tunneling encapsulates the original passenger protocol packet in an outer packet
header. For example, f... | [
{
"name": "gre",
"desc": "Encapsulation protocol. Options include gre and gre-in-udp. You must also specify whether the tunnel is IPv4 or IPv6. A IPv4 example using GRE follows."
},
{
"name": "tunnel-end-point name {",
"desc": ""
},
{
"name": "ipv4 {",
"desc": ""
},
{
"name":... | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"Components of Filter-Based Tunneling Across IPv4 Networks",
"Understanding Filter-Based Tunneling Across IPv4 Networks",
"Firewall Filter Terminating Actions",
"enhanced-mode (Network Services)"
] |
tunnel-group | tunnel-group group-name {
aaa-access-profile profile-name;
dynamic-profile profile-name;
hello-interval seconds;
hide-avps;
l2tp-access-profile profile-name;
local-gateway address {
address address;
gateway-name gateway-name;
}
maximum-send-window packets;
maximum-ses... | [edit services l2tp] | Specify the L2TP tunnel properties.
NOTE: Subordinate statement support depends on the platform. See individual
statement topics for more detailed support information. | [
{
"name": "group-name",
"desc": "Identifier for the tunnel group."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for MX Series routers introduced in Junos OS Release 11.4. | [
"Configuring L2TP Tunnel Groups",
"Configuring an L2TP Tunnel Group for LNS Sessions with Inline Services Interfaces"
] |
tunnel-initiated | tunnel-initiated; | [edit firewall family ethernet-switching filter name term name from vxlan],
[edit firewall family ethernet-switching filter name term name from ip-version ipv4 vxlan],
[edit firewall family ethernet-switching filter name term name from ip-version ipv6 vxlan],
[edit logical-systems name firewall family ethernet-switchin... | You can enforce per-VNI egress rate limits on VXLAN tunnel-initiated traffic using a filter with the vxlan
tunnel-initiated match qualifier and the egress profile1 filter profile. This configuration targets VXLAN
traffic and preserves locally switched or routed flows while it helps prevent congestion, mitigate denial-
... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.4R1 | [
"Overview of Firewall Filters (QFX Series)"
] |
tunnel-inspection | tunnel-inspection
{
inspection-profile profile-name
{
vxlan vxlan-tunnel-name
{
policy-set policy-set;
vni vni-name;
}
}
traceoptions (Security)
{
file <filename> <files files> <match match> <size size> <(worl... | [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... | [
{
"name": "inspection-profile profile-name",
"desc": "Configure a tunnel inspection profile to connect the outer policy and"
},
{
"name": "trace-option",
"desc": "Trace options for Network Security tunnel-inspection. Configure trace option for tunnel"
},
{
"name": "vni vni-name",
"de... | Security—To view this statement in the configuration.
Security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.1R1. | [
"CLI Explorer"
] |
tunnel-limit (Protocols AMT) | tunnel-limit number; | [edit logical-systems logical-system-name protocols amt relay],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols amt
relay],
[edit protocols amt relay],
[edit routing-instances routing-instance-name protocols amt relay] | Limit the number of Automatic Multicast Tunneling (AMT) data tunnels created. The system might reach
a dynamic upper limit of tunnels of all types before the static AMT limit is reached. | [
{
"name": "number",
"desc": "Maximum number of data AMTs that can be created on the system."
}
] | 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 the AMT Protocol"
] |
tunnel-limit (Routing Instances Provider Tunnel Selective) | tunnel-limit number; | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel selective],
[edit routing-instances routing-instance-name provider-tunnel selective] | Specify a limit on the number of selective tunnels that can be created for an LSP. This limit can be
applied to the following types of selective tunnels:
•
Ingress replication tunnels
•
LDP-signaled LSP
•
LDP point-to-multipoint LSP
•
PIM-SSM provider tunnel
•
RSVP-signaled LSP
•
RSVP-signaled point-to-multipoint LSP | [
{
"name": "number",
"desc": "Specify the tunnel limit."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring Point-to-Multipoint LSPs for an MBGP MVPN"
] |
tunnel-limit (Routing Instances) | tunnel-limit limit; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
mdt],
[edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel family (inet | inet6) mdt],
[edit routing-instances routing-instance-name protocols pim mdt],
[edit routing-instances ... | Limit the number of data MDTs created in this VRF instance. If the limit is 0, then no data MDTs are
created for this VRF instance. | [
{
"name": "limit",
"desc": "Maximum number of data MDTs for this VRF instance."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. In Junos OS Release 17.3R1, the mdt hierarchy was
moved from provider-tunnel to the provider-tunnel family inet and provider-tunnel family inet6 hierarchies as
part of an upgrade to add IPv6 support for default MDT in Rosen 7, and data MDT for Rosen 6 and
Rosen 7. The p... | [
"Example: Configuring Data MDTs and Provider Tunnels Operating in Source-Specific Multicast Mode",
"Example: Configuring Data MDTs and Provider Tunnels Operating in Any-Source Multicast Mode"
] |
tunnel-mtu (Services IPsec VPN) | tunnel-mtu bytes; | [edit services ipsec-vpn rule rule-name term term-name then] | Maximum transmission unit (MTU) size for IPsec tunnels. This defines the maximum size of an IP packet,
including the IPsec overhead. | [
{
"name": "bytes",
"desc": "MTU size."
}
] | 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. | [] |
tunnel-mtu (Services Service Set) | tunnel-mtu bytes; | [edit services service-set service-set-name ipsec-vpn-options] | Maximum transmission unit (MTU) size for IPsec tunnels. This statement is useful for dynamic endpoint
tunnels for which you cannot configure the tunnel-mtu statement at the [edit services ipsec-vpn rule rule-
name term term-name then] hierarchy level.
For static IPsec tunnels, this statement sets the tunnel MTU value f... | [
{
"name": "bytes",
"desc": "MTU size."
}
] | 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 IPsec Service Sets",
"Configuring IPsec Rules"
] |
tunnel-mtu | tunnel-mtu; | [edit security ipsec vpn hub-to-spoke-vpn tunnel-mtu tunnel-mtu] | Tunnel MTU is the maximum size of transmit packet for IPsec tunnels. The minimum Tunnel MTU you
can configure for IPv6 is 1390.
Range
Range - The packet size of the minimum tunnel value ranges from 256 to 9192 . | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.3R1 | [
"Next Gen Services Overview"
] |
tunnel-observation | tunnel-observation [ipv4 | ipv6 | mpls-over-udp]; | [edit services flow-monitoring version9 template template-name]
[edit services flow-monitoring version-ipfix template template-name] | Specify the types of MPLS flows on which to enable inline flow monitoring. If you do not configure a
tunnel-observation type, then plain MPLS flow records are created.
You can configure multiple values for tunnel-observation. Flows are created for only the deepest match.
For example, if you configure both ipv4 and mpls... | [
{
"name": "ipv4",
"desc": "Enable flow monitoring for MPLS-IPv4 traffic. You must also configure mpls-template at the [edit services flow-monitoring (version9 | version-ipfix) template template-name] hierarchy level."
},
{
"name": "ipv6",
"desc": "Enable flow monitoring for MPLS-IPv6 traffic. Yo... | 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.
ipv4 and ipv6 options added in Junos OS Release 18.2R1.
Statement introduced in Junos OS Release 18.4R1 on MX Series routers. | [
"Inline Active Flow Monitoring of MPLS-over-UDP Flows on PTX Series Routers",
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250"
] |
tunnel-port (GRE) | tunnel-port port-number | [edit chassis fpc slot-number pic number tunnel-services] | For MX Series 5G Universal Routing Platforms, configure the port number of the tunnel. The range is 0
through 3. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.4R1. | [] |
tunnel-port | tunnel-port port-number tunnel-services; | [edit chassis fpc slot pic pic-number] | Configure the port number for generic routing encapsulation (GRE) tunneling. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Configuring Generic Routing Encapsulation Tunneling"
] |
tunnel-profile (Domain Map) | tunnel-profile profile-name; | [edit access domain map domain-map-name] | Tunnel profile that provides definitions for tunnels associated with the domain map. | [
{
"name": "profile-name",
"desc": "Name of tunnel profile."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Mapping Subscriber Domains to Access and Session Options",
"Configuring a Tunnel Profile for Subscriber Access"
] |
tunnel-profile (L2TP Tunnel Switching) | tunnel-profile profile-name; | [edit access tunnel-switch-profile profile-name] | Specify the name of an L2TP tunnel profile that defines the tunnel to which PPP subscriber traffic is
switched. | [
{
"name": "profile-name",
"desc": "Unique name that identifies the tunnel profile; configured with the tunnel-profile statement"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"L2TP Tunnel Switching For Multiple-Domain Networks"
] |
tunnel-profile (Tunnel Profile) | tunnel-profile profile-name {
tunnel tunnel-id {
identification name;
logical-system logical-system-name;
max-sessions number;
medium type;
nas-port-method cisco-avp;
preference number;
remote-gateway {
address server-ip-address;
gatewa... | [edit access] | Define a tunnel profile for subscriber access. | [
{
"name": "profile-name",
"desc": "Unique name that identifies the tunnel profile. The profile can be referenced from within a"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"L2TP LAC Tunneling for Subscribers"
] |
tunnel-queuing | tunnel-queuing; | [edit chassis fpc slot-number pic pic-number] | Enable class-of-service (CoS) queuing for generic routing encapsulation (GRE) and IP-IP tunnels.
NOTE: The tunnel-queuing option is not supported in chassis cluster mode. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement modified in Release 9.0 of Junos OS. | [] |
tunnel-routing-instance | tunnel-routing-instance {
routing-instance routing-instance;
} | [edit interfaces interface name unit name tunnel encapsulation gre] | Indicates that the tunnel lookup is done with Layer 3 VPN. | [
{
"name": "routing-instance",
"desc": "Routing instance to which tunnel-route belongs or the default routing instance."
}
] | interface | Statement introduced in Junos OS Evolved Release 20.2R1. | [] |
tunnel-services (Chassis) | tunnel-services {
bandwidth bandwidth-value;
multicast;
tunnel-only;
} | [edit chassis fpc slot-number pic number] | For MX Series 5G Universal Routing Platforms, configure the amount of bandwidth for tunnel services.
For ACX Series routers, configure the amount of bandwidth for tunnel services. Only bandwidths of 1
Gbps and 10 Gbps are supported for ACX routers.
For M7i, M10i, M120, M320, T Series and TX Matrix routers with IQ2 PICs... | [
{
"name": "bandwidth",
"desc": "Bandwidth reserved for tunnel services."
},
{
"name": "tunnel–only (Optional)",
"desc": "For M7i, M10i, M120, M320, T Series and TX Matrix routers with IQ2 PICs and"
}
] | 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.
multicast option introduced in Junos OS Evolved Release 25.4R1EVO. | [
"Example: Configuring Tunnel Interfaces on a Gigabit Ethernet 40-Port DPC",
"Example: Configuring Tunnel Interfaces on a 10-Gigabit Ethernet 4-Port DPC",
"Example: Configuring Tunnel Interfaces on the MPC3E"
] |
tunnel-services (Routing Instances VPLS) | tunnel-services {
devices device-names;
primary primary-device-name;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls],
[edit routing-instances routing-instance-name protocols vpls] | Specify that traffic for particular VPLS routing instances be forwarded to specific virtual tunnel (VT)
interfaces, allowing you to load-balance VPLS traffic among all the available VT interfaces on the router.
NOTE: In the VPLS documentation, the word router in terms such as PE router is used to
refer to any device t... | [
{
"name": "devices device-names",
"desc": "Specify the VT interfaces acceptable for use by the VPLS routing instance. If you"
},
{
"name": "primary primary-device-name",
"desc": "Specify the primary VT interface to be used by the VPLS routing"
}
] | 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. | [
"Specifying the VT Interfaces Used by VPLS Routing Instances"
] |
tunnel-services (RSVP) | tunnel-services {
devices device-names;
} | [edit logical-systems logical-system-name protocols rsvp],
[edit protocols rsvp] | Enable ultimate-hop popping on point-to-multipoint LSPs. The Junos OS selects one of the available
virtual tunnel (VT) interfaces to de-encapsulate the egress traffic. By default, the selection process is
performed automatically.
Default
Ultimate-hop popping is disabled. | [
{
"name": "devices device-names",
"desc": "Specify which VT interfaces are used to handle the RSVP traffic."
}
] | 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. | [
"Enabling Ultimate-Hop Popping on Point-to-Multipoint LSPs"
] |
tunnel-source | tunnel-source address; | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel family (inet | inet6) pim-ssm],
[edit routing-instances routing-instance-name provider-tunnel family (inet | inet6) pim-ssm] | Configure the source address for the provider space multipoint generic router encapsulation (mGRE)
tunnel. This statement enables a VPN tunnel source for Rosen 6 or Rosen 7 multicast VPNs. . | [] | 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.
In Junos OS Release 17.3R1, the pim-ssm hierarchy was moved from provider-tunnel to the provider-tunnel
family inet and provider-tunnel family inet6 hierarchies as part of an upgrade to add IPv6 support for
default multicast distribution tree (MDT) in Rosen 7, and data MDT... | [] |
tunnel-source-protocol (Protocols OSPF) | tunnel-source-protocol {
rsvp;
spring-te;
} | [edit logical-systems logical-system-name protocols (ospf | ospf3) traffic-engineering],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(ospf | ospf3) traffic-engineering],
[edit protocols (ospf | ospf3) traffic-engineering],
[edit routing-instances routing-instance-name pr... | Enable SR-TE tunnel support. | [
{
"name": "rsvp",
"desc": "Pick label-switched paths from rsvp. Range: 1 through 255"
},
{
"name": "spring-te",
"desc": "Pick label-switched paths from spring-te. Range: 1 through 255"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.4R1. | [
"Tunneling LDP over SR-TE"
] |
tunnel-switch-profile (L2TP Tunnel Switching, Application) | tunnel-switch-profile profile-name; | [edit access domain map domain-map-name],
[edit services l2tp],
[edit services l2tp tunnel-group group-name] | Specify a tunnel switch profile that determines whether packets in an L2TP session from a LAC are
switched to another session that has a different destination LNS. | [
{
"name": "profile-name",
"desc": "Unique name that identifies the tunnel switch profile."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"L2TP Tunnel Switching For Multiple-Domain Networks"
] |
tunnel-switch-profile (L2TP Tunnel Switching, Definition) | tunnel-switch-profile profile-name {
avp {
bearer-type action;
calling-number action;
cisco-nas-port-info action;
}
tunnel-profile profile-name;
} | [edit access] | Define a tunnel switch profile for subscriber access; specify actions to take for L2TP AVPs in the
switched packets and the profile for the tunnel to which the PPP traffic is switched.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax sec... | [
{
"name": "profile-name",
"desc": "Unique name that identifies the tunnel switch profile. The profile can be applied as a default"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"L2TP Tunnel Switching For Multiple-Domain Networks"
] |
tunnel-termination | tunnel-termination; | [edit interfaces fti number unit logical-unit-number tunnel encapsulation ( gre | ipip | udp )],
[edit interfaces interface-name family inet],
[edit forwarding-options] | Enables the tunnel to terminate on the tunnel underlay interface configured at the [edit interfaces
interface-name family inet] hierarchy level.
On a flexible tunnel interface (FTI), enables tunnel termination for GRE, IPIP , or UDP decapsulation.
NOTE: Starting in Junos OS Evolved Release 20.3R1, this statement is opt... | [] | interface | Statement introduced in Junos OS Evolved Release 20.2R1.
Statement introduced for IPIP tunnels in Junos OS Evolved Release 20.4R1.
Statement introduced for UDP tunnels in Junos OS Evolved Release 21.1R1.
Statement introduced at the [edit forwarding-options] hierarchy level in Junos OS Evolved Release
21.4R2.
Statement... | [] |
tunnel-timeout | tunnel-timeout seconds; | [edit services l2tp tunnel-group name] | Specify the maximum downtime for an L2TP tunnel, after which the tunnel is terminated because the
connection is presumed to have been lost. | [
{
"name": "seconds",
"desc": "Interval after which the tunnel is terminated if no data can be sent."
}
] | 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 Timers for L2TP Tunnels",
"Configuring an L2TP Tunnel Group for LNS Sessions with Inline Services Interfaces"
] |
twamp (Security ALG) | alg {
twamp {
traceoptions {
flag {
all extensive;
}
}
}
} | [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... | [
{
"name": "twamp",
"desc": "Configure the TWAMP ALG."
},
{
"name": "traceoptions",
"desc": "Define the tracing operations for the TWAMP ALG. The TWAMP ALG trace options helps to monitor traffic flow into and out of the NFX Series and SRX Series devices."
},
{
"name": "flag",
"desc": ... | system—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [] |
twamp | twamp {
client {
control-connection name {
control-type (managed | light);
destination-port destination-port;
routing-instance routing-instance;
source-address source-address;
target target-address;
test-start (auto | manual);
... | [edit services monitoring] | Configure the Two-Way Active Measurement Protocol (TWAMP) client or server settings on MX Series
routers, ACX routers, EX4300 Switches, PTX Series routers, EX9200 Series switches, and QFX10000
Series switches.
TWAMP is an open protocol for measurement of two-way metrics. The host that initiates the TCP
connection takes... | [] | 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.
Junos OS Evolved syntax and hierarchy level introduced in Junos OS Evolved 20.3R1 for PTX10003
routers.
Support for the rest of the PTX10000 Series routers added in Junos OS Evolved Release 21.1R1.
control-type and light options added in Junos OS Release 21.1R1.
traps opti... | [
"Configure TWAMP on ACX, MX, M, T, and PTX Series Routers, EX4300 Series, EX9200 Series, and",
"QFX10000 Series Switches"
] |
twamp-server | twamp-server; | [edit interfaces sp-fpc/pic/port unit logical-unit-number] | Specify the service PIC logical interface to provide the TWAMP service. | [] | system—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 TWAMP on MX, M, T, and PTX Series Routers and EX4300 Series Switches"
] |
two-rate | two-rate {
(color-aware | color-blind);
committed-information-rate bps;
committed-burst-size bytes;
peak-information-rate bps;
peak-burst-size bytes;
} | [edit dynamic-profiles profile-name firewall three-color-policer name],
[edit firewall three-color-policer policer-name],
[edit logical-systems logical-system-name firewall three-color-policer policer-name] | Configure a two-rate three-color policer in which marking is based on the committed information rate
(CIR), committed burst size (CBS), peak information rate (PIR), and peak burst size (PBS).
Packets that conform to the CIR or the CBS are assigned low loss priority (green). Packets that exceed
the CIR and the CBS but a... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Logical systems support introduced in Junos OS Release 9.3.
Support at the [edit dynamic-profiles ... three-color-policer name hierarchy levels introduced in Junos OS
Release 11.4. | [
"Three-Color Policer Configuration Overview"
] |
tx-address-change (L2TP LAC) | tx-address-change (accept | ignore | ignore-ip-address | ignore-udp-port | reject | reject-ip-
address | reject-udp-port); | [edit services l2tp tunnel] | Configure whether the LAC accepts, ignores, or rejects requests from an LNS to change the destination
IP address, UDP port, or both.
When configured to ignore change requests, the LAC continues to send packets to the original address
or port, but accepts packets from the new address or port.
When configured to reject c... | [
{
"name": "accept",
"desc": "Accept all change requests for IP address or UDP port."
},
{
"name": "ignore",
"desc": "Ignore all change requests for IP address or UDP port."
},
{
"name": "ignore-ip-address",
"desc": "Ignore a change request for IP address, but accept a change request ... | 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.
reject, reject-ip-address, and reject-udp-port options added in Junos OS Release 16.1. | [
"L2TP LAC Subscriber Configuration"
] |
tx-buffers | tx-buffers (on | off); | [edit interfaces interface-name ether-options configured-flow-control] | Enable or disable an interface to respond to received Ethernet PAUSE messages. If you enable the
transmit buffers to respond to PAUSE messages, when the interface receives a PAUSE message from the
connected peer, the interface stops transmitting frames on the entire link. When the receive buffer on
the connected peer e... | [
{
"name": "on | off",
"desc": "Enable or disable an interface to respond to an Ethernet PAUSE message."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Configuring CoS Asymmetric Ethernet PAUSE Flow Control",
"Enabling and Disabling CoS Symmetric Ethernet PAUSE Flow Control",
"Understanding CoS Flow Control (Ethernet PAUSE and PFC)"
] |
tx-connect-speed-method (L2TP LAC) | tx-connect-speed-method method; | [edit services l2tp] | Specify the method that determines how to derive the connect speed values sent from the LAC to the
LNS.
When the session is being established, the speeds are included in the Incoming-Call-Connected (ICCN)
message. The transmit speed is conveyed in AVP 24 (Tx-Connect-Speed) and the receive speed is
conveyed in AVP 38 (R... | [
{
"name": "method",
"desc": "Method used to derive the connection speed values."
},
{
"name": "actual",
"desc": "(Junos OS Releases 15.1, 16.1, 16.2, 17.1) The speed is derived from the CoS"
},
{
"name": "ancp",
"desc": "The speed is derived from the configured ANCP value for the und... | 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.
Options ancp, pppoe-ia-tag, and static introduced in Junos OS Release 13.1.
Option static deprecated in Junos OS Release 15.1.
Options actual and none added in Junos OS Release 15.1.
Option actual deprecated in Junos OS Release 17.2.
Option service-profile added in Junos O... | [
"L2TP Subscriber Access Lines and Connection Speeds",
"L2TP Subscriber Access Lines and Connection Speeds"
] |
tx-dnu-to-line-source-enable | tx-dnu-to-line-source-enable; | [edit chassis synchronization output interfaces external],
[edit chassis synchronization output interfaces (external-0/0 | external-1/0)] | Configure the transmitting quality level to DNU or DUS on the line source interface that has been
selected as the external output source. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [] |
tx-duration | expected-defect {
tx-duration ; | [edit protocols oam ethernet connectivity-fault-management expected-defect] | The expected duration for which the peer MEP should suppress the LoC alarms. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1. | [] |
tx-enable | expected-defect {
tx-enable ; | [edit protocols oam ethernet connectivity-fault-management expected-defect] | Enable the ethernet expected defect (ETH-ED) function to control if EDM transmission need to be
triggered on ISSU.
The remaining statements are explained separately. See CLI Explorer.
Default
The MEP does not generate EDM PDUs by default. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1. | [] |
tx-power | tx-power dbm; | [edit interfaces interface-name optics-options] | Transmit laser output power (dBm).
Default
If you don’t specify a value, the default transmit laser output power is –2 dBm. | [
{
"name": "dbm",
"desc": "Transmit power value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1.
This statement is supported in MX10008 Universal Routing Platform from Junos OS Release 24.2R1. | [
"100-Gigabit Ethernet OTN Options Configuration Overview"
] |
type (Application Identification) | type type; | [edit services application-identification application application-name] | Specify the type of application, such as FTP or HTTP. | [
{
"name": "type",
"desc": "Type of application such as FTP or HTTP."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
type (ICMP Mapping for Application Identification) | type icmp-type; | [edit services application-identification application application-name icmp-mapping] | Match an ICMP type value to create a custom application signature. | [
{
"name": "value",
"desc": "ICMP code value. Range: 0 through 254"
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
type (Protocols BGP) | type type; | [edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp
group group-name],
[edit protocols bgp group group-name],
[edit routing-instances routing-instance-name protocols bgp group group-name] | Specify the type of BGP peer group.
When configuring a BGP group, you can indicate whether the group is an IBGP group or an EBGP group.
All peers in an IBGP group are in the same AS, while peers in an EBGP group are in different ASs and
normally share a subnet. | [
{
"name": "type",
"desc": "Type of group:"
},
{
"name": "external",
"desc": "External group, which allows inter-AS BGP routing"
},
{
"name": "internal",
"desc": "Internal group, which allows intra-AS BGP routing"
}
] | 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 External BGP Point-to-Point Peer Sessions",
"Example: Configuring Internal BGP Peer Sessions",
"BGP User Guide"
] |
type (RMON Notification) | type type; | [edit snmp rmon event index] | Configure the type of notification generated when a rising or falling threshold is crossed.
Default
log-and-trap | [
{
"name": "type",
"desc": "Type of notification. It can be one of the following:"
},
{
"name": "log",
"desc": "Add an entry to the logTable object."
},
{
"name": "log-and-trap",
"desc": "Send an SNMP trap and add a log entry."
},
{
"name": "none",
"desc": "No notification... | 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"
] |
type (RMON) | type type; | [edit snmp rmon event index] | Type of notification generated when a threshold is crossed. | [
{
"name": "type",
"desc": "Type of notification:"
},
{
"name": "log",
"desc": "Add an entry to logTable."
},
{
"name": "log-and-trap",
"desc": "Send an SNMP trap and make a log entry."
},
{
"name": "none",
"desc": "No notifications are sent."
},
{
"name": "snmptra... | 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. | [
"Configure an RMON Event Entry and Its Attributes"
] |
type (Security Antivirus Feature Profile) | type (juniper-express-engine | kaspersky-lab-engine | sophos-engine); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus] | 15.1X49-D10
The 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 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. Statement updated for Sophos in
Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
... | [] |
type (Security Content Filtering Notification Options) | type (message | protocol-only); | [edit security utm default-configuration]
[edit security utm feature-profile content-filtering profile profile-name notification-options] | When content is blocked, the client generally still receives a successful response code but with modified
content (file replacement) containing a warning message. But with protocol-only notifications, a
protocol-specific error code might be returned to the client. | [
{
"name": "message",
"desc": "Send a generic notification."
},
{
"name": "protocol-only",
"desc": "Send a protocol-specific notification."
}
] | 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. | [] |
type (Security Fallback Block) | type (message | protocol-only); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name
notification-options fallback-block]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name
notification-options fallback-block]
[edit security utm featu... | 15.1X49-D10
The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-
D10 onwards. | [
{
"name": "message",
"desc": "Send a generic notification."
},
{
"name": "protocol-only",
"desc": "Send a protocol-specific notification."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5. Support for Sophos
engine added in Junos OS... | [] |
type (Security IDP Dynamic Attack Group) | type {
values [anomaly signature];
} | [edit security idp dynamic-attack-group dynamic-attack-group-name filters] | Specify an attack type filter to add attack objects based on the type of attack object (signature or
protocol anomaly). | [
{
"name": "values",
"desc": "Name of the attack type filter."
}
] | 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. | [] |
type (Security IDP ICMP Headers) | type {
match (equal | greater-than | less-than | not-equal);
value type-value;
} | [edit security idp custom-attack attack-name attack-type signature protocol icmp] | Specify the primary code that identifies the function of the request/reply. | [
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value type-value",
"desc": "Match a decimal value."
}
] | 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. | [] |
type (Security Virus Detection) | type (message | protocol-only); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name
notification-options virus-detection]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name
notification-options virus-detection]
[edit security utm fea... | 15.1X49-D10
The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-
D10 onwards. | [
{
"name": "message",
"desc": "Send a generic notification."
},
{
"name": "protocol-only",
"desc": "Send a protocol-specific notification."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5. Support for Sophos
engine added in Junos OS... | [] |
type (Security Web Filtering) | type (juniper-enhanced | juniper-local | surf-control-integrated | websense-redirect) | ng-
juniper; | [edit security utm default-configuration web-filtering]
[edit security utm feature-profile web-filtering] | 15.1X49-D10
The surf-control-integrated feature is not supported from Junos OS Release 15.1X49-D10
onwards. | [
{
"name": "juniper-enhanced",
"desc": "Enable Enhanced Web Filtering on the device."
},
{
"name": "juniper-local",
"desc": "Enable Juniper Networks local URL filtering on the device."
},
{
"name": "surf-control-integrated",
"desc": "Enable integrated Web filtering on the device."
}... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The surf-control-integrated feature is not supported from Junos OS Release 15.1X49-D10 onwards. For
previous releases, command introduced in Junos OS Release 9.5.
Command introduced in Junos OS Release 11.4 .
The [edit security utm default-configuration web-filtering] hierarchy level is introduced in Junos OS Release
1... | [] |
type (SNMP v3) | type (inform | trap); | [edit snmp v3 notify name] | Configure the type of SNMP notification. | [
{
"name": "inform",
"desc": "Defines the type of notification as an inform. SNMP informs are confirmed notifications."
},
{
"name": "trap",
"desc": "Defines the type of notification as a trap. SNMP traps are unconfirmed notifications."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
inform option added in Junos OS Release 7.4. | [] |
type (Tunnel Profile) | type tunnel-type; | [edit access tunnel-profile profile-name tunnel tunnel-id] | Specify the tunnel type (protocol).
Default
l2tp | [
{
"name": "tunnel-type",
"desc": "Tunnel protocol type. The only value currently available is l2tp."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"L2TP LAC Tunneling for Subscribers"
] |
type | type {
linux-container | virtual-machine;
} | [edit virtual-network-functions] | Type of the VNF. | [
{
"name": "linux-container",
"desc": "The VNF type is Linux container."
},
{
"name": "virtual-machine",
"desc": "The VNF type is virtual machine."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X53-D40. | [
"Understanding Virtual Network Functions",
"Managing the VNF Life Cycle"
] |
type | type type; | [edit services application-identification application application-name],
[edit services application-identification nested-application name] | Define type of application, such as HTTP or FTP. | [
{
"name": "type",
"desc": "Application type. This is a mandatory value and has a maximum length of 32 characters."
}
] | 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. | [
"Defining an Application Identification",
"Application Identification for Nested Applications"
] |
type-of-service | type-of-service service-type; | [edit services application-identification application application-name] | Define the type of service by service objective. There is no default value. | [
{
"name": "maximize-reliability",
"desc": "Service designed for maximum reliability in packet transmission."
},
{
"name": "maximize-throughput",
"desc": "Service designed for maximum throughput."
},
{
"name": "minimize-delay",
"desc": "Service designed for minimum delay in packet tra... | 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. | [
"Defining an Application Identification",
"U"
] |
uac-policy (Application Services) | uac-policy {
captive-portal captive-portal;
} | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
application-services] | Enable Unified Access Control (UAC) for the security policy. This statement is required when you are
configuring the SRX Series Firewall to act as a Junos OS Enforcer in a UAC deployment. When deployed
as a Junos OS Enforcer, the SRX Series Firewall enforces the policies that are defined on the UAC’s IC
Series UAC Appl... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.4. | [
"Understanding User Role Firewalls",
"Example: Configuring a User Role Firewall on an SRX Series Device"
] |
uac-service | uac-service {
command binary-file-path;
disable;
failover (alternate-media | other-routing-engine);
} | [edit system processes] | Specify the unified access control daemon process. | [
{
"name": "command binary-file-path",
"desc": "Path to the binary process."
},
{
"name": "disable",
"desc": "Disable the unified access control daemon process."
},
{
"name": "failover",
"desc": "Configure the device to reboot if the software process fails four times within 30 seconds... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Firewall User Authentication Overview"
] |
ucode-imem-remap | ucode-imem-remap; | [edit chassis feb slot number] | M120 routers with a single type-1 FPC mapped to an FEB support a microcode remap feature to resolve
microcode overflow resulting in bad PIC combinations.
You can enable the microcode remap by using the ucode-imem-remap statement at the [edit chassis feb slot
number] hierarchy level. The default microcode map will conti... | [] | interfaces—To view this statement in the configuration.
interfaces-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4R2. | [] |
udp (FTI) | udp {
destination {
address ipv4_address;
}
source {
address ipv4_address;
interface interface;
}
} | [edit interfaces name unit name tunnel encapsulation] | Enable UDP encapsulation with IPv4 on FTI logical interfaces. | [] | interface | Statement introduced in Junos OS Release 19.3R1. | [
"Flexible Tunnel Interfaces Overview"
] |
udp (Security IDP Protocol Binding) | udp {
minimum-port port-number <maximum-port port-number>;
} | [edit security idp custom-attack attack-name attack-type chain protocol-binding],
[edit security idp custom-attack attack-name attack-type signature protocol-binding] | Allow IDP to match the attack for specified UDP ports. | [
{
"name": "minimum-port port-number",
"desc": "Minimum port in the port range."
},
{
"name": "maximum-port port-number",
"desc": "Maximum port in the port range."
}
] | 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. | [] |
udp (Security IDP Signature Attack) | udp {
data-length {
match (equal | greater-than | less-than | not-equal);
value data-length;
}
destination-port (Security Signature Attack) {
match (equal | greater-than | less-than | not-equal);
value destination-port;
}
source-port (Security IDP) {
match (e... | [edit security idp custom-attack attack-name attack-type signature protocol] | Allow IDP to match the UDP header information for the signature attack. | [] | 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. | [] |
udp (Security Screen) | udp {
flood {
threshold number;
}
port-scan {
threshold number;
}
udp-sweep {
threshold threshold number;
}
} | [edit security screen ids-option screen-name] | Specify the number of packets allowed per second to the same destination IP address/port pair. When
the number of packets exceeds this value within any 1-second period, the device generates an alarm and
drops subsequent packets for the remainder of that second. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
udp | [edit services monitoring rpm probe-server] | Enable UDP requests for the RPM probe server.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details.
NOTE: The destination-interface statement is not supported on PTX Series routers or for
Junos OS Evolved. | [] | 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.
Statement introduced in Junos OS Evolved Release 20.1R1. | [
"Configuring RPM Receiver Servers"
] | |
udp-encapsulation | udp-encapsulation {
<udp-dest-port destination-port>;
} | [edit services service-set service-set-name ipsec-vpn-options] | Enable multiple path forwarding of IPsec traffic by adding a UDP header to the IPsec encapsulation of
packets. Doing this increases the throughput of IPsec traffic. If you do not enable UDP encapsulation, all
the IPsec traffic follows a single forward path rather than using multiple available paths. | [
{
"name": "udp-dest-port",
"desc": ""
},
{
"name": "destination-port",
"desc": "(Optional) Use the specified UDP destination port for the UDP header that is appended to the ESP encapsulation. Range: 1025 through 65536. Do not use 4500. Default: If you do not include the udp-dest-port statement... | 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 IPsec Service Sets",
"IPsec Multipath Forwarding with UDP Encapsulation"
] |
udp-port | udp-port port-number; | [edit protocols sflow collector] | Configure the UDP port for a remote collector for sFlow network traffic monitoring. The device sends
sFlow UDP datagrams to the collector for analysis. | [
{
"name": "port-number",
"desc": "UDP port number for this collector."
}
] | 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. | [
"Example: Configuring sFlow Technology to Monitor Network Traffic on EX Series Switches",
"Configuring sFlow Technology for Network Monitoring (CLI Procedure)",
"Example: Configuring sFlow Technology to Monitor Network Traffic on MX Series Routers"
] |
udp-sweep | udp-sweep {
threshold number;
} | [edit security screen ids-option screen-name udp] | Configure the device to detect and prevent UDP sweep attack. In a UDP sweep attack, an attacker sends
UDP packets to the target device. If the device responds to those packets, the attacker gets an
indication that a port in the target device is open, which makes the port vulnerable to attack. If a remote
host sends UDP... | [
{
"name": "threshold number",
"desc": "Maximum number of microseconds during which up to 10 UDP packets from the same"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
udp-tcp-port-swap | udp-tcp-port-swap; | [edit services monitoring rfc2544 tests test-name test-name] | Swap the source and destination UDP ports in the test packets. Only UDP port swap and UDP over IPv4
traffic is supported. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X53.
Statement introduced in Junos OS Evolved Release 22.4R1. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers",
"Configuring an RFC 2544-Based Benchmarking Test"
] |
uid (Dynamic Profiles) | uid; | [edit dynamic-profiles profile-name variables variable-name] | Configure a unique ID for parameterized filters in a dynamic profile created for services. The values that
the system uses for these variables are applied when the subscriber authenticates. | [] | 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. | [
"Dynamic Variables Overview"
] |
uid-reference | uid-reference; | [edit dynamic-profiles profile-name variables variable-name] | When you configure a unique ID (UID) variable, include this statement to specify that the value for the
UID is supplied by RADIUS when the subscriber authenticates. | [] | 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. | [
"Unique Identifiers for Firewall Variables",
"Configuring Unique Identifiers for Parameterized Filters",
"Dynamic Variables Overview"
] |
ukern-trace | ukern-trace {
log {
app-type dfw;
logging (off | on);
}
} | [edit chassis fpc ],
[edit chassis lcc name fpc ],
[edit chassis member name fpc ] | Enable or disable logging of all debugging firewall (DFW) ukern-trace logs on the specified FPC slot. The
CLI change takes effect immediately and persists after the FPC slot reboots. | [
{
"name": "app-type",
"desc": "Name of application with ukern-trace logs. The only supported app-type is dfw."
},
{
"name": "logging",
"desc": "Turn ukern-trace logging on or off. By default logging is on."
}
] | interface | Statement introduced in Junos OS Release 17.4 | [
"System Log Overview"
] |
ultimate-hop-popping (Protocols IS-IS) | ultimate-hop-popping; | [edit logical-systems name protocols isis source-packet-routing],
[edit logical-systems name routing-instances name protocols isis source-packet-routing],
[edit protocols isis source-packet-routing],
[edit routing-instances name protocols isis source-packet-routing], | Enable ultimate hop popping for IS-IS. IS-IS advertises a node SID with the P bit set for no penultimate–
hop–popping (PHP) in all prefix SID advertisements. | [] | 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. | [] |
ultimate-hop-popping | ultimate-hop-popping; | [edit logical-systems logical-system-name protocols mpls],
[edit logical-systems logical-system-name protocols mpls label-switched-path label-switched-path-
name],
[edit protocols mpls],
[edit protocols mpls label-switched-path label-switched-path-name] | Enable ultimate-hop popping on LSPs. Configure this statement on the device at the LSP ingress. In
ultimate-hop popping, the MPLS label is popped from the IP packet at the PE router. The IP address is
checked in a second address lookup (also at the PE router), and then the packet is forwarded to its
destination.
Be awa... | [] | 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. | [
"Configuring Ultimate-Hop Popping for LSPs"
] |
ultrahigh-power | ultrahigh-power; | [edit poe interface (all | interface-name)] | Configure a four-pair PoE port to deliver up to 95 W of power. The four-pair PoE standard allows for
power to be delivered over all four pairs of wires in a standard CAT5/6 RJ-45 Ethernet cable.
When you configure the four-pair PoE port with the ultrahigh-power option, the port provides up to 95 W
of power, even if the... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Configuring PoE Interfaces on EX Series Switches"
] |
unattended-boot | unattended-boot; | [edit system] | Set the switch to unattended mode for U-Boot to prevent unauthorized access to the system before the
JUNOS OS login prompt appears. In unattended mode, access to the loader CLI is blocked, as well as
recovery mechanisms such as password recovery by using single-user mode and booting the switch by
using a USB flash driv... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51-D20. | [
"Using Unattended Mode for U-Boot to Prevent Unauthorized Access"
] |
unconditional-src-learn | unconditional-src-learn; | [edit interfaces interface-name unit logical-unit-number family inet] | Enables the router to learn IP addresses from nonvalidated sources when proxy Address Resolution
Protocol (ARP) is configured.
CAUTION: By default, the router learns IP addresses from validated sources only. When
this statement is configured and proxy ARP is enabled on an unnumbered interface, the
router responds to AR... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4R16. | [
"Understanding Proxy ARP",
"Example: Configuring Proxy ARP on an EX Series Switch"
] |
unconfigured-peer-graceful-restart | unconfigured-peer-graceful-restart; | [edit protocols bgp] | When set protocols bgp group group-name allow network is configured to accept dynamic BGP sessions,
unconfigured-peer-graceful-restart statement should be configured to avoid traffic drop during graceful
restart or graceful Routing Engine switchover. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [] |
underlying-interface (ANCP) | underlying-interface underlying-interface-name; | [edit protocols ancp interfaces interface-set interface-set-name] | Configure the underlying interface on which the VLAN demux interface is running. The VLAN demux
interface is the underlying interface for the PPPoE sessions controlled by ANCP. | [
{
"name": "underlying-interface-name",
"desc": "Name of the underlying interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"ANCP Agent Neighbors and Operations",
"ANCP Agent Neighbors and Operations"
] |
underlying-interface (demux0) | underlying-interface underlying-interface-name; | [edit dynamic-profiles profile-name interfaces demux0 interface-name unit unit logical-unit-number
demux-options] | Configure the underlying interface on which the demultiplexing (demux) interface is running.
CAUTION: Before you make any changes to the underlying interface for a demux0
interface, you must ensure that no subscribers are currently present on that underlying
interface. If any subscribers are present, you must remove th... | [
{
"name": "underlying-interface-name",
"desc": "Either the specific name of the interface on which the DHCP discover packet"
}
] | 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.
Support for aggregated Ethernet introduced in Junos OS Release 9.4. | [
"Configuring Dynamic Subscriber Interfaces Using IP Demux Interfaces in Dynamic Profiles",
"Configuring Dynamic Subscriber Interfaces Using VLAN Demux Interfaces in Dynamic Profiles",
"Dynamic PPPoE Subscriber Interfaces over Static Underlying Interfaces Overview",
"Junos OS Network Interfaces Library for Rou... |
underlying-interface (Dynamic PPPoE) | underlying-interface interface-name; | [edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit pppoe-options] | In a dynamic profile, configure the underlying interface on which the router creates the dynamic PPPoE
logical interface. | [
{
"name": "interface-name",
"desc": "Variable used to specify the name of the underlying interface on which the PPPoE logical"
}
] | 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"
] |
underlying-interface | underlying-interface interface-name; | [edit interfaces pp0 unit logical-unit-number pppoe-options],
[edit interfaces demux0 unit logical-unit-number demux-options],
[edit logical-systems logical-system-name interfaces demux0 unit logical-unit-number demux-
options],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number pppoe-opt... | Configure the interface on which PPP over Ethernet is running.
For demux interfaces, configure the underlying interface on which the demultiplexing (demux) interface
is running. | [
{
"name": "interface-name",
"desc": "Name of the interface on which PPP over Ethernet or demux is running. For example,"
}
] | 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.
Support for aggregated Ethernet added in Junos OS Release 9.4. | [
"Configuring an IP Demultiplexing Interface",
"Configuring a VLAN Demultiplexing Interface",
"Configuring the PPPoE Underlying Interface"
] |
unframed | no-unframed (Interfaces) | (unframed | no-unframed); | [edit interfaces interface-name t3-options] | Enable or disable framing for the T3 interface on a 1-Port Clear Channel DS3/E3 GPIM on an SRX Series
Firewall. By default, unframed mode is enabled. Select no-unframed to enable framing. Select unframed
to return to the default mode. | [] | 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. | [
"Example: Configuring a T3 Interface"
] |
unicast (Route Target Community) | unicast {
receiver;
sender;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols mvpn
route-target import-target],
[edit routing-instances routing-instance-name protocols mvpn route-target import-target] | Specify the same target community configured for unicast. | [
{
"name": "receiver",
"desc": "Specify the unicast target community used when importing receiver site routes."
},
{
"name": "sender",
"desc": "Specify the unicast target community used when importing sender site routes."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [
"Configuring VRF Route Targets for Routing Instances for an MBGP MVPN"
] |
unicast (Virtual Tunnel in Routing Instances) | unicast; | [edit logical-systems logical-system-name routing-instances routing-instance-name interface vt-
fpc/pic/port.unit-number],
[edit routing-instances routing-instance-name interface vt-fpc/pic/port.unit-number] | In a multiprotocol BGP (MBGP) multicast VPN (MVPN), configure the virtual tunnel (VT) interface to be
used for unicast traffic only.
Default
If you omit this statement, the VT interface can be used for both multicast and unicast traffic. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Example: Configuring Redundant Virtual Tunnel Interfaces in MBGP MVPNs",
"Example: Configuring MBGP MVPN Extranets"
] |
unicast-ethernet | unicast-ethernet {
destination-mac destination-mac-address destination-mac-mask destination-mac-mask;
ethertype ethertype;
source-mac source-mac-address source-mac-mask source-mac-mask;
} | [edit protocols oam fabric flow-specs flow-specification-name] | Configure unicast Ethernet parameters for a flow specification used in internal fabric monitoring. | [
{
"name": "destination-mac",
"desc": ""
},
{
"name": "destination-mac-address",
"desc": "(Optional) MAC address of the destination fabric maintenance endpoint (FMEP) that is configured in the flow specification."
},
{
"name": "destination-mac-mask destination-",
"desc": ""
},
{
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Overview of Internal Fabric Monitoring",
"Configuring a Fabric Maintenance Association",
"Configuring Flow Specifications"
] |
unicast-ethernet-ipv4 | unicast-ethernet-ipv4 {
source-ip source-ip-address source-ip-mask source-ip-mask;
destination-ip destination-ip-address destination-ip-mask destination-ip-mask;
ip-proto protocol;
source-l4-port source-l4-port-number;
destination-l4-port destination-l4-port-number;
} | [edit protocols oam fabric flow-specs flow-specification-name] | Configure unicast parameters for the Ethernet IPv4 protocol type in the internal fabric monitoring flow
specifications. | [
{
"name": "destination-ip",
"desc": ""
},
{
"name": "destination-ip-address",
"desc": "Unicast IPv4 address of the destination fabric maintenance endpoint (FMEP) that is configured in the fabric maintenance association (FMA). Syntax: Dotted decimal notation without the prefix"
},
{
"nam... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Overview of Internal Fabric Monitoring",
"Configuring a Fabric Maintenance Association",
"Configuring Flow Specifications"
] |
unicast-in-lpm | unicast-in-lpm; | [edit chassis forwarding-options lpm-profile] | For the Unified Forwarding Table feature, specify to store all unicast IPv4 and IPv6 entries with prefixes
with lengths equal to or less than 64 in the table for longest prefix match (LPM) entries, thereby freeing
up space in the Layer 3 host table. Only unicast entries can be moved to the LPM table. Multicast
entries ... | [] | 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-D30. | [
"Understanding the Unified Forwarding Table"
] |
unicast-mode | unicast-mode {
clock-source ip-address {
local-ip-address local-ip-address;
asymmetry number;
}
transport ipv4;
clock-ipv6-source master-ipv6-address {
local-ip-address local-ip-address;
}
transport ipv6;
}
ACX710
unicast-mode {
announce-timeout announc... | [edit protocols ptp client interface interface-name] | Configure the timeReceiver in unicast mode. You can set this option when PTP unicast mode of
messaging is needed. | [
{
"name": "announce-timeout-value",
"desc": "The announce timeout value for announce interval messages. Range: 3 through 10 Default: 3"
},
{
"name": "grantor",
"desc": "Specify that the selected interface port can be grantor. The grantor attribute enables the port to allow for the grant-port p... | 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. | [
"Configuring Precision Time Protocol",
"Example: Configuring Precision Time Protocol",
"Precision Time Protocol Overview",
"IEEE 1588v2 Precision Timing Protocol (PTP)"
] |
unicast-negotiation | unicast-negotiation; | [edit protocols ptp] | Configure unicast negotiation. Unicast negotiation is a method by which the announce, synchronization,
and delay response packet rates are negotiated between the timeTransmitter and the timeReceiver
before a PTP session is established.
For G.8275.2 profile, a maximum of -3 can be set for announce, and -4 can be set for... | [] | 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. | [
"No Link Title",
"Configuring Precision Time Protocol",
"Example: Configuring Precision Time Protocol",
"Precision Time Protocol Overview",
"IEEE 1588v2 Precision Timing Protocol (PTP)"
] |
unicast-reverse-path | unicast-reverse-path (active-paths | feasible-paths); | [edit logical-systems logical-system-name routing-options forwarding-table],
[edit routing-instances routing-instance-name instance-type name routing-options forwarding-
table],
[edit routing-options forwarding-table] | Control the operation of unicast reverse-path-forwarding check. This statement enables the RPF check
to be used when routing is asymmetrical. | [
{
"name": "active-paths",
"desc": "Consider only active paths during the unicast reverse-path check."
},
{
"name": "feasible-paths",
"desc": "Consider all feasible paths during the unicast reverse-path check."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for routing instances added in Junos OS Release 8.3.
NOTE: This feature is not supported on the EX4300 switch, even though it is available
on the device. | [
"Example: Configuring Unicast RPF (On a Router)",
"Enabling Unicast Reverse-Path Forwarding Check for VPNs"
] |
unicast-stream-limit (Protocols AMT) | unicast-stream-limit ; | [edit logical-systems logical-system-name protocols amt relay],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols amt
relay],
[edit protocols amt relay],
[edit routing-instances routing-instance-name protocols amt relay] | Set the upper limit for unicast streams (s,g intf). | [
{
"name": "number",
"desc": "Maximum number of data unicast streams that can be created on the system."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring the AMT Protocol"
] |
unicast-tunnel-name-regular-expression | unicast-tunnel-name-regular-expression {
preferred;
regular-expression;
} | [edit logical-systems name routing-instances name provider-tunnel ingress-replication],
[edit logical-systems name tenants name routing-instances name provider-tunnel ingress-
replication],
[edit routing-instances name provider-tunnel ingress-replication],
[edit tenants name routing-instances name provider-tunnel ingre... | Configure a regular expression for a unicast tunnel to match specific RSVP tunnel LSP names.
NOTE: Regular expressions support 1000 existing P2P LSPs using the default inet.3
table. | [
{
"name": "preferred",
"desc": "Fall-back to default behavior of selecting the active LSP."
},
{
"name": "regular-expression",
"desc": "Regular expression to match unicast tunnels to RSVP tunnel LSP names."
}
] | Statement introduced in Junos OS Release 24.4R1. | [] | |
unicast-umh-election | unicast-umh-election; | [edit routing-instances routing-instance-name protocols mvpn] | Configure a router to use the unicast route preference to determine the single forwarder election. | [] | 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. | [
"Example: Configuring a PIM-SSM Provider Tunnel for an MBGP MVPN"
] |
unidirectional | unidirectional; | [edit interfaces interface-name],
[edit logical-systems logical-system-name interfaces interface-name] | Create two new, unidirectional (transmit-only and receive-only) physical interfaces subordinate to the
original parent interface. Unidirectional links are currently supported only on 10-Gigabit Ethernet
interfaces on the following hardware:
•
4-port 10-Gigabit Ethernet DPC on the MX960 router
•
10–Gigabit Ethernet IQ2 ... | [] | 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. | [
"Understanding Unidirectional Traffic Flow on Physical Interfaces",
"Enabling Unidirectional Traffic Flow on Physical Interfaces"
] |
unidirectional-session-refreshing | unidirectional-session-refreshing; | [edit security zones security-zone] | Use unidirectional session refreshing on a zone to enable two options for a session. Refresh a session by
any packet from any directions. This is a default behavior. Refresh a session by only the packets in the
initial direction.
NOTE: USR (Unidirectional Session Refresh) is skipped for PPTP and IKE ALG data
sessions i... | [] | security | Statement introduced in Junos OS Release 20.4R1. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.