Home > VMware > vCenter 4.1 unable to monitor host hardware status of ESX/ESXi hosts

vCenter 4.1 unable to monitor host hardware status of ESX/ESXi hosts

We recently upgraded our vCenter environment from vCenter 4.0 to vCenter 4.1 so that we could start migrating our ESX/ESXi boxes to ESXi 4.1 since vCenter 4.1 is required to manage ESXi 4.1 hosts. We carried out an in-place upgrade and everything went on well without any issues and we started migrating ESX hosts to ESXi 4.1.

One day we noted that a disk had failed in one of our ESXi Servers but we did not get any alert from vCenter. We rely on vCenter alerts for host hardware status for our ESXi hosts since we cannot install vendor monitoring agents. Realized that the host’s hardware status tab got refreshed only when we manually refreshed or clicked on the host hardware status tab. By default , vCenter is to scan the hosts every 5 minutes for change in status of hardware components. Next we tried to connect to the ESXi Server directly to see if ESXi host was able to detect any change in status of hardware components and ESXi host was able to detect them. This meant that the issue was with Virtual Center.

We then logged a SR with VMware Technical support with whom we had to try out various combinations to rule out all possible issues .

  • We tried to see if ESX host was able to detect status change in hardware components when connected via vSphere client directly. ESXi host was able to detect the status change of hardware components.
  • We were asked to install vCenter 4.1 directly on a VM and see if the issue persisted ( This request was weird I thought !!) . Reason provided was that they wanted to isolate Physical Server issue and also at the same time vCenter 4.1 upgrade issue. We tried to install it freshly on a VM and the issue persisted.
  • We also realized and informed them that vCenter was not able to update hardware status across all ESX/ESXi version of hosts from ESX/ESXi 4.0 to ESX/ESXi 4.1

VMware Technical Support team has finally acknowledged this as a BUG and is currently working on resolution for the same.

What this has meant is that we will have to physically monitor the hosts for any hardware component failure since vCenter hardware alerts wont work !!

