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 |
|---|---|---|---|---|---|---|---|
configuration-database | configuration-database {
ephemeral {
allow-commit-synchronize-with-gres;
commit-synchronize-model (asynchronous | synchronous);
cyclic-version-for-ephemeral-default version;
delete-ephemeral-default;
ignore-ephemeral-default;
instance instance-name {
cycli... | [edit system] | Define parameters for the configuration databases.
Configure the virtual-memory-mapping statement hierarchy to increase the memory space available for the
configuration database size per process, as needed, by using virtual memory mapping and page-pooling.
Configure the ephemeral statement hierarchy to specify options ... | [
{
"name": "extend-size",
"desc": "Increase the maximum memory space available for the configuration database. Table 26 on page 4749 and Table 27 on page 4749 outline the initial releases in which the extend-size value changed and the approximate values. The extended size is based on the default maximum data... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2.
extend-size statement added in Junos OS Evolved Release 22.1R1.
optimize-db-size statement added in Junos OS Evolved Release 24.4R1. | [
"Using Virtual Memory for Process Configuration Data"
] |
configuration-file | server-name configuration-file filepath; | [edit access securid-server] | Specify the path of the SecurID server configuration file. The file is copied on the devices in some
directory location—for example, /var/db/securid/sdconf.rec. | [
{
"name": "server-name",
"desc": "Name of the SecurID authentication server."
},
{
"name": "filepath",
"desc": "Path of the SecurID server configuration file."
}
] | secret—To view this statement in the configuration.
secret-control—To add this statement to the configuration. | Statement introduced in Release 9.1 of Junos OS. | [
"Example: Configuring SecurID User Authentication"
] |
configuration-name | configuration-name configuration-name; | [edit logical-systems logical-system-name protocols mstp],
[edit logical-systems logical-system-name routing-instances routing-instance-name
protocols mstp],
[edit protocols mstp],
[edit routing-instances routing-instance-name protocols mstp] | Specify the configuration name, which is the MSTP region name carried in the MSTP BPDUs. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Support for logical systems added in Junos OS Release 9.6. | [
"Understanding MSTP",
"Understanding BPDUs Used for Exchanging Information Among Bridges",
"Configuring Multiple Spanning Tree Protocol",
"Configuring MSTP on Switches",
"Example: Faster Convergence and Improved Network Stability with RSTP on EX Series Switches",
"Example: Configuring Network Regions for ... |
configuration-servers | configuration-servers {
url {
password password;
}
} | [edit system autoinstallation] | Configure the URL address of a server from which the configuration files must be obtained.
You can download a configuration file automatically from an FTP, Hypertext Transfer Protocol (HTTP), or
Trivial FTP (TFTP) servers. Examples of URLs:
•
tftp://hostname/path/filename
•
ftp://username:password@ftp.hostname.net
•
h... | [
{
"name": "url",
"desc": "Specify the URL address of the server containing the configuration files."
},
{
"name": "password",
"desc": "Specify the password for authentication with the configuration server. Specifying a"
}
] | 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 Autoinstallation of Configuration Files"
] |
configuration-synchronize (Chassis Cluster) | configuration-synchronize {
no-secondary-bootup-auto;
} | {primary:node0}
[edit chassis cluster] | Disables the automatic chassis cluster synchronization between the primary and secondary nodes.
The chassis cluster synchronization feature automatically synchronizes the configuration from the
primary node to the secondary node when the secondary joins the primary as a cluster. If you want to
disable automatic chassis... | [
{
"name": "no-secondary-bootup-auto",
"desc": "Disable the automatic chassis cluster synchronization between the primary and secondary nodes."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X47-D10. | [
"Understanding Automatic Chassis Cluster Synchronization Between Primary and Secondary Nodes"
] |
configure | configure
<batch>
<exclusive>
<private> | Enter configuration mode. When this command is entered without any optional keywords, everyone can
make configuration changes and commit all changes made to the configuration. | [
{
"name": "none",
"desc": "Enter configuration mode."
},
{
"name": "batch",
"desc": "(Optional) Work in the batch commit mode where commit operations are executed in batches."
},
{
"name": "dynamic",
"desc": "(Optional) (Not available for Junos OS Evolved) Configure routing policies ... | configure
Output Fields
When you enter this command, you are placed in configuration mode and the system prompt changes
from hostname> to hostname#.
Sample Output
configure
user@host> configure
Entering configuration mode
[edit]
user@host# | Command introduced before Junos OS Release 7.4.
The dynamic option of the configure command is deprecated for Junos OS Evolved. | [] | |
configured-flow-control | configured-flow-control {
rx-buffers (on | off);
tx-buffers (on | off);
} | [edit interfaces interface-name ether-options] | Configure Ethernet PAUSE asymmetric flow control on an interface. You can set an interface to generate
and send PAUSE messages, and you can set an interface to respond to PAUSE messages sent by the
connected peer. You must set both the rx-buffers and the tx-buffers values when you configure
asymmetric flow control.
Use... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Configuring CoS Asymmetric Ethernet PAUSE Flow Control",
"Enabling and Disabling CoS Symmetric Ethernet PAUSE Flow Control",
"Understanding CoS Flow Control (Ethernet PAUSE and PFC)"
] |
congestion-notification-profile | congestion-notification-profile profile-name {
input {
(dscp | ieee-802.1) {
code-point [code-point-bits] {
pfc {
mru mru-value;
}
xon value;
}
}
cable-length cable-length-value;
}
output {
... | [edit class-of-service],
[edit class-of-service interfaces interface-name] | Configure a congestion notification profile (CNP) to enable priority-based flow control (PFC) on traffic
and apply the profile to an interface. You can apply a CNP to most interfaces, including aggregated
ethernet (AE) interfaces and their individual members.
A congestion notification profile can be configured to enabl... | [
{
"name": "profile-name",
"desc": "Name of the congestion notification profile."
},
{
"name": "pfc-watchdog",
"desc": "Enable the Priority Flow Control (PFC) watchdog. If you do not configure any options, the default values are used."
},
{
"name": "detection number of polling intervals",... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4.
Support for DSCP values introduced in Junos OS Release 17.4R1 for the QFX Series.
pfc-watchdog option introduced in Junos OS Evolved Release 20.4R1. | [
"Configuring CoS PFC (Congestion Notification Profiles)",
"Understanding CoS Flow Control (Ethernet PAUSE and PFC)",
"Understanding CoS IEEE 802.1p Priorities for Lossless Traffic Flows",
"Understanding PFC Using DSCP at Layer 3 for Untagged Traffic",
"Configuring DSCP-based PFC for Layer 3 Untagged Traffic... |
connect-actively | connect-actively {
<capabilities-exchange-timeout seconds>;
<port port-number>;
<repeat-timeout seconds>;
<retry-timeout seconds>;
<timeout seconds>;
transport transport-name;
} | [edit access diameter peer peer-name] | Define the destination port and transport connection used to establish active connections to the
Diameter peer. | [
{
"name": "capabilities-exchange-timeout",
"desc": ""
},
{
"name": "seconds",
"desc": "(Optional) Use the specified amount of time to wait for a Capabilities-Exchange-Answer message. Range: 1 through 65,535 seconds Default: 10 seconds"
},
{
"name": "port port-number",
"desc": "(Opt... | 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. | [] |
connection (Identity Management Advanced Query) | connection {
connect-method (http | https);
port port;
primary {
address address;
ca-certificate ca-certificate;
client-id client-id;
client-secret client-secret;
interface interface-name;
routing-instance routing-instance -name;
source source-address;... | [edit services user-identification identity-management] | Configure parameters for connecting the SRX Series to the Juniper Identity Management Service (JIMS)
server to obtain user identity and device information.
For the SRX Series Firewall to obtain user identity information, you must first establish a connection to
the JIMSserver. The parameters to specify for the connecti... | [
{
"name": "connect-method",
"desc": "Method of connection Values:"
},
{
"name": "http",
"desc": "HTTP connection"
},
{
"name": "https",
"desc": "HTTPS connection"
},
{
"name": "port",
"desc": "Server port Default: 443 Range: 1 through 65535"
},
{
"name": "query... | 1. services—To view this statement in the configuration.
2. services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D100.
Source, interface, and routing-instance options are introduced in Junos OS Release 21.1R1. | [
"Configure Juniper Identity Management Service to Obtain User Identity Information"
] |
connection-flood | connection-flood {
threshold rate;
} | [edit logical-systems name security alg mgcp application-screen],
[edit logical-systems name tenants name security alg mgcp application-screen],
[edit security alg mgcp application-screen],
[edit services alg mgcp application-screen],
[edit tenants name security alg mgcp application-screen] | Configure the connection-flood parameter to limit the number of new connection requests allowed per
Media Gateway (MG) per second. Media Gateway Control Protocol (MGCP) Application Layer Gateway
(ALG) drops the messages exceeding the threshold. | [
{
"name": "threshold rate",
"desc": "Number of connection requests per second allowed per MG."
}
] | 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. | [] |
connection-limit (REST API) | connection-limit limit; | [edit system services rest control] | Specify the maximum number of simultaneous connections for the REST API process. | [
{
"name": "limit",
"desc": "Maximum number of simultaneous connections (IPv4 only). Range: 1 through 1024 Default: 64 NOTE: The maximum number of simultaneous connections that the SRX series supports:"
},
{
"name": "SRX300 and SRX320 - 8 sessions",
"desc": ""
},
{
"name": "SRX34X and S... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
connection-limit | connection-limit limit; | [edit system services finger],
[edit system services ftp],
[edit system services netconf ssh],
[edit system services ssh],
[edit system services telnet],
[edit system services tftp-server],
[edit system services xnm-clear-text],
[edit system services xnm-ssl]
[edit system services rest control] | Configure the maximum number of connections sessions for each type of system service (finger, ftp, ssh,
rest, telnet, xnm-clear-text, or xnm-ssl) per protocol (either IPv6 or IPv4). | [
{
"name": "limit",
"desc": "(Optional) Maximum number of established connections per protocol (either IPv6 or IPv4)."
}
] | 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 DTCP-over-SSH Service for the Flow-Tap Application",
"Configuring SSH Service for Remote Access to the Router or Switch"
] |
connection-protection | connection-protection; | [edit logical-systems logical-system-name protocols l2circuit local-switching interface
interface-name],
[edit logical-systems logical-system-name protocols l2circuit neighbor address interface],
[edit protocols l2circuit local-switching interface interface-name],
[edit protocols l2circuit neighbor address interface i... | Enable connection protection on the Layer 2 circuit. Connection protection enables you to configure a
redundant pseudowire to act as a backup connection and can be configured between PE routers,
maintaining Layer 2 circuit and VPLS services after certain types of failures. This feature helps to
improve the reliability ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Example: Configuring Layer 2 Circuit Switching Protection"
] |
connection-protection-tlv | connection-protection-tlv; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name continuity-check] | Includes connection protection OUI TLV in continuity check messages (CCM) .The TLV is responsible for
carrying the flag information within CCM PDUs. Though this OUI TLV will be included in the CCM
frames by provider edge devices, the value is updated by the provider routers in case the traffic to the
other end of the n... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"Configuring MAC Flush Message Processing in CET Mode",
"Example: Configuring an Action Profile Based on Connection Protection TLVs"
] | |
connections (Circuits) | connections {
interface-switch connection-name {
interface interface-name.unit-number;
}
lsp-switch connection-name {
transmit-lsp label-switched-path;
receive-lsp label-switched-path;
}
p2mp-receive-switch {
output-interface [ interface-name.unit-number ];
r... | [edit logical-systems logical-system-name protocols],
[edit protocols] | Define the connection between two circuits in a CCC connection. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Layer 2 Switching Cross-Connects Using CCC",
"Configuring MPLS LSP Tunnel Cross-Connects Using CCC",
"Configuring TCC",
"Configuring CCC Switching for Point-to-Multipoint LSPs"
] |
connections (Host VPN) | connections {
connection-name {
children {
child-name {
esp-proposal esp-proposal;
local-traffic-selector {
(ipv4-prefix ipv4-prefix | ipv6-prefix ipv6-prefix);
port port;
protocol protocol;
... | [edit security host-vpn] | Configure IPsec connection details. The Internet Key Exchange (IKE) protocol is a component of IPsec
used for performing mutual authentication and establishing and maintaining security associations (SAs).
Each SA describes a specific negotiated set of parameters to protect traffic for a certain time period for
an IPsec... | [
{
"name": "connection-name",
"desc": "Specify the name of the IKE SA connection."
},
{
"name": "dpd-delay",
"desc": "Specify the Dead Peer Detection delay used on the connection. This is the Interval between sending liveness messages. Default: 0, which is disabled Dead Peer Dectection. Range: ... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 18.3R1. | [] |
connections (MPLS) | connections {
remote-interface-switch connection-name {
interface interface-name.unit-number;
transmit-lsp label-switched-path;
receive-lsp label-switched-path;
} | [edit protocols] | Define the connection between two circuits in a CCC connection.
The remaining statements are explained separately. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Example: Configuring MPLS on EX8200 and EX4500 Switches"
] |
connectivity-association (MACsec Interfaces for MX Series) | connectivity-association connectivity-association-name; | [edit security macsec interfaces interface-name] | Applies a connectivity association to an interface, which enables Media Access Control Security
(MACsec) on that interface.
Default
No connectivity associations are associated with any interfaces. | [
{
"name": "connectivity-association-name",
"desc": "Name of the MACsec connectivity association. Range: 1 through 32 alphanumeric characters. Allowed characters are [a-z, A-Z, 0-9]"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Media Access Control Security (MACsec) on Routers"
] |
connectivity-association (MACsec Interfaces) | connectivity-association connectivity-association-name; | [edit security macsec interfaces interface-name] | Applies a connectivity association to an interface, which enables Media Access Control Security
(MACsec) on that interface.
The point-to-point links are secured after security keys are matched at the endpoints of the links. If you
enable MACsec by using the static connectivity association key (CAK) security mode, user... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D15.
Statement introduced on SRX devices in Junos OS Release 15.1X49-D60. | [
"Configuring MACsec on EX, QFX and SRX Devices",
"Understanding Media Access Control Security (MACsec)",
"Configuring Media Access Control Security (MACsec)"
] |
connectivity-association (MX Series) | connectivity-association connectivity-association-name {
exclude-protocol protocol-name;
include-sci;
mka {
bounded-delay;
key-server-priority priority-number;
must-secure;
should-secure;
transmit-interval interval;
eapol-address (pae | provider-bridge | lldp... | [edit security macsec] | Create or configure a MACsec connectivity association.
A connectivity association is not applying MACsec to traffic until it is associated with an interface.
MACsec connectivity associations are associated with interfaces using the interfaces statement in the
[edit security macsec] hierarchy.
Default
No connectivity as... | [
{
"name": "connectivity-association-name",
"desc": "Name of the MACsec connectivity association. Range: 1 through 32 alphanumeric characters. Allowed characters are [a-z, A-Z, 0-9] The remaining statements are explained separately."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Configuring Media Access Control Security (MACsec) on Routers"
] |
connectivity-association | connectivity-association connectivity-association-name;
exclude-protocol protocol-name;
include-sci;
mka {
must-secure;
key-server-priority priority-number;
transmit-interval interval;
}
no-encryption;
offset (0|30|50);
pre-shared-key {
cak hexadecimal-number;... | [edit security macsec] | Create or configure a MACsec connectivity association.
A connectivity association is not applying MACsec to traffic until it is associated with an interface.
MACsec connectivity associations are associated with interfaces using the "interfaces" on page 9540
statement in the [edit security macsec] hierarchy.
Default
No ... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D15.
Statement introduced on SRX Series Firewalls in Junos OS Release 15.1X49-D60. | [
"Configuring MACsec on EX, QFX and SRX Devices",
"Understanding Media Access Control Security (MACsec)",
"Configuring Media Access Control Security (MACsec)"
] |
connectivity-fault-management | connectivity-fault-management {
action-profile profile-name {
action {synchronous-notification
interface-down;
log-and-generate-ais {
interval(1m | 1s);
levelvalue;
priority value;
}
}
default-actions {
... | [edit protocols oam ethernet] | For Ethernet interfaces on M7i and M10i routers with Enhanced CFEB (CFEB-E), and on M120, M320,
MX Series, and T Series routers, specify connectivity fault management for IEEE 802.1ag Operation,
Administration, and Management (OAM) support.
In Junos OS Release 9.3 and later, this statement is also supported on aggregat... | [
{
"name": "Asynchronous-notification",
"desc": "Generate asynchronous-notification (Laser off for optical physical) option is"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [
"IEEE 802.1ag OAM Connectivity Fault Management Overview"
] |
connectivity-fault-management-switches | connectivity-fault-management {
action-profile profile-name {
action {
asynchronous-notification
interface-down;
}
default-actions {
interface-down;
}
event {
adjacency-loss;
}
}
linktrace {
age (30m | 10m | 1m | 30s... | [edit protocols oam ethernet] | Configure connectivity fault management for IEEE 802.1ag Operation, Administration, and Management
(OAM) support.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "Asynchronous-notification",
"desc": "Generate asynchronous-notification (Laser off for optical physical) option is"
},
{
"name": "send-zero-interval-ccm",
"desc": "Programs end point hardware for TX with 0s CCI. This option is introduced in"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2.
performance-monitoring introduced in Junos OS Release 11.4 for EX Series switches. | [
"Configuring Ethernet OAM Connectivity Fault Management (CLI Procedure)",
"Junos OS Network Interfaces Configuration Guide"
] |
connectivity-type | connectivity-type (ce | irb | permanent); | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls],
[edit routing-instances routing-instance-name protocols vpls] | Specify when a VPLS connection is taken down depending on whether or not the interface for the VPLS
routing instance is customer-facing or integrated routing and bridging (IRB).
NOTE: The connectivity-type statement is not supported for FEC 129 VPLS (also known as
LDP VPLS with BGP-based autodiscovery).
Default
ce | [
{
"name": "ce",
"desc": "Require that for the VPLS connection to be up, the customer-facing interface for the VPLS routing"
},
{
"name": "irb",
"desc": "Allow a VPLS connection to remain up so long as an IRB interface is configured for the VPLS routing"
},
{
"name": "permanent",
"des... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.1.
irb option introduced in Junos OS Release 9.3.
permanent option introduced in Junos OS Release 10.4. | [
"Configuring VPLS Routing Instance and VPLS Interface Connectivity",
"Configuring Separate NNI Routing Instances for Layer 2 Wholesale Service Retailers"
] |
console (System Logging) | console {
facility severity;
application-status (any | error);
} | [edit system syslog] | Configure the logging of system messages to the system console. Log messages include priority
information, which is information about log messages’ facility and severity levels. | [
{
"name": "facility",
"desc": "Class (type) of messages to log. To specify multiple classes, include multiple facility severity statements."
},
{
"name": "severity",
"desc": "Severity of the messages that belong to the facility specified by the paired facility name. Messages with severities of t... | 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.
application-status option introduced in Junos OS Evolved 23.1R1. | [
"Directing System Log Messages to the Console",
"System Log Explorer"
] |
console (System Ports) | console {
authentication-order [authentication-methods ];
disable;
insecure;
log-out-on-disconnect;
type terminal-type;
} | [edit system ports] | Configure the characteristics of the console port.
Default
The console port is enabled and its speed is 9600 baud. | [
{
"name": "authentication-order",
"desc": "Specify the order in which the authentication methods such as password ( for local"
},
{
"name": "authentication-methods",
"desc": "One or more authentication methods, listed in the order in which they should be"
},
{
"name": "password",
"de... | 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.
disable option added in Junos OS Release 7.6.
authentication-order option added in Junos OS Release 12.2R3. | [
"Configuring Junos OS to Set Console and Auxiliary Port Properties",
"Configuring Console and Auxiliary Port Properties",
"Determine the Authentication Order for LDAPS, RADIUS, TACACS+, and Password Authentication"
] |
constant | constant value; | [edit unified-edge gateways tdf gateway-name domains domain-name ip-subscriber subscription-id] | Specify a constant string for the Subscription-Id-Data value for IP-based subscribers. This constant value
is used if none of the subscription-id-options methods can be used. In such a case, the Subscription-Id-
Type is END_USER_PRIVATE. | [
{
"name": "value",
"desc": "String that is used for the Subscription-Id-Data value."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring a Set of IP-Based TDF Subscriber Properties with a TDF Domain",
"Understanding the Definition of a Set of IP-Based Subscriber Properties with a TDF Domain",
"IP-Based Subscriber Setup Overview"
] |
constituent-list | constituent-list constituent-list-name {
(administrative-group [ group-names ] | administrative-group-extended [ extended-
administrative-group-names ] | srlg [ srlg-names ]);
} | [edit logical-systems logical-systems-name protocols mpls],
[edit protocols mpls] | Create a list of traffic engineering attributes called constituent attributes, which are the link and node
attributes whose logical combination makes up an abstract hop. The constituent attributes are listed
under administrative groups, extended administrative groups, and Shared Risk Link Groups (SRLGs). | [
{
"name": "constituent-list-name",
"desc": "Name of the constituent list that includes constituent traffic engineering attributes for use in the abstract hop definition."
},
{
"name": "administrative-group [ group-names ]",
"desc": "Names of administrative groups to include in the constituent li... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Example: Configuring Abstract Hops for MPLS LSPs",
"abstract-hop"
] |
cont-stats-collection-interval | cont-stats-collection-interval interval; | [edit logical-systems name routing-instances name routing-options multicast],
[edit logical-systems name routing-options multicast],
[edit logical-systems name tenants name routing-instances name routing-options multicast],
[edit routing-instances name routing-options multicast],
[edit routing-options multicast],
[edi... | Change the default interval (in seconds) at which continuous, persistent IGMP and MLD statistics are
stored on devices that support continuous statistics collection.
Junos OS multicast devices collect statistics of received and transmitted IGMP and MLD control packets
for active subscribers. Devices that support contin... | [
{
"name": "interval",
"desc": "Interval in seconds at which you want the device to store collected continuous IGMP and MLD statistics. Range: 60 seconds to 3600 seconds (5 minutes to 1 hour)."
}
] | routing | Statement introduced in Junos OS Release 19.4R1. | [] |
contact (SNMP) | contact contact; | [edit snmp] | Defines the value of the SNMP MIB II sysContact object, which is the contact person for the managed
system. | [
{
"name": "contact",
"desc": "Name of the contact person. If the name includes spaces, enclose it in quotation marks (\" \")."
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the System Contact on a Device Running Junos OS"
] |
container-devices | container-devices {
device-count number;
} | [edit chassis]
[edit chassis interconnect-device name]
[edit chassis node-group name] | Specify the container devices configuration. The number option specifies the number of sequentially
numbered container interfaces, from ci0 to ci127 maximum. | [
{
"name": "number",
"desc": "Number of container devices."
}
] | chassis—To view this statement in the configuration.
chassis-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.3. | [] |
container-label-switched-path | container-label-switched-path lsp-name {
disable;
description description;
label-switched-path-template;
splitting-merging;
suffix string;
to ip-address;
} | [edit protocols mpls] | Configure a multi-label-switched path (LSP) tunnel between the ingress and the egress routers. The
container LSP consists of several member LSPs to the same destination. | [
{
"name": "disable",
"desc": "Disable MPLS container-label-switched path."
},
{
"name": "description description",
"desc": "Text describing the container LSP."
},
{
"name": "suffix string",
"desc": "Suffix to generate names of member LSPs of the container LSP."
},
{
"name": "... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2.
Statement introduced for QFX Switches in Junos OS Release 15.1X53-D30. | [] |
Content Security | utm {
application-proxy {
traceoptions {
flag flag;
}
}
custom-objects {
custom-url-category object-name {
value [value];
}
filename-extension object-name {
value [value];
}
mime-pattern object-name {
val... | [edit security utm default-configuration]
[edit security] | 15.1X49-D10
The Kaspersky, surf-control-integrated, and express antivirus features are not supported from
Junos OS Release 15.1X49-D10 onwards. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Starting in Junos OS Release 21.4R1, content filtering is performed by detecting the file content and not
the file extensions. So, content filtering options based on mime-type, content-type, and protocol
command is not supported. After you upgrade to Junos OS Release 21.4R1 above listed options are no
more available fo... | [] |
Content Security-policy (Application Services) | utm-policy policy-name; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
application-services] | Configure a Content Security policy for application services and attach this policy to a security profile to
implement it. | [
{
"name": "policy-name",
"desc": "Specify the name of the Content Security policy."
}
] | 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. | [] |
content-destination | content-destination identifier {
address address;
hard-limit bandwidth;
hard-limit-target bandwidth;
soft-limit bandwidth;
soft-limit-clear bandwidth;
ttl hops;
} | [edit services dynamic-flow-capture capture-group client-name] | Identify the destination for captured packets. | [
{
"name": "identifier",
"desc": "Name of the destination."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring the Content Destination"
] |
content-filtering (Logical System Security Feature Profile) | content-filtering {
profile name {
block-command block-command;
block-content-type {
activex;
exe;
http-cookie;
java-applet;
zip;
}
block-extension block-extension;
block-mime {
exception (Security Conten... | [edit logical-systems logical-systems-name security utm feature-profile]
[edit tenants tenant-name security utm feature-profile] | Configures the Content Security content-filtering feature for logical systems. The content filtering
feature controls file transfers across the gateway by checking traffic against configured filter lists. It
evaluates the traffic before all other Content Security features, except Web filtering. You can also
configure t... | [
{
"name": "block-command",
"desc": "Protocol block command custom-objects to the content-filtering profile."
},
{
"name": "block-content-type",
"desc": "Blocks other available content such as exe, http-cookie, java-applet. This is for HTTP only."
},
{
"name": "block-extension",
"desc... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1.
Support for configuration in tenant systems introduced in Junos OS Release 19.2R1. | [
"Content Filtering Overview"
] |
content-filtering (Security Content Security Policy) | content-filtering {
rule-set name {
rule name {
match {
applications [applications];
direction (any | download | upload);
file-types [file-types];
}
then {
action (block | close-client | close-client-and-server | close-server | no-action);
notification {
endpo... | [edit security utm utm-policy policy-name]
[edit logical-systems logical-systems-name security utm utm-policy policy-name]
[edit tenants tenant-name security utm utm-policy policy-name] | Configures a Content Security policy for the content filtering protocols and attach this policy to a
security profile to implement it. Each supported protocol may implement available content filters
differently. Not all filtering capabilities are supported for each protocol. The HTTP protocol supports all
content filte... | [
{
"name": "rule-set name",
"desc": "Name of the content filtering rule set."
},
{
"name": "rule name",
"desc": "Name of the content filtering rule."
},
{
"name": "application",
"desc": "List of applications to be inspected."
},
{
"name": "direction",
"desc": "Direction of... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Support for configuration in logical systems introduced in Junos OS Release 18.3R1.
Support for configuration in tenant systems introduced in Junos OS Release 19.2R1.
rule-set option introduced in Junos OS Release 21.4R1. | [
"Content Filtering"
] |
content-filtering (Security Feature Profile) | content-filtering {
block-command;
block-content-type {
activex;
exe;
http-cookie;
java-applet;
zip;
}
block-extension;
block-mime {
exception;
list;
}
notification-options {
custom-message;
(notify-mail-sender | no-noti... | [edit security utm feature-profile]
[edit security utm default-configuration] | 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": "block-command",
"desc": "Protocol block command custom-objects to the content-filtering profile."
},
{
"name": "block-content-type",
"desc": "Blocks to other available content such as exe, http-cookie, java-applet. This is for HTTP only."
},
{
"name": "block-extension",
"d... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Starting in Junos OS Release 21.4R1, content filtering is performed by detecting the file content and not
the file extensions. So, content filtering options based on mime-type, content-type, and protocol
command is not supported. After you upgrade to Junos OS Release 21.4R1, content filtering option
under the feature-p... | [] |
content-size (Security Antivirus Sophos Engine) | content-size (block | log-and-permit | permit); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus sophos-engine profile profile-name fallback-
options] | If the content size exceeds a set limit, the content is either passed or blocked.
NOTE: When you configure the content-size value, keep in mind that in certain cases,
content size is available in the protocol headers, so the max-content-size fallback is
applied before a scan request is sent. However, in many cases, con... | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
},
{
"name": "permit",
"desc": "Permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Sophos Antivirus Configuration Overview"
] |
content-size | content-size (block | log-and-permit); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name
fallback-options]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name fallback-
options] | If the content size exceeds a set limit, the content is either passed or blocked. The default action is log-
and-permit.
NOTE: When you configure the content-size value, keep in mind that in certain cases,
content size is available in the protocol headers, so the max-content-size fallback is
applied before a scan reque... | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
content-size-limit | content-size-limit value; | [edit security utm feature-profile anti-virus juniper-express-engine profile profile-name scan-
options]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name scan-
options]
[edit security utm default-configuration anti-virus scan-options] | The content size check occurs before the scan request is sent. The content size refers to accumulated
TCP payload size. The maximum configurable content size varies with different platforms. For example,
the content size ranges from 20 through 40,000 for SRX4100. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5. Support for Sophos
engine added in Junos OS Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS R... | [] |
context (Application Identification) | context {
context;
} | [edit services]
[edit services application-identification application application-name over protocol-type signature name
member name ] | Specify context for matching application running over TCP, UDP, or Layer 7.
Application identification supports custom application signatures to detect applications as they pass
through the device. You can create custom application signatures for applications based on ICMP, IP
protocol, IP address, and Layer 7. While c... | [
{
"name": "context",
"desc": "Specify the context type. For example, Following options are available in application signature package version 3284."
},
{
"name": "ftp-content-type",
"desc": "Content type of the transferred file."
},
{
"name": "ftp-file-name",
"desc": "Filename being ... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D40.
Support for Next Gen Services introduced in Junos OS Releases 19.3R2 and 19.4R1 on MX Series
MX240, MX480 and MX960 using the MX-SPC3 services card. | [
"Understanding Junos OS Application Identification Custom Application Signatures"
] |
context (Security Custom Attack) | context context-name; | [edit security idp custom-attack attack-name attack-type signature] | Define the location of the signature where IDP should look for the attack in a specific Application Layer
protocol. | [
{
"name": "context-name",
"desc": "Name of the context under which the attack has to be matched."
}
] | 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. | [] |
context (SNMPv3) | context context-name; | [edit snmp v3 snmp-community community-index] | Specify the SNMPv3 context for access control. A context identifies a collection of information
accessible for an SNMP entity. | [] | 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 the SNMPv3 Community"
] |
context | context value; | [edit services application-identification nested-application name signature name member name] | Define a service-specific context, such as http-url. | [
{
"name": "value",
"desc": "Use the specified service-specific context:"
},
{
"name": "http-header-content-type",
"desc": "Use the service context http-header-content-type."
},
{
"name": "http-header-host",
"desc": "Use the service context http-header-host."
},
{
"name": "htt... | system—To view this statement in the configuration.
system control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Application Identification for Nested Applications"
] |
context-identifier (Protocols IS-IS) | context-identifier identifier; | [edit logical-systems logical-system-name protocols isis],
[edit protocols isis] | Configure IS-IS context identifier information. | [
{
"name": "identifier",
"desc": "IPv4 address that defines a protection pair. The context identifier is manually configured on both primary and protector PEs."
}
] | 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. | [] |
context-identifier (Protocols OSPF) | context-identifer identifier | [edit logical-systems logical-system-name protocols (ospf |ospf3) area area-id],
[edit protocols (ospf | ospf3) area area-id] | Configure OSPF context-identifier information. | [
{
"name": "identifer",
"desc": "IPv4 address that defines a protection pair. The context identifier is manually configured on both the primary and protector provider edge (PE) devices."
}
] | 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. | [] |
continuity-check (EX Series Switch Only) | continuity-check {
hold-interval minutes;
interface-status-tlv;
interval (10m | 10s | 1m | 1s| 100ms);
loss-threshold number;
port-status-tlv;
} | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name] | Specify continuity check protocol options.
The remaining statements are explained separately. See CLI Explorer. | [
{
"name": "interface-status-tlv",
"desc": "Includes interface status TLV in CCM."
},
{
"name": "port-status-tlv",
"desc": "Includes port status TLV in CCM."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Configuring Ethernet OAM Connectivity Fault Management (CLI Procedure)",
"Junos OS Network Interfaces Configuration Guide"
] |
continuity-check | continuity-check {
convey-loss-threshold;
hold-interval minutes;
interface-status-tlv;
interval (10m | 10s | 1m | 1s| 100ms | 10ms| 3.3ms);
loss-threshold number;
port-status-tlv;
} | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name] | Specify continuity check protocol options.
NOTE: When the continuity-check interval is set to 3.3ms, the actual interval is 4ms
(250 pps). | [
{
"name": "convey-loss-threshold",
"desc": "Enable loss-threshold-tlv transmission."
},
{
"name": "hold-interval minutes",
"desc": "Specify the continuity check hold-interval, in minutes."
},
{
"name": "interface-status-tlv",
"desc": "Enable interface-status-tlv transmission."
},
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4. | [
"Configuring Continuity Check Protocol Parameters for Fault Detection"
] |
control (REST API) | control {
allowed-sources [ value-list ];
connection-limit limit;
} | [edit system services rest] | Specify the allowed source IP addresses and maximum number of simultaneous connections for the
REST API process.
The remaining statements are explained separately. See CLI Explorer. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
control-channel (Protocols Link Management Peer) | control-channel control-channel-interface; | [edit logical-systems logical-system-name protocols link-management peer peer-name],
[edit protocols link-management peer peer-name] | Specify the control channel interface for the peer. | [
{
"name": "control-channel-interface",
"desc": "Name of the control channel interface."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring LMP Peers"
] |
control-channel (Protocols OAM) | control-channel {
pwe3-control-word;
pw-label-ttl-1;
router-alert-label;
} | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
l2vpn oam],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
oam],
[edit routing-instances routing-instance-name protocols l2vpn oam],
[edit routing-instances routing-instance-n... | Configure the Virtual Circuit Connection Verification (VCCV) BFD control channel. VCCV provides a
control channel associated with a pseudowire. You can configure a number of different CV types for this
control channel, based on the configuration of the pseudowire. | [
{
"name": "pwe3-control-word",
"desc": "For BGP-based pseudowires that send OAM packets with a control word that has"
},
{
"name": "pw-label-ttl-1",
"desc": "For BGP-based pseudowires that send OAM packets with the MPLS pseudowire label and"
},
{
"name": "router-alert-label",
"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.0. | [
"Configuring BFD for VCCV for Layer 2 VPNs, Layer 2 Circuits, and VPLS"
] |
control-channel | control-channel channel-name {
vlan vlan-id;
interface name interface-name
} | [edit protocols protection-group ethernet-ring name (east-interface | west-interface)] | Configure the Ethernet RPS control channel logical interface to carry the RAPS PDU. The related
physical interface is the physical ring port. | [
{
"name": "vlan vlan-id",
"desc": "If the control channel logical interface is a trunk port, then a dedicated vlan vlan-id defines"
},
{
"name": "interface name interface-name",
"desc": "Interface name of the control channel."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 14.153-D10 for QFX Series switches. | [
"Ethernet Ring Protection Switching Overview",
"Example: Configuring Ethernet Ring Protection Switching on EX Series Switches",
"Example: Configuring Ethernet Ring Protection Switching on QFX Series and EX Series Switches",
"Supporting ELS",
"Configuring Ethernet Ring Protection Switching on Switches (CLI P... |
control-connection (Junos OS Evolved) | control-connection control-client-name {
control-type (managed | light);
destination-port destination-port;
routing-instance routing-instance-name;
source-address source-address;
target target-address;
test-start (auto | manual);
test-interval seconds;
traps {
control-connect... | [edit services monitoring twamp client] | For Junos OS Evolved, configure all the Two-Way Active Measurement Protocol (TWAMP) control
clients that can connect to the server. A TWAMP control connection is responsible for initiating,
starting, and ending the test sessions between a TWAMP client and a TWAMP server for performance
measurement. However, when the co... | [
{
"name": "control-client-name",
"desc": "Name of the control client."
},
{
"name": "control-type",
"desc": ""
},
{
"name": "(managed |",
"desc": ""
},
{
"name": "light)",
"desc": "Specify how you want to manage the control connection. Values: Configure one of the follow... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 20.3R1.
traps option introduced in Junos OS Evolved Release 21.3R1.
IPv6 address support introduced in Junos OS Evolved Release 21.4R1.
The local-link sub-option of the target option for TWAMP Light test sessions introduced in Junos OS
Evolved Release 22.3R1.
The inline-... | [
"Understanding Two-Way Active Measurement Protocol on Routers"
] |
control-connection (Junos OS) | control-connection control-client-name {
authentication-mode
control-type (managed | light);
destination-interface interface-name;
destination-port port;
history-size size;
moving-average-size number;
persistent-results
routing-instance instance-name;
target-address (url url | addre... | [edit services rpm twamp client] | List all the TWAMP control clients that can connect to this server. You must configure at least one client
to enable TWAMP. | [
{
"name": "control-client-name",
"desc": "Name of the control client. The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1.
Statement introduced in Junos OS Evolved Release 20.3R1.
control-type option introduced in Junos OS Release 21.1R1 and Junos OS Evolved Release 20.3R1.
source-address option and the local-link sub-option of the target-address option for TWAMP Light test
sessions introduced... | [
"Understand Two-Way Active Measurement Protocol",
"control-connection (Junos OS Evolved)"
] |
control-cores | control-cores control-number; | [edit chassis fpc slot-number pic pic-number adaptive-services service-package extension-
provider] | Configure control cores. Any cores not configured as either control or data cores are treated as user
cores. When the number of control cores is changed, the PIC reboots. | [
{
"name": "control-number",
"desc": "Number of control cores. At least one core must be a control core."
}
] | 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. | [] |
control-link-recovery | control-link-recovery; | [edit chassis cluster] | Enable control link recovery to be done automatically by the system.
If the control link fails, the secondary node enters to ineligible and then to disabled state. If the control
link recovers with in three consecutive responses, the device auto reboots irrespective of the state
(ineligible or disable) of the node. You... | [] | 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 Cluster Failover Parameters"
] |
control-plane-bandwidth-percent (Node Slicing) | control-plane-bandwidth-percent percent; | [edit chassis network-slices guest-network-functions gnf] | Allocate a percentage of the bandwidth that exists on the control plane on the router to the specified
guest network function (GNF). Allocating bandwidth prevents potential overutilization by one GNF over
another. | [
{
"name": "percent",
"desc": "Percentage of control plane bandwidth."
}
] | 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.2. | [] |
control-polarity | control-polarity (negative | positive); | [edit interfaces interface-name serial-options] | For X.21 interfaces only, configure the control signal polarity. | [
{
"name": "positive",
"desc": "Positive signal polarity."
},
{
"name": "negative",
"desc": "Negative signal polarity."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Serial Signal Polarities"
] |
control-ports | control-ports fpc {
port;
} | [edit chassis cluster] | Enable the specific control port to use as a control link for the chassis cluster. By default, all control
ports are disabled.
After connecting the control ports, you need to configure the control ports to setup control links as a
step to establish the chassis cluster.
You need to configure a minimum of one control por... | [
{
"name": "fpc slot-number",
"desc": "Flexible PIC Concentrator (FPC) slot number."
},
{
"name": "port port-number",
"desc": "Port number on which to configure the control port."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. Support. | [] |
control-signal | control-signal (assert | de-assert | normal); | [edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options] | For X.21 interfaces only, configure the to-DCE signal. | [
{
"name": "assert",
"desc": "The to-DCE signal must be asserted."
},
{
"name": "de-assert",
"desc": "The to-DCE signal must be deasserted."
},
{
"name": "normal",
"desc": "Normal request-to-send (RTS) signal handling, as defined by ITU-T Recommendation X.21."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Serial Signal Handling"
] |
control-source | control-source identifier {
allowed-destinations [ destinations ];
minimum-priority value;
no-syslog;
notification-targets address port port-number;
service-port port-number;
shared-key value;
source-addresses [ addresses ];
} | [edit services dynamic-flow-capture capture-group client-name] | Identify the source of the dynamic flow capture request. | [
{
"name": "identifier",
"desc": "Name of control source."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Configuring the Control Source"
] |
control-vlan | control-vlan (vlan-id | vlan-name) | [edit protocols protection-group ethernet-ring],
[edit protocols protection-group ethernet-ring name (east-interface | west-interface)] | Specify the VLAN that carries the protocol data units (PDUs) between the nodes in the protected
Ethernet ring. This is a control VLAN, meaning that it carries data for one instance of an Ethernet ring
protection switching (ERPS) in the control channel. Use a control VLAN on trunk port interfaces. One
control channel ca... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 14.153-D10 for QFX Series switches. | [
"Example: Configuring Ethernet Ring Protection Switching on EX Series Switches",
"Example: Configuring Ethernet Ring Protection Switching on QFX Series and EX Series Switches",
"Supporting ELS",
"Configuring Ethernet Ring Protection Switching on Switches (CLI Procedure)"
] |
control-word (Protocols Layer 2 Circuit Neighbor) | (control-word | no-control-word); | [edit logical-systems logical-system-name protocols l2circuit neighbor address
interface interface-name],
[edit protocols l2circuit neighbor address interface interface-name] | Specify the control word. The control word is four bytes long and is inserted between the Layer 2
protocol data unit (PDU) being transported and the virtual circuit (VC) label that is used for
demultiplexing. | [
{
"name": "control-word",
"desc": "Enable the use of the control word."
},
{
"name": "no-control-word",
"desc": "Disable the use of the control word."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Control Word for Frame Relay Interfaces"
] |
control-word (Protocols Layer 2 VPN) | control-word; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
l2vpn],
[edit routing-instances routing-instance-name protocols l2vpn] | Specify the control word. The control word is 4 bytes long and is inserted between the Layer 2 protocol
data unit (PDU) being transported and the virtual connection (VC) label that is used for demultiplexing.
NOTE: The following configuration statements are ignored for time-division multiplexing
pseudowires at the [edi... | [] | 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. | [
"Disabling the Control Word for Layer 2 VPNs"
] |
control-word | control-word; | edit logical-systems logical-system-name routing-instances routing-instance-name protocols evpn],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls
mesh-group mesh-group-na... | Set control-word to request that other routers insert a control word between the label stack and the MPLS
payload.
Enabling control-word prevents provider edge routers from incorrectly identifying a VPLS payload as an
IPv4 or IPv6 payload. This prevents out-of-order packet delivery in a VPLS network that is configured ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1.
Statement introduced for static pseudowires in mesh-group and in VPLS instance in Junos OS Release
20.3R1.
Statement introduced for the MPC-10E line card on the MX series router in Junos OS Release 21.3R1
and Junos OS Release 21.2R3-S3. | [
"Control Word for BGP VPLS Overview",
"Configuring a Control Word for BGP VPLS"
] |
controller (OVSDB) | controller ip-address {
inactivity-probe-duration milliseconds;
maximum-backoff-duration milliseconds;
protocol protocol {
port number;
}
} | [edit protocols ovsdb] | Configure a connection between a Juniper Networks device running the Open vSwitch Database
(OVSDB) management protocol and a software-defined networking (SDN) controller. You can connect a
Juniper Networks device to more than one SDN controller for redundancy.
In a VMware NSX environment, one cluster of NSX controllers... | [
{
"name": "ip-address",
"desc": "IPv4 address of the SDN controller."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1R2. | [
"Setting Up OVSDB on Juniper Networks Devices That Support the Dynamic Configuration of",
"VXLANs",
"Setting Up the OVSDB Protocol on Juniper Networks Devices that Support Manual Configuration of",
"VXLANs",
"Understanding How to Set Up OVSDB Connections on a Juniper Networks Device"
] |
controller (Protocols OpenFlow) | controller {
address address;
id id;
protocol tcp {
port port;
}
role equal;
} | [edit protocols openflow switch switch-name] | Configure the OpenFlow controller connection information for a virtual switch on an OpenFlow-enabled
device running Junos OS. If you configure a virtual switch with a single controller, by default, the
controller is in active mode, and the switch automatically initiates a connection to the controller. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Understanding Support for OpenFlow on Devices Running Junos OS",
"Understanding the Virtual Switch Connection to the OpenFlow Controller on Devices Running Junos",
"OS"
] |
controller | controller(p4 | re); | [edit services inline-monitoring instance] | PTX10004, PTX10008, and PTX10016 devices running Junos OS Evolved Release 22.1R1 can provide
an SDN-based backbone (data center interconnect) for target networks. It works by using a firewall filter
to redirect matching packets, via a P4Runtime agent running in Junos OS Evolved on the Routing Engine,
to a P4 controller... | [
{
"name": "p4",
"desc": "Select this option to have the P4Runtime agent send packets to the P4 controller (instead of the default Routing Engine)."
},
{
"name": "re",
"desc": "Select this option to send packets to the default Routing Engine."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 22.1R1. | [
"Firewall Filter Match Conditions and Actions (PTX Series Routers)"
] |
convert-clock-class-to-quality-level | convert-clock-class-to-quality-level; | [edit protocols ptp slave] | Configure the timeReceiver to enable it to retrieve Ethernet Synchronization Message Channel (ESMC)
information from the Precision Time Protocol (PTP) clock class.
When this option is set, the outgoing quality level depends on the PTP clock class mapping, irrespective
of the clock being configured in hybrid mode or pur... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring Hybrid Mode and ESMC Quality Level Mapping",
"Example: Configuring Hybrid Mode and ESMC Quality Level Mapping",
"Precision Time Protocol Overview",
"Synchronous Ethernet Overview",
"Understanding ESMC Quality Level Mapping",
"Understanding Hybrid Mode"
] |
convert-sa-to-msdp | convert-sa-to-msdp; | [edit routing-instances instance-name protocols mvpn mvpn-mode spt-only] | Enable conversion of MVPN Type 5 routes to MSDP Source Active (SA) routes.
Default
Conversion of MVPN Type 5 routes to MSDP SA routes is disabled.
MVPN Type 5 route to MSDP SA conversion works in spt-only mode. rpt-spt mode is not supported. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.1. | [] |
convey-loss-threshold | convey-loss-threshold; | [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name continuity-check] | Enable loss-threshold-tlv transmission.
During a unified ISSU, the control plane may go down for several seconds and cause CFM continuity
check packets to get dropped. This may cause the remote maintenance endpoint (MEP) to detect a
connectivity loss and mark the MEP as down. To keep the MEP active during a unified ISS... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [] | |
copy | copy existing-statement to new-statement | Make a copy of an existing statement in the configuration. | [
{
"name": "existing-statement",
"desc": "Statement to copy."
},
{
"name": "new-statement",
"desc": "Copy of the statement."
}
] | configure—To enter configuration mode, but other required privilege levels depend on where the
statement is located in the configuration hierarchy. | Command introduced before Junos OS Release 7.4. | [
"Copying a Statement in the Configuration"
] | |
copy-dont-fragment-bit (Services IPsec VPN) | copy-dont-fragment-bit; | [edit services ipsec-vpn rule rule-name term term-name then] | Copy the do not fragment (DF) bit value to only the outer header and not modify the inner header of the
IPsec packet. If the encapsulated packet size exceeds the tunnel maximum transmission unit (MTU), the
packet is fragmented before encapsulation. This functionality is supported on MX Series routers with
MS-MICs and M... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Configuring IPsec Rules"
] |
copy-dont-fragment-bit (Services Set) | copy-dont-fragment-bit; | [edit services service-set service-set-name ipsec-vpn-options] | Copy the do not fragment (DF) bit value to only the outer header and not modify the inner header of the
IPsec packet in dynamic endpoint tunnels. If the encapsulated packet size exceeds the tunnel maximum
transmission unit (MTU), the packet is fragmented before encapsulation. This functionality is supported
on MX Serie... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1. | [
"Configuring IPsec Service Sets",
"Configuring IPsec Rules"
] |
copy-plp-all | copy-plp-all; | [edit class-of-service] | Enable PLP bit copying for ingress and egress for unicast and multicast traffic when traffic is ingressing
one FPC and egressing the other (from E3-FPC to non-E3 FPC on M320 routers, or from ES-FPC to
non-ES FPC on T Series routers). | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.3. | [
"Managing Congestion by Setting Packet Loss Priority for Different Traffic Flows"
] |
copy-tos-to-outer | copy-tos-to-outer service-type (gre | mt); | [edit chassis] | For static and dynamic IPv4 GRE tunnel interfaces and MT tunnel interfaces on MPCs, copy the inner IP
header’s ToS bits to the outer IP packet header for traffic transiting the router. This statement affects all
MPC interfaces and takes precedence over the "copy-tos-to-outer-ip-header-transit" on page 4907,
which appli... | [] | 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. | [] |
copy-tos-to-outer-ip-header | copy-tos-to-outer-ip-header; | [edit interfaces gr-fpc/pic/port unit logical-unit-number],
[edit interfaces gre unit logical-unit-number],
[edit logical-systems logical-system-name interfaces gr-fpc/pic/port unit logical-unit-number],
[edit logical-systems logical-system-name interfaces gre unit logical-unit-number] | For GRE tunnel interfaces and GRE interfaces for GMPLS control channels only, enable the inner IP
header’s ToS bits to be copied to the outer IP packet header for traffic originating in the Routing Engine.
To verify that this option is enabled at the interface level, use the show interfaces interface-name detail
comman... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2.
Support for GRE interfaces for Generalized MPLS (GMPLS) introduced in Junos OS Release 12.3R7. | [
"Configuring a GRE Tunnel to Copy ToS Bits to the Outer IP Header"
] |
copy-tos-to-outer-ip-header-transit | copy-tos-to-outer-ip-header-transit; | [edit interfaces gr-fpc/pic/port unit logical-unit-number] | For static IPv4 GRE tunnel interfaces on MPCs, copy the inner IP header’s ToS bits to the outer IP
packet header for traffic transiting the router.
Default
If you omit this statement, the ToS bits in the outer IP header are set to 0. | [] | 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. | [] |
core-dump | (core-dump | no-core-dump); | [edit interfaces mo-fpc/pic/port multiservice-options] | A useful tool for isolating the cause of a problem. Core dumping is enabled by default. The
directory /var/tmp contains core files. Junos OS saves the current core file (0) and the four previous core
files, which are numbered from 1 through 4 (from newest to oldest):
NOTE: By default, all members of a configured user g... | [] | 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 Flow Monitoring"
] |
core-facing | core-facing; | [edit interfaces interface-name unit logical-unit-number family family] | Specifies that the VLAN is physically connected to a core-facing ISP router and ensures that the network
does not improperly treat the interface as a client interface. When specified, the interface is inserted
into the core-facing default mesh group where traffic from pseudowires that belong to the default mesh
group i... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1.
Support for EVPN-MPLS on PTX Series routers added in Junos OS Evolved Release 23.1R1. | [
"Junos OS Subscriber Management and Services Library",
"Tunnel Services Overview",
"Tunnel Interface Configuration on MX Series Routers Overview"
] |
corouted-bidirectional | corouted-bidirectional; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name] | Specify that the label-switched path be established as a corouted bidirectional packet LSP. You cannot
configure this statement at the same time as the corouted-bidirectional-passive statement.
Default
This statement 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 12.2. | [
"Configuring Corouted Bidirectional LSPs"
] |
corouted-bidirectional-passive | corouted-bidirectional-passive; | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls label-switched-path lsp-name] | Specify that the label-switched path be a passive LSP associated with a bidirectional LSP when it is
signaled at the ingress router. This passive LSP enables the MPLS application to utilize the reverse LSP.
You cannot configure this statement at the same time as the corouted-bidirectional statement.
Default
This statem... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring Corouted Bidirectional LSPs"
] |
corrupt-file | corrupt-file (block | log-and-permit); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name fallback-
options] | Corrupt file is the error returned by the scan engine when engine detects a corrupted file. The default
action is log-and-permit. | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Kaspersky antivirus feature is not supported from Junos OS Release 15.1X49-D10 onwards. For
previous releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Full Antivirus Configuration Overview"
] |
cos-rule-sets (Service Set Next Gen Services) | cos-rule-sets [cos-rule-set-name]; | [edit services service-set service-set-name] | Specify the services CoS rule set to apply to the service set. The service set processes the rules in the
order they appear in the rule set.
The service set that the CoS rule set is assigned to must include at least one stateful firewall rule or NAT
rule, or CoS does not work. Only stateful firewall and NAT rules can b... | [
{
"name": "cos-rule-set-name",
"desc": "Name of the services CoS rule set."
}
] | system—To view this statement in the configuration.
system-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)"
] |
cos-rules (Service Set Next Gen Services) | cos-rules [cos-rule-name]; | [edit services service-set service-set-name] | Specify the CoS rules to apply to the service set. You can configure multiple rules.
The service set that the CoS rule is assigned to must include at least one stateful firewall rule or NAT
rule, or CoS does not work. Only stateful firewall and NAT rules can be used with CoS rules in a service
set. | [
{
"name": "cos-rule-name",
"desc": "CoS rule name."
}
] | system—To view this statement in the configuration.
system-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)"
] |
cos-rules (Service Set) | cos-rules [cos-rule-name]; | [edit services service-set service-set-name] | Specify the CoS rules to apply to the service set. You can configure multiple rules.
The service set that the CoS rule is assigned to must include at least one stateful firewall rule or NAT
rule, or CoS does not work. Only stateful firewall and NAT rules can be used with CoS rules in a service
set. | [
{
"name": "cos-rule-name",
"desc": "CoS rule 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.1. | [
"Configuring CoS Rules"
] |
cost | cost cost; | [edit logical-systems logical-system-name protocols (mstp | rstp | vstp) interface interface-name],
[edit logical-systems logical-system-name protocols mstp msti msti-id interface interface-name],
[edit logical-systems logical-system-name protocols vstp vlan vlan-id interface interface-name],
[edit logical-systems logi... | For Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol
(VSTP), or Multiple Spanning Tree Protocol (MSTP), configure the link cost to control which bridge is the
designated bridge and which interface is the designated interface.
Default
The link cost is determined by the link ... | [
{
"name": "cost",
"desc": "(Optional) Link cost associated with the port."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.4.
Statement updated in Junos OS Release 9.4 for EX Series switches to add VSTP support.
Support for logical systems added in Junos OS Release 9.6. | [
"Understanding Spanning-Tree Instance Interfaces",
"Understanding STP",
"Understanding RSTP",
"Understanding MSTP"
] |
count (HTTP Header Enrichment) | count; | [edit services hcm tag-rule rule-name term term-number then] | Enable the collection of statistics for HTTP header enrichment for the tag rule term. The collection of
statistics for a term is disabled by default. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview",
"Configuring Tag Rules",
"Configuring HCM Profiles and Assigning Tag Rules",
"Junos Web Aware HTTP Header Enrichment Overview"
] |
count (Protocols PIM) | count number; | [edit protocols pim interface (Protocols PIM) interface-name multiple-triggered-joins
] | Specify the count for the number of triggered joins to be sent between PIM neighbors through the PIM
interface. Optionally, you can configure the count number using the count statement at the [edit protocols
pim interface interface-name multiple-triggered-joins] hierarchy level.
•
Range: 5 through 15
•
Default: 5 | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1R1. | [] |
count (Security Custom Attack) | count count-value; | [edit security idp custom-attack attack-name time-binding] | Specify the number of times that IDP detects the attack within the specified scope before triggering an
event. | [
{
"name": "count-value",
"desc": "Number of times IDP detects the attack."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
count (Security Policies) | count; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then] | Enable a count, in bytes or kilobytes, of all network traffic the policy allows to pass through the device in
both directions: the originating traffic from the client to the server (from the from-zone to the to-zone),
and the return traffic from the server to the originating client. | [] | 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. Statement updated in Junos OS Release 12.1X47-D10. | [
"Security Policies Overview"
] |
count | count number; | [edit access profile profile-name client-name-filter client-name] | Specify the number of characters to be stripped from a client name, from right to left, until the specified
number of characters are deleted. The resulting name is sent to the authentication server. | [
{
"name": "number",
"desc": "Number of characters to be stripped in a client name."
}
] | access—To view this statement in the configuration.
access-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS. | [
"Obtaining Username and Role Information Through Firewall Authentication"
] |
counter | counter {
counter-id counter-index;
} | [edit firewall policer policer-name] | (On EX8200 switches only) Configure a policer counter. | [
{
"name": "counter-id counter-index",
"desc": "Global management counter ID."
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Configuring Policers to Control Traffic Rates (CLI Procedure)",
"Configuring Firewall Filters (CLI Procedure)",
"Understanding the Use of Policers in Firewall Filters"
] |
counter-profiles | custom-profiles {
counter-profiles <counter-profile-name> {
app {
<app-name> {
counter-4k <num-of-counter-engines>
counter-8k <num-of-counter-engines>
counter-16k <num-of-counter-engines>
}
}
} | [edit system packet-forwarding-options] | storm-control
Storm control support
voq
HQoS statistics
tcam-ingress
TCAM related statistics support for ingress direction
- used by firewall filters
perf-mon-ingress
Twamp, inline sFlow functionality related support for
ingress direction
ifl-ingress
IFL statistics support for ingress direction
policer-ingress
Policer ... | [
{
"name": "counter-profiles counter-profile-name",
"desc": "Specify the name of the counter profile"
},
{
"name": "app app-name",
"desc": "In a counter profile, specify the application name that will utilize the counter"
}
] | 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.3R1 on ACX7100-32C, ACX7100-48L,ACX7332,
ACX7348, ACX7509, ACX7024, and ACX7024X | [] |
counters | counters {
counter-name;
} | [edit accounting-options filter-profile profile-name] | Names of counters for which filter profile statistics are collected. The packet and byte counts for the
counters are logged to a file in the /var/log directory. | [
{
"name": "counter-name",
"desc": "Name of the counter."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Counters"
] |
cpu (resource-manager) | cpu {
disable-management;
match {
threshold threshold;
}
then {
alarm;
drop-cps;
drop-flows;
log;
max-session-setup-rate max-session-setup-rate;
}
} | [edit security resource-manager] | Configure resource manager cpu options to control cpu load. Resource manager takes protective action
when the traffic load reaches the threshold. | [] | security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [
"Traffic Processing on SRX Series Devices Overview"
] |
cpu (TDF Gateway) | cpu cpu-pct; | [edit unified-edge gateways tdf gateway-name cac] | Configure the threshold for the maximum amount of CPU that the TDF gateway can use. If the amount
of CPU that the TDF gateway uses reaches the threshold, the SNMP trap jnxScgSMCPUThreshHigh is
generated. | [
{
"name": "cpu-pct",
"desc": "Maximum percentage of CPU. Range: 1 through 90."
}
] | 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 a TDF Gateway"
] |
cpu | cpu {
reserved percent;
} | [edit system security-profile] | Specify the percentage of CPU utilization that is always available for a logical system. The available CPU
space percentage value is configured in a security profile that is bound to a logical system.
Only the primary administrator can create security profiles and bind them to logical systems.
NOTE: The cpu-control opt... | [
{
"name": "reserved percent",
"desc": "A reserved quota that guarantees that the percentage of CPU specified is always"
}
] | 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. | [
"Understanding Logical Systems Security Profiles (Primary Administrators Only)"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.