The track hub-pw associates spoke PW status with hub PW status.
The undo track hub-pw deletes the association between spoke PW status and hub PW status.
By default, spoke PW status is not associated with hub PW status.
Usage Scenario
Figure 1 shows a VPLS PW redundancy scenario. The UPE connects to SPE1 over PW1, a primary PW, and connects to SPE2 over PW2, a secondary PW. PW1 and PW2 work in backup mode. SPEs and NPEs are connected using hub PWs.
Under normal circumstances, if all hub PWs connected to SPE1 go Down but PW1 is Up, the upstream traffic still travels along the primary PW, PW1. As a result, traffic gets lost. To prevent traffic loss, you can run the track hub-pw command on SPE1 to associate spoke PW status with hub PW status. After the track hub-pw command is configured, SPE1 notifies the UPE of switching traffic to the secondary PW for transmission after detecting that all connected hub PWs go Down.
Prerequisites
This command can only be used for a spoke PW to track the status of hub PWs. The peer peer-address [ negotiation-vc-id vc-id ] [ tnl-policy policy-name ] upe must have been run the create a spoke PW.
The peer peer-address [ negotiation-vc-id vc-id ] pw pw-name command must have been run to display the PW view. This is because the track hub-pw command can only be run in the VSI-LDP-PW view.