vSphere DPM and HP iLO3

[Ollfried]

Hi,

Has anyone successfully configured DPM with iLO3? iLO2 works fine, but trying to configure iLO3 gives an error.

[MauroBonder]

check if help https://sps.one-source.ch/public/knowledge/Knowledge%20Base/VMware%20DPM%20mit%20HP%20Server.pdf

[Ollfried]

No, because iLO2 works, only iLO3 does not.

[ccslancaster]

We have the same issue here. DL80g5 with ILO2 work fine, DL380 g7 with ILO3 fail.

We get the same error in that you cannot setup ILO details correctly in the "Edit IPM/iLO settings dialog box.

When you look in the ILO logs you see the DPM user logon/logout but vcenter looks like it can't handle ILO3.

There was a similar post here - http://communities.vmware.com/message/1634995#1634995 which said vsphere 4.1 solved the issue but it appears not.

We are on vcenter 4.1 U1

Cheers.

[chriswahl]

I can confirm that iLO3 works fine on my cluster of DL580 G7s with DPM going to/from standby. I have the advanced iLO3, not sure if that matters or not.

Edit: I'm using vSphere ESXi 4.1u1 and vCenter 4.1

Message was edited by: chriswahl00

[ccslancaster]

Thanks for that info Chris.

We're on ESX 4.1 U1 hosts as well as Vcenter 4.1 U1. Maybe they fixed it in vcenter 4.1 and then broke it in 4.1 U1 (I'm assuming its a vcenter problem)

We're also on advanced rather than standard, ILO 3 v1.2 (latest version).

I'll raise a call with VMware.

[Ollfried]

Good Info, thank you. I had a call with HP, they asked me to raise a call with vmware, too. If you let me know what they say I will not call them myself.

Btw: I tried on 4.0U2 and 4.1u1 with ilo standard and advanced in version 1.12(?) 1.15 and 1.20.

VMware Communities<http://communities.vmware.com/index.jspa>

vSphere DPM and HP iLO3

reply from ccslancaster<http://communities.vmware.com/people/ccslancaster> in VMware vCenter™ Server - View the full discussion<http://communities.vmware.com/message/1749206#1749206

[ccslancaster]

Am in the middle of troubleshooting this with vmware and while that was ongoing saw that another related thread now has several ways to solve this - http://communities.vmware.com/message/1749568#1749568