Cisco Cisco Prime Network Registrar 8.3 故障排查指南

Cisco Prime Network Registrar IPAM 8.3 Disaster Recovery Guide



3.1.2 Disaster Recovery Procedure

This section describes the procedure necessary to initiate a DR event or
exercise under this scenario.

3.1.2.1 Change the IP of the DR Executive

3.1.2.1.1 Linux

Change the IP address and associated parameters, including netmask and
gateway, for the network interface 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. The IP address must be set to the IP
address of the failed Production Executive, which must be offline.

3.1.2.2 Promote the DR Executive to Production status

Promoting the DR Executive to Production status involves updating
the default.incontrol and incstatus files on the DR Executive from
copies of these files from the Production Executive (see section
3.1.1.3). This configures the DR Executive to start all services required

for normal operation.

3.1.2.2.1 Linux

In order to “promote” the DR Executive so that it may become the
Production IPAM Executive, you must run the PromoteExec.sh script
provided in the $INCHOME/etc/support directory of the IPAM installation:

> $INCHOME/etc/support/PromoteExec.sh

3.1.2.3 Restart the DR Executive IPAM services

3.1.2.3.1 Linux

Run the incontrol script to restart all services on the DR Executive:
> $INCHOME/etc/incontrol restart

3.1.3 Return to Normal

This section describes the procedure necessary to return to normal
operation where the Production Executive is in use, and the DR Executive
is in standby mode.

3.1.3.1 Change the IP of the DR Executive

Follow the same procedure described above to change the IP of the

DR Executive back to its original IP.