Advertisements
Categories: VMware Tags: , ,
  1. JJ Gunn
    March 26, 2011 at 4:25 am

    I have vCenter 4.1 Update 1 installed (build 345043) with ESX/ESXi (348481) and the alerts work sometimes. VMware still has work to do on the auto-updating of the hardware status

    • March 26, 2011 at 7:07 am

      Yes , This issue is still open with VMware and we are yet to get a solution from them . To their credit i must say we never had a problem in the previous versions .

      • Magnus Ericson
        April 28, 2011 at 5:38 pm

        Hi we are having the same issue…have got any more info from vmware ?

      • April 28, 2011 at 11:55 pm

        The Bug is still open with VMware and their engineers are working on this.

  2. Juan Pablo Reyes
    May 3, 2011 at 6:26 pm

    Hi

    There is a link to official information of VMware regarding this Bug?.

    Regards…

    • May 3, 2011 at 7:12 pm

      I am not sure on that but I have the Bug ID case which VMware is working on.

  3. Squuiid
    May 5, 2011 at 12:19 am

    Any updates folks? This is quite the bug and it is very disappointing that VMware still don’t have a fix for it.

    • JJ Gunn
      May 10, 2011 at 7:56 pm

      Hi. I’m currently using Dell hardware (1950, 2950, R610 & R710) Updated BIOS to 3.0.0 for R610 & R710’s and my alerts seem to be working 100%. I installed the latest patch from 4/28/2011 via Update Manager. Currently using ESXi 381591 with vCenter 4.1 (345043).

      I’ll report back if I find any issues. Hope this is helpful. Your environment may be different

      • May 11, 2011 at 6:50 am

        HI – The issue does not seem to be with Hardware since we have tested it with hardware from multiple vendor and still VC is not able to monitor the hardware status of the Servers.

  4. Mannan
    August 8, 2011 at 10:30 pm

    Hi,
    we are able to see the devices in the hardware status tab. My question is, is a there a config file or any other setting through which we can get alerted if there is an hardware issue

    • August 10, 2011 at 7:41 am

      You can use vCenter to configure e-mail alerts for change in hardware status.

  5. Murphy
    August 17, 2011 at 3:12 pm

    has this been resolved yet? any news from VMware?

    • August 19, 2011 at 10:52 am

      No News as such from VMware but it got automatically resolved in our Environment. My Thoughts are it might have been caused by some Windows Patch ..

      • Murphy
        August 19, 2011 at 5:49 pm

        hhmm, i applied all windows updates to my VC but the problem is still there. If I pull a disk VC only notices if I browse to the hardware status tab.

        ESX has all the latest updates too, brand new ESXi 4.1 U1 install and matching VC.

        Dell PE 1950 with all the latest F/W.

      • Syed
        August 19, 2011 at 6:38 pm

        we had the same problem in our environment, we fixed it yesterday itself.. by following the below steps:

        After upgrading to vCenter Server 4.1, we are experience these symptoms:

        1. The search function does not work or is very slow.

        2. Hardware status tab fails to open. (You see the error:Do not have permission for this command)

        Description : we need to follow the below steps to fix this issue.

        1. Stop the VirtualCenter Management Webservices service. For more information, see Stopping, starting, or restarting vCenter services (1003895).

        2. Go Start > Applications > VMware > VMware Tomcat > Configure Tomcat

        3. Click the Java tab.

        4. Double the number in the Maximum memory pool field.

        5. Click OK.

        6. Restart the VirtualCenter Management Webservices service. For more information, see Stopping, starting, or restarting vCenter services (1003895).

        Note: It may take a few minutes after restarting VirtualCenter Management Webservices service for the Search function to start working again. If the issue is not addressed after an adequate amount of time, it may be necessary to further increase the number in the Maximum memory pool field and restart the VirtualCenter Management Webservices service again.

  6. Syed
    August 19, 2011 at 6:36 pm

    we had the same problem in our environment, we fixed it yesterday itself.. by following the below steps:

    After upgrading to vCenter Server 4.1, we are experience these symptoms:

    1. The search function does not work or is very slow.

    2. Hardware status tab fails to open. (You see the error:Do not have permission for this command)

    Description : we need to follow the below steps to fix this issue.

    1. Stop the VirtualCenter Management Webservices service.

    2. Go Start > Applications > VMware > VMware Tomcat > Configure Tomcat

    3. Click the Java tab.

    4. Double the number in the Maximum memory pool field.

    5. Click OK.

    6. Restart the VirtualCenter Management Webservices service.

    Note: It may take a few minutes after restarting VirtualCenter Management Webservices service for the Search function to start working again. If the issue is not addressed after an adequate amount of time, it may be necessary to further increase the number in the Maximum memory pool field and restart the VirtualCenter Management Webservices service again.

    • Murphy
      August 19, 2011 at 7:54 pm

      my problem is not following an upgrade, but a fresh install of the whole setup.

      also the hardware tab does not faile to open… your faults dont seem related to the original post.

    • JJ Gunn
      September 29, 2011 at 11:27 pm

      This makes sense. When I initially built our vCenter I built it for a Large deployment (300 hosts) which cranks up the JAVA memory.

      All vCenters should be built with the large option to avoid these types of errors. You can scale back the memory if you are using a smaller deployment.

  7. September 9, 2011 at 4:06 am

    Same exact problem in our environment…same “its a bug reply” from VMware support with no fix in sight.

    Our temporary workaround is to restart the “VMware VirtualCenter Management Webservices” service via a scheduled task calling on a simple 1-liner powershell script every 24 hours.

    “Invoke-Command -computer NVVC -scriptblock {restart-service “VMware VirtualCenter Management Webservices” -force}”

    Restarting the service causes vCenter to re-poll all the attached hosts for hardware status (among other things).

    • September 9, 2011 at 7:12 am

      For some weird reason , the issue got automatically resolved with the latest windows updates and I assume this is something to do with windows update breaking the communication. If esx is able to detect a hardware failure , check if alarms work at vCenter even if it doesn’t show at the hardware status tab.

  8. Jaime T.
    September 27, 2011 at 11:20 pm

    I was having the exact same issue on the Hardware tab for ESXi 4.1 hosts on a new vCenter 4.1 host. The hardware tab worked on ESX 4.0 hosts, but not the ones I built with ESXi 4.1. Anyway, doubling the java max memory to 2048MB resolved the issue for me. Thanks for the info Syed.

    Jaime

    • Mick
      October 1, 2011 at 1:52 am

      nice syed, fixed my issue.

  9. October 25, 2011 at 10:23 pm

    One thing I noticed on a recent project was that when running the virtualcenter management webservices service as a domain service account, we would not get alarms on hardware failures (power supply, etc). When we changed this to run as the Local System account, it works like a charm now. Alarms will pop up for hardware changes and clear when the alarm condition is cleared.

    We deduced this in part by restarting webservices: after restart any pending alarms would pop, but no further alarms would show up unless we went to the Hardware Status page. Then they would appear.

    – Mike

  10. LarryT
    December 16, 2011 at 9:58 pm

    Thanks for following those that kept responding through to the end.

    1. We just created lab with vSphere 4.1 Update 2 and vCenter (same).
    2. We are getting storage alerts and hardware status works
    = teste on Dell PowerEdge 2950
    = next two weeks, we are testing ESXi deployment on R910 with SD cards

    Current problem is the Storage Alerts do show upon the Hardware tab, but don’t show up on the actual hardware. Dell was worked through the issue with one of our SA’s but now the “proposed solution” that Dell wants to apply is to “re-signature of the local datastore” to resolve the error message. When asked why, they wanted to know which “of the 5 slices of the raid 1 ESXi is installed on”.

  1. No trackbacks yet.

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

%d bloggers like this: