• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • Unexplored Territory Podcast
  • HA Deepdive
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

vCenter Server 4.0 Patch 1

Duncan Epping · Aug 21, 2009 ·

Don’t think many people have noticed this KB article yet or even experienced this issue with HA but nevertheless it’s worth mentioning. Apparently there’s an issue with HA in vCenter 4.0 when a class A network is being used. When a node fails this will not be detected and thus the fail-over of VMs will not occur. Although not many customers are using these class A ranges it is something I think you all should be aware of. This issue has been resolved and VMware released the following KB article which contains a link to the patch:

http://kb.vmware.com/kb/1013013
A vSphere 4.0 VMware High Availability cluster may not failover virtual machines when ESX is configured with certain IP addresses

You experience these symptoms:

  • In vCenter 4.0, VMware HA might not failover virtual machines when a host failure occurs.
  • When the ESX host’s IP address in a VMware HA enabled cluster is configured with certain IP addresses, the node failure detection algorithm fails.
  • You are susceptible to this issue when all of your Service Console Port(s) or Management Network IP address(s) on your ESX host fall within the following range:
    3.x.x.x – 9.x.x.x
    26.x.x.x – 99.x.x.x

Note: You are not affected if one of Service Console Port(s) or Management Network IP address(s) on your ESX host falls outside of this range.

Related

Server bug, ESX, esxi, ha, update, upgrade, vSphere

Reader Interactions

Comments

  1. Jason Boche says

    21 August, 2009 at 19:02

    Heard about this 2 weeks ago from my SE. Thanks for bringing it out in the open Duncan.

    Jas

  2. Vladan says

    22 August, 2009 at 06:22

    That’s the range where our ESXi 4 test server is sitting… oh my…

    But since I have second management consoles on second management network on different IP range, I am not affected. As I saw in the KB.

    Two solutions: Install the patch or change the ip range for your management console.

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist and Distinguished Engineering Architect at Broadcom. Besides writing on Yellow-Bricks, Duncan is the co-author of the vSAN Deep Dive and the vSphere Clustering Deep Dive book series. Duncan is also the host of the Unexplored Territory Podcast.

Follow Us

  • X
  • Spotify
  • RSS Feed
  • LinkedIn

Recommended Book(s)

Advertisements




Copyright Yellow-Bricks.com © 2025 · Log in