cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
975
Views
4
Helpful
5
Replies

UCCX 8.0 Disaster Recovery System error

fei he
Level 2
Level 2

Hi All

When browse to DRS GUI, no new devices, schedules, or status are be viewed from DRF console but both DRF Master/Local are running.

It is standalone server.

Version - 8.0.2.10000-41

Any solution?

5 Replies 5

Jonathan Schulenberg
Hall of Fame
Hall of Fame

Have you tried restarting the DRF Master, and Local (in that order) daemons?

Hi Jo

I've not done yet. I will get it sort out tomorrow and share the outcomes. Is there any logs require to collect prior DRF restart to avoid logs being over written?

Sent from Cisco Technical Support iPhone App

Hi Jo

i've managed to restart DRF master/local service successfully but there is no change. Error is still there.

Furthermore, i suspected that there are heaps of core dump generated on server. At this point, I will open a TAC case to get both issue addressed.

Thx for your help earlier.

Hi Jo

I opened a TAC for further support.

Thanks for your help.

Cheers

This case is resolved under assistance of TAC.

DRF Master log indicate following error regarding cannot opening certian DRF files:

INFO [main] - drfUtils:ReadXMLObject: Unable to read XML file: /usr/local/platform/conf/drfComponent.xml

INFO [main] - drfUtils:ReadXMLObject: Unable to read XML file: /usr/local/platform/conf/drfHistory.xml

INFO [main] - drfUtils:ReadXMLObject: Unable to read XML file: /usr/local/platform/conf/drfRestoreHistory.xml

INFO [main] - drfUtils:ReadXMLObject: Unable to read XML file: /usr/local/platform/conf/drfConfiguration.xml

All 4 .xml files are corrupted. To restore these files, root access is required (whereas you need to raise TAC case).

Resolution Summry:

  • Through Root, removed the following files to get them regenerated,
    • drfComponent.xml
    • drfHistory.xml
    • drfRestoreHistory.xml
    • drfConfiguration.xml
  • Regenerated ipsec.pem
  • Downloaded ipsec.pem, then Uploaded it as ipsec_trust
  • Regenerated tomcat.pem
  • Downloaded tomcat.pem, then Uploaded it as tomcat_trust
  • Restart Cisco Tomcat, DRF Master and DRF Local services with no joy.
  • Through root deleted Certs
  • Regenerated IPSEC certs again
  • Tried to add the device through CLI with no luck.
  • Through root, accessed drfComponent and added the following,

  10

  10

 

   

 

Then issue resolved.