Use the commands in this section to configure the basic settings for a single-interface Central Management System cluster in a WAN deployment that uses a non-default interface.
Configuring the primary node
Perform the procedures in this section in order to configure the primary node.
Configure the default HA interface:
Verify and save your changes:
Start the cluster engine:
Configuring the secondary node
Perform the procedures in this section in order to configure the secondary node.
Configure the default HA interface:
Add the node to the cluster:
Verify and save your changes:
Start the cluster engine:
Note
You can perform a manual failover to test the cluster.
Examples
The following example configures the primary node in the single-interface WAN deployment using a non-default interface.
node1 (config) # interface ether3 ip address 10.2.140.25 /26
node1 (config) # no interface ether3 shutdown
node1 (config) # ip route 10.2.0.0 /26 10.2.140.1 ether3
node1 (config) # ip route 10.17.0.0 /24 ether3
node1 (config) # ha interface default ether3
node1 (config) # show ha configuration
...
node1 (config) # write memory
node1 (config) # ha engine restart
...
node1 (config) # show ha status
...The following example configures the secondary node in the single-interface WAN deployment using a non-default interface.
node2 (config) # interface ether3 ip address 10.17.220.25 /24
node2 (config) # no interface ether3 shutdown
node2 (config) # ip route 10.17.0.0 /24 10.17.220.254 ether3
node2 (config) # ip route 10.2.0.0 /26 ether3
node2 (config) # ha interface default ether3
node2 (config) # ha node join 10.2.127.144
Enter password for admin account on primary node: ********
Node joining has started
Please check the status with CLI 'show ha configuration'.
node2 (config) # show ha configuration
...
node2 (config) # write memory
node2 (config) # ha engine restart
...
node2 (config) # show ha status
...Note
For examples showing the full output of the show commands, see Viewing the cluster configuration using the CLI and Viewing the cluster status using the CLI .