After an interesting time trying to locate the proper support pages for iLO 3 firmware update downloads for the above Integrity server, even when using google to search hpe, I'm asking here. Does anyone know if current firmware kits for a Proliant that uses an iLO 3 can be used (presumably just the BIN file) to update the iLO on the Integrity server?

Thanks

On Thursday, June 17, 2021 at 7:18:52 PM UTC-4, Rich Jordan wrote:
> After an interesting time trying to locate the proper support pages for iLO 3 firmware update downloads for the above Integrity server, even when using google to search hpe, I'm asking here. Does anyone know if current firmware kits for a Proliant that uses an iLO 3 can be used (presumably just the BIN file) to update the iLO on the Integrity server?
>
> Thanks
The answer is NO. The firmware kits for Proliant and Integrity are completely different.

Are you looking for something like this?

https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_9f4d133ebf704e849625019793#tab-history

On Thursday, June 17, 2021 at 7:22:39 PM UTC-5, Kenneth Randell wrote:
> On Thursday, June 17, 2021 at 7:18:52 PM UTC-4, Rich Jordan wrote:
> > After an interesting time trying to locate the proper support pages for iLO 3 firmware update downloads for the above Integrity server, even when using google to search hpe, I'm asking here. Does anyone know if current firmware kits for a Proliant that uses an iLO 3 can be used (presumably just the BIN file) to update the iLO on the Integrity server?
> >
> > Thanks
> The answer is NO. The firmware kits for Proliant and Integrity are completely different.
>
> Are you looking for something like this?
>
> https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_9f4d133ebf704e849625019793#tab-history

Don't think so, but we'd have to get the servers under support to get access to check since that appears to be a full firmware kit for blade servers, and so not a free download (as iLO updates used to be).

Maybe we can get to the real thing using hte customer's support account for their existing older integrity server. Again, right now, I'm only looking for iLO firmware, not system.

Thanks

On Friday, June 18, 2021 at 6:48:08 PM UTC-4, Rich Jordan wrote:
> On Thursday, June 17, 2021 at 7:22:39 PM UTC-5, Kenneth Randell wrote:
> > On Thursday, June 17, 2021 at 7:18:52 PM UTC-4, Rich Jordan wrote:
> > > After an interesting time trying to locate the proper support pages for iLO 3 firmware update downloads for the above Integrity server, even when using google to search hpe, I'm asking here. Does anyone know if current firmware kits for a Proliant that uses an iLO 3 can be used (presumably just the BIN file) to update the iLO on the Integrity server?
> > >
> > > Thanks
> > The answer is NO. The firmware kits for Proliant and Integrity are completely different.
> >
> > Are you looking for something like this?
> >
> > https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_9f4d133ebf704e849625019793#tab-history
> Don't think so, but we'd have to get the servers under support to get access to check since that appears to be a full firmware kit for blade servers, and so not a free download (as iLO updates used to be).
>
> Maybe we can get to the real thing using hte customer's support account for their existing older integrity server. Again, right now, I'm only looking for iLO firmware, not system.
>
> Thanks

Sorry, I think I posted the link for the cloud system firmware bundles have everything for blade systems.. The latest rx2800 i4 firmware bundle I can find is here, but still requires a contract to download:

https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_54d0b9fdeb11460bbe83cd5ed9#tab-history

On Friday, June 18, 2021 at 8:00:58 PM UTC-5, Kenneth Randell wrote:
> On Friday, June 18, 2021 at 6:48:08 PM UTC-4, Rich Jordan wrote:
> > On Thursday, June 17, 2021 at 7:22:39 PM UTC-5, Kenneth Randell wrote:
> > > On Thursday, June 17, 2021 at 7:18:52 PM UTC-4, Rich Jordan wrote:
> > > > After an interesting time trying to locate the proper support pages for iLO 3 firmware update downloads for the above Integrity server, even when using google to search hpe, I'm asking here. Does anyone know if current firmware kits for a Proliant that uses an iLO 3 can be used (presumably just the BIN file) to update the iLO on the Integrity server?
> > > >
> > > > Thanks
> > > The answer is NO. The firmware kits for Proliant and Integrity are completely different.
> > >
> > > Are you looking for something like this?
> > >
> > > https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_9f4d133ebf704e849625019793#tab-history
> > Don't think so, but we'd have to get the servers under support to get access to check since that appears to be a full firmware kit for blade servers, and so not a free download (as iLO updates used to be).
> >
> > Maybe we can get to the real thing using hte customer's support account for their existing older integrity server. Again, right now, I'm only looking for iLO firmware, not system.
> >
> > Thanks
> Sorry, I think I posted the link for the cloud system firmware bundles have everything for blade systems.. The latest rx2800 i4 firmware bundle I can find is here, but still requires a contract to download:
>
> https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_54d0b9fdeb11460bbe83cd5ed9#tab-history

