Manualsbrain.com
  1. Manuals
  2. Brands
  3. Cisco
  4. Cisco Prime Network Registrar 8.0
  5. Troubleshooting Guide

Cisco Cisco Prime Network Registrar 8.0 Troubleshooting Guide

Download
Page of 37
 
 
 
 
 
 
 
 
 
 
 
 
Disaster Recovery Guide for Cisco Prime Network Registrar IPAM 8.0 - Using MySQL Replication    13 
 
 
 
 
 
 
 
 
 
 
 
in the $INCHOME/etc/support directory of the Cisco Prime 
Network Registrar IPAM installation: 
> $INCHOME/etc/support/PromoteExec.sh 
 
3.1.2.4  Restart the DR Executive Cisco Prime Network Registrar IPAM 
services 
3.1.2.4.1 Linux/Solaris 
Run the Cisco Prime Network Registrar IPAM script to restart 
all services on the DR Executive: 
> $INCHOME/etc/incontrol restart 
Choose Stop Cisco Prime Network Registrar IPAM, wait 
for the services to stop, then choose Start Cisco Prime 
Network Registrar IPAM. 
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. 
3.1.3.2  Prepare the Active Master on the DR Executive for demotion 
The Active Master database running on the DR Executive 
must be demoted so that it no longer accepts any 
changes.  But this demotion cannot take place until the 
database on the Production Executive is back in synch 
with the Active Master on the DR Executive.  This 
requires that we dump the current state of the database 
on the DR Executive in order to load the data on the 
restored Production Executive.  To accomplish this, 
the prepmaster.sh script provided in the 
$INCHOME/etc/support directory must be run with 
the „-d‟ command line option.  This will cause the 
database to be dumped and the appropriate options for 
the prepslave.sh script will be generated.