Anyone here in this bubble that could give me access to a #HPE #ProLiant (lab) server with access to ILO?
Must be at least Gen9.

Background: I'm working on a new open source monitoring plugin for HPE hardware monitoring and I want to do some field tests before public release.

DM me please.

Just hit a wall by finding software that doesn't work on my (beloved) HP #Proliant N40L Microserver. The 15 year old _ H Y P R E x T R E M E _ AMD Turon II isn't supported by Node 22 so I can't boot up #Homarr - Might finally be time to retire.

Two #HP #ProLiant DL380 Gen10. Used. In working condition. No OS loaded

1. #Intel #Xeon Bronze 3006 CPU @1.70GHz, 64 GB RAM, 24x 2TB SAS drives, 2 power supplies

2. Intel Xeon Silver 4110 CPU @2.1GHz, 64 GB RAM, 3x 480GB SATA SSD, 5x 2TB SAS drives, 2 power supplies

https://www.govdeals.com/en/asset/173/6507

#computers #govdeals #servers #NAS #homelab

Me parece impresionante lo fácil que es mover todo el sistema #UnRAID físicamente de un servidor a otro totalmente distinto. En mi caso de un HP #ProLiant ML110 G7 con 3 discos mecánicos y un SSD a un Dell #PowerEdge T330. Sólo he tenido que llevarme el "pincho" USB (que lo puedo "esconder" dentro del servidor gracias al conector USB que tiene en la placa base) y los discos y conectarlo todo en el T330. Arrancar y listo. (1/3)

Was setting up the new router yesterday and also upgraded the #Proxmox 7 (EoL) install on our old HP #ProLiant (DL360p G8) to latest 8.2. Worked like a charm ♥️

Hoping the connection issues are fixed now. This is the self hosting part that sucks but realistically.. who cares if my mailserver or the blog is offline for a few hours? The whole 24/7 idea is kinda nuts. Whatever happened to Hold The Line, Please.

#BSI WID-SEC-2024-1842: [NEU] [mittel] #HPE #ProLiant #undSynergy: Mehrere Schwachstellen ermöglichen Privilegieneskalation

Ein lokaler Angreifer kann mehrere Schwachstellen in HPE ProLiant und HPE Synergy ausnutzen, um seine Privilegien zu erhöhen.

https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2024-1842

Warn- und Informationsdienst

In light of a failed hard drive on my refurbished #proliant (one of four drives in the array), I'm doing a deep backup of media files and databases before doing my first hot-swap.

When I first started this digital madness c. 2010, it was a few directories I manually created on a 500GB portable drive. Today's backup of 90,000+ files is going to a spare 4TB external drive.

#homelab

The Integrated Lights-Out (ILO) Management on HPE #ProLiant servers support the #Redfish DMTF API since ILO4.

To make the communication to the API easier, #HPE created the #opensource ilorest command in 2016.

However, depending on your #Linux server setup, you might run into an error when executing ilorest - a misleading error pointing to a library issue.

In my latest #blog post I share how #ilorest can be debugged and find out the real reason.

https://www.claudiokuenzler.com/blog/1400/debugging-ilorest-error-while-loading-shared-libraries-eperm-operation-not-permitted

Debugging HPE ilorest command failing with error while loading shared libraries: libz.so.1

Under certain situations, depending on your server setup, the ilorest command from HPE does not work and fails with a (misleading) error pointing to library problem.

Claudio Kuenzler

Are you running #ProLiant DX with Nutanix AOS and do you get a warning about incorrect SAS cabling after installing the last patches? You might want to take a look at this. #Nutanix #HPE

https://vcloudnine.de/hpe-hba-cabling-check-falsely-issues-a-warning/

hpe_hba_cabling_check falsely issues a warning - A blog about virtualization, cloud, storage, networking and IT stuff.