VMware vSphere

 View Only
  • 1.  VMKernel IP mismatch problem

    Posted Jul 26, 2012 03:52 AM

    I have an ESX 5 host with a vmkernel management interface ip address of 10.10.10.31. I can resolve the host name to the address and it's pingable. vCenter has no alarm state on the host.

    The hypervisor however reports the host address as 10.10.50.31?

    Anyone seen this before?

    Thanks

    Brendan



  • 2.  RE: VMKernel IP mismatch problem

    Posted Jul 26, 2012 07:33 AM

    Where dos the hypervisor report a wrong IP ? in the DCUI or in vCenter ?

    Are you sure the name does not resolve to 2 IP using round robin ?



  • 3.  RE: VMKernel IP mismatch problem

    Posted Jul 26, 2012 09:24 AM

    Reports it incorrectly in the DCUI. Only single record in DNS

    Cheers,

    Brendan

    Sent from smartphone.



  • 4.  RE: VMKernel IP mismatch problem

    Posted Jul 26, 2012 07:42 AM

    Do you have any other vmkernel IPs set up? vmotion? I've seen the wrong IP displayed before, in the DCUI, after using host profiles.



  • 5.  RE: VMKernel IP mismatch problem

    Posted Jul 26, 2012 09:24 AM

    Yes vmotion and fault tolerance vmk. The FT IP is the one the DCUI reports as its management IP.

    Tried removing FT vmk. No change

    Cheers,

    Brendan

    Sent from smartphone.



  • 6.  RE: VMKernel IP mismatch problem
    Best Answer

    Posted Jul 26, 2012 10:56 AM


  • 7.  RE: VMKernel IP mismatch problem

    Posted Jul 26, 2012 09:26 PM

    Beauty that article pointed me in the right direction!

    I tried the command esxcfg-advcfg -s vmk1 /Net/ManagementIface which is supposed to resolve "If you have your management IP address on a vmk number other than vmk0 the DCUI console will display the wrong IP address" may have worked in 4.x but not in 5

    The way I corrected this was to create a new management interface 'vmk0', disconnect the host, reconnect with new management IP on vmk0, remove the vmk3 adapter, reconfigure the vmk0 to the correct address, disconnect and reattach the host. I was also changing the DNS and host file records whilst doing this.

    All looks good now :smileyhappy:

    Cheers for you time guys,

    Brendan