Contents

UP backup commands· 1

UP backup commands (UPs) 1

bind interface· 1

user-plane access-interface track· 2

user-plane control-tunnel-down switchover track· 3

user-plane switchover track uplink-group· 4

user-plane switchover track up-peer-name· 5

 

UP backup commands

In a CUSP network, the device can act only as a UP and must work with the CP for complete UP backup configuration. For more information about UP backup, see UP backup in the CP and UP Separation Configuration Guide.

You can configure the commands in this document on only UPs in a CUSP network. Before configuring the commands, make sure you understand their impacts on the network to avoid network failures caused by incorrect configuration.

Follow these guidelines when you use the commands in this document:

·     The commands marked with (CPs) apply only to CPs.

·     The commands marked with (UPs) apply only to UPs. Before configuring such commands, make sure you understand their impacts on the network to avoid network failures caused by incorrect configuration.

UP backup commands (UPs)

bind interface

Use bind interface to bind a VSRP instance to a UP interface.

Use undo bind interface to restore the default.

Syntax

bind interface interface-type interface-number

undo bind interface

Default

A VSRP instance is not bound to any UP interfaces.

Views

VSRP instance view

Predefined user roles

network-admin

Parameters

interface-type interface-number: Specifies an interface by its type and number.

Usage guidelines

Application scenarios

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.

Restrictions and guidelines

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

Application scenarios

This feature is applicable to scenarios where the UP monitors the user-side link status of the UP device itself through Track.

Operating mechanism

After you configure this feature, when Track on the UP detects a user-side link failure on the UP, the UP reports the faulty interface information to the CP. Upon receiving the failure information, the CP triggers 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.

Restrictions and guidelines

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

·     The service interface and track entry specified in this command must have a one-to-one correspondence. You cannot associate a service interface with multiple track entries, or associate multiple service interfaces with the same track entry.

·     You cannot execute this command to edit the association between the service interface and track entry. To do that, first execute the undo user-plane access-interface track command to remove the association, and then execute the user-plane access-interface track command.

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

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

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

Application scenarios

This feature is applicable to scenarios where the UP uses Track to monitor its network-side link state.

In the CUSP scenario, a router exists between the CP and UP, and a CUSP channel has been set up between the CP and UP.

When the UP where the master interface resides detects the CUSP channel disconnection, the UP performs a master/backup interface switchover. The CP can also detect disconnection of the CUSP channel to the UP, and notifies the UP associated with the backup interface to switch its interface to master.

If the CUSP control channel is disconnected, the master interface on the master UP automatically switches over to backup after the CUSP channel disconnection. Because the CP cannot notify the backup UP to switch to master, multiple backups exist and no master is available. As a result, services become unavailable.

Operating mechanism

After you configure this feature, when the CUSP control channel is disconnected , if the link between the UP and router is normal based on the status of the track entry, the fault occurred between CP and router. In this case, the master interface on the UP does not need to switch to the backup interface.

Restrictions and guidelines

·     This task applies only to UPs.

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

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

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

Application scenarios

This feature is applicable to scenarios where the UP uses Track to monitor its network-side link state.

Operating mechanism

After you configure this feature, when a network-side interface failure occurs, Track notifies the track entry status to the UP, which then reports the failure information to the CP. Upon receiving the failure information, the CP instructs the UP or the UP interface to perform master/backup switchover.

The UP sends the specified resource group name to the CP in addition to the failure information. The CP can identify the UP and a group of interfaces on the UP by resource group name in order to instruct the UP or UP interface to perform master/backup switchover.

Restrictions and guidelines

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

·     The resource group and track entry specified in this command must have a one-to-one correspondence. You cannot associate a resource group with multiple track entries, or associate multiple resource groups with the same track entry.

·     You cannot execute this command to edit the association between the resource group and track entry. To do that, first 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.

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

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

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 CPs).

Usage guidelines

Application scenarios

This feature is applicable to scenarios where the local UP uses Track to monitor network-side link state of another UP in the same UP backup group.

Operating mechanism

After you configure this feature, when a network-side interface failure occurs, Track on the local UP notifies the track entry status to the UP, and the local UP reports the peer UP failure information to the CP. Upon receiving the failure information, the CP instructs the interfaces on the faulty UP to perform master/backup switchover.

Restrictions and guidelines

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

·     The peer UP and track entry specified in this command must have a one-to-one correspondence. You cannot associate a peer UP with multiple track entries, or associate multiple peer UPs with the same track entry.

·     You cannot execute this command to edit the association between the peer UP and track entry. To do that, first 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.

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

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

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