I don't recall that HP ever hid iLO firmware behind a paywall or made full firmware kits the only way to get ilo firmware.

The machines will be under support, but are not yet. Guess we wait.

On 2021-06-21, Rich Jordan <jordan@ccs4vms.com> wrote:
>
> I don't recall that HP ever hid iLO firmware behind a paywall or made full firmware kits the only way to get ilo firmware.
>
> The machines will be under support, but are not yet. Guess we wait.

IIRC, at one time, it was freely downloadable and then HPE restricted
firmware update access to supported contract/warranty customers.

Anyone feel free to correct me if I am wrong, but HPE did move to
lockdown access to firmware images that were once freely available IIRC.

For example, here's one I accessed at random:

https://support.hpe.com/hpesc/public/swd/detail?swItemId=ux-122918-1

Note how you are told you need to have an active warranty or support
agreement when you click the download button.

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.

On 2021-06-21, Rich Jordan <jordan@ccs4vms.com> wrote:
>
> I don't recall that HP ever hid iLO firmware behind a paywall or made full firmware kits the only way to get ilo firmware.
>

BTW, I've had a bit of a look because I was curious but the only old
standalone iLO firmware pages I could find were for x64 (ie x86-64)
and not Itanium.

Everything for Itanium, including old pages, appears to be in a bundle.

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.

Simon Clubley schrieb am 21.06.2021 um 19:19:
> On 2021-06-21, Rich Jordan <jordan@ccs4vms.com> wrote:
>>
>> I don't recall that HP ever hid iLO firmware behind a paywall or made full firmware kits the only way to get ilo firmware.
>>
>> The machines will be under support, but are not yet. Guess we wait.
>
> IIRC, at one time, it was freely downloadable and then HPE restricted
> firmware update access to supported contract/warranty customers.
>
> Anyone feel free to correct me if I am wrong, but HPE did move to
> lockdown access to firmware images that were once freely available IIRC.
>
> For example, here's one I accessed at random:
>
> https://support.hpe.com/hpesc/public/swd/detail?swItemId=ux-122918-1
>
> Note how you are told you need to have an active warranty or support
> agreement when you click the download button.

Iirc most everything (but not all) for x86 (BIOS, ILO,
Windows-/Linux-/VMware-related) is freely available. Not so for Itanium
(or Alpha).

Hans.

On 6/21/2021 5:36 PM, Hans Bachner wrote:

> Iirc most everything (but not all) for x86 (BIOS, ILO,
> Windows-/Linux-/VMware-related) is freely available. Not so for Itanium (or Alpha).

Yes, iLO and BIOS are freely available for X86, but not the rest of the firmware
that is on the system.

--
-- Rob

On 6/21/2021 6:34 PM, Robert A. Brooks wrote:
> On 6/21/2021 5:36 PM, Hans Bachner wrote:
>
>> Iirc most everything (but not all) for x86 (BIOS, ILO,
>> Windows-/Linux-/VMware-related) is freely available. Not so for
>> Itanium (or Alpha).
>
> Yes, iLO and BIOS are freely available for X86, but not the rest of the
> firmware that is on the system.
>

Competition can be a wonderful thing.

Not knowledgeable about newest servers, wonder what AMD has to compare
with iLO, if anything?

--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: davef@tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486

