VMware Cloud Community
billdossett
Hot Shot
Hot Shot

vmware cloud foundation esxi host validation failing

so I posted about this before... and I am now deploying with VIA...

after imaging with VIA, I have four hosts, all 4 have vswitch0 and all four have vmnic0 connected to vswitch 0 at 10Gb.

All  four on VMCF validation have wornings 

 

ESXi host 192.168.25.182 (terrapin-esxi02) has 0 physical NICs connected to vSwitch0 (Expecting 1)
VM network does not exist on ESXi host 192.168.25.182 (terrapin-esxi02) - example screen shot attached.
 
They are emulex cards, OneConnect, model isn't specifically on the supported list, but have been using them with VMware and built VSAN cluster with them in vsphere/esxi 7U1 with no problems so far...  not really sure what else I can do on this, its a warning so I can proceed once I get rid of a couple of other pesky errors... but not too hopeful.
 
 
 

 

 

Bill Dossett
0 Kudos
3 Replies
shank89
Expert
Expert

For the portgroup error, ensure all hosts have the vm port group and untagged.

 

Also check the bring up log for any finer details.  If they are just warnings and you are sure its all good, you may be able to proceed by acknowledging the errors/warnings.

Shashank Mohan

VCIX-NV 2022 | VCP-DCV2019 | CCNP Specialist

https://lab2prod.com.au
LinkedIn https://www.linkedin.com/in/shankmohan/
Twitter @ShankMohan
Author of NSX-T Logical Routing: https://link.springer.com/book/10.1007/978-1-4842-7458-3
0 Kudos
billdossett
Hot Shot
Hot Shot

all switches have vm portgroup and it is untagged also have management portgroup with vmkernel. also  untagged...  my screen grab apparently did not get attached...  all exactly like imaging appliance left them and imaging appliance seemed happy with all of it... so I guess I will try and proceed as soon as I figure out why it can't ping my time server when clearly I can ping the time server from the hosts...  and a couple of other small items.

Bill Dossett
0 Kudos
billdossett
Hot Shot
Hot Shot

so I did a fresh run... the logs are voluminous - but I found this...

2021-01-26T15:30:24.000+0000 [bringup,779066e0aab7759c,fbb3] INFO [c.v.e.s.c.u.c.SshCommandExecuter,pool-2-thread-20] Command 'esxcli network vswitch standard list' output: vSwitch0
Name: vSwitch0
Class: cswitch
Num Ports: 2816
Used Ports: 4
Configured Ports: 128
MTU: 1500
CDP Status: both
Beacon Enabled: false
Beacon Interval: 1
Beacon Threshold: 3
Beacon Required By:
Uplinks: vmnic0
Portgroups: VM Network, Management Network
Exit Code: 0

 

this is clearly listing vSwitch0 with VM Network and vnmnic0 is connected... however the warning under ESXi host configuration validation is:

ESXi host 192.168.25.182 (terrapin-esxi02) has 0 physical NICs connected to vSwitch0 (Expecting 1)
VM network does not exist on ESXi host 192.168.25.182 (terrapin-esxi02)
 
when I get down to vSphere Network Validation then the step is skipped ,
Validation skipped due to internal error...  I assume because of the error above?
 
but also I have 
 
IP address pool.ntp.org is not pingable from ESXi host 192.168.25.181
 
under network configuration validation - is it literally looking for IP addresses?  I use pool as it always responds whereas individual IP addresses may not... and when I login to hosts, they can all ping pool.ntp.org 100% - my firewall allows time syncing as my many systems on my network sync to external NTP.
 
At this point I have stopped making any progress so I am going to go back to working on my NSX-T deploy - I thought that might be easier to bring up via VCF, but I have a good blog to follow now for NSX-T so will see how far I can get with that this time.
 
Thanks
Bill
 
Bill Dossett
0 Kudos