Cisco Cisco Prime Network Registrar 8.1 Troubleshooting Guide

Cisco Prime Network Registrar IPAM 8.1.1 Disaster Recovery Guide - Using MySQL Replication

If Production Executive is down, or database was not

demoted:

>$INCHOME/etc/support/promote_master.sh -c

3.2.2.3 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.3.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.4 Restart the DR Executive Cisco Prime Network Registrar IPAM

services

3.2.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 IPControl, wait for the services to stop, then

choose

Start IPControl.

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