edmandsj
Enthusiast
Enthusiast

'Host CPU/memory/connection' on (HOST) changed from Green to Gray....then Gray to Green?

Jump to solution

Hey Everyone,

I am trying to track down an issue with one of my two hosts. My Cluster (2 hosts in HA/vMotion) is fairly basic but runs lots of VM's that require 100% uptime (as if we want to accept less Smiley Wink ). Below is the output that I receive every couple of weeks. It's a little concerning to know that for some reason a node is dropping out, or is it even dropping out? I don't see any vMotion alerts or tasks within this time frame. Nothing seems to break. Uptime on each VM and the node in question leads me to believe that nothing actually goes wrong, but it may be worse than I think. I mean it only does this for 17 seconds...how bad could it be, right?

I am assuming 'Host memory usage', 'Host cpu usage', 'Host service console swap rates', etc... are going from Green to Gray and then Gray to Green means that it is not a resource problem, just an indicator that it is "grayed out" because it has no information to report and/or a lost connection.

I suppose I am wondering if this is network related, host hardware related, vsphere related, or something I can't even think of. The host disconnects for 7 seconds and no vMotioning happens. I believe that 30 seconds is the rule before it vMotions? I mean, I'd rather not vMotion if I can avoid it.

Either way, what do you think?

Alarm 'Host service console swap rates' on (HOSTNAME) changed from Gray to Green
info
7/6/2011 7:53:35 PM
(HOSTNAME)

Alarm 'Host memory usage' on (HOSTNAME) changed from Gray to Green
info
7/6/2011 7:53:35 PM
(HOSTNAME)

Alarm 'Host cpu usage' on (HOSTNAME) changed from Gray to Green
info
7/6/2011 7:53:35 PM
(HOSTNAME)

Alarm 'Host is down' on (HOSTNAME) sent email to (EMAIL ADDRESS);
info
7/6/2011 7:53:26 PM
(HOSTNAME)

Alarm 'Host is down' on (HOSTNAME) triggered an action
info
7/6/2011 7:53:26 PM
(HOSTNAME)

Alarm 'Host is down' on (HOSTNAME) changed from Yellow to Green
info
7/6/2011 7:53:26 PM
(HOSTNAME)

Alarm 'Host connection and power state' on (HOSTNAME) changed from Red to Green
info
7/6/2011 7:53:26 PM
(HOSTNAME)

Established a connection
info
7/6/2011 7:53:25 PM
(HOSTNAME)

Established a connection
info
7/6/2011 7:53:25 PM
(HOSTNAME)

Alarm 'Host connection and power state' on (HOSTNAME) sent email to (EMAIL ADDRESS);
info
7/6/2011 7:53:20 PM
(HOSTNAME)

Alarm 'Host connection failure': an SNMP trap for entity (HOSTNAME) was sent
info
7/6/2011 7:53:20 PM
(HOSTNAME)

Alarm 'Host connection failure' on (HOSTNAME) triggered an action
info
7/6/2011 7:53:20 PM
(HOSTNAME)

Alarm 'Host connection failure' on (HOSTNAME) changed from Gray to Gray
info
7/6/2011 7:53:20 PM
(HOSTNAME)

Alarm 'Host service console swap rates' on (HOSTNAME) changed from Green to Gray
info
7/6/2011 7:53:19 PM
(HOSTNAME)

Alarm 'Host memory usage' on (HOSTNAME) changed from Green to Gray
info
7/6/2011 7:53:19 PM
(HOSTNAME)

Alarm 'Host cpu usage' on (HOSTNAME) changed from Green to Gray
info
7/6/2011 7:53:19 PM
(HOSTNAME)

Alarm 'Host is down' on (HOSTNAME) changed from Green to Yellow
info
7/6/2011 7:53:19 PM
(HOSTNAME)

Alarm 'Host connection and power state' on (HOSTNAME) triggered an action
info
7/6/2011 7:53:19 PM
(HOSTNAME)

Alarm 'Host connection and power state' on (HOSTNAME) changed from Green to Red
info
7/6/2011 7:53:19 PM
(HOSTNAME)

Host is not responding
error
7/6/2011 7:53:18 PM
(HOSTNAME)

0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal

My memory don't allow me to hold records for long Smiley Wink. Last year I believe I have seen this problem and it was a bug. There were a patch for this also. It was a BUG which will bother you every now and then, trust me there was no problem at all from the environment perspective.

I don't remember the KB article or the patch revision talking about this, but you may need to look at the kb.vmware.com to see if you find any.

View solution in original post

0 Kudos
5 Replies
admin
Immortal
Immortal

My memory don't allow me to hold records for long Smiley Wink. Last year I believe I have seen this problem and it was a bug. There were a patch for this also. It was a BUG which will bother you every now and then, trust me there was no problem at all from the environment perspective.

I don't remember the KB article or the patch revision talking about this, but you may need to look at the kb.vmware.com to see if you find any.

0 Kudos
Mancio76
Enthusiast
Enthusiast

Hy,

I have the same problem!!

Have you found a solution?

thanks

Andrea

0 Kudos
edmandsj
Enthusiast
Enthusiast

I believe it was a bug. upgraded to vsphere 5 and everything is ok.

0 Kudos
Mancio76
Enthusiast
Enthusiast

ok

thanks

0 Kudos
Mancio76
Enthusiast
Enthusiast

sorry, on last thing

what version didi you have?

thanks

Andrea

0 Kudos