How to configure MCS Redundancy

MCS presents the 1-1 redundancy feature in which the same MCS configuration can be replicated on another MCS instance.

There is a Local and a remote MCS instance. In the first MCS, the local is configured as the main, and the remote instance is secondary, and in the second MCS, the local is configured as secondary, and the remote is the main. Thus, both the MCS are active and share a common configuration. Please ensure the secondary MCS system has a clean DB before configuring it to the main MCS.

Follow the steps below to configure MCS redundancy.

1. On the home screen of the MCS GUI, click on the top left corner (highlighted in green) and click on Redundancy (under Management).

Open

In the system configuration page, you can configure the local and remote MCS instance. Please make sure both the MCS has the same version and device configurations.

Open

2. In this example two MCS instances are configured for redundancy (MCS1 - 192.168.10.40 and MCS2 - 192.168.10.42). In MCS1, click on the Remote option and click on edit as shown below. Add the MCS2 IP address (192.168.10.42) in the Addresses field and click on the save button.

3. The MCS Redundancy is configured.

4. Similarly, goto the MCS2 (192.168.10.42), change the local from Main priority to Secondary (as shown below) and click on save. 

5. Add the MCS1 (192.168.10.40) as Remote host (Main) as shown below.

Now, both the MCS’s (MCS1 - 192.168.10.40 and MCS2 - 192.168.10.42) share the same configuration. In this example, both the MCS’s holds the MCM9000 (192.168.10.156) configuration. To verify, goto Notifications → Notification Agents → Redis Agent. The MCM9000 share the same configuration with MCS1 - 192.168.10.40 and MCS2 - 192.168.10.42.