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 |
|---|---|---|---|---|---|---|---|
system (Export Profiles) | system {
information;
status {
queue;
traffic;
}
} | [edit services analytics export-profiles] | Configure a system-wide export profile for streaming network analytics data to remote servers. Each
profile is a template that defines the type of data being streamed for that system.
NOTE: The system statement is not available in Junos OS Releases prior to 13.2X51-D15. | [
{
"name": "information",
"desc": "Information about the system, including boot time, model, serial number, maximum number of ports, collector information, and interface list."
},
{
"name": "status",
"desc": "System status information to be streamed. Values:"
},
{
"name": "queue",
"d... | 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"
] |
system (Memory) | system {
frequency (minutes | hours | days) value;
minor-event {
threshold swap-usage value ;
action snmp-trap;
}
major-event {
threshold swap-usage value ;
action [snmp-trap | live-vmcore];
}
critical-event {
threshold swap-usage value ;
action ... | [edit system monitor memory] | Configure system level memory monitoring. | [
{
"name": "frequency",
"desc": "Specify the frequency of system level memory monitoring. You can specify the frequency in days, hours or minutes. Possible values: 1 through 65535."
},
{
"name": "minor-event",
"desc": "Indicates a non-critical event that, if left unchecked, may cause an interrupt... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.1. | [
"System Log Overview",
"System Log Explorer"
] |
system login (Junos Node Slicing) | system login {
user username ;
class class-name;
idle-timeout idle-timeout;
} | [edit ] | Create a non-root user in JDM for Junos node slicing. The non-root user accounts function only inside
JDM, not on the host server. | [
{
"name": "user username",
"desc": "Username of the account."
},
{
"name": "class class-name",
"desc": "Predefined login classes that JDM supports for non-root users."
},
{
"name": "super-user",
"desc": ""
},
{
"name": "operator",
"desc": ""
},
{
"name": "read-onl... | Statement introduced in Junos OS Release 18.3 R1. | [
"Setting Up Junos Node Slicing",
"Setting Up Junos Node Slicing"
] | |
system-defaults | system-defaults {
classifiers exp {
classifier-name;
}
traffic-control-profiles {
interface-set-input profile-name;
interface-set-output profile-name;
}
} | [edit class-of-service],
[edit dynamic-profiles name class-of-service] | Define system defaults for CoS parameters. You can define a global system default EXP classifier, a
global default input traffic control profile (TCP), and/or a global default output TCP.
If you configure a global system default EXP classifier, then all interfaces use that EXP classifier to
classify MPLS traffic.
On de... | [
{
"name": "classifier-name",
"desc": "Name of the behavior aggregate (BA) exp classifier or default for the default exp classifier."
},
{
"name": "profile-name",
"desc": "For interface-set-input, the default input TCP for dynamic interface-sets. For interface-set-output, the default output TCP f... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2.
traffic-control-profiles option added in Junos OS Release 19.3R1. | [] |
system-id (Interfaces) | system-id system-id; | [edit interfaces aeX aggregated-ether-options lacp] | Define the LACP system identifier at the aggregated Ethernet interface level.
The user-defined system identifier in LACP enables two ports from two separate routers (M Series or
MX Series routers) to act as though they were part of the same aggregate group.
The system identifier is a 48-bit (6-byte) globally unique fie... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2R1 | [
"Configuring LACP for Aggregated Ethernet Interfaces"
] |
system-id (Junos Fusion Satellite Device Cluster) | system-id mac-address; | [edit chassis satellite-management cluster cluster-name fpc slot-id ] | Assign the specified FPC identifier to the satellite device in the satellite device cluster based on the
satellite device’s MAC address.
For instance, if you wanted the satellite device using MAC address 01:02:03:AA:BB:CC in the satellite
device cluster named building-1 to be assigned FPC identifier 101, enter the set ... | [
{
"name": "mac-address",
"desc": "Specifies the MAC address of the satellite device."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1. | [
"Configuring or Expanding a Junos Fusion Enterprise"
] |
system-id (Junos Fusion) | system-id mac-address; | [edit chassis satellite-management fpc slot-id] | Assign the specified FPC identifier to the satellite device based on the satellite device’s MAC address.
For instance, if you wanted the satellite device using MAC address 01:02:03:AA:BB:CC to be assigned
FPC identifier 101, enter the set chassis satellite-management fpc 101 system-id 01:02:03:AA:BB:CC
statement.
A Jun... | [
{
"name": "mac-address",
"desc": "Specifies the MAC address of the satellite device."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring Junos Fusion Provider Edge",
"Configuring or Expanding a Junos Fusion Enterprise"
] |
system-id | system-id system-id-value {
ip-address(es);
} | [edit logical-systems logical-system-name protocols (mstp | rstp)],
[edit logical-systems logical-system-name protocols vstp vlan vlan-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(mstp | rstp)],
[edit logical-systems logical-system-name routing-instances routing-ins... | Determine the system identifier value for bridges in a VPLS multihomed Layer 2 ring with MPLS
infrastructure. | [
{
"name": "system-id-value",
"desc": "System identifier in the format nnnnnn:nnnnnn, where n = any digit from 0 through 9."
},
{
"name": "ip-address(es)",
"desc": "Valid IP host addresses in the format ip-address/32."
}
] | 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. | [
"Understanding VPLS Multihoming"
] |
system-priority (chassis) | system-priority priority; | [edit chassis aggregated-devices ethernet lacp] | Define LACP system priority for aggregated Ethernet interfaces at the global (chassis) level.
The device with the lower system priority value determines which links between LACP partner devices
are active and which are in standby for each LACP group. The device on the controlling end of the link
uses port priorities to... | [
{
"name": "priority",
"desc": "Priority for the aggregated Ethernet system. A smaller value indicates a higher priority."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [
"Configuring Junos OS for Supporting Aggregated Devices",
"Configuring LACP Link Protection of Aggregated Ethernet Interfaces for Switches"
] |
system-priority (interfaces) | system-priority priority; | [edit interfaces aeX aggregated-ether-options lacp] | Define LACP system priority at the aggregated Ethernet interface level. This system priority value takes
precedence over a system priority value configured at the global [edit chassis] hierarchy level.
The device with the lower system priority value determines which links between LACP partner devices
are active and whi... | [
{
"name": "priority",
"desc": "Priority for the aggregated Ethernet system. A smaller value indicates a higher priority."
}
] | 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. | [] |
system-services (Security Zones Host Inbound Traffic) | system-services {
(service-name | all <service-name except>);
} | [edit security zones security-zone zone-name host-inbound-traffic] | Specify the types of incoming system service traffic that can reach the device for all interfaces in a
security zone. By default, a security zone has all system services disabled. You can allow the inbound
system services traffic in one of the following ways:
•
Allow system services individually.
•
Allow all system ser... | [
{
"name": "service-name",
"desc": ""
},
{
"name": "all",
"desc": "Traffic from the defined system services available on the Routing Engine (RE). Use"
},
{
"name": "any-service",
"desc": "All system services on an entire port range including the system services"
},
{
"name": "... | 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. | [
"Security Zones Overview",
"Supported System Services for Host Inbound Traffic"
] |
system-services (Security Zones Interfaces) | system-services service-name {
except;
} | [edit security zones security-zone zone-name interfaces interface-name host-inbound-traffic] | Specify the types of traffic that can reach the device on a particular interface. | [
{
"name": "service-name",
"desc": "Service for which traffic is allowed. The following services are supported:"
},
{
"name": "all",
"desc": "Enable all possible system services available on the Routing Engine (RE)."
},
{
"name": "any-service",
"desc": "Enable services on entire port ... | 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. | [
"Security Zones Overview",
"Supported System Services for Host Inbound Traffic",
"T"
] |
t1-interval | t1-interval value-in-milliseconds; | [edit logical-systems name security alg sip],
[edit logical-systems name tenants name security alg sip],
[edit security alg sip],
[edit services alg sip],
[edit tenants name security alg sip] | Configure t1-interval parameter to specify the maximum round-trip time (RTT) (in milliseconds) allowed
for Session Initiation Protocol (SIP) transactions. | [
{
"name": "value-in-milliseconds",
"desc": "Maximum round-trip time (RTT) allowed measured in milliseconds."
}
] | 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. | [] |
t1-options (BITS Interfaces Signal Type) | t1-options {
framing (esf | sf);
} | [edit chassis synchronization interfaces bits] | Specify options for the T1 signal type for the building-integrated timing supply (BITS) interface. Valid
only if t1 is the signal-type configured at the [edit chassis synchronization source interfaces interface-name
bits signal-type] hierarchy. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"External Clock Synchronization Overview for ACX Series Routers",
"Configuring External Clock Synchronization for ACX Series Routers",
"Synchronous Ethernet Overview"
] |
t1-options | t1-options {
framing (esf | sf);
line-encoding (ami | b8zs);
} | [edit chassis synchronization interfaces external],
[edit chassis synchronization interfaces (external-0/0 | external-1/0) e1-options] | Configure the T1 interface options. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [] |
t310 | t310-value seconds; | [edit interfaces br-pim/0/port isdn-options] | For ISDN interfaces, configure the Q.931-specific timer for T310, in seconds. The Q.931 protocol is
involved in the setup and termination of connections. | [
{
"name": "seconds",
"desc": "Timer value, in seconds."
}
] | 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. | [] |
t391 | t391 number; | [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options] | For link services interfaces only, set the Frame Relay link integrity polling interval. | [
{
"name": "number",
"desc": "Link integrity polling interval."
}
] | 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 Keepalives on Link Services Physical Interfaces"
] |
t392 | t392 number; | [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options] | For link services interfaces only, set the Frame Relay polling verification interval. | [
{
"name": "number",
"desc": "Polling verification interval."
}
] | 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 Keepalives on Link Services Physical Interfaces"
] |
t4-interval | t4-interval value-in-seconds; | [edit logical-systems name security alg sip],
[edit logical-systems name tenants name security alg sip],
[edit security alg sip],
[edit services alg sip],
[edit tenants name security alg sip] | Configure t4-interval parameter to specify the maximum length of time (in seconds) that the network
can take to clear messages between client and server Session Initiation Protocol (SIP) transactions. | [
{
"name": "value-in-seconds",
"desc": "Maximum number of seconds that the network can take to clear messages between"
}
] | 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. | [] |
table | table table-name; | [edit dynamic policy-options condition],
[edit logical-systems logical-system-name policy-options condition if-route-exists ],
[edit logical-systems logical-system-name policy-options condition if-route-exists address-family
ccc],
[edit logical-systems logical-system-name policy-options condition if-route-exists addre... | Specify a routing table in which the route must exist for the condition to be met and the route to be
considered a match. | [
{
"name": "table table-name",
"desc": "Routing table name, such as inet.0."
}
] | 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.
Support for configuration in the dynamic database introduced in Junos OS Release 9.5.
Support for configuration in the dynamic database introduced in Junos OS Release 9.5 for EX Series
switches.
Support for the address families introduced in Junos OS Release 13.2. | [
"Conditional Advertisement and Import Policy (Routing Table) with certain match conditions",
"Example: Configuring Pseudowire Redundancy in a Mobile Backhaul Scenario"
] |
tacplus | tacplus {
server {
server-address {
port port-number;
routing-instance routing-instance;
secret password;
single-connection;
source-address address;
timeout seconds;
}
}
} | [edit system accounting destination] | Configure the Terminal Access Controller Access Control System Plus (TACACS+) servers. | [
{
"name": "server-address",
"desc": "Address of the TACACS++ authentication server."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
routing-instance option introduced in Junos OS Release 17.4R1. | [
"Configuring TACACS+ System Accounting"
] |
tacplus-options | tacplus-options {
(exclude-cmd-attribute | no-cmd-attribute-value);
authorization-time-interval minutes;
enhanced-accounting;
(strict-authorization | no-strict-authorization);
service-name service-name;
timestamp-and-timezone;
} | [edit system] | Configure TACACS+ options for authentication and accounting. | [
{
"name": "authorization-time-interval",
"desc": ""
},
{
"name": "minutes",
"desc": "Configure the time interval at which the authorization profile that is configured on the TACACS+ server is fetched by the Junos OS device during a TACACS+ authentication session. The TACACS+ server sends the aut... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
no-cmd-attribute-value and exclude-cmd-attribute options introduced in Junos OS Release 9.3.
timestamp-and-timezone option introduced in Junos OS Release 12.2.
strict-authorization and no-strict-authorization options introduced in Junos OS Release 13.3 for EX Series,
M ... | [
"Configuring Periodic Refresh of the TACACS+ Authorization Profile",
"Configuring TACACS+ Authentication",
"Configuring TACACS+ System Accounting",
"Determine the Authentication Order for LDAPS, RADIUS, TACACS+, and Password Authentication"
] |
tacplus-server | tacplus-server server-address {
port port-number;
routing-instance routing-instance;
secret password;
single-connection;
source-address source-address;
timeout seconds;
} | [edit system] | Configure the IPv4 or IPv6 TACACS+ server. | [
{
"name": "server-address",
"desc": "Address of the IPv4 or IPv6 TACACS+ authentication server. NOTE: Wildcard characters cannot be used in the TACACS+ server address or source address. This is because the TACACS+ server and source can accept both IPv4 and IPv6 addresses and, if you use wildcard characters ... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
routing-instance option introduced in Junos OS Release 17.4R1. | [
"Configuring TACACS+ Authentication"
] |
tag (Access) | tag route-tag; | [edit routing-options access route ip-prefix</prefix-length>],
[edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
access route prefix],
[edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
rib routing-table-name access route prefix],... | Dynamically configure the tag for an access route. | [
{
"name": "route-tag",
"desc": "Either the specific tag you want to assign to the access route or either of the following tag"
},
{
"name": "variables:",
"desc": ""
},
{
"name": "$junos-framed-route-tag",
"desc": "Tag assigned to an IPv4 access route; the variable is dynamically repl... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2.
Support at the [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
access route prefix] and [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-
options rib routing-table-name access route prefix] ... | [
"Routes for DHCP and PPP Subscriber Access Networks"
] |
tag (Configuring Notification Targets) | tag tag-name; | [edit snmp v3 notify name] | Configure a set of target addresses to receive SNMP traps or informs (for IPv4 packets only). | [
{
"name": "tag-name",
"desc": "Define the target addresses to which an SNMP notification is sent. Target addresses"
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [] |
tag (HTTP Header Enrichment) | tag tag-name {
encrypt {
hash algorithm;
prefix hash-prefix;
}
ipv4-mask ipv4-mask;
ipv6-mask ipv6-mask;
ipv4-or-value ipv4-or-value;
ipv6-or-value ipv6-or-value;
tag-attribute tag-attr-name;
tag-header header;
tag-separator separator;
} | [edit services hcm tag-rule rule-name term term-number then] | Configure the tags to be applied to the HTTP headers. If you configure a tag, you must include the tag-
header statement. | [
{
"name": "tag-name",
"desc": "Name of the tag."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview",
"Configuring Tag Rules",
"Configuring HCM Profiles and Assigning Tag Rules",
"Junos Web Aware HTTP Header Enrichment Overview"
] |
tag (Routing Options) | tag metric type number; | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options (aggregate | generate | static) (defaults | route)],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name (aggregate | generate | static) (defaults | ro... | Associate a tag with a static, aggregate, or generated route.
Default
No tag strings are associated with routes. | [
{
"name": "metric",
"desc": "Tag metric."
},
{
"name": "type number",
"desc": "Tag type."
}
] | 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: Summarizing Static Routes Through Route Aggregation"
] |
tag (SNMP) | tag tag-name; | [edit snmp v3 notify name],
[edit snmp v3 snmp-community community-index] | Configure a set of targets to receive traps or informs (for IPv4 packets only). | [
{
"name": "tag-name",
"desc": "Identifies the address of managers that are allowed to use a community string."
}
] | 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. | [] |
tag2 (Dynamic Access Routes) | tag2 route-tag2; | [edit dynamic-profiles profile-name routing-instances $junos-routing-instance routing-options
access route prefix],
[edit dynamic-profiles profile-name routing-options access route prefix] | [
{
"name": "route-tag2",
"desc": "One of the following values the specific tag2 value you want to assign to the access route or"
},
{
"name": "the following predefined variable:",
"desc": "A specific tag 2 value for the specified access route prefix."
},
{
"name": "$junos-framed-route-tag... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"PPP Subscriber Access Networks Overview"
] | |
tag-attribute (HTTP Header Enrichment Tag Rule) | tag-attribute [tag-attr-name]; | [edit services hcm tag-rule rule-name term term-number then tag tag-name] | Specify one or more tag attributes (for the tag header and separator) to insert into the HTTP header.
NOTE: The tag attribute specified here must already be defined at the [edit services hcm]
hierarchy level. | [
{
"name": "tag-attr-name",
"desc": "Tag attribute. To specify multiple attributes at one time, include the attributes in square"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview",
"Configuring Tag Rules"
] |
tag-attribute (HTTP Header Enrichment) | tag-attribute [tag-attr-name]; | [edit services hcm] | Specify one or more tag attributes that can be used in tag rules for HTTP header enrichment.
These attributes are stored in the subscriber database for subscribers. After these attributes are
configured, they can be used in the tag rules. HTTP tag rules can be configured to choose one or more
of these attributes to ins... | [
{
"name": "tag-attr-name",
"desc": "Tag attribute. To specify multiple attributes at one time, include the attributes in square"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring HTTP Header Enrichment Overview",
"Configuring Tag Rules",
"Junos Web Aware HTTP Header Enrichment Overview"
] |
tag-group | tag-group name {
application-tags [ application-tags... ]
} | [edit services application-identification application-group application-group-name | Specify a unique tag group identifier to create your own application group based on the application
attributes. Application group allows you to associate a related applications under a single name for
simplified, consistent reuse when using any application services.
For example: If you want to group application traffic... | [
{
"name": "name",
"desc": ""
},
{
"name": "A unique tag group identifier",
"desc": ""
},
{
"name": "application-tags",
"desc": "Application tag to configure the application group. (Supported tags available in the latest version of application signature) - basic, networking, email, we... | system | Statement introduced in Junos OS Release 21.1R1. | [
"Configure Packet Capture For Unknown Application Traffic"
] |
tag-header (HTTP Header Enrichment) | tag-header header; | [edit services hcm tag-rule rule-name term term-number then tag tag-name] | Specify the tag header for the tag to be inserted into the HTTP header. This is a required configuration.
You can configure a total of 16 unique tag headers for all the tag rules you configure. | [
{
"name": "header",
"desc": "Tag header."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview",
"Configuring Tag Rules",
"Configuring HCM Profiles and Assigning Tag Rules",
"Junos Web Aware HTTP Header Enrichment Overview"
] |
tag-list | tag-list tag-list; | [edit snmp v3 target-address target-address-name] | Configure an SNMP tag list used to select target addresses. | [
{
"name": "tag-list",
"desc": "Define sets of target addresses (tags). To specify more than one tag, specify the tag names as a"
}
] | 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. | [] |
tag-operation (HTTP Header Enrichment) | tag-operation (add | delete | modify); | [edit services hcm tag-rule rule-name term term-name then tag tag-name] | Specify the operation to be performed on the specified tag of the tag rule set.
NOTE: The tag rule must already be defined at the [edit services hcm] hierarchy level. | [
{
"name": "add",
"desc": "Add the specified tag with previously existing tag in the tag rule set."
},
{
"name": "delete",
"desc": "Delete the specified tag from the tag rule set."
},
{
"name": "modify",
"desc": "Modify the existing tag in the tag rule set."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview"
] |
tag-protocol-id (Dynamic VLANs) | tag-protocol-id tpids; | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number input-vlan-
map],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number output-vlan-
map] | For dynamic VLAN interfaces, configure the outer TPID value. All TPIDs you include in input and output
VLAN maps must be among those you specify at the [edit interfaces interface-name gigether-options
ethernet-switch-profile tag-protocol-id [ tpids ]] hierarchy level.
Default
If the tag-protocol-id statement is not con... | [
{
"name": "tpids",
"desc": "TPIDs to be accepted on the VLAN. Specify TPIDs in hexadecimal format."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Configuring Inner and Outer TPIDs and VLAN IDs"
] |
tag-protocol-id (TPID to Rewrite) | tag-protocol-id tpid; | [edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interfa... | For Gigabit Ethernet IQ and 10-Gigabit Ethernet IQ2 and IQ2-E interfaces only, configure the outer
TPID value. All TPIDs you include in input and output VLAN maps must be among those you specify at
the [edit interfaces interface-name gigether-options ethernet-switch-profile tag-protocol-id [ tpids ]]
hierarchy level.
F... | [] | 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 Inner and Outer TPIDs and VLAN IDs"
] |
tag-protocol-id TPID (TPIDs Expected to Be Sent or Received) | tag-protocol-id [tpids]; | [edit interfaces interface-name gigether-options ethernet-switch-profile],
[edit interfaces interface-name aggregated-ether-options ethernet-switch-profile],
[edit interfaces interface-name aggregated-ether-options ethernet-switch-profile],
[edit interfaces interface-name ether-options ethernet-switch-profile] | For Gigabit Ethernet IQ and 10-Gigabit Ethernet IQ2 and IQ2-E interfaces, aggregated Ethernet with
Gigabit Ethernet IQ interfaces, and Gigabit Ethernet PICs with SFPs (except the 10-port Gigabit Ethernet
PIC, and the built-in Gigabit Ethernet port on the M7i router), define the TPIDs expected to be sent or
received on ... | [
{
"name": "tpids",
"desc": "TPIDs to be accepted on the VLAN. Specify TPIDs in hexadecimal."
}
] | 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. | [
"Configuring Frames with Particular TPIDs to Be Processed as Tagged Frames",
"Configuring Q-in-Q Tunneling on EX Series Switches with ELS Support"
] |
tag-rule (HTTP Header Enrichment) | tag-rule rule-name {
term term-number {
from {
destination-address {
(any-ipv4 | any-ipv4 except);
(any-ipv6 | any-ipv6 except);
(any-unicast | any-unicast except);
(prefix | prefix except);
}
destination-add... | [edit services hcm] | Configure the tag rules that enrich HTTP headers with the appropriate tags.
You must configure at least one term for a tag rule, but you can configure multiple terms. Terms are
evaluated in the order they are configured. If a data packet matches all the criteria in the from statement
in any of the terms, then the actio... | [
{
"name": "rule-name",
"desc": "Name of the tag rule."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring HTTP Header Enrichment Overview",
"Configuring Tag Rules",
"Configuring HCM Profiles and Assigning Tag Rules",
"Junos Web Aware HTTP Header Enrichment Overview"
] |
tag-rule (Profiles for HTTP Header Enrichment) | tag-rule rule-name; | [edit services hcm profile profile-name] | Specify the tag rule to be associated with the HCM profile.
NOTE: The tag rule specified here must already be defined at the [edit services hcm]
hierarchy level. | [
{
"name": "rule-name",
"desc": "Name of the tag rule. Range: 1 through 63 alphanumeric characters"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview",
"Configuring HCM Profiles and Assigning Tag Rules"
] |
tag-rule-set (HTTP Header Enrichment) | tag-rule-set rule-set-name {
[rule rule-name];
} | [edit services hcm] | Configure the tag rule set for HTTP header enrichment so that you can group multiple configured tag
rules into one tag rule set. | [
{
"name": "rule-set-name",
"desc": "Name of the tag rule set. The remaining statement is explained separately. See CLI Explorer."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview"
] |
tag-rule-sets (Service Set) | tag-rule-sets rule-set-name; | [edit services service-set service-set-name] | Specify the HTTP header enrichment tag rule set included in the service set. You can configure only one
tag rule set. If you specify a tag rule set, you cannot specify a tag rule. | [
{
"name": "rule-set-name",
"desc": "Name of the tag rule set."
}
] | 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. | [
"Applying Services to Subscriber-Aware Traffic with a Service Set",
"Configuring HTTP Header Enrichment Overview"
] |
tag-rules (Service Set) | [tag-rules rule-name;] | [edit services service-set service-set-name] | Specify one or more HTTP header enrichment tag rules to include in the service set. You can configure
multiple tag rules. If you specify any tag rules, you cannot specify a tag rule set. | [
{
"name": "rule-name",
"desc": "Name of the tag rule. Range: 1 through 63 alphanumeric characters"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Applying Services to Subscriber-Aware Traffic with a Service Set",
"Configuring HTTP Header Enrichment Overview"
] |
tag-separator (HTTP Header Enrichment) | tag-separator separator; | [edit services hcm tag-rule rule-name term term-number then tag tag-name] | Specify the tag separator for the tag to be inserted into the HTTP header. | [
{
"name": "separator",
"desc": "Tag separator. You may use a forward slash (/) or pipe ( | ). Default: / (forward slash)"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview",
"Configuring Tag Rules",
"Configuring HCM Profiles and Assigning Tag Rules",
"Junos Web Aware HTTP Header Enrichment Overview"
] |
tag-value (HTTP Header Enrichment) | tag-value value; | [edit services hcm tag-rule then tag] | Specify the tag value for the specified tag name.
NOTE: The tag rule must already be defined at the [edit services hcm] hierarchy level. | [
{
"name": "value",
"desc": "String of up to 16 alphanumeric characters"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview"
] |
tags (Application Identification) | tags tag-name tag-value; | [edit services application-identification application application-name] | Specify an application tag that provides general information about the application, such as associated
risk factors, technology, and the type of traffic. The tag consists of a user-defined name and value. | [
{
"name": "tag-name",
"desc": "Name for the tag, which is a textual string."
},
{
"name": "tag-value",
"desc": "Value for the tag."
}
] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
talk | talk {
disable;
traceoptions {
flag {
all {
extensive
}
}
}
} | [edit logical-systems name security alg],
[edit logical-systems name tenants name security alg],
[edit security alg],
[edit services alg],
[edit tenants name security alg] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "disable",
"desc": "Disable the TALK program ALG. By default, the TALK program ALG is enabled."
},
{
"name": "traceoptions",
"desc": "Configure TALK program ALG tracing options."
},
{
"name": "flag",
"desc": "Trace operation to perform."
},
{
"name": "all",
"des... | 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 tenant option is introduced in Junos OS Release 18.3R1. | [
"Understanding the TALK ALG"
] |
target (Routing Instances MVPN) | target target-value {
receiver target-value;
sender target-value;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols mvpn
route-target import-target],
[edit routing-instances routing-instance-name protocols mvpn route-target import-target] | Specify the target value when importing sender and receiver site routes. | [
{
"name": "target-value",
"desc": "Specify the target value when importing sender and receiver site routes."
},
{
"name": "receiver",
"desc": "Specify the target community used when importing receiver site routes."
},
{
"name": "sender",
"desc": "Specify the target community used whe... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [
"Configuring VRF Route Targets for Routing Instances for an MBGP MVPN"
] |
target | target (url URL | address) local-link IPv6-link-local-interface-name; | [edit services monitoring rpm owner name test name] | (Required) Specify the destination IPv4 or IPv6 address or URL used for the probes. | [
{
"name": "address",
"desc": "(Junos OS Evolved) For all RPM probe types other than the HTTP probes, use the specified IPv4 or IPv6 address for the target host. (Prior to Junos OS Evolved Release 23.1R1, only IPv4 addresses are supported for RPM probes.) If you also configure the link-local option, you must... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.3 for EX Series switches.
Statement introduced in Junos OS Release 13.2 for PTX Packet Transport routers.
Statement introduced in Junos OS Release 18.1 for QFX Series switches.
Statement introduced in Junos OS Evolved Release 2... | [
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches"
] |
target-address (SNMP) | target-address target-address-name {
address (SNMP) address;
address-mask address-mask;
logical-system (SNMP) logical-system;
port port-number;
retry-count (SNMP) number;
routing-instance (SNMPv3) instance;
tag-list tag-list;
target-parameters target-parameters-name;
timeout (SNMP) s... | [edit snmp v3] | Configure the address of an SNMP management application and the parameters to be used in sending
notifications. | [
{
"name": "target-address-name",
"desc": "String that identifies the target address."
}
] | 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. | [] |
target-address (TWAMP) | target-address address local-link IPv6-link-local-interface-name; | [edit services rpm twamp client control-connection control-client-name],
[edit services rpm twamp client control-connection control-client-name test-session session-name] | (Required) Specify the destination IPv4 or IPv6 address used for Junos OS probes. For specifying the
target address for TWAMP control connections and tests, see "control-connection (Junos OS Evolved)"
on page 4864. | [
{
"name": "address",
"desc": "For TWAMP managed control connections and test sessions, use the specified IPv4 or IPv6 address for the target host. MX Series and PTX Series Junos OS TWAMP Light test sessions support both IPv4 and IPv6 addresses. NOTE: Starting with Junos OS Release 14.2R2, the RPM client rou... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 9.3 for EX Series switches.
Statement introduced in Junos OS Release 13.2 for PTX Packet Transport routers.
Support at the [edit services rpm twamp client control-connection control-client-name] hierarchy level
introduced in Jun... | [
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
target-attachment-identifier (Protocols VPWS) | target-attachment-identifier identifier; | [edit logical-systems logical-system-name routing-instances instance-name protocols l2vpn site
site-name interface interface-name],
[edit routing-instances instance-name protocols l2vpn site site-name interface interface-name] | For FEC 129, specify the VPWS target attachment identifier. The point-to-point nature of VPWS
requires that you specify the source access individual identifier (SAII) and the target access individual
identifier (TAII). This SAII-TAII pair defines a unique pseudowire between two PE devices.
Auto-discovery routes are use... | [
{
"name": "identifier",
"desc": "The numerical identifier for the Layer 2 VPN site."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Example: Configuring FEC 129 BGP Autodiscovery for VPWS"
] |
target-logical-system (Domain Map) | target-logical-system logical-system-name {
target-routing-instance routing-instance-name;
} | [edit access domain map domain-map-name] | Configure a non-default logical system and optionally a non-default routing instance for the subscriber’s
interface in a domain map.
You use the target-routing-instance statement at the [edit access domain map domain-map-name] hierarchy level
to configure a non-default routing instance for the default logical system.
... | [
{
"name": "logical-system-name",
"desc": "Name of the logical system."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"Mapping Subscriber Domains to Access and Session Options"
] |
target-parameters | At the [edit snmp v3] hierarchy level:
target-parameters target-parameters-name {
profile-name;
parameters {
message-processing-model (v1 | v2c | V3);
security-level (authentication | none | privacy);
security-model (usm | v1 | v2c);
security-name security-name;
}
}
At the [e... | [edit snmp v3]
[edit snmp v3 target-address target-address-name] | Configure the message processing and security parameters for sending notifications to a particular
management target. The target parameters are configured at the [edit snmp v3] hierarchy level. The
remaining statements at this level are explained separately.
Then apply the target parameters configured at the [edit snmp... | [] | 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. | [] |
target-routing-instance (Domain Map) | target-routing-instance (routing-instance-name | default); | [edit access domain map domain-map-name],
[edit access domain map domain-map-name target-logical-system logical-system-name] | Configure the routing instance of the subscriber context.
NOTE: Subscriber management is supported in the default logical system only. The
target-logical-system statement, which appears in the CLI, is not supported in current
Junos OS releases.
Default
For dynamic LNS sessions, the routing instance of the peer (LAC fac... | [
{
"name": "routing-instance-name",
"desc": "Name of the routing instance."
},
{
"name": "default",
"desc": "The default routing instance."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
default option added in Junos OS Release 13.3. | [
"Mapping Subscriber Domains to Access and Session Options",
"Mapping Subscriber Domains to Access and Session Options"
] |
targeted-broadcast | targeted-broadcast; | [edit interfaces interface-name unit name family inet] | Specify the IP packets destined for a Layer 3 broadcast address to be forwarded to both an egress
interface and the Routing Engine, or to an egress interface only. The packets are broadcast only if the
egress interface is a LAN interface.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "forward-and-send-to-re",
"desc": "Allow packets to be forwarded and sent to Routing Engine."
},
{
"name": "forward-only",
"desc": "Allow packets only to be forwarded. Default When this statement is not included, broadcast packets are sent to the Routing Engine only."
}
] | 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.
Statement introduced in Junos OS Release 11.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Statement introduced in Junos OS Release 20.4R1 for the SRX Series. | [
"Configuring Targeted Broadcast",
"Understanding Targeted Broadcast",
"targeted-distribution (Dynamic Demux Interfaces over Aggregated"
] |
Ethernet) | targeted-distribution; | [edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number] | Configure egress data for a dynamic logical interface to be sent across a single member link in an
aggregated Ethernet bundle. A backup link is provisioned and CoS scheduling resources are switched to
the backup link in the event that the primary assigned link goes down. The aggregated Ethernet
interface must be config... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring the Distribution Type for Demux Subscribers on Aggregated Ethernet Interfaces"
] |
targeted-distribution (Static Interfaces over Aggregated Ethernet) | targeted-distribution (replicate | scale); | [edit interfaces demux0 unit logical-unit-number],
[edit interfaces pp0 unit logical-unit-number] | Configure egress data for a logical interface to be sent across a single member link in an aggregated
Ethernet bundle. A backup link is provisioned and CoS scheduling resources are switched to the backup
link in the event that the primary assigned link goes down. The aggregated Ethernet interface must be
configured wit... | [
{
"name": "replicate",
"desc": "Scheduler parameters are copied to each of the targeted aggregated interface links."
},
{
"name": "scale",
"desc": "Scheduler parameters are scaled based on number of targeted links and applied each of the"
}
] | 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. | [
"Configuring the Distribution Type for PPPoE Subscribers on Aggregated Ethernet Interfaces",
"Verifying the Distribution of PPPoE Subscribers in an Aggregated Ethernet Interface",
"Targeted Traffic Distribution on Aggregated Ethernet Interfaces in a Virtual Chassis",
"Configuring Module Redundancy for a Virtu... |
targeted-distribution | targeted-distribution {
primary-list primary-list;
backup-list backup-list;;
} | [edit logical-systems name interfaces name unit ] | Configure egress data for a member link in an aggregated Ethernet bundle. Specify a distribution list as
primary list and a different distribution list as backup list. A backup list is provisioned in the event the
primary list goes down. | [
{
"name": "primary-list",
"desc": "(Optional) Specify the role of the distribution list as primary. Member links of the aggregated Ethernet are assigned membership to the distribution list."
},
{
"name": "backup-list",
"desc": "(Optional) Specify the role of the distribution list as backup. Memb... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1. | [
"Targeted Distribution of Static Logical interfaces Across Aggregated Ethernet Member Links",
"distribution-list"
] |
targeted-hello | targeted-hello {
hello-interval seconds;
hold-time seconds;
} | [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] | Specify the LDP timer and LDP hold time for targeted hellos. | [] | 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. | [
"Configuring the LDP Timer for Hello Messages",
"Configuring the Delay Before LDP Neighbors Are Considered Down"
] |
targeted-options (Grouping Subscribers by Bandwidth Usage) | targeted-options {
backup backup;
group group;
primary primary;
weight ($junos-interface-target-weight | weight-value);
} | [edit dynamic-profiles name interfaces name unit logical-unit-number],
[edit dynamic-profiles name logical-systems name interfaces name unit logical-unit-number],
[edit interfaces name unit logical-unit-number] | Configure primary and backup links, group similar subscribers, and specify a subscriber weight for
manual targeting to distribute subscribers across aggregated Ethernet member links. | [
{
"name": "backup",
"desc": "(Optional) Specify a backup member link per subscriber when you configure manual targeting."
},
{
"name": "group",
"desc": "(Optional) Assign a group name for subscribers with similar bandwidth usage. Subscribers that are configured for targeted distribution without ... | 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.
weight option added in Junos OS Release 17.3 for MX Series and MX Virtual Chassis.
$junos-interface-target-weight option added in Junos OS Release 18.4R1. | [
"Understanding Support for Targeted Distribution of Logical Interface Sets of Static VLANs over",
"Aggregated Ethernet Logical Interfaces",
"Using RADIUS-Sourced Weights for Interface and Interface Set Targeted Distribution",
"RADIUS-Sourced Weights for Interface and Interface Set Targeted Distribution"
] |
targeted-options (Manual Targeting) | targeted-options {
(logical-interface-chassis-redundancy | logical-interface-fpc-redundancy);
rebalance-periodic {
interval interval;
start-time start-time;
}
rebalance-subscriber-granularity rebalance-subscriber-granularity;
type (auto | manual);
} | [edit dynamic-profiles name interfaces name aggregated-ether-options],
[edit dynamic-profiles name logical-systems name interfaces name aggregated-ether-options],
[edit interfaces name aggregated-ether-options] | Configure manual targeting or auto-targeting.
Specify the type of targeting to be used for targeted distribution. Specify the targeting option as manual
for conventional VLAN targeting. By default, the targeting option is auto. | [
{
"name": "type",
"desc": "Configure manual targeting type as manual or auto. Specify the type of targeting to be used for targeted distribution. Values:"
},
{
"name": "auto",
"desc": "Configure targeted-distribution without specific primary and backup links."
},
{
"name": "manual",
... | 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. | [
"Ethernet Interfaces Overview",
"Targeted Traffic Distribution on Aggregated Ethernet Interfaces in a Virtual Chassis",
"Targeted Distribution of Static Logical interfaces Across Aggregated Ethernet Member Links",
"distribution-list"
] |
targeted-options (PS Interface) | targeted-options {
logical-interface-chassis-redundancy;
logical-interface-fpc-redundancy;
rebalance-periodic {
interval interval;
start-time start-time;
}
rebalance-subscriber-granularity;
single-targeted-link;
type {
manual;
}
} | [edit interfaces ps name] | Configure the option to achieve targeted distribution only for subscriber-interface on pseudowire (PS)
IFDs when the PS IFD anchor point is a redundant logical tunnel (RLT), which has multiple LT links in
active-active mode (not in link-protection mode). | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.4R1. | [
"MPLS Pseudowire Subscriber Logical Interfaces",
"targeted-distribution"
] |
targets (Unified Edge) | targets {
target-name {
<destination-host hostname>;
destination-realm realm-name;
network-element element-name;
priority priority-value;
}
} | [edit unified-edge diameter-profiles gx-profile profile-name] | Configure the targets for this Diameter profile. | [
{
"name": "target-name",
"desc": "Name of the target."
},
{
"name": "destination-host",
"desc": ""
},
{
"name": "hostname",
"desc": "(Optional) Use the name of the destination host associated with this target."
},
{
"name": "destination-realm",
"desc": ""
},
{
"na... | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [] |
targets | targets {
address;
} | [edit snmp trap-group group-name] | Configure one or more systems to receive SNMP traps. | [
{
"name": "address",
"desc": "IPv4 or IPv6 address of the system to receive traps. You must specify an address, not a"
}
] | 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. | [] |
tca (IPLC) | tca tca-identifier (enable-tca | no-enable-tca) (threshold number | threshold-24hrs number) ; | [edit chassis fpc fpc-slot optical-options] | Granularity
Range Minimum/
Maximum
Default and
Recommended Value
Erbium-Doped Fiber Amplifier (EDFA) Input Power (for Both EDFAs)
osc-tx-power-low-tca
OSC TX power low TCA
—2/-0.5 dBm
—1 dBm
Default
By default, TCAs are disabled. | [
{
"name": "tca-identifier",
"desc": "Specify the name of the TCA identifier."
},
{
"name": "enable-tca | no-enable-tca",
"desc": "Enable or disable the threshold crossing alert."
},
{
"name": "threshold number",
"desc": "Specify the 15-minute interval threshold."
},
{
"name":... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Releases 15.1F6 and 17.1R1. | [
"Enabling and Configuring Thresholds on the Integrated Photonic Line Card Performance Monitors",
"show chassis fpc optical-properties alarms",
"show chassis fpc optical-properties edfa",
"show chassis fpc optical-properties status",
"Integrated Photonic Line Card Base and Expansion Module Overview",
"Unde... |
tca | tca tca-identifier (enable-tca | no-enable-tca) (threshold number | threshold-24hrs number) | [edit interfaces interface-name optics-options]
[edit interfaces interface-name otn-options] | TCAs can give the management system an early indication as to the state of the associated entity when
it crosses a certain threshold. TCAs can be set for both minimum and maximum values for gauges and
only maximum values for counters. The timely detection of TCAs is essential to proactively manage the
interface. TCAs a... | [
{
"name": "tca-identifier",
"desc": "At the otn-options hierarchy level, it can be one of the following:"
},
{
"name": "odu-tca-bbe",
"desc": "ODU background block error threshold-crossing defect trigger"
},
{
"name": "odu-tca-bbe-fe",
"desc": "ODU far-end background block error thre... | 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. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
tcp (Security IDP Protocol Binding) | tcp {
minimum-port port-number <maximum-port port-number>;
} | [edit security idp custom-attack attack-name attack-type chain protocol-binding],
[edit security idp custom-attack attack-name attack-type signature protocol-binding] | Allow IDP to match the attack for specified TCP ports. | [
{
"name": "minimum-port port-number",
"desc": "Minimum port in the port range."
},
{
"name": "maximum-port port-number",
"desc": "Maximum port in the port range."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
tcp (Security IDP Signature Attack) | tcp {
ack-number {
match (equal | greater-than | less-than | not-equal);
value acknowledgement-number;
}
data-length {
match (equal | greater-than | less-than | not-equal);
value tcp-data-length;
}
destination-port (Security Signature Attack) {
match (equal |... | [edit security idp custom-attack attack-name attack-type signature protocol] | Allow IDP to match the TCP header information for the signature attack. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
tcp (Security Screen) | tcp {
fin-no-ack;
land;
port-scan {
threshold number;
}
syn-ack-ack-proxy {
threshold number;
}
syn-fin;
syn-flood {
alarm-threshold number;
attack-threshold number;
destination-threshold number;
source-threshold number;
timeout sec... | [edit security screen ids-option screen-name] | Configure TCP-layer intrusion detection service (IDS) options.
NOTE: On all SRX Series Firewalls, the TCP synchronization flood alarm threshold value
does not indicate the number of packets dropped, however the value does show the
packet information after the alarm threshold has been reached.
The synchronization cookie... | [] | 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. | [] |
tcp | [edit services monitoring rpm probe-server] | Specify the port information for the TCP server.
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.
Statement introduced in Junos OS Evolved 23.4R1. | [
"Configuring RPM Receiver Servers"
] | |
tcp-aggressive-transmission | tcp-aggressive-transmission; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor neighbor-
address],
[edit logical-systems logical-system-name routing-instances routing-instance-name pro... | Enables a TCP socket option for the affected BGP sessions, which prioritizes pure ACKs and does not
exponentially back-off retransmission for couple of retransmissions. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [] |
tcp-encap | tcp-encap {
profile profile-name;
ssl-profile ssl-profile-name;
log ;
}
traceoptions {
file filename {
files number;
match regular-expression;
size maximum-file-size;
(world-readable | no-world-readable);
}
flag (all | c... | [edit security] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "profile profile-name",
"desc": "Configure a TCP encapsulation profile for a remote access client to a remote access gateway on an SRX Series Firewall to define the data encapsulation operation."
},
{
"name": "ssl-profile ssl-profile-name",
"desc": "Specify the SSL termination profile ... | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D80.
Support for the ssl-profile option added in Junos OS Release 18.1R1. | [
"Local User Authentication Using Pre-shared Key (CLI Procedure)"
] |
tcp-fast-open | tcp-fast-open {
disabled;
drop;
} | [edit services service-set service-set-name service-set-options] | Specify how TCP Fast Open (TFO) enabled packets are to be handled.
Default
By default, all TFO packets are forwarded by the service PIC. | [
{
"name": "disabled",
"desc": "Any TCP packet with the TFO option present has the TFO option stripped from the TCP header of the packet, and the rest of the packet is forwarded as is. The benefit of stripping the header over dropping the packet is that the client does not have to wait for the retransmission... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2. | [
"Exchanging Data More Efficiently Using TCP Fast Open"
] |
tcp-flags | tcp-flags {
(ack | no-ack);
(fin | no-fin);
(psh | no-psh);
(r1 | no-r1);
(r2 | no-r2);
(rst | no-rst);
(syn | no-syn);
(urg | no-urg);
} | [edit security idp custom-attack attack-name attack-type signature protocol tcp] | Specify that IDP looks for a pattern match whether or not the TCP flag is set. | [
{
"name": "ack | no-ack",
"desc": "When set, the acknowledgment flag acknowledges receipt of a packet."
},
{
"name": "fin | no-fin",
"desc": "When set, the final flag indicates that the packet transfer is complete and the connection"
},
{
"name": "psh | no-psh",
"desc": "When set, th... | 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. | [] |
tcp-forwarding (Processes) | tcp-forwarding {
disable;
traceoptions {
file filename <files number> <match regular-expression > <size maximum-file-size> <world-
readable | no-world-readable>;
flag flag;
level (all | error | info | notice | verbose | warning);
no-remote-trace;
}
} | [edit system processes] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "disable",
"desc": "Disable the TCP port forwarding process, tcpfwdd. The remaining statement is explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | trace—To view this statement in the configuration.
trace-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1. | [
"Tracing TCP Port Forwarding Events for Troubleshooting",
"TCP Port Forwarding for Remote Device Management"
] |
tcp-forwarding (Remote Device Management) | tcp-forwarding {
listening-port port-number listening-address ipv4-listening-address {
allowed-source ipv4-prefix;
forwarding-address ipv4-forwarding-address;
forwarding-port forwarding-port-number;
max-connections number;
}
} | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services],
[edit logical-systems logical-system-name system services],
[edit routing-instances routing-instance-name system services],
[edit system services] | Configure the mapping between the TCP listening address/listening port combination on the BNG and
the TCP port forwarding address/port combination where the BNG forwards the incoming data stream.
TCP port forwarding is used when the BNG, together with one or more access nodes, is treated as a
single addressable point o... | [
{
"name": "allowed-source",
"desc": ""
},
{
"name": "ipv4-prefix",
"desc": "(Optional) Restrict the IPv4 prefixes from which TCP connections are accepted on the listening port. The allowed-source value is compared to the source address in the TCP header from the triggering entity. When you do no... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1. | [
"TCP Port Forwarding for Remote Device Management"
] |
tcp-initial-timeout | tcp-initial-timeout seconds; | [edit security flow tcp-session] | Define the length of time (in seconds) that the device keeps an initial TCP session in the session table
before dropping it, or until the device receives a FIN (no more data) or RST (reset) packet. The FIN flag
indicates the end of data transmission to finish a TCP connection. | [
{
"name": "seconds",
"desc": "Number of seconds that the device keeps an initial TCP session in the session table before"
}
] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Understanding Traffic Processing on Security Devices"
] |
tcp-keepcnt | tcp-keepcnt number; | [edit services rpm twamp (client control-connection control-client-name |server)] | Number of unacknowledged probes to send before considering the connection dead and notifying the
application layer. The range is 1 through 50.
Default
The default number of TCP KEEPALIVEs sent is 6. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1. | [
"Configuring TWAMP on MX, M, T, and PTX Series Routers and EX4300 Series Switches",
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
tcp-keepidle | tcp-keepidle seconds; | [edit services rpm twamp (client control-connection control-client-name |server)] | Time interval between the last data packet sent and the first keepalive probe. The range is 1 through
600 seconds.
Default
The default value is 120 seconds. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1. | [
"Configuring TWAMP on MX, M, T, and PTX Series Routers and EX4300 Series Switches",
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
tcp-keepintvl | tcp-keepintvl seconds; | [edit services rpm twamp (client control-connection control-client-name |server)] | Time interval between successive keepalive probes. The range is 1 second through 600 seconds.
Default
The default value is 5 seconds. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1. | [
"Configuring TWAMP on MX, M, T, and PTX Series Routers and EX4300 Series Switches",
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
tcp-log | set services service-set ss1 syslog host server-IP tcp-log | [edit services service-set] | Configure TCP/TLS for logging syslog events and notifications. | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | [] | |
tcp-mss (Interfaces) | tcp-mss tcp-mss; | [edit dynamic-profiles name interfaces name unit name family inet],
[edit dynamic-profiles name interfaces name unit name family inet6],
[edit dynamic-profiles name logical-systems name interfaces name unit name family inet],
[edit dynamic-profiles name logical-systems name interfaces name unit name family inet6],
[edi... | Enable and specify the TCP maximum segment size (MSS) in bytes for transit packets in the specified
protocol family. The TCP MSS value must be lower than the MTU of the interface.
When the device receives a TCP packet with the SYN bit and MSS option set, it examines the MSS
value. If the MSS option specified in the pac... | [
{
"name": "bytes",
"desc": "TCP MSS value for SYN packets with a higher MSS value set. Range: 64 through 65535 bytes. Default: TCP MSS is disabled."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 21.1R1. Use Feature Explorer to confirm platform and
release support for this feature. | [
"Configure TCP Options"
] |
tcp-mss (Internet Options) | tcp-mss bytes; | [edit system internet-options] | Enable and specify the TCP maximum segment size (MSS) for IPV4 traffic in bytes.
When the device receives a TCP packet with the SYN bit and MSS option set, it examines the MSS
value. If the MSS option specified in the packet is larger than the MSS you configured with the tcp-mss
statement, the router replaces the MSS v... | [
{
"name": "bytes",
"desc": "TCP MSS value for SYN packets with a higher MSS value set. Range: 64 through 65535 bytes. Default: TCP MSS is disabled."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. Use Feature Explorer to confirm platform and release
support for this feature. | [
"Configure TCP Options"
] |
tcp-mss (Protocols BGP) | tcp-mss segment-size; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor neighbor-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protoco... | Configure the maximum segment size (MSS) for the TCP connection for BGP neighbors. You can set the
MSS globally or for a particular neighbor. If the router receives a TCP packet with the SYN bit and the
MSS option set, and the MSS option specified in the packet is larger than the MSS value specified by the
tcp-mss stat... | [
{
"name": "segment-size",
"desc": "MSS for the TCP connection. Range: 1 through 4096"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. Use Feature Explorer to confirm platform and release
support for this feature. | [
"Example: Limiting TCP Segment Size for BGP"
] |
tcp-mss (Security Flow) | tcp-mss {
all-tcp {
mss value;
}
gre-in {
mss value;
}
gre-out {
mss value;
}
ipsec-vpn {
mss value;
}
} | [edit security flow] | Configure TCP maximum segment size (TCP MSS) for the following packet types:
•
All TCP packets for network traffic.
•
GRE packets entering the IPsec VPN tunnel.
•
GRE packets exiting the IPsec VPN tunnel.
•
TCP packets entering the IPsec VPN tunnel.
If all the four TCP MSS options are configured simultaneously, then th... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"ipsec-vpn (Security Flow)",
"Understanding Traffic Processing on Security Devices"
] |
tcp-mss (Services) | tcp-mss number; | [edit services service-set service-set-name] | Specify the TCP Maximum Segment Size (MSS) allowed for the service set. | [
{
"name": "number",
"desc": "MSS value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring Service Set Limitations"
] |
tcp-no-flag (IDS Screen Next Gen Services) | tcp-no-flag; | [edit services screen ids-option screen-name tcp] | Identify and drop TCP packets that have no flag fields set. A TCP no flag attack can cause unpredictable
behavior on the target. | [] | 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"
] |
tcp-no-flag | tcp-no-flag; | [edit security screen ids-option screen-name tcp] | Enable the device to drop illegal TCP packets with a missing or malformed flag field. | [] | 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. | [] |
tcp-non-syn | tcp-non-syn {
drop-flow;
drop-flow-send-rst;
} | [edit services service-set service-set-name service-set-options] | Specify how the first non-SYN TCP packet is processed on services PICs. When a services PIC receives
the first non-SYN TCP packet for processing, the packet is dropped. | [
{
"name": "drop-flow",
"desc": "When a services PIC receives the first non-SYN TCP packet for processing, the packet is dropped. A drop flow created on the services PIC ensures that subsequent non-SYN TCP packets with the same 5-tuple information (source and destination addresses, protocol, and source and d... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R2. | [
"Configuring Service Sets to be Applied to Services Interfaces"
] |
tcp-options (Security Policies) | tcp-options {
initial-tcp-mss mss-value;
reverse-tcp-mss mss-value;
sequence-check-required;
syn-check-required;
window-scale;
} | Hierarchy Level
[edit logical-systems logical-systems-name security policies explicit-proxy-profile name policy
policy-name from then permit]
[edit logical-systems logical-systems-name security policies from-zone zone-name to-zone zone-
name policy policy-name then permit]
[edit logical-systems logical-systems-name se... | Specify the TCP options for each policy. You can configure sync and sequence checks for each policy
based on your requirements, and, because each policy has two directions, you can configure a TCP MSS
value for both directions or for just one direction. To configure per-policy TCP options, you must turn off
the respect... | [
{
"name": "initial-tcp-mss",
"desc": "Configure the TCP maximum segment size (MSS) for packets that arrive at the ingress interface (initial direction), match a specific policy, and for which a session is created. The value you configure overrides the TCP MSS value in the incoming packet when the value in t... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The tcp-options, sequence-check-required, and syn-check-required statements are introduced in Junos OS
Release 10.4.
The initial-tcp-mss and reverse-tcp-mss statements are introduced in Junos OS Release 12.3X48-D20.
The window-scale statement is introduced in Junos OS Release 15.1X49-D70. | [
"Security Policies Overview",
"Understanding Security Policy Rules",
"Understanding Security Policy Elements",
"tcp-mss (Security Flow)"
] |
tcp-rst | tcp-rst; | [edit security zones security-zone zone-name] | Enable the device to send a TCP segment with the RST (reset) flag set to 1 (one) in response to a TCP
segment with any flag other than SYN set and that does not belong to an existing session.
During flow first path process, a TCP RST packet is sent to the traffic originator if the TCP packet trying
to create the flow s... | [] | 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. | [
"Example: Configuring the TCP-Reset Parameter"
] |
tcp-seq-ooo-window (Security Forwarding Options) | tcp-seq-ooo-window Kbytes; | [edit security forwarding-options services-offload] | Specify the TCP sequence out of order window threshold (Kbytes) for Service offload. The configured
threshold range is from 0 Kbytes to 1023 Kbytes | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 | [
"TCP Sessions"
] |
tcp-session (Service Set Next Gen Services) | tcp-session {
inactivity-asymm-tcp-timeout ;
inactivity-tcp-timeout ;
open-timeout ;
tcp-fast-open ;
tcp-mss ;
tcp-non-syn ;
tcp-tickles ;
} | [edit services service-set service-set-name service-set-options] | Configure the TCP options for the service set. | [
{
"name": "close-timeout",
"desc": "Timeout period for TCP session tear-down (2. through 300 seconds)"
},
{
"name": "ignore-errors",
"desc": "Ignore anomalies or errors for TCP"
},
{
"name": "\"inactivity-asymm-tcp-timeout",
"desc": ""
},
{
"name": "\" on page 8889",
"des... | 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. | [] |
tcp-session | tcp-session {
aggressive-tcp-ack;
fin-invalidate-session;
maximum-window(128K | 1M | 256K | 512K | 64K);
no-sequence-check;
no-syn-check;
no-syn-check-in-tunnel;
rst-invalidate-session;
rst-sequence-check;
strict-syn-check;
tcp-fast-open;
tcp-initial-timeout seconds;
... | [edit security flow] | Configure TCP session attributes:
•
Aggressive TCP ACK
•
FIN invalidate session—To Immediately end the session on receipt of fin (FIN) segment.
•
Maximum window—Maximum TCP proxy scaled receive window, default 256K bytes.
•
TCP sequence number checking.
•
TCP SYN bit checking.
•
Reset (RST) checking.
•
Initial TCP sess... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Understanding Traffic Processing on Security Devices"
] |
tcp-session-install-interval (Security Forwarding Options) | tcp-session-install-interval mseconds; | [edit security forwarding-options services-offload] | Specify the timeout value for TCP install NP session (mseconds). The configured interval range is from
50 msec to 30,000 msec. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 | [
"TCP Sessions"
] |
tcp-sweep | tcp-sweep {
threshold number;
} | [edit security screen ids-option screen-name tcp] | Configure the device to detect and prevent TCP sweep attack. In a TCP sweep attack, an attacker sends
TCP SYN packets to the target device as part of the TCP handshake. If the device responds to those
packets, the attacker gets an indication that a port in the target device is open, which makes the port
vulnerable to a... | [
{
"name": "threshold number",
"desc": "Maximum number of microseconds during which up to 10 TCP SYN packets from the"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Attack Detection and Prevention Overview",
"Example: Configuring Multiple Screening Options"
] |
tcp-syn-defense (IDS MS-MPC) | tcp-syn-defense; | [edit services ids rule rule-name term term-name then] | Close unestablished TCP connections and send a TCP RST to the end host to clear the TCP states on it
when the open-timeout value at the [edit interfaces interface-name service-options] hierarchy level expires.
This provides protection against TCP SYN flooding attacks. This statement can only be used in IDS rules
assign... | [] | 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"
] |
tcp-syn-fragment-check (IDS MS-MPC) | tcp-syn-fragment-check; | [edit services ids rule rule-name term term-name then] | Identify and drop TCP SYN packets that are IP fragments. This statement can only be used in IDS rules
assigned to a service set on an MS-MPC. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
tcp-tickles (Service Set Next Gen Services) | tcp-tickles tcp-tickles; | [edit services service-set service-set-name service-set-options tcp-session] | Define the maximum number of keep-alive messages sent before a TCP session is allowed to timeout. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R1. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.