Appendix D: N-Command Failover Configuration
A 2nd address is not required, so it is left blank. The 3rd IP address has a subnet just big enough for the master,
slave, and a few spare computers for troubleshooting.
3. Repeat the 3rd IP address setup on the slave unit. Choose IP addresses for each network card within the subnet
of the master. You may use the Ping tool on the IP settings page to check communication.
4. If you do not have strict IP requirements, an example master/slave IP configuration could be:
Master
Eth0: 172.10.21.201 / 255.255.255.252
Eth1: 172.20.21.201 / 255.255.255.252
Slave
Eth0: 172.10.21.202 / 255.255.255.252
Eth1: 172.20.21.202 / 255.255.255.252
5. Navigate to Admin > Master / Slave on the master unit. Now that the 3rd IP addresses are configured, the menu
shows other N-Commands it has found on the network and offers to configure them to be the slave. See
Figure 56
.
FIG. 56 Choose Slave
6. The slave must have its 3rd IP addresses configured. If the unit is not configured correctly, N-Command will
offer the address so you may configure it.
FIG. 57 Configure Slave Address
7. Once all addresses are configured, click the Assign Master and Slave button to set up master/slave. You may
also use the Ping tool to check connections. N-Command internally tests configurations before accepting the
unit as slave. See Figure 58
.
To Next Page
Loading...
Need help?
General
