Cisco Cisco Prime Network Registrar 8.1 Troubleshooting Guide
Cisco Prime Network Registrar IPAM 8.1.1 Disaster Recovery Guide
21
3.3.1 Prerequisites
The following prerequisites must be met in order to
support a DR event or exercise under this scenario.
3.3.1.1 Configure Virtual IP address on Production and DR
Executives
Select a single, virtual IP address that is routable to
both the Production and DR Executives.
Configure this virtual IP address, in addition
to each machine’s “real” IP address, on the
network interface connected to the
management subnet. The management subnet
is the segment in which the Cisco Prime
Network Registrar IPAM Agents are
connected. Configure the virtual IP address
using the accepted method of defining IP
addressing information on that platform. For
example, on Red Hat this can be done using
system-config-network
system-config-network
.
3.3.1.2 Installation of Cisco Prime Network Registrar IPAM on
Production and DR Executives
During the installation of the Cisco Prime
Network Registrar IPAM software on both the
Production and DR Executive, you should
enter the
virtual IP address when prompted for
the IP address of the system and executive on
the initial setup screens.
3.3.1.3 Updated copies of default.incontrol and incstatus
If the Cisco Prime Network Registrar IPAM
Executive software is installed and running directly
from shared storage device, this prerequisite is not
required. This is required if only the database itself is
mirrored.
As indicated previously, you must keep current
copies of the default.incontrol and incstatus
files from the Production Executive on the
DR Executive. Both files are located in
$INCHOME/etc. When copied to the DR
Executive, they must be named
default.incontrol.primary and
incstatus.primary, respectively.