On 6/21/2021 8:03 PM, Dave Froble wrote:
> On 6/21/2021 6:34 PM, Robert A. Brooks wrote:
>> On 6/21/2021 5:36 PM, Hans Bachner wrote:
>>
>>> Iirc most everything (but not all) for x86 (BIOS, ILO,
>>> Windows-/Linux-/VMware-related) is freely available. Not so for
>>> Itanium (or Alpha).
>>
>> Yes, iLO and BIOS are freely available for X86, but not the rest of the
>> firmware that is on the system.
>>
>
> Competition can be a wonderful thing.
>
> Not knowledgeable about newest servers, wonder what AMD has to compare with iLO,
> if anything?

I wasn't clear in my response; I did not mean to draw a distinction between the
Proliant Intel vs. the Proliant AMD series.

iLO is motherboard CPU-agnostic; it's the same iLO for a DL380 and DL385 (the
nomenclature is such that for the Proliant line, the xx5 variant is with an
AMD CPU).

--
-- Rob

On 6/21/2021 10:33 PM, Robert A. Brooks wrote:
> On 6/21/2021 8:03 PM, Dave Froble wrote:
>> On 6/21/2021 6:34 PM, Robert A. Brooks wrote:
>>> On 6/21/2021 5:36 PM, Hans Bachner wrote:
>>>
>>>> Iirc most everything (but not all) for x86 (BIOS, ILO,
>>>> Windows-/Linux-/VMware-related) is freely available. Not so for
>>>> Itanium (or Alpha).
>>>
>>> Yes, iLO and BIOS are freely available for X86, but not the rest of the
>>> firmware that is on the system.
>>>
>>
>> Competition can be a wonderful thing.
>>
>> Not knowledgeable about newest servers, wonder what AMD has to compare
>> with iLO, if anything?
>
> I wasn't clear in my response; I did not mean to draw a distinction
> between the Proliant Intel vs. the Proliant AMD series.
>
> iLO is motherboard CPU-agnostic; it's the same iLO for a DL380 and DL385
> (the nomenclature is such that for the Proliant line, the xx5 variant is
> with an
> AMD CPU).
>

Since you're answering questions ...

:-)

Is the iLO an HPe thing, or do others use it, or something similar?

Does x86 VMS require an iLO?

Or something similar?

I'm aware that VSI is looking to the HPe Proliant systems, but I'm still
holding an old grudge because of the 386 FP fiasco, and more recently
against HP(e). To be fair, I guess I should also hold a grudge for AMD
not producing the motherboards that would work with Alpha, as I believe
they agreed to do.

--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: davef@tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486

Den 2021-06-22 kl. 05:39, skrev Dave Froble:
> On 6/21/2021 10:33 PM, Robert A. Brooks wrote:
>> On 6/21/2021 8:03 PM, Dave Froble wrote:
>>> On 6/21/2021 6:34 PM, Robert A. Brooks wrote:
>>>> On 6/21/2021 5:36 PM, Hans Bachner wrote:
>>>>
>>>>> Iirc most everything (but not all) for x86 (BIOS, ILO,
>>>>> Windows-/Linux-/VMware-related) is freely available. Not so for
>>>>> Itanium (or Alpha).
>>>>
>>>> Yes, iLO and BIOS are freely available for X86, but not the rest of the
>>>> firmware that is on the system.
>>>>
>>>
>>> Competition can be a wonderful thing.
>>>
>>> Not knowledgeable about newest servers, wonder what AMD has to compare
>>> with iLO, if anything?
>>
>> I wasn't clear in my response; I did not mean to draw a distinction
>> between the Proliant Intel vs. the Proliant AMD series.
>>
>> iLO is motherboard CPU-agnostic; it's the same iLO for a DL380 and DL385
>> (the nomenclature is such that for the Proliant line, the xx5 variant is
>> with an
>> AMD CPU).
>>
>
> Since you're answering questions ...
>
> :-) >
> Is the iLO an HPe thing, or do others use it, or something similar?
>
> Does x86 VMS require an iLO?
>
> Or something similar?
>
> I'm aware that VSI is looking to the HPe Proliant systems, but I'm still
> holding an old grudge because of the 386 FP fiasco, and more recently
> against HP(e).  To be fair, I guess I should also hold a grudge for AMD not
> producing the motherboards that would work with Alpha, as I believe they
> agreed to do.
>

I think your questions already have answers available to everyone.

