There was a question on VMTN this week about the use of the management IP’s in a “smaller” cluster as the isolation address for vSphere HA. The plan was to disable the default isolation address (default gateway) and then add every management IP as an isolation address. In this case 5 or 6 IP’s would be added. I had to think this through and went through the steps of what happens in the case of an isolation event:
- no traffic between secondary and primary or primary and secondary hosts (depending on whether the primary is isolated or one of the secondary hosts)
- if it was a secondary which is potentially isolated then the secondary will start a “primary election process”
- if it was the primary which is potentially isolated then the primary will try to ping the isolation addresses
- if it was a secondary and there’s no response to the election process then the secondary host will ping the isolation address after it has elected itself as primary host
- if there’s no response to any of the pings (happen in parallel) then the isolation is declared and the isolation response is triggered
Now the question is: will there be a response when the host tries to ping itself while it is isolated, as you need to add all ip-addresses to “isolation address” options for it to make sense… And that is what I tested. It will ping all isolation addresses. All but one will fail, the one that will be successful is the management IP address of the host which is isolated. (You can still ping your own IP when the NICs are disconnected even.) Leaving the VMs running as one of the isolation addresses responded.
In other words, don’t do this. The isolation address should be a reliable address outside of the ESXi host, preferably on the same network as the management.