VMware

Odd behaviour with host after reboot in v7 cluster

Hello all,

Running a 2-node cluster under vsphere 7.

* **vSphere Client version 7.0.0.10600**
* Hosts: VMware ESXi, 7.0.0, 16324942

After rebooting the trouble host, the VMkernel adapter for two vmk devices revert IPs, therefore loosing connectivity. I have gone to: host > configure > VMkernel adpaters and explicitly given the static IP addresses. Incidentally, it also looses the value for Syslog.global.logDir, and I have to re-assign the datastore/path. The hosts are booting off USB flash drives, have a small SATA datastore, but everyhing is configured to run (inc. logDir) off NFS from NAS.

Below is the correct IP configuration:

Name IPv4 Address IPv4 Netmask IPv4 Broadcast Address Type Gateway DHCP DNS
—- ————– ————- ————– ———— ———– ——–
vmk0 192.168.2.102 255.255.252.0 192.168.3.255 STATIC 192.168.1.1 false
vmk1 172.16.100.102 255.255.255.0 172.16.100.255 STATIC 0.0.0.0 false
vmk2 192.168.1.152 255.255.252.0 192.168.3.255 DHCP 192.168.1.1 false
vmk3 192.168.1.153 255.255.252.0 192.168.3.255 DHCP 192.168.1.1 false

after reboot, this is what shows up

Name IPv4 Address IPv4 Netmask IPv4 Broadcast Address Type Gateway DHCP DNS
—- ————- ————- ————– ———— ———– ——–
vmk0 192.168.2.102 255.255.252.0 192.168.3.255 STATIC 192.168.1.1 false
vmk1 172.16.3.102 255.255.255.0 172.16.3.255 STATIC 0.0.0.0 false
vmk2 192.168.1.152 255.255.252.0 192.168.3.255 DHCP 192.168.1.1 false
vmk3 192.168.1.153 255.255.252.0 192.168.3.255 DHCP 192.168.1.1 false

Does anyone have any ideas *WHY* this is happening and how to remedy?

Thanks!


View Reddit by MarconicoView Source

Related Articles

One Comment

  1. Once you change the logdir path back and reboot again does it lose it again? I have had this issue specifically when using USB boot devices (in my case, SD cards) because the bootbank gets all messed up somehow. I’m wondering if “state.tgz” on the bootbank is messed up so when you reboot and it reads the config from that, it gets the wrong thing.

    Before getting into more complex solutions, did you try simply removing the problem vmk adapter, rebooting, making sure it is gone, then adding back a new one, rebooting and testing if config sticks?

Leave a Reply

Close