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.
...
Note the following about the automatic failover feature:
A failover pair is supported only on NetMRI NT-1400, NT-2200, and NT-4000 (G8-only) appliances.
A failover pair is supported on virtual NetMRI appliances in NetMRI 7.5.4 and later releases.
The primary and secondary appliances must have the same hardware models or VM configurations and software versions.
The management IP address of the primary and secondary appliances must be on the same subnet.
The VIP address, which is shared by the primary and secondary appliances, must be on the same subnet as that of the management IP address.
Deploying Automatic Failover for New Appliances
Following are the pre-requisites for deploying automatic failover for new appliances:
...
Set up and configure two new NetMRI appliances as separate and make sure that the appliances are running NetMRI 7.1.1 or later.
For collector failover configuration, make sure that the appliances are running NetMRI 7.1.2 or later. For a failover pair, make sure that the appliances are running NetMRI 7.1.4 or later.Connect both the systems using one of the following methods:
Direct methodDirect replication: You can connect the systems directly through their HA ports. For virtual appliances, direct replication method is used in a separate VM-only network that contains only an HA pair.
Network methodNetwork replication: You can connect the HA port of both systems to a network using an Ethernet cable. For virtual machines, network replication method means a virtual machine in one subnet is connected to a virtual machine in another subnet through a network.
Note that 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.
Run the Setup Wizard on both appliances and set the admin password and install the license. The admin password must be the same on both systems. At this point in time, it is not necessary to complete the entire configuration wizard on both systems. You can complete the configuration only on the primary system.
If the systems were not shipped with version 7.1.1 or later, you must upgrade the systems to the latest release.
After upgrading both systems to NetMRI versions 7.1.1 or later, repartition the systems by accessing the Admin Shell of each system and executing the
repartition
command.
Note that therepartition
command applies only to physical appliances.
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.Choose one system to take the primary role. You can choose the system for which you have completed the entire configuration, otherwise, the configuration might be lost.
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.
Note |
---|
NoteAfter 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. |
Migrating Existing Systems as Failover Pairs
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.
...