R3303-HP HSR6800 Routers MPLS Configuration Guide

168
Configuring primary and backup static VCs for a service
instance
NOTE:
This feature is supported only on routers with SAP-4EXPs.
To perform this task, complete the following operations on a PE:
• Create a service instance on a Layer 2 Ethernet interface.
• Configure a packet matching rule for the service instance.
• Create a primary static VC and a backup static VC for the service instance.
After you perform these operations, packets arriving at the Layer 2 Ethernet interface and matching the
packet matching rule are forwarded over the primary VC, or over the backup VC if the primary VC is
down, or if you manually switch traffic to the backup VC.
To create multiple VCs with the same attributes (such as VC encapsulation type and VC tunneling policy),
you do not need to configure the attributes one by one for each VC. Instead, you can create a PW class,
configure VC attributes in the PW class, and then reference the PW class in each VC.
To create a primary static VC and a backup static VC for a service instance:
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Create a PW class and enter
PW class view.
pw-class pw-class-name
Optional.
By default, no PW class is created.
3. Specify the VC
encapsulation type.
trans-mode { ethernet | vlan }
Optional.
By default, the VC encapsulation
type is VLAN.
4. Specify the tunneling policy.
pw-tunnel-policy policy-name
Optional.
If you do not specify a tunneling
policy, the default tunneling policy is
used. The default tunneling policy
selects only one tunnel in this order:
LSP tunnel, GRE tunnel, CR-LSP
tunnel.
For information about how to
configure a tunneling policy, see
"Configuring MPLS L3VPN."
5. Return to system view.
quit N/A
6. Enter Layer 2 Ethernet
interface view.
interface interface-type
interface-number
N/A
7. Create a service instance
and enter service instance
view.
service-instance instance-id
By default, no service instance is
created.
8. Configure a packet
matching rule for the service
instance.
encapsulation { s-vid vlan-id
[ only-tagged ] | port-based |
tagged }
By default, no packet matching rule
is configured for the service instance.