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 |
|---|---|---|---|---|---|---|---|
enhanced-mode | enhanced-mode; | [edit dynamic-profiles profile-name firewall family family-name filter filter-name],
[edit firewall filter filter-name],
[edit firewall family family-name filter filter-name],
[edit logical-systems logical-system-name firewall filter filter-name],
[edit logical-systems logical-system-name firewall family family-nam... | Limit static service filters or API-client filters to term-based filter format only for inet or inet6 families
when enhanced network services mode is configured at the [edit chassis network-services] hierarchy level.
You cannot attach enhanced mode filters to local loopback, management, or MS-DPC interfaces. These
inte... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4.
Statement introduced in Junos OS Release 23.2 for SRX4600, SRX5400, SRX5600, and SRX5800.
Statement introduced in Junos OS Release 24.4 for SRX4700. | [
"Network Services Mode Overview",
"Firewall Filters and Enhanced Network Services Mode Overview",
"Configuring a Filter for Use with Enhanced Network Services Mode",
"Firewall Filter Match Conditions for IPv4 Traffic",
"Firewall Filter Match Conditions for IPv6 Traffic",
"Firewall Filter Terminating Actio... |
enhanced-mode-override | enhanced-mode-override; | [edit dynamic-profiles profile-name firewall family family-name filter filter-name],
[edit firewall filter filter-name],
[edit firewall family family-name filter filter-name],
[edit logical-systems logical-system-name firewall filter filter-name],
[edit logical-systems logical-system-name firewall family family-name... | Overrides the default filter enhanced-mode of dynamic service filters when the chassis is running in
network-services enhanced IP mode. It functions similarly to the "enhanced-mode" on page 6686
statement used to override the default IP mode of static filters when the chassis is running in network-
services enhanced IP... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Network Services Mode Overview",
"Firewall Filters and Enhanced Network Services Mode Overview",
"Configuring a Filter for Use with Enhanced Network Services Mode"
] |
enhanced-policer | enhanced-policer | [edit chassis] | Collect additional statistics to be displayed using show commands. An FPC restart is required after
changing this configuration.
A warning log message is generated when you commit a configuration that contains the enhanced-policer
statement. The log message states that the enhanced policer is enabled on FPCs only after... | [] | 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. | [
"Router Chassis Configuration Statements",
"Enhanced Policer Statistics Overview",
"show policer"
] |
enhanced-priority-mode | enhanced-priority-mode; | [edit chassis fpc slot-number traffic-manager] | Enable the enhanced priority mode. When you enable the enhanced priority mode, the scheduler
supports four additional per-priority shaping rates and two additional excess priorities at the interface
and interface set level. The four additional per-priority shaping rates are: Guaranteed Strict-high,
Guaranteed Medium-lo... | [] | 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.
Statement introduced in Junos OS Release 18.1 for PTX Series. | [
"Per-Priority Shaping on MIC and MPC Interfaces Overview"
] |
enhanced-scale (IRB Interface) | interface irb.<unit> {
enhanced-scale;
} | [edit interfaces irb unit unit] | Enable the IRB interface to allocate Next Hop Identifiers (NHId) from the extended space, thereby
supporting up to 1.5 million ARP/ND unicast next hop entries. This feature is essential for environments
requiring a high scale of next hop entries. | [] | admin: To view this statement in the configuration. | admin-control: To add this statement to the configuration. | [] |
enhanced-transmission-selection | enhanced-transmission-selection {
no-auto-negotiation;
no-recommendation-tlv;
recommendation-tlv {
no-auto-negotiation;
}
} | [edit protocols dcbx interface interface-name] | Disable advertising the enhanced transmission selection (ETS) state of the interface to the peer. To
disable ETS on the interface, do not enable ETS on the interface in the class-of-service (CoS)
configuration.
Disabling ETS autonegotiation stops the QFX Series from advertising the ETS Configuration TLV and the
ETS Rec... | [
{
"name": "no-auto-negotiation",
"desc": "Disable automatic negotiation of ETS (Configuration TLV and Recommendation TLV)"
},
{
"name": "no-recommendation-tlv",
"desc": "Disable automatic negotiation of the ETS Recommendation TLV"
},
{
"name": "recommendation-tlv",
"desc": "Enable au... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring DCBX Autonegotiation",
"Example: Configuring CoS Hierarchical Port Scheduling (ETS)",
"Understanding DCB Features and Requirements"
] |
enrollment | enrollment {
url url-name;
retry number-of-enrollment-attempts;
retry-interval seconds;
} | [edit security pki ca-profile ca-profile-name] | Specify the URL and enrollment parameters of the certificate authority (CA) for Adaptive Services (AS)
and MultiServices PICs installed on MX Series, M Series, and T Series routers. | [
{
"name": "url url-name",
"desc": "Location of the CA to which the router sends the Simple Certificate Enrollment Protocol-based (SCEP-based) certificate enrollment requests for the configured CA profile. Use the CA host DNS"
},
{
"name": "retry number-of-enrollment-attempts",
"desc": "Number of... | 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. | [
"Specifying an Enrollment URL",
"Specifying the Enrollment Properties"
] |
enrollment-retry | enrollment-retry attempts; | [edit security certificates] | (Encryption interface on M Series and T Series routers and EX Series switches only) Specify how many
times a router or switch can resend a digital certificate request. | [
{
"name": "attempts",
"desc": "Number of enrollment retries."
}
] | 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 Number of Enrollment Retries"
] |
enrollment-url | enrollment-url url-name; | [edit security certificates certification-authority ca-profile-name] | (Encryption interface on M Series and T Series routers and EX Series switches only) Specify where your
router or switch sends Simple Certificate Enrollment Protocol-based (SCEP-based) certificate enrollment
requests (certificate authority URL). | [
{
"name": "url-name",
"desc": "Certificate authority URL."
}
] | 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 an Enrollment URL"
] |
enterprise-oid | enterprise-oid; | [edit snmp trap-options] | Add the snmpTrapEnterprise object, which shows the association between an enterprise-specific trap
and the organization that defined the trap, to standard SNMP traps. By default, the snmpTrapEnterprise
object is added only to the enterprise-specific traps. When the enterprise-oid statement is included in the
configurat... | [] | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0 | [
"Configuring SNMP Trap Options"
] |
entropy-label (protocols bgp) | entropy-label {
elc-v2-compatible;
import [ import ... ];
no-next-hop-validation;
} | [edit fabric protocols bgp family inet labeled-unicast],
[edit fabric protocols bgp group name family inet labeled-unicast],
[edit fabric protocols bgp group name neighbor name family inet labeled-unicast],
[edit logical-systems name protocols bgp family inet labeled-unicast],
[edit logical-systems name protocols bgp g... | Insert the entropy label into the BGP labeled unicast LSP packets, which assists the transit router in
load-balancing BGP traffic across equal-cost multipaths or link aggregation groups. The ingress label
edge router inspects the flow information of a packet and maps it to an entropy label, which is inserted
into the B... | [
{
"name": "elc-v2-compatible",
"desc": "Send and accept ELCv2 in addition to ELCv3"
},
{
"name": "import",
"desc": "Policy to select BGP LSPs to use entropy label"
},
{
"name": "no-next-hop-validation",
"desc": "Don't validate next hop field against route next hop"
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1.
elc-v2-compatible statement introduced in Junos OS Release 23.1. | [
"Configuring an Entropy Label for a BGP Labeled Unicast LSP",
"Example: Configuring an Entropy Label for a BGP Labeled Unicast LSP",
"Understanding Entropy Label for BGP Labeled Unicast LSP"
] |
entropy-label (protocols mpls) | entropy-label {
ingress-policy ingress-policy-name;
} | [edit logical-systems logical-system-name protocols ldp] | Assists the transit router in load-balancing MPLS traffic across ECMP paths or Link Aggregation groups
by introducing the entropy label to the MPLS label stack. The entropy label allows routers to load
balance MPLS traffic by using a hash-input without the need to perform deep packet inspection. Deep
packet inspection ... | [] | 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. | [
"Configuring the Entropy Label for LSPs"
] |
environment-monitoring-policy (satellite-management) | environment-monitoring-policy policy-name; | [edit chassis satellite-management]
[edit chassis satellite-management fpc slot-id] | Enable an environment monitoring policy in a Junos Fusion.
You configure environment monitoring policies for a Junos Fusion in the [edit policy-options environment-
monitoring-policy policy-name] hierarchy.
You can configure an environment monitoring policy in a Junos Fusion for a single satellite device using
the fpc ... | [
{
"name": "policy-name",
"desc": "Specifies the name of the environment monitoring policy. The policy-name name is defined as part of the environment monitoring policy configuration procedure, which is handled in the [edit policy-options environment-monitoring-policy policy-name] hierarchy."
}
] | 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 Satellite Device Alarm Handling Using an Environment Monitoring Satellite Policy in a",
"Junos Fusion",
"Understanding Satellite Policies in a Junos Fusion"
] |
environment-monitoring-policy (satellite-policies) | environment-monitoring-policy policy-name {
alarm {
linkdown [ignore | red | yellow]
}
term term-name{
from {
product-model model-name;
}
}
} | [edit policy-options satellite-policies] | Configure an environment monitoring satellite policy for a device or devices in a Junos Fusion.
An environment monitoring satellite policy is used to configure alarm behavior on satellite devices in a
Junos Fusion.
The environment monitoring policy is applied to a Junos Fusion using the environment-monitoring-policy
st... | [
{
"name": "policy-name",
"desc": "Specifies the user-defined name of the environment monitoring 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 Satellite Device Alarm Handling Using an Environment Monitoring Satellite Policy in a",
"Junos Fusion",
"Understanding Satellite Policies in a Junos Fusion"
] |
epacl-firewall-optimization | epacl-firewall-optimization | [edit chassis forwarding-options] | Enable epacl-firewall-optimization to use Layer 2 and Layer 3 match conditions in firewall filters to support
micro-segmentation on VXLAN deployments. Filtering in both the ingress and egress directions is
supported. (For egress filtering on VLANs, this statement is not needed.)
For example, to create micro-segmentatio... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 21.1R1 for QFX5110 and QFX5120 Series switches. | [] |
ephemeral | ephemeral {
allow-commit-synchronize-with-gres;
commit-synchronize-model (asynchronous | synchronous);
cyclic-version-for-ephemeral-default version;
delete-ephemeral-default;
ignore-ephemeral-default;
instance instance-name {
cyclic-version version;
resize {
database-... | [edit system configuration-database] | Configure settings for the ephemeral configuration database.
The ephemeral database is an alternate configuration database. It enables Juniper Extension Toolkit
(JET) applications and NETCONF and Junos XML protocol client applications to simultaneously load and
commit configuration changes on Junos devices and with sig... | [
{
"name": "allow-commit-synchronize-with-",
"desc": ""
},
{
"name": "gres",
"desc": "Enable a device that has GRES enabled and that uses the asynchronous commit synchronize model for the ephemeral database to synchronize an ephemeral instance to the backup Routing Engine when you request a commi... | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 16.2R2 and Junos OS Evolved Release 22.1R1.
commit-synchronize-model option added in Junos OS Release 21.1R1.
delete-ephemeral-default statement added in Junos OS Release 22.1R1.
cyclic-version-for-ephemeral-default statement added in Junos OS Release 23.2R1 and Junos OS Evolved... | [
"Understanding the Ephemeral Configuration Database",
"Enabling and Configuring Instances of the Ephemeral Configuration Database",
"Committing and Synchronizing Ephemeral Configuration Data Using the NETCONF or Junos XML",
"Protocol"
] |
equals (DHCP Relay Agent) | equals {
ascii name {
drop drop;
forward-only forward-only;
local-server-group local-server-group;
}
hexadecimal name {
drop drop;
forward-only forward-only;
local-server-group local-server-group;
}
} | [edit bridge-domains name forwarding-options dhcp-relay group name relay-option],
[edit bridge-domains name forwarding-options dhcp-relay group name relay-option option-60],
[edit bridge-domains name forwarding-options dhcp-relay group name relay-option option-77],
[edit bridge-domains name forwarding-options dhcp-rela... | Configure the exact match criteria used with the DHCP relay agent selective processing feature. DHCP
relay agent compares the configured match string with the option-specific string received in DHCP
client packets. If there is an exact left-to-right match, DHCP performs the action you define for the
match criteria.
You... | [
{
"name": "ascii-string",
"desc": "ASCII string of 1 through 255 alphanumeric characters."
},
{
"name": "hexadecimal-string",
"desc": "Hexadecimal string of 1 through 255 hexadecimal characters (0 through 9, a through f, A through F). The remaining statements are explained separately. Search for... | 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.
Statement updated in Junos OS Release 17.4. | [
"Using DHCP Option Information to Selectively Process DHCP Client Traffic",
"DHCPv4 and DHCPv6 Forward-Only Action for Relay Traffic with Unknown DHCP Server Address"
] |
equals (Dynamic Profile) | equals expression; | [edit dynamic-profiles profile-name variables variable-name] | Configure an expression—a group of arithmetic operators, string operators, and operands—for a user-
defined variable that is evaluated at run time and returned as the variable value. | [
{
"name": "expression",
"desc": "Expression evaluated to return a value for the user-defined variable."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Configuring User-Defined Dynamic Variables in Dynamic Profiles",
"User-Defined Variables",
"Using Variable Expressions in User-Defined Variables"
] |
equals (Event Policy) | event1.attribute-name equals event2.attribute-name; | [edit event-options policy policy-name attributes-match] | Configure an event policy to trigger only if the event1 attribute and the event2 attribute have the same
value. The referenced events must be either the trigger event or the correlating events included in the
event policy’s within statements.
An attributes-match statement can include multiple comparison statements. The... | [
{
"name": "event1.attribute-name",
"desc": "Attribute of one event."
},
{
"name": "event2.attribute-name",
"desc": "Attribute of another event."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Use Correlated Events to Trigger an Event Policy"
] |
equals | equals {
value;
} | [edit unified-edge gateways tdf gateway-name domain-selection term term-name from called-station-
id],
[edit unified-edge gateways tdf gateway-name domain-selection term term-name from calling-
station-id],
[edit unified-edge gateways tdf gateway-name domain-selection term term-name from class],
[edit unified-edge gate... | Specify the value that the RADIUS attribute must equal.
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": "value",
"desc": "Value that the RADIUS attribute must equal."
}
] | 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"
... |
eracl-ip6-match (packet-forwarding-options) | eracl-ip6-match {
(srcip6-and-destip6 | srcip6-only);
}
} | [edit system packet-forwarding-options] | Use the options of this command to allow source and/or destination IPv6 address match conditions for
eRACL inet6 filters.
In Junos, firewall filters are classified as ingress or egress depending on where in the sequence the
packet is evaluated and action taken. Filtering IPv6 traffic on an inet6 egress interface can be... | [
{
"name": "eracl-ip6-",
"desc": ""
},
{
"name": "match",
"desc": "Configuring match conditions in a firewall filter for IPv6 source and/or destination IP addresses is only allowed if the srcip6-and-destip6 or the srcip6-only options described below are enabled. The two options cannot both be ena... | flow-tap | Statement introduced in Junos OS Release 19.1 (EX4300 and QFX5100 Series switches only). | [
"Example: Configuring an Egress Filter Based on IPv6 Source or Destination IP Addresses"
] |
eracl-profile (packet-forwarding-options) | eracl-profile {
eracl-scale;
} | [edit system packet-forwarding-options firewall]
[edit system packet-forwarding-options firewall eracl-profile eracl-scale] | Use the option of this command to configure egress firewall filters, also known as eRACLs, in scaled
mode. This feature is supported only in the egress direction (routed traffic exiting the device).
In Junos, firewall filters are classified as ingress or egress depending on where in the sequence the
packet is evaluated... | [
{
"name": "eracl-scale",
"desc": "Use this option to increase the number of egress firewall filters to 2000. When you configure an egress filter in scaled mode, the switch uses ingress TCAM space (IFP) to achieve the higher scale. NOTE: After configuring, modifying, or deleting the eracl-profile statement, ... | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 19.4R2 (QFX5220 switches). | [
"Planning the Number of Firewall Filters to Create",
"Firewall Filter Match Conditions and Actions (QFX5220, QFX5700 and the QFX5130-32CD)",
"Configuring Firewall Filters"
] |
erroneous-ccm | erroneous-ccm; | [edit protocols oam ethernet connectivity-fault-management action-profile action-profile-name
event ais-trigger-condition] | Configure the defect condition that raises an alarm indication signal when any cross-connect continuity
check messages (CCMs) with an unexpected MEP ID or an erroneous maintenance domain level are
received by the MEP. | [] | 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 Alarm Indication Signal (ETH-AIS) Function Overview",
"Configuring ETH-AIS on a CFM MEP"
] |
error (Security) | error {
(fatal | major | minor) {
threshold threshold number;
action (alarm | disable-pfe | offline-pic | log | get-state |offline | reset);
}
} | [edit chassis],
[edit chassis fpc slot-number] | Configure the threshold at which FPC errors will take the action you configure to be performed by the
device.
Some devices include an internal framework for detecting and correcting FPC errors that can have the
potential to affect services. You can classify FPC errors according to severity, set an automatic recovery
ac... | [
{
"name": "fatal",
"desc": "Fatal error on the FPC. An error that results in the blockage of a considerable amount of traffic"
},
{
"name": "major",
"desc": "Major error on the FPC. An error that results in continuing loss of packet traffic but does not"
},
{
"name": "minor",
"desc":... | interface
To view this in the configuration.
interface-control
To add this to the configuration. | Statement introduced in Junos OS Release 15.1X49-D40. | [] |
error | error {
error_id {
severity (fatal | major | minor)
state {
disable:
}
}
major {
threshold threshold-value;
action
}
minor {
threshold threshold-value;
action
}
fatal {
threshold threshold-value;
action
... | [edit chassis fpc slot-number],
[edit chassis sib slot slot-number] | Configure the threshold at which FPC or SIB errors will take the action you configure to be performed
by the device. Starting from Junos OS Release 18.1R3, you can configure error thresholds and actions at
the error scope and error category levels on MX Series routers.
Some Juniper devices include an internal framework... | [
{
"name": "fatal",
"desc": "Fatal error on the FPC. An error that results in blockage of considerable amount of traffic"
},
{
"name": "major",
"desc": "Major error on the FPC. An error that results in continuing loss of packet traffic but does not"
},
{
"name": "minor",
"desc": "Mino... | interface
To view this statement in the configuration.
interface-control
To add this statement to the configuration. | Statement introduced in Junos OS Release 13.3.
Reset-pfe error action support added to PTX10003 in Junos OS Evolved Release 22.4R1. | [
"Fabric Resiliency",
"Configure FPC Error Levels and Actions"
] |
error-id | error-id {
pfe;
severity {
(fatal | major | minor)
}
state {
disable;
}
} | [edit chassis fpc slot-number error],
[edit chassis sib slot slot-number error] | Manage an error by using the error identifier. This feature allows you to disable an error or modify its
severity. The disable option allows you to stop the error from being reported in the system until the error
is enabled again.
An error-id, a unique error identifier, is represented as a Uniform Resource Identifier (... | [
{
"name": "severity",
"desc": "Apply a new severity to the error ID. You can apply any of the following severities:"
},
{
"name": "fatal",
"desc": "Fatal error on the FPC. An error that results in blockage of considerable amount of traffic"
},
{
"name": "major",
"desc": "Major error ... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.2R1. | [
"Configure FPC Error Levels and Actions",
"Manage FPC Errors"
] |
es-options | es-options {
backup-interface interface-name;
} | [edit interfaces interface-name] | On ES interfaces, configure ES interface-specific interface properties.
The backup-interface statement is explained 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 ES PIC Redundancy"
] |
esi | esi identifier {
all-active | single-active;
auto-derive {
lacp;
}
df-election-granularity {
per-esi {
lacp-oos-on-ndf;
}
per-esi-vlan;
per-evi;
}
df-election-type {
mod;
preference {
least;
non-revertive;
... | [edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number],
[edit protocols evpn interconnect],
[edit routing-instances routing-instance-name protocols evpn interconnect] | Configure an Ethernet Segment Identifier (ESI) in either EVPN multihoming active/standby or active/
active mode by using one of the following methods:
•
Manually configure an ESI on a physical, aggregated Ethernet, or logical interface using the esi
identifier configuration statement.
•
Configure an aggregated Ethernet... | [
{
"name": "identifier",
"desc": "Ten octet value. Reserved values: ESI value 0 and all fixed filters. You can't use the reserved values for configuring a multihomed Ethernet segment. NOTE: You can't configure two interfaces (physical, logical, or aggregated Ethernet) with the same ESI value. However, start... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1.
source-bmac option introduced in Junos OS Release 18.1R1 on MX Series routers with MPCs and MICs.
auto-derive stanza introduced in Junos OS Release 18.4R1 on MX Series routers and QFX Series
switches.
Support at the following hierarchy levels introduced in Junos OS Release... | [
"Example: Configuring an ESI on a Logical Interface With EVPN Multihoming",
"Understanding Automatically Generated ESIs in EVPN Networks"
] |
esi-resolution-per-bridge-domain | esi-resolution-per-bridge-domain; | [edit protocols evpn] | Enables a device to support per bridge domain routing. By default, Junos OS Evolved devices advertise
different MPLS labels for each bridge domain in an EVPN-MPLS network configured with VLAN aware
services. In contrast, the devices running Junos OS support a single label for each routing instance.
When you have both t... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Command introduced in Junos OS Release 21.1. | [
"Changing Duplicate MAC Address Detection Settings"
] |
esmc-transmit (Chassis Synchronization) | esmc-transmit {
interfaces (all | interface-name);
}
ACX710
esmc-transmit {
interfaces {
(all | interface-name) {
squelch {
method ql-dnu;
quality-level quality-level;
}
}
}
} | [edit chassis synchronization] | Enable Ethernet Synchronization Message Channel (ESMC) packet transmission on all interfaces or on a
specific interface. | [
{
"name": "interfaces (all |",
"desc": ""
},
{
"name": "interface-name)",
"desc": "Specify the interface. To enable ESMC packet transmission on all interfaces, use all. To enable ESMC packet transmission on one interface, use the name of the interface."
}
] | 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.
bits option introduced in Junos OS Release 20.2R1. | [
"Interfaces Fundamentals"
] |
establish-tunnels | establish-tunnels (immediately | on-traffic | responder-only); | [edit services ipsec-vpn] | Specify when IKE is activated: immediately after VPN information is configured and configuration
changes are committed, or only when data traffic flows. In the second case, IKE needs to be negotiated
with the peer gateway. Starting in Junos OS Release 18.2R1, you can also specify that the MX Series
router only responds... | [
{
"name": "immediately",
"desc": "IKE is activated immediately after VPN configuration and configuration changes are committed."
},
{
"name": "on-traffic",
"desc": "IKE is activated only when data traffic flows. IKE needs to be negotiated with the peer gateway."
},
{
"name": "responder-o... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Release 8.5 of Junos OS.
responder-only option added in Junos OS Release 18.2R1. | [
"Understanding Junos VPN Site Secure"
] |
ether-options | [edit interfaces interface-name]
[edit interfaces interface-range range] | Configure ether-options properties for a Gigabit Ethernet or 10-Gigabit Ethernet interface.
In Junos OS Evolved, when you configure set interfaces interface ether-options 802.3ad ae name at the same
time as you apply a second configuration to the same interface at the [edit interfaces interface]
hierarchy, the second c... | [
{
"name": "loopback-remote",
"desc": "Starting in Junos OS Evolved Release 20.1R1, enable remote loopback."
}
] | 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.
autostate-exclude option introduced in Junos OS Release 14.1x53-D40 for QFX5100 switches only.
fec and loopback-remote options introduced in Junos OS Evolved Release 20.1R1. | [
"Gigabit Ethernet Interface",
"Configuring LACP Link Protection of Aggregated Ethernet Interfaces for Switches",
"Configuring Q-in-Q Tunneling on EX Series Switches with ELS Support"
] | |
ether-pseudowire | ether-pseudowire {
zero-control-word;
} | [edit forwarding-options enhanced-hash-key family mpls] | Load-balance IP over Ethernet pseudowire. Presence of zero-control-word in the payload indicates an
Ethernet frame.
zero-control-word
Precedes Ethernet packet to indicate the start Ethernet farme in an MPLS ether-
pseudowire payload. | [] | 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 for the MX Series. | [
"MPLS Encapsulated Payload Load-balancing Overview"
] |
ether-type (Chassis FPC) | ether-type index etype | [edit chassis fpc slot] | Add or remove a custom EtherType value in the ternary content addressable memory (TCAM) table of
EtherType values for a specified FPC slot number on the device.
Ethernet frame headers contain an EtherType field (two octets in length) to identify the protocol in the
frame's payload so that a receiving device knows how t... | [
{
"name": "index",
"desc": "(Required) EtherTypes TCAM table index where you want to replace the default EtherType value with a new EtherType value. The TCAM table can hold up to 32 EtherType entries, but ten locations (0-5 and 28-31) are reserved for default EtherTypes that can't be reconfigured. Range: 6... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Introduced in Junos OS Release 21.1R1. | [] |
ether-type (Dynamic Load Balancing) | ether-type (ipv4|ipv6|mpls|none); | [edit forwarding-options enhanced-hash-key ecmp-dlb] | EtherType for dynamic load balancing.
NOTE: On QFX5130 and QFX5700 devices, ether-type is not supported on Junos OS
Evolved. | [
{
"name": "ether-type (ipv4 | ipv6| mpls)",
"desc": "Ether-type for DLB:"
},
{
"name": "ipv4",
"desc": "Set dynamic load balancing for IPv4."
},
{
"name": "ipv6",
"desc": "Set dynamic load balancing for IPv6."
},
{
"name": "mpls",
"desc": "Set dynamic load balancing for M... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.4R1. | [
"Dynamic Load Balancing (DLB)"
] |
ether-type (VLAN) | ether-type (0x8100 | 0x88a8 | 0x9100) | [edit ethernet-switching-options dot1q-tunneling] | Configure a global value for the tag protocol identifier (EtherType) of the service VLAN tags (outer tags)
in Q-in-Q tunneling. Only one Ethertype value is supported at a time. The Ethertype value appears in
the Ethernet type field of the packet. It specifies the protocol being transported in the Ethernet frame. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
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. | [
"Example: Setting Up Q-in-Q Tunneling on EX Series Switches",
"Configuring Q-in-Q Tunneling on EX Series Switches",
"Configuring Q-in-Q Tunneling on QFX Series Switches",
"Example: Setting Up Q-in-Q Tunneling on QFX Series Switches"
] |
ether-type | ether-type ether-type; | [edit applications application application-name] | Two-octet field in an Ethernet frame that defines the protocol encapsulated in the frame payload. See
http://standards.ieee.org/develop/regauth/ethertype/eth.txt for a list of Institute of Electrical and
Electronics Engineers (IEEE) EtherTypes.
NOTE: To create a FIP application, use the EtherType 0x8914. | [
{
"name": "type",
"desc": "Identifier for the EtherType."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1. | [
"Defining an Application for DCBX Application Protocol TLV Exchange",
"Example: Configuring DCBX Application Protocol TLV Exchange",
"Understanding DCBX Application Protocol TLV Exchange"
] |
ethernet (Aggregated Devices) | ethernet {
device-count number;
lacp {
link-protection {
non-revertive;
}
system-priority;
} | [edit chassis aggregated-devices] | Configure properties for Ethernet aggregated devices on the switch.
The remaining statement is explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Configuring Aggregated Ethernet Links (CLI Procedure)",
"Configuring LACP Link Protection of Aggregated Ethernet Interfaces for Switches",
"Junos OS Ethernet Interfaces Configuration Guide"
] |
ethernet (Alarm) | ethernet {
link-down (red | yellow | ignore);
} | [edit chassis alarm],
[edit chassis interconnect-device name alarm],
[edit chassis node-group name alarm] | Configure alarms for an Ethernet interface. | [] | 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. | [] |
ethernet (Chassis) | ethernet {
device-count number;
lacp {
link-protection {
non-revertive;
}
system-priority number;
}
} | [edit chassis aggregated-devices] | Configure properties for aggregated Ethernet devices. | [] | 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. | [] |
ethernet (CoS for Multidestination Traffic) | ethernet {
broadcast forwarding-class-name;
} | [edit class-of-service multi-destination family] | Specify the Ethernet broadcast traffic family.
NOTE: On EX4300 switches, including switches in a virtual chassis or virtual chassis
fabric configuration, you cannot explicitly configure multi-destination (broadcast,
multicast, and destination lookup fail) traffic classification. By default, all multi-
destination traff... | [] | 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"
] |
ethernet (Protocols OAM) | [edit protocols oam] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.2.
connectivity-fault-management introduced in Junos OS Release 10.2 for EX Series switches. | [
"Enabling IEEE 802.3ah OAM Support",
"Example: Configuring Ethernet OAM Link Fault Management"
] | |
ethernet | ethernet {
device-count number;
} | [edit chassis aggregated-devices],
[edit chassis node-group aggregated-devices] | Configure properties for aggregated Ethernet devices on the switch.
The remaining statement is explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Understanding Link Aggregation and Link Aggregation Control Protocol in a Junos Fusion",
"Configuring Link Aggregation",
"Junos OS Network Interfaces Library for Routing Devices"
] |
ethernet-frame-size | ethernet-frame-size ethernet-frame-size; | [edit protocols oam fabric flow-specs flow-specification-name] | Configure the Ethernet frame size in the flow specification parameters for internal fabric monitoring. | [
{
"name": "ethernet-frame-size",
"desc": "Integer defining the size (in bytes) of the Ethernet frame. Range: 256 to 9116 bytes"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.2. | [
"Overview of Internal Fabric Monitoring",
"Configuring a Fabric Maintenance Association",
"Configuring Flow Specifications"
] |
ethernet-policer-profile | ethernet-policer-profile {
input-priority-map {
ieee802.1p premium [ values ];
}
output-priority-map {
classifier {
premium {
forwarding-class class-name {
loss-priority (high | low);
}
}
}
}
policer... | [edit interfaces interface-name gigether-options ethernet-switch-profile],
[edit interfaces interface-name aggregated-ether-options ethernet-switch-profile] | NOTE: On QFX Series standalone switches, this statement hierarchy is only supported
on the Enhanced Layer 2 Switching CLI.
For Gigabit Ethernet IQ, 10-Gigabit Ethernet, Gigabit Ethernet PICs with SFPs (except the 10-port
Gigabit Ethernet PIC and the built-in Gigabit Ethernet port on the M7i router), and 100-Gigabit Eth... | [] | 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"
] |
ethernet-ring | ethernet-ring ring-name {
control-vlan (vlan-id | vlan-name);
data-channel {
vlan number
}
east-interface {
control-channel channel-name {
vlan number;
interface name interface-name
}
}
guard-interval number;
node-id mac-address;
restore-i... | [edit protocols protection-group] | For Ethernet PICs on MX Series routers or for EX Series switches, , specify the Ethernet ring in an
Ethernet ring protection switching configuration. | [
{
"name": "ring-name",
"desc": "Name of the Ethernet protection ring."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.4.
Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 14.153-D10 for QFX Series switches. | [
"Ethernet Ring Protection Switching Overview",
"Example: Configuring Ethernet Ring Protection Switching on EX Series Switches",
"Example: Configuring Ethernet Ring Protection Switching on QFX Series and EX Series Switches",
"Supporting ELS",
"Configuring Ethernet Ring Protection Switching on Switches (CLI P... |
ethernet-switch-profile | ethernet-switch-profile {
ethernet-policer-profile {
input-priority-map {
ieee802.1p premium [values];
}
output-priority-map {
classifier {
premium {
forwarding-class class-name {
loss-priority (high | low);
... | [edit interfaces interface-name gigether-options],
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name ether-options] | NOTE: On QFX Series standalone switches, the ethernet-policer-profile CLI hierarchy and
the mac-learn-enable statement are supported only on the Enhanced Layer 2 Switching CLI.
For Gigabit Ethernet IQ, 10-Gigabit Ethernet IQ2 and IQ2-E, and Gigabit Ethernet PICs with SFPs
(except the 10-port Gigabit Ethernet PIC, aggre... | [] | 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.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Metro Routers. | [
"Configuring Gigabit Ethernet Policers",
"Configuring Gigabit Ethernet Policers",
"Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview",
"Configuring Q-in-Q Tunneling on EX Series Switches with ELS Support"
] |
ethernet-switching (Port Mirroring) | ethernet-switching;
output {
interface interface-name {
}
no-filter-check;
}
vlan vlan-name {
no-tag;
}
} | [edit forwarding-options port-mirroring [instance name] family] | Specify that the output interface for the port mirror will be configured as an ethernet-switching interface. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2. | [
"Understanding Port Mirroring and Analyzers",
"Configuring Port Mirroring",
"Examples: Configuring Port Mirroring for Local Analysis"
] |
ethernet-switching (firewall profiles) | ethernet-switching {
(profile1 | profile2 | udf-profile1);
egress {
profile1;
}
} | [edit system packet-forwarding-options firewall profiles] | Configure the profile options for family ethernet-switching filters. You can use the command show pfe filter
hw profile-info to view the hardware profile information.
NOTE: Changing the profile options will restart the PFE when committed. | [
{
"name": "profile1",
"desc": "Selects matches of profile1 (refer to show pfe filter hw profile-info); restarts PFE"
},
{
"name": "profile2",
"desc": "Selects matches of profile2 (refer to show pfe filter hw profile-info); restarts PFE"
},
{
"name": "udf-profile1",
"desc": "Selects m... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced prior to Junos OS Release 21.1R1 and Junos OS Evolved Release 21.1R1.
egress profile1 option introduced in Junos OS Evolved Release 25.4R1 | [
"Overview of Firewall Filters (QFX Series)"
] |
ethernet-switching | ethernet-switching {
filter {
group filter-group-number;
input filter-name;
input-list [ filter-names ];
output filter-name;
output-list [ filter-names ];
}
interface-mode (access | trunk);
recovery-timeout seconds;
storm-control profile-name;
vlan {
... | [edit interfaces ge-chassis/slot/port unit logical-unit-number] family | Configure Ethernet switching protocol family information for the logical interface.
The remaining statements are explained separately. See CLI Explorer.
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. | [
"Configuring Gigabit and 10-Gigabit Ethernet Interfaces for EX4600 and QFX Series Switches",
"JUNOS Software Network Interfaces Configuration Guide"
] |
ethernet-switching | ethernet-switching {
block-non-ip-all;
bpdu-vlan-flooding;
bypass-non-ip-unicast;
no-packet-flooding {
no-trace-route;
}
} | For EX Series and QFX Series switches:
[edit interfaces ge-chassis/slot/port unit logical-unit-number] family
For SRX Series Firewalls:
[edit security flow] | Configure Ethernet switching protocol family information for the logical interface. Changes default Layer
2 forwarding behavior.
The remaining statements are explained separately. See CLI Explorer.
Default
You must configure a logical interface to be able to use the physical device. | [
{
"name": "block-non-ip-all",
"desc": "Block all Layer 2 non-IP and non-ARP traffic, including multicast and broadcast"
},
{
"name": "bpdu-vlan-flooding",
"desc": "Set 802.1D bridge protocol data unit (BPDU) flooding based on VLAN on which"
},
{
"name": "bypass-non-ip-unicast",
"desc... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
security—To view this in the configuration.
security-control—To add this to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring Gigabit and 10-Gigabit Ethernet Interfaces for EX4600 and QFX Series Switches",
"Understanding Traffic Processing on Security Devices",
"JUNOS Software Network Interfaces Configuration Guide"
] |
ethernet-switching-options | [edit] | Configure Ethernet switching options.
The remaining statements are explained separately. See CLI Explorer. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Understanding Port Mirroring and Analyzers",
"Understanding How to Protect Access Ports from Common Attacks",
"Port Security Features",
"Understanding BPDU Protection for STP, RSTP, and MSTP",
"Understanding Redundant Trunk Links (Legacy RTG Configuration)",
"Understanding Storm Control",
"Understandin... | |
ethernet-vlan (Protocols Link Management) | ethernet-label {
vlan-id-range vlan-id-range;
} | [edit protocols link-management te-link te-link-name] | Specify the TE-link to be used for Layer 2 VLAN label-switched path (LSP). | [
{
"name": "vlan-id-range vlan-id-range",
"desc": "Pool of VALN IDs."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [] |
eui-64 | eui-64; | [edit interfaces interface-name unit number family inet6 address address] | For interfaces that carry IP version 6 (IPv6) traffic, automatically generate the host number portion of
interface addresses. | [] | 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"
] |
evc-protocol cfm | evc-protocol cfm {
maintenance-association association-name | vpls routing-instance routing-id;
maintenance-domain domain-id;
mep-id mep-id;
} | [edit protocols oam ethernet evcs] | Specify connectivity fault management (CFM) or virtual private LAN service (VPLS) as the Ethernet
virtual connection (EVC) protocol. | [
{
"name": "management-domain domain-id",
"desc": "(Optional) For CFM, specify the CFM management domain."
},
{
"name": "management-association",
"desc": ""
},
{
"name": "association-id",
"desc": "(Optional) For CFM, specify the CFM management association."
},
{
"name": "routi... | 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.
mep-id mep-id statement introduced in Junos OS Release 15.1. | [
"Configuring Ethernet Local Management Interface"
] |
evcs | evcs evc-id {
evc-protocol cfm;
remote-uni-count count;
multipoint-to-multipoint;
} | [edit protocols oam ethernet] | On MX Series routers with ge, xe, or ae interfaces, configure an OAM Ethernet virtual connection. | [
{
"name": "remote-uni-count count",
"desc": "(Optional) Specify the number of remote UNIs in the EVC configuration, the"
},
{
"name": "multipoint-to-multipoint",
"desc": "(Optional) Specify multiple points in the EVC configuration, the default is point-to-point if remote-uni-count is 1."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5. | [
"Configuring Ethernet Local Management Interface"
] |
event (CFM) | event {
adjacency-loss;
interface-status-tlv {
down;
lower-layer-down;
}
port-status-tlv blocked;
rdi;
} | [edit protocols oam ethernet connectivity-fault-management action-profile profile-name] | Configure threshold values for connectivity fault management events in an action profile. | [
{
"name": "adjacency-loss",
"desc": "Connectivity is lost."
},
{
"name": "interface-status-tlv [ lower-layer-down",
"desc": ""
},
{
"name": "down ]",
"desc": "Values that need to be monitored in interface status TLV."
},
{
"name": "port-status-tlv",
"desc": "Values that n... | 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 a CFM Action Profile to Specify CFM Actions for CFM Events"
] |
event (Enhanced Subscriber Management) | event {
catastrophic-failure {
reboot (master | standby);
}
} | [edit system services subscriber-management overrides] | Configure the router to detect a type of event and automatically take action when the event is detected. | [
{
"name": "catastrophic-failure",
"desc": "Specify that the event is a corruption of the shared memory."
},
{
"name": "reboot (master |",
"desc": ""
},
{
"name": "standby)",
"desc": "Specify which Routing Engine is rebooted when the shared memory corruption is detected. You can confi... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.1R1. | [
"Configuring Junos OS Enhanced Subscriber Management"
] |
event (LFM) | [edit protocols oam ethernet link-fault-management action-profile] | Configure link events in an action profile for Ethernet OAM link fault management (LFM).
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.
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Monitoring Protocol Status",
"Configuring Ethernet OAM Link Fault Management"
] | |
event | event index {
community community-name;
description description;
type type;
} | [edit snmp rmon] | Configure RMON event entries. | [
{
"name": "index",
"desc": "Identifier for a specific event entry."
}
] | 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"
] |
event-options | event-options {
destinations {
destination-name {
archive-sites {
url <password password>;
}
transfer-delay seconds;
}
}
event-script {
dampen {
dampen-options {
cpu-factor cpu-factor;
li... | [edit] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5. | [] |
event-rate (Next Gen Services Service-Set Local System Logging) | event-rate rate-per-second; | [edit services services-set name syslog] | Rate at which log messages are sent per second to the local file. | [] | system | Statement introduced in Junos OS Release 19.3R2. | [
"Understanding Next Gen Services CGNAT Global System Logging",
"Enabling Global System Logging for Next Gen Services",
"Configuring System Logging to One or More Remote Servers for Next Gen Services",
"Configuring Local System Logging for Next Gen Services"
] |
event-rate | event-rate rate; | [edit security log]
[edit logical-systems name security log]
[edit tenants tenant-name security log] | Limits the rate at which logs will be streamed per second. | [
{
"name": "rate",
"desc": "Rate at which logs will be streamed per second."
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 10.0.
The [edit logical-systems name security log] and [edit tenants tenant-name security log] hierarchy levels
introduced in Junos OS Release 19.1R1. | [] |
event-script (Event Options) | event-script {
dampen {
dampen-options {
cpu-factor cpu-factor;
line-interval line-interval;
time-interval time-interval;
}
}
file filename {
cert-file path;
checksum hash-algorithm hash-value;
dampen {
dampen-options {... | [edit event-options] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and resto... | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Store and Enable Junos Automation Scripts"
] |
event-script (Event Policy) | event-script filename {
arguments {
argument-name argument-value;
}
destination destination-name {
retry-count count retry-interval seconds;
transfer-delay seconds;
}
output-filename filename;
output-format (text | xml);
user-name username;
} | [edit event-options policy policy-name then] | Configure an event policy to execute one or more event scripts when triggered.
The remaining statements are explained separately. See CLI Explorer. | [] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.6. | [
"Execute Event Scripts in an Event Policy",
"Configure an Event Policy to Pass Arguments to an Event Script"
] |
event-thresholds | event-thresholds {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
} | [edit protocols oam link-fault-management interface interface-name] | Configure threshold limit values for link events in periodic OAM PDUs.
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 8.4. | [
"Configuring Threshold Values for Local Fault Events on an Interface"
] |
events (Event Policy Correlated Events) | events [ events ]; | [edit event-options policy policy-name within seconds] | Configure events that must occur within a specified time interval before one of the trigger events in
order for the event policy to be triggered. | [
{
"name": "[ events ]",
"desc": "List of events. Events can be internally generated, or they can be generated by Junos OS processes."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Use Correlated Events to Trigger an Event Policy"
] |
events (Event Policy Trigger Events) | events [ events ]; | [edit event-options policy policy-name] | Configure one or more events that will trigger the event policy. If one or more of the listed events
occurs, the policy is executed. | [
{
"name": "[ events ]",
"desc": "List of events. Events can be generated by Junos OS processes, or they can be internally generated."
}
] | maintenance—To view or add this statement in the configuration. | Statement introduced in Junos OS Release 7.5. | [
"Use Correlated Events to Trigger an Event Policy"
] |
evpn (Easy EVPN LAG Configuration) | evpn {
defaults-override {
no-aggregate-device-count-config;
no-loop-detect-config;
no-platform-defaults-config;
no-policy-and-routing-options-config;
no-storm-control-config;
no-underlay-config
}
device-attribute {
loopback {
peer1-subnet peer1-subnet;
peer2-subnet peer2-... | [edit services] | Specify parameters to generate an Ethernet VPN (EVPN) fabric configuration with one or more
customer edge (CE) devices or end servers that are:
•
Single-homed to a provider edge (PE) device in the EVPN fabric.
•
Multihomed on an Ethernet segment identified by an Ethernet segment identifier (ESI), and
connected in a lin... | [
{
"name": "defaults-override",
"desc": "Select options to skip statements that the commit script would otherwise include by"
},
{
"name": "default when it generates the configuration:",
"desc": ""
},
{
"name": "no-aggregate-device-count-config",
"desc": "Don't derive and include the ... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.2R1. | [
"Easy EVPN LAG (EZ-LAG) Configuration"
] |
evpn (EVPN Multicast Replication) | evpn {
irb {
(local-only | local-remote | oism | enhanced-oism);
}
smet-forwarding;
smet-nexthop-limit smet-nexthop-limit;
} | [edit forwarding-options multicast-replication] | Enable multicast forwarding options in an EVPN-VXLAN or EVPN-MPLS network.
The irb options enable one of the supported integrated routing and bridging multicast modes in an
EVPN-VXLAN network. The available irb options are mutually exclusive. Also, only the local-remote, oism,
and enhanced-oism modes support forwarding... | [
{
"name": "smet-forwarding",
"desc": "Enables selective multicast Ethernet Tag (SMET) forwarding mode in an EVPN-MPLS network."
},
{
"name": "smet-nexthop-limit smet-",
"desc": ""
},
{
"name": "nexthop-limit",
"desc": "Configures a limit for the number of SMET next hops for selective... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | smet-forwarding option introduced in Junos OS Evolved Release 24.4R1. | [
"Overview of Selective Multicast Forwarding",
"Configuring the number of SMET Nexthops"
] |
evpn | evpn {
advertise-zero-ethernet-tag;
assisted-replication {
leaf {
replicator-activation-delay seconds;
}
replicator {
inet ip;
vxlan-encapsulation-source-ip (assisted-replicator-ip | ingress-replication-ip |
retain-incoming-source-ip);
}
}... | [edit logical-systems logical-system-name routing-instances routing-instance-name protocols],
[edit protocols],
[edit routing-instances routing-instance-name protocols] | CAUTION: Enabling tracing can adversely impact scale and performance and may
increase security risk. We strongly recommend using the trace, tracing, or traceoptions
commands only under the guidance of a JTAC support engineer. After collecting the
debug information, immediately disable tracing to minimize risk and rest... | [
{
"name": "colored-tunnel-address",
"desc": "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."
},
{
"name": "designated-forwarder-election-",
"desc": ""
},
{
"n... | 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.
designated-forwarder-election-hold-time seconds statement introduced in Junos OS Release 14.1.
extended-vlan-list vlan-id | [vlan-id set] statement introduced in Junos OS Release 14.1.
NOTE: QFX10000 switches don't support the extended-vlan-list statement.
designated-forwa... | [
"Implementing EVPN-VXLAN for Data Centers",
"Configuring EVPN Routing Instances",
"Tracing EVPN Traffic and Operations",
"Provider Backbone Bridging (PBB) and EVPN Integration Overview",
"Optimized Inter-Subnet Multicast in EVPN Networks"
] |
evpn-aliasing-optimize | evpn-aliasing-optimize; | [edit logical-systems logical-system-name routing-options forwarding-table ],
[edit routing-options forwarding-table] | Enables EVPN aliasing optimization. EVPN aliasing optimization allows the device to quickly recover
when a link to a multihomed PE device fails. It reduces reduces convergence time, and improves device
performance. By default, evpn-aliasing-optimize is enabled on the PTX10008 Router. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Command introduced in Junos Evolve OS Release 21.1. | [] |
evpn-ssm-reports-only | evpn-ssm-reports-only; | [edit bridge-domains bridge-domain-name protocols igmp-snooping],
[edit bridge-domains bridge-domain-name protocols mld-snooping],
[edit protocols igmp-snooping vlan vlan-name],
[edit protocols mld-snooping vlan vlan-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols igmp-
... | Accept and process only (S,G) reports for source-specific multicast (SSM) groups when:
•
You configure Internet Group Management Protocol (IGMP) snooping for IGMP version 3 (IGMPv3)
with IPv4 multicast traffic in an EVPN network.
•
You configure Multicast Listener Discovery (MLD) snooping for MLD version 2 (MLDv2) wit... | [] | routing | Statement introduced in Junos OS Release 18.4R1.
Statement added in Junos OS Releases 19.4R2 and 20.3R1 on ACX Series routers with EVPN multicast
support. | [
"Overview of Multicast Forwarding with IGMP or MLD Snooping in an EVPN-MPLS Environment",
"Overview of Multicast Forwarding with IGMP Snooping or MLD Snooping in an EVPN-VXLAN",
"Environment",
"Configure Multicast Forwarding with MLD Snooping in an EVPN-MPLS Environment"
] |
evpn-vxlan (Easy EVPN LAG Configuration) | evpn-vxlan {
dhcp-relay name {
dhcp-server-address dhcp-server-address;
relay-source relay-source;
vrf-instance vrf-instance;
}
irb irb-instance {
apply-config-groups apply-config-groups;
instance {
mac-vrf-instance mac-vrf-instance;
vrf-instance vrf-instance;
}
subnet-addr... | [edit services evpn] | Specify parameters the device uses to generate an Ethernet VPN (EVPN) fabric configuration with
Virtual Extensible LAN (VXLAN) encapsulation.
You use the statements in the [edit services evpn] hierarchy level to simplify configuring an EVPN fabric
with Ethernet segment identifier (ESI) link aggregation groups (LAGs) in... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 and Junos OS Evolved Release 23.2R1. | [
"Easy EVPN LAG (EZ-LAG) Configuration"
] |
evpn-vxlan | evpn-vxlan {
gbp {
ingress-enforcement;
ingress-src-tag filter <gbp-filter>
mac-ip-inter-tagging;
tag-only-policy;
}
host-originated-packets {
gbp-src-tag gbp-src-tag;
}
reroute-address {
inet address;
inet6 address;
}
shared-tunnels;
... | [edit forwarding-options],
[edit logical-systems name routing-instances name forwarding-options] | Set various global or per-routing-instance options in an EVPN-VXLAN fabric. | [
{
"name": "gbp ingress-enforcement",
"desc": "Configure Group Based Policy (GBP) policy enforcement at the ingress node."
},
{
"name": "gbp ingress-src-tag filter <gbp-",
"desc": ""
},
{
"name": "filter>",
"desc": "Associate the specified <gbp-filter> with the routing instance. Use t... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.4R1 for supported EX4100, EX4400, EX4650, and
QFX5120 Series switches.
tag-only-policy option introduced in 23.2R1 for the QFX5120-48YM, QFX5120-48Y, and EX4650-48Y
Series switches.
reroute-address option introduced in Junos OS 21.3R1 for the QFX5110 and QFX5120 Series swtich... | [
"Microsegmentation Using Group-Based Policies",
"Fast Reroute for Egress Link Protection with EVPN-VXLAN Multihoming"
] |
examine-dhcp | (examine-dhcp | no-examine-dhcp) {
forwarding-class class-name;
} | [edit ethernet-switching-options secure-access-port vlan (all | vlan-name)] | Enable DHCP snooping on all VLANs or on the specified VLAN.
NOTE: If you configure DHCP for all VLANs and you enable a different port security
feature on a specific VLAN, you must also explicitly enable DHCP snooping on that
VLAN. Otherwise, the default value of no DHCP snooping applies to that VLAN.
•
examine-dhcp—Ena... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.0. | [
"Example: Configuring Port Security (non-ELS)",
"Example: Protecting Against Address Spoofing and Layer 2 DoS Attacks",
"Example: Protecting Against ARP Spoofing Attacks",
"Example: Prioritizing Snooped and Inspected Packet",
"Enabling DHCP Snooping (non-ELS)",
"Enabling DHCP Snooping (J-Web Procedure)"
] |
examine-dhcpv6 | examine-dhcpv6 {
forwarding-class class-name;
} | [edit ethernet-switching-options secure-access-port vlan (all | vlan-name)] | Enable DHCPv6 snooping on all VLANs or on the specified VLAN.
NOTE: If you configure DHCP for all VLANs and you enable a different port security
feature on a specific VLAN, you must also explicitly enable DHCP snooping on that
VLAN. Otherwise, the default value of no DHCP snooping applies to that VLAN.
When DHCP snoopi... | [] | 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. | [
"Example: Configuring Port Security (non-ELS)",
"Example: Protecting Against Address Spoofing and Layer 2 DoS Attacks",
"Example: Protecting Against ARP Spoofing Attacks",
"Example: Prioritizing Snooped and Inspected Packet",
"Enabling DHCP Snooping (non-ELS)",
"Enabling DHCP Snooping (J-Web Procedure)"
] |
examine-fip | examine-fip {
examine-vn2vn {
beacon-period milliseconds;
}
fc-map fc-map-value;
no-fip-snooping-scaling;
} | [edit ethernet-switching-options secure-access-port vlan (all | vlan-name)] | NOTE: This statement supports the original CLI. If your switch runs the Enhanced Layer
2 Software (ELS) CLI, see "examine-vn2vf" on page 6861 for VN_Port to VF_Port
(VN2VF_Port) FIP snooping, and see "examine-vn2vn" on page 6863 for VN_Port to
VN_Port (VN2VN_Port) FIP snooping. For ELS details, see Using the Enhanced L... | [] | 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.
Statement examine-vn2vn introduced in Junos OS Release 12.2 for the QFX Series.
Statement no-fip-snooping-scaling introduced in Junos OS Release 13.2X52-D10 for the QFX Series. | [
"Example: Configuring an FCoE Transit Switch",
"Configuring VN2VF_Port FIP Snooping and FCoE Trusted Interfaces on an FCoE Transit Switch"
] |
examine-vn2vf | examine-vn2vf {
} | [edit vlans vlan-name forwarding-options fip-security] | NOTE: This statement supports the Enhanced Layer 2 Software (ELS) CLI. If your switch
runs the original (non-ELS) software, see examine-fip. For ELS details, see Using the
Enhanced Layer 2 Software CLI.
Enable VN_Port to VF_Port (VN2VF_Port) FIP snooping on the specified VLAN. Ensure that the VLAN is
a dedicated FCoE V... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced for the ELS CLI in Junos OS Release 13.2 for the QFX Series. | [
"Understanding VN_Port to VF_Port FIP Snooping on an FCoE Transit Switch",
"Understanding FCoE Transit Switch Functionality",
"Configuring VN2VF_Port FIP Snooping and FCoE Trusted Interfaces on an FCoE Transit Switch"
] |
examine-vn2vn | examine-vn2vn {
beacon-period milliseconds;
} | Original CLI
[edit ethernet-switching-options secure-access-port vlan (all | vlan-name) examine-fip]
ELS CLI for Platforms that Support FCoE
[edit vlans vlan-name forwarding-options fip-security]
NOTE: The examine-vn2vn configuration statement is in a different hierarchy on the original
CLI than on the Enhanced Layer ... | Enable VN_Port to VN_Port (VN2VN) FIP snooping on a specified VLAN. The VLAN must be a dedicated
FCoE VLAN that transports only FCoE traffic. A VLAN cannot support VN2VN FIP snooping and
VN_Port to VF_Port FIP snooping (VN2VF) simultaneously. Configure separate VLANs for VN2VN FIP
snooping and VN2VF FIP snooping.
When ... | [] | 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.
Statement introduced for the ELS CLI in Junos OS Release 13.2 for the QFX Series. | [
"Example: Configuring VN2VN_Port FIP Snooping (FCoE Hosts Directly Connected to the Same FCoE",
"Transit Switch)",
"Example: Configuring VN2VN_Port FIP Snooping (FCoE Hosts Directly Connected to Different FCoE",
"Transit Switches)",
"Example: Configuring VN2VN_Port FIP Snooping (FCoE Hosts Indirectly Connec... |
exceed-action | exceed-action {
drop;
syslog;
} | [edit services service-set services-set-name subscriber-profile profile-name max-data-sessions-
per-subscriber] | Specify the action if the maximum data sessions per subscriber exceed the maximum limit. You must
also specify the drop rate of the packets for drop and system log details for syslog. | [] | 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. | [] |
exception (Security Content Filtering) | exception list-name; | [edit security utm default-configuration]
[edit security utm feature-profile content-filtering profile profile-name block-mime] | Configure the content filter to use an exception list to the MIME block list (custom objects). | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Content Filtering Overview"
] |
exception | exception listname; | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus mime-whitelist]
[edit security utm feature-profile anti-virus mime-whitelist list listname] | Configure the antivirus scanner to use an exception list to the MIME bypass list (custom objects). To use
the exception list, you first create a allowlist custom-object list with the list statement. The system will
first look at any existing allowlist mime pattern. If it matches an item, it will then continue to look f... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
exception-reporting | exception-reporting {
category category-name {
inline-monitoring-instance inline-monitoring-instance;
}
} | [edit chassis fpc slot-number pfe identifier] | Enable reporting of exceptions in the forwarding path. | [] | 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"
] |
exceptions | exceptions {
forwarding;
routing;
} | [edit system resiliency] | Subscribe to forwarding, operating system, and routing exceptions for the on-box collector.
Default
The on-box collector is disabled. | [
{
"name": "forwarding",
"desc": "Subscribe to forwarding exceptions."
},
{
"name": "os",
"desc": "(Junos OS only) Subscribe to operating system exceptions."
},
{
"name": "routing",
"desc": "Subscribe to routing exceptions."
}
] | system—To view this statement in the configuration.
system-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"
] |
excess-bandwidth-share | excess-bandwidth-share (proportional value | equal); | [edit class-of-service interfaces interface-set interface-set-name] | Specify the method of sharing excess bandwidth in a hierarchical scheduler environment. With
hierarchical schedulers, you can provide shaping and scheduling at the service VLAN level as well as
other levels, such as the physical interface. You can also group a set of logical interfaces and then apply
scheduling and sha... | [
{
"name": "equal",
"desc": "Share excess bandwidth equally among the configured interfaces."
},
{
"name": "proportional value",
"desc": "(Default) Share excess bandwidth proportionally according to the specified value. In this mode, the excess bandwidth is shared at the ratio of the logical inte... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.5. | [
"Configuring Hierarchical Schedulers for CoS",
"Configuring Interface Sets",
"Enhanced Queuing DPC CoS Properties",
"Configuring MDRR on Enhanced Queuing DPCs"
] |
excess-burst-size (QFX) | excess-burst-size bytes; | [edit firewall three-color-policer policer-name single-rate] | Configure the maximum number of bytes allowed for incoming traffic to burst above the committed
information rate and still be marked with medium-high packet loss priority (yellow). Packets that exceed
the excess burst size (EBS) are marked with high packet loss priority (red).
NOTE: When you include the excess-burst-si... | [
{
"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 11.1. | [
"Configuring Two-Color and Three-Color Policers to Control Traffic Rates",
"Overview of Policers"
] |
excess-burst-size | excess-burst-size bytes; | [edit dynamic-profiles profile-name firewall three-color-policer name single-rate],
[edit firewall three-color-policer policer-name single-rate] | For a single-rate three-color policer, configure the excess burst size (EBS) as a number of bytes. The EBS
allows for moderate periods of bursting traffic that exceeds both the committed information rate (CIR)
and the committed burst size (CBS).
NOTE: When you include the excess-burst-size statement in the configuratio... | [
{
"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] hierarchy level introduced in Junos Release OS 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"
] |
excess-priority (Dynamic Schedulers) | excess-priority (low | high | $junos-cos-scheduler-excess-priority | none); | [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] | Determine the priority of excess bandwidth traffic on a scheduler in a dynamic profile. | [
{
"name": "low",
"desc": "Excess traffic for this scheduler has low priority."
},
{
"name": "high",
"desc": "Excess traffic for this scheduler has high priority."
},
{
"name": "$junos-cos-scheduler-excess-priority",
"desc": "Variable for the excess-priority that is replaced with a va... | 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.
none option added in Junos OS Release 11.4. | [
"Managing Excess Bandwidth Distribution for Dynamic CoS on MIC and MPC Interfaces"
] |
excess-priority | excess-priority [ low | medium-low | medium-high | high | none]; | [edit class-of-service schedulers scheduler-name] | Determine the priority of excess bandwidth traffic on a scheduler.
NOTE: For Link Services IQ (LSQ) PICs or Multiservices PIC (MS-PICs), the excess-priority
statement is allowed for consistency, but ignored. If an explicit priority is not configured
for these interfaces, a default low priority is used. This default pr... | [
{
"name": "low",
"desc": "Excess traffic for this scheduler has low priority."
},
{
"name": "medium-low",
"desc": "Excess traffic for this scheduler has medium-low priority."
},
{
"name": "medium-high",
"desc": "Excess traffic for this scheduler has medium-high priority."
},
{
... | 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.
Option none introduced in Junos OS Release 11.4. | [
"Configuring Excess Bandwidth Sharing on IQE PICs",
"Bandwidth Sharing on Nonqueuing Packet Forwarding Engines Overview",
"Managing Excess Bandwidth Distribution on Static Interfaces on MICs and MPCs"
] |
excess-rate (Dynamic Schedulers) | excess-rate percent (percentage | $junos-cos-scheduler-excess-rate | proportion value); | [edit dynamic-profiles profile-name class-of-service schedulers scheduler-name] | Determine the percentage of excess bandwidth traffic to share. | [
{
"name": "percentage",
"desc": "Percentage of the excess bandwidth to share."
},
{
"name": "$junos-cos-scheduler-excess-rate",
"desc": "Variable for the excess rate that is specified for a scheduler. The variable"
},
{
"name": "value",
"desc": "Proportion of the excess bandwidth to ... | 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. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Managing Excess Bandwidth Distribution for Dynamic CoS on MIC and MPC Interfaces"
] |
excess-rate (Dynamic Traffic Shaping) | excess-rate (percent percentage | $junos-cos-excess-rate) | proportion value); | [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | For an MPC interface, determine the percentage or proportion of excess bandwidth traffic to share for
all priorities of traffic. | [
{
"name": "percentage",
"desc": "Percentage of the excess bandwidth to share."
},
{
"name": "value",
"desc": "Proportion of the excess bandwidth to share."
},
{
"name": "$junos-cos-excess-rate",
"desc": "Variable for the excess rate that is specified for the logical interface. The va... | 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. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Managing Excess Bandwidth Distribution for Dynamic CoS on MIC and MPC Interfaces"
] |
excess-rate (Schedulers) | excess-rate (percent percentage | proportion value); | [edit class-of-service schedulers scheduler-name],
[edit class-of-service traffic-control-profiles traffic-control-profile-name] | Determine the percentage of excess port bandwidth for which a queue (forwarding class) that is not a
strict-high priority queue or forwarding class set (priority group) can contend. Excess bandwidth is the
extra port bandwidth left after strict-high priority queues and the guaranteed minimum bandwidth
requirements of o... | [
{
"name": "percentage",
"desc": "Percentage of the excess bandwidth to share."
},
{
"name": "value",
"desc": "Proportion of the excess bandwidth to share."
}
] | 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. | [
"Configuring Scheduler Transmission Rate",
"Configuring Excess Bandwidth Sharing on IQE PICs",
"Allocating Excess Bandwidth Among Frame Relay DLCIs on Multiservices PICs",
"Managing Excess Bandwidth Distribution on Static Interfaces on MICs and MPCs",
"Defining CoS Queue Schedulers for Port Scheduling",
"... |
excess-rate-high (Dynamic Traffic Shaping) | excess-rate-high ((percent percentage | $junos-cos-excess-rate-high) | proportion value); | [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | For an MPC/MIC interface, determine the percentage of excess bandwidth for high-priority traffic to
share. | [
{
"name": "percentage",
"desc": "Percentage of the excess bandwidth to share."
},
{
"name": "value",
"desc": "Proportion of the excess bandwidth to share."
},
{
"name": "$junos-cos-excess-rate-high",
"desc": "Variable for the excess rate that is specified for high-priority traffic on... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Managing Excess Bandwidth Distribution for Dynamic CoS on MIC and MPC Interfaces"
] |
excess-rate-high | excess-rate-high (percent percentage | proportion value); | [edit class-of-service traffic-control-profiles traffic-control-profile-name] | For a MIC or MPC interface, determine the percentage of excess bandwidth from high-priority traffic to
share. | [
{
"name": "percentage",
"desc": "Percentage of the excess bandwidth to share."
},
{
"name": "proportion",
"desc": "Proportion of the excess bandwidth to share."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Managing Excess Bandwidth Distribution on Static Interfaces on MICs and MPCs"
] |
excess-rate-low (Dynamic Traffic Shaping) | excess-rate-low ((percent percentage | $junos-cos-excess-rate-low) | proportion value); | [edit dynamic-profiles profile-name class-of-service traffic-control-profiles profile-name] | For an MPC/MIC interface, determine the percentage of excess bandwidth for low-priority traffic to
share. | [
{
"name": "percentage",
"desc": "Percentage of the excess bandwidth to share."
},
{
"name": "value",
"desc": "Proportion of the excess bandwidth to share."
},
{
"name": "$junos-cos-excess-rate-low",
"desc": "Variable for the excess rate that is specified for low-priority traffic on t... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Guidelines for Configuring Dynamic CoS for Subscriber Access",
"Managing Excess Bandwidth Distribution for Dynamic CoS on MIC and MPC Interfaces"
] |
excess-rate-low | excess-rate-low (percent percentage | proportion value); | [edit class-of-service traffic-control-profiles traffic-control-profile-name] | For a MIC or MPC interface, determine the percentage of excess bandwidth from low-priority traffic to
share. | [
{
"name": "percentage",
"desc": "Percentage of the excess bandwidth to share."
},
{
"name": "value",
"desc": "Proportion of the excess bandwidth to share."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [
"Managing Excess Bandwidth Distribution on Static Interfaces on MICs and MPCs"
] |
excess-rate-medium-high | excess-rate-medium-high (percent percentage | proportion value); | [edit class-of-service traffic-control-profiles traffic-control-profile-name] | For MPC7E-MRATE, MPC7E-10G, MPC8E, and MPC9E interfaces, determine the percentage of excess
bandwidth from high-priority traffic to share. | [
{
"name": "percentage",
"desc": "Percentage of the excess bandwidth to share."
},
{
"name": "proportion",
"desc": "Proportion of the excess bandwidth to share."
}
] | 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. | [
"Managing Excess Bandwidth Distribution on Static Interfaces on MICs and MPCs",
"Per-Priority Shaping on MIC and MPC Interfaces Overview"
] |
excess-rate-medium-low | excess-rate-medium-low (percent percentage | proportion value); | [edit class-of-service traffic-control-profiles traffic-control-profile-name] | For MPC7E-MRATE, MPC7E-10G, MPC8E, and MPC9E interfaces, determine the percentage of excess
bandwidth from low-priority traffic to share. | [
{
"name": "percentage",
"desc": "Percentage of the excess bandwidth to share."
},
{
"name": "value",
"desc": "Proportion of the excess bandwidth to share."
}
] | 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. | [
"Managing Excess Bandwidth Distribution on Static Interfaces on MICs and MPCs",
"Per-Priority Shaping on MIC and MPC Interfaces Overview"
] |
exclude (Diameter Gx Profiles) | exclude {
an-gw-address;
default-eps-bearer-qos;
packet-filter-information;
packet-filter-operation;
rat-type;
} | [edit unified-edge diameter-profiles gx-profile profile-name attributes] | Configure the attribute-value pairs (AVPs) to be excluded from the credit control request (CCR)
messages between the MX Series router and the policy and charging enforcement function (PCEF). | [
{
"name": "an-gw-address",
"desc": "Exclude the AN-GW-Address AVP."
},
{
"name": "default-eps-bearer-qos",
"desc": "Exclude the Default-EPS-Bearer-QoS AVP."
},
{
"name": "packet-filter-information",
"desc": "Exclude the Packet-Filter-Information AVP."
},
{
"name": "packet-fil... | 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. | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.