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 |
|---|---|---|---|---|---|---|---|
egress (Analyzer) | egress {
bridge-domain bridge-domain-name;
interface (all | interface-name);
routing-instance {
instance-name {
bridge-domain bridge-domain-name;
}
}
} | [edit forwarding-options analyzer analyzer-name input] | Specify ports where traffic exiting the interface is to be mirrored in a mirroring configuration.
The remaining statements are explained separately. See CLI Explorer. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X50-D10. | [
"Example: Configuring Mirroring for Remote Monitoring of Employee Resource Use Through a Transit",
"Switch on EX9200 Switches"
] |
egress (Buffer Configuration) | egress {
percent percent;
buffer-partition (lossless | lossy | multicast) {
percent percent;
}
} | [edit class-of-service shared-buffer] | Configure the global shared buffer pool allocation for egress traffic. The system allocates the shared
buffer pool dynamically across its ports as the ports require memory space. Some buffer space is
reserved for other buffers such as dedicated buffers (buffers allocated permanently to ports).
The percentage you specif... | [
{
"name": "percent percent",
"desc": "Percentage of available egress buffer space allocated to the shared buffer pool. If the"
}
] | 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. | [
"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... |
egress | egress {
interface (all | interface-name);
}
vlan (vlan-id | vlan-name); | For platforms without ELS:
[edit ethernet-switching-options analyzer name input]
For platforms with ELS:
[edit forwarding-options analyzer name input] | Specify interface or VLAN for which egressing traffic is mirrored. (The vlan statement is not supported
on all switches.)
The remaining statement is explained separately. See CLI Explorer.
NOTE: If you configure Junos OS to mirror egress packets, do not configure more than
2000 VLANs. If you do so, some of the mirrored... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Understanding Port Mirroring and Analyzers",
"Configuring Port Mirroring",
"Examples: Configuring Port Mirroring for Local Analysis"
] |
egress-chaining | egress-chaining {
spring-te;
} | [edit routing-options forwarding-table] | Enable egress chaining for devices that support a maximum of two labels push at the ingress. You can
configure egress chaining to implement more than two labels push using a composite next hop at the
egress and pass a pointer from the ingress to the egress about the location of its label stack. Route
pointing to this n... | [
{
"name": "spring-te",
"desc": "Enable egress chaining for segment routing traffic-engineered (SPRING-TE) routes. When you configure the spring-te, you set the egress chain flag in the SPRING-TE route’s next hop. This enables installation of a composite next hop in the egress Packet Forwarding Engine (PFE).... | routing | Statement introduced in Junos OS Release 20.4R1. | [] |
egress-l2-extended-match | egress-l2-extended-match | [edit system packet-forwarding-options firewall-profile] | Set this configuration to support TCP-flags, dscp, ip-version, source-port, destination-port, ip-source-
address, ip-destination-address, source-prefix-list, destination-prefix-list, and icmp-type matches for
egress port firewall filters and egress VLAN firewall filters.
NOTE: The configuration is applicable for EX4400... | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos Release 23.4. | [] |
egress-policer-overhead | egress-policer-overhead bytes; | [edit chassis fpc slot-number pic pic-number] | Add the specified number of bytes to the actual length of an Ethernet frame when determining the
actions of Layer 2 policers, MAC policers, or queue rate limits applied to output traffic on the line card.
You can configure egress policer overhead to account for egress shaping overhead bytes added to
output traffic on t... | [
{
"name": "bytes",
"desc": "Number of bytes added to a packet exiting an interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 11.1. | [
"Policer Overhead to Account for Rate Shaping Overview",
"Example: Configuring Policer Overhead to Account for Rate Shaping",
"Configuring a Policer Overhead",
"CoS on Enhanced IQ2 PICs Overview"
] |
egress-policy | egress-policy [ policy-names ]; | [edit logical-systems logical-system-name protocols ldp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols ldp],
[edit protocols ldp],
[edit routing-instances routing-instance-name protocols ldp] | Control the prefixes advertised into LDP.
Default
Only the loopback address is advertised. | [
{
"name": "policy-names",
"desc": "Name of one or more routing policies."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Prefixes Advertised into LDP from the Routing Table"
] |
egress-protection (BGP) | egress-protection {
context-identifier context-id-ip-address;
keep-import policy-name;
} | [edit protocols bgp group group-name family inet labeled-unicast],
[edit protocols bgp group group-name family inet-vpn unicast],
[edit protocols bgp group group-name family inet6-vpn unicast],
[edit protocols bgp group group-name family iso-vpn unicast] | Enable egress protection for the configured BGP Network Layer Reachability Information (NLRI). | [
{
"name": "context-identifier",
"desc": ""
},
{
"name": "context-id-ip-address",
"desc": "(Optional) The IPv4 address of the context identifier."
},
{
"name": "keep-import policy-name",
"desc": "The import policy that contains routes with the configured route target community. BGP ke... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4R3.
Statement introduced for labeled unicast in Junos OS Release 14.1. | [
"Example: Configuring Egress Protection for Layer 3 VPN Services",
"Example: Configuring Layer 3 VPN Egress Protection with RSVP and LDP",
"Example: Configuring Egress Protection for BGP Labeled Unicast"
] |
egress-protection (Layer 2 circuit) | egress-protection {
protected-l2circuit {
egress-pe address;
ingress-pe address;
virtual-circuit-id identifier;
}
protector-interface interface-name;
protector-pe address {
context-identifier identifier;
lsp lsp-name;
}
} | [edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name],
[edit protocols l2circuit neighbor address interface interface-name] | Configures an egress protection virtual circuit (EPVC). | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS release 10.4. | [
"Example: Configuring an Egress Protection LSP for a Layer 2 Circuit"
] |
egress-protection (MPLS) | egress-protection {
context-identifier context-id {
primary | protector;
metric igp-metric-value;
advertise-mode (stub-alias | stub-proxy);
}
} | [edit logical-systems logical-system-name protocols mpls],
[edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name],
[edit protocols mpls],
[edit protocols mpls label-switched-path lsp-name] | Enables an Edge Protection Virtual Circuit (EPVC) for the MPLS protocol. | [
{
"name": "context-identifier context-id-ip-address",
"desc": "(Optional) The context identifier IPv4 address."
},
{
"name": "metric igp-metric-value",
"desc": "(Optional) The IGP metric value ranging from 2 through 16777215."
},
{
"name": "(primary | protector)",
"desc": "On the pri... | 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.
Options primary, protector, and metric introduced in Junos OS Release 11.4R3.
Option advertise-mode introduced in Junos OS Release 13.3. | [
"Example: Configuring Egress Protection for Layer 3 VPN Services",
"Example: Configuring Layer 3 VPN Egress Protection with RSVP and LDP"
] |
egress-protection (Routing Instances) | egress-protection {
context-identifier context-id-ip-address;
}
} | [edit routing-instances routing-instance-name] | Enable egress instance protection and provides customer edge (CE) VRF-level context-id granularity for
each virtual routing and forwarding (VRF) instance. | [
{
"name": "context-identifier context-id-ip-address",
"desc": "(Optional) The IPv4 address for the context identifier of the protected PE router."
}
] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4R3. | [
"Example: Configuring Egress Protection for Layer 3 VPN Services"
] |
egress-quantization | egress-quantization | [edit forwarding-options enhanced-hash-key ecmp-dlb] | Selective dynamic load balancing selects an optimal link based on:
•
Port load metric - Amount of traffic in bytes transmitted in recent past over each ECMP link.
•
Port queue metric - Amount of traffic in number of cells enqueued on each ECMP link for
transmission.
Use egress-quantization to configure the desired rati... | [
{
"name": "apply-groups",
"desc": ""
},
{
"name": "max",
"desc": ""
},
{
"name": "min",
"desc": ""
},
{
"name": "rate-weightage",
"desc": ""
}
] | 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. | [
"Dynamic Load Balancing (DLB)"
] |
egress-shaping-overhead | egress-shaping-overhead number; | [edit chassis fpc slot-number pic pic-number traffic-manager],
[edit chassis lcc number fpc slot-number pic pic-number traffic-manager] | Number of bytes to add to packet to determine shaped session packet length.
NOTE: On M Series and T Series routers with Gigabit Ethernet Intelligent Queuing 2
(IQ2) PICs and Enhanced IQ2 (IQ2E) PICs and on MX Series routers with Dense Port
Concentrators (DPCs) only, to account for egress shaping overhead bytes added to... | [
{
"name": "number",
"desc": "When traffic management (queuing and scheduling) is configured on the egress side, the number"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 8.3. | [] |
egress-stats (Flat-File Accounting Options) | egress-stats {
all-fields;
input-bytes;
input-packets;
output-bytes;
output-packets;
queue-id;
red-drop-bytes;
red-drop-packets;
tail-drop-packets;
total-drop-packets;
} | [edit accounting-options flat-file-profile profile-name fields] | Specify egress queue statistics to be collected for the interface. | [
{
"name": "all-fields",
"desc": "Collect all egress queue statistics available for the interface context, logical or physical."
},
{
"name": "input-bytes",
"desc": "Collect the number of octets queued including traffic dropped because of congestion."
},
{
"name": "input-packets",
"de... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 16.1R4. | [
"Configuring Flat-File Accounting for Layer 2 Wholesale",
"Configuring Flat-File Accounting for Extensible Subscriber Services Management",
"Flat-File Accounting Overview"
] |
egress-te | egress-te {
backup-path backup-path;
import;
install-address address;
no-install;
rib (inet.0 | inet6.0);
} | [edit logical-systems logical-system-name protocols bgp],
[edit logical-systems logical-system-name protocols bgp group group-name],
[edit logical-systems logical-system-name protocols bgp group group-name neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols b... | Enable egress peer engineering to direct core service traffic such as MPLS RSVP to a specific single-hop
egress BGP peer. The ingress BGP peer can traffic-engineer the core inet unicast and inet6 unicast
service traffic using BGP labeled unicast towards a specific egress BGP peer, which is also the AS
boundary router.
... | [
{
"name": "none",
"desc": "Enable traffic engineering on the egress peer."
},
{
"name": "backup-path backup-path",
"desc": "(Optional) Specify a predefined template that has the configured backup path for MPLS fast reroute."
},
{
"name": "import",
"desc": "Import policy to set attrib... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2R4. | [
"Configuring Egress Peer Traffic Engineering by Using BGP Labeled Unicast and Enabling MPLS Fast",
"Reroute",
"Egress Peer Traffic Engineering Using BGP Labeled Unicast Overview",
"Example: Configuring Egress Peer Traffic Engineering Using BGP Labeled Unicast"
] |
egress-te-adj-segment | egress-te-adj-segment name {
egress-te-backup-ip-forward instance-name;
egress-te-backup-segment label label-value;
egress-te-set set-name weight weight;
label label-value;
next-hop next-hop-address;
egress-te-link-attribute {
delay-metric <value>
}
} | [edit logical-systems name protocols bgp group name neighbor],
[edit logical-systems name routing-instances name protocols bgp group
name neighbor],
[edit logical-systems name tenants name routing-instances name protocols
bgp group name ... | Specify a BGP peer adjacency segment for only multihop EBGP peers. You can specify a segment set so
that the packet is sent to any member in the set, which is the equal-cost multipath next hop. You can
include an adjacent segment or a node segment to the same peer segment set. You must configure
"egress-te-node-segment... | [
{
"name": "egress-te-backup-ip-forward instance-",
"desc": ""
},
{
"name": "name",
"desc": "Specify a routing-instance name to use the IP forward backup path for egress TE."
},
{
"name": "egress-te-backup-segment label label-",
"desc": ""
},
{
"name": "value",
"desc": "Sp... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R1.
egress-te-backup-ip-forward option introduced in Release 20.1R1.
delay-metric <value> option introduced in Junos os Release 21.4R1. | [] |
egress-te-backup-paths | egress-te-backup-paths {
template path-name {
ip-forward rti-name;
peer peer-addr;
remote-nexthop remote-nh-addr;
}
} | [edit logical-systems logical system name protocols bgp],
[edit logical-systems logical system name protocols bgp group group-name],
[edit protocols bgp],
[edit protocols bgp group group-name] | Specify backup paths for MPLS fast reroute (FRR) on an egress peer, which has traffic engineering
enabled. Egress peer engineering directs core service traffic such as MPLS RSVP to a specific egress BGP
peer. The ingress BGP peer can traffic-engineer the core inet unicast and inet6 unicast service traffic
using BGP lab... | [
{
"name": "template",
"desc": ""
},
{
"name": "path-name",
"desc": "Define a template that can be reused by multiple BGP groups or peers. All addresses listed in one template must belong to the same IP address family as the protected device that is the egress BGP peer."
},
{
"name": "ip-... | 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 R4. | [
"Configuring Egress Peer Traffic Engineering by Using BGP Labeled Unicast and Enabling MPLS Fast",
"Reroute",
"Egress Peer Traffic Engineering Using BGP Labeled Unicast Overview",
"Example: Configuring Egress Peer Traffic Engineering Using BGP Labeled Unicast"
] |
egress-te-node-segment | egress-te-node-segment name {
egress-te-backup-ip-forward instance-name;
egress-te-backup-segment label label-value;
egress-te-set set-name weight weight;
label label-value;
} | [edit logical-systems name protocols bgp group name neighbor],
[edit logical-systems name routing-instances name protocols bgp group
name neighbor],
[edit logical-systems name tenants name routing-instances name protocols
bgp group name ... | Specify a BGP peer node segment for both single hop and multihop EBGP peers. You can configure a
node segment as a member of a segment set so that the packet is sent to any member that is the ECMP
next hop in the set. Before configuring a node segment as a member of a segment set, you must create a
segment set first. I... | [
{
"name": "egress-te-backup-ip-forward",
"desc": ""
},
{
"name": "instance-name",
"desc": "Specify a routing-instance name to use the IP forward backup path for egress TE."
},
{
"name": "egress-te-backup-segment label",
"desc": ""
},
{
"name": "label-value",
"desc": "Spec... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R1.
egress-te-backup-ip-forward option introduced in Release 20.1R1. | [] |
egress-te-set-segment | egress-te-set-segment name {
egress-te-backup-ip-forward <instance-name>;
egress-te-backup-segment label label-value;
label label-value;
} | [edit logical-systems name protocols bgp],
[edit logical-systems name routing-instances name protocols bgp],
[edit logical-systems name tenants name routing-instances name protocols bgp],
[edit protocols bgp],
[edit routing-instances name protocols bgp],
... | Specify a peer segment set that can include adjacency segments or node segments, or a combination of
both as members. You can assign a label, which is represented as equal-cost multipath next hop to send
a packet to any member in the set.
name
Specify a unique name for the BGP peer segment set. | [
{
"name": "egress-te-backup-ip-forward instance-",
"desc": ""
},
{
"name": "name",
"desc": "Specify a routing-instance name to use the IP forward backup path for egress TE."
},
{
"name": "egress-te-backup-segment label label-",
"desc": ""
},
{
"name": "value",
"desc": "Sp... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.4R1.
egress-te-backup-ip-forward option introduced in Release 20.1R1. | [] |
ei-mapping-timeout (Source NAT Next Gen Services) | ei-mapping-timeout ei-mapping-timeout; | [edit services nat source pool nat-pool-name] | Specify the timeout period for endpoint independent translations that use the NAT pool. Mappings that
are inactive for this amount of time are dropped.
If you do not configure ei-mapping-timeout for endpoint independent translations, then the mapping-timeout
value is used for endpoint independent translations. | [
{
"name": "ei-mapping-timeout ei-",
"desc": ""
},
{
"name": "mapping-timeout",
"desc": "The timeout period in seconds. Range: 120 through 86,400 Default: 300 (timeout period for endpoint independent translations is set by mapping-timeout value at the [edit services nat source pool nat-pool-nam... | 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. | [] |
ei-mapping-timeout | mapping-timeout seconds; | [edit services nat pool nat-pool-name] | Specify the duration for endpoint independent translations that use the specified NAT pool. This
includes endpoint-independent mapping (EIM) and endpoint-independent filtering (EIF). | [
{
"name": "seconds",
"desc": "Lifetime of endpoint independent mappings in seconds."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | ei-mapping-timeout statement introduced in JUNOS Releases 12.3. | [
"Network Address Translation Configuration Overview"
] |
eif-flow-limit | eif-flow-limit number-of-flows | [edit services nat rule rule-name term term-name then translated secure-nat-mapping] | Specify the maximum number of inbound flows allowed on EIF mapping to the configured value. This
limit is per EIF mapping and is per given instance of time. For example, if eif-flow-limit is configured as n,
then only n inbound connections are allowed at a given instance of time, The n+1 and subsequent
connections arri... | [] | 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 | [
"Protecting CGN Devices Against Denial of Service (DOS) Attacks"
] |
em-hw-profile | em-hw-profile; | [edit chassis forwarding-options] | (QFX5120 only) Configure a unified forwarding table (UFT) profile to allocate the amount of MAC
address, layer 3 host, longest prefix match (LPM), and exact-match (EM) memory available for software-
based flow-based telemetry (FBT) for VXLANs. You must reboot the switch after committing this
statement to the configurat... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 22.2R1. | [
"Flow-Based Telemetry for VXLANs"
] |
email-notify | email-notify {
admin-email email-address;
custom-message message;
custom-message-subject message-subject;
} | [edit security utm feature-profile anti-virus kaspersky-lab-engine pattern-update]
[edit security utm feature-profile anti-virus juniper-express-engine pattern-update]
[edit security utm feature-profile anti-virus sophos-engine pattern-update]
[edit security utm default-configuration anti-virus avira-engine pattern-upd... | You can configure the device to notify a specified administrator when patterns are updated. This is an e-
mail notification with a custom message and a custom subject line. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1.
Support for Avira engine added in Junos OS ... | [] |
embedded-rp | embedded-rp {
group-ranges {
destination-ip-prefix</prefix-length>;
}
maximum-rps limit;
} | [edit logical-systems logical-system-name protocols pim rp],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim
rp],
[edit protocols pim rp],
[edit routing-instances routing-instance-name protocols pim rp] | Configure properties for embedded IP version 6 (IPv6) RPs.
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 7.4. | [
"Configuring PIM Embedded RP for IPv6"
] |
ENABLE (DTCP) | ENABLE DTCP/0.8
Csource-ID: user-name
Criteria-ID: variable
X-Drop-Policy: variable
Flags: flags | Specify the DTCP attributes used in ENABLE messages to cause the router to trigger a drop policy if one
does not already exist from a prior DTCP ADD or DTCP ENABLE command.
The DTCP ENABLE message can only be issued on a Criteria-ID that was returned in a response to a
previous DTCP ADD command. The policy applies to a... | [
{
"name": "X-Drop-Policy:",
"desc": ""
},
{
"name": "variable",
"desc": "Name of the policy that determines which mirrored packets are no longer sent to the mediation device."
}
] | Not applicable.
Sample Output
command-name
ENABLE DTCP/0.8
Csource-ID: ft-user1
Criteria-ID: 1
X-Drop: T1
Flags: STATIC
Seq: 1
Authentication-Info: c16d2d9d1679facf0c4a66683af6114d341e4033
DTCP/0.8 200 OK
SEQ: 7
CRITERIA-ID: 2
TIMESTAMP: 2011-02-13 15:56:49.609 | Command introduced in Junos OS Release 12.3. | [
"DTCP Messages Used for Subscriber Secure Policy",
"DTCP-Initiated Subscriber Secure Policy Overview"
] | |
enable (Enhanced Subscriber Management) | enable (force); | [edit system services subscriber-management] | Enable the Junos OS enhanced subscriber management software architecture to support configuration
of dynamic interfaces and services for subscriber management. To use dynamic profiles and
authentication to create and manage dynamic subscriber interfaces and services, you must enable
enhanced subscriber management and r... | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1R3. | [
"Configuring Junos OS Enhanced Subscriber Management",
"Junos OS Enhanced Subscriber Management Overview"
] |
enable | enable service-name {
concurrent-data-sessions max-session-number;
} | [edit services service-set services-set-name subscriber-profile profile-name] | Enable the service name for the subscriber profile. | [
{
"name": "service-name",
"desc": "Name of the enabled service."
}
] | admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.4. | [] |
enable | enable {
download-timeout minutes;
interval (Security IDP) hours;
start-time (Security IDP) start-time;
} | [edit security idp security-package automatic] | Enables the automatic download of the IDP security package. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
enable-all-ifl | enable-all-ifl; | [edit protocols layer2-control mac-rewrite interface interface-name] | Enable tunneling for STP, VTP, CDP, and other supported protocols on all logical interfaces (VLANs)
configured on the interface.
NOTE: Tunneling on all logical interfaces is enabled automatically for PVST/PVST+. | [] | 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. | [
"Understanding Layer 2 Protocol Tunneling"
] |
enable-all-qmodules | (enable-all-qmodules | no-enable-all-qmodules); | [edit security idp sensor-configuration global] | Enable all the qmodules of the global rulebase IDP security policy. By default all the qmodules are
enabled. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
enable-asymmetric-traffic-processing (Service Set Next Gen Services) | enable-asymmetric-traffic-processing; | [edit services service-set service-set-name service-set-options] | Enable the service set to handle unidirectional traffic. | [] | 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. | [] |
enable-asymmetric-traffic-processing | enable-asymmetric-traffic-processing; | [edit services service-set service-set-name service-set-options] | Enable APPID to perform application matching on unidirectional traffic. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring APPID Support for Unidirectional Traffic"
] |
enable-call-distribution | enable-call-distribution; | [edit security alg sip ] | When you configure this mode, the call SPU distributes the SIP calls according to the call-id of each SIP
call instead of proxy IP. | [] | 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. | [] |
enable-descriptive-session-syslog | enable-descriptive-session-syslog; | edit services service-set service-set-name service-set-options | Display descriptive information of session logs.
You can enable syslog to display information related to inside and outside packets, byte count, and the
session id for both open and close sessions. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 20.3. | [] |
enable-explorer (REST API) | enable-explorer; | [edit system services rest] | Enable the REST API Explorer. This GUI is disabled by default, and can be enabled by specifying set
system services rest enable-explorer. To disable the REST API Explorer, specify delete system services rest
enable-explorer. To learn more about the REST API Explorer, see Example: Using the REST API Explorer. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.2. | [
"Example: Using the REST API Explorer"
] |
enable-extended-ql-tlv | enable-extended-ql-tlv; | [edit chassis synchronization] | tnc
Clock traceable to a transit node clock (option-2 only).
If you do not configure the quality level and the clock source does not receive ESMC
messages, the quality level is set to DNU for network option-1 and DUS for network
option-2. | [
{
"name": "quality-level",
"desc": "The available quality levels are as follows: Table 39: Quality Levels Quality Level"
}
] | 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 EVO. | [
"synchronization (ACX Series)",
"show chassis synchronization"
] |
enable-flow-tracing (Services) | enable-flow-tracing; | [edit services ssl proxy profile profile-name]
[edit services ssl termination profile profile-name]
[edit services ssl initiation profile profile-name] | Enable flow tracing for the profile.
When you configure enable-flow-tracing for SSL profiles, the debug tracing will be enabled on that profile
when the flag is set as selected-profile. | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. This statement is supported. | [
"SSL Proxy Overview",
"Configuring SSL Forward Proxy",
"Enabling Debugging and Tracing for SSL Proxy"
] |
enable-gtpu-distribution | enable-gtpu-distribution; | [edit security forwarding-process application-services] | Use the enable-gtpu-distribution option to enable GTP control plane (GTP-C) and GTP user plane (GTP-
U) session distribution. This helps to distribute the GTP-C and GTP U traffic on all Services Processing
Units (SPUs) by using tunnel-based session distribution, where the GTP-C or the GTP-U traffic of
different tunnels... | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D40. | [
"Understanding GTP Support for Central Point Architecture"
] |
enable-heuristics | enable-heuristics; | [edit services application-identification] | (Junos OS Release 12.1X47 and earlier—AppID 1.0 only) Enable APPID to identify encrypted data
packets in point-to-point applications by using heuristics methodology. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2.
Statement deprecated in Junos OS Release 12.3X48-D10 and later. | [
"Configuring APPID Support for Heuristics"
] |
enable-ipv6-services-for-lac (L2TP) | enable-ipv6-services-for-lac; | [edit services l2tp] | Enable the LAC to create the IPv6 address family (inet6) when establishing a tunnel for subscribers,
allowing IPv6 filters to be applied. By default, the LAC requires only family inet to enable forwarding into
an IP tunnel. It can apply IPv4 firewall filters to the session. Even when family inet6 is included in the
dyn... | [] | 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. | [
"L2TP LAC Tunneling for Subscribers",
"L2TP LAC Subscriber Configuration"
] |
enable-mac-move-action | enable-mac-move-action; | [edit bridge-domains bridge-domain-name] | Enable the MAC move action feature at the bridge domain level. This statement blocks the logical
interface for the bridge domain when a MAC move is detected on the 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.
Statement supported in Junos OS Release 14.2 for MX104 Router. | [
"Configuring a Bridge Domain"
] |
enable-packet-pool | (enable-packet-pool | no-enable-packet-pool); | [edit security idp sensor-configuration global] | Enable the packet pool to use when the current pool is exhausted. By default packet pool is enabled. | [] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [] |
enable-performance-mode (Application Identification) | enable-performance-mode; | [edit services application-identification] | Set the deep packet inspection (DPI) in performance mode for application identification. Performance
mode improves application traffic throughput by limiting the maximum DPI processing to four packets
per session. This limit includes both client-to-server and server-to-client directions. By default,
performance mode is... | [] | view-level—To view this statement in the configuration.
control-level—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1.
Support for Next Gen Services introduced in Junos OS Releases 19.3R2 and 19.4R1 on MX Series
MX240, MX480 and MX960 using the MX-SPC3 services card. | [
"Application Identification Overview"
] |
enable-performance-mode | enable-performance-mode max-packet-threshold number; | [edit services application-identification] | Set the deep packet inspection (DPI) in performance mode for application identification.
The application traffic throughput can be improved by setting the DPI in performance mode with default
packet inspection limit as two packets, including both client-to-server and server-to-client directions. By
default, performance... | [
{
"name": "max-packet-threshold number",
"desc": "Set the maximum packet threshold for DPI performance mode. Range: 1 through 100 Default: 2"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X47-D10. | [
"Improving the Application Traffic Throughput"
] |
enable-rejoin (Aggregated Multiservices) | enable-rejoin; | [edit interfaces interface-name load-balancing-options member-failure-options redistribute-all-
traffic] | Enable the failed member to rejoin the aggregated Multiservices (AMS) interface after the member
comes back online.
For many-to-one (N:1) high availability (HA) for service applications like Network Address Translation
(NAT), this configuration allows the failed members to rejoin the pool of active members automaticall... | [] | 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.
Support added in Junos OS Release 19.3R2 for Next Gen Services on MX Series routers MX240, MX480
and MX960 with the MX-SPC3 services card. | [
"Understanding Aggregated Multiservices Interfaces",
"Example: Configuring an Aggregated Multiservices Interface (AMS)"
] |
enable-reroute-uniform-link-check | enable-reroute-uniform-link-check nat; | [edit security flow] | Enable retaining an existing session with Network Address Translation (NAT) rule when there is a change
in egress interface because of rerouting.
The enable-reroute-uniform-link-check nat command is disabled by default.
When the enable-reroute-uniform-link-check nat command is enabled:
•
If the new egress interface and... | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 18.3R1. | [] |
enable-reverse-reroute | enable-reverse-reroute; | [edit security zones security-zone zone-name] | Reroute the reverse traffic when there is a link switch for the incoming traffic.
When you configure the enable-reverse-reroute option for a security zone, then the packets of each
session that has been initiated from the zone are checked for the change in the incoming interface.
When an incoming packet arrives on an i... | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1X49-D123. | [
"Understanding Advanced Policy-Based Routing"
] |
enable-session-cache | enable-session-cache; | [edit services ssl termination profile profile-name]
[edit services ssl initiation profile profile-name] | Enable SSL session cache.
You can enable session caching to cache session information, such as the pre-master secret key and
agreed-upon ciphers, for both the client and server.
The cached information is identified by a session ID. In subsequent connections both parties agree to
use the session ID to retrieve the infor... | [] | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1X44-D10. This statement is supported. | [
"SSL Proxy Overview",
"Configuring SSL Forward Proxy",
"Enabling Debugging and Tracing for SSL Proxy"
] |
enable-snmp-tunnel-statistics (L2TP) | enable-snmp-tunnel-statistics; | [edit services l2tp] | Enable collection of L2TP tunnel and global counters for SNMP statistics.
NOTE: The system load can increase when you enable these counters and also use
RADIUS interim accounting updates. We recommend you enable these counters when
you are using only SNMP statistics.
Default
Disabled. | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 12.1R4 and supported in later 12.1Rx releases.
Statement supported in Junos OS Release 12.2R2 and later 12.2Rx releases. (Not supported in Junos OS
Release 12.2R1.)
Statement supported in Junos OS Release 12.3 and later releases. | [
"L2TP for Subscriber Access Overview"
] |
enable-subscriber-analysis (Services Options VMS Interfaces) | enable-subscriber-analysis; | [edit interfaces interface-name services-options] | Enable the creation of subscribers if the following are not configured, but you want subscribers to be
created:
•
NAT
•
The max-sessions-per-subscriber statement at the [edit services service-set service-set-name] hierarchy
level | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 19.3R2. | [
"How to Configure Services Interfaces for Next Gen Services"
] |
encap-type | encap-type(ipv4 | ipv6); | [edit interfaces name unit name tunnel] | Define the type of encapsulation on the IP tunnel interface .
You must configure this option if you configure source-interface or source-hostname or destination-hostname. | [
{
"name": "ipv4",
"desc": "For IPv4 tunnel encapsulation"
},
{
"name": "ipv6",
"desc": "For IPv6 tunnel encapsulation"
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2R1 for SRX Series Firewalls (SRX1500, SRX4100,
SRX4200, SRX5400, SRX5600, SRX5800, and vSRX3.0)
Statement introduced in Junos OS Release 23.4R1 for SRX Series Firewalls (SRX38, SRX300, SRX320,
SRX340, and SRX345) | [
"Tunnel Services Overview"
] |
encapsulate-inner-vlan | encapsulate-inner-vlan | [edit routing-instances routing-instance-name vlans vlan-name vxlan],
[edit vlans vlan-name vxlan] | Configure the switch to preserve the original VLAN tag (in the inner Ethernet packet) when performing
Virtual Extensible LAN (VXLAN) encapsulation.
Preserving the original VLAN tag is implicit with VLAN bundle services. As a result, in an EVPN-VXLAN
environment, you don't need to configure this option with EVPN MAC-VRF... | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 14.1R2. | [
"Understanding VXLANs",
"Examples: Tunneling Q-in-Q Traffic in an EVPN-VXLAN Overlay Network",
"Manually Configuring VXLANs on QFX Series and EX4600 Switches",
"Examples: Manually Configuring VXLANs on QFX Series and EX4600 Switches"
] |
encapsulation (Dynamic Interfaces) | encapsulation (atm-ccc-cell-relay | atm-ccc-vc-mux | atm-cisco-nlpid | atm-tcc-vc-mux | atm-
mlppp-llc | atm-nlpid | atm-ppp-llc | atm-ppp-vc-mux | atm-snap | atm-tcc-snap | atm-vc-mux |
ether-over-atm-llc | ether-vpls-over-atm-llc | ether-vpls-over-fr | ether-vpls-over-ppp |
ethernet | frame-relay-ccc | frame-relay-... | [edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number] | Dynamic interface configuration of the logical link-layer encapsulation type. | [
{
"name": "atm-ccc-cell-relay",
"desc": "Use ATM cell-relay encapsulation."
},
{
"name": "atm-ccc-vc-mux",
"desc": "Use ATM virtual circuit (VC) multiplex encapsulation on circuit cross-connect (CCC)"
},
{
"name": "atm-cisco-nlpid",
"desc": "Use Cisco ATM network layer protocol ID (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.4. | [
"Configuring a Retail Dynamic Profile for Use in the Layer 2 Wholesale Solution",
"Configuring PPP over ATM2 Encapsulation Overview"
] |
encapsulation (interfaces) | encapsulation ( dix | ether-vpls-fr | frame-relay-ppp | ppp-over-ether | vlan-bridge | vlan-ccc
| vlan-tcc | vlan-vpls ); | [edit interfaces interface-name unit logical-unit-number] | Specify the physical link layer encapsulation type. For some devices, you may also specify the logical link
layer encapsulation type. See Feature Explorer for more information.
NOTE: Not all encapsulation types are supported on all switches. See the switch CLI.
Default
ppp—Use serial PPP encapsulation.
Physical Interfa... | [] | 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 9.5. | [
"Understanding Physical Encapsulation on an Interface",
"Configuring Interface Encapsulation on Physical Interfaces",
"Configuring CCC Encapsulation for Layer 2 VPNs",
"Configuring Layer 2 Switching Cross-Connects Using CCC",
"Configuring TCC Encapsulation for Layer 2 VPNs and Layer 2 Circuits",
"Configur... |
encapsulation (interfaces-fti) | encapsulation {
( gre | ipip | udp )
destination {
address address;
}
key key;
source {
address address;
}
{
routing-instance routing-instance;
... | [edit interfaces fti number unit logical-unit-number tunnel] | Configure encapsulation over tunnel.
The remaining statements are explained separately. See CLI Explorer. | [] | interface | Statement introduced in Junos OS Evolved Release 20.2R1.
Statement introduced for IPIP tunnels in Junos OS Evolved Release 20.4R1.
Statement introduced for UDP tunnels in Junos OS Evolved Release 21.1R1.
Statement introduced in Junos OS Evolved 24.1R1 for ACX Series routers (GRE tunnels) | [] |
encapsulation (Logical Interface) | encapsulation (atm-ccc-cell-relay | atm-ccc-vc-mux | atm-cisco-nlpid | atm-mlppp-llc | atm-nlpid
| atm-ppp-llc | atm-ppp-vc-mux | atm-snap | atm-tcc-snap | atm-tcc-vc-mux | atm-vc-mux | ether-
over-atm-llc | ether-vpls-over-atm-llc | ether-vpls-over-fr | ether-vpls-over-ppp | ethernet |
ethernet-ccc | ethernet-vpls |... | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number],
[edit interfaces rlsq number unit logical-unit-number]
[edit protocols evpn] | 20.1R1
Starting in Junos OS Release 20.1R1, aggregated ethernet interfaces supports VLAN TCC (Translational
cross-connect) encapsulation on MX series platforms. | [
{
"name": "atm-ccc-cell-relay",
"desc": "Use ATM cell-relay encapsulation."
},
{
"name": "atm-ccc-vc-mux",
"desc": "Use ATM virtual circuit (VC) multiplex encapsulation on CCC circuits. When you use this"
},
{
"name": "atm-cisco-nlpid",
"desc": "Use Cisco ATM network layer protocol i... | 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.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to
determine if a feature is supported on your platform.
Release | [
"Configuring Layer 2 Switching Cross-Connects Using CCC",
"Configuring the Encapsulation for Layer 2 Switching TCCs",
"Configuring Interface Encapsulation on Logical Interfaces",
"Configuring the CCC Encapsulation for LSP Tunnel Cross-Connects",
"Circuit and Translational Cross-Connects Overview",
"Identi... |
encapsulation (logical-link-layer) | encapsulation type; | [edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] | Specify the logical link-layer encapsulation type. | [
{
"name": "atm-mlppp-llc",
"desc": "For ATM2 IQ physical interfaces only, use Multilink Point-to-Point Protocol (MLPPP) over"
},
{
"name": "frame-relay-ppp",
"desc": "For Frame Relay circuits, use Frame Relay PPP encapsulation."
},
{
"name": "multilink-ppp",
"desc": "By default, voic... | 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 Encapsulation for Voice Services",
"Junos OS Network Interfaces Library for Routing Devices"
] |
encapsulation (Physical Interface) | encapsulation (multilink-frame-relay-uni-nni | ... ); | [edit interfaces interface-name],
[edit interfaces rlsqnumber:number] | Physical link-layer encapsulation type.
Default
MLFR UNI NNI encapsulation (on link services interfaces). | [
{
"name": "multilink-frame-relay-uni-nni",
"desc": "Use MLFR UNI NNI encapsulation. This encapsulation is used only on link"
}
] | 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 Encapsulation for Link Services Physical Interfaces",
"Junos OS Network Interfaces Library for Routing Devices"
] |
encapsulation (protocols evpn) | encapsulation (mpls | srv6 | vxlan); | [edit protocols evpn],
[edit protocols evpn interconnect],
[edit routing-instances routing-instance-name protocols evpn],
[edit routing-instances routing-instance-name protocols evpn interconnect] | Configure an encapsulation type for EVPN features. | [
{
"name": "encapsulation",
"desc": ""
},
{
"name": "mpls",
"desc": "Use the encapsulation mpls statement with the interconnected-vlan-list statement as part of the \"interconnect\" on page 9193 configuration stanza for seamless stitching of EVPN-VXLAN data centers through EVPN-MPLS. You configur... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | The encapsulation vxlan statement was introduced in Junos OS Release 16.1.
The encapsulation mpls statement was added to the interconnect stanza in Junos OS Release 21.4R1.
The encapsulation srv6 statement was introduced in Junos OS Release 22.4R1. | [
"Understanding EVPN with VXLAN Data Plane Encapsulation",
"EVPN Over VXLAN Encapsulation Configuration Overview for QFX Series and EX4600 Switches",
"Example: Configuring an EVPN Control Plane and VXLAN Data Plane",
"Implementing EVPN-VXLAN for Data Centers",
"Configuring EVPN-VPWS over SRv6"
] |
encapsulation-overhead | encapsulation-overhead bytes; | [edit access group-profile profile-name ppp],
[edit access profile profile-name client client-name ppp] | Configure the encapsulation overhead for class-of-service calculations. | [
{
"name": "bytes",
"desc": "The number of bytes used as encapsulation overhead for the session."
}
] | 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)"
] |
encapsulation-type (Layer 2 Circuits) | encapsulation-type (atm-aal5 | atm-cell | atm-cell-port-mode | atm-cell-vc-mode | atm-cell-vp-
mode | cesop | cisco-hdlc | ethernet | ethernet-vlan | frame-relay | frame-relay-port-mode |
interworking | ppp | satop-e1 | satop-e3 | satop-t1 | satop-t3); | [edit logical-systems logical-system-name protocols l2circuit local-switching interface
interface-name],
[edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name],
[edit protocols l2circuit local-switching interface interface-name],
[edit protocols l2circuit neighbor add... | Specify the type of Layer 2 traffic transiting the Layer 2 circuit. | [
{
"name": "atm-aal5",
"desc": "ATM Adaptation Layer (AAL/5)"
},
{
"name": "atm-cell",
"desc": "ATM cell relay"
},
{
"name": "atm-cell-port-mode",
"desc": "ATM cell relay port promiscuous mode"
},
{
"name": "atm-cell-vc-mode",
"desc": "ATM VC cell relay nonpromiscuous mode... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Configuring the Encapsulation Type for the Layer 2 Circuit Neighbor Interface"
] |
encapsulation-type (Layer 2 VPNs) | encapsulation-type (atm-aal5 | atm-cell | atm-cell-port-mode | atm-cell-vc-mode | atm-cell-vp-
mode | cesop | cisco-hdlc | ethernet | ethernet-vlan | frame-relay | frame-relay-port-mode |
interworking | ppp | satop-e1 | satop-e3 | satop-t1 | satop-t3); | [edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
l2vpn],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
l2vpn neighbor addr... | Specify the type of Layer 2 traffic originating from the CE device. Only the ethernet and ethernet-vlan
encapsulation types are supported for VPLS. Not all encapsulation types are supported on the switches.
See the switch CLI. | [
{
"name": "atm-aal5",
"desc": "ATM Adaptation Layer (AAL/5)"
},
{
"name": "atm-cell",
"desc": "ATM cell relay"
},
{
"name": "atm-cell-port-mode",
"desc": "ATM cell relay port promiscuous mode"
},
{
"name": "atm-cell-vc-mode",
"desc": "ATM VC cell relay nonpromiscuous mode... | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 9.2. | [
"Configuring the Encapsulation Type",
"Configuring VPLS Routing Instances",
"Configuring the Encapsulation Type for the Layer 2 Circuit Neighbor Interface",
"Configuring an MPLS-Based Layer 2 VPN (CLI Procedure)"
] |
encapsulation-udp-fti | encapsulation {
udp
destination {
addressaddress;
}
key key;
source {
addressaddress;
}
tunnel-routing-instance {
routing-instance routing-instance;
}
tunnel-termination;
port-profile profile-name;
}
}
... | [edit interfaces fti number unit logical-unit-number tunnel] | Configure UDP encapsulation over tunnel.
The remaining statements are explained separately. See CLI Explorer. | [] | interface | Statement introduced in Junos OS Evolved Release 21.1R1. | [] |
encoding (QFX Series) | encoding (differential | non-differential); | [edit interfaces interface-name optics-options] | Specify the encoding mode. | [
{
"name": "differential",
"desc": "Differential phase line encoding."
},
{
"name": "non-differential",
"desc": "Non-differential phase line encoding."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.2R1. | [
"Configuring Link Down Notification for Optics Options Alarm or Warning",
"100-Gigabit Ethernet OTN Options Configuration Overview"
] |
encoding (security) | encoding (binary | pem); | [edit security ike policy ike-peer-address],
[edit security certificates certification-authority ca-profile-name] | (Encryption interface on M Series and T Series routers and EX Series switches only) Specify the file
format used for the local-certificate and local-key-pair statements. | [
{
"name": "binary",
"desc": "Binary file format."
},
{
"name": "pem",
"desc": "Privacy-enhanced mail (PEM), an ASCII base 64 encoded format."
}
] | 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 Type of Encoding Your CA Supports",
"Configuring an IKE Policy for Digital Certificates for an ES PIC"
] |
encoding | encoding (nrz | nrzi); | [edit interfaces interface-name serial-options] | For serial interfaces, set the line encoding format.
Default
The default line encoding is non-return to zero (NRZ). | [
{
"name": "nrz",
"desc": "Use NRZ line encoding."
},
{
"name": "nrzi",
"desc": "Use non-return to zero inverted (NRZI) line encoding."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Serial Line Encoding"
] |
encoding-type | encoding-type (ethernet | packet | pdh | sonet-sdh); | [edit logical-systems logical-system-name protocols mpls label-switched-path lsp-name lsp-
attributes],
[edit protocols mpls label-switched-path lsp-name lsp-attributes] | Specify the encoding type of payload carried by the LSP. It can be any of the following:
•
ethernet—Ethernet
•
packet—Packet
•
pdh—Plesiochronous digital hierarchy (PDH)
•
sonet-sdh—SONET/SDH
Default
packet | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring the Encoding Type"
] |
encrypt (HTTP Header Enrichment) | encrypt {
hash algorithm;
prefix hash-prefix;
} | [edit services hcm tag-rule rule-name term term-number then tag tag-name] | Specify the transform to be applied to the header for the HTTP header enrichment so that you can add
subscriber attributes in a way that is obscured from the user.
NOTE: If you include this statement, then you also must configure hash and prefix
statements. | [
{
"name": "hash algorithm",
"desc": "Use the specified hashing algorithm. Currently, only md5 is supported."
},
{
"name": "prefix hash-prefix",
"desc": "Use the specified prefix key (up to 63 alphanumeric characters). The prefix key is concatenated with the specified tag attribute and hashed. Th... | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 17.1. | [
"Configuring HTTP Header Enrichment Overview",
"Configuring Tag Rules",
"Configuring HCM Profiles and Assigning Tag Rules",
"Junos Web Aware HTTP Header Enrichment Overview"
] |
encryption (Junos OS) | encryption {
algorithm (des-cbc | 3des-cbc | aes-128-cbc | aes-192-cbc | aes-256-cbc);
key (ascii-text key | hexadecimal key);
} | [edit security ipsec security-association sa-name manual direction (inbound | outbound |
bidirectional)] | Configure an encryption algorithm and key for a manual Security Association. | [
{
"name": "algorithm",
"desc": "Type of encryption algorithm. It can be one of the following:"
},
{
"name": "des-cbc",
"desc": "Has a block size of 8 bytes (64 bits); its key size is 48 bits long."
},
{
"name": "3des-cbc",
"desc": "Has block size of 8 bytes (64 bits); its key size is... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
aes-128-cbc, aes-192-cbc, and aes-256-cbc algorithm options added in Junos OS Release 15.1. | [
"Example: Using IPsec to Protect BGP Traffic",
"Configuring Manual IPsec Security Associations for an ES PIC"
] |
encryption (Junos-FIPS Software) | encryption {
algorithm 3des-cbc;
key ascii-text ascii-text-string;
} | [edit security ipsec internal security-association manual direction] | Define the encryption parameters for internal Routing-Engine–to–Routing-Engine communication. The
remaining statements are explained separately.
NOTE: The hexadecimal format must be used for the encryption key to be FIPS
compliant. The hexadecimal keys provide maximum key strength. | [] | Crypto Officer—To view and add this statement in the configuration. | Statement introduced before Junos OS Release 7.4. | [] |
encryption (MACsec for MX Series) | encryption; | [edit security macsec connectivity-association connectivity-association-name secure-channel
secure-channel-name] | Enable MACsec encryption within a secure channel.
You can enable MACsec without enabling encryption. If a connectivity association with a secure channel
that has not enabled MACsec encryption is associated with an interface, traffic is forwarded across the
Ethernet link in clear text. You are, therefore, able to view t... | [] | 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"
] |
encryption (MACsec) | encryption; | [edit security macsec connectivity-association connectivity-association-name secure-channel secure-
channel-name] | Enable MACsec encryption within a secure channel.
You can enable MACsec without enabling encryption. If a connectivity association with a secure channel
that has not enabled MACsec encryption is associated with an interface, traffic is forwarded across the
Ethernet link in clear text. You are, therefore, able to view t... | [] | 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. | [
"Configuring MACsec on EX, QFX and SRX Devices"
] |
encryption | encryption {
algorithm algorithm;
key (ascii-text key | hexadecimal key);
} | [edit services ipsec-vpn rule rule-name term term-name then manual direction direction] | Configure an encryption algorithm and key for manual SA. | [
{
"name": "algorithm",
"desc": "Type of encryption algorithm. The algorithm can be one of the following:"
},
{
"name": "des-cbc",
"desc": "Has a block size of 8 bytes (64 bits); the key size is 48 bits long."
},
{
"name": "3des-cbc",
"desc": "Has a block size of 8 bytes (64 bits); th... | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4.
aes-128-cbc, aes-192-cbc, and aes-256-cbc options added in Junos OS Release 7.6. | [
"Configuring Security Associations"
] |
encryption-algorithm (Security IKE) | encryption-algorithm (3des-cbc | aes-128-cbc | aes-128-gcm | aes-192-cbc | aes-256-cbc | aes-256-
gcm | chacha20-poly1305 | des-cbc); | [edit security ike proposal proposal-name] | Configure an encryption algorithm for an IKE proposal. The device does not delete existing IPsec SAs
when you update the encryption-algorithm configuration in the IKE proposal. | [
{
"name": "3des-cbc",
"desc": "Has a block size of 24 bytes; the key size is 192 bits long."
},
{
"name": "aes-128-cbc",
"desc": "Advanced Encryption Standard (AES) 128-bit encryption algorithm."
},
{
"name": "aes-128-gcm",
"desc": "AES 128-bit authenticated encryption algorithm supp... | 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. Support for aes-128-gcm and aes-256-gcm options added in
Junos OS Release 15.1X49-D40.
Starting in Junos OS Release 20.2R1, we’ve changed the help text description as NOT RECOMMENDED for the
CLI options 3des-cbc and des-cbc for devices running IKED with junos-ike package in... | [
"IPsec Overview",
"Installing Junos IKE package"
] |
encryption-algorithm (Security) | encryption-algorithm (3des-cbc | des-cbc | aes-128-cbc | aes-128-gcm | aes-192-cbc | aes-256-cbc
| aes-256-gcm); | [edit security ike proposal ike-proposal-name],
[edit security ipsec proposal ipsec-proposal-name] | Configure an IKE or IPsec encryption algorithm. Two algorithms are supported: Cipher Block Chaining
(CBC) and Galois/Counter Mode (GCM). CBC is older than GCM and is less secure. GCM is considered
more secure than CBC since it provides built-in authentication and integrity checks. GCM is also more
efficient for paralle... | [
{
"name": "3des-cbc",
"desc": "Encryption algorithm with key size of 24 bytes; its key size is 192 bits long."
},
{
"name": "des-cbc",
"desc": "Encryption algorithm with key size of 8 bytes; its key size is 48 bits long."
},
{
"name": "aes-128-cbc",
"desc": "Advanced encryption algor... | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring an IKE Proposal for Dynamic SAs",
"Configuring an IPsec Proposal for an ES PIC"
] |
encryption-algorithm | encryption-algorithm algorithm; | [edit services ipsec-vpn ike proposal proposal-name],
[edit services ipsec-vpn ipsec proposal proposal-name] | Configure an IKE or IPsec encryption algorithm. | [
{
"name": "3des-cbc",
"desc": "Has a block size of 24 bytes; the key size is 192 bits long."
},
{
"name": "aes-128-cbc",
"desc": "Advanced Encryption Standard (AES) 128-bit encryption algorithm."
},
{
"name": "aes-192-cbc",
"desc": "AES 192-bit encryption algorithm."
},
{
"na... | 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.
aes-128-cbc, aes-192-cbc, and aes-256-cbc options added in Junos OS Release 7.6.
aes-128-gcm, aes-192-gcm, and aes-256-gcm options added in Junos OS Release 17.3R1. | [
"Configuring IKE Proposals",
"Configuring IPsec Proposals"
] |
encryption-failures | encryption-failures {
threshold value;
} | [edit security alarms potential-violation] | Raise a security alarm after exceeding a specified number of encryption failures.
Default
Multiple encryption failures do not cause an alarm to be raised. | [
{
"name": "failures",
"desc": "Number of encryption failures up to which an alarm is not raised. When the configured number"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"IPsec Overview",
"Monitoring VPN Traffic"
] |
end-dx2v-sid | end-dx2v-sid end-dx2v-sid; | [edit logical-systems name routing-instances name protocols evpn source-packet-routing srv6
locator],
[edit logical-systems name routing-instances name protocols l2vpn source-packet-routing srv6
locator],
[edit logical-systems name routing-instances name protocols vpls source-packet-routing srv6
locator],
[edit logi... | Segment routing header based END.DX2V SID. | [] | [none specified] | Statement introduced in Junos OS Evolved Release 25.2R1. | [
"Configuring EVPN VPWS over SRv6 with Traffic Engineering"
] |
end-interface | end-interface {
interface interface-name;
no-revert;
protect-interface interface-name;
} | [edit logical-systems logical-system-name protocols l2circuit local-switching interface
interface-name],
[edit protocols l2circuit local-switching interface interface-name] | Specify the end interface for a local interface switch.
NOTE: The protect interface must be configured prior to configuring the no-revert
statement.
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 7.4. | [
"Configuring Local Interface Switching in Layer 2 Circuits"
] |
end-user-profile | end-user-profile profile-name profile-name
domain-name domain-name;
{
attribute device-category {
string string-value;
}
attribute device-identity {
string string-value;
}
attribute device-vendor {
string string-value;
}
attribute device-type {
string string-value;
}
attribute device-os {
string st... | [edit services user-identification device-information] | Specify the name of the device identity profile, also referred to as the end-user-profile, and either one or
more of its attributes or the name of the Active Directory domain to which the device belongs.
The device identity profile is a key component of the SRX Series Firewall identity feature, which enables
you to con... | [
{
"name": "profile-name profile-name",
"desc": "Name of the device identity profile; for example, marketing-west-coast."
},
{
"name": "domain domain-name",
"desc": "Name of the domain to which the device belongs; for example, domain1."
},
{
"name": "attribute device-vendor string",
"... | services—To view this statement in the configuration.
services-control—To add this statement to the configuration. | Statement introduced in Junos OS 15.1X49-D70. | [
"Understanding Access Control to Network Resources Based on Device Identity Information",
"Understanding the Device Identity Attributes and Profiles for the Integrated User Firewall Device",
"Identity Authentication Feature",
"Understanding the Device Identity Authentication Table and Its Entries"
] |
endpoint-registration-timeout | endpoint-registration-timeout value-in-seconds; | [edit logical-systems name security alg h323],
[edit logical-systems name tenants name security alg h323],
[edit security alg h323],
[edit services alg h323],
[edit tenants name security alg h323] | Configure the endpoint-registration-timeout to specify the timeout value in seconds for entries in the
NAT table. | [
{
"name": "value-in-seconds",
"desc": "Timeout value."
}
] | 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. | [] |
enforce-first-as | enforce-first-as; | [edit fabric protocols bgp],
[edit fabric protocols bgp group group_name],
[edit fabric protocols bgp group group_name neighbor address],
[edit logical-systems name],
[edit logical-systems name protocols bgp],
[edit logical-systems name protocols bgp group group_name],
[edit logical-systems name pr... | Enforce that the first (left-most) autonomous system number (ASN) in AS-path is the previous neighbor's
ASN. When configured, this statement enforces that as the domain is transited, the routes received from
an EBGP peer have the peer’s ASN in the left-most position of the AS path. | [] | 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. | [
"Prepending 4-Byte AS Numbers in an AS Path",
"Example: Enforcing Correct Autonomous System Number in AS-Path in BGP Network"
] |
enforce-strict-scale-limit-license (Subscriber Management) | enforce-strict-scale-limit-license; | [edit system services subscriber-management] | Configure the router to strictly enforce the subscriber scaling license, and to not allow the normal grace
period. No additional subscribers are allowed to log in after the number of subscribers reaches the
maximum allowed for the license. | [] | system—To view this statement in the configuration.
system-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.2. | [
"Configuring User-Defined Dynamic Variables in Dynamic Profiles",
"User-Defined Variables",
"Using Variable Expressions in User-Defined Variables"
] |
engine-id (Forwarding Options) | engine-id number; | [edit forwarding-options accounting name output interface interface-name],
[edit forwarding-options monitoring name output interface interface-name],
[edit forwarding-options sampling instance instance-name family (inet | inet6 | mpls) output
interface interface-name],
[edit forwarding-options sampling family (inet | ... | Specify the engine ID number for flow monitoring and accounting services. | [
{
"name": "number",
"desc": "Identity of accounting interface."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Traffic Sampling on MX, M and T Series Routers",
"Configuring Flow Monitoring",
"Configuring Discard Accounting"
] |
engine-id | engine-id {
(local engine-id-suffix | use-default-ip-address | use-mac-address);
} | [edit snmp] | Define a unique identifier for an SNMPv3 engine by configuring the suffix of the engine ID. The engine
ID is used for identification only and not for addressing. There are two parts of an engine ID: the prefix
and the suffix. The prefix is formatted according to the specifications defined in RFC 3411, An
Architecture f... | [
{
"name": "local engine-id-suffix",
"desc": "The engine ID suffix is set based on the data entered."
},
{
"name": "use-default-ip-address",
"desc": "The engine ID suffix is generated from the default IP address."
},
{
"name": "use-mac-address",
"desc": "The engine ID suffix is genera... | snmp—To view this statement in the configuration.
snmp-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 11.1. | [
"Configuring the Local Engine ID"
] |
engine-not-ready (Security Antivirus Sophos Engine) | default (block | log-and-permit | permit); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus sophos-engine profile profile-name fallback-
options] | The scan engine is initializing itself, for example, loading the signature database. During this phase, it is
not ready to scan a file. A file could either pass or be blocked according to this setting. | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
},
{
"name": "permit",
"desc": "Permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | Statement introduced in Release 11.1.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [
"Sophos Antivirus Configuration Overview"
] |
engine-not-ready | engine-not-ready (block | log-and-permit); | [edit security utm default-configuration]
[edit security utm feature-profile anti-virus juniper-express-engine profile profile-name
fallback-options]
[edit security utm feature-profile anti-virus kaspersky-lab-engine profile profile-name fallback-
options] | The scan engine is initializing itself, for example, loading the signature database. During this phase, it is
not ready to scan a file. A file could either pass or be blocked according to this setting. The default
action is block. | [
{
"name": "block",
"desc": "Log the error and deny the traffic"
},
{
"name": "log-and-permit",
"desc": "Log the error and permit the traffic"
}
] | security—To view this statement in the configuration.
security-control—To add this statement to the configuration. | The Express and Kaspersky antivirus feature is not supported from Junos OS Release 15.1X49-D10
onwards. For previous releases, statement introduced in Junos OS Release 9.5.
The [edit security utm default-configuration] hierarchy level is introduced in Junos OS Release 18.2R1. | [] |
engine-type | engine-type number; | [edit forwarding-options accounting name output interface interface-name],
[edit forwarding-options monitoring name output interface interface-name],
[edit forwarding-options sampling instance instance-name family (inet | inet6 | mpls) output
interface interface-name],
[edit forwarding-options sampling family (inet | ... | Specify the engine type number for flow monitoring and accounting services. The engine type attribute
refers to the type of the flow switching engine, such as the route processor or a line module. The
configured engine type is inserted in output cflowd packets. The Source ID, a 32-bit value to ensure
uniqueness for all... | [
{
"name": "number",
"desc": "Platform-specific accounting interface type."
}
] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced before Junos OS Release 7.4. | [
"Configuring Traffic Sampling on MX, M and T Series Routers",
"Configuring Flow Monitoring",
"Configuring Discard Accounting"
] |
enhanced (forwarding-class-accounting) | enhanced {
overhead-bytes overhead-value (0-255 bytes);
traffic-type (ucast | mcast);
family (ipv4 | ipv6 | both );
direction (ingress | egress | both);
} | [edit interfaces interface-name forwarding-class-accounting],
[edit interfaces interface-name unit logical-unit-number forwarding-class-accounting] | Specify the traffic and type for which you want to apply counters. A single aggregate counter per
forwarding class can be used for inet and inet6 flows. Forwarding class accounting applies to transit
traffic only, not host-generated or host-bound traffic. For ingress, only packets forwarded to the fabric
are counted. F... | [
{
"name": "overhead-bytes",
"desc": ""
},
{
"name": "overhead-value",
"desc": "The number of overhead-bytes to be accounted. Range: 0 through 255 bytes Default: If zero, or no value is specified, the number of overhead-bytes will be determined by the encapsulation configured on 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 14.1 in MX Series. | [
"CoS-Based Interface Counters for IPv4 or IPv6 Aggregate on Layer 2"
] |
enhanced (Protocols EVPN OISM) | enhanced {
forward-on-source-bridge-domain {
forward-policy [ forwarding-policy-name ... ];
}
} | [edit routing-instances name protocols evpn oism] | Set options in a Layer 3 virtual routing and forwarding (VRF) routing instance on an EVPN fabric device
for optimized intersubnet multicast (OISM) running in enhanced OISM mode.
The options are explained separately. See CLI Explorer for all options. | [] | routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration. | Statement introduced in Junos OS and Junos OS Evolved Release 25.2R1. | [
"Enhanced OISM Exception Policy to Forward on Source VLAN Instead of SBD for Packets with",
"TTL=1",
"Overview of Enhanced OISM",
"How Enhanced OISM Works"
] |
enhanced | enhanced; | [edit forwarding-options storm-control],
[edit logical-systems name routing-instances name forwarding-options storm-control],
[edit logical-systems name tenants name routing-instances name forwarding-options storm-control],
[edit routing-instances name forwarding-options storm-control],
[edit tenants name routing-insta... | Storm control defines a threshold for broadcast, unknown unicast, or multicast traffic. If traffic exceeds
this threshold, storm control drops the packets. When a filter is applied to the storm control interface,
the dropped packet count increases even when storm control does not drop packets. You can configure
enhance... | [] | interface | Statement introduced in Junos OS Release 17.4R1. | [
"Enabling and Disabling Storm Control (ELS)"
] |
enhanced-cfm-mode | enhanced-cfm-mode enhanced-cfm-mode; | [edit logical-systems name protocols oam ethernet connectivity-fault-management],
[edit protocols oam ethernet connectivity-fault-management] | Enables enhanced CFM mode. When you enable enhanced CFM mode, Junos OS supports 32, 000
maintenance association end points (MEPs) and maintenance intermediate points (MIPs) each per
chassis for bridge, VPLS, L2VPN, and CCC domains. To support enhanced CFM mode, configure the
network services mode on the router as enhan... | [] | Routing | Statement introduced in Junos OS Release 17.2R1. | [
"Enabling Enhanced Connectivity Fault Management Mode"
] |
enhanced-convergence | enhanced-convergence; | [edit interfaces aeX aggregated-ether-options mc-ae]
[edit interfaces irb unit unit-number] | NOTE: On EX9200 and QFX10000 switches, enhanced convergence is applicable for
unicast traffic only—for example, when a MAC address is learned over an MC-AE
interface, or an ARP entry is resolved over an MC-AE interface.
NOTE: Enhanced convergence is not supported on QFX5100, QFX5110, QFX5120,
QFX5200-48Y, QFX5200-32C, ... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 15.1R1. | [] |
enhanced-hash-key (EX) | enhanced-hash-key {
family any {
incoming-interface-index;
no-tunnel-payload;
}
family inet {
gtp-tunnel-endpoint-identifier;
no-destination-port;
no-source-port;
type-of-service;
}
family inet6 {
gtp-tunnel-endpoint-identifier;
no-dest... | [edit forwarding-options]
Junos OS Evolved uses the set command instead of edit. | Configure the hashing key used to hash link aggregation group (LAG) and equal-cost multipath (ECMP)
traffic, or enable adaptive load balancing (ALB) in a Virtual Chassis Fabric (VCF).
NOTE: Starting in Junos OS Release 14.1X53-D46, 15.1R7, 16.1R6, 17.1R3, 17.2R2,
17.3R2, and 17.4R1, the ALB feature is deprecated. If fa... | [] | interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 13.2X51-D15.
The fabric-load-balance statement introduced in Junos OS Release 14.1X53-D10.
The fabric-load-balance statement deprecated starting in Junos OS Releases 14.1X53-D46, 15.1R7,
16.1R6, 17.1R3, 17.2R2, 17.3R2, and 17.4R1.
The hash-seed statement introduced in Junos OS ... | [
"Configuring the Fields in the Algorithm Used To Hash LAG Bundle and ECMP Traffic (CLI Procedure)",
"Understanding the Algorithm Used to Hash LAG Bundle and Egress Next-Hop ECMP Traffic",
"Understanding Passive Monitoring",
"Understanding Per-Packet Load Balancing"
] |
enhanced-hash-key profile1/profile2 | enhanced-hash-key profile1/profile2 profile-fields | [edit forwarding-options] | no-in-tunnel
Inner tunnel header fields
Traffic Class
no-in-layer3-pri
Inner L3 dscp/dp fields
no-layer3-pri
L3 dscp/dp fields
Layer 2
no-in-layer2
Inner layer2 fields
no-layer2
DMAC, SMAC and VLAN fields
Layer 3
no-in-layer3-proto
Inner L3 protocol fields
no-layer3-proto
L3 protocol fields
no-layer3-source-address
L3 ... | [
{
"name": "profile1",
"desc": ""
},
{
"name": "profile2",
"desc": ""
}
] | •
interface—To view this statement in the configuration.
•
interface-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.2 | [
"hash-seed (profile)",
"load-balance profile1/profile2"
] |
enhanced-hash-key | Syntax (Junos OS Evolved)
enhanced-hash-key {
family any {
incoming-interface-index;
no-tunnel-payload;
in-destination-mac;
in-source-mac;
in-outvlan;
in-invlan;
}
family inet {
gtp-tunnel-endpoint-identifier;
no-destination-port;
no-so... | [edit forwarding-options],
[edit logical-systems logical-system-name routing-instances instance-name forwarding-options],
[edit routing-instances instance-name forwarding-options]
Junos OS Evolved uses the set command instead of edit. | Configure the hashing key used to hash link aggregation group (LAG) and equal-cost multipath (ECMP)
traffic, or enable adaptive load balancing (ALB) in a Virtual Chassis Fabric (VCF).
NOTE: Starting in Junos OS Release 14.1X53-D46, 15.1R7, 16.1R6, 17.1R3, 17.2R2,
17.3R2, and 17.4R1, the ALB feature is deprecated. If fa... | [
{
"name": "services-loadbalancing",
"desc": "Distributes traffic across PICs based on source IP address when a route pointing"
},
{
"name": "symmetric",
"desc": "Enable symmetric load balancing across aggregated Ethernet interfaces. This option is needed"
},
{
"name": "inet",
"desc":... | 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.
services-loadbalancing statement introduced in Junos OS Release 11.2.
gtp-tunnel-endpoint-identifier statement introduced in Junos OS Release 13.2
The fabric-load-balance statement introduced in Junos OS Release 14.1X53-D10.
The fabric-load-balance statement deprecated sta... | [
"Understanding the Algorithm Used to Load Balance Traffic on MX Series Routers",
"Configuring Symmetrical Load Balancing on an 802.3ad Link Aggregation Group on MX Series",
"Routers",
"Configuring the Fields in the Algorithm Used To Hash LAG Bundle and ECMP Traffic (CLI Procedure)",
"Understanding the Algor... |
enhanced-hierarchical-policer (Dynamic Profiles) | enhanced-hierarchical-policer name {
logical-interface-policer;
high {
committed-burst-size variable_name;
committed-information-rate variable_name;
max-committed-information-rate variable_name;
then discard;
}
low {
committe... | [edit dynamic-profiles name firewall] | You can configure enhanced hierarchical policer under dynamic profile to rate limit traffic for
subscribers. Traffic policing is supported at four levels of hierarchies with respect to the traffic priority-
High, Medium-High, Medium-Low, and Low.
When you configure enhanced hierarchical policer under a dynamic profile... | [
{
"name": "name",
"desc": "Enhanced hierarchical policer name"
},
{
"name": "high",
"desc": "The policer is assigned to rate-limit traffic from the high traffic priority."
},
{
"name": "medium-high",
"desc": "The policer is assigned to rate-limit traffic from the medium-high traffic ... | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Evolved Release 25.4R1. | [] |
enhanced-hierarchical-policer | enhanced-hierarchical-policer enhanced-hierarchical-policer-name | [edit firewall] | Configure up to four policers in an enhanced hierarchical policer configuration to police traffic from four
traffic priority levels, namely, high, medium-high, medium-low, and low. | [] | firewall—To view this statement in the configuration.
firewall-control—To add this statement to the configuration. | Statement introduced in Junos OS Release 23.3. | [] |
enhanced-mode (Network Services) | enhanced-mode; | [edit chassis network-services] | PTX1000, PTX3000 and PTX5000 Routers—When you configure enhanced-mode on PTX series routers, the
following features are enabled on the router:
•
Filter-based generic routing encapsulation (GRE) for IPV4 and IPV6 tunneling.
•
promote gre-key statement for configuring gre-key as one of the matches in a filter.
•
promote ... | [] | 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. | [
"Network Services Mode Overview"
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.