HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem - General
cancel
Showing results for 
Search instead for 
Did you mean: 

C-class OA not giving out assigned ebipa addresses to blades

 
Frank Ng
Advisor

C-class OA not giving out assigned ebipa addresses to blades

Old OA firmware: 1.30
New OA firmware: 2.10

iLo firmware: 1.29

OA configurations relating to ebipa ...

SET EBIPA SERVER 10.50.0.51 1
SET EBIPA SERVER 10.50.0.52 2
SET EBIPA SERVER 10.50.0.53 3
SET EBIPA SERVER 10.50.0.54 4
SET EBIPA SERVER 10.50.0.55 5
SET EBIPA SERVER 10.50.0.56 6
SET EBIPA SERVER 10.50.0.57 7
SET EBIPA SERVER 10.50.0.58 8
SET EBIPA SERVER 10.50.0.59 9
SET EBIPA SERVER 10.50.0.60 10
SET EBIPA SERVER 10.50.0.61 11
SET EBIPA SERVER 10.50.0.62 12
SET EBIPA SERVER 10.50.0.63 13
SET EBIPA SERVER 10.50.0.64 14
SET EBIPA SERVER 10.50.0.65 15
SET EBIPA SERVER 10.50.0.66 16
SET EBIPA SERVER NETMASK 255.255.252.0
SET EBIPA SERVER GATEWAY 10.50.0.1
SET EBIPA SERVER DOMAIN "xxx.com"
ADD EBIPA SERVER DNS 10.50.8.131
ADD EBIPA SERVER DNS 10.50.8.71
ENABLE EBIPA SERVER 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16

This is how the show ebipa looks like ...

sf3-ba-oa2> show ebipa

EBIPA Settings - Device Bay iLO Processors

Domain: xxx.com

Subnet Mask: 255.255.252.0 Gateway: 10.50.0.1
DNS Server1: 10.50.8.71 Server2: 10.50.8.131
Server3: 0.0.0.0

Bay Enabled EBIPA Address Current Address Device Type
--- ------- --------------- --------------- ------------
1 Yes 10.50.0.111 N/A
2 Yes 10.50.0.112 N/A
3 Yes 10.50.0.113 N/A
4 Yes 10.50.0.114 N/A
5 Yes 10.50.0.115 N/A
6 Yes 10.50.0.116 N/A
7 Yes 10.50.0.117 N/A
8 Yes 10.50.0.118 0.0.0.0 Server Blade
9 Yes 10.50.0.119 0.0.0.0 Server Blade
10 Yes 10.50.0.120 0.0.0.0 Server Blade
11 Yes 10.50.0.121 0.0.0.0 Server Blade
12 Yes 10.50.0.122 0.0.0.0 Server Blade
13 Yes 10.50.0.123 0.0.0.0 Server Blade
14 Yes 10.50.0.124 0.0.0.0 Server Blade
15 Yes 10.50.0.125 N/A
16 Yes 10.50.0.126 N/A


As you can see, the current address is either NA or 0.0.0.0, in which case, you can't hit the ilo IP or do a direct OA connect to server via connect server #.

All 16 blades populated.

We have around 200 blades here, I was able to upgrade the iLo via hponcfg/hprsm on all the other ones except for this enclosure. This enclosure is running a custom version of 64bit redhat kernel. hprsm won't install, so i can't use hponcfg since the iLo kernel objects come with hprsm.

I can't connect to the iLo so I can't upgrade the firmware on the iLos. I can't use hponcfg due to custom kernel. The only thing to make this work is to plug in the SUV dongle and giving them static IPs and once they have IPs I can load in the firmware via the bin file. But this enclosure is kind of important and can't afford the downtime.

Any ideas?

3 REPLIES
otto warlich
Regular Advisor

Re: C-class OA not giving out assigned ebipa addresses to blades

Hello Frank,

Did you try to set the ilo-ip addresses on DHCP also. And did you get the same result?

If not there is maybe a possiblility to reset the ILO.

If you did, I believe the only solution is to reinsert the blade.

With regards,

Otto
Blazhev_1
Honored Contributor

Re: C-class OA not giving out assigned ebipa addresses to blades

Hi Frank,

please note
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=1842750&swItem=MTX-24b81875234f43f998d3b8afcb&prodNameId=3288156&swEnvOID=1005&swLang=8&taskId=135&mode=4&idx=2

There is written that OA FW 2.10 requires minimum ilo2 FW 1.42...1.29 is incompatible with 2.10, so you can forget about EBIPA. You can downgrade the OA to 1.30, check the iLO2 pages if ilo2 is configured for DHCP and then reassign the EBIPA IPs and apply.
Hope this helps!

Regards,
Pac

Frank Ng
Advisor

Re: C-class OA not giving out assigned ebipa addresses to blades

I have reinserted the blade with no help.

So, yes, I understand that the OA firmware and the ilo firmware conflicts. But what I don't understand is, I have 200 blades, only this one enclosure is doing that.

Like I mentioned before, the other blades ilo is still accessable after the oa firmware upgrade, and I was able to up the ilo firmware with the OS.

The only reason why I can't with this one enclosure is because of the customer kernel it's running.

Because 1.30 firmware is no longer available for download, I basically have to replace the OAs with one that hasn't been upgraded yet so I can access the ilos again, and up the ilo firmware with ilo webpage loading the bin file.

I've looked at the oa firmware fixes and release notes, none of which mentions that it fixed the ebipa problem. So I don't understand how this is an known issue. Oh well.