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 |
|---|---|---|---|---|---|---|---|
client-negotiation-match (DHCPv6 Relay Agent) | client-negotiation-match incoming-interface; | [edit forwarding-options dhcp-relay dhcpv6 overrides],
[edit forwarding-options dhcp-relay dhcpv6 group group-name overrides],
[edit forwarding-options dhcp-relay dhcpv6 group group-name interface interface-name overrides] | Configure the match criteria the DHCPv6 relay agent uses to uniquely identify IPv6 subscribers or
clients. | [
{
"name": "incoming-interface",
"desc": "Allow only one client device to connect on the interface. If the client device changes, the router deletes the existing client binding and creates a binding for the newly connected device."
}
] | 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. | [
"Automatically Logging Out DHCPv6 Clients",
"Extended DHCP Relay Agent Overview",
"Allowing Only One DHCP Client Per Interface"
] |
client-response-ttl | client-response-ttl number; | [edit forwarding-options helpers bootp],
[edit forwarding-options helpers bootp interface (interface-name | interface-group)] | Set the IP time-to-live (TTL) value in BOOTP response messages sent to a BOOTP client. If you do not
include the client-response-ttl statement, the default is to leave the TTL field unchanged. | [
{
"name": "number",
"desc": "IP time-to-live (TTL) value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.1. | [
"Configuring Routers, Switches, and Interfaces as DHCP and BOOTP Relay Agents"
] |
client-session-timeout (Access Profile) | client-session-timeout minutes; | [edit access profile profile-name session-options] | Specify the amount of time after which user sessions are terminated, regardless of user activity (also
known as a forced or hard authentication timeout). | [
{
"name": "minutes",
"desc": "Number of minutes after which user sessions are terminated."
}
] | 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"
] |
client-type (Subscriber Limits) | client-type (any | dhcp | l2tp | pppoe) {
chassis {
limit limit;
}
fpc slot-number {
limit limit;
pic number {
limit limit;
port number {
limit limit;
}
}
}
} | [edit system services resource-monitor subscribers-limit] | Configure the maximum number of subscribers of the client type that are allowed to be logged in. You
can configure limits for subscribers per chassis, per MPC, per MIC, and per port. When the configured
maximum number of subscribers is logged in for any level, subsequent logins at that level are denied
until the curren... | [
{
"name": "name",
"desc": "Type of client for which subscriber limits are configured. Values:"
},
{
"name": "any",
"desc": "Apply the limit to the sum of all DHCP, L2TP, and PPPoE clients."
},
{
"name": "dhcp",
"desc": "Apply the limit to DHCP clients."
},
{
"name": "l2tp",
... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R1. | [
"Limiting Subscribers by Client Type and Hardware Element with Resource Monitor",
"Resource Monitoring for Subscriber Management and Services"
] |
client-type | client-type (autoconfig | stateful); | [edit interfaces interface-name unit logical-unit-number family inet6 dhcpv6-client]
[edit logical-systems logical -system-name interfaces interface-name unit logical-unit-number
family inet6 dhcpv6-client]
[edit tenants tenant-name interfaces interface-name unit logical-unit-number family inet6 dhcpv6-
client] | The type of DHCPv6 client. | [
{
"name": "autoconfig",
"desc": "Autoconfig client type for router advertisement"
},
{
"name": "stateful",
"desc": "Stateful client type for address assignment"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X45-D10.
The logical-systems and tenants options are introduced in Junos OS Release 18.4R1. | [
"DHCPv6 Client Overview"
] |
clients (Security) | clients configuration-name {
ipsec-vpn vpn-name;
remote-exceptions ip-address/mask;
remote-protected-resources ip-address/mask;
user username;
user-groups user-group-name;
} | [edit security dynamic-vpn] | Create a client configuration for the dynamic VPN feature. Within the configuration, specify a name for
the configuration, reference a standard VPN configuration to use for IPsec negotiations, specify which
resources to protect, define any exceptions, and list the users to which the dynamic VPN configuration
applies.
I... | [
{
"name": "configuration-name",
"desc": "Name of the client configuration."
},
{
"name": "ipsec-vpn",
"desc": "Use this statement to specify which IPsec VPN configuration the dynamic VPN feature should use to secure traffic."
},
{
"name": "remote-exceptions",
"desc": "Use this statem... | 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.
Statement user-groups introduced in Junos OS Release 12.1X44-D10. | [
"Dynamic VPN Overview"
] |
clients (SNMP Community) | clients {
address <restrict>;
} | [edit snmp communitycommunity community-name] | Specify the IPv4 or IPv6 addresses of the SNMP client hosts that are authorized to use this community.
Default
If you omit the clients statement, all SNMP clients using this community string are authorized to access
the router. | [
{
"name": "address",
"desc": "Address of an SNMP client that is authorized to access this router. You must specify an"
},
{
"name": "restrict",
"desc": "(Optional) Do not allow the specified SNMP client to access the router."
}
] | 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 SNMP Communities"
] |
clients | clients client-name {
accounting {
secret password;
response-cache-timeout seconds;
}
address client-address;
<prefer-framed-ip-address>
<prefer-framed-ipv6-prefix>
source-interface interface ipv4-address address;
} | [edit access radius] | Configure a RADIUS client for each GGSN, PGW, or BNG that sends subscriber session requests to the
MX Series router and identifies it as a RADIUS server. | [
{
"name": "client-name",
"desc": "Name for the client. Range: 1 through 50 alphanumeric characters. Allowed characters are a-z, A-Z, 0-9."
}
] | 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. | [
"Configuring RADIUS Clients That Send Accounting Requests for IP-Based Subscribers"
] |
clns-routing | clns-routing; | [edit protocols isis],
[edit routing-instances routing-instance-name protocols isis] | Enable IS-IS to exchange Connectionless Network Service (CLNS) routes. CLNS is a Layer 3 protocol,
similar to IPv4. CLNS uses network service access points (NSAPs) to address end systems and
intermediate systems. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring IS-IS for CLNS",
"Example: Configuring Static Routes for CLNS When No IGP is Present",
"Example: Configuring BGP for CLNS VPNs",
"Understanding BGP for CLNS VPNs",
"Understanding Static Routes for CLNS"
] |
clns-updown-compatibility | clns-updown-compatibility; | [edit logical-systems logical-system-name protocols isis],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
isis],
[edit protocols isis],
[edit routing-instances routing-instance-name protocols isis] | When you enable IS-IS to exchange Connectionless Network Service (CLNS) routes, Junos OS sets the
reserved (R) bit in the default metric field inside type, length, and value (TLV) type-3 (ES-Neighbor) as a
marker for routing loop prevention. Junos OS uses the up/down bit for marking prefixes on the Level 2-
to-Level 1 ... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4R7. | [
"Example: Configuring IS-IS for CLNS",
"Example: Configuring Static Routes for CLNS When No IGP is Present",
"Example: Configuring BGP for CLNS VPNs",
"Understanding BGP for CLNS VPNs",
"Understanding Static Routes for CLNS"
] |
clock-class | clock-class clock-class-value; | [edit protocols ptp client clock-class-to-quality-level-mapping ] | Configure the clock class to the set ESMC quality level.
Default
Following are the default clock class values for various clocks:
•
Boundary clock–248
•
Ordinary clock (timeTransmitter)–52
•
Ordinary clock (timeReceiver)–255 | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2R2. | [
"Configuring Hybrid Mode and ESMC Quality Level Mapping",
"Example: Configuring Hybrid Mode and ESMC Quality Level Mapping",
"Understanding Hybrid Mode",
"Precision Time Protocol Overview",
"Synchronous Ethernet Overview"
] |
clock-class-to-quality-level-mapping | clock-class-to-quality-level-mapping {
clock-class clock-class-value;
{
quality-level ql-value;
}
} | [edit protocols ptp slave] | Configure the timeReceiver to override the default Precision Time Protocol (PTP) clock class to Ethernet
Synchronization Message Channel (ESMC) mapping.
The remaining statements are explained separately. See CLI Explorer. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2R2. | [
"Configuring Hybrid Mode and ESMC Quality Level Mapping",
"Example: Configuring Hybrid Mode and ESMC Quality Level Mapping",
"Understanding Hybrid Mode",
"Precision Time Protocol Overview",
"Synchronous Ethernet Overview"
] |
clock-ipv6-client | clock-ipv6-client slave-ip-address; | [edit protocols ptp master interface interface-name unicast-mode transport ipv4] | Configure the IPv6 address of the timeReceiver. | [
{
"name": "slave-ip-address",
"desc": "The IPv6 address for the timeReceiver."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Precision Time Protocol",
"Example: Configuring Precision Time Protocol",
"Precision Time Protocol Overview"
] |
clock-ipv6-source | clock-ipv6-source master-ipv6-address {
local-ip-address local-ip-address;
} | [edit protocols ptp client interface interface-name unicast-mode transport] | Configure the IPv6 address of the timeTransmitter. | [
{
"name": "master-ipv6-address",
"desc": "IPv6 address for the timeTransmitter."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Precision Time Protocol",
"Example: Configuring Precision Time Protocol",
"Precision Time Protocol Overview"
] |
clock-mode (Clock Synchronization) | clock-mode (auto-select | free-run); | [edit chassis synchronization] | Configure the mode of operation to select the clock source from a free-run local oscillator or from an
external qualified clock. On MX240, MX480, and MX960 routers with enhanced MPCs, the free-run
clock is provided by a local oscillator. On other MX Series routers, the free-run clock is provided by the
SCB.
Default
aut... | [
{
"name": "auto-select",
"desc": "Select the best external clock source as a clock source."
},
{
"name": "free-run",
"desc": "Select the free-run local oscillator as a clock source."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2R4. | [] |
clock-mode | clock-mode (boundary | ordinary); | [edit protocols ptp] | Configure the clock mode as either boundary clock or ordinary clock. The clock mode determines
whether the node is going to act as a timeReceiver, or timeTransmitter, or both. This attribute is
mandatory and has no default value. | [
{
"name": "boundary",
"desc": "The clock mode of the node is a boundary clock where the clock acts as both timeTransmitter"
},
{
"name": "ordinary",
"desc": "The clock mode of the node is a system clock where the clock acts either as a timeTransmitter"
}
] | 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 Precision Time Protocol",
"Example: Configuring Precision Time Protocol",
"Precision Time Protocol Overview",
"IEEE 1588v2 Precision Timing Protocol (PTP)",
"Configuring the Precision Time Protocol G.8275.2 Enhanced Profile (Telecom Profile)"
] |
clock-rate | clock-rate rate; | [edit interfaces interface-name serial-options] | For EIA-530 and V.35 interfaces, configure the interface speed, in megahertz (MHz). | [
{
"name": "rate",
"desc": "You can specify one of the following rates:"
},
{
"name": "2.048 MHz",
"desc": ""
},
{
"name": "2.341 MHz",
"desc": ""
},
{
"name": "2.731 MHz",
"desc": ""
},
{
"name": "3.277 MHz",
"desc": ""
},
{
"name": "4.096 MHz",
"d... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Serial Clocking Mode"
] |
clock-source (hybrid) | clock-source ip-address {
interface interface1-name;
interface interface2-name;
} | [edit protocols ptp slave hybrid synchronous-ethernet-mapping] | Configure the IP address of the PTP timeTransmitter and its possible Synchronous Ethernet source
interfaces. | [
{
"name": "interface interface1-name",
"desc": "Synchronous Ethernet interface traceable to the same PTP timeTransmitter"
},
{
"name": "interface interface2-name",
"desc": "Synchronous Ethernet interface traceable to the same PTP timeTransmitter"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2R2. | [
"Configuring Hybrid Mode and ESMC Quality Level Mapping",
"Example: Configuring Hybrid Mode and ESMC Quality Level Mapping",
"Understanding Hybrid Mode",
"Precision Time Protocol Overview",
"Synchronous Ethernet Overview"
] |
clock-synchronization | clock-synchronization {
memory-logging {
clksyncd {
file-dump-on-wrap;
memory-log-disable;
}
lc-clocking {
file-dump-on-wrap;
memory-log-disable;
}
timingd-re {
file-dump-on-wrap;
memory-log-disable;
... | [edit logical-systems name protocols],
[edit protocols] | Configuring parameters common to SyncE and PTP | [
{
"name": "memory-logging",
"desc": "Trace options for timing modules"
},
{
"name": "timing-events-extended",
"desc": "Enable extended timing events"
}
] | routing-To view this statement in the configuration.
Release Information | [] | |
clocking-mode | clocking-mode (dce | internal | loop); | [edit interfaces interface-name serial-options] | For EIA-530 and V.35 interfaces, configure the clock mode. You cannot configure clocking-mode dce on a
DTE router using an X.21 serial line protocol (detected automatically when an X.21 cable is plugged into
the serial interface). | [
{
"name": "dce",
"desc": "DCE timing (DTE mode only, not valid for X.21)."
},
{
"name": "internal",
"desc": "Internal baud timing."
},
{
"name": "loop",
"desc": "Loop timing."
}
] | 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 Clocking Mode"
] |
close-timeout | close-timeout seconds; | [edit interfaces interface-name services-options]
[edit services service-set service-set-name service-set-options tcp-session | Configure the timeout period for Transmission Control Protocol (TCP) session tear-down. | [
{
"name": "seconds",
"desc": "Timeout period. Default: 1 second Range: 2 through 300 seconds"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3.
Support for Next Gen Services added in Junos OS Release 19.3R2 on MX Series MX240, MX480 and
MX960 using MX-SPC3 services card. | [
"Configuring Default Timeout Settings for Services Interfaces"
] |
cluster (Chassis) | cluster {
configuration-synchronize (Chassis Cluster) {
no-secondary-bootup-auto;
}
control-interface {
node name {
disable;
}
}
control-link-recovery;
control-ports fpc {
port;
}
health-monitoring;
heartbeat-interval milliseconds;
hear... | [edit chassis] | 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": "configuration-synchronize",
"desc": "Disable automatic chassis cluster synchronization. See \"configuration-synchronize (Chassis Cluster)\" on page 4755."
},
{
"name": "control-interface",
"desc": "Disable and Enable chassis cluster control-link interface on SRX1500, SRX4100, SRX4200,... | 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.
The health-monitoring option is introduced in Junos OS Release 18.4R1.
The control-interface option is introduced in Junos OS Release 20.4R1 for SRX1500 devices.
The Redundancy mode option is introduced in Junos OS Release 24.4R1. | [] |
cluster (Junos Fusion) | cluster cluster-name{
cascade-ports interface-name;
cluster-id cluster-id-number;
fpc slot-id{
alias alias;
description description;
member-id member-id-number;
system-id mac-address;
}
} | [edit chassis satellite-management ] | Create and name a satellite device cluster.
Default
Satellite device clusters are not present, by default. | [
{
"name": "cluster-name",
"desc": "Specifies the name of the satellite device cluster. 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 16.1R1. | [
"Configuring or Expanding a Junos Fusion Enterprise"
] |
cluster | cluster cluster-identifier; | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp... | Specify the cluster identifier to be used by the route reflector cluster in an internal BGP group.
CAUTION: If you configure both route reflection and VPNs on the same routing device,
the following modifications to the route reflection configuration cause current BGP
sessions to be reset:
•
Adding a cluster ID—If a BG... | [
{
"name": "cluster-identifier",
"desc": "4-byte number (such as an IPv4 address)."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring BGP Route Reflectors",
"Understanding External BGP Peering Sessions"
] |
cluster-id (Junos Fusion Satellite Device Cluster) | cluster-id cluster-id-number; | [edit chassis satellite-management cluster cluster-name] | Assign a cluster identification number to a satellite device cluster in a Junos Fusion.
The cluster identification number is used to identify a satellite device cluster in a Junos Fusion.
Default
Cluster identification numbers are not assigned in a Junos Fusion, by default. | [
{
"name": "cluster-id-number",
"desc": "Specifies the cluster identification number of the satellite device cluster in the Junos Fusion."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R1. | [
"Configuring or Expanding a Junos Fusion Enterprise"
] |
cluster-id (Protocols PIM) | cluster-id identifier; | [edit dynamic-profiles name protocols pim],
[edit logical-systems name protocols pim],
[edit logical-systems name routing-instances name protocols pim],
[edit logical-systems name tenants name routing-instances name protocols pim],
[edit protocols pim],
[edit routing-instances name protocols pim],
[edit tenants name ro... | Configure a cluster indentifier. It is a 32-bit non-zero identifier used to group a set of PIM nodes in a
cluster. A complex PIM topology can be divided into clusters of PIM nodes based on different colors.
•
Range: 1 through 4294967295 | [
{
"name": "private-tlv",
"desc": "Enable use of private TLVs for interoperability with other vendors."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 25.2R1. | [
"Hash-based PIM RPF Selection"
] |
cmcast-joins-limit-inet (MVPN Selective Tunnels) | cmcast-joins-limit-inet number; | [edit logical-systems logical-system-name routing-instances instance-name provider-tunnel
selective],
[edit routing-instances instance-name provider-tunnel selective] | Configure the maximum number of IPv4 customer multicast entries
The purpose of the cmcast-joins-limit-inet statement is to supplement the multicast forwarding-cache
limit when the MVPN rpt-spt mode is configured and when traffic is flowing through selective service
provider multicast service interface (S-PMSI) tunnels... | [
{
"name": "number",
"desc": "Maximum number of customer multicast entries for IPv4."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Examples: Configuring the Multicast Forwarding Cache",
"Example: Configuring MBGP Multicast VPN Topology Variations"
] |
cmcast-joins-limit-inet6 (MVPN Selective Tunnels) | cmcast-joins-limit-inet6 number; | [edit logical-systems logical-system-name routing-instances instance-name provider-tunnel
selective],
[edit routing-instances instance-name provider-tunnel selective] | Configure the maximum number of IPv6 customer multicast entries
The purpose of the cmcast-joins-limit-inet6 statement is to supplement the multicast forwarding-cache
limit when the MVPN rpt-spt mode is configured and when traffic is flowing through selective service
provider multicast service interface (S-PMSI) tunnels... | [
{
"name": "number",
"desc": "Maximum number of customer multicast entries."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3. | [
"Examples: Configuring the Multicast Forwarding Cache",
"Example: Configuring MBGP Multicast VPN Topology Variations"
] |
coa-accounting (AAA Profile) | coa-accounting (enable | disable); | [edit unified-edge aaa profiles aaa-profile-name radius policy] | Enable or disable the initiation of a RADIUS accounting start from the MX Series router to the RADIUS
server. Enabling this feature is required if the RADIUS server cannot initiate a change of authorization
request without an accounting record. Specifying enable does not cause the MX Series router to report
any billing... | [
{
"name": "enable",
"desc": "Initiate a RADIUS accounting start from the MX Series Router to the RADIUS server."
},
{
"name": "disable",
"desc": "Do not initiate a RADIUS accounting start from the MX Series Router to the RADIUS server."
}
] | 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"
] |
coa-immediate-update | coa-immediate-update; | [edit access profile profile-name accounting] | Configure the router to send an Acct-Update message to the RADIUS accounting server immediately
following a CoA operation. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. | [
"RADIUS Servers and Parameters for Subscriber Access",
"Configuring Per-Subscriber Session Accounting"
] |
coa-no-override service-class-attribute | coa-no-override service-class-attribute; | [edit access profile profile-name accounting] | Specify that, after a CoA action that changes the RADIUS Class attribute, accounting reports for the
subscriber’s service sessions continue to use the original Class attribute that was assigned when the
service sessions were created. The new Class attribute value is used in accounting reports for the
subscriber session... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"RADIUS Servers and Parameters for Subscriber Access",
"Configuring Per-Subscriber Session Accounting"
] |
code (AAA Profile) | code numeric-code; | [edit unified-edge aaa profiles aaa-profile-name radius policy activation-attribute],
[edit unified-edge aaa profiles aaa-profile-name radius policy deactivation-attribute] | Configure the RADIUS attributes that you want to carry the PCC rulebase name for rulebase activations
and deactivations from the RADIUS policy server to the MX Series router. By default, the rulebase name
is carried in the ERX-Service-Activate Juniper vendor-specific attribute (VSA) for activations and in the
ERX-Servi... | [
{
"name": "numeric-code",
"desc": "Numeric value for the RADIUS AVP."
}
] | 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"
] |
code (Application Identification) | code icmp-code; | [edit services application-identification application application-name icmp-mapping] | Match the specified ICMP code to create a custom application signature. | [
{
"name": "value",
"desc": "Numeric value for the ICMP code. Range: 0 through 254"
}
] | 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"
] |
code (IDP) | code {
match (equal | greater-than | less-than | not-equal);
value code-value;
} | [edit security idp custom-attack attack-name attack-type signature protocol icmp],
[edit security idp custom-attack attack-name attack-type signature protocol icmpv6] | Specify the secondary code that identifies the function of the request/reply within a given type. | [
{
"name": "match (equal | greater-than | less-than | not-equal)",
"desc": "Match an operand."
},
{
"name": "value code-value",
"desc": "Match a decimal value."
}
] | 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. Statement modified in Junos OS Release 12.3X48-D25
to add ICMPv6 protocol support. | [] |
code | code numeric-code; | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from attribute name] | Specify the custom attribute’s AVP code for the incoming RADIUS request from the subscriber.
After this criterion and the other match criteria specified for the TDF domain or PCEF profile selection
term are matched, the specified TDF domain or PCEF profile is selected. | [
{
"name": "numeric-code",
"desc": "Numeric value for the code. Range: 0 through 255."
}
] | unified-edge—To view this statement in the configuration.
unified-edge-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Assignment of TDF Subscriber Properties and Policy-Control Properties to IP-Based",
"Subscribers",
"Understanding Selection of Properties for an IP-Based TDF Subscriber",
"Understanding Selection of Policy-Control Properties for an IP-based TDF Subscriber",
"IP-Based Subscriber Setup Overview"
... |
code-point (Congestion Notification) | code-point up-bits pfc; | [edit class-of-service congestion-notification-profile profile-name input ieee-802.1],
[edit class-of-service interfaces interface-name congestion-notification-profile profile-name
input ieee-802.1] | Configure the IEEE 802.1p (User Priority) code point bits as input for creating the priority-based flow
control (PFC) congestion notification profile, which you will associate with a particular traffic class. | [
{
"name": "pfc",
"desc": "PFC flow control method"
},
{
"name": "up-bits",
"desc": "Three-bit pattern of the User Priority field in an IEEE 802.1Q tag"
}
] | 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 FCoE Transit Switch",
"Configuring Priority-Based Flow Control for an EX Series Switch (CLI Procedure)"
] |
code-point (Fibre Channel Interfaces) | code-point code-point-bits; | [edit class-of-service interfaces fibre-channel-interface-name rewrite-value input ieee-802.1] | Configure the IEEE 802.1p code point value assigned to all traffic received from the Fibre Channel (FC)
network on the specified FC interface (NP_Port). When native FC traffic from the FC SAN arrives at the
NP_Port interface, the NP_Port interface encapsulates it in Ethernet to create FCoE packets before
forwarding the... | [
{
"name": "code-point-bits",
"desc": "Value of the code-point bits, in decimal form."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | [
"Example: Configuring IEEE 802.1p Priority Remapping on an FCoE-FC Gateway",
"Understanding CoS IEEE 802.1p Priority Remapping on an FCoE-FC Gateway",
"Understanding CoS Classifiers"
] | |
code-point (Input Congestion Notification) | code-point [code-point-bits] {
pfc {
mru mru-value;
}
xon
} | [edit class-of-service congestion-notification-profile profile-name input dscp],
[edit class-of-service congestion-notification-profile profile-name input ieee-802.1] | Enable priority-based flow control (PFC) on an IEEE 802.1p code point (priority) or a Differentiated
Services code point (DSCP) value (to implement DSCP-based PFC at Layer 3).
Use this statement to configure PFC to operate based on an IEEE 802.1p code point in the VLAN-
tagged packet header at Layer 2, or on a DSCP val... | [
{
"name": "code-point-bits",
"desc": "Code point bit pattern corresponding to an IEEE 802.1p 3-bit priority value when used"
}
] | 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.
Support for DSCP values introduced in Junos OS Release 17.4R1 for the QFX Series. | [
"Example: Configuring CoS PFC for FCoE Traffic",
"Configuring CoS PFC (Congestion Notification Profiles)",
"Understanding CoS Flow Control (Ethernet PAUSE and PFC)",
"Understanding PFC Using DSCP at Layer 3 for Untagged Traffic",
"Configuring DSCP-based PFC for Layer 3 Untagged Traffic"
] |
code-point (Output Congestion Notification) | code-point [ code-point-bits ] {
flow-control-queue [ queue | list-of-queues ];
} | [edit class-of-service congestion-notification-profile profile-name output ieee-802.1] | Specify the IEEE 802.1p code point bits that identify the traffic you want to enable for priority-based
flow control (PFC) pause.
Default
By default, IEEE 802.1p priorities 3 and 4 (code points 011 and 100, respectively) are enabled for PFC
pause on all Ethernet interfaces. If you explicitly configure priorities to pau... | [
{
"name": "code-point-bits",
"desc": "3-bit value in decimal form."
}
] | interfaces—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.3. | [
"Configuring CoS PFC (Congestion Notification Profiles)",
"Example: Configuring Two or More Lossless FCoE IEEE 802.1p Priorities on Different FCoE Transit",
"Switch Interfaces",
"Example: Configuring Two or More Lossless FCoE Priorities on the Same FCoE Transit Switch",
"Interface",
"Example: Configuring ... |
code-point (Rewrite Rules) | code-point [ alias ] [ bit-pattern ]; | [edit class-of-service rewrite-rules (dscp | ieee-802.1) forwarding-class class-name loss-priority
level] | Configure a code-point alias or bit set to apply to a forwarding class for a rewrite rule. | [
{
"name": "alias",
"desc": "Name of the alias."
},
{
"name": "bit-pattern",
"desc": "Value of the code-point bits, in decimal form."
}
] | 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. | [
"Defining CoS Rewrite Rules",
"Understanding CoS Classifiers",
"Understanding CoS Classifiers"
] |
code-point | code-point [ aliases ] [ bit-patterns ]; | [edit class-of-service rewrite-rules type rewrite-name forwarding-class class-name] | Specify one or more code-point aliases or bit sets for association with a forwarding class. | [
{
"name": "aliases",
"desc": "Name of each alias."
},
{
"name": "bit-patterns",
"desc": "Value of the code-point bits, in decimal form."
}
] | 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 Rewrite Rules"
] |
code-point-aliases | code-point-aliases {
type {
alias-name bits;
}
} | [edit class-of-service] | Define an alias for a CoS marker. You can use the alias instead of the bit pattern when you specify the
code point during configuration. | [
{
"name": "alias-name",
"desc": "Name of the code-point alias."
},
{
"name": "bits",
"desc": "6-bit value of the code-point bits, in decimal form."
},
{
"name": "type",
"desc": "CoS marker type."
}
] | 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. | [
"Defining Aliases for CoS Value Bit Patterns"
] |
code-points (Application Maps) | code-points [ aliases ] [ bit-patterns ]; | [edit policy-options application-maps application-map-name application application-name] | Define one or more code-point aliases or bit sets for an application. | [
{
"name": "aliases",
"desc": "Name of the alias or aliases."
},
{
"name": "bit-patterns",
"desc": "Value of the code-point bits, in decimal form."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Configuring an Application Map for DCBX Application Protocol TLV Exchange",
"Example: Configuring DCBX Application Protocol TLV Exchange",
"Example: Configuring DCBX to Support an iSCSI Application",
"Understanding DCBX Application Protocol TLV Exchange",
"Understanding DCBX Application Protocol TLV Exchan... |
code-points (Classifiers) | code-points ([ aliases ] | [ bit-patterns ]); | [edit class-of-service classifiers type classifier-name forwarding-class class-name loss-
priority level] | Specify one or more DSCP code-point aliases or bit sets to apply to a forwarding class. | [
{
"name": "aliases",
"desc": "Name of the DSCP alias."
},
{
"name": "bit-patterns",
"desc": "Value of the code-point bits, in six-bit binary form."
}
] | 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. | [
"Understanding Interfaces",
"Understanding How Behavior Aggregate Classifiers Prioritize Trusted Traffic",
"Example: Configuring Behavior Aggregate Classifiers",
"Example: Configuring BA Classifiers on Transparent Mode Security Devices"
] |
collapsed-forward | collapsed-forward (monitor | optimize); | [edit chassis network-slices guest-network-functions gnf id af-name] | Configure a fabric path optimization mode to optimize the fabric path of the traffic flowing over
abstracted fabric (af) interfaces between two guest network functions (GNFs). After configuring fabric
path optimization, you can use the command show interfaces af-interface-name in GNF to view the number
of packets that ... | [
{
"name": "monitor",
"desc": "If you configure this mode, the peer GNF monitors the traffic flow and sends information to the source GNF about the Packet Forwarding Engine to which the traffic is being forwarded currently and the desired Packet Forwarding Engine that could provide an optimized path. However... | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4R1. | [
"Understanding Junos Node Slicing"
] |
collector (Analytics) | collector {
local {
file filename {
size size;
files number;
}
}
address ip-address {
port number {
transport protocol {
export-profile profile-name;
}
}
}
} | [edit services analytics] | Configure a local file for storing network analytics statistics and/or a remote server for receiving
streamed statistics data.
NOTE: The collector statement is not available in Junos OS Releases prior to 13.2X51-
D15.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Network Analytics Overview"
] |
collector (Flow Collection) | collector interface-name; | [edit services flow-collector interface-map] | Configure the default flow collector interface for interface mapping. | [
{
"name": "interface-name",
"desc": "Default flow collector interface."
}
] | 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 Interface Mappings"
] |
collector (Flow Monitoring Logs for NAT) | collector collector-name {
source-ip address;
destination-address address;
destination-port port-number;
} | [edit services jflow-log] | Specify the name of the collector to which flow monitoring log messages in IPFIX or version 9 flow
template format for NAT events must be sent. The generated flow monitoring logs for NAT events in
flow template format are sent to the specified host or external device that functions as the NetFlow
collector. You must as... | [
{
"name": "collector-name",
"desc": "Name of the collector to which flow monitoring log messages for NAT events in flow"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding NAT Event Logging in Flow Monitoring Format on an MX Series Router or NFX250",
"Configuring Log Generation of NAT Events in Flow Monitoring Record Format on an MX Series",
"Router or NFX250",
"Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats",
"Exa... |
collector (Flow Template Profiles for NAT) | collector collector-name; | [edit services jflow-log template-profile template–profile-name] | Specify the name of the collector to be associated with a template profile. The generated flow
monitoring logs for NAT events in flow template format are sent to the specified collector. You must
have previously configured the collector by using the collector collector-name statement at the [edit
services jflow-log] hi... | [
{
"name": "collector-name",
"desc": "Name of the collector to which flow monitoring log messages for NAT events in flow"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding NAT Event Logging in Flow Monitoring Format on an MX Series Router or NFX250",
"Configuring Log Generation of NAT Events in Flow Monitoring Record Format on an MX Series",
"Router or NFX250",
"Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats",
"Exa... |
collector (Inline Monitoring) | collector collector-name {
destination-address destination-IP-address;
destination-port destination-port;
source-address source-IP-address;
} | [edit services inline-monitoring instance instance-name] | Configure an collector for inline monitoring. The monitored packets are exported to the collector in an
IPFIX format. The actual packet is exported in an IPFIX format up to the configured clip length. By
default, Junos OS supports a maximum packet length of 126 bytes, starting with the Ethernet header.
The IPFIX format... | [
{
"name": "collector-name",
"desc": "Name of the collector."
},
{
"name": "destination-address",
"desc": ""
},
{
"name": "destination-IP-address",
"desc": "IPv4 destination IP address."
},
{
"name": "destination-port",
"desc": ""
},
{
"name": "destination-port-num... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS 19.4R1.
Statement introduced in Junos Evolved OS Release 22.2R1. | [
"Understanding Inline Monitoring Services"
] |
collector (LRF Profile) | collector collector-name {
destination {
address collector-address;
port collector-port-number;
}
source-address source-address;
} | [edit services lrf profile profile-name] | Configure a collector that receives logging and reporting data. This collector can be specified in LRF
rules. | [
{
"name": "collector-name",
"desc": "Name for the collector. Range: Up to 32 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.
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"
] |
collector (LRF Rule) | collector collector-name; | [edit services lrf profile profile-name rule lrf-rule-name then report] | Specify the collector that receives the data if the LRF rule is matched. | [
{
"name": "collector-name",
"desc": "Name of the collector that receives the data. The referenced collector must already be defined at the [edit services lrf profile profile-name] hierarchy level."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support for Next Gen Services introduced in Junos OS Release 19.3R1 on MX Series. | [
"Configuring Logging and Reporting for Junos OS Subscriber Aware",
"Configuring an LRF Profile for Subscribers",
"Configuring Logging and Reporting for Subscriber Management"
] |
collector | PTX10016, QFX5230-64CD, QFX5240-64OD, and QFX5240-64QD)
collector ip-v4/v6-address {
dscp dscp;
forwarding-class forwarding-class;
routing-instance routing-instance name;
udp-port port-number;
} | [edit protocols sflow] | Configure a remote collector for sFlow network traffic monitoring. The device sends sFlow UDP
datagrams to this collector for analysis. You can configure up to four collectors on the device. You
configure a collector by specifying its IP address and a UDP port. | [
{
"name": "dscp dscp",
"desc": "Configure Differentiated Services Code Point (DSCP) values per collector. These values are applied to all the packets destined for that collector. A change in the DSCP configuration resets all the counters for the collector and the new configuration comes into effect."
},
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3.
dscp and forwarding-class options introduced in Junos OS Release 19.1R1.
routing-instance options introduced in Junos OS Evoloved Release 24.2R1. | [
"Example: Configuring sFlow Technology to Monitor Network Traffic on EX Series Switches",
"Configuring sFlow Technology for Network Monitoring (CLI Procedure)",
"Example: Configuring sFlow Technology to Monitor Network Traffic on MX Series Routers"
] |
collector-group (Flow Monitoring Logs for NAT) | collector-group collector-group-name {
[collector-name1 collector-name2];
} | [edit services jflow-log] | Specify the name of the collector group that contains a set of NetFlow collectors to which flow
monitoring log messages in IPFIX or version 9 flow template format for NAT events must be sent. You
must define at least one collector in the group. A maximum of up to eight collectors can be aggregated
into a collector grou... | [
{
"name": "collector-group-name",
"desc": "Name of the collector group to which flow monitoring log messages for NAT events"
},
{
"name": "collector-name",
"desc": "Name of the collector to be assigned to the group of collectors. You must have previously"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding NAT Event Logging in Flow Monitoring Format on an MX Series Router or NFX250",
"Configuring Log Generation of NAT Events in Flow Monitoring Record Format on an MX Series",
"Router or NFX250",
"Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats",
"Exa... |
collector-group (Flow Template Profiles for NAT) | collector-group collector-group-name; | [edit services jflow-log template-profile template–profile-name] | Specify the name of the collector group to be associated with a template profile. The generated flow
monitoring logs for NAT events in flow template format are sent to the specified collector group. By
using a collector group, you can effectively and optimally transmit flow monitoring logs to a cluster of
collectors in... | [
{
"name": "collector-group-name",
"desc": "Name of the collector group to which log messages for NAT events in flow"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1. | [
"Understanding NAT Event Logging in Flow Monitoring Format on an MX Series Router or NFX250",
"Configuring Log Generation of NAT Events in Flow Monitoring Record Format on an MX Series",
"Router or NFX250",
"Monitoring NAT Events on MX Series Routers by Logging NAT Operations in Flow Template Formats",
"Exa... |
color | color {
metric-value;
<type metric_type>
} | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options (aggregate | generate | static) (defaults | route)],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name (aggregate | generate | static) (defaults | ro... | Fine-grained preference value for a static, aggregate, or generated route.
You can also specify a primary route preference (by including the color statement in the configuration),
and a secondary preference that is used as a tiebreaker (by including the color2 statement). You can also
mark route preferences with additi... | [
{
"name": "metric_value",
"desc": "The metric value for an aggregate, a generated, or a static route."
},
{
"name": "type metric_type",
"desc": "(Optional) External metric type for routes exported by OSPF. When routes are"
}
] | 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.
Statement introduced in Junos OS Release 9.0. | [
"Example: Summarizing Static Routes Through Route Aggregation"
] |
color-aware | color-aware; | [edit firewall three-color-policer policer-name single-rate],
[edit firewall three-color-policer policer-name two-rate] | Configure the way preclassified packets are metered. In color-aware mode, the switch can assign a
higher packet-loss priority, but cannot assign a lower packet loss priority (PLP). For example, suppose an
upstream device assigns medium-high PLP to a packet because the packet exceeded its committed
information rate (CIR... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Overview of Policers",
"Understanding Color-Aware Mode for Single-Rate Tricolor Marking",
"Understanding Color-Aware Mode for Two-Rate Tricolor Marking"
] |
color-blind | color-blind; | [edit dynamic-profiles profile-name firewall three-color-policer name single-rate],
[edit dynamic-profiles profile-name firewall three-color-policer name two-rate],
[edit firewall three-color-policer policer-name single-rate],
[edit firewall three-color-policer policer-name two-rate] | For a three-color policer, configure the way preclassified packets are metered. In color-blind mode, the
local router ignores the preclassification of packets and can assign a higher or lower packet loss priority.
For example, suppose an upstream router assigned medium-high packet loss priority to a packet because
the ... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4.
Support at the [edit dynamic-profiles ... single-rate] and [edit dynamic-profiles ... two-rate] hierarchy
levels introduced in Junos OS Release 11.4. | [
"Three-Color Policer Configuration Overview",
"Color Modes for Three-Color Policers"
] |
colored-tunnel-address | colored-tunnel-address {
(inet | inet6);
} | [edit routing-instances name protocols evpn],
[edit routing-instances name vtep-source-interface (inet | inet6) | Colored tunnel address to be used as SVTEP address. When configured within an EVPN IP-VRF routing
instance, this statement supports EVPN Type 5 routes over a colored IP fabric. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 25.4R1. | [] |
command (Op Scripts) | command filename-alias; | [edit system scripts op file filename] | Configure a filename alias for an op script file. This allows you to run the op script by referencing either
the script filename or the filename alias. | [
{
"name": "filename-alias",
"desc": "Alias for the op script file."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Enabling an Op Script and Defining a Script Alias"
] |
commands (Event Policy Change Configuration) | commands {
"command";
} | [edit event-options policy policy-name then change-configuration] | Specify the configuration mode commands to execute when the corresponding event policy is triggered.
When the event policy is triggered upon receipt of the specified event or events, the event process
(eventd) invokes the configured commands to update the candidate configuration, which is then
committed, provided that ... | [
{
"name": "command",
"desc": "Configuration mode command to be executed. Enclose each command in quotation marks (\" \"), and specify the complete statement path to the element, identifier, or value as you do in configuration mode when issuing commands at the [edit] hierarchy level. The following configurat... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Configure an Event Policy to Change the Configuration"
] |
commands (Event Policy Execute Commands) | commands {
"command";
} | [edit event-options policy policy-name then execute-commands] | Specify the operational mode commands to be issued when the corresponding event policy is triggered.
When the event policy is triggered, the event process (eventd) executes the commands in the order in
which they appear in the event policy configuration.
NOTE: If you include the op url command to execute a remote scrip... | [
{
"name": "command",
"desc": "Operational mode command to be executed. Enclose each command in quotation marks (\" \"). You can include variables in commands. The eventd process replaces each variable with values contained in the events that trigger the policy. You can use command variables of the"
},
{... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5. | [
"How to Represent the Correlating Event in an Event Policy",
"Configure an Event Policy to Execute Operational Mode Commands"
] |
commit (Commit Scripts) | commit {
allow-transients;
dampen {
dampen-options {
cpu-factor cpu-factor;
line-interval line-interval;
time-interval time-interval;
}
}
direct-access;
file filename {
allow-transients;
... | [edit system scripts] | For Junos OS commit scripts, configure the commit-time scripting mechanism. | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.4. | [
"Commit Script Overview",
"How Commit Scripts Work",
"Storing and Enabling Scripts"
] |
commit (System) | commit {
commit-synchronize-server;
config-sync-with-scp;
delta-export;
fast-synchronize;
force-commit-log;
notification;
peers;
peers-synchronize;
persist-groups-inheritance | no-persist-groups-inheritance;
server;
synchronize;
}
The parameters for fast-synchronize and synch... | [edit system] | Configure options for Junos OS commit. | [
{
"name": "commit-synchronize-server",
"desc": "(Optional) Specify traceoptions for commit synchronize server actions."
},
{
"name": "config-sync-with-scp",
"desc": "(Optional) Enable SCP for synchronizing configuration data in a Virtual Chassis. Only"
},
{
"name": "delta-export",
"d... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.4.
Option persist-groups-inheritance added in Junos OS Release 13.2.
Option delta-export added in Junos OS Release 14.2.
Option peers added in Junos OS Release 14.2R6.
Option peers-synchronize added in Junos OS Release 14.2R6.
Option no-persist-groups-inheritance added in Jun... | [
"Improving Commit Time When Using Configuration Groups"
] |
commit activate | commit activate{
comment;
and-quit;
peers-synchronize;
synchronize;
} | [edit system] | Activate a previously prepared commit. Upon successful validation, during the activation stage,
previously prepared commits are activated. Also, pending activation files are checked during this stage. If
there are pending activation files, the existence of required files and daemon map present in the
database data stru... | [
{
"name": "and-quit",
"desc": "(Optional) Commit the configuration and, if the configuration contains no errors and the commit succeeds, exit from configuration mode."
},
{
"name": "no-synchronize",
"desc": "(Optional) Do not synchronize the commit. Configure the commit prepare statement to run ... | configure—To enter configuration mode.
system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R1. | [
"Committing a Configuration",
"Committing a Configuration"
] |
commit prepare | commit prepare{
and-quit;
no-synchronize;
peers-synchronzie;
synchronize;
} | [edit system] | Prepare for an upcoming commit activation. Prepare the configurations that can be activated at a later
stage. During the preparation stage, all the required files and databases are generated and the
configuration is validated. A file is created that indicates if the commit is pending for activation. In the
event of fa... | [
{
"name": "and-quit",
"desc": "(Optional) Commit the configuration and, if the configuration contains no errors and the commit succeeds, exit from configuration mode."
},
{
"name": "no-synchronize",
"desc": "(Optional) Do not synchronize the commit. Configure the commit prepare statement to run ... | configure—To enter configuration mode.
system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3. | [
"Committing a Configuration",
"Committing a Configuration"
] |
commit | commit
<activate>
<and-quit>
<at “string”>
<check>
<comment <comment-string>
<confirmed>
<fast-synchronize>
<peers-synchronize>
<prepare>
<scripts>
<synchronize | no-synchronize>
<no-fast-synchronize>
< | > | 25.4R1
Starting in Junos OS and Junos OS Evolved Release 25.4R1, the fast-synchronize commit model is the
default model for all Junos OS and Junos OS Evolved dual Routing Engine devices, EX Series Virtual
Chassis, and MX Series Virtual Chassis. | [
{
"name": "none",
"desc": "Execute the commit command without any options to commit the configuration changes to the configuration database."
},
{
"name": "activate",
"desc": ""
},
{
"name": "(Optional)",
"desc": "Complete commit in two steps of preparing the configuration for commit... | configure—To enter configuration mode.
NOTE: If you are using Junos OS in a Common Criteria environment, system log
messages are created whenever a secret attribute is changed (for example, password
changes or changes to the RADIUS shared secret). These changes are logged during the
following configuration load operat... | Command introduced before Junos OS Release 7.4.
Option synchronize scripts introduced in Junos OS Release 13.2.
Option no-synchronize introduced in Junos OS Release 17.2R1
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supp... | [
"Adding a Comment to Describe the Committed Configuration",
"Committing Configurations on a Routing Matrix with a TX Matrix Plus Router",
"Commit Script Overview",
"Deactivating and Reactivating Statements and Identifiers in a Device Configuration",
"Monitoring the Commit Process",
"Scheduling a Commit Op... | |
commit-delay | commit-delay seconds; | [edit snmp nonvolatile] | Configure the timer for the SNMP Set reply and start of the commit. | [
{
"name": "seconds",
"desc": "Delay between an affirmative SNMP Set reply and start of the commit."
}
] | 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. | [] |
commit-interval | commit-interval interval; | [edit system services extensible-subscriber-services] | Specify the interval at which Extensible Subscriber Services Manager issues requests for committing op
script configurations. Requests that are received and processed within the interval are committed in a
batch at the end of the interval. Requests that are processed after the interval are committed at the end
of the n... | [
{
"name": "interval",
"desc": "Length of the interval. Range: 10 through 3600 seconds Default: 20 seconds"
}
] | 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. | [
"Op Script Overview"
] |
commit-options | commit-options {
check <synchronize>;
force;
log "comment-string";
synchronize;
} | [edit event-options policy policy-name then change-configuration] | Customize the commit options for configuration updates made through an event policy. The check
statement and the other commit-options statements are mutually exclusive. | [
{
"name": "check",
"desc": ""
},
{
"name": "<synchronize>",
"desc": "Verify that the candidate configuration is syntactically correct, but do not commit the changes. On dual control plane systems, when the check synchronize statement is configured, the candidate configuration on one control plan... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Configure an Event Policy to Change the Configuration"
] |
commit-synchronize-server | commit-synchronize-server {
traceoptions {
file {
filename;
files number;
microsecond-stamp;
size maximum-file-size;
(world-readable | no-world-readable);
}
flag (all | debug | ephemeral-commit | operational-command);
no-rem... | [edit system commit] | 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": "filename",
"desc": "Name of the file to receive the output of the tracing operation. NOTE: If you configure traceoptions and do not explicitly specify a filename for logging the events, the events are logged in the file /var/log/commitd by default."
},
{
"name": "files number",
"desc"... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R3 and Junos OS Evolved Release 22.1R1. | [] |
committed-burst-size | committed-burst-size bytes; | [edit dynamic-profiles profile-name firewall three-color-policer name single-rate],
[edit dynamic-profiles profile-name firewall three-color-policer name two-rate],
[edit firewall three-color-policer policer-name single-rate],
[edit firewall three-color-policer policer-name two-rate] | For a three-color policer, configure the committed burst size (CBS) as a number of bytes.
NOTE: When you include the committed-burst-size statement in the configuration, you
must also include the committed-information-rate statement at the same hierarchy level.
In three-color policing, a committed information rate (CI... | [
{
"name": "bytes",
"desc": "Number of bytes. You can specify a value in bytes either as a complete decimal number or as a"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4.
Support at the [edit dynamic-profiles ... single-rate] and [edit dynamic-profiles ... two-rate] hierarchy
levels introduced in Junos OS Release 11.4. | [
"Three-Color Policer Configuration Overview",
"Policer Bandwidth and Burst-Size Limits",
"Policer Color-Marking and Actions",
"Dual Token Bucket Algorithms",
"Determining Proper Burst Size for Traffic Policers"
] |
committed-information-rate | committed-information-rate bps; | [edit dynamic-profiles profile-name firewall three-color-policer name single-rate],
[edit dynamic-profiles profile-name firewall three-color-policer name two-rate],
[edit firewall three-color-policer policer-name single-rate],
[edit firewall three-color-policer policer-name two-rate] | For a three-color policer, configure the committed information rate as a number of bits per second. The
committed information rate (CIR) is the guaranteed bandwidth for traffic arriving at or departing from
the interface under normal line conditions.
NOTE: When you include the committed-information-rate statement in th... | [
{
"name": "bps",
"desc": "Number of bits per second. You can specify a value in bits per second either as a complete decimal"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.4.
Support at the [edit dynamic-profiles ... single-rate] and [edit dynamic-profiles ... two-rate] hierarchy
levels introduced in Junos OS Release 11.4. | [
"Three-Color Policer Configuration Overview",
"Policer Bandwidth and Burst-Size Limits",
"Policer Color-Marking and Actions",
"Dual Token Bucket Algorithms",
"Determining Proper Burst Size for Traffic Policers"
] |
community (Policy Options) | community name {
invert-match;
members [ community-ids ];
} | [edit dynamic policy-options],
[edit logical-systems logical-system-name policy-options],
[edit policy-options] | Define a community, extended community or large community for use in a routing policy match
condition. | [
{
"name": "name",
"desc": "Name that identifies the regular expression. The name can contain letters, numbers, and hyphens"
},
{
"name": "invert-match",
"desc": "Invert the results of the community expression matching. The community match condition"
},
{
"name": "members community-ids",
... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support for configuration in the dynamic database introduced in Junos OS Release 9.5.
Support for configuration in the dynamic database introduced in Junos OS Release 9.5 for EX Series
switches.
Support for BGP large community introduced in Junos OS Release 17.3 for MX ... | [
"Understanding BGP Communities, Extended Communities, and Large Communities as Routing Policy",
"Match Conditions",
"Understanding How to Define BGP Communities and Extended Communities"
] |
community (Protocols Layer 2 Circuit) | community community-name {
invert-match;
members community-members;
} | [edit logical-systems logical-system-name policy-options],
[edit logical-systems logical-system-name protocols l2circuit local-switching interface
interface-name backup-neighbor address],
[edit logical-systems logical-system-name protocols l2circuit neighbor address
interface interface-name],
[edit logical-systems l... | Specify the community for the Layer 2 circuit. | [
{
"name": "community-name",
"desc": "Name of the Layer 2 circuit community."
},
{
"name": "invert-match",
"desc": "Invert the results of the community expression match."
},
{
"name": "members community-members",
"desc": "Specify the members of the community."
}
] | 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.
Hierarchy levels associated with the backup-neighbor statement (pseudowire redundancy) added in Junos
OS Release 9.2. | [
"Configuring the Layer 2 Circuit Community",
"Configuring Pseudowire Redundancy on the PE Router",
"Example: Configuring Layer 2 Circuit Switching Protection"
] |
community (RMON) | community community-name; | [edit snmp rmon event index] | Configure the SNMP trap group that is used when generating a trap (if the eventType object is
configured to send traps). If that trap group has the rmon-alarm trap category configured, a trap is sent
to all the targets configured for that trap group. The community string in the trap matches the name of
the trap group (... | [
{
"name": "community-name",
"desc": "Name of the trap group that is used when generating a trap if the event is"
}
] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"RMON MIB Event, Alarm, Log, and History Control Tables",
"Configuring RMON Alarms and Events",
"Monitoring RMON MIB Tables",
"Understanding RMON",
"Junos OS Network Management Configuration Guide"
] |
community (Routing Options) | community ([ community-ids ] | no-advertise | no-export | no-export-subconfed | none | llgr-
stale | no-llgr); | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options (aggregate | generate | static) (defaults | route)],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name (aggregate | generate | static) (defaults | ro... | Associate BGP community information with a static, aggregate, or generated route.
NOTE: BGP large community is available only for static routes.
Default
No BGP community information is associated with static routes. | [
{
"name": "community-ids",
"desc": "One or more community identifiers. The community-ids format varies according to the"
},
{
"name": "as-number",
"desc": "AS number of the community member. It can be a value from 1 through 65,535. The AS"
},
{
"name": "community-value",
"desc": "Ide... | 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.
llgr-stale and no-llgr options added in Junos OS Release 15.1.
Support for BGP large community introduced in Junos OS Release 17.3 for MX Series, PTX Series, and
QFX Series. | [
"Example: Summarizing Static Routes Through Route Aggregation"
] |
community (SNMP) | community community-name {
authorization authorization;
client-list-name client-list-name;
clients {
address restrict;
}
view view-name;
} | [edit snmp] | Define an SNMP community. An SNMP community authorizes SNMP clients based on the source IP
address of incoming SNMP request packets. A community also defines which MIB objects are available
and the operations (read-only or read-write) allowed on those objects.
NOTE: The authorization read-write option is not supported... | [
{
"name": "community-name",
"desc": "Community string. 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 SNMP Communities",
"Configuring the SNMP Community String"
] |
community | community community-name; | [edit snmp rmon event index] | The trap group that is used when generating a trap (if eventType is configured to send traps). If that trap
group has the rmon-alarm trap category configured, a trap is sent to all the targets configured for that trap
group. The community string in the trap matches the name of the trap group (and hence, the value of
ev... | [
{
"name": "community-name",
"desc": "Identifies the trap group that is used when generating a trap if the event is configured to"
}
] | 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 an RMON Event Entry and Its Attributes"
] |
community-name | community-name community-name; | [edit snmp v3 snmp-community community-index] | The community name defines an SNMP community. The SNMP community authorizes SNMPv1 or
SNMPv2 clients. The access privileges associated with the configured security name define which MIB
objects are available and the operations (notify, read, or write) allowed on those objects. | [
{
"name": "community-name",
"desc": "Community string for an SNMPv1 or SNMPv2c community. If unconfigured, it is the same"
}
] | 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"
] |
community-vlan | community-vlan vlan community-vlan-name; | [edit vlans primary-vlan-name vlan-id primary-vlan-vlan-id] | Configure the specified community VLAN to be a secondary VLAN of the specified primary VLAN. A
community VLAN is used to transport frames among members of a community (a subset of users within
the VLAN), and to forward frames upstream to the primary VLAN.
NOTE: Before you specify this configuration statement, you must ... | [] | 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)"
] |
community-vlans (MX Series) | community-vlans [ number number-number ]; | [edit bridge-domains bridge-domain-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name bridge-domains
bridge-domain-name bridge-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name bridge-domains
bridge-domain-name,
[edit routing-instances ro... | Configure the specified community VLAN to be a secondary VLAN of the specified primary VLAN. A
community VLAN is used to transport frames among members of a community, which is a subset of
users within the VLAN, and to forward frames upstream to the primary VLAN.
NOTE: When you specify this configuration statement, the... | [
{
"name": "number",
"desc": "Individual VLAN IDs separated by a space."
}
] | 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. | [] |
compatibility (Application Identification) | compatibility junos-compatibility-version; | [edit services application-identification application application-name] | Specify the Junos OS release for compatibility. | [
{
"name": "junos-compatibility-version",
"desc": "Name of the Junos OS software release compatibility version, such as 17.1."
}
] | 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"
] |
compatibility-version | compatibility-version; | [edit protocols protection-group ethernet-ring ring-name] | Specify the compatible version mode to be used. When compatibility-version is set to value 1, the node
operates in ITU-T Recommendation G.8032/Y.1344 version 1 compatible mode. In this mode all the
supported external commands are blocked, ring-id is forced to be 1 and mode of operation is set to
revertive mode. | [
{
"name": "1",
"desc": "Use ITU-T Recommendation G.8032/Y.1344 compatibile mode version 1."
},
{
"name": "2",
"desc": "Use ITU-T Recommendation G.8032/Y.1344 compatibile mode version 2."
}
] | 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)"
] |
compliance (Juniper Secure Connect) | compliance {
post-logon name {
banner {
(file file | message message);
}
}
pre-logon name {
banner {
(file file | message message);
}
term name {
action (accept | reject);
... | [edit security remote-access] | Configure Juniper Secure Connect remote-access compliance rules. | [
{
"name": "file",
"desc": "Specify file-name to load banner message."
},
{
"name": "message",
"desc": "Specify text message."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.1R1.
Support for banner added in Junos OS Release 24.4R1. | [
"Juniper Secure Connect User Guide"
] |
compress (Accounting Options) | compress; | [edit accounting-options file filename] | Compress the accounting file during file transfer to the backup site. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring Accounting-Data Log Files",
"Configuring Flat-File Accounting for Layer 2 Wholesale",
"Configuring Flat-File Accounting for Extensible Subscriber Services Management",
"Flat-File Accounting Overview"
] |
compress-configuration-files (System) | (compress-configuration-files | no-compress-configuration-files); | [edit system] | Compress the current operational configuration file. By default, the current operational configuration file
is compressed, and is stored in the file juniper.conf, in the /config file system, along with the last three
committed versions of the configuration. However, with large networks, the current configuration file
m... | [] | 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. | [
"Compressing the Current Configuration File"
] |
compression (PPP Properties) | compression {
acfc;
pfc;
} | [edit interfaces interface-name ppp-options],
[edit interfaces interface-name unit logical-unit-number ppp-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number ppp-
options] | For interfaces with PPP encapsulation, set Link Control Protocol (LCP) compression options.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Point-to-Point Protocol (PPP)"
] |
compression | compression {
rtp {
f-max-period number;
maximum-contexts number <force>;
port {
minimum port-number;
maximum port-number;
}
queues [ queue-numbers ];
}
} | [edit interfaces interface-nameunit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Configure the compression properties for voice services traffic.
The remaining statements are described separately. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Compression of Voice Traffic"
] |
compression-device (Interfaces) | compression-device name; | [edit interfaces interface-name unit (Interfaces) logical-unit-number] | Specify the compression interface for voice services traffic. | [
{
"name": "name",
"desc": "Name of the AC."
}
] | 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. | [
"Understanding Interfaces"
] |
compression-device (Interfaces) | compression-device interface-name; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Specify the compression interface for voice services traffic. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Configuring the Compression Interface with PPP Encapsulation"
] |
compute-options | compute-options; | [edit protocols source-packet-routing] | Configure compute options applicable to all the computed paths. | [] | routing | Statement introduced in Junos OS Release 19.2R1-S1. | [
"Enabling Distributed CSPF for Segment Routing LSPs"
] |
compute-profile | compute-profile name {
algorithm algorithm-value;
protected {
mandatory;
}
unprotected {
mandatory;
}
bound-metric {
(delay | igp | te);
}
admin-group include-any [ include-any ... ]include-all [ include-all ... ]exclude
[ exclude ... ];
compute-segment-list ... | [edit protocols source-packet-routing] | Configure the compute profile for dynamically computed paths. You can use a compute profile to
logically group the computation constraints. These compute profiles are referenced by the segment
routing paths for computing the primary and secondary segment routing LSPs. | [
{
"name": "name",
"desc": "Name of the computation-profile."
},
{
"name": "algorithm",
"desc": "Algorithm that you would prefer to participate (1 to 255). Values:"
},
{
"name": "1",
"desc": "Strict SPF Algorithm"
},
{
"name": "128 to 255",
"desc": "Flex Algorithm"
},
... | routing | Statement introduced in Junos OS Release 19.2R1-S1. | [
"Enabling Distributed CSPF for Segment Routing LSPs"
] |
concurrent-data-sessions | concurrent-data-sessions max-session-number; | [edit services service-set services-set-name subscriber-profile profile-name enable service-name] | Specify the maximum number of sessions that are concurrently enabled for the named service. The
system randomly selects the number of sessions and enables the named service, whereas other sessions
are not allotted the named service. This facilitates to increase the limit on the number of resources a
service can use. | [
{
"name": "max-session-number",
"desc": "Maximum number of sessions concurrently enabled for the named service."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [] |
condition | condition name {
if-route-exists {
address;
address-family {
ccc {
address;
peer-unit peer-unit;
standby;
table table;
}
inet {
address;
table table;
... | [edit dynamic policy-options],
[edit logical-systems logical-system-name policy-options],
[edit policy-options] | Define a policy condition based on the existence of routes in specific tables for use in BGP export
policies. | [
{
"name": "name",
"desc": "Name to identify Condition"
},
{
"name": "route-active-on",
"desc": "Route is active on a specific node"
},
{
"name": "node0",
"desc": "Route active on node 0"
},
{
"name": "node1",
"desc": "Route active on node 1"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0.
Support for configuration in the dynamic database introduced in Junos OS Release 9.5.
Support for configuration in the dynamic database introduced in Junos OS Release 9.5 for EX Series
switches.
Support for the address families introduced in Junos OS Release 13.2. | [
"Conditional Advertisement and Import Policy (Routing Table) with certain match conditions",
"Example: Configuring Pseudowire Redundancy in a Mobile Backhaul Scenario"
] |
conditional-match | conditional-match name {
offset1 {
base-offset1 (start-of-L2Header | start-of-L3-InnerHeader | start-of-L3-OuterHeader |
start-of-L4-Header);
matchdata1 matchdata1;
matchdata1-mask matchdata1-mask;
offset1-value offset1-value;
}
offset2 {
base-offset2 (start-of-L2Hea... | [edit forwarding-options enhanced-hash-key] | Configure selected bytes to be directly used for user-defined flex hashing or to be used only when the
data pattern in these bytes matches with specific values (conditional match). | [
{
"name": "name",
"desc": "Name identifier"
}
] | interface | Statement introduced in Junos OS Release 20.4R1. | [] |
conditional-metric | conditional-metric {
igp-metric-threshold threshold conditional-metric-value;
} | [edit logical-systems name protocols mpls label-switched-path name],
[edit logical-systems name routing-instances name protocols mpls label-switched-path name],
[edit logical-systems name tenants name routing-instances name protocols mpls label-switched-
path name],
[edit protocols mpls label-switched-path name],
[edit... | Set a conditional metric value for the LSP. | [
{
"name": "igp-metric-threshold",
"desc": "Set conditional LSP metric based on the IGP metric. Range: Maximum 4"
},
{
"name": "threshold",
"desc": "Set conditional IGP metric threshold. Range: 1 through 16777215"
},
{
"name": "conditional-metric-value",
"desc": "Set conditional LSP... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.1R1. | [
"Configuring LSP Metrics"
] |
confederation | confederation confederation-autonomous-system members [ autonomous-systems ]; | [edit logical-systems logical-system-name routing-options],
[edit routing-options] | Specify the routing device’s confederation AS number.
If you administer multiple ASs that contain a very large number of BGP systems, you can group them
into one or more confederations. Each confederation is identified by its own AS number, which is called
a confederation AS number. To external ASs, a confederation app... | [
{
"name": "autonomous-systems",
"desc": "AS numbers of the confederation members."
},
{
"name": "confederation-autonomous-system",
"desc": "Confederation AS number. Use one of the numbers assigned to"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Configuring BGP Confederations",
"Understanding BGP Confederations"
] |
config-sync-with-scp | config-sync-with-scp; | [edit system commit] | (EX Series and QFX Series switches only) Configure secure transfer of configuration data and foreign
files using Secure Copy Protocol (SCP) during a commit or synchronization operation in a Virtual Chassis.
With this configuration, the management process (mgd) uses SCP to encrypt the configuration data
transferred from... | [] | maintenance—To view or add this statement to the configuration | Statement introduced in Junos OS Release 25.2R1. | [
"No Link Title"
] |
configuration-database (Enhanced Subscriber Management) | configuration-database {
max-db-size size;
} | [edit system] | Enhanced subscriber management leverages system shared memory to improve performance and
scaling. Since this memory is used by both the Junos configuration and enhanced subscriber
management, you need to set an upper limit on the memory available to the Junos configuration, which
in turn determines the allocation avail... | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1R3. | [
"Configuring Junos OS Enhanced Subscriber Management",
"Junos OS Enhanced Subscriber Management Overview"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.