Migrating from HPE ProLiant DL380 Gen9 to DL380 Gen11 — Parts, Timeline and Budget Guide
Written for IT leaders planning an HPE ProLiant refresh in 2026. All specs and part numbers come from HPE QuickSpecs and ICD’s live catalog. HPE has retired the Gen9 platform from sale. The single-hop jump past Gen10 is the most common 2U migration ICD sees in 2026 — skipping Gen10 saves one full procurement cycle.
Why this migration
HPE has retired the DL380 Gen9 from sale and publishes no end-of-support date for it. Beyond end of support, HPE post-warranty pricing escalates, SPP firmware bundle cadence drops, and iLO CVE patches tail off. DL380 Gen11 resets the lifecycle clock, brings DDR5 bandwidth, AMX AI tile instructions, and — critically in 2026 — aligns you with HPE’s active security train (iLO 6).
OEM support timeline
HPE publishes no end-of-support date for the DL380 Gen9, so check your coverage with HPE by serial number. After end of support, HPE parts availability becomes best-effort, OneView firmware bundles ship less frequently, and critical CVE patches for iLO/BIOS taper off.
Your DL380 Gen11 is on HPE’s current product line. New HPE SPP (Service Pack for ProLiant) drops land first on the active platforms, which means your security posture improves measurably post-migration.
Compatibility analysis
The DDR4 → DDR5 transition is the single biggest compatibility barrier. DDR5 UDIMM/RDIMM uses 288 pins at 1.1V versus DDR4 at 1.2V; notch positions differ; PMIC is on-DIMM rather than on-motherboard. Zero mechanical carry-over. Expect full memory replacement for this path.
| Subsystem | DL380 Gen9 | DL380 Gen11 | Carry-over |
|---|---|---|---|
| CPU socket | LGA2011-3 | LGA4677 | No — full CPU replacement |
| Memory (DDR4 → DDR5) | 3TB DDR4-2400 | 8TB DDR5-4800/5600 | No — DDR4 not pin-compatible with DDR5 |
| Storage backplane | Smart Array P440ar / P840ar (12G SAS) | Broadcom MegaRAID MR216i-p / MR416i-o | No — controller family change (Smart Array → MR) |
| Drive carriers 2.5″ SFF | HPE Gen8/9 carrier | HPE Gen11 carrier | No — new drive tray |
| Power supplies | 500W-1400W Flex Slot | 800W-2200W Flex Slot (Platinum and Titanium) | Partial — Flex Slot form factor preserved |
| Rails + CMA | HPE Gen8/9 rail kit | HPE Gen11 rail kit | No — new rail kit |
| iLO generation | iLO 4 | iLO 6 | Advanced license transferable with HPE-assisted entitlement move |
Smart Array → MR controller implications
The controller line change from HPE Smart Array to Broadcom-based MR (MegaRAID) controllers on Gen11 is more than a rebrand. Three operational impacts matter in a migration:
- Cache protection hardware changes. The HPE Smart Storage Battery kit (for example 871264-001 with a 145 mm cable or P01367-B21 with a 260 mm cable) depends on the controller and chassis — order the kit HPE QuickSpecs lists for the target controller.
- Array metadata format changes. You cannot physically move a Smart Array P840ar-flashed array into an MR216i-p and expect it to import. The data must be migrated via replication (storage vMotion, DB log shipping, rsync, etc.) — not drive-pulled and re-inserted.
- Management tooling changes. HPE Smart Storage Administrator (SSA) scripts and Ansible modules do not target MR controllers. Rewrite or port to storcli64 / Redfish MR schemas.
Data migration path
Depending on what sits on the DL380 Gen9, the data path varies. For hypervisor hosts (VMware vSphere, Nutanix, KVM, Hyper-V) the cleanest path is live workload migration — vMotion, Nutanix Move, Live Migration — node-by-node. Provision one DL380 Gen11 alongside the cluster, add it as a node, evacuate one DL380 Gen9, retire the DL380 Gen9, repeat. ICD has delivered 40+ of these phased VMware refreshes in the region with near-zero downtime.
For bare-metal databases (Oracle, MSSQL, PostgreSQL) use native replication: Oracle Data Guard, SQL Server AG, PG streaming replication. Target DL380 Gen11 becomes the standby, then failover during a planned window. This protects RPO strictly and lets you roll back if the DL380 Gen11 hits an unexpected issue during burn-in.
For file servers, backup targets, and archive the classic rsync or Robocopy approach works — but plan for longer windows if you are moving from 12G SAS SFF to NVMe E3.S, as the target can ingest 4-10x faster than the source can read.
Parts shopping list (real PNs in ICD’s catalog)
- Target CPU (DL380 Gen11): Xeon Scalable Gen4/Gen5 processors (kit part numbers are specific to each chassis, quoted for your exact server)
- Target memory (DDR5): P43328-B21 (32GB RDIMM DDR5-4800), P43331-B21 (64GB RDIMM DDR5-4800), P50311-B21 (32GB 2Rx8 DDR5-4800), P50312-B21 (64GB 2Rx4 DDR5-4800), P43334-B21 (128GB DDR5-4800 3DS)
- Target controller: P26324-B21 (MR216i-a 12G), P26279-B21 (MR416i-a 12G), P06367-B21 (MR416i-p 12G), P04220-B21 (SR416i-a 24G Tri-Mode), P12688-B21 (SR416i-a 24G)
- Target PSU: P38995-B21 (800W FS Platinum), P18224-B21 (800W FS Titanium)
- Source spares available (DL380 Gen9) for ICD Care+ bridge: 726718-B21 (8GB RDIMM DDR4-2133), 774172-001 (16GB RDIMM DDR4-2133), 726736-B21 (P440ar / 2GB FBWC), 749974-B21 (P440ar / 2GB, Fio kit)
Budget reality in USD
Get a free infrastructure audit and custom proposal. Our team responds within 24 hours.
Migration phases and next steps
- Baseline (week 1). Export current iLO configs, HPE OneView inventory, Smart Array drive maps, BIOS settings, and firmware levels for every DL380 Gen9 node in scope. ICD provides a free export script on request.
- BOM design (week 1-2). RFQ to ICD for BTO DL380 Gen11 configs. ICD returns a cost-audited BOM in 24 hours with HPE part numbers, warranty posture, and lead-time visibility.
- Pilot (week 3-5). Deploy one DL380 Gen11 pilot node. Migrate one non-critical workload (typically a dev/test VM, a secondary DB replica, or a file-server target). Validate performance under load, iLO Redfish scripts, and your backup integration.
- Rolling production cutover (week 5-12). Phased migration by application window. Each DL380 Gen9 node evacuated, retired, optionally repurposed for DR or returned to ICD under buy-back credit.
- Post-migration (week 13+). Turn off HPE support on the retired fleet (or keep it if you are holding as cold spares), re-baseline capacity plans against the new platform headroom, and document the new BOM for next-cycle planning.
Get a migration BOM + TCO model
ICD returns a full BOM, pilot-node quote, phased migration plan, and optional ICD Care+ bridge pricing within 24 hours.
Request a Migration QuoteFrequently Asked Questions
Why skip Gen10 and move a DL380 Gen9 straight to Gen11?
HPE has retired the Gen9 platform from sale, and the single-hop jump past Gen10 is the most common 2U migration seen in 2026. Skipping Gen10 saves one full procurement cycle, and the Gen11 resets the lifecycle clock with DDR5 bandwidth, AMX instructions and iLO 6.
Which DL380 Gen9 components can carry over to a Gen11 build?
Very little. The CPU, DDR4 memory, Smart Array P440ar or P840ar controllers, Gen8/9 drive carriers and rail kit all need replacing. Power supplies are a partial carry-over because the Flex Slot form factor is preserved, and the iLO Advanced license is transferable with an HPE-assisted entitlement move.
Can DL380 Gen9 nodes stay covered while the Gen11 budget is approved?
Yes. If budget approval slips by a quarter, ICD Care+ TPM covers the DL380 Gen9 with tested spares and on-site SLA levels from NBD / 8H to 2H response, so maintenance coverage is not lost. Source spares held for that bridge include 726718-B21 8GB DDR4-2133 RDIMM and 726736-B21 P440ar controllers.
How do we move a VMware cluster from DL380 Gen9 to Gen11 without downtime?
Use live workload migration node by node. Provision one DL380 Gen11 alongside the cluster, add it as a node, evacuate one Gen9 with vMotion, retire it and repeat. The page notes 40+ phased VMware refreshes delivered in the region this way with near-zero downtime.
