- Table of Contents
-
- 09-High Availability Command Reference
- 00-Preface
- 01-RBM commands
- 02-VRRP commands
- 03-BFD commands
- 04-Track commands
- 05-Reth interface and redundancy group commands
- 06-Failover group commands
- 07-Interface collaboration commands
- 08-Interface backup commands
- 09-Monitor Link commands
- 10-Smart Link commands
- 11-Process placement commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 01-RBM commands | 97.20 KB |
Contents
configuration auto-sync enable
display remote-backup-group status
display remote-backup-group sync-check
RBM commands
adjust-cost enable
Use adjust-cost enable to enable RBM to adjust the link cost for the specified routing protocol on the secondary device.
Use undo adjust-cost enable to disable RBM from adjusting the link cost for the specified routing protocol on the secondary device.
Syntax
adjust-cost { bgp | isis | ospf | ospfv3 } enable { absolute [ absolute-cost ] | increment [ increment-cost ] }
undo adjust-cost { bgp | isis | ospf | ospfv3 } enable
Default
RBM does not adjust the link cost for the specified routing protocol on the secondary device.
Views
Remote backup group view
Predefined user roles
network-admin
context-admin
Parameters
bgp: Specifies the BGP protocol.
isis: Specifies the IS-IS protocol.
ospf: Specifies the OSPF protocol.
ospfv3: Specifies the OSPFv3 protocol.
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 secondary 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 secondary device will advertise the original link cost plus this increment cost for the specified routing protocol.
Usage guidelines
In an RBM hot backup system, the routing protocols on the primary and secondary 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 primary device still uses the original link cost advertisement method.
To ensure switchover of both uplink and downlink traffic to the new primary device, configure this command with the same parameters on both the primary and secondary 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 secondary 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 secondary 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 RBM hot backup mode.
Use undo backup-mode to restore the default.
Syntax
backup-mode dual-active
undo backup-mode
Default
The RBM hot backup mode is active/standby.
Views
Remote backup group view
Predefined user roles
network-admin
context-admin
Usage guidelines
RBM hot backup supports active/standby mode and dual-active mode. In active/standby mode, only the primary device processes services. In dual-active mode, both devices process services.
Changing the dual-active mode to active/standby mode might affect services. Make sure you understand the potential impact before performing the operation.
Examples
# Configure the dual-active hot backup 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 disabled.
Views
Remote backup group view
Predefined user roles
network-admin
context-admin
Usage 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 manual-sync
Use configuration manual-sync to manually synchronize the configuration of the primary device to the secondary device.
Syntax
configuration manual-sync
Views
Remote backup group view
Predefined user roles
network-admin
context-admin
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
configuration sync-check
Use configuration sync-check to enable configuration consistency check.
Use undo configuration sync-check to restore the default.
Syntax
configuration sync-check [ interval interval ]
undo configuration sync-check
Default
Configuration consistency check is disabled.
Views
Remote backup group view
Predefined user roles
network-admin
context-admin
Parameters
interval interval: Specifies the configuration consistency check interval, in the range of 1 to 168 hours. The default value is 24.
Usage guidelines
RBM verifies configuration consistency between the primary and secondary devices to avoid service interruption upon primary/secondary member switchover. If a device detects configuration inconsistency, it generates a log for you to manually synchronize configuration.
Examples
# Enable configuration consistency check and set the 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
data-channel
Use data-channel to configure an RBM data channel.
Use undo data-channel to restore the default.
Syntax
data-channel interface interface-type interface-number
undo data-channel
Default
No RBM data channel is configured.
Views
Remote backup group view
Predefined user roles
network-admin
context-admin
Parameters
interface interface-type interface-number: Specifies an interface by its type and number to set up a data channel between the primary and secondary devices.
Usage guidelines
The primary and secondary devices use the interface specified in the command to set up an RBM data channel. The data channel transmits only hot backup packets and the packets that require transparent transmission.
Examples
# Set up an RBM data channel using interface GigabitEthernet 1/2/5/1.
<Sysname> system-view
[Sysname] remote-backup group
[Sysname-remote-backup-group] data-channel interface gigabitethernet 1/2/5/1
device-role
Use device-role to configure the RBM role.
Use undo device-role to restore the default.
Syntax
device-role { primary | secondary }
undo device-role
Default
The RBM role is not configured.
Views
Remote backup group view
Predefined user roles
network-admin
context-admin
Parameters
primary: Assigns the primary role to the device.
secondary: Assigns the secondary role to the device.
Usage guidelines
RBM backs up important configuration from the primary device to the secondary device to prevent service interruption when a primary/secondary member 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.
Examples
# Assign the primary role to the device.
<Sysname> system-view
[Sysname] remote-backup group
[Sysname-remote-backup-group] device-role primary
display remote-backup-group status
Use display remote-backup-group status to display remote backup group status information.
Syntax
display remote-backup-group status
Views
Any view
Predefined user roles
network-admin
network-operator
context-admin
context-operator
Examples
# Display remote backup group status information.
<Sysname> display remote-backup-group status
Remote backup group information:
Backup mode: Dual-active
Device role: Primary
Data channel interface: GigabitEthernet1/2/5/1
Local IPv4: 1.1.1.1
Remote IPv4: 1.1.1.2 Destination port: 1028
Local IPv6: 2019::1
Remote IPv6: 2018::1 Destination port: 1028
Control channel status: Connected
Hot backup status: Enabled
Auto configuration synchronization: Enabled
Configuration consistency check interval: 30 hour
Delay-time: 1 min
Table 1 Command output
|
Field |
Description |
|
Backup mode |
RBM hot backup mode: · Dual-active. · Active/standby. |
|
Device role |
RBM role of the device: · Primary. · Secondary. |
|
Data channel interface |
Interface used to set up the data channel. |
|
Local IPv4 |
Local IP address used by control channel packets. This field is not displayed if the parameter is not configured. |
|
Remote IPv4 |
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. |
|
Hot backup status |
Hot backup status: · Enabled. · Disabled. |
|
Auto configuration synchronization |
Automatic configuration synchronization status: · Enabled. · Disabled. |
|
Configuration consistency check interval |
Configuration consistency check interval in hours. This field is displayed only when configuration consistency check is enabled. |
|
Delay-time |
Delay time for traffic switchover back to the original primary device in minutes. If the value is 0, this switchover feature is disabled for RBM hot backup. |
display remote-backup-group sync-check
Use display remote-backup-group sync-check to display the configuration consistency check result for the remote backup group.
Syntax
display remote-backup-group sync-check
Views
Any view
Predefined user roles
network-admin
network-operator
context-admin
context-operator
Usage guidelines
Use this command when the primary and secondary devices have inconsistent configuration.
The command displays detailed inconsistency information for only the service modules supported by RBM. For a module not supported by RBM, the command displays only the interface where configuration inconsistency exists.
Examples
# Display the configuration consistency check result for the remote backup group. (No inconsistent configuration exists.)
<Sysname> display remote-backup-group sync-check
No inconsistent configuration exists.
# Display the configuration consistency check result for the remote backup group. (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
#
Related commands
configuration sync-check
hot-backup enable
Use hot-backup enable to enable RBM hot backup.
Use undo hot-backup enable to disable RBM hot backup.
Syntax
hot-backup enable
undo hot-backup enable
Default
RBM hot backup is enabled.
Views
Remote backup group view
Predefined user roles
network-admin
context-admin
Usage guidelines
This command enables the primary device in the remote backup group to back up service entries to the secondary device in real time. This prevents service interruption when a primary/secondary member switchover occurs.
Examples
# Enable RBM hot backup.
<Sysname> system-view
[Sysname] remote-backup group
[Sysname-remote-backup-group] hot-backup enable
local-ip
Use local-ip to configure the local IPv4 address for setting up the RBM 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 RBM control channel.
Views
Remote backup group view
Predefined user roles
network-admin
context-admin
Parameters
ipv4-address: Specifies the local IPv4 address for setting up the RBM control channel.
Usage guidelines
RBM 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.
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 RBM 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 RBM 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 RBM control channel.
Views
Remote backup group view
Predefined user roles
network-admin
context-admin
Parameters
ipv6-address: Specifies the local IPv6 address for setting up the RBM control channel.
Usage guidelines
RBM 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.
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 RBM control channel.
<Sysname> system-view
[Sysname] remote-backup group
[Sysname-remote-backup-group] local-ipv6 2019::1
Related commands
local-ip
remote-ipv6
remote-backup group
Use remote-backup group command to enter remote backup group view.
Use undo remote-backup group to remove all settings of the remote backup group.
Syntax
remote-backup group
undo remote-backup group
Views
System view
Predefined user roles
network-admin
context-admin
Usage guidelines
RBM provides backup for important configuration and service entries between devices. It collaborates with VRRP to implement hot backup that enables smooth master/backup switchover upon link failures for service continuity. For more information about VRRP, see High Availability Configuration Guide.
Examples
# Enter remote backup group 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 RBM 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 RBM control channel.
Views
Remote backup group view
Predefined user roles
network-admin
context-admin
Parameters
ipv4-address: Specifies the peer IPv4 address for setting up the RBM control channel.
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
The RBM control channel transmits data by using packets, including remote backup group status packets, configuration consistency check packets, and configuration synchronization packets. RBM 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.
You can specify only one peer IP address with the same port number on the primary and secondary 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 RBM 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
remote-ipv6
Use remote-ipv6 to configure the peer IPv6 address for setting up the RBM 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 RBM control channel.
Views
Remote backup group view
Predefined user roles
network-admin
context-admin
Parameters
ipv6-address: Specifies the peer IPv6 address for setting up the RBM control channel.
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
The RBM control channel transmits data by using packets, including remote backup group status packets, configuration consistency check packets, and configuration synchronization packets. RBM 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.
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.
You can specify only one peer IPv6 address with the same port number on the primary and secondary 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 RBM 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
switchover request
Use switchover request to perform a primary/secondary member switchover.
Syntax
switchover request
Views
Remote backup group view
Predefined user roles
network-admin
context-admin
Usage guidelines
If you want to replace components or upgrade software on the current primary device, you can execute this command to switch services to the secondary device.
This command applies only when RBM operates in active/standby hot backup mode.
In an RBM and VRRP associated network, executing this command might cause temporary virtual IP address conflict in the VRRP group, which is considered a normal condition.
Examples
# Perform a primary/secondary member switchover.
<Sysname> system-view
[Sysname] remote-backup group
[Sysname-remote-backup-group] switchover request
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
RBM is not associated with Track.
Views
Remote backup group view
Predefined user roles
network-admin
context-admin
Parameters
track-entry-number: Specifies a track entry by its ID in the range of 1 to 1024.
Usage guidelines
Use this command to associate RBM with Track to monitor links. If one of the monitored track entries becomes Negative, RBM performs a primary/secondary member switchover and switches traffic to the new primary device to ensure service continuity. For more information about Track, see High Availability Configuration Guide.
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 (High Availability Command Reference)
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
Remote backup group view
Predefined user roles
network-admin
context-admin
Parameters
delay-time: Specifies the switchover delay time in the range of 1 to 50 minutes.
Usage guidelines
After a primary/secondary member switchover in an RBM hot backup system, if the original primary device recovers, traffic will not be switched back by default. Perform this task to enable traffic switchover to the original primary device upon failure recovery. You can set a delay timer to ensure smooth service switchover.
In dual-active hot backup mode, you must configure this command to ensure that both devices can operate after the failure is recovered.
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
