Cisco Unity Connection

Disaster Recovery Web Page Is Unresponsive

Document ID: 117545

Updated: Mar 26, 2014

Contributed by Scott Hills, Cisco TAC Engineer.



This document describes that when the Disaster Recovery web page is used to make a Backup and Restore Unity Connection, there can be problems. This article covers one such situation.


When you log into the Disaster Recovery web page and click any option, no pages load.


Ensure that Disaster Recovery logging is enabled and turned to Debug.

  1. Go to the Cisco Unified Serviceability web page.
  2. Choose Trace > Configuration.
  3. From the Server* drop-down list, choose the server.
  4. From the Service Group* drop-down list, choose Backup and Restore Services.
  5. From the Service* drop-down list, choose Cisco DRF Local (Active).
  6. Ensure that the Trace On check box is checked.
  7. From the Debug Trace Level drop-down list, choose Debug.

Next, reproduce the issue. You might need to restart the DRF master and Local Services in order to conduct a fresh test.

  1. Choose Cisco Unified Serviceability.
  2. Choose Tools > Control Center - Network Services.
  3. Find Backup and Restore Services and Stop and Start Cisco DRF Local and Cisco DRF Master.

Then use the Real Time Monitoring Tool in order to collect the traces:

  1. Go to Trace & Log Central.
  2. Choose Collect Files.
  3. Click Next in order to Select System Services/Applications.
  4. Check both check boxes beside Cisco DRF Local and Cisco DRF Master.

  1. Click Next.
  2. Set the time range of your test and select a Download location.
  3. Click Finish. This starts the collection of logs to the location you specified.

Below are excerpts from logs be sure to notice on the DRF Master Log is showing Unable to create input/output stream to client Fatal Alert received: Bad Certificate.

The DRF Local Logs show:

2014-02-10 11:08:15,342 DEBUG [main] - drfNetServerClient.
Reconnect: Sending version id:
2014-02-10 11:08:15,382 ERROR [main] - NetworkServerClient::Send failure;
2014-02-10 11:08:15,384 FATAL [NetMessageDispatch] - drfLocalAgent.drfLocal
Worker: Unable to send 'Local Agent' client identifier message to Master Agent.
This may be due to Master or Local Agent being down.

The Master Logs show:

2014-02-10 11:19:37,844 DEBUG [NetServerWorker] - Validated Client. IP = Hostname = Request is from a Node within the
2014-02-10 11:19:37,844 DEBUG [NetServerWorker] - drfNetServerWorker.drfNet
ServerWorker: Socket Object InpuputStream to be created
2014-02-10 11:19:37,850 ERROR [NetServerWorker] - drfNetServerWorker.drfNet
ServerWorker: Unable to create input/output stream to client Fatal Alert
received: Bad Certificate


In this case there is a problem with the IPSec certificate on the server and you need to regenerate it, delete the ipsec-trust certificate, and load a new one. Complete these steps in order to address the issue:

  1. Log onto the OS Administration page.
  2. Choose Security > Certificate Management > find.
  3. Click ipsec.pem file and then click regenerate.
  4. After the successful generation of the ipsec.pem file, download the file.
  5. Go back to the certificate management page.
  6. Delete the current corrupted ipsec-trust entry.
  7. Upload the downloaded ipsec.pem file as a ipsec-trust.
  8. Restart DRF Master and DRF Local.
Updated: Mar 26, 2014
Document ID: 117545