Re: ESXI 5.0.0, 62380 on a DL380 G7 (2120 Views)
Reply
Frequent Advisor
Donald J Wood
Posts: 47
Registered: ‎04-01-2005
Message 1 of 14 (2,393 Views)

ESXI 5.0.0, 62380 on a DL380 G7

We're having some issues with seeing the 410i array controller in vSphere on about 1/2 of the 110 servers we've deployed. We are using the vSphere client 5.0.0 build 455964 and we're reviewing the hardware at the Hardware Status tab. It's the storage and battery icon that is missing. Each server has ESXI 5 installed. Also, of the ones I can see, about 1/2 of them have a battery status: Partially Charged alarm. The Controllers have firmware version 5.70.

Honored Contributor
Jan Soska
Posts: 1,255
Registered: ‎01-22-2008
Message 2 of 14 (2,375 Views)

Re: ESXI 5.0.0, 62380 on a DL380 G7

Hello,

your ESX build is quite old. Please patch your server to current level, it could help.

And, there is smart array driver for ESX5 (ok, for custom image creation, but could help) - http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?sp4ts.oid=4091432&sp...

 

jan

Frequent Advisor
Donald J Wood
Posts: 47
Registered: ‎04-01-2005
Message 3 of 14 (2,362 Views)

Re: ESXI 5.0.0, 62380 on a DL380 G7


Jan Soska wrote:

Hello,

your ESX build is quite old. Please patch your server to current level, it could help.

And, there is smart array driver for ESX5 (ok, for custom image creation, but could help) - http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?sp4ts.oid=4091432&sp...

 

jan


Hi and thanks for you reply. My build team is telling me that they are using the VMware image but loading the hp modules through update manager. Which problem does the link correct, the "Missing Controller and Battery" or the "Battery Partially Charged"?

Honored Contributor
Jan Soska
Posts: 1,255
Registered: ‎01-22-2008
Message 4 of 14 (2,336 Views)

Re: ESXI 5.0.0, 62380 on a DL380 G7

Hello, do you have oportunity to install ESX from HP image?

I am checking our enviroment to see how it works here.

 

Jan

Frequent Advisor
Donald J Wood
Posts: 47
Registered: ‎04-01-2005
Message 5 of 14 (2,326 Views)

Re: ESXI 5.0.0, 62380 on a DL380 G7


Jan Soska wrote:

Hello, do you have oportunity to install ESX from HP image?

 

No I cannot. We have two different teams here. We have a server build team and an operations team. I don't build servers, I just support them.


 

Honored Contributor
Jan Soska
Posts: 1,255
Registered: ‎01-22-2008
Message 6 of 14 (2,304 Views)

Re: ESXI 5.0.0, 62380 on a DL380 G7

Hello Donald.

I've checked our enviroment. We have 3 G7 blades running ESXi 5.0, all installed form HP image, all have vissible storage subsystem under Hardware status tab.

For sure you have something missing in your instalation.

Please point you coleagues to great HP page: http://vibsdepot.hp.com/ where is complete information about drivers/software/firmware needed for running HP server with VMware.

 

Jan

Frequent Advisor
Donald J Wood
Posts: 47
Registered: ‎04-01-2005
Message 7 of 14 (2,301 Views)

Re: ESXI 5.0.0, 62380 on a DL380 G7


Jan Soska wrote:

Hello Donald.

I've checked our environment. We have 3 G7 blades running ESXi 5.0, all installed form HP image, all have visible storage subsystem under Hardware status tab.

For sure you have something missing in your installation.

Please point you colleagues to great HP page: http://vibsdepot.hp.com/ where is complete information about drivers/software/firmware needed for running HP server with VMware.

 

Jan


Jan,

Yup, it's funny how the world turns. Sadly, sometimes it's one step forward and two steps back if you know what I mean. The builders might be doing the two step scramble because it looks like these build will be impossible to support with the correct HP driver level installed. The next step are yet to be determined but, I can't wait until we find out..

Frequent Advisor
Donald J Wood
Posts: 47
Registered: ‎04-01-2005
Message 8 of 14 (2,269 Views)

Re: ESXI 5.0.0, 62380 on a DL380 G7

Today we forced the issue and had some Hp engineers on the phone with the builders of the servers. It was confirmed that the builders didn't install the proper Hp support software and other Hp enhancements that would not only let us see the hardware from the system management homepage and also provide proper hardware fault alerting and it would also installed the required hardware drivers. Sad how organizations

have moved in backward direction where people have once again started thinking they can just install an operating system on a enterprise class server without any knowledge of the hardware build requirements.

Honored Contributor
Jan Soska
Posts: 1,255
Registered: ‎01-22-2008
Message 9 of 14 (2,239 Views)

Re: ESXI 5.0.0, 62380 on a DL380 G7

There is nothing more to say... :(

Frequent Advisor
Donald J Wood
Posts: 47
Registered: ‎04-01-2005
Message 10 of 14 (2,169 Views)

Re: ESXI 5.0.0, 62380 on a DL380 G7

[ Edited ]

Here's an update. So we finally got some alerting working via SNMP. Here's an example of some of the SNMP strings we get when we muck around with the power cord on one of the redundant power supplies.

 

  • 1.3.6.1.4.1.6876.4.1 6 307 1.3.6.1.4.1.6876.4.30.1.0 String Power Supply 1 Power Supply 1
  • 1.3.6.1.4.1.232 6 6054 1.3.6.1.2.1.1.5 String teglenx1.travp.net 1.3.6.1.4.1.232.11.2.11.1 Integer 8 1.3.6.1.4.1.232.6.2.9.3.1.1.0.1 Integer 0

 

This doesn't make a lot of sense to me, so can someone please answer me this? ESXI is running on an HP Proliant DL380G7. Why do we get SNMP alerts from both Vmware and HP/Compaq OIDs about the same thing? VMware ESXI makes an operating system where HP makes Hardware. I wouldn't expect the OS to own any Hardware alerting responsibilities just like I wouldn't expect Microsoft, linux, HPUNIX, Or Red Hat to own it ether.

Honored Contributor
Jan Soska
Posts: 1,255
Registered: ‎01-22-2008
Message 11 of 14 (2,132 Views)

Re: ESXI 5.0.0, 62380 on a DL380 G7

Hello Donald,

what is the destination for your snmp traps? do you use tool like HP SIM (System Insight Manger) or other similar?

 

Jan

Frequent Advisor
Donald J Wood
Posts: 47
Registered: ‎04-01-2005
Message 12 of 14 (2,129 Views)

Re: ESXI 5.0.0, 62380 on a DL380 G7

HP SIM was never considered for our environment due to size. We tried it and it couldn't handle all the servers we have. Our enterprise is huge that reports to a BMC trap catcher. Us having SIM or not having SIM is out of scope for this discussion anyway.

 

As you may know, the sender of the traps would be the ESXI hosts and that's where the messages originate. So back to my original question, why send traps from both enterprise IDs?

Honored Contributor
Matti_Kurkela
Posts: 6,271
Registered: ‎12-02-2001
Message 13 of 14 (2,125 Views)

Re: ESXI 5.0.0, 62380 on a DL380 G7

My guess is that VMware wants to provide a uniform, hardware-vendor-neutral interface for basic hardware monitoring: "If it's running VMware ESX, you can always get basic hardware health information this way, no matter if it's HP, Fujitsu, IBM, Dell or something else."

 

But the old vendor-specific MIBs also exist because a) they may offer more specific information in some cases, and b) they allow the VMware systems to be monitored also by existing vendor-specific solutions, like HP SIM... because some people already have those and will want to keep using them.

 

Apparently VMware has understood that in large enterprises, hardware monitoring is often integrated with a complex enterprise monitoring/management system, and trying to force the customer to make major changes to that by vendor decision would usually have the customer looking for other, more cooperative vendors instead.

MK
Frequent Advisor
Donald J Wood
Posts: 47
Registered: ‎04-01-2005
Message 14 of 14 (2,120 Views)

Re: ESXI 5.0.0, 62380 on a DL380 G7

[ Edited ]

Corporations like the one I work for have computer and software system from many different companies that send alerts for many different reasons. In large companies an enterprise monitoring solution that provides a single view into alerting for all of our systems is a must have because most companies now have a centralized monitoring team. HP SIM doesn't provide that. End of story.

 

 

 

The redundancy crated by letting OS manufactures have hooks into the hardware alerting is very confusing. In our environment with our HP systems, it uses to be done one way, with the HP PSP and some SNMP configs. Now we get two traps for the same thing. I think we should be using the HP traps because we’re using HP servers. But, it is leaving other people at my company questioning which one we should be using and if we don't change will we be left behind the eight ball at some point.

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.