https://en.wikipedia.org/wiki/HP_Integrated_Lights-Out

On 06/22/21 08:29, Jan-Erik Söderholm wrote:
> Den 2021-06-22 kl. 05:39, skrev Dave Froble:
>> On 6/21/2021 10:33 PM, Robert A. Brooks wrote:
>>> On 6/21/2021 8:03 PM, Dave Froble wrote:
>>>> On 6/21/2021 6:34 PM, Robert A. Brooks wrote:
>>>>> On 6/21/2021 5:36 PM, Hans Bachner wrote:
>>>>>
>>>>>> Iirc most everything (but not all) for x86 (BIOS, ILO,
>>>>>> Windows-/Linux-/VMware-related) is freely available. Not so for
>>>>>> Itanium (or Alpha).
>>>>>
>>>>> Yes, iLO and BIOS are freely available for X86, but not the rest of
>>>>> the
>>>>> firmware that is on the system.
>>>>>
>>>>
>>>> Competition can be a wonderful thing.
>>>>
>>>> Not knowledgeable about newest servers, wonder what AMD has to compare
>>>> with iLO, if anything?
>>>
>>> I wasn't clear in my response; I did not mean to draw a distinction
>>> between the Proliant Intel vs. the Proliant AMD series.
>>>
>>> iLO is motherboard CPU-agnostic; it's the same iLO for a DL380 and DL385
>>> (the nomenclature is such that for the Proliant line, the xx5 variant is
>>> with an
>>> AMD CPU).
>>>
>>
>> Since you're answering questions ...
>>
>> :-) >
>> Is the iLO an HPe thing, or do others use it, or something similar?
>>
>> Does x86 VMS require an iLO?
>>
>> Or something similar?
>>
>> I'm aware that VSI is looking to the HPe Proliant systems, but I'm
>> still holding an old grudge because of the 386 FP fiasco, and more
>> recently against HP(e). To be fair, I guess I should also hold a
>> grudge for AMD not producing the motherboards that would work with
>> Alpha, as I believe they agreed to do.
>>
>
> I think your questions already have answers available to everyone.
>
> https://en.wikipedia.org/wiki/HP_Integrated_Lights-Out

Most server vendors have an ilo equivalent now, even if not compatible,
though remote managaement tools provide support for multiple vendors.
Both Sun and IBM for example, have for possibly decades...

On 6/22/2021 3:29 AM, Jan-Erik Söderholm wrote:
> Den 2021-06-22 kl. 05:39, skrev Dave Froble:
>> On 6/21/2021 10:33 PM, Robert A. Brooks wrote:
>>> On 6/21/2021 8:03 PM, Dave Froble wrote:
>>>> On 6/21/2021 6:34 PM, Robert A. Brooks wrote:
>>>>> On 6/21/2021 5:36 PM, Hans Bachner wrote:
>>>>>
>>>>>> Iirc most everything (but not all) for x86 (BIOS, ILO,
>>>>>> Windows-/Linux-/VMware-related) is freely available. Not so for
>>>>>> Itanium (or Alpha).
>>>>>
>>>>> Yes, iLO and BIOS are freely available for X86, but not the rest of
>>>>> the
>>>>> firmware that is on the system.
>>>>>
>>>>
>>>> Competition can be a wonderful thing.
>>>>
>>>> Not knowledgeable about newest servers, wonder what AMD has to compare
>>>> with iLO, if anything?
>>>
>>> I wasn't clear in my response; I did not mean to draw a distinction
>>> between the Proliant Intel vs. the Proliant AMD series.
>>>
>>> iLO is motherboard CPU-agnostic; it's the same iLO for a DL380 and DL385
>>> (the nomenclature is such that for the Proliant line, the xx5 variant is
>>> with an
>>> AMD CPU).
>>>
>>
>> Since you're answering questions ...
>>
>> :-) >
>> Is the iLO an HPe thing, or do others use it, or something similar?
>>
>> Does x86 VMS require an iLO?
>>
>> Or something similar?
>>
>> I'm aware that VSI is looking to the HPe Proliant systems, but I'm
>> still holding an old grudge because of the 386 FP fiasco, and more
>> recently against HP(e). To be fair, I guess I should also hold a
>> grudge for AMD not producing the motherboards that would work with
>> Alpha, as I believe they agreed to do.
>>
>
> I think your questions already have answers available to everyone.
>
> https://en.wikipedia.org/wiki/HP_Integrated_Lights-Out

