Cisco Cisco Prime Network Registrar 8.1 Troubleshooting Guide

 

Even with the MySQL Servers configured properly it is 

possible for the Passive Master to drift out of synch with the 

Active Master.  One method for resolving this is to start over 

with a fresh database dump from the master.  This section 

covers the procedure necessary to accomplish this. 

On the Production Executive we need to run the 

resync_master.sh script located in 

$INCHOME/etc/support. 

 

>./resync_master.sh 

 

Dumping the master database and getting Log File Coordinates ... 

Master Log File Coordinates: 

MASTER_LOG_FILE='mysql-bin.000001' 

MASTER_LOG_POS=14158333 

 

Dump File: dbforrepl.sql 

 

Resynchronization Setup Step 1 of 2 complete! 

 

- Copy the Dumpfile: dbforrepl.sql to the slave server. 

- Record the Active Master Log File Coordinates and log in to the passive 
master system. 

- Navigate to /opt/incontrol/etc/support. 

- Once there, run the resync_slave.sh script using the coordinates as 
follows: 

 

./resync_slave.sh -l mysql-bin.000001 -s 14158333 -h 192.168.196.45 -d 
<location of dbforrepl.sql> 

The database dump file created by the resync_master.sh 

script in the previous step needs to be copied to the 

Passive Master box.  In this example, we will use the 

‘scp’ command to accomplish this. 

>scp incadmin@192.168.196.45:/opt/incontrol/etc/support/dbforrepl.sql . 

incadmin@192.168.196.45's password: 

dbforrepl.sql                                 100%  391KB 391.2KB/s   00:00