Onboard Administrator

[Michael Gosselin]

I have been having an issue where the server name goes blank in the OA. I can enter something in the Asset Tag field, but don't understand why it is disappearing initially..

[HEM_2]

I would recommend as a first step that you ensure you are running the latest OA firmware:

http://h18023.www1.hp.com/support/files/server/us/download/26679.html

[Sylvain Gelinas]

Have similar problem. OA is losing status of blade or have wrong status.

Tried reset the OA without good result.

Using latest firmware 1.30

Any idea ??

[Dave Colangelo (SC)]

Any luck with this? I am using firmware v1.30 as well and whenever I image a blade the name goes blank in OA.

[Jim Casselman_2]

I also have the same issue with the name disappearing for a blade. I'm using OA 1.30 firmware.

[Adrian Clint]

I've seen this as well in 1.30.

Can't remember if it was fixed with the latest server BIOS update. Have you tried this?

[Dave Colangelo (SC)]

Same results even with the latest BIOS which I believe is I15 dated 04.06.2007.

[LJM_1]

I had the same issue with 1.30 OA f/w.

Resetting the active OA cleared it up for me.

[Michael Gosselin]

For everyone seeing this...it is only when you image a server?

[Dave Colangelo (SC)]

Reseating the OA card did the trick as LJM posted. The information does dissapear after imaging the servers to answer your question.

Thank you!

[Peter A. Berger Jr.]

All -- I am having the same issue where I cannot use AD authentication to get into OnBoard Administrator.
I've followed the suggestions above:
BIOS I15, Firmware 1.30, Reboot primary and standby OA's. No dice.
I've verified on both domain controller that a "netstat -an | find /i "636" does indeed show me that the DC's are listening on that port.

AD (Win2003 native) is layed out in containers as: domain.com, Users, OA Admins
In the OA Admins global security group I have added both Domain Admins and my own account.

so in the LDAP configuration I have:
ip: xxx.xxx.xxx.xxx
port: 636
CN=Users,DC=domain,DC=com

I cannot login as any AD name. I can only login as local Administrator.

I've tried various OU's, trying port 389 instead of 636 -- no dice. any help/411 would be great. thanks...

[Marcus Loh]

Hi Guys,

Any idea whether we can set more than one email address in the Alert email section? It seems like it accept more than one email address. Using V1.3 now.

Thanks.

[Marcus Loh]

Sorry, i mean it only accept one email address and gives error when inputing more than one email addresses.

[aboerup]

I just wanted to post that say I too have been having issues where the OA will have a blank server listed in a bay number but still otherwise works. Resetting the Active OA solves this issue.
Hopefully a newer firmware comes out soon which gives us a permanent resolution.

[Marcus Loh]

Updating the blade's ILO firmware to V1.30 does help to reflect the servername on the device bay area for me.

[WFHC-WI]

As far as the LDAP logins are concerned here are a couple things to check:

Make sure no blocking of port 636 is taking place between the OA and your DCs.
In the search context fields, enter the full distinguished name of the OU that contains the users who will be logging in. For example:
OU=Milwaukee Employees,OU=All Users,DC=MyComp,DC=net

Note that the "Users" directory in AD is not an OU -- just a container, so searches using that context will most likely fail. You may have to set up a dedicated OU for iLO accounts and create groups and/or users within that OU.

Add directory groups to the OA that have names identical to your AD group names. Differentiations may cause authentication to fail.

Good luck!

[Mikael Winther]

The order IS important:
First you update all you iLO's to version 1.30 or newer.
Then you update your OA to version 2.01 or newer.

Then these problems are history...

[Michael Gosselin]

New firmware seems to have fixed the problem...thanks to everyone that responded.