Posted on

Deciphering HPE Part Numbers: Why Your Server Accessories and Spares Have Three Different Identities

If you have ever managed an HPE ProLiant Gen10 server, you might have noticed something confusing: the part number reported by iLO or the operating system doesn’t match the one you see on the purchase invoice or the official box.

Understanding the “Triple-ID” system used by Hewlett Packard Enterprise is crucial for IT administrators who need to expand or maintain their infrastructure without making costly compatibility errors.

The Three Types of HPE Part Numbers

HPE categorizes every hardware component (RAM, Drives, Power Supplies) into three distinct identification systems:

1. Option Part Number

This is the Commercial Code. It is the primary identifier used by sales teams, resellers, and listed in official QuickSpecs.

  • Where to find it: On the retail box, on your invoice, and in the HPE product catalog.

  • When to use it: Use this code when you want to purchase a new expansion kit. It usually includes the component itself, a warranty statement, and installation guides.

2. Spare Part Number

This is the Maintenance Code. HPE uses this to manage its global inventory for repairs and replacements.

  • Where to find it: Often found on a small “Spare” sticker on the component or in the HPE PartSurfer database.

  • When to use it: Use this code if you are opening a support ticket or requesting a replacement under warranty. If a technician arrives at your data center, the box they carry will likely display this number.

3. Assembly Part Number / Label Part

This is the Manufacturing Code. It identifies the specific physical build of the component as it came off the assembly line.

  • Where to find it: Printed directly on the component’s label (e.g., the RAM stick itself) and reported by iLO (Integrated Lights-Out) or software inventory tools.

  • When to use it: Use this to identify exactly what is currently installed in your server. Since this is the “raw” hardware ID, it is the most accurate way to verify technical specs like Rank, Latency, and Manufacturer.

Term Also Known As Primary Purpose Example
Option Part Marketing/Retail P/N Purchasing new upgrades P00924-B21
Spare Part Replacement P/N Warranty & Repair P06189-001
Assembly Part Label/iLO P/N Hardware identification P03052-091

Why Does This Matter?

The most common mistake occurs during RAM upgrades. An administrator reads the Assembly Part Number from iLO and tries to find it on a reseller’s website. Often, they will only find “refurbished” or “pulled” parts.

To buy a brand-new, officially supported HPE SmartMemory kit, the administrator must “translate” that Assembly Number back into the Option Part Number. Only by matching these correctly can you ensure that your server maintains its performance, stability, and HPE “SmartMemory” features.

The Pricing Paradox: Why Identical Hardware Has Different Costs

One of the most baffling scenarios for an IT procurement manager is finding two listings for what appears to be the same 32GB HPE RAM module, only to discover a massive price discrepancy—sometimes with the “Replacement Part” costing 30% to 50% more than the “Retail Kit.”

If the silicon, the speed, and the capacity are identical, why the difference? The answer lies in the diverging paths of the Expansion Market versus the Spare Parts Market.

The Volume vs. Niche Dynamic

  • The Option Part (Expansion Market): These parts  are produced in massive quantities for the global retail channel. Because they are the primary choice for users upgrading their servers, competition between distributors is fierce. This high-volume, high-competition environment keeps prices aligned with current market trends for DRAM.

  • The Assembly Part (Spare Parts Market): When a buyer searches specifically for an Assembly Number , they are often doing so because they are trying to match an existing failed component exactly. Some specialized “legacy” or “spare part” vendors capitalize on this specific search intent, pricing these items as rare “technical matches” rather than commodity hardware.

Posted on

Come riavviare un server HPE tramite iLO quando il sistema operativo non risponde

Quando un server HPE sembra acceso ma il sistema operativo non risponde, può nascere il dubbio: come forzare un riavvio in sicurezza senza dover intervenire fisicamente in sala server?

Questa è una situazione piuttosto comune in contesti IT: il server non pinga, non è accessibile in RDP o SSH, ma l’interfaccia di gestione remota iLO (Integrated Lights-Out) risulta attiva e funzionante.

