ESX: HA Error – Could not reach isolation address

Posted on Updated on

 vmware01 

Case on my customer, when I enable HA on DMZ Cluster, I get this error “Issue detected on esx.vmware in HA: Could not reach isolation address:  none specified”.

They have 8 ESX Server 3.5 Update 2 dan 1 vCenter 2.5 Update 3.

Solution:

1.       Check your Service Console Default Gateway on that host. Ensure you have the right IP for Gateway.

2.       Re-enable HA on that host.

Hopefully this help.

3 thoughts on “ESX: HA Error – Could not reach isolation address

    solodd said:
    October 1, 2010 at 12:15 am

    Check if you default gateway on the firewall accept ping request and sends pind responses
    Ping can be disabled on firewall DMZ interface.
    You can configure das.isolationaddress on trusted network

    Chris said:
    October 11, 2010 at 2:29 am

    Thanks for this tip – sure enough my management network did not have a default gateway assigned and once I added it in there I was able to setup HA with no problems.

      iswarade responded:
      November 2, 2010 at 12:08 pm

      Nice to help.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s