Well, no. There is the question of "Does x86 VMS require an iLO?"

--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: davef@tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486

> Is the iLO an HPe thing, or do others use it, or something similar?

iLO is the HP trade name for a remote management board. Dell calls it a
DRAC. Others have equivalent products. These boards predate the common
appearance of IPMI, BMC, WfM, etc on motherboards. I imagine current
implementations probably provide and/or are based on the industry
"standards".

Provided remote control services have long included serial console
redirection, kvm functionality, virtual media for booting / installing /
testing, reset button. Newer support includes full power management, a
service processor console for exploring and setting various things.

De

Den 2021-06-22 kl. 16:17, skrev Dave Froble:
> On 6/22/2021 3:29 AM, Jan-Erik Söderholm wrote:
>> Den 2021-06-22 kl. 05:39, skrev Dave Froble:
>>> On 6/21/2021 10:33 PM, Robert A. Brooks wrote:
>>>> On 6/21/2021 8:03 PM, Dave Froble wrote:
>>>>> On 6/21/2021 6:34 PM, Robert A. Brooks wrote:
>>>>>> On 6/21/2021 5:36 PM, Hans Bachner wrote:
>>>>>>
>>>>>>> Iirc most everything (but not all) for x86 (BIOS, ILO,
>>>>>>> Windows-/Linux-/VMware-related) is freely available. Not so for
>>>>>>> Itanium (or Alpha).
>>>>>>
>>>>>> Yes, iLO and BIOS are freely available for X86, but not the rest of
>>>>>> the
>>>>>> firmware that is on the system.
>>>>>>
>>>>>
>>>>> Competition can be a wonderful thing.
>>>>>
>>>>> Not knowledgeable about newest servers, wonder what AMD has to compare
>>>>> with iLO, if anything?
>>>>
>>>> I wasn't clear in my response; I did not mean to draw a distinction
>>>> between the Proliant Intel vs. the Proliant AMD series.
>>>>
>>>> iLO is motherboard CPU-agnostic; it's the same iLO for a DL380 and DL385
>>>> (the nomenclature is such that for the Proliant line, the xx5 variant is
>>>> with an
>>>> AMD CPU).
>>>>
>>>
>>> Since you're answering questions ...
>>>
>>> :-) >
>>> Is the iLO an HPe thing, or do others use it, or something similar?
>>>
>>> Does x86 VMS require an iLO?
>>>
>>> Or something similar?
>>>
>>> I'm aware that VSI is looking to the HPe Proliant systems, but I'm
>>> still holding an old grudge because of the 386 FP fiasco, and more
>>> recently against HP(e).  To be fair, I guess I should also hold a
>>> grudge for AMD not producing the motherboards that would work with
>>> Alpha, as I believe they agreed to do.
>>>
>>
>> I think your questions already have answers available to everyone.
>>
>> https://en.wikipedia.org/wiki/HP_Integrated_Lights-Out
>
> Well, no.  There is the question of "Does x86 VMS require an iLO?"
>

As far as I understand, iLO has nothing to do with the OS, it is a tool
to manage the server HW.

>-----Original Message-----
>From: Info-vax <info-vax-bounces@rbnsn.com> On Behalf Of Dennis Boone
>via Info-vax
>Sent: June-22-21 2:57 PM
>To: info-vax@rbnsn.com
>Cc: Dennis Boone <drb@ihatespam.msu.edu>
>Subject: Re: [Info-vax] RX2800 i4 iLO 3 firmware
>
> > Is the iLO an HPe thing, or do others use it, or something similar?
>
>iLO is the HP trade name for a remote management board. Dell calls it a DRAC.
>Others have equivalent products. These boards predate the common
>appearance of IPMI, BMC, WfM, etc on motherboards. I imagine current
>implementations probably provide and/or are based on the industry
>"standards".
>
>Provided remote control services have long included serial console
>redirection, kvm functionality, virtual media for booting / installing / testing,
>reset button. Newer support includes full power management, a service
>processor console for exploring and setting various things.
>
>De
>_______________________________________________

