We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

VSphere configuration issues

Medium Priority
886 Views
Last Modified: 2012-08-13
Hello,

I have 3 ESX Host in a DC Cluster running ESXi, 4.1.0, 260247. I noticed a note/notice that comes up everytime I select DC Cluster then summary, which states that I have Configuration Issues - HA intiated a failover action in cluster DC Cluster in datacenter RAPA DC.

Not sure what this means. I also notice that some times two of my  HOST will grey/red out and then come right back up. I appreciate your help and support.

Thanks,

nimdatx
Comment
Watch Question

Danny McDanielClinical Systems Analyst

Commented:
it means that you have had a host crash or one(or more) hosts were unable to ping the gateway and there was an isolation event.  If you click on events at the cluster level you can confirm the time(s) this has happened, then start working back to figure out which thing happened and what caused it.

Author

Commented:
Operational Status
Danny McDanielClinical Systems Analyst

Commented:
I would confirm that it's been happening alot by going to the Tasks & Events tab.  Otherwise, it might just be a warning/alarm that hasn't been cleared for a long time.

Author

Commented:
all it says is that HOST esx3.rapa.local in RAPA DC is not responding, then all my VMs on that host disconnected. This happened at 4:52:56

Alarm 'Host connection and power state' on esx1.rapa.local changed from Green to Red. Same for my other two host.  It all started connecting back at 4:52:59.

Author

Commented:
I also noticed that I have a duplicate IP address detected on two of my interfaces. The warning came up as soon as all my host/VMs came up. Do you think that it?
Clinical Systems Analyst
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview
Danny McDanielClinical Systems Analyst

Commented:
yep, that's probably your culprit.  
Paul SolovyovskySenior IT Advisor
CERTIFIED EXPERT
Top Expert 2008

Commented:
Check your DNS.  Make sure you can resolve your vCenter from the hosts via FQDN and short name and visa versa from vCenter.  Typically a DNS issue.

Easy way to check is if you login directly to the host everything is fine it's only when using vCenter.

Author

Commented:
ok....DC Cluster Alarm (Yellow Triangle) went away, however I still have alarms on all three ESX host. I have fixed duplicate Ip issues, but not sure why it's still giving me an alarm? I changed the HA isolation to leave power on. I have 2 nics i can use for a management network redundancy and I tried adding another nic under my vSwitch0 - Management Network, but I still got status of no redundancy.

How can I fix this issue?

Thanks,

nimdatx

Author

Commented:
Got it. Had to add nic to Management Network and VMotion switches. All vSwitches needed at least two nics. I then Reconfigure for HA. I also needed to disable SSH tech support and THEN warning went away.

http://comunities.vmware.com/thread/117258?tstart=0

THANKS so much for your help.

nimdatx
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.