Cisco Cisco Prime Network Registrar 8.1 Troubleshooting Guide

 

Passive Master Log File Coordinates: 

LOG_FILENAME='mysql-bin.000001' 

LOG_START_POS=2645 

 

Replication Setup Step 2 of 3 complete! 

 

- Record the Passive Master Log File Coordinates and return to the master 
system. 

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

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

 

./connect_to_passive.sh -l mysql-bin.000001 -s 2645 -h 192.168.196.46 

Now we have to complete the loop by connecting the Active Master to the 

Passive Master.  This step also includes the startup of the MySQL Replication 

Monitor.  From the Production Executive, we run the following: 

>./connect_to_passive.sh -l mysql-bin.000001 -s 2645 -h 192.168.196.46 

Creating replication user with: GRANT REPLICATION SLAVE, REPLICATION CLIENT ON 
*.* TO repl@'192.168.196.46' IDENTIFIED BY 'fake_password' 

Granting replication user rights to replication monitor db (passive master 
host) with: GRANT SELECT ON replmon.* TO repl@'192.168.196.46' IDENTIFIED BY 
'fake_password' 

Connecting to passive master with: CHANGE MASTER TO 
MASTER_HOST='192.168.196.46',MASTER_USER='repl',MASTER_PASSWORD='fake_password
', MASTER_LOG_FILE='mysql-bin.000001',MASTER_LOG_POS=2645 

 

Starting slave process with: START SLAVE 

Modifying IP Addresses in /opt/incontrol/mysql_replication_monitor.properties 

Turning on control of the replication monitor. 

IPControl MySQL Replication Monitor install successful. 

Starting the replication monitor ... 

IPControl MySQL Replication Monitor is already stopped. 

Waiting 5 seconds before starting... 

 

Starting IPControl MySQL Replication Monitor... 

IPControl MySQL Replication Monitor started. 

 

Replication Setup Step 3 of 3 complete! 

 

This section outlines the steps to be used when the MySQL server running 

on the Production Executive is to be brought down for some reason, and the 

DR Executive MySQL database is to assume the role of Active Master.