Grazie a iLO è possibile eseguire varie operazioni di gestione, tra cui lo spegnimento o il riavvio forzato del sistema. Nel caso affrontato, è stato sufficiente un Force System Reset per ripristinare la macchina.


I pulsanti di alimentazione di iLO e il loro significato

All’interno dell’interfaccia iLO sono disponibili diverse opzioni per controllare l’alimentazione del server. Ecco cosa significano:

  • Graceful Power Off
    Invia un comando di spegnimento ordinato al sistema operativo, simile a “Arresta il sistema” su Windows o shutdown su Linux. Richiede che l’OS sia ancora reattivo.

  • Force Power Off
    Spegne immediatamente il server togliendo l’alimentazione, come se si staccasse la spina. Può causare perdita di dati.

  • Force System Reset
    Riavvia il server senza togliere l’alimentazione, come premere il tasto fisico di reset. È la soluzione più rapida quando il sistema operativo è bloccato.

  • Force Power Cycle
    Spegne e riaccende l’alimentazione del server, simulando la disconnessione e riconnessione della corrente. Utile come ultima risorsa.


La soluzione nel caso pratico

Nel caso in cui il server risultasse acceso ma completamente bloccato, è bastato accedere a iLO e utilizzare il comando Force System Reset. Dopo pochi minuti il sistema operativo è tornato a rispondere correttamente sulla rete.


Conclusione

L’interfaccia iLO è uno strumento prezioso per gestire server HPE in situazioni di emergenza. Conoscere la differenza tra i vari comandi di alimentazione è essenziale per scegliere l’opzione meno invasiva e ridurre al minimo i rischi di perdita di dati.

Posted on

HPE iLO 5 SNMP Not Working? Here’s the Quick Fix

If your HPE iLO 5 SNMP service suddenly stops responding — even though the settings are correct — you’re not alone.

The Problem:

  • SNMP community string configured correctly

  • Port 161 open and reachable

  • iLO web interface shows SNMP as enabled

  • But SNMP queries return no data

The Cause:
A known issue in some iLO 5 firmware versions can cause the SNMP service to hang silently, especially after long uptime or certain configuration changes.

The Solution:

  1. Log in to the iLO web interface.

  2. Go to Information → Diagnostics → Reset iLO.

  3. Confirm the reset (this does not reboot the server, only the iLO controller).

  4. Test SNMP again — it should now respond normally.

Pro Tip:

  • Update to the latest iLO 5 firmware to avoid recurring issues.

  • If SNMP fails again in the future, a quick iLO reset is often all you need.

Sometimes the fastest fix is the simplest — reset iLO, and your SNMP is back in seconds.

Posted on

ILO 2 Power Management

  • momentary press esegue uno spegnimento regolare.
  • Press and Hold forza lo spegnimento del server
  • Cold boot come togliere l’alimentazione e riavviare

Se attraverso ILO il server risulta in standby spingere Momentary Press.

Se attraverso ILO il server sembra acceso ma non c’è il sistema operativo , spingere Cold Boot

Posted on

“Failed bios lock” when installing HPE Reseller Option Kit (ROK) 2019 – 2022 Server

Installing the HPE Re-seller Option Kit (ROK) Windows 2019 or 2022 Standard and Datacenter server software onto VMware virtual machine you should received “Failed BIOS Lock” error which means the HPE branded OS software needs HPE hardware to run.

To solve it, shout down virtual machine and :

  • Enter the Edit Settings of the VM
  • VM Options, Advanced, Edit Configuration, Add Configuration Params then type:
  • Name field: smbios.addHostVendor
  • Value field: TRUE

Posted on

Install Proliant Service Pack using ILO

Scenario

You have downloaded the prolian service pack in iso format and want to install it using ILO.
In ILO open “Remote Console & Media” and load the iso. Restart the server and start installing the service pack. At some point the installation crashes (at a certain percentage of completion).

Solution

The problem is that you used ILO’s HTML5 client to load the ISO; you have to use the Java client.

Hmtl5 remote console unmaps the image after a while