Cisco Cisco Prime Network Registrar 8.1 Troubleshooting Guide
3.1.3.6 Stop Cisco Prime Network Registrar IPAM Services on DR Executive
3.1.3.6.1 Linux/Solaris
Run the incontrol script to stop all services on the DR
Executive:
> $INCHOME/etc/incontrol stop
> $INCHOME/etc/incontrol stop
3.1.3.7 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.1.3.8 Start Cisco Prime Network Registrar IPAM Services on DR Executive
3.1.3.8.1 Linux/Solaris
Run the incontrol script to start all services on the DR
Executive:
> $INCHOME/etc/incontrol start
> $INCHOME/etc/incontrol start
3.1.3.9 Promote the database on the Production Executive
Now that the DR Executive is back to being a Passive
Master, we need to promote the database on the
Production Executive back to an Active Master. To do
this, simply run the promote_master.sh script located
in the $INCHOME/etc/support directory using the
parameters generated by the demote_master.sh script
run on the DR Executive:
> $INCHOME/etc/support/promote_master.sh
–l <binary logfile name> -s <logfile
position>
–l <binary logfile name> -s <logfile
position>
3.1.3.10 Restart Cisco Prime Network Registrar IPAM Services on Production
Executive
3.1.3.10.1
Linux/Solaris
Run the incontrol script to restart all services on the
Production Executive:
> $INCHOME/etc/incontrol restart
Choose
> $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.2 Production and DR Executive use different IPs
In this DR scenario the failed Production Executive is replaced
by the DR Executive, but the machines maintain separate IP
addresses because they are not on the same subnet or there is
no VLAN in place and no virtual IP technology is used. All