Cisco Cisco Prime Network Registrar 8.0 トラブルシューティングガイド
3.1.2.2 Restart the DR Executive Cisco Prime Network Registrar IPAM
services
3.1.2.2.1 Linux/Solaris
Run the Cisco Prime Network Registrar IPAM script to restart
all services on the DR Executive:
> $INCHOME/etc/incontrol restart
> $INCHOME/etc/incontrol restart
3.1.3 Return to Normal
This section describes the procedure necessary to return to
normal operation where the Production Executive is in use,
and the DR Executive is in standby mode.
and the DR Executive is in standby mode.
3.1.3.1 Change the IP of the DR Executive
Follow the same procedure described above to change
the IP of the DR Executive back to its original IP.
the IP of the DR Executive back to its original IP.
3.1.3.2 Stop Cisco Prime Network Registrar IPAM Services on DR
Executive
3.1.3.2.1 Linux/Solaris
Run the Cisco Prime Network Registrar IPAM script to stop
all services on the DR Executive:
> $INCHOME/etc/incontrol stop
> $INCHOME/etc/incontrol stop
->
3.1.3.3 Demote the DR Executive to standby status
Revert the DR Executive to standby by running the
“demote” script which will configure the system to
“demote” script which will configure the system to
start only MySQL:
> $INCHOME/etc/support/DemoteExec.sh
3.1.3.4 Start Cisco Prime Network Registrar IPAM Services on DR
Executive
3.1.3.4.1 Linux/Solaris
Run the Cisco Prime Network Registrar IPAM script to start
all services on the DR Executive:
> $INCHOME/etc/incontrol start
> $INCHOME/etc/incontrol start
3.1.3.5 Copy the DR Executive database
The DR Executive database will need to be copied
back to the Production Executive Database if changes
were made while the Production server was offline. If
back to the Production Executive Database if changes
were made while the Production server was offline. If
no changes were made, this step can be skipped.