Cisco Cisco Prime Network Registrar 8.0 Guide De Dépannage

 

required for MySQL replication to keep the Cisco 

Prime Network Registrar IPAM database updated from 
the Production Executive.  This can be accomplished 

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 

 

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. 

 

This section describes the procedure necessary to initiate a DR 

event or exercise under this scenario. 

If this is a planned DR exercise where the Production 

Executive will eventually resume its role as the Active 
Master database, then demoting the Production 

Executive database at the start is preferable.  To do 
this, execute the demote_master.sh script located in the 

$INCHOME/etc/support directory on the Production 
Executive: 

> $INCHOME/etc/support/demote_master.sh

 

 
This script will ensure that no unintended writes will occur 

on the Production Executive database and will help 

with a smooth transition back to “normal” operation.  
In addition it will generate the appropriate parameters 

to call the promote_master.sh script on the DR 
Executive. 

At this point, we will assume that either the Production 

Executive is down, or that the Production Executive 

database has been demoted to a Passive Master.  
Therefore, we need to promote the database on the DR 

Executive to an Active Master.  The process varies 
slightly dependent upon if the Production Executive 

was demoted.  If it was demoted we will use the 
parameters generated from the demote_master.sh