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 |
|---|---|---|---|---|---|---|---|
tcp-tickles | tcp-tickles tcp-tickles; | [edit interfaces interface-name services-options] | Define the maximum number of keep-alive messages sent before a TCP session is allowed to timeout. | [
{
"name": "tcp-tickles",
"desc": "Number of keep-alive messages."
}
] | 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. | [
"Configuring Default Timeout Settings for Services Interfaces"
] |
tcp-winnuke-check (IDS MS-MPC) | tcp-winnuke-check; | [edit services ids rule rule-name term term-name then] | Identify and drop TCP segments that are destined for port 139 and have the urgent (URG) flag set,
which provides protection against WinNuke attacks. This statement can only be used in IDS rules
assigned to a service set on an MS-MPC. | [] | 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 Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
tcpao-auth-mismatch | tcpao-auth-mismatch {
allow-without-tcpao;
} | [edit fabric protocols bgp]
[edit logical-systems name protocols bgp]
[edit logical-systems name routing-instances name protocols bgp]
[edit logical-systems name tenants name routing-instances name protocols bgp]
[edit routing-instances name protocols bgp]
[edit tenants name routing-instances name protocols bgp]
[edit ... | Continue without TCP-AO if any one TCP endpoint does not have TCP-AO configured. | [
{
"name": "allow-without-tcpao",
"desc": "Allow the connection establishment without TCP-AO."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1. | [
"TCP Authentication Option (TCP-AO)"
] |
tdf (Unified Edge) | tdf gateway-name; | [edit unified-edge gateways] | Specify the name to be used for the traffic detection function (TDF) gateway. | [
{
"name": "gateway-name",
"desc": "Name of the gateway. Range: 1 through 16 characters."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"TDF Gateway Service PICs and Session PICs for Subscriber-Aware Traffic Treatment"
] |
tdf-interface | tdf-interface mif.number; | [edit unified-edge gateways tdf gateway-name domains domain-name] | Specify the TDF interface that the TDF domain uses. A TDF interface is different from other types of
interfaces, and is associated with the TDF service set that is used for the TDF subscriber.
NOTE: The TDF interface must have been previously configured at the [edit interfaces]
hierarchy level.
The TDF interface and th... | [
{
"name": "mif.number",
"desc": "Use the specified TDF interface unit number."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring a Set of IP-Based TDF Subscriber Properties with a TDF Domain",
"Understanding the Definition of a Set of IP-Based Subscriber Properties with a TDF Domain",
"IP-Based Subscriber Setup Overview",
"Configuring TDF Interface to Access Interface Associations in VRFs",
"Configuring TDF Interface to ... |
tdm-options | tdm-options {
ces-psn-channel {
dmac-address dmac-address;
mode (MEF8 | MPLS);
vlan-id-1 vlan-id-1;
vlan-id-2 vlan-id-2;
}
ces-psn-port-channel-id-override-disable;
ces-psn-port-dmac-check-enable;
channel-params {
name... | [edit interfaces interface],
[edit interfaces interface-range] | [
{
"name": "ces-psn-port-channel-id-override-disable",
"desc": "Disable Channel identifier override smart SFP"
},
{
"name": "ces-psn-port-dmac-check-enable",
"desc": "Enable DMAC check on smart SFP"
},
{
"name": "sfp-type",
"desc": "Smart SFP type"
},
{
"name": "CHAN-STM1",
... | [none specified] | Statement introduced in Junos OS Evolved Release 25.4R1 | [] | |
tdm-options (Interfaces) | tdm-options {
ces-psn-channel ...
ces-psn-port-dmac-check-enable ;
iwf-params...
sfp-type sfptype;
tdm-in-loop ;
tdm-out-loop ;
} | [edit interfaces interface-name] | Configure TDM options to enable the smart SFP to encapsulate PDH (Plesiochronous Digital Hierarchy)
and SDH (synchronous Digital Hierarchy) traffic over packet switched networks (PSNs). | [
{
"name": "ces-psn-port-dmac-check-",
"desc": ""
},
{
"name": "enable",
"desc": "Enables checking of the destination MAC address of the incoming packets on the receiving SFP. If you have configured the destination MAC address using the dmac-address option, use this option to verify the MAC addre... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4. | [] |
te-class-matrix | te-class-matrix {
tenumber {
priority priority;
traffic-class {
ctnumber priority priority;
}
}
} | [edit logical-systems logical-system-name protocols mpls diffserv-te],
[edit protocols mpls diffserv-te] | Specify the traffic engineering class matrix for a multiclass LSP or a DiffServ-aware traffic engineering
LSP.
Default
The default traffic engineering class matrix is:
te-class-matrix {
te0 traffic-class ct0 priority 7;
te1 traffic-class ct1 priority 7;
te2 traffic-class ct2 priority 7;
te3 traffic-clas... | [
{
"name": "ctnumber",
"desc": "Specify the number of the class type. It can be one of four values: ct0, ct1, ct2, or ct3."
},
{
"name": "priority priority",
"desc": "Specify the priority of the class type. It can be one of eight values from 0 through 7."
},
{
"name": "tenumber",
"des... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Traffic Engineering Classes"
] |
te-link | te-link te-link-name {
disable;
ethernet-vlan;
interface interface-name {
disable;
local-address ip-address;
remote-address ip-address;
remote-id id-number;
}
local-address ip-address;
remote-address ip-address;
remote-id id-number;
} | [edit protocols link-management],
[edit protocols link-management peer peer-name] | Represent a collection of physical ports or time slots. Assign a traffic engineering link to the specified
network peer. | [
{
"name": "te-link-name",
"desc": "Name of the collection of physical ports or the name of the time slots."
},
{
"name": "disable",
"desc": "Disable the traffic engineering link or an interface to a traffic engineering link."
}
] | 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.
ethernet-vlan option introduced in Junos OS Release 14.2. | [
"Configuring LMP Traffic Engineering Links"
] |
te-policy | te-policy {
apply-groups
apply-groups-except
groups
node-as
router-id
spring-te
|
} | [edit policy-options policy-statement name from traffic-engineering] | Specify traffic engineering related parameters. | [
{
"name": "node-as",
"desc": "Node AS number"
},
{
"name": "router-id",
"desc": "Router ID to match against the node added by TE policy"
},
{
"name": "spring-te",
"desc": ""
},
{
"name": "SPRING-TE policy related parameters",
"desc": ""
}
] | routing | [
"Link-State Distribution using BGP"
] | |
tear-drop (IDS Screen Next Gen Services) | tear-drop; | [edit services screen ids-option screen-name ip] | Identify and drop fragmented IP packets that overlap, which protects against teardrop attacks. In
teardrop attacks, the target machine uses up its resources as it attempts to reassemble the packets, and
then it can no longer process valid traffic. | [] | 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"
] |
tei-option | tei-option (first-call | power-up); | [edit interfaces br-pim/0/portisdn-options] | For ISDN interfaces, configure when the Terminal Endpoint Identifier (TEI) negotiates with the ISDN
provider. | [
{
"name": "first-call",
"desc": "Activation does not occur until the call setup is sent."
},
{
"name": "power-up",
"desc": "Activation occurs when the Services Router is powered on."
}
] | 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. | [] |
telemetries (PoE) | telemetries {
disable;
duration hours;
interval minutes;
} | [edit poe interface (all | interface-name)] | Allow logging of per-port PoE power consumption. The telemetries section must be explicitly specified
to enable logging. If left unspecified, telemetries is disabled by default.
Default
If the telemetries statement is specified, logging is enabled with the default values for interval and
duration. | [] | 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. | [] |
telemetries | telemetries {
disable;
duration hours;
interval minutes;
} | [edit poe interface (all | interface-name)] | Enable the logging of power consumption of a PoE interface over time.
If you want to log the power consumption of a PoE interface, you must explicitly specify the telemetries
statement. When you commit the configuration, logging begins, with data being collected at the
specified intervals. Logging stops at the end of t... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Statement introduced in Junos OS Release 12.2 for ACX2000 Universal Metro Routers. | [
"Configuring PoE Interfaces on EX Series Switches"
] |
telemetry | telemetry {
subscriber-statistics;
service-statistics;
}
interfaces junos-interface-name {
unit "$junos-interface-unit" {
family [inet | inet6] {
filter {
input "inputFilter";
output "outputFilter";
}
... | [edit dynamic-profiles profile-name] | Enable telemetry collection of subscriber statistics and queue statistics.
Include the subscriber-statistics statement to enable the export of subscriber statistics through
telemetry. When this statement is configured, you must also include the actual-transit-statistics
statement at the [edit dynamic-profiles profile-n... | [
{
"name": "subscriber-statistics",
"desc": "Enable the export of interface meta-data and export of subscriber accurate statistics. When this statement is configured, you must also include the actual-transit-statistics statement at the [edit dynamic-profiles profile-name interfaces interface-name unit unit-n... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS 18.4. | [
"Enable Export of Subscriber Statistics and Queue Statistics",
"Understanding Enabling Export of Subscriber Statistics and Queue Statistics for Dynamic Interfaces",
"and Interface-Sets",
"Guidelines for Exporting Subscriber Statistics and Queue Statistics for Dynamic Interfaces and",
"Interface-Sets",
"Gu... |
telemetry | telemetry {
statistics{
no-ingress;
no-transit;
}
} | [edit logical-systems name protocols source-packet-routing],
[edit protocols source-packet-routing] | Enable telemetry on segment routing traffic engineering policies at ingress nodes. Junos OS creates the
following sensors to collect traffic statistics for segment routing:
•
BGP-SRTE policies for ingress routes, sensors are attached to nexthops in inet{6}color.0 table.
•
Static SRTE policies for ingress routes, sensor... | [
{
"name": "statistics",
"desc": "Enable collection of traffic statistics on segment routing traffic engineering policies."
}
] | routing | Statement introduced in Junos OS Release 18.3R1. | [
"Segment Routing Traffic Engineering at BGP Ingress Peer Overview"
] |
telnet (Access) | telnet {
banner {
fail string;
login string;
success string;
}
} | [edit access firewall-authentication pass-through] | Configure banners for Telnet login prompt, successful authentication, and failed authentication. | [] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [
"SRX Firewall Users",
"Obtaining Username and Role Information Through Firewall Authentication"
] |
telnet (Services) | telnet {
authentication-order [authentication-methods];
connection-limit limit;
rate-limit limit;
} | [edit system services] | Provide Telnet connections from remote systems to the local device. | [
{
"name": "authentication-order",
"desc": ""
},
{
"name": "[authentication-methods",
"desc": "Configure the order in which the software tries different user authentication methods when attempting to authenticate a user. For each login attempt, the software tries the authentication methods in ord... | 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.
Option ldaps introduced in Junos OS Release 20.2R1. | [
"Configuring Telnet Service for Remote Access to a Router or Switch",
"Junos OS User Authentication Methods"
] |
telnet | telnet host
<8bit>
<inet | inet6>
<port port-number>
<routing-instance routing-instance-name> | Open a telnet session to a remote system. Type Ctrl+] to escape from the telnet session to the telnet
command level, and then type quit to exit from telnet.
NOTE: For Junos OS Evolved, use the routing-instance mgmt_junos option to access a
remote system through the management interface. | [
{
"name": "host",
"desc": "Name or address of the remote system."
},
{
"name": "8bit",
"desc": "(Optional) Use an 8-bit data path."
},
{
"name": "bypass-routing",
"desc": "(Optional) Bypass the normal routing tables and send ping requests directly to a system on an attached network. ... | network
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
telnet
user@host> telnet 192.154.1.254
Trying 192.154.169.254...
Connected to level5.company.net.
Escape character is '^]'.
ttypa
login: | Command introduced before Junos OS Release 7.4.
The following options are deprecated in Junos OS Evolved Release 18.3R1: bypass-routing, interface, no-
resolve, and source.
The command tenant option is introduced in Junos OS Release 19.2R1 for SRX Series. | [] | |
temperature-sensor | temperature-sensor sensor-name {
temperature-threshold {
fans-on-full-speed fans-full-speed-temp;
fans-on-full-speed-if-failed-fan full-speed-failed-fan-temp;
fans-on-intermediate-speed fans-intermediate-speed-temp;
fans-to-normal-speed fans-normal-speed-temp;
fire-shutdown f... | [edit chassis cb 0]
[edit chassis fpc fpc_number] | fire-shutdown fire-shutdown-temp
Temperature threshold beyond which Junos triggers a fire
shutdown.
red-alarm red-alarm-temp
Temperature threshold beyond which Junos triggers a red alarm
alert.
red-alarm-if-failed-fan red-alarm-failed-fan-
temp
Temperature threshold beyond which Junos triggers a red alarm
when any fan ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.3R1. | [
"Hardware Compatibility Tool"
] |
template (Flow Monitoring IPFIX Version) | template template-name {
data-record-fields {
include-policy-map-name;
source-prefix-as-path count;
destination-prefix-as-path count;
bgp-source-standard-community count;
bgp-destination-standard-community count;
bgp-source-extended-community count;
bgp-dest... | [edit services flow-monitoring version-ipfix] | Specify the IPFIX output template properties to support flow monitoring. | [
{
"name": "template-name",
"desc": "Name of the IPFIX template."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2.
data-record-fields option introduced in Junos OS Evolved Release 21.4R1.
multi-bgp-path option added in Junos OS Release 24.2R1.
include-policy-map-name option added in Junos OS Evolved 24.4R1. | [
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250",
"Configuring Inline J-Flow to Use IPFIX Flow Templates on MX, vMX and T Series Routers, EX Series",
"Switches, NFX Series Devices, and SRX Devices"
] |
template (Flow Monitoring Version 9) | template template-name {
flow-active-timeout seconds;
flow-inactive-timeout seconds;
flow-key {
flow-direction;
vlan-id;
output-interface;
}
(bridge-template|ipv4-template | ipv6-template | mpls-template |vpls-template label-position
[ positions ] | mpls-ipv4-template label... | [edit services flow-monitoring version9] | Specify the version 9 output template properties to support flow monitoring. | [
{
"name": "template-name",
"desc": "Name of the version 9 template."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3.
multi-bgp-path option added in Junos OS Release 24.2R1. | [
"Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9",
"Flow Templates"
] |
template (Forwarding Options Version IPFIX) | template; | [edit forwarding-options sampling instance family (inet | inet6 | mpls | vpls) output flow-
server hostname version-ipfix] | Specify flow monitoring version IPFIX properties to apply to output sampling records. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250",
"Configuring Inline J-Flow to Use IPFIX Flow Templates on MX, vMX and T Series Routers, EX Series",
"Switches, NFX Series Devices, and SRX Devices"
] |
template (Forwarding Options) | template template-name; | [edit forwarding-options sampling instance instance-name family (inet |inet6 |mpls) output flow-
server hostname version9],
[edit forwarding-options sampling family (inet |inet6 |mpls) output flow-server hostname version9] | Specify flow monitoring version 9 template to be used for output of sampling records. | [
{
"name": "template-name",
"desc": "Name of the version 9 template."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9",
"Flow Templates"
] |
template (Inline Monitoring) | template name {
observation-domain-id observation-domain-id;
option-template-refresh-rate seconds;
primary-data-record-fields name;
template-refresh-rate seconds;
} | [edit services inline-monitoring] | Configure template for inline monitoring services. | [
{
"name": "name",
"desc": "Name of the template."
},
{
"name": "flow-inactive-timeout",
"desc": ""
},
{
"name": "seconds",
"desc": "(EX switches only) Configure the inactive-timeout period for a flow, in seconds, for flow-based telemetry. Once there is no active traffic for a flow, t... | 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.
flow-inactive-timeout and flow-monitoring options introduced in Junos OS Release 21.1R1.
primary-data-record-fields option introduced in Junos OS Release 21.2R1.
Statement introduced in Junos OS Evolved Release 22.2R1 for PTX Series routers.
template-type option introdu... | [
"Inline Monitoring Services",
"Flow-Based Telemetry",
"Flow-Based Telemetry for VXLANs"
] |
template (LRF Profile) | template template-name {
format ipfix;
template-tx-interval tx-time;
template-type template-type;
trigger-type (session-close | volume);
} | [edit services lrf profile profile-name] | Configure a template, which specifies a set of data to be transmitted. This template can be specified in
LRF rules. | [
{
"name": "template-name",
"desc": "Name for the template. Range: Up to 32 characters. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support for Next Gen Services introduced in Junos OS Release 19.3R1 on MX Series. | [
"Configuring Logging and Reporting for Junos OS Subscriber Aware",
"Configuring an LRF Profile for Subscribers",
"Configuring Logging and Reporting for Subscriber Management"
] |
template (LRF Rule) | template template-name; | [edit services lrf profile profile-name rule lrf-rule-name then report] | Specify the template that identifies the type of data to report if the LRF rule is matched. | [
{
"name": "template-name",
"desc": "Name of the template that is used. The referenced template must be configured. Range: Up to 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 17.1.
Support for Next Gen Services introduced in Junos OS Release 19.3R1 on MX Series. | [
"Configuring Logging and Reporting for Junos OS Subscriber Aware",
"Configuring an LRF Profile for Subscribers",
"Configuring Logging and Reporting for Subscriber Management"
] |
template (Services 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-address2 ip-addr... | [edit services url-filter profile profile-name] | Configure a URL filter template.
NOTE: Starting in Junos OS Release 18.3R1, the template statement is deprecated and
has been replaced by the url-filter-template statement. The template statement is
supported for backward compatibility. | [
{
"name": "template-name",
"desc": "Name of the 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."
},
{
"name":... | 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.
disable-url-filtering option introduced in Junos OS Release 17.2R2 and 17.4R1. | [
"Configuring URL Filtering"
] |
template | template; | [edit logical-systems logical-system-name protocols mpls label-switched-path p2mp-lsp-template-
name],
[edit protocols mpls label-switched-path p2mp-lsp-template-name] | Specify a template for the dynamically generated point-to-multipoint LSPs used for VPLS flooding. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Configuring Dynamic Point-to-Multipoint Flooding LSPs with a Preconfigured Template"
] |
template-id | template-id id; | [edit services flow-monitoring version9 template template-name],
[edit services flow-monitoring version-ipfix template template-name] | Define a template ID to be used for flow aggregation of version 9 and IPFIX flows.
MX and QFX Series
The template ID can be a value in the range of 1024 through 65535. If you do not configure a value for
the template ID, a default value is assumed for this ID, which is different for the various address families.
If you... | [
{
"name": "id",
"desc": "Unique identifier for the template to be used for version 9 or IPFIX flows. The range 0-255 is"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1.
Statement introduced in Junos OS Evolved Release 22.4R1. | [
"Configuring Observation Domain ID and Source ID for Version 9 and IPFIX Flows",
"Configuring Template ID and Options Template ID for Version 9 and IPFIX Flows"
] |
template-profile (Flow Monitoring Logs for NAT) | template-profile template-profile-name; | [edit services jflow-log],
[edit services service-set service-set-name jflow-log] | Specify the name of the flow template profile to be used for generating flow monitoring format
messages for NAT events and for transmitting them to the collector. You can define a template profile
for the Jflow service by using this statement at the [edit services jflow-log] hierarchy level, and associate
the template ... | [
{
"name": "template-profile-name",
"desc": "Name of the flow template profile for NAT events. The name can be up to 32"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding NAT Event Logging in Flow Monitoring Format on an MX Series Router or NFX250",
"Configuring Log Generation of NAT Events in Flow Monitoring Record Format on an MX Series",
"Router or NFX250",
"Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats",
"Exa... |
template(Protocols MVPN) | template template-name {
all-regions {
incoming;
ingress-replication {
create-new-ucast-tunnel;
label-switched-path {
label-switched-path-template (Multicast) {
(default-template | lsp-template-name);
}
}
... | [edit protocols mvpn inter-region-template] | A template is configured on a transit area boundary router (ABR) to define the tunnel type for each
region. If a template is not configured on the ABR then the ABR simply reflects the routes without
performing any inter-region segmentation.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Segmented Inter-Area Point-to-Multipoint Label-Switched Paths Overview",
"Example: Configuring Segmented Inter-Area P2MP LSP",
"Configuring Segmented Inter-Area P2MP LSP"
] |
template-refresh-rate (Services) | template-refresh-rate; | [edit services flow-monitoring version9 template template-name] | Specify the template refresh rate. | [
{
"name": "packets",
"desc": "Specify the number of packets. The range is from 1 through 480,000."
},
{
"name": "seconds",
"desc": "Specify the number of seconds. The range is from 10 through 600."
}
] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Understanding Interfaces"
] |
template-refresh-rate | template-refresh-rate packets packets seconds seconds; | [edit services flow-monitoring version9 template template-name],
[edit services flow-monitoring version-ipfix template template-name] | Specify the frequency at which the flow generator sends updates about template definitions to the flow
collector. Specify either the number of packets or the number of seconds. | [
{
"name": "packets",
"desc": "Refresh rate, in number of packets."
},
{
"name": "seconds",
"desc": "Refresh rate, in number of 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.3.
Support at the [edit services flow-monitoring version-ipfix template template-name] hierarchy level added in
Junos OS Release 10.2.
Support at the [edit services flow-monitoring version9 template template-name] hierarchy level added in Junos
OS Release 16.1 for MPLS traffic... | [
"Configuring Flow Aggregation on MX, M, vMX and T Series Routers and NFX250 to Use Version 9",
"Flow Templates",
"Configuring Inline J-Flow to Use IPFIX Flow Templates on MX, vMX and T Series Routers, EX Series",
"Switches, NFX Series Devices, and SRX Devices"
] |
template-tx-interval (LRF Profile) | template-tx-interval tx-time; | [edit services lrf profile profile-name template template-name] | Configure the interval at which to retransmit the template to the collector. | [
{
"name": "tx-time",
"desc": "Time interval in seconds. Default: 60 Range: 10 through 600"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support for Next Gen Services introduced in Junos OS Release 19.3R1 on MX Series. | [
"Configuring Logging and Reporting for Junos OS Subscriber Aware",
"Configuring an LRF Profile for Subscribers",
"Configuring Logging and Reporting for Subscriber Management"
] |
template-type (Flow Monitoring Logs for NAT) | template-type nat; | [edit services jflow-log template-profile template–profile-name] | Specify the type of service for which flow template profiles, in version or IPFIX format, must be used for
generating flow monitoring format messages for NAT events and for transmitting them to the collector.
Currently, you can configure only NAT events or services for generation of log messages in flow
monitoring form... | [
{
"name": "nat",
"desc": "Use flow template profiles for generation of flow monitoring logs for NAT events."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding NAT Event Logging in Flow Monitoring Format on an MX Series Router or NFX250",
"Configuring Log Generation of NAT Events in Flow Monitoring Record Format on an MX Series",
"Router or NFX250",
"Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats",
"Exa... |
template-type (LRF Profile) | template-type template-type; | [edit services lrf profile profile-name template template-name] | Configure the template types for the template, which specify the data fields to include. You must
configure at least one type, and you can configure multiple types.
If Next Gen Services is enabled, then the template types dns, ifl-subscriber, ipv4-extended, ipv6-extended,
mobile-subscriber, video, and wireline-subscrib... | [
{
"name": "template-type",
"desc": "Template type. You must configure at least one of the following types, and you can"
},
{
"name": "configure multiple types:",
"desc": ""
},
{
"name": "device-data",
"desc": "Use data fields specific to the device collecting the logging feed."
},
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support for Next Gen Services introduced in Junos OS Release 19.3R1 on MX Series. | [
"Configuring Logging and Reporting for Junos OS Subscriber Aware",
"Configuring an LRF Profile for Subscribers",
"Configuring Logging and Reporting for Subscriber Management"
] |
templates | templates {
template-name {
interval-duration interval-duration;
inactive-timeout inactive-timeout;
rate {
(layer3 layer3-packets-per-second | media media-bits-per-second);
}
delay-factor {
;
threshold {
(info | warning | cr... | [edit services video-monitoring] | Configure the media delivery index template containing the measurement parameters for video
monitoring. | [
{
"name": "delay-factor",
"desc": "Define delay factor syslog threshold levels."
},
{
"name": "delay-factor-threshold",
"desc": "Delay factor threshold in milliseconds. When the threshold is exceeded, a syslog message is generated."
},
{
"name": "Default: 0",
"desc": "Do not generate... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Configuring Inline Video Monitoring on MX Series Routers"
] |
term (Application Aware Access List) | term term-name {
from {
application-group-any;
application-groups [ application-group-names ];
application-unknown;
applications [ application-names ];
destination-address address <any-unicast>;
destination-address-range low minimum-value high maximum-value;
d... | [edit services aacl rule rule-name] | Define the AACL term properties. | [
{
"name": "term-name",
"desc": "Identifier for the term."
}
] | 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 AACL Rules | [
"No Link Title"
] |
term (Applications) | term term-name {
alg application;
destination-port port-identifier;
icmp-code value;
icmp-type value;
icmp6-code value;
icmp6-type value;
inactivity-timeout (seconds | never);
protocol number;
rpc-program-number number;
source-port port-number;
uuid hex-value;
} | [edit applications application application-name] | Define individual application protocols. | [] | 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. | [
"Security Policy Applications Overview"
] |
term (candidate-uplink-policy) | term term-name{
from {
product-model model-name;
<holddown holddown-time>;
<minimum-links number-of-links>;
<uplink-port-group uplink-port-group-name>;
}
} | [edit policy-options satellite-policies candidate-uplink-port-profile policy-name] | Create and configure a term in a candidate uplink satellite policy within a Junos Fusion.
A term in a candidate uplink port policy in a Junos Fusion is used to apply an uplink failure detection
configuration to certain satellite devices, based on their product model only. The more complex options
that are available for... | [
{
"name": "term-name",
"desc": "The user-defined name of the term. A term is a named structure in which match conditions and configuration statements are defined. A candidate uplink policy policy can contain multiple terms. The terms are evaluated in the order they appear in the configuration. The first ter... | 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"
] |
term (Captive Portal Content Delivery) | term term-name{
from {
destination-address address <except>;
}
then {
accept;
insert tag-name tag-name tag-value tag-value;
redirect url;
rewrite destination-address address <destination-port port-number>;
syslog;
}
} | [edit dynamic-profiles profile-name services captive-portal-content-delivery rule rule-name],
[edit services captive-portal-content-delivery rule rule-name] | Define the term match and action properties for the captive portal content delivery rule. Use the
statement at the [edit services...] hierarchy level for static CPCD. Use the statement at the [edit dynamic-
profiles profile-name services...] hierarchy level for converged services CPCD. | [
{
"name": "term-name",
"desc": "Identifier for the term."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
Support at the [edit dynamic-profiles profile-name services captive-portal-content-delivery rule rule-name]
hierarchy level added in Junos OS Release 17.2R1.
Support for Next Gen Services introduced in Junos OS Release 19.3R2. | [
"HTTP Redirect Service Overview",
"Configuring MS-MPC-Based or MX-SPC3-Based Static HTTP Redirect Services",
"Configuring MS-MPC-Based or MX-SPC3-Based Converged HTTP Redirect Services",
"Configuring Routing Engine-Based, Static HTTP Redirect Services",
"Configuring Routing Engine-Based, Converged HTTP Redi... |
term (Dynamic Profiles) | term term-name {
from {
match-conditions;
}
then {
action;
action-modifiers;
}
only-at-create;
} | [edit dynamic-profiles profile-name firewall family family-name fast-update-filter filter-name],
[edit dynamic-profiles profile-name firewall family family-name filter filter-name] | Define terms for fast update filters. | [
{
"name": "action",
"desc": "(Optional) An action to take if conditions match. If you do not specify an action, the packets that"
},
{
"name": "action-modifiers",
"desc": "(Optional) One or more actions to perform on a packet."
},
{
"name": "from",
"desc": "(Optional) Match packet fi... | 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 dynamic-profiles ... filter filter-name] hierarchy level introduced in Junos OS Release
11.4. | [
"Configuring Fast Update Filters",
"Configuring Terms for Fast Update Filters",
"Fast Update Filter Match Conditions",
"Fast Update Filter Actions and Action Modifiers",
"Parameterized Filters Overview",
"Firewall Filter Terminating and Nonterminating Actions for Protocol-Independent Traffic in Dynamic",
... |
term (Firewall Filter) | term term-name {
from {
match-conditions;
vxlan {
vni vni-id
flags value mask-in-hex value
reserved1 value
reserved2 value
}
ip-version ipv4 {
match-conditions-mpls-ipv4-address;
protocol (tc... | [edit dynamic-profiles profile-name firewall family family-name filter filter-name],
[edit firewall family family-name filter filter-name],
[edit firewall family family-name service-filter filter-name],
[edit firewall family family-name simple-filter filter-name],
[edit logical-systems logical-system-name firewall fami... | Define a firewall filter term. | [
{
"name": "actions",
"desc": "(Optional) Actions to perform on the packet if conditions match. You can specify one"
},
{
"name": "filter-name",
"desc": "(Optional) For family family-name filter filter-name only, reference another standard stateless"
},
{
"name": "from",
"desc": "(Opt... | 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.
filter option introduced in Junos OS Release 7.6.
Logical systems support introduced in Junos OS Release 9.3.
ip-version ipv4 support introduced in Junos OS Release 10.1. | [
"Guidelines for Configuring Firewall Filters",
"Configuring Multifield Classifiers",
"Guidelines for Configuring Simple Filters",
"Guidelines for Configuring and Applying Firewall Filters in Logical Systems"
] |
term (HTTP Header Enrichment) | term term-number {
from {
destination-address {
(any-ipv4 | any-ipv4 except);
(any-ipv6 | any-ipv6 except);
(any-unicast | any-unicast except);
(prefix | prefix except);
}
destination-address-range {
high address low address <except... | [edit services hcm tag-rule rule-name] | Configure a term in a tag rule, which is used to enrich HTTP headers with the appropriate tags. You must
configure at least one term for a tag rule, but you can configure multiple terms. Terms are evaluated in
the order they are configured. If a data packet matches all the criteria in the from statement in any of the
t... | [
{
"name": "term-number",
"desc": "Number for the term. Range: 1 through 32,767"
}
] | 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 HTTP Header Enrichment Overview",
"Configuring Tag Rules",
"Configuring HCM Profiles and Assigning Tag Rules",
"Junos Web Aware HTTP Header Enrichment Overview"
] |
term (IDS MS-DPC) | term term-name {
from {
application-sets set-name;
applications [ application-names ];
destination-address (address | any-unicast) <except>;
destination-address-range low minimum-value high maximum-value <except>;
source-address (address | any-unicast) <except>;
sourc... | [edit services ids rule rule-name] | Define the IDS term properties when using the MS-DPC. | [
{
"name": "term-name",
"desc": "Identifier for the term."
}
] | 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 IDS Rules on an MS-DPC"
] |
term (IDS MS-MPC) | term {
then {
aggregation (IDS) {
destination-prefix prefix-value | destination-prefix-ipv6 prefix-value;
source-prefix prefix-value | source-prefix-ipv6 prefix-value;
}
allow-ip-options {
any;
loose-source-route;
route-record;
... | [edit services ids rule rule-name] | Configure the network attack prevention actions for an IDS rule for a service set on an MS-MPC.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
term (IP Security VPN) | term term-name {
from {
destination-address address;
ipsec-inside-interface interface-name;
source-address address;
}
then {
anti-replay-window-size bits;
backup-remote-gateway address;
clear-dont-fragment-bit;
dynamic {
ike-policy policy-... | [edit services ipsec-vpn rule rule-name] | Define the IPsec term properties. | [
{
"name": "term-name",
"desc": "Identifier for the term."
}
] | 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 IPsec Rules"
] |
term (PCP) | term term-name {
from {
application-sets set-name;
applications [ application-name ];
destination-address address <except>;
destination-address-range high maximum-value low minimum-value <except>;
destination-port high maximum-value low minimum-value;
destination-pre... | [edit services pcp rule rule-name] | Define the PCP rule term properties. A PCP rule assigns the PCP server that handles selected traffic.
PCP is supported on the MS-DPC, MS-100, MS-400, and MS-500 MultiServices PICS. Starting in Junos
OS Release 17.4R1, PCP is also supported on the MS-MPC and MS-MIC.
The remaining statements are explained separately. | [
{
"name": "term-name",
"desc": "Identifier for the term. The remaining statements are explained separately."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2R1. | [
"Configuring Port Control Protocol"
] |
term (satellite-policies) | term term-name{
from {
product-modelmodel-name;
}
} | [edit policy-options satellite-policies candidate-uplink-policy policy-name],
[edit policy-options satellite-policies environment-monitoring-policy policy-name],
[edit policy-options satellite-policies forwarding-policy policy-name] | Create and configure a term in a candidate uplink satellite policy, an environment monitoring satellite
policy, or a forwarding policy satellite policy, within a satellite policy.
A term in a candidate uplink policy, an environment monitoring policy, or a forwarding policy for satellite
devices is used to apply the pol... | [
{
"name": "term term-name",
"desc": "Specifies the user-defined name of the term. A term is a named structure in which match conditions and actions are defined. A candidate uplink policy or environment monitoring policy can contain multiple terms. The term name can contain letters, numbers, and hyphens (-) ... | 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 introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise. | [
"Configuring Satellite Device Alarm Handling Using an Environment Monitoring Satellite Policy in a",
"Junos Fusion",
"Understanding Satellite Policies in a Junos Fusion"
] |
term (Services CoS) | term term-name {
from {
application-sets set-name;
applications [ application-names ];
destination-address address;
destination-prefix-list list-name <except>;
source-address address;
source-prefix-list list-name <except>;
}
then {
application-profile... | [edit services cos rule rule-name] | Define the CoS term properties. | [
{
"name": "term-name",
"desc": "Identifier for the term."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Configuring CoS Rules",
"Configuring CoS Rules on Services PICs"
] |
term (Services NAT) | term term-name {
from {
application-sets set-name;
applications [ application-names ];
destination-address (address | any-unicast) <except>;
destination-address-range low minimum-value high maximum-value <except>;
destination-port range high maximum-value low minimum-value;
... | [edit services nat rule rule-name] | Define the NAT term properties. | [
{
"name": "term-name",
"desc": "Identifier for the term. The remaining statements are explained separately."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Network Address Translation Rules Overview"
] |
term (Services Stateful Firewall) | term term-name {
from {
application-sets set-name;
applications [ application-names ];
destination-address (address | any-ipv4 | any-ipv6 | any-unicast) <except>;
destination-address-range low minimum-value high maximum-value <except>;
destination-prefix-list list-name <excep... | [edit services stateful-firewall rule rule-name] | Define the stateful firewall term properties. | [
{
"name": "term-name",
"desc": "Identifier for the term."
}
] | 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 Stateful Firewall Rules"
] |
term (Simple Filter) | term term-name {
from {
match-conditions;
}
then {
forwarding-class class-name;
loss-priority (high | low | medium);
}
} | [edit firewall family inet simple-filter filter-name] | Define a simple filter term. | [
{
"name": "from",
"desc": "Match packet fields to values. If the from option is not included, all packets are considered to match"
},
{
"name": "match-conditions",
"desc": "One or more conditions to use to make a match."
},
{
"name": "term-name",
"desc": "Name that identifies the ter... | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Multifield Classification",
"Simple Filter Overview",
"Firewall Filter Match Conditions for IPv4 Traffic",
"Firewall Filter Match Conditions for IPv6 Traffic"
] |
term (TDF Domain Selection) | term term-name {
from {
3gpp-imsi {
equals value;
has-prefix value;
has-suffix value;
matches value;
}
attribute name {
code numeric-code;
vendor-id vendor-id;
format {
integer {
... | [edit unified-edge gateways tdf gateway-name domain-selection] | Configure a term that can be used to select the TDF domain for an IP-based subscriber. You can
configure multiple terms (up to 10 terms) for the TDF domain selection, and each term is applied in the
order in which it is configured. You can specify multiple match conditions within the from statement of a
term, and all o... | [
{
"name": "term-name",
"desc": "Identifier for the term. Range: 1 through 50 alphanumeric characters. NOTE: You must configure at least one term."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
term (URL Filter) | term term-name {
from {
src-ip-prefix [prefix1 prefix2];
dest-port [port1 port2];
}
then {
accept;
custom-page custom-page;
http-status-code http-status-code;
redirect-url redirect-url;
tcp-reset;
}
} | [edit services url-filter profile profile-name template template-name] | Define a URL filtering term. A term is a set of match criteria with actions to be taken if the match criteria
is met. You must configure term to configure URL filtering. | [
{
"name": "term-name",
"desc": "Name of the term."
},
{
"name": "from",
"desc": "Define match criteria. The from statement is optional. If you omit the from statement, all source IP prefixes and all destination ports are considered to match. All such combinations then take the configured actions... | 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. | [] |
terminal | terminal; | [edit security idp idp-policy policy-name rulebase-ips rule rule-name] | Set or unset a terminal rule flag. The device stops matching rules for a session when a terminal rule is
matched. | [] | 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. | [] |
terminate (PPPoE Service Name Tables) | terminate; | [edit protocols pppoe service-name-tables table-name service service-name],
[edit protocols pppoe service-name-tables table-name service service-name agent-specifier aci
circuit-id-string ari remote-id-string] | Direct the router to immediately respond to a PPPoE Active Discovery Initiation (PADI) control packet
received from a PPPoE client by sending the client a PPPoE Active Discovery Offer (PADO) packet. The
PADO packet contains the name of the access concentrator (router) that can service the client request.
The terminate ... | [] | 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.
Support at [edit protocols pppoe service-name-tables table-name service service-name agent-specifier aci
circuit-id-string ari remote-id-string] hierarchy level introduced in Junos OS Release 10.2. | [
"Configuring PPPoE Service Name Tables"
] |
terminate-code | terminate-code (aaa (deny | service-shutdown | shutdown) | dhcp | l2tp | ppp | vlan) term-reason
radius value; | [edit access] | Customize the mapping between a termination cause (the internal termination identifier) and a
numerical code value for the cause that is reported in the RADIUS Acct-Terminate-Cause attribute (49).
When a RADIUS Acct-Stop message is issued as a result of the termination of a subscriber or service
session, the RADIUS Acc... | [
{
"name": "aaa",
"desc": "Map internal identifiers for AAA-specific termination causes to a numerical value."
},
{
"name": "deny",
"desc": "Limit selection of termination causes to those associated with denial of subscriber access."
},
{
"name": "dhcp",
"desc": "Map internal identifi... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
vlan option added in Junos OS Release 16.1. | [
"Session Termination Causes and RADIUS Termination Cause Codes",
"Session Termination Causes and RADIUS Termination Cause Codes"
] |
termination (Services) | termination {
profile name {
custom-ciphers;
enable-flow-tracing enable-flow-tracing;
enable-session-cache enable-session-cache;
preferred-ciphers (custom | medium | strong | weak);
protocol-version (all | ssl3 | tls1 | tls11 | tls12);
server-certificate server-cer... | [edit services ssl] | Specify the configuration for Secure Socket Layer (SSL) termination support service.
Following types of SSL profiles are supported on SRX Series to secure connections based on the role of
the SRX Series Firewall:
•
SSL initiation: The SRX Series Firewall, acting as an SSL proxy client, initiates and maintains SSL
sessi... | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. The protocol-version statement is updated to
include tls11 and tls12 from Junos OS Release 15.1X49-D30. | [] |
test (Security IDP) | test test-condition; | [edit security idp custom-attack attack-name attack-type anomaly] | Specify protocol anomaly condition to be checked. | [
{
"name": "test-condition",
"desc": "Name of the anomaly test condition."
}
] | 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. | [] |
test aaa authd-lite user | test aaa authd-lite user username password password profile access-profile-name
<port nas-port>
<zero-stats> | Verify authd-lite subscriber access authentication, accounting, and address allocation configuration.
The test aaa command supports all RADIUS-sourced attributes, both IETF standard attributes and
Juniper Networks VSAs. Received attributes are displayed in the output. For information about standard
RADIUS attributes, s... | [
{
"name": "username",
"desc": "Specify the subscriber username to test."
},
{
"name": "password password",
"desc": "Specify the password associated with the username."
},
{
"name": "profile access-profile-name",
"desc": "Specify the access profile associated with the subscriber."
}... | view
Output Fields
When you enter this command, you are provided feedback on the status of your request. For
information about output fields related to authentication, accounting, and subscriber-specific
information, see the show network-access aaa statistics, show network-access aaa statistics
authentication, show net... | Command introduced in Junos OS Release 11.2. | [
"AAA Testing and Troubleshooting",
"Understanding External Authentication Servers"
] | |
test aaa dhcp user | test aaa dhcp user username
<agent-remote-id ari>
<logical-system logical-system-name>
<mac-address mac-address>
<no-address-request>
<option-82 option-82>
<password password>
<profile access-profile-name>
<routing-instance routing-instance-name>
<service-type service-type>
<source-address source-address>
<terminate-co... | Verify Dynamic Host Configuration Protocol (DHCP) subscriber access authentication, accounting, and
address allocation configuration by creating a test pseudo session.
NOTE: The test aaa command supports all RADIUS-sourced attributes, both IETF
standard attributes and Juniper Networks VSAs. Received attributes are disp... | [
{
"name": "username",
"desc": "Subscriber username to test."
},
{
"name": "agent-remote-id",
"desc": ""
},
{
"name": "ari",
"desc": "(Optional) Value of the DSL Forum Agent-Remote-Id (VSA 26–2)."
},
{
"name": "logical-system",
"desc": ""
},
{
"name": "logical-syst... | view
Output Fields
When you enter this command, you are provided feedback on the status of your request. For
information about output fields related to authentication, accounting, and subscriber-specific
information, see the show network-access aaa statistics, show network-access aaa statistics
authentication, show net... | Command introduced in Junos OS Release 11.2.
Option terminate-code added in Junos OS Release 11.4.
Option agent-remote-id added in Junos OS Release 14.1.
Options no-address-request and service-type added in Junos OS Release 16.1. | [
"AAA Testing and Troubleshooting"
] | |
test aaa ppp user | test aaa ppp user username
<agent-remote-id ari>
<logical-system logical-system-name>
<no-address-request>
<password password>
<profile access-profile-name>
<routing-instance routing-instance-name>
<service-type service-type>
<terminate-code code-value> | Verify Point-to-Point Protocol (PPP) subscriber access authentication, accounting, and address allocation
configuration by creating a test pseudo session.
NOTE: The test aaa command supports all RADIUS-sourced attributes, both IETF
standard attributes and Juniper Networks VSAs. Received attributes are displayed in the... | [
{
"name": "username",
"desc": "Subscriber username to test."
},
{
"name": "agent-remote-id ari",
"desc": "(Optional) Value of the DSL Forum Agent-Remote-Id (VSA 26–2)."
},
{
"name": "logical-system",
"desc": ""
},
{
"name": "logical-system-name",
"desc": "(Optional) Logic... | view
Output Fields
When you enter this command, you are provided feedback on the status of your request. For
information about output fields related to authentication, accounting, and subscriber-specific
information, see the show network-access aaa statistics, show network-access aaa statistics
authentication, show net... | Command introduced in Junos OS Release 11.2.
Option terminate-code added in Junos OS Release 11.4.
Option agent-remote-id added in Junos OS Release 14.1.
Options no-address-request and service-type added in Junos OS Release 16.1. | [
"AAA Testing and Troubleshooting"
] | |
test access profile | test access profile profile-name user username password password <detail> | Specify a profile to use to get information from a RADIUS server, which includes all the information from
the test access radius-server command. | [
{
"name": "detail",
"desc": "(Optional) Show the RADIUS attributes returned by the server."
},
{
"name": "profile-name",
"desc": "Access profile name configured."
},
{
"name": "password",
"desc": "Password for the username."
},
{
"name": "username",
"desc": "User name to ... | view
Output Fields
Table 1901 on page 30304 lists the output fields for the test access profile command. Output fields are
listed in the approximate order in which they appear.
Table 1901: test access profile Output Fields
Field Name
Field Description
Profile Name
Name of the configured access profile.
Client Username... | Command introduced in Junos OS Release 9.1. | [] | |
test access radius-server | test access radius-server address user username password password secret secret
<authentication-port port>
<retry number>
<source-address address>
<timeout number> | Verify RADIUS server authentication parameters. | [
{
"name": "address",
"desc": "RADIUS server under test IP address."
},
{
"name": "password",
"desc": "Password for the user."
},
{
"name": "secret",
"desc": "Secret shared with the RADIUS server."
},
{
"name": "user",
"desc": "User name to be authenticated to the RADIUS s... | view
Output Fields
Table 1902 on page 30310 lists the output fields for the test access radius-server command. Output fields
are listed in the approximate order in which they appear.
Table 1902: test access radius-server Output Fields
Field Name
Field Description
Server
The IP address of the RADIUS server authenticate... | Command introduced in Junos OS Release 9.1. | [] | |
test configuration | test configuration filename
syntax-only | Verify that the syntax of a configuration file is correct. If the configuration contains any syntax or
commit check errors, a message is displayed to indicate the line number and column number in which
the error was found. When using the filename option, this command only accepts text files. | [
{
"name": "filename",
"desc": "Name of the configuration file. This file must be a text file and no other type."
},
{
"name": "syntax-only",
"desc": "(Optional) Check the syntax of a partial configuration file, without checking for commit errors."
}
] | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
test configuration
user@host> test configuration terminal
[Type ^D to end input]
system {
host-name host;
test1;
login;
}
terminal:3:(8) syntax error: test
[edit system]
'test;'
syntax er... | Command introduced before Junos OS Release 7.4.
syntax-only option introduced in Junos OS Release 12.1. | [] | |
test interface restart-auto-negotiation | test interface restart-auto-negotiation interface-name | Restarts auto-negotiation on a Fast Ethernet or Gigabit Ethernet interface. | [
{
"name": "interface-name",
"desc": "Interface name: fe-fpc/pic/port or ge-fpc/pic/port."
}
] | view
Output Fields
Use the show interfaces extensive command to see the state for auto-negotiation.
Sample Output
test interface restart-auto-negotiation
user@host> test interface restart-auto-negotiation fe-1/0/0 | Command introduced in Junos OS Release 7.6. | [] | |
test msdp | test msdp (dependent-peers prefix | rpf-peer originator)
<instance instance-name>
<logical-system (all | logical-system-name)> | Find Multicast Source Discovery Protocol (MSDP) peers. | [
{
"name": "dependent-peers prefix",
"desc": "Find downstream dependent MSDP peers."
},
{
"name": "rpf-peer originator",
"desc": "Find the MSDP reverse-path-forwarding (RPF) peer for the originator."
},
{
"name": "instance instance-name",
"desc": "(Optional) Find MDSP peers for the sp... | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
test msdp dependent-peers
user@host> test msdp dependent-peers 10.0.0.1/24 | Command introduced before Junos OS Release 7.4. | [] | |
test policy | test policy policy-name prefix | Test a policy configuration to determine which prefixes match routes in the routing table.
NOTE: If you are using the test policy command on a logical system, you must first set
the CLI to the logical system context. For example, if you want to test a routing policy
that is configured on logical system R2, first run t... | [
{
"name": "policy-name",
"desc": "Name of a policy."
},
{
"name": "prefix",
"desc": "Destination prefix to match. Additional Information All prefixes in the default unicast routing table (inet.0) that match prefixes that are the same as or longer than the specific prefix are processed by the fro... | view
Output Fields
For information about output fields, see the output field tables for the show route command, the show route
detail command, the show route extensive command, or the show route terse command.
Sample Output
test policy
user@host> test policy test-statics 172.16.0.1/8
inet.0: 44 destinations, 44 routes... | Command introduced before Junos OS Release 7.4. | [
"Understanding Routing Policy Tests"
] | |
test security utm anti-spam | test security utm anti-spam ip-check <test-IP>
<test-IP> test security utm anti-spam. | Use this command to check if the IP (Internet Protocol) is a spam source or it is a configuration problem
when the device doesn't block the spam. The anti-spam feature requires internet connectivity with the
Spam Block List (SBL) server. Domain Name Service (DNS) must be available to access the SBL server. | [
{
"name": "test-IP",
"desc": "Supports both IPv4 and IPv6."
}
] | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Table 1903 on page 30320 lists the output fields for the test security utm anti-spam command. Output
fields are listed in the approximate order in which they appear.
Table 1903: test security utm anti-spam
Field Na... | Command introduced in Junos OS Release 20.2. | [] | |
test security utm enhanced-web-filtering url-check | test security utm web-filtering url-check | Use this test command to send the test-string to web-filtering server (example: Websense ThreatSeeker
Cloud) to test the category and reputation of the test-string.
Starting in Junos OS Release 23.3R1, you can use the test security utm web-filtering url-check test
command to check the category and reputation of a URL. | [
{
"name": "<test-url>",
"desc": "Enhanced-web-filtering threat-check test URL. The maximum length of test URL is 249."
}
] | view
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Table 1904 on page 30324 lists the output fields for the test security utm enhanced-web-filtering url-check
command. Output fields are listed in the approximate order in which they appear.
Table 1904: test security ... | Command introduced in Junos OS Release 20.2.
Command test security utm web-filtering url-check introduced in Junos OS Release 23.3R1. | [
"Enhanced Web Filtering"
] | |
test security utm web-filtering profile | test security utm web-filtering profile <profile-name>
<test-url> Web-filtering test URL | Use this command to check if the test-string matches the specific profile in the Web filtering server. | [
{
"name": "test-url",
"desc": "Enhanced Web filtering threat-check test URL. The maximum length of test URL is 249."
}
] | view
Sample Output
test security utm web-filtering profile
The following example sends profile sportclass and test url www.google.com to the Web filtering server
to check whether the test string matches the specific profile:
user@host> test security utm web-filtering profile sportclass www.google.com
UTM web-filterin... | Command introduced in Junos OS Release 20.2R1. | [
"Enhanced Web Filtering"
] | |
test services l2tp tunnel | test services l2tp tunnel user user-name
<password user-password>
<tunnel-name name> | (MX Series routers only) Test and verify Layer 2 Tunneling Protocol (L2TP) tunnel configurations from
the L2TP access concentrator (LAC). The test determines whether the user can be authenticated and
tunneled according to the L2TP configuration. The establishment of all tunnels associated with the user
is tested. You c... | [
{
"name": "user user-name",
"desc": "Name of the user under test. You must use an existing configured username, although it can be created solely for testing a tunnel configuration."
},
{
"name": "password user-password",
"desc": "(Optional) Authentication password for the specified user. If you... | view
Output Fields
Table 1905 on page 30333 lists the output fields for the test services l2tp tunnel command. Output fields
are listed in the approximate order in which they appear.
Table 1905: test services l2tp tunnel Output Fields
Field Name
Field Description
Tunnel-name
Name of the tunnel as configured in the loc... | Command introduced in Junos OS Release 11.4. | [
"L2TP LAC Tunneling for Subscribers"
] | |
test services monitoring rfc2544 | test services monitoring rfc2544
(test test-name | test-id id)
<routing-instance <routing-instance-name>>
(clear-counters | start | stop) | Start or stop an RFC 2544-based benchmarking test, or clear the statistical counters for a test. You can
start or stop a specific test name, or you can stop a test based on its test identifier. When you trigger an
RFC 2544-based benchmarking test, it passes through a series of states. These states are displayed in
the ... | [
{
"name": "(test test-name | test-id id)",
"desc": "Name of the test to be started or stopped or the unique identifier of the test to be stopped."
},
{
"name": "routing-instance routing-instance-name",
"desc": "(Optional) Name of the routing instance for the test."
},
{
"name": "(clear-c... | view
Sample Output
test services monitoring rfc2544 test test-name start
user@host> test services monitoring rfc2544 test mytest start
If successful, the identifier of the started test is displayed:
Test mytestid 1 started
If unsuccessful, an error message is displayed:
Error starting test mytest: error-description
So... | Command introduced for Junos OS Evolved Release 21.1R1. | [] | |
test services rpm rfc2544-benchmarking test | test services rpm rfc2544-benchmarking test
<clear-counters>
<test-name>
<test-id>
<start | stop> | Start or stop an RFC 2544-based benchmarking test. You can start or stop all of the test names that are
defined on a device, or start or stop a specific test name. You can also stop a test based on its test
identifier. You can also clear the statistical counters associated with the test. When you trigger an RFC
2544-ba... | [
{
"name": "start",
"desc": "Start the RFC 2544-based benchmarking test"
},
{
"name": "stop",
"desc": "Terminate the RFC 2544-based benchmarking test"
},
{
"name": "clear-counters",
"desc": "(ACX Series routers, SRX300, and SRX550HM devices only) Clear the statistics associated with t... | view
Output Fields
To display the results of the benchmarking test, use the show services rpm rfc2544-benchmarking test
command.
Sample Output
test services rpm rfc2544-benchmarking test start
user@host> test services rpm rfc2544-benchmarking test test1 start
Test "test1" id 56 started
The response specifies that a t... | Command introduced in Junos OS Release 12.3X52. | [
"Configuring an RFC 2544-Based Benchmarking Test",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers"
] | |
test | [edit services monitoring rpm owner name] | Specify the range of probes over which the standard deviation, average, and jitter are calculated. The
test name combined with the owner name represent a single RPM configuration instance. | [
{
"name": "test name",
"desc": "You can configure any name up to 32 characters in length. For Junos OS Evolved, if the owner"
}
] | 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.
inet6-options option added in Junos OS Release 14.1R4 for MX Series routers.
Statement introduced in Junos OS Evolved Release 20.1R1.
traps option introduced in Junos OS Evolved Release 21.2R1. | [
"Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, and MX Series",
"Routers",
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches"
] | |
test-agent (Paragon Active Assurance) | test-agent {
cc-account user-account-name;
cc-host DNS-name;
cc-insecure;
cc-password plain-text-password;
cc-port port-number;
cc-user "user@domain";
ta-name test-agent-name;
ta-version version-number;
} | [edit services paa] | Installs and runs an instance of the Paragon Active Assurance (PAA) test agent on the node. Once this
configuration is committed, the node downloads the PAA test agent Docker image from the PAA Control
Center. The node then starts the Docker daemon and loads the PAA test agent Docker image into a
Docker container. The... | [
{
"name": "cc-account user-account-name",
"desc": "(Required) Your PAA Control Center user account."
},
{
"name": "cc-host DNS-name",
"desc": "(Required) IP address or DNS host name of the PAA Control Center."
},
{
"name": "cc-insecure",
"desc": "(Optional) Allow an insecure connecti... | configure | Statement introduced in Junos OS Evolved Release 23.4R1. | [
"Install the Paragon Active Assurance (PAA) Test Agent"
] |
test-count | test-count test_count-number; | [edit services rpm twamp client control-connection control-client-name] | Specify the total number of test session iterations. The range is 0 through 4294967290. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [] |
test-finish-wait-duration (RFC 2544 Benchmarking) | test-finish-wait-duration; | [edit services rpm rfc2544-benchmarkingtests test-name test-name] | Number of seconds to wait after transmitting the last frame and before concluding that the test as
complete. Once the test is complete, the frames received after that are not considered for the result
computation. Use this parameter if the latency introduced by the network under test is high in the
normal conditions. D... | [] | 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. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
test-interface (RFC 2544 Benchmarking) | test-interface interface-name; | [edit services monitoring rfc2544 tests test-name test-name] | Specify the logical interface on which the RFC 2544-based benchmarking test is run.
For Junos OS, if you configure an inet family and the test mode to initiate and terminate test frames on
the same device, the interface you configure is not effective. Instead, the test is run on the egress logical
interface that is det... | [
{
"name": "interface-name",
"desc": "Name of the logical interface on which the test needs to be run."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3.
Statement introduced in Junos OS Evolved Release 21.1R1. | [
"Configuring an RFC 2544-Based Benchmarking Test",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers",
"RFC 2544-Based Benchmarking Tests Overview"
] |
test-interval | test-interval seconds; | [edit services monitoring rpm owner name test name] | Specify the time to wait between tests, in seconds. A test interval of 0 seconds causes the RPM test to
stop after one iteration. | [
{
"name": "seconds",
"desc": "Number of seconds to wait between tests."
}
] | 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 Release 9.3 for EX Series switches.
Statement introduced in Junos OS Release 13.2 for PTX Series Packet Transport routers.
Support at the [edit services rpm twamp client control-connection control-client-name] hierarchy level
introduced ... | [
"Configuring BGP Neighbor Discovery Through RPM",
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches",
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
test-iterator-duration (RFC 2544 Benchmarking) | test-iterator-duration seconds; | [edit services monitoring rfc2544 tests test-name test-name] | Specify the duration of each iteration in seconds. If you configure this value, the default value of each
iteration depends on the type of test being run. For throughput, back-to-back-frames and frame-loss
types of tests, the default value is 20 seconds. For latency tests, the default value is 120 seconds for
Junos OS ... | [
{
"name": "seconds",
"desc": "Number of seconds for which each test iteration is run. Range: 10 through 120 seconds"
}
] | 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 23.4R1. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests",
"rfc2544"
] |
test-iterator-pass-threshold (RFC 2544 Benchmarking) | test-iterator-pass-threshold; | [edit services rpm rfc2544-benchmarkingtests test-name test-name] | Specify the pass threshold of each iteration. | [] | 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. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
test-name | [edit services monitoring rfc2544 tests] | Define the name of the RFC 2544-based benchmarking test. For each unique test name that you
configure, you can specify a test profile, which contains the settings for a test and its type, and also a
test interface, which contains the settings for test packets that are sent and received on the selected
interface. | [
{
"name": "test-name",
"desc": "Test name. The name can be up to 32 characters in length."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3.
Statement introduced in Junos OS Evolved Release 21.1R1. | [
"Configuring an RFC 2544-Based Benchmarking Test",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers",
"RFC 2544-Based Benchmarking Tests for ACX Routers Overview"
] | |
test-only-mode | test-only-mode (true | false): | [edit services unified-access-control ] | Configure the device in test-only mode to log access decisions from the IC Series device without
actually enforcing the decisions. When configured in test-only mode, the SRX Series Firewall enables all
UAC traffic to go through so you can test the implementation without impeding traffic.
Use this statement when you are... | [] | 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. | [] |
test-profile (RFC 2544 Benchmarking) | [edit services monitoring rfc2544],
[edit services monitoring rfc2544 tests test-name test-name] | Specify the name of the test profile to be associated with a particular test name. This parameter is
required when the test mode is configured as initiate-and-terminate. This parameter is disregarded when
the test mode is configured as reflection. A reflection service does not use the parameters specified in
the test ... | [
{
"name": "profile-name",
"desc": "Name of the test profile. The name can be up 32 characters in length. The name must start with a letter. Allowed characters are [a-zA-Z0-9_]"
}
] | 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 for ACX Series routers.
Statement introduced in Junos OS Evolved Release 23.4R1. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] | |
test-session (Junos OS Evolved) | test-session name {
data-size data-size;
destination-port destination-port;
dscp-code-points dscp-code-points;
history-size history-size;
moving-average-size moving-average-size;
offload-type (none | inline-timestamp | pfe-timestamp);
probe-count probe-count;
... | [edit services monitoring twamp client control-connection name] | Specify the TWAMP test session details, including the session name, the contents of the test packet, the
data size, the probe details, and the target destination. You must configure at least one test session. | [
{
"name": "name",
"desc": "Name of the test session."
},
{
"name": "data-size bytes",
"desc": "Specify the size of the data portion of the test packet, in bytes. Range: 0 through 65400 bytes Default: 0"
},
{
"name": "destination-port port",
"desc": "Specify the User Datagram Protoc... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 20.3R1.
traps option introduced in Junos OS Evolved Release 21.3R1.
IPv6 address support introduced in Junos OS Evolved Release 21.4R1.
The local-link sub-option of the target option for TWAMP Light test sessions introduced in Junos OS
Evolved Release 22.3R1.
The inline-... | [
"Understand Two-Way Active Measurement Protocol"
] |
test-session (Junos OS) | test-session session-name {
data-fill-with zeros data;
data-size size;
destination-port port;
dscp-code-points dscp-bits;
offload-type (inline-timestamp | none | pfe-timestamp);
probe-count count;
probe-interval seconds;
source-address source-address;
source-routing {
forwar... | [edit services rpm twamp client control-connection connection-name] | Specify the test session details that includes the session name, the contents of the test packet, the data
size, the probe details, and the target destination details. | [
{
"name": "session-name",
"desc": "Name of the session."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1.
destination-port option added in Junos OS Release 21.1R1.
source-address option and the local-link sub-option of the target-address option for TWAMP Light test
sessions introduced in Junos OS Release 21.4R1.
offload-type option introduced in Junos OS Release 25.4R1.
source... | [
"Understand Two-Way Active Measurement Protocol"
] |
test-type (RFC 2544 Benchmarking) | [edit services monitoring rfc2544 test-profile profile-name] | RFC 2544 defines four main test types. You can configure and perform a test for a certain service, such
as IPv4 or Ethernet, and analyze the results of the test to examine the various SLA parameters of the
service. The test packets traverse through the same path as the regular service traffic. These tests are
repeated ... | [
{
"name": "throughput",
"desc": "Measure the maximum rate at which none of the offered or transmitted frames are dropped by the device on which the test is performed. You use this test to measure the rate of successful transmission against the theoretical rate of the Ethernet media used for testing."
},
... | 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 for ACX Series routers.
Statement introduced in Junos OS Evolved 23.4R1. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests",
"rfc2544"
] | |
tests | [edit services monitoring rfc2544] | Specify the attributes of the test iteration, such as the address family (type of service, IPv4 or Ethernet),
the logical interface, test duration, and test packet size, that are used for a benchmarking test to be run.
The test name combined with the test profile represent a single real-time performance monitoring (RPM... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3.
Statement introduced in Junos OS Evolved Release 21.1R1.
Support for the destination-mac-address, direction, disable-signature-check, in-service, ip-swap, reflect-etype,
reflect-mode, service-type, source-mac-address, and udp-tcp-port-swap configuration statements added in... | [
"Configuring an RFC 2544-Based Benchmarking Test",
"Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers",
"RFC 2544-Based Benchmarking Tests for ACX Routers Overview"
] | |
tftp (Security ALG) | tftp {
disable;
traceoptions {
flag {
all {
extensive
}
}
}
} | [edit logical-systems name security alg],
[edit logical-systems name tenants name security alg],
[edit security alg],
[edit services alg],
[edit tenants name security alg] | 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": "disable",
"desc": "Disable the TFTP ALG. By default, the TFTP ALG is enabled."
},
{
"name": "traceoptions",
"desc": "Configure TFTP ALG tracing options."
},
{
"name": "flag",
"desc": "Trace operation to perform."
},
{
"name": "all",
"desc": "Trace all events."
... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.2.
The tenant option is introduced in Junos OS Release 18.3R1. | [
"Understanding the TFTP ALG"
] |
tftp | tftp {
description text-description;
interface interface-name {
broadcast;
description text-description;
no-listen;
server address <logical-system logical-system-name> <routing-instance routing-instance-
name>;
}
server address <logical-system logical-system-name> <routin... | [edit forwarding-options helpers] | Enable TFTP request packet forwarding.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring DNS and TFTP Packet Forwarding"
] |
tftp-server | tftp-server {
connection-limit connections;
rate-limit connections per minute;
} | [edit system services] | Enable TFTP file transfers | [
{
"name": "connection-limit",
"desc": "Limit number of simultaneous connections (connections) Default: 75 Range: 1 through 250"
},
{
"name": "rate-limit",
"desc": "Limit incoming connection rate (connections per minute) Default: 150 Range: 1 through 250"
}
] | flow-tap—To view this statement in the configuration.
flow-tap-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [] |
then (Captive Portal Content Delivery) | then {
accept;
insert tag-name tag-name tag-value tag-value;
redirect url;
rewrite destination-address address <destination-port port-number>;
syslog;
} | [edit dynamic-profiles profile-name services captive-portal-content-delivery rule rule-name term
term-name],
[edit services captive-portal-content-delivery rule rule-name term term-name] | Define the term actions and any optional action modifiers for the captive portal content delivery rule.
Use the statement at the [edit services...] hierarchy level for static CPCD. Use the statement at the [edit
dynamic-profiles profile-name services...] hierarchy level for converged services CPCD. | [
{
"name": "action",
"desc": "Actions to accept, redirect, or rewrite packets and all subsequent packets in flows that match the rules."
},
{
"name": "accept",
"desc": "Accept the packets and all subsequent packets in flows that match the rules."
},
{
"name": "insert",
"desc": "Insert... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
Support at the [edit dynamic-profiles profile-name services captive-portal-content-delivery rule rule-name term
term-name] hierarchy level added in Junos OS Release 17.2R1.
insert option added in Junos OS Release 19.1R1.
Support for Next Gen Services introduced in Junos OS... | [
"HTTP Redirect Service Overview",
"Firewall Filter Match Conditions Based on Address Fields",
"Configuring MS-MPC-Based or MX-SPC3-Based Static HTTP Redirect Services",
"Configuring MS-MPC-Based or MX-SPC3-Based Converged HTTP Redirect Services",
"Configuring Routing Engine-Based, Static HTTP Redirect Servi... |
then (Event Policy) | then {
change-configuration {
commands {
"command";
}
commit-options {
check <synchronize>;
force;
log "comment-string";
synchronize;
}
retry count number interval seconds;
user-name username;
}
event... | [edit event-options policy policy-name] | Define event policy actions that are executed when an event occurs that triggers the policy. For each
event policy, you can configure multiple actions.
The remaining statements are explained separately. See CLI Explorer. | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Configure an Event Policy to Upload Files",
"Configure an Event Policy to Execute Operational Mode Commands",
"Execute Event Scripts in an Event Policy",
"Configure Event Policies to Ignore an Event",
"Overview of Using Event Policies to Raise SNMP Traps"
] |
then (Filters) | then {
action;
action-modifiers;
} | [edit firewall family family-name filter filter-name term term-name] | Configure a firewall filter action. | [
{
"name": "action",
"desc": "Actions to accept, discard, or forward packets that match all conditions specified in a filter term. Starting in Junos OS Release 18.4R1, two new actions – port-mirror and port-mirror-instance – are added for all match conditions, which enable selective port mirroring of MPLS tr... | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Firewall Filter Match Conditions and Actions (QFX5100, QFX5110, QFX5120, QFX5200, EX4600,",
"EX4650)",
"Configuring Firewall Filters",
"Understanding Firewall Filter Match Conditions",
"Understanding IP-Based Filtering and Selective Port Mirroring of MPLS Traffic"
] |
then (Firewall Filters) | then {
action;
action-modifiers;
} | [edit firewall family family-name filter filter-name term term-name] | Configure a filter action. | [
{
"name": "action",
"desc": "Action to accept, discard, sample or forward packets that match all match conditions specified in a filter term."
},
{
"name": "action-modifiers",
"desc": "Additional actions to analyze, classify, count, or police packets that match all conditions specified in a filt... | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
inline-monitoring-instance option added in Junos OS Release 19.4R1 on MX Series routers with MPCs
excluding MPC10E and MPC11E linecards.
Added additional family support to the inline-monitoring-instance option in Junos OS Release 21.1R1. | [
"Firewall Filter Match Conditions, Actions, and Action Modifiers for EX Series Switches",
"Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on EX Series Switches",
"Example: Using Filter-Based Forwarding to Route Application Traffic to a Security Device",
"Configuring Firewall Filters ... |
then (Hierarchical Policer) | then {
discard;
} | [edit firewall hierarchical-policer aggregate],
[edit firewall hierarchical-policer premium] | On M40e, M120, and M320 (with FFPC and SFPC) edge routers and T320, T640, and T1600 core
routers with Enhanced Intelligent Queuing (IQE) PICs, discard packets when a specified bandwidth or
burst limits for an aggregate level of a hierarchical policer is reached. | [
{
"name": "discard",
"desc": "Discard packets if condition is met."
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Applying Policers",
"Junos OS Class of Service User Guide for Routing Devices"
] |
then (HTTP Header Enrichment) | then {
count;
tag tag-name {
encrypt {
hash algorithm;
prefix hash-prefix;
}
ipv4-mask ipv4-mask;
ipv6-mask ipv6-mask;
ipv4-or-value ipv4-or-value;
ipv6-or-value ipv6-or-value;
tag-attribute tag-attr-name;
tag-header header... | [edit services hcm tag-rule rule-name term term-number] | Specify the actions to be taken if the criteria for the tag rule are matched. For subscribers under static
policy control, the matching conditions for a tag rule are determined by the PCC rule that uses the HCM
profile specifying the tag rule. For subscribers under dynamic policy control, a message from the PCRF
identi... | [] | 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 HTTP Header Enrichment Overview",
"Configuring Tag Rules",
"Configuring HCM Profiles and Assigning Tag Rules",
"Junos Web Aware HTTP Header Enrichment Overview"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.