E Commands
This chapter describes the Cisco NX-OS Multiprotocol Label Switching commands that begin with E.
echo revision
To specify the revision number of the echo packet’s default values, use the echo revision command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to specify the revision number of the echo packet’s default values:
Related Commandss
|
|
|
|---|---|
Enters MPLS OAM configuration mode and customizes the default behavior of echo packets. |
echo vendor-extension
To send the Cisco-specific type, length, value (TLV) extension, use the echo vendor-extension command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to send the Cisco-specific type, length, value (TLV) extensions with echo packets:
Related Commands
|
|
|
|---|---|
Specifies the revision number of the echo packet’s default values. |
|
Enters MPLS OAM configuration mode and customizes the default behavior of echo packets. |
encapsulation dot1q
To configure the matching criteria for mapping dot1q frames on an ingress interface to this interface, use the encapsulation dot1q command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The subinterfaces between the customer-edge (CE) and provide edge (PE) routers that are running Ethernet over MPLS (EoMPLS) must be in the same subnet. All other subinterfaces and backbone devices do not need to be in the same subnet.
Examples
This example shows how to configure the matching criteria for mapping dot1q frames on an ingress interface to this interface:
Related Commands
encapsulation mpls
To specify the Multiprotocol Label Switching (MPLS) encapsulation for a pseudowire port profile, use the encapsulation mpls command.
Syntax Description
Defaults
Command Modes
config-if- prof configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to specify the MPLS encapsulation for a pseudowire port profile:
Related Commands
exclude-address
To specify an IP address while configuring a traffic engineering (TE) explicit-path that TE should avoid using while calculating the label switched path (LSP), use the exclude-address command.
Syntax Description
Defaults
Command Modes
Explicit-path configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
Both primary and backup tunnel paths can be dynamic or explicit and they do not have to use the exclude-address. Because backup tunnels must avoid the protected link or node, you should use the exclude-address command.
When using the exclude-address command to specify the path for a backup tunnel, you must exclude an interface IP address to avoid a link (for creating a next-hop [NHOP] backup tunnel), or a router ID address to avoid a node (for creating an next-next-hop [NNHOP] backup tunnel).
Examples
This example shows how to specify an address to exclude while configuring an explicit-path:
Related Commands
|
|
|
|---|---|
exp
To configure the EXP bits that are forwarded over the member tunnel, use the exp command.
exp [list-of-exp-values] [default]
Syntax Description
EXP bits allowed for the interface. Enter up to eight EXP values separated by spaces. Values range from 0 to 7. The default is the EXP values that were not configured or a specific member tunnel. |
|
Defaults
The member tunnel will forward the packets with the EXP bits that are not being forwarded by other member tunnels that are part of the same bundle.
Command Modes
cbts-member configuration mode
Command History
|
|
|
|---|---|
Usage Guidelines
You cannot configure the following traffic engineering (TE) commands on a class-based tunnel selection (CBTS) member tunnels (auto-bw; autoroute; backup-bw; description; destination; fowarding-adjacency; inherit; source).
Examples
This example shows how to configure the EXP bits that are forwarded over the member tunnel:
Related Commands
|
|
|
|---|---|
explicit-null
To configure an advertised explicit null label in place of an implicit null label, use the explicit-null command. To return to the default setting, use the no form of this command.
explicit-null [for prefix-list | to prefix-list | for prefix-list to prefix-list]
no explicit-null [for prefix-list | to prefix-list | for prefix-list to prefix-list]
Syntax Description
(Optional) Specifies the prefix list that specifies the controls on destination prefixes. |
|
(Optional) Specifies the access list that specifies the controls on Label Distribution Protocol (LDP) peers. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to configure an explicit null label on an egress Label Switching Router (LSR), which causes that LSR to advertise the explicit null label to all adjacent MPLS routers:
This example shows how to configure an explicit null label and specify the for keyword with a prefix list:
This example shows how to configure an explicit null label and specify the to keyword with a prefix list:
Related Commands
|
|
|
|---|---|
Configures the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP). |
explicit-path
To configure an IP explicit path to be used by tunnel-te label switched path (LSPs), or a path dynamically calculated from the TE topology database, use the explicit-path command. To restore the system to its default condition, use the no form of this command.
explicit-path {name path-name | identifier number}
no explicit-path {name path-name | identifier number}
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
This example shows how to configure the tunnel to use a named IP explicit path or a path dynamically calculated from the TE topology database:
Related Commands
|
|
|
|---|---|
Configures the Multiprotocol Label Switching (MPLS) Traffic Engineering Protocol (MPLS-TE). |
Feedback