Configuring A Static Vc On A Layer 3 Interface; Configuring Primary And Backup Static Vcs On A Layer 3 Interface - HP HSR6800 Configuration Manual

After you configure SVC on a Layer 3 interface, packets arriving at this interface are forwarded over
the VC. As a best practice, 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. As a best
practice, 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

Step
1. Enter system view.
2. Enter the view of the
interface connecting the CE.
3. Create a static VC.
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 primary and backup static VCs on a Layer 3
interface
Step
1. Enter system view.
2. Enter the view of the
interface connecting the CE.
3. Create a primary static VC
and a backup static VC and
enter static-L2VC view.
4. Configure the VC labels for
the primary VC.
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 [ { control-word |
ethernet | no-control-word | vlan } |
tunnel-policy tunnel-policy-name ] *
Command
system-view
interface interface-type
interface-number
mpls static-l2vc destination vcid
[ { control-word | ethernet |
no-control-word | vlan } |
[ tunnel-policy
tunnel-policy-name ]
[ backup-peer ip-address vcid
[ backup-tunnel-policy
tunnel-policy-name | revertive
[ wtr-time wtr-time ] ] * ] ] *
static label local local-vc remote
remote-vc
159
Remarks
N/A
N/A
This feature is not
supported on VLAN
interfaces.
Remarks
N/A
N/A
By default, no primary and
backup VCs are created.
To implement VC redundancy,
use the backup-peer keyword
to create a backup VC.
By default, no VC labels are
configured for the primary VC.