Cisco Cisco Prime Network Registrar 8.3 故障排查指南
Cisco Prime Network Registrar IPAM 8.3 Disaster Recovery Guide
18
3.3.1 Prerequisites
The following prerequisites must be met in order to support a DR event or
exercise under this scenario.
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
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 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.
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.
3.3.1.2 Installation of IPAM on Production and DR Executives
During the installation of the 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
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 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.
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.
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.
3.3.2 Disaster Recovery Procedure
This section describes the procedure necessary to initiate a DR event or
exercise under this scenario.
exercise under this scenario.
3.3.2.1 Bring the DR Executive online
Enable the IP connectivity of the DR Executive by either physically
connecting it to the network, or by enabling the switch port to which it
is connected.
is connected.