You can create a NetMRI failover pair using two NetMRI appliances, in which one acts as the primary appliance and the other as the secondary appliance. A failover pair provides a backup or redundant operational mode between the primary and secondary appliances so you can greatly reduce service downtime when one of them is out of service. You can configure two Operation Center (OC) appliances or standalone appliances to form a failover pair.
In a failover pair, the primary appliance actively discovers and manages network devices and serves the Web UI and the CLI over the shared VIP address while the secondary appliance constantly keeps its database synchronized with the primary. Although you can access a failover pair using either the VIP address of the failover pair or the management IP address of the primary appliance, using the management IP is not recommended because, during a failover, the roles of the primary and secondary appliances reverse, and the management IP becomes unreachable. Accessing the failover pair using the VIP address ensures that you are contacting the active primary appliance. Note that during a failover, all active connections between the NetMRI appliances and the network devices are disrupted, and all ongoing processes fail. Also, all active Web UI and CLI sessions are disrupted during a failover and all users with active sessions must reconnect and log in again after the secondary appliance assumes the role of the primary appliance.
Note the following about the automatic failover feature:
Following are the pre-requisites for deploying automatic failover for new appliances:
Infoblox recommends you use the direct replication method for best reliability and performance. The network replication method will have higher latency and a greater chance of connection breakage, and thus lower reliability and performance. |
To deploy two new Operation Center (OC) or standalone appliances to form a failover pair:
Network replication: You can connect the HA port of both systems to a network using an Ethernet cable. For virtual machines, network replication means a virtual machine in one subnet is connected to a virtual machine in another subnet through a network.
Infoblox recommends setting up virtual machines (data center or hypervisor) in the same location. If the machines are not set up in the same location, high latency or limited bandwidth can cause unstable performance. |
Infoblox recommends that you connect the systems using the direct replication method.
After upgrading both systems to NetMRI 7.1.1 or later, repartition the systems by logging in to the Admin Shell of both the systems and enter the repartition
command. For new systems with no network device data collected, you can proceed without resetting and without generating a backup. For systems that are already deployed, and have collected data, follow the steps mentioned in Migrating Existing Systems as Failover Pairs.
The |
Log in to the primary system, click the Settings icon > Setup > Failover Configuration, and then specify the configuration settings on in the Failover Configuration page.
After specifying the failover configuration settings and completing the enable operation, the systems start synchronizing data. This process might take up to one hour, depending on the appliance model. |
You can migrate two existing Operation Center (OC) or standalone appliances to form a failover pair. Ensure that both appliances are running versions NetMRI 7.1.1 or later. To form a collector failover, migrate the existing collector to NetMRI 7.1.2 or later releases.
Following are the pre-requisites for migrating existing systems as a failover pair:
To migrate two existing systems to form a failover pair:
In the steps below, the system that is referred to as the second appliance takes the primary role and the system that is referred to as the existing appliance takes the secondary role in the failover pair. |
Direct replication: You can connect the systems directly through their HA ports. For virtual appliances, direct replication is used in a separate VM-only network that contains only an HA pair.
Network replication: You can connect the HA port of both systems to a network using an Ethernet cable. For virtual machines, network replication means a virtual machine in one subnet is connected to a virtual machine in another subnet through a network.
Infoblox recommends setting up virtual machines (data center or hypervisor) in the same location. If the machines are not set up in the same location, high latency or limited bandwidth can cause unstable performance. |
Infoblox recommends that you connect the systems using the direct replication method.
Log in to the administrative shell on the second system and enter the repartition
command. Note that if the system is already partitioned for failover, an error message appears when you run the repartition
command.
The |
reset system
command, and then enter the repartition
command. Note that if the system is already partitioned for failover, an error message appears when you run the repartition
command. After repartitioning is complete, run the configure server
command, install the license, and then reset the admin password in GUI to match the other system.reset tunserver
and configure tunserver
commands. Enter the VIP address of the Operation Center when prompted for the IP address of the Operation Center server.Log in to the administrative shell on each Collector and run the reset tunclient
and register tunclient
commands. Enter the VIP address of the Operation Center when prompted for the IP address of the Operation Center.
After specifying the failover configuration settings and completing the enable operation, the systems start synchronizing data. This process might take up to one hour, depending on the appliance model. For details about how to configure these settings, refer to the Infoblox NetMRI Administrator Guide. |