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 |
|---|---|---|---|---|---|---|---|
traffic-class (Tunnels) | traffic-class traffic-class-value; | [edit interfaces gre-interface name unit unit number tunnel ]
[edit logical-systems logical-system-name interfaces gre-interface-name unit unit number tunnel] | Configure a static ToS/Traffic Class value in the IPv4/IPv6 header, respectively, of a GRE tunnel. This can
be useful, for example, when you want to apply a different classification to port-mirrored traffic than the
source traffic.
This setting overrides ToS reflection set by copying the inner IP header’s ToS value to ... | [
{
"name": "traffic-class-",
"desc": ""
},
{
"name": "value",
"desc": "The value represents the entire 8-bit differentiated services (DS) field in the IP header, and should be chosen based on the desired DSCP/IP precedence value. For example, if a DSCP value of 111000 is desired, then configure t... | interface | Statement introduced before Junos OS Release 11.2R1. | [
"CoS for Tunnels Overview",
"Configuring CoS for GRE and IP-IP Tunnels",
"Understanding Port Mirroring"
] |
traffic-class-map (Apply to Interface) | traffic-class-map {
(dscp | inet precedence) traffic-class-map-name;
exp traffic-class-map-name;
(ieee-802.1p | ieee-802.1ad) traffic-class-map-name <vlan-tag (inner | outer)>;
} | [edit class-of-service interfaces interface-name ] | Associate traffic class maps with an interface. | [
{
"name": "dscp",
"desc": "DSCP traffic class map; applies to both IPv4 and IPv6 traffic."
},
{
"name": "exp",
"desc": "MPLS EXP traffic class map."
},
{
"name": "ieee-802.1",
"desc": "IEEE 802.1 traffic class map."
},
{
"name": "ieee-802.1ad",
"desc": "IEEE 802.1ad traff... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Managing Ingress Oversubscription at the PFE",
"Configuring Traffic Class Maps to Manage Ingress Oversubscription",
"Example: Configuring Traffic Class Maps"
] |
traffic-class-map | traffic-class-map {
dscp traffic-class-map-name{
traffic-class {
real-time code-points value;
network-control code-points value;
best-effort code-points value;
}
}
exp traffic-class-map-name{
traffic-class {
real-time code-points value;... | [edit class-of-service] | Define the traffic class map for a packet on the basis of the CoS code points.
Traffic class map is a user-configurable input priority map that helps prioritize and classify traffic
entering a Packet Forwarding Engine during ingress oversubscription. You can define traffic class maps
for a packet on the basis of the fo... | [
{
"name": "dscp",
"desc": "DSCP traffic class map. Applies to both IPv4 and IPv6 traffic."
},
{
"name": "exp",
"desc": "MPLS EXP traffic class map."
},
{
"name": "ieee-802.1",
"desc": "IEEE 802.1 traffic class map."
},
{
"name": "ieee-802.1ad",
"desc": "IEEE 802.1ad traff... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Managing Ingress Oversubscription at the PFE",
"Configuring Traffic Class Maps to Manage Ingress Oversubscription",
"Example: Configuring Traffic Class Maps"
] |
traffic-control-profiles (Dynamic CoS Definition) | traffic-control-profiles profile-name {
adjust-minimum rate;
delay-buffer-rate (percent percentage | rate);
excess-rate (percent percentage | proportion value | percent $junos-cos-excess-rate);
excess-rate-high (percent percentage | proportion value);
excess-rate-low (percent percentage | proportion... | [edit dynamic-profiles profile-name class-of-service] | Configure traffic shaping and scheduling profiles for use in a dynamic client profile or a dynamic service
profile. | [
{
"name": "profile-name",
"desc": "Name of the traffic-control profile."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Traffic Scheduling and Shaping for Subscriber Access",
"Using the CLI to Modify Traffic-Control Profiles That Are Currently Applied to Subscribers"
] |
traffic-control-profiles | EX Series (Except EX4600), M Series, MX Series, PTX Series, T Series
traffic-control-profiles profile-name {
adjust-minimum rate;
atm-service (cbr | rtvbr | nrtvbr);
delay-buffer-rate (percent percentage | rate);
excess-rate (percent percentage | proportion value );
excess-rate-high (percent percen... | [edit class-of-service] | ACX Series Routers
Configure traffic-shaping profiles.
NOTE: For CoS on ACX6360-OR, see the documentation for the PTX1000.
EX Series (Except EX4600), M Series, MX Series, T Series, and PTX Series Routers
For Gigabit Ethernet IQ, Channelized IQ PICs, FRF.15 and FRF.16 LSQ interfaces, Enhanced Queuing
(EQ) DPCs, and PTX ... | [
{
"name": "profile-name",
"desc": "Name of the traffic-control profile. This name is also used to specify an output traffic"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement was introduced in Junos OS Release 7.6 (EX series, M series, MX series, T series, and PTX
series devices).
Statement was introduced in Junos OS Release 11.1 for the QFX Series.
Statement was introduced in Junos OS Release 12.3 for ACX series routers.
Statement was introduced in Junos OS Release 14.1X53-D20 fo... | [
"Oversubscribing Interface Bandwidth",
"Understanding Scheduling on PTX Series Routers",
"Example: Configuring CoS Hierarchical Port Scheduling (ETS)",
"Example: Configuring Traffic Control Profiles (Priority Group Scheduling)",
"Example: Configuring Forwarding Class Sets",
"Assigning CoS Components to In... |
traffic-engineering (OSPF) | traffic-engineering {
<advertise-unnumbered-interfaces>;
<credibility-protocol-preference>;
ignore-lsp-metrics;
multicast-rpf-routes;
no-topology;
l3-unicast-topology;
shortcuts {
lsp-metric-into-summary;
}
} | [edit logical-systems logical-system-name protocols (ospf | ospf3)],
[edit protocols (ospf | ospf3)] | Enable the OSPF traffic engineering features.
Default
Traffic engineering support is disabled. | [
{
"name": "advertise-unnumbered-interfaces",
"desc": "(Optional) (OSPFv2 only) Include the link-local identifier in the link-local"
},
{
"name": "credibility-protocol-preference",
"desc": "(Optional) (OSPFv2 only) Use the configured preference value for OSPF"
},
{
"name": "ignore-lsp-met... | 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.
multicast-rpf-routes option introduced in Junos OS Release 7.5.
advertise-unnumbered-interfaces option introduced in Junos OS Release 8.5.
Support for OSPFv3 (ospf3) introduced in Junos OS Release 9.4.
Support for OSPFv3 (ospf3) introduced in Junos OS Release 9.4 for EX... | [
"Example: Enabling OSPF Traffic Engineering Support"
] |
traffic-engineering (Passive TE Mode) | traffic-engineering {
remote-node-id address;
remote-node-router-id address;
} | [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id interface
interface-name passive],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast) area area-id interface interface-name passive],
[edit logical-systems logical-system-name ... | Configure an interface in OSPF passive traffic engineering mode to enable dynamic discovery of OSPF
AS boundary routers.
Default
OSPF passive traffic-engineering mode is disabled. | [
{
"name": "remote-node-id",
"desc": ""
},
{
"name": "address",
"desc": "IP address at the far end of the inter-AS link."
},
{
"name": "remote-node-router-id",
"desc": ""
},
{
"name": "address",
"desc": "Router ID at the far end of the inter-AS link. NOTE: The remote-node-... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.0.
Support for the realm statement introduced in Junos OS Release 9.2.
Support for the realm statement introduced in Junos OS Release 9.2 for EX Series switches.
remote-node-router-id address option introduced in Junos OS Release 14.2. | [
"Example: Configuring OSPF Passive Traffic Engineering Mode",
"Junos OS MPLS Applications User Guide"
] |
traffic-engineering (policy-options) | traffic-engineering {
apply-groups
apply-groups-except
groups
identifier
ipv4-prefix
ipv6-prefix
link ... | [edit policy-options policy-statement name from] | Specify traffic-engineering related parameters. | [
{
"name": "identifier",
"desc": ""
},
{
"name": "BGP-TE identifier (2..18446744073709551615)",
"desc": ""
},
{
"name": "ipv4-prefix",
"desc": ""
},
{
"name": "IPv4 prefix-related parameters",
"desc": ""
},
{
"name": "ipv6-prefix",
"desc": ""
},
{
"name... | routing | [
"Link-State Distribution using BGP"
] | |
traffic-engineering (Protocols BGP) | traffic-engineering {
unicast;
} | [edit logical-systems logical-system-name protocols bgp family],
[edit logical-systems logical-system-name protocols bgp group group-name family],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address family],
[edit logical-systems logical-system-name routing-instances routing-instan... | Enable traffic engineering address family. This generates a multiprotocol address family indicator (AFI)
and a subsequent address family identifier (SAFI) to be negotiated with the BGP peers.
The BGP network layer reachability information (NLRI) information is exchanged between the peers only
when the traffic engineeri... | [
{
"name": "unicast",
"desc": "Include BGP-TE NLRI."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2.
Statement introduced on QFX5100 switches in Junos OS Release 15.1
Statement introduced on QFX10000 switches in Junos OS Release 17.1. | [
"Example: Configuring Link State Distribution Using BGP"
] |
traffic-engineering (Protocols IS-IS) | traffic-engineering {
advertisement;
disable;
credibility-protocol-preference;
family;
ignore-lsp-metrics;
ipv6
l3-unicast-topology;
multipath {
lsp-equal-cost;
}
tunnel-source-protocol (Protocols OSPF);
} | [edit logical-systems logical-system-name protocols isis],
[edit protocols isis] | Configure traffic engineering properties for IS-IS.
IS-IS always performs shortest-path-first (SPF) calculations to determine next hops. For prefixes
reachable through a particular next hop, IS-IS places that next hop for that prefix in the inet.0 routing
table. In addition, for routers running MPLS, IS-IS installs the... | [
{
"name": "advertisement",
"desc": "Advertise TE parameters even if RSVP is not turned on."
},
{
"name": "credibility-protocol-",
"desc": ""
},
{
"name": "preference",
"desc": "Specify that IS-IS should use the configured protocol preference for IGP routes to determine the traffic en... | 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 the family statement introduced in Junos OS Release 9.3.
Support for the credibility-protocol-preference statement introduced in Junos OS Release 9.4.
Support for the multipath statement introduced in Junos OS Release 9.6.
Support for the lsp-equal-cost stat... | [
"Example: Enabling OSPF Traffic Engineering Support",
"Example: Enabling IS-IS Traffic Engineering Support",
"Using Labeled-Switched Paths to Augment SPF to Compute IGP Shortcuts"
] |
traffic-engineering (Protocols MPLS) | traffic-engineering (bgp | bgp-igp | bgp-igp-both-ribs | mpls-forwarding); | [edit logical-systems logical-system-name protocols mpls],
[edit protocols mpls] | Select whether MPLS performs traffic engineering on BGP destinations only or on both BGP and IGP
destinations. Affects only LSPs originating from this routing device, not transit or egress LSPs.
Default
bgp | [
{
"name": "bgp",
"desc": "On BGP destinations only. Ingress routes are installed in the inet.3 routing table."
},
{
"name": "bgp-igp",
"desc": "On both BGP and IGP destinations. Ingress routes are installed in the inet.0 routing table. If IGP"
},
{
"name": "bgp-igp-both-ribs",
"desc"... | 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 for LSPs",
"Configuring MPLS on Provider Edge Switches Using IP-Over-MPLS"
] |
traffic-engineering (SR-TE import policy) | traffic-engineering {
database;
} | [edit protocols source-packet-routing (Segment Routing Traffic Engineering)] | Enable export of all SPRING-TE policies into TED. | [
{
"name": "database",
"desc": "Enable export of all Spring-TE policies into the Traffic engineering database. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.4R1. | [] |
traffic-engineering | traffic-engineering {
disable;
} | [edit protocols (ospf | isis)] | Enable the traffic engineering features of the specified routing protocol.
Default
Traffic engineering is disabled.
Starting in Junos OS release 15.1, traffic engineering is enabled by default whenever the IS-IS protocol is
enabled. You can disable it by including the disable statement at the [edit protocols isis traff... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Example: Configuring MPLS on EX8200 and EX4500 Switches",
"Configuring MPLS on Provider Edge EX8200 and EX4500 Switches Using Circuit Cross-Connect",
"Configuring MPLS on Provider Edge Switches Using IP-Over-MPLS",
"Configuring MPLS on EX8200 and EX4500 Provider Switches",
"Configuring an OSPF Network (J-W... |
traffic-load-balance (Traffic Load Balancer) | traffic-load-balance {
instance instance-name {
client-interface client-interface;
client-vrf client-vrf;
group group-name {
control-interface control-interface-name;
health-check-interface-subunit health-check-interface-subunit;
network-monitoring-profile... | [edit services] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card.
Support added for control-interface and service-id options for Connected Security Distributed Services
(CSDS) in Junos OS Release 25.4... | [
"Traffic Load Balancer Overview",
"Configuring TLB"
] |
traffic-manager | traffic-manager {
egress-shaping-overhead number;
} | [edit chassis fpc slot-number],
[edit chassis fpc slot-number pic pic-number],
[edit chassis fpc slot-number pic pic-number port port-number],
[edit chassis lcc number fpc slot-number pic pic-number] | Enable CoS queuing, scheduling, and shaping.
NOTE: Committing changes to traffic-manager automatically restarts any necessary
components (PICs, DPCs, or FPCs). | [
{
"name": "buffer-monitor-",
"desc": ""
},
{
"name": "enable",
"desc": "Enable port buffer monitoring. Buffer utilization data is collected in one-second intervals and compared with the data from the previous interval. The larger value is kept to keep track of peak buffer occupancy for each queu... | 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. | [
"Enabling a Timestamp for Ingress and Egress Queue Packets"
] |
traffic-options | traffic-options {
sessions-per-client {
limit value;
over-limit (block | log-and-permit);
}
} | [edit security utm utm-policy policy-name] | In an attempt to consume all available resources and hinder the ability of the device, a malicious user
might generate a large amount of traffic all at once. To prevent such activity from succeeding, you can
impose a session throttle.
Starting in Junos OS Release 18.2R1 , we've deprecated the traffic-options statement ... | [] | 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. | [] |
traffic-selector | traffic-selector traffic-selector-name {
local-ip ip-address/netmask;
remote-ip ip-address/netmask;
preference pref_value;
protocol protocol_name/protocol_id;
source-port low-high;
destination-port low-high;
metric metric_value;
description description_value;
term term_name {
loc... | [edit security ipsec vpn vpn-name] | A traffic selector is an agreement between IKE peers to permit traffic through a tunnel, if the traffic
matches a specified pair of local IP address range, remote IP address range, source port range,
destination port range, and protocol. This functionality is supported only for IKEv2.
In the Junos OS Releases earlier t... | [
{
"name": "local-ip ip-address/",
"desc": ""
},
{
"name": "netmask",
"desc": "A local IP address or a local subnetwork protected by the local VPN device."
},
{
"name": "remote-ip ip-address/",
"desc": ""
},
{
"name": "netmask",
"desc": "A remote IP address or a remote sub... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10.
term, protocol, source-port, destination-port, metric, and description options introduced in Junos OS Release
21.1R1.
preference pref_value option introduced in Junos OS Release 22.2R1. | [
"IPsec Overview"
] |
traffic-statistics (Protocols BGP) | traffic-statistics {
labeled-path
file filename <world-readable | no-world-readable>;
interval seconds;
} | [edit logical-systems logical-system-name protocols bgp family (inet | inet6) labeled-unicast],
[edit logical-systems logical-system-name protocols bgp group group-name family (inet | inet6)
labeled-unicast],
[edit protocols bgp family (inet | inet6) labeled-unicast],
[edit protocols bgp group group-name family (inet ... | Enable the collection of traffic statistics for interprovider or carrier-of-carriers VPNs. | [
{
"name": "file filename",
"desc": "Specify a filename for the BGP labeled–unicast traffic statistics file. If you do not specify a"
},
{
"name": "interval seconds",
"desc": "Specify how often BGP labeled-unicast traffic statistics are collected."
},
{
"name": "labeled-path",
"desc":... | 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.
labeled-path introduced in Junos OS Release 18.1R1 for the MX Series. | [
"Configuring BGP to Gather Interprovider and Carrier-of-Carriers VPNs Statistics",
"MPLS Feature Support on QFX Series and EX4600 Switches",
"Understanding Interprovider and Carrier-of-Carriers VPNs"
] |
traffic-statistics (Protocols IS-IS) | traffic-statistics auto-bandwidth auto-bandwidth statistics-granularity per-interface per-
interface; | [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 traffic measuring on the SPRING link. RSVP-TE needs to measure the bandwidth utilized by
SPRING and estimate the available bandwidth at its disposal for traffic engineering. Traffic statistics are
collected at a configured interval. The average of the measured SPRING bandwidth is reported to RSVP
only when a se... | [
{
"name": "auto-bandwidth auto-bandwidth",
"desc": "Specify the name of auto bandwidth."
},
{
"name": "statistics-granularity per-interface",
"desc": "Specify the interface where you need to measure traffic statistics of SPRING traffic."
}
] | 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. | [] |
traffic-statistics (Protocols LDP) | traffic-statistics {
file filename <files number> <size size> <world-readable | no-world-readable>;
interval seconds;
no-penultimate-hop;
} | [edit logical-systems logical-system-name protocols ldp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp],
[edit protocols ldp],
[edit routing-instances routing-instance-name protocols ldp] | LDP traffic statistics display the amount of traffic passed through a router for a particular FEC. | [
{
"name": "file filename",
"desc": "Name of the file to receive the output of the LDP statistics operation. Enclose the name"
},
{
"name": "files number",
"desc": "(Optional) Maximum number of LDP statistics files. When a statistics file named ldp-stat"
},
{
"name": "interval seconds",
... | 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. | [
"Collecting LDP Statistics"
] |
traffic-statistics (Services Analytics) | traffic-statistics {
file filename {
files number-of-files;
size size;
}
interval interval;
} | [edit services analytics] | Enable the logging of traffic statistics in a local file. This statement does not enable traffic statistics
monitoring.
To enable the monitoring of traffic statistics, configure the traffic-statistics configuration statement at
the [edit services analytics interfaces] hierarchy level.
Default
This feature is disabled b... | [
{
"name": "file",
"desc": ""
},
{
"name": "filename",
"desc": "Specify a filename for storing the traffic statistics in the JavaScript Object Notification (JSON) format. The file is stored in the /var/log/ directory of your device. If you do not specify a filename, the data is not stored in a fi... | 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. | [
"Network Analytics Overview"
] |
traffic-statistics-labeled-path | traffic-statistics-labeled-path {
file filename <files files> <size size> <(world-readable | no-world-readable)>;
interval seconds;
} | [edit logical-systems name protocols bgp],
[edit logical-systems name routing-instances name protocols bgp],
[edit protocols bgp],
[edit routing-instances name protocols bgp] | Enable collection of periodic ingress labeled statistics for BGP label-switched paths in a network
configured with segment routing. The traffic statistics are collected at a specified time interval and saved
in a specified file. To collect traffic statistics of labeled unicast IPv4 and IPv6 families for specific BGP
gr... | [
{
"name": "file filename",
"desc": "Specify a filename to collect traffic statistics."
},
{
"name": "interval",
"desc": "Specify a time interval in seconds to collect traffic statistics. Range: 60 through 65535 seconds."
},
{
"name": "size",
"desc": "(Optional) Specify the size of t... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1R1. | [
"Enabling Traffic Statistics Collection for BGP Labeled Unicast"
] |
transaction-timeout | transaction-timeout value-in-seconds; | [edit logical-systems name security alg mgcp],
[edit logical-systems name tenants name security alg mgcp],
[edit security alg mgcp],
[edit services alg mgcp],
[edit tenants name security alg mgcp] | Specify the timeout value for Media Gateway Control Protocol (MGCP) transactions. If the timeout
value exceeds, the MGCP transactions stops. | [
{
"name": "value-in-seconds",
"desc": "Timeout value."
}
] | 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. | [] |
transfer | transfer {
record-level number;
timeout seconds;
} | [edit services flow-collector file-specification variant variant-number] | Specify when to send the flow collection file. The file is sent when either of the two conditions is met. | [
{
"name": "record-level number",
"desc": "Use the specified number of flow collection files collected."
},
{
"name": "timeout seconds",
"desc": "Use the specified timeout duration."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring File Formats"
] |
transfer-delay (Event Policy) | transfer-delay seconds; | [edit event-options destinations destination-name],
[edit event-options policy policy-name then event-script filename destination destination-name],
[edit event-options policy policy-name then execute-commands destination destination-name],
[edit event-options policy policy-name then upload filename (filename | committ... | Configure a delay before transferring files. This allows the files to be completely generated before the
upload starts. If you configure a transfer delay at the [edit event-options destination destination-name]
hierarchy level and at one of the [edit event-options policy policy-name then ...] hierarchy levels, the
resu... | [
{
"name": "seconds",
"desc": "Duration of the delay before files are uploaded."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5.
Support at the [edit event-options policy policy-name then ...] hierarchy levels introduced in Junos OS
Release 8.4. | [
"Configure the Delay Before Files Are Uploaded",
"Define Destinations for Event Policy File Archiving"
] |
transfer-interval | transfer-interval minutes; | [edit accounting-options file filename] | Specify the length of time the file remains open and receives new statistics before it is closed and
transferred to an archive site. | [
{
"name": "minutes",
"desc": "Time the file remains open and receives new statistics before it is closed and transferred to an"
}
] | 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 Accounting Options, Source Class Usage and Destination Class Usage Options"
] |
transfer-log-archive | transfer-log-archive {
archive-sites {
ftp:url {
password "password";
username username;
}
}
filename-prefix prefix;
maximum-age minutes;
} | [edit services flow-collector] | Configure the filename prefix, maximum age, and destination FTP server for log files containing the
transfer activity history for a flow collector interface.
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 Transfer Logs"
] |
transient-filter | transient-filter transient filter name | [edit firewall family firewall family name filter parent filter name] | Configure a transient firewall filter for a parent firewall filter.
When the parent firewall filter is modified, the make-before-break (MBB) process of the system
reprograms the modified parent firewall filter in the hardware. Depending on the size of the parent
firewall filter, this process may take time. In the inter... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved 24.1R1 | [] |
transit (Chained Composite Next Hops) | transit {
(all | no-all);
(l2vpn | no-l2vpn);
(l3vpn | no-l3vpn);
(labeled-bgp | no-labeled-bgp);
(ldp | no-ldp);
(ldp-p2mp | no-ldp-p2mp);
lsp-statistics-from-route;
(rsvp | no-rsvp);
(rsvp-p2mp | no-rsvp-p2mp);
(static | no-static);
} | [edit logical-systems logical-system-name routing-options forwarding-table chained-composite-
next-hop],
[edit routing-options forwarding-table chained-composite-next-hop]
NOTE: The [edit logical-systems] hierarchy level is not supported on the QFX10000
switches. | Allows you to configure the chained composite next hops transit configuration options for devices
handling transit traffic in the network. This statement and the associated functionality is available only
on PTX Packet Transport Routers, QFX10000 switches, and MX204, MX480, MX960, MX10003, and
VMX routers.
Default
All ... | [
{
"name": "all | no-all",
"desc": "Enable or disable chained composite next-hops for all of the possible packet transit protocols and applications. The all | no-all statements do not apply to the lsp-statistics-from-route statement."
},
{
"name": "l2vpn | no-l2vpn",
"desc": "Enable or disable ch... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Accepting Route Updates with Unique Inner VPN Labels in Layer 3 VPNs"
] |
transit | transit incoming-label {
bandwidth bps;
description string;
link-protection bypass-name name;
member-interface member-interface;
next-hop (address | interface-name | address/interface-name);
node-protection bypass-name name next-next-label label;
pop;
stitch {
bandwidth bps;
... | [edit logical-systems name protocols mpls static-label-switched-path name],
[edit logical-systems name routing-instances name protocols mpls static-label-switched-path name],
[edit logical-systems name tenants name routing-instances name protocols mpls static-label-switched-
path name],
[edit protocols mpls static-la... | Configure a transit static LSP.
NOTE: When configuring transit static LSPs with label operation as stitch, the configured
next-hop can only be a valid IP address and not an interface name. | [
{
"name": "incoming-label",
"desc": "Incoming label value. Values: Default: 1000000 through 1048575 Range: 16 through 1048575"
},
{
"name": "member-interface",
"desc": "Aggregated Ethernet (AE) member interface name."
}
] | 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.
switch option introduced in Junos OS Release 14.1X53-D25.
member-interface option introduced in Junos OS Release 17.4R1 for the MX Series and PTX 5000. | [
"Configuring Static LSPs",
"Configuring Static Adjacency Segment Identifier for Aggregate Ethernet Member Links Using Single-",
"Hop Static LSP"
] |
transit-lsp-association | transit-lsp-association transit-association-lsp-group-name {
from-1 address-of-associated-lsp-1;
from-2 address-of-associated-lsp-2;
lsp-name-1 name-of-associated-lsp-1;
lsp-name-2 name-of-associated-lsp-2;
} | [edit protocols mpls] | Associate two label-swiched paths (LSPs) at a transit node to configure a path for sending and receiving
GAL and G-Ach messages for MPLS-TP OAM. | [
{
"name": "transit-association-lsp-group-name",
"desc": "Name of the transit association LSP group."
},
{
"name": "from-1 address-of-associated-lsp-1",
"desc": "Address of the first associated LSP."
},
{
"name": "from-2 address-of-associated-lsp-2",
"desc": "Address of the second ass... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Example: Configuring the MPLS Transport Profile for OAM"
] |
translated | translated {
address-pooling paired;
clat-prefix clat-prefix;
cclat-ipv6-prefix-length
destination-pool nat-pool-name;
destination-prefix destination-prefix;
dns-alg-pool dns-alg-pool;
dns-alg-prefix dns-alg-prefix;
filtering-type endpoint-independent;
mapping-type endpoint-independe... | [edit services nat rule rule-name term term-name then] | Define properties for translated traffic. | [] | 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"
] |
translated-port | translated-port port id; | [edit services nat port-forwarding map-name] | Specify the port to which all traffic will be translated.
The translated-port statement is supported on the MS-DPC, MS-100, MS-400, and MS-500
MultiServices PICS. Starting in Junos OS Release 17.4R1, the translated-port statement is also supported
on the MS-MPC and MS-MIC. | [
{
"name": "port id",
"desc": "The port number to which traffic will be translated."
}
] | 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 Port Forwarding for Static Destination Address Translation",
"Configuring Port Forwarding Without Destination Address Translation"
] |
translation | translation {
max-datasize;
} | [edit system scripts] | Configure options for translation scripts. | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Storing and Enabling Scripts"
] |
translation-table | translation-table {
(to-dscp-from-dscp | to-dscp-ipv6-from-dscp-ipv6 | to-exp-from-exp | to-inet-precedence-from-
inet-precedence) table-name {
to-code-point value from-code-points (* | [ values ]);
}
} | [edit class-of-service] | For an Enhanced IQ PIC or Multiservices PIC, specify the input translation tables. You must also apply
the translation table to a logical interface on the Enhanced IQ PIC or Multiservices PIC.
Default
If you do not include this statement, the ToS bit values in received packet headers are not changed by
the PIC. | [
{
"name": "to-dscp-from-dscp",
"desc": "(Optional) Translate incoming IPv4 DSCP values to new values. You must also configure"
},
{
"name": "to-dscp-ipv6-from-dscp-ipv6",
"desc": "(Optional) Translate incoming IPv6 DSCP values to new values. You must also"
},
{
"name": "to-inet-precedenc... | 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 on Multiservices PIC added in Junos OS Release 9.5. | [
"Configuring ToS Translation Tables",
"Multiservices PIC ToS Translation"
] |
translation-type | translation-type (basic-nat-pt | basic-nat44 | basic-nat66 | nat-44 | deterministic-napt44 |
deterministic-napt64 | dnat-44 | dynamic-nat44 | napt-44 | napt-66 | napt-pt | nptv6 | stateful-
nat464 | stateful-nat64 | twice-basic-nat-44 | twice-dynamic-nat-44 | twice-napt-44) | [edit services nat rule rule-name term term-name then translated] | Specify the NAT translation types. To identify the interface cards and Junos OS releases that support
each translations type, see Carrier-Grade NAT Feature Comparison for Junos Address Aware by Type of
Interface Card. | [
{
"name": "basic-nat44",
"desc": "Translate the source address statically (IPv4 to IPv4)."
},
{
"name": "basic-nat66",
"desc": "Translate the source address statically (IPv6 to IPv6)."
},
{
"name": "basic-nat-pt",
"desc": "Translate the addresses of IPv6 hosts as they originate sessi... | 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.
The following options introduced in Junos OS Release 11.2, replacing all previous options.
•
basic-nat44
•
basic-nat66
•
basic-nat-pt
•
dnat-44
•
dynamic-nat44
•
napt-44
•
napt-66
•
napt-pt
•
stateful-nat64
deterministic-napt44 option introduced in Junos OS Release 12.... | [
"Network Address Translation Rules Overview"
] |
translation-vni | translation-vni vni (1..16777214); | [edit routing-instances routing-instance-name vlans vlan-name vxlan]
[edit routing-instances routing-instance-name vxlan]
[edit vlans vlan-name vxlan] | Configure a VXLAN network identifier (VNI) to which a Juniper Networks switch will translate a VNI in a
packet that it is forwarding. The Juniper Networks switch translates the VNI while it is forwarding traffic
in the following seamless EVPN-VXLAN stitching use cases:
•
From one EVPN-VXLAN point of delivery (POD) to a... | [
{
"name": "vni",
"desc": "Numeric value that represents the VNI to which the VNI in a packet is translated. Range: 1through 16777214"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.3R1. | [] |
transmit-clock | transmit-clock invert; | [edit interfaces interface-name serial-options] | Configure the transmit clock signal. | [
{
"name": "invert",
"desc": "Shift the clock phase 180 degrees."
}
] | 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 the Serial Clocking Mode"
] |
transmit-failure-threshold (RFC 2544 Benchmarking) | transmit-failure-threshold; | [edit services rpm rfc2544-benchmarkingtests test-name test-name] | Specifies the failure threshold value of the transmit test frames. | [] | 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"
] |
transmit-interval (BFD Liveness Detection) | transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
} | [edit logical-systems name routing-instances name protocols (evpn | l2vpn | vpls) oam bfd-liveness-
detection],
[edit logical-systems name routing-instances name protocols (evpn | l2vpn | vpls) neighbor neighbor-
id oam bfd-liveness-detection],
[edit logical-systems name routing-instances name protocols (evpn | l2vpn ... | Specify the transmit interval for the bfd-liveness-detection statement. The negotiated transmit interval for
a peer is the interval between the sending of BFD packets to peers. The receive interval for a peer is the
minimum time that it requires between packets sent from its peer; the receive interval is not negotiated... | [
{
"name": "minimum-interval",
"desc": ""
},
{
"name": "milliseconds",
"desc": "Configure the minimum interval at which the local routing device transmits hello packets to a neighbor with which it has established a BFD session. Optionally, instead of using this statement at this hierarchy level, ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2.
Support for BFD authentication introduced in Junos OS Release 9.6. | [
"Configuring BFD for Layer 2 VPN and VPLS",
"Example: Configuring BFD for Static Routes for Faster Network Failure Detection",
"bfd-liveness-detection (BGP)"
] |
transmit-interval (LAG) | transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
} | [edit interfaces aex aggregated-ether-options bfd-liveness-detection] | Configure the minimum interval and the threshold for transmission of BFD packets for aggregated
Ethernet interfaces. | [
{
"name": "minimum-interval",
"desc": ""
},
{
"name": "milliseconds",
"desc": "Specify the minimum time interval between two transmissions of packets. Range: 1 through 255,000"
},
{
"name": "threshold",
"desc": ""
},
{
"name": "milliseconds",
"desc": "Specify the maximum... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Configuring Micro BFD Sessions for LAG",
"Example: Configuring Independent Micro BFD Sessions for LAG",
"Understanding Independent Micro BFD Sessions for LAG"
] |
transmit-interval (Liveness Detection) | transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
} | [edit protocols iccp peer liveness-detection] | Configure the Bidirectional Forwarding Detection (BFD) transmit interval. The negotiated transmit
interval for a peer is the interval between the sending of BFD liveness detection requests to peers. The
receive interval for a peer is the minimum interval between receiving packets sent from its peer; the
receive interva... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [] |
transmit-interval (MACsec for MX Series) | transmit-interval interval; | [edit security macsec connectivity-association connectivity-association-name mka] | Specifies the transmit interval for MACsec Key Agreement (MKA) protocol data units (PDUs).
The MKA transmit interval setting sets the frequency for how often the MKA PDU is sent to the directly
connected device to maintain MACsec on a point-to-point Ethernet link. A lower interval increases
bandwidth overhead on the li... | [
{
"name": "interval",
"desc": "Specifies the transmit interval, in milliseconds."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Media Access Control Security (MACsec) on Routers"
] |
transmit-interval (MACsec) | transmit-interval interval; | [edit security macsec connectivity-association mka] | Specifies the transmit interval for MACsec Key Agreement (MKA) protocol data units (PDUs).
The MKA transmit interval setting sets the frequency for how often the MKA PDU is sent to the directly
connected device to maintain MACsec on a point-to-point Ethernet link. A lower interval increases
bandwidth overhead on the li... | [
{
"name": "interval",
"desc": "Specifies the transmit interval, in milliseconds."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D60. | [
"Understanding Media Access Control Security (MACsec)",
"Configuring Media Access Control Security (MACsec)"
] |
transmit-interval (PIM BFD Liveness Detection) | transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
} | [edit protocols pim interface interface-name bfd-liveness-detection],
[edit routing-instances routing-instance-name protocols pim interface interface-name bfd-
liveness-detection] | Specify the transmit interval for the bfd-liveness-detection statement. The negotiated transmit interval for
a peer is the interval between the sending of BFD packets to peers. The receive interval for a peer is the
minimum interval between receiving packets sent from its peer; the receive interval is not negotiated
be... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2.
Support for BFD authentication introduced in Junos OS Release 9.6. | [
"Configuring BFD for PIM"
] |
transmit-interval | transmit-interval {
threshold milliseconds;
minimum-interval milliseconds;
} | [edit system services dhcp-local-server liveness-detection method bfd],
[edit system services dhcp-local-server dhcpv6 liveness-detection method bfd],
[edit forwarding-options dhcp-relay liveness-detection method bfd], [edit forwarding-options
dhcp-relay dhcpv6 liveness-detection method bfd],
[edit system services dhc... | Configure the Bidirectional Forwarding Detection (BFD) transmit interval.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Example: Configuring Group Liveness Detection with BFD for DHCP Local Server Clients",
"Example: Configuring Global Liveness Detection with BFD for DHCP Relay Agent Clients"
] |
transmit-rate (Dynamic Schedulers) | transmit-rate (rate | percent percentage | remainder | percent percentage $junos-cos-scheduler-
tx) <exact | rate-limit>; | [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] | Specify the transmit rate or percentage for a scheduler in a dynamic profile.
Default
If you do not include this statement, the default scheduler transmission rate and buffer size percentages
for queues 0 through 7 are 95, 0, 0, 5, 0, 0, 0, and 0 percent. | [
{
"name": "rate",
"desc": "Transmission rate, in bps. You can specify a value in bits per second either as a complete decimal"
},
{
"name": "percent percentage",
"desc": "Percentage of transmission capacity. A percentage of zero drops all packets in the"
},
{
"name": "remainder",
"de... | 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.
The $junos-cos-scheduler-tx predefined variable introduced in Junos OS Release 9.4. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Schedulers in a Dynamic Profile for Subscriber Access"
] |
transmit-rate (EX Series Switches) | transmit-rate (rate | percent percentage | remainder); | [edit class-of-service schedulers scheduler-name] | Specify the transmit rate or percentage for a scheduler.
Default
If you do not include this statement, the default scheduler transmission rate and buffer size percentages
for queues 0 through 7 are 95, 0, 0, 0, 0, 0, 0, and 5 percent. | [
{
"name": "rate",
"desc": "Transmission rate, in bps. You can specify a value in bits per second either as a complete decimal number or as a decimal number followed by the abbreviation k (1000), m (1,000,000), or g (1,000,000,000). Range: 3200 through 160,000,000,000 bps (EX4300 switches only) 8000 through... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Example: Configuring CoS on EX Series Switches",
"Defining CoS Schedulers and Scheduler Maps (CLI Procedure)",
"Defining CoS Schedulers (J-Web Procedure)",
"Understanding CoS Schedulers"
] |
transmit-rate (Schedulers) | transmit-rate (rate | percent percentage | remainder percentage) <exact | rate-limit>; | [edit class-of-service schedulers scheduler-name] | Specify the transmit rate or percentage for a scheduler.
Default
If you do not include this statement, the default scheduler transmission rate and buffer size percentages
for queues 0 through 7 are 95, 0, 0, 5, 0, 0, 0, and 0 percent, respectively.
NOTE: On PTX10008 and PTX10016 routers, the default scheduler transmis... | [
{
"name": "exact",
"desc": "(Optional) Enforce the exact transmission rate. Under sustained congestion, a rate-controlled queue that goes into negative credit fills up and eventually drops packets. This value should never exceed the rate-controlled amount. For PTX Series routers, this option is allowed only... | 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.
rate-limit option introduced in Junos OS Release 8.3. Applied to the Multiservices PICs in Junos OS
Release 9.4. | [
"Configuring Schedulers",
"Configuring Scheduler Transmission Rate",
"Understanding Scheduling on PTX Series Routers"
] |
transmit-rate | [edit class-of-service schedulers scheduler-name] | On QFX5100, EX4600, QFX3500, and QFX3600 switches, and on QFabric systems, the transmit rate
specifies the minimum guaranteed transmission rate or percentage for a queue (forwarding class)
scheduler. The queue transmit rate also determines the amount of excess (extra) priority group
bandwidth that the queue can share o... | [
{
"name": "rate",
"desc": "Minimum transmission rate for the queue, in bps. You can specify a value in bits-per-second either"
},
{
"name": "percent percentage",
"desc": "Minimum percentage of transmission capacity allocated to the queue."
},
{
"name": "exact",
"desc": "(QFX10000 swi... | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
Exact option introduced in Junos OS Release 15.1X53-D10 for the QFX Series. | [
"Example: Configuring CoS Hierarchical Port Scheduling (ETS)",
"Example: Configuring Queue Schedulers",
"Example: Configuring Queue Schedulers for Port Scheduling",
"Understanding CoS Output Queue Schedulers",
"Understanding CoS Port Schedulers on QFX Switches"
] | |
transparent | transparent; | [edit class-of-service interfaces interface-name unit logical-unit-number classifiers ieee802.1
vlan-tag] | Packet classification based on the transparent VLAN tag. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2 | [] |
transparent-proxy | transparent-proxy {
profile name {
drop-on-dns-error;
dynamic-web-application;
dynamic-web-application-group;
proxy-address name {
ip ip;
port port;
}
}
} | [edit services web-proxy] | Configure transparent web proxy profile.
Use the Transparent web proxy feature on an SRX Series Firewall to route traffic through an external
proxy or bypass it for certain applications. Configure a profile with proxy details and bypassed
applications to send traffic directly to the target webserver when needed.
NOTE: ... | [
{
"name": "profile name",
"desc": "Name of the transparent web proxy profile."
},
{
"name": "drop-on-dns-error",
"desc": "Drop the web proxy session on DNS error."
},
{
"name": "dynamic-web-application",
"desc": "Dynamic web application. Specify dynamic applications such as MS Office... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1 | [] |
transport (Diameter Base Protocol) | transport transport-name {
address;
logical-system logical-system-name <routing-instance routing-instance-name >;
routing-instance routing-instance-name
} | [edit diameter] | Configure the Diameter instance and the local IP address for the Diameter local transport connection. | [
{
"name": "transport-name",
"desc": "Name of the transport."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Diameter Base Protocol",
"Diameter Base Protocol"
] |
transport (Diameter Peer) | transport transport-name; | [edit diameter peer peer-name No Link Title] | Specify the transport layer connection to be used for establishing active connections to the peer.
Default
The transport is defined in the default logical system and master routing instance. | [
{
"name": "transport-name",
"desc": "Name of the transport."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Diameter Base Protocol",
"Diameter Base Protocol"
] |
transport (Next Gen Services Syslog Message Security) | transport; | [edit services service-set name syslog | Specify the transport protocol category for which you want to collect local logs. By default, UDP is set
as the transport protocol. | [
{
"name": "apply-groups",
"desc": "Groups from which to inherit configuration data"
},
{
"name": "apply-groups-except",
"desc": "Don't inherit configuration data from these groups"
},
{
"name": "protocol",
"desc": "Set security log transport protocol for the device. You can set the p... | system | Statement introduced in Junos OS Release 19.3R2. | [
"Understanding Next Gen Services CGNAT Global System Logging",
"Enabling Global System Logging for Next Gen Services",
"Configuring System Logging to One or More Remote Servers for Next Gen Services",
"Configuring Local System Logging for Next Gen Services"
] |
transport (Protocols BGP) | transport {
accepted-prefix-limit {
drop-excess< limit-threshold>;
hide-excess< limit-threshold>;
maximum maximum;
teardown<idle-timeout(forever | timeout)>< limit-threshold>;
}
accept-srv6-service;
add-path {
receive;
send {
include-backup-path include-backup-path;
... | [edit fabric protocols bgp family inet6],
[edit fabric protocols bgp group name family inet6],
[edit fabric protocols bgp group name neighbor name family inet6],
[edit logical-systems name protocols bgp family inet6],
[edit logical-systems name protocols bgp group name family inet6],
[edit logical-systems name protocol... | Enable Classful Transport (CT) NLRI for inet6 family in BGP networks. | [
{
"name": "accept-srv6-service",
"desc": "Accept SRv6 service."
},
{
"name": "advertise-srv6-service",
"desc": "Advertise SRv6 service."
},
{
"name": "aigp",
"desc": "Allow sending and receiving of AIGP attribute."
},
{
"name": "disable",
"desc": "Disable sending and rece... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.2R1. | [] |
transport (Security Log) | transport {
protocol (udp | tcp | tls);
tls-profile tls-profile-name;
tcp-connections tcp-connections;
} | [edit security log]
[edit security log stream stream-name]
[edit logical-systems name security log]
[edit tenants tenant-name security log]
[edit logical-systems name security log stream stream-name]
[edit tenants tenant-name security log stream stream-name] | Configure security log transport options. | [
{
"name": "protocol",
"desc": "Specify the type of transport protocol to be used to log the data."
},
{
"name": "UDP",
"desc": "Set the transport protocol to UDP."
},
{
"name": "TCP",
"desc": "Set the transport protocol to TCP."
},
{
"name": "TLS",
"desc": "Set the transp... | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D25.
The [edit logical-systems name security log] and [edit tenants tenant-name security log] hierarchy levels
introduced in Junos OS Release 19.1R1. | [
"Understanding AppTrack"
] |
transport (Services) | transport [ transport-protocols ]; | [edit services nat pool nat-pool-name pgcp] | Configure the BGF to select a NAT pool based on transport protocol type. | [
{
"name": "[ transport-protocol ]",
"desc": "One or more transport protocols."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
transport (System Syslog) | transport(tcp | tls | udp); | [edit system syslog host host-name] | Configure the system syslog transport option. Transport protocol is UDP by default. | [
{
"name": "tcp",
"desc": "Configure TCP as the transport protocol."
},
{
"name": "tls",
"desc": "Configure TLS as the transport protocol. TLS uses certificates to authenticate peers. Before configuring this statement, make sure that your device has CA certificate and the PKI."
},
{
"name... | Statement introduced in Junos OS Release 21.2R1 for EX Series switches and MX Series routers.
Statement introduced in Junos OS Release 21.3R1 for SRX Series and vSRX Virtual Firewall devices. | [
"Configure Syslog over TLS"
] | |
transport-address | transport-address (address | interface | router-id); | [edit logical-systems logical-system-name protocols ldp],
[edit logical-systems logical-system-name protocols ldp interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp],
[edit protocols ldp],
[edit protocols ldp interface interface-name],
[edit routin... | Enables you to configure the IP address used to specify the TCP session for the LDP session. Routers
must first establish a TCP session between one another before they can establish an LDP session. The
TCP session enables the routers to exchange the label advertisements needed for the LDP session. To
establish the TCP ... | [
{
"name": "address",
"desc": "Use the specified IP address as the transport address for the LDP session."
},
{
"name": "interface",
"desc": "Use the first IP address on the interface as the transport address for any LDP sessions to neighbors that can be reached over that interface. You cannot sp... | 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.
address option introduced in Junos OS Release 19.1R1 for all platforms. | [
"Specifying the Transport Address Used by LDP"
] |
transport-class | transport-class {
auto-create;
fallback {
none;
}
name (Transport-class) name {
color color;
fallback {
none;
}
tunnel-egress {
end-point endpoint-address {
import [ import-policy ... ];
}
}
}
any... | [edit routing-options] | Specify the transport layer options. | [
{
"name": "any-class",
"desc": "Specify the predefined transport class that collects tunnels of all transport classes."
},
{
"name": "color color",
"desc": "This is a 32bit color value mapping to any transport class. This auto derives"
},
{
"name": "auto-create",
"desc": "Auto create... | routing | Statement introduced in Junos OS Release 21.2R1. | [
"MPLS Traffic Engineering Configuration"
] |
transport-class | transport-class color; | [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... | By setting the transport-class for a specific LSP, you determine which RSVP tunnels are placed into
corresponding colored inet.3 tables.
NOTE: A maximum of 3 transport-class color tables are supported.
A maximum of 9000 LSPs are supported per transport-class.
A maximum of 9000 ingress replication provider tunnels are ... | [] | Statement introduced in Junos OS Release 24.4R1. | [] | |
transport-monitoring | transport-monitoring; | [edit interfaces] | Monitor the performance and state of packet transport for OTN and optics modules. The following
statistics are monitored:
•
Packet transport for ninety-six 15–minute intervals for the current 24 hours.
•
Cumulative data of the current 24 hours.
•
Cumulative data of the previous 24 hours.
If this statement is configured... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
transport-type | transport-type type; | [edit services hosted-services server-profile server-profile-name] | Configure the transport type. | [
{
"name": "type",
"desc": "Transport type."
}
] | 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. | [
"Configuring Active Flow Monitoring on PTX Series Packet Transport Routers"
] |
trap (Security IKE) | trap {
ipsec-tunnel-down ;
peer-down ;
} | [edit security ike trap] | ipsec-tunnel-down— By enabling the ipsec-tunnel-down option, the traps are generated for IPsec tunnel
going down only when the associated peer IKE SA is up.
peer-down—By enabling the peer-down option, the traps are generated when peer goes down. Traps for
the corresponding IPsec tunnels going down for the peer are not ... | [] | 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 | [
"Enable Peer Down and IPsec Tunnel Down Traps"
] |
trap (Security PKI) | trap {
all certificates number-of-days;
ca-identity number-of-days;
certificate-id number-of-days;
} | [edit security pki] | To configure certificate expiration trap and configure the number of days before to generate the trap.
how
Default
•
all certificates—60 days
•
ca-identity—60 days
•
certificate-id —60 days | [
{
"name": "all certificates number-of-days",
"desc": "Number of days to generate traps for all certificates. You can configure"
},
{
"name": "ca-identity number-of-days",
"desc": "Number of days to generate traps for specified CA certificate. You can"
},
{
"name": "certificate-id number-... | 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 | [
"Enable Peer Down and IPsec Tunnel Down Traps"
] |
trap | trap {
interval trap interval;
} | [edit security screen trap],
[edit tenants tenant-name security screen] | Traps are unsolicited messages sent from an SNMP agent to remote network management systems or
trap receivers. Many enterprises use SNMP traps as part of a fault-monitoring solution, in addition to
system logging. In Junos OS, SNMP traps are not forwarded by default. You can use the SNMP traps by
configuring a trap-gro... | [
{
"name": "interval",
"desc": "Configure the trap interval. Range: 1 through 3600 seconds Default: 2 seconds"
}
] | 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-D20.
The tenant option is introduced in Junos OS Release 18.3R1. | [] |
trap-group | [edit snmp] | Create a named group of hosts to receive the specified trap notifications. The name of the trap group is
embedded in SNMP trap notification packets as one variable binding (varbind) known as the community
name. At least one trap group must be configured for SNMP traps to be sent. | [
{
"name": "group-name",
"desc": "Name of the trap group. If the name includes spaces, enclose it in quotation marks (\" \")."
}
] | 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. | [] | |
trap-options | [edit snmp] | Using SNMP trap options, you can set the source address of every SNMP trap packet sent by the router
or switch to a single address, regardless of the outgoing interface. In addition, you can set the agent
address of each SNMPv1 trap. For more information about the contents of SNMPv1 traps, see RFC
1157.
Default
Disable... | [
{
"name": "context-oid",
"desc": "Add context oid in varbind of all traps originating from non-default logical system and routing instance. If your network management system is not able to handle prefixes such as <routing-instance name>@<trap-group-name> or <logical-system name>/<routing-instance name>@<tra... | 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.
context-oid option introduced in Junos OS Release 17.1. | [] | |
traps (Dynamic Profiles and Interfaces) | (traps | no-traps); | [edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-range interface-range-name] | Enable or disable the sending of Simple Network Management Protocol (SNMP) notifications when the
state of the connection changes.
(Enhanced subscriber management for MX Series routers) To enable SNMP notifications, you must first
configure the interface-mib statement at the [edit dynamic-profiles profile-name interfac... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Metro Routers.
Support at the [edit dynamic-profiles profile-name interfacesinterface-name] hierarchy level introduced in
Junos OS Release 15.1R3 on MX Series routers for enhanced subscriber manageme... | [
"Enabling or Disabling SNMP Notifications on Physical Interfaces",
"Enabling or Disabling SNMP Notifications on Logical Interfaces"
] |
traps (RPM and TWAMP) | traps traps; | [edit services monitoring rpm owner test test-name],
[edit services monitoring twamp client control-connection control-client-name],
[edit services monitoring twamp client control-connection control-client-name test-session session-
name] | Set the trap bit to generate SNMP traps for probes. Traps are sent if the configured threshold is met or
exceeded. For TWAMP, you can configure both control-connection and test-session traps for managed
clients, but only test-session traps for light clients. See SNMP MIB Explorer to learn more about the
SNMP MIB object... | [
{
"name": "traps",
"desc": "Specify one or more SNMP traps. The options are configured per test session, except for the control-connection-closed and the test-iteration-done options. These options are configured only for TWAMP, and only per control connection. The following options are supported:"
},
{
... | 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.
Support at the [edit services rpm twamp client control-connection control-client-name] and [edit services rpm
twamp client control-connection control-client-name test-session session-name] hierarchy levels introduced in
Junos OS Release 15.1 for MX Series routers.
Suppo... | [
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches",
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
tri-color (EX Series Switches) | tri-color {
classifiers {
(dscp | dscp-ipv6 |exp |ieee-802.1 | inet-precedence) classifier-name {
forwarding-class (Forwarding Policy) (class-name | assured-forwarding | best-effort |
expedited-forwarding | network-control) {
loss-priority (high | low | medium-high | medium-low)... | [edit class-of-service] | 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": "percent percentage",
"desc": "Size of the shared buffer as a percentage of the buffer allocated to the shared"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS 11.4 . | [
"Example: Configuring CoS on EX Series Switches",
"Understanding Junos OS CoS Components for EX Series Switches"
] |
tri-color | tri-color; | [edit class-of-service] | For IPv4 packets on M320, MX Series, T Series routers with Enhanced II Flexible PIC Concentrators
(FPCs), and EX Series switches, enable tricolor marking (TCM), as defined in RFC 2698.
Default
If you do not include this statement, tricolor marking is not enabled and the medium packet loss priority
(PLP) is not configur... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring and Applying Tricolor Marking Policers"
] |
trickling | trickling {
timeout value;
} | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name]
[edit security utm feature-profile anti-virus sophos-engine profile profile-name] | 15.1X49-D10
The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-
D10 onwards. | [
{
"name": "value",
"desc": "Timeout interval in seconds."
}
] | 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. Statement updated for
Sophos support in Jun... | [] |
trigger (CoS) | trigger type shaping-rate (percent percentage | rate); | [edit class-of-service adaptive-shapers adaptive-shaper-name] | Specify a trigger type and its associated rate. | [
{
"name": "type",
"desc": "The type of trigger. Currently, the trigger type can be becn only."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [] |
trigger (DHCP Local Server) | trigger {
radius-disconnect;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server reconfigure],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 reconfigure],
[edit logical-systems logical-system-name routing-i... | Configure behavior in response to a trigger for all DHCP clients or only the DHCP clients serviced by the
specified group of interfaces.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
Support at the [edit ... dhcpv6 ...] hierarchy levels introduced in Junos OS Release 10.4. | [
"Configuring Dynamic Reconfiguration of Extended Local Server Clients Overview",
"Configuring Reconfiguration of the Client on Receipt of RADIUS-Initiated Disconnect"
] |
trigger (Event Policy) | trigger (on | after | until) event-count; | [edit event-options policy policy-name within seconds] | Configure an event policy to trigger when an event or set of events occurs event-count times within a
specified time period.
Default
If you do not include this statement, the policy is executed on receipt of the first configured event. | [
{
"name": "after event-count",
"desc": "The policy is executed when the number of matching events received equals event-count + 1."
},
{
"name": "on event-count",
"desc": "The policy is executed when the number of matching events received equals event-count."
},
{
"name": "until event-co... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 8.4. | [
"Trigger an Event Policy Based on Event Count"
] |
trigger | trigger trigger-identifier (hold-time hold-time-value | ignore); | [edit interfaces interface-name otn-options] | Specify defect triggers.
Default
By default, triggers are ignored. | [
{
"name": "trigger-identifier",
"desc": "(For M Series, MX Series, SRX Series, and T Series routers only) Trigger identifier. It"
},
{
"name": "can be one of the following:",
"desc": ""
},
{
"name": "oc-lof",
"desc": "Optical channel Loss of Frame defect trigger."
},
{
"name"... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"10-Gigabit Ethernet OTN Options Configuration Overview",
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
trigger-link-failure | trigger-link-failure interface-name; | [edit interfaces lsq-fpc/pic/port lsq-failure-options] | List of SONET interfaces connected to the LSQ interface that can implement Automatic Protection
Switching (APS) if the Link Services IQ PIC fails. | [
{
"name": "interface-name",
"desc": "Name of SONET interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring the Association between LSQ and SONET Interfaces"
] |
trigger-type (LRF Profile) | trigger-type (session-close | volume); | [edit services lrf profile profile-name template template-name] | Configure the type of trigger that causes the generation of data records and transmission to the
collector. You can only configure one type of trigger.
Default
If you do not include the trigger-type statement, the default trigger is session-close. | [
{
"name": "session-close",
"desc": "Use the closing of the data session to cause the generation of data records and transmission to the collector."
},
{
"name": "volume",
"desc": "Use a data volume limit to cause the generation of data records and transmission to the collector. The data volume l... | 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"
] |
trio-flow-offload | trio-flow-offload minimum-bytes minimum-bytes; | [edit interfaces interface-name services-options] | Enable any plug-in or daemon on a PIC to generate a request to off-load flows to the Packet Forwarding
Engine. This command is available on MX Series routers with Modular Port Concentrators (MPCs) and
Modular Interface Cards (MICs).
NOTE: This feature is not supported for Broadband Edge subscribers (given that service... | [
{
"name": "minimum-bytes",
"desc": "Minimum number of bytes that trigger offloading. When this option is omitted, offloading"
}
] | 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 Flow Offloading on MX Series Routers"
] |
trust-option-82 | trust-option-82; | [edit forwarding-options dhcp-relay overrides],
[edit forwarding-options dhcp-relay group group-name overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay overrides],
[edit logical-systems logical-system-name forwarding-options dhcp-relay group group-name
overrides],
[edit logical-systems... | Enable processing of DHCP client packets that have a gateway IP address (giaddr) of 0 (zero) and contain
option 82 information. By default, the DHCP relay agent treats such packets as if they originated at an
untrusted source, and drops them without further processing. | [] | 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. | [
"Enable Processing of Untrusted Packets So Option 82 Information Can Be Used",
"Overriding the Default DHCP Relay Configuration Settings"
] |
trusted (DHCP Security) | trusted; | [edit vlans vlan-name forwarding-options dhcp-security group group-name overrides] | Specify that the interface in this group is trusted. DHCP snooping and DHCPv6 snooping do not apply
to the trusted interface, even if the VLAN is enabled for DHCP or DHCPv6 snooping. Likewise, DAI, IP
source guard, IPv6 source guard, and IPv6 neighbor discovery inspection—even if they are enabled for
the VLAN—do not ap... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10. | [
"Enabling a Trusted DHCP Server (ELS)",
"Understanding DHCP Snooping (non-ELS)"
] |
trusted | trusted; | [edit bridge-domains bridge-domain-name forwarding-options dhcp-security group group-name overrides] | Allow DHCP responses from the specified interface. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Enabling a Trusted DHCP Server (MX Series Routers)",
"Understanding and Using Trusted DHCP Servers"
] |
trusted-ca (Services) | trusted-ca (all | [ca-profile] ); | [edit services ssl proxy profile profile-name]
[edit services ssl termination profile profile-name]
[edit services ssl initiation profile profile-name] | Specify the list of trusted certificate authority profiles. | [
{
"name": "trusted-ca-name",
"desc": "Specify the certificate authority profile name."
},
{
"name": "all",
"desc": "Select all certificate authority profiles."
}
] | 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. | [
"Configuring SSL Forward Proxy",
"Firewall User Authentication Overview"
] |
trusted-ca | trusted-ca ca-profile-name; | [edit services service-set service-set-name ipsec-vpn-options]
[edit system ntp nts] | Identify one or more trusted IPsec certification authorities for system services and Network Time
Security (NTS) using Network Time Protocol (NTP)
Use set system ntp nts trusted-ca trusted-ca-group NTS-ca-group to specify ca-profiles by name, that are
trusted by the NTS clients. You can specify a trusted ca-group (defi... | [
{
"name": "ca-profile-name",
"desc": "Name of certification authority profile, which is configured at the [edit security pki]"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Configuring IPsec Service Sets"
] |
trusted-keys (DNSSEC) | trusted-keys {
(key dns-key | load-key-file url);
} | [edit system services dns dnssec] | Configure trusted keys in the DNS server. | [
{
"name": "key dns-key",
"desc": "Specify a DNS trusted key."
},
{
"name": "load-key-file url",
"desc": "Specifies the URL of the file that contains the DNS trusted keys."
}
] | 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. | [
"DNSSEC Overview",
"Example: Configuring Secure Domains and Trusted Keys for DNSSEC"
] |
tti | tti tti-identifier; | [edit interfaces interface-name otn-options] | Specify trace identifier options. | [
{
"name": "tti-identifier",
"desc": "Trace identifier. It can be one of the following:"
},
{
"name": "odu-dapi",
"desc": "Optical Channel Data Unit (ODU) Destination Access Point Identifier."
},
{
"name": "odu-expected-receive-dapi",
"desc": "ODU Expected Receive Destination Access P... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"10-Gigabit Ethernet OTN Options Configuration Overview",
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
ttl (Dynamic Flow Capture) | ttl hops; | [edit services dynamic-flow-capture capture-group client-name content-destination identifier] | Configure the time-to-live (TTL) value for the IP-IP header. | [
{
"name": "hops",
"desc": "TTL value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring the Content Destination"
] |
ttl (RPM probe) | ttl hop-count; | [edit services monitoring rpm owner name test name] | Specify the maximum hop count (TTL) for all types of probes (IPv4 and IPv6) in real-time performance
monitoring (RPM) and Two-Way Active Management Protocol (TWAMP). This can be useful when it is
necessary to restrict the scope of the RPM probes so a probe does not unintentionally monitor an
alternative path to the des... | [
{
"name": "hop-count",
"desc": "Prior to Junos OS Release 18.2R1, for RPM, the RPM client always sent a TTL of 64 to 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 for MX Series routers.
Statement introduced in Junos OS Evolved Release 20.1R1. | [
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches"
] |
ttl | ttl value; | [edit interfaces interface-name unit number tunnel] | Set the time-to-live value bit in the header of the outer IP packet. | [
{
"name": "value",
"desc": "Time-to-live value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Tunnel Services Overview"
] |
ttl-threshold | ttl-threshold number; | [edit applications application application-name] | Specify the traceroute time-to-live (TTL) threshold value. This value sets the acceptable level of network
penetration for trace routing. | [
{
"name": "number",
"desc": "TTL threshold value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"ALG Descriptions",
"Configuring the TTL Threshold",
"Examples: Configuring Application Protocols",
"Verifying the Output of ALG Sessions"
] |
tunable-name | tunable-name tunable-name {
tunable-value protocol-value;
} | [edit security idp sensor-configuration detector protocol-name protocol-name] | Specify the name of the tunable parameter to enable or disable the protocol detector for each of the
service. By default, the protocol decoders for all services are enabled. | [
{
"name": "tunable-name",
"desc": "Name of the specific tunable parameter."
}
] | 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. Support. | [] |
tunable-value | tunable-value protocol-value; | [edit security idp sensor-configuration detector protocol-name protocol-name tunable-name
tunable-name] | Specify the value of the tunable parameter to enable or disable the protocol detector for each of the
services. | [
{
"name": "tunable-value",
"desc": "Integer representing a selected option for the switch specified in tunable-name. The range of"
}
] | 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. Support. | [] |
tunables | tunables {
drop-on-zone-mismatch;
enable-logging;
max-route-change value;
no-l3l4-app-lookup
} | [edit security advance-policy-based-routing] | Configure the advanced policy-based (APBR) routing options to streamline the traffic handling.
You can streamline the traffic handling with APBR such as limiting the number of times a route can
change for a session, terminating the session if there is a mismatch between zones when APBR is being
applied in the middle of... | [
{
"name": "drop-on-zone-mismatch",
"desc": "Terminate the session instead of instead of allowing traffic to traverse through the same route bypassing APBR."
},
{
"name": "enable-logging",
"desc": "Enable logging to record events that occur on the device for APBR-related operations."
},
{
... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D110. | [
"Example: Configuring Advanced Policy-Based Routing Policies",
"Advanced Policy-Based Routing"
] |
tunnel (EX Series Switches) | tunnel {
destination destination-address;
source source-address;
ttl number;
} | [edit 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.
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 12.1. | [
"Configuring Generic Routing Encapsulation Tunneling"
] |
tunnel (fti) | tunnel {
encapsulation {
( gre | ipip | udp );
destination {
addressaddress;
}
key key; key;
source {
addressaddress;
}
{
routing-instance routing-instance;
}
... | [edit interfaces fti number unit logical-unit-number] | Configure a tunnel on an FTI interface.
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 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.
virtual-loop option introduced in Junos OS Evolved Release 24.4R1. | [] |
tunnel (Interfaces) | tunnel {
destination;
destination-hostname;
do-not-fragment;
encap-type;
flow-label;
no-path-mtu-discovery;
path-mtu-discovery;
routing-instance {
destination routing-instance-name;
}
source;
source-hostname;
source-interface ; | [edit 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. | [] | 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 Services Overview",
"Junos OS VPNs Library for Routing Devices"
] |
tunnel (L2TP) | tunnel {
assignment-id-format (assignment-id | client-server-id);
failover-resync (failover-protocol | silent-failover);
idle-timeout seconds;
maximum-sessions number;
minimum-retransmission-timeout;
name name {
address ip-address {
drain;
routing-instance routing... | [edit services l2tp] | Configure L2TP tunnel characteristics.
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 11.4.
rx-window-size option added in Junos OS Release 13.2. | [
"L2TP LAC Subscriber Configuration",
"L2TP LNS Inline Service Interfaces"
] |
tunnel (Security Policies) | tunnel {
ipsec-group-vpn group-vpn;
ipsec-vpn vpn-name;
pair-policy pair-policy;
} | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit] | Encapsulate outgoing IP packets and decapsulate incoming IP packets. | [] | 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. The ipsec-group-vpn option added in Junos OS Release
10.2. | [
"Security Policies Overview",
"Understanding Security Policy Rules",
"Understanding Security Policy Elements"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.