Cisco Cisco Prime Network Registrar 8.0 Guide De Dépannage

Page de 37
 
 
 
 
 
 
 
 
 
 
 
 
 
3.2.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.2.3.1  Stop Cisco Prime Network Registrar IPAM Services on DR Executive 
3.2.3.1.1 Linux/Solaris 
Run the Cisco Prime Network Registrar IPAM script to stop 
all services on the DR Executive: 
> $INCHOME/etc/incontrol stop 
3.2.3.2  Demote the DR Executive to standby status 
 
Revert the DR Executive to standby by running the 
“demote” script which will configure the system to 
start only MySQL: 
> $INCHOME/etc/support/DemoteExec.sh
 
 
3.2.3.3  Start Cisco Prime Network Registrar IPAM Services on DR Executive 
3.2.3.3.1 Linux/Solaris 
Run the Cisco Prime Network Registrar IPAM script to start 
all services on the DR Executive: 
> $INCHOME/etc/incontrol start 
3.2.3.4  Restore the Production Executive Database 
The next step depends upon what state the Production 
Executive database was in when the DR Executive assumed 
control and whether the original Production Executive is being 
replaced. 
3.2.3.4.1 Reuse of Demoted Production Executive 
If the Production Executive database was demoted before 
the DR Executive assumed control then the steps are fairly 
simple.  We simply need to demote the DR Executive database, 
record the Log file coordinates, and finally run promote the 
database on the Production Executive using these coordinates. 
3.2.3.4.1.1  Demote the DR Executive Database 
Run the demote_master.sh script located in the 
$INCHOME/etc/support directory. 
> $INCHOME/etc/support/demote_master.sh 
This script will generate the necessary parameters to use 
with the promote_master.sh script to be run on the Production 
Executive.