- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: C-class OA not giving out assigned ebipa addre...
BladeSystem - General
1748285
Members
3925
Online
108761
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2008 03:32 PM
тАО01-18-2008 03:32 PM
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?
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 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2008 07:16 AM
тАО01-20-2008 07:16 AM
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2008 12:14 PM
тАО01-20-2008 12:14 PM
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2008 12:50 PM
тАО01-20-2008 12:50 PM
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.
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.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP