Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 01-High availability group commands | 132.71 KB |
Contents
High availability group commands
configuration auto-sync enable
configuration manual-sync-check
display remote-backup-group status
display remote-backup-group sync-check
High availability group commands
adjust-cost enable
Use adjust-cost enable to enable the HA group to adjust the link cost for the specified routing protocol on the secondary device.
Use undo adjust-cost enable to disable the HA group 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
The HA group does not adjust the link cost for the specified routing protocol on the secondary device.
Views
HA 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 HA group, 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 the HA group to adjust OSPF link cost on the secondary device by specifying an absolute value of 6000.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[Sysname-remote-backup-group] adjust-cost ospf enable absolute 6000
backup-mode
Use backup-mode to configure the HA mode.
Use undo backup-mode to restore the default.
Syntax
backup-mode dual-active
undo backup-mode
Default
The HA mode is active/standby.
Views
HA group view
Predefined user roles
network-admin
context-admin
Usage guidelines
The HA group 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 mode.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[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
HA 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.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[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
HA group view
Predefined user roles
network-admin
context-admin
Usage guidelines
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.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[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
HA group view
Predefined user roles
network-admin
context-admin
Usage guidelines
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. To view the check result, execute the display remote-backup-group sync-check command.
Examples
# Perform a one-off configuration consistency check.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[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.
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
HA 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
The HA group 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.
RBM_P<Sysname>system-view
RBM_P[Sysname] remote-backup group
RBM_P[Sysname-remote-backup-group] configuration sync-check interval 120
Related commands
configuration manual-sync
data-channel
Use data-channel to configure an HA data channel.
Use undo data-channel to restore the default.
Syntax
data-channel interface interface-type interface-number
undo data-channel
Default
No HA data channel is configured.
Views
HA 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 HA data channel. The data channel transmits only backup packets and the packets that require transparent transmission.
The data channel is a Layer 2 channel that can transverse only Layer 2 switches.
Examples
# Set up an HA data channel using interface GigabitEthernet 1/0/1.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[Sysname-remote-backup-group] data-channel interface gigabitethernet 1/0/1
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
HA group view
Predefined user roles
network-admin
context-admin
Parameters
delay-time: Specifies the switchover delay time in the range of 1 to 1440 minutes.
Usage guidelines
After a primary/secondary member switchover in an HA group, 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 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.
RBM_P<Sysname>system-view
RBM_P[Sysname] remote-backup group
RBM_P[Sysname-remote-backup-group] delay-time 2
device-role
Use device-role to configure the HA role.
Use undo device-role to restore the default.
Syntax
device-role { primary | secondary }
undo device-role
Default
The HA role is not configured.
Views
HA 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
The HA group 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.
Each HA group member device adds a prefix to the view prompt to identify its HA role.
· The primary device adds the RBM_P prefix, RBM_P<Sysname> for example.
· The secondary device adds the RBM_S prefix, RBM_S<Sysname> for example.
After you assign HA roles to the HA group member devices, both devices add the RBM_P prefix to their view prompts. The devices display view prompt prefixes according to their HA roles after they set up the HA control channel.
The HA group must contain one primary device and one secondary device.
As a best practice, configure service features on the primary device.
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 remote-backup-group status
Use display remote-backup-group status to display HA 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 HA group status information.
RBM_P<Sysname> display remote-backup-group status
Remote backup group information:
Backup mode: Dual-active
Device management role: Primary
Device status: Active
Data channel interface: GigabitEthernet1/0/1
Local IPv4: 1.1.1.1
Remote IPv4: 1.1.1.2 Destination port: 1028
Control channel status: Connected
Keepalive interval: 1s
Keepalive count: 5
Configuration consistency check interval: 30 hour
Configuration consistency check result: Consistent
Configuration backup status: Batch backup (Do not operate
the device at will, such as board insertion and removal.)
Session backup status: Hot backup enabled
Delay-time: 1 min
Table 1 Command output
|
Field |
Description |
|
Backup mode |
HA mode: · Dual-active. · Active/standby. |
|
Device management role |
HA role of the device: · Primary. · Secondary. |
|
Device status |
Whether the device is in the VRRP active group or VRRP standby group. · Active. · Standby. |
|
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. |
|
Keepalive interval |
Interval for sending HA keepalive packets. |
|
Keepalive count |
Maximum number of HA keepalive attempts. |
|
Configuration consistency check interval |
Configuration consistency check interval in hours. This field is displayed only when configuration consistency check is enabled. |
|
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. |
|
Session backup status |
Status of session entry backup: · Batch backup in progress. · Hot backup enabled. · Hot backup disabled. |
|
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 the HA backup group. |
display remote-backup-group sync-check
Use display remote-backup-group sync-check to display the configuration consistency check result for the HA 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. 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 the HA group. For a feature not supported by the HA group, the command displays only the interface where configuration inconsistency exists.
Examples
# Display the configuration consistency check result for the HA group. (The configuration consistency check has not been performed.)
RBM_P<Sysname> display remote-backup-group sync-check
No configuration consistency checks have been performed.
# Display the configuration consistency check result for the HA group. (No inconsistent configuration exists.)
RBM_P<Sysname> display remote-backup-group sync-check
No inconsistent configuration exists.
# Display the configuration consistency check result for the HA group. (Inconsistent configuration exists.)
RBM_P<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
configuration manual-syn-check
hot-backup enable
Use hot-backup enable to enable service entry hot backup.
Use undo hot-backup enable to disable service entry hot backup.
Syntax
hot-backup enable
undo hot-backup enable
Default
Service entry hot backup is enabled.
Views
HA group view
Predefined user roles
network-admin
context-admin
Usage guidelines
This command enables the primary device in the HA 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 service entry hot backup.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[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 application layer protocols.
Use undo hot-backup protocol enable to disable hot backup for the session entries of application layer protocols.
Syntax
hot-backup protocol { dns | http } * enable
undo hot-backup protocol { dns | http } * enable
Default
The HA group performs hot backup for the session entries of application layer protocols.
Views
HA group view
Predefined user roles
network-admin
context-admin
Parameters
dns: Specifies DNS.
http: Specifies HTTP.
Usage guidelines
For this command to take effect, first execute the hot-backup enable command.
The hot-backup protocol enable command takes effect only on DNS and HTTP. The device automatically backs up the session entries of other application layer protocols after you enable service entry hot backup.
To ensure correct forwarding, enable hot backup for the session entries of application layer protocols if asymmetric-path traffic traverses the HA group. This feature allows the member devices in the HA group to correctly process asymmetric-path traffic.
If the HA group operates in active/standby mode or only symmetric-path traffic exists, disable hot backup for the session entries of application layer protocols to save session entry resources. A member 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.
Examples
# Disable hot backup for the session entries of application layer protocols.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[Sysname-remote-backup-group] undo hot-backup protocol dns enable
Related commands
hot-backup enable
keepalive count
Use keepalive count to set the maximum number of HA keepalive attempts.
Use undo keepalive count to restore the default.
Syntax
keepalive count counts
undo keepalive count
Default
The maximum number of HA keepalive attempts is 10.
Views
HA group view
Predefined user roles
network-admin
context-admin
Parameters
times: Sets the maximum number of HA keepalive attempts, in the range of 1 to 255.
Usage guidelines
If you set the maximum number of HA keepalive attempts to a value too small, network latency will cause incorrect switchovers. If this issue occurs, increase the value of this parameter.
The device periodically sends HA keepalive packets to the HA peer over the HA control channel. If the device has not received any responses from the peer when the maximum number of HA keepalive attempts is reached, the HA control channel is disconnected.
Examples
# Set the maximum number of HA keepalive attempts to 6.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[Sysname-remote-backup-group] keepalive count 6
Related commands
keepalive interval
keepalive interval
Use keepalive interval to set the interval for sending HA keepalive packets.
Use undo keepalive interval to restore the default.
Syntax
keepalive interval interval
undo keepalive interval
Default
The device sends HA keepalive packets at an interval of 1 second.
Views
HA group view
Predefined user roles
network-admin
context-admin
Parameters
interval: Sets the interval for sending HA keepalive packets in seconds, in the range of 1 to 60.
Usage guidelines
The device periodically sends HA keepalive packets to the HA peer over the HA control channel. If the device has not received any responses from the peer when the maximum number of HA keepalive attempts is reached, the HA control channel is disconnected.
Examples
# Set the interval for sending HA keepalive packets to 2 seconds.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[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 HA 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 HA control channel.
Views
HA group view
Predefined user roles
network-admin
context-admin
Parameters
ipv4-address: Specifies the local IPv4 address for setting up the HA control channel.
Usage guidelines
The HA group 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 HA control channel.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[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 HA 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 HA control channel.
Views
HA group view
Predefined user roles
network-admin
context-admin
Parameters
ipv6-address: Specifies the local IPv6 address for setting up the HA control channel.
Usage guidelines
The HA group 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 HA control channel.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[Sysname-remote-backup-group] local-ipv6 2019::1
Related commands
local-ip
remote-ipv6
remote-backup group
Use remote-backup group command to enter HA group view.
Use undo remote-backup group to remove all settings of the HA group.
Syntax
remote-backup group
undo remote-backup group
Views
System view
Predefined user roles
network-admin
context-admin
Usage guidelines
The HA group 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.
Examples
# Enter HA group view.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[Sysname-remote-backup-group]
remote-ip
Use remote-ip to configure the peer IPv4 address for setting up the HA 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 HA control channel.
Views
HA group view
Predefined user roles
network-admin
context-admin
Parameters
ipv4-address: Specifies the peer IPv4 address for setting up the HA 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 HA control channel transmits data by using packets, including HA group 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.
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 HA control channel.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[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 HA 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 HA control channel.
Views
HA group view
Predefined user roles
network-admin
context-admin
Parameters
ipv6-address: Specifies the peer IPv6 address for setting up the HA 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 HA control channel transmits data by using packets, including HA group 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.
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 HA control channel.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[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
HA 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 the HA group operates in active/standby mode.
In an HA group 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.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[Sysname-remote-backup-group] switchover request
track
Use track to associate the HA group with Track.
Use undo track to remove the association.
Syntax
track track-entry-number
undo track track-entry-number
Default
The HA group is not associated with Track.
Views
HA 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 the HA group with Track to monitor links. If one of the monitored track entries becomes Negative, the HA group performs a primary/secondary member switchover and switches traffic to the new primary device to ensure service continuity. For more information about Track, see Network Management and Monitoring Configuration Guide.
To associate the HA group with multiple track entries, execute this command multiple times.
Examples
# Associate the HA group with track entries 1 and 2.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[Sysname-remote-backup-group] track 1
RBM_P[Sysname-remote-backup-group] track 2
Related commands
track (Network Management and Monitoring Command Reference)
track interface
Use track interface to enable the HA group 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 HA group does not monitor any interfaces.
Views
HA group view
Predefined user roles
network-admin
context-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number. You can specify a Layer 2 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
Use this command to enable the HA group 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.
To enable the HA group to monitor multiple interfaces, execute this command multiple times.
The track vlan, track interface, and track commands are mutually exclusive.
The HA group does not support monitoring member ports of aggregate interfaces.
Examples
# Enable the HA group to monitor interfaces GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[Sysname-remote-backup-group] track interface gigabitethernet 1/0/1
RBM_P[Sysname-remote-backup-group] track interface gigabitethernet 1/0/2
Related commands
track
track interface
track vlan
track vlan
Use track vlan to enable the HA group to monitor a VLAN.
Use undo track vlan to remove the configuration.
Syntax
track vlan vlan-id
undo track vlan [ vlan-id ]
Default
The HA group does not monitor any VLANs.
Views
HA group view
Predefined user roles
network-admin
context-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
Use this command to enable the HA group 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.
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 primary and secondary devices.
Do not enable the HA group 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.
To enable the HA group to monitor multiple VLANs, execute this command multiple times.
The track vlan, track interface, and track commands are mutually exclusive.
Examples
# Enable the HA group to monitor VLAN 10.
RBM_P<Sysname> system-view
RBM_P[Sysname] remote-backup group
RBM_P[Sysname-remote-backup-group] track vlan 10
Related commands
track
track interface
track vlan
vrrp ipv6 vrid
Use vrrp ipv6 vrid to create an IPv6 VRRP group and assign a virtual IPv6 address to it, or to assign a virtual IPv6 address to an existing IPv6 VRRP group.
Use undo vrrp ipv6 vrid to remove all configurations of an IPv6 VRRP group, or to remove a virtual IPv6 address from an IPv6 VRRP group.
Syntax
vrrp ipv6 vrid virtual-router-id virtual-ip virtual-address link-local { active | standby }
undo vrrp ipv6 vrid virtual-router-id [ virtual-ip [ virtual-address [ link-local ] ] ]
Default
No IPv6 VRRP groups exist.
Views
Interface view
Predefined user roles
network-admin
context-admin
Parameters
virtual-router-id: Specifies an IPv6 VRRP group by its virtual router ID in the range of 1 to 255.
virtual-ip virtual-address: Specifies a virtual IPv6 address. If you do not specify this option, the undo vrrp ipv6 vrid command removes all virtual IPv6 addresses from the specified IPv6 VRRP group.
link-local: Specifies a link-local address as the virtual IPv6 address.
active: Associates the IPv6 VRRP group with the HA group by adding the device to the IPv6 VRRP active group. The initial role of the device is master.
standby: Associates the IPv6 VRRP group with the HA group by adding the device to the IPv6 VRRP standby group. The initial role of the device is backup.
Usage guidelines
You can execute this command multiple times to assign multiple virtual IPv6 addresses to an IPv6 VRRP group. An IPv6 VRRP group can have a maximum of 16 virtual IPv6 addresses.
The first virtual IPv6 address that you assign to an IPv6 VRRP group must be a link-local address, and it must be removed last.
An IPv6 VRRP group can have only one link-local address as its virtual IPv6 address. For an IPv6 VRRP group to work correctly, you must also assign it a global unicast address as a virtual IPv6 address.
The virtual IPv6 address of an IPv6 VRRP group and the downlink interface IPv6 address of the VRRP group members must be on the same subnet. Otherwise, the hosts on the subnet might fail to access external networks.
You cannot associate an IPv6 VRRP group operating in load balancing mode with the HA group.
You can assign multiple virtual IPv6 addresses to an IPv6 VRRP group associated with the HA group. Make sure the interfaces in the IPv6 VRRP group do not own the virtual IPv6 addresses.
You cannot associate an IPv6 VRRP group with both the HA group and Track.
To modify the settings for the command, first execute the undo form of the command, and then execute the vrrp ipv6 vrid command again.
Examples
# Create IPv6 VRRP group 1, assign virtual IPv6 address fe80::10 to the VRRP group, and assign the device to the VRRP active group. Then assign virtual IPv6 address 1::10 to the VRRP group.
RBM_P<Sysname> system-view
RBM_P[Sysname] interface gigabitethernet 1/0/1
RBM_P[Sysname-GigabitEthernet1/0/1] vrrp ipv6 vrid 1 virtual-ip fe80::10 link-local active
RBM_P[Sysname-GigabitEthernet1/0/1] vrrp ipv6 vrid 1 virtual-ip 1::10
vrrp vrid
Use vrrp vrid to create an IPv4 VRRP group and assign a virtual IP address to it, or to assign a virtual IP address to an existing IPv4 VRRP group.
Use undo vrrp vrid to remove all configurations of an IPv4 VRRP group, or to remove a virtual IP address from an IPv4 VRRP group.
Syntax
vrrp vrid virtual-router-id virtual-ip virtual-address { active | standby }
undo vrrp vrid virtual-router-id [ virtual-ip [ virtual-address ] ]
Default
No IPv4 VRRP groups exist.
Views
Interface view
Predefined user roles
network-admin
context-admin
Parameters
virtual-router-id: Specifies an IPv4 VRRP group by its virtual router ID in the range of 1 to 255.
virtual-ip virtual-address: Specifies a virtual IP address. You cannot specify the virtual IP address as any of the following IP addresses:
· All-zero address (0.0.0.0).
· Broadcast address (255.255.255.255).
· Loopback address.
· IP address of other than Class A, Class B, and Class C.
· Invalid IP address (for example, 0.0.0.1).
If you do not specify the virtual-address argument, the undo vrrp vrid command removes all virtual IP addresses from the specified IPv4 VRRP group.
active: Associates the VRRP group with the HA group by adding the device to the VRRP active group. The initial role of the device is master.
standby: Associates the VRRP group with the HA group by adding the device to the VRRP standby group. The initial role of the device is backup.
Usage guidelines
You can execute this command multiple times to assign multiple virtual IP addresses to an IPv4 VRRP group. An IPv4 VRRP group can have a maximum of 16 virtual IP addresses.
The virtual IP address of an IPv4 VRRP group and the downlink interface IP addresses of the VRRP group members must be on the same subnet. Otherwise, the hosts on the subnet might fail to access external networks.
You cannot associate a VRRP group operating in load balancing mode with the HA group.
For VRRP to operate correctly, make sure a virtual IP address of an IPv4 VRRP group is not the IP address of any interface in the VRRP group.
You can assign multiple virtual IPv4 addresses to an IPv4 VRRP group associated with the HA group. Make sure the interfaces in the IPv4 VRRP group do not own the virtual IPv4 addresses.
You cannot associate a VRRP group with both the HA group and Track.
To modify the settings for the command, first execute the undo form of the command, and then execute the vrrp vrid command again.
Examples
# Create IPv4 VRRP group 1, assign virtual IP address 10.10.10.10 to the VRRP group, and assign the device to the VRRP active group.
RBM_P<Sysname> system-view
RBM_P[Sysname] interface gigabitethernet 1/0/1
RBM_P[Sysname-GigabitEthernet1/0/1] vrrp vrid 1 virtual-ip 10.10.10.10 active
Related commands
display vrrp
