In the CUPS scenario, the CP performs a master/backup switchover upon receiving a failure reported by a UP. Use this command to further implement service switchover of the specified VSRP instance when a master/backup switchover is performed.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Bind VSRP instance vs1 to UP interface Ten-GigabitEthernet 3/1/1.

<Sysname> system-view

[Sysname] vsrp instance vs1

[Sysname-vsrp-instance-vs1] bind interface ten-gigabitethernet 3/1/1

user-plane access-interface track

Use user-plane access-interface track to associate a service interface on the UP with a track entry.

Use undo user-plane access-interface track to restore the default.

Syntax

user-plane access-interface interface-type interface-number track track-entry-number

undo user-plane access-interface interface-type interface-number

Default

The service interface on the UP is not associated with any track entries.

Views

System view

Predefined user roles

network-admin

Parameters

track-entry-number: Specifies the track entry ID in the range of 1 to 1024.

interface-type interface-number: Specifies a service interface on the UP by its type and number.

Usage guidelines

The system supports this feature only in standard system operating mode. For more information about system operating modes, see device management configuration in Fundamentals Configuration Guide.

In a CUPS network, a UP can use Track to monitor the state of the service interface on the UP connected to users. When the link layer protocol of the interface becomes faulty, Track notifies the UP. The UP then reports the event to the CP. Upon receiving the event, the CP instructs the UP to perform a master/backup switchover.

After you specify a service interface for each track entry, the UP will send information about the interfaces to the CP in addition to the failure information. The CP can identify a group of interfaces on the UP by interface information in order to instruct the UP to perform master/backup interface switchover.

The command does not take effect if you specify a nonexistent track entry.

A service interface and a track entry must be in one-to-one correspondence. You cannot associate a service interface with different track entries or associate multiple service interfaces with the same track entry.

You cannot execute this command repeatedly to modify the association between the service interface and track entry. To modify the association, execute the undo user-plane access-interface track command to remove the association, and then execute the user-plane access-interface track command again.

You can execute this command multiple times to associate multiple service interfaces with multiple track entries for the UP.

Examples

# Associate service interface Ten-GigabitEthernet 3/1/1 on the UP with track entry 1.

<Sysname> system-view

[Sysname] user-plane access-interface ten-gigabitethernet 3/1/1 track 1

Related commands

track (High Availability Command Reference)

user-plane control-tunnel-down switchover track

Use user-plane control-tunnel-down switchover track to disable master/backup interface switchover on a UP.

Use undo user-plane control-tunnel-down switchover track to restore the default.

Syntax

user-plane control-tunnel-down switchover track track-entry-number

undo user-plane control-tunnel-down switchover track

Default

When the CUSP channel is disconnected, the UP performs a master/backup switchover regardless of whether the link to its upstream router fails.

Views

System view

Predefined user roles

network-admin

Parameters

track-entry-number: Specifies a track entry to monitor the link between the UP and the upstream router. The value range for the track-entry-number argument is 1 to 1024.

Usage guidelines

The system supports this feature only in standard system operating mode. For more information about system operating modes, see device management configuration in Fundamentals Configuration Guide.

If the CUSP channel is disconnected between the CP and a UP where the master interface resides, the CP and UP take relevant actions upon detecting the failure:

· The UP performs a master/backup switchover.

· The CP notifies the UP associated with the backup interface to switch its interface to master.

If a router exists between the CP and UPs and the CP-to-router link is disconnected, the CP is disconnected from all UPs. The master interface switches over to backup 30 seconds after the CUSP channel failure, resulting in service interruption.

Execute this command to use Track to monitor the availability of the link between the UP and the router. Upon a CUSP channel failure, if the UP-to-router link is still available, the UP will not switch its master interface to backup.

This task applies only to UPs.

The command does not take effect if you specify a nonexistent track entry.

Examples

# Disable master/backup interface switchover on the UP, and specify track entry 1 to monitor the link between the UP and the upstream router.

<Sysname> system-view

[Sysname] user-plane control-tunnel-down switchover track 1

Related commands

up-id switchover

user-plane switchover track uplink-group

Use user-plane switchover track uplink-group to associate the UP with a track entry.