Out of band server management like ILO's, DRAC including remote power mgmt. strategies has been around for decades (early 1980's).

VAX Nautilus and Polarstar systems used external PRO-350/380 PC systems to manage (including Poff/Pon, searchable soft log files) VAX systems.

Bit of trivia - one Nautilus/Pstar console firmware fix involved changing the console command "H" for Help to require a minimum of two characters "HE".

Reason was that some would log into the console mode on a running system, type "H" for help and the running system would then immediately HALT.

(H = help or halt)

For those that remember the WW DEC VAX notesfiles, Atlant Schmidt was the key VAX PC350/380 console firmware developer. Excellent resource.

😊

Regards,

Kerry Main
Kerry dot main at starkgaming dot com

--
This email has been checked for viruses by AVG.
https://www.avg.com

On Tuesday, June 22, 2021 at 6:30:06 PM UTC-5, kemain...@gmail.com wrote:
> >-----Original Message-----
> >From: Info-vax <info-vax...@rbnsn.com> On Behalf Of Dennis Boone
> >via Info-vax
> >Sent: June-22-21 2:57 PM
> >To: info...@rbnsn.com
> >Cc: Dennis Boone <d...@ihatespam.msu.edu>
> >Subject: Re: [Info-vax] RX2800 i4 iLO 3 firmware
> >
> > > Is the iLO an HPe thing, or do others use it, or something similar?
> >
> >iLO is the HP trade name for a remote management board. Dell calls it a DRAC.
> >Others have equivalent products. These boards predate the common
> >appearance of IPMI, BMC, WfM, etc on motherboards. I imagine current
> >implementations probably provide and/or are based on the industry
> >"standards".
> >
> >Provided remote control services have long included serial console
> >redirection, kvm functionality, virtual media for booting / installing / testing,
> >reset button. Newer support includes full power management, a service
> >processor console for exploring and setting various things.
> >
> >De
> >_______________________________________________
>
> Out of band server management like ILO's, DRAC including remote power mgmt. strategies has been around for decades (early 1980's).
>
> VAX Nautilus and Polarstar systems used external PRO-350/380 PC systems to manage (including Poff/Pon, searchable soft log files) VAX systems.
>
> Bit of trivia - one Nautilus/Pstar console firmware fix involved changing the console command "H" for Help to require a minimum of two characters "HE".
>
> Reason was that some would log into the console mode on a running system, type "H" for help and the running system would then immediately HALT.
>
> (H = help or halt)
>
> For those that remember the WW DEC VAX notesfiles, Atlant Schmidt was the key VAX PC350/380 console firmware developer. Excellent resource.
>
> 😊
>
>
> Regards,
>
> Kerry Main
> Kerry dot main at starkgaming dot com
>
>
>
>
>
>
> --
> This email has been checked for viruses by AVG.
> https://www.avg.com

Strictly HP, I have been able to download just the iLO firmware for any Proliant at no cost. Same with the online configurator. BIOS and other firmware as well as the complete spp for proliants has been behind a paywall for a long time now. RX firmware kits have also been paywalled but I had hopes (and I know in the past it was in fact this way) that _kust_ the ilo firmware itself was still freely downloadable.

Maybe HPe no longer GIF since they're not supporting VMS or other uses for the RX series any longer so decided to squeeze more dollars. Don't know.

Would the firmware BIN file from a Proliant iLO 3 work on an Integrity iLO 3?

Thanks
Rich

On 6/22/2021 7:37 PM, Rich Jordan wrote:

> Would the firmware BIN file from a Proliant iLO 3 work on an Integrity iLO

Are you seriously still asking that question?

The first reply to your initial post answered that pretty clearly.

Subject: Re: RX2800 i4 iLO 3 firmware
Date: Thu, 17 Jun 2021 17:22:37 -0700 (PDT)
From: Kenneth Randell <kennethnospam.randell@gmail.com>
Newsgroups: comp.os.vms
References: <8cecbb21-216d-4fca-afa2-5be9d4d37d70n@googlegroups.com>

