Dual Management with Single Heartbeat and Dedicated Database Sync

To allow for access to the server over more than one management interface and segregation between management and database traffic, you can configure two management interfaces and a dedicated interface for database replication. However, in this configuration there can only be one heartbeat interface, which increases the risk for a split-brain state. The configuration includes:

• 2 interfaces for device monitoring and TOS management

  If you have networks that must communicate with a management interface and these networks are not in the scope of the default gateway route, then you must add a static route to the management interface to allow communication with these networks. For more about configuring static routes, see: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-static-routes.html

• 1 interface for database replication

  In this case, the database replication interfaces on the active and standby servers must be configured with IP addresses on the same network.

• 1 interface for the heartbeat

  Disconnection of the heartbeat interfaces while the Active server is running causes a split-brain state, which can cause overload of device and network resources.