Associating Track with MPLS L2VPN
About Track association with MPLS L2VPN
When you bind an AC to a cross-connect on an MPLS L2VPN network, you can associate Track with the AC. Then, the AC is up only when one or more of the associated track entries are positive.
Associating Track with an AC helps detect AC failures. For example, when an AC is a VE-L2VPN interface, the AC interface will not go down upon a link failure because the interface is a virtual interface. To resolve the problem, you can associate Track with the AC to detect failures on the link that connects the PE-agg to the L3VPN or IP backbone. When a failure occurs on the link, the VE-L2VPN interface is set to down. Consequently, the PW bound to the AC goes down. If the PW has a backup PW, traffic can be switched to the backup PW. For more information about VE-L2VPN interfaces and L2VPN access to L3VPN or IP backbone, see MPLS Configuration Guide.
An AC can be one of the following types:
Layer 3 interface.
Ethernet service instance on a Layer 2 Ethernet interface or Layer 2 aggregate interface.
Associating a track entry with a Layer 3 interface bound to a non-BGP cross-connect
Enter system view.
system-view
Enter cross-connect group view.
xconnect-group group-name
Enter cross-connect view.
connection connection-name
Bind the Layer 3 interface to the non-BGP cross-connect and associate the interface with a track entry.
ac interface interface-type interface-number track track-entry-number&<1-3>
By default, a Layer 3 interface is not bound to any cross-connect or associated with any track entries.
Associating a track entry with a Layer 3 interface bound to a BGP cross-connect
Enter system view.
system-view
Enter cross-connect group view.
xconnect-group group-name
Enter auto-discovery cross-connect group view.
auto-discovery bgp
Enter site view.
site site-id [ range range-value ] [ default-offset default-offset-value ]
Enter auto-discovery cross-connect view.
connection remote-site-id remote-site-id
Bind the Layer 3 interface to the BGP cross-connect and associate the interface with a track entry.
ac interface interface-type interface-number track track-entry-number&<1-3>
By default, a Layer 3 interface is not bound to any cross-connect or associated with any track entries.
Associating a track entry with an Ethernet service instance bound to a non-BGP cross-connect
Enter system view.
system-view
Enter cross-connect group view.
xconnect-group group-name
Enter cross-connect view.
connection connection-name
Bind the Ethernet service instance on the interface to the non-BGP cross-connect and associate the service instance with a track entry.
ac interface interface-type interface-number service-instance instance-id [ access-mode { ethernet | vlan } ] track track-entry-number&<1-3>
By default, an Ethernet service instance is not bound to any cross-connect or associated with any track entries.
Associating a track entry with an Ethernet service instance bound to a BGP cross-connect
Enter system view.
system-view
Enter cross-connect group view.
xconnect-group group-name
Enter auto-discovery cross-connect group view.
auto-discovery bgp
Enter site view.
site site-id [ range range-value ] [ default-offset default-offset-value ]
Enter auto-discovery cross-connect view.
connection remote-site-id remote-site-id
Bind the Ethernet service instance on the interface to the BGP cross-connect and associate the service instance with a track entry.
ac interface interface-type interface-number service-instance instance-id [ access-mode { ethernet | vlan } ] track track-entry-number&<1-3>
By default, an Ethernet service instance is not bound to any cross-connect or associated with any track entries.