We have successfully upgraded VMware VCenter & ESXi environment from 7U3 to 8U1 2-3 weeks back. We noticed that Host profile was at time of 7U3. Now we extracted host profile from a upgraded ESXi version 8 node and trying to apply to other nodes. Its getting failed. However when we edit host profile and un-check all four physical NICs from host profile and then when we apply the host profile, it apply successfully
As you unchecked all the NICs and it works well, so the issue could be related to some configuration parameter related to NICs.
Did you get a chance to check the hostd log on the ESXi node ? That will give you more information on why the operation failed with specific errors related to the configuration.
This article may not be related to this issue, just a reference for you to check hostd log on the ESXi node
https://kb.vmware.com/s/article/1039148
Hope this helps!! Or you can attach the hostd.log here, I can check if I see any errors related to the operation.
Regards,
Suresh
Yes all four NICs are working fine.
Some information from hostd log file
2023-05-19T13:23:58.590Z In(166) Hostd[2100266]: [Originator@6876 sub=Default] IPMI SEL sync took 0 seconds 0 sel records, last 3
2023-05-19T13:24:00.496Z Wa(164) Hostd[2100241]: [Originator@6876 sub=Hostsvc.NetworkProvider] Skip saving dvport dvSwitch-651 to : filePath empty
2023-05-19T13:24:00.496Z Wa(164) Hostd[2100241]: [Originator@6876 sub=Hostsvc.NetworkProvider] Skip saving dvport dvSwitch-652 to : filePath empty
2023-05-19T13:24:00.496Z Wa(164) Hostd[2100241]: [Originator@6876 sub=Hostsvc.NetworkProvider] Skip saving dvport dvSwitch-140 to : filePath empty
2023-05-19T13:24:00.497Z Wa(164) Hostd[2100241]: [Originator@6876 sub=Hostsvc.NetworkProvider] Skip saving dvport dvSwitch-630 to : filePath empty
2023-05-19T13:24:00.497Z Wa(164) Hostd[2100241]: [Originator@6876 sub=Hostsvc.NetworkProvider] Skip saving dvport dvSwitch_iSCSI_B-22 to : filePath empty
2023-05-19T13:24:00.498Z Wa(164) Hostd[2100241]: [Originator@6876 sub=Hostsvc.NetworkProvider] Skip saving dvport dvSwitch_iSCSI_B-7 to : filePath empty
2023-05-19T13:24:00.499Z Wa(164) Hostd[2100241]: [Originator@6876 sub=Hostsvc.NetworkProvider] Skip saving dvport dvSwitch_iSCSI_A-22 to : filePath empty
Hostd[2100271]: [Originator@6876 sub=Hostsvc.NetworkProvider opID=02ad1d28 sid=52c35ef1 user=dcui:vsanmgmtd] Refreshing the entire network configuration...
2023-05-19T13:41:00.296Z In(166) Hostd[2100271]: [Originator@6876 sub=Hostsvc.NetworkProvider opID=02ad1d28 sid=52c35ef1 user=dcui:vsanmgmtd] Unable to enable WOL Unable to complete Sysinfo operation. Please see the VMkernel log file for more details.: Not supported
2023-05-19T13:41:00.296Z Wa(164) Hostd[2100271]: [Originator@6876 sub=Hostsvc.NetworkProvider opID=02ad1d28 sid=52c35ef1 user=dcui:vsanmgmtd] WOL capability for nic cannot be turned on.probable bug file against driver: ntg3
2023-05-19T13:41:00.315Z In(166) Hostd[2100271]: [Originator@6876 sub=Hostsvc.NetworkProvider opID=02ad1d28 sid=52c35ef1 user=dcui:vsanmgmtd] Unable to enable WOL Unable to complete Sysinfo operation. Please see the VMkernel log file for more details.: Not supported
2023-05-19T13:41:00.315Z Wa(164) Hostd[2100271]: [Originator@6876 sub=Hostsvc.NetworkProvider opID=02ad1d28 sid=52c35ef1 user=dcui:vsanmgmtd] WOL capability for nic cannot be turned on.probable bug file against driver: ntg3
2023-05-19T13:41:00.329Z In(166) Hostd[2100263]: [Originator@6876 sub=Internalsvc.HostsvcManager opID=02ad1d2b sid=52c35ef1 user=dcui:vsanmgmtd] Start refresh VSAN datastore in Hostd
These messages looks pretty general for me. I dont see any messages related to hostprofile (applying / error message related to HP). Can you please check for the error message which you saw in the webclient in hostd log and share 50 lines before and after the error message or attach the hostd log file in the reply.
I am not able to see any related error (which I see in the webclient) in the logs
Is there any change in vmnic ordering post upgrade?
No. Not a single change was done. is there any further log we can check or any possibility to enable debug logging so we can see what's happening
My issue is resolved. I just put the ESXi host in maintenance mode then reboot the ESXi (earlier we were not rebooting the ESXi ) and then apply the Host Profile
Strange. Good to know that the issue is resolved. VMware products now a days behaves like windows server...reboot fixes most of the issues
