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 |
|---|---|---|---|---|---|---|---|
appfw-rule | appfw-rule {
maximum amount;
reserved amount;
} | [edit system security-profile security-profile-name ]
[edit tenants tenant-name security application-firewall ] | Specify the number of application firewall rule configurations that a primary administrator can configure
for a primary logical system or user logical system, when the security profile is bound to the logical
systems and tenant systems.
Tasks performed by the primary administrator are:
•
Uses security profiles to provi... | [
{
"name": "maximum amount",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its"
},
{
"name": "available",
"desc": "that is, if they are not allocated to other logical systems. The maximum allowed quota"
},
{
"name": "reserved amount",
"desc": "... | 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.
The edit tenant tenant-name security application-firewall level is introduced in Junos OS Release 18.4R1. | [] |
appfw-rule-set | appfw-rule-set {
maximum amount;
reserved amount;
} | [edit system security-profile security-profile-name ]
[edit tenants tenant-name security application-firewall] | Specify the number of application firewall rule set configurations that a primary administrator can
configure for a primary logical system or user logical system when the security profile is bound to the
logical systems and tenant systems.
The primary administrator:
•
Uses security profiles to provision logical systems... | [
{
"name": "maximum amount",
"desc": "A maximum allowed quota. If a logical system requires more of a resource than its"
},
{
"name": "available",
"desc": "that is, if they are not allocated to other logical systems. The maximum allowed quota"
},
{
"name": "reserved amount",
"desc": "... | 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.
The edit tenant tenant-name security application-firewall level is introduced in Junos OS Release 18.4R1. | [
"Application Firewall Overview"
] |
application (Adjustment Control Profiles) | application {
(ancp | dhcp-tags | pppoe-tags | radius-coa)
priority priority;
algorithm algorithm;
}
} | [edit class-of-service adjustment-control-profiles profile-name] | Configure which applications in the adjustment control profile can make shaping rate adjustments.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details. | [] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1. | [
"CoS Adjustment Control Profiles Overview",
"Configuring CoS Adjustment Control Profiles",
"Verifying the CoS Adjustment Control Profile Configuration"
] |
application (Application Identification) | application application-name <description description> {
address-mapping name {
destination {
ip ip-address-prefix;
}
source {
ip ip-address-prefix;
}
order order;
order-priority (high | low);
}
}
alt-name alt-name;
cacheabl... | [edit services application-identification] | Configure identification of an application for which one or more custom signatures are defined. | [
{
"name": "application-name",
"desc": "Name of the application for which one or more custom signatures has been defined."
},
{
"name": "description",
"desc": "(Optional) Textual description of the application for which mappings are provided. The remaining statements are explained separately. Sea... | 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.
Support for Next Gen Services introduced in Junos OS Release 19.3R2 and 19.4R1 on MX Series
MX240, MX480 and MX960. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
application (Application Identification)(SRX Series Firewalls) | application name {
address-mapping mapping-name {
destination {
ip ip;
port-range {
tcp [ tcp ... ];
udp [ udp ... ];
}
wildcard-address address wildcard-mask wildcard-mask;
}
... | [edit services application-identification] | Configure application definition.
You can create custom application signatures by specifying a name, protocol, port where the application
runs, and match criteria. You can create ICMP-based, address-based, IP protocol-based, and Layer 7-
based custom application signatures. Custom applications are created to to identif... | [
{
"name": "application",
"desc": ""
},
{
"name": "application-name",
"desc": "Name of the custom application signature. Must be a unique name with a maximum length of 63 characters. NOTE: Application names are case insensitive."
},
{
"name": "alt-name",
"desc": "Alt name for the appl... | trace—To view this statement in the configuration.
trace-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D40.
Risk option introduced in Junos OS Release 19.1R1. | [
"Example: Configuring Junos OS Application Identification Custom Application Signatures"
] |
application (Application Maps) | application application-name {
code-points [ aliases ] [ bit-patterns ];
} | [edit policy-options application-maps application-map-name] | Add an application to an application map and define the application’s code points. | [
{
"name": "application-name",
"desc": "Name of the application."
}
] | 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. | [
"Configuring an Application Map for DCBX Application Protocol TLV Exchange",
"Example: Configuring DCBX Application Protocol TLV Exchange",
"Example: Configuring DCBX to Support an iSCSI Application",
"Understanding DCBX Application Protocol TLV Exchange",
"Understanding DCBX Application Protocol TLV Exchan... |
application (Applications) | application application-name {
application-protocol (dns | ftp |gprs-gtp-c| gprs-gtp-u | gprs-gtp-v0 |gprs-sctp | http |
ignore | ike-esp-nat | mgcp-ca | mgcp-ua | ms-rpc | q931 | ras | realaudio | rsh | rtsp
| sccp | sip | sqlnet-v2 | sun-rpc | talk | tftp);
description text;
destination-p... | [edit applications] | Configure application properties at the [applications] hierarchy level. | [
{
"name": "application-protocol protocol-name",
"desc": "Specify the name of the application protocol."
},
{
"name": "description text",
"desc": "Describe the application."
},
{
"name": "destination-port port-identifier",
"desc": "Specify a TCP or UDP destination port number."
},
... | 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. | [] |
application (Defining) | application application-name {
disable;
idle-timeout seconds;
index number;
port-mapping {
disable;
port-range {
tcp [ ports-and-port-ranges ];
udp [ ports-and-port-ranges ];
}
}
session-timeout seconds;
type type;
type-of-service service-t... | [edit services application-identification] | Define the application and its properties.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "application-name",
"desc": "Identifier for the application. This is a mandatory value and has a maximum length of 32"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Defining an Application Identification"
] |
application (Extensions) | application {
file script-name {
arguments arguments;
cert-file path;
checksum hash-algorithm hash-value;
daemonize;
interpreter (bash | python | python3);
optional;
refresh;
refresh-from;
respawn-on-normal-exit;
routing-instance;
... | [edit system extensions extension-service] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 16.1. | [] |
application (Including in Rule) | application application-name; | [edit services application-identification rule rule-name] | Identify the application for inclusion in a rule. | [
{
"name": "application-name",
"desc": "Identifier for the application."
}
] | 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 APPID Rules"
] |
application (NAT Next Gen Services) | application [application-name] | [edit services nat destination rule-set rule-set rule rule-name match],
[edit services nat source rule-set rule-set rule rule-name match] | Specify one or more application protocols to which the NAT rule applies. The number of applications
must not exceed 3072. | [] | 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. | [] |
application (Security Alarms) | application {
duration interval;
size count;
threshold value;
} | [edit security alarms potential-violation policy] | Configure alarms for a number of policy violations to an application within a specified time period. | [
{
"name": "duration interval",
"desc": "Indicate the duration of counters."
},
{
"name": "size count",
"desc": "Indicate the number of applications for which policy violation checks can be done"
},
{
"name": "threshold value",
"desc": "Indicate the maximum number of application match... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Security Policies Overview"
] |
application (Security Custom Attack) | application application-name; | [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 a specified application. | [
{
"name": "application-name",
"desc": "Name of the application."
}
] | 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. | [] |
application (Security Destination NAT) | application {
[application];
any;
} | [edit logical-systems name security nat destination rule-set rule-set-name rule rule-name match],
[edit logical-systems name tenants name security nat destination rule-set rule-set-name rule
rule-name match],
[edit security nat destination rule-set rule-set-name rule rule-name match],
[edit services nat destination ru... | Specify an application name to match the rule. You can specify multiple application names, but the
number of application terms must not exceed 3072. | [
{
"name": "application-name",
"desc": "Name of the application."
}
] | 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. | [] |
application (Security IDP) | application application-name; | [edit security idp idp-policy policy-name rulebase-ips rule rule-name match] | Specify an application or an application set name to match. | [
{
"name": "application-name",
"desc": "Name of the application."
}
] | 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. | [] |
application (Security Policies) | application {
[application];
any;
} | [edit security policies from-zone zone-name to-zone zone-name policy policy-name match]
[edit security policies global policy policy-name match] | Specify the IP or remote procedure call (RPC) application or set of applications to be used as match
criteria.
Starting in Junos OS Release 19.1R1, configuring the application statement at the [edit security policies
from-zone zone-name to-zone zone-name policy policy-name match] hierarchy level is optional if the dyna... | [
{
"name": "application-name-or-set",
"desc": "Name of the predefined or custom application or application set used as match criteria."
},
{
"name": "any",
"desc": "Any predefined or custom applications or application sets. NOTE: A custom application that does not use a predefined destination por... | 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 Policies Overview",
"Configure Applications in Unified Policies"
] |
application (Security Source NAT) | application {
[application];
any;
} | [edit logical-systems name security nat source rule-set rule-name rule name match],
[edit logical-systems name tenants name security nat source rule-set name rule name match],
[edit security nat source rule-set rule-set-name rule rule-name match],
[edit services nat source rule-set rule-set-name rule rule-name match],
... | Specify an application name to match the rule. You can specify multiple application names, but the
number of application terms must not exceed 3072. | [
{
"name": "application-name",
"desc": "Name of the application."
}
] | 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. | [] |
application | application application-name {
application-protocol protocol-name;
child-inactivity-timeout seconds;
destination-port port-number;
gate-timeout seconds;
icmp-code value;
icmp-type value;
inactivity-timeout ( seconds | never );
protocol type;
rpc-program-number number;
snmp-comman... | [edit applications],
[edit applications application-set application-set-name] | Configure properties of an application and whether to include it in an application set. | [
{
"name": "application-name",
"desc": "Identifier of the application."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"ALG Descriptions",
"Configuring Application Sets",
"Configuring Application Properties",
"Examples: Configuring Application Protocols",
"Verifying the Output of ALG Sessions"
] |
application-bypass (Juniper Secure Connect) | application-bypass {
term name {
description description;
protocol protocol;
domain-name domain-name
}
} | [edit security remote-access client-config name] | Define Juniper Secure Connect remote client configuration parameters for bypassing certain
applications based on domain names and protocols without passing through the remote access VPN
tunnel. Administrator configures these parameters on the SRX Series Firewall which are pushed to client
application after its successf... | [
{
"name": "application-bypass",
"desc": "Define application-bypass configuration."
},
{
"name": "term",
"desc": "Define an application-bypass entry; specify a term name. Values: Format: Must be a string beginning with a number or letter and consisting of letters, numbers, dashes and underscore... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.1R1. | [
"Juniper Secure Connect Administration Guide"
] |
application-firewall (Application Services) | application-firewall {
rule-set rule-set-name;
} | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
application-services] | Specify the rule sets configured as part of application firewall to be applied to permitted traffic in a
security policy.
The application firewall is defined by a collection of rule sets. You can implement an application firewall
by defining one or more application firewall rule sets and creating rules for each rule se... | [
{
"name": "rule-set rule-set-name",
"desc": "Name of the rule set that contains application firewall specification rules."
}
] | 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. | [
"Application Firewall Overview"
] |
application-firewall | application-firewall {
profile profile-name {
block-message type {
custom-text content custom-html-text;
custom-redirect-url content custom-redirect-url;
}
}
rule-sets rule-set-name {
default-rule {
(deny [block-message] | permit | reject [block-me... | [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... | [] | 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. Updated with the ssl-encryption and reject options in
Junos OS Release 12.1X44-D10. Updated with the block-message option in Junos OS Release 12.1X45-
D10.
The tenant option is introduced for Junos OS Release 18.4R1. | [
"Application Firewall Overview"
] |
application-group (Services) | application-group group-name {
application-groups application-group-name;
applications application-name;
} | [edit services application-identification] | Configure a custom application group for application identification.
Applications can be grouped under predefined and custom application groups. You can add number of
applications or application groups that you want to include in your custom application group.
You can configure an application group to associates relate... | [
{
"name": "group-name",
"desc": "Name of the group. This name is used in policy configuration statements in place of multiple predefined applications, user-defined applications, or other groups."
},
{
"name": "application-groups",
"desc": ""
},
{
"name": "application-group-name",
"de... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Example: Configuring a Custom Application Group for Junos OS Application Identification for",
"Simplified Management"
] |
application-group | application-group group-name {
disable;
application-groups {
application-group-name;
}
applications {
application-name;
}
index number;
} | [edit services application-identification] | Define the properties and contents of the application group. | [
{
"name": "group-name",
"desc": "Unique identifier for the group."
}
] | 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.
Support added in Junos OS release 19.3R2 and 19.4r1 for Next Gen Services on MX240, MX480, and
MX960.
NOTE: The disable and index options are not supported for Next Gen Services. | [] |
application-group-any (AACL) | application-group-any; | [edit services aacl rule rule-name term term-name from]
[edit services aacl rule rule-name No Link Title term-name No Link Title] | Match any application group defined in the database. | [] | 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 Match Conditions in AACL Rules"
] |
application-groups (PCC Rules) | application-groups [application-group-name]; | [edit unified-edge pcef pcc-rules rule-name from],
[edit services pcef pcc-rules rule-name from] | Specify one or more application groups to define the match criteria for the policy and charging control
(PCC) rule. You can specify a maximum of 10 application groups in a PCC rule.
NOTE: You must also include the flows statement. If you do not want to filter subscriber
traffic based on service data flow filters, use f... | [
{
"name": "application-group-name",
"desc": "Name of an application group that is used to detect IP packet flows. Range: 1 through 63 characters. NOTE: The referenced application groups must have been previously configured in the [edit services application-identification] hierarchy level."
}
] | 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 from] 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
Rel... | [
"Configuring Policy and Charging Control Rules"
] |
application-groups (Services AACL) | application-groups [ application-group-names ]; | [edit services aacl rule rule-name term term-name from] | Identify one or more application groups defined in the application identification configuration for
inclusion as a match condition. | [
{
"name": "application-group-names",
"desc": "Identifiers of the application groups."
}
] | 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 Match Conditions in AACL Rules"
] |
application-groups (Services Application Identification) | application-groups {
application-group-name;
} | [edit services application-identification application-group group-name] | Identify the list of application groups for inclusion in a larger application group. An application-group-name
statement is mandatory. | [
{
"name": "application-group-name",
"desc": "Identifier for the application group. Maximum length is 32 characters."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Support added in Junos OS release 19.3R2 and 19.4r1 for Next Gen Services on MX240, MX480, and
MX960. | [
"Configuring Application Groups"
] |
application-identification (Application Identification) | application-identification {
application application-name <description description> {
address-mapping name {
destination {
ip ip-address-prefix;
}
source {
ip ip-address-prefix;
}
order order;
order-prio... | [edit services] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "application",
"desc": ""
},
{
"name": "application-name",
"desc": "Configure application definition. You can create custom application signatures by specifying a name, protocol, port where the application runs, and match criteria."
},
{
"name": "application-group",
"desc":... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support for Next Gen Services introduced in Junos OS Release 19.3R2 and 19.4R1 on MX Series routers
MX240, MX480 and MX960. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
application-identification (IDP Sensor Configuration) | application-identification {
max-packet-memory-ratio percentage-value;
max-reass-packet-memory-ratio percentage-value;
max-tcp-session-packet-memory value;
max-udp-session-packet-memory value;
} | [edit security idp sensor-configuration] | Enable to identify the TCP/UDP application session running on nonstandard ports to match the
application properties of transiting network traffic.
Options define the allocation of IDP memory to application identification for packet and reassembler
use. | [] | 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. Packet memory percentages added in Junos OS Release
12.1X44-D20. | [] |
application-identification (Services) | application-identification {
application application-name {
address-mapping address-name {
filter {
ip ip-address-and-prefix-length;
port-range {
tcp [port];
udp [port];
}
}
}
cach... | [edit services] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "application",
"desc": ""
},
{
"name": "application-name",
"desc": "Configure application definition. You can create custom application signatures by specifying a name, protocol, port where the application runs, and match criteria."
},
{
"name": "application-group",
"desc":... | 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.
Custom application definition option introduced in Junos OS Release 15.1X49-D40.
Risk option introduced in Junos OS Release 19.1R1.
micro-app option introduced in Junos OS Release 19.2R1.
global-offload-byte-limit and inspection-limit options are introduced in Junos OS Rel... | [
"Understanding Application Identification Techniques"
] |
application-identification-profile (Service Set) | application-identification-profile app-id-profile-name; | [edit services service-set service-set-name] | Specify the dummy application identification profile that you configured at the [edit services application-
identification profile] hierarchy level. This profile is a placeholder profile with no configuration options,
but it must be specified to enable application identification functionality on the services plane. | [
{
"name": "app-id-profile-name",
"desc": "Name of the application identification profile."
}
] | 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",
"Identifying the Service Interface That Handles Subscriber Management Application-Aware Policy",
"Control"
] |
application-map | application-map application-map-name; | [edit protocols dcbx interface interface-name] | Specify an application map to apply to an interface. | [
{
"name": "application-map-name",
"desc": "Name of the application map."
}
] | 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. | [
"Applying an Application Map to an Interface for DCBX Application Protocol TLV Exchange",
"Example: Configuring DCBX Application Protocol TLV Exchange",
"Example: Configuring DCBX to Support an iSCSI Application",
"Understanding DCBX Application Protocol TLV Exchange",
"Understanding DCBX Application Protoc... |
application-maps | application-maps application-map-name {
application application-name {
code-points [ aliases ] [ bit-patterns ];
}
} | [edit policy-options] | Define an application map by specifying the applications that belong to the application map. | [
{
"name": "application-map-name",
"desc": "Name of the application map."
}
] | 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. | [
"Configuring an Application Map for DCBX Application Protocol TLV Exchange",
"Example: Configuring DCBX Application Protocol TLV Exchange",
"Example: Configuring DCBX to Support an iSCSI Application",
"Understanding DCBX Application Protocol TLV Exchange",
"Understanding DCBX Application Protocol TLV Exchan... |
application-profile (Services CoS Next Gen Services) | application-profile name {
ftp {
data {
dscp dscp;
forwarding-class forwarding-class;
}
}
sip {
... | [edit services cos] | Configure CoS actions for FTP and SIP traffic. The application profile can then be used in CoS rule
actions. This enables you to apply a certain DSCP, or forwarding-class to a set of L7 flows. | [
{
"name": "profile-name",
"desc": "Name of the application profile."
}
] | 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)"
] |
application-profile | application-profile profile-name {
ftp {
data {
dscp (alias | bits);
forwarding-class class-name;
}
}
sip {
video {
dscp (alias | bits);
forwarding-class class-name;
}
voice {
dscp (alias | bits);
... | [edit services cos],
[edit services cos rule rule-name term term-name then],
[edit services cos rule rule-name term term-name then reverse] | Define or apply a CoS application profile. When you apply a CoS application profile in a CoS rule,
terminate the profile name with a semicolon (;). | [
{
"name": "profile-name",
"desc": "Identifier for the application profile."
}
] | 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 Application Profiles for Use as CoS Rule Actions"
] |
application-protocol (Applications) | application-protocol (bootp | dce-rpc | dce-rpc-portmap | dns | exec | ftp | ftp-data | gprs-gtp-
c | gprs-gtp-u | gprs-gtp-v0 | gprs-sctp | h323 | http | https | icmp | icmpv6 | ignore | iiop |
ike-esp-nat | imap | imaps | ip | login | mgcp-ca | mgcp-ua | ms-rpc | netbios | netshow | none
| pop3 | pop3s | pptp | q93... | [edit applications application],
[edit logical-systems name applications application],
[edit logical-systems name tenants name applications application],
[edit tenants name applications application] | Identify the application protocol name. Application protocols are also called application layer gateways
(ALGs). Define an application layer gateway (ALG) for a particular application. The following ALGs are
supported:
protocol-name—Name of the protocol. The following protocols are supported:
1.
bootp—Bootstrap protoco... | [] | 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.
login options introduced in Junos OS Release 7.4.
ip option introduced in Junos OS Release 8.2.
ike-esp-nat option introduced in Junos OS Release 17.1.
ras option introduced in Junos OS Release 17.1. | [
"Security Policy Application Sets Overview"
] |
application-protocol | application-protocol protocol-name; | [edit applications application application-name] | Identify the application protocol name. Application protocols are also called application layer gateways
(ALGs). | [
{
"name": "protocol-name",
"desc": "Name of the protocol. The following protocols are supported:"
},
{
"name": "bootp",
"desc": "Bootstrap protocol"
},
{
"name": "dce-rpc",
"desc": "DCE RPC"
},
{
"name": "dce-rpc-portmap",
"desc": "DCE RPC portmap"
},
{
"name": "d... | 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.
login options introduced in Junos OS Release 7.4.
ip option introduced in Junos OS Release 8.2.
ike-esp-nat option introduced in Junos OS Release 17.1.
ras option introduced in Junos OS Release 17.1. | [
"ALG Descriptions",
"Configuring Application Sets",
"Configuring Application Properties",
"Examples: Configuring Application Protocols",
"Verifying the Output of ALG Sessions"
] |
application-proxy (Security Content Security) | application-proxy {
traceoptions {
flag flag;
}
} | [edit security utm default-configuration]
[edit security utm] | 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... | [] | 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. | [] |
application-screen (Security H323) | application-screen {
message-flood {
gatekeeper {
threshold rate;
}
}
unknown-message {
permit-nat-applied;
permit-routed;
}
} | [edit logical-systems name security alg h323],
[edit logical-systems name tenants name security alg h323],
[edit security alg h323],
[edit services alg h323],
[edit tenants name security alg h323] | Configure the security screens for the H.323 protocol Application Layer Gateway (ALG) to handle
unknown-messages and protect H.323 server. | [] | 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. | [] |
application-screen (Security MGCP) | application-screen {
connection-flood {
threshold rate;
}
message-flood {
threshold rate;
}
unknown-message {
permit-nat-applied;
permit-routed;
}
} | [edit logical-systems name security alg mgcp],
[edit logical-systems name tenants name security alg mgcp],
[edit security alg mgcp],
[edit services alg mgcp],
[edit tenants name security alg mgcp] | Configure the security screens for the Media Gateway Control Protocol (MGCP) Application Layer
Gateway (ALG) to handle unknown-messages and protect MGCP server. | [] | 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. | [] |
application-screen (Security SCCP) | application-screen {
call-flood {
threshold rate;
}
unknown-message {
permit-nat-applied;
permit-routed;
}
} | [edit logical-systems name security alg sccp],
[edit logical-systems name tenants name security alg sccp],
[edit security alg sccp],
[edit services alg sccp],
[edit tenants name security alg sccp] | Configure the security screens for the Skinny Client Control Protocol (SCCP) Application Layer Gateway
(ALG) to handle unknown-messages and protect SCCP server. | [] | 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. | [] |
application-screen (Security SIP) | application-screen {
protect {
deny {
all {
timeout value-in-seconds;
}
destination-ip address;
timeout value-in-seconds;
}
}
unknown-message {
permit-nat-applied;
permit-routed;
}
} | [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 the security screens for the Session Initiation Protocol (SIP) Application Layer Gateway (ALG)
to handle unknown-messages and protect SIP server.
IPv6 is supported on the SIP ALG along with Network Address Translation Protocol Translation (NAT-PT)
mode and NAT64 address translation.
The type of the <destinati... | [] | 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. | [] |
application-services (Security Forwarding Process) | application-services {
enable-gtpu-distribution;
inline-fpga-crypto (disabled | enabled);
maximize-alg-sessions;
maximize-idp-sessions {
weight (firewall | idp);
}
packet-ordering-mode (Application Services) {
(hardware | software);
}
} | [edit security forwarding-process] | You can configure SRX4100, SRX4200, SRX5400, SRX5600, and SRX5800 devices to switch from an
integrated firewall mode to maximize Intrusion Detection and Prevention (IDP) mode to run IDP
processing in tap mode and increase the capacity of processing with the maximize-idp-sessions option.
Inline tap mode can only be conf... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 9.6. Statement updated in Junos OS Release 10.4. Statement
updated in Junos OS Release 15.1X49-D40 with the enable-gtpu-distribution option. Statement updated
in Junos OS Release 20.4R1 with the inline-fpga-crypto (disabled | enabled) option. | [
"Understanding Traffic Processing on Security Devices"
] |
application-services (Security Policies) | application-services {
(redirect-wx | reverse-redirect-wx);
advanced-anti-malware-policy advanced-anti-malware-policy;
anti-virus-policy anti-virus-policy;
application-traffic-control {
rule-set rule-set;
}
captive-portal {
profile profile;
... | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit] | Enable application services within a security policy. You can enable service such as application firewall,
IDP, Content Security, SSL proxy, and so on by specifying them in a security policy permit action, when
the traffic matches the policy rule. | [
{
"name": "advanced-anti-malware-policy",
"desc": "Specify advanced-anti-malware policy name."
},
{
"name": "application-firewall",
"desc": "Specify the rule sets configured as part of application firewall to be applied to the permitted traffic."
},
{
"name": "application-traffic-control... | 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. | [
"Application Firewall Overview"
] |
application-services (security-metadata-streaming) | application-services {
security-metadata-streaming-policy policy-name;
} | [edit security policies from-zone from-zone to-zone to-zone] | Enable security metadata streaming-policy on SRX Series Firewall.
Default
security-metadata-streaming-
policy policy-name
Specify the security-metadata-streaming policy that you configured at
[edit services] hierarchy level. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.2 R1. | [] |
application-set | application-set application-set-name {
application application-name;
} | [edit applications] | Configure one or more applications to include in an application set. | [
{
"name": "application-set-name",
"desc": "Identifier of an application set."
}
] | system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"ALG Descriptions",
"Configuring Application Sets",
"Configuring Application Properties",
"Examples: Configuring Application Protocols",
"Verifying the Output of ALG Sessions"
] |
application-sets (IDS MS-DPC) | application-sets set-name; | [edit services ids rule rule-name term term-name from] | Define one or more target application sets when using the MS-DPC. | [
{
"name": "set-name",
"desc": "Name of the target application set."
}
] | 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 Match Conditions in IDS Rules"
] |
application-sets (PCP) | applications-sets set-name; | [edit services pcp rule rule-name term term-name from] | Define an application set to which the PCP rule applies. A PCP rule assigns the PCP server that handles
selected traffic.
PCP is supported on the MS-DPC, MS-100, MS-400, and MS-500 MultiServices PICS. Starting in Junos
OS Release 17.4R1, PCP is also supported on the MS-MPC and MS-MIC. | [
{
"name": "set-name",
"desc": "Name of the application set."
}
] | 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"
] |
application-sets (Services CoS) | applications-sets set-name; | [edit services cos rule rule-name term term-name from] | Define one or more target application sets. | [
{
"name": "set-name",
"desc": "Name of the target application set."
}
] | 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 Match Conditions In CoS Rules"
] |
application-sets (Services NAT) | applications-sets set-name; | [edit services nat rule rule-name term term-name from] | Define one or more target application sets. | [
{
"name": "set-name",
"desc": "Name of the target application set."
}
] | 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"
] |
application-sets (Services Stateful Firewall) | applications-sets set-name; | [edit services stateful-firewall rule rule-name term term-name from] | Define one or more target application sets. | [
{
"name": "set-name",
"desc": "Name of the target application set."
}
] | 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 Match Conditions in Stateful Firewall Rules"
] |
application-specific (Protocols OSPF) | application-specific {
attribute-group name {
admin-group;
advertise-interface-delay;
application flex-algorithm;
delay-metric;
te-metric;
}
} | [edit logical-systems logical-system-name protocols ospf area area-id interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ospf
area area-id interface interface-name],
[edit protocols ospf area area-id interface interface-name],
[edit routing-instances ... | Configure application (flexible algorithm) specific attributes such as te-attributes: te-metric, delay-metric,
or admin-groups.
NOTE: The Junos OS and Junos OS Evolved implementation of OSPF application-
specific link attribute supports flexible algorithm application only. | [
{
"name": "attribute-group",
"desc": ""
},
{
"name": "name",
"desc": "Indicates an application-specific link attribute for the link. The attribute-group enables multiple applications to share the same attribute."
},
{
"name": "admin-group",
"desc": "Define an admin-group for the attr... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 22.2R1. | [
"Understanding OSPF Flexible Algorithm for Segment Routing",
"Configuring Application-Specific Link Attribute on an OSPF Interface"
] |
application-status | application-status (any | error) | [edit system syslog console] | Enable logging of application start or stop status. During system reboot, by default, the systemd process
logs messages for applications to the journal log. By default, application stop and start status are written
to the journal log. Only application stop and start errors are logged to the console.
This configuration ... | [
{
"name": "(any | error)",
"desc": ""
},
{
"name": "any",
"desc": "Write all application stop and start status messages to the console."
},
{
"name": "error",
"desc": "Write only application stop and start error messages to the console."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 23.1R1. | [
"System Log Explorer"
] |
application-system-cache | application-system-cache {
no-miscellaneous-services;
security-services;
} | [edit services application-identification] | Enable application system cache (ASC) to save the mapping between an application type and the
corresponding destination IP address, destination port, protocol type, and service.
You can enable the ASC for faster application identification process and disable it for performance
benefits and security.
ASC is enabled by d... | [
{
"name": "no-miscellaneous-services",
"desc": "Disable the ASC for miscellaneous services such as APBR and AppTrack."
},
{
"name": "security-services",
"desc": "Enable the ASC for security services such as security policies, application firewall (AppFW), Juniper ATP Cloud, IDP, and Content Secu... | 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. The options no-miscellaneous-services and security-services
are introduced in Junos OS Release 18.2R1. | [
"Understanding the Application System Cache"
] |
application-system-cache-timeout (Services) | application-system-cache-timeout value; | [edit services application-identification] | Specify the timeout value in seconds for the application system cache (ASC) entries.
ASC saves the mapping between an application type and the corresponding destination IP address,
destination port, protocol type, and service. By default, the ASC saves the mapping information for
3600 seconds.
NOTE: On SRX Series Firew... | [
{
"name": "value",
"desc": "Timeout value for the application system cache entries."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. Support. | [
"Understanding the Application System Cache"
] |
application-system-cache-timeout | application-system-cache-timeout seconds; | [edit services application-identification] | Configure the lifetime for entries in the application system cache.
Specify the timeout value in seconds for the application system cache (ASC) entries.
ASC saves the mapping between an application type and the corresponding destination IP address,
destination port, protocol type, and service. By default, the ASC saves... | [
{
"name": "seconds",
"desc": "Lifetime for system cache entries, in seconds."
}
] | 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.
Support added in Junos OS release 20.2R1 for Next Gen Services on MX240, MX480, and MX960
routers. | [
"Configuring Global APPID Properties"
] |
application-tracking (Security Zones) | application-tracking; | [edit security zones security-zone zone-name] | Enable application tracking support for 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 10.2. | [
"Example: Configuring Application Tracking"
] |
application-tracking | application-tracking {
(first-update | first-update-interval minutes);
disable (Application Tracking);
session-update-interval minutes;
log-session-create;
log-session-close;
session-update-interval session-update-interval;
no-volume-updates;
} | [edit security] | Enable application tracking (AppTrack).
After application identification identifies the application, AppTrack collects statistics for the application
usage on the device, and when the session closes, AppTrack generates a message that provides the byte
and packet counts and duration of the session, and sends details to ... | [
{
"name": "first-update",
"desc": "Generate application tracking initial message when a session is created. This option overrides the first-update-interval option if both are specified."
},
{
"name": "first-update-interval",
"desc": "Interval when the first update message is sent (minutes). NOTE... | 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. Support for disable added in Junos OS Release 11.4.
Configuration statement log-session-create, log-session-close, session-update-interval session-update-interval,
and no-volume-updates are added in Junos OS Release 21.1R1. | [
"Example: Configuring AppTrack"
] |
application-traffic-control (Application Services) | application-traffic-control {
rule-set rule-set-name;
} | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
application-services]
[edit logical-systems logical-system-name security policies from-zone zone-name to-zone zone-
name policy policy-name then permit application-services]
[edit tenants tenant-name security policies from-zon... | Enables AppQoS, application-aware quality of service, as specified in the rules of the specified rule set. | [
{
"name": "rule-set rule-set-name",
"desc": "Name of the rule set that contains application-aware traffic control"
}
] | 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.
Support at the following hierarchy levels introduced in Junos OS Release 19.3R1: [edit logical-systems
logical-system-name security policies from-zone zone-name to-zone zone-name policy policy-name then permit
application-services], and [edit tenants tenant-name security p... | [
"Example: Configuring Application Quality of Service",
"Security Policies Overview"
] |
application-traffic-control | application-traffic-control {
rate-limiters {
rate-limiter-name {
bandwidth-limit value-in-kbps;
burst-size-limit value-in-bytes;
}
}
rule-sets ruleset-name{
{
rule rule-name {
match {
application application-na... | [edit class-of-service] | Mark DSCP values for outgoing packets or apply rate limits based on the specified Layer 7 application
types. | [] | 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. | [
"Example: Configuring AppTrack"
] |
application-unknown | application-unknown | [edit services aacl rule rule-name No Link Title term-name No Link Title] | Enable AACL logging of flows for unknown applications. | [] | Statement introduced in Junos OS Release 11.2. | [] | |
applications (Applications) | applications {
application application-name {
destination-port port-value;
protocol (tcp | udp);
ether-type type;
}
} | [edit] | Define applications that DCBX advertises. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Defining an Application for DCBX Application Protocol TLV Exchange",
"Example: Configuring DCBX Application Protocol TLV Exchange",
"Example: Configuring DCBX to Support an iSCSI Application",
"Understanding DCBX Application Protocol TLV Exchange",
"Understanding DCBX Application Protocol TLV Exchange on E... |
applications (DCBX) | applications {
fcoe {
no-auto-negotiation;
}
} | [edit protocols dcbx interface interface-name] | Configure Data Center Bridging Capability Exchange protocol (DCBX) applications on an interface. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Understanding DCB Features and Requirements"
] |
applications (Diameter) | applications {
pcc-gx {
maximum-pending-requests requests;
}
} | [edit access diameter] | Configure the parameters for Diameter applications. Specify the Diameter application for which you are
configuring the parameters. The Gx application (pcc-gx) is currently supported. | [
{
"name": "pcc-gx",
"desc": "Use the parameters for the Gx application. The remaining statement is explained separately. See CLI Explorer."
}
] | 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. | [] |
applications (IDS MS-DPC) | applications [ application-name ]; | [edit services ids rule rule-name term term-name from] | Define one or more applications to which IDS applies when using the MS-DPC. | [
{
"name": "application-name",
"desc": "Name of the target application."
}
] | 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 Match Conditions in IDS Rules"
] |
applications (PCC Rules) | applications [application-name]; | [edit unified-edge pcef pcc-rules rule-name from],
[edit services pcef pcc-rules rule-name from] | Specify one or more applications to define the match criteria for the policy and charging control (PCC)
rule. You can specify a maximum of 10 applications in a PCC rule.
NOTE: You must also include the flows statement. If you do not want to filter subscriber
traffic based on service data flow filters, use flows any.
If... | [
{
"name": "application-name",
"desc": "Name of one or more applications that is used to detect IP packet flows. Range: 1 through 63 characters. NOTE: The referenced application must have been previously configured in the [edit services application-identification] hierarchy level."
}
] | 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 from] 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
Rel... | [
"Configuring Policy and Charging Control Rules"
] |
applications (PCP) | applications [ application-name ]; | [edit services pcp rule rule-name term term-name from] | Define one or more application protocols to which the PCP rule applies. A PCP rule assigns the PCP
server that handles selected traffic.
PCP is supported on the MS-DPC, MS-100, MS-400, and MS-500 MultiServices PICS. Starting in Junos
OS Release 17.4R1, PCP is also supported on the MS-MPC and MS-MIC. | [
{
"name": "application-name",
"desc": "Name of the application."
}
] | 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"
] |
applications (Services AACL) | applications [ application-names ]; | [edit services aacl rule rule-name term term-name from] | Identify one or more applications defined in the application identification configuration for inclusion as a
match condition. | [
{
"name": "application-names",
"desc": "Identifiers of the applications."
}
] | 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 Match Conditions in AACL Rules"
] |
applications (Services ALGs) | applications { ... } | [edit] | Define the applications used in services. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"ALG Descriptions",
"Configuring Application Sets",
"Configuring Application Properties",
"Examples: Configuring Application Protocols",
"Verifying the Output of ALG Sessions"
] |
applications (Services Application Identification) | applications {
application-name;
} | [edit services application-identification application-group group-name] | Identify the list of applications for inclusion in the application group. | [
{
"name": "application-name",
"desc": "Identifier for the application. Maximum length is 32 characters."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Support added in Junos OS release 19.3R2 and 19.4R1 for Next Gen Services on MX240, MX480, and
MX960. | [] |
applications (Services CoS) | applications [ application-name ]; | [edit services cos rule rule-name term term-name from] | Define one or more applications to which the CoS services apply. | [
{
"name": "application-name",
"desc": "Name of the target application."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Configuring CoS Rules",
"Configuring Match Conditions In CoS Rules"
] |
applications (Services NAT) | applications [ application-name ]; | [edit services nat rule rule-name term term-name from] | Define one or more application protocols to which the NAT services apply. | [
{
"name": "application-name",
"desc": "Name of the target application."
}
] | 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"
] |
applications (Services Stateful Firewall) | applications application-name; | [edit services stateful-firewall rule (Services Stateful Firewall) rule-name term (Services Stateful
Firewall) term-name from (Services Stateful Firewall) ] | Define one or more applications to which the stateful firewall services apply. | [
{
"name": "application-name",
"desc": "Name of the target application."
}
] | 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 Match Conditions in Stateful Firewall Rules"
] |
apply-action-profile | apply-action-profile profile-name; | [edit protocols oam ethernet link-fault-management interface] | Apply the specified action profile to the interface for link-fault management. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Applying an Action Profile"
] |
apply-flags-omit | apply-flags [omit]; | All hierarchy levels | The apply-flags omit statement excludes parts of the configuration from being displayed and omits them
from appearing in the output of the show configuration command. Any omitted configuration is still there
in the configuration and visible to the system upon commit, however it is not displayed to the user
unless speci... | [
{
"name": "omit",
"desc": "Omit the parent statement during normal display."
}
] | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy. | Statement introduced before Junos OS Release 7.4. | [] |
apply-groups (Chassis Cluster) | apply-groups [$node] | [edit chassis cluster] | Apply node-specific parameters to each node in a chassis cluster.
You can use the [edit groups] option to create a unique configuration between the cluster members by
defining a unique hostname for each node and assigning a unique IP address for the fxp0 interface on
each node.
Each group is named after the node it is ... | [
{
"name": "${node}",
"desc": "Each node (node0 or node1) in a chassis cluster."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [] |
apply-groups (Subscriber Secure Policy) | apply-groups group-name; | [edit services radius-flow-tap policy policy-name inet drop-policy rule-name from],
[edit services radius-flow-tap policy policy-name inet6 drop-policy rule-name from] | Specify groups from which to inherit configuration data for the radius-flow-tap policy. | [
{
"name": "group-name",
"desc": "Name of the group that inherits the configuration data."
}
] | flow-tap—To view this statement in the configuration.
flow-tap-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Subscriber Secure Policy Overview",
"Configuring RADIUS-Initiated Subscriber Secure Policy Mirroring Overview"
] |
apply-groups | apply-groups [ group-names ]; | All hierarchy levels | Apply a configuration group to a specific hierarchy level in a configuration, to have a configuration
inherit the statements in the configuration group.
You can specify more than one group name. You must list them in order of inheritance priority. The
configuration data in the first group takes priority over the data i... | [
{
"name": "group-names",
"desc": "One or more names specified in the groups statement."
}
] | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy. | Statement introduced before Junos OS Release 7.4. | [
"Applying a Configuration Group"
] |
apply-groups-except (Subscriber Secure Policy) | apply-groups-except group-name; | [edit services radius-flow-tap policy policy-name inet drop-policy rule-name from],
[edit services radius-flow-tap policy policy-name inet6 drop-policy rule-name from] | Specify groups from which to inherit configuration data for the radius-flow-tap policy. | [
{
"name": "group-name",
"desc": "Name of the group that does not inherit the configuration data."
}
] | flow-tap—To view this statement in the configuration.
flow-tap-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Subscriber Secure Policy Overview",
"Configuring RADIUS-Initiated Subscriber Secure Policy Mirroring Overview"
] |
apply-groups-except | apply-groups-except [ group-names ]; | All hierarchy levels except the top level | Disable inheritance of a configuration group. | [
{
"name": "group-names",
"desc": "One or more names specified in the groups statement."
}
] | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy. | Statement introduced before Junos OS Release 7.4. | [
"Disabling Inheritance of a Configuration Group"
] |
apply-macro | apply-macro apply-macro-name {
parameter-name parameter-value;
} | All hierarchy levels | Use custom syntax in your configuration, which is expanded into standard Junos OS configuration
statements during the commit process using the instructions defined in the corresponding commit script
macro.
Macros work by locating apply-macro statements that you include in the candidate configuration and using
the value... | [
{
"name": "apply-macro-name",
"desc": "Name of the apply-macro statement."
},
{
"name": "parameter-name",
"desc": "One or more parameters. Parameters can be any text you want to include in your configuration."
},
{
"name": "parameter-value",
"desc": "A value that corresponds to the p... | configure—To enter configuration mode; other required privilege levels depend on where the statement
is located in the configuration hierarchy. | Statement introduced in Junos OS Release 7.4. | [
"Overview of Creating Custom Configuration Syntax with Commit Script Macros"
] |
apply-path | apply-path path; | [edit logical-systems logical-system-name policy-options prefix-list name],
[edit policy-options prefix-list name] | Expand a prefix list to include all prefixes pointed to by a defined path. Using the apply-path statement
eliminates most of the effort required to maintain a group prefix list. You can use this expanded list in
defining policies and firewalls.
You can also use the apply-path configuration statement with SNMP, as long ... | [
{
"name": "path",
"desc": "String of elements composed of identifiers or configuration keywords that points to a set of"
}
] | 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 apply-path "access radius-server <*>" configuration for SNMP added in Junos OS Release 16.1.
Support for the prefix-list match condition added in Junos OS Evolved Release 20.2R1 for PTX10003. | [
"Configuring Prefix Lists",
"Example: Configuring a Filter to Limit TCP Access to a Port Based On a Prefix List"
] |
apply-secondary-as-giaddr | apply-secondary-as-giaddr; | For platforms without ELS:
[edit forwarding-options helpers bootp],
[edit forwarding-options helpers bootp interface]
For platforms with ELS:
[edit forwarding-options dhcp-relay overrides]
[edit forwarding-options dhcp-relay group name interface name overrides] | Configures the interfaces on a switch that are DHCP relay agents to be enabled for smart DHCP relay.
Smart DHCP relay enables you to configure alternative IP addresses for the gateway interface so that if
the server fails to reply to the requests sent from the primary gateway address, the switch can resend
the requests... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D26. | [
"Configuring DHCP and BOOTP Relay"
] |
apply-to-half-close-state | apply-to-half-close-state; | [edit security flow tcp-session time-wait-state] | Configure the TCP session timeout in a half-closed state. This enables the system to apply the
configured session timeout on receiving only one FIN packet (either client-to-server or server-to-client).
When this is not configured, the default behavior takes effect—applying the configured TCP session
timeout on receivin... | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 12.1X46-D10. | [
"Understanding Traffic Processing on Security Devices"
] |
appselid | appselid
{ id id;
} | [edit interfaces interface-name optics-options] | Configure application selection with the appsel ID. | [
{
"name": "id",
"desc": "Appsel ID"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.2R1 for PTX10001-36MR, PTX10002-36QDD,
PTX10004, PTX10008, and PTX10016 routers. | [
"show interfaces diagnostics optics-applications",
"400ZR and 400G OpenZR+ Optical Transceivers"
] |
apts | apts {
domain domain | apply-groups | apply-groups-except
} | [edit logical-systems name protocols ptp],
[edit protocols ptp] | Configure the PTP assisted partial timing support (APTS) related parameters. | [
{
"name": "domain",
"desc": "Domain used for APTS profile Range: 44 through 63 Default: 44 NOTE: If the domain is not specified, then the default is applied."
},
{
"name": "apply-groups",
"desc": "Groups to inherit configuration data from"
},
{
"name": "apply-groups-except",
"desc"... | Statement introduced in Junos OS Evolved Release 24.2R2. | [
"Assisted Partial Timing Support on Routing Platforms"
] | |
archival | archival {
configuration {
archive-sites {
file://<path>/<filename>;
ftp://username@host<:port>url-path password password;
http://username@host<:port>url-path password password;
pasvftp://username@host<:port>url-path password password;
scp://userna... | [edit system] | Configure copying of the currently active configuration to an archive site. An archive site can be a file, or
an FTP, HTTP, passive FTP, or SCP location. | [
{
"name": "configuration",
"desc": "Configure the router or switch to periodically transfer its currently active configuration (or after each commit). Parameters include archive-sites, transfer-interval, and transfer-on-commit. NOTE: The [edit system archival] hierarchy is not available on QFabric systems."... | 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. | [
"Backing Up Configurations to an Archive Site"
] |
archive (All System Log Files) | archive <files number> <size size> <start-time time> <transfer-interval interval>
<binary-data | no-binary-data> <world-readable | no-world-readable>; | [edit system syslog file filename] | Configure archiving properties for all system log files. | [
{
"name": "files number",
"desc": "Maximum number of archived log files to retain. When the Junos OS logging utility has"
},
{
"name": "size size",
"desc": "Maximum amount of data that the Junos OS logging utility writes to a log file logfile before"
},
{
"name": "number of gigabytes",
... | 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. | [
"Specifying Log File Size, Number, and Archiving Properties"
] |
archive (Individual System Log File) | archive {
archive-sites site-name {
url <password password>;
}
(binary-data | no-binary-data);
files number;
size size;
start-time YYYY-MM-DD.hh:mm;
transfer-interval interval;
(no-world-readable | world-readable);
} | [edit system syslog file filename] | Configure archiving properties for a specific system log file. | [
{
"name": "archive-sites site-name",
"desc": "FTP URL representing the destination for the archived log file (for information"
},
{
"name": "url",
"desc": "Specify the primary and failover URLs to receive archive files."
},
{
"name": "password password",
"desc": "Password for authent... | 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.
start-time and transfer-interval statements introduced in Junos OS Release 8.5. | [
"Specifying Log File Size, Number, and Archiving Properties"
] |
archive (QFabric System) | archive {
size size;
} | [edit system syslog file filename] | Configure the archiving properties for the system message log file. | [
{
"name": "size size",
"desc": "Maximum amount of system log message data that the QFabric system stores in the log file. Syntax: xk to specify the number of kilobytes, xm for the number of megabytes, or xg for"
},
{
"name": "the number of gigabytes",
"desc": "Range: 65 KB through 1 GB"
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.3. | [] |
archive-sites (Event Policy) | archive-sites {
url <password password>;
} | [edit event-options destinations destination-name] | For a given destination name, configure archive sites to which an event policy can transfer files. To
archive files, you must reference the destination name in the event policy. If you specify more than one
archive site for a particular destination name, the device attempts to transfer to the first archive site in
the ... | [
{
"name": "url",
"desc": "The archive destination specified as a file URI, an active or passive FTP URI, a Secure FTP (SFTP) URI, or a Secure Copy (SCP) URI. Local device directories are also supported (for example, /var/tmp/)."
},
{
"name": "file:<//host>/path",
"desc": ""
},
{
"name": ... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Event Policy File Archiving"
] |
archive-sites (Flow Monitoring) | archive-sites {
ftp:url {
password "password";
username username;
}
} | [edit services flow-collector transfer-log-archive] | Specify the destination for transfer logs.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Transfer Logs"
] |
archive-sites | archive-sites site-name {
password password;
} | [edit accounting-options file filename] | Configure an archive site. If more than one site name is configured, an ordered list of archive sites for the
accounting-data log files is created. When a file is archived, the router or switch attempts to transfer the
file to the first URL in the list, moving to the next site only if the transfer does not succeed. The... | [
{
"name": "site-name",
"desc": "Any valid FTP/HTTP/SCP/SFTP URL to a destination."
},
{
"name": "password password",
"desc": "Password for logging into the archive site."
}
] | 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. | [
"Configuring Archive Sites for the Files"
] |
area | area area-id {
interface interface-name {
no-eligible-remote-backup;
passive;
topology (ipv4-multicast | name) {
disable;
}
}
virtual-link neighbor-id router-id transit-area area-id {
topology (ipv4-multicast | name) {
disable;
}
}... | [edit logical-systems logical-system-name protocols (ospf | ospf3)],
[edit logical-systems logical-system-name protocols ospf3 realm (ipv4-unicast | ipv4-multicast |
ipv6-multicast)],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(ospf | ospf3)],
[edit logical-systems log... | Specify the area identifier for this routing device to use when participating in OSPF routing. All routing
devices in an area must use the same area identifier to establish adjacencies.
Specify multiple area statements to configure the routing device as an area border router. An area border
router does not automaticall... | [
{
"name": "area-id",
"desc": "Area identifier. The identifier can be up to 32 bits. It is common to specify the area number as a"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for the realm statement introduced in Junos OS Release 9.2.
Support for the realm statement introduced in Junos OS Release 9.2 for EX Series switches.
Support for the no-eligible-remote-backup statement introduced in Junos OS Release 15.1. | [
"Understanding OSPF Areas",
"Understanding Multiple Address Families for OSPFv3"
] |
area-range | area-range network/mask-length <exact> <override-metric metric> <restrict>; | [edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id],
[edit logical-systems logical-system-name protocols (ospf | ospf3) area area-id nssa],
[edit logical-systems logical-system-name realm (ipv4-unicast | ipv4-multicast | ipv6-multicast)
area area-id],
[edit logical-systems logical-system-n... | (Area border routers only) For an area, summarize a range of IP addresses when sending summary link
advertisements (within an area). To summarize multiple ranges, include multiple area-range statements.
For a not-so-stubby area (NSSA), summarize a range of IP addresses when sending NSSA link-state
advertisements. The s... | [
{
"name": "exact",
"desc": "(Optional) Summarization of a route is advertised only when an exact match is made with the"
},
{
"name": "mask-length",
"desc": "Number of significant bits in the network mask."
},
{
"name": "network",
"desc": "IP address. You can specify one or more IP a... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for the realm statement introduced in Junos OS Release 9.2.
Support for the realm statement introduced in Junos OS Release 9.2 for EX Series switches. | [
"Example: Summarizing Ranges of Routes in OSPF Link-State Advertisements"
] |
arguments (Event Policy) | arguments {
argument-name argument-value;
} | [edit event-options policy policy-name then event-script filename] | Define the arguments that are passed to an event script when it is invoked from an event policy. | [
{
"name": "argument-name",
"desc": "Name of the argument."
},
{
"name": "argument-value",
"desc": "String specifying the value of the argument."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Configure an Event Policy to Pass Arguments to an Event Script",
"Execute Event Scripts in an Event Policy"
] |
arguments (Op Scripts) | arguments {
argument-name {
description descriptive-text;
}
} | [edit system scripts op file filename] | Define the expected command-line arguments for an op script. Once configured, the list of possible
arguments will be included in the context-sensitive help in the CLI. | [
{
"name": "argument-name",
"desc": "The name of a command-line argument to an op script. The remaining statement is explained separately. See CLI Explorer."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Declare and Use Command-Line Arguments in Op Scripts",
"Configure Help Text for Op Scripts"
] |
arp policer | policer name {
filter-specific;
logical-interface-policer;
physical-interface-policer;
if-exceeding {
(bandwidth-limit bits per second | bandwidth-percent percent);
burst-size-limit bytes;
then <discard> <forwarding-class forwarding-class> <loss-priority (high | low | med... | [edit firewall] | Apply a policer to an interface. Configure policer rate limits and actions. The traffic to the Routing
Engine is controlled by applying the policer on ARP. This prevents network congestion caused by
broadcast storms.
A policer applies two types of rate limits on traffic:
•
Bandwidth—The number of bits per second permit... | [
{
"name": "name",
"desc": "Policer name."
},
{
"name": "filter-specific",
"desc": "Policer is filter-specific."
},
{
"name": "logical-interface-policer",
"desc": "Policer is a logical interface policer."
},
{
"name": "physical-interface-policer",
"desc": "Policer is a phy... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R1. | [
"bandwidth-limit (Hierarchical Policer)",
"burst-size-limit (Hierarchical Policer)"
] |
arp | arp {
aging-timer minutes;
} | [edit system]
[edit interfaces interface-name unit logical-unit-number family inet address address]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet address address]
NOTE: The edit logical-systems hierarchy is not available on QFabric systems. | For Ethernet, Fast Ethernet, and Gigabit Ethernet interfaces only, configure Address Resolution Protocol
(ARP) table entries mapping IP addresses to MAC addresses. IPv4 networks use ARP to map IP network
addresses to physical (MAC) addresses. An address is resolved when the host device receives a proper
ARP reply in re... | [
{
"name": "aging-timer",
"desc": "Time interval in minutes between ARP updates. In environments where the number of ARP entries to update is high (for example, on routers only, metro Ethernet environments), increasing the time between updates can improve system performance. Range: 1 through 240"
},
{
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
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.0.
Statement introduced in Junos OS Release 11.1.
Statement introduced in Junos OS Release 14.1X53-D20.
arp-retries option introduced in Junos OS Evolved Release 22.1R1.
arp-retries option introduced in Junos OS Release 22.1R2. | [
"Configuring Static ARP Table Entries For Mapping IP Addresses to MAC Addresses",
"Configure ARP Learning and Aging Options",
"Adjusting the ARP Aging Timer"
] |
arp-detect | arp-detect milliseconds; | [edit forwarding-options next-hop] | Define the length of time (in milliseconds) for an SPU to wait for an acknowledgement from the Routing
Engine that an ARP request has been received from the SPU. If the Routing Engine fails to respond
within the specific time interval, the SPU considers that the Routing Engine CPU utilization is high at
that moment, an... | [
{
"name": "milliseconds",
"desc": "Number of seconds the SPU waits before receiving a response from Routing Engine."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X48-D65 and Junos OS Release 15.1X49-D130. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.