02-23-2018 12:50 PM - edited 03-17-2019 12:16 PM
Hi Guys,
I am getting these error while trying to view Backup devices on call manager.
Any help please?
Solved! Go to Solution.
02-25-2018 03:35 PM
02-23-2018 10:36 PM
02-23-2018 11:53 PM
Hi,
Firstly, Check for NTP server reachability from CUCM. Secondly, try restarting Cisco DRF Master and Local in PUB.
regds,
aman
02-24-2018 01:13 AM
Hi,
I tried to use different browser, restarted DRF and TOMCAT. Got the NTP fixed still the same issue.
Thanks,
Muk
02-25-2018 02:40 PM
Hi @voipeee,
you are using a Linux OS account (used by OS Admin and DRS) ... are you able to log in the OS Admin with no problem?
Best regards,
Marcelo Morais
02-26-2018 05:33 AM
Hi @Marcelo Morais,
Yes, everything works fine. Even I am able to login to Admin,OS as well as DRS page. But when I click Backup devices nothing happens.
I thing this problem started after I regenerated few certificates before sometime however, I am not sure about this. And I regenerated Cisco Tomcat and restarted the service after that.
02-25-2018 03:35 PM
02-26-2018 12:45 AM
Hi,
In addition to what Vinod has mentioned, are the IP addresses of sftp created under Backup devices reachable from CUCM?
regds,
aman
02-26-2018 05:38 AM
Hi @Aman Soi,
Thanks but I think it has nothing to do with the reachable because even if I have to add the devices I have to go to the same page.
Thanks,
Muk
02-27-2018 02:11 AM
Hi,
I was referring to Backup devices if already created in CUCM.
Good the issue got resolved.
regds,
aman
02-26-2018 05:36 AM
Hi @Aeby Vinod,
I agree with you and this might be the case. I will update you about the status.
Thanks in advance.
02-26-2018 06:28 AM
Hi @Aeby Vinod,
The ipsec certificate is valid. I have pasted here certificate along with the expiry date. Thanks for your help.
CallManager 02/08/2023 Self-signed certificate generated by system |
CallManager-ECDSA 08/19/2022 Self-signed certificate generated by system |
CallManager-trust CAPF-16f3496d Self-signed RSA CAPF 12/16/2016 |
CallManager-trust Cisco_Manufacturing_CA_SHA2 CA-signed RSA Cisco_Manufacturing_CA_SHA2 Cisco_Root_CA_M2 11/12/2037 |
CallManager-trust Cisco_Root_CA_M2 Self-signed RSA Cisco_Root_CA_M2 Cisco_Root_CA_M2 11/12/2037 |
CallManager-trust CAPF-d201ea8d Self-signed RSA CAPF-d201ea8d CAPF-d201ea8d 02/08/2023 |
CallManager-trust Cisco_Manufacturing_CA CA-signed RSA Cisco_Manufacturing_CA Cisco_Root_CA_2048 05/14/2029 |
CallManager-trust 02/08/2023 Trust Certificate |
CallManager-trust CAPF-962bd1bb Self-signed RSA CAPF-962bd1bb CAPF-962bd1bb 03/26/2018 |
CallManager-trust CAPF-49e87588 Self-signed RSA CAPF-49e87588 CAPF-49e87588 12/16/2016 Trust Certificate |
CallManager-trust 12/16/2016 Trust Certificate |
CallManager-trust Cisco_Root_CA_2048 Self-signed RSA Cisco_Root_CA_2048 Cisco_Root_CA_2048 05/14/2029 |
CallManager-trust CAP-RTP-001 Self-signed RSA CAP-RTP-001 CAP-RTP-001 02/06/2023 |
CallManager-trust CAPF-0aa24f9a Self-signed RSA CAPF-0aa24f9a CAPF-0aa24f9a 02/08/2023 Trust Certificate |
CallManager-trust ACT2_SUDI_CA CA-signed RSA ACT2_SUDI_CA Cisco_Root_CA_2048 05/14/2029 |
CallManager-trust CAP-RTP-002 Self-signed RSA CAP-RTP-002 CAP-RTP-002 10/10/2023 |
CallManager-trust CAPF-1ddfa6e0 Self-signed RSA CAPF-1ddfa6e0 CAPF-1ddfa6e0 03/26/2018 Trust Certificate |
CAPF CAPF-d201ea8d Self-signed RSA CAPF-d201ea8d 02/08/2023 Self-signed certificate generated by system |
CAPF-trust CAPF-16f3496d Self-signed RSA CAPF-16f3496d CAPF-16f3496d 12/16/2016 |
CAPF-trust Cisco_Manufacturing_CA_SHA2 CA-signed RSA Cisco_Manufacturing_CA_SHA2 Cisco_Root_CA_M2 11/12/2037 |
CAPF-trust Cisco_Root_CA_M2 Self-signed RSA Cisco_Root_CA_M2 Cisco_Root_CA_M2 11/12/2037 |
CAPF-trust CAPF-d201ea8d Self-signed RSA CAPF-d201ea8d CAPF-d201ea8d 02/08/2023 |
CAPF-trust Cisco_Manufacturing_CA CA-signed RSA Cisco_Manufacturing_CA Cisco_Root_CA_2048 05/14/2029 |
CAPF-trust CAPF-962bd1bb Self-signed RSA CAPF-962bd1bb CAPF-962bd1bb 03/26/2018 |
CAPF-trust Cisco_Root_CA_2048 Self-signed RSA Cisco_Root_CA_2048 Cisco_Root_CA_2048 05/14/2029 |
CAPF-trust CAP-RTP-001 Self-signed RSA CAP-RTP-001 CAP-RTP-001 02/06/2023 |
CAPF-trust ACT2_SUDI_CA CA-signed RSA ACT2_SUDI_CA Cisco_Root_CA_2048 05/14/2029 |
CAPF-trust CAP-RTP-002 Self-signed RSA CAP-RTP-002 CAP-RTP-002 10/10/2023 |
ipsec 02/08/2023 Self-signed certificate generated by system |
ipsec-trust 02/08/2023 Trust Certificate |
ITLRecovery 08/15/2037 Self-signed certificate generated by system |
tomcat 02/08/2023 Self-signed certificate generated by system |
tomcat-ECDSA 08/19/2022 Self-signed certificate generated by system |
tomcat-trust 08/19/2022 Trust Certificate |
tomcat-trust 08/19/2022 Trust Certificate |
tomcat-trust 09/26/2022 Trust Certificate |
tomcat-trust 02/08/2023 Trust Certificate |
tomcat-trust 09/25/2022 Trust Certificate |
tomcat-trust 02/08/2023 Trust Certificate |
tomcat-trust VeriSign_Class_3_Secure_Server_CA_-_G3 CA-signed RSA VeriSign_Class_3_Secure_Server_CA_-_G3 VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5 02/07/2020 Trust Certificate |
tomcat-trust 09/25/2022 Trust Certificate |
tomcat-trust 09/26/2022 Trust Certificate |
TVS fl.us 12/13/2016 |
02-26-2018 01:19 PM
Hey Abey,
This worked for me. Basically I regenerated this ipsec before few days and it displayed to restart DRS M/A however, this is out of mind now. Thank you so much for your help! I really appreciate.
Thanks,
Muk
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide