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 |
|---|---|---|---|---|---|---|---|
privacy-3des | privacy-3des {
(privacy-key privacy-key | privacy-password privacy-password);
} | [edit snmp v3 usm local-engine user username],
[edit snmp v3 usm remote-engine engine-id user username] | Configure the triple Data Encryption Standard (3DES) as the privacy type for the SNMPv3 user.
For privacy encryption, you can either enter a password in clear text, which is immediately encrypted, or,
if you already have the encrypted version (known as a key), enter the key directly.
The remaining statements are explai... | [] | 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. | [] |
privacy-aes128 | privacy-aes128 {
(privacy-key privacy-key | privacy-password privacy-password);
} | [edit snmp v3 usm local-engine user username],
[edit snmp v3 usm remote-engine engine-id user username] | Configure the Advanced Encryption Standard encryption algorithm (CFB128-AES-128 Privacy Protocol)
for the SNMPv3 user.
For privacy encryption, you can either enter a password in clear text, which is immediately encrypted, or,
if you already have the encrypted version (known as a key), enter the key directly.
The remain... | [] | 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. | [] |
privacy-key | privacy-key privacy-key; | [edit snmp v3 usm local-engine user username privacy-3des],
[edit snmp v3 usm local-engine user username privacy-aes128],
[edit snmp v3 usm local-engine user username privacy-des],
[edit snmp v3 usm remote-engine engine-id user username privacy-3des],
[edit snmp v3 usm remote-engine engine-id user username privacy-aes1... | Configure a privacy key for the SNMPv3 user, if you know it. The encrypted version of a password is
known as a key. | [
{
"name": "privacy-key",
"desc": "The encrypted version from the cleartext password. It is an alternative to entering a password."
}
] | 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. | [] |
privacy-none | privacy-none; | [edit snmp v3 usm local-engine user username],
[edit snmp v3 usm remote-engine engine-id user username] | Configure that no encryption be used for the SNMPv3 user. | [] | 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. | [] |
privacy-password | privacy-password privacy-password; | [edit snmp v3 usm local-engine user username privacy-3des],
[edit snmp v3 usm local-engine user username privacy-aes128],
[edit snmp v3 usm local-engine user username privacy-des],
[edit snmp v3 usm remote-engine engine-id user username privacy-3des],
[edit snmp v3 usm remote-engine engine-id user username privacy-aes1... | Configure a privacy password for the SNMPv3 user. | [
{
"name": "privacy-password",
"desc": "Password that a user enters. The password is then converted into a key that is used for"
}
] | 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. | [] |
private-vlan | private-vlan (isolated | community) vlan-id number; | [edit vlans vlan-name] | Configure a secondary VLAN ( either an isolated VLAN or a community VLAN) within a private VLAN
(PVLAN) and specify a VLAN ID for that secondary VLAN. This statement essentially converts a VLAN
into a PVLAN, by carving out discrete subdomains (secondary VLANs) within the primary VLAN. You
must specify a VLAN ID for eac... | [
{
"name": "isolated",
"desc": "The VLAN specified by vlan-name is defined as an isolated VLAN and a VLAN-ID is assigned"
},
{
"name": "community",
"desc": "The VLAN specified by vlan-name is defined as community VLAN and a VLAN-ID is"
}
] | system—To view this statement in the configuration.
system–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1X53-D10. | [
"Creating a Private VLAN on a Single Switch with ELS Support (CLI Procedure)",
"Creating a Private VLAN Spanning Multiple EX Series Switches with ELS Support (CLI Procedure)"
] |
proactive-arp-detection | proactive-arp-detection; | [edit system arp] | Enable proactive ARP detection to check the reachability of connected devices (within an IP subnet
range) on a specified interface. After enabling this statement, you can set the ARP configurations at the
interface level by the setting the: host-discovery address-range, ageing-time-out seconds, and discovery-time-
inte... | [] | admin | Statement introduced in Junos OS Release 18.3R1-S3, 18.3R2 and 19.3R1. | [] |
probe (ICMP Router Discovery) | probe <proxy-ip-address-or-hostname>
<by-address>
<by-index>
<by-name>
<by-remote-address>
<count>
<detail>
<inet>
<inet6>
<interface>
<interval>
<logical-system>
<routing-instance>
<source>
<tos>
<ttl>
<wait> | Query the status of the probed interface. | [
{
"name": "by-address",
"desc": "(Optional) Probe a local interface by address."
},
{
"name": "by-index",
"desc": "(Optional) Probe a local interface by index."
},
{
"name": "by-name",
"desc": "(Optional) Probe a local interface by name."
},
{
"name": "by-remote-address",
... | system-To view this statement in the configuration.
Output Fields
Table 1 lists the output fields for the probe command. The output fields are listed in the appropriate order
in which they appear.
Table 118: probe Output Fields
Field Name
Field Description
Level of Output
icmp-seq
ICMP sequence number of the proxy IP a... | Command introduced in Junos OS Release 20.3R1. | [
"How to Use the Probe Command"
] | |
probe | probe owner {
test test-name {
data-fill data;
data-size size;
delegate-probes probes;
destination-interface interface-name;
destination-port port;
dscp-code-point dscp-bits;
history-size size;
inet6-options source-address ipv6-address;
moving-... | [edit services rpm] | Specify an owner name. The owner name combined with the test name represent a single RPM
configuration instance. | [
{
"name": "owner",
"desc": "Owner name up to 32 characters in length."
}
] | system—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [] |
probe-count | probe-count count; | [edit services monitoring rpm owner name test name] | Specify the number of probes within a test. | [
{
"name": "count",
"desc": "1 through 15 for RPM, for TWAMP 1 through 4,294,967,290."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support at the [edit services rpm twamp client control-connection control-client-name] hierarchy level
introduced in Junos OS Release 15.1 for MX Series routers.
Statement introduced in Junos OS Evolved Release 20.1R1.
Support at the [edit protocols isis interface inter... | [
"Configuring BGP Neighbor Discovery Through RPM",
"Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, and MX Series",
"Routers",
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches"
] |
probe-interval | probe-interval interval; | [edit services monitoring rpm owner name test name] | Specify the time to wait between sending packets, in seconds. | [
{
"name": "interval",
"desc": "Number of seconds, from 1 through 255."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support at the [edit services rpm twamp client control-connection control-client-name] hierarchy level
introduced in Junos OS Release 15.1 for MX Series routers.
Statement introduced in Junos OS Evolved Release 20.1R1.
Support at the [edit protocols isis interface inte... | [
"Configuring BGP Neighbor Discovery Through RPM",
"Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, and MX Series",
"Routers",
"Configuring RPM Probes on M, MX and T Series Routers and EX Series Switches",
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
probe-limit | probe-limit limit; | [edit services rpm] | Configure the maximum number of concurrent probes allowed. | [
{
"name": "limit",
"desc": "Maximum number of concurrent probes allowed."
}
] | 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. | [
"Limiting the Number of Concurrent RPM Probes on M, MX, T and PTX Routers and EX Series",
"Switches"
] |
probe-server | [edit services monitoring rpm] | Enable the RPM server to act as a receiver for the probes, specified per protocol.
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a
linked statement in the Syntax section for details.
NOTE: The destination-interface statement is not supported on PTX Series routers or ... | [] | 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.
Junos OS Evolved Syntax and hierarchy level introduced in Junos OS Evolved Release 20.1R1.
tcp option introduced in Junos OS Evolved Release 23.4R1. | [
"Configuring RPM Receiver Servers"
] | |
probe-type | probe-type type; | [edit services monitoring rpm owner name test name] | Specify the packet and protocol contents of a probe. | [
{
"name": "type",
"desc": "One of the following probe type values:"
},
{
"name": "http-get",
"desc": "(Not available at the [edit services rpm bgp] hierarchy level for Junos OS.) Sends a Hypertext"
},
{
"name": "http-metadata-get",
"desc": "(Not available at the [edit services rpm bg... | 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 Evolved Release 20.1R1.
tcp-ping, http-get, and http-metadata-get probe types introduced in Junos OS Evolved Release 23.4R1. | [
"Understanding Using Probes for Real-Time Performance Monitoring on M, T, PTX, and MX Series",
"Routers",
"Configuring BGP Neighbor Discovery Through RPM"
] |
process (Memory) | process {
frequency (minutes | hours | days) value;
minor-event {
threshold process name memory-limit value ;
action snmp-trap;
}
major-event {
threshold process name memory-limit value ;
action [snmp-trap | live-core | (terminate-process| terminate-process-force)];
... | [edit system monitor memory] | Configure process level memory monitoring. you can specify user-configurable thresholds for monitoring
the Virtual Memory Size (VSZ) of processes. Events are categorized based on severity, depending on the
detected anomaly. The system classifies event severity as Minor, Major, or Critical.
The system uses an algorithm ... | [
{
"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"
] |
process-inform | process-inform {
pool pool-name;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server overrides],
[edit logical-systems logical-system-name routing-instances routing-instance-name system
services dhcp-local-server dhcpv6 overrides],
[edit logical-systems logical-system-name routing-insta... | Enable the processing of DHCP information request messages (DHCPINFORM for DHCPv4 and
INFORMATION-REQUEST for DHCPv6) sent from the client to request DHCP options. For DHCP local
servers, the messages are also passed to the configured server list.
The remaining statements are explained separately. Search for a statemen... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Enabling Processing of Client Information Requests",
"Overriding the Default DHCP Local Server Configuration Settings"
] |
process-monitor | process-monitor {
disable;
traceoptions {
file filename files number match regex size size (world-readable | no-world-readable);
flag flag;
level level;
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 process health monitor process."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [] |
process-non-null-as-null-register | process-non-null-as-null-register; | [edit protocols pim rp local] | When process-non-null-as-null-register is enabled on a PTX device serving as PIM Rendezvous Point (RP)
for multicast traffic, it allows the device to treat non-null registers, such as may be sent from any first
hop router (FHR), as null registers, and thus to form a register state with the device. This statement is
req... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 19.3R1. | [
"Configuring Local PIM RPs"
] |
processes | processes {
all-processes {
no-livecore-dump-on-crash;
}
process-name {
(enable | disable);
failover (alternate-media | other-routing-engine);
no-livecore-dump-on-crash;
timeout seconds;
traceoptions {
file <filename> <files files> <match expressio... | [edit system] | 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": "all-processes",
"desc": ""
},
{
"name": "option",
"desc": "(Junos OS Evolved only) Apply a configured setting to all processes that support that setting."
},
{
"name": "(enable | disable)",
"desc": "(Optional) Enable or disable a specified process."
},
{
"name": "f... | 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.
no-livecore-dump-on-crash option added in Junos OS Evolved Release 24.4R1. | [
"Disabling Junos OS Processes"
] |
product-model (Junos Fusion) | product-model model-name; | [edit policy-options satellite-policies candidate-uplink–port-policy policy-name term term-name
from],
[edit policy-options satellite-policies forwarding-policy policy-name term term-name from] | Define the satellite device product models that will use the candidate uplink port policy defined in the
from statement.
The other statements in the same from statement are applied to satellite devices that match the product-
model model-name definition. Those configuration statements are not applied to satellite devic... | [
{
"name": "model-name",
"desc": "Defines the satellite device product models that will use the candidate uplink port policy. It can be a complete device model name, to match that device model exactly. You can also use the wildcard character (*) in the match term to match zero or more of any character. Some ... | 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"
] |
product-name | product-name name; | [edit access diameter] | Configure the product name that is advertised in the Capabilities-Exchange-Request or Capabilities-
Exchange-Answer message. | [
{
"name": "name",
"desc": "Name of product that is the advertised value of the Product-Name AVP. Default: Juniper Diameter Client"
}
] | 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. | [] |
products | products {
values [product-value];
} | [edit security idp dynamic-attack-group dynamic-attack-group-name filters] | Specify a products filter to add attack objects based on the application that is vulnerable to the attack. | [
{
"name": "values",
"desc": "Name of the products filter. You can configure multiple filters separated by spaces and enclosed"
}
] | 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. | [] |
profile (Access) | profile profile-name {
accounting {
accounting-stop-on-access-deny;
accounting-stop-on-failure;
duplication;
duplication-attribute-format;
duplication-filter;
duplication-vrf;
order [accounting-method];
statistics (time | volume-time);
}
addr... | [edit access] | Create a profile containing a set of attributes that define device management access. | [
{
"name": "name",
"desc": "Profile name"
},
{
"name": "accounting",
"desc": "Specifies the accounting options"
},
{
"name": "address-assignment",
"desc": "Specify the address assignment pool"
},
{
"name": "authentication-order",
"desc": "Order in which authentication mech... | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
inet6-pool option is introduced in Junos OS Release 20.3R1.
none option is introduced in Junos OS Release 20.3R1. | [
"Understanding Interfaces",
"Understanding User Authentication for Security Devices",
"Ethernet Switching and Layer 2 Transparent Mode Overview"
] |
profile (Application Firewall) | profile profile-name {
block-message {
type {
custom-redirect-url {
content content;
}
custom-text {
content content;
}
}
}
} | [edit security application-firewall] | Define the profile of the response to be issued when an application firewall rule set blocks HTTP or
HTTPS traffic with a deny or reject action.
Although drop and reject actions are logged, application firewall does not notify users when either
action is taken. To provide an explanation for the action or to redirect t... | [
{
"name": "name",
"desc": "Profile name."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10. | [
"Application Firewall Overview"
] |
profile (Application Identification) | profile profile-name {
rule-set rule-set-name;
} | [edit services application-identification] | Define members of the application profile, which consists of one or more rule sets. | [
{
"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 9.5.
Support added in Junos OS release 19.3R2 and 19.4R1 for Next Gen Services on MX240, MX480, and
MX960. | [
"Configuring Application Profiles"
] |
profile (Captive Portal Content Delivery) | profile name
cpcd-rule-sets rule-set-name;
cpcd-rules rule-name;
dynamic;
http-redirect-options url;
ipda-rewrite-options {
destination-address destination-address;
destination-port destination-port;
}
} | [edit services captive-portal-content-delivery] | Configure the service profile for HTTP redirect services, also known as Captive Portal and Content
Delivery (CPCD) services. The profile contains rules or rule sets that specify the details of the service.
The CPCD service profile is included in a service set that applies the service to a service interface. This
statem... | [
{
"name": "cpcd-rule-sets rule-set-name",
"desc": "Specify a list of sets of service rules."
},
{
"name": "cpcd-rules rule-name",
"desc": "Specify a service rule."
},
{
"name": "dynamic",
"desc": "Indicate that the service is a dynamic, converged service."
},
{
"name": "http-... | services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
Support for Next Gen Services introduced in Junos OS Release 19.3R2. | [
"HTTP Redirect Service Overview",
"Configuring MS-MPC-Based or MX-SPC3-Based Static HTTP Redirect Services",
"Configuring MS-MPC-Based or MX-SPC3-Based Converged HTTP Redirect Services",
"Configuring Routing Engine-Based, Static HTTP Redirect Services",
"Configuring Routing Engine-Based, Converged HTTP Redi... |
profile (Explicit Proxy) | profile name {
default-policy(deny-all | permit-all);
policy name {
description description;
match {
destination-address;
destination-address-excluded;
destination-identity-feed [ destination-identity-feed ... ];
dynamic-application;
application;
source-address;
so... | [edit logical-systems name tenants name security policies explicit-proxy],
[edit security policies explicit-proxy],
[edit tenants name security policies explicit-proxy] | Define a explicit proxy profile policy context.
The SRX Series Firewall applies security enforcement based on the rules created in the explicit web
proxy profile policy. | [
{
"name": "name",
"desc": "Explicit proxy profile name"
},
{
"name": "default-policy",
"desc": "Default policy action when no policy matches in rulebase."
},
{
"name": "deny-all",
"desc": "Deny all traffic if no policy match"
},
{
"name": "permit-all",
"desc": "Permit all... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.4R1. | [] |
profile (HTTP Header Enrichment) | profile profile-name {
tag rule rule-name;
} | [edit services hcm] | Configure an HCM profile, which points to one or more tag rules that Junos OS uses to enrich HTTP
headers with the appropriate tags. You can configure a maximum of 100 HCM profiles.
For subscriber traffic under static policy control, a tag rule is used if it is included in the HCM profile
specified in a PCC rule that t... | [
{
"name": "profile-name",
"desc": "Name of the HCM profile. 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",
"Configuring HCM Profiles and Assigning Tag Rules"
] |
profile (icap-redirect) | profile name {
fallback-option {
connectivity (block | log-permit | permit);
default-action (block | log-permit | permit);
timeout (block | log-permit | permit);
}
http {
redirect-request redirect-request;
redirect-response redirect-response;
}
server name { ... | [edit services] | Configure the ICAP redirect profile.
The ICAP server profile allows the ICAP server to process request messages, response messages,
fallback options, and so on, for the permitted traffic.
When you configure an ICAP redirect service on SRX Series Firewalls, you must configure the ICAP
redirect profile. The ICAP redirect... | [
{
"name": "profile name",
"desc": "ICAP redirect profile name."
},
{
"name": "fallback-option",
"desc": "Fallback options to specify the actions the device applies if the ICAP server is unavailable."
},
{
"name": "http",
"desc": "Redirect request and redirect response for HTTP traffi... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.1 R1. | [
"ICAP Service Redirect"
] |
profile (Juniper Secure Connect) | profile realm-name {
access-profile access-profile;
client-config client-config;
compliance {
pre-logon compliance-rule;
}
description description;
ipsec-vpn ipsec-vpn;
options {
multi-access;
user-domain user-domain;
}
} | [edit security remote-access] | Configure remote user connection profiles for the Juniper Secure Connect clients.
The remote access profiles allow you to deploy connection settings for the remote users by pushing the
configuration file on the client devices. You can create multiple profiles and set one of the profiles as the
default profile.
NOTE: S... | [
{
"name": "realm-name",
"desc": "Set realm-name as remote-access profile name. This is the profile identifier in FQDN/ RealmName format. Examples: ra.example.com/hr, if FQDN is ra.example.com and Realm name is hr. ra.example.com/engineering, if FQDN is ra.example.com and Realm name is engineering. ra.exampl... | security | Statement introduced in Junos OS Release 20.3R1.
compliance option added in Junos OS Release 23.1R1.
Realms format changed to FQDN/RealmName or FQDN in Junos OS Release 23.1R1.
user-domain option added in Junos OS Release 24.4R1. | [
"Juniper Secure Connect Administrator Guide"
] |
profile (LRF) | profile profile-name {
collector collector-name {
destination {
address collector-address;
port collector-port-number;
}
source-address source-address;
}
http-log-multiple-transactions;
policy-based-logging;
rule lrf-rule-name {
then {
... | [edit services lrf] | Configure an LRF profile to specify a set of logging and reporting parameters, which includes data
templates, collectors, and LRF rules.
For Junos OS Subscriber Aware, you can then assign an LRF profile to a subscriber by assigning the
profile to the TDF service set associated with the subscriber’s TDF domain.
For Juno... | [
{
"name": "profile-name",
"desc": "Name of the LRF profile. Range: Up to 63 characters. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
vendor-support option introduced in Junos OS Release 17.2.
Support for Next Gen Services introduced in Junos OS Release 19.3R1 on MX Series. | [
"Configuring Logging and Reporting for Junos OS Subscriber Aware",
"Configuring an LRF Profile for Subscribers",
"Configuring Logging and Reporting for Subscriber Management",
"Logging and Reporting Function for Subscribers"
] |
profile (Rule Sets) | profile profile-name; | [edit security application-firewall rule-sets rule-set-name] | Specifies the profile of the block message to be used for any deny or reject action in the rule set that
specifies the block-message option.
The block-message option enables you to provide an explanation for the action or to redirect the client
to an informative webpage. You can configure the block-message in set secu... | [
{
"name": "profile-name",
"desc": "Name of the block-message profile to be used for this rule set."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10. | [
"Application Firewall Overview"
] |
profile (Security Antispam SBL) | profile profile-name {
custom-tag-string [string];
(sbl-default-server | no-sbl-default-server);
spam-action (block | tag-header | tag-subject);
} | [edit security utm default-configuration]
[edit security utm feature-profile anti-spam sbl] | Create a profile for the antispam sbl feature. This profile includes all subsequent configuration options. | [] | 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. | [] |
profile (Security Antivirus Juniper Express Engine) | profile profile-name {
fallback-options {
content-size (block | log-and-permit);
default (block | log-and-permit);
engine-not-ready (block | log-and-permit);
out-of-resources (block | (log-and-permit);
timeout (block | log-and-permit);
too-many-requests (block | log-... | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine] | Create a profile for the Juniper express engine. This profile includes all subsequent configuration
options. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The express engine feature is not supported from Junos OS Release 15.1X49-D10 onwards. For
previous releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Express Antivirus Configuration Overview"
] |
profile (Security Antivirus Kaspersky Lab Engine) | profile profile-name {
fallback-options {
content-size (block | log-and-permit);
corrupt-file (block | log-and-permit);
decompress-layer (block | log-and-permit);
default (block | log-and-permit);
engine-not-ready (block | log-and-permit);
out-of-resources (block | (... | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus kaspersky-lab-engine] | Create a profile for the Kaspersky Lab engine. This profile includes all subsequent configuration options. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Kaspersky feature is not supported from Junos OS Release 15.1X49-D10 onwards. For previous
releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
profile (Security Content Filtering) | profile profile-name {
block-command protocol-command-list;
block-content-type (activex | exe | http-cookie | java-applet | zip);
block-extension extension-list;
block-mime {
exception list-name;
list list-name;
}
notification-options {
custom-message message;
(n... | [edit security utm default-configuration]
[edit security utm feature-profile content-filtering] | Create a profile for the content-filtering feature. This profile includes all subsequent configuration
options. | [] | 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. | [
"Content Filtering Overview"
] |
profile (Security GTP) | profile profile_name {
apn pattern-string {
imsi-prefix imsi-prefix-digits {
action {
drop;
pass;
selection {
ms;
net;
vrf;
}
}
}
}
drop {
... | [edit security gtp] | Use the profile option to create a profile for the GPRS tunneling protocol (GTP) feature. This profile
includes all subsequent configuration options.
From Junos OS Release 20.4R1 onwards, the [edit security gprs gtp] hierarchy level is replaced by [edit
security gtp]. | [
{
"name": "<NI>: for example internet, internet.public",
"desc": "<NI>.<OI>: for example internet.mnc005.mcc244.gprs, internet.public.mnc005.mcc244.gprs APN string configuration supports wild card “*” in place of OI. You can specify APN as <NI>.”*” and configure the matching APN string. You don’t need to sp... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. The restart-path option added in Junos OS Release 11.4.
New GPRS tunneling protocol (GTP) message types added in Junos OS Release 11.4. Support for GTPv2
added in Junos OS Release 11.4. Statement modified in Junos OS Release 15.1X49-D40.The must-ie-v1,
must-ie-v2, remove-i... | [
"Understanding GTP Path Restart",
"Understanding GTPv2 Tunnel Cleanup",
"GTPv1 Message Filtering"
] |
profile (Security SCTP) | profile profile-name {
association-timeout association-timeout;
drop (Security SCTP) {
m3ua-service name;
payload-protocol name;
}
handshake-timeout handshake-timeout;
limit (Security SCTP) {
address name {
payload-protocol (asap | bicc | ddp-segment | ddp-stream ... | [edit security sctp] | Use the profile option to create a profile of the Stream Control Transmission Protocol (SCTP) feature.
This profile includes all subsequent configuration options.
From Junos OS Release 20.4R1 onwards, the [edit security gprs sctp] hierarchy level is replaced by [edit
security sctp]. | [
{
"name": "name",
"desc": "Specify SCTP configuration name."
},
{
"name": "nat-only",
"desc": "Specify only do payload IPs translation for SCTP packet."
}
] | 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 the nat-only option added in Junos OS
Release 12.1X45-D10. Support for the permit option is added in Junos OS Release 12.1X46-D10. | [
"Understanding Stream Control Transmission Protocol",
"Understanding SCTP Multichunk Inspection"
] |
profile (Security Sophos Engine Antivirus) | profile <name> {
fallback-options {
content-size (block | log-and-permit | permit);
default (block | log-and-permit | permit);
engine-not-ready (block | log-and-permit | permit);
out-of-resources (block | log-and-permit | permit);
timeout (block | log-and-permit | permit);
... | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus sophos-engine] | Create a profile for the Sophos antivirus engine. This profile includes all subsequent configuration
options. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Sophos Antivirus Configuration Overview"
] |
profile (Security Web Filtering Juniper Enhanced) | profile profile-name {
category customurl-list name {
action (block | log-and-permit | permit | quarantine);
}
custom-block-message value;
custom-quarantine-message value;
default (block | log-and-permit | permit | quarantine);
fallback-settings {
default (block | log-and-per... | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering juniper-enhanced] | Create a profile for the juniper-enhanced feature. This profile includes all subsequent configuration
options. | [] | 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 security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Monitoring Web Filtering Configurations"
] |
profile (Security Web Filtering Juniper Local) | profile profile-name {
custom-block-message value;
default (block | log-and-permit | permit);
fallback-settings {
default (block | log-and-permit);
server-connectivity (block | log-and-permit);
timeout (block | log-and-permit);
too-many-requests (block | log-and-permit);
... | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering juniper-local] | Create a profile for the web-filtering juniper–local feature. This profile includes all subsequent
configuration options. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Monitoring Web Filtering Configurations",
"Example: Configuring Local Web Filtering"
] |
profile (Security Web Filtering Surf Control Integrated) | profile profile-name {
category customurl-list name {
action (block | log-and-permit | permit);
}
custom-block-message value;
default (block | log-and-permit | permit);
fallback-settings {
default (block | log-and-permit);
server-connectivity (block | log-and-permit);
... | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering surf-control-integrated] | Create a profile for the web-filtering surf-control-integrated feature. This profile includes all subsequent
configuration options. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Surf-Control feature is not supported from Junos OS Release 15.1x49-D10 onwards. For previous
releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Monitoring Web Filtering Configurations"
] |
profile (Security Web Filtering Websense Redirect) | profile profile-name {
account value;
custom-block-message value;
fallback-settings {
default (block | log-and-permit);
server-connectivity (block | log-and-permit);
timeout (block | log-and-permit);
too-many-requests (block | log-and-permit);
}
server {
... | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering websense-redirect] | Create a profile for the web-filtering web-sense feature. This profile includes all subsequent
configuration options. | [] | 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. | [
"Monitoring Web Filtering Configurations"
] |
profile (security) | profile name {
category {
aamw {
field-extra-name name;
field-namename;
}
antispam {
field-extra-name name;
field-namename;
}
antivirus {
field-extra-name name;
field-namename;
}
apptrack {
field-extra-name name;
field-namename;
}
content-filter {
field-extra-name name;
field-namename;
}
idp {
field-extra-name name;
f... | [edit security log] | Configure the security log profile to define the policy related log format including fields selection and
fields order for the log. You can apply the log profile to a policy to get the log in a predefined format.
Configure the stream and the log server to send the logs to the destination before configuring the
profile.... | [
{
"name": "category",
"desc": "Selects the category of events for the profile"
},
{
"name": "stream-name",
"desc": "Specify the destination to send the log. One log profile can point to multiple streams. Different log profiles can point to the same stream. You need to configure the stream mode f... | Configuration statement profile is added in Junos OS Release 21.1R1. | [] | |
profile (Services Application Identification) | profile app-id-profile-name; | [edit services application-identification] | Configure an application identification profile. This profile is a placeholder profile with no configuration
options, but it must be created 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"
] |
profile (Services PCEF) | profile pcef-profile-name; | [edit services pcef] | Configure a policy and charging enforcement function (PCEF) profile that is a placeholder profile with no
configuration options. This profile must be created to enable PCEF functionality on the services plane.
You apply this placeholder profile to the subscriber-aware service set. | [
{
"name": "pcef-profile-name",
"desc": "Name of the PCEF 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"
] |
profile (Services Proxy) | profile (Services Proxy) name {
protocol {
http {
host host;
password password;
port port;
username username;
}
}
} | [edit services proxy] | Define proxy profiles that enable the system to route outbound HTTP or HTTPS traffic through a proxy
server. This configuration is useful in environments where direct internet access is restricted or
monitored, and proxy authentication is required.
Each proxy profile can include one or more protocol-specific configurat... | [
{
"name": "name",
"desc": "Proxy profile name."
},
{
"name": "protocol",
"desc": "Protocol type for the profile. Support is available for only HTTP connections. See protocol (Services Proxy)."
}
] | system | Statement introduced in Junos OS Release 18.3R1. | [
"Predefined Application Signatures for Application Identification"
] |
profile (Services SSL Proxy) | profile name {
actions {
allow-strong-certificate;
crl {
disable;
if-not-present (allow | drop);
ignore-hold-instruction-code;
}
disable-session-resumption;
ignore-server-auth-failure;
log {
all;
errors;
... | [edit services ssl proxy],
[edit logical-systems logical-system-name services ssl proxy] | Specify the SSL server profile. An SSL proxy profile defines SSL behavior for the SRX Series Firewall.
The SSL proxy profile will be applied to the security policy as application services.
We have updated the limits for trusted CA certificates, server certificates, and URL categories in both
SSL forward proxy and SSL r... | [
{
"name": "profile-name",
"desc": "Profile identifier."
},
{
"name": "actions",
"desc": "Logging and traffic related actions."
},
{
"name": "custom-ciphers",
"desc": "Custom cipher list. Values:"
},
{
"name": "ecdhe-rsa-with-3des-ede-cbc-sha",
"desc": "ECDHE/RSA, 3DES ED... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10.
The crl statement is supported from 15.1X49-D30.
The logical system option is introduced in Junos OS Release 19.1R1. | [
"SSL Proxy Overview",
"Configuring SSL Forward Proxy",
"Enabling Debugging and Tracing for SSL Proxy"
] |
profile (SSL Initiation) | profile profile-name {
actions {
crl {
disable disable;
if-not-present (allow | drop);
ignore-hold-instruction-code ignore-hold-instruction-code;
}
ignore-server-auth-failure ignore-server-auth-failure;
}
client-certificate client-certificate;
... | [edit services ssl initiation] | Specify the name of the profile for SSL initiation support service.
SSL initiation is a process where the SRX Series Firewall acts as in SSL proxy client, initiates the SSL
sessions with an SSL server. The SRX Series Firewall receives clear text from an HTTP client. It encrypts
and transmits the data as ciphertext to t... | [
{
"name": "actions",
"desc": "Specify the certification revocation checks and traffic related actions for configuring SSL initiation support service."
},
{
"name": "crl",
"desc": "Specify certificate revocation actions. The certificate revocation list (CRL) contains the list of digital certifica... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. The protocol-version statement is updated to
include tls11 and tls12 from Junos OS Release 15.1X49-D30. | [
"Configuring SSL Forward Proxy"
] |
profile (SSL Termination) | profile name {
custom-ciphers;
enable-flow-tracing enable-flow-tracing;
enable-session-cache enable-session-cache;
preferred-ciphers (custom | medium | strong | weak);
protocol-version (all | ssl3 | tls1 | tls11 | tls12);
server-certificate server-certificate;
trusted-ca ... | [edit services ssl termination] | Specify the name of the profile for SSL termination support service.
Traffic from the client to SRX Series is encrypted and terminated at SRX Series, which then re-encrypts
traffic to the back-end server.
SSL termination is a process where the SRX Series Firewall acts as an SSL proxy server, terminates the
SSL session... | [
{
"name": "custom-ciphers",
"desc": "Configure custom cipher for an SSL profile. Custom ciphers allow you to define your own cipher list. If you do not want to use one of the three categories (strong, medium, or week) of preferred ciphers, you can select ciphers from each of the categories to form a custom ... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. The protocol-version statement is updated to
include tls11 and tls12 from Junos OS Release 15.1X49-D30. | [
"Configuring SSL Forward Proxy",
"Firewall User Authentication Overview"
] |
profile (Subscriber Access) | profile profile-name {
accounting {
address-change-immediate-update
accounting-stop-on-access-deny;
accounting-stop-on-failure;
ancp-speed-change-immediate-update;
coa-immediate-update;
coa-no-override service-class-attribute;
duplication;
duplication... | [edit access] | Configure a subscriber access profile that includes subscriber access, L2TP, or PPP properties. | [
{
"name": "profile-name",
"desc": "Name of the profile."
}
] | 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. | [
"Point-to-Point Protocol (PPP)",
"Layer 2 Tunneling Protocol (L2TP)",
"L2TP LNS Inline Service Interfaces",
"Configuring the PPP Challenge Handshake Authentication Protocol",
"Configuring the PPP Password Authentication Protocol",
"JSRC for Subscriber Provisioning and Accounting",
"Configuring Service A... |
profile (Traffic Load Balancer) | profile profile-name {
custom {
cmd priority {
default-real-service-status (down | up);
expect (ascii | binary) receive-string;
port port;
real-service-action (down | up);
send (ascii | binary) send-string;
}
protocol (tcp | udp);
... | [edit services network-monitoring] | Configure a monitoring profile that can be used for health-checking a group of TLB servers. | [
{
"name": "custom",
"desc": "Use custom probes for server health checking."
},
{
"name": "cmd priority",
"desc": "Use the specified command priority to send for a custom probe. Values: 1 or 2"
},
{
"name": "default-real-service-status (down | up)",
"desc": "Assign a server status fo... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Traffic Load Balancer Overview",
"Configuring TLB"
] |
profile (Web Filter) | profile profile-name {
dns-filter {
database-file filename;
dns-resp-ttl seconds;
dns-server [ ip-address ];
hash-key key-string;
hash-method hash-method-name;
statistics-log-timer minutes;
wildcarding-level level;
}
dns-filter-template template-name {
client-interfaces [ client-interfac... | [edit services web-filter]
Hierarchy Level (before Junos OS Release 18.3R1)
[edit services url-filter] | Define URL filter profile or DNS filter profile.
A URL filter profile is for filtering access to disallowed URLs. A URL filter profile includes a general
database setting and templates. The template settings apply to specific interfaces or to access from
specific source IP address prefixes, and override the database se... | [
{
"name": "profile-name",
"desc": "Name of the filter profile."
},
{
"name": "url-filter-database filename",
"desc": "Specify the filename of the URL filter database. This option is mandatory."
}
] | 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.
dns-filter, dns-filter-templates, global-dns-stats-log-timer, and url-filter-template options introduced in Junos
OS Release 18.3R1.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"DNS Request Filtering for Disallowed Website Domains",
"Configuring URL Filtering"
] |
profile | profile profile-name {
accounting {
accounting-stop-on-access-deny;
accounting-stop-on-failure;
order (radius | [ accounting-order-data-list ];
}
authentication-order [authentication-method];
radius {
(accounting-server [server-addresses] | accounting-server-... | [edit access] | Configure an access profile that specifies authentication and accounting parameters. Authentication and
accounting parameters run only if you specify the profile name. The access profile contains the entire
authentication, authorization, and accounting (AAA) configuration that aids in handling AAA requests,
including t... | [
{
"name": "profile-name",
"desc": "Profile name of up to 32 characters. NOTE: The [edit access] 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 in Junos OS Release 9.0. | [
"Example: Connecting a RADIUS Server for 802.1X to an EX Series Switch",
"Configuring 802.1X RADIUS Accounting (CLI Procedure)"
] |
profile(dynamic-application) | profile name {
redirect-message {
type {
custom-text {
content content;
}
redirect-url {
content content;
}
}
}
} | [edit security dynamic-application] | Define a profile to provide an explanation for the policy action or to redirect the client request to an
informative webpage when a policy blocks HTTP or HTTPS traffic with a deny or reject action in a
security policy.
Although drop and reject actions can be logged, the users might not be notified when either action is... | [
{
"name": "name",
"desc": "Name of the profile. Values:"
},
{
"name": "redirect-message",
"desc": "Defines the profile of the notification sent to clients when HTTP or HTTPS traffic is blocked by a reject or deny action from an application firewall."
},
{
"name": "type",
"desc": "Th... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Unified Security Policies"
] |
profile-sharing | profile-sharing {
except {
as-path-length as-path-length
policy policy;
}
} | [edit logical-systems name protocols bgp global-load-balancing],
[edit logical-systems name routing-instances name protocols bgp global-load-balancing],
[edit protocols bgp global-load-balancing],
[edit routing-instances name protocols bgp global-load-balancing], | Allow profiles with disjoint paths to share the same HW profile. GLB profile sharing is disabled by
default. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.4R1. | [] |
profile-type (Dynamic Service Profiles) | profile-type remote-device-service; | [edit dynamic-profiles profile-name] | Specify that the dynamic service profile containing this statement is not applied locally to the router.
Instead, it is applied to an external device by means of the remote device services manager daemon
(rdmd). It enables an external authority, such as PCRF to reference the dynamic service profile to
provision or depr... | [
{
"name": "remote-device-service",
"desc": "Service profile type that causes the profile to be applied to an external device by means of the remote device services manager daemon (rdmd)."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1. | [
"Configuring Remote Device Management for Service Provisioning",
"Remote Device Services Manager (RDSM) Overview"
] |
profile-type (PTP) | profile-type (aes67 | aes67-smpte | enterprise-profile | g.8275.2.enh | smpte) | [edit protocols ptp] | On the MX Series, configure the G.8275.1 or the enhanced G.8275.1 PTP profile for applications that
require accurate phase and time synchronization. This profile supports the architecture defined in ITU-T
G.8275 to enable the distribution of phase and time with full timing support and is based on the second
version of ... | [
{
"name": "aes67",
"desc": "(QFX Series only) Enable the AES67 PTP profile."
},
{
"name": "aes67-smpte",
"desc": ""
},
{
"name": "(QFX Series only) Enable the AES67+SMPTE PTP",
"desc": "profile."
},
{
"name": "enterprise-profile",
"desc": "(QFX Series only) Enable the ent... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1R1.
PTP profile-type options added to QFX5130-48C devices in Junos OS Evolved Release 24.2R1 | [
"Precision Time Protocol Overview",
"Configuring the Precision Time Protocol Enterprise Profile",
"Configuring the Precision Time Protocol G.8275.2 Enhanced Profile (Telecom Profile)"
] |
profile-variable-set (Dynamic Profiles) | profile-variable-set {
variable-set-name {
junos-layer2-output-policer policer-name;
}
} | [edit dynamic-profiles profile-name] | Specify the policer used in the variable set. | [
{
"name": "junos-layer2-output-policer policer-name",
"desc": "Layer 2 policer that you want to substitute in the dynamic"
}
] | 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. | [
"Applying the Policers to Dynamic Profile Interfaces",
"Creating a Dynamic Profile for the Complex Configuration"
] |
profile-variable-set (Routing Instances) | profile-variable-set variable-set-name | [edit routing-instances routing-instance-name protocols vpls associate-profile] | Specify the variable set to apply to the dynamic profile for the routing instance. | [
{
"name": "variable-set-name",
"desc": "Name of the variable set to use when this dynamic profile is applied to the routing"
}
] | 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. | [
"Attaching Dynamic Profiles to Routing Instances for the Complex Configuration"
] |
profilerd | profilerd {
command binary-file-path;
disable;
failover (alternate-media | other-routing-engine);
} | [edit system processes] | Specify the profiler process. | [
{
"name": "command binary-file-path",
"desc": "Path to binary for process."
},
{
"name": "disable",
"desc": "Disable the profiler process."
},
{
"name": "failover",
"desc": "Configure the device to reboot if the software process fails four times within 30 seconds,"
},
{
"name... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [] |
profiles (AAA) | profiles aaa-profile-name {
radius {
accounting {
network-element network-element-name;
}
authentication {
network-element network-element-name;
}
policy {
activation-attribute {
<code numeric-code;>
<vendor-... | [edit unified-edge aaa] | Configure a profile of the policy control attributes for RADIUS servers. This profile is used by the policy
and charging enforcement function (PCEF) profile. | [
{
"name": "aaa-profile-name",
"desc": "Name of the AAA profile."
}
] | 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. | [
"Configuring an AAA Profile",
"Understanding AAA Profiles",
"Understanding How a RADIUS Server Controls Policy and Charging Control Rules"
] |
profiles (PCEF) | profiles profile-name {
aaa-policy-control {
aaa-profile aaa-profile-name;
pcc-rulebases [rulebase-name <time-of-day-profile profile-name>];
user-password password;
}
dynamic-policy-control {
pcc-rules {
[rule-name precedence number <time-of-day-profile profile-n... | [edit unified-edge pcef],
[edit services pcef] | Set up the overall policy and charging enforcement function (PCEF) configuration that can be applied to
subscribers.
NOTE: You can configure only one of the following statements in a PCEF profile: aaa-
policy-control, static-policy-control, or dynamic-policy-control.
You can configure a maximum of 32 policy and chargi... | [
{
"name": "profile-name",
"desc": "Name of the PCEF profile. Range: 1 through 63 characters. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | 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] hierarchy level introduced for Junos OS Broadband Subscriber
Management in Junos OS Release 17.2 on MX Series. | [
"Configuring a Policy and Charging Enforcement Function Profile for Junos OS Subscriber Aware",
"Dynamic Policies",
"Configuring a Policy and Charging Enforcement Function Profile for Junos OS Subscriber Aware",
"Static Policies",
"Configuring a Policy and Charging Enforcement Function Profile for Junos OS ... |
profiles (RFC 2544 Benchmarking) | profiles {
test-profile profile-name {
test-type (throughput | latency | frame-loss | back-back-frames);
packet-size bytes;
step-percent percent;
bandwidth-kbps kpbs;
}
} | [edit services rpm rfc2544-benchmarking] | Configure the test profile to specify attributes, such as the period for the test and the type of test to be
performed, for the RFC 2544-based benchmarking test. The test profile is referenced in the test
interface to perform a specific type of benchmarking test and compute statistics to describe the
performance charac... | [
{
"name": "profiles",
"desc": "Define the test profile for the RFC 2544-based benchmarking test to examine and analyze the performance characteristics of a network interconnecting device."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3X53. | [
"RFC 2544-Based Benchmarking Tests Overview",
"Configuring RFC 2544-Based Benchmarking Tests"
] |
profiles | profiles {
profile-name {
sip-user-id simple-ip-user-id;
sip-password simple-ip-password;
access-point-name apn;
authentication-method (pap | chap | none);
}
} | [edit interfaces interface-name cellular-options gsm-options] | Configure a profile to establish a data call with a Global System for Mobile Communications (GSM)
cellular network. You can configure up to 16 profiles. | [
{
"name": "profile-name",
"desc": "Name of the profile."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Understanding Ethernet Interfaces"
] |
programmable-rpd | programmable-rpd {
client name {
interface-notification name;
}
purge-timeout (never | timeout);
rib-service {
dynamic-next-hop-interface (disable);
}
stats-aggregation-interval seconds;
stats-sampling-interval seconds;
traceoptions {
file filename <files files> <size size> <(world-readable | no-world-re... | [edit logical-systems name routing-options],
[edit routing-options] | 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... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2.
stats-aggregation-interval and stats-sampling-interval statements introduced in Junos OS Evolved Release
22.2R1. | [] |
promiscuous | promiscuous; | [edit vlans vlan-name interfaces interface-name] | Configure an access or trunk port to be promiscuous. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Creating a Private VLAN on a Single QFX Switch without ELS Support",
"Creating a Private VLAN Spanning Multiple QFX Series Switches without ELS Support"
] |
promiscuous-mode (Dynamic IGMP Interface) | promiscuous-mode; | [edit dynamic-profiles profile-name protocols igmp interface interface-name] | Specify that the interface accepts IGMP reports from hosts on any subnetwork. When you enable
promiscuous mode, all routing devices on the Ethernet segment must be configured for promiscuous
mode. Otherwise, only the interface configured with lowest IPv4 address acts as the querier for IGMP
for this Ethernet segment. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Dynamic IGMP Configuration Overview",
"Configuring Dynamic DHCP Client Access to a Multicast Network",
"Accepting IGMP Messages from Remote Subnetworks"
] |
promiscuous-mode (Interfaces) | promiscuous-mode; | [edit interfaces interface-name ] | Enable promiscuous mode on Layer 3 Ethernet interfaces. When promiscuous mode is enabled on an
interface, all packets received on the interface are sent to the central point or Services Processing Unit
regardless of the destination MAC address of the packet.
You can also enable promiscuous mode on chassis cluster redun... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Enabling and Disabling Promiscuous Mode on Ethernet Interfaces (CLI Procedure)"
] |
promiscuous-mode (Protocols IGMP) | promiscuous-mode; | [edit logical-systems logical-system-name protocols igmp interface interface-name],
[edit protocols igmp interface interface-name] | Specify that the interface accepts IGMP reports from hosts on any subnetwork. Note that when
enabling promiscuous-mode, all routing devices on the ethernet segment must be configured with the
promiscuous mode statement. Otherwise, only the interface configured with lowest IPv4 address acts as
the querier for IGMP for t... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Accepting IGMP Messages from Remote Subnetworks"
] |
promote | Syntax for promote gre-key
promote gre-key;
Syntax for promote dscp
promote dscp;
Syntax for promote traffic-class
promote traffic-class; | [edit firewall family family-name filter filter-name] | Use the promote gre-key or promote dscp configuration statements to use gre-key or dscp match conditions in
an inet firewall filter. Use the promote traffic-class configuration statement to use the traffic-class match
condition in an inet6 firewall filter.
NOTE: When you apply any of these configuration statements, the... | [
{
"name": "gre-key",
"desc": ""
},
{
"name": "dscp",
"desc": ""
},
{
"name": "traffic-class",
"desc": ""
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1F3 and 16.1R2. | [
"Guidelines for Configuring Firewall Filters",
"Guidelines for Applying Standard Firewall Filters",
"Firewall Filter Match Conditions for IPv4 Traffic"
] |
propagate-settings | propagate-settings interface-name; | [edit system services dhcp]
[edit system services dhcp pool] | Enable or disable the propagation of TCP/IP settings received on the device acting as Dynamic Host
Configuration Protocol (DHCP) client. The settings can be propagated to the server pool running on the
device. Use the system services dhcp to set this feature globally. Use the system services dhcp pool to set the
featur... | [
{
"name": "logical-interface-name",
"desc": "Name of the logical interface to receive TCP/IP settings from the external"
}
] | system—To view this in the configuration.
system-control—To add this to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Understanding Traffic Processing on Security Devices"
] |
propagate-tc | propagate-tc; | [edit protocols protection-group ethernet-ring ring-name] | Enable topology change propagation from a sub-ring to an interconnected major-ring. By default,
topology change propagation is disabled. | [] | 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. | [
"Ethernet Ring Protection Switching Overview",
"Configuring Ethernet Ring Protection Switching on Switches (CLI Procedure)"
] |
propagation-delay | propagation-delay milliseconds; | [edit protocols pim],
[edit protocols pim interface (Protocols PIM) interface-name],
[edit routing-instances routing-instance-name protocols pim],
[edit routing-instances routing-instance-name protocols pim interface (Protocols PIM) interface-
name],
[edit logical-systems logical-system-name protocols pim],
[edit logi... | Set a delay for implementing a PIM prune message on the upstream routing device on a multicast
network for which join suppression has been enabled. The routing device waits for the prune pending
period to detect whether a join message is currently being suppressed by another routing device. | [
{
"name": "milliseconds",
"desc": "Interval for the prune pending timer, which is the sum of the propagation-delay value and"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Example: Enabling Join Suppression"
] |
proposal (Security Group VPN Member IKE) | proposal proposal-name {
authentication-algorithm (sha-256 | sha-384);
authentication-method pre-shared-keys;
description description;
dh-group (group14 | group24);
encryption-algorithm (aes-128-cbc | aes-192-cbc | aes-256-cbc);
lifetime-seconds seconds;
} | [edit security group-vpn member ike] | Define an IKE proposal. You can configure one or more IKE proposals. Each proposal is a list of IKE
attributes to protect the IKE connection between the IKE host and its peer. | [
{
"name": "proposal proposal-name",
"desc": "Name of the IKE proposal. The proposal name can be up to 32 alphanumeric"
},
{
"name": "authentication-algorithm",
"desc": "Configure the Internet Key Exchange (IKE) authentication algorithm. Hash"
},
{
"name": "sha-256",
"desc": "Produces... | 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. | [
"Group VPNv2 Overview"
] |
proposal (Security Group VPN Server IKE) | proposal proposal-name {
authentication-algorithm (sha-256 | sha-384);
authentication-method pre-shared-keys;
description description;
dh-group (group14 | group24);
encryption-algorithm (aes-128-cbc | aes-192-cbc | aes-256-cbc);
} | [edit security group-vpn server ike] | Define an IKE proposal for group VPN server. You can configure one or more IKE proposals. Each
proposal is a list of IKE attributes to protect the IKE connection between the IKE host and its peer. | [
{
"name": "proposal proposal-name",
"desc": "Name of the IKE proposal. The proposal name can be up to 32 alphanumeric"
},
{
"name": "authentication-algorithm",
"desc": "Configure the Internet Key Exchange (IKE) authentication algorithm. Hash"
},
{
"name": "sha-256",
"desc": "Produces... | 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. | [
"Group VPNv2 Overview"
] |
proposal (Security Group VPN Server IPsec) | proposal proposal-name {
authentication-algorithm (hmac-sha-256-128);
description description;
encryption-algorithm (aes-128-cbc | aes-192-cbc | aes-256-cbc);
lifetime-seconds seconds;
} | [edit security group-vpn server ipsec] | Define an IPsec proposal. Group VPNv2 is supported on SRX300, SRX320, SRX340, SRX345,
SRX550HM, SRX1500, SRX4100, SRX4200, and SRX4600 devices and vSRX Virtual Firewall instances. | [
{
"name": "proposal-name",
"desc": "Name of the IPsec proposal."
},
{
"name": "authentication-algorithm hmac-sha-256-128",
"desc": "Configure the IPsec authentication algorithm. Produces a 256-bit"
},
{
"name": "description description",
"desc": "Text the description of IPsec proposa... | 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. | [
"Group VPNv2 Overview"
] |
proposal (Security IKE Dynamic SA) | proposal ike-proposal-name {
authentication-algorithm (md5 | sha1 | sha-256);
authentication-method (dsa-signatures | pre-shared-keys | rsa-signatures);
description description;
dh-group (group1 | group2 | group 5 | group14);
encryption-algorithm algorithm;
lifetime-seconds seconds;
} | [edit security ike] | Define an IKE proposal for a dynamic SA. | [
{
"name": "ike-proposal-name",
"desc": "Specify an IKE proposal name."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring an IKE Proposal for Dynamic SAs"
] |
proposal (Security IKE) | proposal proposal-name {
authentication-algorithm (md5 | sha-256 | sha-384 | sha1 | sha-512);
authentication-method (certificates | digital-signature | dsa-signatures | ecdsa-
signatures-256 | ecdsa-signatures-384 | ecdsa-signatures-521 | pre-shared-keys | rsa-signatures
| ecdsa-signatures-521);
descriptio... | [edit security ike] | Define an IKE proposal. | [
{
"name": "proposal-name",
"desc": "Name of the IKE proposal. The proposal name can be up to 32 alphanumeric characters long."
},
{
"name": "authentication-algorithm",
"desc": "Configure the Internet Key Exchange (IKE) authentication hash algorithm that authenticates packet data. It can be one o... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 8.5.
Support for dh-group group 14 and dsa-signatures added in Junos OS Release 11.1.
Support for sha-384, ecdsa-signatures-256, ecdsa-signatures-384, group19, group20, and group24 options added in
Junos OS Release 12.1X45-D10.
Support for ecdsa-signatures-256 and ecdsa-signatures... | [
"IPsec Overview",
"Configuring an IKE Proposal for Dynamic SAs"
] |
proposal (Security IPsec) | proposal proposal-name {
authentication-algorithm (hmac-md5-96 | hmac-sha-256-128 | hmac-sha-256-96 | hmac-sha-384 |
hmac-sha-512 | hmac-sha1-96);
description description;
encryption-algorithm (3des-cbc | aes-128-cbc | aes-128-gcm | aes-192-cbc | aes-192-gcm |
aes-256-cbc | aes-256-gcm | chacha20-poly1305... | [edit security ipsec] | Define an IPsec proposal. An IPsec proposal lists protocols and algorithms (security services) to be
negotiated with the remote IPsec peer. | [
{
"name": "proposal-name",
"desc": "Name of the IPsec proposal."
},
{
"name": "authentication-algorithm",
"desc": "Configure the IPsec authentication algorithm. Authentication algorithm is the hash algorithm that authenticates packet data. It can be one of six algorithms: Values: The hash algor... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
extended-sequence-number option introduced in Junos OS Release 19.4R1.
Starting in Junos OS Release 20.2R1, we’ve changed the help text description as NOT RECOMMENDED for the
CLI options hmac-md5-96, hmac-sha1-96, 3des-cbc, and des-cbc for devices running iked process w... | [
"Configuring an IPsec Proposal for an ES PIC",
"Installing Junos IKE package"
] |
proposal (Services IKE) | proposal proposal-name {
authentication-algorithm (md5 | sha1 | sha-256);
authentication-method (ecdsa-signatures-256 | ecdsa-signatures-384 | pre-shared-keys | rsa-
signatures);
description description;
dh-group (group1 | group2 | group5 |group14 | group15 | group16 | group19 | group20 |
group24);
... | [edit services ipsec-vpn ike] | Define an IKE proposal for a dynamic SA.
NOTE: In Junos FIPS mode, ECDSA options of the authentication-method statement are not
supported in Junos OS Release 17.3R1. Starting in Junos OS Release 17.4R1, ECDSA is
supported in Junos FIPS mode. | [
{
"name": "proposal-name",
"desc": "IKE proposal name."
}
] | 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. | [
"Configuring IKE Proposals"
] |
proposal (Services IPsec VPN) | proposal proposal-name {
authentication-algorithm (hmac-md5-96 | hmac-sha1-96);
description description;
encryption-algorithm algorithm;
lifetime-seconds seconds;
protocol (ah | esp | bundle);
} | [edit services ipsec-vpn ipsec] | Define an IPsec proposal for a dynamic SA. | [
{
"name": "proposal-name",
"desc": "IPsec proposal name."
}
] | 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. | [
"Configuring IPsec Proposals"
] |
proposals (Services) | proposals [ proposal-names ]; | [edit services ipsec-vpn ike policy policy-name],
[edit services ipsec-vpn ipsec policy policy-name] | Define a list of proposals to include in the IKE or IPsec policy. | [
{
"name": "proposal-names",
"desc": "List of IKE or IPsec proposal names."
}
] | 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. | [
"Configuring IKE Proposals",
"Configuring IPsec Proposals"
] |
proposals | proposals [ proposal-names ]; | [edit security ike policy ike-peer-address],
[edit security ipsec policy ipsec-policy-name] | Associate one or more proposals with an IKE or IPsec policy. | [
{
"name": "proposal-names",
"desc": "Name of one or more proposals."
}
] | 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. | [
"Configuring an IKE Policy for Preshared Keys",
"Configuring the IPsec Policy for an ES PIC"
] |
protect (Security) | protect {
deny {
all {
timeout value-in-seconds;
}
destination-ip address;
timeout value-in-seconds;
}
} | [edit security alg],
[edit security sip (Security)],
[edit security application-screen (Security SIP)] | Configure options to protect servers against INVITE attacks. | [] | 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. | [] |
protect core | protect core; | [edit routing-instances routing-instance-name routing-options] | In an MPLS VPN Core network, enable BGP Prefix-Independent Convergence (PIC) Edge to install a VPN
route in the forwarding table for use as an alternate path when a provider edge (PE) router fails or
connectivity to a PE router is lost. This alternate link is used until global convergence through the
interior gateway p... | [] | 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.
Support in Layer 3 VPN routers is extended to BGP PIC with multiple routes in the global tables such as
inet and inet6 unicast, and inet and inet6 labeled unicast in Junos OS Release 15.1.
Support for Resource Reservation Protocol (RSVP) introduced in Junos OS Release 16.1... | [
"Configuring BGP PIC Edge for MPLS Layer 3 VPNs",
"Example: Configuring Provider Edge Link Protection in Layer 3 VPNs",
"Introduction to Configuring Layer 3 VPNs",
"LDP Operation",
"Understanding Multiprotocol BGP"
] |
protect | protect (hierarchy | statement | identifier) | Protect a hierarchy, statement, or identifier from modification or deletion. | [
{
"name": "hierarchy",
"desc": "(Optional) Protect a specific hierarchy."
},
{
"name": "statement",
"desc": "(Optional) Protect a specific statement."
},
{
"name": "identifier",
"desc": "(Optional) Protect a specific identifier."
},
{
"name": "none",
"desc": ""
}
] | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy. | Command introduced in Junos OS Release 11.2. | [
"Example: Protecting the Configuration from Modification or Deletion"
] | |
protect-interface | protect-interface interface-name; | [edit bridge-domains bridge-domain-name interface],
[edit logical-systems logical-system-name bridge-domains bridge-domains interface],
[edit logical-systems logical-system-name protocols l2circuit neighbor address
interface interface-name],
[edit logical-systems logical-system-name protocols l2circuit local-switching... | Provide a backup for the protected interface in case of failure. Network traffic uses the primary interface
only, as long as the primary interface functions. | [
{
"name": "interface-name",
"desc": "Name of the protect interface to configure."
}
] | 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 at the following hierarchy levels introduced in Junos OS Release 17.4: [edit bridge domains], [edit
logical-systems], and [edit routing-instances]. | [
"Configuring the Protect Interface",
"Configuring EVPN Active-Standby Multihoming to a Single PE Device"
] |
protect-maintenance-association (OAM) | protect-maintenance-association protect-ma-name; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name ] | Configure the name of the protect transport path for the maintenance-association. | [
{
"name": "protect-ma-name",
"desc": "The name of the protect transport path."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4 | [
"Configuring Connectivity Fault Management (CFM)"
] |
protected-l2circuit | protected-l2circuit {
egress-pe address;
ingress-pe address;
virtual-circuit-id identifier;
} | [edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name egress-protection],
[edit protocols l2circuit neighbor address interface interface-name egress-protection] | Configures the protected Layer 2 circuit as part of an egress protection virtual circuit (EPVC). | [
{
"name": "egress-pe address",
"desc": "Specify the address of the egress PE router for the protected Layer 2 circuit."
},
{
"name": "ingress-pe address",
"desc": "Specify the address of the ingress PE router for the protected Layer 2 circuit."
},
{
"name": "virtual-circuit-id",
"des... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS release 10.4. | [
"Example: Configuring an Egress Protection LSP for a Layer 2 Circuit"
] |
protection (Protocols BGP) | protection; | [edit routing-instances instance-name protocols bgp family inet unicast],
[edit routing-instances instance-name protocols bgp family inet6 unicast],
[edit routing-instances instance-name protocols bgp family inet labeled-unicast],
[edit routing-instances instance-name protocols bgp family inet6 labeled-unicast] | Configure the backup path to protect the active provider edge path in a Layer 3 VPN or a BGP labeled
unicast path. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | [
"Example: Configuring Provider Edge Link Protection in Layer 3 VPNs",
"Example: Configuring Provider Edge Link Protection for BGP Labeled Unicast Paths"
] | |
protection (Protocols MPLS) | protection; | [edit logical-systems logical-system-name protocols bgp group group-name family inet labeled-
unicast],
[edit protocols bgp group group-name family inet labeled-unicast] | Configure protection on a link between two routers in different autonomous systems. | [] | 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. | [
"Understanding MPLS Inter-AS Link Protection"
] |
protection-group | protection-group {
ethernet-ring ring-name {
data-channel {
vlan number
}
east-interface {
control-channel channel-name {
vlan number;
interface name interface-name
}
}
... | [edit protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [
"Ethernet Ring Protection Switching Overview",
"Ethernet Ring Protection Using Ring Instances for Load Balancing",
"Example: Configuring Load Balancing Within Ethernet Ring Protection for MX Series Routers",
"Configuring Ethernet Ring Protection Switching on Switches (CLI Procedure)",
"Example: Configuring ... |
protection-revert-time | protection-revert-time seconds; | [edit logical-systems logical-system-name protocols mpls interface interface-name static],
[edit protocols mpls interface interface-name static] | Specify the amount of time (in seconds) that a static LSP must wait before traffic reverts from the bypass
path to the original path.
If you have configured a value of 0 seconds for the protection-revert-time statement and traffic is switched
to the bypass path, the traffic remains on that path indefinitely. It is neve... | [
{
"name": "seconds",
"desc": "Time in seconds."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Configuring Static LSPs"
] |
protector-interface | protector-interface interface-name; | [edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name egress-protection],
[edit protocols l2circuit neighbor address interface interface-name egress-protection] | Configures the protector interface for an egress protection LSP. | [
{
"name": "interface-name",
"desc": ""
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS release 10.4. | [
"Example: Configuring an Egress Protection LSP for a Layer 2 Circuit"
] |
protector-pe | protector-pe address {
context-identifier identifier;
lsp lsp-name;
}
} | [edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name egress-protection],
[edit protocols l2circuit neighbor address interface interface-name egress-protection] | Configures the protector PE router for an egress protection LSP. Test. | [
{
"name": "address",
"desc": ""
},
{
"name": "context-identifier identifier",
"desc": ""
},
{
"name": "lsp lsp-name",
"desc": ""
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS release 10.4. | [
"Example: Configuring an Egress Protection LSP for a Layer 2 Circuit"
] |
protocol (Application Identification) | protocol (http | ssl | tcp | udp); | [edit services application-identification application application-name over protocol-type
signature l4-l7-signature-name] | Identify the protocol bundles to be monitored to classify applications. This statement is not available if
the MX Series router is running Next Gen Services. | [
{
"name": "http",
"desc": "Use the HTTP protocol ."
},
{
"name": "ssl",
"desc": "Use the SSL protocol."
},
{
"name": "tcp",
"desc": "Use the TCP protocol."
},
{
"name": "udp",
"desc": "Use the UDP protocol."
}
] | 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. | [
"Application Identification Overview",
"Configuring Custom Application Signatures"
] |
protocol (Applications) | protocol protocol-name; | [edit applications application application-name ]
[edit applications application application-name term term-name] | Specify the networking protocol name or number.
The networking protocol type combines with destination-port to identify an application type. For
example, to create an application for iSCSI, use the protocol tcp with the destination port number 3260. | [
{
"name": "protocol-name",
"desc": "Networking protocol name. The following text values are supported. For a complete list of"
},
{
"name": "ah",
"desc": "IP Security Authentication Header"
},
{
"name": "egp",
"desc": "Exterior gateway protocol"
},
{
"name": "esp",
"desc"... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement modified in Junos OS Release 8.5. | [
"Security Policy Application Sets Overview"
] |
protocol (Drop Profile Map) | protocol protocol drop-profile profile-name; | [edit class-of-service schedulers scheduler-name drop-profile-map loss-priority (low | medium-high |
high)] | Configure the protocol type for the specified weighted random early detection (WRED) drop profile. | [
{
"name": "protocol",
"desc": "Type of protocol. The protocol can be:"
},
{
"name": "any",
"desc": "Accept any protocol type."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [] |
protocol (Drop Profiles) | protocol protocol drop-profile profile-name; | [edit class-of-service schedulers scheduler-name] | Specify the protocol type for the specified drop profile. | [
{
"name": "drop-profile profile-name",
"desc": "Name of the drop profile."
},
{
"name": "protocol",
"desc": "Type of protocol. It can be:"
},
{
"name": "any",
"desc": "Accept any protocol type."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Example: Configuring CoS on EX Series Switches",
"Configuring CoS Tail Drop Profiles (CLI Procedure)",
"Understanding CoS Tail Drop Profiles"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.