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 |
|---|---|---|---|---|---|---|---|
bridge-priority | bridge-priority priority; | [edit logical-systems logical-system-name protocols (mstp | rstp)],
[edit logical-systems logical-system-name protocols mstp msti msti-id],
[edit logical-systems logical-system-name protocols vstp vlan vlan-id],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(mstp | rstp)],... | Configures the bridge priority, which determines which bridge is elected as the root bridge. If two
bridges have the same path cost to the root bridge, the bridge priority determines which bridge
becomes the designated bridge for a LAN segment.
Default
32,768 | [
{
"name": "priority",
"desc": "The bridge priority can be set only in increments of 4096."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.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 MSTP",
"Understanding VSTP",
"Understanding Bridge Priority for Election of Root Bridge and Designated Bridge",
"Example: Configuring Network Regions for VLANs with MSTP on Switches"
] |
bridge-template | bridge-template; | [edit services flow-monitoring version-ipfix | version9 template template-name] | Specify that the template is used for bridge records or for VPLS records. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Configuring Inline Active Flow Monitoring Using Routers, Switches or NFX250"
] |
brief | (brief | full); | [edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options (aggregate | generate) (defaults | route)],
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-
options rib routing-table-name (aggregate | generate) (defaults | route)],
[edit logic... | Configure all AS numbers from all contributing paths to be included in the aggregate or generated
route’s path.
•
brief—Include only the longest common leading sequences from the contributing AS paths. If this
results in AS numbers being omitted from the aggregate route, the BGP ATOMIC_ATTRIBUTE path
attribute is inclu... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Example: Summarizing Static Routes Through Route Aggregation",
"Example: Configuring a Conditional Default Route Policy",
"Understanding Conditionally Generated Routes"
] |
broadcast (Forwarding class) | broadcast forwarding-class-name; | [edit class-of-service multi-destination family ethernet] | Specify the forwarding class for the broadcast traffic belonging to the Ethernet family. | [
{
"name": "forwarding-class-name",
"desc": "Name of the forwarding class:"
},
{
"name": "mcast-af",
"desc": "Default forwarding class for assured forwarding of multicast traffic."
},
{
"name": "mcast-be",
"desc": "Default best-effort forwarding class for multicast traffic."
},
{
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Understanding CoS Schedulers",
"Understanding CoS Forwarding Classes",
"Understanding CoS Classifiers"
] |
broadcast (Interfaces) | broadcast address; | [edit interfaces interface-name unit logical-unit-number family family address address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family address address] | Set the broadcast address on the network or subnet. On a subnet you cannot specify a host address of 0
(0.0.0.0), nor can you specify a broadcast address (255.255.255.255). For example, in the statement set
interface ge-0/0/0 unit 0 family inet address 10.1.1.0/24, the subnet address 10.1.1.0 has the host address of
0.... | [
{
"name": "address",
"desc": "Broadcast address. The address must have a host portion of either all ones or all zeros. You"
}
] | 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 Interface Address"
] |
broadcast (Router Discovery) | (broadcast | multicast); | [edit logical-systems logical-system-name protocols router-discovery address address],
[edit protocols router-discovery address address] | Specify when the server should include the IP addresses in router advertisement packets. On the same
physical interfaces, some addresses might be included only in multicast packets, while others might be
included only in broadcast packets.
If you specify broadcast, the server includes the addresses in router advertisem... | [] | 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. | [
"Understanding the ICMP Protocol for Discovering Gateways to Other Networks",
"Example: Configuring the ICMP Protocol for Discovering Gateways to Other Networks"
] |
bucket-size | bucket-size number; | [edit snmp rmon history index] | Configure the sampling of Ethernet statistics for network fault diagnosis, planning, and performance
tuning.
Default | [
{
"name": "number",
"desc": "Number of discrete samples of Ethernet statistics requested."
}
] | snmp—To view this statement in the configuration.
snmp–control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Understanding RMON",
"RMON MIB Event, Alarm, Log, and History Control Tables",
"Configuring RMON History Sampling",
"Monitoring RMON MIB Tables",
"Junos OS Network Management Configuration Guide"
] |
buffer-dynamic-threshold (Schedulers) | buffer-dynamic-threshold value; | [edit class-of-service schedulers] | Adjust the maximum size of the shared-buffer pool at the egress buffer partition for each queue.
NOTE: This option is not supported for lossless queues.
During congestion or micro-burst scenarios, dedicated buffers can be exhausted, and queues start
consuming from the shared buffer pool. The device dynamically calculat... | [
{
"name": "buffer-dynamic-threshold",
"desc": ""
},
{
"name": "value",
"desc": "Threshold for maximum buffer share for a queue at the egress buffer partition. Range: 0-10"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved 22.3R1. | [] |
buffer-partition (Egress) | buffer-partition (lossless | lossy | multicast) {
percent percent;
dynamic-threshold value;
} | [edit class-of-service shared-buffer egress] | The egress shared buffer pool is divided into three partitions. Each partition reserves a percentage of the
available shared buffer pool for a type of traffic, so that the switch provides enough resources to
support a mix of best-effort, lossless, and multicast traffic (multicast also includes broadcast and
destinatio... | [
{
"name": "dynamic-threshold",
"desc": ""
},
{
"name": "value",
"desc": "Threshold for maximum buffer share for a queue at the egress buffer partition."
},
{
"name": "lossless",
"desc": "Shared buffer space reserved for all lossless egress traffic."
},
{
"name": "lossy",
... | 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.
dynamic-threshold option introduced in Junos OS Release 19.1R1.
dynamic-threshold option introduced in Junos OS Evolved Release 19.4R1.
Platform-Specific Behavior
Use Feature Explorer to confirm platform and release support for specific features.
Use the following table to... | [
"Example: Recommended Configuration of the Shared Buffer Pool for Networks with Mostly Best-",
"Effort Unicast Traffic",
"Example: Recommended Configuration of the Shared Buffer Pool for Networks with Mostly Multicast",
"Traffic",
"Example: Recommended Configuration of the Shared Buffer Pool for Networks wi... |
buffer-partition (Ingress) | buffer-partition (lossless | lossless-headroom | lossy) {
percent percentage;
dynamic-threshold value;
} | [edit class-of-service shared-buffer ingress] | The ingress shared buffer pool is divided into three partitions. Each partition reserves a percentage of
the available shared buffer pool for a type of traffic, so that the switch provides enough resources to
support a mix of best effort (best-effort unicast and multicast) and lossless traffic. To better support the
mi... | [
{
"name": "dynamic-threshold",
"desc": ""
},
{
"name": "value",
"desc": "Threshold for maximum buffer share for a queue at the ingress buffer partition."
},
{
"name": "lossless",
"desc": "Shared buffer space reserved for all lossless ingress traffic."
},
{
"name": "lossless-h... | 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.
dynamic-threshold option introduced in Junos OS Release 19.1R1.
dynamic-threshold option introduced in Junos OS Evolved Release 19.4R1.
Platform-Specific Behavior
Use Feature Explorer to confirm platform and release support for specific features.
Use the following table to... | [
"Example: Recommended Configuration of the Shared Buffer Pool for Networks with Mostly Best-",
"Effort Unicast Traffic",
"Example: Recommended Configuration of the Shared Buffer Pool for Networks with Mostly Multicast",
"Traffic",
"Example: Recommended Configuration of the Shared Buffer Pool for Networks wi... |
buffer-rate (Schedulers) | buffer-rate (percent percent | rate); | [edit class-of-service schedulers scheduler-name] | Configure the base rate for buffer size calculation. The buffer rate is the target rate of a VOQ, which is
the intended egress queue rate during typical congestion. The target rate is an import parameter for
VOQs, as the ratio of the drain rate to the target rate determines how much buffer adjustment happens
at ingress... | [
{
"name": "percent percentage",
"desc": "Buffer rate as a percentage of the total buffer. Range: 0 through 100"
},
{
"name": "rate",
"desc": "Buffer rate as an absolute value."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 24.4R1. | [
"buffer-size"
] |
buffer-size (Dynamic Scheduling) | buffer-size (percent (percentage | $junos-cos-scheduler-bs) | remainder | temporal (microseconds
| $junos-cos-scheduler-bs)); | [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] | Specify buffer size.
Default
If you do not include this statement, the default scheduler transmission rate and buffer size percentages
for queues 0 through 7 are 95, 0, 0, 5, 0, 0, 0, and 0 percent. | [
{
"name": "percent percentage",
"desc": "Buffer size as a percentage of total buffer."
},
{
"name": "remainder",
"desc": "Remaining buffer available."
},
{
"name": "temporal microseconds",
"desc": "Buffer size as a temporal value. The queuing algorithm starts dropping packets"
},
... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3.
The $junos-cos-scheduler-bs predefined variable introduced in Junos OS Release 9.4. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Configuring Schedulers in a Dynamic Profile for Subscriber Access"
] |
buffer-size (Schedulers) | buffer-size (percent percentage | remainder | shared | temporal microseconds); | [edit class-of-service schedulers scheduler-name] | Specify buffer size in a scheduler configuration.
You configure the proportion of port buffers allocated to a particular output queue using the following
process:
1. Configure a scheduler and set the buffer-size option.
2. Use a scheduler map to map the scheduler to the forwarding class that is mapped to the queue to
w... | [
{
"name": "percent",
"desc": ""
},
{
"name": "percentage",
"desc": "Buffer size as a percentage of the total buffer. Range: 0 through 100"
},
{
"name": "remainder",
"desc": "Remaining buffer available."
},
{
"name": "shared",
"desc": "On PTX Series routers, set a queue’s... | 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.
shared option introduced in Junos OS Release 18.1. | [
"Managing Congestion on the Egress Interface by Configuring the Scheduler Buffer Size",
"Example: Configuring CoS on EX Series Switches",
"Defining CoS Schedulers and Scheduler Maps (CLI Procedure)",
"Defining CoS Schedulers (J-Web Procedure)",
"Understanding CoS Schedulers"
] |
bulk-call-mode | bulk-call-mode; | [edit security alg sip ] | When there are multiple users behind SIP proxies at either end of an SRX, with multiple SIP calls
ongoing between the users via these SIP proxies and through the device, and all SIP traffic is using the
same 5 tuples, this results in a single SIP control session on the device, referred to as SIP bulk call or a
SIP "fat... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.4R1. | [] |
bulk-leasequery (DHCP Relay Agent) | bulk-leasequery {
attempts number-of-attempts;
timeout seconds;
trigger automatic;
} | [edit forwarding-options dhcp-relay],
[edit forwarding-options dhcp-relay dhcpv6],
[edit logical-systems logical-system-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name] | Enable support for bulk leasequery on a DHCPv4 or DHCPv6 relay agent. You can also configure
parameters that the DHCP relay agent uses when sending DHCP bulk leasequery messages to obtain
lease information from the DHCP local servers in the logical system/routing instance.
NOTE: You must also configure support on the r... | [
{
"name": "attempts",
"desc": ""
},
{
"name": "number-of-attempts",
"desc": "Specify the number of times the DHCP relay agent attempts to send DHCP bulk leasequery messages to the configured DHCP servers in the logical system/routing instance. DHCP relay agent resends the query message if the co... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1. | [
"Configuring and Using DHCP Bulk Leasequery"
] |
bum-hashing | bum-hashing; | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls],
[edit routing-instances routing-instance-name protocols vpls] | Load balance VPLS BUM (broadcast, unknown, and multicast) traffic across all members of an aggregate
interface for the routing instance.
NOTE: On MX Series routers, the bum-hashing configuration is not required when the
router is operating in enhanced-ip or enhanced-ethernet modes. If set, the configuration is
ignored. | [] | 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. | [
"Load Balancing VPLS Non-Unicast Traffic Across Member Links of an Aggregate Interface",
"Example: Configuring Multicast Load Balancing over Aggregated Ethernet Links"
] |
bundle (Interfaces) | bundle bundle-name; | [edit interfaces interface-name unit logical-unit-number family mlppp] | Specify the logical interface name the link joins. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Understanding Interfaces"
] |
bundle (multilink) | bundle (ml-fpc/pic/port | ls-fpc/pic/port); | [edit interfaces interface-name unit logical-unit-number family mlfr-end-to-end],
[edit interfaces interface-name unit logical-unit-number family mlfr-uni-nni] | Associate the multilink interface with the logical interface it is joining. | [
{
"name": "ml-fpc/pic/port",
"desc": "Name of the multilink interface you are linking."
},
{
"name": "ls-fpc/pic/port",
"desc": "Name of the link services interface you are linking."
}
] | 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 Links in a Multilink or Link Services Bundle"
] |
bundle | bundle (lsq-fpc/pic/port | ... ); | [edit interfaces lsq-fpc/pic/port unit logical-unit-number family mlppp] | Associate the voice services interface with the logical interface it is joining. | [
{
"name": "lsq-fpc/pic/port",
"desc": "Name of the voice services interface you are linking."
}
] | 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 Voice Services Bundles with MLPPP Encapsulation"
] |
burst (DDoS) | burst size; | For MX Series routers, T4000 routers, and EX9200 switches:
[edit system ddos-protection protocols protocol-group (aggregate | packet-type)]
For ACX Series routers, PTX Series routers and QFX Series switches:
[edit system ddos-protection protocols protocol-group (aggregate | packet-type)] | Configure the DDoS burst limit; that is, the maximum number of packets that is allowed in a burst of
traffic by the specified policer. When this value is exceeded, a violation is declared. | [
{
"name": "size",
"desc": "Number of packets that are allowed in a burst by the aggregate or packet-type policer."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Control Plane DDoS Protection Aggregate or Individual Packet Type Policers"
] |
burst-scale (DDoS) | burst-scale percentage; | [edit system ddos-protection protocols protocol-group (aggregate | packet-type) fpc slot-number] | (MX Series routers with only MPCs, T4000 routers with only FPC5s, PTX Series routers, EX9200
switches, or QFX Series switches) Configure the percentage by which the DDoS burst limit is scaled
down for the aggregate or packet-type policer on the card in the specified slot. | [
{
"name": "percentage",
"desc": "Percentage multiplied by the burst limit to reduce the number of packets allowed in a burst"
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Control Plane DDoS Protection Aggregate or Individual Packet Type Policers"
] |
burst-size (Default Local Policy) | burst-size uplink uplink-burst-size downlink downlink-burst-size; | [edit unified-edge gateways tdf gateway-name domains domain-name ip-subscriber default-local-
policy] | Specify the allowed burst size for a subscriber’s uplink and downlink traffic during the TDF IP-based
subscriber creation process. Uplink traffic originates from the subscriber towards the public data
network (PDN), and downlink traffic comes from the PDN and is destined for the subscriber. | [
{
"name": "uplink-burst-size",
"desc": "Burst size value for the uplink direction. Range: 1500 through 1,500,000,000 bytes."
},
{
"name": "downlink-burst-size",
"desc": "Burst size value for the downlink direction. Range: 1500 through 1,500,000,000 bytes"
}
] | 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 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"
] |
burst-size (TDF Domain) | burst-size {
apply-groups [group-names];
apply-groups-except [group-names];
downlink downlink-burst-size;
uplink uplink-burst-size ;
} | [edit unified-edge gateways tdf gateway-name domains domain-name] | Configure the TDF domain’s default TDF subscriber allowed burst size for uplink and downlink traffic.
Uplink traffic originates from the subscriber towards the public data network (PDN), and downlink traffic
comes from the PDN and is destined for the subscriber. | [
{
"name": "downlink-burst-size",
"desc": "Burst size value for the downlink direction. Range: 1500 through 1,500,000,000 bytes."
},
{
"name": "uplink-burst-size",
"desc": "Burst size value for the uplink direction. Range: 1500 through 1,500,000,000 bytes."
}
] | 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 Set of IP-Based TDF Subscriber Properties with a TDF Domain",
"Configuring IFL-Based TDF Subscribers and Properties with a TDF Domain",
"Understanding the Definition of a Set of IP-Based Subscriber Properties with a TDF Domain",
"IP-Based and IFL-Based TDF Subscribers Overview",
"IP-Based Sub... |
burst-size | burst-size bytes; | [edit forwarding-options storm-control-profiles profile-name all] | Configure the number of bytes of bursting traffic allowed to pass through a storm control interface. The
burst size allows for short periods of back-to-back traffic at average rates that exceed the storm control
level. If either the burst size or rate exceeds the limit, traffic will be dropped.
Storm control enables th... | [
{
"name": "bytes",
"desc": "Burst size limit in bytes."
}
] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.3R3-S7, 17.4R3-S2, and 18.1R1. | [
"Determining Proper Burst Size for Traffic Policers",
"Enabling and Disabling Storm Control (ELS)"
] |
burst-size-limit (Hierarchical Policer) | burst-size-limit bytes; | [edit dynamic-profiles profile-name firewall hierarchical-policer aggregate if-exceeding],
[edit dynamic-profiles profile-name firewall hierarchical-policer premium if-exceeding],
[edit firewall hierarchical-policer aggregate if-exceeding],
[edit firewall hierarchical-policer premium if-exceeding] | On M40e, M120, and M320 (with FFPC and SFPC) edge routers; on MPCs hosted on MX Series routers;
on T320, T640, and T1600 core routers with Enhanced Intelligent Queuing (IQE) PICs; and on T4000
routers with Type 5 FPC and Enhanced Scaling Type 4 FPC, configure the burst-size limit for premium or
aggregate traffic in a h... | [
{
"name": "bytes",
"desc": "Burst-size limit in bytes. The minimum recommended value is the maximum transmission unit"
},
{
"name": "routers)",
"desc": ""
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
Support at the [edit dynamic-profiles ... if exceeding] hierarchy level introduced in Junos OS Release
11.4. | [
"Hierarchical Policer Configuration Overview",
"Policer Bandwidth and Burst-Size Limits",
"Policer Color-Marking and Actions",
"Single Token Bucket Algorithm",
"Determining Proper Burst Size for Traffic Policers",
"Hierarchical Policers",
"bandwidth-limit (Hierarchical Policer)"
] |
burst-size-limit (Policer for Gigabit Ethernet Interfaces) | burst-size-limit bytes; | [edit interfaces interface-name gigether-options ethernet-switch-profile ethernet-policer-profile
policer cos-policer-name aggregate],
[edit interfaces interface-name gigether-options ethernet-switch-profile ethernet-policer-profile
policer cos-policer-name premium] | Define a policer to apply to nonpremium traffic. | [
{
"name": "bytes",
"desc": "Burst length."
}
] | 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 Gigabit Ethernet Policers"
] |
burst-size-limit (Policer) | burst-size-limit bytes; | [edit dynamic-profiles profile-name firewall policer policer-name if-exceeding],
[edit firewall policer policer-name if-exceeding],
[edit logical-systems logical-system-name policer policer-name if-exceeding] | For a single-rate two-color policer, configure the burst size as a number of bytes. The burst size allows
for short periods of traffic bursting (back-to-back traffic at average rates that exceed the configured
bandwidth limit). Single-rate two-color policing uses the single token bucket algorithm to measure
traffic-flo... | [
{
"name": "bytes",
"desc": "Burst-size limit in bytes. The minimum recommended value is the maximum transmission unit"
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Support at the [edit dynamic-profiles ... if-exceeding] hierarchy level introduced in Junos OS Release 11.4. | [
"Two-Color Policer Configuration Overview",
"Policer Bandwidth and Burst-Size Limits",
"Policer Color-Marking and Actions",
"Single Token Bucket Algorithm",
"Determining Proper Burst Size for Traffic Policers"
] |
burst-size-limit | burst-size-limit bytes; | [edit firewall policer policer-name if-exceeding]
[edit logical-systems logical-system-name firewall policer policer-name if-exceeding] | Specify the maximum allowed burst size to control the amount of traffic bursting. | [
{
"name": "bytes",
"desc": "Decimal value or a decimal number followed by k (thousand) or m (million)."
},
{
"name": "1500 through 1,00,000,000,000 bytes (routers)",
"desc": ""
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
Logical systems support introduced in Junos OS Release 9.3. | [
"Example: Configuring Firewall Filters for Port, VLAN, and Router Traffic on EX Series Switches",
"Configuring Policers to Control Traffic Rates (CLI Procedure)",
"Understanding the Use of Policers in Firewall Filters",
"Basic Single-Rate Two-Color Policers"
] |
by-destination (IDS MS-DPC) | by-destination {
hold-time seconds;
maximum number;
packets number;
rate number;
} | [edit services ids rule rule-name term term-name then session-limit] | Apply limit to sessions based on numbers generated from the configured destination (IP or subnet) or
application when using the MS-DPC. | [
{
"name": "hold-time seconds",
"desc": "Length of time for which to stop all new flows once the rate of events exceeds the"
},
{
"name": "maximum number",
"desc": "Maximum number of open sessions per application or IP address."
},
{
"name": "packets number",
"desc": "Maximum peak pac... | 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 Actions in IDS Rules"
] |
by-destination (IDS MS-MPC) | by-destination {
by-protocol {
icmp {
maximum number;
packets number;
rate number;
}
tcp {
maximum number;
packets number;
rate number;
}
udp {
maximum number;
packets number;
... | [edit services ids rule rule-name term term-name then session-limit] | Configure the IDS rule session limits for an individual destination address or subnet. This protects
against network probing attacks and network flooding attacks. This IDS rule can only be assigned to a
service set on an MS-MPC.
When a session limit is exceeded for a destination, packets to the destination are dropped ... | [
{
"name": "maximum number",
"desc": "Specify the maximum number of concurrent sessions allowed for an individual destination address or subnet."
},
{
"name": "packets number",
"desc": "Specify the maximum number of packets per second allowed for an individual destination address or subnet."
},... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
by-destination (IDS Screen Next Gen Services) | by-destination {
by-protocol {
icmp {
maximum-sessions number;
packets-rate number;
session-rate number;
}
tcp {
maximum-sessions number;
packet-rate number;
session-rate number;
}
udp {
maxim... | [edit services screen ids-option screen-name limit-session] | Configure session limits for individual destination addresses or for individual destination subnets. This
protects against network probing attacks and network flooding attacks. You can specify limits for
specific protocols (ICMP, TCP, and UDP), or specify limits independent of a protocol. When a session
limit is exceed... | [
{
"name": "maximum-sessions",
"desc": ""
},
{
"name": "number",
"desc": "Specify the maximum number of concurrent sessions allowed for an individual destination address or subnet."
},
{
"name": "packet-rate number",
"desc": "Specify the maximum number of packets per second allowed fo... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
by-pair (IDS MS-DPC) | by-pair {
hold-time seconds;
maximum number;
packets number;
rate number;
} | [edit services ids rule rule-name term term-name then session-limit] | Apply limit to paired stateful firewall and NAT flows (forward and reverse) when using the MS-DPC. | [
{
"name": "hold-time seconds",
"desc": "Length of time for which to stop all new flows once the rate of events exceeds the"
},
{
"name": "maximum number",
"desc": "Maximum number of open sessions per application or IP address."
},
{
"name": "packets number",
"desc": "Maximum peak pac... | 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 Actions in IDS Rules"
] |
by-protocol (IDS MS-MPC) | by-protocol {
icmp {
maximum number;
packets number;
rate number;
}
tcp {
maximum number;
packets number;
rate number;
}
udp {
maximum number;
packets number;
rate number;
}
} | [edit services ids rule rule-name term term-name then session-limit by-destination],
[edit services ids rule rule-name term term-name then session-limit by-source] | Configure the IDS rule session limits for an individual destination or source address or subnet for the
specified protocol. This protects against network probing attacks and network flooding attacks. This IDS
rule can only be assigned to a service set on an MS-MPC.
When a session limit is exceeded for a source or desti... | [
{
"name": "icmp",
"desc": "Apply session limits to ICMP packets."
},
{
"name": "maximum",
"desc": ""
},
{
"name": "number",
"desc": "Specify the maximum number of concurrent ICMP sessions allowed for an individual destination or source address or subnet."
},
{
"name": "packet... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
by-protocol (IDS Screen Next Gen Services) | by-protocol {
icmp {
maximum-sessions number;
packet-rate number;
session-rate number;
}
tcp {
maximum-sessions number;
packet-rate number;
session-rate number;
}
udp {
maximum-sessions number;
packet-rate number;
session-rate ... | [edit services screen ids-option screen-name limit-session by-destination],
[edit services screen ids-option screen-name limit-session by-source] | Configure session limits for individual destination or source addresses, or for individual destination or
source subnets, for the specified protocol. This protects against network probing attacks and network
flooding attacks. When a session limit is exceeded for a source or destination for the protocol, packets
from th... | [
{
"name": "icmp",
"desc": "Apply session limits to ICMP packets."
},
{
"name": "maximum-sessions number",
"desc": "Specify the maximum number of concurrent ICMP sessions allowed for individual destination or source addresses, or for individual destination or source subnets."
},
{
"name":... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
by-source (IDS MS-DPC) | by-source {
hold-time seconds;
maximum number;
packets number;
rate number;
} | [edit services ids rule rule-name term term-name then session-limit (IDS MS-DPC)] | Apply limit to sessions based on numbers generated from the configured source (IP or subnet) or
application when using the MS-DPC. | [
{
"name": "hold-time seconds",
"desc": "Length of time for which to stop all new flows once the rate of events exceeds the"
},
{
"name": "maximum number",
"desc": "Maximum number of open sessions per application or IP address."
},
{
"name": "packets number",
"desc": "Maximum peak pac... | 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 Actions in IDS Rules"
] |
by-source (IDS MS-MPC) | by-source {
by-protocol {
icmp {
maximum number;
packets number;
rate number;
}
tcp {
maximum number;
packets number;
rate number;
}
udp {
maximum number;
packets number;
... | [edit services ids rule rule-name term term-name then session-limit] | Configure the IDS rule session limits for an individual source address or subnet. This protects against
network probing attacks and network flooding attacks. When a session limit is exceeded for a source,
packets from the source are dropped until the session limit is no longer exceeded. This IDS rule can only
be assign... | [
{
"name": "maximum number",
"desc": "Specify the maximum number of concurrent sessions allowed for an individual source address or subnet."
},
{
"name": "packets number",
"desc": "Specify the maximum number of packets per second allowed for an individual source address or subnet."
},
{
"... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring Protection Against Network Attacks on an MS-MPC",
"Understanding IDS on an MS-MPC"
] |
by-source (IDS Screen Next Gen Services) | by-source {
by-protocol {
icmp {
maximum-sessions number;
packet-rate number;
session-rate number;
}
tcp {
maximum-sessions number;
packet-rate number;
session-rate number;
}
udp {
maximum-ses... | [edit services screen ids-option screen-name limit-session] | Configure session limits for individual source addresses or for individual source subnets. This protects
against network probing attacks and network flooding attacks. You can specify limits for specific
protocols (ICMP, TCP, and UDP), or specify limits independent of a protocol. When a session limit is
exceeded for a s... | [
{
"name": "maximum-sessions",
"desc": ""
},
{
"name": "number",
"desc": "Specify the maximum number of concurrent sessions allowed for an individual source address or subnet."
},
{
"name": "packet-rate number",
"desc": "Specify the maximum number of packets per second allowed for an ... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"Configuring Network Attack Protection With IDS Screens for Next Gen Services"
] |
bypass (Signaled LSP) | bypass bypass-name {
bandwidth bps;
description text;
hop-limit number;
no-cspf;
path address <strict | loose>;
priority setup-priority reservation-priority;
subscription subscription-percentage;
to address;
} | [edit logical-systems logical-system-name protocols rsvp interface interface-name link-
protection],
[edit protocols rsvp interface interface-name link-protection] | Enables you to configure specific bandwidth and path constraints for a bypass LSP. It is possible to
individually configure multiple bypass LSPs. If you do not configure the bypass LSPs individually, they all
share the same path and bandwidth constraints.
If you specify the bandwidth, hop-limit, and path statements for... | [
{
"name": "bypass-name",
"desc": "(Required) Specify a name for the bypass LSP. The name can be up to 64 characters."
},
{
"name": "description",
"desc": "Provides a textual description of the bypass LSP. Enclose any descriptive text that includes spaces in quotation marks (\" \"). Any descripti... | 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.
description option was added in Junos OS Release 10.4.
subscription subscription-percentage option introduced in Junos OS Release 19.2R1 on all platforms. | [
"Configuring Bypass LSPs"
] |
bypass (Static LSP) | bypass bypass-name {
bandwidth bps;
description string;
next-hop (address | interface-name | address/interface-name);
next-table string
push out-label;
to address;
} | [edit logical-systems logical-system-name protocols mpls static-label-switched-path lsp-name],
[edit protocols mpls static-label-switched-path lsp-name] | Configure specific bandwidth and path constraints for a bypass ingress LSP. It is possible to configure
multiple bypass LSPs individually. If you do not, they all share the same path and bandwidth constraints.
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 before Junos OS Release 10.1. | [
"Configuring Static LSPs"
] |
bypass | (bypass | no-bypass); | [edit interfaces interface-name otn-options odu-delay-management] | Pass or do not pass the delay measurement (DM) value through a node.
Default
If you omit the bypass statement, the default behavior is to disable ODU delay management options.
By default, do not pass the DM value through a node. | [
{
"name": "bypass",
"desc": "Pass the DM value through a node."
},
{
"name": "no-bypass",
"desc": "Do not pass the DM value through a node."
}
] | 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. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM"
] |
bypass-aggregate (DDoS) | bypass-aggregate; | For MX Series routers, T4000 routers, and EX9200 switches:
[edit system ddos-protection protocols protocol-group packet-type]
For QFX10000 Series and QFX5200 switches:
[edit system ddos-protection protocols protocol-group packet-type]
NOTE: The bypass-aggregate option is not supported on PTX Series routers and
QFX100... | Prevent this packet type from being considered by the DDoS aggregate policer. Traffic for the packet
type is still included in traffic statistics. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring Control Plane DDoS Protection"
] |
bypass-queuing-chip | bypass-queuing-chip; | [edit interfaces interface-name] | On MPCs that contain a queuing chip and on vMX routers, bypass the queuing chip to increase the
available bandwidth when rich queuing features are not required. When applied on a vMX router, this
option saves a vCPU.
CAUTION: When enabling this option, do not oversubscribe the port bandwidth. Also,
after committing thi... | [] | 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. | [
"Increasing Available Bandwidth on Rich-Queuing MPCs by Bypassing the Queuing Chip"
] |
bypass-traffic-on-exceeding-flow-limits | bypass-traffic-on-exceeding-flow-limits; | [edit services service-set service-set-name service-set-options] | Bypass traffic when exceeding the maximum flow limit. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1.
Statement introduced in Junos OS Release 19.3R2 on MX240, MX480 and MX960 routers using the
MX-SPC3 services card. | [
"Configuring Service Sets to be Applied to Services Interfaces"
] |
bypass-traffic-on-pic-failure | bypass-traffic-on-pic-failure; | [edit services service-set service-set-name service-set-options] | When the MultiServices PIC configured for a service set is either administratively taken offline or
undergoes a failure, all the traffic entering the configured interface with an IDP service set would be
dropped without notification. To avoid this traffic loss, include the bypass-traffic-on-pic-failure statement.
When ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1. | [
"Configuring Service Sets to be Applied to Services Interfaces"
] |
bytes (Dynamic Traffic Shaping) | bytes bytes | $junos-cos-byte-adjust; | [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name overhead-
accounting],
[edit class-of-service traffic-control-profiles profile-name overhead-accounting] | Configure the number of overhead bytes. | [
{
"name": "bytes",
"desc": "Byte adjustment value for the cell-mode or frame-mode shaping options. This can be the predefined"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"CoS Adjustment Control Profiles Overview",
"Configuring Dynamic Shaping Parameters to Account for Overhead in Downstream Traffic Rates",
"Bandwidth Management for Downstream Traffic in Edge Networks Overview",
"egress-shaping-overhead"
] |
bytes (otn-options) | bytes transmit-payload-type value; | [edit interfaces interface-name otn-options] | Specify the transmit payload type on OTN header bytes. | [
{
"name": "value",
"desc": "Transmit payload type."
}
] | 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.
Statement introduced in Junos OS Release 19.2R1-S1 for ACX5448-D routers. | [
"100-Gigabit Ethernet OTN Options Configuration Overview",
"Configuring OTN Interfaces on P1-PTX-2-100G-WDM",
"C"
] |
c-timeout | c-timeout value-in-minutes; | [edit logical-systems name security alg sip],
[edit logical-systems name tenants name security alg sip],
[edit security alg sip],
[edit services alg sip],
[edit tenants name security alg sip] | Configure the c-timeout parameter to Specify the time out interval for Session Initiation Protocol (SIP)
transactions in minutes. | [
{
"name": "value-in-minutes",
"desc": "Timeout interval."
}
] | 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. | [] |
ca-chain (REST API) | ca-chain ca-chain; | [edit system services rest https] | Configure Certificate authority chain profile to perform https REST API request using mutual and server
authentications. | [] | system | Statement introduced in Junos OS Release 20.4R1. | [] |
ca-identity | ca-identity ca-identity; | [edit security pki ca-profile ca-profile-name] | Specify the certificate authority (CA) identity to use in requesting digital certificates for J Series Services
Routers and Adaptive Services (AS) and MultiServices PICs installed in M Series and T Series routers. | [
{
"name": "ca-identity",
"desc": "The name of the CA identity. This name is typically the domain name of the CA."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Enroll a Certificate"
] |
ca-name | ca-name ca-identity; | [edit security certificates certification-authority] | (Encryption interface on M Series and T Series routers and EX Series switches only) Specify the
certificate authority (CA) identity to use in the certificate request. | [
{
"name": "ca-identity",
"desc": "CA identity to use in the certificate request."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Specifying the Certificate Authority Name"
] |
ca-profile (Security PKI) | ca-profile ca-profile-name {
administrator {
e-mail-address e-mail-address;
}
ca-identity ca-identity ;
enrollment {
retry number;
retry-interval seconds;
url url-name;
}
proxy-profile;
revocation-check;
routing-instance routing-instance-name ;... | [edit security pki] | Configure certificate authority (CA) profile. The CA profile contains the name and URL of the CA or RA,
as well as retry-timer settings. | [
{
"name": "ca-profile-name",
"desc": "Name of a trusted CA."
},
{
"name": "administrator",
"desc": ""
},
{
"name": "email-address",
"desc": "Specify an administrator e-mail address to which the certificate request is sent. By default, there is no preset e-mail address."
},
{
... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 8.5. Support for ca-identity option is added in Junos OS Release
11.1. Support for ocsp and use-ocsp options added in Junos OS Release 12.1X46-D20.
Support for proxy-profile option is added in Junos OS Release 18.2R1.
Support for source-address is introduced in Junos OS Release 15... | [
"Basic Elements of PKI in Junos OS"
] |
ca-profile (Services) | ca-profile ca-profile; | [edit services unified-access-control infranet-controller hostname] | Specify the certificate authority (CA) of the certificate that the SRX Series Firewall should use in
communications with an Infranet Enforcer. The SRX Series Firewall uses the CA to validate the IC Series
UAC Appliance server certificate.
Use this statement if you have loaded certificates from multiple certificate auth... | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4. | [] |
ca-type | ca-type type {
ca-value value;
} | [edit protocols lldp-med interface (all | interface-name location civic-based)] | For Link Layer Discovery Protocol–Media Endpoint Device (LLDP-MED), configure the location types
and values that comprise the location information advertised from the device to the MED. This
information is used during emergency calls to identify the location (civic or postal address) of the caller.
For further informat... | [
{
"name": "ca-type",
"desc": ""
},
{
"name": "type",
"desc": "Specify category codes that together with values represent information about the civic or postal address of the caller’s location. The address is divided into information types, with each information type represented by a code. Some o... | 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. | [
"Example: Setting Up VoIP with 802.1X and LLDP-MED on an EX Series Switch"
] |
cable-length (Congestion Notification) | cable-length cable-length-value; | [edit class-of-service congestion-notification-profile profile-name input] | Specify the length of the cable between the interface and its peer interface in meters. The system uses
the cable length and the maximum receive unit (MRU) to calculate the amount of buffer headroom
reserved to support priority-based flow control (PFC). The the shorter the cable length and lower the
MRU, the less headr... | [
{
"name": "cable-length-value",
"desc": "Length of the cable in meters. (Generally from 1 to 300 meters, but there is no"
},
{
"name": "configuration restriction.)",
"desc": ""
}
] | 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",
"Understanding CoS Flow Control (Ethernet PAUSE and PFC)",
"Understanding CoS IEEE 802.1p Priorities for Lossless Traffic Flows"
] |
cac (TDF Gateway) | cac {
cpu cpu-pct;
maximum-sessions max-sessions;
maximum-sessions-trap-percentage max-sessions-pct;
memory memory-pct;
} | [edit unified-edge gateways tdf gateway-name] | Configure the call admissions control (CAC) parameters for the TDF gateway.
The remaining statements are explained separately. See CLI Explorer. | [] | 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"
] |
cache (Security Log) | cache {
exclude exlude-name {
destination-address destination-address;
destination-port destination-port;
event-id event-id;
failure;
interface-name interface-name;
policy-name policy-name;
process process-name;
protocol protocol;
source-addre... | [edit security log] | Cache security log events in the audit log buffer. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement modified in Junos OS Release 9.2. | [] |
cache | cache {
size value;
timeout value;
} | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering surf-control-integrated]
[edit security utm feature-profile web-filtering juniper-enhanced] | 15.1X49-D10
The Surf-Control feature is 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. | The Surf-Control feature is not supported from Junos OS Release 15.1X49-D10 onwards. For previous
releases, statement introduced in Junos OS Release 9.5 for surf-control integrated.
Statement introduced in Junos OS Release 11.4 .
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Re... | [] |
cache-size | cache-size bytes; | [edit security certificates] | (Encryption interface on M Series and T Series routers and EX Series switches only) Configure the cache
size for digital certificates. | [
{
"name": "bytes",
"desc": "Cache size for digital certificates."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Cache Size"
] |
cache-timeout-negative | cache-timeout-negative seconds; | [edit security certificates] | (Encryption interface on M Series and T Series routers and EX Series switches only) Configure a negative
cache for digital certificates. | [
{
"name": "seconds",
"desc": "Negative time to cache digital certificates, in seconds."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Negative Cache"
] |
cacheable (Application Identification) | cacheable; | [edit services application-identification application application-name] | Enable the application system cache (ASC), which saves the mapping between an application type and
the corresponding destination IP address, destination port, protocol type, and service. The ASC is
disabled by default. | [] | 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"
] |
cak (MX Series) | cak hexadecimal-number; | [edit security macsec connectivity-association connectivity-association-name pre-shared-key] | Specifies the connectivity association key (CAK) for a pre-shared key.
A pre-shared key includes a connectivity association key name (CKN) and a CAK. A pre-shared key is
exchanged between two devices at each end of a point-to-point link to enable MACsec using dynamic
security keys. The MACsec Key Agreement (MKA) protoc... | [
{
"name": "hexadecimal-number",
"desc": "The key name, in hexadecimal format. For AES-128 the CAK key length is 32 hexadecimal characters, and for AES-256 it is 64. If you enter a key name with fewer characters than the standard (32 for cipher-suite gcm-aes-128, and 64 for cipher-suite gcm-aes-256), Junos w... | 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"
] |
cak | ckn hexadecimal-number; | [edit security macsec connectivity-association connectivity-association-name pre-shared-key],
[edit security macsec connectivity-association connectivity-association-name fallback-key] | Specifies the connectivity association key (CAK) for a preshared key.
A preshared key includes a connectivity association key name (CKN) and a CAK. A preshared key is
exchanged between two devices at each end of a point-to-point link to enable MACsec using dynamic
security keys. The CKN is a 64-digit hexadecimal number... | [
{
"name": "hexadecimal-number",
"desc": "The key name, in hexadecimal format. For AES-128 the CAK key length is 32 hexadecimal characters, and for AES-256 it is 64. If you enter a key name with fewer characters than the standard (32 for cipher-suite gcm-aes-128, and 64 for cipher-suite gcm-aes-256), Junos w... | 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 for 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)"
] |
calculation-weight | calculation-weight {
delay delay-value;
delay-variation delay-variation-value;
} | [edit protocols oam ethernet connectivity-fault-management performance-monitoring sla-iterator-profiles
profile-name] | Configure the calculation weight for delay and delay variation.
NOTE: This option is applicable only for two-way delay measurement.
The remaining statements are explained separately. See CLI Explorer. | [] | Configure—To enter configuration mode.
Control—To modify any configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring an Iterator Profile",
"Configure an Iterator Profile on a Switch (CLI Procedure)"
] |
call-flood | call-flood {
threshold rate;
} | [edit logical-systems name security alg sccp application-screen],
[edit logical-systems name tenants name security alg sccp application-screen],
[edit security alg sccp application-screen],
[edit services alg sccp application-screen],
[edit tenants name security alg sccp application-screen] | Limit the number of calls per second allowed to Skinny Client Control Protocol (SCCP) client. Calls
exceeding the threshold are dropped by the SCCP Application Layer Gateway (ALG). | [
{
"name": "threshold rate",
"desc": "Number of calls per second per 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. | [] |
call-rate-statistics | call-rate-statistics {
history records;
interval minutes;
} | [edit unified-edge gateways tdf gateway-name],
[edit unified-edge gateways tdf gateway-name domains domain-name] | Configure call rate statistics for a TDF gateway or a TDF domain. | [
{
"name": "records",
"desc": "Number of call-rate statistics records to save. When the number of call-rate records equals this value and a new record is received, the oldest record is replaced by the new record."
},
{
"name": "minutes",
"desc": "Length of statistics collection interval."
}
] | unified-edge—To view this statement in the configuration.
unified-edge—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring Call-Rate Statistics Collection"
] |
callback | callback; | [edit interfaces dln unit logical-unit-number dialer-options incoming-map],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number dialer-options
incoming-map] | On J Series Services Routers with interfaces configured for ISDN, configure the dialer to terminate the
incoming call and call back the originator after the callback wait period. The default wait time is 5
seconds. To configure the wait time, include the callback-wait-period statement at the [edit interfaces dl n
unit ... | [] | 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. | [] |
callback-wait-period | callback-wait-period time; | [edit interfaces dln unit logical-unit-number dialer-options],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number dialer-options] | On J Series Services Routers with interfaces configured for ISDN with callback, specify the amount of
time the dialer waits before calling back the caller. The default wait time is 5 seconds. The wait time is
necessary because, when a call is rejected, the switch waits for up to 4 seconds on point-to-multipoint
connect... | [
{
"name": "time",
"desc": "Time the dialer waits before calling back the caller."
}
] | 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. | [] |
called-station-id (OCS Partition) | called-station-id station-name; | [edit access ocs partition partition-name] | Include the Called-Station-Id AVP value in all CCR-GY packets. | [
{
"name": "station-name",
"desc": "Called station name defined for the Called-Station-Id AVP to include in all CCR-GY packets."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.2. | [
"Configuring the OCS Partition",
"Policy and Charging Enforcement Function Overview for Broadband Wireline Subscribers",
"Understanding Gy Interactions Between the Router and the OCS",
"Understanding Interactions Between the PCRF, PCEF, and OCS"
] |
called-station-id | called-station-id {
equals value;
matches value;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from] | Specify the RADIUS AVP called station ID for the incoming RADIUS request from the IP-based
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.
The remaining statements are explained s... | [] | 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"
... |
caller | caller (caller-id | accept-all); | [edit interfaces dln unit logical-unit-number dialer-options incoming-map],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number dialer-options
incoming-map] | On J Series Services Routers with interfaces configured for ISDN, specify the dialer to accept a specified
caller number or accept all incoming calls. | [
{
"name": "caller-id",
"desc": "Incoming caller number. You can configure multiple caller IDs on a dialer. The caller ID of the"
},
{
"name": "accept-all",
"desc": "Any incoming call in an associated interface is accepted."
}
] | 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. | [] |
calling-number (L2TP Tunnel Switching) | calling-number action; | [edit access tunnel-switch-profile profile-name avp] | Specify the action taken on the Calling Number AVP (22) in the L2TP packets during tunnel switching if
the AVP is negotiated when the first session is created. | [
{
"name": "action",
"desc": "One of the following actions:"
},
{
"name": "drop",
"desc": "Drop the AVP."
},
{
"name": "regenerate",
"desc": "Regenerate the AVP based on the local policy at the LTS and send it in the switched"
},
{
"name": "relay",
"desc": "Forward the AVP... | 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. | [
"L2TP Tunnel Switching For Multiple-Domain Networks"
] |
calling-number | calling-number number; | [edit interfaces br-pim/0/port isdn-options] | On J Series Services Routers with ISDN interfaces, configure the calling number to include in outgoing
calls. | [
{
"name": "number",
"desc": "Calling number."
}
] | 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 ISDN Physical Interface Properties"
] |
calling-station-id | calling-station-id {
equals value;
matches value;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from] | Specify the RADIUS AVP calling station ID for the incoming RADIUS request from the IP-based
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.
The remaining statements are explained ... | [] | 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"
... |
calling-station-id-format (Subscriber Management) | calling-station-id-format {
agent-circuit-id;
agent-remote-id;
interface-description;
interface-text-description;
mac-address;
nas-identifier;
stacked-vlan;
vlan;
} | [edit access profile profile-name radius options] | Specify the information that the router includes in the Calling-Station-ID (RADIUS IETF attribute 31)
that is passed to the RADIUS server during authentication and accounting. You can include one or more
optional values in any combination.
Default
The router displays the Calling-Station-ID set by the client. | [
{
"name": "agent-circuit-id",
"desc": "Include the agent circuit identifier (ACI) string, which uniquely identifies the subscriber’s"
},
{
"name": "agent-remote-id",
"desc": "Include the agent remote identifier (ARI) string, which identifies the subscriber on the"
},
{
"name": "interface... | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.1.
mac-address, interface-text-description, stacked-vlan, and vlan options added in Junos OS Release 15.1. | [
"Configuring a Calling-Station-ID with Additional Options"
] |
candidate-uplink-port-policy (satellite-policies) | candidate-uplink-port-policy policy-name{
<holddownholddown-time>;
<minimum-linksnumber-of-links>;
<uplink-port-group uplink-port-group-name>;
term term-name {
from {
product-model model-name;
<holddown holddown-time>;
<minimum-links number-of-links>;
... | [edit policy-options satellite-policies] | Configures a candidate uplink port profile, which contains uplink failure detection feature configuration
that can be applied to satellite devices in a Junos Fusion.
Default
There is no configured candidate uplink port profile, by default. | [
{
"name": "policy-name",
"desc": "User-defined name for the policy. 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 14.2R3. | [
"Configuring Junos Fusion Provider Edge",
"Configuring or Expanding a Junos Fusion Enterprise"
] |
capabilities (Protocols RIFT) | capabilities {
(flood-reduction | no-flood-reduction);
} | [edit protocols rift] | Enable the RIFT capability of reducing flooding globally.
If this capability is enabled, the node refloods TIEs only if it is the flood leader on the incoming link.
If you do not specify any of the options under the capabilities statement, the default behavior is to
enable flood reduction. | [
{
"name": "flood-reduction",
"desc": "(Optional) Enable flood reduction globally."
},
{
"name": "no-flood-reduction",
"desc": "(Optional) Disable flood reduction globally. Default: Flood reduction is enabled."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4R1. | [
"Understanding Junos Implementation of Routing in Fat Tree (RIFT) Protocol"
] |
captive-portal (Services UAC Policy) | captive-portal captive-portal-policy-name; | [edit security policies from-zone zone-name to-zone zone-name policy policy-name then permit
application-services uac-policy] | Create the captive portal policy in the UAC security policy. You use the captive portal policy to configure
the captive portal feature on the Junos OS Enforcer. By configuring the captive portal feature, you can
redirect traffic destined for protected resources to the IC Series device or to the URL you configure on
the... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [
"Security Policies Overview"
] |
captive-portal (Services UAC) | captive-portal redirect-policy-name{
redirect-traffic (all | unauthenticated);
redirect-url redirect-url;
} | [edit services unified-access-control] | Specify the preconfigured security policy for captive portal on the Junos OS Enforcer to enable the
captive portal feature. The captive portal policy is configured as part of the UAC policy.
By configuring the captive portal feature, you can redirect traffic destined for protected resources to the
IC Series device or t... | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2. | [] |
captive-portal | captive-portal {
authentication-profile-name authentication-profile-name
custom-options {
banner-message string;
footer-bgcolor color;
footer-message string;
footer-text-color color;
form-header-bgcolor color;
form-header-message string;
form-header-text-c... | [edit services] | Configure captive portal to authenticate clients connected to the switch for access to the network.
Default
Captive portal is disabled. | [
{
"name": "authentication-profile-name access-",
"desc": ""
},
{
"name": "profile-name",
"desc": "Specify the name of the access profile to be used for captive portal authentication. You configure the access profile at the [edit access profile] hierarchy level. The access profile contains the RA... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.1.
user-keepalive introduced in Junos OS Release 16.1 for EX Series switches. | [
"Example: Setting Up Captive Portal Authentication on an EX Series Switch",
"Designing a Captive Portal Authentication Login Page on Switches",
"Configuring Captive Portal Authentication (CLI Procedure)",
"Configuring an EX Series Switch to Use Junos Pulse Access Control Service for Network Access",
"Contro... |
captive-portal-content-delivery-profile (Services) | captive-portal-content-delivery-profile profile-name
interface-service {
service-interface name;
}
next-hop-service {
inside-service-interface interface-name.unit-number;
outside-service-interface interface-name.unit-number;
outside-service-interface-type local;
} | [edit services service-set service-set-name] | NOTE: Starting in Junos OS Release 17.2R1, you can configure converged services for
MS-MPCs and MS-MICs. Starting in Junos OS Release 19.3R2, you can configure
converged services for SPC3s if you have enabled Next Gen Services on the MX Series
router. At the edit service-set service set name captive-portal-content-deli... | [
{
"name": "service-interface name",
"desc": "Name of the service device associated with the interface-wide service set."
}
] | services—To view this statement in the configuration.
services–control—To add this statement to the configuration. | Statement introduced before Junos OS Release 17.2.
Support for Next Gen Services introduced in Junos OS Release 19.3R2. | [
"HTTP Redirect Service Overview"
] |
capture-file (Security) | capture-file {
filename;
files number;
format pacp-format;
size maximum-file-size;
(world-readable | no-world-readable);
} | [edit security datapath-debug] | Sets packet capture for performing the datapath-debug action. | [
{
"name": "filename",
"desc": "Name of the file to receive the output of the packet capturing operation."
},
{
"name": "files",
"desc": "Maximum number of capture files."
},
{
"name": "format",
"desc": "Describes the format of the capture file. The default format file is pcap. You ca... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.4. | [
"System Log Messages"
] |
capture-group | capture-group client-name {
content-destination identifier {
address address;
hard-limit bandwidth;
hard-limit-target bandwidth;
soft-limit bandwidth;
soft-limit-clear bandwidth;
ttl hops;
}
control-source identifier {
allowed-destinations [ destinatio... | [edit services dynamic-flow-capture] | Define the capture group values.
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 7.4. | [
"Configuring the Capture Group"
] |
casb | casb {
instance instance-name {
application application-name;
domain domain-name;
instance-id instnace-id;
tag tag-value;
type type;
}
casb-policy policy-name {
rules rule-name {
match {
application application-name {
act... | [edit security] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [
{
"name": "\"instance \" on page",
"desc": ""
},
{
"name": "9144instance-name",
"desc": "CASB instance name. Configure CASB instance with application, instance ID, domain, and type. Creating instances for SaaS applications ensures controlled access, data security, and differentiation between cor... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.2R1. | [] |
casb-policy | casb-policy policy-name {
rules rule-name {
match {
application application-name {
actity activity-name {
[param-name param-value param-name param-value]
}
instance instance-name;
}
applicat... | [edit security] | Configure Cloud Access Security Broker (CASB) policy. CASB policy includes set of rules to match a
section of traffic based on applications or instances and then specify actions to apply on the matched
traffic and take active or passive preventive actions. | [
{
"name": "\"rules\" on page 16677",
"desc": ""
},
{
"name": "rule-name",
"desc": "Configure rules for the CASB policy."
},
{
"name": "log-activity",
"desc": "(optional) Define activity logging for the CASB policy. Available options are login, download, and upload."
},
{
"nam... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 24.2R1. | [] |
cascade-port | cascade-port; | [edit interfaces interface-name] | Configure the specified interface on the aggregation device in a Junos Fusion into a cascade port.
Additional configuration is required to configure cascade ports on a Junos Fusion. See Configuring Junos
Fusion Provider Edge or Configuring or Expanding a Junos Fusion Enterprise.
Default
No interfaces are cascade ports,... | [
{
"name": "interface-name",
"desc": "Specifies the name of the interface."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring or Expanding a Junos Fusion Enterprise",
"Configuring Junos Fusion Provider Edge"
] |
cascade-ports (Junos Fusion Satellite Device Cluster) | cascade-ports interface-name; | [edit chassis satellite-management cluster cluster-name] | Associate a cascade port with a satellite device cluster in a Junos Fusion.
This command defines which cascade ports are associated with a satellite device cluster only. An
interface still needs to be converted into a cascade port before it performs cascade port functions.
There are multiple ways to convert an interfac... | [
{
"name": "interface-name",
"desc": "Specifies the name of the interface on the aggregation device that is associated with the satellite device cluster."
}
] | 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"
] |
cascade-ports | cascade-ports interface-name; | [edit chassis satellite-management fpc slot-id] | Associate a cascade port with an FPC slot ID number in a Junos Fusion.
The FPC slot ID of the satellite device is determined by the value entered as the FPC slot-id. For
instance, if the set chassis satellite-management fpc 105 cascade-ports xe-0/0/1 statement is used to
configure interface xe-0/0/1 into a cascade port... | [
{
"name": "interface-name",
"desc": "Specifies the name of the interface."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R3. | [
"Configuring or Expanding a Junos Fusion Enterprise",
"Configuring Junos Fusion Provider Edge"
] |
categories | categories {
category;
} | [edit snmp trap-group group-name] | Define the types of traps that are sent to the targets of the named trap group.
Default
If you omit the categories statement, all trap types are included in trap notifications, except the timing-
events category. You must explicitly configure generation of timing traps by including the timing-events
statement at the [e... | [
{
"name": "authentication",
"desc": "Authentication failures."
},
{
"name": "chassis",
"desc": "Chassis or environment notifications."
},
{
"name": "chassis-cluster",
"desc": "(For SRX Series) Clustering notifications."
},
{
"name": "configuration",
"desc": "Configuration... | 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 Trap Groups"
] |
category (Security Dynamic Attack Group) | category {
values [category-value];
} | [edit security idp dynamic-attack-group dynamic-attack-group-name filters] | Specify a category filter to add attack objects based on the category. | [
{
"name": "values",
"desc": "Name of the category filter. You can configure multiple filters separated by spaces and enclosed"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.3. | [] |
category (Security Logging) | category (all | content-security | fw-auth | screen | alg | nat | flow | sctp | gtp | ipsec |
idp | rtlog | pst-ds-lite | appqos | secintel | aamw | dnsf) | [edit security log stream stream-name]
[edit logical-systems name security log stream stream-name]
[edit tenants tenant-name security log stream stream-name] | Set the category of logging to all or content-security. Note that for the WELF format, the category must
be set to content-security. | [
{
"name": "all",
"desc": "All events are logged. By default, all the events listed in the category parameter are logged."
},
{
"name": "content-security",
"desc": "Only content security events are logged."
},
{
"name": "fw-auth",
"desc": "Firewall authentication events are logged."
... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0. Statement modified in Junos OS Release 15.1X49-D40.
The [edit logical-systems name security log stream stream-name] hierarchy level introduced in Junos OS
Release 18.2R1.
The [edit tenants tenant-name security log stream stream-name] hierarchy levels introduced in Junos OS... | [
"Application Security User Guide for Security Devices",
"Logical Systems and Tenant Systems User Guide for Security Devices"
] |
category (Security Web Filtering) | category name{
action (block | log-and-permit | permit | quarantine);
custom-message message-name;
} | [edit security utm default-configuration]
[edit security utm feature-profile web-filtering surf-control-integrated profile profile-name]
[edit security utm feature-profile web-filtering juniper-enhanced profile profile-name] | Select a custom URL category list you created (custom objects) for filtering against. The custom-message
configuration option is used to notify the users when the URL is blocked or quarantined for each EWF
category. You can customize the message with options such as user message or redirect URL. User
messages indicate ... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4 .
Starting with Junos OS Release 15.1X49-D10, the SurfControl integrated feature is no longer supported.
For previous releases, statement introduced in Junos OS Release 9.5. The custom-message option
introduced in Junos OS Release 15.1X49-D110.
The [edit security utm defaul... | [
"Redirect Web Filtering"
] |
category (System Logging) | category category, category....category; | [edit services service-set service-set-name syslog stream] | Specify the categories for which you want to collect logs. | [
{
"name": "all",
"desc": "All events are logged"
},
{
"name": "content-security",
"desc": "Content security events are logged"
},
{
"name": "fw-auth",
"desc": "Fw-auth events are logged"
},
{
"name": "screen",
"desc": "Screen events are logged"
},
{
"name": "alg",... | system—To view this statement in the configuration. | Statement introduced in Junos OS Release 19.3R2. | [] |
category | category category-name {
inline-monitoring-instance inline-monitoring-instance;
} | [edit chassis fpc slot-number pfe identifier exception-reporting] | (Required) Configure the PFE exception category type and assign a particular inline-monitoring instance
to it. | [
{
"name": "category-name",
"desc": "Name of the category. Include more than one category statement in your configuration if you want reporting for more than one exception type (Junos OS only). You can specify one of the following types on each category statement:"
},
{
"name": "all",
"desc": "(J... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.2R1 for MX Series routers.
Statement introduced in Junos Evolved OS Release 22.2R1 for PTX Series routers. | [
"Juniper Resiliency Interface"
] |
cbr rate | cbr rate; | [edit interfaces interface-name atm-options vpi vpi-identifier shaping] | For ATM encapsulation only, define a constant bit rate bandwidth utilization in the traffic-shaping
profile. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Command introduced in Release 9.5 of Junos OS. | [] |
cbr | cbr rate; | [edit interfaces at-fpc/pic/port atm-options vpi vpi-identifier shaping],
[edit interfaces at-fpc/pic/port unit logical-unit-number address address family family
multipoint-destination address shaping],
[edit interfaces at-fpc/pic/port unit logical-unit-number shaping],
[edit logical-systems logical-system-name interfa... | For ATM encapsulation only, define a constant bit rate bandwidth utilization in the traffic-shaping
profile.
Default
Unspecified bit rate (UBR); that is, bandwidth utilization is unlimited. | [
{
"name": "rate",
"desc": "Peak rate, in bits per second (bps) or cells per second (cps). You can specify a value in bits per second either as a complete decimal number or as a decimal number followed by the abbreviation k (1000), m (1,000,000), or g (1,000,000,000). You can also specify a value in cells pe... | 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 the ATM Traffic-Shaping Profile Overview",
"rtvbr",
"vbr"
] |
ccc (Routing Policy Condition) | ccc {
interface-name;
standby;
peer-unit unit-number;
table table-name;
} | [edit logical-systems logical-system-name policy-options condition if-route-exists address-
family],
[edit policy-options condition if-route-exists address-family] | Specify that the route must correspond to a CCC prefix to be considered a match. | [
{
"name": "interface-name",
"desc": "Interface used to establish the CCC route."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Example: Configuring Pseudowire Redundancy in a Mobile Backhaul Scenario"
] |
ccc | ccc; | [edit interfaces ge-fpc/slot/port unit logical-unit-number family] | Configure the logical interface as a circuit cross-connect (CCC).
NOTE: On QFX10002 switches, circuit cross-connects are not supported on aggregated
Ethernet interfaces.
Default
You must configure a logical interface to be able to use the physical device. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [] |
cdvt | cdvt rate; | [edit firewall atm-policer atm-policer-name] | Define the Cell Delay/Variation Tolerance (CDVT) rate on a clear-channel multirate circuit emulation
MIC. | [
{
"name": "rate",
"desc": "CDVT rate in microseconds."
}
] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [] |
cell-mode (Dynamic Traffic Shaping) | cell-mode (bytes bytes | $junos-cos-byte-adjust | cell-mode-bytes cell-mode-bytes |$junos-cos-
byte-adjust-cell); | [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name overhead-
accounting],
[edit class-of-service traffic-control-profiles profile-name overhead-accounting] | Configure the mode to shape downstream ATM traffic as cells. | [
{
"name": "bytes",
"desc": "Byte adjustment value for the cell-mode or frame-mode shaping options."
},
{
"name": "$junos-cos-byte-adjust",
"desc": "Predefined variable for byte adjustment that is replaced with a value obtained from the RADIUS server when a subscriber authenticates over the inter... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.2.
Variable $junos-cos-byte-adjust-cell introduced in Junos OS Release 13.1. | [
"CoS Adjustment Control Profiles Overview",
"Configuring CoS Adjustment Control Profiles",
"Configuring Dynamic Shaping Parameters to Account for Overhead in Downstream Traffic Rates",
"Bandwidth Management for Downstream Traffic in Edge Networks Overview",
"egress-shaping-overhead"
] |
cell-overhead | cell-overhead; | [edit access group-profile profile-name ppp],
[edit access profile profile-name client client-name ppp] | Configure the session to use Asynchronous Transfer Mode (ATM)-aware egress shaping on the IQ2 PIC. | [] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [
"Point-to-Point Protocol (PPP)"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.