On Thursday, June 17, 2021 at 7:18:52 PM UTC-4, Rich Jordan wrote:
> After an interesting time trying to locate the proper support pages for iLO 3
> firmware update downloads for the above Integrity server, even when using
> google to search hpe, I'm asking here. Does anyone know if current firmware
> kits for a Proliant that uses an iLO 3 can be used (presumably just the BIN
> file) to update the iLO on the Integrity server?
>
> Thanks

The answer is NO. The firmware kits for Proliant and Integrity are completely
different.

Are you looking for something like this?

https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_9f4d133ebf704e849625019793#tab-history
--
-- Rob

On Tuesday, June 22, 2021 at 7:05:42 PM UTC-5, Robert A. Brooks wrote:
> On 6/22/2021 7:37 PM, Rich Jordan wrote:
>
>
> > Would the firmware BIN file from a Proliant iLO 3 work on an Integrity iLO
> Are you seriously still asking that question?
>
> The first reply to your initial post answered that pretty clearly.
>
> Subject: Re: RX2800 i4 iLO 3 firmware
> Date: Thu, 17 Jun 2021 17:22:37 -0700 (PDT)
> From: Kenneth Randell <kennethnos...@gmail.com>
> Newsgroups: comp.os.vms
> References: <8cecbb21-216d-4fca...@googlegroups.com>
> On Thursday, June 17, 2021 at 7:18:52 PM UTC-4, Rich Jordan wrote:
> > After an interesting time trying to locate the proper support pages for iLO 3
> > firmware update downloads for the above Integrity server, even when using
> > google to search hpe, I'm asking here. Does anyone know if current firmware
> > kits for a Proliant that uses an iLO 3 can be used (presumably just the BIN
> > file) to update the iLO on the Integrity server?
> >
> > Thanks
>
> The answer is NO. The firmware kits for Proliant and Integrity are completely
> different.
>
> Are you looking for something like this?
>
> https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_9f4d133ebf704e849625019793#tab-history
> --
> -- Rob

Rob,
sorry if I offended. The links posted in response were for an Integrity system firmware kit that included iLO firmware, not just the iLO firmware package. As such, the context was mixed; clearly the overall firmware kits for the systems would have to be different. You also posted later "iLO is motherboard CPU-agnostic"; I wasn't clear if that crossed architectures or not but the context there only mentioned AMD vs Intel so guess it doesn't.

I hadn't quite given up on finding the standalone ilo firmware that lists as supported for Integrity or VMS/HPUX. Apparently that was pointless.

Thank you for confirming. We're waiting on formal support being added so everything related to this hardware is on hold.

HPe certainly makes this more difficult than it should be.

Thanks.

On 6/23/2021 10:43 AM, Rich Jordan wrote:

> Rob, sorry if I offended.

No, I should not have responded in such a fashion; I was in a bit of a cranky mood.

> The links posted in response were for an
> Integrity system firmware kit that included iLO firmware, not just
> the iLO firmware package. As such, the context was mixed; clearly
> the overall firmware kits for the systems would have to be different.
> You also posted later "iLO is motherboard CPU-agnostic"; I wasn't
> clear if that crossed architectures or not but the context there only
> mentioned AMD vs Intel so guess it doesn't.

My guess is that if you attempted to upload the wrong firmware, it would fail the
header checksum validation, so it's not as if you could brick the iLO itself with
the wrong firmware.

However, it's just a guess.

When not paying enough attention to what I was doing, I have attempted to update an iLO3 with
iLO4 firmware, and that does fail the header validation.

--

-- Rob

On 6/23/2021 10:43 AM, Rich Jordan wrote:

> HPe certainly makes this more difficult than it should be.

HPe doesn't care about you, just your money ...

--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: davef@tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486

On 2021-06-23 15:17:08 +0000, Dave Froble said:

> On 6/23/2021 10:43 AM, Rich Jordan wrote:
>
>> HPe certainly makes this more difficult than it should be.

It's long been difficult to find stuff at DEC, Compaq, HP, and HPE. At
IBM and Dell too, for that matter. That's seemingly been a hallmark of
enterprise computing. Simple is hard. Clarity is hard.

> HPe doesn't care about you, just your money ...

