Understanding EoMPLS
Enter the no form of each command to delete the tunnel or disable the feature or capability. To remove
all primary auto tunnels, enter the clear mpls traffic-eng auto-tunnel primary privileged EXEC
command.
Beginning in privileged EXEC mode, follow these steps to establish MPLS backup auto tunnels:
Command
Step 1
configure terminal
Step 2
mpls traffic-eng auto-tunnel backup
Step 3
mpls traffic-eng auto-tunnel backup
nhop-only
Step 4
mpls traffic-eng auto-tunnel backup
tunnel-num [min num] [max num]
Step 5
mpls traffic-eng auto-tunnel backup timers
removal unused sec
Step 6
mpls traffic-eng auto-tunnel backup config
unnumbered interface interface-id
Step 7
mpls traffic-eng auto-tunnel primary
config mpls ip
Step 8
end
Step 9
show interface tunnel tunnel-num
Step 10
copy running-config startup-config
Enter the no form of each command to delete the tunnel or disable the feature or capability.
Understanding EoMPLS
Any Transport over MPLS (AToM) is a solution for transporting Layer 2 packets over an MPLS network,
allowing service providers to use the MPLS network to provide connectivity between customer sites with
existing Layer 2 networks. Instead of separate networks with network management environments,
service providers can use the MPLS network to transport all types of traffic for different customers. The
switch supports EoMPLS, a subset of AToM that uses a tunneling mechanism to carry Layer 2 Ethernet
traffic.
EoMPLS encapsulates Ethernet frames in MPLS packets and forwards them across the MPLS network.
Each frame is sent as a single packet, and the provider-edge (PE) routers connected to the backbone add
and remove labels as appropriate for packet encapsulation:
•
Cisco ME 3800X and 3600X Switch Software Configuration Guide
34-26
The ingress PE router receives an Ethernet frame and encapsulates the packet by removing the
preamble, the start of frame delimiter (SFD), and the frame check sequence (FCS). The rest of the
packet header is not changed.
Chapter 34
Configuring MPLS, MPLS VPN, MPLS OAM, and EoMPLS
Purpose
Enter global configuration mode.
Configure the switch to automatically create next-hop (NHOP) and
next-next hop (NNHOP) backup tunnels.
Configure the switch to automatically build only next-hop (NHOP)
backup tunnels.
Configure the range of tunnel interface numbers for backup
autotunnels.
Configure how frequently (in seconds) a timer scans the backup
autotunnels and removes tunnels that are not being used. Valid values
are 0 to 604800. The default is every 3600 seconds (60 minutes).
Enable IP processing without an explicit address.
interface interface-id is the interface on which IP processing will be
enabled without an explicit address. The default interface is
Loopback0.
Enable Label Distribution Protocol (LDP) on primary autotunnels.
Return to privileged EXEC mode.
Verify the configuration.
(Optional) Save your entries in the configuration file.
OL-23400-01