absolute [ absolute-cost ]: Specifies an absolute cost in the range of 1 to 65535. The default value is 65500. If you specify this option, the standby device will advertise an absolute link cost for the specified routing protocol.

increment [ increment-cost ]: Specifies an increment cost in the range of 1 to 65535. The default value is 100. If you specify this option, the standby device will advertise the original link cost plus this increment cost for the specified routing protocol.

Usage guidelines

Application scenarios

In an RBM system, the routing protocols on the RBM member devices advertise link cost according to their respective operation mechanisms. This command allows you to enable the routing protocols to advertise link cost modified as configured. The active device still uses the original link cost advertisement method. This ensures service continuity by switching both uplink and downlink traffic to the new active device upon an active/standby switchover.

Restrictions and guidelines

In an RMB network configured with dynamic routing protocols, to ensure switchover of both uplink and downlink traffic to the new active device, configure this command with the same parameters on both RBM member devices.

In dual-active mode, both devices advertise link cost according to the operation mechanisms of the running routing protocols. When one device is faulty and becomes the standby device, it will advertise link cost modified as configured.

To enable the feature for multiple routing protocols, execute this command multiple times by specifying the protocols.

If you execute the command multiple times for a specific routing protocol, the most recent configuration takes effect.

Examples

# Enable RBM to adjust OSPF link cost on the standby device by specifying an absolute value of 6000.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] adjust-cost ospf enable absolute 6000

backup-mode

Use backup-mode to configure the hot backup mode.

Use undo backup-mode to restore the default.

Syntax

backup-mode { dual-active | mirror-mode }

undo backup-mode

Default

The hot backup mode is active/standby.

Views

RBM view

Predefined user roles

network-admin

Parameters

dual-active: Specifies the dual-active mode.

mirror-mode: Specifies the mirroring mode.

Usage guidelines

Application scenarios

The hot backup system supports the active/standby mode, mirroring mode, and dual-active mode. In active/standby mode, the active device processes all services. In mirroring mode, the interfaces on the two devices (except the management interface and RBM channel interface) use the same IP address, and only the active device processes services. In dual-active mode, both devices process services to increase the capability of the hot backup system and load share traffic.

Restrictions and guidelines

When the device automatically elects the hot backup role, you cannot configure the dual-active mode for it.

In the mirroring mode, the hot backup system synchronizes configuration of the interface from the primary device to the interface on the secondary device. When the running status of the devices switches, the administrator can only remotely log in to the current active device for management. If the active device is the secondary device, the configuration changes made by the administrator on the current device will not be synchronized to the standby device, resulting in inconsistent configuration between the primary and secondary devices. To resolve this issue, use automatic hot backup role election for the hot backup system in mirroring mode.

To avoid impact on services, do not randomly switch between the active/standby mode, mirroring mode, and dual-active mode.

Examples

# Configure the dual-active mode.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] backup-mode dual-active

configuration auto-sync enable

Use configuration auto-sync enable to enable automatic configuration synchronization.

Use undo configuration auto-sync enable to disable automatic configuration synchronization.

Syntax

configuration auto-sync enable

undo configuration auto-sync enable

Default

Automatic configuration synchronization is enabled.

Views

RBM view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

In an RBM network, enable this feature to automatically synchronize key configuration from the primary device to the secondary device. This feature prevents service interruption due to configuration loss on the peer end upon an active/standby switchover.

Restrictions and guidelines

The automatic configuration synchronization feature synchronizes existing configuration on the primary device in bulk to the secondary device. Consequent synchronization for added, deleted, or modified configuration will be performed in real time.

If the amount of configuration to be synchronized is large, bulk synchronization might take one to two hours.

Examples

# Enable automatic configuration synchronization.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] configuration auto-sync enable

configuration auto-sync enable route-static

Use configuration auto-sync enable route-static to enable static route synchronization by RBM.

Use undo configuration auto-sync enable route-static to disable static route synchronization by RBM.

Syntax

configuration auto-sync enable route-static

undo configuration auto-sync enable route-static

Default

Static route synchronization by RBM is enabled.

Views

RBM view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

Enable this feature only when virtual IP addresses are configured to direct traffic on the RBM system or when the hot backup system operates in mirroring mode. Do not enable this feature in any other RBM scenarios.

This feature enables the primary device to copy all static routes to the secondary device in automatic or manual configuration synchronization.

Restrictions and guidelines

This feature takes effect only after automatic configuration synchronization is enabled by using the configuration auto-sync enable command. If you enable automatic configuration synchronization prior to static route synchronization, the device will automatically synchronize the static routes added after static route synchronization is enabled. To synchronize the static routes configured before static route synchronization is enabled, execute the configuration manual-sync command to synchronize the configuration manually.

Examples

# Enable static route synchronization by RBM.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] configuration auto-sync enable

[Sysname-remote-backup-group] configuration auto-sync enable route-static

Related commands

configuration auto-sync enable

configuration manual-sync

Use configuration manual-sync to manually synchronize the configuration of the primary device to the secondary device.

Syntax

configuration manual-sync

Views

RBM view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

In an RBM network, in addition to automatic configuration synchronization, you can manually synchronize configuration from the primary device to the secondary device in bulk. This feature prevents service interruption due to configuration loss on the peer end upon an active/standby switchover.

Restrictions and guidelines

This command takes effect only on the primary device.

This command does not take effect when bulk configuration backup is in progress. To view the backup progress, execute the display remote-backup-group status command.

Examples

# Manually synchronize the configuration of the primary device to the secondary device.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] configuration manual-sync

Related commands

display remote-backup-group status

configuration manual-sync-check

Use configuration manual-syn-check to perform a one-off configuration consistency check.

Syntax

configuration manual-sync-check

Views

RBM view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

This command allows you to perform a one-off configuration consistency check as needed. If the system detects configuration inconsistency, it generates a log for you to manually synchronize configuration.

Restrictions and guidelines

To view the check result, execute the display remote-backup-group sync-check command.

Examples

# Perform a one-off configuration consistency check.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] configuration manual-sync-check

Related commands

configuration manual-sync

display remote-backup-group sync-check

configuration sync-check

Use configuration sync-check to enable configuration consistency check and set the configuration consistency check interval.

Use undo configuration sync-check to disable configuration consistency check.

Syntax

configuration sync-check [ interval interval | { daily | weekly { fri | mon | sat | sun | thu | tue | wed } } time ]

undo configuration sync-check

Default

Configuration consistency check is enabled, and the configuration consistency check interval is 24 hours.

Views

RBM view

Predefined user roles

network-admin

Parameters

interval interval: Specifies the configuration consistency check interval, in the range of 1 to 168 hours. The default value is 24.

daily: Performs configuration consistency check every day.

weekly: Performs configuration consistency check every week.

fri: Specifies Friday.

mon: Specifies Monday.

sat: Specifies Saturday.

sun: Specifies Sunday.

thu: Specifies Thursday.

tue: Specifies Tuesday.

wed: Specifies Wednesday.

time: Specifies the configuration consistency check time in the format of hh:mm:ss. The value range for this argument is 00:00:00 to 23:59:59.

Usage guidelines

Application scenarios

The RBM system verifies configuration consistency between the primary and secondary devices to avoid service interruption upon active/standby switchover. If a device detects configuration inconsistency, it generates a log for you to manually synchronize configuration.

Restrictions and guidelines

If you do not specify any parameters, this command enables configuration consistency check and sets the configuration consistency check interval to 24 hours.

Examples

# Enable configuration consistency check and set the configuration consistency check interval to 120 hours.

<Sysname>system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] configuration sync-check interval 120

Related commands

configuration manual-sync

configuration manual-sync-check

crc enable

Use crc enable to enable CRC for RBM bulk data backup.

Use undo crc enable to disable CRC for RBM bulk data backup.

Syntax

crc enable

undo crc enable

Default

CRC is disabled for RBM bulk data backup.

Views

RBM view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

In a hot backup system, two member devices transmit information such as operational status, critical configurations, and service entries through the RBM channel. To prevent malicious packet attacks and data tampering, users can enable CRC verification by using this feature. With this feature enabled, a member device performs CRC integrity verification on the configuration data backed up in real time by the primary device to secondary device and the session entries backed up by the active device to the standby device. The device will collect error statistics for troubleshooting purposes when abnormal packets are detected.

Restrictions and guidelines

If the CPU usage is high and RBM channel security is guaranteed, you can disable this feature to reduce the CPU usage.

Examples

# Enable CRC for RBM bulk data backup.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] crc enable

data-channel

Use data-channel to configure a data channel.

Use undo data-channel to restore the default.

Syntax

data-channel interface interface-type interface-number

