R3303-HP HSR6800 Routers MPLS Configuration Guide

166
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Create a remote CCC
connection.
ccc ccc-connection-name interface
interface-type interface-number in-label
in-label-value out-label out-label-value
{ nexthop ip-address | out-interface
interface-type interface-number }
[ control-word | no-control-word ]
The interface interface-type
interface-number option specifies
a PE-CE interface of the PE. By
specifying the interface, you bind
the AC link on the interface to the
remote CCC connection to be
created.
Configuring a P device
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Configure a transit static LSP.
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
For more
information about
the static-lsp
command, see
MPLS Command
Reference.
Configuring SVC MPLS L2VPN
You can configure an ordinary static VC (SVC) or configure a pair of primary and backup SVCs in the
following methods:
• Configure a static VC on a Layer 3 interface. This method does not support VC redundancy.
• Configure a primary static VC and a backup static VC on a Layer 3 interface. This method
implements VC redundancy.
• Configure a primary static VC and a backup static VC for a service instance. This method
implements VC redundancy.
After you configure SVC on a Layer 3 interface, packets arriving at this interface are forwarded over the
VC. HP recommends that you configure SVC on a Layer 3 interface when all users connected to the Layer
3 interface have their packets forwarded over the same VC.
After you configure SVC for a service instance applied on a Layer 2 Ethernet interface, the interface uses
the service instance to match incoming packets. Packets matching the service instance are forwarded
over the VC. A service instance can match all packets received on the interface, packets carrying the
specified VLAN tags, all tagged packets, or packets with no VLAN tags. HP recommends that you
configure static VCs in this way when the users connected to the same Layer 2 interface must use different
VCs to forward packets.
Service instances can be created only on Layer 2 Ethernet interfaces.
Configuring a static VC on a Layer 3 interface