Why is a member switch displayed as unknown or down while the member switch is actually Up

S series switches (excluding the S1700) in V200R002 and later versions, and V100R006C05 do not support HGMP.
When a member switch in a cluster is Up but displayed as unknown or down, the possible causes and solutions are as follows:
Cause 1: The configuration is not saved after the switch is added to the cluster and reset.
Solution: Add the member switch to the cluster again and save the configurations of the command switch and the member switch.

Cause 2: The command switch re-establishes a cluster but the command for deleting the original cluster is not delivered to the member switch. This is because the member switch is Down when the cluster is deleted or the command switch is reset without saving the configuration. The new cluster name is different from the original one. Another possible cause is that the super password is configured on the member switch using the super password command.
NOTE: S series switches in V200R003 and later versions, and V100R006C05 do not support the super password command.
The super password configured on the command switch is copied to member switches when the cluster is created.
In this case, you cannot add the member by running the command of re-joining the cluster. The message “Candidate device refused�?is displayed.
Solution:
Re-establish a cluster using the original cluster name, add the member switch to the cluster again, and save the configuration.
Specify the super password to add the member switch to the cluster.

Cause 3: The mVLAN configured on the member switch is different from that configured on the command switch.
Solution: Change the mVLAN on the member switch to ensure that the mVLANs of all switches in the cluster are the same.
NOTE: In this case, you cannot add the member by running the command of re-joining the cluster. The message “Candidate device no response�?or no message is displayed.

Scroll to top