Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 03-Cloud cluster commands | 253.61 KB |
Cloud cluster configuration commands
cloud-cluster auto-merge enable
cloud-cluster auto-update enable
cloud-cluster configuration active
cloud-cluster service-cluster domain
cloud-cluster service-cluster isolate master
cloud-cluster service-cluster mac-address persistent
cloud-cluster service-cluster mad domain
cloudcluster-optimize wlan reliable-access
display cloud-cluster configuration
display cloud-cluster service-cluster container
Cloud cluster configuration commands
cloud-cluster auto-merge enable
Use cloud-cluster auto-merge enable to enable cloud cluster auto-merge.
Use undo cloud-cluster auto-merge enable to disable cloud cluster auto-merge.
Syntax
cloud-cluster auto-merge enable
undo cloud-cluster auto-merge enable
Default
The cloud cluster auto-merge feature is enabled. The cloud cluster that has failed in the master election reboots automatically to complete the cloud cluster merge.
Views
System view
Predefined user roles
network-admin
Usage guidelines
Application scenarios
The cloud cluster auto-merge feature takes effect on merges caused by the following events:
· The cloud cluster link recovers from a link failure.
· The cloud clusters to be merged already have the cloud cluster port bindings required for merging, and those port bindings are activated.
Operating mechanism
Cloud clusters that are merging perform master election. The auto-merge feature enables member devices in the cloud cluster that fails the master election to automatically reboot for completing the cloud cluster merge. If the cloud cluster auto-merge feature is disabled, you must log in to the cloud cluster that fails master election, and then follow the system instructions to manually reboot member devices in the cloud cluster. Only in this way can the member devices in the failing cloud cluster join the winning cloud cluster.
For a successful merge, make sure the cloud cluster auto-merge feature is enabled on both cloud clusters that are merging.
Examples
# Enable cloud cluster auto-merge.
<Sysname> system-view
[Sysname] cloud-cluster auto-merge enable
cloud-cluster auto-update enable
Use cloud-cluster auto-update enable to enable software auto-update.
Use undo cloud-cluster auto-update enable to disable software auto-update.
Syntax
cloud-cluster auto-update enable
undo cloud-cluster auto-update enable
Default
Software auto-update is enabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
Operating mechanism
The software auto-update feature automatically propagates the current software images of the master in the cloud cluster to member devices you are adding to the cloud cluster. Those devices will join the cloud cluster again after software image synchronization.
When the software auto-update feature is disabled, new devices can join the cloud cluster even if their software images are different from those of the master in the cloud cluster. However, the software image differences might affect the running of some cloud cluster features on the new member devices. As a best practice to avoid such issue, enable the software auto-update feature.
Prerequisites
To ensure a successful software update, verify that the new device you are adding to the cloud cluster has sufficient storage space for the new software images. If the device does not have sufficient storage space, the cloud cluster automatically deletes the current software images of the device. If the reclaimed space is still insufficient, the device cannot complete the auto-update. You must reboot the device, and then access the BootWare menus to delete unused files.
Examples
# Enable software auto-update.
<Sysname> system-view
[Sysname] cloud-cluster auto-update enable
cloud-cluster configuration active
Use cloud-cluster configuration active to activate cloud cluster configuration.
Syntax
cloud-cluster configuration active
Views
System view
Predefined user roles
network-admin
Usage guidelines
Application scenarios
After editing cloud cluster configuration, for the new configuration to take effect, you must execute this command to activate the configuration.
Recommended actions
As a best practice, plan the entire cluster and configure all member device settings (such as member IDs, IPs, roles, IPs of members to be added to the cluster, and interfaces for binding) in advance. Connect cables of the physical cluster and then execute this command to form the cluster directly.
Restrictions and guidelines
Refer to the prompt information on the device to see whether the device reboots automatically after this command is executed.
Examples
# After configuring the cluster member device settings, activate the configuration. (The following configuration information is for illustration only.)
<Sysname> system-view
[Sysname] cloud-cluster member 1 renumber 2
[Sysname] cloud-cluster configuration active
New cluster configuration:
cloud-cluster service-cluster domain 0
cloud-cluster hello cloud-timeout 7 service-timeout 10
cloud-cluster member 2
role manager-worker
cluster-link bind interface GigabitEthernet 2/0/2
cluster-link bind interface GigabitEthernet 2/0/3
The system will activate and save the configuration, and it might do a restart. Continue? [Y/N]: y
The current configuration will be written to the device. Are you sure? [Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Saved the current configuration to mainboard device successfully.
Related commands
cloud-cluster member remember
cloud-cluster service-cluster domain
cluster-link bind interface
ip address
join cluster
cloud-cluster link-delay
Use cloud-cluster link-delay to set a delay for the container cluster interfaces to report link down events.
Use undo cloud-cluster link-delay to restore the default.
Syntax
cloud-cluster link-delay interval
undo cloud-cluster link-delay
Default
The delay interval is 0. The container cluster interfaces report link down events without delay.
Views
System view
Predefined user roles
network-admin
Parameters
interval: Sets a delay interval in milliseconds. The value range is 0 to 3000. If you set the interval to 0, link down events are reported without delay.
Usage guidelines
Application scenarios
To prevent frequent container cluster splits and merges upon frequent link flappings within the container cluster, use this command to configure the container cluster interfaces to delay reporting link down events.
Operating mechanism
Container cluster links have two physical states, up and down. Container cluster interfaces do not delay reporting link up events. They report link up events immediately after the container cluster links come up.
After you set a delay time for container cluster link down report, a container cluster interface does not report a link down event to the container cluster immediately after its link goes down. If the container cluster link is still down when the delay time is reached, the interface reports the link down event to the container cluster.
Restrictions and guidelines
This command takes effect immediately after configuration. You do not need to use the cloud-cluster configuration active command to activate the configuration.
Examples
# Set the delay time to 300 milliseconds for container cluster link down report.
<Sysname> system-view
[Sysname] cloud-cluster link-delay 300
cloud-cluster member
Use cloud-cluster member to enter cloud cluster member view.
Use undo cloud-cluster member to clear all configuration in cloud cluster member view.
Syntax
cloud-cluster member member-id
undo cloud-cluster member member-id
Default
The member ID is 1.
Views
System view
Predefined user roles
network-admin
Parameters
member-id: Specifies the member ID for the device in the cluster. The value range is 1 to 2.
Usage guidelines
Application scenarios
A member ID is the unique identifier used to identify a device in a cluster.
Operation mechanism
You can only use this command to enter a specific cloud cluster member view that already exists. To edit the member ID for a device, use the cloud-cluster member renumber command.
Examples
# Enter the cloud cluster member view for member ID 1.
<Sysname> system-view
[Sysname] cloud-cluster member 1
[Sysname-ccluster-member-1]
Related commands
cloud-cluster member renumber
cloud-cluster configuration active
cloud-cluster member renumber
Use cloud-cluster member renumber to edit the member ID for a device.
Use undo cloud-cluster member renumber remove the editing of the member ID for a device.
Syntax
cloud-cluster member member-id renumber new-member-id
undo cloud-cluster member member-id renumber
Default
The member ID is 1.
Views
System view
Predefined user roles
network-admin
Parameters
member-id: Specifies the current member ID of the device. The value range is 1 to 2.
new-member-id: Specifies the new member ID of the device. The value range is 1 to 2.
Usage guidelines
Application scenarios
A device cannot be added to the cluster if the device member ID is the same as the member ID of a device that is already in the cluster. To add the device into the cluster, first use this command to edit the member ID.
Restrictions and guidelines
This command can inherits configuration in the member ID view to the new member ID view. For the configuration to take effect, save the configuration and reboot the device that the original member ID identifies.
The undo cloud-cluster member renumber command can only remove the new member ID configured in this configuration progress. The new member ID configuration cannot be removed once the device reboots.
After you execute this command, you must execute the cloud-cluster configuration active command. The configuration takes effect together with other cloud cluster settings.
Examples
# Change the device member ID from 1 to 2.
<Sysname> system-view
[Sysname] cloud-cluster member 1 renumber 2
This command will take effect after the cloud cluster configuration is activated. The command might result in configuration change or loss when it takes effect. Continue? [Y/N]:y
[Sysname]
Related commands
cloud-cluster configuration active
cloud-cluster member
cloud-cluster service-cluster domain
Use cloud-cluster service-cluster domain to assign a container cluster domain ID to each member device or to a container cluster.
Use undo cloud-cluster service-cluster domain to restore the default.
Syntax
cloud-cluster service-cluster domain domain-id
undo cloud-cluster service-cluster domain
Default
The container cluster domain ID is 0.
Views
System view
Predefined user roles
network-admin
Parameters
domain-id: Specifies a domain ID for the container cluster. The value range is 0 to 4294967295.
Usage guidelines
Application scenarios
You can deploy multiple container clusters on the same cloud cluster network. One container cluster forms one container cluster domain. Container cluster domain IDs uniquely identify container clusters and prevent container clusters from interfering with one another. A container cluster has only one container cluster domain ID. Modify the domain IDs of container clusters according to the network plan and avoid make random changes.
Restrictions and guidelines
After you execute this command to set a container cluster domain ID and configure other settings, you must execute the cloud-cluster configuration active command. The configuration takes effect with other cloud cluster settings.
Examples
# Set the container cluster domain ID to 1.
<Sysname> system-view
[Sysname] cloud-cluster service-cluster domain 1
The configuration will take effect at the next startup.
Operation succeeded.
Related commands
cloud-cluster configuration active
cloud-cluster service-cluster isolate master
Use cloud-cluster service-cluster isolate master to isolate the master container in the container master.
Syntax
cloud-cluster service-cluster isolate master
Views
System view
Predefined user roles
network-admin
Usage guidelines
Application scenarios
When the master container in a cluster requires an upgrade or hardware replacement, or encounters a failure, you can perform this task to proactively isolate the master. This allows the cluster to promptly elect a new master container to take over tasks.
Operating mechanism
After you execute this command, the system operates as follows:
1. Automatically sets the management Ethernet interface of the master container as a MAD reserved port temporarily.
2. Notifies the container cluster to elect a new master container.
3. Disables all interfaces on the device, except the MAD reserved ports. The state of the disabled port changes to MAD down. MAD reserved ports include the management Ethernet interface and those configured by the mad exclude interface command.
4. Sets the state of the master container to be isolated to Recovery.
Prerequisites
As a best practice, before isolating the master container, use the ip address ip-address { mask-length | mask } cluster-member member-id command to configure an IP address for the management Ethernet interface for each container in the container cluster. This allows access to the container if it gets isolated or splits off.
Restrictions and guidelines
· Note that executing this command will cause the container cluster to split and isolate the master container from the cluster. Before you execute this command, make sure the links of the master container have backup links.
· To restore the isolated master container to its normal working state, manually executing the reboot command. After the reboot, the container will join other containers as a standby container.
· When the cloud cluster has only one device, do not execute this command, because this command will prevent the cluster from operating.
Examples
# Isolate the master container in the container cluster that contains multiple members.
<Sysname> system-view
[Sysname] cloud-cluster service-cluster isolate master
As a best practice for members of the main control board cluster to access the container after isolation or splitting, first use the "ip address cluster-member" command under the M-GigabitEthernet port to specify an IP address for the members.
Isolating the master device will perform MAD down on the device's interfaces except for the M-GigabitEthernet and the interface specified by the mad exclude interface command.
Are you sure you want to isolate the device? [Y/N]:
# Isolate the master container in the container cluster that contains only one member.
<Sysname> system-view
[Sysname] cloud-cluster service-cluster isolate master
The current cluster contains only one master device. Continue? [Y/N]:n
Related commands
display mad verbose
ip address (Network Connectivity Command Reference)
mad exclude interface
cloud-cluster service-cluster mac-address persistent
cloud-cluster service-cluster mac-address persistent to configure container cluster bridge MAC persistence.
undo cloud-cluster service-cluster mac-address persistent to enable the container cluster to change its bridge MAC address as soon as the address owner leaves.
Syntax
cloud-cluster service-cluster mac-address persistent { always | timer }
undo cloud-cluster service-cluster mac-address persistent
Default
The container cluster bridge MAC address does not change after the address owner leaves.
Views
System view
Predefined user roles
network-admin
Parameters
always: Enables the container cluster bridge MAC address to be permanent. The container cluster bridge MAC address does not change after the address owner leaves.
timer: Enables the container cluster bridge MAC address to remain unchanged for 6 minutes after the address owner leaves. If the address owner rejoins the container cluster within the time limit, the container cluster bridge MAC address does not change. If the address owner does not rejoin within the time limit, the container cluster uses the bridge MAC address of the current primary container as the bridge MAC address.
Usage guidelines
Application scenarios
A container cluster uses the bridge MAC address of its primary container as the container cluster bridge MAC address. When the primary container changes, the container cluster bridge MAC address changes. Some protocols (for example, STP) use the container cluster bridge MAC address to identify a device, and bridge MAC address changes might cause transient traffic disruption. You can use this command to configure container cluster bridge MAC persistence.
Operating mechanism
You can configure the container cluster bridge MAC address to remain unchanged for 6 minutes after the address owner leaves. If the address owner rejoins the container cluster within 6 minutes, the container cluster bridge MAC address does not change. If the address owner does not rejoin within 6 minutes, the container cluster uses the bridge MAC address of the current primary container as the container cluster bridge MAC address.
You can configure the container cluster bridge MAC address to be permanent. The container cluster bridge MAC address does not change after the address owner leaves.
If you do not use this command, a container cluster changes its bridge MAC address as soon as the address owner leaves. The container cluster uses the bridge MAC address of the current primary container as the container cluster bridge MAC address.
Restrictions and guidelines
Container cluster merge fails if any two member containers have the same bridge MAC address. Container cluster bridge MAC addresses do not affect container cluster merge.
If a container cluster has cross-member aggregate links, do not use the undo cloud-cluster service-cluster mac-address persistent command. Use of this command might cause traffic disruption.
This command takes effect immediately after configuration. You do not need to use the cloud-cluster configuration active command to activate the configuration.
Examples
# Enable the container cluster bridge MAC address to be permanent.
<Sysname> system-view
[Sysname] cloud-cluster service-cluster mac-address persistent always
cloud-cluster service-cluster mad domain
Use cloud-cluster service-cluster mad domain to assign a MAD domain ID to container clusters.
Use undo cloud-cluster service-cluster mad domain to restore the default.
Syntax
cloud-cluster service-cluster mad domain domain-id
undo cloud-cluster service-cluster mad domain
Default
The MAD domain ID is 0 for container clusters.
Views
System view
Predefined user roles
network-admin
Parameters
domain-id: Specifies a MAD domain ID for container clusters. The value range is 0 to 4294967295.
Usage guidelines
Operating mechanism
The container clusters in a cloud cluster use the assigned MAD domain ID only for MAD. All member devices in the cloud cluster share this MAD domain ID. Upon receiving a MAD packet, a container compares the MAD domain ID in the packet with the local MAD domain ID. The container processes the MAD packet only if the two MAD domain IDs are the same. Containers in the same cloud cluster must use the same MAD domain ID. To ensure the correct running of MAD, make sure each cloud cluster uses a unique MAD domain ID.
You can change the MAD domain ID of container clusters by using the cloud-cluster service-cluster mad domain or mad enable command. The MAD domain IDs configured by using these commands overwrite each other. As a best practice, set the MAD domain ID for container clusters according to the network plan, and do not change the MAD domain ID unless necessary.
Examples
Set the MAD domain ID to 1 for container clusters.
<Sysname> system-view
[Sysname] cloud-cluster service-cluster mad domain 1
Related commands
cloud-cluster enable
cloud-cluster configuration active
mad enable
cloudcluster-optimize wlan reliable-access
Use cloudcluster-optimize wlan reliable-access to enable cloud cluster optimization for reliable WLAN access.
Use undo cloudcluster-optimize wlan reliable-access to disable cloud cluster optimization for WLAN access.
Syntax
cloudcluster-optimize wlan reliable-access
undo cloudcluster-optimize wlan reliable-access
Default
cloud cluster optimization for WLAN access is enabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
Use this command to guarantee reliable AP and client access. This command accelerates cloud cluster master election, new member joining, and cloud cluster member role change to prevent cloud cluster events from causing unstable AP and client access.
Examples
# Enable cloud cluster optimization for reliable WLAN access.
<Sysname> system-view
[Sysname] cloudcluster-optimize wlan reliable-access
cluster-link bind interface
Use cluster-link bind interface to bind container cluster links to physical interfaces.
Use undo cluster-link bind interface to unbind container cluster links from physical interfaces.
Syntax
cluster-link [ control | data ] bind interface interface-type interface-number
undo cluster-link [ control | data ] bind interface interface-type interface-number
Default
Container cluster links are not bound to any physical interface.
Views
Cloud cluster member view
Predefined user roles
network-admin
Parameters
[ control | data ]: Specifies the container cluster link to operate as a control link or a data link. If you do not specify this keyword, the link operates as a control and data link.
· control: Specifies the link to operate as a control link. The control link transfers cluster protocol packets for devices in the cloud cluster.
· data: Specifies the link to operate as a data link. The data link transfers service packets for devices in the cloud cluster.
interface-type interface-number: Specifies the type and number for the physical interface. For information on which ports on devices of various models can be used as physical ports for the cluster, see the relevant manual of the product.
Usage guidelines
|
|
CAUTION: The undo cluster-link bind command might cause the cluster to split. Use this command with caution. |
Application scenarios
A physical cluster communicates in Layer 3 based on member IP addresses. As long as the routes between the member device IPs are reachable, the physical cluster can exchange protocol messages and maintain its operation.
To use a container cluster, you must use this command to bind physical interfaces. A container cluster link requires one control link and one data link. The bound interfaces interact with the container cluster to control packets and data packets forwarded between devices.
Operation mechanism
When this command is executed, the cluster module automatically shuts down the specified interface (the same effect as executing the shutdown command) automatically and switches the bound physical interface to the cluster physical interface. After a successful switch, the system automatically enables the interface (the same effect as executing the undo shutdown command). The configuration on the interface will be restored to the default settings.
You can execute this command multiple times to bind multiple physical interfaces to the control or data channel. The physical interfaces will share the load of forwarding packets.
Restrictions and guidelines
After this command is configured, to edit the link type for a cluster physical interface, you must first unbind the link from the interface and then change the link type.
After you execute this command, you must execute the cloud-cluster configuration active command for the configuration to take effect together with other cloud cluster settings.
When you bind container cluster links to physical interfaces, follow these restrictions and guidelines:
· When you bind a container cluster link to a physical interface, make sure the physical interface is not a management port.
· The device supports up to eight container cluster links.
· When multiple container cluster links are required, use one of the following methods to create them:
¡ Do not specify the [ control | data ] parameter for all of the container cluster links. Those links operate as control and data links.
¡ Configure some of the container cluster links as control links and the other container cluster links as data links. If you use this method, the container cluster operates correctly only if the device has both data links and control links.
· When you configure multiple container cluster links on a single device, interfaces bound to the same type of container cluster links must have the same physical bandwidth. For example, the interfaces bound to two control links are GE ports, and the interfaces bound to two links are 10GE ports.
Examples
# Bind the cluster link to interface GigabitEthernet 1/0/1.
<Sysname> system-view
[Sysname] cloud-cluster member 1
[Sysname-ccluster-member-1] cluster-link bind interface gigabitethernet 1/0/1
The system will shut down and then bring up the interface. Continue? [Y/N]: y
# Unbind the cluster link from the physical interface.
<Sysname> system-view
[Sysname] cloud-cluster member 1
[Sysname-ccluster-member-1] undo cluster-link bind interface GigabitEthernet 1/0/1
Be cautious. If this is the only link in the cluster control channel, the unbind operation will cause the cloud cluster to split. Continue anyway? [Y/N]: y
Related commands
cloud-cluster configuration active
cloud-cluster member
display cloud-cluster
Use display cloud-cluster to display information about the physical cluster.
Syntax
display cloud-cluster [ member member-id ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
member member-id: Specifies a member device in the cluster by its ID. The value range is 1 to 2.
verbose: Displays detailed information about the physical cluster. To display brief information about the physical cluster, do not specify this keyword.
Examples
# Display brief information about the physical cluster.
<Sysname> display cloud-cluster
Manager list:
Member ID Role Member IP State Heartbeat(ms)
1 Leader 1.1.1.1 online 0
2 Follower 1.1.1.2 online 700
Worker list:
Member ID State Heartbeat(ms) Joined at
1 online 100 2023/1/2 22:10:34
2 online 200 2023/1/2 22:10:34
# Display detailed information about the physical cluster.
<Sysname> display cloud-cluster verbose
Member ID : 1
Role : Manager(Leader)
Member IP : 1.1.1.1/24
Join-cluster IP : 1.1.1.1
Heartbeat(ms) : 700
Listen port : 3536
Joined at : 2023/1/2 22:10:34
Container ID : 1
Container UUID: 0cfadd7138c6
Created at : 2023/1/2 22:10:34
Image : cd934004f53f
Name : cluster1
Location : 1
State :Normal
Member ID : 2
Role : Manager(Follower)
Member IP : 1.1.1.2/24
Join-cluster IP : 1.1.1.1
Heartbeat(ms) : 600
Listen port : 3536
Joined at : 2023/1/2 22:10:34
Container ID : 2
Container UUID: df687a7d4dfa
Created at : 2023/1/2 22:10:34
Image : cd934004f53f
Name : cluster2
Location : 2
State : Normal
Table 1 Command output
|
Field |
Description |
|
Manager list |
Manager member information. |
|
Worker list |
Worker member information. |
|
Member ID |
Cluster member ID. You can identify a physical device by its member ID. |
|
Role |
Role of the device in the cluster: · Manager(Leader)—The device is the leader manager and is a worker. · Manager(Follower)—The device is the follower manager and is a worker. · Manager(Candidate)—Leader election is in progress. The role of the device has not been determined. |
|
IP address of the member device. |
|
|
Join-cluster IP |
IP address that the member device used to join the cluster. The IP address is the IP address of another member device in the cluster. |
|
Heartbeat(ms) |
Time that have elapsed since the last heartbeat interaction with other cluster members, in milliseconds. |
|
Listen port |
Port that listens to packets from other member devices in the cluster. This port ensures packet exchanges between member devices in the cluster. |
|
Joined at |
Time when the member device joined the cluster. Supported time formats include: · YYYY-MM-DD HH:MM:SS · YYYY-MM-DD HH:MM:SS UTC±HH:MM DST · YYYY-MM-DD HH:MM:SS UTC±HH:MM · YYYY-MM-DD HH:MM:SS DST UTC±HH:MM indicates that a time zone is configured with the clock timezone command. DST indicates that the daylight saving time is configured with the clock summer-time command. |
|
Container ID |
ID of the container running on the member device. |
|
UUID that the Linux system assigned to the container. Container UUIDs are for internal use only. |
|
|
Created at |
Time when the container was created. Supported time formats include: · YYYY-MM-DD HH:MM:SS · YYYY-MM-DD HH:MM:SS UTC±HH:MM DST · YYYY-MM-DD HH:MM:SS UTC±HH:MM · YYYY-MM-DD HH:MM:SS DST UTC±HH:MM indicates that a time zone is configured with the clock timezone command. DST indicates that the daylight saving time is configured with the clock summer-time command. |
|
Image |
Name of the image used to start the container. |
|
Name |
Container name. |
|
Location |
Member device on which the container runs. In the current software version, this field displays the ID of the member device. |
|
State |
Running state of the container: · Normal—The container is operating correctly. · Mad—Two primary containers exist. · Isolate—The container is isolated. |
Related commands
cloud-cluster member
display cloud-cluster configuration
Use display cloud-cluster configuration to display cloud cluster configuration information.
Syntax
display cloud-cluster service-cluster container [ container-id ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
member member-id: Specifies a member device in the cluster by its ID. The value range is 1 to 2. If you do not specify any member device, this command displays configuration information for all member devices in the cluster.
Examples
# Display cloud cluster configuration information.
<Sysname> display cloud-cluster configuration
Cloud-cluster: Enable
Service cluster domain ID: 1
Service cluster mad domain ID: 0
MAC persistent for service cluster: Always
Cloud-cluster hello timeout: 7 s
Service-cluster hello timeout: 10 s
Cloud-cluster auto merge: Enable
Cloud-cluster auto update: Enable
Cloud-cluster link-delay: 0 ms
Member ID: 1
Role: Manager,Worker
Member IP: 1.1.1.1/24
Join-cluster IP: 1.1.1.1
Cluster-link interfaces:
Control links: GigabitEthernet1/0/1
GigabitEthernet1/0/2
Data links : GigabitEthernet1/0/1
GigabitEthernet1/0/2
Table 2 Command output
|
Field |
Description |
|
Whether the physical cluster mode is enabled. · Enable—The device is in cluster mode. |
|
|
Member ID |
Cluster member ID. You can identify a physical device by its member ID. |
|
Role |
Role of the device in the physical cluster. Supported roles include: · Manager—Manager in the physical cluster. · Worker—Worker in the physical cluster. |
|
Member IP |
IP address of the member. |
|
Join-cluster IP |
IP address that the member used to join the cluster. |
|
Cluster-link interfaces |
Physical ports used for cluster establishment. |
|
Data links |
Physical ports that provide data links. |
|
Service cluster domain ID |
Container cluster domain ID. Each container cluster has a unique container cluster domain ID. A container can join a container cluster only if its cluster domain ID is the same as that of the existing members in the container cluster. |
|
Service cluster mad domain ID |
MAD domain ID for the container cluster. Each MAD domain has a unique domain ID. Upon receiving a MAD packet, the device compares the MAD domain ID in the packet with the local MAD domain ID. The device processes the MAD packet only if the two MAD domain IDs are the same. |
|
MAC persistent for service cluster |
Bridge MAC persistence setting for the container cluster. Supported values include: · None—Bridge MAC address of the current master replaces the original bridge MAC address as soon as the owner of the original address leaves. · Always—Bridge MAC address of the cluster does not change after the address owner leaves. · Timer—Bridge MAC address of the cluster remains unchanged for 6 minutes after the address owner leaves. |
|
Cloud-cluster hello timeout |
Hello timeout time for members of the physical cluster, in milliseconds. |
|
Service-cluster hello timeout |
Hello timeout time for members of the container cluster, in milliseconds. |
|
Cloud-cluster auto merge |
Enabling status of the auto-merge feature: · Enable—The feature is enabled. · Disable—The feature is disabled. |
|
Cloud-cluster auto update |
Enabling status of the software auto-update feature: · Enable—The feature is enabled. · Disable—The feature is disabled. |
|
Cloud-cluster link-delay |
Delay timer for the container cluster interfaces to report link down events, in milliseconds. |
display cloud-cluster service-cluster container
Use display cloud-cluster service-cluster container to container information of the container cluster.
Syntax
display cloud-cluster service-cluster container [ container-id ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
container-id: Specifies a container by its ID. The value range is 1 to 2. If you do not specify any container, this command displays information about all containers in the container cluster.
verbose: Displays detailed container information. To display brief container information, do not specify this keyword.
Examples
# Display brief information about all containers in the container cluster.
<Sysname> display cloud-cluster service-cluster container
Container ID Slot ID Member ID Role Status
*+1 1 1 Master Online
2 2 2 Standby Online
---------------------------------------------------------------
* indicates the device is the master.
+ indicates the device through which the user logs in.
# Display detailed information about all containers in the container cluster.
<Sysname> display cloud-cluster service-cluster container verbose
Service-cluster name: System
Domain ID : 0
Cluster Bridge MAC: 00e0-fc00-1001
Container ID : 1
Member ID : 1
Slot ID : 1
Health : Healthy(100)
Bridge MAC : 00e0-fc00-1001
CPU MAC : 00f0-fc00-1001
Control links: GigabitEthernet1/0/1(UP)
GigabitEthernet1/0/2(DOWN)
Data links : GigabitEthernet1/0/3(UP)
Cluster connection : Reachable
Status : Online
Self hello timeout (ms) : N/A
Master hello timeout (ms): N/A
Table 3 Command output
|
Field |
Description |
|
Service-cluster name |
Name of the container cluster. In the current software version, only System is supported. |
|
Domain ID of the container cluster. You can identify a container cluster by its domain ID. |
|
|
Cluster Bridge MAC |
Bridge MAC address of the cluster. |
|
The cluster assigns an ID to a container when the container is created. |
|
|
Cluster member ID. You can identify a physical device by its member ID. If the device is the master device, an asterisk (*) will be displayed in front of the member ID. If the device is being operated by the user, a plus sign (+) will be displayed in front of the member ID. |
|
|
Slot ID |
Global slot number. |
|
Role |
Role of the member container in the cluster: · Master—Master container. · Standby—Standby container. |
|
Health |
System health state: · Healthy(100)—The system is healthy. · Unhealthy(n)—The system is unhealthy. If the value of n gets greater, the system health state worsens. |
|
Bridge MAC |
|
|
CPU MAC |
CPU MAC address of the member container. |
|
Control links |
Physical ports that provide control links, and their physical status. |
|
Data links |
Physical ports that provide data links, and their physical status. |
|
Cluster connection |
Whether the cluster agent service and the cluster manager can reach each other: · Reachable: They can reach each other. · Unreachable: They cannot reach each other. |
|
Status |
Running state of the container: · Online—The container is online. · Offline—The container is offline. · MAD down—The container is forbidden. |
|
Self hello timeout (ms) |
Hello timeout time for the container, in milliseconds. The container sends hello packets to the master container at specific intervals. This field displays N/A for the master container. |
|
Master hello timeout (ms) |
Hello timeout time for the master container, in milliseconds. The master container sends hello packets to the container at specific intervals. This field displays N/A for the master container. |
|
* indicates the device is the master |
This symbol indicates that the device is the master device. |
|
+ indicates the device through which the user logs in |
This symbol indicates that the device is being operated by the user. |
Related commands
cloud-cluster member
display mad
Use display mad to display MAD settings.
Syntax
display mad [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
verbose: Displays detailed MAD configuration information. If you do not specify this keyword, the command displays brief MAD configuration information.
Examples
# Display brief MAD configuration information.
<Sysname> display mad
MAD LACP enabled.
# Display detailed MAD configuration information.
<Sysname> display mad verbose
Multi-active recovery state: No
Excluded ports (user-configured):
Bridge-Aggregation4
Vlan-interface999
Excluded ports (system-configured):
Service-cluster physical interfaces:
Ten-GigabitEthernet1/0/1
Ten-GigabitEthernet1/0/2
Ten-GigabitEthernet2/0/1
Ten-GigabitEthernet2/0/2
Member interfaces of excluded interface Bridge-Aggregation 4:
Ten-GigabitEthernet1/0/4
Ten-GigabitEthernet2/0/4
MAD LACP enabled interface: Bridge-Aggregation 1
MAD status : Normal
Member ID Port MAD status
1 Ten-GigabitEthernet1/0/5 Normal
2 Ten-GigabitEthernet2/0/5 Normal
Table 4 Command output
|
Field |
Description |
|
MAD LACP enabled. |
Status of LACP MAD. This field displays MAD LACP disabled if LACP MAD is disabled. |
|
Multi-active recovery state |
Whether the container cluster is in Recovery state: · Yes—The container cluster is in Recovery state. When MAD detects that a container cluster has split into multiple container clusters, it allows one container cluster to forward traffic. All the other container clusters are set to the Recovery state. In Recovery state, MAD shuts down all common network interfaces in the container cluster except for the system- and user-excluded network interfaces. · No—The container cluster is not in Recovery state. It is active and can forward traffic. |
|
Excluded ports (user-configured) |
Network interfaces manually configured to not shut down when the container cluster transits to the Recovery state. |
|
Excluded ports (system-configured) |
Network interfaces set to not shut down by the system when the container cluster transits to the Recovery state. These interfaces are not manually configured. · IRF physical interfaces: Physical interfaces in the container cluster. · Member interfaces of excluded interface Bridge-Aggregation interface-number: Member interfaces of a Layer 2 aggregate interface if the aggregate interface is excluded from the MAD shutdown action. · Member interfaces of excluded interface Route-Aggregation interface-number: Member interfaces of a Layer 3 aggregate interface if the aggregate interface is excluded from the MAD shutdown action. |
|
MAD LACP enabled interface |
Interface on which LACP MAD is enabled. This field is displayed for each interface enabled with LACP MAD. This field displays MAD LACP disabled if LACP MAD is disabled. |
|
MAD status |
LACP MAD operating status: · Normal—LACP MAD is operating correctly. · Faulty—LACP MAD is not operating correctly. Verify the following items: ¡ Verify that the ports on LACP MAD links are up. ¡ Verify that the intermediate device supports LACP MAD. ¡ Verify that all member devices have member ports used for LACP MAD. |
|
Member ID Port MAD status |
LACP MAD details: · Member ID—ID of the member in the container cluster. · Port—Member ports of the aggregate interface used for LACP MAD. · MAD status—LACP MAD operating state on a member port. Values include Normal and Faulty. |
display wlan ap statistics cloud-cluster switch-over-state
Use display wlan ap statistics cloud-cluster switch-over-state to display the status of the flag bits during the master/standby switchover process in the cloud cluster, helping users determine the current logic process of master/standby switchover.
Syntax
display wlan ap statistics cloud-cluster switch-over-state [ history ]
Views
Any view
Predefined user roles
network-admin
Parameters
history: Displays the logs for master/standby switchover-related flag bits.
Usage guidelines
Use this command to view the status, set time, and flip time of the cloud cluster flag bits, thereby determining the current logic process of master/standby switchover.
Examples
# Display the status of the flag bits during the master/standby switchover process in the cloud cluster.
<Sysname> display wlan ap statistics cloud-cluster switch-over-state
Switch-over flag Current value Last change at
AgentRespEnable FALSE 03-21/07:57:38
UpgradingFlag FALSE 03-21/07:57:36
DenyApOnline FALSE 03-21/07:57:38
CurrentMasterLIP 8 03-21/07:57:37
Table 1 Command output
|
Field |
Description |
|
Switch-over flag |
Master/standby switchover flag bits. Available flag bits include: · AgentRespEnable—Agent response flag, activated during cold standby when the main board is removed or during hot standby when any board is removed. During this period, CAPWAP tunnel response agent is activated to prevent AP disconnections. It can be used to intercept command deployment. The flag is set to enabled during master/standby switchover or in case of board removal, and is set to disabled after the master/standby switchover is complete. · UpgradingFlag—Upgrading flag, activated during master/standby switchover. The flag is set to enabled when standby device initialization starts, and is set to disabled after master/standby switchover is complete. · DenyApOnline—Association denial flag, used to intercept AP associations during the master/standby switchover process. The flag is set to enabled when standby device initialization starts, and is set to disabled after master/standby switchover is complete. · CurrentMasterLIP—Board number of the current master device. |
|
Current value |
Current value of the flag, which indicates the status of the function represented by the flag. The values of the AgentRespEnable, UpgradingFlag, and DenyApOnline are TRUE or FALSE, where TRUE represents Enabled and FALSE represents Disabled. For CurrentMasterLIP, this field displays the board number of the current master device. |
|
Last change at |
Time when the flag bit value was last changed. |
# Display the logs for master/standby switchover-related flag bits.
<Sysname> display wlan ap statistics cloud-cluster switch-over-state history
Switch-over flag : AgentRespEnable
Current value : FALSE
History:
10-10/15:51:27 : FALSE
10-10/15:50:12 : TRUE
--------------------------------------------------
Switch-over flag : UpgradingFlag
Current value : FALSE
History:
10-10/15:53:11 : FALSE
10-10/15:52:22 : TRUE
--------------------------------------------------
Switch-over flag : DenyApOnline
Current value : TRUE
History:
10-10/15:56:21 : TRUE
10-10/15:55:33 : FALSE
--------------------------------------------------
Switch-over flag : CurrentMasterLIP
Current value : 8
History:
03-21/07:57:36 : 8
Table 2 Command output
|
Field |
Description |
|
Switch-over flag |
Master/standby switchover flag bits. Available flag bits include: · AgentRespEnable—Agent response flag, activated during cold standby when the main board is removed or during hot standby when any board is removed. During this period, CAPWAP tunnel response agent is activated to prevent AP disconnections. It can be used to intercept command deployment. The flag is set to enabled during master/standby switchover or in case of board removal, and is set to disabled after the master/standby switchover is complete. · UpgradingFlag—Upgrading flag, activated during master/standby switchover. The flag is set to enabled when standby device initialization starts, and is set to disabled after master/standby switchover is complete. · DenyApOnline—Association denial flag, used to intercept AP associations during the master/standby switchover process. The flag is set to enabled when standby device initialization starts, and is set to disabled after master/standby switchover is complete. · CurrentMasterLIP—Board number of the current master device. |
|
Current value |
Current value of the flag, which indicates the status of the function represented by the flag. The values of the AgentRespEnable, UpgradingFlag, and DenyApOnline are TRUE or FALSE, where TRUE represents Enabled and FALSE represents Disabled. For CurrentMasterLIP, this field displays the board number of the current master device. |
|
History |
Flag bit logs. |
join-cluster
Use join-cluster to specify a cluster IP address to add the device into the cluster.
Use undo join-cluster to remove the cluster IP configuration. The device will leave the cluster.
Syntax
join-cluster ip ipv4-address
undo join-cluster
Default
The cluster IP address is not specified. In this case, if you activate the cloud cluster configuration on the device, the device elects itself to act as the leader.
Views
Cloud cluster member view
Predefined user roles
network-admin
Parameters
ip ipv4-address: Specifies the IP address of a member device in the target cluster.
Usage guidelines
Application scenarios
To create a physical cluster, you must execute this command on all member devices of the physical cluster. To configure a device as the leader of the physical cluster, do not configure this command or use the member IP address of the device as the cluster IP address. The device will create a cluster with itself acting as the leader and you must configure this command on other follower devices.
Operation mechanism
When you create a cluster, first select a device to act as the leader and select the subnet for internal cluster communication. Configure and enable the leader. When adding other devices into the cluster, follow these guidelines:
· As a best practice, specify the leader IP address in this command. A new device can establish connection with the leader directly to join the cluster.
· If you specify the IP address of another member device in the cluster in this command, the new device sends connection request to the member device. Then, the member device transfers the request to the leader and the new device can establish connection with the leader to join the cluster.
If the specified IP address cannot be reached, the device cannot join the cluster. In this case, the display cloud-cluster command displays no cluster information and the container on the device operates for the single device as the master.
To ensure that the device is removed from the cluster, you must first execute the undo join cluster command and then execute the cloud-cluster configuration active command. During the removal, the configuration, data, and typology of the current cluster will be deleted from the device and container-related configuration will be retained. The device will create a cluster with itself acting as the leader and the container on the device operates as the master.
To add a member device that has been isolated from the cluster, log in to the device and execute the join cluster command. Save the configuration and reboot the device, and the device will be added to the cluster again.
Restrictions and guidelines
After you execute this command, you must execute the cloud-cluster configuration active command for the configuration to take effect together with other cloud cluster settings.
Examples
# Add the device to the cloud cluster that contains the member device with IP address 1.1.1.1.
<Sysname> system-view
[Sysname] cloud-cluster member 1
[Sysname-ccluster-member-1] join-cluster ip 1.1.1.1
# Isolate the device with member ID 2 from the cluster.
<Sysname> system-view
[Sysname] cloud-cluster member 2
[Sysname-ccluster-member-2] undo join-cluster
Member 2 will be isolated from the cluster with its network interfaces disabled. Continue? [Y/N]: y
Related commands
cloud-cluster member
cloud-cluster configuration active
member-ip
mad enable
Use mad enable to enable LACP MAD.
Use undo mad enable to disable LACP MAD.
Syntax
mad enable
undo mad enable
Default
LACP MAD is disabled.
Views
Aggregate interface view
Predefined user roles
network-admin
Usage guidelines
LACP MAD requires a device that supports extended LACPDUs for MAD to act as the intermediate device. You must set up a dynamic link aggregation group that spans all cloud cluster member devices between the container cluster and the intermediate device. To enable dynamic link aggregation, configure the link-aggregation mode dynamic command on the aggregate interface.
If one container cluster uses another container cluster as the intermediate device for LACP MAD, you must assign the two container clusters different domain IDs for correct split detection. False detection causes container cluster split.
You can change the MAD domain ID by using one of the following commands: cloud-cluster service-cluster mad domain or mad enable. Only the most recent configuration takes effect. You must configure the MAD domain ID according to the network plan, and do not change it unless necessary.
Examples
# Enable LACP MAD on Bridge-Aggregation 1, a Layer 2 dynamic aggregate interface.
<Sysname> system-view
[Sysname] interface bridge-aggregation 1
[Sysname-Bridge-Aggregation1] link-aggregation mode dynamic
[Sysname-Bridge-Aggregation1] mad enable
You need to assign a domain ID (range: 0-4294967295)
[Current domain ID is: 0]: 1
The assigned domain ID is: 1
# Enable LACP MAD on Layer 3 dynamic aggregate interface 1.
<Sysname> system-view
[Sysname] interface route-aggregation 1
[Sysname-Route-Aggregation1] link-aggregation mode dynamic
[Sysname-Route-Aggregation1] mad enable
You need to assign a domain ID (range: 0-4294967295)
[Current domain ID is: 0]: 1
The assigned domain ID is: 1
Related commands
cloud-cluster service-cluster mad domain
mad exclude interface
Use mad exclude interface to exclude an interface from being shut down when the container cluster transits to the Recovery state upon detection of a multi-active collision.
Use undo mad exclude interface to configure the container cluster to shut down an interface when it transits to the Recovery state upon detection of a multi-active collision.
Syntax
mad exclude interface interface-type interface-number
undo mad exclude interface interface-type interface-number
Default
Except for the network interfaces automatically excluded by the system, all network interfaces are shut down when the container cluster transits to the Recovery state. The system automatically excludes the following network interfaces from being shut down:
· Container cluster physical interfaces.
· Member interfaces of an aggregate interface if the aggregate interface is excluded from being shut down.
Views
System view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
Usage guidelines
If an interface must be kept in up state for special purposes such as Telnet connection, exclude the interface from the shutdown action. As a best practice to avoid incorrect traffic forwarding, do not exclude any interfaces except the interfaces used for Telnet.
The interfaces that have been shut down by MAD come up when the member devices reboot to join the recovered container cluster. If the active container cluster fails before the link is recovered, use the mad restore command on the inactive container cluster to recover the inactive container cluster. This command also brings up all interfaces that were shut down by MAD.
Examples
# Exclude GigabitEthernet 1/0/1 from being shut down when the MAD status transits to Recovery.
<Sysname> system-view
[Sysname] mad exclude interface gigabitethernet 1/0/1
Related commands
mad restore
mad restore
Use mad restore to restore the normal MAD state of the container cluster in Recovery state.
Syntax
mad restore
Views
System view
Predefined user roles
network-admin
Usage guidelines
If the active container cluster has failed to work before the container cluster split problem is fixed, use this command to restore a container cluster in Recovery state. The recovered container cluster will take over the active container cluster role.
Examples
# Restore the normal MAD state of the container cluster in Recovery state.
<Sysname> system-view
[Sysname] mad restore
This command will restore the device from multi-active conflict state. Continue? [Y/N]:Y
Restoring from multi-active conflict state, please wait...
member-ip
Use member-ip to specify the member IP address for a device.
Syntax
member-ip ipv4-addr mask-length
Default
The member IP address is not specified for a device.
Views
Cloud cluster member view
Predefined user roles
network-admin
Parameters
ipv4-addr: Specifies the member IP address for the device to communicate in the cluster. The address cannot be a loop address, broadcast address, multicast address, or 0.X.X.X.
mask-length: Specifies the mask length for the member IP address, in the range of 1 to 31.
Usage guidelines
Application scenarios
Member IP address is used by a device to communicate in the cluster for exchanging physical cluster protocol packets. All members in the physical cluster must be configured with member IP addresses.
Restrictions and guidelines
Make sure physical clusters in a network use different subnets for internal cluster communication.
Make sure all member IP addresses in a cluster are in the same subnet. To add a device into a cluster, make sure the device IP address and IP addresses of member devices in the cluster are in the same subnet.
You cannot delete a member IP address and can only change the IP address to an address in the same subnet as the IP address of other members. To change the IP address to an address in a different subnet, first execute the undo join-cluster and cloud-cluster configuration active commands in sequence to remove the device from the cluster.
After you execute this command, you must execute the cloud-cluster configuration active command. The configuration takes effect together with other cloud cluster settings.
Examples
# Configure the IP address for device with member ID 1 as 1.1.1.1/24.
<Sysname> system-view
[Sysname] cloud-cluster member 1
[Sysname-ccluster-member-1] member-ip 1.1.1.1 24
Related commands
cloud-cluster configuration active
cloud-cluster member
join-cluster