Appendix D: N-Command Failover Configuration
Stopping Master/Slave
At any time, the master/slave relationship can be severed by navigating (on each unit) to Admin > Configure
master/slave and setting the unit to Unassigned. If system services have stopped, they will be started.
NOTE: If the databases have been synced, this could cause duplicate IP problems. It is best to isolate the slave unit
when un-pairing.
Important Notes
During failover/override transitions, the N-Command units are reconfiguring their network cards to new IP
addresses. Units that are connected will see the connection broken and will need to reestablish connection
(very common occurrence for network devices).
A master will not override another master. If a system is misconfigured and has two masters, both units will
start as normal and refuse to override each other.
If a system is misconfigured to have two slaves, whichever unit boots first will take control.
A slave will not attempt to import if the master says its data is not good.
There are no configuration options on the slave. The master dictates everything.
Data only flows from the master to the slave. The master never imports from the slave.
Once configured for master/slave, the slave's web page is accessible only from the 3rd IP addresses (until a
failover or it is Unassigned).
To Next Page
Loading...
Need help?
General
