Configuring Svc Mpls L2Vpn; Configuring Martini Mpls L2Vpn - HP 10500 SERIES Configuration Manual

Step
2. Configure a transit static LSP.

Configuring SVC MPLS L2VPN

SVC MPLS L2VPN does not use any signaling protocol to transfer L2VPN information. It uses tunnels to
transport data between PEs. SVC supports LDP LSP and CR-LSP tunnles. By default, LDP LSP tunnels are
used.
After you configure SVC on a Layer 3 interface, packets arriving at this interface are forwarded over the
VC. If the Layer 3 interface is a VLAN interface, all packets carrying the tag of the VLAN are forwarded
over the VC, no matter which Layer 2 Ethernet interfaces that the packets arrived at. The device chooses
a VC for a received packet according to only the VLAN tag carried in the packet. It cannot differentiate
the users and services on different Layer 2 Ethernet interfaces. HP recommends that you configure SVC
on a VLAN interface when all users connected to the VLAN interface have their packets forwarded over
the same VC.
To configure SVC MPLS L2VPN:
Step
1. Enter system view.
2. Enter the view of the interface connecting
the CE.
3. Create a static VC connection.
The label range for SVC is 16 to 1023, which is the label range for static LSPs.
The transmit-vpn-label and receive-vpn-label configured on the local PE must be the same as the
receive-vpn-label and transmit-vpn-label configured on the peer PE.

Configuring Martini MPLS L2VPN

To configure Martini MPLS L2VPN, complete the following tasks:
Configure the remote peer.
1.
Martini MPLS L2VPN requires PEs to exchange VC labels. Because PEs may not be connected to
each other directly, you must specify the peer PE on each PE to establish a remote session and
transfer VC FECs and VC labels through the session.
Create a VC in Martini mode, in one of the following ways:
2.
Configure a Martini VC on a Layer 3 interface.
In this way, packets arriving at this interface are forwarded over the created VC. If the Layer 3
interface is a VLAN interface, all packets carrying the tag of the VLAN are forwarded over the
Command
static-lsp transit lsp-name incoming-interface
interface-type interface-number in-label in-label
{ nexthop next-hop-addr | outgoing-interface
interface-type interface-number } out-label out-label
Command
system-view
interface interface-type interface-number
mpls static-l2vc destination destination-router-id
transmit-vpn-label transmit-label-value receive-vpn-label
receive-label-value [ ethernet | vlan } | tunnel-policy
tunnel-policy-name ] *
201
Remarks
For static LSP
configuration
commands, see
MPLS Command
Reference.