Cisco Cisco Prime Network Registrar 8.1 Troubleshooting Guide
Cisco Prime Network Registrar IPAM 8.1.1 Disaster Recovery Guide
6
It is recommended that the DBMover script is
run
at least once daily.
Note the dbmover-wrapper.sh script must be updated
w/ valid email addresses for the ‘to’ and ‘from’ sections
and a smtp domain name.
2.3.1.3 $INCHOME/etc/dbmover-wrapper.sh
This script adds functionality to dbmover.sh
by testing for errors and sending an alert if it
detects there were problems transferring data
from the Production Executive to the DR
Executive. Either this script or the
dbmover.sh script should be run periodically.
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.Cisco Prime Network Registrar
IPAM
This file contains entries for each of the Cisco
Prime Network Registrar IPAM services,
specifying which individual services are
started/stopped when the
$INCHOME/etc/incontrol start/stop script
is run. It is important for the DR Executive
has a copy of this file from the Production
Executive, so that the same environment can
be duplicated on the DR machine.
Any time the default.incontrol file is modified
on the Production Executive for any reason
the updated file
must be copied to
$INCHOME/etc/default.incontrol.primary
on the DR Executive. This file is required for
the automated PromoteExec script that is
utilized during a DR scenario.
2.3.2.2 $INCHOME/etc/incstatus
This script is used to check which Cisco Prime
Network Registrar IPAM services are running
on the system. Generally, this file is kept in
sync with the default.incontrol file above.
That is, when a new service is added or
removed from starting/stopping in
default.incontrol, it is also added or removed