There are alternatives for ~all IT hardware vendors. Among others,
SuperMicro for servers, Brother for printers, and Synology for servers
and NAS.

The Synology packages have replaced a number of purpose-dedicated local
servers: https://www.synology.com/en-us/dsm/packages

OpenVMS V9.2 is going to shuffle a whole lot of longstanding
assumptions around hardware, too. The x86-64 upgrade cycle tends to be
much shorter—three to five years—than that of Alpha or Itanium servers.
And hypervisor guest support means we'll be seeing massively overloaded
OpenVMS guests co-resident on too little hardware with ongoing efforts
toward server constipation, err, toward server consolidation.

--
Pure Personal Opinion | HoffmanLabs LLC

On 2021-06-22 23:27:16 +0000, <kemain.nospam@gmail.com> said:

> Out of band server management like ILO's, DRAC including remote power
> mgmt. strategies has been around for decades (early 1980's).

Outboard console was more of a necessity back then, as the earliest VAX
itself was comparatively, well, stupid.

The VAX-11/780 operated as a peripheral of an LSI-11, in a manner of
consideration. Boot the LSI, which then loads and boots Star and
Starlet.

Later VAX systems got somewhat smarter.

Remote management was something comparatively new for OpenVMS folks,
first arriving with Itanium for many of the OpenVMS sites around.

> VAX Nautilus and Polarstar systems used external PRO-350/380 PC systems
> to manage (including Poff/Pon, searchable soft log files) VAX systems.

The Nautilus family used Pro 350 and Pro 380 hardware, with those boxes
renamed as VAX console. The Polarstar family used a MicroVAX II as the
console. The MicroVAX was one of the distinguishing features of
Polarstar. VAX-11/780 used an LSI-11, as mentioned above. The VAX 9000
service processor unit comprised of 4 MicroVAX II processors. Alpha
eventually added RCM and RMC hardware outboard, all the way up to the
entirely gonzo server management network present within the
Marvel-class AlphaServer boxes; AlphaServer GS1280, etc.

IBM used last year's mainframe model as this year's channel controller
as that old joke went, and analogous jokes about VAX consoles.

None of these VAX and Alpha consoles was supported for remote Ethernet
network access, with the gear supporting remote serial access at best.
Early on, this serial access was intended for DEC Field Service to dial
in (modems, remember those?) and diagnose the server.

Yes, some older sites did routinely use terminal servers as a
workaround for remote console access, or used a console app such as
VAXcluster Console System (VCS) or Minicom and serial cabling, or
screen/tmux, etc. And I've remotely tapped into the Marvel internal
network, as have others. These were wildly insecure, by present-day
standards.

HP and HPE iLO, Dell iDRAC, the SuperMicro BMC, and various other
available gear all substantially improve on what the older server
consoles could do, though. Particularly around remote management and
monitoring and automation, and with far better support for server
installation. And with better connection security. (Usually. Somewhat.
See below.)

For lower-end boxes, Intel vPro and AMD Pro management access is
available from various vendors.

iLO 2 and iLO 2 are hardware limited and which reportedly constrains
what is possible with the hardware, and are nowadays best kept
isolated. There are exploits against these, including the CVE-2013-4786
vulnerability.

"There is no resolution to this issue. The authentication process for
the IPMI 2.0 specification mandates that the server send a salted SHA1
or MD5 hash of the requested user's password to the client, prior to
the client authenticating. The BMC returns the password hash for any
valid user account requested. This password hash can be broken using an
offline brute force or dictionary attack. Because this functionality is
a key part of the IPMI 2.0 specification, there is no way to fix the
problem without deviating from the IPMI 2.0 specification."

Meaning you will want to disable IPMI ( MP:CM> sa -lanipmi d ) if
you're not using it, and not on a constrained-access management network.

And another reason for isolation: iLO 2 and iLO 3 ssh security is badly
down-revision, which means connecting using something similar to this:
ssh -o HostKeyAlgorithms=ssh-rsa,ssh-dss -o
KexAlgorithms=diffie-hellman-group1-sha1 -o Ciphers=aes128-cbc,3des-cbc
-o MACs=hmac-md5,hmac-sha1 User@Server.Example.Com

--
Pure Personal Opinion | HoffmanLabs LLC