undo data-channel

Default

No data channel is configured.

Views

RBM view

Predefined user roles

network-admin

Parameters

interface interface-type interface-number: Specifies an interface by its type and number to set up a data channel between the RBM member devices.

Usage guidelines

Application scenarios

RBM uses the data channel to transmit backup packets and the packets that require transparent transmission to the peer device. This prevents service interruption due to service entry loss on the standby device upon an active/standby switchover.

Restrictions and guidelines

The data channel transmits only backup packets and the packets that require transparent transmission.

Examples

# Set up a data channel using interface GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] data-channel interface gigabitethernet 1/0/1

Related commands

data-channel mode

delay-time

Use delay-time to enable traffic switchover upon failure recovery.

Use undo delay-time to disable traffic switchover upon failure recovery.

Syntax

delay-time delay-time

undo delay-time

Default

Traffic switchover upon failure recovery is disabled.

Views

RBM view

Predefined user roles

network-admin

Parameters

delay-time: Specifies the switchover delay time in the range of 1 to 1440 minutes.

Usage guidelines

Application scenarios

After an active/standby switchover in an RBM system, if the original active device recovers, traffic will not be switched back by default. Perform this task to enable traffic switchover to the original active device upon failure recovery. You can set a delay timer to ensure smooth service switchover.

Restrictions and guidelines

In dual-active mode, you must execute this command to ensure that both devices can operate after the failure is recovered.

If this timer is modified during the countdown of the switchover delay timer, the switchover will still be performed according to the old timer value. Subsequent switchovers will be performed based on the modified timer value. If traffic switchover upon failure recovery is disabled during the countdown of the switchover delay timer, no switchover will occur.

Examples

# Enable traffic switchover upon failure recovery and set the switchover delay time to two minutes.

<Sysname>system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] delay-time 2

device-role

Use device-role to configure the RBM role.

Use undo device-role to restore the default.

Syntax

device-role { auto | primary | secondary }

undo device-role

Default

The RBM role is not configured.

Views

RBM view

Predefined user roles

network-admin

Parameters

auto: Enables automatic RBM role election based on the device running status.

primary: Assigns the primary role to the device.

secondary: Assigns the secondary role to the device.

Usage guidelines

Application scenarios

The RBM system backs up important configuration from the primary device to the secondary device to prevent service interruption when an active/standby switchover occurs. The configuration on the secondary device is overwritten. The unidirectional backup mechanism avoids configuration conflicts, especially in dual-active mode, and ensures configuration consistency on the primary and secondary devices.

Hot backup roles can be configured manually or automatically elected based on device running status.

· Manual configuration—Use commands to assign the RBM roles. The RBM role of a device is fixed, unless you change the role from the CLI. This method is applicable in active/standby or dual-active mode for devices with independent management interfaces. It does not apply to mirroring mode.

· Automatic election—Hot backup roles are elected and switch over with the device running status. The standby device is the secondary device, and the active device is the primary device. This method is applicable for devices with service interfaces as management interface in active/standby or mirroring mode. It does not apply to dual-active mode.

Restrictions and guidelines

Configure one member device as the primary device and the other as the secondary device in the RBM system. To use automatic RBM role election, set the role to auto for both RBM member devices.

As a best practice, configure service modules only on the primary device, not on the secondary device.

In the active/standby or dual-active mode, the device roles are identified as follows:

· Primary device—The system adds the RBM_P prefix before the view prompt in the command line, for example, RBM_P<Sysname>.

· Secondary device—The system adds the RBM_S prefix before the view prompt in the command line, for example, RBM_S<Sysname>.

In the mirroring mode, the device roles are identified as follows:

· Primary device—The system adds the RBM_MIRROR_P prefix before the view prompt in the command line, for example, RBM_MIRROR_P<Sysname>.

· Secondary device—The system adds the RBM_MIRROR_S prefix before the view prompt in the command line, for example, RBM_MIRROR_S<Sysname>.

After you assign RBM roles to the RBM member devices, both devices add the RBM_P prefix to their view prompts. The devices display view prompt prefixes according to their RBM roles after they set up the control channel.

If RBM member devices use service interfaces as the management interfaces and running status of the devices switches, the administrator can only remotely log in to the current active device for management. If the active device is the secondary device, the configuration changes made by the administrator on the current device will not be synchronized to the standby device, resulting in inconsistent configuration between the primary and secondary devices. To resolve this issue, use automatic RBM role election.

Examples

# Assign the primary role to the device.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] device-role primary

RBM_P[Sysname-remote-backup-group]

display mac-address virtual

Use display mac-address virtual to display virtual MAC addresses.

Syntax

