mpls l2vc track admin-vc

Function

The mpls l2vc track admin-vc command associates service PWs with the mPWs.

The undo mpls l2vc track admin-vc command deletes the association between service PWs and mPWs.

By default, service PWs are not associated with the mPWs.

Format

mpls l2vc [ secondary | bypass ] track admin-vc interface loopback interface-number

undo mpls l2vc [ secondary | bypass ] track admin-vc

Parameters

Parameter	Description	Value
secondary	Associates the secondary service PW with the mPW.	-
bypass	Associates the bypass service PW with the mPW.	-
interface loopback interface-number	Specifies the loopback interface on which the mPW is configured.	The value is a decimal integer and must be the same as the number of the loopback interface on which the mPW is configured.

Views

Interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

BFD is often configured for PWs to quickly detect PW faults. If there are a large number of service PWs with the same source and destination, you can configure mPWs with the same source and destination as those of the service PWs and associate these service PWs with the mPWs. By tracking the status of the mPWs, BFD can quickly detect faults on service PWs associated with the mPWs. BFD does not need to be configured for service PWs. This method reduces the number of BFD sessions and saves system resources and public network link bandwidth.

You can run the mpls l2vc track admin-vc command to associate service PWs with mPWs for service PW status monitoring.

Prerequisites

Service PWs and mPWs have been created using the mpls l2vc and mpls l2vc admin commands.

An mPW and its associated service PW must have the same peers.
A service PW can be associated with only one mPW.
Multiple service PWs with the same source and destination can be associated with only one mPW.

Precautions

After service PWs are associated with an mPW, the mPW detects public network link faults in a unified manner.

If the mPW status remains unchanged, traffic can be properly forwarded over service PWs.
If the mPW detects a public link fault, the mPW changes its status from Up to Down and notifies all its associated service PWs.
- If both primary and secondary service PWs exist, the mPW triggers a switchover between the primary and secondary service PWs.
- If only one service PW exists, the service PW changes its status from Up to Down and stops forwarding data.
After the fault is rectified, the mPW changes its status from Down to Up. If both primary and secondary service PWs exist, a switchover will be performed between them based on the configured revertive switching policy. If only one service PW exists, the service PW changes its status from Down to Up. The service PW then starts to forward traffic again.

The mpls l2vc track admin-vc command applies to only single-hop primary and secondary PWs and does not apply to multi-hop PWs.

Example

# Associate the primary service PW with the mPW.

<HUAWEI> system-view
[HUAWEI] interface loopback 0
[HUAWEI-Loopback0] mpls l2vc 1.1.1.1 1 admin
[HUAWEI-Loopback0] quit
[HUAWEI] interface vlanif 10
[HUAWEI-Vlanif10] mpls l2vc 1.1.1.1 5
[HUAWEI-Vlanif10] mpls l2vc track admin-vc interface loopback 0

# Associate the secondary service PW with the mPW.

<HUAWEI> system-view
[HUAWEI] interface loopback 1
[HUAWEI-Loopback1] mpls l2vc 2.2.2.2 2 admin
[HUAWEI-Loopback1] quit
[HUAWEI] interface vlanif 20
[HUAWEI-Vlanif20] mpls l2vc 1.1.1.1 10
[HUAWEI-Vlanif20] mpls l2vc 2.2.2.2 6 secondary
[HUAWEI-Vlanif20] mpls l2vc secondary track admin-vc interface loopback 1

# Associate the bypass service PW with the mPW.

<HUAWEI> system-view
[HUAWEI] interface loopback 2
[HUAWEI-Loopback2] mpls l2vc 3.3.3.3 3 admin
[HUAWEI-Loopback2] quit
[HUAWEI] interface vlanif 30
[HUAWEI-Vlanif30] mpls l2vc 1.1.1.1 20 bypass
[HUAWEI-Vlanif30] mpls l2vc 3.3.3.3 7 bypass
[HUAWEI-Vlanif30] mpls l2vc bypass track admin-vc interface loopback 2