
159
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 Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter the view of the
interface connecting the CE.
interface
interface-type interface-number
N/A
3.
Create a static VC.
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
] *
This feature is not
supported on VLAN
interfaces.
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 Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter the view of the
interface connecting the CE.
interface
interface-type
interface-number
N/A
3.
Create a primary static VC
and a backup static VC and
enter static-L2VC view.
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
] ] * ] ] *
By default, no primary and
backup VCs are created.
To implement VC redundancy,
use the
backup-peer
keyword
to create a backup VC.
4.
Configure the VC labels for
the primary VC.
static label local
local-vc
remote
remote-vc
By default, no VC labels are
configured for the primary VC.