1-8
To do…
Use the command…
Remarks
Enter system view
system-view
—
Configure a transit static LSP
static-lsp transit
lsp-name
incoming-interface
interface-type interface-number
in-label in-label
nexthop
next-hop-addr
out-label
out-label
Required
z
With CCC, no static LSPs are required on the PEs but dedicated bidirectional static LSPs are
required on all the P devices between the PEs for transmitting the data of the CCC connection.
z
For static LSP configuration commands, refer to
MPLS Basics Commands
in the
MPLS Volume
.
Configuring SVC MPLS L2VPN
SVC MPLS L2VPN does not use any signaling protocol to transfer L2VPN information. Instead, it uses
tunnels to transport data between PEs.
SVC supports LDP LSP and CR-LSP. By default, LDP LSP tunnels are used.
Configuration Prerequisites
Before configuring SVC MPLS L2VPN, complete these tasks:
z
Configuring IGP on the PEs and P devices to guarantee the IP connectivity of the MPLS backbone
z
Configuring MPLS basic capability and MPLS LDP for the MPLS backbone on the PEs and P
devices to establish LDP LSPs
z
Enabling MPLS L2VPN on the PEs
z
For VLAN access, configuring a subinterface; for ATM access, configuring a VC
z
Establishing the tunnels between PEs according to the tunneling policy.
To configure SVC MPLS L2VPN, you need the following data:
z
Types and numbers of the interfaces connecting the CEs
z
Destination LSR ID of SVC
z
Incoming and outgoing labels of the L2VPN connection
z
SVC tunneling policy
Configuration Procedure
Follow these steps to configure SVC MPLS L2VPN on the PE:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enter interface view for the
interface connecting the CE
interface interface-type
interface-number
—
Summary of Contents for S7906E - Switch
Page 82: ...1 4 DeviceA interface tunnel 1 DeviceA Tunnel1 service loopback group 1...
Page 200: ...1 11 DeviceB display vlan dynamic No dynamic vlans exist...
Page 598: ...ii...
Page 1757: ...4 9...
Page 1770: ...6 4...
Page 2017: ...2 11 Figure 2 3 SFTP client interface...
Page 2238: ...1 16 DeviceA cfd linktrace service instance 1 mep 1001 target mep 4002...