i have prepared an ESXi Host with VMWare ESXi 6.7 , installed VCSA as a Guest on the same host . i setup the IP of VCSA with the same range of ESXi Management IP , after installation i am unable to connect to VCSA through network , but i can connect / Manage ESXi through Network ,
do we have any specific configuration on ESXi Host for the Guest
It's not unusual to have both, ESXi, and vCenter in the same subnet, so that's not an issue.
There's got to be another reason for the issue you have.
Are you able to login to the vCSA's console and ping out from there, e.g. to the default gateway?
André
yes, I have ESXI and VCSA on the same VLAN. Assume you are using the same Standard network (standard switch) or did you add a vDS/Port group and not tag correctly?
In >95% of my setups VCSA is always in the same Subnet/VLAN as the ESXi Hosts.
Things which may go wrong
- You have forgot to set a VLAN ID on the Virtual Machine Portgroup
- The ESXi Management VMKernel use different vmnics (uplinks) as your VM Portgroup and you configurated the pSwitch ports differently
- You have multiple Uplinks in an active/active manner an one of them is a faulty one ... this the the one where your VCSA is located on
But most likley you have missconfigurated the Gateway/DNS of the VCSA.
Do you have another VM which is located on the Same Portgroup(and Host) which can you test?
Regards,
Joerg
It's not a complex situation, please check the following points again:
1. IP address & Subnet mask of your ESXi VMKernel port (management IP Address) and also assigned IP combination for the VCSA in deployment wizard.
2. VLAN IDs if you assigned for the management port group and VM Network.
3. Uplinks of vSwitch for that VM Network, and also its failover order (vmnic). Check in both of vSwitch settings and also port group settings.
4. Connect to the VCSA Bash Shell and ping your client and also the ESXi hosts from this vCenter server and check the results.
5. Deploy a test VM that is connected to the port group that VCSA is still connected to that, then check the network connectivity again.
i am checking all these points mentioned & update here