Use undo user-plane switchover track uplink-group to remove the association.

Syntax

user-plane switchover track track-entry-number uplink-group group-name

undo user-plane switchover track track-entry-number

Default

A UP is not associated with any track entries.

Views

System view

Predefined user roles

network-admin

Parameters

track-entry-number: Specifies the track entry ID in the range of 1 to 1024.

uplink-group group-name: Specifies a UP uplink network resource group by its name, a case-sensitive string of 1 to 31 characters excluding spaces. You can enter spaces in the string when it is placed within quotation marks (").

Usage guidelines

The system supports this feature only in standard system operating mode. For more information about system operating modes, see device management configuration in Fundamentals Configuration Guide.

In a CUPS network, a UP can use Track to monitor the state of the network interface. When the network interface goes down, Track notifies the UP. The UP then reports the event to the CP. Upon receiving the event, the CP instructs the UP to perform a master/backup switchover.

After you specify a resource group for each track entry, the UP will send the resource group names to the CP in addition to the failure information. The CP can identify a group of interfaces on the UP by resource group name in order to instruct the UP to perform master/backup interface switchover.

The command does not take effect if you specify a nonexistent track entry.

A resource group and a track entry must be in one-to-one correspondence. You cannot associate a resource group with different track entries or associate multiple resource groups with the same track entry.

You cannot execute this command repeatedly to modify the association between the resource group and track entry. To modify the association, execute the undo user-plane switchover track uplink-group command to remove the association, and then execute the user-plane switchover track uplink-group command again.

You can execute this command multiple times to associate multiple resource groups with multiple track entries for the UP.

Examples

# Associate the UP with track entry 1.

<Sysname> system-view

[Sysname] user-plane switchover track 1 uplink-group aaa

Related commands

track (High Availability Command Reference)

user-plane switchover track up-peer-name

Use user-plane switchover track up-peer-name to associate the peer UP with a track entry on the local UP.

Use undo user-plane switchover track up-peer-name to remove the association.

Syntax

user-plane switchover track track-entry-number up-peer-name up-peer-name

undo user-plane switchover track track-entry-number up-peer-name

Default

The peer UP is not associated with any track entries.

Views

System view

Predefined user roles

network-admin

Parameters

track-entry-number: Specifies the track entry ID in the range of 1 to 1024.

up-peer-name: Specifies a UP by its name, a case-sensitive string of 1 to 31 characters excluding spaces. You can enter spaces in the string when it is placed within quotation marks ("). The name must be the same as that specified in the up-id switchover command on the CP.

Usage guidelines

The system supports this feature only in standard system operating mode. For more information about system operating modes, see device management configuration in Fundamentals Configuration Guide.

In a CUPS network, if an intermediate device connects the CP and UP, the following conditions might exist:

· The CUSP channel status is faulty.

· The UP is operating correctly.

In this case, the CP will perform master/backup interface switchover, resulting in resource consumption. The CUSP channel status cannot be used as the only criteria to determine operating status of the UP. When the UP becomes faulty, the CUSP channel is disconnected and the failure cannot be reported to the CP. To address this issue, specify a peer UP in the same UP backup group as the local UP to monitor the network state.

This command associates Track with the network interface state of the peer UP. When the network interface goes down, Track notifies the local UP. The local UP then reports the event to the CP. Upon receiving the event, the CP instructs the faulty UP to perform a master/backup interface state switchover.

The command does not take effect if you specify a nonexistent track entry.

A peer UP and a track entry must be in one-to-one correspondence. You cannot associate a peer UP with different track entries or associate multiple peer UPs with the same track entry.

You cannot execute this command repeatedly to modify the association between the peer UP and track entry. To modify the association, execute the undo user-plane switchover track up-peer-name command to remove the association, and then execute the user-plane switchover track up-peer-name command again.

You can execute this command multiple times to associate multiple peer UPs with multiple track entries for the UP.

Examples

# Associate peer UP up2 with track entry 1 to monitor its status.

<Sysname> system-view

[Sysname] user-plane switchover track 1 up-peer-name up2

Related commands

track

17-BRAS Services Command Reference

UP backup commands