Cluster Ip-Pool; Cluster Commander - Edge-Core ES4624-SFP Basic Management Manual

Switch (config)#no cluster run

30.3.2 cluster ip-pool

Command: cluster ip-pool <commander-ip>
no cluster ip-pool
Function: Configure private IP address pool for member switches of the cluster.
Parameters ： commander-ip ： cluster IP address pool for allocating internal IP
addresses of the cluster commander-ip is the head address of the address pool, of which
the valid format is 10.x.x.x, in dotted-decimal notation; the address pool should be big
enough to hold 128 members, which requires the last byte of addresses to be less than
126（254 – 128 = 126） 。IP address pool should never be changed with commander
configured. The change can only be done after the "no cluster commander" command
being executed.
Command mode: Global Mode
Default: The default address pool is 10.254.254.1.
Usage Guide： When candidate switches becomes cluster members, the commander
switch allocates a private IP address to each member for the communication within the
cluster, and thus to realized its management and maintenance of cluster members. This
command can only be used on non-commander switches. Once the cluster established,
users can not modify its IP address pool. The NO command of this command will restore
the address pool back to default value, which is 10.254.254.1.
Example: Set the private IP address pool used by cluster member devices as
10.254.254.10
Switch(config)#cluster ip-pool 10.254.254.10

30.3.3 cluster commander

Command: cluster commander <cluster-name>
no cluster commander
Function: Set the switch as a commander switch, and create a cluster.
Parameter: <cluster-name> is the cluster's name, no longer than 32 characters.
Command mode: Global Mode
Default: Default setting is no commander switch. cluster_name is null by default.
Usage Guide： This command sets the role of a switch as commander switch and creates
a cluster, which can only be executed on non commander switches. The cluster_name
cannot be changed after the switch becoming a commander, and "no cluster commander"
should be executed first to do that. The no operation of this command will cancel the
617