Cisco Cisco Prime Network Registrar 8.0 トラブルシューティングガイド

ページ / 24
 
 
 
 
 
 
 
 
 
 
 
 
using the DemoteExec.sh script provided in the 
$INCHOME/etc/support directory of the Cisco Prime 
Network Registrar IPAM installation: 
> $INCHOME/etc/support/DemoteExec.sh 
3.2.1.4  Updated copies of default.incontrol and incstatus 
 
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, and located in $INCHOME/etc. 
 
3.2.2  Disaster Recovery Procedure 
This section describes the procedure necessary to initiate a DR 
event or exercise under this scenario. 
3.2.2.1  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.3.1.3).  This configures the DR 
Executive to start all services required for normal operation.  
In addition, the promote operation will update the Cisco Prime 
Network Registrar IPAM database with the IP address of the 
DR Executive for the Executive and Task Manager IP address 
System Properties, and IP address of the Executive Agent. 
3.2.2.1.1 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 
in the $INCHOME/etc/support directory of the Cisco Prime 
Network Registrar IPAM installation: 
> $INCHOME/etc/support/PromoteExec.sh
 
 
3.2.2.2  Restart the DR Executive Cisco Prime Network Registrar IPAM 
services 
3.2.2.2.1 Linux/Solaris 
Run the Cisco Prime Network Registrar IPAM script to restart 
all services on the DR Executive: 
> $INCHOME/etc/incontrol restart