Skip to main content

I am trying to deploy Prism Central but unable to do that, getting below error. Not sure what I am doing wrong, this happens during post deployment.

 

 

How much resources does the node/cluster has? Looks like the environment is a bit slow. 


I have 2 node cluster, presently no witness node is installed, do you think might that be the reason?. I have sufficient resource 256 GB ram and 40 Core CPU.


No that should not be an issue for now. Are you installing Prism Central in a different VLAN then where the CVM and AHV reside?

If so, are all firewall rules in place? Software Type : Ports and Protocols


Hello,

I dont have any firewall and all are in same broadcast domain, VM is getting created and I can even ping the IP address of Central. During deployment I can see some micro services option where it is something showing an internal interface, which is default selected and have the IP assigned 192.168.5.1 as gateway and 2-62 as IP address as it is asking for 5 free. Do we need 192.168.5.1 somewhere in my switch?


The 192.168.5.x is the Internal Network for prism central. Just leave it. Are you 100% sure prism central is not installed correctly? Can you go https://>pcvm_ip>:9440 and login and configure PC? 


I tried browsing it shows me certificate error but once I proceed page does not loadup and with error. This happens during post deployment only.


What does the command “cluster start” show when running in the Prism Central VM?


Are you saying to ssh to Central and check this command, I will check this tomorrow, I am done for today. Normally what the screenshot says which I posted initially, what may be the reason?


Hey ​@Himanshusince1989 

A few things to check:

  1. Verify firewall rules allow necessary ports (see ​@JeroenTielen  link).

  2. SSH into Prism Central VM and run cluster status to see which services failed.

  3. Double-check the internal IP/subnet/gateway settings provided during Prism Central deployment.

Let us know how it goes.


Appreciate your help everyone. CVM were out of timesync, once updated with the correct NTP server then it for deployed.