Getting HA Cluster IP config errors

[sgumm1]

In VI 3.5 with a HA cluster I am getting an IP resolution inconsistency. For some reason the secondary Console network IP used as a heartbeat is conflicting with the primary Console network IP.

# ./ft_gethostbyname

ft_gethostbyname(INIT) FAILED!

It should respond sonmething like this:

# ./ft_gethostbyname

10.223.127.203 vm3650cos001

192.168.100.51 vm3650cos001

[mark_chuman]

I am seeing the same thing. I only have one service console connection. Is /etc/opt/vmware/aam structure empty? Mine is, I think this is part of the problem.

[mike_laspina]

Hello,

I looks like a vmkernel routing issue.

Your default route should be the primary console 10.223.127.193

esxcfg-route -a default 10.223.127.193

then add a secondary route using

esxcfg-route -a 192.168.200.0/24 192.168.200.1

As you can see that is where it is defined in vmware.