DNA Center Installation Problem

[SecurityEng99]

Hello

I'm trying to install Cisco DNAC on ESXI with recommended resources, but I have been run into fun issues. Right now I have DNAC version 2.3.5.5 is running, but I see this error showing on the top of the GUI

Automation and Assurance services have been temporarily disrupted. The system is working to restore this functionality.

and when I click fore more details, I see the following:

ggregationjobs	ndp	Down	5.0.178	Metrics   |  Logs
pipelineruntime-taskmgr-assurance-1	ndp	Down	5.1.64	Metrics   |  Logs
pipelineruntime-taskmgr-assurance-2	ndp	Down	5.1.64	Metrics   |  Logs
pipelineruntime-taskmgr-base	ndp	Down	5.1.64	Metrics   |  Logs
pipelineruntime-taskmgr-data	ndp	Down	5.1.64	Metrics   |  Logs
pipelineruntime-taskmgr-spa-apps	ndp	Down	5.1.64	Metrics   |  Logs
pipelineruntime-taskmgr-timeseries	ndp	Down	5.1.64	Metrics   |  Logs
release-job	maglev-system	Down	1.0	Metrics   |  Logs
distributed-cache-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
file-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
messagecatalog	fusion	Down	2.1.616.60023	Metrics   |  Logs
task-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
telemetry-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
cnsr-reasoner	fusion	Down	7.28.616.210007	Metrics   |  Logs
apic-em-inventory-manager-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
apic-em-network-programmer-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
apic-em-pki-broker-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
config-archive-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
data-cob	fusion	Down	7.1.616.60023	Metrics   |  Logs
grouping-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
ipam-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
licensemanager	fusion	Down	2.1.616.60023	Metrics   |  Logs
maintenance-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
messaging-persistence-scanner-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
network-design-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
network-validation-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
networkvalidationpyservice	fusion	Down	2.1.616.60023	Metrics   |  Logs
orchestration-engine-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
scheduler-service	fusion	Down	7.1.616.60023	Metrics   |  Logs
search-service	fusion	Down	7.1.616.60023	Metrics   |  Logs

Please advise

[marce1000]

 - Check DNAC VM resources being used with the hypervisor from ESXI and or try to increase memory for the VM , 

 M.

[Tomas de Leon]

You mention that you are trying to install Catalyst Center Release 2.3.5.5 on ESXi. This is problem #1. This is not supported. Although some folks may get this to work, you are or can waste a lot of time in trying to get this work.

The official release for Catalyst Center on ESXi is 2.3.7.4 and is GA. You can download the OVA and deployment on ESXi with no issues (as long as your resources meet specifications). I would advise using the officially supported release for Catalyst Center on ESXi is 2.3.7.4.

• Release Notes for Cisco Catalyst Center on ESXi, Release 2.3.7.4
• Cisco Catalyst Center 2.3.7.4 on ESXi Deployment Guide
• Cisco Catalyst Center 2.3.7.4 on ESXi Administrator Guide

[SecurityEng99]

tried to use the OVA file 2.3.7.4 and I got error below

Failed to deploy OVF package. Cause: A general system error occurred: Transfer failed: Invalid response code: 500.

Any idea about that ?

[Tomas de Leon]

- What version of vsphere or vcenter are you using?
- In order to make things happen a little faster and smoother, I added the OVA to the Content Library on vcenter first. Then deployed from there.  If you did not use content library, try that method.
- also verify the md5sum on OVA after you downloaded from software.cisco.com

[SecurityEng99]

- What version of vsphere or vcenter are you using?   Version 8.0.2.0 and md5sum  looks good. I tried the Content Library as well and no luck. 

[Tomas de Leon]

SecurityEng99,

The error could be related to different causes. You mentioned that the transfer failed in the original post. This is why I suggested the Content Library method. This would eliminate the transfer issue since already in your VMWare enironment.

If you select a new vm from the OVA in the Content Libary and it fails. The next step would look into the vmware logs to see what the exact messages are in regards to the failure.

It is hard to determine without logs and looking thru some of the configuration. The best course of action is to open a Cisco TAC Case so the TAC engineer can properly assess your issues.

Without Logs this is all guess work.