Cisco Cisco Prime Network Registrar 8.0 トラブルシューティングガイド
Disaster Recovery Guide for Cisco Prime Network Registrar IPAM 8.0
11
3.1.1.3 Updated copies of default.incontrol and incstatus
As indicated previously, you must keep current copies
of the default.incontrol and incstatus files from the
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
are located in $INCHOME/etc. When copied to the
DR Executive, they must be named
default.incontrol.primary and incstatus.primary,
default.incontrol.primary and incstatus.primary,
respectively.
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/Solaris
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
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
. The IP address must be set
to the IP address of the failed Production Executive, which
must be offline.
3.1.2.1.2 Linux/Solaris
In order to “promote” the DR Executive so that it may
become the Production Cisco Prime Network Registrar IPAM
Executive, you must run the PromoteExec.sh script provided
Executive, you must run the PromoteExec.sh script provided
in the $INCHOME/etc/support directory of the Cisco Prime
Network Registrar IPAM installation:
> $INCHOME/etc/support/PromoteExec.sh
Network Registrar IPAM installation:
> $INCHOME/etc/support/PromoteExec.sh