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 |
|---|---|---|---|---|---|---|---|
then (IDS MS-DPC) | then {
aggregation (IDS) {
destination-prefix prefix-number | destination-prefix-ipv6 prefix-value;
source-prefix prefix-number | source-prefix-ipv6 prefix-value;
}
(force-entry | ignore-entry);
logging {
syslog;
threshold rate;
}
session-limit {
by-destin... | [edit services ids rule rule-name term term-name] | Define the IDS term actions when using the MS-DPC. | [] | 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"
] |
then (IDS MS-MPC) | 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;
route-alert;
security;
... | [edit services ids rule rule-name term term-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"
] |
then (IP Security VPN) | then {
anti-replay-window-size bits;
backup-remote-gateway address;
clear-dont-fragment-bit;
dynamic {
ike-policy policy-name;
ipsec-policy policy-name;
}
initiate-dead-peer-detection;
manual {
direction (inbound | outbound | bidirectional) {
authenticatio... | [edit services ipsec-vpn rule rule-name term term-name] | Define the IPsec term actions. | [] | 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"
] |
then (LRF rule) | then {
report {
collector collector-name;
template template-name;
time-limit time-interval;
volume-limit volume;
}
} | [edit services lrf profile profile-name rule lrf-rule-name] | Configure the actions to take if the LRF rule is matched.
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"
] |
then (PCC Rules) | then {
pcc-action-profile profile-name;
} | [edit unified-edge pcef pcc-rules rule-name],
[edit services pcef pcc-rules rule-name] | Specify the policy and charging control (PCC) action profile for a PCC rule. The PCC action profile
specifies the actions to apply to subscriber traffic that matches any of the from statements in the PCC
rule. A PCC rule configuration must include the then statement and a PCC action profile. The referenced
PCC action p... | [] | For Junos OS Subscriber Aware:
unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration.
For Junos OS Broadband Subscriber Management:
services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support at the [edit services pcef pcc-rules rule-name] hierarchy level introduced for Junos OS Broadband
Subscriber Management in Junos OS Release 17.2 on MX Series.
Support for Next Gen Services for Junos OS Broadband Subscriber Management introduced in Junos OS
Release ... | [
"Configuring Policy and Charging Control Rules",
"Configuring Policy and Charging Control Action Profiles For Junos OS Subscriber Aware",
"Configuring Policy and Charging Control Action Profiles for Subscriber Management"
] |
then (PCP) | then {
pcp-server server-name;
} | [edit services pcp rule rule-name term term-name] | Specify the PCP server to handle the traffic that matches the PCP rule term.
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. | [] | 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"
] |
then (Policer Action) | then {
policer-action;
} | [edit firewall policer policer-name]
[edit logical-systems logical-system-name firewall policer policer-name] | Configure a policer action. | [
{
"name": "policer-action",
"desc": "Actions to take are:"
},
{
"name": "discard",
"desc": "Discard traffic that exceeds the rate limits defined by the policer."
},
{
"name": "forwarding-class class-name",
"desc": "Classify traffic that exceeds the rate limits defined by the policer.... | 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. | [
"Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on EX Series Switches",
"Configuring Policers to Control Traffic Rates (CLI Procedure)",
"Configuring Firewall Filters (CLI Procedure)",
"Understanding the Use of Policers in Firewall Filters",
"Basic Single-Rate Two-Color Policers"
] |
then (Policers) | then {
policer-action;
} | [edit firewall policer policer-name] | Configure a policer action. | [
{
"name": "policer-action",
"desc": "Allowed policer actions are discard, loss-priority high, and loss-priority low. discard"
}
] | 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. | [
"Configuring Two-Color and Three-Color Policers to Control Traffic Rates",
"Configuring Firewall Filters",
"Overview of Policers"
] |
then (Security Application Firewall) | then {
(deny [block-message] | permit | reject [block-message]);
} | [edit security application-firewall rule-set rule-set-name rule rule-name] | Specify the action to be performed when traffic matches the associated match criteria.
Note that an application firewall is applied after a session has already been created by the security
firewall. When traffic is rejected or denied by an application firewall, therefore, logs contain a session
open message, a session ... | [
{
"name": "deny",
"desc": "Block the traffic at the firewall. The device drops the packet. By default, no message is returned"
},
{
"name": "block-message",
"desc": "(Optional) In application firewall rules, provide information to the user regarding"
},
{
"name": "permit",
"desc": "P... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. Statement updated in Junos OS Release 12.1X44-D10
with the reject option. The block-message option added in Junos OS Release 12.1X45-D10. | [
"Example: Configuring an Application Group for Application Firewall"
] |
then (Security Destination NAT) | then {
destination-nat (off | pool pool-name | rule-session-count-alarm (clear-threshold value |
raise-threshold value));
} | [edit security nat destination rule-set rule-set-name rule rule-name] | Specify the action to be performed when traffic matches the destination NAT rule criteria. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. Statement modified in Junos OS Release 12.1X45-D10. | [] |
then (Security IDP Policy) | then {
action (Security Rulebase IPS) {
class-of-service {
dscp-code-point number;
forwarding-class forwarding-class;
}
(close-client | close-client-and-server | close-server |drop-connection | drop-packet |
ignore-connection | mark-diffserv value | no-action | reco... | [edit security idp idp-policy policy-name rulebase-ips rule rule-name] | Specify the action to be performed when traffic matches the defined criteria. | [] | 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. | [] |
then (Security Policies) | then {
count {
alarm {
per-minute-threshold number;
per-second-threshold number;
}
}
deny;
log {
session-close;
session-init;
}
permit {
application-services {
application-firewal... | [edit security policies from-zone zone-name to-zone zone-name policy policy-name] | Specify the policy action to be performed when packets match the defined criteria. | [] | 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. Support for the services-offload option added in Junos OS
Release 11.4. Support for the ssl-termination-profile and web-redirect-to-https options added in Junos OS
Release 12.1X44-D10. Support for the user-firewall option added in Junos OS Release 12.1X45-D10.
Support for t... | [] |
threshold-logging-interval | threshold-logging-interval <minutes> | [edit tenants tenant name security idp sensor-configuration packet-log]
[edit logical system logical system name security idp sensor-configuration packet-log] | The minimum time interval in minutes between log messages for maximum sessions or memory reached. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.3 | [
"Security Policies Overview",
"Understanding Security Policy Rules",
"Understanding Security Policy Elements"
] |
then (Security Source NAT) | then source-nat;
interface {
persistent-nat {
address-mapping;
inactivity-timeout seconds;
max-session-number value;
permit (any-remote-host | target-host | target-host-port);
}
}
off;
pool <pool-name... | [edit security nat source rule-set rule-set-name rule rule-name] | Specify the action to be performed when traffic matches the source NAT rule criteria. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. Statement modified in Junos OS Release 12.1X45-D10. | [] |
then (Security Static NAT) | then {
static-nat {
inet {
routing-instance (default | routing-instance-name);
}
nptv6-prefix {
address-prefix;
routing-instance routing-instance-name;
nptv6-prefix-name {
address-prefix-name;
routing-instance routin... | [edit security nat static rule-set rule-set-name rule rule-name] | Specify the action to be performed when traffic matches the static NAT rule criteria. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.6. Statement modified in Junos OS Release 12.1X45-D10.
Statement modified in Junos OS Release 12.3X48-D25. | [] |
then (Services CoS Next Gen Services) | then {
application-profile profile-name;
dscp (alias | bits);
forwarding-class class-name;
reflexive; | revert; | reverse {
application-profile profile-name;
dscp (alias | bits);
forwarding-class class-name;
}
} | [edit services cos rule rule-name policy policy-name] | Specify the Differentiated Services (DiffServ) code point (DSCP) marking and forwarding-class
assignments for packets that are processed by a service set and that match the conditions of the policy
in a services CoS rule.
The service set that the CoS rule is assigned to must include at least one stateful firewall rule ... | [
{
"name": "application-profile",
"desc": ""
},
{
"name": "profile-name",
"desc": "The application profile that sets the CoS actions for FTP and SIP traffic."
},
{
"name": "dscp (alias | bits)",
"desc": "Either a code point alias or a DSCP bit value to apply to the packet."
},
{
... | 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. | [
"Class of Service for Services PICs (Next Gen Services)"
] |
then (Services CoS) | then {
application-profileprofile-name;
dscp (alias | bits);
forwarding-class class-name;
syslog;
reflexive; | revert; | reverse {
application-profile profile-name;
dscp (alias | bits);
forwarding-class class-name;
syslog;
}
} | [edit services cos rule rule-name term term-name] | Define the CoS term actions.
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 8.1. | [
"Configuring CoS Rules on Services PICs",
"Configuring Actions in CoS Rules"
] |
then (Services NAT) | then {
no-translation;
port-forwarding-mappings map-name;
translated {
address-pooling paired;
clat-prefix clat-prefix;
destination-pool nat-pool-name;
destination-prefix destination-prefix;
dns-alg-pool dns-alg-pool;
dns-alg-prefix dns-alg-prefix;
fil... | [edit services nat rule rule-name term term-name] | Define the NAT term actions.
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"
] |
then (Services Stateful Firewall) | then {
(accept <skip-ids>| discard | reject);
syslog;
} | [edit services stateful-firewall rule rule-name term term-name] | Define the stateful firewall term actions. You can configure the router to accept, discard, or reject the
targeted traffic. The other actions are optional. | [
{
"name": "accept",
"desc": "Accept the traffic and send it on to its destination."
},
{
"name": "accept skip-ids",
"desc": "The packet is accepted and sent on to its destination, but IDS rule processing configured"
},
{
"name": "discard",
"desc": "Do not accept traffic or process it... | 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.
skip-ids option added in Junos OS Release 17.1 on MS-MPC and MS-MIC on MX Series. | [
"Configuring Actions in Stateful Firewall Rules",
"https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/config-",
"guide-policy/config-guide-policy.html",
"Configuring Protection Against Network Attacks on an MS-MPC"
] |
then (Stateful Firewall Rule Next Gen Services) | then {
count;
deny;
permit;
reject;
} | [edit services policies stateful-firewall-rule rule-name policy policy-name] | Specify the actions for a stateful firewall rule policy. The policy actions are applied to flows that meet
the policy’s matching properties. | [
{
"name": "count",
"desc": "Enables a count, in bytes or kilobytes, of all network traffic the policy allows to pass."
},
{
"name": "deny",
"desc": "Drop the packets."
},
{
"name": "permit",
"desc": "Accept the packets and send them to their destination."
},
{
"name": "reject... | 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 Stateful Firewalls for Next Gen Services"
] |
then (TDF Domain Selection) | then {
domain tdf-domain-name;
pcef-profile pcef-profile-name;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name] | Specify the TDF domain or the PCEF profile to be selected when the criteria specified in the domain
selection statement match.
NOTE: This statement is required even if you have not specified any match criteria. The
TDF domain must have been previously configured at the [edit unified-edge gateways tdf
gateway-name domai... | [] | 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"
... |
thermal-health-check | thermal-health-check {
action-onfail (auto-shutdown | none);
power-threshold-percent value;
} | [edit chassis] | Remedy
Severity
PEM %d shutdown -
Insufficient system load
(Junos OS)
PSM %d shutdown -
Insufficient system load
(Junos OS Evolved)
Appears at PSM-level
when the load of any
active PSM is below 20%.
System shuts down these
PSMs, provided N+2
redundancy criteria is
met.
No remedy required for
this alarm. Maintaining a
l... | [
{
"name": "fet-failure-check",
"desc": "Enable FET failure detection, and configure an action to be taken upon FET failure."
},
{
"name": "action-onfail",
"desc": "Choose an action to be performed on detection of a thermal health event. The following"
},
{
"name": "options are available:... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.1R1.
fet-failure-check option introduced in Junos OS Release 21.2R1. | [] |
three-color-policer (Applying) | three-color-policer {
(single-rate | two-rate) policer-name;
} | [edit firewall family family-name filter filter-name term term-name then]
[edit logical-systems logical-system-name firewall family family-name filter filter-name term term-
name then] | Apply a tricolor marking policer. | [
{
"name": "single-rate",
"desc": "Named tricolor policer is a single-rate policer."
},
{
"name": "two-rate",
"desc": "Named tricolor policer is a two-rate policer."
},
{
"name": "policer-name",
"desc": "Name of a tricolor policer."
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4.
single-rate statement added in Junos OS Release 8.2.
Logical systems support introduced in Junos OS Release 9.3. | [
"Configuring and Applying Tricolor Marking Policers",
"Firewall Filter Nonterminating Actions",
"Three-Color Policer Configuration Overview"
] |
three-color-policer (Configuring) (EX) | three-color-policer policer-name {
action {
loss-priority high then discard ;
}
single-rate {
(color-aware | color-blind);
committed-burst-size bytes;
committed-information-rate bps;
excess-burst-size bytes;
}
two-rate {
(color-aware | color-blind);
... | [edit firewall] | Configure a three-color policer. | [
{
"name": "policer-name",
"desc": "Name of the three-color policer. Reference this name when you apply the policer to an"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Tricolor Marking Policers"
] |
three-color-policer (Configuring) | three-color-policer policer-name | uid {
action {
loss-priority high then discard;
}
filter-specific;
logical-interface-policer;
physical-interface-policer;
shared-bandwidth-policer;
single-rate {
(color-aware | color-blind);
committed-burst-size bytes;
commit... | [edit dynamic-profiles profile-name firewall],
[edit firewall],
[edit logical-systems logical-system-name firewall] | Configure a three-color policer in static firewall filters or dynamic firewall filters in a dynamic client
profile or a dynamic service profile. | [
{
"name": "policer-name",
"desc": "Name of the three-color policer. Reference this name when you apply the policer to an"
},
{
"name": "uid",
"desc": "When you configure a policer at the [edit dynamic-profiles] hierarchy level, you must assign a variable"
}
] | 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.
The action and single-rate statements added in Junos OS Release 8.2.
Logical systems support introduced in Junos OS Release 9.3.
Support at the [edit dynamic-profiles ... firewall] hierarchy level introduced in Junos OS Release 11.4. | [
"Configuring and Applying Tricolor Marking Policers",
"Three-Color Policer Configuration Guidelines",
"Basic Single-Rate Three-Color Policers",
"Basic Two-Rate Three-Color Policers",
"Two-Color and Three-Color Logical Interface Policers",
"Two-Color and Three-Color Physical Interface Policers",
"Two-Col... |
three-color-policer | three-color-policer policer-name {
action {
loss-priority high then discard;
}
single-rate {
(color-aware | color-blind);
committed-information-rate bps;
committed-burst-size bytes;
excess-burst-size bytes;
}
two-rate {
(color-aware | color-blind);
... | [edit firewall],
[edit logical-systems logical-system-name firewall] | Configure a three-color policer. | [
{
"name": "policer-name",
"desc": "Name of the three-color policer. Use this name when you apply the policer to an"
}
] | 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. | [
"Configuring Two-Color and Three-Color Policers to Control Traffic Rates",
"Overview of Policers"
] |
threshold (Bridge Domains) | threshold suppress value <reuse value>; | [edit bridge-domains bridge-domain-name multicast-snooping-options forwarding-cache],
[edit logical-systems logical-system-name routing-instances routing-instance-name multicast-
snooping-options forwarding-cache],
[edit logical-systems logical-system-name routing-instances routing-instance-name bridge-domains
bridge-... | Configure the suppression and reuse thresholds for multicast snooping forwarding cache limits. | [
{
"name": "suppress value",
"desc": "Value to begin suppressing new multicast forwarding cache entries. This value is"
},
{
"name": "reuse value",
"desc": "(Optional) Value to begin creating new multicast forwarding cache entries. If configured,"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Example: Configuring Multicast Snooping"
] |
threshold (Detection Time) | threshold milliseconds; | [edit protocols iccp peer liveness-detection detection-time] | Specify the threshold for the adaptation of the detection time for a Bidirectional Forwarding Detection
(BFD) session. When the detection time adapts to a value equal to or greater than the threshold, a single
trap and a single system log message are sent.
NOTE: The threshold time must be greater than or equal to the m... | [
{
"name": "milliseconds",
"desc": "Value for the detection time adaptation threshold."
}
] | 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. | [] |
threshold (detection-time) | threshold milliseconds; | [edit system services dhcp-local-server liveness-detection method bfd detection-time],
[edit system services dhcp-local-server dhcpv6 liveness-detection method bfd detection-time],
[edit forwarding-options dhcp-relay liveness-detection method bfd detection-time],
[edit forwarding-options dhcp-relay dhcpv6 liveness-dete... | Specify the threshold for the adaptation of the detection time. When the BFD session detection time
adapts to a value equal to or greater than the threshold, a single trap and a single system log message
are sent.
NOTE: The threshold time must be greater than or equal to the minimum-interval or the
minimum-receive-inte... | [
{
"name": "milliseconds",
"desc": "Value for the detection time adaptation threshold."
}
] | 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"
] |
threshold (Interfaces) | threshold <value>; | [edit interfaces interface-name radio-router] | This option controls the percentage of bandwidth change required for routing updates. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"PPPoE-Based Radio-to-Router Protocols Overview"
] |
threshold (MSDP Active Source Messages) | threshold number; | [edit logical-systems logical-system-name protocols msdp active-source-limit],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols msdp
active-source-limit],
[edit protocols msdp active-source-limit],
[edit routing-instances routing-instance-name protocols msdp active-source-lim... | Configure the random early detection (RED) threshold for MSDP active source messages. This number
must be less than the configured or default maximum. | [
{
"name": "number",
"desc": "RED threshold for active source messages."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring MSDP with Active Source Limits and Mesh Groups"
] |
threshold (Multicast Forwarding Cache) | threshold {
log-warning value;
suppress value;
reuse value;
mvpn-rpt-suppress value;
mvpn-rpt-reuse value;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast forwarding-cache],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast forwarding-cache family (inet | inet6)],
[edit logical-systems logical-system-name ... | Configure the suppression, reuse, and warning log message thresholds for multicast forwarding cache
limits. You can configure the thresholds globally for the multicast forwarding cache or individually for the
IPv4 and IPv6 multicast forwarding caches. Configuring the threshold statement globally for the multicast
forwa... | [
{
"name": "suppress or mvpn-rpt-suppressvalue",
"desc": "Value at which to begin suppressing new multicast forwarding"
}
] | 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. | [
"Examples: Configuring the Multicast Forwarding Cache"
] |
threshold (PIM BFD Detection Time) | threshold milliseconds; | [edit protocols pim interface interface-name bfd-liveness-detection detection-time],
[edit routing-instances routing-instance-name protocols pim interface interface-name bfd-
liveness-detection detection-time] | Specify the threshold for the adaptation of the BFD session detection time. When the detection time
adapts to a value equal to or greater than the threshold, a single trap and a single system log message
are sent.
NOTE: The threshold value must be equal to or greater than the transmit interval.
The threshold time must ... | [
{
"name": "milliseconds",
"desc": "Value for the detection time adaptation threshold."
}
] | 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"
] |
threshold (PIM BFD Transmit Interval) | threshold milliseconds; | [edit protocols pim interface interface-name bfd-liveness-detection transmit-interval],
[edit routing-instances routing-instance-name protocols pim interface interface-name bfd-
liveness-detection transmit-interval] | Specify the threshold for the adaptation of the BFD session transmit interval. When the transmit
interval adapts to a value greater than the threshold, a single trap and a single system message are sent. | [
{
"name": "milliseconds",
"desc": "Value for the transmit interval adaptation threshold."
}
] | 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. | [
"Configuring BFD for PIM"
] |
threshold (PIM Entries) | threshold value; | [edit logical-systems logical-system-name protocols pim sglimit],
[edit logical-systems logical-system-name protocols pim sglimit family],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
sglimit],
[edit logical-systems logical-system-name routing-instances routing-instan... | Configure a threshold at which a warning message is logged when a certain number of PIM entries have
been received by the device. | [
{
"name": "value",
"desc": "Threshold at which a warning message is logged. This is a percentage of the maximum number of"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [] |
threshold (Routing Instances) | threshold {
group group-address {
source source-address {
rate threshold-rate;
}
}
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
mdt],
[edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel family inet | inet6 mdt],
[edit routing-instances routing-instance-name protocols pim mdt],
[edit routing-instances ro... | Establish a threshold to trigger the automatic creation of a data MDT.
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 before Junos OS Release 7.4. In Junos OS Release 17.3R1, the mdt hierarchy was
moved from provider-tunnel to the provider-tunnel family inet and provider-tunnel family inet6 hierarchies as
part of an upgrade to add IPv6 support for default MDT in Rosen 7, and data MDT for Rosen 6 and
Rosen 7. The p... | [
"Example: Configuring Data MDTs and Provider Tunnels Operating in Source-Specific Multicast Mode",
"Example: Configuring Data MDTs and Provider Tunnels Operating in Any-Source Multicast Mode"
] |
threshold (Services IPsec) | threshold number; | [edit services ipsec-vpn rule rule-name term term-name then dead-peer-detection] | Specify the maximum number of unsuccessful dead peer detection (DPD) requests to be sent before the
peer is considered unavailable. The threshold value is used for IKEv1 security associations (SAs). Starting
in Junos OS Release 17.2R1, the threshold value is also applicable to IKEv2 SAs. In Junos OS Release 17.1
and ea... | [
{
"name": "number",
"desc": "Maximum number of unsuccessful DPD requests to be sent. Range: 1 through 10 Default: 3"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
IKEv2 support introduced in Junos OS Release 17.2. | [
"Configuring IPsec Rules"
] |
threshold (Services Logging and SYN-Cookie Defenses) | threshold rate; | [edit services ids rule rule-name term term-name then logging],
[edit services ids rule rule-name term term-name then syn-cookie] | Specify the threshold for logging or applying SYN-cookie defenses when using the MS-DPC. | [
{
"name": "rate",
"desc": "Logging threshold number of events per second."
},
{
"name": "rate",
"desc": "SYN-cookie defense number of SYN attacks per second."
}
] | 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 Actions in IDS Rules"
] |
threshold (transmit-interval) | threshold milliseconds; | [edit system services dhcp-local-server liveness-detection method bfd transmit-interval],
[edit system services dhcp-local-server dhcpv6 liveness-detection method bfd transmit-interval],
[edit forwarding-options dhcp-relay liveness-detection method bfd transmit-interval],
[edit forwarding-options dhcp-relay dhcpv6 live... | Specify the threshold for detecting the adaptation of the transmit interval. When the BFD session
transmit interval adapts to a value greater than the threshold, a single trap and a single system message
are sent. | [
{
"name": "milliseconds",
"desc": "Threshold value."
}
] | 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"
] |
threshold | threshold threshold-value; | [edit chassis fpc slot-number error fatal],
[edit chassis fpc slot-number error major],
[edit chassis fpc slot-number error minor],
[edit chassis error fatal],
[edit chassis error major],
[edit chassis error minor] | Configure the threshold value at which to take action. If the severity level of the error is fatal, the action
is carried out only once when the total number of errors crosses the threshold value. If the severity level
of the error is major, the action is carried out once after the occurrence crosses the threshold. If ... | [
{
"name": "number",
"desc": "Specify the threshold of error counts at which to take action. Range: 0 through 4,294,967,295"
}
] | interface
To view this statement in the configuration.
interface-control
To add this statement to the configuration. | Statement introduced for PTX Series routers in Junos OS Release 13.3.
Statement introduced for MX240, MX480 MX960, and MX2020 routers in Junos OS Release 14.2. | [
"Fabric Resiliency",
"Managing Errors"
] |
threshold-count | threshold-count count; | [edit protocols l2-learning global-mac-move] | (MX Series routers only) Configure the threshold count value for MAC move reports.
Default | [
{
"name": "count",
"desc": "Number of MAC moves needed in the notification time to generate a MAC move report."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
Support for logical systems added in Junos OS Release 9.6. | [
"Configuring MAC Move Parameters"
] |
threshold-logging-interval | threshold-logging-interval <minutes> | [edit tenants tenant-name security idp sensor-configuration packet-log],
[edit logical-systems logical-system-name security idp sensor-configuration packet-log] | The minimum time interval in minutes between log messages for maximum sessions or memory reached. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.3 | [] |
threshold-rate | threshold-rate kbps; | [edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel selective group address source source-address],
[edit logical-systems logical-system-name routing-instances routing-instance-name provider-
tunnel selective group group-address wildcard-source],
[edit logical-systems logi... | Specify the data threshold required before a new tunnel is created for a dynamic selective point-to-
multipoint LSP. This statement is part of the configuration for point-to-multipoint LSPs for MBGP
MVPNs and PIM-SSM GRE or RSVP-TE selective provider tunnels. | [
{
"name": "number",
"desc": "Specify the data threshold required before a new tunnel is created."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring Point-to-Multipoint LSPs for an MBGP MVPN",
"Configuring PIM-SSM GRE Selective Provider Tunnels"
] |
threshold-time | threshold-time seconds; | [edit protocols l2-learning global-mac-move] | (MX Series routers only) Configure the threshold time value for MAC move reports when the MAC
address moves at least a specified number of times (threshold count) in the configured interval.
Default
1 second | [
{
"name": "seconds",
"desc": "Timer threshold before MAC move reports are generated."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
Support for logical systems added in Junos OS Release 9.6. | [
"Configuring MAC Move Parameters"
] |
thresholds (Junos OS Evolved) | thresholds {
control-failure (on | off);
successive-loss number;
total-loss number;
threshold-type (microseconds | average);
} | [edit services monitoring rpm owner name test name]
[edit services monitoring twamp client control-connection name test-session name] | Specify the thresholds used for real-time performance monitoring (RPM) and Two-Way Active
Measurement Protocol (TWAMP) probes. A system log message is generated when the configured
threshold is exceeded. | [
{
"name": "control-failure (on |",
"desc": ""
},
{
"name": "off)",
"desc": "Specify whether control failure should be reported as a test failure. Default: on"
},
{
"name": "successive-loss",
"desc": ""
},
{
"name": "number",
"desc": "Measures the number of packets lost i... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved 20.1R1 for RPM.
Statement introduced in Junos OS Evolved 20.3R1 for TWAMP. | [
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
thresholds (Junos OS) | thresholds thresholds; | [edit services rpm probe owner test test-name],
[edit services rpm twamp client control-connection control-client-name] | Specify thresholds used for the probes. A system log message is generated when the configured
threshold is exceeded. Likewise, an SNMP trap (if configured) is generated when a threshold is
exceeded.
NOTE: If you configure a value of zero using the thresholds option for a certain probe
parameter, the generation of SNMP ... | [
{
"name": "thresholds",
"desc": "Specify one or more threshold measurements. The following options are supported:"
},
{
"name": "egress-time",
"desc": "Measures maximum source-to-destination time per probe."
},
{
"name": "ingress-time",
"desc": "Measures maximum destination-to-source... | 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] hierarchy level
introduced in Junos OS Release 15.1 for MX Series routers. | [
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches",
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
thresholds | thresholds {
clear clear-value;
interval interval-value;
set set-value;
warning-clear warning-clear-value;
warning-set warning-set-value;
} | [edit interfaces interfaces-name link-degrade-monitor] | Configure the BER threshold values (such as set and clear thresholds) at which different corrective
actions must be triggered on a degraded interface. | [
{
"name": "clear clear-value",
"desc": "The BER threshold value at which the degraded link is considered recovered and the corrective action applied to the interface is reverted. You can configure this value in the 1E–n format, where 1 is the mantissa (remains constant) and n is the exponent. For example, a... | 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. | [
"Link Degrade Monitoring Overview"
] |
time | time {
equals {
value;
}
greater-than value;
less-than value;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from attribute name
format] | Specify the custom AVP attribute’s format as time and the value to match for the incoming RADIUS
request from the IP-based subscriber.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selected.
The rema... | [] | 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"
... |
time-binding | time-binding {
count count-value;
scope (destination | peer | source);
interval time-interval;
} | [edit security idp custom-attack attack-name] | Allow IDP to detect a sequence of the same attacks over a period of time. | [
{
"name": "count count-value",
"desc": "Specify the number of times that IDP detects the attack within the specified scope before triggering an event."
},
{
"name": "interval time-interval",
"desc": "Specify the maximum time interval between any two instances of a time-binding custom attack. Sy... | 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.
Interval option introduced in Junos OS Release 18.4R1. | [
"Time Bindings"
] |
time-format | time-format (year | millisecond | year millisecond); | [edit system syslog]
[edit security log] | Include the year, the millisecond, or both, in the timestamp on every standard-format system log
message. The additional information is included for messages directed to each destination configured by
a file, console, or user statement at the [edit system syslog] hierarchy level, but not to destinations
configured by a... | [
{
"name": "millisecond",
"desc": "Include the millisecond in the timestamp."
},
{
"name": "year",
"desc": "Include the year in the timestamp."
}
] | 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. | [
"Include the Year or Millisecond in Timestamps"
] |
time-interval (Dampen Options) | time-interval microseconds; | [edit event-options event-script dampen dampen-options],
[edit event-options event-script file filename dampen dampen-options],
[edit system scripts commit dampen dampen-options],
[edit system scripts op dampen dampen-options],
[edit system scripts op file filename dampen dampen-options] | Specify the length of time during which to pause the execution of one or more scripts.
Script dampening is initiated when CPU use exceeds the value specified using the cpu-factor statement.
Junos OS then executes the number of lines of script specified using the line-interval statement and
then pauses script execution ... | [
{
"name": "microseconds",
"desc": "Specify the time in microseconds to pause script execution. Range: 1 through 4,294,967,295 microseconds Default: 100 microseconds"
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Dampen Script Execution"
] |
time-limit (LRF Rule) | time-limit time-interval; | [edit services lrf profile profile-name rule lrf-rule-name then report] | Configure the time limit to be used for reporting. The template that the LRF rule is using must have
trigger-type time configured. | [
{
"name": "time-interval",
"desc": "The time limit in seconds. Range: 60 through 1800 Default: 300"
}
] | 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"
] |
time-wait-state | time-wait-state {
(session-ageout | session-timeout seconds);
} | [edit security flow tcp-session] | Defines the length of time (in seconds) that the device keeps the defined TCP session in the session
table. The default is 150 seconds. | [
{
"name": "session-ageout",
"desc": "Set a TCP session to age out, using the service based timeout value."
},
{
"name": "session-timeout seconds",
"desc": "Set the session timeout value allowed before the device ages out a session"
}
] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Understanding Traffic Processing on Security Devices"
] |
time-zone | time-zone (GMT hour-offset | time-zone); | [edit system] | Set the local time zone. To have the time zone change take effect for all processes running on the router
or switch, you must reboot the router or switch.
Default
UTC | [
{
"name": "GMT hour-offset",
"desc": "Set the time zone relative to UTC time."
},
{
"name": "time-zone",
"desc": "Specify the time zone as UTC, which is the default time zone, or as a string such as PDT (Pacific"
}
] | 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.
GMT hour-offset option added in Junos OS Release 7.4. | [
"Modifying the Default Time Zone for a Router or Switch Running Junos OS"
] |
timeout (Access LDAP) | timeout seconds; | [edit access ldap-server server-address]
[edit access profile profile-name ldap-server server-address] | Configure the amount of time that the local device waits to receive a response from an LDAP server. | [
{
"name": "seconds",
"desc": "Amount of time to wait."
}
] | 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. | [
"Example: Configuring RADIUS and LDAP User Authentication"
] |
timeout (DHCP Local Server) | timeout timeout-value; | [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 the initial value in seconds between attempts to reconfigure all DHCP clients or only the
DHCP clients serviced by the specified group of interfaces. | [
{
"name": "timeout-value",
"desc": "Initial retry timeout value."
}
] | 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 Dynamic Reconfiguration Attempts for DHCP Clients"
] |
timeout (Diameter Network Element) | timeout seconds; | [edit access diameter network-element element-name peer peer-name] | Configure the amount of time to wait for a response from this peer before transmitting the request to
another peer. | [
{
"name": "seconds",
"desc": "Amount of time to wait before transmitting the request. Range: 1 through 100 seconds Default: 4 seconds"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [] |
timeout (Flow Maps) | timeout (never non-discard-entry-only | minutes); | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast flow-map flow-map-name],
[edit logical-systems logical-system-name routing-options multicast flow-map flow-map-name],
[edit routing-instances routing-instance-name routing-options multicast flow-map flow-map-nam... | Configure the timeout value for multicast forwarding cache entries associated with the flow map. | [
{
"name": "minutes",
"desc": "Length of time that the forwarding cache entry remains active."
},
{
"name": "never non-discard-entry-only",
"desc": "Specify that the forwarding cache entry always remain active. If you omit"
}
] | 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. | [] |
timeout (Multicast) | timeout minutes <family (inet | inet6)>; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options multicast forwarding-cache],
[edit logical-systems logical-system-name routing-options multicast forwarding-cache],
[edit routing-instances routing-instance-name routing-options multicast forwarding-cache],
[edit routing-... | Configure the timeout value for multicast forwarding cache entries. In general, you should regularly
refresh the forwarding cache so it does not fill up with old entries and thus prevent newer, higher-
priority, entries from being added. | [
{
"name": "minutes",
"desc": "Length of time that the forwarding cache limit remains active."
},
{
"name": "family (inet | inet6)",
"desc": "(Optional) Apply the configured timeout to either IPv4 or IPv6 multicast forwarding"
}
] | 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. | [
"Example: Configuring the Multicast Forwarding Cache"
] |
timeout (RADIUS Server) | timeout seconds; | [edit access radius-server address],
[edit access profile profile-name radius-server address] | Configure the amount of time that the device waits to receive a response from a RADIUS server before
retrying the request. | [
{
"name": "seconds",
"desc": "Number of seconds to wait. Range: 1 through 90 Default: 3"
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement modified in Release 8.5 of Junos OS for SRX Series Firewalls.
Statement introduced in Junos OS Release 17.1 for MX Series Routers. | [
"Configuring RADIUS Servers",
"Understanding Network Elements",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules",
"External Authentication Servers"
] |
timeout (Security Antivirus Fallback Options Sophos Engine) | default (block | log-and-permit | permit); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus sophos-engine profile profile-name fallback-
options] | Scanning a complex file could consume resources and time. If the time it is taking to scan exceeds the
timeout setting in the antivirus profile, the processing is terminated and the content is either passed or
blocked without completing the virus checking. The decision is made based on the timeout fallback
option. | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
},
{
"name": "permit",
"desc": "Permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
timeout (Security Antivirus Fallback Options) | timeout (block | log-and-permit); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name
fallback-options]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name fallback-
options] | 15.1X49-D10
The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-
D10 onwards. | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Change History Table
Feature support is det... | [] |
timeout (Security Antivirus Scan Options) | timeout value; | [edit security utm feature-profile anti-virus juniper-express-engine profile profile-name scan-
options]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name scan-
options]
[edit security utm default-configuration anti-virus scan-options] | 15.1X49-D10
The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-
D10 onwards. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5 . Support for Sophos
engine added in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS ... | [] |
timeout (Security GTP) | timeout value; | [edit security gtp profile profile-name] | Use the timeout option to set the tunnel timeout value in hours. The default is 36 hours. If a device
detects no activity in a tunnel for a specified period, it removes the tunnel from the state table.
From Junos OS Release 20.4R1 onwards, the [edit security gprs gtp profile profile-name] hierarchy level is
replaced b... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. Support. | [
"Understanding GTPv2 Tunnel Cleanup",
"Example: Setting the Timeout Value for GTPv2 Tunnels"
] |
timeout (Security Screen) | timeout seconds; | [edit security screen ids-option screen-name tcp syn-flood] | Specify the maximum length of time before a half-completed connection is dropped from the queue.
You can decrease the timeout value until you see any connections dropped during normal traffic
conditions. | [
{
"name": "seconds",
"desc": "Time interval before a half-completed connection is dropped from the queue."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
timeout (Security Web Filtering Cache) | timeout value; | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering surf-control-integrated cache]
[edit security utm feature-profile web-filtering juniper-enhanced cache] | 15.1X49-D10
The surf-control-integrated feature is not supported from Junos OS Release 15.1X49-D10
onwards. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The surf-control-integrated feature is not supported from Junos OS Release 15.1X49-D10 onwards. For
previous releases, statement introduced in Junos OS Release 9.5.
Statement introduced in Junos OS Release 11.4 .
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Cha... | [] |
timeout (Security Web Filtering Fallback Settings) | timeout (block | log-and-permit); | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering surf-control-integrated profile profile-name
fallback-settings]
[edit security utm feature-profile web-filtering websense-redirect profile profile-name fallback-
settings]
[edit security utm feature-profile web-filtering juniper... | 15.1X49-D10
The surf-control-integrated feature is not supported from Junos OS Release 15.1X49-D10
onwards. | [
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
},
{
"name": "block",
"desc": "Log the error and deny the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The surf-control-integrated feature is not supported from Junos OS Release 15.1X49-D10 onwards. For
previous releases, statement introduced in Junos OS Release 9.5.
Statement introduced in Junos OS Release 11.4 .
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Cha... | [] |
timeout (Security Web Filtering) | timeout value; | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering websense-redirect profile profile-name]
[edit security utm feature-profile web-filtering juniper-enhanced profile profile-name] | Enter a timeout limit for requests. Once this limit is reached, fail mode settings are applied. The default
here is 15 seconds. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
timeout (Services) | timeout seconds; | [edit services unified-access-control ] | Specify the value, in seconds, that the SRX Series Firewall should wait to get a heartbeat response from
an IC Series UAC Appliance (default is 300). If the SRX Series Firewall does not receive it in the specified
time, it takes the action specified by the timeout-action configuration statement. It also tries again to ... | [] | 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. | [] |
timeout (SNMP) | timeout seconds; | [edit snmp v3 target-address target-address-name] | Configure the timeout period (in seconds) for SNMP informs. | [
{
"name": "seconds",
"desc": "Number of seconds to wait for an inform acknowledgment. If no acknowledgment is received"
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [] |
timeout | timeout seconds; | [edit ethernet-switching-options secure-access-port dhcp-snooping-file],
[edit ethernet-switching-options secure-access-port dhcpv6-snooping-file] | Specify a timeout value for remote read and write operations. This value determines the amount of time
that the switch waits for a remote system to respond when the DHCP snooping database is stored on
the remote FTP site.
Default
None | [
{
"name": "seconds",
"desc": "Value in seconds."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
Support at the [edit ethernet-switching-options secure-access-port dhcpv6-snooping-file] hierarchy level
introduced in Junos OS Release 14.1X53-D10 for EX Series switches. | [
"Configuring Persistent Bindings in the DHCP or DHCPv6 (non-ELS)",
"Understanding DHCP Snooping (non-ELS)"
] |
timeout-action | timeout-action (close | no-change | open): | [edit services unified-access-control ] | Specify what the SRX Series Firewall should do when a timeout occurs and the device cannot connect to
an Infranet Enforcer.
Use this statement when you are configuring the SRX Series Firewall to act as a Junos OS Enforcer in a
Unified Access Control (UAC) deployment. When deployed as a Junos OS Enforcer, the SRX Series... | [
{
"name": "close",
"desc": "Close existing sessions and block any further traffic. This is the default option."
},
{
"name": "no-change",
"desc": "Preserve existing sessions and require authentication for new sessions."
},
{
"name": "open",
"desc": "Preserve existing sessions and all... | 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. | [] |
timeout-active-flows (DDoS Flow Detection) | timeout-active-flows; | [edit system ddos-protection protocols protocol-group packet-type] | (MX Series routers with only MPCs, T4000 Core Routers with only FPC5s, or EX9200 switches) Enable
culprit flows for the packet type to time out according to the timeout period. The culprit flow is
suppressed for the duration of the timeout period. When the period expires, the flow times out and is
released from suppre... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support for Enhanced Subscriber Management added in Junos OS Release 17.3R1. | [
"Configuring the Timeout Period for a Culprit Flow",
"Setting Up and Using Flow Detection"
] |
timeout-grace (Access) | timeout grace seconds; | [edit access radius-options] | Configure a grace period during which a RADIUS server that times out after failing to respond to an
authentication request is not considered to be down (if other servers are available) or unreachable (if it is
the only configured server). The server is marked as down or unreachable only when it does not
successfully re... | [
{
"name": "seconds",
"desc": "Duration of the server timeout grace period."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2. | [
"RADIUS Servers and Parameters for Subscriber Access",
"RADIUS Servers and Parameters for Subscriber Access"
] |
timestamp | timestamp {
clock-drift value;
known-peer-window seconds;
new-peer-window seconds;
} | [edit protocols neighbor-discovery secure] | Configure timestamp options, which are used to ensure that solicitation and redirect messages are not
being replayed. | [
{
"name": "clock-drift value",
"desc": "Specify the allowable drift in time between the synchronization of peers. For value,"
},
{
"name": "known-peer-window seconds",
"desc": "Specify the expected interval in seconds between Secure Neighbor"
},
{
"name": "new-peer-window seconds",
"... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Secure IPv6 Neighbor Discovery"
] |
timestamp-format (RFC 2544 Benchmarking) | timestamp-format; | [edit services rpm rfc2544-benchmarkingtests test-name test-name] | Specify the time stamp format. | [] | 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"
] |
timestamp-option (IDS Screen Next Gen Services) | timestamp-option; | [edit services screen ids-option screen-name ip] | Identify and drop IPv4 packets that have the IP option of 4 (Internet timestamp). | [] | 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"
] |
tls (HTTP Servers) | tls {
local-certificate certificate-id;
mutual-authentication {
authentication-type (dont-request-cert | request-and-require-cert-and-verify | request-
and-require-cert-but-dont-verify | request-cert-and-verify | request-cert-but-dont-verify);
certificate-authority certificate-authority-profile-... | [edit system services http servers server] | Configure Transport Layer Security (TLS) settings for the given server.
You must specify the local certificate that the server uses for authentication. You can optionally
configure mutual authentication and define the settings that the network device uses for the client
certificate. | [
{
"name": "authentication-type",
"desc": "(Optional) Specify the requirement for client certificates."
},
{
"name": "dont-request-cert",
"desc": "Do not request a client certificate."
},
{
"name": "request-and-require-cert-and-verify",
"desc": "Require a certificate from the client a... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1 and Junos OS Evolved Release 25.2R1. | [
"Configure gRPC Services"
] |
tls (NETCONF) | tls {
client-identity client-id {
fingerprint fingerprint;
map-type (san-dirname-cn | specified);
username username;
}
default-client-identity {
map-type (san-dirname-cn | specified);
username username;
}
local-certificate local-certificate;
traceopti... | [edit system services netconf] | 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": "local-certificate local-certificate",
"desc": "TLS server’s local certificate ID, which must be loaded into the Junos public key infrastructure (PKI)."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.2R1.
Statement introduced in Junos OS Evolved Release 21.4R1. | [
"NETCONF Sessions over Transport Layer Security (TLS)"
] |
tls | tls | [edit system syslog host host transport] | Configure this Transport Layer Security (TLS) protocol to forward syslog messages securely.
This configuration uses certificates to authenticate peers. Before configuring this statement, make sure
that your device has CA certificate and the PKI. To know more about CA certificate and PKI, refer Self-
Signed Digital Cert... | [] | Statement introduced in Junos OS Release 21.2R1.
Statement introduced in Junos OS Evolved Release 23.4R1. | [] | |
tls-min-version | tls-min-version (v1.1 | v1.2); | [edit access profile profile-name ldap-server ip-address] | Configure Transport Layer Security (TLS) version to limit the lowest supported versions of TLS that are
enabled for SSL connections. | [
{
"name": "v1.1",
"desc": "Accept TLS version 1.1. This enhanced version of TLS provides protection against cipher-block chaining (CBC) attacks."
},
{
"name": "v1.2",
"desc": "Accept TLS version 1.2. This enhanced version of TLS provides improved flexibility for negotiation of cryptographic algo... | 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-D70. | [
"Firewall User Authentication Overview",
"Example: Configuring Integrated User Firewall on SRX Series"
] |
tls-peer-name | tls-peer-namepeer-host-name; | [edit access profile profile-name ldap-server ip-address] | Configure the peer hostname to be authenticated. | [] | 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-D70. | [
"Firewall User Authentication Overview",
"Obtaining Username and Role Information Through Firewall Authentication",
"LDAP Functionality in Integrated User Firewall"
] |
tls-timeout | tls-timeout seconds; | [edit access profile profile-name ldap-server ip-address] | Specify timeout value on the Transport Layer Security (TLS) handshake. The TLS handshake is
responsible for the encryption keys exchange necessary to establish secure sessions between client and
server.
Range: 3 through 90 seconds. | [] | 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-D70. | [
"Firewall User Authentication Overview",
"Obtaining Username and Role Information Through Firewall Authentication",
"LDAP Functionality in Integrated User Firewall"
] |
tls-type | tls-type {
start-tls;
} | [edit access profile profile-name ldap-server ip-address] | Configure Lightweight Directory Access Protocol (LDAP) over Secure Sockets Layer/Transport Layer
Security (SSL/TLS) for secure communication. Transport Layer Security StartTLS extension for LDAP is
used for the firewall user authentication and the integrated user firewall authentication for obtaining
username and role ... | [
{
"name": "start-tls",
"desc": "Configure LDAP over StartTLS. The StartTLS communications occurs over TCP port 389."
}
] | 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-D70. | [
"Firewall User Authentication Overview",
"Obtaining Username and Role Information Through Firewall Authentication",
"LDAP Functionality in Integrated User Firewall"
] |
tlsdetails | tlsdetails {
local-certificate certificate-id;
trusted-ca-group trusted-ca-group-name {
ca-profiles ca-profile-name};
} | [edit system syslog host host] | Configure the TLS authentication parameter. | [
{
"name": "local-certificate certificate-id",
"desc": "Use this option to specify the local certificate ID for authentication. The local certificate contains the public key and identify information for the device."
},
{
"name": "certificate-authority",
"desc": ""
},
{
"name": "certificat... | Statement introduced in Junos OS Release 21.2R1 for EX and MX Series routers.
Statement introduced in Junos OS Release 21.3R1 for SRX Series and vSRX Virtual Firewall devices. | [
"Configuring a Trusted CA Profile Group"
] | |
tlv-filter | tlv-filter tlv-name; | [edit protocols lldp],
[edit protocols lldp-med],
[edit protocols lldp interface interface-name],
[edit protocols lldp-med interface interface-name] | Select the type, length, and value (TLV) messages that should not be advertised by the Link Layer
Discovery Protocol (LLDP) or LLDP Media Endpoint Discovery (LLDP-MED) protocol. LLDP-capable
devices transmit information in type, length, and value (TLV) messages to neighbor devices. Device
information can include inform... | [
{
"name": "tlv-name",
"desc": "Specify the non-mandatory TLV message that you want to disable. Values: You can disable the following TLV messages for LLDP:"
},
{
"name": "cloud-reach-event-tlv",
"desc": "Use to have cloud-ready EX4400 Series switches stop sending"
},
{
"name": "jnpr-cha... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3. | [
"Configuring LLDP (CLI Procedure)",
"Understanding LLDP and LLDP-MED on EX Series Switches"
] |
tlv-select | tlv-select tlv-name; | [edit protocols lldp],
[edit protocols lldp-med],
[edit protocols lldp interface interface-name],
[edit protocols lldp-med interface interface-name] | Select the type, length, and value (TLV) messages that should be advertised by Link Layer Discovery
Protocol (LLDP) or LLDP Media Endpoint Discovery (LLDP-MED) protocol. LLDP-capable devices
transmit information in type, length, and value (TLV) messages to neighbor devices. Device information
can include information su... | [
{
"name": "tlv-name",
"desc": "Specify the non-mandatory TLV message that you want to advertise. Values: You can advertise the following TLV messages for LLDP:"
},
{
"name": "jnpr-chassis-serial",
"desc": "The chassis serial number."
},
{
"name": "jnpr-vcp",
"desc": "Juniper virtual... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3. | [
"Configuring LLDP (CLI Procedure)",
"Understanding LLDP and LLDP-MED on EX Series Switches"
] |
tm | tm (ignore | normal | require); | [edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options] | For EIA-530 interfaces only, configure the from-DCE signal, test-mode (TM). | [
{
"name": "ignore",
"desc": "The from-DCE signal is ignored."
},
{
"name": "normal",
"desc": "Normal TM signal handling as defined by the TIA/EIA Standard 530."
},
{
"name": "require",
"desc": "The from-DCE signal must be asserted."
}
] | 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 Signal Handling"
] |
tm-polarity | tm-polarity (negative | positive); | [edit interfaces interface-name serial-options] | Configure TM signal polarity. | [
{
"name": "negative",
"desc": "Negative signal polarity."
},
{
"name": "positive",
"desc": "Positive signal polarity."
}
] | 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 Serial Signal Polarities"
] |
to (Security Source NAT) | to {
interface [interface-name];
routing-instance [routing-instance-name];
zone [zone-name];
} | [edit security nat source rule-set rule-set-name] | Specify the destination of the packet among the routing instance, interface, or zone. | [
{
"name": "interface [interface-name]",
"desc": "Name of the interface."
},
{
"name": "routing-instance [routing-instance-name]",
"desc": "Name of the routing instance."
},
{
"name": "zone [zone-name]",
"desc": "Name of the zone."
}
] | 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. | [] |
to | to address; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
bypass],
[edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name
ingress],
[edit protocols mpls labe... | Specify the egress router of a dynamic LSP. | [
{
"name": "address",
"desc": "IPv4 or IPv6 address of the egress router."
}
] | 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 IPv6 addresses in static LSP configurations are provided in Junos OS Release 17.2R1. | [
"Configuring the Egress Router Address for LSPs"
] |
to-zone (Security IDP Policy) | to-zone (zone-name | any); | [edit security idp idp-policy policy-name rulebase-exempt rule rule-name match]
[edit security idp idp-policy policy-name rulebase-ips rule rule-name match] | Specify a destination zone to be associated with the security policy. The default value is any. | [
{
"name": "zone-name",
"desc": "Name of the destination zone object."
}
] | 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. | [] |
to-zone (Security Policies Global) | to-zone {
[zone-name];
any;
} | [edit security policies global policy policy-name match] | Identify a single destination zone or multiple destination zones to be used as a match criteria for a
policy. You must configure specific zones or default to any zone, but you cannot have both in a global
policy. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X47-D10. | [
"Global Policy Overview",
"Example: Configuring a Global Policy with No Zone Restrictions",
"Example: Configuring a Global Policy with Multiple Zones"
] |
to-zone (Security Policies) | to-zone zone-name {
policy policy-name {
description description;
match {
application {
[application];
any;
}
destination-address {
[address];
any;
any-ipv4;
any-ipv6;
... | [edit security policies from-zone zone-name] | Specify a destination zone to be associated with the security policy. | [
{
"name": "zone-name",
"desc": "Name of the destination zone object."
},
{
"name": "junos-host",
"desc": "Default security zone for self-traffic of the device."
}
] | 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. Support for the services-offload and junos-host options
added in Junos OS Release 11.4. Support for the source-identity option added in Junos OS Release 12.1.
Support for the ssl-termination-profile and web-redirect-to-https options added in Junos OS Release
12.1X44-D10. | [
"Security Policies Overview",
"Understanding Security Policy Rules",
"Understanding Security Policy Elements"
] |
token (DHCP Local Server) | token token-value; | [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-... | Configure a plain-text token for all DHCP clients or only the DHCP clients serviced by the specified
group of interfaces. The token enables rudimentary entity authentication to protect against
inadvertently instantiated DHCP servers. A null token (empty string) indicates that the configuration
token functionality is no... | [
{
"name": "token-value",
"desc": "Plain-text alphanumeric string."
}
] | 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 a Token for DHCP Local Server Authentication"
] |
too-many-requests (Security Antivirus Fallback Options Sophos Engine) | default (block | log-and-permit | permit); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus sophos-engine profile profile-name fallback-
options] | If the total number of messages received concurrently exceeds the device limits, the content is either
passed or blocked depending on the too-many-request fallback option. (The allowed request limit is not
configurable.) | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
},
{
"name": "permit",
"desc": "Permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
too-many-requests (Security Antivirus Fallback Options) | too-many-requests (block | log-and-permit); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name
fallback-options]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name fallback-
options] | 15.1X49-D10
The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-
D10 onwards. | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky Antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Change History Table
Feature support is det... | [] |
too-many-requests (Security Web Filtering Fallback Settings) | too-many-requests (block | log-and-permit); | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering surf-control-integrated profile profile-name
fallback-settings]
[edit security utm feature-profile web-filtering websense-redirect profile profile-name fallback-
settings]
[edit security utm feature-profile web-filtering junipe... | 15.1X49-D10
The surf-control-integrated feature is not supported from Junos OS Release 15.1X49-D10
onwards. | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The surf-control-integrated feature is not supported from Junos OS Release 15.1X49-D10 onwards. For
previous releases, statement introduced in Junos OS Release 9.5.
Statement introduced in Junos OS Release 11.4 .
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Cha... | [] |
top | top <configuration-command> | Return to the top level of configuration command mode, which is indicated by the [edit] banner. | [
{
"name": "configuration-command",
"desc": "(Optional) Issue configuration mode commands from the top of the hierarchy."
}
] | configure—To enter configuration mode. | Command introduced before Junos OS Release 7.4. | [
"Displaying the Current Configuration"
] | |
topologies (Multitopology Routing) | topologies {
family (inet | inet6) {
topology topology-name;
}
} | [edit logical-systems logical-system-name routing-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options] | Configure a topology for multitopology routing. Each topology creates a new routing table that is
populated with direct routes from the topology. | [
{
"name": "family",
"desc": "Configure the type of family address type."
},
{
"name": "inet",
"desc": "IPv4"
},
{
"name": "inet6",
"desc": "IPv6"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Example: Configuring Multitopology Routing to Provide Redundancy for Multicast Traffic over",
"Separate Network Paths",
"Example: Configuring Multitopology Routing for Class-Based Forwarding of Voice, Video, and Data",
"Traffic",
"Understanding Multitopology Routing for Class-Based Forwarding of Voice, Vid... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.