display mac-address virtual [ mac-address | interface interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

mac-address: Specifies a MAC address in H-H-H format. The first eight hexadecimal digits of the MAC address must be 40fe-9555. You can omit the consecutive zeros at the beginning of each segment. For example, you can enter 40fe-9555-1 for 40fe-9555-0001.

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

Usage guidelines

If you do not specify any parameters, this command displays all virtual MAC addresses.

Examples

# Display all virtual MAC addresses.

<Sysname> display mac-address virtual

MAC address Port

40fe-9555-0101 GigabitEthernet1/0/1

40fe-9555-0002 GigabitEthernet1/0/2

Table 1 Command output

Field	Description
MAC address	Virtual MAC address.
Port	Name of the interface that uses the virtual MAC address. If the interface name contains the at sign (@), the interface is assigned to a non-default vSystem, and the number after @ is the vSystem ID.

Related commands

mac-address virtual

display mad

Use display mad to display MAD configuration.

Syntax

display mad [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Parameters

verbose: Displays detailed MAD configuration. If you do not specify this keyword, the command displays brief MAD configuration.

Examples

# Display brief MAD configuration.

<Sysname> display mad

MAD ARP disabled.

MAD ND disabled.

# Display detailed MAD configuration

<Sysname> display mad verbose

Multi-active recovery state: No

MAD ARP disabled.

MAD ND disabled.

Table 2 Command output

Field

Description

Multi-active recovery state

Whether RBM is in Recovery state:

· Yes—RBM is in Recovery state. When MAD detects that a hot backup system has split, it allows one member device to forward traffic. All the other member devices are set to the Recovery state.

· No—RBM is not in Recovery state.

‌

display remote-backup-group status

Use display remote-backup-group status to display RBM status information.

Syntax

display remote-backup-group status

Views

Any view

Predefined user roles

network-admin

network-operator

context-admin

context-operator

Examples

# Display RBM status information on the default context.

<Sysname> display remote-backup-group status

Local remote backup group information:

Backup mode: Dual-active

Device management role: Primary

Device running management role: Primary

Device running status: Active

Local total priority: 10000

Switchover threshold for priority-based election: 1

Priority-based election status: Enabled

Data channel interface: GigabitEthernet1/0/1

Data channel mode: Layer3

Local IP: 1.1.1.1

Remote IP: 1.1.1.2 Destination port: 1028

Control channel status: Connected

Context control channel status : Connected

Keepalive interval: 1s

Keepalive count: 10

Configuration consistency check interval: 24 hour

Configuration consistency check result: Consistent

Configuration backup status: Batch backup (Do not operate

the device at will, such as board insertion and removal.)

Static route backup status: Enabled

Running-data auto sync status: Enabled

Session backup status: Hot backup enabled

NSR stutas: Disable

Mirroring status: Disabled

Delay-time: 4 min

Remaining switchover delay time: 3 minutes, 32 seconds

Uptime since last switchover: 0 days, 0 hours, 11 minutes

Peer remote backup group information:

Backup mode: Dual-active

Device management role: Secondary

Device running status: Standby

Peer total priority: 10000

Switchover threshold for priority-based election: 1

Priority-based election status: Enabled

Data channel interface: GigabitEthernet1/0/1

Data channel mode: Layer3

Local IP: 1.1.1.2

Remote IP: 1.1.1.1 Destination port: 1028

Control channel status: Connected

Context control channel status: Connected

Keepalive interval: 1s

Keepalive count: 10

Configuration consistency check interval: 24 hour

Configuration consistency check result: Consistent

Configuration backup status: Batch backup (Do not operate

the device at will, such as board insertion and removal.)

Static route backup status: Enabled

Running-data auto sync status: Enabled

Session backup status: Hot backup enabled

NSR stutas: Disable

Mirroring status: Disabled

Delay-time: 4 min

Remaining switchover delay time: 3 minutes, 32 seconds

Switchover records:

Time Status change Cause

2021-06-22 13:33:33 Initial to Standby Local device rebooted

2021-06-22 14:34:34 Initial to Active Peer device rebooted

# Display RBM status information on non-default contexts.

<Sysname> display remote-backup-group status

Remote backup group information:

Backup mode: Dual-active

Device management role: Auto

Device running management role: Primary

Local total priority: 10000

Priority-based election status: Enabled

Device running status: Active

Control channel status: Connected

Configuration backup status: Batch backup (Do not operate

the device at will, such as board insertion and removal.)

Table 3 Command output

Field	Description
Backup mode	Hot backup mode: · Dual-active. · Active/standby. · Mirror.
Device management role	RBM role of the device: · Primary. · Secondary. · Auto—Automatic RBM role election is enabled.
Device running management role	Effective RBM role. · Primary (The two member devices have the same role. Please assign different roles to them.). · Secondary (The two member devices have the same role. Please assign different roles to them.). · Primary—Automatic RBM role election is enabled on both RBM member devices, and the local device is the primary device. · Secondary—Automatic RBM role election is enabled on both RBM member devices, and the local device is the secondary device. · Primary(Batch backup in progress)—The device is automatically elected as the primary device, and the device is bulk synchronizing configuration. Do not make any changes to the software or hardware of the device. · Primary (Only one of the two member devices has the auto role. Please assign the auto role to both of them.). · Secondary (Only one of the two member devices has the auto role. Please assign the auto role to both of them).
Device running status	Running status of the device. · Active. · Standby. · Initial—The local IP address, peer IP address, or RBM role is not configured.
Local total priority	Overall priority of the local device. This field is not displayed if RBM priority-based election is not enabled.
Peer total priority	Overall priority of the peer device. This field is not displayed if RBM priority-based election is not enabled.
Switchover threshold for priority-based election	RBM active/standby switchover threshold. This field is not displayed if RBM priority-based election is not enabled.
Priority-based election status	Status of the RBM priority-based election feature. Options include: · Enabled—Indicates that RBM priority-based election is enabled. · Enabled (Ineffective)—Indicates that RBM priority-based election is enabled but has not taken effect. · Disabled—Indicates that RBM priority-based election is disabled.
Data channel interface	Interface used to set up the data channel.
Data channel mode	This field is not supported in the current software version. Data channel mode: Layer 2 or Layer 3.
Local IP	Local IP address used by control channel packets. This field is not displayed if the parameter is not configured.
Remote IP	Peer IP address used by control channel packets. This field is not displayed if the parameter is not configured.
Local IPv6	Local IPv6 address used by control channel packets. This field is not displayed if the parameter is not configured.
Remote IPv6	Peer IPv6 address used by control channel packets. This field is not displayed if the parameter is not configured.
Destination port	Peer port number used by control channel packets.
Control channel status	Control channel status: · Connected. · Disconnected.
Configure channel status	Status of the configuration channel for a non-default context: · Connected. · Disconnected. This field is available only for non-default contexts. A non-default context cannot synchronize configuration if this channel is disconnected.
Context control channel status	Link state of the context. This field is not displayed if no context is configured. Options include: · Connected—Indicates that the link has been successfully established for the context. · Disconnected—Indicates that the link is not established for the context.
Keepalive interval	Interval for sending keepalive packets.
Keepalive count	Maximum number of keepalive attempts.
Configuration consistency check time	Time when configuration consistency check is performed. This field is displayed only after configuration consistency check is enabled and the configuration consistency check interval is set. For example: · 08:15:00 means the check is performed at 08:15:00 every day. · 08:15:00 Monday means the check is performed at 08:15:00 every Monday.
Configuration consistency check interval	Configuration consistency check interval in hours. This field is displayed only after configuration consistency check is enabled and the configuration consistency check interval is set.
Configuration consistency check result	Result of the configuration consistency check: · Consistent. · Inconsistent. · Checking. · Not Performed.
Configuration backup status	Status of configuration backup: · Batch backup in progress (Do not operate the device at will, such as board insertion and removal.). · Auto sync enabled. · Auto sync disabled.
Static route backup status	Status of static route synchronization: · Enabled. · Disabled.
Running-data auto sync status	Status of running data auto sync: · Enabled. · Disabled.
Session backup status	Status of session entry backup: · Batch backup in progress. · Hot backup enabled. · Hot backup disabled.
NSR status	‌ NSR status: · Enabled(Location of the preferred standby MPU: Invalid)—NSR is enabled but ineffective, because only one MPU is in place. · Enabled(Location of the preferred standby MPU: CPU 0 on slot 1 in chassis 1)—NSR is enabled, and the location of the preferred standby MPU is displayed. · Disabled.
Mirroring status	Current status of the mirroring mode: · Disabled—The mirroring mode is disabled. · Config unsynced—The mirroring mode is enabled, and bulk synchronization is not performed for configuration information. · Synced—The mirroring mode is enabled, and bulk synchronization for configuration information is completed. · Disconnected—The channel is disconnected. · Running—The mirroring mode is being enabled. · Disabling—The mirroring mode is being disabled.
Delay-time	Delay time for traffic switchover back to the original active device in minutes. This field is not displayed and the traffic switchover feature is disabled for the RBM system if the delay time is not configured.
Remaining switchover delay time	Remaining delay time for traffic switchover back to the original active device in minutes. This field is not displayed if traffic switchover is disabled.
Uptime since last switchover	Runtime of the device as the current role, which indicates the duration from the most recent device state change to the present.
Switchover records	Primary/secondary switchover information for the device.
Time	Time when the primary/secondary role of the device is switched.
Status change	Role switchover of the device. Options include: · Initial to Active. · Initial to Standby. · Active to Initial. · Standby to Initial. · Active to Standby. · Standby to Active. · Active to Active. · Standby to Standby.
Cause	Cause for the primary/secondary role switchover of the device. Options include: · Configuration batch backup finished. · Session batch backup finished. · Local RBM process restarted. · Peer RBM process restarted. · The local device joins the RBM hot backup system. · The peer device joins the RBM hot backup system. · The local device leaves the remote backup group. · The peer device leaves the remote backup group. · Interface status changed—A change in interface status leads to a change in link status. · Health status changed—The health status of the switching fabric module changed. · Switchover request—The switchover request command is executed to perform an active/standby switchover. · Switchover active—The switchover active command is executed to perform an active/standby switchover. · Switchover standby—The switchover standby command is executed to perform an active/standby switchover. · Switchover reset—The switchover reset command is executed to perform an active/standby switchover. · SecBlade count changed—The number of security modules on the device changed. · Keepalive link established—The keepalive link is established in the control channel. · Keepalive link disconnected—The keepalive link is disconnected in the control channel. · HA configuration changed. · Failed to establish RBM channel—The RBM channel failed to be established after device startup or RBM process startup. · MAD detection failed. · MAD detected a conflict and disabled the peer device, and the local device became active. · MAD detected a conflict and disabled the local device. · MAD restore event—The MAD event is cleared, which recovers the disabled device to normal. · Track entries changed. · Track VRRP changed. · Track VLANs changed. · Track interfaces changed. · Context status changed—The status of the non-default context changes. For example, the non-default context is disabled or enabled. · NSR recover—NSR recovered the RBM channel to normal successfully. · Standby-to-active MPU switchover. · Delay timer expired for traffic switchover upon failure recovery after the local device reboots. · Delay timer expired for traffic switchover upon failure recovery after the peer device reboots. · Delay timer expired for traffic switchover upon failure recovery after the local configuration change. · Delay timer expired for traffic switchover upon failure recovery after the peer configuration change.

‌

display remote-backup-group sync-check

Use display remote-backup-group sync-check to display the configuration consistency check result for RBM.

Syntax

display remote-backup-group sync-check

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

Application scenarios

Use this command when the RBM member devices have inconsistent configuration.

Restrictions and guidelines

You can view the inconsistent configuration only after the configuration consistency check is finished.

The command displays detailed inconsistency information for only the service features supported by RBM. For a feature not supported by RBM, the command displays only the interface where configuration inconsistency exists.

Examples

# Display the configuration consistency check result for RBM. (The configuration consistency check has not been performed.)

<Sysname> display remote-backup-group sync-check

No configuration consistency checks have been performed.

# Display the configuration consistency check result for RBM. (No inconsistent configuration exists.)

<Sysname> display remote-backup-group sync-check

No inconsistent configuration exists.

# Display the configuration consistency check result for RBM. (Inconsistent configuration exists.)

<Sysname> display remote-backup-group sync-check

Inconsistent configuration exists.

Configuration on secondary device:

security-policy ip

rule 0 name abc

source-zone trust

destination-zone untrust

Configuration on primary device:

security-policy ip

rule 0 name abc

source-zone dmz

destination-zone trust

Context 2

Configuration on secondary device:

security-policy ip

rule 0 name 10

Configuration on primary device:

security-policy ip

Context 3

Configuration on secondary device:

object-group ipv6 address d

security-policy ipv6

rule 0 name d

source-ip d

Configuration on primary device:

security-policy ipv6

rule 0 name d

Related commands

configuration sync-check

configuration manual-sync-check

display remote-backup-group trans-data

Use display remote-backup-group trans-data to display statistics of the mirroring-mode-specific data transmitted through the data channel.

Syntax

display remote-backup-group trans-data

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display statistics of the mirroring-mode-specific data transmitted through the data channel.

<Sysname> display remote-backup-group trans-data

Context: ctx1

Service: NAT

Total packets received by local RBM from local NAT: 90

Total bytes received by local RBM from local NAT: 2390283

Total packets received by local RBM from peer RBM: 90

Total packets sent by local RBM to peer RBM: 100

Total bytes received by local RBM from peer RBM: 2390283

Total bytes sent by local RBM to peer RBM: 8912398

Total RBMtoRBM channel block: 39

Total RBM channel connection failures: 7782

Total packets sent by peer RBM to peer NAT: 100

Total bytes sent by peer RBM to peer NAT: 8912398

context: ctx2

Service: NAT

Total packets received by local RBM from local NAT: 90

Total bytes received by local RBM from local NAT: 2390283

Total packets received by local RBM from peer RBM: 90

Total packets sent by local RBM to peer RBM: 100

Total bytes received by local RBM from peer RBM: 2390283

Total bytes sent by local RBM to peer RBM: 8912398

Total RBMtoRBM channel block: 39

Total RBM channel connection failures: 7782

Total packets sent by peer RBM to peer NAT: 100

Total bytes sent by peer RBM to peer NAT: 8912398

Related commands

reset remote-backup-group trans-data

hot-backup enable

Use hot-backup enable to enable RBM service entry hot backup.

Use undo hot-backup enable to disable RBM service entry hot backup.

Syntax

hot-backup enable

undo hot-backup enable

Default

RBM service entry hot backup is enabled.

Views

RBM view

Predefined user roles

network-admin

Usage guidelin

This command enables the active device in the RBM system to back up service entries to the standby device in real time. This prevents service interruption when an active/standby switchover occurs.

Examples

# Enable RBM service entry hot backup.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] hot-backup enable

hot-backup protocol enable

Use hot-backup protocol enable to enable hot backup for the session entries of RBM application layer protocols.

Use undo hot-backup protocol enable to disable hot backup for the session entries of RBM application layer protocols.

Syntax

hot-backup protocol { dns | http } * enable

undo hot-backup protocol { dns | http } * enable

Default

The RBM system performs hot backup for the session entries of application layer protocols.

Views

RBM view

Predefined user roles

network-admin

Parameters

dns: Specifies DNS.

http: Specifies HTTP.

Usage guidelines

Application scenarios

Enable HTTP and DNS backup if asymmetric-path traffic traverses the RBM system. HTTP and DNS backup ensures that a flow and its return traffic are processed correctly on RBM members.

If hot backup active/standby or mirroring mode is used or only symmetric-path traffic traverses the RBM system, disabling HTTP and DNS backup can improve performance of RBM members at the expense of delayed data synchronization. When you disable HTTP and DNS backup, make sure you are fully aware of the impact on the network. A device removes a DNS or HTTP connection if packet exchange is inactive. When a switchover interrupts a connection, the DNS or HTTP client re-initiates the connection immediately, which has little impact on user services.

Restrictions and guidelines

For this command to take effect, first execute the hot-backup enable command.

The RBM system backs up the sessions created for other application protocols as long as service entry backup is enabled.

Examples

# Disable hot backup for the session entries of RBM application layer protocols.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] undo hot-backup protocol dns enable

Related commands

hot-backup enable

ip address

Use ip address to assign a floating IP address to an interface.

Use undo ip address to remove an IP address from an interface.

Syntax

ip address { ip-address { mask-length | mask } | ip-address/mask-length } [ sub ] float

undo ip address [ ip-address { mask-length | mask } [ sub ] ]

Default

No IP address is assigned to an interface.

Views

Interface view

Predefined user roles

network-admin

context-admin

Parameters

ip-address: Specifies an IP address in dotted decimal notation.

mask-length: Specifies the subnet mask length in the range of 1 to 31. For a loopback interface, the value range is 1 to 32.

mask: Specifies the subnet mask in dotted decimal notation.

sub: Assigns a secondary IP address to the interface.

float: Assigns a floating IP address to the interface. This keyword is applicable only to RBM-based hot backup.

Usage guidelines

Application scenarios

Use the command to assign a primary or secondary IP address to an interface. An interface typically has only one primary IP address. If the interface connects to multiple subnets, configure primary and secondary IP addresses on the interface so the subnets can communicate with each other through the interface.

You can assign a floating IP address to an interface on an RBM-based hot backup system. The floating attribute does not take effect in other scenarios.

In RBM-based hot backup, floating IP addresses can simplify hot backup configuration. On the active device, assign floating IP addresses to the interfaces attached to downstream tenants, and the addresses will be automatically synchronized to the standby device. With floating IP addresses, you do not need to configure VRRP virtual addresses on the service interfaces of the hot backup member devices.

Restrictions and guidelines

An interface can have only one primary IP address. If you execute this command multiple times to specify different primary IP addresses, the most recent configuration takes effect.

You cannot assign secondary IP addresses to an interface that obtains an IP address through BOOTP, DHCP, PPP address negotiation, or IP unnumbered.

If you do not specify any parameters, the undo ip address command removes all IP addresses from the interface. The undo ip address ip-address { mask | mask-length } command removes the primary IP address. The undo ip address ip-address { mask | mask-length } sub command removes a secondary IP address.

The primary and secondary IP addresses assigned to the interface can be located on the same network segment. Different interfaces on your device must reside on different network segments.

Configure floating IP addresses only on the active device in a hot backup system operating in active/standby mode. Floating IP addresses are not available in mirroring or dual-active mode. You cannot configure, modify, or delete floating IP addresses on the standby device. For more information about VRRP, see VRRP configuration in High Availability Configuration Guide.

To remove the floating attribute for an IP address, execute the ip address command to assign the IP address again without specifying the float keyword.

Examples

# Assign GigabitEthernet 1/0/1 a primary IP address 129.102.0.1 and a secondary IP address 202.38.160.1, with both subnet masks being 255.255.255.0. ‌

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0/1

[Sysname-GigabitEthernet1/0/1] ip address 129.102.0.1 255.255.255.0

[Sysname-GigabitEthernet1/0/1] ip address 202.38.160.1 255.255.255.0 sub

Related commands

display ip address float (Layer 3—IP Services Command Reference)

ipv6 address

mac-address virtual

ip send-packet source-mac prefer virtual-mac

Use ip send-packet source-mac prefer virtual-mac to enable an interface to preferentially use the virtual MAC as the source MAC when sending packets.

Use undo ip send-packet source-mac prefer virtual-mac to disable an interface from preferentially using the virtual MAC as the source MAC when sending packets.

Syntax

ip send-packet source-mac prefer virtual-mac

undo ip send-packet source-mac prefer virtual-mac

Default

An interface is disabled from preferentially using the virtual MAC address as the source MAC address when sending packets.

Views

System view

Predefined user roles

network-admin

network-operator

Usage guidelines

Application scenarios

In specific RBM scenarios (including RBM collaboration with VRRP and RBM collaboration with virtual addresses), the service interfaces of RBM member devices use virtual MAC addresses to send ARP replies. However, packets processed by the active device are encapsulated with the real interface MAC addresses, which might result in service issues. For example, when the upstream and downstream devices of RBM member devices use strict uRPF check, packets might be dropped to cause service interruption.

To avoid this issue, enable the RBM primary device to preferentially use virtual MAC addresses as the source MAC addresses of packets. Then, packets from the active device can be encapsulated with virtual MAC addresses.

Restrictions and guidelines

In the scenario of RBM collaboration with virtual addresses, besides using this feature, you can also use the undo vrrp virtual-mac enable command to configure ARP packets to use the real MAC addresses to avoid service interruption. The two features are mutually exclusive.

This feature supports configuration synchronization. Once you enable the automatic configuration backup feature, you must enable this feature only on the RBM primary device. When you configure multiple VRRP groups to collaborate with RBM on an interface, this feature is not supported.

Use this feature only in scenarios of RBM collaboration with VRRP and RBM collaboration with virtual addresses. Do not use this feature in other scenarios.

With this feature enabled, the source MAC address used by the RBM member device for sending packets is a virtual MAC address, which remains unchanged during switchover. This might cause the outgoing interface in the MAC address entry for this virtual MAC address on upstream and downstream devices to switch repeatedly during active/standby switchover, leading to transient traffic interruption.

Examples

# Enable interfaces to preferentially use the virtual MAC addresses as the source MAC addresses when sending packets.

<Sysname> system-view

[Sysname] ip send-packet source-mac prefer virtual-mac

Related commands

vrrp virtual-mac enable (High Availability Command Reference)

ipv6 address

Use ipv6 address to assign an IPv6 global unicast address to an interface.

Use undo ipv6 address to delete an IPv6 global unicast address from an interface.

Syntax

ipv6 address { ipv6-address prefix-length | ipv6-address/prefix-length } float

undo ipv6 address [ ipv6-address prefix-length | ipv6-address/prefix-length ]

Default

No IPv6 global unicast address is assigned to an interface.

Views

Interface view

Predefined user roles

network-admin

context-admin

Parameters

ipv6-address: Specifies an IPv6 address.

prefix-length: Specifies a prefix length in the range of 1 to 128.

float: Assigns a floating IPv6 address to the interface. This keyword is applicable only to RBM-based hot backup.

Usage guidelines

Application scenarios

Like public IPv4 addresses, IPv6 global unicast addresses are assigned to ISPs. This type of address allows for prefix aggregation to reduce the number of global routing entries.

You can assign a floating IPv6 address to an interface on an RBM-based hot backup system. The floating attribute does not take effect in other scenarios. In RBM-based hot backup, floating IPv6 addresses can simplify hot backup configuration. On the active device, assign floating IPv6 addresses to the interfaces attached to downstream tenants, and the addresses will be automatically synchronized to the standby device. With floating IPv6 addresses, you do not need to configure VRRP virtual addresses on the service interfaces of the hot backup member devices.

Restrictions and guidelines

If you do not specify any parameters, the undo ipv6 address command deletes all IPv6 addresses of an interface.

Configure floating IPv6 addresses only on the active device in a hot backup system operating in active/standby mode. Floating IPv6 addresses are not available in mirroring or dual-active mode. You cannot configure, modify, or delete floating IPv6 addresses on the standby device. For more information about VRRP, see VRRP configuration in High Availability Configuration Guide.

To remove the floating attribute for an IPv6 address, execute the ipv6 address command to assign the IPv6 address again without specifying the float keyword.

Examples

# Set the IPv6 global unicast address of GigabitEthernet 1/0/1 to 2001::1 with prefix length 64. ‌

Method 1:

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0/1

[Sysname-GigabitEthernet1/0/1] ipv6 address 2001::1/64

Method 2:

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0/1

[Sysname-GigabitEthernet1/0/1] ipv6 address 2001::1 64

Related commands

display ipv6 address float (Layer 3—IP Services Command Reference)

ip address

mac-address virtual

keepalive count

Use keepalive count to set the maximum number of keepalive attempts.

Use undo keepalive count to restore the default.

Syntax

keepalive count counts

undo keepalive count

Default

The maximum number of keepalive attempts is 10.

Views

RBM view

Predefined user roles

network-admin

Parameters

times: Sets the maximum number of keepalive attempts, in the range of 1 to 255.

Usage guidelines

If the value for the maximum number of keepalive attempts is too small, network latency will cause incorrect switchovers. If this issue occurs, increase the value of this parameter.

The device periodically sends keepalive packets to the RBM peer over the control channel. If the device has not received any responses from the peer when the maximum number of keepalive attempts is reached, the control channel is disconnected.

Examples

# Set the maximum number of keepalive attempts to 6.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] keepalive count 6

Related commands

keepalive interval

Use keepalive interval to set the interval for sending keepalive packets.

Use undo keepalive interval to restore the default.

Syntax

keepalive interval interval

undo keepalive interval

Default

The device sends keepalive packets at one-second intervals.

Views

RBM view

Predefined user roles

network-admin

Parameters

interval: Sets the interval for sending keepalive packets in seconds, in the range of 1 to 60.

Usage guidelines

The device periodically sends keepalive packets to the peer over the control channel. If the device has not received any responses from the peer when the maximum number of keepalive attempts is reached, the control channel is disconnected.

Examples

# Set the interval for sending keepalive packets to 2 seconds.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] keepalive interval 2

Related commands

keepalive count

local-ip

Use local-ip to configure the local IPv4 address for setting up the control channel.

Use undo local-ip to restore the default.

Syntax

local-ip ipv4-address

undo local-ip

Default

The local IPv4 address is not configured for setting up the control channel.

Views

RBM view

Predefined user roles

network-admin

Parameters

ipv4-address: Specifies the local IPv4 address for setting up the control channel. The IP address cannot be an all-zero, loopback, or multicast address.

Usage guidelines

Application scenarios

An RBM control channel transmits RBM heartbeat packets and status packets, configuration consistency check packets, and packets used for configuration synchronization, and uses these packets to maintain RBM status and synchronize configuration information.

The hot backup system compares the specified local and peer IP address to determine the device role for setting up the control channel. The device with higher IP address acts as the server to listen for TCP connection requests, and the other device acts as the client to initiate the TCP connection.

Restrictions and guidelines

You can configure a local IPv4 address or a local IPv6 address, but not both.

Examples

# Configure the local IPv4 address as 1.1.1.2 for setting up the control channel.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] local-ip 1.1.1.2

Related commands

local-ipv6

remote-ip

local-ipv6

Use local-ipv6 to configure the local IPv6 address for setting up the control channel.

Use undo local-ipv6 to restore the default.

Syntax

local-ipv6 ipv6-address

undo local-ipv6

Default

The local IPv6 address is not configured for setting up the control channel.

Views

RBM view

Predefined user roles

network-admin

Parameters

ipv6-address: Specifies the local IPv6 address for setting up the control channel. The IP address cannot be an all-zero address, loopback address, multicast address, or IPv6 address with an embedded IPv4 address.

Usage guidelines

Application scenarios

The hot backup system compares the specified local and peer IPv6 address to determine the device role for setting up the control channel. The device with higher IPv6 address acts as the server to listen for TCP connection requests, and the other device acts as the client to initiate the TCP connection.

Restrictions and guidelines

You can configure a local IPv4 address or a local IPv6 address, but not both.

Examples

# Configure the local IPv6 address as 2019::1 for setting up the control channel.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] local-ipv6 2019::1

Related commands

local-ip

remote-ipv6

mac-address virtual

Use mac-address virtual to modify the virtual MAC address of an interface.

Use undo mac-address virtual to restore the default.

Syntax

mac-address virtual mac-address

undo mac-address virtual

Default

The virtual MAC address of an interface is automatically assigned by the device, and the primary and secondary devices assign the same virtual MAC address to the interfaces with the same ID.

Views

Layer 3 Ethernet interface view

Layer 3 aggregate interface view

VLAN interface view

Management Ethernet interface view

Reth interface view

Predefined user roles

network-admin

context-admin

Parameters

Usage guidelines

Application scenarios

On an RBM system, the administrator can configure a floating IP address and a virtual MAC address on an interface of the primary device for other devices to communicate with the RBM member devices through the floating IP address and the virtual MAC address. The source MAC address of the service packets sent by the primary and secondary devices is the virtual MAC address, and the source IP address is the floating IP address. Other devices do not know the real IP addresses or MAC addresses of the primary and secondary devices, which facilitates RBM management and security deployment.

Typically, the virtual MAC address of an interface is automatically assigned by the device. If multiple interfaces of a device are assigned the same virtual MAC address, use this command to manually modify the virtual MAC addresses of involved interfaces to resolve the conflict.

Restrictions and guidelines

If you change virtual MAC addresses on the primary device, the primary device will synchronize the modifications to the virtual MAC address to the secondary device. This mechanism ensures consistent virtual MAC addresses between the primary and secondary devices.

Virtual MAC addresses are supported only in active/standby mode, not in mirroring or dual-active mode.

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

If an interface is assigned to a non-default context in exclusive mode, a user can log in to the non-default context and modify the interface's virtual MAC address in interface view.

If an interface is assigned to a non-default context in shared mode, a user cannot modify the interface's virtual MAC address in interface view. The virtual MAC address of the interface shared with the non-default context is automatically generated by the system.

If an interface is assigned to a non-default vSystem, the virtual MAC address of the interface used within the non-default vSystem is automatically generated by the system. You cannot modify the virtual MAC address of the interface.

Examples

# Change the virtual MAC address to 40fe-9555-1234 on GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0/1

[Sysname-GigabitEthernet1/0/1]mac-address virtual 40fe-9555-1234

Related commands

display mac-address virtual

ip address

ipv6 address

mad arp enable

Use mad arp enable to enable ARP MAD.

Use undo mad arp enable to disable ARP MAD.

Syntax

mad arp enable

undo mad arp enable

The following compatibility matrix shows the support of hardware platforms for this command:

Series	Models	Command compatibility
M9000 series	M9006, M9010, M9014, M9016-V	Yes
M9000-S series	M9008-S, M9008-S-V	Yes
M9000-AK series	M9000-AK001	Yes
M9000-AI-E series	M9000-AI-E4, M9000-AI-E8, M9000-AI-E16	Yes
M9000-X series	M9000-X06, M9000-X06-B, M9000-X06-B-G, M9000-X06-G, M9000-X10	Yes
M9000-AI-X series	M9000-AI-X06, M9000-AI-X10	Yes
M9000-CN series	M9000-CN04	No

‌

The following compatibility matrix shows the support of hardware platforms for this command:

Models	Command compatibility
L5000-AD930	No
L5000-AD920, M9000-AD6	Yes
L5000-AD920-G	Yes

‌

Default

ARP MAD is disabled.

Views

VLAN interface view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

On a RBM system, if the RBM channel is disconnected, RBM will fail. Both member devices become active and process services, but they are no longer in RBM mode, impacting subsequent asymmetric traffic.

With MAD configured, when the RBM channel is disconnected, the member devices will use MAD to maintain the RBM status. However, the member devices will be unable to synchronize configuration and service entries, and transparently forward traffic. If the RBM mode is active/standby, the mode remains unchanged. If the RBM mode is dual-active or mirroring, the mode will switch to active/standby.

Restrictions and guidelines

Do not enable ARP MAD on VLAN-interface 1. VLAN 1 cannot be used for MAD.

If you execute the mad arp enable command, you must enter a domain ID. The domain ID does not affect the MAD feature. To use the current domain ID, press Enter.

The domain ID is a global setting. You can use either the mad arp enable or mad nd enable command to edit the global domain ID on an hot backup member device. If you configure the global domain ID multiple times, the most recent configuration takes effect.

Examples

# Enable ARP MAD on VLAN-interface 3.

<Sysname> system-view

[Sysname] interface vlan-interface 3

[Sysname-Vlan-interface3] mad arp enable

You need to assign a domain ID (range: 0-4294967295)

[Current domain is: 0]: 1

The assigned domain ID is: 1

Related commands

mad nd enable

Use mad nd enable to enable ND MAD.

Use undo mad nd enable to disable ND MAD.

Syntax

mad nd enable

undo mad nd enable

The following compatibility matrix shows the support of hardware platforms for this command:

Series	Models	Command compatibility
M9000 series	M9006, M9010, M9014, M9016-V	Yes
M9000-S series	M9008-S, M9008-S-V	Yes
M9000-AK series	M9000-AK001	Yes
M9000-AI-E series	M9000-AI-E4, M9000-AI-E8, M9000-AI-E16	Yes
M9000-X series	M9000-X06, M9000-X06-B, M9000-X06-B-G, M9000-X06-G, M9000-X10	Yes
M9000-AI-X series	M9000-AI-X06, M9000-AI-X10	Yes
M9000-CN series	M9000-CN04	No

‌

The following compatibility matrix shows the support of hardware platforms for this command:

Models	Command compatibility
L5000-AD930	No
L5000-AD920, M9000-AD6	Yes
L5000-AD920-G	Yes

‌

Default

ND MAD is disabled.

Views

VLAN interface view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

Restrictions and guidelines

Do not enable ND MAD on VLAN-interface 1. VLAN 1 cannot be used for MAD.

If you execute the mad nd enable command, you must enter a domain ID. The domain ID does not affect the MAD feature. To use the current domain ID, press Enter.

Examples

# Enable ND MAD on VLAN-interface 3.

<Sysname> system-view

[Sysname] interface vlan-interface 3

[Sysname-Vlan-interface3] mad nd enable

You need to assign a domain ID (range: 0-4294967295)

[Current domain is: 0]: 1

The assigned domain ID is: 1

Related commands

mad arp enable

mirror mgt-interface

Use mirror mgt-interface to configure the management interface for the mirroring mode.

Use undo mirror mgt-interface to restore the default.

Syntax

mirror mgt-interface interface-type interface-number

Views

RBM view

Default

The management interface for the mirroring mode is not configured.

Predefined user roles

network-admin

Parameters

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

Usage guidelines

Application scenarios

In RBM mirroring mode, interface configurations on the primary device (except the management interface and RBM channel interface) are synchronized to the secondary device. Interfaces connected to the network management device and log host have use the same IP addresses on both devices. Only the primary device can establish connections with the network management device and log host. The secondary device cannot establish the connections. To avoid this issue, you can configure the mirroring mode management interface, whose configurations will not be synchronized.

Restrictions and guidelines

You can configure the management interface for the mirroring mode only in RBM mirroring mode. If the mirroring mode is disabled for the device, the management interface for the mirroring mode restores to the default setting.

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

Examples

Configure the management interface for the mirroring mode as GigabitEthernet 1/0/1.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] backup-mode mirror-mode

[Sysname-remote-backup-group] mirror mgt-interface gigabitethernet 1/0/1

nsr enable

Use nsr enable to enable RBM non-stop-routing (NSR).

Use undo nsr enable to disable RBM NSR.

Syntax

nsr enable

undo nsr enable

The following compatibility matrix shows the support of hardware platforms for this command:

Series	Models	Command compatibility
M9000 series	M9006, M9010, M9014, M9016-V	Yes
M9000-S series	M9008-S, M9008-S-V	Yes
M9000-AK series	M9000-AK001	Yes
M9000-AI-E series	M9000-AI-E4, M9000-AI-E8, M9000-AI-E16	Yes
M9000-X series	M9000-X06, M9000-X06-B, M9000-X06-B-G, M9000-X06-G, M9000-X10	Yes
M9000-AI-X series	M9000-AI-X06, M9000-AI-X10	Yes
M9000-CN series	M9000-CN04	No

‌

Default

RBM NSR is enabled.

Views

RBM view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

On a hot standby system, if the active MPU of an hot backup member device fails, the standby MPU will detect the active MPU failure and become the new active MPU. As the original MPU process exits, the RBM channel will disconnect, and the new MPU needs to re-establish the channel. When RBM NSR is enabled, the active MPU will back up the established channel information to the standby MPU. In the event of an active MPU failure, the standby MPU will use the backed-up channel information to set up the RBM channel, ensuring a smooth transition to the active MPU and avoiding RBM channel disconnection.

Restrictions and guidelines

If the standby MPU fails after RBM NSR is enabled, the RBM channel will be disconnected. In this case, disable RBM NSR to maintain RBM channel connectivity and then re-enable it after replacing the standby MPU.

During MPU bulk configuration backup, RBM NSR cannot work correctly. If the active MPU fails, the standby MPU cannot smoothly switch to the active MPU role, and the RBM channel will disconnect, requiring the new MPU to re-establish the channel.

Examples

# Disable RBM NSR.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] undo nsr enable

remote-backup group

Use remote-backup group command to enter RBM view.

Use undo remote-backup group to remove all settings in RBM view.

Syntax

remote-backup group

undo remote-backup group

Views

System view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

Remote Backup Management (RBM) uses H3C proprietary RBM to manage implement device-level high availability (HA). It enables two nodes to back up each other dynamically to ensure user service continuity upon failure of one of the nodes.

Restrictions and guidelines

You cannot use the commands in RBM view to synchronize configuration information. To do that, manually configure the RBM member devices.

Examples

# Enter RBM view.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group]

remote-ip

Use remote-ip to configure the peer IPv4 address for setting up the control channel.

Use undo remote-ip to restore the default.

Syntax

remote-ip ipv4-address [ port port-number ]

undo remote-ip ipv4-address

Default

The peer IPv4 address is not configured for setting up the control channel.

Views

RBM view

Predefined user roles

network-admin

Parameters

ipv4-address: Specifies the peer IPv4 address for setting up the control channel. The IP address cannot be an all-zero, loopback, or multicast address.

port port-number: Specifies a port by its number used for establishing TCP connection. The value range for the port-number argument is 1024 to 65535, and the default value is 60064.

Usage guidelines

Operating mechanism

The control channel transmits data by using packets, including RBM status packets, configuration consistency check packets, and configuration synchronization packets. Each member device compares the specified local and peer IP address to determine the device role for setting up the control channel. The device with higher IP address acts as the server to listen for TCP connection requests, and the other device acts as the client to initiate the TCP connection.

If the port number is configured on the server, the port provides services for the client. If the port number is configured on the client, the port serves as the destination port to establish TCP connection to the server. The source port is randomly generated on the client.

Restrictions and guidelines

You can specify only one peer IP address with the same port number on the RBM member devices.

You can configure a remote IPv4 address or a remote IPv6 address, but not both.

Examples

# Configure the peer IPv4 address and port number as 1.1.1.1 and 4456 for setting up the control channel.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] remote-ip 1.1.1.1 port 4456

Related commands

local-ip

remote-ipv6

Use remote-ipv6 to configure the peer IPv6 address for setting up the control channel.

Use undo remote-ipv6 to restore the default.

Syntax

remote-ipv6 ipv6-address [ port port-number ]

undo remote-ipv6 ipv6-address

Default

The peer IPv6 address is not configured for setting up the control channel.

Views

RBM view

Predefined user roles

network-admin

Parameters

ipv6-address: Specifies the peer IPv6 address for setting up the control channel. The IP address cannot be an all-zero address, loopback address, multicast address, or IPv6 address with an embedded IPv4 address.

port port-number: Specifies a port by its number used for establishing TCP connection. The value range for the port-number argument is 1024 to 65535, and the default value is 60064. Make sure the port number is not in use.

Usage guidelines

Operating mechanism

The control channel transmits data by using packets, including RBM status packets, configuration consistency check packets, and configuration synchronization packets. Each member device compares the specified local and peer IPv6 address to determine the device role for setting up the control channel. The device with higher IPv6 address acts as the server to listen for TCP connection requests, and the other device acts as the client to initiate the TCP connection.

Restrictions and guidelines

You can specify only one peer IPv6 address with the same port number on the RBM member devices.

You can configure a remote IPv4 address or a remote IPv6 address, but not both.

Examples

# Configure the peer IPv6 address and port number as 2018::1 and 4456 for setting up the control channel.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] remote-ipv6 2018::1 port 4456

Related commands

local-ipv6

remote-ip

reset remote-backup-group trans-data

Use reset remote-backup-group trans-data to clear statistics of the mirroring-mode-specific data transmitted through the data channel.

Syntax

reset remote-backup-group trans-data

Views

RBM user view

Predefined user roles

network-admin

network-operator

Examples

# Clear statistics of the mirroring-mode-specific data transmitted through the data channel.

<Sysname> reset remote-backup-group trans-data

Related commands

display remote-backup-group trans-data

running-data auto-sync enable

Use running-data auto-sync enable to enable automatic synchronization for running data.

Use undo running-data auto-sync enable to disable automatic synchronization for running data.

Syntax

running-data auto-sync enable

undo running-data auto-sync enable

Default

Automatic synchronization for running data is enabled.

Views

RBM view

Predefined user roles

network-admin

Usage guidelines

The hot backup member devices generate running data when processing packets, and perform packet detection and forwarding based on the running data. To ensure service continuity upon an active/standby switchover, back up running data between the hot backup member devices. In the active/standby-mode or mirroring-mode hot backup network, only the active device processes services. The active device synchronizes running data to the standby device. In the dual-active-mode hot backup network, both hot backup members process services. They both generate running data and back up running data to each other.

In the current software version, RBM-based hot backup supports synchronizing the following dynamic running data: DNS entries, ARP entries, load balancing (LB) proximity entries, and LB running data, as well as running data of IPsec, IKE, and IKEv2.

Examples

# Enable automatic synchronization for running data.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] running-data auto-sync enable

session manual-sync

Use session manual-sync to bulk back up local session entries to the hot backup peer.

Syntax

In standalone mode:‌

session manual-sync [ slot slot-number [ cpu cpu-number ] ]

In IRF mode:

session manual-sync [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

Views

RBM view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command backs up session entries for all cards. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command backs up session entries for all cards. (In IRF mode.) ‌

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

Usage guidelines

Application scenarios

If the hot backup member devices have inconsistent session entries, you can manually bulk back up local session entries from one hot backup member device to the other.

Restrictions and guidelines

This command does not take effect during bulk configuration backup or bulk service entry backup. To examine whether bulk configuration backup or bulk service entry backup is in progress, execute the display remote-backup-group status command. The minimum interval between two executions of the session manual-sync command is 1 minute.

Examples

# Bulk back up local session entries to the hot backup peer.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] session manual-sync

Related commands

display remote-backup-group status

silent-backup-interface

Use silent-backup-interface to disable the standby device from sending or receiving protocol packets of a dynamic routing protocol.

Use undo silent-backup-interface to enable the standby device to send and receive protocol packets of a dynamic routing protocol.

Syntax

silent-backup-interface { ospf | ospfv3 }

undo silent-backup-interface { ospf | ospfv3 }

Default

The standby device can send and receive protocol packets of a dynamic routing protocol.

Views

RBM view

Predefined user roles

network-admin

Parameters

ospf: Specifies OSPF.

ospfv3: Specifies OSPFv3.

Usage guidelines

Application scenarios

Different routing protocols have different default priorities. When the RBM member devices run multiple routing protocols, traffic might still be forwarded to the failed link after you set a higher cost value for a link. This command disconnects the neighbor relationships for a dynamic routing protocol on the standby device. The active device can send and receive protocol packets of that dynamic routing protocol, and correctly process both uplink and downlink traffic.

Restrictions and guidelines

You can execute this command multiple times to disable multiple dynamic routing protocols on the standby device.

You cannot use this command together with the adjust-cost enable command.

Examples

# Disable the standby device from sending or receiving OSPF protocol packets.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] silent-backup-interface ospf

Related commands

adjust-cost enable

switchover

Use switchover to perform an active/standby switchover.

Syntax

switchover { active | request | reset | standby }

Views

RBM view

Predefined user roles

network-admin

Parameters

active: Switches the running status of the peer device to standby. The local device retains its active state. This parameter is available only when the RBM system is operating in dual-active mode.

request: Performs an active/standby switchover. This parameter is available only when the RBM system is operating in active/standby or mirroring mode.

reset: Performs running status re-election. This parameter is available when the RBM system is operating in active/standby, mirroring, or dual-active mode.

standby: Switches the running status of the local device to standby. This parameter is available only when the RBM system is operating in dual-active mode.

Usage guidelines

Application scenarios

To replace components or upgrade software on one device, you can execute this command to switch services to the other device.

Operating mechanism

The function of this command is as follows:

· switchover request—In an active/standby or mirroring RBM system, use this command to trigger an active/standby switchover on either the active device or standby device.

· switchover active—In a dual-active RBM system, typically both member devices are active. From a member device, you can use this command to switch the running status of the peer device to standby. The local device retains its active state.

· switchover standby—In a dual-active RBM system, typically both member devices are active. You can use this command to switch the running status of one member device to standby. The peer device retains its active state.

· switchover reset—In an active/standby or dual-active RBM system, use this command to perform running status re-election on either the active device or standby device.

Prerequisites

Use this feature when both member devices are operating correctly. This command does not take effect if the RBM status is abnormal. For example, when a service interface of the active device fails and the running status changes to standby, the switchover request command will not switch the running status back to active.

Restrictions and guidelines

In an RBM system and VRRP associated network, executing this command might cause temporary virtual IP address conflict in the VRRP group, which is considered a normal condition. For more information about VRRP, see High Availability Configuration Guide.

For stable operation of the RBM system, do not repeatedly execute this command within one minute.

Examples

# Perform an active/standby switchover.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] switchover request

switchover vrrp backup

Use switchover vrrp backup to specify the peer device as the default operating device in a VRRP group.

Use undo switchover vrrp backup to restore the default.

Syntax

switchover vrrp [ ipv6 ] vrid virtual-router-id backup

undo switchover vrrp [ [ ipv6 ] vrid virtual-router-id ] backup

The following compatibility matrix shows the support of hardware platforms for this command:

Series	Models	Command compatibility
M9000 series	M9006, M9010, M9014, M9016-V	No
M9000-S series	M9008-S, M9008-S-V	No
M9000-AK series	M9000-AK001	No
M9000-AI-E series	M9000-AI-E4	No
M9000-AI-E series	M9000-AI-E8, M9000-AI-E16	Yes
M9000-X series	M9000-X06, M9000-X06-B, M9000-X06-B-G, M9000-X06-G, M9000-X10	No
M9000-AI-X series	M9000-AI-X06, M9000-AI-X10	No
M9000-CN series	M9000-CN04	No

‌

Default

The RBM role election result determines the default operating device in a VRRP group associated with RBM.

Views

RBM view

Predefined user roles

network-admin

Parameters

ipv6: Specifies an IPv6 VRRP group. To specify an IPv4 VRRP group, do not specify this keyword.

vrid virtual-router-id: Specifies a VRRP group by its virtual router ID in the range of 1 to 255.

Usage guidelines

Application scenarios

This command enables you to switch all traffic of a VRRP group to the RBM peer device. After you execute this command, the RBM module sets the role of the local device to backup in the specified VRRP group, and the peer device becomes the master.

Restrictions and guidelines

This command takes effect only when both member devices in the RBM system are in active state.

Before RBM channels are set up, you can use this command without following any restrictions. After RBM channels are set up, you can use this command only when both member devices in the RBM system are in active state. If executed on the secondary device, this command will be deleted.

You can execute this command for multiple VRRP groups.

If you execute the undo switchover vrrp backup command without specifying any parameters, the command takes effect on all VRRP groups associated with RBM.

Examples

# Specify the peer device as the default operating device in VRRP group 1 when RBM is operating in dual-active mode.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] switchover vrrp vrid 1 backup

track

Use track to associate RBM with Track.

Use undo track to remove the association.

Syntax

track track-entry-number

undo track track-entry-number

Default

The RBM system is not associated with Track.

Views

RBM view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

Application scenarios

If the hot backup system operates in mirroring mode or collaborates with virtual addresses or routing, to avoid active/standby device switchover failure upon failure of the upstream and downstream links or interfaces, associate RBM with track entries.

Use this command to associate RBM with Track to monitor links. If one of the monitored track entries becomes Negative, the RBM system performs an active/standby switchover and switches traffic to the new active device to ensure service continuity. For more information about Track, see Network Management and Monitoring Configuration Guide.

Restrictions and guidelines

You can use the track interface and track commands in conjunction, but you cannot use these commands to monitor the same interfaces.

To associate RBM with multiple track entries, execute this command multiple times.

Examples

# Associate RBM with track entries 1 and 2.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] track 1

[Sysname-remote-backup-group] track 2

Related commands

track (Network Management and Monitoring Command Reference)

track interface

Use track interface to enable RBM to monitor an interface.

Use undo track interface to remove the configuration.

Syntax

track interface interface-type interface-number

undo track interface [ interface-type interface-number ]

Default

The RBM system does not monitor any interfaces.

Views

RBM view

Predefined user roles

network-admin

Parameters

interface-type interface-number: Specifies an interface by its type and number. You can specify a Layer 2 or Layer 3 Ethernet interface in the current software version. If you do not specify this argument, the undo form of the command removes the monitoring for all interfaces.

Usage guidelines

Application scenarios

Use this command to enable RBM to monitor the interfaces connecting the uplink and downlink devices. The monitored interfaces can forward packets only when they are all up. If any of the monitored interfaces goes down, none of them will be able to forward packets.

Restrictions and guidelines

If the uplink and downlink interfaces of the RBM system are Layer 3 Ethernet interfaces and RBM is used with static routes, use the track interface command to monitor those interfaces.

If the uplink and downlink interfaces of the RBM system are Layer 2 Ethernet interfaces connected to peer Layer 3 interfaces, use the track interface command to monitor the Layer 2 Ethernet interfaces.

You can use the track interface and track commands in conjunction, but you cannot use these commands to monitor the same interfaces.

The track vlan and track interface commands are mutually exclusive. You cannot configure both of them.

You cannot use the track interface command to monitor the interfaces used by VRRP.

This feature applies only to transparent in-path deployment of RBM and the network configured with RBM and static route association.

To enable RBM to monitor multiple interfaces, execute this command multiple times. Make sure the monitored interfaces operate in the same mode.

The RBM system does not support monitoring member ports of aggregate interfaces.

Examples

# Enable RBM to monitor interfaces GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] track interface gigabitethernet 1/0/1

[Sysname-remote-backup-group] track interface gigabitethernet 1/0/2

Related commands

track

track interface

track vlan

Use track vlan to enable RBM to monitor a VLAN.

Use undo track vlan to remove the configuration.

Syntax

track vlan vlan-id

undo track vlan [ vlan-id ]

Default

The RBM system does not monitor any VLANs.

Views

RBM view

Predefined user roles

network-admin

Parameters

vlan-id: Specifies a VLAN by its ID in the range of 1 to 4094. If you do not specify this argument, the undo form of the command removes the monitoring for all VLANs.

Usage guidelines

Application scenarios

Use this command to enable RBM to monitor the VLANs of the uplink and downlink devices. The monitored VLANs are active and the member ports can forward packets only when the member ports are all up. If any of the member ports goes down, none of them will be able to forward packets, and all the monitored VLANs will become inactive.

Operating mechanism

In active/standby mode, the state of monitored VLANs is active on the primary device and inactive on the secondary device.

In dual-active mode, the state of monitored VLANs is active on both the RBM member devices.

Restrictions and guidelines

Do not enable RBM to monitor VLAN 1 (to which all access ports belong by default). This restriction prevents an unused interface in down state from interrupting operation of other interfaces in VLAN 1.

The track vlan command is mutually exclusive with the track interface command. You cannot use the track vlan command in conjunction with the track interface command.

To enable RBM to monitor multiple VLANs, execute this command multiple times.

Examples

# Enable RBM to monitor VLAN 10.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] track vlan 10

Related commands

track

track interface

track vlan

transparent-transmit enable

Use transparent-transmit enable to enable transparent service traffic transmission between the RBM members.

Use undo transparent-transmit enable to disable transparent service traffic transmission between the RBM members.

Syntax

transparent-transmit enable

undo transparent-transmit enable

Default

Transparent service traffic transmission is enabled.

Views

RBM view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

If an asymmetric-path flow traverses the hot backup system operating in dual-active mode, the flow and its return traffic are processed by different RBM members. This will degrade the traffic processing performance of modules such as NBAR, load balancing, and DPI. For example, the packet recognition rate of NBAR might drop. For an asymmetric-path flow and its return traffic to be processed by the same RBM member, enable transparent service traffic transmission.

Restrictions and guidelines

Enable transparent service traffic transmission only when asymmetric-path traffic traverses the hot backup system operating in dual-active mode. Transparent service traffic transmission is resource-intensive. Make sure you are fully aware of the impact of this feature when you use it on a live network.

Examples

# Enable transparent service traffic transmission between the RBM members.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] transparent-transmit enable

wait-interface-up delay-time

Use wait-interface-up delay-time to configure the interface recovery wait timer.

Use undo wait-interface-up delay-time to restore the default.

Syntax

wait-interface-up delay-time time-value

undo wait-interface-up delay-time

Default

The interface recovery wait timer is 32 seconds.

Views

RBM view

Predefined user roles

network-admin

Parameters

time-value: Specifies the interface recovery wait timer in the range of 5 to 60 seconds.

Usage guidelines

Applicable scenarios

In an RBM network, you can use the track interface or track vlan command to monitor the uplink and downlink interfaces, ensuring consistency for the states of the monitored interfaces. If an active/standby switchover occurs due to failure of a monitored interface on the active device, the other monitored interfaces on the original active device will also be unable to forward packets. After the failed interface recovers, traffic switches back to the original active device if traffic switchover upon failure recovery is enabled and the switchover delay timer has expired. The other monitored interfaces will also recover to normal status.

If the recovery time is too long for any other monitored interfaces, another active/standby switchover might occur. To avoid this issue, you can configure an interface recovery wait timer. Traffic will switch to the peer device only if the monitored interfaces have not completed recovery or another monitored interface has failed upon expiration of the wait timer.

Restrictions and guidelines

If a monitored interface has failed before the switchover delay timer expires, traffic will still switch to the interface-associated device, which results in service interruption. This situation will persist until another switchover is triggered upon expiration of the interface recovery wait timer. As a best practice, configure the interface recovery wait time as short as possible provided that the other monitored interfaces have sufficient time to recover.

As a best practice, configure this command only in the scenario where you use the track interface or track vlan command to monitor the uplink and downlink interfaces in the network. You do not need to configure this command in other scenarios.

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

Examples

# Configure the interface recovery wait timer as 60 seconds.

<Sysname> system-view

[Sysname] remote-backup group

[Sysname-remote-backup-group] wait-interface-up delay-time 60

Related commands

track interface

track vlan

16-High Availability Command Reference

RBM-based hot backup commands

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Related commands

Application scenarios

Restrictions and guidelines

Related commands

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

keepalive interval

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Operating mechanism

Restrictions and guidelines

Related commands

Operating mechanism

Restrictions and guidelines

Related commands

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Related commands

Application scenarios

Operating mechanism

Prerequisites

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Application scenarios

Operating mechanism

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

Applicable scenarios