Cisco Cisco Prime Network Registrar 8.1 故障排查指南
Cisco Prime Network Registrar IPAM 8.1.1 Disaster Recovery Guide - Using MySQL Replication
11
they must be named default.incontrol.primary and
incstatus.primary, respectively.
3.1.2 Disaster Recovery Procedure
This section describes the procedure necessary to initiate a DR
event or exercise under this scenario.
3.1.2.1 Change the IP of the DR Executive
3.1.2.1.1 Linux/Solaris
Change the IP address and associated parameters, including
netmask and gateway, for the network interface using the
accepted method of defining IP addressing information on that
platform. For example, on Red Hat this can be done using
system-config-network.
system-config-network.
The IP address must be set
to the IP address of the failed Production Executive, which
must be offline.
3.1.2.2 Promote the DR Executive to Active Master
If the Production Executive is down, then the current
Active Master database on it is down as well.
Therefore the DR Executive must assume control and
become the new Active Master. This is accomplished
by calling the promote_master.sh script using the ‘-c’
command line option:
1.
Log into the DR Executive as incadmin.
2.
Run the promote_master.sh script as follows:
$INCHOME/etc/support/promote_master.sh –c
3.1.2.3 Promote the DR Executive to Production status
Promoting the DR Executive to Production status involves
updating the default.incontrol and incstatus files on the DR
Executive from copies of these files from the Production
Executive (see section 3.1.1.3). This configures the DR
Executive to start all services required for normal operation.
3.1.2.3.1 Linux/Solaris
In order to “promote” the DR Executive so that it may
become the Production Cisco Prime Network Registrar IPAM
Executive, you must run the PromoteExec.sh script provided