Cisco Cisco Prime Network Registrar 8.1 Troubleshooting Guide
up the Production Executive to listen for changes on
the DR Executive and to begin monitoring the state of
replication. All three of these steps are handled by
scripts provided with Cisco Prime Network Registrar
IPAM. These scripts are detailed below.
2.3.1.1.1 $INCHOME/etc/support/prepmaster.sh
Run this script on the Production Executive to grant access to
the DR Executive replication account and update the
configuration file, my.cnf, to support replication. After making
the appropriate changes to the configuration file, the master is
restarted. The script then creates the starting point for
replication, using mysqldump. This starting point, or dump
file, will be created in the current directory. When the script
completes, it will display the steps necessary to configure the
slave (or Passive Master). This includes the correct parameters
to pass to the prepslave.sh script on the DR Executive.
2.3.1.1.2 $INCHOME/etc/support/prepslave.sh
Run this script on the DR Executive to update the
configuration file, my.cnf. to support replication. It also loads
the starting point for the db from the master. In order to
configure the slave, you will
need the Log File Coordinates
provided when the prepmaster.sh script was run on the master
server. When this script completes it will display the
appropriate parameters to pass to the connect_to_passive.sh
script on the Production Executive.
2.3.1.1.3 $INCHOME/etc/support/connect_to_passive.sh
Run this script on the Production Executive to complete the
connection between the master and slave servers. It defines
the Active Master as a slave to the Passive Master. In addition
it configures the appropriate settings to run the MySQL
Replication Monitor utility, and starts this utility.
2.3.1.1.4 Example Configuration
To see an annotated example of configuring a Production and
DR Executive for MySQL Replication please refer to
Appendix A.
2.3.1.2 Adding a DR Executive and replication to existing Production
Executive not logging for replication
This describes the case where a Production Executive is already
in use, but MySQL replication is not being used. Follow the
same steps as described in the previous section “Replication
Setup for new install of both Production and DR Executives.”