Cisco Cisco Prime Network Registrar 8.0 Guide De Dépannage

Page de 37
 
 
 
 
 
 
 
 
 
 
 
 
Disaster Recovery Guide for Cisco Prime Network Registrar IPAM 8.0 - Using MySQL Replication    7 
 
 
 
 
 
 
 
 
 
 
 
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.” 
 
2.3.1.3  Adding a DR Executive and replication to existing Production 
Executive already logging for replication 
Follow the instructions in the previous sections with one 
exception.  You should include the „-d‟ command line 
parameter when running the prepmaster.sh script on the 
Production Executive.  This will skip the steps of modifying 
the mysql configuration and will essentially just dump the 
existing database and provide the Log File Coordinates 
necessary to configure the slave (or Passive Master).  
 
2.3.2  Startup and status scripts 
The Cisco Prime Network Registrar IPAM installation includes 
two scripts used frequently by administrators to start and stop 
the Cisco Prime Network Registrar IPAM services and to 
check the status of the currently running services. 
2.3.2.1  $INCHOME/etc/default.incontrol 
 
This file contains entries for each of the Cisco Prime 
Network Registrar IPAM services, specifying which