{"title":"HPE Servers","description":"\u003cp data-start=\"509\" data-end=\"524\"\u003e\u003cstrong data-start=\"509\" data-end=\"524\"\u003eHPE Servers\u003c\/strong\u003e\u003c\/p\u003e\n\u003cp data-start=\"526\" data-end=\"856\"\u003e\u003cstrong data-start=\"526\" data-end=\"550\"\u003eHPE ProLiant servers\u003c\/strong\u003e are trusted by businesses and data centers around the world for their reliability, scalability, and enterprise performance. Whether you need a compact rack server, a high-capacity storage platform, or a dense blade server environment, HPE offers solutions designed to support a wide range of IT workloads.\u003c\/p\u003e\n\u003cp data-start=\"858\" data-end=\"1248\"\u003eOur selection includes popular systems from multiple generations, including \u003cstrong data-start=\"934\" data-end=\"973\"\u003eHPE Gen9, Gen10, and Gen10+ servers\u003c\/strong\u003e, with configurations suited for virtualization, application hosting, databases, and storage infrastructure. From models like the \u003cstrong data-start=\"1103\" data-end=\"1135\"\u003eDL360 and DL380 rack servers\u003c\/strong\u003e to \u003cstrong data-start=\"1139\" data-end=\"1162\"\u003eBL460 blade servers\u003c\/strong\u003e, HPE platforms are built to deliver dependable performance in demanding environments.\u003c\/p\u003e\n\u003cp data-start=\"1250\" data-end=\"1506\" data-is-last-node=\"\" data-is-only-node=\"\"\u003eAt \u003cstrong data-start=\"1253\" data-end=\"1274\"\u003eWholesale Servers\u003c\/strong\u003e, we provide professionally tested \u003cstrong data-start=\"1309\" data-end=\"1348\"\u003eHPE servers and enterprise hardware\u003c\/strong\u003e ready to power your business network, data center, or lab environment. Browse our collection to find the right ProLiant server for your infrastructure needs.\u003c\/p\u003e","products":[{"product_id":"dl380-g9-2-5-16-bay-chassis","title":"HPE ProLiant DL380 Gen9 16-Bay 2.5\" Drives","description":"\u003cp\u003eThe refurbished HPE ProLiant DL380 Gen9 16-Bay 2.5\" is HPE's Gen9 dual-socket 2U mainstream platform - the data-center workhorse of the Gen9 generation, built around Intel Xeon E5-2600 v3 (Haswell-EP) or v4 (Broadwell-EP) processors on the Grantley platform with the C610 chipset. Two sockets, up to 22 cores per CPU on v4 (44 cores total), 24 DDR4 DIMM slots, 3 TB maximum memory, sixteen 2.5\" SFF hot-swap bays as the standard mainstream configuration, modular Smart Array storage controllers, embedded 4-port 1 GbE plus optional FlexibleLOM mezzanine, and iLO 4 management. This is the HPE counterpart to the Dell PowerEdge R730 (2U 2S Grantley) - same generation, same workload positioning, equivalent feature set.\u003c\/p\u003e\u003cp\u003eGen9 launched in 2014 (v3) with a v4 refresh in 2016. It sits one generation behind Gen10 and three behind Gen11. As of 2026, HPE active warranty and Pointnext ProSupport on Gen9 hardware has ended, and third-party maintenance is the standard production support path. We're not going to soft-pedal Gen9's age: for new mission-critical deployments where Silicon Root of Trust, PCIe Gen4, DDR4-2933+ memory speed, or current HPE support matter, the Gen10 step (DL380 Gen10) delivers material improvements. Where the DL380 Gen9 still earns its place is fleet-extension of existing Gen9 estates, lab and staging environments mirroring production, and budget-driven deployments where the Gen10 acquisition cost isn't justified by the actual performance requirement.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL380 Gen9 Fits in the Family\u003c\/h2\u003e\u003cp\u003eThe DL380 has been HPE's dual-socket mainstream platform across multiple generations - the default when you needed a 2U dual-socket general-purpose server. The Gen9 chassis introduced the modular drive-bay system that carried forward through Gen10 (8\/10\/12\/16\/18\/24 SFF or 4\/12 LFF from a common base), uses the same iLO 4 management and FlexibleLOM networking as the rest of the Gen9 line, and pairs 24 DIMM slots and a 3 TB memory ceiling with up to 6 PCIe Gen3 slots.\u003c\/p\u003e\u003cp\u003eThe 16-Bay 2.5\" is the Gen9 mainstream SFF sweet spot. Eight bays is too few for most production database, VM-density, or HCI workloads on a dual-socket platform; twenty-four bays is more than most workloads need and pushes power, thermal, and controller decisions toward higher tiers. Sixteen bays is the right balance for the most common dual-socket SFF deployments: vSphere clusters with a local SSD tier, mid-tier SQL Server or Oracle hosts, Hyper-V hosts, VDI hosts with persistent storage, mid-size vSAN\/S2D nodes, and general-purpose file and application servers needing meaningful SFF capacity. If 8 bays cover your workload, use the DL380 Gen9 8-Bay companion; if 24 are needed, use the 24-Bay companion.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage - 16 SFF Bays\u003c\/h2\u003e\u003cp\u003eSixteen 2.5\" SAS\/SATA hot-swap bays across two drive boxes (8 + 8) in the front of the chassis, with field upgrades to 18 or 24 SFF via additional drive-cage kits and rear-mounted 2 SFF or 3 LFF expansion through the Universal Media Bay or rear-bay kits. At full population with 3.84 TB SAS SSDs the 16-bay configuration delivers roughly 61 TB raw, and larger drives on later firmware push that higher. Drive options span the full Gen9 SFF portfolio: SAS SSDs in mixed-use and read-intensive tiers (200 GB through 3.84 TB at launch), SATA SSDs for cost-optimized roles, 10K and 15K SAS HDDs for moderate-IOPS data (up to 2.4 TB SFF), self-encrypting drives for compliance, and NVMe via the Express Bay option (up to 6 SFF positions, consuming bay count).\u003c\/p\u003e\u003cp\u003eCommon 16-bay storage profiles in production:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eVMware vSAN node.\u003c\/strong\u003e 2x SSDs for ESXi boot, 4-6 mixed-use SSDs as cache, 8-10 larger SSDs as capacity. The DL380 Gen9 is a documented vSAN ReadyNode; check the current VMware HCL for firmware support.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSQL Server or Oracle host with local SSDs.\u003c\/strong\u003e 2x SSDs RAID 1 for OS, 2x SSDs RAID 1 for tempdb or Oracle Grid, 8-12 SAS SSDs in RAID 10 for database files. For larger databases, primary on SAN with the 16 bays as a high-performance local tier.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eHCI or VDI host.\u003c\/strong\u003e 16 bays in HBA mode for software-defined storage (S2D, vSAN, Nutanix on KVM), or RAID 6\/10 SSD pools for Citrix\/Horizon profile and image storage.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eThree patterns: 2x SSDs in RAID 1 in standard bays (consuming 2 of 16); 2x rear-bay SSDs via the rear-2-SFF kit (preserving all 16 front bays); or M.2 SATA via the HPE M.2 enablement card in a PCIe slot. Where front-bay capacity matters, we default to the rear-2-SFF kit unless the customer specifies otherwise.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Controllers\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen9 introduced the HPE modular Smart Array \"ar\" controller form factor - controllers that mount in a dedicated chassis slot rather than consuming a PCIe position. Controller options:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P440ar (2 GB FBWC).\u003c\/strong\u003e The mainstream production controller. Full hardware RAID 0\/1\/5\/6\/10\/50\/60, 2 GB flash-backed write cache. The right pick for the 16-bay configuration in most production workloads.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P840ar (4 GB FBWC).\u003c\/strong\u003e Premium controller with a larger cache - specify when write workload pressures the P440ar's 2 GB (SQL Server transaction logs, write-intensive Oracle redo, sustained-write HCI cache tiers).\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array H241 (HBA mode, PCIe plug-in).\u003c\/strong\u003e Clean SAS pass-through for software-defined storage (vSAN, Ceph, ZFS, S2D). No hardware RAID.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDynamic Smart Array B140i (embedded software RAID).\u003c\/strong\u003e Acceptable for OS boot mirroring; not appropriate for production data on a 2-socket platform.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThe HPE Smart Storage Battery is required with any P-series controller. The Gen9 FBWC battery has a documented 5-7 year service life; many refurbished units have batteries past spec, and we replace cache modules as part of build prep when needed.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors\u003c\/h2\u003e\u003cp\u003e1 or 2 sockets of Intel Xeon E5-2600 v3 (Haswell-EP) or v4 (Broadwell-EP) on the C610 Grantley chipset. Mixing v3 and v4 is not supported - all installed CPUs must be the same generation, though a field upgrade from v3 to v4 (replacing both simultaneously) is supported. Single-socket builds cut DIMM slots in half (12 instead of 24) and PCIe to 3 slots, so 2-socket is the production standard.\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2680 v4 (14 cores, 120W, DDR4-2400).\u003c\/strong\u003e The Gen9 production mainstream - 28 cores at 2S, balanced TDP, standard heatsink.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2690 v4 (14 cores, 135W, 2.6 GHz).\u003c\/strong\u003e Higher base frequency for single-thread-sensitive workloads within the core budget.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2699 v4 (22 cores, 145W).\u003c\/strong\u003e Top-bin Broadwell-EP - 44 cores at 2S, the platform maximum. Requires the high-performance heatsink (auto-included for 120W+ CPUs).\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2650 v4 (12 cores, 105W).\u003c\/strong\u003e Mid-tier production at modest TDP and lower acquisition cost - good for general virtualization and application servers.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2620 v4 (8 cores, 85W) and E5-2667 v4 (8 cores, 135W, 3.2 GHz).\u003c\/strong\u003e Entry-tier and high-frequency specialty SKUs; the 2667 v4 is the per-core-licensing pick for Oracle and SQL Server Enterprise. Haswell-EP v3 equivalents are available at lower cost with a DDR4-2133 cap.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eMemory\u003c\/h2\u003e\u003cp\u003e24 DDR4 DIMM slots (12 per CPU; only 12 available with a single CPU). RDIMM and LRDIMM are supported but cannot be mixed in one server; maximum 3 TB with 128 GB LRDIMMs across all 24 slots on v4 CPUs. HPE DDR4 Smart Memory is required for rated speeds - third-party DDR4 drops to lower speeds, documented HPE behavior across Gen9.\u003c\/p\u003e\u003cp\u003eMemory speed depends on CPU generation and population: v3 caps at DDR4-2133, v4 at DDR4-2400, and full 24-DIMM population drops to DDR4-1866 or DDR4-1600 depending on rank. For maximum bandwidth, populate at 1 DPC (12 DIMMs at 2S). HPE Persistent Memory (NVDIMM-N, 8 GB and 16 GB) is supported on v4 CPUs for DRAM-class latency with battery-backed persistence - uncommon, but available for SQL Server transaction logs and in-memory database WAL.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking and PCIe Expansion\u003c\/h2\u003e\u003cp\u003eEmbedded HPE 4-port 1 GbE 331i adapter standard, no slot consumption. The optional FlexibleLOM mezzanine supports 10 GbE SFP+ (530FLR\/534FLR), 10 GBASE-T, 25 GbE SFP28, and converged FlexFabric. Unlike the DL580 Gen9, Wake-on-LAN works on both embedded 1 GbE and FlexibleLOM here. PCIe expansion is 3 PCIe Gen3 slots with one CPU, expanding to 6 with both CPUs populated; the +3-slot riser requires the second processor. All slots are PCIe Gen3 and support cards up to 150W, higher with the supplemental power cable kit.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eGPU Support\u003c\/h2\u003e\u003cp\u003eGPU and accelerator support is bounded by the PCIe Gen3 generation and the 2U thermal envelope:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSingle-width accelerators.\u003c\/strong\u003e Cards like the NVIDIA Tesla T4 (70W, single-slot, passive) for inference, transcoding, or VDI graphics offload. They fit standard riser positions and need no GPU power cable kit.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDouble-width GPUs.\u003c\/strong\u003e Passively cooled Gen9-era cards (NVIDIA M40, M60, K80-class). These require the high-performance heatsink and an additional GPU power cable kit (PN 669777-B21); plan for up to two, subject to PSU sizing.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eThermal envelope.\u003c\/strong\u003e GPU builds require performance heatsinks and the high-performance fan kit, and ASHRAE A3\/A4 ambient headroom is reduced with double-wide cards. We validate inlet temperature against the configuration at quote time.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eFPGA and specialty cards.\u003c\/strong\u003e The PCIe Gen3 x16 slots accept FPGA and specialty cards within the 150W per-slot limit. PCIe Gen3 bandwidth is the ceiling - workloads needing PCIe Gen4 GPU bandwidth belong on Gen10 Plus or Gen11.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eManagement - iLO 4 Generation\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen9 ships with HPE iLO 4: remote console (iLO Advanced license for full graphical KVM), virtual media, IPMI, SNMP telemetry, Active Health System logging, and HPE OneView compatibility - the same iLO 4 generation across the Gen9 line, which is part of the platform's operational-standardization value. The key difference from Gen10 is that iLO 4 has no Silicon Root of Trust; the hardware-anchored firmware verification chain arrived with iLO 5 on Gen10. UEFI Secure Boot is supported and is the right pattern for production Gen9 builds, with compensating controls where a compliance framework requires firmware-integrity attestation. iLO Advanced is typically a separate cost and is rarely optional for production data-center deployments; we quote it explicitly.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\u003cp\u003eHPE Flex Slot power supplies in 1+1 redundant configurations, up to 96% efficient Titanium, plus the Gen9-distinctive optional Flexible Slot Battery Backup module for in-chassis ride-through. PSU options:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003e500W Platinum.\u003c\/strong\u003e Entry tier for low-TDP single-CPU or modest dual-CPU builds.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e800W Platinum\/Titanium.\u003c\/strong\u003e The standard production PSU - 2x 800W in 1+1 covers all common dual-socket builds including E5-2680\/2690 v4 with full memory and 16 SSDs.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e1400W Platinum.\u003c\/strong\u003e Required for top-bin E5-2699 v4 or double-wide GPU builds. Supports both low-line and high-line input.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThermal: ASHRAE A3 (40°C) and A4 (45°C) extended-ambient operation is supported with the optional performance heatsinks (auto-included for 120W+ CPUs).\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePhysical Specs \u0026amp; Platform Notes\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eForm factor:\u003c\/strong\u003e 2U rackmount, standard-depth Gen9 enclosure shared across the DL380 Gen9 bay-count variants; with the cable management arm installed, plan for additional rear clearance.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe expansion:\u003c\/strong\u003e up to 6 PCIe Gen3 slots with both CPUs populated (3 with one CPU), split full-height and low-profile across the primary and secondary risers; the secondary riser requires the second processor.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eParts availability:\u003c\/strong\u003e excellent. The DL380 Gen9 shipped in one of the largest install bases of any 2U generation, so drives, PSUs, risers, heatsinks, FlexibleLOM cards, and Smart Array controllers are widely available; third-party maintenance spares depth is strong in major metros.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAccessories we recommend:\u003c\/strong\u003e the 2U SFF ball-bearing sliding rail kit (P\/N 679365-001 \/ 737412-001; see the \u003ca href=\"\/products\/hp-dl380-g8-g9-sff-sliding-rails-679365-001-737412-001\"\u003eDL380 Gen9 2U SFF sliding rail kit\u003c\/a\u003e), the optional Universal Media Bay (PN 724865-B21) for front VGA and USB, the rear-2-SFF kit for boot placement, and the GPU power cable kit (PN 669777-B21) on accelerator builds.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePlatform notes:\u003c\/strong\u003e CPU hot-plug is not supported, and v3\/v4 CPUs cannot be mixed. NVMe via the Express Bay option consumes specific front-bay positions. Confirm FlexibleLOM and drive-backplane compatibility against the specific build at quote time.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003e\u003cstrong\u003eWhere it excels:\u003c\/strong\u003e The DL380 Gen9 16-Bay 2.5\" is the right answer for fleet-extension of an existing Gen9 estate and for budget-driven dual-socket workloads that fit the E5-2600 v3\/v4 envelope. It is a strong fit for vSphere and Hyper-V clusters with a local SSD tier, mid-tier SQL Server and Oracle hosts, VDI hosts with persistent storage, mid-size vSAN and S2D nodes, and general-purpose file and application servers that need meaningful SFF capacity without the 24-bay storage budget. Sixteen bays is the SFF sweet spot for the most common production dual-socket deployments.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhere to look instead:\u003c\/strong\u003e If eight bays cover the workload, the \u003ca href=\"\/products\/hp-proliant-dl380-g9-2-5-8-bay-server\"\u003eDL380 Gen9 8-Bay 2.5\"\u003c\/a\u003e is the more economical choice; for maximum SFF density, step to the \u003ca href=\"\/products\/dl380-g9-2-5-24-bay-chassis\"\u003eDL380 Gen9 24-Bay 2.5\"\u003c\/a\u003e; for bulk HDD capacity, the \u003ca href=\"\/products\/hp-proliant-dl380-g9-12-bay-3-5-chassis\"\u003eDL380 Gen9 12-Bay 3.5\"\u003c\/a\u003e is purpose-built. New mission-critical deployments that need iLO 5 Silicon Root of Trust, PCIe Gen4, or DDR4-2933+ bandwidth should move to the \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\"\u003c\/a\u003e. Dell-standardized shops should compare the \u003ca href=\"\/products\/dell-poweredge-r730-16-bay-2-5-chassis\"\u003eDell PowerEdge R730 16-Bay 2.5\"\u003c\/a\u003e, the equivalent 2U Grantley platform.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eBottom line:\u003c\/strong\u003e This is the HPE Gen9 2U workhorse, and for the right buyer it is one of the strongest price-to-capability values on the refurbished market. The typical customer is an IT team standardizing on an existing Gen9 fleet, a lab or staging environment mirroring production, or a budget-conscious deployment where the Gen10 premium isn't justified by the actual performance requirement. Buy it when operational familiarity and acquisition cost matter more than current-generation security and memory-bandwidth features; step up to Gen10 when they do.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL380 Gen9 Fits in 2026\u003c\/h2\u003e\u003cp\u003eHPE active warranty and Pointnext ProSupport have ended for both v3 and v4 builds, so third-party maintenance from established providers (Park Place, Service Express, Curvature) is the standard production support pattern, with strong spares depth in major metros given the broad install base. Two generations sit above Gen9: Gen10 (Skylake\/Cascade Lake) added iLO 5 with Silicon Root of Trust and DDR4-2933, and Gen10 Plus \/ Gen11 brought PCIe Gen4 and DDR5.\u003c\/p\u003e\u003cp\u003eThe DL380 Gen9 16-Bay 2.5\" earns its place in 2026 when existing Gen9 standardization makes a capacity-add cheaper than a generational step, when VMware\/Hyper-V clusters need additional nodes, when lab\/dev\/staging mirrors production, or when the workload's performance envelope sits well within Gen9 capability. The 16-bay configuration specifically is the SFF sweet spot - meaningful local storage without committing to the 24-bay budget when the workload doesn't need it.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eHPE active warranty and ProSupport on Gen9 has ended.\u003c\/strong\u003e Third-party maintenance is the standard pattern; we coordinate contracts as part of the quote when requested.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eiLO 4, not iLO 5 - no Silicon Root of Trust.\u003c\/strong\u003e Firmware protection via UEFI Secure Boot only; a documented gap versus Gen10 for platform-attestation frameworks.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDDR4 speed cap at DDR4-2400 (v4) or DDR4-2133 (v3),\u003c\/strong\u003e and full 24-DIMM population drops further to DDR4-1866\/1600. Material for memory-bandwidth-sensitive workloads.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSingle-CPU configurations limit DIMM and PCIe\u003c\/strong\u003e to 12 slots and 3 slots respectively; 2-CPU is the production standard.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe Gen3 only.\u003c\/strong\u003e A hard generational limit for PCIe Gen4 NICs, NVMe, or GPU bandwidth - step to Gen10 Plus or Gen11.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eFBWC battery is a wear item\u003c\/strong\u003e (5-7 year life); we disclose battery state and replace past-spec cache modules during build prep.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMixing v3 and v4 CPUs is not supported,\u003c\/strong\u003e and HPE Smart Memory is required for rated speeds.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eThis server is right for\u003c\/th\u003e\n\u003cth\u003eConsider Gen10\/Gen11 for\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ VMware\/Hyper-V cluster nodes at Gen9 standardization\u003c\/td\u003e\n\u003ctd\u003e❌ New mission-critical deployments requiring iLO 5 + Silicon Root of Trust\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ Mid-tier SQL Server \/ Oracle hosts with local SSD tier\u003c\/td\u003e\n\u003ctd\u003e❌ PCIe Gen4 NIC, NVMe, or GPU bandwidth requirements\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ VDI hosts requiring SFF-bay-heavy storage\u003c\/td\u003e\n\u003ctd\u003e❌ Memory-bandwidth-sensitive workloads (DDR4-2933+ needed)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ HCI nodes (vSAN, S2D, Nutanix on KVM) at Gen9 platform\u003c\/td\u003e\n\u003ctd\u003e❌ Workloads requiring more than 3 TB memory per host\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ Capacity-add to an existing DL380 Gen9 fleet\u003c\/td\u003e\n\u003ctd\u003e❌ Active HPE ProSupport requirement\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eFewer SFF bays (8) at the same Gen9 platform?\u003c\/strong\u003e → \u003ca href=\"\/products\/hp-proliant-dl380-g9-2-5-8-bay-server\"\u003eDL380 Gen9 8-Bay 2.5\"\u003c\/a\u003e - reduced storage scope, same platform.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMaximum SFF density (24)?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g9-2-5-24-bay-chassis\"\u003eDL380 Gen9 24-Bay 2.5\"\u003c\/a\u003e.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eLFF (3.5\") drives for bulk capacity?\u003c\/strong\u003e → \u003ca href=\"\/products\/hp-proliant-dl380-g9-12-bay-3-5-chassis\"\u003eDL380 Gen9 12-Bay 3.5\"\u003c\/a\u003e - high-capacity NL-SAS pool.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eA lower-cost 2U Gen9 value tier?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl180-gen9-lff-build-your-own\"\u003eHPE ProLiant DL180 Gen9 LFF\u003c\/a\u003e - cost-optimized 2U dual-socket Gen9.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eGen10 with iLO 5, Silicon Root of Trust, DDR4-2933?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\"\u003c\/a\u003e.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDell alternative at the same tier?\u003c\/strong\u003e → \u003ca href=\"\/products\/dell-poweredge-r730-16-bay-2-5-chassis\"\u003eDell PowerEdge R730 16-Bay 2.5\"\u003c\/a\u003e - 2U 2S Grantley, equivalent positioning.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e4-socket Gen9?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl580-gen9-5-bay-build-your-own\"\u003eDL580 Gen9 5-Bay 2.5\"\u003c\/a\u003e - 4U 4-socket E7 flagship.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us the workload, CPU generation preference (v3 vs v4), memory target, storage configuration (bay count, drive types, RAID layout, controller preference), networking requirement (embedded 1 GbE vs FlexibleLOM), boot configuration, PSU model, and quantity. We respond within 24 hours with a validated configuration including HPE Power Advisor sizing and third-party maintenance coordination when requested. Every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in testing, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951241486535,"sku":"BP-013606","price":291.62,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-g9-16-bay-25-drives-790075.png?v=1765539627"},{"product_id":"hp-proliant-dl380-g10-3-5-12-bay-server","title":"HPE ProLiant DL380 Gen10 12-Bay 3.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL380 Gen10 12-Bay 3.5\" is the LFF capacity configuration of HPE's 2U dual-socket Gen10 platform: twelve large-form-factor 3.5\" SAS\/SATA hot-swap bays on the same Purley dual-socket motherboard, same memory architecture, same iLO 5 management, and same Smart Array RAID family as the 16-Bay 2.5\" canonical. This page covers the LFF chassis and its bulk-capacity storage profile.\u003c\/p\u003e\u003cp\u003eFor the full platform-fact story (processors, memory architecture, FlexibleLOM networking, PCIe expansion, iLO 5 management, Smart Array controllers, power supplies, physical specs), see the \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\" canonical page\u003c\/a\u003e. Everything documented there applies to this 12-Bay LFF variant; this page focuses on what's different about the LFF chassis and the workloads it serves.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhat's Different About This Chassis\u003c\/h2\u003e\u003cp\u003eThe 12-Bay 3.5\" is the bulk-capacity variant of the DL380 Gen10 family. Three things define it relative to the SFF siblings:\u003c\/p\u003e\u003col\u003e\n\u003cli\u003e\n\u003cstrong\u003eLFF drive support.\u003c\/strong\u003e Twelve 3.5\" hot-swap bays accept 7,200 RPM NL-SAS \/ SATA enterprise capacity drives at up to 20 TB each (current generation). The platform also accepts 3.5\" SAS HDDs at 10K or 15K RPM (legacy choice, rarely deployed today) and 3.5\" enterprise SATA HDDs. SFF 2.5\" drives are NOT supported in the 12-Bay 3.5\" backplane.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eBulk-capacity workload profile.\u003c\/strong\u003e The 12-Bay LFF is sized for NAS, file serving, backup repository, archive, object storage, and Ceph capacity-tier OSD nodes. The storage profile is high-capacity, sequential-throughput-optimized; random IOPS per drive (150 to 200 on 7,200 RPM NL-SAS) is intentionally modest. This is bulk capacity in a 2U enterprise chassis.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e240 TB raw at maximum density.\u003c\/strong\u003e 12 x 20 TB NL-SAS = 240 TB raw, approximately 180 TB usable at RAID 6. This is the largest single-server capacity envelope in the Gen10 lineup and one of the densest 2U LFF capacities in the broader market.\u003c\/li\u003e\n\u003c\/ol\u003e\u003cp\u003eThe 12-Bay LFF is the right chassis when capacity-per-dollar drives the design and high random IOPS is not the binding constraint. When the workload is random-IOPS-bound or NVMe-latency-sensitive, the SFF chassis (16-Bay or 24-Bay 2.5\") is the right call.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Architecture\u003c\/h2\u003e\u003cp\u003eTwelve 3.5\" SAS\/SATA hot-swap front bays. Optional mid-plane adds 4 LFF (16 LFF total) and optional rear 3LFF + 2 SFF on appropriate Gen10 12-Bay variants, totaling up to 19 LFF + 2 SFF drives on flagship configurations. The 12-Bay base configuration (twelve front bays only) is the most common WS-stocked variant.\u003c\/p\u003e\u003cp\u003eCommon 12-Bay 3.5\" configurations we deploy:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eNAS \/ file serving at scale:\u003c\/strong\u003e 12 x NL-SAS HDDs at 16 TB or 20 TB each. 12 x 20 TB NL-SAS at RAID 6 = 200 TB raw \/ approximately 160 TB usable. Suitable for general-purpose enterprise file shares, SMB\/CIFS departmental shares, NFS exports, and Windows Storage Server deployments. Memory at 128 GB to 256 GB is the practical range; file system caching from DRAM meaningfully improves read throughput on spinning disk arrays.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eBackup repository (Veeam, Commvault, NetBackup):\u003c\/strong\u003e 12 x NL-SAS HDDs at RAID 6 or RAID 60 (when expanded with optional mid-plane to 16 LFF). The DL380 Gen10 12-Bay is widely deployed as Veeam ReFS repository or XFS landing for backup workloads where high write throughput and high capacity matter more than random IOPS. Pair with 25 GbE FlexibleLOM for backup ingestion at line rate.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCeph capacity-tier OSD nodes:\u003c\/strong\u003e 12 OSDs per node with NL-SAS HDDs, paired with separate flash-tier nodes for cache and metadata. The 12-Bay LFF is the right HPE platform for Ceph capacity tiers where cost-per-TB drives the design. Plan memory at 6 GB per OSD plus 16 GB overhead (96 GB to 128 GB per node typical).\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eArchive and tier-3 storage:\u003c\/strong\u003e Long-retention cold storage where data is written once and read rarely. 12 x 20 TB NL-SAS at RAID 6 with low memory and minimal CPU. Often deployed with HSM (hierarchical storage management) software that tiers data between this and faster storage.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eObject storage nodes (S3-compatible: MinIO, Scality, Cloudian, OSNexus):\u003c\/strong\u003e Software-defined object storage with the 12 LFF bays as the storage layer. The DL380 Gen10 12-Bay is a common building block for on-premises S3 deployments where the workload economics favor LFF over SFF.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMixed SAS SSD + NL-SAS tiered storage:\u003c\/strong\u003e 1 to 2 SAS SSDs in the optional mid-plane SFF bays for metadata or hot-data tier alongside 12 NL-SAS HDDs for bulk; tiered approach meaningfully improves effective NAS throughput for frequently-accessed data.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch2\u003eRAID Strategy for LFF Capacity\u003c\/h2\u003e\u003cp\u003eRAID strategy on 12-Bay LFF is the most consequential choice in the configuration because rebuild times on 16 TB to 20 TB drives are long enough that single-parity is not safe:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 6 mandatory for all NL-SAS \/ capacity configurations.\u003c\/strong\u003e Rebuild times on 16 TB to 20 TB NL-SAS HDDs at the 12-bay level commonly exceed 24 to 30 hours per drive; two-drive fault tolerance is non-negotiable. RAID 5 at this drive capacity is not a supportable production configuration.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 60 for backup repositories and Veeam ReFS:\u003c\/strong\u003e Two RAID 6 sets striped (6 + 6 drives) provides redundancy per set with aggregate throughput approaching dual-controller bandwidth. Strong fit for Veeam ReFS where the underlying file system contributes additional resilience.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eJBOD \/ HBA mode for software-defined storage:\u003c\/strong\u003e Smart Array E208i-a (HBA mode) is the controller for Ceph, ZFS, and similar software-defined stacks that require direct disk access. RAID handled at the software layer (Ceph replication, ZFS RAIDZ, etc.).\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a (4 GB FBWC) is the production hardware-RAID default for NAS and backup workloads.\u003c\/strong\u003e The 4 GB write cache absorbs burst writes meaningfully on NL-SAS arrays; sustained write throughput is bounded by spinning disk bandwidth.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eBoot configuration: HPE M.2 enablement kit installs 1 or 2 M.2 SATA SSDs in a dedicated bay outside the 12 LFF data bays. We strongly recommend M.2 boot; capacity nodes should have all 12 LFF bays available for data.\u003c\/p\u003e\u003ch2\u003eMemory and Networking for Bulk Storage\u003c\/h2\u003e\u003cp\u003eFor NAS and file serving, plan memory at 128 GB to 256 GB per node. File system caching from DRAM is the primary lever to improve effective read throughput on spinning disk arrays; more memory equals more hot data served from cache rather than disk seeks. Workloads with high read-to-write ratios benefit disproportionately from large caches.\u003c\/p\u003e\u003cp\u003eFor Veeam repository and backup workloads, 128 GB is the practical minimum for serious repository nodes; 256 GB is common for high-concurrency backup environments. Veeam ReFS metadata caching benefits from substantial memory; XFS-based Linux repositories similarly benefit.\u003c\/p\u003e\u003cp\u003eFor Ceph capacity-tier OSDs, 96 GB to 128 GB per node (12 OSDs at 6-8 GB each plus daemon overhead). BlueStore deployments at this capacity benefit from the higher end of that range.\u003c\/p\u003e\u003cp\u003eNetworking: the FlexibleLOM is the right slot for the primary network. For backup ingestion or NAS serving at production scale, 2 x 25 GbE SFP28 via the HPE 631FLR-SFP28 is the typical fit. For smaller-scale deployments, 2 x 10 GbE BASE-T or SFP+ FlexibleLOMs are adequate. 100 GbE FlexibleLOMs exist but are bandwidth-bound by PCIe Gen3 at the x8 mezzanine; for true 100 GbE throughput, the platform is Gen10+ with PCIe Gen4.\u003c\/p\u003e\u003ch2\u003ePower Sizing for LFF Capacity Workloads\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eConfiguration\u003c\/th\u003e\n\u003cth\u003ePSU Recommendation\u003c\/th\u003e\n\u003cth\u003eEst. Peak Draw\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eLight (2x Silver 4214, 64 GB, 12 NL-SAS HDDs, P816i-a)\u003c\/td\u003e\n\u003ctd\u003e2 x 500W Platinum (hot-plug redundant)\u003c\/td\u003e\n\u003ctd\u003e~360W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBalanced NAS (2x Gold 5218, 256 GB, 12 NL-SAS HDDs, P816i-a, 2 x 10 GbE)\u003c\/td\u003e\n\u003ctd\u003e2 x 800W Platinum\u003c\/td\u003e\n\u003ctd\u003e~440W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eVeeam repository (2x Gold 5218, 256 GB, 12 NL-SAS HDDs, P816i-a, 2 x 25 GbE)\u003c\/td\u003e\n\u003ctd\u003e2 x 800W Platinum\u003c\/td\u003e\n\u003ctd\u003e~460W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eCeph capacity-tier OSD (2x Gold 5218, 128 GB, 12 NL-SAS HDDs, E208i-a, 2 x 25 GbE)\u003c\/td\u003e\n\u003ctd\u003e2 x 800W Platinum\u003c\/td\u003e\n\u003ctd\u003e~420W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003cp\u003eLFF configurations draw meaningfully less peak power than SFF SSD configurations because spinning disks have lower steady-state power than enterprise SSDs at full load. 2 x 800W Platinum is the recommended PSU for production LFF deployments; the headroom over typical draw supports startup spin-up surge and accommodates fan ramp on high-temperature deployments.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhen to Pick a Different Chassis\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSFF SAS SSD storage:\u003c\/strong\u003e The \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\"\u003c\/a\u003e or \u003ca href=\"\/products\/hpe-dl380-g10-2-5-24-bay-chassis\"\u003e24-Bay 2.5\"\u003c\/a\u003e siblings are the right chassis for SAS SSD database storage, vSAN, and any workload bound by random IOPS or SSD-class latency.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNVMe-bound workloads:\u003c\/strong\u003e Gen10 LFF chassis has no native NVMe path. For NVMe storage tiers, evaluate the DL380 Gen10 Plus with NVMe-capable backplane.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003evSAN hybrid or all-flash:\u003c\/strong\u003e The 12-Bay LFF is not the right chassis for vSAN; the SFF siblings (16-Bay or 24-Bay 2.5\") are the vSAN platform.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eHigher per-node bay count:\u003c\/strong\u003e When 12 LFF bays is not enough, the optional mid-plane (up to 16 LFF) and rear-drive cage (up to 19 LFF + 2 SFF) configurations are available on flagship 12-Bay variants. Verify configuration at quote time.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e1U dense compute:\u003c\/strong\u003e The DL360 Gen10 1U pair-partner with 4 LFF bays is denser per rack U for workloads where 12 bays per node is excess.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eProduction greenfield past 2028:\u003c\/strong\u003e For long-horizon deployments, the DL380 Gen10 Plus 12-Bay LFF or Gen11 12-Bay LFF brings PCIe Gen4 \/ Gen5 and current-gen processor support.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10 12-Bay 3.5\" LFF is the right HPE platform for bulk-capacity storage workloads where cost-per-TB drives the design: large-scale NAS, backup repository infrastructure, Ceph capacity-tier OSD nodes, object storage, and archive. The platform's PCIe Gen3 limitation is largely irrelevant for spinning disk bulk storage workloads (the binding constraint is drive bandwidth, not interconnect bandwidth). The DDR4-2933 memory ceiling and Cascade Lake CPU envelope are similarly well-matched to bulk storage workloads where compute and memory are sized to the workload, not the platform ceiling.\u003c\/p\u003e\u003cp\u003eFor HPE-standardized shops, the 12-Bay LFF is the natural fit for storage capacity workloads at refurbished-market economics. The Dell PowerEdge R740xd 12-Bay 3.5\" is the cross-vendor tier-equivalent; choice between platforms is typically driven by which vendor the shop is standardized on, not by capability deltas.\u003c\/p\u003e\u003cp\u003eBottom line: For bulk capacity storage on the Gen10 platform, the 12-Bay 3.5\" LFF delivers proven enterprise reliability at meaningfully lower acquisition cost than current-generation alternatives. We deploy it most often as Veeam backup repository nodes, departmental NAS infrastructure, Ceph capacity-tier OSDs, and object storage building blocks.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eExcels at ✅\u003c\/th\u003e\n\u003cth\u003eWhere to look elsewhere ❌\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eLarge-scale NAS \/ file serving (up to 240 TB raw)\u003c\/td\u003e\n\u003ctd\u003eRandom-IOPS-bound workloads (use SFF SSD siblings)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eVeeam, Commvault, NetBackup repository nodes\u003c\/td\u003e\n\u003ctd\u003evSAN hybrid or all-flash (use 16-Bay or 24-Bay)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eCeph capacity-tier OSD clusters\u003c\/td\u003e\n\u003ctd\u003eNVMe storage tiers (use DL380 Gen10+ with NVMe)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eObject storage (MinIO, Scality, Cloudian)\u003c\/td\u003e\n\u003ctd\u003eDatabase storage tiers (use SAS SSD on SFF chassis)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eArchive and tier-3 cold storage\u003c\/td\u003e\n\u003ctd\u003eProduction greenfield past 2028 (consider Gen10+ \/ Gen11)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMixed SSD + NL-SAS tiered storage\u003c\/td\u003e\n\u003ctd\u003eMore than 16 LFF needed without flagship riser config\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eReady to Configure\u003c\/h2\u003e\u003cp\u003eTell us your capacity target, workload type (NAS, backup, Ceph, object), memory target, networking requirements, and unit quantity. We respond within 24 hours. Volume pricing applies at 5 units and above. Every Wholesale Servers DL380 Gen10 12-Bay LFF ships after a 12+ hour burn-in test covering every PCIe slot, every memory channel, and every drive bay. Standard 180-day warranty included; 1-Year, 2-Year, and 3-Year Premium warranty options available. Call 1-800-778-1545 or use the quote form on this page.\u003c\/p\u003e\u003cp\u003eIf your deployment has a 3+ year production horizon, we will also quote the DL380 Gen11 or Gen10 Plus 12-Bay LFF for comparison on request.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951241617607,"sku":"BP-013608","price":1326.73,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-g10-12-bay-35-drives-737679.png?v=1765539623"},{"product_id":"dl380-g10-2-5-16-bay-server","title":"HPE ProLiant DL380 Gen10 16-Bay 2.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL380 Gen10 16-Bay 2.5\" is the canonical SFF configuration of HPE's 2U dual-socket flagship, the platform that anchored mid-decade enterprise infrastructure for HPE shops the way the Dell R740 did for Dell shops. Sixteen 2.5\" hot-swap SAS\/SATA bays on the full Purley dual-socket platform with up to 24 DDR4 RDIMM\/LRDIMM slots, dual 1st or 2nd Generation Intel Xeon Scalable processors (Skylake-SP \/ Cascade Lake-SP, LGA 3647), HPE iLO 5 management with Silicon Root of Trust, and HPE Smart Array Gen10 RAID. This page anchors the canonical DL380 Gen10 platform-fact documentation at Wholesale Servers; the 24-Bay 2.5\" and 12-Bay 3.5\" LFF sibling pages reference this page for shared platform vocabulary.\u003c\/p\u003e\u003cp\u003eThe DL380 Gen10 is the HPE-shop equivalent of the Dell R740 in tier and target workloads: 2U, dual-socket, broad chassis flexibility (LFF and multiple SFF densities), strong I\/O envelope, iLO 5 management. The Gen10 was widely deployed across mid-tier enterprise from 2017 through 2022 as the VMware standard, the database tier workhorse, and the vSAN hybrid cluster node of choice. In 2026, the Gen10 platform is widely deployed with excellent parts availability and deep institutional operating knowledge. For dev\/test infrastructure, expanding existing Gen10 estates, vSAN OSA clusters on vSphere 6.x or 7.x, lab environments, and budget-conscious production where current-gen Sapphire\/Emerald Rapids genuinely is not required, the DL380 Gen10 16-Bay is the cost-correct call.\u003c\/p\u003e\u003cp\u003eThe 16-Bay 2.5\" is the canonical DL380 Gen10 chassis at Wholesale Servers because it is the storage-flexibility anchor of the family: enough bays for vSAN hybrid OSA with proper cache-to-capacity ratios, enough bays for all-SSD database storage tiers, enough bays for mixed SSD\/HDD tiered storage, and small enough to remain economical per-node for scale-out cluster designs. The 24-Bay 2.5\" sibling adds bay count for vSAN all-flash multi-disk-group architectures and Ceph OSD nodes; the 12-Bay 3.5\" LFF sibling shifts the storage profile to bulk capacity for NAS, backup, and object storage. We deploy the 16-Bay 2.5\" most often as VMware vSAN hybrid nodes, SQL Server and PostgreSQL database tiers with SSD storage, virtualization hosts with substantial local storage, and converged infrastructure workloads where the storage-to-compute ratio fits within 16 SFF bays.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10 uses Intel's Purley platform with the LGA 3647 socket and supports both 1st Generation Xeon Scalable (Skylake-SP, 14 nm, 2017) and 2nd Generation Xeon Scalable (Cascade Lake-SP, 14 nm refresh, 2019). Both generations are drop-in compatible in the same socket; a Gen10 originally shipped with Skylake silicon can be upgraded to Cascade Lake without a motherboard swap. The 2nd gen Cascade Lake is the typical refurbished-market silicon today and is what we usually recommend.\u003c\/p\u003e\u003cp\u003eCPU ceiling on Cascade Lake reaches 28 cores per socket on the Xeon Platinum 8280 (205W TDP). The mainstream-deployed envelope is 16 to 24 cores per socket on Gold 6230, 6240, 6248, 6252 SKUs. Memory speed depends on processor SKU: Gold 6200 and 5222 reach DDR4-2933 at 1 DPC; remaining Gold 5200 series, Gold 6100, Gold 5100, and Silver 4100 series cap at DDR4-2666. AVX-512 is supported across the Xeon Scalable line; 6200-series and the 5222 support 2x 512-bit FMA units, while 5200-series (other than 5222), 5100, 6100, and Silver SKUs support 1x 512-bit FMA. This affects HPC-style FP-heavy throughput; for typical virtualization and database workloads, it is rarely the deciding factor.\u003c\/p\u003e\u003cp\u003eOur default recommendation for general-purpose virtualization is 2x Gold 6242 (16C \/ 32T at 2.8 GHz, 150W TDP, 22 MB cache) or 2x Gold 6248 (20C \/ 40T at 2.5 GHz, 150W TDP, 27.5 MB cache). For higher-density VDI or container workloads, 2x Gold 6230 (20C \/ 40T at 2.1 GHz) balances core count with thermal envelope. For SQL Server licensed by core, fewer faster cores work best: 2x Gold 6244 (8C \/ 16T at 3.6 GHz) or 2x Gold 6246 (12C \/ 24T at 3.3 GHz) deliver clock speed at lower license counts.\u003c\/p\u003e\u003ch2\u003eMemory\u003c\/h2\u003e\u003cp\u003e24 DDR4 DIMM slots, twelve per CPU, six channels per CPU at 2 DPC. Mainstream maximum is 1.5 TB dual-socket with 64 GB RDIMMs (24 x 64 GB). Higher capacity is achievable with LRDIMMs: 128 GB LRDIMM x 24 = 3 TB dual-socket. NVDIMM-N is supported on the DL380 Gen10 but is restricted to 1st Generation Xeon Scalable (Skylake) only; if your workload needs NVDIMM-N, verify the CPU SKU. Intel Optane Persistent Memory 100-series (Apache Pass) is supported with Cascade Lake (2nd Gen Xeon Scalable) on M-suffix CPU SKUs (e.g., Gold 6240M, 6242M, 8260M); these are required for the high per-socket memory ceilings (4.5 TB per socket with L-series, 2 TB per socket with M-series).\u003c\/p\u003e\u003cp\u003eHPE memory rules: DIMMs must be installed in even quantities for balanced operation. Mixing of RDIMM and LRDIMM is not supported in the same configuration. HPE DDR4 Smart Memory is required to achieve rated speeds; third-party DIMMs will operate at reduced speed even if compatible. We populate memory in matched sets of 12 (one per channel per CPU, balanced across both sockets) for production deployments. Asymmetric configurations work for limited-budget builds but trade off bandwidth.\u003c\/p\u003e\u003cp\u003eFor VMware vSAN hybrid nodes, 256 GB to 512 GB per node is the practical range; vSAN 7.x with 16 SFF bays at 4-6 disk groups uses memory aggressively for caching and metadata. For database workloads, plan for 75-90% of working set in memory plus headroom; SQL Server and PostgreSQL benefit significantly from large buffer pools.\u003c\/p\u003e\u003ch2\u003eStorage\u003c\/h2\u003e\u003cp\u003eThe 16-Bay 2.5\" SFF configuration provides sixteen front-mounted 2.5\" hot-swap bays accepting SAS, SATA, and (with the Universal Media Bay option and Premium SFF backplane) up to 2 NVMe drives via the optional bays. Native NVMe in the 16-Bay configuration is limited compared to Gen10+ or 11; for substantial NVMe storage, the platform of record is HPE ProLiant DL380 Gen10 Plus or DL380 Gen11 with the appropriate NVMe backplane.\u003c\/p\u003e\u003cp\u003eCommon 16-Bay storage configurations we deploy:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eVMware vSAN hybrid OSA (vSphere 6.x \/ 7.x):\u003c\/strong\u003e 2 to 4 SAS SSDs (1.6 TB to 3.84 TB write-intensive) for cache tier, 12 to 14 NL-SAS HDDs (4 TB to 16 TB) for capacity tier. The classic Gen10 vSAN hybrid deployment, fully supported on vSphere 7.x, proven to scale across hundreds of hybrid OSA clusters. vSAN 8.x ESA is NOT supported on Gen10; for ESA you need Gen10+ or Gen11.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAll-SAS SSD performance storage:\u003c\/strong\u003e 16 x SAS SSDs at RAID 10 yields 8 drives of usable capacity with strong write performance and predictable rebuild times. The typical fit is SQL Server, Oracle, PostgreSQL, MySQL, and other relational database storage tiers where NVMe latency is not the binding constraint and SAS endurance and dual-port redundancy matter.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMixed SSD + HDD tiered storage:\u003c\/strong\u003e 4 to 6 SAS SSDs for hot data alongside 10 to 12 NL-SAS HDDs for bulk; cost-effective tiering for general file serving, application data, and modest databases.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003evSAN all-flash OSA (smaller clusters):\u003c\/strong\u003e 4 SAS SSD cache + 12 SAS SSD capacity. For larger vSAN all-flash with multiple disk groups per node, the 24-Bay 2.5\" sibling provides better cluster economics.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eBoot configuration: HPE M.2 boot via the optional M.2 enablement kit installs 1 or 2 M.2 SATA SSDs in a dedicated bay outside the 16 data bays. We strongly recommend M.2 boot rather than consuming a data bay for OS. The HPE NS204i-p (Gen10+) NVMe boot device is not native to Gen10 (it's a Gen10+ option); on Gen10 the SATA M.2 enablement kit is the boot path of record.\u003c\/p\u003e\u003ch2\u003eSmart Array Controllers (HPE RAID)\u003c\/h2\u003e\u003cp\u003eHPE's Gen10 Smart Array lineup replaces the Dell PERC analogy: same role, different naming. The relevant controllers for DL380 Gen10 16-Bay are:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a (4 GB FBWC):\u003c\/strong\u003e Flexible Smart Array slot, dual-controller, supports all 16 internal SFF bays plus external SAS expansion. The default recommendation for hardware-RAID production workloads with substantial write activity. Flash-backed write cache survives power loss. FBWC battery is a wear item; check status on used inventory.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P408i-a (2 GB FBWC):\u003c\/strong\u003e Lower-cache version of the P816i-a, internal-only. Adequate for many production workloads without the cost of the 4 GB cache.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-a (HBA mode):\u003c\/strong\u003e 8-port HBA, no on-controller RAID. Required for vSAN OSA, Ceph, ZFS pass-through, and any software-defined storage stack that requires direct disk visibility. The HPE equivalent of Dell's HBA330.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array S100i (software RAID):\u003c\/strong\u003e SATA-only software RAID via Intel VROC-equivalent. Acceptable for boot drives in M.2 slots; we do not deploy it on production data arrays.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eOur default for production virtualization with hardware RAID is the P816i-a; the FBWC and 4 GB cache pay off on mixed workloads. For vSAN OSA the E208i-a is mandatory; vSAN requires direct disk access. For Ceph and ZFS the E208i-a is similarly the right choice.\u003c\/p\u003e\u003ch2\u003eNetworking\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10 ships with an embedded 4 x 1 GbE NIC on most BTO configurations (HPE 331i \/ Broadcom BCM5719). Higher-performance networking is delivered via the HPE FlexibleLOM slot, which accepts a wide range of LOM adapters: 4 x 1 GbE, 2 x 10 GbE BASE-T, 2 x 10 GbE SFP+, 2 x 25 GbE SFP28, and 2 x 100 GbE on appropriate FlexibleLOM cards. The FlexibleLOM does NOT consume a PCIe slot; it occupies a dedicated mezzanine slot on the riser. This is the HPE equivalent of Dell's rNDC and serves the same purpose: dense networking without sacrificing PCIe expansion.\u003c\/p\u003e\u003cp\u003eFor 10 GbE deployments, the typical FlexibleLOM is the HPE 562FLR-SFP+ (Intel X710, 2 x 10 GbE SFP+) or 562FLR-T (Intel X550, 2 x 10 GbE BASE-T). For 25 GbE the 631FLR-SFP28 (Mellanox ConnectX-4 LX) is standard. For VMware deployments, verify driver support against the FlexibleLOM you order; older Mellanox FlexibleLOMs have specific ESXi support matrices.\u003c\/p\u003e\u003cp\u003eFor dense networking beyond the FlexibleLOM, add-in PCIe NICs occupy the PCIe slots described below. 4 x 10 GbE on a single FlexibleLOM is achievable; for 4 x 25 GbE plan for a FlexibleLOM plus a single PCIe NIC.\u003c\/p\u003e\u003ch2\u003ePCIe Expansion\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10 supports up to 8 PCIe Gen3 slots distributed across three risers. Standard riser is the Primary Riser (slots 1-3); optional Secondary Riser (slots 4-6) requires a second CPU; optional Tertiary Riser (slots 7-8) can also be configured. Slot widths depend on the riser SKU chosen: HPE offers multiple riser SKUs from the standard x8 \/ x16 \/ x8 to the GPU-capable x16 \/ x16 \/ x16 configurations.\u003c\/p\u003e\u003cp\u003ePCIe Gen3 is a meaningful limitation versus Gen10+ (PCIe Gen4) and Gen11 (PCIe Gen5). For NVMe SSDs operating at Gen4 link speeds, Gen3 caps the link to half-bandwidth; for 100 GbE NICs, Gen3 x8 is at the bandwidth ceiling. For most virtualization, database, and general-purpose workloads, PCIe Gen3 remains adequate; for AI inference with high-bandwidth GPUs or Gen4 NVMe-bound storage, this is where Gen10 hits its ceiling.\u003c\/p\u003e\u003cp\u003eGPU support: the DL380 Gen10 with the x16 \/ x16 \/ x16 Primary and Secondary risers (HPE P14374-B21 and P14373-B21) supports up to 7 NVIDIA T4 16 GB single-width 70W GPUs, or 6 T4s balanced across both processors. Double-width GPUs are limited to 3 cards per platform on appropriate riser configurations; the platform supports up to 3 x 300W double-width accelerators (V100, RTX 6000, A30, A40) in flagship riser SKUs. The Gen10's GPU envelope is genuinely strong for a 2U rack; the limit is PCIe Gen3 bandwidth more than power or physical slots.\u003c\/p\u003e\u003ch2\u003ePower Supplies\u003c\/h2\u003e\u003cp\u003eHPE Flex Slot power supplies, hot-plug, redundant. Wattage options span 500W to 1600W in 94% Platinum and Titanium efficiency tiers. Dual PSU is standard for production deployments.\u003c\/p\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eConfiguration\u003c\/th\u003e\n\u003cth\u003ePSU Recommendation\u003c\/th\u003e\n\u003cth\u003eEst. Peak Draw\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eLight (2x Silver 4214, 128 GB, 4 SAS SSDs, P408i-a)\u003c\/td\u003e\n\u003ctd\u003e2 x 500W Platinum (hot-plug redundant)\u003c\/td\u003e\n\u003ctd\u003e~280W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBalanced (2x Gold 6242, 384 GB, 12 SAS SSDs + 4 NL-SAS, P816i-a)\u003c\/td\u003e\n\u003ctd\u003e2 x 800W Platinum\u003c\/td\u003e\n\u003ctd\u003e~480W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eHeavy (2x Gold 6248, 768 GB, 16 SAS SSDs vSAN AF, P816i-a, 2 x 25 GbE)\u003c\/td\u003e\n\u003ctd\u003e2 x 1000W Platinum\u003c\/td\u003e\n\u003ctd\u003e~640W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMaximum (2x Platinum 8280, 1.5 TB, 16 SAS SSDs, 3 x V100 GPUs)\u003c\/td\u003e\n\u003ctd\u003e2 x 1600W Titanium\u003c\/td\u003e\n\u003ctd\u003e~1450W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003cp\u003eFor most 16-Bay 2.5\" deployments without GPUs, 2 x 800W Platinum is the recommended PSU. GPU configurations require 2 x 1600W Titanium. Single-PSU configurations are technically supported but we do not deploy single-PSU in production.\u003c\/p\u003e\u003ch2\u003eManagement and Security: iLO 5\u003c\/h2\u003e\u003cp\u003eHPE iLO 5 is the integrated remote management controller on Gen10, the HPE counterpart to Dell iDRAC9. iLO 5 brought a major security upgrade over iLO 4: Silicon Root of Trust validates firmware integrity at the hardware level during boot, preventing firmware-level attacks via a hardware-anchored chain of trust. This is a meaningful security feature for production environments; it is the HPE equivalent of Dell's iDRAC9 System Lockdown \/ Silicon-Based Security on 14th gen.\u003c\/p\u003e\u003cp\u003eiLO 5 supports HTML5 remote console (no Java required), Redfish REST API, IPMI 2.0, virtual media via web upload, remote KVM, full server power and thermal telemetry, and integration with HPE OneView for fleet management. Standard iLO 5 includes remote console and basic management; iLO Advanced license unlocks virtual media via integrated remote console, directory services integration, and several enterprise features. Most refurbished Gen10 units arrive with iLO Standard; we can include iLO Advanced licenses on request at quote.\u003c\/p\u003e\u003cp\u003eFor VMware shops, iLO 5 integrates cleanly with vCenter Server via HPE OneView for vCenter. For broad fleet management, HPE OneView 5.x or 6.x is the management plane; OneView 8.x and InfoSight integration are also available.\u003c\/p\u003e\u003ch2\u003ePhysical Specs and Platform Notes\u003c\/h2\u003e\u003cp\u003e2U rack, approximately 27.83\" deep (708 mm). Weight 73.6 lbs (33.4 kg) at typical fully-loaded configuration. Standard EIA 19\" rack mount via HPE Easy Install rail kit (679368-001 \/ 728437-001 for SFF, 679365-001 \/ 737412-001 for variant configurations). Rail kits are not included with bare server purchase; verify at quote time.\u003c\/p\u003e\u003cp\u003eChassis is welded and not field-convertible between LFF and SFF; the 16-Bay 2.5\" backplane is fixed at the chassis level. To convert between bay counts or form factors, the chassis itself must be replaced (a separate chassis SKU).\u003c\/p\u003e\u003cp\u003eCooling: six hot-plug fans in the standard configuration; high-temperature fans optional for sustained 35°C ambient deployments. Acoustic envelope is typical 2U rack server, not designed for office use.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10 16-Bay 2.5\" is HPE's mid-decade 2U workhorse and remains a workhorse: widely deployed, well-understood, with mature firmware and broad parts availability. For HPE-standardized shops running VMware vSphere 7.x with vSAN hybrid OSA, the DL380 Gen10 16-Bay is the cost-correct platform when current-generation is genuinely not required. For database tiers with all-SAS SSD storage where NVMe latency is not the binding constraint, this platform delivers strong performance at meaningfully lower acquisition cost than Gen10+ or Gen11.\u003c\/p\u003e\u003cp\u003eWhere the platform falls short: vSAN 8.x ESA is not supported (no native NVMe backplane on 16-Bay; ESA requires Gen10+ or Gen11 with NVMe). PCIe Gen3 limits NVMe and high-speed networking ceilings. The platform's CPU support tops out at Cascade Lake (28 cores per socket maximum); modern Sapphire Rapids and Emerald Rapids workloads with high core counts and DDR5 bandwidth needs are outside the platform's envelope. HPE official support is winding down for Gen10; OneView and InfoSight continue, but HPE TAC engagement for Gen10-specific issues has narrowing horizons.\u003c\/p\u003e\u003cp\u003evs DL360 Gen10 1U pair-partner: the DL360 is the 1U sibling with the same processor lineup, memory architecture, iLO 5, and Smart Array compatibility. The choice is form factor and storage profile: DL360 Gen10 8-Bay or 10-Bay 2.5\" for dense 1U deployments where storage requirements stay below 10 bays; DL380 Gen10 16-Bay where the storage-to-compute ratio needs the larger chassis.\u003c\/p\u003e\u003cp\u003evs DL380 Gen10+ (Plus): the Gen10+ moves to 3rd Gen Xeon Scalable (Ice Lake, LGA 4189), PCIe Gen4, DDR4-3200, and native NVMe backplane options. For greenfield deployments running production beyond 2028, or for vSAN ESA, the Gen10+ is the right platform. For existing Gen10 estates or shorter lifecycle builds, the Gen10 economics are compelling.\u003c\/p\u003e\u003cp\u003evs Dell PowerEdge R740 16-Bay 2.5\" (Dell tier-equivalent): same architectural tier, same Skylake\/Cascade Lake processor generation, same DDR4 generation. The Dell R740 has 24 DIMM slots versus Gen10's 24 DIMM slots (parity), Dell PERC vs HPE Smart Array (parity in function, different naming), iDRAC9 vs iLO 5 (parity in capability). The choice between R740 and DL380 Gen10 is typically driven by which vendor the shop is standardized on, not by capability deltas.\u003c\/p\u003e\u003cp\u003eBottom line: For HPE-standardized environments where the workload fits the platform envelope, the DL380 Gen10 16-Bay 2.5\" delivers proven enterprise capability at refurbished-market economics. We deploy it most often as VMware vSAN hybrid OSA nodes, SQL Server database tiers with SAS SSD storage, and general-purpose 2U virtualization hosts where the 16-bay storage profile fits.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eExcels at ✅\u003c\/th\u003e\n\u003cth\u003eWhere to look elsewhere ❌\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eVMware vSAN hybrid OSA on vSphere 6.x \/ 7.x\u003c\/td\u003e\n\u003ctd\u003evSAN 8.x ESA (use DL380 Gen10+ or Gen11)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eSQL Server, Oracle, PostgreSQL with SAS SSD storage\u003c\/td\u003e\n\u003ctd\u003eNVMe-latency-bound databases (use DL380 Gen10+)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eGeneral-purpose 2U virtualization for HPE shops\u003c\/td\u003e\n\u003ctd\u003eWorkloads requiring DDR5 or Sapphire Rapids cores\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMixed SSD + HDD tiered storage in 16 SFF bays\u003c\/td\u003e\n\u003ctd\u003eMore than 16 SFF bays needed (use 24-Bay sibling)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eGPU inference with up to 6 NVIDIA T4 cards\u003c\/td\u003e\n\u003ctd\u003eLFF bulk capacity workloads (use 12-Bay LFF sibling)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eDev\/test, lab, training infrastructure at low cost\u003c\/td\u003e\n\u003ctd\u003eProduction workloads running beyond 2028 (consider Gen10+ or Gen11)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eExpansion of existing Gen10 estates\u003c\/td\u003e\n\u003ctd\u003evSAN with all-NVMe disk groups (use Gen10+ with NVMe backplane)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe Gen3 only.\u003c\/strong\u003e 48 lanes per CPU at Gen3 speeds. Gen4 NVMe SSDs operate at half-link bandwidth; 100 GbE NICs at x8 are at the Gen3 ceiling. For Gen4-bound workloads, Gen10+ is the platform of record.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNo native NVMe backplane on 16-Bay.\u003c\/strong\u003e NVMe in Gen10 16-Bay is via Universal Media Bay (up to 2 NVMe bays) or PCIe AIC; not native 16-bay NVMe. For substantial NVMe storage, the platform is Gen10+ or Gen11 with appropriate backplane.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003evSAN 8.x ESA not supported.\u003c\/strong\u003e vSAN OSA on vSphere 7.x is fully supported. ESA requires NVMe storage and is platform-restricted to Gen10+ or newer with NVMe backplane.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDDR4 generation, 2933 MT\/s ceiling.\u003c\/strong\u003e Gold 6200-series and 5222 reach 2933 at 1 DPC; the rest of the lineup caps at 2666. Modern bandwidth-heavy workloads benefit from DDR5; for those, Gen11 is the platform.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCPU ceiling at Cascade Lake 28 cores per socket.\u003c\/strong\u003e Workloads benefiting from 32, 40, 48, or 64 cores per socket (Ice Lake, Sapphire Rapids, Emerald Rapids) are outside the platform's envelope.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNVDIMM-N restricted to Skylake (1st gen Xeon Scalable).\u003c\/strong\u003e Cascade Lake CPUs require Optane PMem 100-series (Apache Pass) on M-suffix SKUs for persistent memory; NVDIMM-N is a Skylake-only path.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMixed RDIMM\/LRDIMM not supported.\u003c\/strong\u003e The platform requires homogeneous DIMM technology; mixing in the same configuration is unsupported.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eHPE official support narrowing.\u003c\/strong\u003e Gen10 OneView and InfoSight integration continues, but HPE TAC engagement for Gen10-specific issues has decreasing horizons. Critical production workloads on multi-year horizons should evaluate the upgrade path.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eiLO Advanced license typically not included.\u003c\/strong\u003e Most refurbished Gen10 ship with iLO Standard. iLO Advanced (for integrated remote console virtual media, directory services, and several enterprise features) is licensed separately. We can include iLO Advanced licenses at quote.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eFBWC battery is a wear item.\u003c\/strong\u003e Smart Array P816i-a and P408i-a use flash-backed write cache with a capacitor pack. The capacitor is a wear item with a service life of approximately 5 years; refurbished units may have aged capacitors. We test FBWC health during burn-in and replace when out of spec.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWelded chassis.\u003c\/strong\u003e Bay configuration is fixed at the chassis level. Converting between 8-bay, 16-bay, 24-bay SFF, or 12-bay LFF requires chassis replacement, not field reconfiguration.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eHPE-only parts and firmware.\u003c\/strong\u003e Gen10 firmware updates require HPE Service Pack for ProLiant (SPP) and an active HPE account in most cases. Third-party drives and DIMMs may operate at reduced speed or with warning indicators in iLO 5.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eGeneration Context\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen9 is the immediate predecessor: same 2U tier on the Intel Grantley platform (E5-2600 v3 Haswell \/ v4 Broadwell), DDR4-2400, iLO 4. The Gen9 is meaningfully older and operates at lower memory bandwidth, PCIe Gen3 (same as Gen10), and lacks Silicon Root of Trust. For workloads sized to Gen9 cost economics, the DL380 Gen9 16-Bay or 24-Bay variants at Wholesale Servers are options; the Gen10 brings Skylake\/Cascade Lake compute, iLO 5 security, and broader OS support.\u003c\/p\u003e\u003cp\u003eThe DL380 Gen10 Plus is the successor: same 2U chassis form factor, but new motherboard architecture with the LGA 4189 socket for 3rd Generation Xeon Scalable (Ice Lake, 10 nm). The Gen10 Plus brings PCIe Gen4, DDR4-3200, native NVMe backplane options, and the Silicon Root of Trust security model carried forward. For greenfield production with extended lifecycle, the Gen10 Plus is typically the right call. For cost-primary deployments fitting the Gen10 envelope, the Gen10 saves meaningful acquisition cost.\u003c\/p\u003e\u003cp\u003eThe DL380 Gen11 is the current-generation: 4th Gen Sapphire Rapids and 5th Gen Emerald Rapids Xeon Scalable, DDR5, PCIe Gen5, iLO 6, completely new platform. For workloads requiring current-gen capability (DDR5 bandwidth, CXL, PCIe Gen5 NVMe, very high core counts), the Gen11 is the platform of record.\u003c\/p\u003e\u003cp\u003eCross-family pair-partner (1U sibling): The HPE ProLiant DL360 Gen10 is the 1U platform pair-partner, same processor lineup, same memory architecture, same iLO 5 and Smart Array compatibility, in the denser 1U form factor with fewer drive bays (4 LFF, 8 SFF, or 10 SFF). For dense rack deployments where 16 SFF bays per node is excess, the DL360 Gen10 is the right call.\u003c\/p\u003e\u003cp\u003eCross-vendor tier-equivalent: Dell PowerEdge R740 is the architectural counterpart in the Dell catalog: same Purley platform, same processor support, same DDR4 generation, same tier positioning. Choice between R740 and DL380 Gen10 is typically driven by vendor standardization. Both are available at Wholesale Servers; if your shop is mixed-vendor, we can quote both for comparison.\u003c\/p\u003e\u003cp\u003eFamily siblings (DL380 Gen10):\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003e24-Bay 2.5\" SFF:\u003c\/strong\u003e Higher-density SFF for vSAN all-flash multi-disk-group nodes, Ceph OSD clusters, and large SAS SSD storage tiers where 24 bays per node improves cluster economics.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e12-Bay 3.5\" LFF:\u003c\/strong\u003e Bulk capacity for NAS, backup, archive, and object storage. Up to 240 TB raw with 20 TB NL-SAS drives.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eRequest a Quote\u003c\/h2\u003e\u003cp\u003eTell us your workload, vSAN or storage design (if applicable), drive type and quantity, memory target, networking requirements, and unit quantity. We respond within 24 hours. Volume pricing applies at 5 units and above. Every Wholesale Servers DL380 Gen10 ships after a 12+ hour burn-in test covering every PCIe slot, every memory channel, and every drive bay. Standard 180-day warranty included; 1-Year, 2-Year, and 3-Year Premium warranty options available. Call 1-800-778-1545 or use the quote form on this page.\u003c\/p\u003e\u003cp\u003eIf your deployment has a 3+ year production horizon, we will also quote the DL380 Gen11 or Gen10 Plus for comparison on request.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951241650375,"sku":"BP-013609","price":804.68,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-gen10-16-bay-25-drives-874519.png?v=1765539623"},{"product_id":"hpe-dl380-g10-2-5-24-bay-chassis","title":"HPE ProLiant DL380 Gen10 24-Bay 2.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL380 Gen10 24-Bay 2.5\" is the maximum SFF density configuration of HPE's 2U dual-socket Gen10 platform: twenty-four 2.5\" SAS\/SATA hot-swap bays on the same Purley dual-socket motherboard, same memory architecture, same iLO 5 management, and same Smart Array RAID family as the 16-Bay canonical. This page covers the 24-Bay storage architecture and when this chassis is the right call versus the 16-Bay 2.5\" canonical or the 12-Bay 3.5\" LFF sibling.\u003c\/p\u003e\u003cp\u003eFor the full platform-fact story (processors, memory architecture, FlexibleLOM networking, PCIe expansion, iLO 5 management, Smart Array controllers, power supplies, physical specs), see the \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\" canonical page\u003c\/a\u003e. Everything documented there applies to this 24-Bay variant; this page focuses on what's different about the 24-bay chassis and the storage-design implications that follow from the higher bay count.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhat's Different About This Chassis\u003c\/h2\u003e\u003cp\u003eThe 24-Bay 2.5\" is the storage-flagship variant of the DL380 Gen10 family. Three things define it relative to the 16-Bay canonical:\u003c\/p\u003e\u003col\u003e\n\u003cli\u003e\n\u003cstrong\u003eEight additional SFF bays.\u003c\/strong\u003e Twenty-four front-mounted 2.5\" hot-swap bays versus sixteen on the canonical, with no change to the memory, processor, or PCIe envelope. The chassis is the same external dimensions; the additional bays come from the dense backplane configuration (Box 1, Box 2, and Box 3 each populated with 8 SFF bays).\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCluster-economics workloads.\u003c\/strong\u003e The 24-bay configuration is sized for vSAN all-flash with multiple disk groups per node, Ceph OSD nodes where per-node OSD count drives cluster economics, and SAS SSD database tiers requiring substantial local storage. These workloads benefit from the additional bays in ways that 16-bay configurations cannot accommodate.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSame Gen10 platform ceilings.\u003c\/strong\u003e The 24-Bay does not unlock additional capability beyond storage: same PCIe Gen3, same DDR4-2933 ceiling, same Cascade Lake processor lineup, same iLO 5, same Smart Array P816i-a \/ P408i-a \/ E208i-a options. Workloads that need PCIe Gen4, DDR4-3200, or Ice Lake compute should evaluate the DL380 Gen10 Plus, not the 24-Bay Gen10.\u003c\/li\u003e\n\u003c\/ol\u003e\u003chr\u003e\u003ch2\u003eStorage Architecture\u003c\/h2\u003e\u003cp\u003eTwenty-four 2.5\" SAS\/SATA hot-swap bays in three Box configurations (Box 1, Box 2, Box 3 at 8 bays each). The Smart Array P816i-a (4 GB FBWC) is the natural RAID controller for hardware-RAID configurations across all 24 bays; the E208i-a HBA is the natural controller for vSAN OSA, Ceph, and ZFS deployments requiring direct disk access.\u003c\/p\u003e\u003cp\u003eCommon 24-Bay configurations we deploy:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eVMware vSAN all-flash OSA with multiple disk groups (vSphere 6.x \/ 7.x):\u003c\/strong\u003e Up to 5 disk groups per node, each with 1 SSD cache + up to 4 SSD capacity drives. 24 bays supports 5 disk groups (5 cache + 19 capacity) or 4 disk groups (4 cache + 20 capacity). Multiple disk groups per node increases vSAN storage parallelism linearly; this is the canonical Gen10 vSAN all-flash node configuration. vSAN 8.x ESA is NOT supported on Gen10; for ESA the DL380 Gen10 Plus with NVMe backplane is the platform.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCeph OSD nodes (24 OSDs per node):\u003c\/strong\u003e With the E208i-a HBA in pass-through mode, each of the 24 bays becomes an independent OSD. The DL380 Gen10 24-Bay is widely deployed as Ceph OSD nodes in Red Hat Ceph Storage and SUSE Enterprise Storage clusters; the high OSD-per-node count and the secondary-market acquisition cost make compelling cluster economics. Plan memory at 6 GB per OSD plus 16 GB overhead (192 GB per node typical) and dedicated 25 GbE or 100 GbE cluster networking.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAll-SAS SSD database storage:\u003c\/strong\u003e 24 x SAS SSDs at RAID 10 yields 12 drives of usable capacity. With 3.84 TB SAS SSDs, that's 46 TB usable; with 7.68 TB, 92 TB usable. The typical fit is large SQL Server, Oracle, or PostgreSQL instances requiring substantial local SSD capacity with high endurance and dual-port redundancy.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eTiered SSD + HDD at 24-bay density:\u003c\/strong\u003e 6 to 8 SAS SSDs for hot tier (cache or storage tier) alongside 16 to 18 NL-SAS HDDs for bulk capacity. With 16 TB NL-SAS HDDs and 7.68 TB SAS SSDs, this yields substantial tiered storage in a single 2U chassis: roughly 60 TB SSD raw and 280 TB HDD raw for a combined 340 TB before RAID overhead.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eVeeam repository \/ backup target node:\u003c\/strong\u003e 24 NL-SAS HDDs at RAID 60 (two RAID 6 sets striped) provides high-capacity backup landing with two-drive fault tolerance per set. The Gen10's bandwidth envelope is well-matched to Veeam's typical backup throughput targets.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThe 24-bay storage configuration is where the Gen10 platform's PCIe Gen3 limitation becomes meaningful: aggregated throughput from 24 high-performance SAS SSDs can saturate Gen3 lanes to the Smart Array controller in some workloads. For workloads where this is the binding constraint, the DL380 Gen10 Plus with PCIe Gen4 is the upgrade path.\u003c\/p\u003e\u003ch2\u003eRAID and Controller Guidance\u003c\/h2\u003e\u003cp\u003eRAID strategy at 24-bay scale matters more than at 16-bay because rebuild times and parity-group fault tolerance scale with array size:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 6 mandatory for NL-SAS HDD arrays.\u003c\/strong\u003e Rebuild times on 16-20 TB NL-SAS drives at 24-bay density commonly exceed 36 hours; two-drive fault tolerance is non-negotiable. Never RAID 5 at this drive count and capacity.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 10 for SAS SSDs.\u003c\/strong\u003e Fast rebuild times, predictable write performance, fault tolerance per mirrored pair. Half the usable capacity, but the operational characteristics are correct for production database storage.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 60 for backup targets.\u003c\/strong\u003e Two RAID 6 sets striped: 12 + 12 across 24 drives. Survives two drive failures per set; rebuilds happen in parallel per set; aggregate throughput meets Veeam-class backup repository requirements.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a (4 GB FBWC) is the production hardware-RAID default.\u003c\/strong\u003e The 4 GB write cache pays off at 24-bay scale where Smart Array battery-backed write reordering meaningfully improves random write performance. FBWC battery health is a wear item; we verify at burn-in.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-a HBA mode for software-defined storage.\u003c\/strong\u003e vSAN, Ceph, and ZFS require direct disk access; the E208i-a is the supported HBA for these workloads on Gen10.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eBoot configuration: HPE M.2 enablement kit installs 1 or 2 M.2 SATA SSDs outside the 24 data bays. We strongly recommend this rather than consuming a data bay for OS, especially at 24-bay configurations where every data bay contributes to cluster or capacity economics.\u003c\/p\u003e\u003ch2\u003eMemory Sizing for 24-Bay Workloads\u003c\/h2\u003e\u003cp\u003eThe 24-Bay platform's storage workloads typically require more memory than general-purpose 16-Bay configurations:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003evSAN all-flash, 5 disk groups per node:\u003c\/strong\u003e 384 GB to 768 GB per node. vSAN memory overhead grows with disk group count and capacity drive count; 5-disk-group nodes are at the high end of vSAN memory consumption.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCeph OSD nodes, 24 OSDs:\u003c\/strong\u003e 192 GB to 256 GB per node. Roughly 6 GB per OSD plus daemon overhead; some workloads benefit from 8 GB per OSD on BlueStore deployments with substantial capacity drives.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAll-SAS SSD database, 12-drive RAID 10:\u003c\/strong\u003e Memory sized to the workload, not the storage. SQL Server with 92 TB usable benefits from 768 GB to 1.5 TB depending on working-set size; PostgreSQL similar.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eVeeam repository node:\u003c\/strong\u003e 128 GB to 256 GB. Veeam repository memory scales with concurrent backup jobs and ReFS \/ XFS cache requirements; 128 GB is the practical minimum for serious repository nodes.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eHPE memory rules from the 16-Bay canonical apply identically: DIMMs in even quantities, no RDIMM\/LRDIMM mixing, HPE DDR4 Smart Memory required for rated speeds, matched sets of 12 for balanced production deployment.\u003c\/p\u003e\u003ch2\u003ePower Sizing for 24-Bay Workloads\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eConfiguration\u003c\/th\u003e\n\u003cth\u003ePSU Recommendation\u003c\/th\u003e\n\u003cth\u003eEst. Peak Draw\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBalanced (2x Gold 6242, 384 GB, 24 SAS SSDs, P816i-a)\u003c\/td\u003e\n\u003ctd\u003e2 x 800W Platinum (hot-plug redundant)\u003c\/td\u003e\n\u003ctd\u003e~580W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eHeavy (2x Gold 6248, 768 GB, 24 SAS SSDs vSAN AF, P816i-a, 2 x 25 GbE)\u003c\/td\u003e\n\u003ctd\u003e2 x 1000W Platinum\u003c\/td\u003e\n\u003ctd\u003e~740W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eStorage-heavy (2x Gold 6230, 256 GB, 24 NL-SAS HDDs RAID 60, P816i-a)\u003c\/td\u003e\n\u003ctd\u003e2 x 800W Platinum\u003c\/td\u003e\n\u003ctd\u003e~520W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMaximum (2x Platinum 8280, 1 TB, 24 SAS SSDs, FlexibleLOM, 2 PCIe NICs)\u003c\/td\u003e\n\u003ctd\u003e2 x 1600W Titanium\u003c\/td\u003e\n\u003ctd\u003e~1100W\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003cp\u003eFor typical 24-bay deployments, 2 x 1000W Platinum is the recommended PSU. Heavily-populated all-SSD configurations with 2 x 25 GbE networking can push toward 800W steady-state; 1000W gives headroom for transient peaks. Single-PSU configurations are not deployed in production at this storage density.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhen to Pick a Different Chassis\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003e16 SFF bays sufficient:\u003c\/strong\u003e The \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\" canonical\u003c\/a\u003e is meaningfully lower-cost per node and is the right call when storage requirements stay below 16 SFF bays. vSAN hybrid OSA with 1-2 disk groups, all-SSD database tiers with 8-12 drives, and general-purpose 2U virtualization fit comfortably in the 16-bay envelope.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eLFF capacity drives needed:\u003c\/strong\u003e The \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eDL380 Gen10 12-Bay 3.5\" LFF sibling\u003c\/a\u003e is the right chassis for bulk NAS, backup, archive, and object storage workloads where 7,200 RPM NL-SAS capacity drives at 16 TB to 20 TB each deliver the storage economics.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003evSAN 8.x ESA target:\u003c\/strong\u003e The DL380 Gen10 platform (any chassis) does not support vSAN ESA. For ESA, the DL380 Gen10 Plus or Gen11 with NVMe backplane is the platform.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNVMe-bound workloads:\u003c\/strong\u003e The 24-Bay 2.5\" Gen10 SAS backplane does not support native NVMe across all 24 bays. For NVMe storage tiers, evaluate the DL380 Gen10 Plus 24-Bay NVMe configurations.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe Gen4 NICs or accelerators required:\u003c\/strong\u003e Gen10 is PCIe Gen3 only. 100 GbE NICs operate at the Gen3 x8 ceiling; AI accelerators expecting Gen4 bandwidth are bottlenecked. The DL380 Gen10 Plus is the upgrade.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e1U form factor:\u003c\/strong\u003e The DL360 Gen10 1U pair-partner is denser per rack U, with bay options up to 10 SFF. For dense 1U deployments where 24 bays per node is excessive, the DL360 Gen10 is the right form factor.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10 24-Bay 2.5\" is the storage-density specialist of the Gen10 family. For HPE-standardized shops building vSAN all-flash OSA clusters with multiple disk groups per node, Ceph OSD clusters with high per-node OSD count, or large SAS SSD database tiers, the 24-Bay 2.5\" is the right chassis. The economics are particularly compelling for Ceph deployments and Veeam repository nodes where per-node storage density drives total infrastructure cost.\u003c\/p\u003e\u003cp\u003eThe Gen10 platform constraints (PCIe Gen3, no native NVMe backplane, vSAN OSA only, Cascade Lake CPU ceiling) apply identically to the 24-Bay as to the 16-Bay canonical; the 24-Bay does not unlock new platform capability beyond storage. For workloads where those constraints are binding, the DL380 Gen10 Plus or Gen11 is the platform of record.\u003c\/p\u003e\u003cp\u003eFor storage-density workloads on Gen10's PCIe Gen3 envelope, the 24-Bay delivers production-proven capability at meaningfully lower acquisition cost than current-generation alternatives. We deploy it most often as vSAN all-flash OSA nodes with 4-5 disk groups, Ceph OSD nodes at 24 OSDs per node, and Veeam backup repository nodes at high NL-SAS capacity.\u003c\/p\u003e\u003cp\u003eBottom line: When 16 SFF bays per node is not enough and you can accept the Gen10 platform envelope, the 24-Bay 2.5\" delivers the storage density at proven enterprise quality. When you can fit in 16 bays, the 16-Bay canonical is the cost-correct call.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eExcels at ✅\u003c\/th\u003e\n\u003cth\u003eWhere to look elsewhere ❌\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003evSAN all-flash OSA with multiple disk groups per node\u003c\/td\u003e\n\u003ctd\u003evSAN 8.x ESA (use DL380 Gen10+ with NVMe)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eCeph OSD clusters at 24 OSDs per node\u003c\/td\u003e\n\u003ctd\u003e16 OSDs sufficient (16-Bay lower cost)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eLarge SAS SSD database storage tiers\u003c\/td\u003e\n\u003ctd\u003eNVMe-bound database tiers (use DL380 Gen10+)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eVeeam repository nodes with 24 NL-SAS HDDs\u003c\/td\u003e\n\u003ctd\u003eLFF capacity drives needed (use 12-Bay LFF)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eTiered SSD + HDD at high density in 2U\u003c\/td\u003e\n\u003ctd\u003eWorkloads bottlenecked on PCIe Gen3\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eExpansion of existing Gen10 vSAN estates\u003c\/td\u003e\n\u003ctd\u003eProduction greenfield with 3+ year horizon (consider Gen10+ or Gen11)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eReady to Configure\u003c\/h2\u003e\u003cp\u003eTell us your vSAN, Ceph, or backup design, drive type and quantity, memory target, networking requirements, and unit quantity. We respond within 24 hours. Volume pricing applies at 5 units and above. Every Wholesale Servers DL380 Gen10 24-Bay ships after a 12+ hour burn-in test covering every PCIe slot, every memory channel, and every one of the 24 drive bays. Standard 180-day warranty included; 1-Year, 2-Year, and 3-Year Premium warranty options available. Call 1-800-778-1545 or use the quote form on this page.\u003c\/p\u003e\u003cp\u003eIf your deployment has a 3+ year production horizon, we will also quote the DL380 Gen11 or Gen10 Plus 24-Bay for comparison on request.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951241683143,"sku":"BP-013610","price":653.46,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-g10-24-bay-25-drives-694439.png?v=1765539623"},{"product_id":"dl380-g9-2-5-24-bay-chassis","title":"HPE ProLiant DL380 Gen9 24-Bay 2.5\" Drives","description":"\u003cp\u003eThe refurbished HPE ProLiant DL380 Gen9 24-Bay 2.5\" is the maximum SFF density configuration in the DL380 Gen9 family - twenty-four 2.5\" hot-swap bays in the standard 2U chassis. It carries the same Intel Xeon E5-2600 v3 (Haswell-EP) or v4 (Broadwell-EP) dual-socket platform, the same 24 DDR4 DIMM slots and 3 TB memory ceiling, and the same iLO 4 management as the rest of the Gen9 line. What changes is the storage architecture: 24 SAS\/SATA SSDs or HDDs deliver substantial local capacity in a single 2U host, which makes the 24-Bay the right Gen9 platform for HCI nodes (vSAN, S2D, Nutanix on KVM), high-density VDI hosts, database hosts with local primary SSD storage, and any workload where maximum local SFF capacity in one dual-socket 2U chassis is the design driver.\u003c\/p\u003e\u003cp\u003eThis page focuses on what is specific to the 24-bay variant - when maximum SFF density is the right design, and the controller, RAID, NVMe, and power decisions that change at 24 SFF. For the shared platform vocabulary, the canonical is the \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units. The 24-bay configuration benefits from extra design discussion - controller sizing, RAID layout, NVMe planning, and power budget all matter more here than at lower bay counts.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhen 24 SFF Bays Is the Right Design\u003c\/h2\u003e\u003cp\u003eMost production DL380 Gen9 workloads are well served by 8 or 16 bays. The 24-Bay earns its place specifically when:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003evSAN ReadyNode at maximum density.\u003c\/strong\u003e 4-6 cache SSDs in disk groups paired with 18-20 capacity SSDs delivers substantial usable capacity per host. The DL380 Gen9 is a documented vSAN ReadyNode - verify the current VMware HCL for firmware and ESXi support at deployment time.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eStorage Spaces Direct (S2D) high-density nodes.\u003c\/strong\u003e S2D scales IOPS and capacity with drive count; 24 SSDs as 4 cache + 20 capacity, or all-flash 24-way, delivers high per-node capacity at Gen9 standardization.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eHigh-density VDI hosts.\u003c\/strong\u003e Citrix or Horizon environments running 100+ desktops per host benefit from the 24-bay budget for profile management, image deltas, and personal data; SFF SSDs deliver the random-IOPS profile VDI needs.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDatabase hosts with local primary SSD storage.\u003c\/strong\u003e SQL Server, Oracle, or PostgreSQL hosts where the design choice is local SSD rather than SAN - 24 SAS SSDs in the right RAID layout deliver high IOPS without SAN dependency.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMixed NVMe + SSD tiering.\u003c\/strong\u003e The Express Bay option supports SFF NVMe positions; on the 24-bay this gives a hot NVMe tier alongside a bulk SAS\/SATA SSD tier.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eIf 16 bays cover the workload, the \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay canonical\u003c\/a\u003e is the better economic choice at the same platform vocabulary. Pay for 24 bays specifically when the workload needs the additional storage budget.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage - 24 SFF Bays\u003c\/h2\u003e\u003cp\u003eTwenty-four 2.5\" SAS\/SATA hot-swap bays across three drive boxes (Box 1, 2, 3) in the front of the chassis. With all 24 bays populated, the Universal Media Bay (which occupies one drive-box position) is not supported - production 24-bay builds rely on iLO 4 remote management instead. Drive options span the full Gen9 SFF portfolio: SAS SSDs in mixed-use and read-intensive tiers (200 GB through 3.84 TB at launch, larger on later firmware), SATA SSDs for cost-optimized roles, 10K\/15K SAS HDDs, self-encrypting drives for compliance, and NVMe via the Express Bay option in specific positions. At full population with 3.84 TB SAS SSDs the 24-bay delivers roughly 92 TB raw.\u003c\/p\u003e\u003ch3\u003eRAID at 24 SFF\u003c\/h3\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eHCI (vSAN, S2D, Nutanix) - HBA pass-through.\u003c\/strong\u003e Storage redundancy lives in the HCI software, so the H241 HBA with no hardware RAID is the right pattern; disk groups and policies are configured at the HCI layer.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDatabase hosts - RAID 10 across split pools.\u003c\/strong\u003e 24 SSDs as 12 mirror pairs in RAID 10 for high write performance and fast rebuild. The 50% overhead is accepted in exchange for write performance.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eVDI hosts - RAID 6 or RAID 60.\u003c\/strong\u003e Single RAID 6 (22+2) or two striped RAID 6 groups of 12 (RAID 60). RAID 60 is preferred at this drive count for rebuild-scope reduction; SSD rebuilds run in hours, not days.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCapacity-tier SSD - RAID 6.\u003c\/strong\u003e 24x 3.84 TB SAS SSDs in RAID 6 deliver roughly 84 TB usable for a read-heavy capacity tier behind workload caching.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eAt 24 bays, consuming 2 for boot still leaves 22 for data, but M.2 boot via the HPE M.2 enablement card or a rear-2-SFF kit is still preferred for production - it preserves all 24 front bays for the storage layer, which matters most for HCI where every front bay should be available to the software. We default to M.2 or rear-2-SFF on every HCI-context 24-Bay quote.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Controllers at 24-Bay Scale\u003c\/h2\u003e\u003cp\u003eAt 24 SSDs, controller cache and lane budget matter more than at lower bay counts:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P840ar (4 GB FBWC).\u003c\/strong\u003e The standard production controller for 24-bay hardware-RAID builds. 4 GB cache absorbs burst writes across the larger pool; full RAID 0\/1\/5\/6\/10\/50\/60.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array H241 (HBA mode, PCIe plug-in).\u003c\/strong\u003e The most common 24-bay pattern, because HCI is the dominant 24-bay workload. Clean SAS pass-through.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P840 (PCIe plug-in, 4 GB FBWC).\u003c\/strong\u003e Same silicon as the P840ar in plug-in form - useful for dual-controller designs (one for OS\/system disks, one for the 24-bay pool).\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P440ar (2 GB FBWC).\u003c\/strong\u003e Supported, but the 2 GB cache is undersized for write-intensive 24-SSD workloads. Acceptable for read-heavy workloads only.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eFor HCI, multiple HBA controllers may be needed depending on backplane configuration to pass through all 24 bays; we engineer the right combination at quote time against the vSAN\/S2D\/Nutanix HCL. The HPE Smart Storage Battery is required with any P-series controller.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors\u003c\/h2\u003e\u003cp\u003e1 or 2 sockets of Intel Xeon E5-2600 v3 (Haswell-EP) or v4 (Broadwell-EP) on the C610 Grantley chipset; v3 and v4 cannot be mixed, and 2-socket is the production standard (single-socket halves DIMM slots to 12 and PCIe to 3). At 24-bay scale, HCI and VDI consolidation tend to push CPU selection higher than general-purpose 8\/16-bay builds:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2680 v4 (14 cores, 120W).\u003c\/strong\u003e The mainstream production pick - 28 cores at 2S, balanced TDP, standard heatsink. Common HCI\/VDI baseline.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2690 v4 (14 cores, 135W, 2.6 GHz) and E5-2699 v4 (22 cores, 145W).\u003c\/strong\u003e Higher frequency and the 44-core platform maximum respectively for high-VM-density nodes; both 120W+ ship with the high-performance heatsink.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2667 v4 (8 cores, 135W, 3.2 GHz).\u003c\/strong\u003e The per-core-licensing pick for local-SSD database hosts (Oracle, SQL Server Enterprise).\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2650 v4 (12 cores, 105W).\u003c\/strong\u003e Mid-tier at modest TDP for capacity-tier or lighter HCI nodes. Haswell-EP v3 equivalents are available at lower cost with a DDR4-2133 cap.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eMemory\u003c\/h2\u003e\u003cp\u003e24 DDR4 DIMM slots (12 per CPU; 12 with a single CPU). RDIMM and LRDIMM are supported but not mixable; maximum 3 TB with 128 GB LRDIMMs on v4. HPE DDR4 Smart Memory is required for rated speeds. Speed depends on generation and population: v3 caps at DDR4-2133, v4 at DDR4-2400, and full 24-DIMM population drops to DDR4-1866\/1600. For 24-bay HCI and VDI nodes, 256-512 GB is typical (vSAN\/S2D baselines plus VM workload); database hosts size memory to working set plus overhead. NVDIMM-N (8\/16 GB) is supported on v4 for transaction-log persistence.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking and PCIe Expansion\u003c\/h2\u003e\u003cp\u003eEmbedded HPE 4-port 1 GbE 331i standard, with the optional FlexibleLOM mezzanine for 10 GbE SFP+ (530FLR\/534FLR), 10 GBASE-T, 25 GbE SFP28, or converged FlexFabric - 10\/25 GbE FlexibleLOM is strongly recommended for HCI east-west traffic. PCIe expansion is 3 PCIe Gen3 slots with one CPU, expanding to 6 with both populated (the +3-slot riser requires the second CPU). Plan lane budget carefully when Express Bay NVMe is in scope, since NVMe positions consume dedicated PCIe lanes alongside HBA and FlexibleLOM cards.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eGPU Support\u003c\/h2\u003e\u003cp\u003eGPU support is bounded by PCIe Gen3 and the 2U thermal envelope, and at 24 bays it competes with NVMe and HBA cards for lane and slot budget:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSingle-width accelerators.\u003c\/strong\u003e NVIDIA Tesla T4 (70W, passive) for inference or VDI graphics offload; no GPU power cable kit required.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDouble-width GPUs.\u003c\/strong\u003e Gen9-era M40\/M60\/K80-class cards require the high-performance heatsink and the GPU power cable kit (PN 669777-B21); plan for up to two, subject to PSU sizing and slot contention with HBAs.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eThermal and lanes.\u003c\/strong\u003e A fully populated 24-bay plus double-wide GPUs is a dense thermal and PCIe-lane load - we validate inlet temperature and lane allocation at quote time. PCIe Gen3 bandwidth is the ceiling; PCIe Gen4 GPU workloads belong on Gen10 Plus or Gen11.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eManagement - iLO 4 Generation\u003c\/h2\u003e\u003cp\u003eHPE iLO 4: remote console (iLO Advanced for full graphical KVM), virtual media, IPMI, SNMP telemetry, Active Health System logging, and OneView compatibility - the same iLO 4 across the Gen9 line. Unlike Gen10's iLO 5, iLO 4 has no Silicon Root of Trust; UEFI Secure Boot is the firmware-integrity baseline, with compensating controls where a compliance framework requires platform attestation. On dense 24-bay builds with no Universal Media Bay, iLO 4 remote access covers the operational requirement the front media bay would otherwise serve. iLO Advanced is typically a separate cost and rarely optional in production; we quote it explicitly.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePower and Cooling at 24-Drive Scale\u003c\/h2\u003e\u003cp\u003eA fully populated 24-Bay with 2x E5-2680 v4, 24 DIMMs, and 24 SAS SSDs draws roughly 700-900W sustained; higher-bin CPUs (E5-2690\/2699 v4) and NVMe push that to 900-1,100W. PSU sizing:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003e2x 800W Flex Slot Platinum (typical production).\u003c\/strong\u003e Covers mainstream dual-socket builds with full memory and 24 SSDs in 1+1 redundancy.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e2x 1400W Flex Slot Platinum (high TDP).\u003c\/strong\u003e Required for E5-2699 v4 or double-wide GPU builds; supports low-line and high-line input.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e500W - not recommended at 24 bays.\u003c\/strong\u003e Marginal for sustained 24-drive workloads; use 800W minimum.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eTake redundant PSU on every 24-Bay production build - HCI, VDI, and database hosts are workloads where unplanned downtime has documented cost. We run the HPE Power Advisor and validate thermal headroom against every 24-Bay quote; ASHRAE A3 (40°C) ambient is supported with performance heatsinks, with confirmation of inlet spec per configuration.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePhysical Specs \u0026amp; Platform Notes\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eForm factor:\u003c\/strong\u003e 2U rackmount, standard-depth Gen9 enclosure; with the cable management arm installed, plan for additional rear clearance.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe expansion:\u003c\/strong\u003e up to 6 PCIe Gen3 slots with both CPUs (3 with one), split full-height and low-profile across the primary and secondary risers; the secondary riser requires the second processor. Lane budget is tighter at 24 bays once NVMe, HBA, and FlexibleLOM cards are added.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eParts availability:\u003c\/strong\u003e excellent - one of the largest 2U install bases, so drives, PSUs, risers, heatsinks, and Smart Array controllers are widely available; third-party maintenance spares depth is strong in major metros.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAccessories we recommend:\u003c\/strong\u003e the 2U SFF ball-bearing sliding rail kit (P\/N 679365-001 \/ 737412-001; see the \u003ca href=\"\/products\/hp-dl380-g8-g9-sff-sliding-rails-679365-001-737412-001\"\u003eDL380 Gen9 2U SFF sliding rail kit\u003c\/a\u003e), the HPE M.2 enablement card or rear-2-SFF kit for boot placement, and the GPU power cable kit (PN 669777-B21) on accelerator builds. The Universal Media Bay (PN 724865-B21) is not available at full 24-bay population.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePlatform notes:\u003c\/strong\u003e CPU hot-plug is not supported, and v3\/v4 CPUs cannot be mixed. NVMe via the Express Bay option consumes specific front-bay positions and PCIe lanes. Confirm HCI HCL status (vSAN\/S2D\/Nutanix) against current firmware before committing.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003e\u003cstrong\u003eWhere it excels:\u003c\/strong\u003e The 24-Bay is the right answer when maximum local SFF capacity in a single 2U Gen9 host is the design driver - vSAN ReadyNodes at maximum density, S2D high-density nodes, 100+-desktop VDI hosts, and database hosts that keep primary storage local on SSD rather than SAN. It is also the natural capacity-add for an existing Gen9 HCI fleet that needs another high-density node at the same platform standard.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhere to look instead:\u003c\/strong\u003e If 16 bays cover the workload, the \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e is more economical at the same vocabulary; for compute-driven workloads with networked storage, the \u003ca href=\"\/products\/hp-proliant-dl380-g9-2-5-8-bay-server\"\u003eDL380 Gen9 8-Bay 2.5\"\u003c\/a\u003e; for bulk HDD capacity, the \u003ca href=\"\/products\/hp-proliant-dl380-g9-12-bay-3-5-chassis\"\u003eDL380 Gen9 12-Bay 3.5\"\u003c\/a\u003e. New deployments needing iLO 5, PCIe Gen4, or DDR4-2933+ should step to the \u003ca href=\"\/products\/hpe-dl380-g10-2-5-24-bay-chassis\"\u003eDL380 Gen10 24-Bay 2.5\"\u003c\/a\u003e. Dell-standardized shops should compare the \u003ca href=\"\/products\/dell-poweredge-r730xd-24-bay-2-5-chassis\"\u003eDell PowerEdge R730xd 24-Bay 2.5\"\u003c\/a\u003e.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eBottom line:\u003c\/strong\u003e This is the densest SFF Gen9 host we build, and it earns its premium only when the workload genuinely needs the storage budget. The typical buyer is running HCI, high-density VDI, or local-SSD databases and is standardizing on Gen9 for cost or fleet-consistency reasons. Buy it for the storage density; if 16 bays cover you, save the money and take the canonical.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSame Gen9 platform limits as the canonical:\u003c\/strong\u003e HPE active warranty ended, iLO 4 without Silicon Root of Trust, DDR4 speed caps, PCIe Gen3 only, FBWC battery as a wear item. See the \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003e16-Bay canonical\u003c\/a\u003e for the full platform detail.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eUniversal Media Bay unavailable at full 24-bay population\u003c\/strong\u003e - the media bay occupies a drive-box position; production 24-bay builds use remote iLO 4 access.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eController choice matters more here.\u003c\/strong\u003e The P440ar 2 GB cache is undersized for write-intensive 24-SSD workloads; P840ar (4 GB) or H241 HBA is the right answer depending on whether redundancy lives in the controller or the software.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSingle-PSU operation is not a production configuration\u003c\/strong\u003e at 700W-1.1 kW sustained; take redundant PSU.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNVMe at 24-bay scale consumes PCIe lane budget\u003c\/strong\u003e alongside HBA and FlexibleLOM; plan expansion carefully.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eHCI HCL verification is required\u003c\/strong\u003e - vSAN ReadyNode, S2D, and Nutanix status depend on specific firmware and software versions.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eThis server is right for\u003c\/th\u003e\n\u003cth\u003eConsider alternatives for\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ vSAN ReadyNode at maximum SFF density\u003c\/td\u003e\n\u003ctd\u003e❌ 8 or 16 bays sufficient (use 8-Bay or 16-Bay canonical)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ Storage Spaces Direct (S2D) high-density nodes\u003c\/td\u003e\n\u003ctd\u003e❌ Bulk-capacity workloads needing LFF (use 12-Bay 3.5\")\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ High-density VDI hosts (100+ sessions per host)\u003c\/td\u003e\n\u003ctd\u003e❌ New deployments needing iLO 5 \/ PCIe Gen4\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ Database hosts with local primary SSD storage\u003c\/td\u003e\n\u003ctd\u003e❌ Memory configurations above 3 TB per host\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ Capacity-add to an existing Gen9 HCI fleet\u003c\/td\u003e\n\u003ctd\u003e❌ Active HPE ProSupport requirement\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003e16 SFF bays sufficient?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e - the SFF sweet spot at lower cost.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e8 SFF bays for compute-driven workloads?\u003c\/strong\u003e → \u003ca href=\"\/products\/hp-proliant-dl380-g9-2-5-8-bay-server\"\u003eDL380 Gen9 8-Bay 2.5\"\u003c\/a\u003e - VM nodes with networked storage.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eBulk capacity rather than SFF performance?\u003c\/strong\u003e → \u003ca href=\"\/products\/hp-proliant-dl380-g9-12-bay-3-5-chassis\"\u003eDL380 Gen9 12-Bay 3.5\"\u003c\/a\u003e - LFF for backup, file servers, archive.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eA lower-cost 2U Gen9 value tier?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl180-gen9-lff-build-your-own\"\u003eHPE ProLiant DL180 Gen9 LFF\u003c\/a\u003e - cost-optimized 2U dual-socket Gen9.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eGen10 24-Bay with iLO 5, DDR4-2933, Silicon Root of Trust?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-dl380-g10-2-5-24-bay-chassis\"\u003eDL380 Gen10 24-Bay 2.5\"\u003c\/a\u003e.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDell alternative at the same 24 SFF tier?\u003c\/strong\u003e → \u003ca href=\"\/products\/dell-poweredge-r730xd-24-bay-2-5-chassis\"\u003eDell PowerEdge R730xd 24-Bay 2.5\"\u003c\/a\u003e - 2U 2S Grantley, equivalent positioning.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us the workload (HCI platform \/ VDI \/ database \/ capacity-tier SSD), HCI software and HCL context if relevant, CPU and core target, memory target, storage architecture (drive mix, NVMe requirement, RAID layout), controller preference (P840ar for hardware RAID, H241 for HCI\/HBA), boot pattern, networking requirement (10\/25 GbE FlexLOM strongly recommended), PSU model, and quantity. We respond within 24 hours with a validated configuration including HCL verification, RAID-sizing math, and HPE Power Advisor sizing. Every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in testing, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951241846983,"sku":"BP-013612","price":338.43,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-g9-24-bay-25-drives-954872.png?v=1765539623"},{"product_id":"hp-proliant-dl380-g9-2-5-8-bay-server","title":"HPE ProLiant DL380 Gen9 8-Bay 2.5\" Drives","description":"\u003cp\u003eThe refurbished HPE ProLiant DL380 Gen9 8-Bay 2.5\" is the compute-focused member of the DL380 Gen9 family - the eight-bay variant of HPE's Gen9 dual-socket 2U mainstream platform, with eight 2.5\" SFF hot-swap bays in the standard chassis. It runs the same Intel Xeon E5-2600 v3 (Haswell-EP) or v4 (Broadwell-EP) processors on the Grantley platform with the C610 chipset, the same 24 DDR4 DIMM slots and 3 TB memory ceiling, the same modular Smart Array storage controllers, the same FlexibleLOM networking, and the same iLO 4 management as the rest of the Gen9 line. What is different is the storage footprint: eight bays is the sweet spot for compute-driven workloads where primary data lives on SAN, NFS, or a distributed file system and local storage handles the OS, application binaries, and modest hot-data staging.\u003c\/p\u003e\u003cp\u003eWithin the family, the sixteen-bay configuration is the mainstream SFF default; this eight-bay build is for deployments that do not need that much local storage and would rather not pay for bays that sit empty. For family-level positioning and the cross-vendor comparison, the \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e is the primary page. This page carries the full platform detail in its own right and focuses on what is specific to the eight-bay variant: when eight SFF bays is the right tool, the bay-count-driven workload patterns, and the storage decisions that change at eight versus sixteen or twenty-four.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhen 8 SFF Bays Is the Right Default\u003c\/h2\u003e\u003cp\u003eThe 8-Bay DL380 Gen9 fits most production dual-socket Gen9 workloads where storage is networked rather than local. The bay-count decision framework:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eVM cluster nodes with SAN-backed datastores.\u003c\/strong\u003e Boot plus a small local cache or VM tier lives on the eight bays; primary datastores sit on shared FC or iSCSI SAN reached through an FC HBA in PCIe expansion.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eApplication servers with modest local data.\u003c\/strong\u003e The OS plus four to six SSDs for application data, logs, or staging, with the database backend on the network. Web, app, and middleware tiers where local storage is supplementary.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMid-tier SQL Server or Oracle hosts with networked primary storage.\u003c\/strong\u003e Local SSDs cover the OS, tempdb or Oracle Grid binaries, and transaction logs while the datafiles live on SAN.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDomain controllers, file servers, and infrastructure services.\u003c\/strong\u003e Modest local capacity is sufficient, delivered at materially lower acquisition cost than the 16- or 24-bay builds.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eBranch office and ROBO deployments.\u003c\/strong\u003e Dual-socket compute with modest local storage for branch file services, AD\/DNS, and application hosting; eight bays matches the typical ROBO footprint.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eLab, dev, and staging environments.\u003c\/strong\u003e Mirroring Gen9 production at lower per-node cost, where eight bays is sufficient for non-production patterns.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eIf the workload genuinely needs more than eight bays of local storage (VDI hosts, HCI nodes, database hosts with local primary storage, mid-size file servers), step to the \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e for the SFF sweet spot or the \u003ca href=\"\/products\/dl380-g9-2-5-24-bay-chassis\"\u003eDL380 Gen9 24-Bay 2.5\"\u003c\/a\u003e for maximum SFF density. If eight is sufficient, the 8-Bay delivers the same Gen9 platform at meaningful cost savings.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage - 8 SFF Bays\u003c\/h2\u003e\u003cp\u003eEight 2.5\" SAS\/SATA hot-swap bays in the standard chassis configuration (Box 1 populated). The DL380 Gen9 chassis is upgradeable to 16, 18, or 24 SFF in the field via additional drive-cage kits (Box 2 and Box 3 plus the appropriate backplane), but the eight-bay starting point is the right answer when the workload does not anticipate needing more local storage. The optional Universal Media Bay (PN 724865-B21) is available on the eight-bay chassis and provides front VGA, 2x USB 2.0, and optional 2 SFF rear bays plus optical-drive support - useful for deployments that need front-panel management ports.\u003c\/p\u003e\u003cp\u003eDrive options span the full Gen9 SFF portfolio: SAS SSDs in mixed-use and read-intensive endurance tiers (200 GB through 3.84 TB at Gen9 launch, larger capacities on later firmware), SATA SSDs for cost-optimized OS and bulk-storage roles, 10K and 15K SAS HDDs for moderate-IOPS data (300 GB through 2.4 TB at SFF), self-encrypting drive variants for compliance, and NVMe SSDs via the Express Bay option in Box 1 (consuming bay count for NVMe positions).\u003c\/p\u003e\u003cp\u003eCommon DL380 Gen9 8-Bay storage profiles:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eVMware cluster node, SAN datastore primary.\u003c\/strong\u003e 2x SSDs RAID 1 ESXi boot, six bays for a vSAN cache tier or local-VM datastore. Primary VM storage on shared FC\/iSCSI SAN.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eHyper-V cluster node with CSV cache.\u003c\/strong\u003e 2x SSDs for Windows Server, six SSDs for a CSV cache tier. Primary VM storage on SOFS or SAN.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eApplication server with local logs\/staging.\u003c\/strong\u003e 2x SSDs RAID 1 OS, 4-6 SSDs in RAID 5\/10 for app data and logs. Primary data backend on a networked database.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSQL Server with networked datafiles.\u003c\/strong\u003e 2x SSDs OS, 2x SSDs tempdb mirror, 4x SSDs log files in RAID 10. Primary database files on a SAN datastore.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDomain controller \/ infrastructure services.\u003c\/strong\u003e 2x SSDs RAID 1 for OS and AD\/DNS\/DHCP roles, the remaining bays for supplementary storage or left unused.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eBranch office multi-role server.\u003c\/strong\u003e 2x SSDs OS, six SAS HDDs in RAID 6 for branch file shares. Cost-optimized branch deployment with single-server compute and storage.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eOn the eight-bay configuration, boot-drive placement matters more than on 16- or 24-bay builds because consuming two of eight bays for the OS is a meaningful 25% of the storage budget. Three options:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eRear-bay 2 SFF kit.\u003c\/strong\u003e Preserves all eight front bays for data; the OS lives in the rear bays. The right pattern when front-bay capacity matters.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eM.2 SATA SSDs via the HPE M.2 enablement card.\u003c\/strong\u003e M.2 boot in a PCIe slot, freeing all front bays for data. Consumes a PCIe slot but preserves the storage budget.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e2x front-bay SSDs in RAID 1.\u003c\/strong\u003e The simplest configuration; consumes two of eight front bays. Acceptable when the six remaining bays cover the workload's data requirement.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eWe default to the rear-bay 2 SFF kit on 8-Bay DL380 Gen9 quotes when front-bay capacity is at all constrained, and to the standard front-bay RAID 1 pattern when the workload comfortably fits in six bays of data.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Controllers\u003c\/h2\u003e\u003cp\u003eThe controller decision does not change with bay count - only the cache-sizing tradeoff does. The same modular Smart Array \"ar\" controllers used across the family apply here:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P440ar (2 GB FBWC).\u003c\/strong\u003e The mainstream production controller for the eight-bay build. 2 GB of flash-backed write cache is comfortably sized for eight SSDs under most workload patterns, and it is the right pick for traditional hardware RAID in production.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array H241 (HBA mode, PCIe plug-in).\u003c\/strong\u003e For software-defined storage (vSAN, S2D, Ceph, ZFS). Clean SAS pass-through with no hardware RAID.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P840ar (4 GB FBWC).\u003c\/strong\u003e The premium controller. Rarely needed at eight bays - the P440ar's 2 GB cache is sufficient for this storage scale.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDynamic Smart Array B140i (embedded software RAID).\u003c\/strong\u003e Acceptable for OS boot mirroring only; not appropriate for production data.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThe HPE Smart Storage Battery is required with any P-series controller. The Gen9 FBWC battery is a wear item with a documented 5-7 year service life; we disclose battery state on every quote and replace cache modules that are past spec as part of build prep.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors\u003c\/h2\u003e\u003cp\u003e1 or 2 sockets of Intel Xeon E5-2600 v3 (Haswell-EP) or v4 (Broadwell-EP) on the C610 Grantley chipset. Mixing v3 and v4 is not supported - all installed CPUs must be the same generation, though a field upgrade from v3 to v4 (replacing both at once) is supported. Single-socket builds cut DIMM slots in half (12 instead of 24) and PCIe to three slots, so 2-socket is the production standard. The eight-bay chassis shares the same 2U thermal envelope as the higher-bay variants, and its lower drive count leaves a little more power and airflow headroom for top-bin CPUs.\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2680 v4 (14 cores, 120W, DDR4-2400).\u003c\/strong\u003e The Gen9 production mainstream - 28 cores at 2S, balanced TDP, standard heatsink.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2690 v4 (14 cores, 135W, 2.6 GHz).\u003c\/strong\u003e Higher base frequency for single-thread-sensitive workloads within the same core budget.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2699 v4 (22 cores, 145W).\u003c\/strong\u003e Top-bin Broadwell-EP - 44 cores at 2S, the platform maximum. Requires the high-performance heatsink (auto-included for 120W+ CPUs).\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2650 v4 (12 cores, 105W).\u003c\/strong\u003e Mid-tier production at modest TDP and lower acquisition cost - a good fit for general virtualization and application servers.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2620 v4 (8 cores, 85W) and E5-2667 v4 (8 cores, 135W, 3.2 GHz).\u003c\/strong\u003e Entry-tier and high-frequency specialty SKUs; the 2667 v4 is the per-core-licensing pick for Oracle and SQL Server Enterprise. Haswell-EP v3 equivalents are available at lower cost with a DDR4-2133 cap.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eMemory\u003c\/h2\u003e\u003cp\u003e24 DDR4 DIMM slots (12 per CPU; only 12 are available with a single CPU). RDIMM and LRDIMM are supported but cannot be mixed in one server; the maximum is 3 TB with 128 GB LRDIMMs across all 24 slots on v4 CPUs. HPE DDR4 Smart Memory is required for rated speeds - third-party DDR4 drops to lower speeds, documented HPE behavior across Gen9.\u003c\/p\u003e\u003cp\u003eMemory speed depends on CPU generation and population: v3 caps at DDR4-2133, v4 at DDR4-2400, and full 24-DIMM population drops to DDR4-1866 or DDR4-1600 depending on rank. For maximum bandwidth, populate at 1 DPC (12 DIMMs at 2S). HPE Persistent Memory (NVDIMM-N, 8 GB and 16 GB) is supported on v4 CPUs for DRAM-class latency with battery-backed persistence - uncommon, but available for SQL Server transaction logs and in-memory database WAL.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking and PCIe Expansion\u003c\/h2\u003e\u003cp\u003eThe embedded HPE 4-port 1 GbE 331i adapter is standard and consumes no slot. The optional FlexibleLOM mezzanine supports 10 GbE SFP+ (530FLR\/534FLR), 10 GBASE-T, 25 GbE SFP28, and converged FlexFabric. Unlike the DL580 Gen9, Wake-on-LAN works on both the embedded 1 GbE and the FlexibleLOM here. PCIe expansion is three PCIe Gen3 slots with one CPU, expanding to six with both CPUs populated; the +3-slot secondary riser requires the second processor. All slots are PCIe Gen3 and accept cards up to 150W, higher with the supplemental power-cable kit. On a SAN-backed eight-bay build, an FC HBA or a 10\/25 GbE FlexibleLOM is usually the first expansion priority.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eGPU Support\u003c\/h2\u003e\u003cp\u003eGPU and accelerator support is bounded by the PCIe Gen3 generation and the 2U thermal envelope. The eight-bay build's lower drive count can leave a little more PSU headroom for accelerators, but the slot and thermal limits are the same as the rest of the family:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSingle-width accelerators.\u003c\/strong\u003e Cards like the NVIDIA Tesla T4 (70W, single-slot, passive) for inference, transcoding, or VDI graphics offload. They fit standard riser positions and need no GPU power-cable kit.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDouble-width GPUs.\u003c\/strong\u003e Passively cooled Gen9-era cards (NVIDIA M40, M60, K80-class). These require the high-performance heatsink and an additional GPU power-cable kit (PN 669777-B21); plan for up to two, subject to PSU sizing.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eThermal envelope.\u003c\/strong\u003e GPU builds require performance heatsinks and the high-performance fan kit, and ASHRAE A3\/A4 ambient headroom is reduced with double-wide cards. We validate inlet temperature against the configuration at quote time.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eFPGA and specialty cards.\u003c\/strong\u003e The PCIe Gen3 x16 slots accept FPGA and specialty cards within the 150W per-slot limit. PCIe Gen3 bandwidth is the ceiling - workloads needing PCIe Gen4 GPU bandwidth belong on Gen10 Plus or Gen11.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eManagement - iLO 4 Generation\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen9 ships with HPE iLO 4: remote console (an iLO Advanced license enables full graphical KVM), virtual media, IPMI, SNMP telemetry, Active Health System logging, and HPE OneView compatibility - the same iLO 4 generation across the Gen9 line, which is part of the platform's operational-standardization value. The key difference from Gen10 is that iLO 4 has no Silicon Root of Trust; the hardware-anchored firmware-verification chain arrived with iLO 5 on Gen10. UEFI Secure Boot is supported and is the right pattern for production Gen9 builds, with compensating controls where a compliance framework requires firmware-integrity attestation. iLO Advanced is typically a separate cost and is rarely optional for production data-center deployments; we quote it explicitly.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\u003cp\u003eThe same HPE Flex Slot power supplies as the rest of the DL380 Gen9 family - 500W, 800W, or 1400W Platinum\/Titanium in 1+1 redundant configurations, plus the optional HPE Flexible Slot Battery Backup module. The eight-bay configuration's lower drive count means lower total power draw than the 16- or 24-bay variants: 500W PSUs are adequate for many eight-bay builds, and 800W in 1+1 covers all common dual-socket configurations including E5-2680\/2690 v4 with full memory.\u003c\/p\u003e\u003cp\u003eFor high-TDP CPUs (E5-2699 v4 at 145W, E5-2667 v4 at 135W) or builds with double-wide GPUs, 1400W PSUs are required. We run the HPE Power Advisor against every DL380 Gen9 quote to validate PSU sizing. Thermal: ASHRAE A3 (40 C) and A4 (45 C) extended-ambient operation is supported with the performance heatsinks (auto-included for 120W+ CPUs).\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePhysical Specs \u0026amp; Platform Notes\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eForm factor:\u003c\/strong\u003e 2U rackmount, standard-depth Gen9 enclosure shared across the DL380 Gen9 bay-count variants; with the cable management arm installed, plan for additional rear clearance.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe expansion:\u003c\/strong\u003e up to six PCIe Gen3 slots with both CPUs populated (three with one CPU), split full-height and low-profile across the primary and secondary risers; the secondary riser requires the second processor.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eParts availability:\u003c\/strong\u003e excellent. The DL380 Gen9 shipped in one of the largest install bases of any 2U generation, so drives, PSUs, risers, heatsinks, FlexibleLOM cards, and Smart Array controllers are widely available, and third-party maintenance spares depth is strong in major metros.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAccessories we recommend:\u003c\/strong\u003e the 2U SFF ball-bearing sliding rail kit (P\/N 679365-001 \/ 737412-001; see the \u003ca href=\"\/products\/hp-dl380-g8-g9-sff-sliding-rails-679365-001-737412-001\"\u003eDL380 G8\/G9 2U SFF sliding rail kit\u003c\/a\u003e), the optional Universal Media Bay (PN 724865-B21) for front VGA and USB, the rear-2-SFF kit for boot placement, and the GPU power-cable kit (PN 669777-B21) on accelerator builds.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePlatform notes:\u003c\/strong\u003e CPU hot-plug is not supported, and v3\/v4 CPUs cannot be mixed. NVMe via the Express Bay option consumes specific front-bay positions, which is a tighter tradeoff at eight bays than at sixteen or twenty-four. Confirm FlexibleLOM and drive-backplane compatibility against the specific build at quote time.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003e\u003cstrong\u003eWhere it excels:\u003c\/strong\u003e The eight-bay DL380 Gen9 is the right answer for compute-driven dual-socket workloads where primary storage is networked. It is a strong fit for VM cluster nodes with SAN-backed datastores, application and middleware servers with modest local data, mid-tier SQL Server and Oracle hosts whose datafiles live on SAN, domain controllers and infrastructure services, branch-office and ROBO deployments, and lab or staging environments mirroring Gen9 production. When the workload does not need a large local SSD pool, paying for sixteen or twenty-four bays is wasted budget, and the eight-bay build delivers the same Gen9 platform for less.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhere to look instead:\u003c\/strong\u003e If the workload needs a large local storage tier, the \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e is the SFF sweet spot and the \u003ca href=\"\/products\/dl380-g9-2-5-24-bay-chassis\"\u003eDL380 Gen9 24-Bay 2.5\"\u003c\/a\u003e is the maximum-density option; for bulk HDD capacity, the \u003ca href=\"\/products\/hp-proliant-dl380-g9-12-bay-3-5-chassis\"\u003eDL380 Gen9 12-Bay 3.5\"\u003c\/a\u003e is purpose-built. New mission-critical deployments that need iLO 5 Silicon Root of Trust, PCIe Gen4, or DDR4-2933+ bandwidth should move to the \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\"\u003c\/a\u003e. Budget-driven 2U Gen9 deployments that can trade SFF for LFF should compare the \u003ca href=\"\/products\/hpe-proliant-dl180-gen9-lff-build-your-own\"\u003eHPE ProLiant DL180 Gen9 LFF\u003c\/a\u003e value tier. Dell-standardized shops should compare the \u003ca href=\"\/products\/dell-poweredge-r730-8-bay-2-5-chassis\"\u003eDell PowerEdge R730 8-Bay 2.5\"\u003c\/a\u003e, the equivalent 2U Grantley platform at the same bay count.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eBottom line:\u003c\/strong\u003e The eight-bay DL380 Gen9 is the cost-disciplined member of the family - the build you choose when the compute is the point and the storage lives on the network. The typical customer is an IT team adding SAN-backed VM cluster nodes to an existing Gen9 estate, standing up application or infrastructure servers, or deploying branch and ROBO sites where local capacity is modest. Buy it when eight bays genuinely cover the local-storage requirement; step up to the 16- or 24-bay companions the moment a large local SSD pool is in the picture, and step to Gen10 when current-generation security and memory bandwidth matter.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSame Gen9 platform limitations as the rest of the family.\u003c\/strong\u003e HPE active warranty has ended; iLO 4 has no Silicon Root of Trust; DDR4 speed caps at DDR4-2400 (v4) or DDR4-2133 (v3) and drops further under full DIMM population; PCIe Gen3 only; the FBWC battery is a wear item; v3\/v4 CPU mixing is not supported; and HPE Smart Memory is required for rated speeds.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eBoot-drive consumption hurts more at eight bays.\u003c\/strong\u003e Two bays for an OS RAID 1 mirror is 25% of the budget, so rear-bay or M.2 boot is strongly preferred on builds where data capacity matters.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eFuture expansion to 16 or 24 bays requires backplane and cage kits.\u003c\/strong\u003e The field upgrade is supported but not trivial - if the workload may grow into more bays within the platform's service life, start at the 16- or 24-bay variant to avoid the expansion exercise.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNVMe consumes bay count.\u003c\/strong\u003e The Express Bay NVMe option occupies physical front-bay positions, so on the eight-bay build the storage budget tightens further when NVMe-tier performance is required.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eThis server is right for\u003c\/th\u003e\n\u003cth\u003eConsider alternatives for\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ VM cluster nodes with SAN-backed datastores\u003c\/td\u003e\n\u003ctd\u003e❌ VDI hosts requiring SFF-bay-heavy storage (use 16-Bay)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ Application servers and middleware tier\u003c\/td\u003e\n\u003ctd\u003e❌ HCI nodes needing a high local drive count (use 16- or 24-Bay)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ Database hosts with networked primary storage\u003c\/td\u003e\n\u003ctd\u003e❌ Database hosts with local primary storage (use 16- or 24-Bay)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ Domain controllers and infrastructure services\u003c\/td\u003e\n\u003ctd\u003e❌ Workloads requiring more than eight bays at Gen9\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ Branch office and ROBO deployments\u003c\/td\u003e\n\u003ctd\u003e❌ New mission-critical deployments needing iLO 5\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ Lab\/dev\/staging mirroring Gen9 production\u003c\/td\u003e\n\u003ctd\u003e❌ Memory-bandwidth-sensitive workloads (Gen10+)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed more SFF bays at Gen9?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e - the SFF sweet spot for VDI, HCI, and database hosts with local SSD.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed maximum SFF density at Gen9?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g9-2-5-24-bay-chassis\"\u003eDL380 Gen9 24-Bay 2.5\"\u003c\/a\u003e - 24 SFF bays at Gen9.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed LFF (3.5\") drives for bulk capacity?\u003c\/strong\u003e → \u003ca href=\"\/products\/hp-proliant-dl380-g9-12-bay-3-5-chassis\"\u003eDL380 Gen9 12-Bay 3.5\"\u003c\/a\u003e - high-capacity NL-SAS HDD pool.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWant a lower-cost 2U Gen9 value tier?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl180-gen9-lff-build-your-own\"\u003eHPE ProLiant DL180 Gen9 LFF\u003c\/a\u003e - cost-optimized 2U dual-socket Gen9.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed Gen10 with iLO 5, DDR4-2933, and Silicon Root of Trust?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\"\u003c\/a\u003e - current-generation 2U.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDell shop alternative at the same Gen9 dual-socket 2U tier?\u003c\/strong\u003e → \u003ca href=\"\/products\/dell-poweredge-r730-8-bay-2-5-chassis\"\u003eDell PowerEdge R730 8-Bay 2.5\"\u003c\/a\u003e - 2U 2S Grantley, equivalent positioning.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMounting hardware?\u003c\/strong\u003e → \u003ca href=\"\/products\/hp-dl380-g8-g9-sff-sliding-rails-679365-001-737412-001\"\u003eDL380 G8\/G9 2U SFF sliding rail kit\u003c\/a\u003e (P\/N 679365-001 \/ 737412-001).\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us the workload, CPU generation preference (v3 vs v4), memory target, storage configuration (drive types, RAID layout, controller preference, boot pattern), networking requirement (embedded 1 GbE vs FlexibleLOM), PSU configuration, and quantity. We respond within 24 hours with a validated configuration including HPE Power Advisor sizing and third-party maintenance coordination when requested. Every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in testing, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951241814215,"sku":"BP-013603","price":217.82,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-gen9-8-bay-25-drives-848287.png?v=1765539623"},{"product_id":"dl360-g9-3-5-4-bay-chassis","title":"HPE ProLiant DL360 Gen9 4-Bay 3.5\" Drives [Gen9]","description":"\u003cp\u003eThe refurbished HPE ProLiant DL360 Gen9 4-Bay 3.5\" is the large-form-factor (LFF) member of HPE's Gen9 1U dual-socket line: four 3.5\" SAS\/SATA hot-swap bays in a 1U chassis. It carries the same Intel Grantley platform as the rest of the family, Intel Xeon E5-2600 v3 (Haswell-EP) or v4 (Broadwell-EP) on the C610 chipset, 24 DDR4 DIMM slots with a 3 TB ceiling, HPE modular Smart Array controllers, the FlexibleLOM mezzanine, and iLO 4 management. What is specific to this variant is the form factor: four LFF bays in 1U is a deliberately narrow combination that pairs high rack density with bulk-capacity HDD storage for edge, branch, ROBO, and backup roles where both rack space and capacity matter.\u003c\/p\u003e\u003cp\u003eThis page covers what changes on the LFF chassis: the workloads where 1U LFF is the right tool, the RAID math at four large-capacity drives, and the storage decisions that differ from the SFF configurations. The shared compute, memory, networking, and management platform is the same across every DL360 Gen9 chassis; for the full platform reference, the \u003ca href=\"\/products\/hpe-proliant-dl360-g9-8-bay-2-5-chassis\"\u003eDL360 Gen9 8-Bay 2.5\"\u003c\/a\u003e is the primary page for the family.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty after a 12+ hour burn-in test, and volume pricing starts at 5 units.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhen 1U LFF Is the Right Combination\u003c\/h2\u003e\u003cp\u003e1U LFF is a narrow configuration on purpose. Most LFF workloads run on 2U or 4U platforms with twelve or more bays for capacity scaling, and most 1U workloads run SFF for performance per bay. The DL360 Gen9 4-Bay 3.5\" earns its place only when both 1U rack density and large-format HDD capacity are genuine requirements at the same time:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eEdge compute with bulk local storage.\u003c\/strong\u003e Edge sites running analytics preprocessing, IoT collection, or video work that also need local capacity for staging before central upload. Four 8 TB to 12 TB NL-SAS drives deliver roughly 24 TB to 36 TB raw in 1U of rack space.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eBranch office multi-role servers.\u003c\/strong\u003e A single 1U box running AD, DNS, DHCP, file shares, print, and modest local virtualization. Four LFF bays in RAID 6 or RAID 10 cover branch-scale file capacity without a separate storage chassis.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eROBO file servers at 1U density.\u003c\/strong\u003e Regional and satellite offices with hard rack-space limits, where a 1U compute-plus-storage box covers most branch infrastructure on one server.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRemote backup targets.\u003c\/strong\u003e Backup repositories at sites where a 2U-or-larger storage box does not fit the rack envelope. Four high-capacity NL-SAS drives in RAID 6 hold a useful branch retention window.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmall to mid-scale surveillance NVR.\u003c\/strong\u003e Camera counts that fit within four LFF drives of retention, where the recorder shares the rack with other 1U gear.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eLab, dev, and test bulk storage.\u003c\/strong\u003e Lower-priority capacity where 1U cost and density matter more than scale.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eIf four LFF bays are enough and 1U density is the constraint, this configuration does real work. If bulk capacity is the primary driver and 1U is not required, the \u003ca href=\"\/products\/hp-proliant-dl380-g9-12-bay-3-5-chassis\"\u003eDL380 Gen9 12-Bay 3.5\"\u003c\/a\u003e at 2U is the better fit, with three times the bay count for twice the rack space.\u003c\/p\u003e\u003ch2\u003eStorage - 4 LFF Bays\u003c\/h2\u003e\u003cp\u003eFour 3.5\" SAS\/SATA hot-swap bays sit across the front of the 1U chassis. NVMe options are limited on the LFF chassis; the Express Bay NVMe support lives on the SFF DL360 Gen9 variants. When a 1U LFF build needs some flash alongside HDD capacity, the practical patterns are LFF SSDs in 3.5\" carriers or an M.2 SATA SSD on a PCIe enablement card for the boot and high-performance tier. At full population, four LFF bays reach roughly 56 TB raw with 14 TB drives, before RAID overhead.\u003c\/p\u003e\u003cp\u003eThe drive portfolio spans the full Gen9 LFF range:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eNL-SAS HDDs.\u003c\/strong\u003e The bulk-capacity workhorse: 4 TB through 14 TB MDL drives at 7,200 RPM, optimized for sequential throughput and capacity per dollar.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e10K and 15K SAS HDDs.\u003c\/strong\u003e Higher per-drive IOPS than NL-SAS at a lower capacity ceiling: 10K LFF tops near 2.4 TB, 15K LFF near 900 GB.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eLFF SSDs.\u003c\/strong\u003e SAS or SATA SSDs in 3.5\" carriers. Rarely the efficient choice on form factor alone, but valid when LFF is locked in for chassis reasons.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSelf-encrypting drives (SED).\u003c\/strong\u003e Available for compliance-regulated bulk storage.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eRAID at 4 LFF\u003c\/h3\u003e\u003cp\u003eRAID layout at four LFF drives works differently than at twelve, because the small bay count changes the overhead math:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 10 (two mirrored pairs, striped).\u003c\/strong\u003e 50 percent overhead, roughly 24 TB usable with 12 TB drives. Our usual default at exactly four drives: the overhead is identical to RAID 6 but write performance is better and the rebuild scope is smaller.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 6 (dual parity).\u003c\/strong\u003e Same 50 percent overhead at four drives, roughly 22 TB usable with 12 TB drives. Preferred when read capacity matters more than write speed; dual parity protects against a second drive failing during the multi-day rebuild that large LFF drives require.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 5 (single parity).\u003c\/strong\u003e 25 percent overhead, roughly 36 TB usable with 12 TB drives, but not recommended at LFF capacity: single parity across multi-day rebuild windows is high risk. We will quote it on explicit request and flag the risk in writing.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eJBOD \/ HBA pass-through.\u003c\/strong\u003e When the storage abstraction lives in software (ZFS, software-defined NAS), the H240ar HBA is the right controller.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eThe 4-Bay LFF chassis has a boot problem: two of four bays for a mirrored OS volume is 50 percent of the storage budget, which is rarely acceptable. M.2 SATA on the HPE M.2 SSD enablement card is the answer on essentially every 4-Bay LFF production build, since it puts boot in a PCIe slot and preserves all four LFF bays for data. Front-bay boot is a fallback only when two bays of data are genuinely sufficient, and a single unmirrored boot drive is not a production pattern. We default to M.2 boot on every 4-Bay LFF quote and confirm the PCIe slot allocation accordingly.\u003c\/p\u003e\u003ch2\u003eStorage Controllers\u003c\/h2\u003e\u003cp\u003eThe same HPE modular Smart Array family runs here, with selection skewed toward the cache sizing a four-drive bulk-storage workload actually needs:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P440ar (2 GB flash-backed write cache, battery-backed).\u003c\/strong\u003e The right production controller at four LFF; the 2 GB cache is comfortably sized for a four-drive array. Mounts in the modular slot without consuming a PCIe slot.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array H240ar (HBA \/ pass-through).\u003c\/strong\u003e For software-defined NAS or ZFS file servers that want raw disks rather than hardware RAID.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P840 (4 GB flash-backed write cache, battery-backed).\u003c\/strong\u003e Available for write-intensive needs, but rarely required at four LFF; the P440ar is usually sufficient.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eB140i (embedded software RAID via the chipset).\u003c\/strong\u003e Acceptable for boot mirroring only; not a production data-RAID controller on a dual-socket platform.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eAll P-series controllers require the HPE Smart Storage Battery for write-back caching, and the flash-backed cache module is a wear item we verify and replace as part of build prep on any refurbished unit.\u003c\/p\u003e\u003ch2\u003eProcessors\u003c\/h2\u003e\u003cp\u003eOne or two sockets of Intel Xeon E5-2600 v3 (Haswell-EP) or v4 (Broadwell-EP) on the Grantley C610 platform, drop-in compatible within the socket but not mixable in one server. Core counts reach 18 per CPU on v3 and 22 per CPU on v4, with TDPs from roughly 55 W to 145 W. Bulk-storage roles rarely need the top bins, so CPU selection on this variant usually skews lower than on a dense SFF compute node:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2620 v4 (8 cores, 85 W).\u003c\/strong\u003e The common branch and edge pick; 16 cores across two sockets is plenty for file and infrastructure roles, and the low TDP sits easily inside the 1U envelope.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2640 v4 (10 cores, 90 W) or E5-2650 v4 (12 cores, 105 W).\u003c\/strong\u003e Mid-tier choices when the box runs compute alongside the storage role.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2680 v4 or higher.\u003c\/strong\u003e Reserved for consolidated branch or edge-analytics builds that pair four-LFF storage with meaningful compute.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eTop-bin CPUs still require the performance heatsink and high-performance fan kit, and a single-socket build exposes only 12 of the 24 DIMM slots and half the PCIe lanes, so the second socket matters whenever memory or expansion does.\u003c\/p\u003e\u003ch2\u003eMemory\u003c\/h2\u003e\u003cp\u003e24 DDR4 DIMM slots, 12 per CPU. The platform ceiling is 3 TB with 128 GB LRDIMMs; RDIMM is the mainstream choice, with 64 GB to 128 GB total covering most branch and edge bulk-storage workloads. ZFS-based file servers are the exception and benefit from more memory (128 GB to 256 GB) for ARC cache. Speed is population-dependent: DDR4-2400 on v4 and DDR4-2133 on v3 at one DIMM per channel, stepping down a tier at full two-DIMM-per-channel population. HPE Smart Memory is required for rated speeds; third-party DIMMs may train slower or fail to post. This platform predates Intel Optane persistent memory, so PMem is not part of the conversation here.\u003c\/p\u003e\u003ch2\u003eNetworking and PCIe Expansion\u003c\/h2\u003e\u003cp\u003eNetworking runs through the FlexibleLOM mezzanine, so the network personality is a build choice that does not cost a PCIe slot. For bulk-storage roles, 10 GbE FlexibleLOM (the 530FLR-SFP+ or 534FLR-SFP+ dual-port adapters) is the sensible default on backup-target and edge-analytics builds, while the 331FLR quad-port 1 GbE is acceptable for a pure branch file server. PCIe expansion is the 1U constraint: up to three PCIe Gen3 slots with both CPUs populated, and on this variant one of them is usually committed to the M.2 boot card. When more expansion than that is needed, the 2U DL380 Gen9 is the right move.\u003c\/p\u003e\u003ch2\u003eGPU Support\u003c\/h2\u003e\u003cp\u003eGPU support in the 1U envelope is limited to single-width, low-profile cards within the chassis power and thermal budget; there is no room for double-wide accelerators. On a bulk-storage LFF build a GPU is rarely part of the spec, but for the edge-analytics case a single low-profile accelerator such as an NVIDIA T-series card fits. Anything heavier (double-wide, multi-GPU, or high per-card power) belongs in the 2U DL380 Gen9 rather than this chassis.\u003c\/p\u003e\u003ch2\u003eManagement - iLO 4 Generation\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen9 uses iLO 4. iLO Standard is included for health monitoring, power control, and basic remote access; iLO Advanced is the licensed tier for full graphical remote console, virtual media, and remote KVM, and it is usually quoted separately, which matters for lights-out edge and branch sites where remote hands are scarce. Intelligent Provisioning handles firmware and driver deployment, and the Active Health System log is the first place to check a refurbished unit's history. On security, iLO 4 predates the Silicon Root of Trust introduced on Gen10; UEFI Secure Boot is the firmware integrity baseline, and a TPM module is available where a hardware root is required.\u003c\/p\u003e\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\u003cp\u003ePower comes from HPE Flex Slot hot-plug supplies in 500 W, 800 W, and 1400 W ratings at Platinum and Titanium efficiency, configured 1+1 for redundancy. Four LFF HDDs draw less storage-tier power than eight to ten SAS SSDs, so an 800 W pair is the standard production choice and 500 W is adequate for an entry-tier branch build on E5-2620-class CPUs. For edge sites without a rack UPS, the HPE Flex Slot battery backup module is worth adding for short power-event ride-through. Thermally the 1U chassis supports ASHRAE A3 (40 C) and A4 (45 C) inlet ranges; LFF HDDs run cooler than dense SSD arrays, and the wider ambient range helps at edge sites without dedicated cooling. We target a 25 C to 30 C inlet on production deployments.\u003c\/p\u003e\u003ch2\u003ePhysical Specs \u0026amp; Platform Notes\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eForm factor:\u003c\/strong\u003e 1U rack chassis, standard depth for four-post racks, with the usual rear allowance for cable management.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe expansion:\u003c\/strong\u003e up to three PCIe Gen3 slots with both CPUs populated, low-profile only; one slot is typically committed to the M.2 boot card on this variant.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eParts availability:\u003c\/strong\u003e excellent. Gen9 LFF drives, controllers, FlexibleLOM adapters, PSUs, and rails are deep on the secondary market. HPE active warranty support has ended, and third-party maintenance is the standard production support path in 2026.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAccessories we recommend:\u003c\/strong\u003e the \u003ca href=\"\/products\/hp-dl360-g8-g9-sff-1u-sliding-rails-679368-001-728437-001\"\u003eHPE 1U ball-bearing sliding rail kit (P\/N 679368-001 \/ 728437-001)\u003c\/a\u003e for the DL360 Gen9 chassis, a cable management arm, and the HPE M.2 SSD enablement card so boot stays off the four LFF bays.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePlatform notes:\u003c\/strong\u003e M.2 boot is effectively mandatory here to avoid spending half the bays on the OS; CPU hot-plug is not supported; LFF rebuild windows run into days at production load, so plan RAID 10 or RAID 6 rather than RAID 5; and NVMe is not a practical option on the LFF chassis.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003e\u003cstrong\u003eWhere it excels:\u003c\/strong\u003e This is the configuration for the genuine 1U-plus-LFF case: edge compute nodes that need local bulk storage, branch and ROBO servers consolidating file and infrastructure roles, small backup targets and surveillance recorders where a 2U storage box will not fit the rack. Four high-capacity NL-SAS drives in RAID 10 or RAID 6, an M.2 boot device, and a low-TDP dual-socket CPU pairing make a capable, rack-efficient branch server.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhere to look instead:\u003c\/strong\u003e If bulk capacity is the real driver and 1U is not a hard constraint, the \u003ca href=\"\/products\/hp-proliant-dl380-g9-12-bay-3-5-chassis\"\u003eDL380 Gen9 12-Bay 3.5\"\u003c\/a\u003e gives three times the bays at 2U. If SFF SSD performance matters more than LFF capacity, the \u003ca href=\"\/products\/hpe-proliant-dl360-g9-8-bay-2-5-chassis\"\u003eDL360 Gen9 8-Bay 2.5\"\u003c\/a\u003e is the standard 1U compute build, and the \u003ca href=\"\/products\/dl360-g9-2-5-10-bay-hot-swap-psu\"\u003eDL360 Gen9 10-Bay 2.5\"\u003c\/a\u003e is the densest SFF option. For current-generation 1U LFF with iLO 5, the \u003ca href=\"\/products\/hpe-proliant-dl360-g10-4-bay-3-5-build-your-own-server\"\u003eDL360 Gen10 4-Bay 3.5\"\u003c\/a\u003e is the step up.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eBottom line:\u003c\/strong\u003e A niche but useful build for the IT team that has decided, for good rack-space reasons, that bulk storage has to live in 1U. It is the right tool for edge, branch, ROBO, and small backup roles, and the wrong tool the moment capacity scaling or SFF performance becomes the priority. Size the four-bay capacity ceiling against the deployment's growth before committing, because field expansion past four LFF bays means a different chassis.\u003c\/p\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003eOnly four LFF bays: the raw capacity ceiling is roughly 56 TB with 14 TB drives, less after RAID. Capacity-led builds belong on the DL380 Gen9 12-Bay LFF.\u003c\/li\u003e\n\u003cli\u003eBoot consumes 50 percent of the bays in the front, so M.2 boot is effectively mandatory.\u003c\/li\u003e\n\u003cli\u003eLFF rebuild times run into days at production load; RAID 10 or RAID 6 strongly preferred, RAID 5 is high risk at this capacity.\u003c\/li\u003e\n\u003cli\u003eNVMe is not a practical option on the LFF chassis; for NVMe at 1U Gen9, use the SFF 8-Bay or 10-Bay variants.\u003c\/li\u003e\n\u003cli\u003eiLO 4 management, without the Silicon Root of Trust hardware attestation introduced on Gen10.\u003c\/li\u003e\n\u003cli\u003eDDR4 speed caps at DDR4-2400 (v4) or DDR4-2133 (v3) and steps down under full DIMM population; HPE Smart Memory required for rated speeds.\u003c\/li\u003e\n\u003cli\u003ePCIe Gen3 only, three slots in 1U, with one usually committed to the M.2 boot card.\u003c\/li\u003e\n\u003cli\u003eNo double-wide GPU support in 1U; single-width low-profile accelerators only.\u003c\/li\u003e\n\u003cli\u003eHPE active warranty has ended; production support is via third-party maintenance.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eThis server is right for\u003c\/th\u003e\n\u003cth\u003eConsider alternatives for\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eEdge compute with bulk local storage at 1U\u003c\/td\u003e\n\u003ctd\u003eMore than four LFF bays needed (use DL380 Gen9 12-Bay 3.5\")\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBranch and ROBO multi-role file servers\u003c\/td\u003e\n\u003ctd\u003eSFF SSD performance as the primary driver (use the 8-Bay or 10-Bay 2.5\")\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eRemote backup targets where 1U is required\u003c\/td\u003e\n\u003ctd\u003eNew deployments needing iLO 5 and Silicon Root of Trust\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eSmall to mid-scale surveillance NVR at 1U\u003c\/td\u003e\n\u003ctd\u003eWorkloads needing PCIe Gen4 NVMe bandwidth\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eLab, dev, and test bulk storage at 1U density\u003c\/td\u003e\n\u003ctd\u003eMore than roughly 56 TB raw at 1U\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed more LFF bays?\u003c\/strong\u003e The \u003ca href=\"\/products\/hp-proliant-dl380-g9-12-bay-3-5-chassis\"\u003eDL380 Gen9 12-Bay 3.5\"\u003c\/a\u003e is the 2U LFF platform for backup, file serving, and archive at scale.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed SFF performance in 1U Gen9?\u003c\/strong\u003e The \u003ca href=\"\/products\/hpe-proliant-dl360-g9-8-bay-2-5-chassis\"\u003eDL360 Gen9 8-Bay 2.5\"\u003c\/a\u003e is the standard 1U compute build, and the \u003ca href=\"\/products\/dl360-g9-2-5-10-bay-hot-swap-psu\"\u003eDL360 Gen9 10-Bay 2.5\"\u003c\/a\u003e is the densest SFF option.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed current-generation 1U LFF with iLO 5?\u003c\/strong\u003e The \u003ca href=\"\/products\/hpe-proliant-dl360-g10-4-bay-3-5-build-your-own-server\"\u003eDL360 Gen10 4-Bay 3.5\"\u003c\/a\u003e is the direct generational step up.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWorking to the tightest budget on a 1U Gen9 LFF build?\u003c\/strong\u003e The \u003ca href=\"\/products\/hpe-proliant-dl160-gen9-4-bay-lff-build-your-own\"\u003eDL160 Gen9 4-Bay 3.5\"\u003c\/a\u003e is the value-tier 1U Gen9 step down.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eStandardized on Dell?\u003c\/strong\u003e The \u003ca href=\"\/products\/dell-poweredge-r630-10-bay-chassis\"\u003eDell PowerEdge R630 10-Bay 2.5\"\u003c\/a\u003e is the equivalent 1U dual-socket Grantley platform from the same generation.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us the workload (edge compute, branch file server, ROBO, remote backup, or surveillance NVR), the drive capacity target (8, 10, 12, or 14 TB), the RAID layout (RAID 10 or RAID 6 are the usual picks at four drives), the controller preference, the M.2 boot configuration, the FlexibleLOM choice (1 or 10 GbE is typical here), the PSU configuration, and the quantity. We respond within 24 hours with a validated configuration including drive-capacity verification, RAID sizing math, and HPE Power Advisor sizing. Every refurbished unit ships with the Wholesale Servers 180-day warranty after a 12+ hour burn-in test, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951242764487,"sku":"BP-013615","price":412.24,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl360-gen9-4-bay-35-drives-188542.png?v=1765539623"},{"product_id":"hpe-proliant-dl360-g9-8-bay-2-5-chassis","title":"HPE ProLiant DL360 Gen9 8-Bay 2.5\" Drives [Gen9]","description":"\u003cp\u003eThe refurbished HPE ProLiant DL360 Gen9 8-Bay 2.5\" is the standard SFF configuration of HPE's Gen9 1U dual-socket platform, and the build we treat as the default DL360 Gen9 for general production. Eight 2.5\" SAS\/SATA hot-swap front bays sit ahead of the Intel Grantley platform: Intel Xeon E5-2600 v3 (Haswell-EP) or v4 (Broadwell-EP) processors on the C610 chipset, 24 DDR4 DIMM slots with a 3 TB memory ceiling, HPE modular Smart Array storage controllers, the FlexibleLOM network mezzanine, and iLO 4 out-of-band management. Eight bays is the right-sized storage footprint for the large majority of 1U dual-socket Gen9 workloads, where primary storage is networked and local disk handles boot, cache, and logs.\u003c\/p\u003e\u003cp\u003eThis is the full platform reference for the DL360 Gen9: processors, memory, storage controllers, networking, management, power, and an honest read on where a 2014-era platform belongs in a 2026 procurement decision. Where a build needs more than eight bays in the same 1U chassis, the 10-Bay configuration is the maximum-SFF option; where the workload wants large-format capacity, the 4-Bay 3.5\" covers it; and where eight bays of local storage are not enough, the 1U form factor is the wrong tool and the 2U DL380 Gen9 is the better answer. Each alternative is linked in context below.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty after a 12+ hour burn-in test, and volume pricing starts at 5 units.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL360 Gen9 Fits in the Family\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen9 is HPE's 1U dual-socket Gen9 workhorse, the 1U pair-partner to the 2U DL380 Gen9. Within the 1U DL360 Gen9 line there are three storage chassis: the 8-Bay 2.5\" SFF on this page, the higher-density \u003ca href=\"\/products\/dl360-g9-2-5-10-bay-hot-swap-psu\"\u003eDL360 Gen9 10-Bay 2.5\"\u003c\/a\u003e for the maximum SFF count in 1U, and the \u003ca href=\"\/products\/dl360-g9-3-5-4-bay-chassis\"\u003eDL360 Gen9 4-Bay 3.5\"\u003c\/a\u003e for large-format bulk capacity at the edge. The compute, memory, networking, and management platform is identical across all three; the only thing that changes is the front-bay layout.\u003c\/p\u003e\u003cp\u003eStep outside the 1U envelope and the decision is about expansion, not generation. When a workload needs more than three PCIe slots or more than ten drives, the \u003ca href=\"\/products\/hp-proliant-dl380-g9-2-5-8-bay-server\"\u003eDL380 Gen9 8-Bay 2.5\"\u003c\/a\u003e 2U companion is the right move: same Grantley platform, six PCIe slots, double-wide GPU support, and far more storage headroom. For a Dell-shop equivalent at the same 1U Gen9 tier, the \u003ca href=\"\/products\/dell-poweredge-r630-10-bay-chassis\"\u003eDell PowerEdge R630 10-Bay 2.5\"\u003c\/a\u003e is the direct counterpart: 1U, dual-socket, the same E5-2600 v3\/v4 Grantley generation.\u003c\/p\u003e\u003ch2\u003eStorage - 8 SFF Bays\u003c\/h2\u003e\u003cp\u003eEight 2.5\" SAS\/SATA hot-swap bays line the front of the chassis. This is the standard DL360 Gen9 SFF layout; the 10-Bay variant adds two more bays in the position the optical drive would otherwise occupy. NVMe is supported through the Express Bay option in specific front-bay positions, trading SAS\/SATA bay count for PCIe-attached NVMe lanes when low-latency local flash is the requirement.\u003c\/p\u003e\u003cp\u003eThe drive portfolio spans the full Gen9 SFF range: SAS SSDs in mixed-use and read-intensive endurance classes, cost-optimized SATA SSDs, 10K and 15K SAS HDDs for spinning capacity, self-encrypting (SED) variants for compliance-driven deployments, and NVMe via Express Bay. At full population, eight SFF bays deliver tens of terabytes of raw capacity depending on drive selection, with high-capacity SAS and SATA SSDs reaching the largest per-bay figures.\u003c\/p\u003e\u003cp\u003eCommon 8-Bay storage profiles we quote:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003evSphere cluster node, SAN datastore primary.\u003c\/strong\u003e 2x SSDs in RAID 1 for ESXi boot (or M.2 boot to preserve all eight bays), six SSDs for a vSAN cache device or local datastore. Primary VM storage lives on shared FC or iSCSI.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eHyper-V cluster node with CSV cache.\u003c\/strong\u003e 2x SSDs for Windows Server boot, six SSDs for CSV cache. Primary VM storage on Storage Spaces Direct or SAN.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eKubernetes worker host.\u003c\/strong\u003e 2x SSDs in RAID 1 for the OS, six SSDs for ephemeral local storage and container image layers. Persistent volumes ride a network CSI provider.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWeb and application tier.\u003c\/strong\u003e 2x SSDs in RAID 1 for the OS, four to six SSDs in RAID 5 or RAID 10 for application data, logs, and staging.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMid-tier SQL Server or Oracle, networked primary storage.\u003c\/strong\u003e 2x SSDs for the OS, 2x SSDs mirrored for tempdb or redo, four SSDs in RAID 10 for logs. Primary datafiles on SAN.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eInfrastructure and branch services.\u003c\/strong\u003e 2x SSDs in RAID 1 for the OS and roles, the remaining bays for supplementary capacity or left open for field growth.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eM.2 SATA via the HPE M.2 SSD enablement card is the cleanest boot pattern on this chassis: it consumes one PCIe slot but keeps all eight front bays available for data. The alternative is 2x SFF SSDs in RAID 1 in the front bays, which costs two of the eight bays. On an 8-bay build that is 25 percent of the storage budget spent on boot, so we default to M.2 boot on DL360 Gen9 8-Bay quotes unless the PCIe slot budget is already committed, in which case front-bay RAID 1 is the fallback.\u003c\/p\u003e\u003ch2\u003eStorage Controllers\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen9 runs HPE's modular Smart Array controller family. We quote the controller to the workload rather than defaulting to the top SKU:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P440ar (2 GB flash-backed write cache, battery-backed).\u003c\/strong\u003e The mainstream production default for mixed and read-heavy workloads. Mounts in the dedicated modular slot without consuming a standard PCIe slot.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P840 (4 GB flash-backed write cache, battery-backed).\u003c\/strong\u003e The write-intensive choice for transactional databases and heavy logging, where the larger cache earns its place. Occupies a PCIe slot.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array H240ar (HBA \/ pass-through mode).\u003c\/strong\u003e The right controller for software-defined and hyperconverged storage stacks (vSAN, Storage Spaces Direct, Ceph, ZFS) that want raw disks rather than hardware RAID.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eB140i (embedded software RAID via the chipset).\u003c\/strong\u003e OS-boot and light-duty only. We do not quote B140i as a production data-RAID controller; it is a boot-volume convenience, not a storage controller.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eAll P-series controllers require the HPE Smart Storage Battery for write-back caching, and the flash-backed write cache module is a documented wear item that should be checked on any refurbished unit. For any production array with a meaningful write path, the P440ar or P840 with battery-backed cache is the recommendation; pass-through HBA only when the storage layer is handled in software.\u003c\/p\u003e\u003ch2\u003eProcessors\u003c\/h2\u003e\u003cp\u003eOne or two sockets of Intel Xeon E5-2600 v3 (Haswell-EP) or v4 (Broadwell-EP) on the Grantley C610 platform. The two generations are drop-in compatible within the same socket but cannot be mixed in a single server. Core counts run up to 18 per CPU on v3 (E5-2699 v3) and up to 22 per CPU on v4 (E5-2699 v4), so a dual-socket v4 build reaches 44 cores. TDPs span roughly 55 W on low-power SKUs to 145 W on the top bins.\u003c\/p\u003e\u003cp\u003eThe 1U thermal envelope is the constraint that drives CPU selection here. Top-bin parts such as the E5-2699 v4 at 145 W and the high-frequency E5-2667 v4 at 135 W require the performance heatsink and the high-performance fan kit; we validate thermal headroom on every top-bin quote rather than assuming the standard heatsink will carry it. A common field error is ordering a high-TDP CPU into a chassis that shipped with standard cooling, so we confirm the heatsink and fan configuration matches the CPU bin before a build leaves.\u003c\/p\u003e\u003cp\u003eOne more trap worth naming: a single-socket DL360 Gen9 populates only half the platform. Single-CPU builds expose just 12 of the 24 DIMM slots and roughly half the PCIe lanes, so if memory capacity or expansion matters, the second socket is not optional.\u003c\/p\u003e\u003ch2\u003eMemory\u003c\/h2\u003e\u003cp\u003e24 DDR4 DIMM slots, 12 per CPU across the platform's memory channels. The ceiling is 3 TB using 128 GB LRDIMMs across all 24 slots; a more typical production build runs 32 GB or 64 GB RDIMMs, landing at 768 GB or 1.5 TB respectively. RDIMM is the mainstream choice; LRDIMM unlocks the highest capacities at a latency cost; NVDIMM-N is available as a niche persistence option on supported configurations. This platform predates Intel Optane persistent memory, which arrived with the later Cascade Lake generation, so PMem is not part of the DL360 Gen9 conversation.\u003c\/p\u003e\u003cp\u003eMemory speed is population-dependent. Broadwell-EP v4 CPUs run DDR4-2400 at one DIMM per channel; Haswell-EP v3 tops out at DDR4-2133. Fully populating to two DIMMs per channel steps the speed down a tier, which is the expected behavior, not a fault, and worth planning around when a build needs both maximum capacity and maximum bandwidth. HPE Smart Memory is required to hit rated speeds; third-party DIMMs may train at a lower speed or refuse to post.\u003c\/p\u003e\u003ch2\u003eNetworking and PCIe Expansion\u003c\/h2\u003e\u003cp\u003eNetworking runs through the FlexibleLOM mezzanine rather than fixed onboard ports, so the network personality is a build-spec choice that does not consume a PCIe slot. Options span the 331FLR quad-port 1 GbE for management-tier and branch builds, the 530FLR-SFP+ and 534FLR-SFP+ dual-port 10 GbE SFP+ adapters for mainstream production, 10GBASE-T for copper 10 GbE plants, and 25 GbE SFP28 for the densest east-west fabrics. For dense 1U production, dual-port 10 GbE FlexibleLOM is the typical default.\u003c\/p\u003e\u003cp\u003ePCIe expansion is where the 1U chassis shows its limits. With both CPUs populated the DL360 Gen9 offers up to three PCIe Gen3 slots through its riser options, and the slot budget gets allocated carefully: a discrete Smart Array controller, an M.2 boot card, and an add-in NIC or accelerator can fill the chassis quickly. When a workload needs more than three slots, that is the signal to move to the 2U DL380 Gen9 rather than fight the 1U slot count.\u003c\/p\u003e\u003ch2\u003eGPU Support\u003c\/h2\u003e\u003cp\u003eGPU and accelerator support in the DL360 Gen9 1U envelope is limited to single-width, low-profile cards within the chassis power and thermal budget; the NVIDIA T-series single-slot accelerators are the representative fit. There is no room for double-wide compute GPUs in 1U. Workloads that need full-height double-wide accelerators, multiple GPUs, or higher per-card power belong in the 2U DL380 Gen9 or a 4-socket DL560-class platform, where the chassis can deliver the airflow and slot width a large accelerator requires.\u003c\/p\u003e\u003ch2\u003eManagement - iLO 4 Generation\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen9 uses iLO 4, not the iLO 5 that arrived with Gen10. iLO Standard is included and covers health monitoring, power control, and basic remote access; iLO Advanced is the licensed tier that unlocks full graphical remote console, virtual media, and integrated remote KVM, and it is usually quoted separately. Intelligent Provisioning handles firmware and driver deployment, and the Active Health System log is the first place to look when diagnosing a refurbished unit's history.\u003c\/p\u003e\u003cp\u003eOn the security baseline, iLO 4 predates HPE's Silicon Root of Trust, which is a Gen10 hardware feature. UEFI Secure Boot is the firmware integrity baseline on Gen9, and a TPM module is available for platforms that need a hardware root for BitLocker or measured boot. Deployments with a hard requirement for Silicon Root of Trust hardware attestation should step to the Gen10 platform.\u003c\/p\u003e\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\u003cp\u003ePower comes from HPE Flex Slot hot-plug supplies in 500 W, 800 W, and 1400 W ratings at Platinum and Titanium efficiency, configured 1+1 for redundancy. The 800 W Flex Slot pair is the standard production configuration and carries a dual-socket build with a full complement of drives; 500 W is adequate for entry-tier single-CPU builds; 1400 W is reserved for top-bin CPUs paired with high-draw expansion. HPE Power Advisor sizing is part of every quote so the PSU matches the as-configured draw rather than a nameplate guess.\u003c\/p\u003e\u003cp\u003eThermally the chassis supports ASHRAE A3 (40 C) and A4 (45 C) inlet ranges with the performance heatsinks fitted, though we target a 25 C to 30 C inlet for service-life optimization on production deployments. Top-bin CPUs require the high-performance fan kit and a thermal confirmation at quote time; the 1U envelope leaves less headroom than the 2U platform, so cooling is validated rather than assumed.\u003c\/p\u003e\u003ch2\u003ePhysical Specs \u0026amp; Platform Notes\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eForm factor:\u003c\/strong\u003e 1U rack chassis, standard-depth, fitting standard four-post racks; cable management adds the usual rear depth allowance behind the chassis.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe expansion:\u003c\/strong\u003e up to three PCIe Gen3 slots with both CPUs populated, allocated through the riser options; low-profile cards only in the 1U envelope.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eParts availability:\u003c\/strong\u003e excellent. Gen9 is one of the most widely deployed enterprise generations ever shipped, so drives, controllers, FlexibleLOM adapters, PSUs, and rails are deep on the secondary market. HPE active warranty support has ended, and third-party maintenance is the standard production support path in 2026.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAccessories we recommend:\u003c\/strong\u003e the \u003ca href=\"\/products\/hp-dl360-g8-g9-sff-1u-sliding-rails-679368-001-728437-001\"\u003eHPE 1U SFF ball-bearing sliding rail kit (P\/N 679368-001 \/ 728437-001)\u003c\/a\u003e for tool-less rack mounting, a cable management arm for serviceability, and the high-performance fan and heatsink kit on any top-bin CPU build.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePlatform notes:\u003c\/strong\u003e the 8-bay and 10-bay backplanes differ, so a field upgrade from eight to ten bays is a cage-and-backplane job rather than a drop-in; CPU hot-plug is not supported; M.2 boot is strongly preferred over front-bay boot on this chassis to preserve data bays; and top-bin CPU builds need their cooling validated before deployment.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003e\u003cstrong\u003eWhere it excels:\u003c\/strong\u003e The 8-Bay DL360 Gen9 is the right answer for 1U dual-socket nodes where storage is networked and local disk carries boot, cache, and logs. It is a strong fit for vSphere and Hyper-V cluster nodes backed by SAN or hyperconverged datastores, Kubernetes worker pools, stateless web and application tiers in dense racks, mid-tier databases with networked primary storage, and the broad class of infrastructure services (domain controllers, DNS, monitoring) that want a reliable 1U box at low acquisition cost.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhere to look instead:\u003c\/strong\u003e If a build needs ten drives in 1U, start at the \u003ca href=\"\/products\/dl360-g9-2-5-10-bay-hot-swap-psu\"\u003eDL360 Gen9 10-Bay 2.5\"\u003c\/a\u003e rather than expanding bays later. If it needs more than three PCIe slots, double-wide GPUs, or substantially more storage, the \u003ca href=\"\/products\/hp-proliant-dl380-g9-2-5-8-bay-server\"\u003e2U DL380 Gen9\u003c\/a\u003e is the correct form factor. If the deployment requires iLO 5 and Silicon Root of Trust, step up to the \u003ca href=\"\/products\/dl360-g10-chassis\"\u003eDL360 Gen10 8-Bay 2.5\"\u003c\/a\u003e. Where budget is the hard constraint and a value-tier 1U Gen9 will do, the \u003ca href=\"\/products\/hpe-proliant-dl160-gen9-4-bay-lff-build-your-own\"\u003eDL160 Gen9 4-Bay 3.5\"\u003c\/a\u003e is the cost-floor option.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eBottom line:\u003c\/strong\u003e This is the default 1U Gen9 build for an organization that runs networked primary storage and wants dependable dual-socket compute at refurbished pricing. It suits the IT team standardizing a virtualization or container cluster on proven hardware, or filling out an infrastructure tier where the per-node cost matters more than the latest platform features. Buyers who need maximum local storage, heavy PCIe expansion, or current-generation security hardware should read the alternatives above before committing.\u003c\/p\u003e\u003ch2\u003eWhere the DL360 Gen9 Fits in 2026\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen9 launched in 2014 on the Grantley platform, which makes it roughly eleven to twelve years into its service life as of 2026. That is mature, not obsolete. The platform is two HPE generations behind the current Gen11 line and one behind Gen10 and Gen10 Plus, and HPE's own active warranty coverage has lapsed, so the honest framing is that this is a cost-driven acquisition where the workload fits comfortably inside the E5-2600 v3\/v4 envelope and third-party maintenance covers production support.\u003c\/p\u003e\u003cp\u003eThat describes a lot of real workloads. Dev, test, and staging environments, branch and edge compute, infrastructure services, lab build-outs, and budget-constrained virtualization clusters all run well on Gen9 hardware at a fraction of current-generation cost. Where the workload needs the newer platform's memory bandwidth, PCIe Gen4, larger core counts, or Silicon Root of Trust security, the \u003ca href=\"\/products\/dl360-g10-chassis\"\u003eDL360 Gen10\u003c\/a\u003e is the step up. The decision is a straightforward cost-versus-capability tradeoff, and for a large share of 1U dual-socket workloads the Gen9 still lands on the right side of it.\u003c\/p\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003eiLO 4 management, without the Silicon Root of Trust hardware attestation introduced on Gen10.\u003c\/li\u003e\n\u003cli\u003eDDR4 speed caps at DDR4-2400 (v4) or DDR4-2133 (v3), and steps down a tier under full two-DIMM-per-channel population.\u003c\/li\u003e\n\u003cli\u003ePCIe Gen3 only, and just three slots in the 1U chassis, which is a tight expansion budget.\u003c\/li\u003e\n\u003cli\u003eThe flash-backed write cache module on Smart Array P-series controllers is a wear item and should be verified on any refurbished unit.\u003c\/li\u003e\n\u003cli\u003ev3 and v4 CPUs cannot be mixed in the same server, and single-socket builds expose only half the DIMM slots and PCIe lanes.\u003c\/li\u003e\n\u003cli\u003eHPE Smart Memory is required to reach rated DIMM speeds; third-party memory may train slower or fail to post.\u003c\/li\u003e\n\u003cli\u003eNetworking is FlexibleLOM-only with no fixed onboard ports, so a FlexibleLOM adapter is mandatory, not optional.\u003c\/li\u003e\n\u003cli\u003eThe 1U thermal envelope limits cooling headroom; top-bin CPUs require the performance fan and heatsink kit and a thermal check.\u003c\/li\u003e\n\u003cli\u003eNo double-wide GPU support in 1U; single-width low-profile accelerators only.\u003c\/li\u003e\n\u003cli\u003eMoving from eight to ten bays in the field is a cage-and-backplane change, not a drive add, so size the bay count up front.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eThis server is right for\u003c\/th\u003e\n\u003cth\u003eConsider alternatives for\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eVM and container cluster nodes with networked datastores at 1U density\u003c\/td\u003e\n\u003ctd\u003eBuilds needing ten drives in 1U (use the 10-Bay 2.5\")\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eStateless web and application tiers in dense compute racks\u003c\/td\u003e\n\u003ctd\u003eWorkloads needing more than three PCIe slots (use the 2U DL380 Gen9)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eKubernetes worker hosts and infrastructure services\u003c\/td\u003e\n\u003ctd\u003eDouble-wide GPU or multi-GPU compute (use DL380 Gen9 or DL560)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMid-tier databases with primary storage on SAN\u003c\/td\u003e\n\u003ctd\u003eDatabase hosts needing large local primary storage\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBranch, edge, lab, dev, and staging deployments\u003c\/td\u003e\n\u003ctd\u003eNew deployments requiring iLO 5 and Silicon Root of Trust\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eCost-driven 1U Gen9 standardization on proven hardware\u003c\/td\u003e\n\u003ctd\u003eWorkloads that need current-generation memory bandwidth or PCIe Gen4\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed ten SFF bays in the same 1U chassis?\u003c\/strong\u003e The \u003ca href=\"\/products\/dl360-g9-2-5-10-bay-hot-swap-psu\"\u003eDL360 Gen9 10-Bay 2.5\"\u003c\/a\u003e is the maximum-SFF density option on the platform.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed large-format capacity at the edge?\u003c\/strong\u003e The \u003ca href=\"\/products\/dl360-g9-3-5-4-bay-chassis\"\u003eDL360 Gen9 4-Bay 3.5\"\u003c\/a\u003e takes LFF drives in the same 1U body for bulk-capacity branch and backup roles.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed more PCIe slots or more storage than 1U allows?\u003c\/strong\u003e The \u003ca href=\"\/products\/hp-proliant-dl380-g9-2-5-8-bay-server\"\u003eDL380 Gen9 8-Bay 2.5\"\u003c\/a\u003e is the 2U companion with six PCIe slots and double-wide GPU support.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed current-generation 1U with iLO 5 and Silicon Root of Trust?\u003c\/strong\u003e The \u003ca href=\"\/products\/dl360-g10-chassis\"\u003eDL360 Gen10 8-Bay 2.5\"\u003c\/a\u003e is the direct generational step up.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWorking to the tightest budget on a 1U Gen9 build?\u003c\/strong\u003e The \u003ca href=\"\/products\/hpe-proliant-dl160-gen9-4-bay-lff-build-your-own\"\u003eDL160 Gen9 4-Bay 3.5\"\u003c\/a\u003e is the value-tier 1U Gen9 step down.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eStandardized on Dell?\u003c\/strong\u003e The \u003ca href=\"\/products\/dell-poweredge-r630-10-bay-chassis\"\u003eDell PowerEdge R630 10-Bay 2.5\"\u003c\/a\u003e is the equivalent 1U dual-socket Grantley platform from the same generation.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us the workload, the CPU generation preference (v3 versus v4), the CPU TDP context (the 1U thermal envelope matters for top-bin choices), the memory target, the storage configuration (drive types, RAID layout, controller preference, and M.2 versus front-bay boot), the FlexibleLOM choice (1, 10, or 25 GbE), the PSU configuration, and the quantity. We respond within 24 hours with a validated configuration that includes HPE Power Advisor sizing, thermal validation on high-TDP builds, and third-party maintenance coordination when you want it. Every refurbished unit ships with the Wholesale Servers 180-day warranty after a 12+ hour burn-in test, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951242928327,"sku":"BP-013616","price":307.83,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl360-gen9-8-bay-25-drives-104158.png?v=1765539623"},{"product_id":"dl360-g9-2-5-10-bay-hot-swap-psu","title":"HPE ProLiant DL360 Gen9 10-Bay 2.5\" Drives [Gen9]","description":"\u003cp\u003eThe refurbished HPE ProLiant DL360 Gen9 10-Bay 2.5\" is the maximum-SFF-density configuration of HPE's Gen9 1U dual-socket line: ten 2.5\" SAS\/SATA hot-swap bays, the most front storage the 1U chassis holds. It runs the same Intel Grantley platform as the rest of the family, Intel Xeon E5-2600 v3 (Haswell-EP) or v4 (Broadwell-EP) on the C610 chipset, up to 22 cores per CPU on v4 (44 cores across two sockets), 24 DDR4 DIMM slots with a 3 TB ceiling, HPE modular Smart Array controllers, the FlexibleLOM mezzanine, and iLO 4 management. The two extra bays over the standard 8-Bay build are the point: this is the variant to pick when SFF capacity inside a single rack unit is the driver.\u003c\/p\u003e\n\n\u003cp\u003eThis page covers what is specific to the 10-bay layout, the high-density storage profiles it enables and where the extra two bays earn their place. The compute, memory, networking, and management platform is shared across every DL360 Gen9 chassis; the \u003ca href=\"\/products\/hpe-proliant-dl360-g9-8-bay-2-5-chassis\"\u003eDL360 Gen9 8-Bay 2.5\"\u003c\/a\u003e is the primary page for the family and the standard build for compute-driven 1U workloads that do not need the extra bays.\u003c\/p\u003e\n\n\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty after a 12+ hour burn-in test, and volume pricing starts at 5 units.\u003c\/p\u003e\n\n\u003chr\u003e\n\n\u003ch2\u003eWhen 10 SFF Bays Is the Right Density\u003c\/h2\u003e\n\u003cp\u003eTen 2.5\" bays is the maximum SFF count the DL360 Gen9 1U chassis supports, and the two bays beyond the standard eight come from the area a slim optical drive would otherwise occupy. The 10-Bay is the right pick when local SFF capacity matters within the 1U footprint, rather than the compute-first case the 8-Bay covers:\u003c\/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eDense vSphere cluster nodes with vSAN.\u003c\/strong\u003e Boot off M.2 or a front-bay pair, two cache SSDs, and six to eight capacity SSDs in the vSAN disk group, all in 1U. The extra bays let a hyperconverged node carry a useful local capacity tier without going to 2U.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eHyper-V and Storage Spaces Direct nodes at rack density.\u003c\/strong\u003e The same HCI pattern on the Microsoft side, where S2D ReadyNode-style designs benefit from the extra capacity disks per 1U node.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWeb and application tier in dense racks.\u003c\/strong\u003e A boot pair plus four to eight SSDs for application data and logs, at 1U per server, for deployments running many instances behind load balancers.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eHyperscale-style compute pools.\u003c\/strong\u003e Kubernetes worker pools and container hosts where local SSD carries ephemeral data and image layers while persistent volumes ride the network.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMid-tier databases with local working storage.\u003c\/strong\u003e Boot, a mirrored tempdb or redo pair, and additional SSDs for local working sets, with primary datafiles on SAN.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eEdge and ROBO where one 1U box does everything.\u003c\/strong\u003e Ten bays cover branch file services, infrastructure roles, and local virtualization on a single rack-efficient server.\u003c\/li\u003e\n\u003c\/ul\u003e\n\u003cp\u003eIf the workload is compute-driven and does not need ten bays, the \u003ca href=\"\/products\/hpe-proliant-dl360-g9-8-bay-2-5-chassis\"\u003eDL360 Gen9 8-Bay 2.5\"\u003c\/a\u003e is the standard build. If bulk large-format capacity is the requirement, the \u003ca href=\"\/products\/dl360-g9-3-5-4-bay-chassis\"\u003eDL360 Gen9 4-Bay 3.5\"\u003c\/a\u003e takes LFF drives in the same 1U body. And if storage or expansion needs exceed what 1U holds, the 2U \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e is the move.\u003c\/p\u003e\n\n\u003ch2\u003eStorage - 10 SFF Bays\u003c\/h2\u003e\n\u003cp\u003eTen 2.5\" SAS\/SATA hot-swap bays across the front of the chassis, the maximum SFF configuration for the 1U DL360 Gen9. NVMe is supported through the Express Bay option in specific positions (up to four SFF NVMe), trading SAS\/SATA bay count for PCIe-attached NVMe lanes. At full population, ten SFF bays deliver tens of terabytes of raw capacity depending on drive choice, with high-capacity SAS and SATA SSDs reaching the largest per-bay figures.\u003c\/p\u003e\n\u003cp\u003eThe drive portfolio spans the full Gen9 SFF range: SAS SSDs in mixed-use and read-intensive endurance classes, cost-optimized SATA SSDs, 10K and 15K SAS HDDs for moderate-IOPS spinning storage, self-encrypting (SED) variants for compliance, and NVMe via Express Bay. Common 10-Bay storage profiles we quote:\u003c\/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003evSAN node.\u003c\/strong\u003e M.2 or front-bay boot, two cache SSDs, six to eight capacity SSDs in the disk group, primary VM storage distributed across the cluster.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eS2D node.\u003c\/strong\u003e A boot pair, cache and capacity SSDs split per the Storage Spaces Direct design, with the extra bays improving per-node capacity.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWeb and app tier.\u003c\/strong\u003e 2x SSDs in RAID 1 for the OS, four to eight SSDs in RAID 5 or RAID 10 for application data and logs.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eContainer host.\u003c\/strong\u003e A boot pair plus local SSDs for ephemeral data and image layers; persistent volumes on a network CSI provider.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMid-tier database.\u003c\/strong\u003e An OS pair, mirrored tempdb or redo, additional SSDs for local working sets, primary datafiles on SAN.\u003c\/li\u003e\n\u003c\/ul\u003e\n\u003ch3\u003eBoot Drives\u003c\/h3\u003e\n\u003cp\u003eM.2 SATA via the HPE M.2 SSD enablement card is the cleanest boot pattern: it sits in a PCIe slot and preserves all ten front bays for data. The alternative is 2x SFF SSDs in RAID 1 in the front bays, which costs two of the ten bays, a 20 percent bite versus 25 percent on the 8-Bay. The DL360 Gen9 chassis has no rear drive bays, so M.2 and front-bay are the two practical boot options, and we default to M.2 boot on 10-Bay quotes where the PCIe budget allows so the full ten bays stay available for the storage tier.\u003c\/p\u003e\n\n\u003ch2\u003eStorage Controllers\u003c\/h2\u003e\n\u003cp\u003eThe DL360 Gen9 takes HPE's modular Smart Array controllers, which mount in a chassis-specific slot rather than a PCIe expansion position. That matters more here than on the 2U platform because the 1U chassis has only three PCIe slots total, so keeping the storage controller off PCIe leaves all three slots for networking, an HBA, or an accelerator.\u003c\/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P440ar (2 GB flash-backed write cache, battery-backed).\u003c\/strong\u003e The mainstream production controller; full hardware RAID 0\/1\/5\/6\/10\/50\/60 in the modular slot. The right pick for most 10-Bay production builds.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array H240ar (HBA \/ pass-through, modular).\u003c\/strong\u003e The HCI and software-defined choice (vSAN, Storage Spaces Direct, Ceph), clean SAS pass-through without consuming a PCIe slot.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P840 (PCIe, 4 GB flash-backed write cache, battery-backed).\u003c\/strong\u003e For write-intensive workloads where the 2 GB cache is not enough; it occupies a PCIe slot, so it is a deliberate tradeoff against the tight 1U slot budget.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eB140i (embedded software RAID via the chipset).\u003c\/strong\u003e Boot mirroring only; not a production data-RAID controller on a dual-socket platform.\u003c\/li\u003e\n\u003c\/ul\u003e\n\u003cp\u003eAll P-series controllers require the HPE Smart Storage Battery for write-back caching. The flash-backed cache module is a wear item with a finite service life, and many refurbished units arrive with batteries past spec, so we check battery state and replace aged modules as part of build prep.\u003c\/p\u003e\n\n\u003ch2\u003eProcessors\u003c\/h2\u003e\n\u003cp\u003eOne or two sockets of Intel Xeon E5-2600 v3 (Haswell-EP) or v4 (Broadwell-EP) on the Grantley C610 platform, drop-in compatible within the socket but not mixable in one server. Single-socket builds are supported but expose only 12 of the 24 DIMM slots and a reduced PCIe count, so two sockets is the production standard. The 1U thermal envelope is the real constraint: the chassis carries CPUs up to 145 W, but the top bins need the performance heatsink and high-performance fan kit and an inlet-temperature check, because the 1U margin is tighter than the 2U platform. Common picks:\u003c\/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2620 v4 (8 cores, 85 W).\u003c\/strong\u003e Entry-tier production; 16 cores at two sockets, the easiest thermal envelope, the budget and branch choice.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2650 v4 (12 cores, 105 W).\u003c\/strong\u003e Balanced mid-tier; 24 cores at modest TDP, the general-purpose 1U dual-socket default.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2680 v4 (14 cores, 120 W).\u003c\/strong\u003e Production mainstream; 28 cores at two sockets, comfortable in the 1U envelope on the standard heatsink.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2667 v4 (8 cores, 135 W, 3.2 GHz base).\u003c\/strong\u003e High-frequency, low-core-count for per-core-licensed software; requires the performance heatsink.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2699 v4 (22 cores, 145 W).\u003c\/strong\u003e Top bin; 44 cores at two sockets is achievable but at the edge of the 1U thermal envelope, so it requires the performance heatsink, performance fans, and an inlet-temperature confirmation. We validate thermal headroom on every top-bin quote.\u003c\/li\u003e\n\u003c\/ul\u003e\n\u003cp\u003eA common field error is dropping a high-TDP CPU into a chassis that shipped with standard cooling, so we confirm the heatsink and fan kit match the CPU bin before a build leaves.\u003c\/p\u003e\n\n\u003ch2\u003eMemory\u003c\/h2\u003e\n\u003cp\u003e24 DDR4 DIMM slots, 12 per CPU, the same memory architecture as the 2U DL380 Gen9; HPE did not cut DIMM count for the 1U form factor on Gen9. The ceiling is 3 TB with 128 GB LRDIMMs across all 24 slots, while a typical production build runs 32 GB or 64 GB RDIMMs for 768 GB or 1.5 TB. RDIMM is the mainstream choice and LRDIMM unlocks the top capacities at a latency cost; NVDIMM-N is available on v4 configurations as a niche persistence option. Speed is population-dependent: DDR4-2400 on v4 and DDR4-2133 on v3 at one DIMM per channel, stepping down a tier at full two-DIMM-per-channel population. HPE Smart Memory is required for rated speeds, and this platform predates Intel Optane persistent memory, so PMem is not part of the conversation here.\u003c\/p\u003e\n\n\u003ch2\u003eNetworking and PCIe Expansion\u003c\/h2\u003e\n\u003cp\u003eThe DL360 Gen9 uses FlexibleLOM as the primary networking mezzanine, with no embedded fixed ports alongside it, so the FlexibleLOM choice is part of the build spec and does not consume a PCIe slot. Options span the 331FLR quad-port 1 GbE, the 530FLR-SFP+ and 534FLR-SFP+ dual-port 10 GbE SFP+ adapters, 10GBASE-T, and 25 GbE SFP28 FlexFabric. Dense 1U racks usually pair with top-of-rack 10 GbE, so 10 GbE FlexibleLOM is the typical default; 1 GbE is acceptable for branch and edge.\u003c\/p\u003e\n\u003cp\u003ePCIe expansion is the 1U constraint: up to three PCIe Gen3 slots with both CPUs populated, versus six on the 2U DL380 Gen9. A single-socket build populates only two of the three. The slot budget is tight, so it gets allocated deliberately between an add-in HBA, a discrete controller, an accelerator, or specialty cards. When a workload needs more than three slots, the DL380 Gen9 is the right form factor.\u003c\/p\u003e\n\n\u003ch2\u003eGPU Support\u003c\/h2\u003e\n\u003cp\u003eGPU support in the 1U envelope is single-width, low-profile cards only, within the chassis power and thermal budget, with an NVIDIA T-series single-slot accelerator as the representative fit. There is no room for double-wide compute GPUs in 1U. Workloads that need double-wide accelerators, multiple GPUs, or higher per-card power belong in the 2U DL380 Gen9 or a 4-socket DL560-class platform, where the chassis can deliver the slot width and airflow a larger accelerator requires.\u003c\/p\u003e\n\n\u003ch2\u003eManagement - iLO 4 Generation\u003c\/h2\u003e\n\u003cp\u003eThe DL360 Gen9 ships with iLO 4, the same management generation as the rest of the Gen9 line, which is a real value point for a fleet standardizing on Gen9. iLO Standard covers health monitoring, power control, IPMI, SNMP telemetry, and the Active Health System log; iLO Advanced is the licensed tier for full graphical remote console and virtual media, and for a 1U lights-out deployment it is rarely optional given the operational benefit. We quote iLO Advanced explicitly when the deployment needs it.\u003c\/p\u003e\n\u003cp\u003eThe architectural difference from Gen10 is the security baseline: iLO 4 predates the Silicon Root of Trust hardware verification introduced with iLO 5. UEFI Secure Boot is the firmware integrity baseline on Gen9, and a TPM module is available where a hardware root is required. Deployments under compliance frameworks that require platform attestation should treat this as a documented gap versus Gen10 and either add compensating controls or step up.\u003c\/p\u003e\n\n\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\n\u003cp\u003eHPE Flex Slot hot-plug supplies in 1+1 redundancy. The 500 W Platinum supply suits low-TDP single-CPU or modest dual-CPU builds; the 800 W Platinum or Titanium pair is the standard production choice and carries a dual-socket build with full memory and ten SSDs, including E5-2680 or E5-2690 v4; the 1400 W Platinum is the pick for top-bin E5-2699 v4 or NVMe-heavy builds. HPE Power Advisor sizing is part of every quote so the supply matches the as-configured draw.\u003c\/p\u003e\n\u003cp\u003eThermally the 1U chassis runs hotter than 2U at equivalent CPU TDP because the envelope is tighter. ASHRAE A3 (40 C) and A4 (45 C) extended ambient operation are supported on most configurations with performance heatsinks, though the top of A4 eats operational margin. We target a 25 C to 30 C inlet for service-life optimization on production deployments and validate thermals on every top-bin CPU quote.\u003c\/p\u003e\n\n\u003ch2\u003ePhysical Specs \u0026amp; Platform Notes\u003c\/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eForm factor:\u003c\/strong\u003e 1U rack chassis, standard depth for four-post racks, with the usual rear allowance for cable management.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe expansion:\u003c\/strong\u003e up to three PCIe Gen3 slots with both CPUs populated (two with a single CPU), low-profile in the 1U envelope; the modular controller slot keeps the Smart Array off PCIe.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eParts availability:\u003c\/strong\u003e excellent. Gen9 SFF drives, modular controllers, FlexibleLOM adapters, PSUs, and rails are deep on the secondary market. HPE active warranty support has ended, and third-party maintenance is the standard production support path in 2026.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAccessories we recommend:\u003c\/strong\u003e the \u003ca href=\"\/products\/hp-dl360-g8-g9-sff-1u-sliding-rails-679368-001-728437-001\"\u003eHPE 1U SFF ball-bearing sliding rail kit (P\/N 679368-001 \/ 728437-001)\u003c\/a\u003e for tool-less mounting, a cable management arm, and the HPE M.2 SSD enablement card so boot stays off the ten front bays.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePlatform notes:\u003c\/strong\u003e the two extra bays over the 8-Bay come from the optical-drive area and share the same backplane family; there are no rear drive bays on this chassis; CPU hot-plug is not supported; and top-bin CPU builds need their cooling validated before deployment.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch2\u003eOur Assessment\u003c\/h2\u003e\n\u003cp\u003e\u003cstrong\u003eWhere it excels:\u003c\/strong\u003e The 10-Bay is the configuration for hyperconverged and storage-leaning 1U nodes: vSAN and Storage Spaces Direct clusters that want a real local capacity tier per node, dense web and application tiers, and edge or ROBO boxes that consolidate compute and storage into a single rack unit. When the design calls for the most SFF capacity HPE puts in a 1U Gen9 chassis, this is the build.\u003c\/p\u003e\n\u003cp\u003e\u003cstrong\u003eWhere to look instead:\u003c\/strong\u003e If the workload is compute-driven and does not need ten bays, the \u003ca href=\"\/products\/hpe-proliant-dl360-g9-8-bay-2-5-chassis\"\u003eDL360 Gen9 8-Bay 2.5\"\u003c\/a\u003e is the standard and more economical build. For large-format bulk capacity, the \u003ca href=\"\/products\/dl360-g9-3-5-4-bay-chassis\"\u003eDL360 Gen9 4-Bay 3.5\"\u003c\/a\u003e is the LFF option. For more PCIe slots, double-wide GPUs, or more than ten drives, the \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e at 2U is the form factor, and for current-generation 1U with iLO 5 and Silicon Root of Trust, the \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003eDL360 Gen10 10-Bay 2.5\"\u003c\/a\u003e is the step up.\u003c\/p\u003e\n\u003cp\u003e\u003cstrong\u003eBottom line:\u003c\/strong\u003e This is the maximum-density 1U Gen9 SFF build, for the team that wants local storage capacity without giving up rack density. It suits HCI cluster nodes and storage-leaning compute at refurbished pricing, and it is more chassis than a compute-only workload needs, where the 8-Bay is the better-value pick. Buyers who need current-generation security hardware, PCIe Gen4, or active HPE support should weigh the Gen10 step before committing.\u003c\/p\u003e\n\n\u003ch2\u003eWhere the DL360 Gen9 Fits in 2026\u003c\/h2\u003e\n\u003cp\u003eThe DL360 Gen9 launched in 2014 on Haswell-EP with a Broadwell-EP refresh in 2016, which puts it roughly eleven to twelve years into service as of 2026. HPE active warranty and ProSupport on Gen9 hardware has ended for both v3 and v4 builds, and third-party maintenance from established providers is the standard production support path. Gen10 (Skylake-SP and Cascade Lake-SP) introduced iLO 5 with Silicon Root of Trust, faster DDR4, and per-core performance gains, while Gen10 Plus and Gen11 brought PCIe Gen4 and DDR5.\u003c\/p\u003e\n\u003cp\u003eThe honest framing is a cost-versus-capability call. For new mission-critical deployments that need current security baselines, faster memory, PCIe Gen4, or active HPE support, the \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003eDL360 Gen10\u003c\/a\u003e is the right answer. The Gen9 10-Bay earns its place extending an existing Gen9 fleet, in rack-density-driven workloads, in lab and staging that mirrors Gen9 production, and in budget-driven deployments where the workload fits the platform and the broad Gen9 parts supply is operationally valuable.\u003c\/p\u003e\n\n\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\n\u003cul\u003e\n\u003cli\u003eHPE active warranty and ProSupport on Gen9 has ended for both v3 and v4 builds; production support is via third-party maintenance.\u003c\/li\u003e\n\u003cli\u003eiLO 4, not iLO 5, so no Silicon Root of Trust; firmware integrity rests on UEFI Secure Boot, a documented gap for platform-attestation compliance.\u003c\/li\u003e\n\u003cli\u003eDDR4 speed caps at DDR4-2400 (v4) or DDR4-2133 (v3) and steps down under full DIMM population; HPE Smart Memory required for rated speeds.\u003c\/li\u003e\n\u003cli\u003ePCIe expansion is three slots maximum; workloads needing more belong on the 2U DL380 Gen9 with six slots.\u003c\/li\u003e\n\u003cli\u003eNo double-wide GPU support in 1U; single-width low-profile accelerators only.\u003c\/li\u003e\n\u003cli\u003ePCIe Gen3 only; PCIe Gen4 needs Gen10 Plus or Gen11.\u003c\/li\u003e\n\u003cli\u003eThe 1U thermal envelope is tighter than 2U; top-bin CPUs require the performance heatsink and fan kit and an inlet check.\u003c\/li\u003e\n\u003cli\u003eThe flash-backed write cache module on P-series controllers is a wear item and is verified on every refurbished unit.\u003c\/li\u003e\n\u003cli\u003eNetworking is FlexibleLOM-only with no embedded fixed ports, so a FlexibleLOM adapter is mandatory.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\n\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eThis server is right for\u003c\/th\u003e\n\u003cth\u003eConsider alternatives for\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eDense 1U vSphere and Hyper-V nodes with local capacity\u003c\/td\u003e\n\u003ctd\u003eCompute-only 1U workloads that do not need ten bays (use the 8-Bay 2.5\")\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003evSAN and Storage Spaces Direct nodes at rack density\u003c\/td\u003e\n\u003ctd\u003eWorkloads needing more than three PCIe slots (use the 2U DL380 Gen9)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eWeb and application tier in dense racks\u003c\/td\u003e\n\u003ctd\u003eDouble-wide GPU or multi-GPU compute (use DL380 Gen9 or DL560)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eKubernetes worker and container hosts at 1U\u003c\/td\u003e\n\u003ctd\u003eNew deployments requiring iLO 5 and Silicon Root of Trust\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eEdge and ROBO consolidating compute and storage in 1U\u003c\/td\u003e\n\u003ctd\u003eLarge-format bulk capacity (use the 4-Bay 3.5\" or DL380 Gen9 LFF)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eCapacity-add to an existing DL360 Gen9 fleet\u003c\/td\u003e\n\u003ctd\u003eWorkloads needing current memory bandwidth or PCIe Gen4\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\n\n\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eCompute-driven and do not need ten bays?\u003c\/strong\u003e The \u003ca href=\"\/products\/hpe-proliant-dl360-g9-8-bay-2-5-chassis\"\u003eDL360 Gen9 8-Bay 2.5\"\u003c\/a\u003e is the standard 1U build for the family.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed large-format capacity in 1U?\u003c\/strong\u003e The \u003ca href=\"\/products\/dl360-g9-3-5-4-bay-chassis\"\u003eDL360 Gen9 4-Bay 3.5\"\u003c\/a\u003e takes LFF drives for edge and backup roles.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed more PCIe slots or more than ten drives?\u003c\/strong\u003e The \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e is the 2U companion with six PCIe slots.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed current-generation 1U with iLO 5 and Silicon Root of Trust?\u003c\/strong\u003e The \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003eDL360 Gen10 10-Bay 2.5\"\u003c\/a\u003e is the direct generational step up.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWorking to the tightest budget on a 1U Gen9 build?\u003c\/strong\u003e The \u003ca href=\"\/products\/hpe-proliant-dl160-gen9-4-bay-lff-build-your-own\"\u003eDL160 Gen9 4-Bay 3.5\"\u003c\/a\u003e is the value-tier 1U Gen9 step down.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eStandardized on Dell?\u003c\/strong\u003e The \u003ca href=\"\/products\/dell-poweredge-r630-10-bay-chassis\"\u003eDell PowerEdge R630 10-Bay 2.5\"\u003c\/a\u003e is the equivalent 1U dual-socket Grantley platform from the same generation.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\n\u003cp\u003eTell us the workload, the CPU generation preference (v3 versus v4), the CPU TDP context (the 1U thermal envelope matters for top-bin choices), the memory target, the storage configuration (drive types, RAID layout, controller preference, and M.2 versus front-bay boot), the FlexibleLOM choice (1, 10, or 25 GbE), the PSU configuration, and the quantity. We respond within 24 hours with a validated configuration including HPE Power Advisor sizing, thermal validation on high-TDP builds, and third-party maintenance coordination when you want it. Every refurbished unit ships with the Wholesale Servers 180-day warranty after a 12+ hour burn-in test, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951242830023,"sku":"BP-003825","price":144.01,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl360-gen9-10-bay-25-drives-742204.png?v=1765539623"},{"product_id":"dl360-g10-chassis","title":"HPE ProLiant DL360 Gen10 8-Bay 2.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL360 Gen10 8-Bay 2.5\" is the mainstream 1U SFF configuration in the Gen10 lineup and the most-deployed DL360 variant across HPE customer sites. Eight 2.5\" SAS\/SATA hot-swap bays, dual-socket Intel Xeon Scalable (Skylake-SP or Cascade Lake-SP), 24 DDR4 DIMM slots, iLO 5 with Silicon Root of Trust, and the same Smart Array storage controller family as the rest of the Gen10 line. For virtualization hosts, application servers, scale-out compute nodes, and most workloads where 8 SFF bays cover the storage design, this is the standard 1U HPE pick - and almost always the right one over the 10-Bay variant.\u003c\/p\u003e\u003cp\u003eThis is the sibling page to the \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003eDL360 Gen10 10-Bay 2.5\"\u003c\/a\u003e canonical. The full platform vocabulary - Purley socket support, memory architecture, controller comparisons, iLO 5 details, FlexibleLOM networking, GPU constraints, generational positioning - lives on that page and applies identically here. This page focuses on what's specific to the 8-Bay configuration: when it's the right pick, how the bay count maps to common workloads, and the cost-versus-flexibility tradeoff against the 10-Bay.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhy the 8-Bay Is the Right Default\u003c\/h2\u003e\u003cp\u003eEight 2.5\" SFF bays in 1U is the configuration HPE built the DL360 around. The 10-Bay is a density variant for specific workloads where two extra bays measurably change the cluster math; the 8-Bay is the version that fits the bulk of real-world 1U deployments. If you're not running Ceph at scale, vSAN with two disk groups per host, or a distributed database that genuinely wants 10 drives per node, the 8-Bay covers your storage design with no compromise.\u003c\/p\u003e\u003cp\u003eThe cost difference is modest but real - the 10-Bay backplane and additional drive cage carry a premium, plus two more drives in your bill of materials if you're filling the bays. For a virtualization host running 4-6 SSDs for local datastore plus an M.2 boot device, the 8-Bay is the right answer. For an application server with 2-4 SSDs and primary data on SAN, the 8-Bay has surplus capacity. The 10-Bay earns its premium when the extra bays land in a specific cluster math problem; the 8-Bay wins everywhere else.\u003c\/p\u003e\u003cp\u003eBay-count map for common 8-Bay deployments:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003evSphere host with local SSD datastore:\u003c\/strong\u003e 2 drives RAID 1 for OS + 4-6 SSDs RAID 10 for datastore, 0-2 bays held back for spares. Comfortable fit.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eHyper-V cluster node with CSV on iSCSI\/FC:\u003c\/strong\u003e 2 drives RAID 1 for OS + 4 SSDs for Hyper-V Replica or Cluster Shared Storage cache, remaining bays unused or M.2 boot frees all 8 bays for data. Plenty of room.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eKubernetes worker with local PV provisioning:\u003c\/strong\u003e M.2 boot + 4-8 SSDs for CSI-attached persistent volumes. Bays scale with the per-node PV workload.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003evSAN single-disk-group host:\u003c\/strong\u003e 1 cache SSD + 4-7 capacity drives is a single vSAN disk group, perfectly served by 8 bays. Two disk groups per host pushes you toward the 10-Bay, which is exactly why the 10-Bay exists.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eApplication server with local SSD storage:\u003c\/strong\u003e 2 drives RAID 1 OS + 2-4 SSDs for application\/log volumes. 8 bays is more than enough.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eVeeam proxy or distributed component:\u003c\/strong\u003e 2 drives RAID 1 + 2-4 SSDs for staging or cache. Typical proxy build fits cleanly in 8 bays.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eStorage and Controllers\u003c\/h2\u003e\u003cp\u003eEight 2.5\" SAS\/SATA hot-swap bays on the standard backplane. SAS SSDs, SATA SSDs, SAS HDDs at 10K and 15K, and NL-SAS SFF drives are all supported. Controller options are the full Smart Array Gen10 family covered on the \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003e10-Bay canonical page\u003c\/a\u003e: P408i-a SR (2 GB FBWC, mainstream production controller), P816i-a SR (4 GB FBWC, write-heavy or tri-mode requirements), E208i-a SR (HBA mode for vSAN, Ceph, S2D, ZFS), and S100i SR (software RAID, boot-only).\u003c\/p\u003e\u003cp\u003eFor 8-Bay deployments specifically, the P408i-a is the right controller in 90%+ of cases. Its 2 GB FBWC is sized appropriately for the I\/O patterns 8 SFF drives produce in a 1U chassis. The P816i-a's larger cache earns its place at higher drive counts (16+ bays in the DL380 platform) where cache pressure becomes a real bottleneck; in the 1U 8-Bay envelope, the P408i-a almost always covers the working set. The E208i-a HBA is the right pick for any software-defined storage workload, and S100i should only be used for OS boot mirroring when no Smart Array P-series is in the build.\u003c\/p\u003e\u003cp\u003eFBWC battery is a wear item with roughly 5-year service life - same caveat that applies to every P-series Smart Array, documented on the canonical page and disclosed on every build quote.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eBoot Drive Options\u003c\/h2\u003e\u003cp\u003eHPE M.2 enablement kit is the cleanest boot solution on the DL360 Gen10 8-Bay. It mounts in a PCIe slot, takes a SATA M.2 drive (typically 480 GB), and frees all 8 SFF bays for data. Strongly recommended when you're using all 8 bays for the workload's data tier.\u003c\/p\u003e\u003cp\u003eAlternative: 2x SFF SAS or SATA SSDs in two of the 8 bays under hardware RAID 1, consuming 2 bays for OS. This is the right approach when the M.2 kit isn't available or when you're not using all 8 bays for data and don't mind giving up two of them for OS mirroring. For a build with 4-6 data drives, the 2-bay OS mirror is perfectly reasonable.\u003c\/p\u003e\u003cp\u003eHPE NS204i-p (the dedicated dual-NVMe M.2 boot device) is a Gen10 Plus and Gen11 feature, not a Gen10 option. If you need NVMe boot specifically on Gen10, it's via the M.2 enablement kit (SATA M.2) or via a PCIe-attached NVMe drive routed to a specific bay - not via NS204i-p.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors, Memory, and Networking\u003c\/h2\u003e\u003cp\u003eSame as the canonical: dual-socket LGA 3647 Purley platform, 1st Gen and 2nd Gen Xeon Scalable drop-in compatible, 24 DDR4 DIMM slots, DDR4-2933 on Gold 6200\/5222 (DDR4-2666 on the rest), up to 1.5 TB RDIMM or 3 TB LRDIMM dual-socket, HPE Smart Memory required for rated speed operation. The full processor and memory documentation lives on the \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003e10-Bay canonical page\u003c\/a\u003e.\u003c\/p\u003e\u003cp\u003eNetworking: HPE FlexibleLOM mezzanine slot (does not consume PCIe) for the primary network interface, 3 PCIe Gen3 slots in the standard riser configuration for HBAs, additional NICs, or up to two single-width T4-class GPUs. The 1U PCIe constraint is the same as the 10-Bay; the bay-count difference doesn't change the PCIe layout.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eThe 8-Bay vs. 10-Bay Decision\u003c\/h2\u003e\u003cp\u003eThree questions decide it:\u003c\/p\u003e\u003col\u003e  \u003cli\u003e\n\u003cstrong\u003eDoes your storage design fit in 8 bays?\u003c\/strong\u003e If yes - and for most virtualization, application, and compute-primary deployments, yes - the 8-Bay is the right choice. The 10-Bay's premium isn't justified.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eAre you running vSAN with two disk groups per host, or Ceph at 10 OSDs per 1U?\u003c\/strong\u003e If yes, the 10-Bay's two extra bays land in a specific cluster math problem. Take the 10-Bay.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eIs the per-node data-drive count in your design 9 or 10?\u003c\/strong\u003e This usually means a distributed database or storage workload with explicit 1U density requirements. Take the 10-Bay.\u003c\/li\u003e\n\u003c\/ol\u003e\u003cp\u003eIf the answer to all three is no, the 8-Bay is the cleaner pick. Same processors, same memory, same management, same controllers - just two fewer bays and a slightly lower price.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e    \u003cth\u003eThis server excels at\u003c\/th\u003e    \u003cth\u003eConsider alternatives for\u003c\/th\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Standard 1U virtualization hosts (vSphere, Hyper-V, KVM)\u003c\/td\u003e    \u003ctd\u003e❌ vSAN 2-disk-group hosts (use 10-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Application servers with local SSD datastores\u003c\/td\u003e    \u003ctd\u003e❌ Ceph at 10 OSDs per 1U (use 10-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Kubernetes worker pools with M.2 boot + 4-8 PVs\u003c\/td\u003e    \u003ctd\u003e❌ LFF drive requirements in 1U (use 4-Bay 3.5\")\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Scale-out compute clusters in HPE shops\u003c\/td\u003e    \u003ctd\u003e❌ More than 8 SFF bays needed (use DL380)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Veeam proxies and distributed backup infrastructure\u003c\/td\u003e    \u003ctd\u003e❌ GPU compute beyond 2x T4 (use DL380)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ SAN-connected compute with minimal local storage\u003c\/td\u003e    \u003ctd\u003e❌ PCIe Gen4 NVMe bandwidth required (use Gen10 Plus)\u003c\/td\u003e  \u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cp\u003eSame generational caveats as the rest of the DL360 Gen10 family: PCIe Gen3 (modern Gen4 NVMe runs at half rated bandwidth), DDR4-2933 maximum memory speed (Ice Lake-SP and Sapphire Rapids beat it), 1U thermal envelope constrains top-bin Platinum CPUs, FBWC battery is a wear item, iLO Advanced licensing is typically separate on refurbished units, HPE Smart Memory required for rated DIMM speed. The \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003e10-Bay canonical\u003c\/a\u003e covers each of these in detail. Same platform, same generation, same constraints - the only thing that changes between 8-Bay and 10-Bay is the bay count itself.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed 10 SFF bays at 1U density?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003eDL360 Gen10 10-Bay 2.5\" (canonical)\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed LFF drives in 1U?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl360-g10-4-bay-3-5-build-your-own-server\"\u003eDL360 Gen10 4-Bay 3.5\"\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed more PCIe slots, more bays, or GPU compute?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\"\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDell shop alternative?\u003c\/strong\u003e → \u003ca href=\"\/products\/dell-poweredge-r640-8bay-2-5-build-your-own\"\u003eDell PowerEdge R640 8-Bay 2.5\"\u003c\/a\u003e - architectural counterpart on the Dell side\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us the workload, CPU SKU preference (or per-socket core count and clock target), memory capacity, storage configuration including controller preference, network topology and FlexibleLOM choice, and quantity. We respond within 24 hours, every refurbished unit ships with the 180-day warranty and 12+ hour burn-in, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951242862791,"sku":"BP-013618","price":460.84,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl360-gen10-8-bay-25-drives-885647.png?v=1765539623"},{"product_id":"hp-proliant-dl380-g9-12-bay-3-5-chassis","title":"HPE ProLiant DL380 Gen9 12-Bay 3.5\" Drives","description":"\u003cp\u003eThe refurbished HPE ProLiant DL380 Gen9 12-Bay 3.5\" is the large-form-factor (LFF) member of the DL380 Gen9 family - twelve 3.5\" SAS\/SATA hot-swap bays in the standard 2U chassis, built for bulk capacity rather than SFF performance density. It runs the same Intel Xeon E5-2600 v3 (Haswell-EP) or v4 (Broadwell-EP) processors on the Grantley platform with the C610 chipset, the same 24 DDR4 DIMM slots and 3 TB memory ceiling, the same modular Smart Array controllers, the same FlexibleLOM networking, and the same iLO 4 management as the rest of the Gen9 line. What changes is the storage architecture: twelve large-capacity NL-SAS or SAS HDDs deliver a high-capacity bulk pool - up to roughly 168 TB raw with 14 TB drives on supported firmware - which makes this the right HPE Gen9 platform for backup targets, archive storage, capacity-tier file servers, Veeam repositories, and any workload where bulk HDD capacity matters more than IOPS-per-dollar.\u003c\/p\u003e\u003cp\u003eWithin the family, the sixteen-bay 2.5\" build is the mainstream SFF default; this twelve-bay build is the LFF answer for deployments where capacity-per-dollar and sequential throughput matter more than random-IOPS performance. For the SFF configurations, the \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e is the mainstream companion. This page carries the full platform detail in its own right and focuses on the LFF variant: when twelve 3.5\" bays is the right form factor, the bulk-capacity workload patterns, and the controller and RAID decisions that change at twelve high-capacity HDDs.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhen 12 LFF Bays Is the Right Form Factor\u003c\/h2\u003e\u003cp\u003eLFF (3.5\") versus SFF (2.5\") is a capacity-versus-performance tradeoff: LFF HDDs deliver far higher per-drive capacity at lower cost-per-TB, but slower per-drive IOPS than SFF SAS or SSDs. The 12-Bay 3.5\" earns its place when:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eVeeam Backup \u0026amp; Replication repositories.\u003c\/strong\u003e 12x 10-12 TB NL-SAS in RAID 6 delivers roughly 90-110 TB usable. Veeam's write-intensive sequential workload suits LFF NL-SAS; per-drive IOPS is not the bottleneck for backup targets.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eFile servers with a bulk-capacity requirement.\u003c\/strong\u003e 12x 8-12 TB NL-SAS in RAID 6 for AD-integrated SMB\/NFS shares and document repositories - a common consolidation target for organizations folding several older file servers onto one dense host.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNAS-style storage gateways.\u003c\/strong\u003e TrueNAS, OpenZFS, or the Windows Server file role delivers a large per-host footprint at materially lower cost than dedicated appliances. The HBA-mode H241 is the right pattern for ZFS.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eLong-term archive and compliance retention.\u003c\/strong\u003e Sequential-write, infrequent-read workloads - record retention, log archives, regulatory data, legal hold - where capacity-per-dollar beats the access-time gap versus SSD.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDistributed file system nodes (Ceph, MinIO, GlusterFS).\u003c\/strong\u003e Twelve large OSDs per 2U node for scale-out clusters where total cluster capacity matters more than per-OSD IOPS.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSurveillance and video storage.\u003c\/strong\u003e Write-heavy sequential NVR\/VMS workloads; twelve high-capacity bays hold months of multi-camera retention on one chassis.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eCapacity tier behind SSD caching.\u003c\/strong\u003e The bulk HDD tier in a two-tier design, paired with a separate SSD-tier host or storage-tiering software.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eIf the workload is performance-sensitive (random-IOPS databases, VDI, latency-bound application data), the SFF variants are correct - the \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e for the SFF sweet spot or the \u003ca href=\"\/products\/dl380-g9-2-5-24-bay-chassis\"\u003eDL380 Gen9 24-Bay 2.5\"\u003c\/a\u003e for maximum SSD density. LFF NL-SAS does not match SFF SSD performance; the 12-Bay LFF is purpose-built for the bulk-capacity pattern.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage - 12 LFF Bays\u003c\/h2\u003e\u003cp\u003eTwelve 3.5\" SAS\/SATA hot-swap bays across the front of the chassis. The LFF chassis also supports a rear 3 LFF expansion (rear-3-LFF kit) for 15 total LFF bays, or a rear 2 SFF kit for OS boot drives that preserves all front-bay capacity. The optional Universal Media Bay is an SFF-chassis accessory only and is not available here.\u003c\/p\u003e\u003cp\u003eDrive options span the full Gen9 LFF portfolio:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eNL-SAS HDDs.\u003c\/strong\u003e The bulk-capacity workhorse: 4, 6, 8, 10, 12, and 14 TB MDL (midline) drives across the Gen9 lifecycle, with later firmware supporting larger. 7,200 RPM, optimized for sequential workloads and capacity-per-dollar.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSAS HDDs at 10K and 15K.\u003c\/strong\u003e Higher per-drive IOPS than NL-SAS at a lower capacity ceiling - 10K LFF tops out near 2.4 TB, 15K near 900 GB. Used when the LFF chassis is required but the workload needs IOPS headroom over pure NL-SAS.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eLFF SSDs.\u003c\/strong\u003e SAS or SATA SSDs in 3.5\" carriers. Available but rarely the right choice - SFF chassis configurations deliver SSD performance more efficiently. They make sense only when LFF is locked in for fleet or certification reasons.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSelf-encrypting drives (SED).\u003c\/strong\u003e For compliance-regulated bulk storage needing drive-level encryption (HIPAA archives, regulated retention).\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eRAID at 12 LFF\u003c\/h3\u003e\u003cp\u003eRAID layout at 12 LFF NL-SAS differs from SFF SSD because rebuild times on large drives run in days, not hours. A 12 TB rebuild can take 24-48 hours under load, during which the array is degraded and a second failure on the volume causes data loss. The defaults:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 6 (production default).\u003c\/strong\u003e Dual parity tolerates two simultaneous failures - the right margin given multi-day rebuilds. 12x 12 TB yields roughly 110 TB usable. Strongly preferred for production bulk storage.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 60 (two striped RAID 6 groups of six).\u003c\/strong\u003e Narrows rebuild scope to six drives. Slightly higher overhead; useful at 14 TB+ where single-RAID-6 rebuild windows become painful.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 10 (six striped mirrors).\u003c\/strong\u003e Faster writes and rebuilds at 50% capacity overhead. Rarely right at 12 LFF NL-SAS - the LFF workloads are sequential-write, where the RAID 6 write penalty is acceptable and capacity loss matters more.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRAID 5 (single parity).\u003c\/strong\u003e Not recommended at LFF capacity - single-drive parity with multi-day rebuilds is high risk. We quote it only on explicit request, with the risk flagged in writing.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eJBOD \/ HBA pass-through.\u003c\/strong\u003e When redundancy lives in software (ZFS, Ceph, MinIO). The H241 HBA is the right pick.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eThe LFF backplane does not accept front-bay SFF drives, so boot options are:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eRear-bay 2 SFF kit.\u003c\/strong\u003e The standard pattern: 2x SFF SSDs in RAID 1 in the rear bays, preserving all twelve front bays for data.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eM.2 SATA via the HPE M.2 enablement card.\u003c\/strong\u003e M.2 boot in a PCIe slot - consumes a slot but no drive bays.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e2x LFF SSDs in front bays.\u003c\/strong\u003e Possible but wasteful, spending two large-capacity bays on the OS. Not recommended.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eWe default to the rear-bay 2 SFF kit on every 12-Bay LFF quote unless the customer specifies otherwise.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Controllers\u003c\/h2\u003e\u003cp\u003eController selection at 12 LFF NL-SAS is weighted toward larger write cache and HBA-mode capability:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P840ar (4 GB FBWC).\u003c\/strong\u003e The standard production controller. 4 GB of flash-backed write cache absorbs sustained sequential writes from backup workloads and handles drive-type variation across twelve HDDs - the right pick for hardware RAID at this scale.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P840 (4 GB FBWC, PCIe plug-in).\u003c\/strong\u003e Same silicon in PCIe form, for dual-controller builds or when the modular slot holds another card.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array H241 (HBA mode, PCIe plug-in).\u003c\/strong\u003e Clean SAS pass-through for ZFS, Ceph, MinIO, and software-defined storage - the right choice for distributed file system nodes.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P440ar (2 GB FBWC).\u003c\/strong\u003e Supported, but 2 GB is undersized for sustained-write LFF. Acceptable for read-heavy archival roles; not the default for write-intensive bulk storage.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDynamic Smart Array B140i (embedded software RAID).\u003c\/strong\u003e Boot-mirroring only; not for production data.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThe HPE Smart Storage Battery is required with any P-series controller. The Gen9 FBWC battery is a wear item with a documented 5-7 year service life; we disclose battery state on every quote and replace past-spec cache modules as part of build prep.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors\u003c\/h2\u003e\u003cp\u003e1 or 2 sockets of Intel Xeon E5-2600 v3 (Haswell-EP) or v4 (Broadwell-EP) on the C610 Grantley chipset. Mixing v3 and v4 is not supported - all CPUs must match, though a field upgrade replacing both at once is fine. Single-socket builds halve the DIMM slots (12 instead of 24) and cut PCIe to three slots, so 2-socket is the production standard. Bulk-storage builds usually skew to lower- or mid-bin Broadwell-EP, since the workload is sequential-I\/O bound rather than compute-bound:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2620 v4 (8 cores, 85W).\u003c\/strong\u003e A common backup-target and archive pick - 16 cores at 2S is ample for a Veeam proxy\/repository role, and the low TDP saves power and cooling.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2640 v4 (10 cores, 90W, 2.4 GHz).\u003c\/strong\u003e Balanced mid-tier; 20 cores at 2S handles file-server consolidation alongside backup.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2650 v4 (12 cores, 105W).\u003c\/strong\u003e Mid-tier production with headroom for distributed file system nodes (Ceph OSD, MinIO) where some per-node compute matters.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2680 v4 (14c\/120W) and E5-2690 v4 (14c\/135W).\u003c\/strong\u003e Reserved for bulk storage paired with real compute - a consolidated file-plus-app host, or a backup proxy with restore-side processing.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE5-2667 v4 (8 cores, 135W, 3.2 GHz).\u003c\/strong\u003e The high-frequency, per-core-licensing pick when a database engine shares the host; uncommon on pure bulk storage. Haswell-EP v3 equivalents cost less with a DDR4-2133 cap.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eMemory\u003c\/h2\u003e\u003cp\u003e24 DDR4 DIMM slots (12 per CPU; only 12 with a single CPU). RDIMM and LRDIMM are supported but cannot be mixed; the maximum is 3 TB with 128 GB LRDIMMs across all 24 slots on v4. HPE DDR4 Smart Memory is required for rated speeds - third-party DDR4 runs slower, documented HPE behavior across Gen9.\u003c\/p\u003e\u003cp\u003eSpeed depends on CPU generation and population: v3 caps at DDR4-2133, v4 at DDR4-2400, and full 24-DIMM population drops to DDR4-1866 or 1600 depending on rank. Bulk-storage roles need modest memory - 64-128 GB suits file servers and backup targets. Higher capacity (256-512 GB) fits ZFS ARC cache, scale-out Veeam, or hosts running additional workloads alongside storage. HPE Persistent Memory (NVDIMM-N, 8\/16 GB) is supported on v4 but uncommon on capacity-tier builds.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking and PCIe Expansion\u003c\/h2\u003e\u003cp\u003eThe embedded HPE 4-port 1 GbE 331i adapter is standard and consumes no slot. The optional FlexibleLOM mezzanine supports 10 GbE SFP+ (530FLR\/534FLR), 10 GBASE-T, 25 GbE SFP28, and converged FlexFabric. Unlike the DL580 Gen9, Wake-on-LAN works on both the embedded 1 GbE and the FlexibleLOM. PCIe expansion is three PCIe Gen3 slots with one CPU, six with both populated; the secondary riser requires the second processor. Slots accept cards up to 150W, higher with the supplemental power-cable kit. On a backup-target or file-server build, a 10 GbE or 25 GbE FlexibleLOM is usually the first expansion priority - ingest bandwidth, not local IOPS, is the typical bottleneck.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eGPU Support\u003c\/h2\u003e\u003cp\u003eGPUs are uncommon on a bulk-storage build, but the LFF chassis carries the same PCIe Gen3 and 2U thermal envelope as the family, so accelerators are available when a storage host doubles as a light compute or media node:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSingle-width accelerators.\u003c\/strong\u003e Cards like the NVIDIA Tesla T4 (70W, single-slot, passive) for transcoding, inference, or video analytics on a surveillance or media host. They fit standard riser positions and need no GPU power-cable kit.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDouble-width GPUs.\u003c\/strong\u003e Passively cooled Gen9-era cards (NVIDIA M40, M60, K80-class) require the high-performance heatsink and the GPU power-cable kit (PN 669777-B21); plan up to two, subject to PSU sizing and drive-tier power draw.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eThermal envelope.\u003c\/strong\u003e GPU builds need performance heatsinks and the high-performance fan kit; extended-ambient headroom narrows with double-wide cards alongside twelve spinning HDDs. We validate inlet temperature at quote time.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eFPGA and specialty cards.\u003c\/strong\u003e Accepted within the 150W per-slot limit. PCIe Gen3 bandwidth is the ceiling - workloads needing PCIe Gen4 belong on Gen10 Plus or Gen11.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eManagement - iLO 4 Generation\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen9 ships with HPE iLO 4: remote console (an iLO Advanced license enables full graphical KVM), virtual media, IPMI, SNMP telemetry, Active Health System logging, and HPE OneView compatibility - the same iLO 4 generation across the Gen9 line, part of the platform's operational-standardization value. The key difference from Gen10 is that iLO 4 has no Silicon Root of Trust; that hardware-anchored firmware-verification chain arrived with iLO 5 on Gen10. UEFI Secure Boot is supported and is the right pattern for production Gen9, with compensating controls where a framework requires firmware-integrity attestation. iLO Advanced is typically a separate cost and rarely optional for production data-center deployments; we quote it explicitly.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\u003cp\u003eThe same HPE Flex Slot power supplies as the rest of the family - 500W, 800W, or 1400W Platinum\/Titanium in 1+1 redundant configurations, plus the optional HPE Flexible Slot Battery Backup. The 12-Bay LFF draws more storage-tier power than SFF SSD builds: roughly 7-10W per spinning HDD versus 5-8W per SAS SSD. A fully populated 12-Bay LFF with mid-tier dual CPUs, 256 GB of RAM, and 12x 12 TB NL-SAS draws about 500-700W sustained.\u003c\/p\u003e\u003cp\u003e800W Flex Slot PSUs in 1+1 cover all common 12-Bay LFF builds; 500W is marginal, and 1400W is overkill unless paired with high-TDP CPUs or GPUs. We default to 2x 800W Platinum and run the HPE Power Advisor against every configuration to validate sizing. Thermal: ASHRAE A3 (40 C) is comfortable for LFF builds; A4 (45 C) is supported but shortens drive service life and is rarely the right envelope where drive longevity matters.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePhysical Specs \u0026amp; Platform Notes\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eForm factor:\u003c\/strong\u003e 2U rackmount, standard-depth Gen9 enclosure shared across the DL380 Gen9 bay-count variants; with the cable management arm installed, plan for additional rear clearance.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe expansion:\u003c\/strong\u003e up to six PCIe Gen3 slots with both CPUs populated (three with one CPU), split full-height and low-profile across the primary and secondary risers; the secondary riser requires the second processor.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eParts availability:\u003c\/strong\u003e excellent. The DL380 Gen9 shipped in one of the largest 2U install bases of any generation, so drives, PSUs, risers, heatsinks, FlexibleLOM cards, and Smart Array controllers are widely available, and third-party maintenance spares depth is strong in major metros.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAccessories we recommend:\u003c\/strong\u003e the 2U LFF ball-bearing sliding rail kit (see the \u003ca href=\"\/products\/hp-dl380-dl560-g9-g10-lff-sliding-rails\"\u003eDL380 \/ DL560 G9\/G10 2U LFF sliding rail kit\u003c\/a\u003e), the rear-2-SFF kit for boot placement, the rear-3-LFF kit when fifteen LFF bays are needed, and the GPU power-cable kit (PN 669777-B21) on the rare accelerator build.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePlatform notes:\u003c\/strong\u003e CPU hot-plug is not supported, and v3\/v4 CPUs cannot be mixed. The LFF backplane does not accept front-bay SFF drives, so boot lives in the rear bays or on M.2. Confirm FlexibleLOM and drive-backplane compatibility against the specific build at quote time.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003e\u003cstrong\u003eWhere it excels:\u003c\/strong\u003e The 12-Bay LFF DL380 Gen9 is the right answer for bulk-capacity dual-socket workloads where sequential throughput and cost-per-TB outweigh random IOPS - Veeam and other backup repositories, general-purpose and consolidated file servers, long-term archive and compliance retention, NAS-style gateways on TrueNAS or OpenZFS, distributed file system nodes, surveillance and video storage, and the capacity tier behind an SSD cache. Twelve large NL-SAS drives in a single 2U chassis deliver a dense, affordable pool that SFF chassis cannot match on cost-per-TB.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhere to look instead:\u003c\/strong\u003e If the workload is performance-sensitive, the SFF members are the right tool - the \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e for the SFF sweet spot, the \u003ca href=\"\/products\/dl380-g9-2-5-24-bay-chassis\"\u003eDL380 Gen9 24-Bay 2.5\"\u003c\/a\u003e for maximum SSD density, and the \u003ca href=\"\/products\/hp-proliant-dl380-g9-2-5-8-bay-server\"\u003eDL380 Gen9 8-Bay 2.5\"\u003c\/a\u003e for compute-driven nodes with networked storage. New mission-critical deployments needing iLO 5 Silicon Root of Trust, PCIe Gen4, or DDR4-2933+ bandwidth should move to the \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eDL380 Gen10 12-Bay 3.5\"\u003c\/a\u003e. Budget-driven LFF deployments that can trade features for cost should compare the \u003ca href=\"\/products\/hpe-proliant-dl180-gen9-lff-build-your-own\"\u003eHPE ProLiant DL180 Gen9 LFF\u003c\/a\u003e value tier. Dell-standardized shops should compare the \u003ca href=\"\/products\/dell-poweredge-r730xd-12-bay-3-5-chassis\"\u003eDell PowerEdge R730xd 12-Bay 3.5\"\u003c\/a\u003e, the equivalent 2U Grantley LFF platform at the same bay count.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eBottom line:\u003c\/strong\u003e The 12-Bay LFF is the capacity member of the family - the build you choose when the storage is the point and the budget is measured in dollars-per-terabyte. The typical customer is standing up a Veeam repository, consolidating file servers, building a TrueNAS or Ceph capacity node, or sizing surveillance retention. Buy it when bulk HDD capacity and sequential throughput are what the workload needs; step to the SFF companions the moment random-IOPS performance is in the picture, and step to Gen10 when current-generation security and memory bandwidth matter.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSame Gen9 platform limits as the rest of the family.\u003c\/strong\u003e HPE active warranty has ended; iLO 4 has no Silicon Root of Trust; DDR4 caps at 2400 (v4) or 2133 (v3) and drops further at full population; PCIe Gen3 only; the FBWC battery is a wear item; v3\/v4 mixing is unsupported; HPE Smart Memory is required for rated speeds.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eLFF rebuild times run in days, not hours.\u003c\/strong\u003e A 10-14 TB NL-SAS rebuild under load takes 24-48+ hours. RAID 5 is high risk at this capacity; RAID 6 or 60 is the right answer, and you should plan for extended degraded-state windows.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNo front-bay boot.\u003c\/strong\u003e The LFF backplane does not accept front SFF drives, so boot is the rear-2-SFF kit or M.2 - factor it into the build.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNo Universal Media Bay on the LFF chassis.\u003c\/strong\u003e The Media Bay is SFF-chassis-only, so front-panel VGA and USB are not available on this variant.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eLFF SSDs are not the efficient SSD form factor.\u003c\/strong\u003e If the workload genuinely needs SSD performance, the SFF chassis is the right platform; LFF SSDs exist but rarely make sense.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDrive-capacity ceiling depends on firmware and certification.\u003c\/strong\u003e Maximum per-drive capacity is bounded by HPE firmware support and drive certification; we verify the ceiling for the specific build at quote time.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eThis server is right for\u003c\/th\u003e\n\u003cth\u003eConsider alternatives for\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ Veeam and backup repositories\u003c\/td\u003e\n\u003ctd\u003e❌ VM cluster nodes with SAN datastores (use 8-Bay SFF)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ File servers with a bulk-capacity requirement\u003c\/td\u003e\n\u003ctd\u003e❌ VDI hosts requiring SFF performance (use 16-Bay SFF)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ Long-term archive and compliance retention\u003c\/td\u003e\n\u003ctd\u003e❌ HCI nodes (use 16- or 24-Bay SFF)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ Distributed file system nodes (Ceph, MinIO, ZFS)\u003c\/td\u003e\n\u003ctd\u003e❌ Database hosts with a random-IOPS workload\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ Surveillance and video storage\u003c\/td\u003e\n\u003ctd\u003e❌ New mission-critical deployments needing iLO 5\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e✅ Capacity tier behind SSD caching\u003c\/td\u003e\n\u003ctd\u003e❌ Workloads requiring more than 12-15 LFF bays\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed SFF (2.5\") for SSD performance density?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e - the SFF sweet spot for VDI, HCI, and database hosts with local SSD.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed a compute-driven node with networked storage?\u003c\/strong\u003e → \u003ca href=\"\/products\/hp-proliant-dl380-g9-2-5-8-bay-server\"\u003eDL380 Gen9 8-Bay 2.5\"\u003c\/a\u003e - fewer SFF bays for SAN-backed compute.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed maximum SFF density at Gen9?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g9-2-5-24-bay-chassis\"\u003eDL380 Gen9 24-Bay 2.5\"\u003c\/a\u003e - 24 SFF bays for HCI and high-density local SSD.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWant a lower-cost LFF value tier?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl180-gen9-lff-build-your-own\"\u003eHPE ProLiant DL180 Gen9 LFF\u003c\/a\u003e - cost-optimized 2U dual-socket Gen9 LFF.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed Gen10 LFF with iLO 5, DDR4-2933, and Silicon Root of Trust?\u003c\/strong\u003e → \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eDL380 Gen10 12-Bay 3.5\"\u003c\/a\u003e - current-generation 2U LFF.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDell shop alternative at the same Gen9 12 LFF tier?\u003c\/strong\u003e → \u003ca href=\"\/products\/dell-poweredge-r730xd-12-bay-3-5-chassis\"\u003eDell PowerEdge R730xd 12-Bay 3.5\"\u003c\/a\u003e - 2U 2S Grantley, equivalent positioning.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMounting hardware?\u003c\/strong\u003e → \u003ca href=\"\/products\/hp-dl380-dl560-g9-g10-lff-sliding-rails\"\u003eDL380 \/ DL560 G9\/G10 2U LFF sliding rail kit\u003c\/a\u003e.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us the workload (backup target, file server, archive, surveillance, or distributed storage), the capacity target, drive-capacity preference (8 \/ 10 \/ 12 \/ 14 TB), RAID layout, controller preference (P840ar for hardware RAID, H241 for HBA and software-defined storage), boot pattern, networking requirement (10 GbE FlexibleLOM strongly recommended for backup ingest), PSU configuration, and quantity. We respond within 24 hours with a validated configuration including drive-capacity verification, RAID-sizing math, and HPE Power Advisor sizing, with third-party maintenance coordination when requested. Every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in testing, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951242895559,"sku":"BP-013617","price":606.66,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-gen9-12-bay-35-drives-669950.png?v=1765539623"},{"product_id":"hpe-proliant-dl360-g10-10-bay-2-5-chassis","title":"HPE ProLiant DL360 Gen10 10-Bay 2.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL360 Gen10 10-Bay 2.5\" is the densest 1U SFF configuration in the Gen10 family and the canonical 1U HPE Gen10 page on our site. Ten 2.5\" hot-swap bays, dual-socket Intel Xeon Scalable (Skylake-SP first generation or Cascade Lake-SP second generation), 24 DDR4 DIMM slots, iLO 5 with Silicon Root of Trust, and the HPE Smart Array storage controller family in a 1U chassis optimized for compute density. This is HPE's 1U workhorse for IT teams standardized on the ProLiant line and the architectural counterpart to the Dell PowerEdge R640 - choose by your shop's vendor standardization, not by capability gaps, because at this tier the two platforms trade blows feature for feature.\u003c\/p\u003e\u003cp\u003eFor HPE shops running vSphere clusters, Hyper-V deployments, scale-out application infrastructure, Kubernetes worker pools, or any compute-primary workload where rack density and per-node power efficiency matter more than per-chassis storage capacity, the DL360 Gen10 10-Bay is the right answer. Pair it with its 2U sibling, the \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\"\u003c\/a\u003e, when storage flexibility or PCIe expansion requires the larger chassis. Same processors. Same memory. Same iLO 5. Different chassis-level constraints.\u003c\/p\u003e\u003cp\u003eTo talk through a configuration, call 1-800-778-1545 or use the quote form below. We respond within 24 hours, every refurbished unit ships under our 180-day warranty, and every server runs through 12+ hour burn-in testing before it leaves the bench. Volume pricing kicks in at 5 units.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePlatform Overview - Purley in 1U\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen10 sits on Intel's Purley platform with the LGA 3647 socket, identical to the DL380 Gen10. That means the same dual-generation processor support: 1st Gen Intel Xeon Scalable (Skylake-SP) for the original Gen10 launch, and 2nd Gen Xeon Scalable (Cascade Lake-SP) added mid-lifecycle as a drop-in upgrade with no board respin required. If you're sourcing CPUs separately or planning a future upgrade path, this matters: any Cascade Lake-SP processor in the supported TDP range works in a Skylake-era DL360, and any Skylake-SP processor works in a later-production Cascade Lake-era DL360, subject to BIOS revision compatibility.\u003c\/p\u003e\u003cp\u003eThe 1U thermal envelope is the meaningful constraint versus the 2U DL380. Both chassis support the same processor SKUs in principle, but the DL360 has tighter heatsink options and less airflow headroom. Processors above 165W TDP - Platinum 8260, 8268, 8280 territory - require careful confirmation of heatsink configuration and ambient inlet temperature. The DL360 ships with two heatsink variants: a standard heatsink for processors up to roughly 150W, and a high-performance heatsink for processors above that. For Gold 6230 (20 cores, 125W), Gold 6240 (18 cores, 150W), and similar mainstream dual-socket SKUs, the DL360 is comfortable. For top-bin Platinum parts where you genuinely need every core at every clock, the DL380 2U is the safer thermal envelope. We'll confirm the heatsink and ambient guidance at quote time based on the CPU SKU you specify.\u003c\/p\u003e\u003cp\u003eMemory architecture is identical to the DL380: 24 DDR4 DIMM slots total across both sockets, six memory channels per CPU at two DIMMs per channel. The supported DIMM speeds depend on the processor: Gold 6200-series and Gold 5222 SKUs run DDR4-2933 at 1 DIMM per channel, the rest of the Skylake and Cascade Lake lineup runs DDR4-2666. RDIMM capacity goes up to 64 GB per slot for 1.5 TB per dual-socket system; LRDIMM goes to 128 GB per slot for 3 TB total. Intel Optane Persistent Memory 100-series is supported with M-suffix Cascade Lake CPUs (Gold 6230M, Platinum 8260M, etc.) in the documented ratios. HPE NVDIMM-N is supported on Skylake-only platforms - not Cascade Lake - and that's a vendor product matrix limitation, not an Intel one.\u003c\/p\u003e\u003cp\u003eHPE's memory population rules apply identically to the DL360 and the DL380: DIMMs must be installed in even quantities per CPU, RDIMM and LRDIMM cannot be mixed, and only HPE DDR4 Smart Memory is qualified to run at the rated speeds. Third-party memory will physically work but typically drops to DDR4-2400 regardless of the CPU's rated speed. If you have a DDR4-2933 workload requirement, you need HPE Smart Memory. We stock HPE Smart Memory and will spec the kit at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage - 10 SFF Bays, the Density Pick\u003c\/h2\u003e\u003cp\u003eTen 2.5\" SAS\/SATA hot-swap bays in 1U is the maximum SFF density on the DL360 Gen10 platform. Two additional bays over the more common 8-Bay configuration. The 10-Bay backplane is fully SAS\/SATA-capable across all ten slots, and NVMe is supported on the original Gen10 only via dedicated NVMe expansion - native backplane NVMe across all bays is a Gen10 Plus and Gen11 feature, not original Gen10. If you need direct-attached NVMe storage at meaningful capacity, the Gen10 supports it through PCIe expansion cards routing to specific NVMe-capable bays, not as a backplane-wide capability.\u003c\/p\u003e\u003cp\u003eThe 10-Bay configuration earns its place over the 8-Bay in three specific scenarios:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eCeph OSD nodes at 1U density.\u003c\/strong\u003e Ten OSDs per 1U node is a meaningful density improvement over eight when you're sizing a Ceph cluster for object storage or RBD workloads. The math at scale matters: a 12-node Ceph cluster with 10 OSDs per node is 120 OSDs; the same cluster at 8 OSDs per node is 96 OSDs. That 25% capacity difference per rack at the same rack-U cost is the reason this configuration exists.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003evSAN hybrid configurations.\u003c\/strong\u003e vSAN hybrid wants one SSD cache device per disk group and up to seven HDDs per group, with two disk groups per host as a common configuration. Ten bays gives you 2x (1 cache + 4 capacity) cleanly with two bays held back, or 2x (1 cache + 4 capacity) with the remaining two used for OS boot if you're not using M.2. vSAN all-flash configurations benefit similarly: 2x (1 cache + 4 capacity) all-SSD at 1U is a genuine vSAN ReadyNode-class density point.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDistributed databases and Kubernetes persistent volumes.\u003c\/strong\u003e Cassandra nodes, MongoDB replica set members, Elasticsearch data nodes, or Kubernetes CSI-backed persistent volume hosts all benefit from the extra two bays when the workload's per-node storage requirement is in the 6-10 drive range. Eight bays is tight when you also need OS boot drives in the bay count; ten bays gives breathing room.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eIf your storage design fits in 8 bays comfortably and you're using HPE's M.2 enablement kit or a single boot drive in a bay, the \u003ca href=\"\/products\/dl360-g10-chassis\"\u003e8-Bay variant\u003c\/a\u003e is the simpler and slightly less expensive choice. The 10-Bay premium is modest but it's a real cost - pay it when the bays earn their place, not by default.\u003c\/p\u003e\u003cp\u003eDrive options span the full Gen10 portfolio: SAS SSDs from 480 GB through 15.36 TB across read-intensive, mixed-use, and write-intensive endurance classes; SATA SSDs in mixed-use and read-intensive for cost-sensitive workloads; SAS HDDs at 10K and 15K from 600 GB through 2.4 TB for moderate-IOPS workloads; and NL-SAS in SFF form factor up to 2.4 TB for capacity tiers in SFF chassis. We carry the full HPE-branded drive line and will spec the right tier and endurance class based on your workload's read\/write profile and the controller's queue depth tolerance.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Controllers - Smart Array Family\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen10's controller options are identical to the DL380 Gen10's, configured for the 1U chassis:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P408i-a SR Gen10 with 2 GB FBWC.\u003c\/strong\u003e The mainstream production controller: RAID 0\/1\/5\/6\/10\/50\/60, 2 GB flash-backed write cache, full hardware RAID acceleration. This is the right pick for hardware-RAID storage where the OS sees a single logical drive per RAID group. The FBWC battery is a wear item with roughly a 5-year service life under typical conditions - plan a battery replacement somewhere in years 4 through 5, and watch iLO for cache module health alerts. We disclose this on every quote; a refurbished P408i-a's battery may have meaningful runtime already on it, and we either replace the cache module up front or document the battery's measured state at burn-in.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a SR Gen10 with 4 GB FBWC.\u003c\/strong\u003e The premium controller: same RAID modes, 4 GB FBWC, higher port count, and tri-mode SAS\/SATA\/NVMe support on supported drives. Specify the P816i-a when the workload is write-heavy at scale (transactional databases, write-mostly logging, video ingest) and the 2 GB cache on the P408i-a is the bottleneck. For most 1U DL360 deployments, the P408i-a is plenty; the P816i-a is the right call when you've actually measured cache pressure on a comparable workload or you need NVMe drive support alongside SAS\/SATA.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-a SR Gen10 (HBA mode).\u003c\/strong\u003e The HBA controller for software-defined storage: vSAN, Ceph, Storage Spaces Direct (S2D), ZFS-based appliances. No hardware RAID, just clean SAS HBA pass-through to the OS or hypervisor. This is the right pick for any storage-defined-in-software architecture where the hardware RAID controller would actually interfere with the SDS layer's drive-level visibility.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eS100i SR Gen10 (software RAID).\u003c\/strong\u003e The chipset-integrated software RAID solution. Adequate for boot-drive mirrors on Windows or Linux but not appropriate for production data RAID. Use it for OS boot if you don't have an M.2 enablement kit installed; use a real Smart Array P-series or HBA for data.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eBoot drive options on the DL360 Gen10 are the HPE M.2 enablement kit (PCIe-attached M.2 carrier with SATA M.2 drive support, typically 480 GB) or a SAS\/SATA SSD pair in two of the front bays under hardware RAID 1. The HPE NS204i-p NVMe boot device that ships standard on Gen10 Plus and Gen11 is not natively supported on original Gen10 - that's a generational platform line, not a configuration option. If you need NVMe boot specifically on Gen10, it's via the M.2 kit or via a PCIe-attached NVMe drive in a bay, not via NS204i-p.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking and PCIe\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen10 provides 3 PCIe Gen3 slots in a 1U chassis - a meaningfully tighter constraint than the DL380's 8 slots, and the single most important architectural difference between the 1U and 2U chassis at this tier. Slot 1 and slot 2 are full-height half-length, slot 3 is low-profile. The standard riser configuration supports two x16 slots; an alternative riser provides three slots with a x16\/x8\/x8 layout.\u003c\/p\u003e\u003cp\u003eHPE's FlexibleLOM mezzanine slot is separate from the PCIe slots and does not consume one. This is HPE's equivalent of Dell's rNDC (network daughter card) on the R640 - a dedicated mezzanine for the primary network interface that leaves all three PCIe slots free for HBAs, GPUs, or additional NICs. FlexibleLOM options span 1 GbE quad-port, 10 GbE SFP+ dual-port and quad-port, 10 GbE RJ45 dual-port and quad-port, 25 GbE SFP28 dual-port, and 100 GbE QSFP28 dual-port. For HCI workloads (vSAN, S2D, Ceph) where 25 GbE has become the standard interconnect, the 25 GbE SFP28 FlexibleLOM plus a 25 GbE SFP28 PCIe NIC in slot 1 is the standard high-bandwidth configuration. We'll spec the FlexibleLOM and any additional PCIe NICs at quote time based on your network topology.\u003c\/p\u003e\u003cp\u003eGPU support in 1U is sharply constrained relative to the DL380. The DL360 Gen10 supports a maximum of two single-width low-profile GPUs - typically NVIDIA T4 or A2 in the inference\/light-compute class. Double-width GPUs (V100, A100, A40, A30) and full-height cards do not fit the 1U chassis at all. If you need GPU compute beyond two T4-class cards, this is not the right chassis - the \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10\u003c\/a\u003e supports up to seven T4s or three V100s with the GPU riser kit. The DL360 is a CPU compute platform first; GPU is a secondary capability bounded by the 1U thermal and slot envelope.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eManagement - iLO 5 with Silicon Root of Trust\u003c\/h2\u003e\u003cp\u003eiLO 5 is HPE's out-of-band management processor, the architectural equivalent of Dell's iDRAC9 on R640\/R740 generations. Full remote KVM, virtual media mounting (mount an ISO over the network for OS install), serial-over-LAN, hardware health monitoring, power and thermal telemetry, REST API (Redfish-compliant), HPE OneView integration, and Active Health System logging. iLO is on a dedicated management network port - segregate it on a management VLAN; never expose iLO to the production network or the public internet without VPN. Both have full filesystem access to the host and full power control.\u003c\/p\u003e\u003cp\u003eSilicon Root of Trust is HPE's Gen10-and-later platform security baseline. It's a hardware-anchored chain of trust starting from the iLO 5 silicon, verifying iLO firmware, then BIOS, then OS bootloader against cryptographic measurements baked into the silicon at manufacture. This is functionally equivalent to Dell's iDRAC9 System Lockdown plus Intel Boot Guard, just architected differently. For environments with security audit requirements - PCI DSS, HIPAA, FedRAMP-aligned, or any environment where firmware tampering is a documented threat - Silicon Root of Trust is a meaningful differentiator from older Gen9 hardware that predates it.\u003c\/p\u003e\u003cp\u003eOne important note on refurbished units: iLO Advanced licensing is typically not included on refurbished Gen10 hardware. iLO Advanced unlocks the full feature set - remote KVM in particular, plus integrated remote console, video record\/replay, virtual folder, and email alerting. The base iLO 5 license that ships with the hardware includes health monitoring, IPMI, and basic remote access but not the full graphical remote KVM. We can include iLO Advanced licensing on builds where it's required - call this out at quote time so we spec the license correctly.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\u003cp\u003eHPE Flex Slot power supplies in the standard hot-plug redundant configuration. Wattages span 500W, 800W, 1600W, and 1600W -48V DC. Platinum efficiency on the 500W and 800W; Titanium efficiency on the 1600W (96% efficiency at 50% load, the highest 80 PLUS tier). For a typical dual-socket Gold-class DL360 with 16 DIMMs and 10 SFF SSDs, the 800W Platinum redundant pair is the standard sizing - generous headroom for any reasonable configuration and excellent efficiency at typical load. For high-TDP Platinum-CPU builds, top-bin DIMM populations, or single-PSU operation with redundancy as the failover path, step to the 1600W Titanium pair. We size the PSUs to the build and document the expected peak draw at quote time.\u003c\/p\u003e\u003cp\u003eFans are dual-rotor, fully redundant, hot-swappable. Inlet temperature spec is 10°C to 35°C ambient for standard operation; ASHRAE A3 (10°C to 40°C) supported on most configurations and A4 (5°C to 45°C) on specific reduced-CPU configurations. For colocation environments running ASHRAE A2 or stricter, the DL360 has plenty of thermal margin in any dual-socket Gold-class build. For high-density racks running hot, confirm the inlet spec at quote time - particularly for Platinum-CPU configurations approaching the 165W per-socket envelope.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL360 Gen10 Fits in 2026\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen10 launched in 2017 and was Cascade Lake-refreshed in 2019. By 2026, it's two platform generations behind current: Gen10 Plus (Ice Lake-SP, PCIe Gen4, 2020) and Gen11 (Sapphire Rapids \/ Emerald Rapids, DDR5, PCIe Gen5, 2023-2024). That generational gap is real and we won't pretend otherwise. What it means in practice:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003ePer-core performance is solid; per-socket maximums are dated.\u003c\/strong\u003e A Cascade Lake Gold 6230 at 20 cores per socket \/ 40 cores dual-socket is still a competitive virtualization host in 2026 - VMware vSphere 8 supports it, Windows Server 2025 supports it, modern Linux supports it, container workloads run fine. What's dated is socket-level scaling: Ice Lake-SP hit 40 cores per socket, Sapphire Rapids hit 60, Emerald Rapids hit 64. If your workload's bottleneck is socket-level core count, Gen10 is behind.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePCIe Gen3 is the I\/O limit.\u003c\/strong\u003e NVMe drives, 100 GbE NICs, and modern GPUs are all Gen4 or Gen5 internally. They work in Gen3 slots at reduced lane bandwidth - a Gen4 x4 NVMe drive runs at Gen3 x4 speeds, which is roughly half its rated throughput. For storage-intensive or networking-intensive deployments where Gen4 bandwidth actually matters, Gen10 Plus or Gen11 is the right platform. For compute-primary workloads where Gen3 NVMe bandwidth is sufficient, the limit doesn't bite.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eMemory bandwidth ceilings are real.\u003c\/strong\u003e DDR4-2933 maxes out at roughly 23.5 GB\/s per channel, six channels per socket, ~141 GB\/s per socket peak. Ice Lake-SP brought eight channels and DDR4-3200; Sapphire Rapids brought DDR5-4800. Memory-bandwidth-bound workloads (in-memory databases, HPC, certain analytics) see meaningful uplift on newer platforms. General-purpose virtualization and application serving rarely hit the memory bandwidth ceiling on Gen10.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThat said, Gen10 is widely deployed across the enterprise installed base in 2026. HPE supports Gen10 firmware updates through 2027 under standard lifecycle policy, and parts availability for both new and refurbished components is broad - this is the most-deployed ProLiant generation in service today. For HPE shops standardized on Gen10 and looking to expand existing clusters with matching hardware, the platform makes complete sense. For greenfield deployments where budget allows, Gen10 Plus or Gen11 will get you Ice Lake or newer with PCIe Gen4\/5 and more headroom for the next five years.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cp\u003eThe points worth saying out loud before you buy:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eThe Smart Array FBWC battery is a wear item.\u003c\/strong\u003e Cache module batteries have a service life of roughly 5 years under typical operating conditions, often less in hot environments. A refurbished P408i-a or P816i-a's battery may have meaningful runtime already. We replace cache modules on builds where the battery is past spec, and we document the measured battery state on every unit shipped with a P-series controller.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eiLO Advanced licensing is usually not included.\u003c\/strong\u003e Refurbished Gen10 units typically ship with the base iLO 5 license, not iLO Advanced. If you need integrated remote console KVM (the graphical remote console most people associate with iLO), the iLO Advanced license is a real cost. We'll quote it explicitly when it's required.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eThe DL360 is a CPU compute platform, not a GPU compute platform.\u003c\/strong\u003e Two single-width T4-class cards is the practical ceiling. If you need GPU compute at scale, the DL380 Gen10 or a purpose-built GPU server is the right answer.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eOriginal Gen10 is PCIe Gen3.\u003c\/strong\u003e Modern NVMe and 100 GbE cards work but at reduced bandwidth versus their Gen4\/Gen5 native platforms. For PCIe-Gen3-bandwidth-bound workloads specifically, this matters.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eHPE memory rules are strict.\u003c\/strong\u003e Third-party DDR4 will run at DDR4-2400 regardless of the CPU's rated speed. HPE DDR4 Smart Memory is required for rated DDR4-2666 or DDR4-2933 operation. This is documented HPE behavior, not a defect.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e    \u003cth\u003eThis server excels at\u003c\/th\u003e    \u003cth\u003eConsider alternatives for\u003c\/th\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ VMware vSphere \/ Hyper-V compute clusters at 1U density\u003c\/td\u003e    \u003ctd\u003e❌ Workloads requiring 24 SFF bays or 12 LFF bays\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Ceph OSD nodes at 10 OSDs per 1U\u003c\/td\u003e    \u003ctd\u003e❌ GPU compute beyond 2x T4-class single-width\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ vSAN hybrid or all-flash with 2 disk groups per host\u003c\/td\u003e    \u003ctd\u003e❌ More than 3 PCIe expansion cards needed\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Kubernetes worker pools with local persistent volumes\u003c\/td\u003e    \u003ctd\u003e❌ Memory-bandwidth-bound HPC (Gen10 Plus \/ Gen11 better)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Scale-out application infrastructure in HPE shops\u003c\/td\u003e    \u003ctd\u003e❌ PCIe Gen4 NVMe bandwidth as a hard requirement\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Distributed databases (Cassandra, MongoDB, Elasticsearch)\u003c\/td\u003e    \u003ctd\u003e❌ Top-bin Platinum CPUs in dense racks (DL380 thermal headroom)\u003c\/td\u003e  \u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eCross-Vendor Notes - DL360 Gen10 vs. Dell R640\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen10 and the Dell PowerEdge R640 are direct architectural counterparts. Both are 1U dual-socket Purley-platform servers. Both support 1st Gen and 2nd Gen Xeon Scalable. Both top out at 24 DDR4 DIMM slots. Both have integrated BMC-class management (iLO 5 vs. iDRAC9) with full remote console capability. Both have a dedicated network mezzanine slot (FlexibleLOM vs. rNDC) that doesn't consume a PCIe slot. Both have similar storage controller families (Smart Array P-series vs. PERC H730\/H740\/H840). The DL360 has 3 PCIe slots vs. the R640's 3 PCIe slots - identical. Drive bay configurations align closely (HPE 8-bay and 10-bay vs. Dell 8-bay and 10-bay).\u003c\/p\u003e\u003cp\u003eThe differences are at the vendor-ecosystem level: management software (iLO + OneView vs. iDRAC + OpenManage), licensing models for advanced features, the vendor's installed-base relationships, parts ecosystem and refresh cadence, and support contract pricing. None of these is a capability gap. Pick by your shop's vendor standardization and your existing tooling investments. If you're an HPE shop running OneView and Insight, the DL360 is the right answer. If you're a Dell shop running OpenManage Enterprise, the \u003ca href=\"\/products\/dell-poweredge-r640-10bay-2-5-build-your-own\"\u003eR640 10-Bay\u003c\/a\u003e is the right answer. We sell both and we'll quote both honestly.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eFrequently Asked\u003c\/h2\u003e\u003cp\u003e\u003cstrong\u003eDoes the DL360 Gen10 support Cascade Lake processors?\u003c\/strong\u003e Yes. The platform supports both 1st Gen Xeon Scalable (Skylake-SP) and 2nd Gen Xeon Scalable (Cascade Lake-SP) as drop-in compatible processors with appropriate BIOS revision. Cascade Lake brings hardware Spectre\/Meltdown mitigations, slightly higher core counts at the top of the stack, support for Optane Persistent Memory 100-series, and minor power efficiency improvements. Most production refurbished DL360 Gen10 units we ship are Cascade Lake-equipped.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eIs the DL360 Gen10 the same as the DL360 Gen10 Plus?\u003c\/strong\u003e No. Gen10 Plus is a different platform: Ice Lake-SP processors on LGA 4189, PCIe Gen4, eight memory channels per socket, and the HPE NS204i-p NVMe boot device standard. Gen10 is Purley\/Skylake-Cascade Lake\/PCIe Gen3. They look similar externally and share the DL360 chassis lineage, but the motherboard, processor socket, and I\/O are different generations. If you've been told \"DL360 Gen10\" and you need PCIe Gen4 or Ice Lake, confirm the actual SKU before purchase.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eCan I run VMware vSphere 8 on the DL360 Gen10?\u003c\/strong\u003e Yes. vSphere 8 supports both Skylake-SP and Cascade Lake-SP processors and HPE certifies Gen10 ProLiant hardware against vSphere 8. There are no platform-level blockers. vSphere 9 deprecates some older hardware - check VMware's HCL at the time of deployment for current support status. As of early 2026, Gen10 is fully on the vSphere 8 HCL.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhat about Windows Server 2025?\u003c\/strong\u003e Supported. HPE has Gen10 firmware and driver updates qualified against Windows Server 2025; the platform meets all of WS2025's hardware baseline requirements including TPM 2.0 (optional but available on Gen10 via the HPE TPM 2.0 module). Standard build.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eDoes the DL360 Gen10 support NVMe drives?\u003c\/strong\u003e Yes, via the NVMe expansion kit on specific bay positions. Native NVMe across all bays is a Gen10 Plus and Gen11 feature; the original Gen10 supports NVMe on a subset of bays through PCIe lane routing from a Smart Array P816i-a (tri-mode) or a dedicated NVMe-bay enablement kit. If NVMe is core to your storage design, we can spec it; if NVMe is the dominant storage tier, Gen10 Plus is the more native platform.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eDo you ship the iLO Advanced license?\u003c\/strong\u003e Optional. The base iLO 5 license that ships with refurbished Gen10 hardware does not include integrated remote console (graphical KVM), remote media, or some of the advanced telemetry features. iLO Advanced unlocks all of these. Call it out at quote time and we'll include the license SKU.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhat's the warranty?\u003c\/strong\u003e 180-day Wholesale Servers warranty on every refurbished unit, covering parts and labor. Pre-shipment burn-in testing is 12+ hours minimum on every server. Extended warranty options are available; ask at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us the workload, the CPU SKU (or the per-socket core count and clock target - we'll recommend the SKU), memory capacity, storage configuration including controller preference, network topology and FlexibleLOM choice, and quantity. We respond within 24 hours, every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below to start a conversation.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951242961095,"sku":"BP-013619","price":693.07,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl360-gen10-10-bay-25-drives-207415.png?v=1765539623"},{"product_id":"hpe-proliant-dl360-g10-4-bay-3-5-build-your-own-server","title":"HPE ProLiant DL360 Gen10 4-Bay 3.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL360 Gen10 4-Bay 3.5\" is the only 1U LFF configuration in the Gen10 lineup - four large-format 3.5\" hot-swap bays in the same compact 1U chassis as the SFF DL360 variants, with full dual-socket Xeon Scalable compute. This is the platform for edge computing nodes, branch office servers, and remote site deployments that need bulk local storage capacity without stepping to 2U. Four 20 TB NL-SAS drives delivers 80 TB raw in a 1U footprint, which is meaningful capacity for edge and branch deployments where rack space is constrained and bulk local storage is a real requirement.\u003c\/p\u003e\u003cp\u003eThis is a sibling page to the \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003eDL360 Gen10 10-Bay 2.5\"\u003c\/a\u003e canonical. The full platform vocabulary - Purley socket support, memory architecture, controller comparisons, iLO 5 with Silicon Root of Trust, FlexibleLOM networking, generational positioning - lives on that page and applies identically here. This page focuses on what's specific to the 4-Bay 3.5\" configuration: when 1U LFF is the right call, how 4 large-format bays map to common edge and branch workloads, and the cost-versus-flexibility decision against the 2U DL380 Gen10 12-Bay LFF.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhen 1U LFF Is the Right Configuration\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen10 4-Bay 3.5\" fills a specific niche: you need LFF bulk storage capacity, and 1U is a hard requirement. The only other path to LFF drives in 1U from HPE is the DL160 Gen10 (also 4-Bay LFF, but lower-spec compute - single-CPU or limited dual-CPU, fewer DIMM slots, more entry-tier overall). If 2U is acceptable, the \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eDL380 Gen10 12-Bay 3.5\"\u003c\/a\u003e delivers three times the LFF bays with the same compute platform and meaningful per-bay cost savings - that's almost always the better answer when 2U fits.\u003c\/p\u003e\u003cp\u003eThe DL360 4-Bay 3.5\" is the right call specifically when:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eEdge computing nodes.\u003c\/strong\u003e Full DL360 enterprise compute (dual-socket Xeon Scalable, 24 DIMM slots, iLO 5 management) alongside 4 LFF drives for local bulk storage, in a 1U footprint that fits constrained edge racks. For retail back-of-store deployments, manufacturing floor compute, or cell tower edge sites, the combination of real server-class compute and meaningful local storage in 1U is genuinely useful.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eBranch office file servers.\u003c\/strong\u003e 4x 12 TB or 4x 16 TB NL-SAS in RAID 6 gives 24-32 TB usable for branch NAS, file server, or Active Directory integrated storage at remote sites. The 1U footprint matters at branch sites where rack space is at a premium and shipping a 2U server to every branch isn't worth the cost.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eRemote backup targets.\u003c\/strong\u003e Veeam-style remote backup repositories or Active Directory-replicated DFS shares at remote sites. 4 large-capacity NL-SAS drives, 12+ hour burn-in tested, with iLO 5 for remote troubleshooting when there's no on-site IT staff. The reliability profile and remote management matter as much as the capacity here.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDistributed Ceph capacity-tier nodes.\u003c\/strong\u003e If you're running a Ceph cluster across many small edge sites and need 4 large NL-SAS OSDs per site in 1U, this is the platform. Per-site compute headroom is full DL360 dual-socket capacity, which is plenty for the OSD daemon load.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eStorage - 4 LFF Bays\u003c\/h2\u003e\u003cp\u003eFour 3.5\" SAS\/SATA hot-swap bays. Drive options span the full LFF portfolio:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eNL-SAS HDDs for bulk capacity.\u003c\/strong\u003e The mainstream pick. 4 TB, 8 TB, 12 TB, 16 TB, and 20 TB capacities. NL-SAS gives you full SAS protocol on bulk drives - end-to-end checksums, dual-port active-active capability, and queue depth advantages over SATA NL drives.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSAS HDDs at 10K and 15K RPM.\u003c\/strong\u003e Moderate-IOPS workloads where you want some performance alongside capacity. 10K SAS at 1.2-1.8 TB or 15K SAS at 600 GB-1.2 TB. The economics rarely justify these in LFF over SAS SSDs for performance, but the option exists for shops standardized on 10K LFF SAS.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSAS or SATA SSDs in LFF carriers.\u003c\/strong\u003e For workloads needing flash performance in LFF form factor. Possible but usually not the right answer - if you need SSDs, the SFF variants (8-Bay or 10-Bay 2.5\") deliver better drive density per chassis and lower per-GB cost for SSD storage.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eRAID at 4 Drives\u003c\/h3\u003e\u003cp\u003eRAID at low drive counts is its own conversation, and the 4-Bay configuration is the rare case where it's actually worth thinking carefully:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eRAID 6 (2 drives parity).\u003c\/strong\u003e 2 drives usable from 4 - 50% of raw. Two-drive fault tolerance, which matters at 16+ TB drive sizes because rebuild times after a failure are long and the probability of a second failure during rebuild is non-trivial. The capacity penalty is significant but the reliability is worth it for production data on large drives.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eRAID 10 (mirroring + striping).\u003c\/strong\u003e 2 drives usable from 4 - 50% of raw. Better write performance than RAID 6, faster rebuilds (single-drive copy versus parity reconstruction), still one-drive fault tolerance per mirror pair. Often the right choice when write performance matters and the capacity is sufficient.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eRAID 5 (1 drive parity).\u003c\/strong\u003e 3 drives usable from 4 - 75% of raw. Single-drive fault tolerance, which is the controversial part: industry consensus has moved away from RAID 5 on large drives because rebuild times leave the array vulnerable to a second failure for too long. At 12+ TB drive sizes specifically, RAID 5 is genuinely risky. At smaller drives (4-8 TB) and for less-critical data with off-site backup, it's defensible.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eFor most 4-bay deployments with large NL-SAS drives, we recommend RAID 6 even with the 50% capacity penalty. The reliability margin is worth the storage. RAID 10 is the right call when write performance is the dominant requirement. RAID 5 is a discussion to have at quote time only - we'll walk through your specific risk tolerance and capacity needs.\u003c\/p\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eStrongly recommend the HPE M.2 enablement kit for boot, freeing all 4 LFF bays for data. At 4 bays, consuming 2 of them for a RAID 1 OS mirror is a real capacity hit (50% of raw lost to OS alone before any data RAID overhead). The M.2 kit mounts in a PCIe slot, takes a SATA M.2 drive at 480 GB or larger, and leaves the 4 LFF bays entirely available for the workload's data tier.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Controllers\u003c\/h2\u003e\u003cp\u003eSame options as the rest of the DL360 Gen10 family. The \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003e10-Bay canonical\u003c\/a\u003e covers the full Smart Array Gen10 portfolio in detail. For 4-Bay LFF NL-SAS workloads specifically:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P408i-a SR (2 GB FBWC):\u003c\/strong\u003e The right pick for NL-SAS RAID 6 production data. The 2 GB cache is appropriately sized for the write patterns 4 NL-SAS drives produce. FBWC battery is a wear item with roughly 5-year service life - disclosed on every build.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-a SR (HBA mode):\u003c\/strong\u003e For Ceph OSD nodes at the edge, ZFS-based appliances, or any software-defined storage layer where you want direct drive visibility.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eS100i SR (software RAID):\u003c\/strong\u003e Boot drive only, not appropriate for production data.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eP816i-a is overkill at 4 drives - its 4 GB cache and tri-mode capabilities address bottlenecks that don't exist at this drive count. P408i-a is the right answer.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eCompute, Memory, Networking\u003c\/h2\u003e\u003cp\u003eIdentical to the rest of the DL360 Gen10 family: dual-socket LGA 3647 Purley, Skylake-SP and Cascade Lake-SP supported, 24 DDR4 DIMM slots, up to 3 TB LRDIMM, HPE Smart Memory required for rated DDR4-2666 or DDR4-2933 operation. iLO 5 with Silicon Root of Trust standard, FlexibleLOM mezzanine for primary networking, 3 PCIe Gen3 slots. The 4-Bay 3.5\" chassis doesn't change any of this - it's the bay configuration that's different, not the platform.\u003c\/p\u003e\u003cp\u003eFor edge deployments specifically, the iLO 5 remote management capability is the feature that earns its keep. Remote KVM, virtual media for OS installation, hardware health telemetry, and full power control over the dedicated iLO management network port means you can fully manage a branch-office server from headquarters without ever sending IT staff on-site. This is the operational lever that makes edge deployments practical at scale - and the reason the DL360 4-Bay 3.5\" earns its place over consumer or workstation-class hardware at remote sites.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eThe 1U LFF vs. 2U LFF Decision\u003c\/h2\u003e\u003cp\u003eIf 2U is acceptable, the \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eDL380 Gen10 12-Bay 3.5\"\u003c\/a\u003e delivers three times the LFF bays in the same processor and memory platform. The economics almost always favor the DL380 12-Bay at sites where rack space accommodates 2U: more capacity, more RAID flexibility (RAID 6 at 12 drives is 10 drives usable - 83% of raw, versus the 4-Bay's 50%), and per-bay cost that's meaningfully lower at scale.\u003c\/p\u003e\u003cp\u003eThe DL360 4-Bay 3.5\" wins specifically when 1U is the hard constraint - rack space at the edge or branch site is the design driver, and the 4-bay capacity ceiling is acceptable. If you're not constrained to 1U, the DL380 12-Bay is the better answer almost every time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e    \u003cth\u003eThis server excels at\u003c\/th\u003e    \u003cth\u003eConsider alternatives for\u003c\/th\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Edge computing with LFF bulk storage in 1U\u003c\/td\u003e    \u003ctd\u003e❌ More than 4 LFF bays needed (use DL380 12-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Branch office NAS\/file server in 1U racks\u003c\/td\u003e    \u003ctd\u003e❌ SFF SSD requirements (use DL360 8-Bay or 10-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Remote backup targets at branch sites\u003c\/td\u003e    \u003ctd\u003e❌ 2U acceptable (DL380 12-Bay more storage-flexible)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Distributed Ceph capacity-tier nodes at edge\u003c\/td\u003e    \u003ctd\u003e❌ Performance-tier storage needs SSDs in SFF\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Remote DFS replication targets\u003c\/td\u003e    \u003ctd\u003e❌ Heavy compute alongside lots of storage (DL380)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Manufacturing\/retail floor compute with local storage\u003c\/td\u003e    \u003ctd\u003e❌ GPU compute requirements (use DL380)\u003c\/td\u003e  \u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cp\u003eSame generational caveats as the rest of the DL360 Gen10 family - PCIe Gen3, DDR4 memory speed ceilings, 1U thermal constraints on top-bin Platinum CPUs, FBWC battery as a wear item, iLO Advanced licensing typically separate on refurbished units. The \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003e10-Bay canonical\u003c\/a\u003e covers each in detail.\u003c\/p\u003e\u003cp\u003ePlus one specific to the 4-Bay LFF configuration: the bay count itself is the binding constraint. Four bays at 50% RAID 6 capacity gives 2 drives usable - meaningful but limited. If your storage requirements grow beyond what 4 LFF bays at RAID 6 can serve, the path forward is replacing the chassis, not adding bays. Size the build with growth in mind, or accept that this is a fixed-capacity deployment.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e2U acceptable for more LFF bays?\u003c\/strong\u003e → \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eDL380 Gen10 12-Bay 3.5\"\u003c\/a\u003e - 3x the bays, same compute platform\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSFF SSDs in 1U instead of LFF HDDs?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003eDL360 Gen10 10-Bay 2.5\" (canonical)\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed 8 SFF bays in 1U?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl360-g10-chassis\"\u003eDL360 Gen10 8-Bay 2.5\"\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eLower-spec compute alongside LFF storage?\u003c\/strong\u003e → DL160 Gen10 4-Bay 3.5\" (entry-tier 1U LFF, lower CPU\/memory ceiling)\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us the workload, capacity target, CPU SKU preference, memory capacity, RAID preference at 4 drives, network topology and FlexibleLOM choice, and quantity. We respond within 24 hours, every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951269798087,"sku":"BP-013620","price":706.47,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/1800x1200_84.png?v=1765539687"},{"product_id":"hp-proliant-dl160-g10-4-bay-3-5-build-your-own-server","title":"HPE ProLiant DL160 Gen10 4-Bay 3.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL160 Gen10 4-Bay 3.5\" is HPE's value-tier 2P 1U platform in the Gen10 lineup - a dual-socket Xeon Scalable server in a 1U chassis built for SMB and service-provider workloads where the cost difference versus the DL360 matters more than the memory ceiling and DIMM count. Four 3.5\" LFF hot-swap bays, 16 DDR4 DIMM slots (eight per CPU, two fewer per CPU than the DL360), iLO 5 with Silicon Root of Trust, HPE Smart Array controller support, and dual embedded 1 GbE for primary networking - in a chassis that trades the DL360's memory headroom and FlexibleLOM-standard configuration for a lower entry cost.\u003c\/p\u003e\u003cp\u003eThis is the HPE architectural counterpart to the Dell PowerEdge R440 - 2P 1U value-tier in the same Purley generation. For HPE customers running branch office workloads, distributed compute clusters where per-node cost is the design driver, edge file servers, or any deployment where the DL360's 24 DIMM slots and 1.5-3 TB memory ceiling are surplus to requirements, the DL160 delivers the same processor family and same management architecture at a meaningfully lower price point. It's not a stripped-down DL360 - it's a different chassis built around different cost-versus-capacity tradeoffs.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL160 Gen10 Fits in the Family\u003c\/h2\u003e\u003cp\u003eHPE positions the DL160 Gen10 as \"2P 1U at compelling price point for SMB and service providers.\" That's accurate. The DL160 is genuinely a 2P server - both sockets are populated in production builds, dual-socket scaling works as designed, and the Purley platform is identical to the DL360 and DL380. What's different is what HPE designed the chassis to economize on:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e16 DIMM slots total versus 24 on the DL360.\u003c\/strong\u003e Eight DIMMs per CPU instead of twelve. With 64 GB RDIMMs that's a 1 TB maximum versus the DL360's 1.5 TB. The eight DIMMs per CPU still cover six memory channels (each at one DIMM per channel plus two channels at two DIMMs), so the bandwidth architecture is unchanged - what's gone is the headroom to populate larger memory configurations.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e2x embedded 1 GbE standard, FlexibleLOM optional.\u003c\/strong\u003e The DL160 ships with two 1 GbE ports built into the chassis. A FlexibleLOM mezzanine can be added via the FlexibleLOM riser kit, but it's not standard - and adding it consumes one of the available riser positions. The DL360, by contrast, has FlexibleLOM as a standard mezzanine that doesn't consume any PCIe slot.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eRiser-based PCIe configuration.\u003c\/strong\u003e Up to 3 PCIe slots maximum with the optional secondary riser, fewer in default configurations. The riser kit options determine the slot count, and some configurations (e.g. the FlexibleLOM riser) trade slots for I\/O capability.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eBronze\/Silver CPU sweet spot.\u003c\/strong\u003e The DL160 supports Bronze 3100, Silver 4100, Gold 5000\/6000, and lower-bin Platinum SKUs. Where the DL360 is comfortable with Gold-class dual-socket as the typical build, the DL160's price point is optimized around Bronze and Silver for the SMB and service-provider markets HPE designed it for. Top-bin Platinum CPUs are supported but the economics rarely justify them in this chassis - if you need top-bin Platinum, you usually also need the DL360's DIMM headroom.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThis is the right platform when those four constraints - 1 TB memory ceiling, embedded 1 GbE, modest PCIe expansion, Bronze\/Silver-tier CPU sweet spot - are acceptable for the workload. Pay the DL360 premium only when one of those constraints actually bites your design.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage - 4 LFF Bays\u003c\/h2\u003e\u003cp\u003eFour 3.5\" SAS\/SATA hot-swap bays in the front of the chassis. Drive options span the full LFF portfolio: NL-SAS HDDs for bulk capacity (4 TB through 20 TB), SAS HDDs at 10K and 15K for moderate-IOPS workloads, and SAS or SATA SSDs in LFF carriers for performance in LFF form factor. RAID-at-4-drives guidance is the same as the DL360 4-Bay 3.5\" - RAID 6 strongly preferred for large-capacity NL-SAS, RAID 10 when write performance is the priority, RAID 5 only with explicit discussion of risk tolerance.\u003c\/p\u003e\u003cp\u003eBay-count map for common DL160 4-Bay deployments:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eBranch office file server (SMB-scale).\u003c\/strong\u003e 4x 8 TB or 12 TB NL-SAS in RAID 6 gives 16-24 TB usable for branch NAS, AD-integrated file shares, or shared user storage at remote sites. The DL160's lower acquisition cost matters when you're deploying across many branches.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eService provider compute node with local storage.\u003c\/strong\u003e Bronze or Silver dual-socket compute, 256-512 GB RAM, and 4 LFF bays for tenant storage or VM datastores. Service providers running many small-scale tenants benefit from the per-node cost optimization.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eVeeam backup target at remote site.\u003c\/strong\u003e 4 large-capacity NL-SAS drives for remote backup repositories. The lower compute spec is fine - Veeam Backup \u0026amp; Replication's CPU requirement on a remote proxy is modest. Spend the savings on more drives.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDistributed Ceph or MinIO node at small scale.\u003c\/strong\u003e 4 OSDs per 1U node for capacity-tier storage with modest per-node compute. The DL160's economics work well at scale when you're deploying many nodes.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSMB primary application server.\u003c\/strong\u003e Single dual-socket build with 4 LFF drives for OS + application + local data. The Bronze\/Silver-tier CPU is sufficient for SMB application workloads.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eThe HPE Universal SATA HHHL M.2 Kit is the cleanest boot solution on the DL160 Gen10 - it mounts in a PCIe slot, takes one or two SATA M.2 drives, and frees all 4 LFF bays for data. Strongly recommended given the 4-bay constraint. Note that the M.2 kit requires the DL160\/120 Gen10 M.2 SATA Cable Kit as an additional part - HPE breaks this into separate SKUs, which we handle on the BoM at quote time. The alternative is 2x SFF SAS\/SATA SSDs in a RAID 1 OS mirror occupying two of the 4 LFF bays via LFF-to-SFF adapter brackets, but this consumes half the bay count for OS alone.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Controllers\u003c\/h2\u003e\u003cp\u003eThe DL160 Gen10 supports the same Smart Array Gen10 controller family as the DL360 and DL380, sourced as PCIe plug-in cards rather than as type-a modular controllers in some configurations:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P408i-a SR Gen10 (2 GB FBWC).\u003c\/strong\u003e The mainstream production RAID controller. 2 GB flash-backed write cache, full hardware RAID 0\/1\/5\/6\/10\/50\/60. Right pick for NL-SAS RAID 6 in a production build. The FBWC battery is a wear item with roughly 5-year service life - we disclose battery state on every quote and replace cache modules on builds where the battery is past spec.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a SR Gen10 (4 GB FBWC).\u003c\/strong\u003e Premium controller. Same RAID modes, larger cache, tri-mode SAS\/SATA\/NVMe support. Specify when write workload is heavy enough to pressure the 2 GB cache on the P408i-a - rarely needed at 4 drives, but available when the I\/O profile justifies it.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-p SR Gen10 (HBA mode, PCIe plug-in).\u003c\/strong\u003e The HBA controller for software-defined storage workloads (Ceph, ZFS, S2D). No hardware RAID; clean SAS pass-through.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eS100i SR Gen10 (software RAID).\u003c\/strong\u003e Chipset-integrated software RAID. Acceptable for OS boot mirroring, not appropriate for production data.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThe HPE Smart Storage Battery is required when any P-series performance RAID controller is installed - this is a separate part from the FBWC cache module on the controller itself. We include the battery in every quote that specifies a P-series controller.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors and Memory\u003c\/h2\u003e\u003cp\u003eDual-socket LGA 3647 Purley platform, identical to the DL360 and DL380. Both 1st Generation Intel Xeon Scalable (Skylake-SP) and 2nd Generation (Cascade Lake-SP) are supported as drop-in compatible processors. The DL160's CPU sweet spot is the Bronze 3100 series (4-8 cores, low TDP, DDR4-2133 max memory speed at the bottom of the stack) and Silver 4100\/4200 series (8-12 cores, DDR4-2400 to DDR4-2666). Gold 5200\/6200 series are supported and run their full rated DDR4-2933 with HPE Smart Memory; Platinum is supported but rarely the right economic call in this chassis.\u003c\/p\u003e\u003cp\u003eMemory: 16 DDR4 DIMM slots total (8 per CPU), supporting RDIMM and LRDIMM (no UDIMM at production scale). Six memory channels per CPU with the eight DIMM slots arranged as six channels at one DPC plus two channels at two DPC - the bandwidth architecture is identical to the DL360, the difference is the headroom for additional memory beyond a balanced six-channel population. Maximum 1 TB with 64 GB RDIMMs at dual-socket. HPE DDR4 Smart Memory required for rated speed operation - third-party DDR4 drops to DDR4-2400 regardless of CPU rated speed, same documented HPE behavior as the rest of the Gen10 line. RDIMM and LRDIMM cannot be mixed; even DIMM quantities per CPU required.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking and PCIe Expansion\u003c\/h2\u003e\u003cp\u003eThe DL160 Gen10 ships with 2x embedded 1 GbE ports on the chassis as standard. For shops with 10 GbE or higher requirements:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eFlexibleLOM riser kit.\u003c\/strong\u003e Adds a FlexibleLOM mezzanine to one of the riser positions, enabling 10 GbE SFP+, 10 GbE RJ45, 25 GbE SFP28, or other FlexibleLOM options. This consumes one PCIe slot's worth of riser capacity.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePCIe plug-in NICs.\u003c\/strong\u003e Standard PCIe NIC cards in available slots - 10 GbE, 25 GbE, or 100 GbE depending on the riser configuration and slot count.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eMaximum 3 PCIe slots with the optional secondary riser installed (requires second CPU populated). Default configurations have fewer. The slot budget on the DL160 is tight - allocate carefully between storage controller, FlexibleLOM\/NIC, and any additional cards. Standard production builds for branch-office workloads usually need just a P408i-a Smart Array and either FlexibleLOM riser or PCIe NIC - that fits comfortably in the available slots.\u003c\/p\u003e\u003cp\u003eGPU support is limited to single-width low-profile cards at most, and the DL160 is not designed for GPU workloads. If GPU compute is a requirement, the DL360 Gen10 or DL380 Gen10 is the right answer.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eManagement - iLO 5 with Silicon Root of Trust\u003c\/h2\u003e\u003cp\u003eSame iLO 5 management architecture as the DL360 and DL380, with the same caveat: iLO Standard ships with the hardware on refurbished units, and iLO Advanced licensing is typically a separate cost when needed for full graphical remote KVM, virtual media mounting, and advanced telemetry. The base iLO 5 license covers health monitoring, IPMI, and basic remote access. We'll quote iLO Advanced explicitly when the deployment requires it.\u003c\/p\u003e\u003cp\u003eSilicon Root of Trust is standard - the same hardware-anchored chain of trust starting from iLO 5 silicon, verifying iLO firmware, BIOS, and OS bootloader against cryptographic measurements. This is the same Gen10 security baseline that applies across the DL line. For SMB and branch-office deployments where firmware tampering is a documented concern (any environment subject to compliance audit, plus any deployment in physically-accessible locations like retail back-of-store), Silicon Root of Trust is real value at this price point.\u003c\/p\u003e\u003cp\u003eSecure Recovery is also Gen10-baseline: the firmware can detect compromised firmware and roll back to a known-good state automatically. Combined with iLO 5's signed firmware update model, the security posture on a DL160 is identical to a much more expensive DL380 - one of the genuine value points of buying into the Gen10 family at the entry tier.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\u003cp\u003eHPE Flex Slot power supplies in single or redundant configurations. Redundant PSU operation requires the HPE DL160\/180 Gen10 Redundant Power Supply Enablement Kit - this is not standard on every model and we'll spec it when redundant power is a requirement. Wattages span 500W and 800W for typical Bronze\/Silver-tier builds; higher-wattage Flex Slot PSUs are supported for Gold-class configurations.\u003c\/p\u003e\u003cp\u003eSingle-PSU operation is acceptable for non-production or branch-office workloads where the cost savings matter and the deployment is not mission-critical at the single-server level. For production HA workloads, take the redundant PSU kit - it's a modest add to the BoM and protects against the most common cause of single-server downtime.\u003c\/p\u003e\u003cp\u003eInlet temperature spec is 10°C to 35°C standard, with ASHRAE A3 support on most configurations. For branch-office deployments in environments without dedicated server-room cooling (closets, equipment rooms, retail back-of-store), the wider ambient operating range matters. Confirm the inlet spec for the specific CPU SKU and configuration at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL160 Gen10 Fits in 2026\u003c\/h2\u003e\u003cp\u003eSame generational positioning as the rest of the Gen10 line. Launched in 2017, Cascade Lake-refreshed in 2019, two generations behind Gen10 Plus (Ice Lake-SP, PCIe Gen4, 2020) and Gen11 (Sapphire Rapids \/ Emerald Rapids, DDR5, 2023-2024). The platform is widely deployed and supported - HPE firmware updates through 2027 under standard lifecycle, broad parts availability for both new and refurbished.\u003c\/p\u003e\u003cp\u003eWhat's specific to the DL160 in 2026: the value proposition is sharper now than at launch because the DL160's \"sufficient for SMB and branch workloads\" hardware envelope still genuinely covers those workloads. SMB file server requirements haven't grown dramatically; branch-office compute workloads haven't transformed. The DL160's hardware is dated but its workload fit isn't. For HPE shops adding capacity to existing fleets or standardizing on Gen10 for cost-controlled deployments, the DL160 4-Bay 3.5\" delivers genuine work at meaningful cost savings versus a DL360-class deployment.\u003c\/p\u003e\u003cp\u003eThat said, if the deployment is greenfield and the budget allows, Gen10 Plus or Gen11 will get you Ice Lake or newer with PCIe Gen4\/5 and more headroom for the next five years. The DL160 Gen10 is the right call when budget is the design constraint - which is exactly what HPE built the chassis for.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e16 DIMM slots, 1 TB memory ceiling.\u003c\/strong\u003e Two fewer DIMMs per CPU than the DL360. If your workload's per-node memory requirement is above 1 TB, this isn't the right platform - step to the DL360.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e2x embedded 1 GbE only by default.\u003c\/strong\u003e Anything more requires the FlexibleLOM riser kit (which consumes riser capacity) or PCIe NICs. The DL360's standard FlexibleLOM is a meaningful differentiator if 10 GbE+ is a baseline requirement.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eTight PCIe slot budget.\u003c\/strong\u003e Maximum 3 slots with the optional secondary riser. Allocate carefully between storage controller, networking, and any additional cards.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eRedundant PSU is optional, not standard.\u003c\/strong\u003e Single-PSU operation is the default. For production HA, add the redundant PSU enablement kit - we'll include it explicitly when specified.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eBronze CPUs cap memory speed at DDR4-2133.\u003c\/strong\u003e If you take the price-optimized Bronze 3100 series, memory bandwidth drops below what Silver\/Gold deliver. For memory-bandwidth-sensitive workloads, Silver is the minimum reasonable CPU tier.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSame Gen10 generational caveats apply.\u003c\/strong\u003e PCIe Gen3, DDR4-2933 ceiling (with appropriate CPU), iLO Advanced licensing separate, FBWC battery as a wear item. The DL360 canonical covers these in detail and they apply identically here.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e    \u003cth\u003eThis server excels at\u003c\/th\u003e    \u003cth\u003eConsider alternatives for\u003c\/th\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ SMB primary servers (file, AD, applications)\u003c\/td\u003e    \u003ctd\u003e❌ Memory requirement above 1 TB (use DL360)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Branch office file servers in 1U LFF\u003c\/td\u003e    \u003ctd\u003e❌ More than 4 LFF bays needed (use DL380 12-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Service provider compute at price-point optimization\u003c\/td\u003e    \u003ctd\u003e❌ 10 GbE+ as baseline networking requirement (DL360 better)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Remote Veeam backup targets at branch sites\u003c\/td\u003e    \u003ctd\u003e❌ Top-bin Platinum CPU workloads (DL360\/DL380)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Distributed Ceph capacity-tier at scale\u003c\/td\u003e    \u003ctd\u003e❌ GPU compute requirements\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Cost-controlled HPE shop deployments\u003c\/td\u003e    \u003ctd\u003e❌ Many PCIe expansion cards needed\u003c\/td\u003e  \u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed 24 DIMM slots and full DL360 memory\/networking?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl360-g10-4-bay-3-5-build-your-own-server\"\u003eDL360 Gen10 4-Bay 3.5\"\u003c\/a\u003e - same Purley platform, 24 DIMMs, FlexibleLOM standard\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed more than 4 LFF bays?\u003c\/strong\u003e → \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eDL380 Gen10 12-Bay 3.5\"\u003c\/a\u003e - 3x the bays in 2U\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed SFF drives instead of LFF?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl360-g10-10-bay-2-5-chassis\"\u003eDL360 Gen10 10-Bay 2.5\" (canonical)\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDell shop alternative at the same tier?\u003c\/strong\u003e → Dell PowerEdge R440 - 2P 1U value-tier on the Dell side, same generation\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us the workload, CPU tier preference (Bronze\/Silver\/Gold), memory target, storage configuration including RAID and controller, network requirement (embedded 1 GbE vs. FlexibleLOM riser vs. PCIe NIC), PSU redundancy, and quantity. We respond within 24 hours, every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in testing, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951272091847,"sku":"BP-013621","price":706.47,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl160-gen9-4-bay-35-drives-523949.png?v=1765539688"},{"product_id":"server-design-lab-hpe-dl560-g10-8-bay-2-5-drives","title":"HPE ProLiant DL560 Gen10 8-Bay 2.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL560 Gen10 8-Bay 2.5\" is HPE's 4-socket flagship in the Gen10 lineup - a dense quad-socket Xeon Scalable platform in a 2U chassis (not 4U; HPE engineered the DL560 as a high-density 2U 4S server, which is one of its primary differentiators against competitors). Up to four 1st or 2nd Generation Intel Xeon Scalable processors, 48 DDR4 DIMM slots, 6 TB maximum memory with LRDIMMs, eight 2.5\" SFF hot-swap bays, up to 8 PCIe Gen3 slots with full riser configuration, FlexibleLOM networking, iLO 5 with Silicon Root of Trust, and up to 4 HPE Flex Slot power supplies. Built for scale-up workloads that have genuinely exhausted dual-socket compute and memory headroom.\u003c\/p\u003e\u003cp\u003eThis is the HPE architectural counterpart to the Dell PowerEdge R840 - 2U 4-socket Purley on the Dell side, same generation, same workload positioning. For SAP HANA scale-up, Oracle Database Enterprise consolidation, mission-critical virtualization at extreme VM density, or Microsoft SQL Server Enterprise at maximum core-license consolidation, the DL560 Gen10 is the right HPE platform. The 8-Bay 2.5\" variant is the standard configuration: maximum 4-socket compute paired with 8 SFF bays for OS, application data, and hot dataset staging, expecting primary bulk storage on SAN or distributed file systems.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units. DL560 configurations benefit from a design conversation early - workload architecture, Oracle\/SAP licensing implications, power budget at 4-socket TDP, and thermal validation all matter before hardware selection.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL560 Gen10 Fits in the Family\u003c\/h2\u003e\u003cp\u003eThe DL560 Gen10 is a fundamentally different platform from the DL360 and DL380. Where the DL380 Gen10 tops out at 56 cores dual-socket (28+28) and 3 TB memory, the DL560 Gen10 carries up to 112 cores across four sockets and up to 6 TB memory with LRDIMMs (12 TB with HPE Persistent Memory on L-series Cascade Lake CPUs). It is the HPE Gen10 platform for workloads that don't scale horizontally - the workloads where you need a single OS instance to see all the cores and all the memory.\u003c\/p\u003e\u003cp\u003eHonest framing on the 4-socket decision: most enterprise workloads don't require 4-socket servers. Dual-socket platforms (DL380, DL360) handle the vast majority of virtualization, database, and application serving workloads at materially lower cost and complexity. The DL560 makes sense when:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eA specific workload requires scale-up rather than scale-out.\u003c\/strong\u003e SAP HANA on a single certified appliance. Oracle Database Enterprise where licensing economics favor fewer sockets with more cores each. Microsoft SQL Server Enterprise where per-core licensing makes a single high-core-count server cheaper than multiple smaller ones.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eThe application is not horizontally scalable.\u003c\/strong\u003e Legacy enterprise applications, in-memory analytics platforms, or single-instance databases that cannot be sharded across nodes.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eMaximum single-chassis memory capacity is a genuine architectural requirement.\u003c\/strong\u003e 6 TB in a 2U chassis is meaningful when the working set has to fit in a single server's RAM.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePer-socket Oracle\/SQL licensing creates the right economics.\u003c\/strong\u003e Oracle Database Enterprise charges per physical core; a 4-socket server with 4x 24-core CPUs licenses 96 cores under one server count. Two 2-socket servers with the same cores license the same 96 cores but count as two servers - a discussion to have with your Oracle licensing team before committing to architecture.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eIf your workload can run across multiple dual-socket nodes without licensing penalty or architectural friction, the DL380 Gen10 is almost always more cost-efficient. The DL560 is a precision tool for specific scale-up requirements, not a default upgrade from DL380.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage - 8 SFF Bays\u003c\/h2\u003e\u003cp\u003eEight 2.5\" SAS\/SATA\/NVMe hot-swap bays in the front of the chassis (Drive Box 1). The DL560 Gen10 chassis supports field upgrades to 16 or 24 SFF via additional Drive Box 2 and Box 3 kits - if your build needs more than 8 bays, the 24-Bay variant is the right starting point rather than upgrading later. The 8-Bay configuration is correctly sized for the common 4-socket workload pattern: OS plus application binaries plus hot dataset staging, expecting primary data to live on SAN, NFS, or distributed file system.\u003c\/p\u003e\u003cp\u003eDrive options span the full Gen10 SFF portfolio: SAS SSDs in mixed-use and read-intensive endurance tiers (480 GB through 7.68 TB), SATA SSDs for cost-optimized boot\/OS roles, SAS HDDs at 10K and 15K for moderate-IOPS data, NVMe SSDs via the 6SFF+2NVMe drive cage option, and self-encrypting drive (SED) variants for compliance-regulated deployments.\u003c\/p\u003e\u003cp\u003eCommon DL560 8-Bay storage profiles in production:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSAP HANA appliance.\u003c\/strong\u003e 2x SATA SSDs in RAID 1 for OS, 6x mixed-use SAS SSDs in RAID 10 for HANA log and shared volumes. Primary HANA data volumes mirror to external NetApp or HPE Primera storage; local SSDs handle log persistence and warm-data staging.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eOracle Database with ASM on SAN.\u003c\/strong\u003e 2x SAS SSDs in RAID 1 for OS plus Oracle Grid Infrastructure binaries, 6 bays available for local Fast Recovery Area or archive log staging. Primary database storage on Fibre Channel or iSCSI SAN via the HPE FC HBA in PCIe expansion.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eMission-critical VMware cluster node.\u003c\/strong\u003e 2x SSDs in RAID 1 for ESXi boot. Remaining 6 bays unused or populated for vSAN cache tier. Primary VM storage on shared SAN datastore. The DL560's 4-socket compute drives high VM density per host with the storage layer abstracted via vSphere.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSQL Server Enterprise consolidation host.\u003c\/strong\u003e 2x SSDs in RAID 1 for OS, 2x SSDs in RAID 1 for tempdb, 4x SAS SSDs in RAID 10 for log files. Primary SQL data on SAN. The 8-bay configuration is sufficient for SQL's local-disk patterns when primary data is networked.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eMicrosoft Hyper-V or VMware HCI candidate.\u003c\/strong\u003e When 8 SSDs are configured as the storage tier for a 4-socket HCI host, expect to provision high-endurance SAS SSDs and pair with an HBA-mode controller (E208i-a) rather than hardware RAID. The DL560's 4-socket compute justifies the per-node cost when extreme VM density requires fewer, larger HCI nodes.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eThe HPE M.2 SSD enablement option mounts boot drives in a PCIe slot or on the CPU mezzanine board, freeing all 8 SFF bays for data. For DL560 production builds, M.2 boot is the recommended pattern - the 8-bay storage budget is already tight against scale-up workload patterns and consuming 2 bays for OS boot mirroring is wasteful. We include the M.2 enablement kit by default on DL560 quotes unless customer specifies otherwise.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Controllers\u003c\/h2\u003e\u003cp\u003eThe DL560 Gen10 supports the full Gen10 Smart Array family plus the MR-series controllers that are specific to higher-drive-count and high-IOPS workloads:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P408i-a SR Gen10 (2 GB FBWC).\u003c\/strong\u003e The mainstream production controller. Full hardware RAID 0\/1\/5\/6\/10\/50\/60, 2 GB flash-backed write cache. Right pick for the 8-bay configuration when traditional hardware RAID is the storage model. FBWC battery is a wear item with roughly 5-year service life - we disclose battery state on every quote.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a SR Gen10 (4 GB FBWC).\u003c\/strong\u003e Premium controller. Same RAID modes, larger cache, supports tri-mode SAS\/SATA\/NVMe lanes. Specify when write workload is heavy enough to pressure the 2 GB cache - common for SQL Server log files or Oracle redo logs on local storage.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P824i-p MR Gen10 (4 GB cache, CacheCade).\u003c\/strong\u003e MR-series controller introduced with Gen10 for high-drive-count and CacheCade-accelerated workloads. 24 internal SAS lanes, 12G SAS, CacheCade SSD acceleration for HDD pools. Relevant on the 24-Bay DL560 more than the 8-Bay; available here for builds that anticipate later expansion to 16 or 24 SFF.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-a SR Gen10 (HBA mode).\u003c\/strong\u003e The HBA controller for software-defined storage workloads (vSAN, Ceph, ZFS, Storage Spaces Direct). No hardware RAID; clean SAS pass-through. Right pick when the storage abstraction is the hypervisor or distributed file system, not the controller.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eS100i SR Gen10 (chipset software RAID).\u003c\/strong\u003e Acceptable for OS boot mirroring; not appropriate for production data on a 4-socket platform.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThe HPE Smart Storage Battery is required when any P-series performance RAID controller is installed. We include the battery in every quote that specifies a P-series controller. On a DL560 build with the P824i-p MR, confirm CacheCade SSD requirements at quote time - the MR controller's value depends on the CacheCade configuration matching the workload.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors and Memory\u003c\/h2\u003e\u003cp\u003e1, 2, or 4 sockets of Intel Xeon Scalable in the LGA 3647 Purley platform. The 4-socket configuration requires the HPE DL5x0 Gen10 CPU Mezzanine Board Kit (872222-B21 for 1st Gen, P07991-B21 v2 for 2nd Gen support) - this is a separate board carrying sockets 3 and 4 plus 24 additional DIMM slots. Production DL560 deployments are almost always 4-socket; 2-socket DL560 configurations exist but the platform's value proposition is the 4S scale-up. If the design only needs 2 sockets, the DL380 Gen10 is a better fit at significantly lower cost.\u003c\/p\u003e\u003cp\u003eBoth 1st Generation Intel Xeon Scalable (Skylake-SP) and 2nd Generation (Cascade Lake-SP) are supported. Mixing 1st and 2nd Generation CPUs is not supported - all installed processors must be from the same generation. Cascade Lake brings DDR4-2933 support (vs. DDR4-2666 on Skylake), HPE Persistent Memory support, and the M and L series CPUs with extended memory ceiling capability.\u003c\/p\u003e\u003cp\u003eCPU options for production 4-socket builds:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eGold 6230 (20 cores, 125W, DDR4-2933).\u003c\/strong\u003e Common production sweet spot - 80 cores total at 4S, manageable thermal envelope, balanced single-thread performance. Right pick for general 4-socket virtualization and database consolidation.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eGold 6248 (20 cores, 150W, DDR4-2933).\u003c\/strong\u003e Higher base frequency than 6230 at the cost of higher TDP. 80 cores total. Good fit for Oracle and SQL Server where single-thread performance matters within the per-core licensing model.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eGold 6248R (24 cores, 205W, DDR4-2933).\u003c\/strong\u003e 96 cores total at 4S. Higher TDP - 4x 205W in a 2U chassis is thermally aggressive and requires confirmation of inlet temperature spec and PSU sizing. We validate thermal headroom on every 6248R-class quote.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePlatinum 8280 (28 cores, 205W, DDR4-2933).\u003c\/strong\u003e 112 cores total - the maximum core count for DL560 Gen10. Same thermal considerations as 6248R. Right pick when maximum cores in a single server is the requirement, typically driven by Oracle or SQL Server licensing economics.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePlatinum 8276M \/ 8276L (28 cores, M\/L SKUs).\u003c\/strong\u003e Extended memory ceiling - M-series enables 2 TB per socket (8 TB platform), L-series enables 4.5 TB per socket with Persistent Memory. Required for memory configurations beyond the standard 6 TB LRDIMM ceiling.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eMemory: 48 DDR4 DIMM slots total - 12 per CPU across 4 sockets. Six memory channels per CPU at 2 DPC. Maximum 3 TB with 64 GB RDIMMs, 6 TB with 128 GB LRDIMMs, up to 12 TB with HPE Persistent Memory on L-series CPUs. HPE DDR4 Smart Memory required for rated speed operation - third-party DDR4 drops to DDR4-2400 regardless of CPU rated speed, same documented HPE behavior as the rest of the Gen10 line. RDIMM and LRDIMM cannot be mixed; balanced symmetric population across all populated sockets required for optimum performance.\u003c\/p\u003e\u003cp\u003eFull 48-DIMM population at 2 DPC drops memory speed by one bin under DIMM-population rules (DDR4-2933 capable DIMMs run at DDR4-2666 at 2 DPC on supported CPUs). For maximum memory bandwidth, populate at 1 DPC (24 DIMMs total, 6 per CPU) - this is the configuration HPE recommends for SAP HANA and other bandwidth-sensitive workloads.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking and PCIe Expansion\u003c\/h2\u003e\u003cp\u003eFlexibleLOM mezzanine for primary networking - same architecture as the DL360 and DL380 Gen10. Networking options span 1 GbE quad-port, 10 GbE SFP+ dual or quad-port, 10 GBASE-T dual-port, 25 GbE SFP28 dual-port, and 10 GbE plus 100 GbE converged. The DL560 has FlexibleLOM standard (not via consumable riser like the DL160), and it doesn't consume any PCIe expansion slot - this is one of the platform's value points against alternatives.\u003c\/p\u003e\u003cp\u003ePCIe expansion: up to 8 PCIe 3.0 slots maximum with primary + secondary + tertiary risers installed. The slot map depends on CPU count and riser configuration:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003ePrimary riser - 3 slots, always available.\u003c\/strong\u003e Standard with the chassis.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSecondary riser - 3 slots, requires 2nd CPU populated.\u003c\/strong\u003e Standard riser kit options include x8\/x8\/x8 or x8\/x16\/x8 configurations. Slimline riser variant (873418-B21) provides NVMe slimline connections but no additional PCIe slots.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eTertiary riser - 2 slots, requires 2nd CPU populated AND only 2 PSUs installed.\u003c\/strong\u003e The tertiary riser physically conflicts with the 3rd and 4th PSU positions - 4-PSU configurations cannot accommodate the tertiary riser. For 4-PSU builds, the maximum is 6 PCIe slots; for 2-PSU builds, the full 8 slots are available.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThis PSU-vs-tertiary-riser tradeoff is specific to the DL560 chassis and matters at design time. For workloads that need both 4 PSUs (high-TDP 4-socket configurations) AND 8 PCIe slots (many adapters), the DL560 cannot deliver both - this is one of the few hard architectural limits on the platform. Most production builds prioritize the 4-PSU redundancy and accept 6 slots.\u003c\/p\u003e\u003cp\u003eGPU support: the DL560 Gen10 supports 1-2 single-width GPU accelerators in the right riser configurations. It is not a primary GPU compute platform - if AI training or heavy GPU virtualization is the workload, the HPE Apollo or DL380 Gen10 with 2x double-width GPU is a better fit. The DL560's GPU support is for selective acceleration alongside its 4-socket CPU workload, not as a primary GPU host.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eManagement - iLO 5 with Silicon Root of Trust\u003c\/h2\u003e\u003cp\u003eSame iLO 5 management architecture as the rest of the Gen10 line. iLO Standard ships with the hardware on refurbished units; iLO Advanced licensing is typically a separate cost when needed for full graphical remote KVM, virtual media mounting, Active Health System telemetry, and Workload Advisor recommendations. On a 4-socket mission-critical platform, iLO Advanced is rarely optional - we'll quote it explicitly with any DL560 build.\u003c\/p\u003e\u003cp\u003eSilicon Root of Trust is standard - the same hardware-anchored chain of trust starting from iLO 5 silicon, verifying iLO firmware, BIOS, and OS bootloader against cryptographic measurements. For SAP HANA, Oracle, and SQL Server deployments subject to compliance audit (SOC 2, PCI-DSS, HIPAA, FedRAMP), Silicon Root of Trust delivers documented platform-attestation evidence that's required in modern compliance frameworks. This is one of the genuine value points of buying into Gen10 at the 4-socket tier.\u003c\/p\u003e\u003cp\u003eNUMA topology visibility through iLO 5 and HPE OneView is meaningful on a 4-socket platform. Workload placement across 4 sockets is consequential - cross-socket memory access (CPU 1 reading CPU 4's memory) incurs latency penalty versus same-socket access. iLO 5 provides the topology data; the workload (hypervisor NUMA scheduling, database affinity settings, OS process binding) does the actual placement. For SAP HANA and Oracle in particular, NUMA tuning is a standard part of production deployment.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\u003cp\u003eHPE Flex Slot power supplies, 1 to 4 PSUs depending on configuration. A fully-populated DL560 with 4x Gold 6248 (4x 150W = 600W CPU), 48 DDR4 DIMMs (approximately 150-200W), and 8 SAS SSDs (approximately 80W) plus fans and overhead draws approximately 1,200-1,500W sustained. With 4x Platinum 8280 at 205W each (820W CPU alone), the draw rises to approximately 1,500-1,800W sustained.\u003c\/p\u003e\u003cp\u003ePSU sizing recommendations by configuration:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e2x 800W Flex Slot PSU (low-TDP 4-socket).\u003c\/strong\u003e Adequate for 4x 125W CPU configurations (Gold 6230 class) with modest memory and storage. Marginal headroom; not recommended for production HA.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e2x 1600W Flex Slot Titanium PSU (typical production).\u003c\/strong\u003e Standard production redundant configuration for most DL560 builds. 1600W PSUs require high-line input (200-240VAC) - confirm rack PDU and circuit capacity. Provides full redundancy at all common CPU configurations including 205W Platinum.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e4x 1600W Flex Slot Titanium PSU (maximum redundancy).\u003c\/strong\u003e 2+2 redundancy at high TDP. Required when high availability and high TDP combine. Trades off the tertiary PCIe riser as discussed in the Networking section.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003ePower redundancy at 4-socket scale matters more than at dual-socket scale - the workloads that justify a DL560 (SAP HANA, Oracle, mission-critical SQL) are workloads where unplanned downtime has documented cost. Take the redundant PSU configuration on every production DL560 build.\u003c\/p\u003e\u003cp\u003eInlet temperature spec: 10°C to 35°C standard, with ASHRAE A3 (40°C) and A4 (45°C) support on selected configurations. At 4-socket high-TDP, the thermal envelope is real - confirm rack cooling and inlet temperature for the specific CPU SKU at quote time. We validate thermal configurations as part of every DL560 quote.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL560 Gen10 Fits in 2026\u003c\/h2\u003e\u003cp\u003eSame generational positioning as the rest of the Gen10 line. Launched in 2017, Cascade Lake-refreshed in 2019, two generations behind DL560 Gen11 (Sapphire Rapids \/ Emerald Rapids 4-socket, DDR5, 2023-2024). The platform is widely deployed in production at scale across enterprise SAP HANA, Oracle, and mission-critical virtualization deployments - HPE firmware updates continue under standard lifecycle, broad parts availability for both new and refurbished.\u003c\/p\u003e\u003cp\u003eWhat's specific to the DL560 in 2026: the platform is mature, the workloads it serves haven't fundamentally changed (SAP HANA still scales up, Oracle licensing economics still favor fewer sockets with more cores, SQL Server Enterprise per-core licensing still benefits from consolidation), and the per-core acquisition cost is meaningfully lower than Gen11 for the same workload envelope. For organizations adding 4-socket capacity to existing SAP HANA, Oracle, or SQL Server consolidation deployments where standardization on Gen10 reduces operational complexity, the DL560 Gen10 8-Bay delivers genuine work at significantly reduced cost versus the Gen11 alternative.\u003c\/p\u003e\u003cp\u003eThe framework is the same as the rest of HPE Gen10: this is mature platform with one generation of headroom in front of it, deployed widely, well-understood. Not the newest, not obsolete, the right tool for specific workload patterns when budget is a meaningful design constraint.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e4-socket configurations require the CPU Mezzanine Board Kit.\u003c\/strong\u003e This is a separate part (872222-B21 for 1st Gen, P07991-B21 for 2nd Gen support). A 2-socket DL560 without the mezzanine board is supported but rarely the right design choice - if 2 sockets are sufficient, use a DL380.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e4x 1600W PSU and tertiary PCIe riser are mutually exclusive.\u003c\/strong\u003e Maximum 6 PCIe slots with 4 PSUs, maximum 8 PCIe slots with 2 PSUs. Production HA builds typically take 4 PSUs and accept 6 slots.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e48 DIMM slots at 2 DPC drop memory speed by one bin.\u003c\/strong\u003e Full 48-DIMM population runs DDR4-2933 capable DIMMs at DDR4-2666. For HANA or bandwidth-sensitive workloads, populate at 1 DPC (24 DIMMs) for full speed.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eMixing 1st and 2nd Gen Xeon Scalable not supported.\u003c\/strong\u003e All four sockets must be same-generation CPUs. This applies across the Gen10 platform and is enforced at boot.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSame Gen10 generational caveats apply.\u003c\/strong\u003e PCIe Gen3 (not Gen4), DDR4-2933 ceiling, iLO Advanced licensing typically separate, FBWC battery as a wear item, third-party DDR4 limited to DDR4-2400 regardless of CPU. The DL380 Gen10 canonical covers these in detail and they apply identically here.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e4-socket TDP and thermals require validation.\u003c\/strong\u003e 4x 205W Platinum in a 2U chassis is thermally aggressive. Confirm inlet temperature spec, rack cooling capacity, and rack PDU sizing before deployment. We validate thermal configurations as part of every quote.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNot a GPU compute platform.\u003c\/strong\u003e The DL560's PCIe slot map and thermal budget are not designed for primary GPU workloads. For GPU compute, the HPE Apollo or DL380 Gen10 with double-width GPU is the right answer.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e    \u003cth\u003eThis server excels at\u003c\/th\u003e    \u003cth\u003eConsider alternatives for\u003c\/th\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ SAP HANA scale-up appliances (HANA-certified)\u003c\/td\u003e    \u003ctd\u003e❌ Workloads that scale horizontally (use DL380)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Oracle Database Enterprise large-instance consolidation\u003c\/td\u003e    \u003ctd\u003e❌ General-purpose virtualization (use DL380)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ SQL Server Enterprise per-core consolidation\u003c\/td\u003e    \u003ctd\u003e❌ Large local storage requirement above 8 SFF (use DL560 24-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Mission-critical extreme VM density per host\u003c\/td\u003e    \u003ctd\u003e❌ Budget-constrained dual-socket-sufficient projects\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ In-memory analytics requiring 4-6 TB single-server RAM\u003c\/td\u003e    \u003ctd\u003e❌ Primary GPU compute workloads (use Apollo)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Per-socket licensing economics (Oracle, SQL Server)\u003c\/td\u003e    \u003ctd\u003e❌ Workloads requiring PCIe Gen4\/Gen5 (use Gen10+ or Gen11)\u003c\/td\u003e  \u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed 24 SFF bays for high-density local storage alongside 4-socket compute?\u003c\/strong\u003e → \u003ca href=\"\/products\/server-design-lab-hpe-dl560-g10-24-bay-2-5-drives\"\u003eDL560 Gen10 24-Bay 2.5\"\u003c\/a\u003e - same 4-socket platform, 3x the SFF bay count\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDual-socket is sufficient?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\"\u003c\/a\u003e - significantly lower cost and complexity at the dual-socket tier\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDell shop alternative at the same 4-socket 2U tier?\u003c\/strong\u003e → Dell PowerEdge R840 - 2U 4-socket Purley on the Dell side, same generation, equivalent workload positioning\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed PCIe Gen4 and DDR5 at 4-socket?\u003c\/strong\u003e → Contact us for DL560 Gen11 availability when budget allows the generational step\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eDL560 configurations start with a design conversation. Tell us the workload (SAP HANA \/ Oracle \/ SQL Server \/ virtualization \/ in-memory analytics), licensing context (per-core, per-socket, ULA), CPU and core target, memory target including any Persistent Memory requirement, storage configuration (local SSD pattern plus external SAN\/NFS), PSU redundancy preference, PCIe expansion requirements, and quantity. We respond within 24 hours with a validated configuration including thermal and power-budget confirmation. Every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in testing, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951273074887,"sku":"BP-013622","price":984.9,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-dl560-gen10-8-bay-25-drives-736155.png?v=1765539690"},{"product_id":"server-design-lab-hpe-dl560-g10-24-bay-2-5-drives","title":"HPE ProLiant DL560 Gen10 24-Bay 2.5\" Drives [Gen10]","description":"\u003cp\u003eThe HPE ProLiant DL560 Gen10 24-Bay 2.5\" pairs HPE's 4-socket flagship compute platform with maximum SFF storage density - twenty-four 2.5\" hot-swap bays in a 2U chassis alongside up to four Intel Xeon Scalable processors, 48 DDR4 DIMM slots, 6 TB memory ceiling with LRDIMMs, FlexibleLOM networking, iLO 5 with Silicon Root of Trust, and up to 4 HPE Flex Slot power supplies. This is a deliberately specialized configuration: 4-socket compute for scale-up workloads combined with 24-bay SFF storage for high-density database, analytics, or HCI data that lives locally rather than on a SAN.\u003c\/p\u003e\u003cp\u003eFor the full DL560 Gen10 platform documentation - including the honest framing on when 4-socket compute is and isn't the right call, Section 12 platform vocabulary (CPU\/memory\/PCIe\/management), and Dell PowerEdge R840 cross-vendor reference - see the \u003ca href=\"\/products\/server-design-lab-hpe-dl560-g10-8-bay-2-5-drives\"\u003eDL560 Gen10 8-Bay 2.5\"\u003c\/a\u003e canonical. This page focuses on what's specific to the 24-bay variant: when 24 SFF bays alongside 4-socket compute is the right tool, the bay-count-driven workload patterns, and the storage controller and power decisions that change at 24 bays.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units. The 24-bay configuration benefits from extra design discussion - 4-socket compute plus 24 SSDs in 2U is genuinely dense and the architectural choices have downstream operational consequences worth getting right at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhen 24 SFF Bays + 4-Socket Makes Sense\u003c\/h2\u003e\u003cp\u003eThe 24-Bay DL560 is a deliberately narrow configuration. Most 4-socket workloads (SAP HANA, Oracle Database, mission-critical virtualization, SQL Server Enterprise) don't need 24 local SFF drives - they either use a SAN for primary storage or a smaller number of high-performance local SSDs alongside networked storage. The DL360-class 8-Bay DL560 is the right answer for most of those builds.\u003c\/p\u003e\u003cp\u003eThe 24-Bay DL560 earns its place when both 4-socket compute AND high-density local SSD storage are genuine requirements. The specific scenarios:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSAP HANA with large local SSD persistence layer.\u003c\/strong\u003e HANA in-memory databases benefit from local NVMe\/SSD for log persistence and warm-data tiering rather than depending on SAN latency for log writes. 24 SFF bays alongside HANA-scale memory (3-6 TB DDR4 + up to 12 TB Persistent Memory on L-series CPUs) enables a complete in-memory plus fast-persistence architecture in a single chassis. The persistence layer fits in the chassis instead of crossing the SAN, which matters for HANA savepoint and log-replay latency.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eOracle Database with local ASM diskgroups.\u003c\/strong\u003e Oracle RAC or large-instance Oracle databases where the design choice is local SSD storage rather than SAN. 24 SAS SSDs in ASM disk groups deliver high IOPS and predictable latency without the SAN dependency. Common when SAN is unavailable, undesirable for licensing\/cost reasons, or simply when the database team has decided ASM-on-local-SSD is the operational pattern they want to standardize on.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSQL Server Enterprise with extensive tempdb and log staging on local SSDs.\u003c\/strong\u003e Per-core SQL Server licensing economics already favor consolidation on 4-socket compute; pairing with 24 high-endurance SSDs lets the entire tempdb plus transaction log infrastructure live on local NVMe\/SAS rather than crossing the SAN. Datafile-on-SAN plus tempdb-and-logs-on-local-SSD is a documented Microsoft pattern for performance-sensitive SQL Server deployments.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eHigh-density VMware HCI or vSAN ReadyNode at 4-socket scale.\u003c\/strong\u003e vSAN ReadyNode configurations at 24 SFF bays with 4-socket compute deliver high VM density per host. Fewer, larger HCI nodes reduce vSphere license count (which is per-CPU socket) and rack footprint. The 24-bay DL560 is at the high end of the vSAN ReadyNode footprint and works well when the goal is consolidating to the fewest hosts possible.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eIn-memory analytics with large local hot-data tier.\u003c\/strong\u003e Analytics workloads (Splunk, Elasticsearch hot-tier, in-memory data grids) that need both maximum processing capacity (4-socket) and large local SSD datasets that don't fit entirely in DRAM but are too latency-sensitive for SAN. 24 SAS SSDs as a tiered hot-data layer behind in-memory analytics is a meaningful configuration.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eMicrosoft Storage Spaces Direct (S2D) at 4-socket scale.\u003c\/strong\u003e S2D requires HBA-mode storage and benefits from high drive counts per node for performance scaling. 24 NVMe or SAS SSDs in a 4-socket S2D node delivers a high-density HCI design with the per-node compute headroom to host many workloads.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eIf either the 4-socket compute or the 24-bay storage capacity is more than the workload actually needs, a different platform delivers better economics. The DL380 Gen10 24-Bay covers high-density storage at the dual-socket tier; the DL560 Gen10 8-Bay covers 4-socket compute with modest local storage. Pay for both 4-socket and 24-bay only when both are genuine requirements.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage - 24 SFF Bays\u003c\/h2\u003e\u003cp\u003eTwenty-four 2.5\" SAS\/SATA\/NVMe hot-swap bays across three drive boxes (Box 1, Box 2, Box 3) in the front of the chassis. With the full 24-bay configuration populated, the optional Universal Media Bay (front display port plus optical drive) is not supported - the media bay occupies the same physical position as one of the drive boxes. Production 24-bay builds typically don't need the media bay; remote iLO 5 access covers the operational requirements that the media bay served on earlier platforms.\u003c\/p\u003e\u003cp\u003eDrive options span the full Gen10 SFF portfolio: SAS SSDs (mixed-use and read-intensive endurance tiers, 480 GB through 7.68 TB), SATA SSDs for cost-optimized roles, SAS HDDs at 10K and 15K for moderate-IOPS data, NVMe SSDs via specific drive cage and riser combinations (see NVMe section below), and self-encrypting drive variants for compliance-regulated deployments. Per-drive type mixing is supported subject to controller capability.\u003c\/p\u003e\u003cp\u003eRAID guidance at 24 SFF bays: RAID 6 is appropriate for capacity-optimized SAS\/SATA SSD pools where rebuild windows on individual drive failure need to be tolerated; RAID 10 is appropriate for write-intensive workloads where the 50% capacity overhead is acceptable in exchange for write performance and shorter rebuild windows; RAID 50 or RAID 60 across multiple sub-pools (e.g. 2x RAID 6 of 12 drives, striped) balances rebuild scope against usable capacity. We discuss RAID layout in every 24-Bay quote.\u003c\/p\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eM.2 boot via the HPE M.2 SSD enablement option is strongly recommended at 24 bays - consuming 2 bays for OS boot mirroring wastes meaningful storage capacity in a configuration that exists specifically for high-density local SSD. M.2 boot mounts in a PCIe slot or on the CPU mezzanine board and frees all 24 SFF bays for data. Standard on our 24-Bay DL560 quotes unless customer specifies otherwise.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Controllers at 24-Bay Scale\u003c\/h2\u003e\u003cp\u003eAt 24 SFF bays, the storage controller decision matters more than at 8 bays - controller capability, RAID overhead, and write-cache sizing become primary design factors rather than secondary considerations:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a SR Gen10 (4 GB FBWC).\u003c\/strong\u003e The standard production controller for the 24-Bay configuration. 4 GB flash-backed write cache absorbs burst writes across the larger drive pool, tri-mode SAS\/SATA\/NVMe support handles mixed drive types. Full hardware RAID 0\/1\/5\/6\/10\/50\/60. Right pick for traditional hardware RAID across 24 SAS SSDs.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P824i-p MR Gen10 (4 GB cache, CacheCade).\u003c\/strong\u003e MR-series controller with 24 internal SAS lanes - the controller is purpose-designed for 24-drive configurations. CacheCade SSD acceleration accelerates HDD pools when the drive mix includes both SSD and HDD. The right controller when the deployment uses dedicated CacheCade SSDs to front a larger HDD pool, or when maximum lane count matters for sustained throughput.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-a SR Gen10 plus additional E208 (HBA mode).\u003c\/strong\u003e For software-defined storage workloads (vSAN, Ceph, ZFS, Storage Spaces Direct) at 24-bay scale. Multiple HBA controllers may be required to deliver pass-through for all 24 bays; we'll spec the right combination at quote time based on backplane configuration.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P408i-a SR Gen10 (2 GB FBWC).\u003c\/strong\u003e Supported on the 24-bay configuration but the 2 GB cache is smaller than ideal for 24 SSDs under heavy write load. Acceptable for primarily read-heavy or moderate-write workloads; for write-intensive workloads the P816i-a is the better default.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThe HPE Smart Storage Battery is required when any P-series performance RAID controller is installed. At 24 bays the battery is essentially mandatory - write workload at this drive count makes write-cache protection a hard requirement. We include the battery on every 24-Bay quote with a P-series controller. On P824i-p MR builds, confirm CacheCade SSD requirements at quote time - the MR controller's value depends on the CacheCade SSD configuration matching the workload's read\/write profile.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNVMe at 24 Bays\u003c\/h2\u003e\u003cp\u003eThe DL560 Gen10 supports up to 12 NVMe SSDs (half of the 24-bay backplane) with the right combination of NVMe drive cages, PCIe risers, and Smart Array controllers. NVMe at this drive count requires PCIe lane budget that competes with other expansion (the 4-port NVMe Mezzanine card on the CPU mezzanine board doesn't consume PCIe slots but is limited to 8 NVMe drives; beyond that requires PCIe slot consumption).\u003c\/p\u003e\u003cp\u003eCommon NVMe configurations on the 24-Bay DL560:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e8 NVMe + 16 SAS\/SATA SFF.\u003c\/strong\u003e NVMe via the mezzanine card (no PCIe slot consumption), remaining 16 bays via SAS\/SATA on a P816i-a or HBA. Typical hot\/warm storage tiering pattern.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e12 NVMe + 12 SAS\/SATA SFF.\u003c\/strong\u003e Maximum NVMe configuration via PCIe slot consumption for additional NVMe lanes. Higher-bandwidth tier for performance-critical local storage paired with bulk SAS\/SATA. Verifies feasibility at quote time given competing PCIe demand.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e24 SAS\/SATA SFF.\u003c\/strong\u003e All-SAS or all-SATA configuration with no NVMe. Simpler PCIe planning; appropriate when NVMe-tier performance isn't the design requirement.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eFor most production 24-Bay DL560 workloads, all-SAS-SSD is the right answer - the per-drive performance of modern SAS SSDs is high enough that the NVMe step-up isn't required, and the SAS-only configuration simplifies PCIe planning meaningfully. If NVMe is a genuine workload requirement, we'll engineer the riser and controller combination at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePower and Cooling at 24-Drive Scale\u003c\/h2\u003e\u003cp\u003eA fully-populated DL560 Gen10 24-Bay with 4x Gold 6248 (4x 150W = 600W CPU), 48 DDR4 DIMMs (approximately 150-200W), and 24 SAS SSDs (approximately 240W) plus fans and overhead draws approximately 1,400-1,700W sustained. With 4x Platinum 8280 at 205W each (820W CPU alone) and 24 NVMe SSDs, the draw rises to approximately 1,800-2,000W sustained.\u003c\/p\u003e\u003cp\u003eAt this power envelope, 1600W Titanium PSUs are mandatory and 4-PSU configurations are typically required for production HA. Recall from the canonical that 4x 1600W PSUs and the tertiary PCIe riser are mutually exclusive - on the 24-Bay configuration, 4-PSU is typically the right choice (high TDP plus production HA) and the platform delivers 6 PCIe slots maximum rather than 8.\u003c\/p\u003e\u003cp\u003e1600W Flex Slot Titanium PSUs require high-line input (200-240VAC) - confirm rack PDU and circuit capacity before deployment. We validate power budgets including PDU phase balance for every 24-Bay DL560 quote.\u003c\/p\u003e\u003cp\u003eThermal envelope: 24 SAS SSDs plus 4 high-TDP CPUs in 2U is thermally aggressive. Inlet temperature spec of 10°C to 35°C standard applies but at the upper limit (32-35°C inlet), confirm specific CPU SKU support against the HPE thermal matrix. ASHRAE A3\/A4 support is configuration-specific at this density; we validate thermal headroom on every quote.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSame 4-socket platform limitations as the canonical 8-Bay.\u003c\/strong\u003e 4x 1600W PSU and tertiary PCIe riser mutually exclusive; full 48-DIMM population drops memory speed one bin; 1st and 2nd Gen Xeon Scalable cannot be mixed; 4-socket TDP requires thermal validation; not a primary GPU compute platform. See the DL560 Gen10 8-Bay canonical for full Section 12 platform vocabulary.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eUniversal Media Bay not supported with full 24-bay population.\u003c\/strong\u003e The media bay occupies the same physical position as one of the three drive boxes. Production 24-bay builds don't typically need the media bay; remote iLO 5 access covers the same operational requirements.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNVMe at full 24-bay scale is PCIe-budget-limited.\u003c\/strong\u003e Maximum 12 NVMe drives requires PCIe slot consumption beyond the 4-port mezzanine card. NVMe beyond 8 drives competes with FlexibleLOM, storage controller, and any other expansion - we engineer this carefully at quote time.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eStorage controller decision matters more at 24 bays.\u003c\/strong\u003e The P408i-a (2 GB cache) is supported but undersized for write-intensive workloads at 24 SSDs. P816i-a (4 GB) is the standard recommendation; P824i-p MR for CacheCade-accelerated workloads. The wrong controller choice at 24 bays produces measurable performance loss under load.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSingle-PSU operation not appropriate.\u003c\/strong\u003e The 24-Bay DL560 draws 1.4-2.0 kW sustained - single PSU is not a production configuration at this power level. Take redundant PSU (2x or 4x 1600W) on every production build.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSame Gen10 generational caveats apply.\u003c\/strong\u003e PCIe Gen3, DDR4-2933 ceiling, iLO Advanced licensing typically separate, FBWC battery as a wear item, third-party DDR4 limited to DDR4-2400 regardless of CPU. The DL380 Gen10 canonical and DL560 Gen10 8-Bay canonical cover these in detail and they apply identically here.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e    \u003cth\u003eThis server is right for\u003c\/th\u003e    \u003cth\u003eConsider alternatives for\u003c\/th\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ SAP HANA with large local SSD persistence layer\u003c\/td\u003e    \u003ctd\u003e❌ 8 SFF bays sufficient alongside 4-socket (use DL560 8-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Oracle Database with local ASM diskgroups\u003c\/td\u003e    \u003ctd\u003e❌ Dual-socket sufficient with 24 SFF (use DL380 24-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ SQL Server Enterprise with local tempdb\/log on SSD\u003c\/td\u003e    \u003ctd\u003e❌ SAN-only storage architecture (use DL560 8-Bay)\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ vSAN ReadyNode at 4-socket consolidation\u003c\/td\u003e    \u003ctd\u003e❌ Budget-constrained projects\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ High-density in-memory analytics with local hot tier\u003c\/td\u003e    \u003ctd\u003e❌ Workloads requiring more than 12 NVMe drives\u003c\/td\u003e  \u003c\/tr\u003e  \u003ctr\u003e    \u003ctd\u003e✅ Storage Spaces Direct (S2D) at 4-socket scale\u003c\/td\u003e    \u003ctd\u003e❌ Primary GPU compute workloads (use Apollo)\u003c\/td\u003e  \u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e8 SFF bays sufficient alongside 4-socket compute?\u003c\/strong\u003e → \u003ca href=\"\/products\/server-design-lab-hpe-dl560-g10-8-bay-2-5-drives\"\u003eDL560 Gen10 8-Bay 2.5\" (canonical)\u003c\/a\u003e - same 4-socket platform at lower cost when local storage requirement is modest\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDual-socket with 24 SFF bays?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-dl380-g10-2-5-24-bay-chassis\"\u003eDL380 Gen10 24-Bay 2.5\"\u003c\/a\u003e - 24 SFF capacity at the dual-socket tier, significantly lower cost\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed 16 SFF bays at dual-socket?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay 2.5\"\u003c\/a\u003e - the dual-socket sweet spot for medium-density SFF storage\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eDell shop alternative at the same 4-socket 2U tier?\u003c\/strong\u003e → Dell PowerEdge R840 - 2U 4-socket Purley on the Dell side, equivalent positioning, supports up to 24 SFF in similar configurations\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed PCIe Gen4 and DDR5 at 4-socket?\u003c\/strong\u003e → Contact us for DL560 Gen11 availability when budget allows the generational step\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003e24-Bay DL560 configurations are sufficiently specialized that we recommend a design conversation before hardware selection. Tell us the workload (SAP HANA \/ Oracle \/ SQL Server \/ vSAN \/ analytics \/ S2D), licensing context, CPU and core target, memory target including any Persistent Memory requirement, storage architecture (drive type mix, RAID layout, NVMe requirement), controller preference (P816i-a vs P824i-p MR vs HBA), PSU redundancy preference, PCIe expansion requirements, and quantity. We respond within 24 hours with a validated configuration including thermal, power-budget, and PCIe-budget confirmation. Every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in testing, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951273173191,"sku":"BP-013583","price":2000.6,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/1800x1200_6.png?v=1765539691"},{"product_id":"hpe-proliant-dl580-gen9-5-bay-build-your-own","title":"HPE ProLiant DL580 Gen9 5-Bay 2.5\" Drives","description":"\u003cp\u003eThe HPE ProLiant DL580 Gen9 5-Bay 2.5\" is HPE's Gen9 4-socket flagship - a true 4U enterprise scale-up platform built around Intel Xeon E7-4800\/8800 v3 (Haswell-EX) or v4 (Broadwell-EX) processors. Up to four CPUs, \u003cstrong\u003e96 DDR4 DIMM slots\u003c\/strong\u003e across 8 memory cartridges (the highest single-server DIMM count in the Gen9 line), 6 TB maximum memory, five 2.5\" SFF bays standard (expandable to 10 with the Express Bay kit including up to 5 NVMe), 9 PCIe Gen3 slots all full-length full-height, an embedded HPE Smart Array P830i 12 Gb\/s SAS controller, FlexibleLOM networking, iLO 4 management, and 2 to 4 hot-plug PSUs. This is the HPE counterpart to the Dell PowerEdge R930 (4U 4S Brickland) and is positioned for mission-critical scale-up workloads where Gen9-era hardware still delivers genuine value: SAP HANA on certified Gen9 builds, Oracle Database on Brickland-generation E7 CPUs, large-memory virtualization consolidation, and mission-critical legacy applications running on validated Gen9 platforms.\u003c\/p\u003e\u003cp\u003eGen9 is a generation behind Gen10 (Skylake-SP \/ Cascade Lake-SP), three generations behind Gen11 (Sapphire Rapids \/ Emerald Rapids). The platform launched in 2014 (v3) with a v4 refresh in 2016. HPE active warranty and ProSupport on Gen9 hardware has ended for both v3 and v4 builds - third-party maintenance is the standard production support path in 2026. We are not going to soft-pedal this: if budget allows the Gen10 step (DL560 Gen10 or the DL580 Gen10 \/ Gen10 Plus 4U flagship), the architectural and management improvements (iLO 5 with Silicon Root of Trust, faster memory, more cores per CPU) are material for new mission-critical deployments. Where Gen9 still earns its place is in fleet-extension and capacity-add for existing Gen9 SAP HANA, Oracle, or scale-up virtualization deployments where operational standardization on a single platform generation reduces complexity, and in budget-driven scale-up where the Gen10 acquisition cost is not justified by the workload's actual performance ceiling.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units. DL580 Gen9 configurations benefit from a design conversation early - workload architecture, SAP HANA certification status check, Oracle\/SQL Server licensing context, and PCIe expansion requirements all matter before hardware selection.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL580 Gen9 Fits in the Family\u003c\/h2\u003e\u003cp\u003eThe DL580 Gen9 is HPE's true 4U enterprise scale-up flagship at the Gen9 generation. Two architectural distinctions matter compared to the other HPE Gen9 4-socket option:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eDifferent Xeon family than the DL560 Gen9.\u003c\/strong\u003e The DL580 Gen9 uses Intel Xeon E7-4800\/8800 v3 or v4 (Haswell-EX or Broadwell-EX, Brickland platform, Intel C602J chipset). The \u003ca href=\"\/products\/hpe-proliant-dl560-gen9-8-bay-build-your-own\"\u003eHPE ProLiant DL560 Gen9 8-Bay 2.5\"\u003c\/a\u003e uses E5-4600 v3\/v4 (Haswell-EP \/ Broadwell-EP, Grantley platform). The E7 family delivers a higher per-CPU memory ceiling, more memory channels per CPU through the memory-cartridge architecture, and the C602J chipset's expanded RAS feature set (lockstep mode, MCA Recovery Execution Path, online memory sparing). For SAP HANA and other workloads requiring maximum per-server memory plus RAS, the E7 platform is materially different from E5.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e4U vs 2U.\u003c\/strong\u003e The DL580 Gen9's 4U chassis enables 9 PCIe slots (all FL\/FH), up to 4 GPUs, and the memory-cartridge drawer design for easy CPU and DIMM access. The DL560 Gen9 is 2U and trades expansion for density. For workloads that need both 4-socket compute AND extensive PCIe expansion (InfiniBand fabrics, multiple HBAs, GPU acceleration alongside CPU compute), the DL580 is the right answer; for 4-socket without heavy expansion, the DL560 is more cost-efficient at half the rack space.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eWithin the family, then, the DL580 Gen9 is the choice when the workload genuinely needs four E7 sockets with maximum memory, RAS, and PCIe expansion. When it does not, the 2U 4-socket DL560 Gen9 or the dual-socket DL380 Gen9 is the more economical Gen9 answer. The detailed case for when this platform still earns its place in 2026 is in the section below.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage - 5 SFF Bays Standard, Expandable to 10\u003c\/h2\u003e\u003cp\u003eThe DL580 Gen9 ships with 5 standard 2.5\" SAS\/SATA hot-swap bays in the front of the chassis. The Express Bay Kit (788359-B21) extends storage capacity to 10 drives total, including support for up to 5 NVMe drives in the upper bay position. The 5-bay standard configuration reflects the DL580's design priority: this is a compute and PCIe expansion platform, not a storage-dense server. Primary bulk storage is expected to live on SAN, NFS, or distributed file systems; local drives are typically for OS, application binaries, and hot dataset staging.\u003c\/p\u003e\u003cp\u003eCommon DL580 Gen9 storage configurations:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eOS plus application binaries (2-3 bays used).\u003c\/strong\u003e 2x SSDs in RAID 1 for OS, optional 1 SSD for application or log staging, primary data on SAN. The most common pattern for SAP HANA on certified Gen9 builds where data and log volumes live on certified external storage.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eOracle Database with local Fast Recovery Area.\u003c\/strong\u003e 2x SSDs for OS plus Oracle Grid Infrastructure binaries, 2-3 SSDs in RAID for local FRA or archive-log staging, primary database storage on SAN via a Fibre Channel HBA in PCIe expansion.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e5 NVMe upper-bay configuration (Express Bay Kit).\u003c\/strong\u003e 5 NVMe SSDs for a high-performance local storage tier. Useful where local NVMe latency is needed alongside SAN bulk storage. Requires the Express Bay Kit and appropriate PCIe lane provisioning.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e10-drive expanded configuration.\u003c\/strong\u003e Express Bay Kit installed, 10 SFF bays populated mixing SAS\/SATA SSDs and NVMe per workload - the maximum local storage configuration on the platform.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eFor OS boot on the DL580 Gen9, 2x SAS or SATA SSDs in RAID 1 in the standard SFF bays is the most common pattern. The platform does not have a dedicated M.2 slot on the system board the way Gen10 does - HPE's M.2 SSD enablement on Gen9 is via SATA M.2 adapter cards in PCIe slots, which is less elegant than the Gen10 integrated solution. For most production DL580 Gen9 builds, 2x SFF SSDs in the standard bays for OS is the right pattern, accepting the consumption of 2 of the 5 standard bays for boot.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Controllers\u003c\/h2\u003e\u003cp\u003eThe DL580 Gen9 ships with an embedded \u003ca href=\"\/products\/hpe-p830i-embedded-raid-dl580-g9\"\u003eHPE Smart Array P830i embedded RAID controller for the DL580 Gen9\u003c\/a\u003e - a 12 Gb\/s SAS controller embedded on the system board with 4 GB flash-backed write cache. This is a key difference from Gen10 platforms, where the type-a Smart Array controllers (P408i-a, P816i-a) plug into a dedicated slot. The P830i delivers full hardware RAID 0\/1\/5\/6\/10\/50\/60 and 12 Gb\/s SAS support.\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P830i (embedded, 4 GB FBWC).\u003c\/strong\u003e Standard with the chassis. Full hardware RAID across the 5 SFF bays (or 10 with Express Bay). 4 GB FBWC sized appropriately for the modest local drive count. The FBWC battery is a wear item - we disclose battery state on every quote and replace cache modules where the battery is past spec.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAdditional Smart Array controllers via PCIe.\u003c\/strong\u003e P441, P841, and Gen9-era controllers are available as PCIe plug-in cards for external SAS expansion (D3700 enclosures and similar). Relevant when the deployment needs more than 10 local bays via external chassis.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eHBA mode via P441 or H241.\u003c\/strong\u003e For software-defined storage on a 4-socket Gen9 platform (rare but supported - vSAN on Gen9, Ceph, ZFS), HBA-mode controllers deliver clean SAS pass-through.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThe HPE Smart Storage Battery is required for the embedded P830i and any added P-series controllers. We include the battery on every quote with P-series controllers. The battery is a documented wear item on Gen9 platforms - many refurbished units have batteries past their service life, which we replace as part of build prep when needed.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors\u003c\/h2\u003e\u003cp\u003e2, 3, or 4 sockets of Intel Xeon E7-4800\/8800 v3 (Haswell-EX) or v4 (Broadwell-EX) on the Intel C602J Brickland chipset. The platform requires a minimum of 2 CPUs; production deployments are almost always 4-socket, since that is the platform's value proposition. Mixing different processor models is not supported - all installed CPUs must be the same SKU, and v3 and v4 generations cannot be mixed.\u003c\/p\u003e\u003cp\u003eCPU options for production DL580 Gen9 builds:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eE7-8890 v4 (24 cores, 165W, DDR4-2400).\u003c\/strong\u003e The top-bin Broadwell-EX. 96 cores total at 4S - the maximum core count for the platform. The right pick when maximum cores in a single server is the requirement.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE7-8880 v4 (22 cores, 150W, DDR4-2400).\u003c\/strong\u003e 88 cores at 4S, a balanced TDP envelope for production workloads. A common SAP HANA and Oracle production CPU choice on the v4 generation.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE7-8890 v3 (18 cores, 165W, DDR4-1866).\u003c\/strong\u003e Top-bin Haswell-EX. 72 cores at 4S. Memory speed caps at DDR4-1866 versus DDR4-2400 on v4 - the v3 memory speed gap is material for memory-bandwidth-sensitive workloads.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE7-4830 v4 (14 cores, 115W, DDR4-2133).\u003c\/strong\u003e Lower-bin Broadwell-EX for cost-optimized 4-socket builds. 56 cores at 4S at a meaningfully lower TDP and acquisition cost.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eE7-8893 v4 (4 cores, 140W, DDR4-2400, 3.2 GHz).\u003c\/strong\u003e A high-frequency low-core-count SKU - 16 cores at 4S at 3.2 GHz base. The specialty pick for per-core licensing optimization where single-thread performance and minimum core count matter more than total core count.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eHeatsink and thermal note: the top-bin 165W E7 SKUs (E7-8890 v3\/v4) require the high-performance heatsink, and a 4-socket build at 165W per CPU is a serious thermal load even in the 4U chassis. Confirm the heatsink and fan configuration against the CPU selection at quote time; a common field error is pairing top-bin CPUs with a base heatsink kit.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eMemory\u003c\/h2\u003e\u003cp\u003eMemory architecture is materially different from Gen10. The DL580 Gen9 uses \u003cstrong\u003ememory cartridges\u003c\/strong\u003e: each CPU socket connects to 2 memory cartridges, each cartridge carrying 12 DIMM slots, for 24 DIMMs per CPU and 96 DIMMs total at 4S. The cartridge design enables tool-less access to DIMMs and CPUs via the chassis drawer mechanism - one of the platform's distinctive design features. Minimum population is 2 cartridges (one per CPU) and 4 DIMMs per server; maximum is 8 cartridges (96 DIMMs) at 4S.\u003c\/p\u003e\u003cp\u003eMaximum memory is 6 TB with 64 GB LRDIMMs across all 96 slots. RDIMM and LRDIMM cannot be mixed, and quad-rank LRDIMM is required for the maximum memory configurations. DDR4 speed depends on CPU generation: PC4-2133P (DDR4-2133) is required for v3 CPUs and runs at DDR4-1866 under full DIMM population; PC4-2400T (DDR4-2400) is required for v4 CPUs. DIMM-population rules drop memory speed under full population - at a full 96-DIMM configuration on v4 CPUs, expect DDR4-1866 or DDR4-1600 depending on rank and load. Memory bandwidth at 4S Gen9 is genuinely high, but the population rules matter for workload sizing: if peak bandwidth matters more than peak capacity, populate fewer DIMMs per channel.\u003c\/p\u003e\u003cp\u003eRAS features distinctive to the E7 platform: HPE Lockstep Memory Mode (paired-DIMM lockstep for SDDC+1 protection), MCA Recovery Execution Path (machine-check architecture recovery), Patrol and Demand Scrubbing (background ECC scrubbing), and Memory Online Spare Mode. These are meaningful for HANA, Oracle, and mission-critical SQL Server workloads where uncorrectable memory errors must be avoided in production. They are the main reason to choose the E7 DL580 over the E5 DL560 when the workload is RAS-sensitive.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking and PCIe Expansion\u003c\/h2\u003e\u003cp\u003eFlexibleLOM mezzanine handles primary networking - the standard FlexibleLOM architecture, same as the rest of the HPE ProLiant line. Networking options span 1 GbE quad-port (331FLR), 10 GbE SFP+ FlexFabric (534FLR-SFP+, 2 ports), 10 GbE base-T, and FlexFabric converged options. One quirk specific to the DL580 Gen9: \u003cstrong\u003eWake-on-LAN is not supported when using FlexibleLOM adapters\u003c\/strong\u003e. For deployments that depend on WoL for remote power-on (uncommon in 4-socket production but occasionally relevant for lab\/dev environments), use PCIe NICs rather than FlexLOM.\u003c\/p\u003e\u003cp\u003ePCIe expansion is genuine value on the DL580 Gen9: \u003cstrong\u003e9 PCIe Gen3.0 slots maximum\u003c\/strong\u003e with all 4 CPUs installed, all full-length \/ full-height. The standard slot layout is 4x PCIe 3.0 x8 plus 5x PCIe 3.0 x16. PCIe slot availability depends on CPU count - 2-CPU configurations leave some slots inactive because the lanes are anchored to the upper sockets. For workloads that pair 4-socket compute with InfiniBand fabrics, multiple Fibre Channel HBAs, or several add-in NICs, 9 Gen3 slots is real capability that the 2U DL560 platforms cannot match.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eGPU Support\u003c\/h2\u003e\u003cp\u003eThe DL580 Gen9 is one of the relatively few Gen9 4-socket platforms with serious GPU compute capability via PCIe. The 4U chassis and 9 full-length \/ full-height PCIe Gen3 slots support \u003cstrong\u003eup to 4 GPGPUs\u003c\/strong\u003e, with the practical limit set by PSU capacity and slot allocation rather than physical fit. Typical deployments use double-width passive accelerators of the Gen9 era (NVIDIA M40 \/ M60-class) or single-width inference cards (T4-class) where the workload favors density over per-card throughput.\u003c\/p\u003e\u003cp\u003eTwo constraints govern GPU builds on this platform. First, power: a 4-socket E7 build already draws heavily before GPUs, so multi-GPU configurations need the 1500W PSUs and 200-240VAC high-line input (see Power and Cooling). Second, generation: these are PCIe Gen3 slots. For modern training accelerators that assume PCIe Gen4\/Gen5 host bandwidth, the Gen3 link is a real ceiling - this platform is suited to inference, VDI acceleration, and legacy CUDA workloads validated on the Gen9 generation, not current-generation large-model training. If GPU throughput on a modern PCIe fabric is the goal, step to a Gen10 Plus or Gen11 platform; if the requirement is 4-socket CPU compute with supplementary GPU acceleration on validated Gen9 software stacks, the DL580 Gen9 delivers it.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eManagement - iLO 4 Generation\u003c\/h2\u003e\u003cp\u003eThe DL580 Gen9 ships with \u003cstrong\u003eHPE iLO 4\u003c\/strong\u003e firmware (NOT iLO 5 - that is Gen10). iLO 4 delivers the core management functionality: remote console access (iLO Advanced license required for graphical KVM), virtual media mounting, IPMI, SNMP telemetry, Active Health System logging, and integration with HPE OneView. The Gen9 iLO chip has 4 GB NAND storage with 1 GB of user-configurable space accessible via UEFI.\u003c\/p\u003e\u003cp\u003eImportant architectural difference from Gen10: \u003cstrong\u003eiLO 4 does not have Silicon Root of Trust\u003c\/strong\u003e. The hardware-anchored chain of trust that verifies firmware, BIOS, and OS bootloader from iLO silicon was introduced with iLO 5 on Gen10. For deployments subject to modern compliance audit (SOC 2 Type II, recent PCI-DSS revisions, FedRAMP) where platform-attestation evidence is required, iLO 4 \/ Gen9 does not deliver the same firmware-tampering protection. Standard UEFI Secure Boot is supported and is the right pattern for production Gen9 builds; expect compensating controls in the compliance framework around firmware integrity.\u003c\/p\u003e\u003cp\u003eiLO Advanced licensing is typically a separate cost - we quote it explicitly when the deployment requires full graphical remote KVM or virtual media beyond what iLO Standard delivers.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\u003cp\u003eHPE Common Slot power supplies, 2 to 4 PSUs depending on configuration. A minimum of 2 PSUs is required by HPE QuickSpecs. PSU options:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003e1200W Common Slot Platinum Plus (94% efficient).\u003c\/strong\u003e The standard production PSU for most DL580 Gen9 builds. Supports low-line (110-120VAC) and high-line (200-240VAC) input. 2x PSU for N+1 redundancy, 4x PSU for N+N redundancy in highly-loaded configurations.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e1500W Common Slot (high-line only).\u003c\/strong\u003e For high-TDP configurations with multiple GPUs or top-bin E7-8890 v4 CPUs at 4S. Requires 200-240VAC input and is not usable on standard 110V US circuits. 4x 1500W for full N+N at high TDP.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eMixing PSU models is not supported - all PSUs in a server must match. PSU selection matters: a fully-populated DL580 Gen9 with 4x E7-8890 v4 (165W each), 96 DDR4 DIMMs, 10 SSDs, and 4 GPUs can draw 1,800-2,500W sustained peak. At that draw, 4x 1500W is the right configuration; 4x 1200W is marginal. We run the HPE Power Advisor against every DL580 Gen9 quote to validate PSU sizing. The 4U chassis provides better thermal headroom than 2U platforms - ASHRAE A3 (40C) and A4 (45C) extended ambient support is documented on most configurations, which matters for deployments without dedicated server-room cooling. Confirm the specific configuration's inlet temperature spec at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePhysical Specs \u0026amp; Platform Notes\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eForm factor:\u003c\/strong\u003e 4U rack chassis. The depth and weight are substantial for a 4-socket scale-up box; plan rack real estate and a two-person lift for installation, and confirm rail-to-rack depth before delivery.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe expansion:\u003c\/strong\u003e 9 PCIe Gen3.0 slots maximum at 4S, all full-length \/ full-height (4x x8 + 5x x16). Slot count scales down with fewer CPUs because lanes are anchored to the upper sockets.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eParts availability:\u003c\/strong\u003e mature and strong. Gen9 spares depth (PSUs, fans, DIMM cartridges, P830i cache modules, drive carriers) is excellent across the secondary market, and established third-party maintenance providers carry field-engineer coverage in major metros now that HPE active support has ended.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAccessories we recommend:\u003c\/strong\u003e the \u003ca href=\"\/products\/hp-dl580-g9-sliding-rail-kit\"\u003eHPE DL580 Gen9 sliding rail kit\u003c\/a\u003e for a serviceable 4U mount (the cartridge-drawer design assumes the server can slide out for CPU\/DIMM access), the Express Bay Kit (788359-B21) when more than 5 local drives or NVMe are needed, and the HPE Smart Storage Battery for the embedded P830i.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePlatform notes:\u003c\/strong\u003e 3-socket configurations are not supported - the platform runs 2 or 4 CPUs only. CPU hot-plug is not supported. The memory-cartridge drawer mechanism is the distinctive serviceability feature; budget rack depth for the drawer to extend.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003e\u003cstrong\u003eWhere it excels:\u003c\/strong\u003e The DL580 Gen9 is at its best as a 4-socket scale-up box for RAS-sensitive, large-memory workloads on the E7 platform - SAP HANA on certified Gen9 builds, Oracle Database Enterprise on settled E7 licensing, and large-memory virtualization consolidation where 6 TB of DDR4 actually fits the working set. It is also the Gen9 4-socket platform to pick when the workload pairs CPU compute with heavy PCIe expansion (InfiniBand, multiple HBAs, or up to 4 GPGPUs), because the 4U chassis and 9 Gen3 slots give it expansion that the 2U DL560 platforms cannot match.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhere to look instead:\u003c\/strong\u003e If you need 4-socket compute without the expansion or the E7 RAS feature set, the 2U DL560 Gen9 on the E5-4600 platform is more cost-efficient at half the rack space. If most of the workload does not actually require four sockets, the dual-socket DL380 Gen9 covers the majority of Gen9 workloads at far lower cost. And if the deployment needs iLO 5 with Silicon Root of Trust, faster memory, and a current support path, step up to the DL560 Gen10 (linked in the section below). Each of these alternatives is linked under Where to Look Instead.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eBottom line:\u003c\/strong\u003e Buy the DL580 Gen9 when you are extending or matching an existing Gen9 scale-up fleet, when certified SAP HANA or settled Oracle E7 licensing makes the refurbished step cheaper than a generational jump, or when you need the maximum memory, RAS, and PCIe expansion that only the 4U E7 platform delivers at this generation. The typical buyer is a datacenter or enterprise team standardizing on Gen9 for operational consistency, or a budget-driven scale-up project where the workload's performance ceiling does not justify Gen10\/Gen11 acquisition cost. For greenfield mission-critical work, take the newer generation; for everything inside that Gen9 envelope, this is the right box.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL580 Gen9 Fits in 2026\u003c\/h2\u003e\u003cp\u003eThe Gen9 generation launched in 2014 (v3 \/ Haswell-EX) with a v4 refresh in 2016 (Broadwell-EX). HPE active warranty and Pointnext ProSupport on Gen9 hardware ended for v3 builds first and v4 builds following the standard HPE lifecycle. As of 2026, third-party maintenance from established providers is the standard production support pattern for both generations of the platform. We coordinate maintenance contracts as part of the build quote when requested - established TPM providers (Park Place, Service Express, Curvature, and others) maintain spares depth and field-engineer coverage for Gen9 hardware in major metros.\u003c\/p\u003e\u003cp\u003eTwo generations sit above Gen9 in HPE's roadmap: Gen10 (Skylake-SP launched 2017, Cascade Lake-SP refresh 2019), which introduced iLO 5 with Silicon Root of Trust and meaningful per-core performance improvements; and Gen10 Plus \/ Gen11 (Ice Lake-SP 2020, Sapphire Rapids 2023, Emerald Rapids 2024), which brought PCIe Gen4 and DDR5 to the 4-socket platform line. For new mission-critical SAP HANA, Oracle Database, or scale-up consolidation deployments where current-generation support, modern security baselines, and forward-looking platform headroom matter, the Gen10 Plus or Gen11 step is the right answer.\u003c\/p\u003e\u003cp\u003eThe DL580 Gen9 earns its place in 2026 specifically when one of these patterns applies: existing Gen9 operational standardization where adding capacity at the same generation reduces complexity; certified SAP HANA on Gen9 where the certification still applies and budget favors the refurbished step over current-generation acquisition; Oracle Database with E7 platform licensing that is already settled and operationally productive; large-memory virtualization where 6 TB DDR4 actually fits the working set; or lab\/dev\/staging environments mirroring Gen9 production for operational fidelity. Outside those patterns, Gen10 or current-generation is generally the better answer for new deployments.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eHPE active warranty and ProSupport on Gen9 has ended.\u003c\/strong\u003e Both v3 (2014) and v4 (2016) builds are out of HPE active support. Third-party maintenance from established providers (Park Place, Service Express, Curvature) is the standard production pattern; we coordinate maintenance contracts as part of the build quote when requested.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eiLO 4, not iLO 5 - no Silicon Root of Trust.\u003c\/strong\u003e Firmware-tampering protection is via UEFI Secure Boot only. For compliance frameworks requiring platform attestation, this is a documented gap versus Gen10.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDDR4 speed gap between v3 and v4 CPUs.\u003c\/strong\u003e v3 caps at DDR4-2133 (1866 under full DIMM population); v4 supports DDR4-2400. For memory-bandwidth-sensitive workloads, v4 is materially better than v3.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMemory speed drops under full DIMM population.\u003c\/strong\u003e At 96 DIMMs populated on v4 CPUs, expect DDR4-1866 or DDR4-1600 depending on DIMM rank and load. Full capacity loses bandwidth - that tradeoff has to be sized deliberately.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e5 standard SFF bays only; 10 with the Express Bay Kit.\u003c\/strong\u003e If the workload needs more than 10 local bays, the DL580 Gen9 is not the right chassis. Plan SAN or external chassis storage accordingly.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWake-on-LAN not supported with FlexibleLOM.\u003c\/strong\u003e Use PCIe NICs if WoL is a requirement. Production 4-socket deployments rarely depend on WoL, but it is worth noting.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSAP HANA certification status verification required.\u003c\/strong\u003e SAP HANA on Gen9 was certified at launch; certification status for ongoing SAP support requires explicit verification against SAP's current Certified and Supported SAP HANA Hardware Directory. We check this for every HANA-context quote.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eEmbedded P830i battery is a wear item.\u003c\/strong\u003e Gen9 FBWC batteries have a 5-7 year service life and many refurbished units have batteries past spec. We disclose state on every quote and replace cache modules where appropriate as part of build prep.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe Gen3 only.\u003c\/strong\u003e No PCIe Gen4\/Gen5. For workloads requiring PCIe Gen4 NICs, NVMe, or GPU bandwidth, this is a hard generational limit - step to Gen10 Plus or Gen11.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eThis server is right for\u003c\/th\u003e\n\u003cth\u003eConsider Gen10\/Gen11 for\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eCapacity-add to existing Gen9 SAP HANA deployments (cert check required)\u003c\/td\u003e\n\u003ctd\u003eNew greenfield mission-critical HANA\/Oracle\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eOracle Database Enterprise on existing E7 platform standardization\u003c\/td\u003e\n\u003ctd\u003eCompliance frameworks requiring Silicon Root of Trust\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eLarge-memory virtualization where 6 TB fits the working set\u003c\/td\u003e\n\u003ctd\u003eWorkloads requiring PCIe Gen4\/Gen5 bandwidth\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e4-socket workloads with 9 PCIe slots required and Gen3 is sufficient\u003c\/td\u003e\n\u003ctd\u003eProduction memory configurations above 6 TB\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eInference \/ VDI \/ legacy CUDA GPU acceleration alongside CPU compute\u003c\/td\u003e\n\u003ctd\u003eCurrent-generation large-model GPU training\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eLab\/dev\/staging mirroring Gen9 production\u003c\/td\u003e\n\u003ctd\u003eActive HPE ProSupport requirement\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed a Gen10 4-socket platform with iLO 5 and Silicon Root of Trust?\u003c\/strong\u003e The \u003ca href=\"\/products\/server-design-lab-hpe-dl560-g10-8-bay-2-5-drives\"\u003eHPE ProLiant DL560 Gen10 8-Bay 2.5\"\u003c\/a\u003e is the 2U 4-socket Gen10 flagship with the full modern feature set.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed 4-socket with high-density local SSD at Gen10?\u003c\/strong\u003e The \u003ca href=\"\/products\/server-design-lab-hpe-dl560-g10-24-bay-2-5-drives\"\u003eHPE ProLiant DL560 Gen10 24-Bay 2.5\"\u003c\/a\u003e pairs 24 SFF bays with 4 sockets at the Gen10 generation.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWant 4-socket Gen9 without the 4U expansion overhead?\u003c\/strong\u003e The \u003ca href=\"\/products\/hpe-proliant-dl560-gen9-8-bay-build-your-own\"\u003eHPE ProLiant DL560 Gen9 8-Bay 2.5\"\u003c\/a\u003e is the 2U E5-4600 alternative at half the rack space.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDual-socket sufficient at Gen9?\u003c\/strong\u003e The \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eHPE ProLiant DL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e covers most workloads that do not actually need 4-socket E7, at far lower cost.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDell shop alternative at the same 4U 4-socket Brickland tier?\u003c\/strong\u003e The Dell PowerEdge R930 is the 4U 4-socket E7-4800\/8800 v3\/v4 counterpart on the Dell side - equivalent positioning, same generation.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eDL580 Gen9 configurations require a design conversation. Tell us the workload (HANA \/ Oracle \/ SQL Server \/ virtualization \/ scale-up application), certification status if SAP HANA is in scope, CPU generation preference (v3 vs v4, with the memory-speed implications), memory target, storage requirement (5 standard or 10 with Express Bay including NVMe), PCIe expansion list (NICs, HBAs, GPUs, InfiniBand), PSU model (1200W vs 1500W), and quantity. We respond within 24 hours with a validated configuration including HPE Power Advisor sizing, certification verification when relevant, and third-party maintenance coordination if requested. Every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in testing, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951277465799,"sku":"BP-013626","price":1448.14,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-dl580-gen9-5-bay-25-drives-865516.png?v=1765539699"},{"product_id":"hpe-proliant-dl560-gen9-8-bay-build-your-own","title":"HPE ProLiant DL560 Gen9 8-Bay 2.5\" Drives [Gen9]","description":"\u003cp\u003eThe HPE ProLiant DL560 Gen9 8-Bay 2.5\" is HPE's Gen9 4-socket dense 2U platform, the Grantley counterpart to the DL580 Gen9 4U Brickland flagship. It is built around Intel Xeon E5-4600 v3 (Haswell-EP) or E5-4600 v4 (Broadwell-EP) processors on the Intel C610 Grantley platform, not the E7-4800\/8800 Brickland chips used in the DL580 Gen9. That CPU-family difference is the single most important thing to understand about this server. A 4-socket DL560 Gen9 carries up to four E5-4600 CPUs, 48 DDR4 DIMM slots, a 3 TB memory ceiling, eight 2.5\" SFF hot-swap bays, 6 PCIe Gen3 slots, FlexibleLOM networking, and iLO 4 management. It is the HPE architectural counterpart to the Dell PowerEdge R830 (2U 4-socket Grantley), same generation, same workload positioning.\u003c\/p\u003e\n\u003cp\u003eThe DL560 Gen9 is one generation behind the DL560 Gen10 (Purley, Skylake-SP \/ Cascade Lake-SP, 2017) and two generations behind the DL560 Gen11 (Sapphire Rapids \/ Emerald Rapids, DDR5, 2023). The platform launched in 2014 with the v3 silicon and was refreshed with v4 in 2016. As of 2026, HPE active warranty and Pointnext support on Gen9 hardware has ended, so third-party maintenance is the standard production support path. We are not going to soft-pedal Gen9's age: for new mission-critical scale-up deployments where current security baselines, DDR4-2933, PCIe Gen4, or active HPE support matter, the DL560 Gen10 step is the right answer. Where the DL560 Gen9 still earns its place is in budget-driven 4-socket consolidation, capacity-add to existing Gen9 fleets, and per-core-licensed Oracle and SQL Server hosts that fit within the 3 TB memory ceiling.\u003c\/p\u003e\n\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units. A DL560 Gen9 build benefits from a design conversation early: workload architecture, Oracle and SQL Server licensing implications, power budget at 4-socket TDP, and thermal validation in the 2U envelope all matter before hardware selection.\u003c\/p\u003e\n\u003chr\u003e\n\u003ch2\u003eDL560 Gen9 vs DL580 Gen9: The Platform Decision\u003c\/h2\u003e\n\u003cp\u003eBoth are HPE Gen9 4-socket platforms, but they are not interchangeable. The platform-fact differences drive the buying decision:\u003c\/p\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eCPU family.\u003c\/strong\u003e DL560 Gen9 uses E5-4600 v3\/v4 (Haswell-EP \/ Broadwell-EP) on the Grantley platform with the C610 chipset, the same silicon family as the DL380 Gen9 dual-socket but in a 4-socket layout. The DL580 Gen9 uses E7-4800\/8800 v3\/v4 (Haswell-EX \/ Broadwell-EX) on the Brickland platform, a different CPU family with a higher RAS feature set.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eMemory ceiling and slot count.\u003c\/strong\u003e DL560 Gen9 has 48 DIMM slots (12 per CPU) and a 3 TB ceiling. DL580 Gen9 has 96 DIMM slots through its memory-cartridge architecture and a 6 TB ceiling. The DL580 doubles the per-server memory ceiling at materially higher cost.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003ePCIe expansion.\u003c\/strong\u003e DL560 Gen9 provides 6 PCIe Gen3 slots in the 2U layout. DL580 Gen9 provides 9 PCIe Gen3 slots in a 4U layout for serious GPU and high-bandwidth expansion.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eForm factor.\u003c\/strong\u003e DL560 Gen9 is 2U, roughly one rack U per CPU, which is a genuine density advantage. DL580 Gen9 is 4U with drawer-style memory-cartridge access.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eRAS feature set.\u003c\/strong\u003e The DL580 Gen9 E7 platform delivers Lockstep memory mode, MCA Recovery, and expanded memory online sparing, which matter for workloads where uncorrectable memory errors must be avoided. The DL560 Gen9 E5 platform has standard ECC and patrol scrubbing but not the E7's expanded RAS set.\u003c\/li\u003e\n\u003c\/ul\u003e\n\u003cp\u003eChoose the DL560 Gen9 for budget-driven 4-socket consolidation, general-purpose 4-socket virtualization at Gen9, workloads that fit within the 3 TB memory ceiling, rack-density-driven deployments where 2U versus 4U matters, and any 4-socket workload that does not need E7 RAS features. Choose the \u003ca href=\"\/products\/hpe-proliant-dl580-gen9-5-bay-build-your-own\"\u003eDL580 Gen9 5-Bay 2.5\" 4U platform\u003c\/a\u003e when SAP HANA certification mandates the DL580 specifically, when E7 RAS features are required, when the memory requirement exceeds 3 TB, or when 4-socket plus extensive PCIe and GPU expansion is the design.\u003c\/p\u003e\n\u003chr\u003e\n\u003ch2\u003eWhere the DL560 Gen9 Fits in 2026\u003c\/h2\u003e\n\u003cp\u003eThe DL560 Gen9 launched in 2014 on the v3 silicon and was refreshed with the v4 step in 2016. HPE active warranty and Pointnext ProSupport on Gen9 hardware has ended; third-party maintenance is the standard production support path, and parts availability on the secondary market is broad and stable for both new-old-stock and reconditioned components.\u003c\/p\u003e\n\u003cp\u003eAbove this generation sits the DL560 Gen10 (Purley, iLO 5 with Silicon Root of Trust, DDR4-2933, HPE Persistent Memory) and then the DL560 Gen11 (Sapphire Rapids \/ Emerald Rapids, DDR5, PCIe Gen5). The generational step is the right answer for new mission-critical deployments that need current firmware security baselines, faster memory, PCIe Gen4 or Gen5, or active HPE support. For an organization standing up brand-new SAP HANA, Oracle, or scale-up consolidation infrastructure, plan around Gen10 or Gen11, not Gen9.\u003c\/p\u003e\n\u003cp\u003eThe DL560 Gen9 earns its place in 2026 specifically when one of these patterns applies: capacity-add to an existing Gen9 4-socket fleet where operational standardization is the driver; budget-driven 4-socket compute and memory consolidation where the E7 platform's premium is not justified; lab, dev, and staging environments that mirror Gen9 4-socket production; Oracle and SQL Server consolidation hosts where per-core licensing economics favor four sockets and the working set fits within 3 TB; and rack-density-constrained 4-socket deployments where the 2U chassis beats a 4U alternative on footprint.\u003c\/p\u003e\n\u003chr\u003e\n\u003ch2\u003eStorage: 8 SFF Bays\u003c\/h2\u003e\n\u003cp\u003eEight 2.5\" SAS\/SATA hot-swap bays sit in the front of the chassis. The 8-Bay configuration reflects the platform's design priority: 4-socket compute and memory consolidation rather than high-density local storage. Primary bulk storage is expected to live on SAN, NFS, or a distributed file system, with local drives carrying the OS, application binaries, hot dataset staging, and transaction logs.\u003c\/p\u003e\n\u003cp\u003eDrive options span the full Gen9 SFF portfolio: SAS SSDs in mixed-use and read-intensive endurance tiers, SATA SSDs for cost-optimized OS roles, SAS HDDs at 10K and 15K for moderate-IOPS data, NVMe SSDs via Express Bay (which consumes bay count), and self-encrypting drive variants for compliance-regulated deployments. For the full Gen9 drive portfolio detail, the \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\" platform page\u003c\/a\u003e documents the same drive ecosystem.\u003c\/p\u003e\n\u003cp\u003eCommon DL560 Gen9 8-Bay storage profiles in production:\u003c\/p\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eOracle Database with networked primary storage.\u003c\/strong\u003e Two SSDs in RAID 1 for the OS plus Oracle Grid binaries, two to four SSDs in RAID 1 or RAID 10 for Fast Recovery Area or archive logs, primary database on Fibre Channel or iSCSI SAN.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSQL Server Enterprise consolidation host.\u003c\/strong\u003e Two SSDs in RAID 1 for the OS, two in RAID 1 for tempdb, four in RAID 10 for transaction logs, primary data on SAN. Per-core SQL Server licensing economics drive the four-socket consolidation.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eMission-critical VMware cluster node.\u003c\/strong\u003e Two SSDs in RAID 1 for ESXi boot, remaining bays for a vSAN cache tier or left unused, primary VM storage on a shared SAN datastore. The four-socket compute drives high VM density per host.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eLarge-memory analytics or in-memory data grid.\u003c\/strong\u003e A single OS instance with up to 3 TB of memory paired with eight SFF SSDs for the OS, swap, and intermediate working data.\u003c\/li\u003e\n\u003c\/ul\u003e\n\u003ch3\u003eBoot Drives\u003c\/h3\u003e\n\u003cp\u003eM.2 SATA boot via the HPE M.2 SSD enablement card is the cleanest pattern for the 8-Bay configuration. It mounts in a PCIe slot and frees all eight SFF bays for data, which matters because the 8-bay storage budget is already tight against four-socket workload patterns. We default to M.2 boot on every DL560 Gen9 quote unless the customer specifies otherwise.\u003c\/p\u003e\n\u003chr\u003e\n\u003ch2\u003eStorage Controllers\u003c\/h2\u003e\n\u003cp\u003eThe DL560 Gen9 uses the Gen9 Smart Array family in modular and PCIe plug-in form factors:\u003c\/p\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSmart Array P440ar (2 GB FBWC).\u003c\/strong\u003e The mainstream production controller. Full hardware RAID 0\/1\/5\/6\/10\/50\/60 with a 2 GB flash-backed write cache. The right pick for the 8-bay configuration in most workloads.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSmart Array P840ar (4 GB FBWC).\u003c\/strong\u003e The premium controller. A larger write cache for write-intensive workloads such as SQL Server transaction logs and Oracle redo logs on local storage.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSmart Array H241 (HBA mode, PCIe).\u003c\/strong\u003e Clean SAS pass-through for vSAN, Storage Spaces Direct, Ceph, or ZFS where the storage abstraction is the hypervisor or distributed file system rather than the controller.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eDynamic Smart Array B140i (embedded software RAID).\u003c\/strong\u003e Acceptable for boot mirroring only, not for production data on a four-socket platform.\u003c\/li\u003e\n\u003c\/ul\u003e\n\u003cp\u003eThe HPE Smart Storage Battery is required when any P-series performance RAID controller is installed, and we include it in every quote that specifies one. The flash-backed write cache battery is a wear item with a finite service life, and we disclose its state on every quote.\u003c\/p\u003e\n\u003chr\u003e\n\u003ch2\u003eProcessors\u003c\/h2\u003e\n\u003cp\u003eThe DL560 Gen9 takes 2, 3, or 4 sockets of Intel Xeon E5-4600 v3 (Haswell-EP) or v4 (Broadwell-EP) on the Intel C610 Grantley chipset with the LGA 2011-3 socket. Production deployments are almost always four-socket, because that is the platform's entire value proposition. The four-socket configuration uses a CPU mezzanine board that carries sockets 3 and 4 plus their associated DIMM slots, the same architectural pattern as the DL560 Gen10.\u003c\/p\u003e\n\u003cp\u003eThe E5-4600 family is distinct from the E5-2600 family used in the DL380 Gen9 and DL360 Gen9. Both are Grantley on the C610 chipset, but the E5-4600 supports the four-socket QPI topology that the E5-2600 does not. Mixing CPU SKUs is not supported; all installed processors must be the same model, and v3 and v4 generations cannot be mixed.\u003c\/p\u003e\n\u003cp\u003eRepresentative CPU options for production four-socket builds:\u003c\/p\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eE5-4669 v4 (22 cores, 135W).\u003c\/strong\u003e Top-bin Broadwell-EP for this platform, 88 cores across four sockets. The maximum core count for the DL560 Gen9.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eE5-4660 v4 (16 cores, 120W).\u003c\/strong\u003e A balanced production pick at 64 cores across four sockets, for builds that need more cores than the 4640 without paying for the top bin.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eE5-4640 v4 (12 cores, 105W).\u003c\/strong\u003e Mid-tier production at 48 cores and a moderate thermal envelope, common for general four-socket virtualization and database consolidation.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eE5-4627 v4 (10 cores, 135W, higher base frequency).\u003c\/strong\u003e A higher-clock, lower-core-count specialty SKU for per-core-licensing optimization on Oracle and SQL Server.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eE5-4610 v4 (10 cores, 105W).\u003c\/strong\u003e The entry four-socket option at 40 cores and low cost.\u003c\/li\u003e\n\u003c\/ul\u003e\n\u003cp\u003eTop-bin configurations such as four E5-4669 v4 CPUs are at the edge of the 2U thermal envelope and require performance heatsinks and a high-performance fan kit; we validate the thermal configuration on every high-TDP quote.\u003c\/p\u003e\n\u003chr\u003e\n\u003ch2\u003eMemory\u003c\/h2\u003e\n\u003cp\u003eThe DL560 Gen9 has 48 DDR4 DIMM slots total, 12 per CPU across the four sockets. The E5-4600 Grantley platform runs \u003cstrong\u003efour memory channels per CPU at up to three DIMMs per channel\u003c\/strong\u003e (3 DPC), which is how 12 slots per socket are reached. This is the fact most often gotten wrong on this platform: it is four channels per CPU, not six. The six-channel figure belongs to the later Purley generation and does not apply to Grantley.\u003c\/p\u003e\n\u003cp\u003eMaximum memory is 3 TB across all 48 slots using 64 GB modules. RDIMM and LRDIMM cannot be mixed in the same system. Memory speed caps at DDR4-2133 on v3 CPUs and DDR4-2400 on v4 CPUs, and the speed steps down by one bin under full 3 DPC population. HPE DDR4 Smart Memory is required for rated-speed operation; third-party DDR4 drops to a lower speed regardless of the CPU's rated speed, which is the same documented behavior across the HPE Gen9 line.\u003c\/p\u003e\n\u003cp\u003eNote the architectural distinction from the DL580 Gen9: that platform carries 96 DIMM slots and a 6 TB ceiling through its memory-cartridge design. For a workload that needs more than 3 TB in a single host, the DL580 Gen9 or a Gen10 platform is the right answer. For workloads up to 3 TB, the DL560 Gen9 delivers four-socket scale-up at significantly lower cost. Balanced symmetric population across all populated sockets is required for predictable performance, and NUMA-aware placement matters at four sockets.\u003c\/p\u003e\n\u003chr\u003e\n\u003ch2\u003eNetworking and PCIe Expansion\u003c\/h2\u003e\n\u003cp\u003eFlexibleLOM mezzanine handles primary networking, the same architecture as the rest of the HPE ProLiant Gen9 line, with 1 GbE, 10 GbE SFP+, and 10GBASE-T options. FlexibleLOM does not consume a PCIe expansion slot, which is one of the platform's quiet advantages over designs that put primary networking on a plug-in card.\u003c\/p\u003e\n\u003cp\u003ePCIe expansion provides up to 6 PCIe Gen3 slots in the 2U four-socket layout. Slot availability depends on how many CPUs are populated; some slots are electrically inactive with fewer than four CPUs installed, because their lanes originate from sockets 3 and 4. For a four-socket build planning extensive add-in cards (HBAs, additional NICs, accelerators), confirm the slot map against the populated CPU count at design time.\u003c\/p\u003e\n\u003chr\u003e\n\u003ch2\u003eGPU Support\u003c\/h2\u003e\n\u003cp\u003eThe DL560 Gen9 is not a GPU compute platform. The 2U four-socket chassis supports at most single-width low-profile cards in the right slot positions, and its PCIe slot map and thermal budget were designed for four-socket CPU scale-up, not for double-width accelerators. If GPU compute is the workload, the four-socket \u003ca href=\"\/products\/hpe-proliant-dl580-gen9-5-bay-build-your-own\"\u003eDL580 Gen9 5-Bay 4U platform\u003c\/a\u003e is the right Gen9 answer, with its 9 PCIe slots and double-wide GPU support; for current-generation GPU density, look at a Gen10 or later platform built for accelerators.\u003c\/p\u003e\n\u003chr\u003e\n\u003ch2\u003eManagement: iLO 4 Generation\u003c\/h2\u003e\n\u003cp\u003eManagement is iLO 4, the Gen9 generation, not the iLO 5 that arrived with Gen10. iLO Standard ships with refurbished units; iLO Advanced licensing is typically a separate cost when full graphical remote KVM, virtual media mounting, and Active Health System telemetry are needed, and on a four-socket mission-critical platform iLO Advanced is rarely optional. We quote it explicitly with any DL560 Gen9 build.\u003c\/p\u003e\n\u003cp\u003eThe Gen9 firmware integrity baseline is UEFI Secure Boot. The DL560 Gen9 does not have the hardware-anchored Silicon Root of Trust that Gen10 introduced; if a documented hardware root-of-trust attestation chain is a compliance requirement, that is a reason to step to the \u003ca href=\"\/products\/server-design-lab-hpe-dl560-g10-8-bay-2-5-drives\"\u003eDL560 Gen10 8-Bay platform\u003c\/a\u003e. NUMA topology visibility through iLO 4 and HPE OneView is meaningful here, because workload placement across four sockets is consequential: cross-socket memory access carries a latency penalty, and hypervisor NUMA scheduling, database affinity settings, and OS process binding all matter for performance.\u003c\/p\u003e\n\u003chr\u003e\n\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\n\u003cp\u003eHPE Common Slot or Flex Slot power supplies handle power, with 2 to 4 PSUs in production configurations. A fully populated four-socket DL560 Gen9 with mid-tier CPUs and full memory draws roughly 1,000 to 1,400W sustained; with top-bin E5-4669 v4 CPUs and expansion, the draw rises to roughly 1,400 to 1,800W sustained.\u003c\/p\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003e2x 1200W PSU (typical production).\u003c\/strong\u003e Standard for most four-socket Gen9 builds, covering mid-tier CPU configurations in N+1 redundancy.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003e2x or 4x 1500W PSU (high TDP).\u003c\/strong\u003e Required for top-bin CPU configurations or builds with extensive expansion. The 1500W supplies require high-line input at 200 to 240VAC, so confirm rack PDU and circuit capacity.\u003c\/li\u003e\n\u003c\/ul\u003e\n\u003cp\u003eTake redundant PSU on every production build; the workloads that justify four sockets are workloads where unplanned downtime has documented cost. We run the HPE Power Advisor against every quote. Thermally, a 2U four-socket chassis is aggressive: ASHRAE A3 ambient operation is supported with performance heatsinks, and we confirm the inlet temperature spec for top-bin CPU configurations at quote time.\u003c\/p\u003e\n\u003chr\u003e\n\u003ch2\u003ePhysical Specs and Platform Notes\u003c\/h2\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eForm factor.\u003c\/strong\u003e 2U rack chassis carrying four sockets, roughly one rack U per CPU, a genuine density advantage over the 4U DL580 Gen9 for the same socket count. Confirm rack depth and rail clearance against your cabinet at quote time.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003ePCIe expansion.\u003c\/strong\u003e Up to 6 PCIe Gen3 slots in the four-socket layout, with availability tied to the populated CPU count as noted above.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eParts availability.\u003c\/strong\u003e Mature and broad. Gen9 components are widely available on the secondary market; with HPE active support ended, third-party maintenance is the standard production support path and we coordinate it on request.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eAccessories we recommend.\u003c\/strong\u003e The HPE 2U rail kit and cable management arm for the chassis (confirm the exact kit for your rack at quote), and the HPE M.2 SSD enablement card so OS boot does not consume an SFF data bay.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003ePlatform notes.\u003c\/strong\u003e The four-socket configuration requires the CPU mezzanine board carrying sockets 3 and 4; NUMA-aware workload placement is consequential at four sockets; high-TDP CPU builds require performance heatsinks and a high-performance fan kit; and FlexibleLOM networking does not consume a PCIe slot.\u003c\/li\u003e\n\u003c\/ul\u003e\n\u003chr\u003e\n\u003ch2\u003eOur Assessment\u003c\/h2\u003e\n\u003cp\u003e\u003cstrong\u003eWhere it excels.\u003c\/strong\u003e The DL560 Gen9 is at its best as a budget-driven four-socket scale-up host: Oracle and SQL Server consolidation where per-core licensing economics favor fewer sockets with more cores each, general four-socket virtualization standardized on Gen9, and capacity-add to an existing Gen9 fleet. The 2U footprint is a real advantage when rack density matters, and the E5-4600 platform delivers four-socket compute and up to 3 TB of memory at a fraction of the cost of current-generation four-socket hardware.\u003c\/p\u003e\n\u003cp\u003e\u003cstrong\u003eWhere to look instead.\u003c\/strong\u003e If the working set needs more than 3 TB per host, or the workload requires the E7 platform's Lockstep and MCA Recovery RAS features, the \u003ca href=\"\/products\/hpe-proliant-dl580-gen9-5-bay-build-your-own\"\u003eDL580 Gen9 4U platform\u003c\/a\u003e is the correct Gen9 choice. If you need iLO 5, Silicon Root of Trust, DDR4-2933, or active HPE support, step to the \u003ca href=\"\/products\/server-design-lab-hpe-dl560-g10-8-bay-2-5-drives\"\u003eDL560 Gen10 8-Bay platform\u003c\/a\u003e. If two sockets are genuinely sufficient, the \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e or the 1U \u003ca href=\"\/products\/dl360-g9-2-5-10-bay-hot-swap-psu\"\u003eDL360 Gen9 10-Bay 2.5\"\u003c\/a\u003e deliver the same Grantley generation at materially lower cost and complexity.\u003c\/p\u003e\n\u003cp\u003e\u003cstrong\u003eBottom line.\u003c\/strong\u003e The DL560 Gen9 is a precision tool for four-socket scale-up at Gen9 economics, not a default upgrade from a dual-socket server. It is the right buy when the workload genuinely needs four sockets, fits within 3 TB of memory, and does not require E7 RAS features or current-generation firmware security, and when acquisition cost is a meaningful design constraint.\u003c\/p\u003e\n\u003chr\u003e\n\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eMemory ceiling at 3 TB.\u003c\/strong\u003e Lower than the DL580 Gen9's 6 TB. For workloads needing more than 3 TB per host, the DL580 Gen9 or a Gen10 platform is correct.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eE5 RAS set, not E7.\u003c\/strong\u003e Standard ECC and patrol scrubbing rather than the DL580 Gen9's Lockstep, MCA Recovery, and expanded online sparing. For workloads that mandate E7-class RAS, the DL580 Gen9 is the right platform.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eFour-socket TDP in a 2U envelope.\u003c\/strong\u003e Top-bin E5-4669 v4 configurations sit at the edge of the thermal envelope and require performance heatsinks and high-performance fans.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eNo CPU mixing.\u003c\/strong\u003e All four CPUs must be the same SKU, and v3 and v4 generations cannot be mixed.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eLimited GPU expansion.\u003c\/strong\u003e Not a primary GPU compute platform. For four-socket plus GPU at Gen9, the DL580 Gen9 4U is correct.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eNUMA placement matters.\u003c\/strong\u003e Cross-socket memory access carries a latency penalty; hypervisor NUMA scheduling and database affinity settings all matter for performance.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eGen9 generational caveats apply.\u003c\/strong\u003e HPE active warranty ended, iLO 4 without Silicon Root of Trust, DDR4-2400 (v4) or DDR4-2133 (v3) speed cap with step-down under full population, PCIe Gen3 only, flash-backed write cache battery as a wear item, and HPE Smart Memory required for rated speeds.\u003c\/li\u003e\n\u003c\/ul\u003e\n\u003chr\u003e\n\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\n\u003ctable\u003e\n  \u003ctr\u003e\n\u003cth\u003eThis server is right for\u003c\/th\u003e\n\u003cth\u003eConsider alternatives for\u003c\/th\u003e\n\u003c\/tr\u003e\n  \u003ctr\u003e\n\u003ctd\u003eBudget-driven 4-socket consolidation at Gen9\u003c\/td\u003e\n\u003ctd\u003eMemory requirements above 3 TB (use DL580 Gen9 or DL560 Gen10)\u003c\/td\u003e\n\u003c\/tr\u003e\n  \u003ctr\u003e\n\u003ctd\u003eOracle and SQL Server per-core licensing optimization\u003c\/td\u003e\n\u003ctd\u003eE7 RAS feature requirements (use DL580 Gen9)\u003c\/td\u003e\n\u003c\/tr\u003e\n  \u003ctr\u003e\n\u003ctd\u003e4-socket virtualization standardized on Gen9\u003c\/td\u003e\n\u003ctd\u003eNew mission-critical deployments needing iLO 5 (use DL560 Gen10)\u003c\/td\u003e\n\u003c\/tr\u003e\n  \u003ctr\u003e\n\u003ctd\u003eCapacity-add to an existing DL560 Gen9 fleet\u003c\/td\u003e\n\u003ctd\u003eGPU compute at 4-socket (use DL580 Gen9 4U)\u003c\/td\u003e\n\u003c\/tr\u003e\n  \u003ctr\u003e\n\u003ctd\u003eLab, dev, and staging mirroring 4-socket Gen9 production\u003c\/td\u003e\n\u003ctd\u003eActive HPE ProSupport requirements\u003c\/td\u003e\n\u003c\/tr\u003e\n  \u003ctr\u003e\n\u003ctd\u003eRack-density 4-socket where 2U versus 4U matters\u003c\/td\u003e\n\u003ctd\u003eWorkloads requiring PCIe Gen4 or DDR4-2933 and faster\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\n\u003chr\u003e\n\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eNeed the E7 platform with 96 DIMMs and a 6 TB ceiling?\u003c\/strong\u003e The \u003ca href=\"\/products\/hpe-proliant-dl580-gen9-5-bay-build-your-own\"\u003eDL580 Gen9 5-Bay 2.5\"\u003c\/a\u003e is the 4U 4-socket Brickland flagship for scale-up workloads.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eNeed Gen10 4-socket with iLO 5 and Silicon Root of Trust?\u003c\/strong\u003e The \u003ca href=\"\/products\/server-design-lab-hpe-dl560-g10-8-bay-2-5-drives\"\u003eDL560 Gen10 8-Bay 2.5\"\u003c\/a\u003e is the current-generation four-socket platform.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eDual-socket Gen9 sufficient, 2U?\u003c\/strong\u003e The \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eDL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e is the 2U dual-socket Grantley mainstream.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eDual-socket Gen9 sufficient, 1U?\u003c\/strong\u003e The \u003ca href=\"\/products\/dl360-g9-2-5-10-bay-hot-swap-psu\"\u003eDL360 Gen9 10-Bay 2.5\"\u003c\/a\u003e is the 1U dual-socket Grantley option.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eDell shop alternative at the same Gen9 4-socket 2U tier?\u003c\/strong\u003e The Dell PowerEdge R830 is the 2U 4-socket E5-4600 Grantley counterpart, equivalent positioning, same generation.\u003c\/li\u003e\n\u003c\/ul\u003e\n\u003chr\u003e\n\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\n\u003cp\u003eA DL560 Gen9 build starts with a design conversation. Tell us the workload (Oracle, SQL Server, virtualization, SAP HANA at Gen9, or general four-socket consolidation), the licensing context (per-core or per-socket), the CPU and core target, the memory target within the 3 TB ceiling, the storage configuration, the FlexibleLOM choice, the PSU and redundancy preference, and the quantity. We respond within 24 hours with a validated configuration including HPE Power Advisor sizing, thermal validation for high-TDP builds, and third-party maintenance coordination when requested. Every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in testing, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951278022855,"sku":"BP-013623","price":489.85,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl560-gen9-8-bay-25-156055.png?v=1765539699"},{"product_id":"hpe-proliant-dl180-gen9-lff-build-your-own","title":"HPE ProLiant DL180 Gen9 LFF 3.5\" Drives [Gen9]","description":"\u003cp\u003eThe HPE ProLiant DL180 Gen9 LFF is HPE's value-tier 2U dual-socket Gen9 platform, the cost-optimized counterpart to the DL380 Gen9 mainstream tier. It is built around Intel Xeon E5-2600 v3 (Haswell-EP) or v4 (Broadwell-EP) processors on the Grantley platform with the C610 chipset, the same silicon family as the DL380 and DL360 Gen9. Two sockets, up to 22 cores per CPU on v4, 16 DDR4 DIMM slots (8 per CPU, half the DL380 Gen9's 24-slot count and the primary value-tier delta), a 1 TB memory ceiling, and LFF (3.5\") drive bays in 8 LFF or 15 LFF configurations depending on chassis variant. Storage controllers are PCIe plug-in cards rather than the modular \"ar\" form factor, networking is embedded 4-port 1 GbE, and management is iLO 4. This is the HPE counterpart to the Dell PowerEdge R530 (2U dual-socket Grantley value-tier), positioned for budget-driven bulk-storage, branch, ROBO, and SMB workloads where the DL380 Gen9's mainstream feature set is more than the workload requires.\u003c\/p\u003e\u003cp\u003eThe DL180 Gen9 is a generation behind the Gen10 line (Skylake-SP and Cascade Lake-SP, launched 2017) and two generations behind the Gen10 Plus and Gen11 platforms. It launched across the 2014 to 2016 window with the Haswell-EP and Broadwell-EP E5-2600 refresh. As of 2026, HPE active warranty and standard ProLiant support on Gen9 hardware has ended, and third-party maintenance is the standard production support path. We are not going to soft-pedal Gen9's age: for new mission-critical deployments that need iLO 5 with Silicon Root of Trust, faster DDR4, or an active vendor support contract, the Gen10 step is the right answer. Where the DL180 Gen9 still earns its place is in budget-driven capacity and branch workloads where acquisition cost per usable terabyte is the deciding factor.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL180 Gen9 Fits in the Family\u003c\/h2\u003e\u003cp\u003eHPE positions the DL180 Gen9 as the value-tier 2U dual-socket Gen9 platform, the budget-driven alternative to the DL380 Gen9 mainstream. The platform-fact differences from the DL380 Gen9:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003e16 DIMM slots versus 24.\u003c\/strong\u003e 8 DIMMs per CPU on the DL180 Gen9 versus 12 on the DL380 Gen9. Both use the same four memory channels per CPU; the DL180 Gen9 populates two DIMMs per channel (2 DPC) where the DL380 Gen9 reaches three DIMMs per channel (3 DPC). Maximum memory is 1 TB with 64 GB RDIMMs versus the DL380 Gen9's 3 TB ceiling.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array PCIe plug-in only, no modular \"ar\" slot.\u003c\/strong\u003e The DL180 Gen9 does not have the dedicated modular controller slot the DL380 Gen9 introduced. The storage controller consumes a PCIe slot. P440 (2 GB FBWC) and P840 (4 GB FBWC) in PCIe form factor are the production controllers; H241 is the HBA for software-defined storage.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eReduced PCIe expansion.\u003c\/strong\u003e Three PCIe Gen3 slots standard with one riser, expandable to six with the secondary riser kit, which requires the second CPU. The six-slot maximum matches the DL380 Gen9, but the default is fewer slots and the riser requirements differ.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eFlexibleLOM is optional via a separate riser kit.\u003c\/strong\u003e Unlike the DL380 Gen9, where FlexibleLOM sits on a dedicated mezzanine, on the DL180 Gen9 the FlexibleLOM riser kit adds FlexLOM capability but consumes one of the available PCIe positions. Embedded 4-port 1 GbE is standard.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDrive bay configurations.\u003c\/strong\u003e Two main LFF chassis variants: 8 LFF and 15 LFF. The 8 LFF chassis is the standard value-tier configuration; the 15 LFF chassis (12 front LFF plus 3 rear LFF) is the high-density option. Specify the chassis variant at quote time based on the bay-count requirement.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eiLO 4 Standard.\u003c\/strong\u003e The same iLO 4 generation as the rest of the Gen9 line, but the DL180 Gen9 typically ships with iLO Standard licensing; iLO Advanced is a separate cost when a full graphical remote console is needed.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch2\u003eStorage - LFF Chassis Variants\u003c\/h2\u003e\u003cp\u003eThe DL180 Gen9 chassis is available in multiple LFF configurations:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003e8 LFF chassis (standard value-tier).\u003c\/strong\u003e Eight 3.5\" front bays. The most common DL180 Gen9 configuration, delivering branch-scale and SMB-scale bulk capacity at the lowest acquisition cost.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e15 LFF chassis (high-density variant).\u003c\/strong\u003e Twelve 3.5\" front bays plus three rear 3.5\" bays. The maximum LFF configuration on the DL180 Gen9, approaching DL380 Gen9 12-Bay capacity at value pricing.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eMixed LFF plus rear SFF variants.\u003c\/strong\u003e Some chassis configurations support 8 LFF plus 2 rear SFF for OS boot. This is build-spec dependent.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eDrive options span the standard Gen9 LFF portfolio: NL-SAS HDDs (4 to 14 TB MDL across the Gen9 lifecycle), 10K and 15K SAS HDDs (lower capacity ceiling), LFF SSDs (rarely the right choice at this tier), and SED variants for compliance.\u003c\/p\u003e\u003cp\u003eCommon DL180 Gen9 storage profiles:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eBranch office file server (8 LFF chassis).\u003c\/strong\u003e Eight 8 to 12 TB NL-SAS HDDs in RAID 6 deliver roughly 48 to 72 TB usable for branch SMB\/NFS shares, document storage, and archive at lower cost than the DL380 Gen9 alternative.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eVeeam backup repository (15 LFF chassis).\u003c\/strong\u003e Twelve front plus three rear LFF. RAID 6 across the twelve front bays plus a RAID 1 mirror on the rear bays for repository metadata, or a full 15-drive RAID 60. A strong pick for branch and mid-size backup deployments.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eArchive and compliance retention (8 LFF or 15 LFF).\u003c\/strong\u003e Long-term sequential-write workloads where capacity-per-dollar matters more than per-host feature set.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSurveillance NVR (small to mid scale, 15 LFF).\u003c\/strong\u003e Twelve to fifteen LFF bays for multi-camera video retention.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDistributed file system nodes at value pricing (Ceph, MinIO).\u003c\/strong\u003e Lower per-node cost for capacity-tier deployments where total cluster capacity matters more than per-node feature set.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSMB primary server with bulk capacity.\u003c\/strong\u003e A single 2U LFF host combining file services, application hosting, and modest virtualization for a small business.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eRAID at LFF Scale\u003c\/h3\u003e\u003cp\u003eThe LFF RAID guidance matches the DL380 Gen9 12-Bay LFF: RAID 6 is strongly preferred for production bulk storage because dual parity tolerates a second-drive failure during multi-day rebuild windows; RAID 60 suits larger drive capacities (10 to 14 TB) where reducing rebuild scope matters; RAID 10 fits write-intensive workloads where the 50 percent capacity overhead is acceptable; RAID 5 is not recommended at LFF capacity. JBOD and HBA pass-through via the H241 controller serve ZFS, Ceph, MinIO, and other software-defined storage stacks.\u003c\/p\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eBoot options on the LFF chassis: M.2 SATA via the HPE M.2 enablement card in a PCIe slot (preserves all front bays); a rear 2 SFF bay kit (on chassis variants that support it); or two front LFF bays in RAID 1 (consuming 2 of 8 or 2 of 15 LFF bays). On the 8 LFF chassis, consuming two bays for boot is 25 percent of the storage budget, so M.2 boot is strongly preferred. On the 15 LFF chassis, the rear-bay SFF kit is the standard pattern. We default to M.2 boot on 8 LFF quotes and rear-bay 2 SFF on 15 LFF quotes.\u003c\/p\u003e\u003ch2\u003eStorage Controllers\u003c\/h2\u003e\u003cp\u003eThe DL180 Gen9 uses PCIe plug-in Smart Array controllers; there is no modular \"ar\" slot, which is a DL380 Gen9 family feature. Controller options:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P440 (PCIe, 2 GB FBWC).\u003c\/strong\u003e The mainstream production controller. Full hardware RAID 0\/1\/5\/6\/10\/50\/60. The right pick for 8 LFF builds with traditional hardware RAID.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P840 (PCIe, 4 GB FBWC).\u003c\/strong\u003e The premium controller. The larger cache suits write-intensive workloads such as Veeam backup ingest and sustained-write archive. The right pick for 15 LFF builds with heavy sustained write.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array H241 (PCIe, HBA mode).\u003c\/strong\u003e A clean SAS pass-through HBA for software-defined storage (ZFS, Ceph, MinIO).\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDynamic Smart Array B140i (embedded software RAID).\u003c\/strong\u003e Chipset-integrated software RAID, acceptable for M.2 boot mirroring only and not appropriate for production data.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eAn HPE Smart Storage Battery is required with the P-series controllers. The FBWC battery is a documented Gen9 wear item; we disclose battery state on every quote and replace cache modules carrying past-spec batteries as part of build prep. Because the controller is PCIe rather than modular, it consumes one of the available slots: on a three-slot configuration the storage controller, a FlexibleLOM riser, and any additional expansion card need careful slot allocation. The six-slot maximum with the secondary riser gives more headroom for combined storage, networking, and expansion builds.\u003c\/p\u003e\u003ch2\u003eProcessors\u003c\/h2\u003e\u003cp\u003eOne or two sockets of Intel Xeon E5-2600 v3 (Haswell-EP, 2014) or v4 (Broadwell-EP, 2016) on the C610 Grantley platform, socket LGA 2011-3, up to 22 cores per CPU on v4. This is the same processor stack as the DL380 and DL360 Gen9, so CPU sourcing and field experience carry across the Gen9 fleet. v3 and v4 cannot be mixed in one system, and a v3-to-v4 field upgrade replaces both CPUs together.\u003c\/p\u003e\u003cp\u003eDL180 Gen9 CPU selection skews toward the lower-bin and mid-tier parts (E5-2620 v4, E5-2640 v4, E5-2650 v4), consistent with the value-tier positioning and the branch, backup, and archive workloads the platform serves. Top-bin parts such as the E5-2699 v4 (22 cores, 145W) or E5-2667 v4 (135W) are supported but require the performance heatsink and fan kit, and they are rarely the right economics on a value-tier 2U. The configuration trap to avoid is the single-socket build: populating only one CPU strands half the DIMM slots and the riser positions that depend on the second processor, so a single-socket DL180 Gen9 is the right call only when the workload genuinely will not grow into the second socket.\u003c\/p\u003e\u003ch2\u003eMemory\u003c\/h2\u003e\u003cp\u003eSixteen DDR4 DIMM slots, eight per CPU. This is the defining value-tier delta against the DL380 Gen9's 24 slots. The architecture is four memory channels per CPU populated at two DIMMs per channel (2 DPC); the DL380 Gen9 reaches three DIMMs per channel (3 DPC) across the same four channels, which is how it gets to 24 slots. Maximum memory on the DL180 Gen9 is 1 TB with 64 GB RDIMMs.\u003c\/p\u003e\u003cp\u003eRDIMM is the mainstream choice; LRDIMM is available where the largest module capacities are needed to approach the 1 TB ceiling, and RDIMM and LRDIMM cannot be mixed. Rated speeds are DDR4-2400 on v4 and DDR4-2133 on v3, and full DIMM population steps the speed down under the standard Gen9 population rules. HPE DDR4 Smart Memory is required to reach rated speeds; third-party DDR4 drops to a lower bus speed. A single-CPU configuration exposes only the eight slots on the populated socket, the other reason the single-socket build is usually a false economy on this platform.\u003c\/p\u003e\u003ch2\u003eNetworking and PCIe Expansion\u003c\/h2\u003e\u003cp\u003eEmbedded 4-port 1 GbE (the 331i adapter) is standard. FlexibleLOM is optional through the FlexibleLOM riser kit, which adds the FlexLOM slot but consumes one of the available PCIe positions; this differs from the DL380 Gen9, where FlexLOM lives on a dedicated mezzanine that does not cost a PCIe slot. For deployments that need 10 GbE or 25 GbE, the FlexLOM riser is the typical path; for the 1 GbE-sufficient workloads that drive most DL180 Gen9 deployments (branch file servers, modest backup targets), the embedded ports are enough.\u003c\/p\u003e\u003cp\u003ePCIe expansion is three Gen3 slots by default, expandable to six with the secondary riser kit, which requires the second CPU. Because the storage controller and any FlexibleLOM riser draw from the same pool of slots, plan the slot budget up front: a typical production build allocates one slot to the Smart Array controller, one to the FlexLOM riser when 10 GbE is required, and leaves the remainder for HBAs or additional NICs.\u003c\/p\u003e\u003ch2\u003eGPU Support\u003c\/h2\u003e\u003cp\u003eThe DL180 Gen9 is not a GPU platform. The value-tier 2U chassis allocates its PCIe and power budget to storage and networking, it does not support double-wide accelerators, and the workloads it is built for (bulk capacity, backup, archive) do not call for GPU compute. If a build needs GPU acceleration, the right answer is a platform with the thermal envelope and PCIe budget for the cards: for a current-generation 2U, see the \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eHPE ProLiant DL380 Gen10 12-Bay 3.5\" Drives\u003c\/a\u003e, or tell us the accelerator at quote time and we will size a GPU-capable chassis instead.\u003c\/p\u003e\u003ch2\u003eManagement - iLO 4 Generation\u003c\/h2\u003e\u003cp\u003eManagement is HPE Integrated Lights-Out 4 (iLO 4). The DL180 Gen9 ships with iLO Standard, which covers health monitoring, the Active Health System log, IPMI, and basic remote management; iLO Advanced licensing is a separate cost and unlocks the full graphical remote console and virtual media. There is no Silicon Root of Trust at this generation, that hardware-anchored firmware verification arrived with iLO 5 on Gen10, so UEFI Secure Boot is the firmware-integrity baseline here. The practical upside is fleet consistency: the same iLO 4 generation runs across every Gen9 ProLiant, so a shop already operating Gen9 hardware manages the DL180 Gen9 with the tools and runbooks it already has.\u003c\/p\u003e\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\u003cp\u003eHPE Flex Slot power supplies in 1+1 redundant configurations. PSU selection skews to the lower wattages (500W and 800W) that match the value-tier workload mix; the 1400W high-output supplies are rarely needed because branch file servers, backup targets, and archive storage are not high-TDP. Two 800W Platinum supplies in 1+1 redundancy cover most production DL180 Gen9 configurations. The 2U chassis with LFF storage runs comfortably in standard data-center cooling, supports ASHRAE A3 (40 C) extended ambient, and the lower CPU TDP typical of these deployments sits well inside the 2U thermal envelope.\u003c\/p\u003e\u003ch2\u003ePhysical Specs \u0026amp; Platform Notes\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eForm factor:\u003c\/strong\u003e 2U rack chassis at standard rack depth; an HPE 2U cable management arm is available for serviceable cable routing.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe expansion:\u003c\/strong\u003e three Gen3 slots by default and up to six with the secondary riser (requires the second CPU), in a mix of full-height and low-profile positions depending on riser configuration.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eParts availability:\u003c\/strong\u003e Gen9 secondary-market supply is mature and strong; drives, PSUs, risers, rail kits, and FBWC cache modules are all readily sourced. HPE active support has ended, so third-party maintenance is the production support path.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAccessories we recommend:\u003c\/strong\u003e the matching HPE 2U LFF sliding rail kit (P\/N 737413-001), a cable management arm, an M.2 enablement card for boot, and the FlexibleLOM riser kit when 10 GbE networking is required.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePlatform notes:\u003c\/strong\u003e the 8 LFF versus 15 LFF chassis choice is a build-spec decision and not practically field-upgradable; the FBWC battery is a Gen9 wear item we disclose and replace during build prep; and HPE Smart Memory is required for rated DDR4 speeds.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003e\u003cstrong\u003eWhere it excels:\u003c\/strong\u003e The DL180 Gen9 is at its best in budget-driven capacity roles: branch and ROBO file servers, Veeam backup repositories at moderate scale, archive and compliance retention, small-to-mid surveillance NVR, and capacity-tier distributed-storage nodes (Ceph, MinIO) where per-node cost is what matters. In each of these the platform delivers genuine work at materially lower acquisition cost than the mainstream tier, because the workload fits comfortably inside 1 TB of memory and modest PCIe expansion.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhere to look instead:\u003c\/strong\u003e When the workload needs more than 1 TB of memory or a modular \"ar\" Smart Array controller, the \u003ca href=\"\/products\/hp-proliant-dl380-g9-12-bay-3-5-chassis\"\u003eHPE ProLiant DL380 Gen9 12-Bay 3.5\" Drives\u003c\/a\u003e is the right step up. For 1U LFF at the edge or branch, the \u003ca href=\"\/products\/dl360-g9-3-5-4-bay-chassis\"\u003eHPE ProLiant DL360 Gen9 4-Bay 3.5\" Drives\u003c\/a\u003e or the value-tier 1U \u003ca href=\"\/products\/hpe-proliant-dl160-gen9-4-bay-lff-build-your-own\"\u003eHPE ProLiant DL160 Gen9 4-Bay 3.5\" Drives\u003c\/a\u003e fit a smaller footprint. For a current generation with iLO 5, move to the \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eHPE ProLiant DL380 Gen10 12-Bay 3.5\" Drives\u003c\/a\u003e. Buyers shopping Dell will find the equivalent in the \u003ca href=\"\/products\/dell-poweredge-r530-8-bay-chassis\"\u003eDell PowerEdge R530 8-Bay 3.5\" Drives\u003c\/a\u003e.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eBottom line:\u003c\/strong\u003e The DL180 Gen9 is the value 2U LFF box for an organization buying branch, backup, and archive capacity where dollars-per-usable-terabyte is the deciding number and the per-host feature set of the mainstream tier would go unused. The typical buyer is a budget-conscious IT team standing up or expanding bulk storage, comfortable running on third-party maintenance, and choosing the platform precisely because it does less than a DL380 and costs less to match. If that describes the deployment, the DL180 Gen9 is the correct, defensible choice.\u003c\/p\u003e\u003ch2\u003eWhere the DL180 Gen9 Fits in 2026\u003c\/h2\u003e\u003cp\u003eThe DL180 Gen9 launched on Haswell-EP (E5-2600 v3) in 2014 and carried the Broadwell-EP (v4) refresh in 2016. The Gen10 line that sits above it arrived in 2017 on the Skylake-SP and Cascade Lake-SP platform. As of 2026, HPE active warranty and standard ProLiant support on Gen9 hardware has ended, and third-party maintenance is the standard, well-supported production path for the platform.\u003c\/p\u003e\u003cp\u003eWhat sits above the DL180 Gen9 in HPE's roadmap is the Gen10 mainstream (the DL380 Gen10, with iLO 5 and Silicon Root of Trust, faster DDR4, and the 24-DIMM, 3 TB memory topology) and beyond it the Gen10 Plus and Gen11 platforms on Ice Lake and Sapphire Rapids. The generational step up is the right answer for new mission-critical workloads, for anything that needs hardware-anchored firmware security, and for memory or expansion requirements the value tier cannot meet. The Gen8 predecessor is end-of-support and not something we stock or recommend in 2026.\u003c\/p\u003e\u003cp\u003eThe DL180 Gen9 earns its place in 2026 specifically when one of these patterns applies: a capacity-add to an existing Gen9 fleet where operational standardization and matching spares matter; a lab, dev, or staging tier mirroring Gen9 production at the lowest cost; a budget-driven branch, backup, or archive deployment where capacity-per-dollar is the deciding factor; a certified or fixed-image workload validated on the Gen9 platform; or a bulk-storage role where the mainstream tier's features would simply go unused. Outside those patterns, price the Gen10 step and compare.\u003c\/p\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eThe standard Gen9 platform limitations apply.\u003c\/strong\u003e HPE active warranty has ended; iLO 4 has no Silicon Root of Trust; DDR4 speeds cap below the Gen10 line; PCIe is Gen3 only; the FBWC battery is a wear item; and HPE Smart Memory is required for rated speeds.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e16 DIMM slots, 1 TB memory ceiling.\u003c\/strong\u003e Eight fewer DIMMs per system than the DL380 Gen9. Workloads needing more than 1 TB belong on the DL380 Gen9.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNo modular \"ar\" Smart Array slot.\u003c\/strong\u003e The storage controller consumes a PCIe slot; allocate carefully on three-slot default configurations.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eFlexibleLOM via a separate riser kit only.\u003c\/strong\u003e FlexLOM requires the riser kit and consumes a PCIe position; the DL380 Gen9's dedicated FlexLOM mezzanine does not exist here.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eiLO Advanced is typically a separate cost.\u003c\/strong\u003e The DL180 Gen9 ships with iLO Standard; the full remote graphical console requires Advanced licensing.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eLFF rebuild times run into days at production load.\u003c\/strong\u003e RAID 6 or RAID 60 is strongly preferred; RAID 5 is high-risk at LFF capacity.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eBoot-drive consumption hits the 8 LFF chassis hard.\u003c\/strong\u003e Two bays for an OS RAID 1 mirror is 25 percent of the 8 LFF budget; M.2 boot is strongly preferred.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eChassis-variant selection is a build-time decision.\u003c\/strong\u003e Moving between 8 LFF and 15 LFF chassis is not a practical field upgrade.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eThis server is right for\u003c\/th\u003e\n\u003cth\u003eConsider alternatives for\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBudget-driven branch, ROBO, and SMB deployments\u003c\/td\u003e\n\u003ctd\u003eMemory requirements above 1 TB (use the DL380 Gen9)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eVeeam backup targets at moderate scale\u003c\/td\u003e\n\u003ctd\u003eExtensive PCIe expansion needs\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBulk-capacity file servers within the 1 TB ceiling\u003c\/td\u003e\n\u003ctd\u003eWorkloads requiring a modular \"ar\" Smart Array\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eArchive and compliance retention at value pricing\u003c\/td\u003e\n\u003ctd\u003eNew mission-critical deployments needing iLO 5\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eSurveillance NVR at small to mid scale\u003c\/td\u003e\n\u003ctd\u003eMemory-bandwidth-sensitive workloads\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eDistributed file-system nodes at lower per-node cost\u003c\/td\u003e\n\u003ctd\u003eAn active HPE ProSupport requirement\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed more than 1 TB of memory at Gen9 LFF?\u003c\/strong\u003e The \u003ca href=\"\/products\/hp-proliant-dl380-g9-12-bay-3-5-chassis\"\u003eHPE ProLiant DL380 Gen9 12-Bay 3.5\" Drives\u003c\/a\u003e is the mainstream 2U LFF with 24 DIMMs and a 3 TB ceiling.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed a modular Smart Array \"ar\" controller?\u003c\/strong\u003e The same \u003ca href=\"\/products\/hp-proliant-dl380-g9-12-bay-3-5-chassis\"\u003eDL380 Gen9 12-Bay 3.5\"\u003c\/a\u003e carries the modular controller slot.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed 1U LFF for edge or branch?\u003c\/strong\u003e The \u003ca href=\"\/products\/dl360-g9-3-5-4-bay-chassis\"\u003eHPE ProLiant DL360 Gen9 4-Bay 3.5\" Drives\u003c\/a\u003e is the 1U dual-socket LFF with a smaller footprint.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWant the value-tier 1U at Gen9?\u003c\/strong\u003e The \u003ca href=\"\/products\/hpe-proliant-dl160-gen9-4-bay-lff-build-your-own\"\u003eHPE ProLiant DL160 Gen9 4-Bay 3.5\" Drives\u003c\/a\u003e is the 1U value-tier counterpart.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eShopping Dell at the same value-tier 2U?\u003c\/strong\u003e The \u003ca href=\"\/products\/dell-poweredge-r530-8-bay-chassis\"\u003eDell PowerEdge R530 8-Bay 3.5\" Drives\u003c\/a\u003e is the equivalent 2U dual-socket Grantley value-tier on the Dell side.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed Gen10 LFF with iLO 5?\u003c\/strong\u003e The \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eHPE ProLiant DL380 Gen10 12-Bay 3.5\" Drives\u003c\/a\u003e is the current-generation LFF mainstream.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us the workload (branch file server, backup target, archive, SMB primary, or surveillance), the chassis variant (8 LFF or 15 LFF), the CPU generation preference (v3 or v4), the memory target within the 1 TB ceiling, the storage configuration (drive types, capacity, RAID layout, controller preference), the networking requirement (embedded 1 GbE or a FlexLOM riser), the boot pattern (M.2, rear SFF, or LFF front-bay), the PSU configuration, and the quantity. We respond within 24 hours with a validated configuration, including HPE Power Advisor sizing and third-party maintenance coordination when requested. Every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in testing, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951278678215,"sku":"BP-013604","price":269.82,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl180-gen9-35-drives-741757.png?v=1765539699"},{"product_id":"hpe-proliant-dl160-gen9-4-bay-lff-build-your-own","title":"HPE ProLiant DL160 Gen9 4-Bay 3.5\" Drives [Gen9]","description":"\u003cp\u003eThe HPE ProLiant DL160 Gen9 4-Bay 3.5\" is HPE's value-tier 1U dual-socket Gen9 platform with LFF storage, refurbished and configured to order. It is the cost-optimized 1U counterpart to the DL360 Gen9 mainstream tier, built on the Intel Grantley platform with the C610 chipset and Intel Xeon E5-2600 v3 (Haswell-EP, 2014) or v4 (Broadwell-EP, 2016) processors, the same CPU family that runs across the rest of the Gen9 dual-socket line. Two sockets, 16 DDR4 DIMM slots (8 per CPU, half the DL360 Gen9's 24-slot count, which is the defining value-tier delta), a 1 TB memory ceiling, four 3.5\" LFF hot-swap bays, PCIe plug-in Smart Array storage, embedded 2-port 1 GbE with FlexibleLOM optional via a riser kit, and iLO 4 management. On the Dell side, the architectural counterpart is the Dell PowerEdge R430, the 1U 2-socket Grantley value-tier chassis with equivalent positioning.\u003c\/p\u003e\u003cp\u003eThis is the niche-but-real corner of the Gen9 lineup: 1U, LFF, value-tier, and dual-socket all at once. The combination earns its place specifically when 1U rack density matters, bulk-capacity 3.5\" HDDs are the right storage shape, and the workload's compute and memory envelope fits inside the value-tier feature set. HPE no longer sells Gen9 new and factory warranty support has ended, so third-party maintenance is the standard production support path in 2026. We are not going to soft-pedal the platform's age: for a new mission-critical buildout that needs iLO 5 security, faster memory, or PCIe Gen4, the Gen10 step is the right answer. Where the DL160 Gen9 still earns its place is in edge compute with local bulk storage, branch and ROBO file servers, remote backup targets, and budget-driven SMB primary servers where 1U cost per node is the design constraint.\u003c\/p\u003e\u003cp\u003eTo configure a build, call 1-800-778-1545 or use the quote form below. Every refurbished unit ships under our 180-day warranty with 12+ hour burn-in testing, and volume pricing starts at 5 units.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL160 Gen9 Fits in the Family\u003c\/h2\u003e\u003cp\u003eThe Gen9 dual-socket line splits along two axes: value-tier versus mainstream-tier, and 1U versus 2U. The DL160 Gen9 sits at the value-tier, 1U corner. Reading the four platforms side by side is the fastest way to confirm this is the right chassis:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eDL160 Gen9 (this platform).\u003c\/strong\u003e 1U value-tier dual-socket. 16 DIMM slots, 1 TB maximum, 2-3 PCIe slots, embedded 2-port 1 GbE, PCIe plug-in Smart Array only. Value feature set at 1U density.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDL360 Gen9.\u003c\/strong\u003e 1U mainstream dual-socket. 24 DIMM slots, 3 TB maximum, 3 PCIe slots, FlexibleLOM standard, modular \"ar\" Smart Array. Mainstream feature set at 1U density. See the \u003ca href=\"\/products\/dl360-g9-2-5-10-bay-hot-swap-psu\"\u003eHPE ProLiant DL360 Gen9 10-Bay 2.5\"\u003c\/a\u003e for the full Gen9 1U platform reference.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDL180 Gen9.\u003c\/strong\u003e 2U value-tier dual-socket. 16 DIMM slots, 1 TB maximum, 3-6 PCIe slots, embedded 4-port 1 GbE, PCIe plug-in Smart Array. The same value feature set as this platform but at 2U density with far more storage capacity.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDL380 Gen9.\u003c\/strong\u003e 2U mainstream dual-socket. 24 DIMM slots, 3 TB maximum, 6 PCIe slots, modular \"ar\" plus PCIe Smart Array. The full-feature 2U workhorse.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eChoose the DL160 Gen9 when budget is the design constraint, 1U rack density matters, the 1 TB memory ceiling is sufficient, and 3.5\" storage at modest scale fits the workload. Step to the DL360 Gen9 4-Bay 3.5\" when memory needs to exceed 1 TB or a modular \"ar\" Smart Array is required. Step to the DL180 Gen9 when 2U is acceptable and more LFF capacity is needed. Step to the DL380 Gen9 when both the mainstream feature set and 2U storage capacity matter together.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage - 4 LFF Bays\u003c\/h2\u003e\u003cp\u003eFour 3.5\" SAS\/SATA hot-swap bays sit across the front of the 1U chassis. The DL160 Gen9 is also built in an 8-bay 2.5\" SFF chassis variant for deployments that need SFF performance in the 1U value-tier footprint; specify the chassis variant at quote time. This page covers the 4-bay LFF configuration.\u003c\/p\u003e\u003cp\u003eDrive options span the Gen9 LFF portfolio: NL-SAS HDDs are the workhorse for bulk capacity (4 to 14 TB across the Gen9 lifecycle), 10K and 15K SAS HDDs trade capacity for higher per-drive IOPS, LFF SSDs are available but rarely the right economic call in this form factor, and self-encrypting drive variants cover compliance-regulated workloads.\u003c\/p\u003e\u003cp\u003eCommon DL160 Gen9 4-bay LFF storage profiles:\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eEdge compute with bulk local storage.\u003c\/strong\u003e Four 8-12 TB NL-SAS drives in RAID 10 or RAID 6 deliver roughly 16-24 TB usable for staging and buffering at the edge, at 1U value pricing.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eBranch office single-server roles.\u003c\/strong\u003e Combined AD, DNS, and DHCP plus file shares plus light virtualization on one 1U box. Four LFF in RAID 6 covers branch file storage.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eROBO file servers.\u003c\/strong\u003e A lower-cost alternative to the DL360 Gen9 for branch deployments that do not need the mainstream feature set.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eRemote backup targets.\u003c\/strong\u003e Smaller remote sites with modest retention. Four LFF in RAID 6 delivers branch-scale backup capacity at 1U.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSMB primary server.\u003c\/strong\u003e File services, application hosting, and modest virtualization on a single chassis where value pricing fits the budget.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmall-scale surveillance NVR.\u003c\/strong\u003e Four LFF bays handle small camera counts with modest retention.\u003c\/li\u003e\n\u003c\/ul\u003e\u003ch3\u003eRAID at 4 LFF\u003c\/h3\u003e\u003cp\u003eAt exactly four LFF, RAID 10 and RAID 6 carry the same 50% capacity overhead, and RAID 10 is usually preferred for better write performance and a smaller rebuild scope. We do not quote RAID 5 for large-capacity spinning-disk arrays at this scale, because the rebuild window on multi-terabyte drives exposes the array to a second-drive failure. RAID 1 with a spare suits high-availability small deployments. JBOD and HBA pass-through via the H241 serve software-defined storage stacks.\u003c\/p\u003e\u003ch3\u003eBoot Drives\u003c\/h3\u003e\u003cp\u003eDedicating two of four LFF bays to OS boot consumes half the storage budget, so M.2 SATA boot through the HPE M.2 enablement card in a PCIe slot is effectively required on this chassis. We default to M.2 boot on every 4-bay LFF DL160 Gen9 quote, which keeps all four front bays available for data.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage Controllers\u003c\/h2\u003e\u003cp\u003eThe value-tier delta shows up here: the DL160 Gen9 has no modular \"ar\" Smart Array slot, so the controller is always a PCIe plug-in card that consumes one of the limited expansion slots, the same constraint the DL180 Gen9 carries.\u003c\/p\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P440 (PCIe, 2 GB FBWC).\u003c\/strong\u003e The production controller for hardware RAID at four LFF. The 2 GB flash-backed write cache is comfortably sized for a four-drive workload.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array P840 (PCIe, 4 GB FBWC).\u003c\/strong\u003e Available when specifically required, but rarely needed at four LFF; the P440's 2 GB cache is sufficient at this drive count.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eSmart Array H241 (PCIe, HBA mode).\u003c\/strong\u003e Pass-through for software-defined storage such as ZFS or a software NAS, where the operating system owns the disks directly.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eDynamic Smart Array B140i (chipset software RAID).\u003c\/strong\u003e Acceptable for boot mirroring only; not appropriate for production data on a dual-socket platform.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eAn HPE Smart Storage Battery backs the flash-backed write cache on the P-series controllers. The FBWC battery is a known Gen9 wear item; we disclose its state on every quote and replace past-spec cache batteries as part of build prep. Because the controller occupies a PCIe slot, slot allocation is tight on this 1U chassis: a typical production build spends one slot on M.2 boot, one on the Smart Array, and one on a FlexibleLOM riser, which fills the maximum three-slot configuration. Plan the PCIe budget at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors\u003c\/h2\u003e\u003cp\u003eOne or two Intel Xeon E5-2600 v3 (Haswell-EP, 2014) or v4 (Broadwell-EP, 2016) processors on the LGA 2011-3 socket and C610 chipset, drop-in compatible within the generation. Mixing v3 and v4 in one system is not supported; a v3-to-v4 field upgrade means replacing both CPUs together.\u003c\/p\u003e\u003cp\u003eThe 1U value-tier positioning usually pairs with mid- and lower-bin CPUs. The branch, edge, and SMB workloads that drive DL160 Gen9 deployments are rarely compute-bound, so parts like the E5-2620 v4 (8 cores) and E5-2640 v4 (10 cores) are the common, economical fit. Top-bin parts such as the E5-2699 v4 (22 cores) are supported, but a 145W top-bin CPU in a 1U value chassis is usually the wrong economic call; if the workload needs that much compute, the mainstream DL360 Gen9 or a 2U platform is the better home for it. High-TDP CPUs require the performance heatsink and fan kit, and a missing heatsink kit is the most common configuration error we see on 1U Gen9 builds, so we validate it on every quote.\u003c\/p\u003e\u003cp\u003eA single-socket build is supported, but the second socket carries half the DIMM slots: a one-CPU DL160 Gen9 can populate only 8 of its 16 DIMM slots. If memory capacity matters, populate both sockets.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eMemory\u003c\/h2\u003e\u003cp\u003eSixteen DDR4 DIMM slots, eight per CPU, for a 1 TB maximum with 64 GB RDIMMs. This is the headline value-tier delta against the DL360 Gen9's 24-slot, 3 TB topology. The memory channels run at DDR4-2400 with v4 CPUs and DDR4-2133 with v3; both step down under full DIMM population per the standard Gen9 population rules, and HPE Smart Memory is required to reach rated speeds, since third-party DIMMs drop to a lower bus speed.\u003c\/p\u003e\u003cp\u003eRDIMM is the right default for this platform; LRDIMM is available for the largest capacity points but should not be mixed with RDIMM in the same system. NVDIMM-N persistent memory is a Gen9 v4 option but is rarely deployed on a value-tier 1U chassis, where the workloads that justify persistent memory are uncommon. For most DL160 Gen9 builds, populate one DIMM per channel per CPU first for best speed, then fill the second slot per channel only when capacity demands it.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking and PCIe Expansion\u003c\/h2\u003e\u003cp\u003eEmbedded networking on the DL160 Gen9 is a 2-port 1 GbE adapter, a further value-tier reduction from the 4-port embedded 1 GbE on the DL180 and DL380 Gen9. A FlexibleLOM is optional through the FlexibleLOM riser kit, which adds 10 GbE or quad-port 1 GbE options but consumes a PCIe position rather than riding a dedicated mezzanine slot the way it does on the DL360 Gen9.\u003c\/p\u003e\u003cp\u003ePCIe expansion is the tightest resource on this chassis: two PCIe Gen3 slots with a single CPU, three slots with both CPUs and the optional secondary riser. With the storage controller, an M.2 boot card, and a FlexibleLOM riser all competing for those slots, a fully configured DL160 Gen9 typically has no slots left over. Decide up front which of networking expansion, hardware RAID, and M.2 boot the build actually needs, because all of them plus an additional card will not fit. This is the single most important planning decision on the platform.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eGPU Support\u003c\/h2\u003e\u003cp\u003eThe DL160 Gen9 is not a GPU platform. The 1U thermal envelope and the value-tier PCIe budget leave no room for a double-wide accelerator, and the few low-profile slots are normally claimed by storage and networking. A single-width low-profile card is the practical ceiling, and even that is uncommon on this chassis. If the workload needs GPU compute, step to a 2U platform with the slots, power, and cooling for it, such as the \u003ca href=\"\/products\/dl380-g9-2-5-16-bay-chassis\"\u003eHPE ProLiant DL380 Gen9 16-Bay 2.5\"\u003c\/a\u003e, which supports up to two double-wide GPUs. Buying a 1U value chassis and expecting to add an accelerator later is the trap this section exists to prevent.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eManagement - iLO 4 Generation\u003c\/h2\u003e\u003cp\u003eThe DL160 Gen9 ships with HPE Integrated Lights-Out 4 (iLO 4), the management generation shared across the entire Gen9 fleet, which is a real value point when you are standardizing operations on one firmware generation. iLO 4 Standard is included with the hardware and covers health monitoring, power control, and basic remote management. iLO Advanced licensing, typically a separate cost and more strongly separated on the value tier, unlocks the full graphical remote console, virtual media, and the richer scripting interface. UEFI Secure Boot is the firmware-integrity baseline. iLO 4 predates the Silicon Root of Trust hardware-anchored firmware verification that arrived with iLO 5 on Gen10; if hardware-rooted firmware attestation is a requirement, that is a reason to move to the Gen10 generation rather than Gen9.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePower and Cooling\u003c\/h2\u003e\u003cp\u003eHPE Flex Slot power supplies, redundant in a 1+1 configuration. The value-tier 1U chassis skews toward the lower wattage tiers: dual 500W Platinum is the standard configuration for entry branch and edge builds, and dual 800W covers builds with mid-tier CPUs and full memory. The high-wattage 1400W tier is not the typical fit here, because the DL160 Gen9 is not designed for the high-TDP CPU and heavy-expansion configurations that would draw it.\u003c\/p\u003e\u003cp\u003eThe 1U thermal envelope follows the same rules as the DL360 Gen9: top-bin CPUs require the performance heatsink and fan kit, and inlet temperature matters. For the lower- and mid-bin CPUs that suit most DL160 Gen9 deployments, the thermal envelope is comfortable in standard data-center and branch-office cooling. We size PSUs against the actual CPU, DIMM, and drive configuration rather than defaulting to the largest available, so the quote reflects real peak draw.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePhysical Specs \u0026amp; Platform Notes\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eForm factor.\u003c\/strong\u003e 1U rack chassis at standard rack depth, with four 3.5\" LFF front bays in this configuration. Fits any standard 19-inch rack on the included rail kit.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePCIe expansion.\u003c\/strong\u003e Two PCIe Gen3 slots with one CPU, three with both CPUs and the secondary riser; all low-profile in the 1U chassis. No full-height or double-wide card support.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eParts availability.\u003c\/strong\u003e Strong. Gen9 is a mature, high-volume platform, so E5-2600 v3\/v4 CPUs, DDR4 DIMMs, Smart Array controllers, PSUs, and rails are widely stocked on the secondary market. HPE factory support has ended, so third-party maintenance is the standard production support path.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eAccessories we recommend.\u003c\/strong\u003e The HPE 1U ball-bearing rail kit (the gen-spanning DL160\/DL360 1U rail, HPE part numbers 679368-001 and 728437-001) for tool-less rack mounting, the HPE M.2 enablement card for boot so the front bays stay free for data, and the FlexibleLOM riser kit when 10 GbE networking is required.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003ePlatform notes.\u003c\/strong\u003e No modular \"ar\" Smart Array slot, so the controller always consumes a PCIe slot; embedded LOM is 2-port 1 GbE rather than the 4-port found on the larger Gen9 chassis; the 4-bay LFF capacity ceiling is roughly 56 TB raw with 14 TB drives; and CPU hot-plug is not supported on this platform.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003e\u003cstrong\u003eWhere it excels:\u003c\/strong\u003e The DL160 Gen9 4-Bay 3.5\" is the right answer when three things are true at once: you need 1U rack density, you want bulk-capacity 3.5\" storage, and the workload fits the value-tier feature set. That describes edge compute nodes with local staging storage, branch and ROBO file servers, small remote backup targets, and budget-driven SMB primary servers. In those roles it does exactly what is asked at a lower per-node cost than the mainstream DL360 Gen9.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhere to look instead:\u003c\/strong\u003e The moment a workload needs more than 1 TB of memory, a modular \"ar\" Smart Array, or more PCIe expansion than the tight 1U slot budget allows, the value tier stops being the right tool. Step to the DL360 Gen9 4-Bay 3.5\" for the mainstream 1U feature set, the DL180 Gen9 LFF for more 3.5\" capacity in 2U, or the DL360 Gen9 8-Bay 2.5\" when SFF performance matters more than bulk LFF capacity.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eBottom line:\u003c\/strong\u003e This is a deliberately narrow chassis for a deliberately narrow buyer: the operator who wants a dual-socket Gen9 server in 1U with 3.5\" bays and is buying on cost, not on headroom. If that is the deployment, the DL160 Gen9 is well-matched and economical. If the build is likely to grow into more memory, more storage, or expansion cards, buy the headroom now in the DL360 Gen9 or a 2U platform rather than hitting the value-tier ceiling six months in.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhere the DL160 Gen9 Fits in 2026\u003c\/h2\u003e\u003cp\u003eThe Gen9 platform launched on Intel's Grantley architecture with the Xeon E5-2600 v3 (Haswell-EP) in 2014 and was refreshed with the v4 (Broadwell-EP) in 2016. As of 2026 it is two generations back: Gen10 (Purley, Skylake-SP and Cascade Lake-SP) arrived in 2017, and Gen11 (Sapphire Rapids) is the current shipping generation. HPE active warranty and standard support on Gen9 hardware have ended, so third-party maintenance is the established production support path for these servers today.\u003c\/p\u003e\u003cp\u003eWhat sits above Gen9 in HPE's roadmap brings real improvements. Gen10 adds the iLO 5 Silicon Root of Trust, faster DDR4-2933 memory on the right CPUs, and a broader Smart Array lineup, while Gen11 moves to DDR5, PCIe Gen5, and current Xeon Scalable cores. For a new mission-critical deployment that needs hardware-rooted firmware security, the newest memory and I\/O bandwidth, or a long forward support runway, the Gen10 or Gen11 step is the right answer, and we will quote it.\u003c\/p\u003e\u003cp\u003eThe DL160 Gen9 earns its place in 2026 specifically when one of these patterns applies: adding capacity to an existing Gen9 fleet where operational standardization on one platform and one management generation has real value; lab, dev, and staging environments that mirror a Gen9 production estate; budget-driven branch, edge, and ROBO roles where 1U cost per node is the deciding factor; small remote backup and file-server targets that do not justify current-generation pricing; and SMB primary servers whose workload sits comfortably inside the E5-2600 v3\/v4 envelope. In those contexts the lower acquisition cost is the point, and the platform's age is a managed tradeoff rather than a liability.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHonest Limitations\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eGen9-wide platform age.\u003c\/strong\u003e HPE active warranty has ended, iLO 4 has no Silicon Root of Trust, memory is capped at DDR4-2400, expansion is PCIe Gen3 only, and the FBWC cache battery is a wear item that needs checking on a refurbished unit.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003e16 DIMM slots, 1 TB ceiling.\u003c\/strong\u003e Half the DL360 Gen9's DIMM count. Workloads that need more memory belong on the mainstream tier.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNo modular \"ar\" Smart Array slot.\u003c\/strong\u003e The storage controller always consumes a PCIe slot, the same value-tier constraint the DL180 Gen9 carries.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eTight 1U PCIe budget.\u003c\/strong\u003e Two or three slots maximum. With M.2 boot, a Smart Array, and a FlexibleLOM riser, the slots are usually all spoken for.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eEmbedded LOM is 2-port 1 GbE.\u003c\/strong\u003e Fewer ports than the 4-port embedded LOM on the larger Gen9 chassis; reaching four ports or 10 GbE means spending a PCIe slot on a FlexibleLOM riser.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eFour LFF bays only in this configuration.\u003c\/strong\u003e Roughly 56 TB raw with 14 TB drives is the ceiling. More 3.5\" capacity means stepping to a 2U platform such as the DL180 Gen9 or DL380 Gen9.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eBoot consumes front-bay capacity unless you use M.2.\u003c\/strong\u003e Dedicating two of four LFF bays to boot is half the storage budget, which is why M.2 boot is effectively mandatory here.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNot a GPU platform.\u003c\/strong\u003e No double-wide support in 1U; the value tier rarely deploys accelerators anyway.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eiLO Advanced is usually a separate cost.\u003c\/strong\u003e Full remote console and virtual media require the Advanced license.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e\n\u003ctr\u003e\n\u003cth\u003eThis server is right for\u003c\/th\u003e\n\u003cth\u003eConsider alternatives for\u003c\/th\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eEdge compute with bulk local storage at 1U\u003c\/td\u003e\n\u003ctd\u003eMemory requirements above 1 TB (use the DL360 Gen9)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBranch office single-server deployments\u003c\/td\u003e\n\u003ctd\u003eMore than 4 LFF bays needed (use the DL180 Gen9)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eROBO file servers at value pricing\u003c\/td\u003e\n\u003ctd\u003eWorkloads needing a modular \"ar\" Smart Array\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eRemote backup targets at 1U value-tier\u003c\/td\u003e\n\u003ctd\u003eNew mission-critical builds needing iLO 5 security\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eSMB primary servers with bulk capacity\u003c\/td\u003e\n\u003ctd\u003eExtensive PCIe expansion or GPU compute\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eLab, dev, and test bulk storage at 1U\u003c\/td\u003e\n\u003ctd\u003eAn active HPE factory support requirement\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eWhere to Look Instead\u003c\/h2\u003e\u003cul\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed the mainstream 1U LFF feature set at Gen9?\u003c\/strong\u003e The \u003ca href=\"\/products\/dl360-g9-3-5-4-bay-chassis\"\u003eHPE ProLiant DL360 Gen9 4-Bay 3.5\"\u003c\/a\u003e is the same 1U LFF form factor with 24 DIMM slots, modular Smart Array, and FlexibleLOM standard.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed more 3.5\" capacity at Gen9?\u003c\/strong\u003e The \u003ca href=\"\/products\/hpe-proliant-dl180-gen9-lff-build-your-own\"\u003eHPE ProLiant DL180 Gen9 LFF\u003c\/a\u003e brings the same value feature set to 2U with 8 or 15 LFF bays.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eNeed SFF performance at 1U Gen9?\u003c\/strong\u003e The \u003ca href=\"\/products\/hpe-proliant-dl360-g9-8-bay-2-5-chassis\"\u003eHPE ProLiant DL360 Gen9 8-Bay 2.5\"\u003c\/a\u003e is the 1U mainstream SFF chassis for compute-driven workloads.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWant the Dell equivalent?\u003c\/strong\u003e The \u003ca href=\"\/products\/dell-poweredge-r430-lff-chassis\"\u003eDell PowerEdge R430 4-Bay 3.5\"\u003c\/a\u003e is the 1U 2-socket Grantley value-tier counterpart with equivalent positioning.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWant the current-generation value 1U?\u003c\/strong\u003e The \u003ca href=\"\/products\/hp-proliant-dl160-g10-4-bay-3-5-build-your-own-server\"\u003eHPE ProLiant DL160 Gen10 4-Bay 3.5\"\u003c\/a\u003e is the direct successor with iLO 5 and the Purley platform.\u003c\/li\u003e\n\u003cli\u003e\n\u003cstrong\u003eWant current-generation mainstream 1U LFF?\u003c\/strong\u003e The \u003ca href=\"\/products\/hpe-proliant-dl360-g10-4-bay-3-5-build-your-own-server\"\u003eHPE ProLiant DL360 Gen10 4-Bay 3.5\"\u003c\/a\u003e is the Gen10 mainstream 1U LFF chassis.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eThe DL160 Gen9's own predecessor, the Gen8-era DL160, is end-of-support and not a platform we stock or recommend in 2026.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us the workload (edge, branch, ROBO, remote backup, SMB, or surveillance), the chassis variant (4-bay LFF or 8-bay SFF), the CPU generation preference (v3 or v4), the memory target within the 1 TB ceiling, the storage layout (drive types, RAID level, controller, and M.2 boot), the networking requirement (embedded 2-port 1 GbE or a FlexibleLOM riser), the PSU configuration, and the quantity. We respond within 24 hours with a validated build, including HPE Power Advisor sizing and third-party maintenance coordination when you need it. Every refurbished unit ships with the Wholesale Servers 180-day warranty and 12+ hour burn-in testing, and volume pricing starts at 5 units. Call 1-800-778-1545 or use the quote form below.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951278514375,"sku":"BP-013627","price":220.42,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/1800x1200_81.png?v=1765539699"},{"product_id":"server-design-lab-hpe-proliant-dl360-g10-10-bay-2-5-drives","title":"HPE ProLiant DL360 Gen10+ 10-Bay 2.5\" Drives","description":"\u003cp\u003eThe DL360 Gen10+ 10-Bay 2.5\" is the maximum SFF density 1U configuration on the current-generation HPE platform — ten hot-swap bays with PCIe Gen4 NVMe support, Ice Lake Xeon, 32 DIMM slots, and vSAN ESA compatibility. Two additional bays over the DL360 Gen10+ 8-Bay for workloads where drive count per 1U node is a meaningful design variable.\u003c\/p\u003e\u003cp\u003eFor full Gen10+ platform details see the \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-8-bay-build-your-own\"\u003eDL380 Gen10+ 8-Bay page\u003c\/a\u003e. For 8-Bay vs. 10-Bay guidance see the \u003ca href=\"\/products\/hpe-proliant-dl360-gen10-plus-8-bay-build-your-own\"\u003eDL360 Gen10+ 8-Bay page\u003c\/a\u003e.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWhen the 10-Bay Earns Its Place in Gen10+\u003c\/h2\u003e\u003cp\u003eSame reasoning as the Gen10 10-Bay — the extra two bays matter when Ceph OSD count per 1U node (10 vs. 8 makes a meaningful cluster size difference at scale), vSAN drive group designs that need more drives per node, or any storage-first 1U deployment where 10 bays provides more flexibility than 8 without stepping to 2U.\u003c\/p\u003e\u003cp\u003eAt Gen10+ pricing levels, the cost delta between 8-Bay and 10-Bay is relatively small against the total configuration cost. When in doubt about future storage expansion at 1U, the 10-Bay provides flexibility the 8-Bay can't retrofit.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage — 10 SFF Bays with Gen4 NVMe\u003c\/h2\u003e\u003cp\u003eTen 2.5\" hot-swap bays with PCIe Gen4 NVMe backplane. Same drive flexibility as 8-Bay Gen10+: Gen4 NVMe SSDs for vSAN ESA, SAS\/SATA for OSA or hardware RAID, or mixed configurations. Smart Array E208i-a (HBA mode) for vSAN ESA. Smart Array P408i-o (2 GB FBWC) for hardware RAID.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eThe right choice when 10 Gen4 NVMe drives in 1U is a specific design target — dense vSAN ESA nodes, 10 Ceph OSD nodes per 1U chassis, or distributed storage where maximizing drives-per-rack-unit drives cluster economics. For most Gen10+ 1U deployments, the 8-Bay covers the storage design. We'll advise at quote time.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eNavigation:\u003c\/strong\u003e Gen10 equivalent → \u003ca href=\"\/products\/hpe-proliant-dl360-gen10-10-bay-2-5-chassis\"\u003eDL360 Gen10 10-Bay\u003c\/a\u003e. 8-Bay alternative → \u003ca href=\"\/products\/hpe-proliant-dl360-gen10-plus-8-bay-build-your-own\"\u003eDL360 Gen10+ 8-Bay\u003c\/a\u003e. 2U option → \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-16-bay-build-your-own\"\u003eDL380 Gen10+ 16-Bay\u003c\/a\u003e.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e\n\u003cth\u003eThis server excels at\u003c\/th\u003e\n\u003cth\u003eConsider alternatives for\u003c\/th\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ vSAN ESA at 10 NVMe drives per 1U node\u003c\/td\u003e\n\u003ctd\u003e❌ 8 drives sufficient (use Gen10+ 8-Bay)\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Ceph 10 OSD per 1U density\u003c\/td\u003e\n\u003ctd\u003e❌ 2U preferred for more storage flexibility\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Maximum Gen4 NVMe drives per 1U chassis\u003c\/td\u003e\n\u003ctd\u003e❌ Gen10 ESA not required (Gen10 10-Bay sufficient)\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us your storage architecture, drive count preference, and quantity. We'll return Gen10 and Gen10+ pricing for comparison. Volume pricing at 5 units and above.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951283003591,"sku":"BP-012706","price":5004.5,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/1800x1200_80.png?v=1765539707"},{"product_id":"hpe-proliant-dl360-gen10-plus-8-bay-build-your-own","title":"HPE ProLiant DL360 Gen10+ 8-Bay 2.5\" Drives","description":"\u003cp\u003eThe HPE ProLiant DL360 Gen10+ is the current-generation 1U platform — the Ice Lake Xeon equivalent of the DL360 Gen10, with PCIe Gen4, 32 DIMM slots, vSAN ESA support, and extended lifecycle. For HPE shops standardizing on Gen10+ infrastructure or requiring vSAN ESA in a 1U chassis, this is the platform.\u003c\/p\u003e\u003cp\u003eFor full Gen10+ platform details (what changes from Gen10 — Ice Lake, PCIe Gen4, 32 DIMM slots, vSAN ESA) see the \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-8-bay-build-your-own\"\u003eDL380 Gen10+ 8-Bay page\u003c\/a\u003e. For 1U vs. 2U decision guidance see the \u003ca href=\"\/products\/dl360-g10-chassis\"\u003eDL360 Gen10 8-Bay page\u003c\/a\u003e. Everything there applies to the Gen10+ equivalent with the Gen10+ compute and storage platform advantages.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage — 8 SFF Bays with Gen4 NVMe\u003c\/h2\u003e\u003cp\u003eEight 2.5\" hot-swap bays with PCIe Gen4 NVMe backplane support — native Gen4 NVMe in a 1U chassis. For vSAN ESA 1U nodes, Kubernetes persistent volume backends with Gen4 NVMe latency, and edge deployments where 1U form factor and current-generation NVMe are both requirements, the DL360 Gen10+ 8-Bay is the platform.\u003c\/p\u003e\u003cp\u003eSmart Array E208i-a (HBA mode) for vSAN ESA. Smart Array P408i-o (2 GB FBWC) for hardware RAID SAS\/SATA configurations.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eGen10+ vs. Gen10 DL360 — When the Premium Is Justified\u003c\/h2\u003e\u003cp\u003eSame calculus as DL380 Gen10+ vs. Gen10: lifecycle extending past 2028, vSAN ESA target, Gen4 NVMe requirement, or Ice Lake core count advantage over Cascade Lake. For compute-primary deployments without those specific requirements, the DL360 Gen10 delivers equivalent performance at lower cost. We'll quote both.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eThe DL360 Gen10+ 8-Bay is the right platform for vSAN ESA 1U nodes, Gen4 NVMe in a 1U chassis, and HPE shops building infrastructure with 5+ year lifespans. For everything else in 1U, the DL360 Gen10 is cost-effective and proven.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eNavigation:\u003c\/strong\u003e Gen10 equivalent → \u003ca href=\"\/products\/dl360-g10-chassis\"\u003eDL360 Gen10 8-Bay\u003c\/a\u003e. Gen10+ 10-Bay → \u003ca href=\"\/products\/hpe-proliant-dl360-gen10-plus-10-bay-2-5-chassis\"\u003eDL360 Gen10+ 10-Bay\u003c\/a\u003e. 2U Gen10+ → \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-8-bay-build-your-own\"\u003eDL380 Gen10+ 8-Bay\u003c\/a\u003e.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e\n\u003cth\u003eGen10+ 1U is justified for\u003c\/th\u003e\n\u003cth\u003eGen10 1U is sufficient for\u003c\/th\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ vSAN ESA 1U nodes\u003c\/td\u003e\n\u003ctd\u003e✓ vSAN OSA on vSphere 7.x\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Gen4 NVMe in 1U form factor\u003c\/td\u003e\n\u003ctd\u003e✓ SAS\/SATA storage\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Lifecycle 5+ years + Gen10+ standardization\u003c\/td\u003e\n\u003ctd\u003e✓ 2–4 year lifecycle\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us your workload, vSAN architecture, NVMe requirements, and quantity. We'll return Gen10 and Gen10+ pricing for comparison. Volume pricing at 5 units and above.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951282970823,"sku":"BP-012705","price":4644.46,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/hpe-proliant-dl360-gen-10-server-2x-gold-6138-20ghz-40-cores-128gb-ram-8x-900gb-sas-hdd-720707.png?v=1765539707"},{"product_id":"hpe-proliant-dl380-gen10-plus-16-bay-build-your-own","title":"HPE ProLiant DL380 Gen10+ 16-Bay 2.5\" Drives","description":"\u003cp\u003eThe DL380 Gen10+ 16-Bay 2.5\" brings the Gen10+ platform advantages — Ice Lake Xeon, PCIe Gen4, 32 DIMM slots, vSAN ESA support — to a 16-bay SFF density configuration. This is the Gen10+ platform for vSAN all-flash ESA clusters, high-density NVMe storage tiers, and converged workloads requiring more than 8 SFF bays with the full Gen10+ feature set.\u003c\/p\u003e\u003cp\u003eFor full Gen10+ platform details (Ice Lake processors, memory architecture, PCIe Gen4 advantages, vSAN ESA requirements, Smart Array controllers, iLO 5) see the \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-8-bay-build-your-own\"\u003eDL380 Gen10+ 8-Bay page\u003c\/a\u003e. This page covers the 16-bay storage story and when it makes sense over the 8-bay or 24-bay Gen10+ configurations.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage — 16 SFF Bays with Gen4 NVMe\u003c\/h2\u003e\u003cp\u003eSixteen 2.5\" hot-swap bays. PCIe Gen4 NVMe backplane available on Gen10+ — NVMe drives connect at full Gen4 bandwidth. For vSAN ESA all-flash clusters, 16 NVMe drives per node enables multiple ESA storage pools per node with meaningful capacity and IOPS per chassis.\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003evSAN ESA all-flash:\u003c\/strong\u003e 16 NVMe drives across 16 bays — all drives participate in the unified ESA storage pool. No cache\/capacity split — ESA manages its own tiering internally. 25 GbE minimum for ESA; 100 GbE recommended for high-density nodes.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003evSAN OSA hybrid or all-flash:\u003c\/strong\u003e SSD cache tier + SAS\/SATA HDD capacity tier. 16 bays supports larger disk groups with better cache\/capacity ratios than 8-bay configurations.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eHigh-density SAS SSD storage:\u003c\/strong\u003e 16x SAS SSDs at RAID 10 for database and analytics tiers requiring high-endurance SSD performance without NVMe latency requirements.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003e\u003cstrong\u003eGen10+ vs. Gen10 16-Bay for vSAN:\u003c\/strong\u003e The Gen10+ 16-Bay supports vSAN ESA (ESA requires NVMe + Gen10+ minimum). Gen10 16-Bay is OSA-only. If your vSAN target is ESA, Gen10+ is required. If OSA on vSphere 7.x is your target, Gen10 delivers comparable performance at lower cost.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10+ 16-Bay is the premium vSAN ESA and high-density NVMe storage configuration — justified when vSAN ESA is the target, PCIe Gen4 NVMe performance is required, or the deployment lifecycle extends to 2030+. For OSA deployments or shorter lifecycle projects, the Gen10 16-Bay provides comparable storage density at meaningfully lower acquisition cost.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eUpgrade context:\u003c\/strong\u003e Replaces → \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay\u003c\/a\u003e when ESA\/Gen4 justified. Step up from → \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-8-bay-build-your-own\"\u003eDL380 Gen10+ 8-Bay\u003c\/a\u003e when drive count needs to double. Step down from → \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-24-bay-build-your-own\"\u003eDL380 Gen10+ 24-Bay\u003c\/a\u003e when 16 bays covers the storage design.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e\n\u003cth\u003eThis server excels at\u003c\/th\u003e\n\u003cth\u003eConsider alternatives for\u003c\/th\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ vSAN ESA all-flash (16 NVMe per node)\u003c\/td\u003e\n\u003ctd\u003e❌ vSAN OSA on vSphere 7.x (Gen10 sufficient)\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ High-density Gen4 NVMe storage tiers\u003c\/td\u003e\n\u003ctd\u003e❌ 8 bays sufficient (Gen10+ 8-Bay lower cost)\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Converged workloads requiring 16 SFF bays + Ice Lake\u003c\/td\u003e\n\u003ctd\u003e❌ LFF drives needed\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Infrastructure lifecycle 5+ years + vSAN ESA\u003c\/td\u003e\n\u003ctd\u003e❌ Budget-primary shorter lifecycle\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us your vSAN architecture (ESA or OSA), NVMe vs. SAS\/SATA preference, Ice Lake CPU target, memory requirement, and quantity. We'll return formal pricing alongside Gen10 and Gen10+ 8-Bay comparisons. Volume pricing at 5 units and above.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951283134663,"sku":"BP-012711","price":6462.65,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-gen10-16-bay-25-drives-874519.png?v=1765539623"},{"product_id":"hpe-proliant-dl380-gen10-plus-8-bay-build-your-own","title":"HPE ProLiant DL380 Gen10+ 8-Bay 2.5\" Drives","description":"\u003cp\u003eThe HPE ProLiant DL380 Gen10+ is the current-generation HPE 2U platform — a meaningful step forward from the Gen10 in several areas that matter for infrastructure built to run into the late 2020s. If the DL380 Gen10 is the mature workhorse, the Gen10+ is the investment in platform longevity. For procurement teams evaluating whether to buy Gen10 or Gen10+, this page explains exactly what changes and when the premium is justified.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eGen10+ vs. Gen10 — what actually improves:\u003c\/strong\u003e\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eIntel Xeon Scalable 3rd Gen (Ice Lake, 2021):\u003c\/strong\u003e Up to 40 cores per CPU (vs. 28 on Gen10 Cascade Lake), hardware-level security mitigations, improved IPC, better memory speed support. Total dual-socket: up to 80 cores \/ 160 threads.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePCIe Gen4:\u003c\/strong\u003e Double the bandwidth of PCIe Gen3 on Gen10. Meaningful for NVMe storage (Gen4 NVMe saturates 7+ GB\/s vs. ~3.5 GB\/s for Gen3), GPU workloads, and high-bandwidth interconnects.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e32 DDR4 DIMM slots:\u003c\/strong\u003e Up from 24 on Gen10. More slots enables higher total memory capacity with standard RDIMM sizes rather than requiring LRDIMMs to reach high capacities.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNative NVMe backplane support:\u003c\/strong\u003e Gen10+ introduced native front-bay NVMe on select configurations — no PCIe card workaround required for NVMe-primary storage architectures.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003evSAN ESA support:\u003c\/strong\u003e vSAN 8.x Express Storage Architecture (ESA) is supported on Gen10+ with NVMe — not available on Gen10. For VMware shops planning ESA migration, Gen10+ is the minimum hardware requirement.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eExtended lifecycle:\u003c\/strong\u003e Gen10+ will remain in HPE's support window longer than Gen10. For infrastructure with 5–7 year planned lifespans, the Gen10+ provides more runway before end-of-support events.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003e\u003cstrong\u003eWhen Gen10 is still the right call:\u003c\/strong\u003e If you're building infrastructure with a 2–4 year planned lifecycle, PCIe Gen4 isn't a requirement for your workload, vSAN OSA on vSphere 7.x is your VMware target, and the Gen10+ price premium exceeds your budget tolerance — the Gen10 is a completely legitimate choice. We'll quote both side-by-side so you can make the decision with full information.\u003c\/p\u003e\u003cp\u003eFor HPE platform vocabulary (iLO 5, Smart Array, FlexLOM, FBWC) see the \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-8-bay-build-your-own\"\u003eDL380 Gen10 8-Bay page\u003c\/a\u003e — all of it carries forward to Gen10+. This page covers what changes in Gen10+.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors — Ice Lake Xeon Scalable (3rd Gen)\u003c\/h2\u003e\u003cp\u003eDual Intel Xeon Scalable 3rd Generation (Ice Lake, 2021). Up to 40 cores per CPU — the Gold 6338 (32 cores, 2.0 GHz, 205W) and Platinum 8380 (40 cores, 2.3 GHz, 270W) represent the high-end configurations. For balanced deployments, the Gold 6336Y (24 cores, 2.4 GHz, 185W) or Gold 6326 (16 cores, 2.9 GHz, 185W) are common mid-range choices providing strong per-core frequency alongside meaningful core counts.\u003c\/p\u003e\u003cp\u003eIce Lake brings meaningful IPC improvement over Cascade Lake — approximately 15–20% in typical enterprise workloads. For workloads that are CPU-bound, this translates to more VMs per host, faster database query execution, and better application response times with the same core count as Gen10.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eHigh-TDP awareness on Ice Lake:\u003c\/strong\u003e Many Ice Lake Gold\/Platinum SKUs carry 185–270W TDP — significantly higher than equivalent Cascade Lake SKUs. Heatsink and airflow configuration is critical. We validate thermal configurations for all Gen10+ builds before quoting.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eMemory — 32 DIMM Slots\u003c\/h2\u003e\u003cp\u003e32 DDR4 DIMM slots — 16 per CPU, eight memory channels per socket (vs. six on Gen10). The additional channels and slots provide meaningful advantages:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003eAt 32 DIMMs, maximum DDR4 RDIMM capacity reaches ~4 TB without requiring LRDIMMs — 128 GB RDIMMs × 32 = 4 TB. Gen10 required LRDIMMs to reach comparable densities.\u003c\/li\u003e  \u003cli\u003eEight memory channels per socket (vs. six on Gen10) means more aggregate bandwidth at full population — meaningful for memory-bandwidth-intensive workloads.\u003c\/li\u003e  \u003cli\u003eDDR4 speed at 1 DPC on Ice Lake: up to 3200 MT\/s on supported SKUs. At 2 DPC: typically 2933–3200 MT\/s depending on specific CPU — higher than Gen10's 2666 MT\/s ceiling at 2 DPC.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eMaximum memory: up to 8 TB with 256 GB LRDIMMs across all 32 slots — the highest memory capacity available in a Gen10+ 2U DL380 configuration.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage — 8 SFF Bays with PCIe Gen4 NVMe\u003c\/h2\u003e\u003cp\u003eEight 2.5\" hot-swap bays. The Gen10+ introduces native NVMe backplane support on configured chassis — NVMe drives connect directly to the PCIe Gen4 fabric for full Gen4 bandwidth. This is a meaningful change from Gen10 where NVMe required PCIe add-in cards. Confirm NVMe backplane configuration at quote time — not all DL380 Gen10+ 8-Bay configurations ship with the NVMe-capable backplane by default.\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003ePCIe Gen4 NVMe (where backplane configured):\u003c\/strong\u003e Gen4 NVMe SSDs deliver up to 7 GB\/s sequential read — approximately 2× the bandwidth ceiling of Gen3 NVMe on Gen10. For NVMe-primary storage architectures, the Gen10+ is the platform.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSAS\/SATA drives:\u003c\/strong\u003e Standard SAS\/SATA drives continue to work on the Gen10+ backplane — the platform is backwards-compatible with existing drive inventory.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eM.2 boot via enablement kit — recommended to keep all 8 bays for data.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eSmart Array Controllers\u003c\/h2\u003e\u003cp\u003eSame controller family as Gen10 but updated for Gen10+ integration:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P408i-o (2 GB FBWC):\u003c\/strong\u003e Standard production RAID controller for Gen10+ configurations. Updated model designation for Gen10+ compatibility.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a (4 GB FBWC):\u003c\/strong\u003e Top-tier write-cache RAID option for Gen10+ production storage.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-a (HBA mode):\u003c\/strong\u003e Required for vSAN ESA configurations — direct drive pass-through to vSAN kernel management.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003evSAN ESA — The Gen10+ Advantage\u003c\/h2\u003e\u003cp\u003eVMware vSAN 8.x Express Storage Architecture (ESA) is the current-generation vSAN storage model. ESA requires: 14th gen or newer hardware (Gen10+ qualifies), NVMe storage (not SAS\/SATA), and vSphere 8.x. ESA eliminates the traditional cache\/capacity disk group model — all NVMe drives participate in a unified storage pool with significantly better performance and simpler management than OSA.\u003c\/p\u003e\u003cp\u003eIf your VMware roadmap targets vSAN ESA, Gen10+ with NVMe is the minimum hardware requirement. Gen10 is OSA-only. We help customers evaluate ESA readiness as part of every vSAN Gen10+ quote.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePower Supplies\u003c\/h2\u003e\u003cp\u003eIce Lake TDPs are higher than equivalent Cascade Lake — Gen10+ requires larger PSU configurations for fully-loaded builds. Standard recommendations:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e2x 800W Flex Slot Platinum:\u003c\/strong\u003e For moderate TDP CPU configurations (≤185W per socket) with standard memory and SFF SSD drives.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e2x 1600W Flex Slot Titanium:\u003c\/strong\u003e Required for high-TDP Ice Lake configurations (185W+ per socket), GPU installations, or fully-loaded NVMe configurations. Our standard recommendation for Gen10+ production deployments.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eManagement — iLO 5\u003c\/h2\u003e\u003cp\u003eSame iLO 5 as Gen10 — iLO 5 Advanced license required for production (remote KVM, Active Health System, virtual media). Gen10+ adds iLO 5 server security improvements including enhanced Secure Boot and additional firmware integrity features. TPM 2.0 included by default on Gen10+ configurations.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10+ 8-Bay is the right platform when: your infrastructure lifecycle extends beyond 2028, vSAN ESA is in your VMware roadmap, PCIe Gen4 NVMe bandwidth is a requirement, or Ice Lake's core count (up to 40 per socket) justifies the premium over Gen10 Cascade Lake (up to 28 per socket). For HPE shops building production infrastructure today that needs to be relevant through 2030, this is the platform we recommend. For shorter lifecycles or workloads that don't leverage Gen4\/ESA\/Ice Lake advantages, the Gen10 delivers better ROI.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhere to look instead:\u003c\/strong\u003e\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eGen10 ROI more important than Gen10+ features?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-8-bay-build-your-own\"\u003eDL380 Gen10 8-Bay\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed more SFF bays?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-16-bay-build-your-own\"\u003eDL380 Gen10+ 16-Bay\u003c\/a\u003e or \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-24-bay-build-your-own\"\u003eDL380 Gen10+ 24-Bay\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed LFF drives?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-12-bay-lff-build-your-own\"\u003eDL380 Gen10+ 12-Bay 3.5\"\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed 1U Gen10+?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl360-gen10-plus-8-bay-build-your-own\"\u003eDL360 Gen10+ 8-Bay\u003c\/a\u003e\n\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e\n\u003cth\u003eGen10+ is the right call when\u003c\/th\u003e\n\u003cth\u003eGen10 is sufficient when\u003c\/th\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ vSAN 8.x ESA deployment target\u003c\/td\u003e\n\u003ctd\u003e✓ vSAN OSA on vSphere 7.x\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ PCIe Gen4 NVMe storage architecture\u003c\/td\u003e\n\u003ctd\u003e✓ SAS\/SATA or Gen3 NVMe storage\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Infrastructure lifecycle 5+ years\u003c\/td\u003e\n\u003ctd\u003e✓ 2–4 year planned lifecycle\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Ice Lake core density (up to 80 cores dual-socket)\u003c\/td\u003e\n\u003ctd\u003e✓ Cascade Lake sufficient for workload\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ 32 DIMM slot capacity advantage\u003c\/td\u003e\n\u003ctd\u003e✓ 24 DIMM slots sufficient\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us your workload, vSAN architecture target (OSA or ESA), memory requirements, NVMe vs. SAS\/SATA preference, and quantity. We'll return formal pricing alongside a Gen10 comparison so you can evaluate the generational premium against your lifecycle and workload requirements. Volume pricing at 5 units and above.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951282938055,"sku":"BP-012710","price":5562.56,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-gen10-8-bay-25-drives-452269.png?v=1765539706"},{"product_id":"hpe-proliant-dl380-gen10-plus-12-bay-lff-build-your-own","title":"HPE ProLiant DL380 Gen10+ 12-Bay 3.5\" Drives","description":"\u003cp\u003eThe DL380 Gen10+ 12-Bay 3.5\" brings Ice Lake Xeon, PCIe Gen4, and 32 DIMM slots to the LFF capacity configuration — twelve 3.5\" hot-swap bays alongside the current-generation HPE 2U platform. For HPE shops building long-lifecycle NAS, large-scale backup infrastructure, or Ceph capacity-tier nodes where the deployment must remain relevant into the late 2020s, the Gen10+ LFF configuration delivers platform longevity that the Gen10 does not.\u003c\/p\u003e\u003cp\u003eFor full Gen10+ platform details see the \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-8-bay-build-your-own\"\u003eDL380 Gen10+ 8-Bay page\u003c\/a\u003e. For full LFF storage guidance (NL-SAS configuration, RAID 6 requirements, Ceph OSD memory sizing, NAS caching) see the \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eDL380 Gen10 12-Bay 3.5\" page\u003c\/a\u003e — the storage story is identical; only the compute platform changes.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eGen10+ vs. Gen10 for LFF Bulk Storage\u003c\/h2\u003e\u003cp\u003eFor NAS, backup, and archive workloads on spinning disk, the practical performance difference between Gen10 and Gen10+ is modest — the I\/O path on NL-SAS HDDs is the bottleneck, not CPU generation or PCIe bandwidth. The Gen10+ LFF configuration earns its premium over Gen10 when:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003eThe deployment lifecycle extends to 2030+ and Gen10 platform aging is a concern\u003c\/li\u003e  \u003cli\u003eThe node also runs meaningful compute workloads alongside LFF storage (converged NAS\/application server) where Ice Lake's IPC improvement matters\u003c\/li\u003e  \u003cli\u003eHPE Pointnext support longevity is a contractual requirement favoring the newer platform\u003c\/li\u003e  \u003cli\u003eThe organization has a Gen10+ standardization policy for new infrastructure purchases\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003eFor storage-primary deployments where spinning disk is the bottleneck and lifecycle extends only 3–4 years, the Gen10 12-Bay 3.5\" delivers equivalent storage performance at meaningfully lower acquisition cost. We'll show you both at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage — 12 LFF Bays\u003c\/h2\u003e\u003cp\u003eTwelve 3.5\" SAS\/SATA hot-swap bays. Up to 240 TB raw with 20 TB NL-SAS. RAID 6 mandatory for large-capacity NL-SAS arrays. Smart Array P816i-a (4 GB FBWC) for production NAS with write workloads. Smart Array E208i-a (HBA mode) for Ceph, GlusterFS, ZFS. Same drive options and RAID guidance as the Gen10 LFF configuration.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eJustified for long-lifecycle LFF deployments or converged workloads where Ice Lake compute matters alongside LFF storage. For storage-primary spinning disk deployments with shorter lifecycles, the Gen10 12-Bay delivers better ROI. We'll quote both.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eNavigation:\u003c\/strong\u003e Gen10 equivalent → \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eDL380 Gen10 12-Bay 3.5\"\u003c\/a\u003e. Gen10+ SFF alternative → \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-8-bay-build-your-own\"\u003eDL380 Gen10+ 8-Bay\u003c\/a\u003e.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e\n\u003cth\u003eGen10+ LFF is justified for\u003c\/th\u003e\n\u003cth\u003eGen10 LFF is sufficient for\u003c\/th\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Long-lifecycle NAS (deployment to 2030+)\u003c\/td\u003e\n\u003ctd\u003e✓ Storage-primary NAS, 3–4 year lifecycle\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Converged compute + LFF with Ice Lake IPC\u003c\/td\u003e\n\u003ctd\u003e✓ Spinning disk bottleneck workloads\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Gen10+ platform standardization policy\u003c\/td\u003e\n\u003ctd\u003e✓ Budget-primary bulk storage\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us your workload, capacity target, lifecycle requirement, and quantity. We'll return Gen10 and Gen10+ pricing side-by-side. Volume pricing at 5 units and above.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951282839751,"sku":"BP-012723","price":8262.83,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-gen10-12-bay-35-drives-710892.png?v=1765539707"},{"product_id":"hpe-proliant-dl380-gen10-plus-24-bay-build-your-own","title":"HPE ProLiant DL380 Gen10+ 24-Bay 2.5\" Drives","description":"\u003cp\u003eThe DL380 Gen10+ 24-Bay 2.5\" is the maximum SFF density configuration on the Gen10+ platform — twenty-four hot-swap bays with PCIe Gen4 NVMe backplane support, Ice Lake Xeon, 32 DIMM slots, and vSAN ESA compatibility. For HPE shops building the largest vSAN ESA clusters, high-density NVMe-oF storage targets, or Ceph deployments at maximum per-node drive count with the newest platform generation, this is the configuration.\u003c\/p\u003e\u003cp\u003eFor full Gen10+ platform details see the \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-8-bay-build-your-own\"\u003eDL380 Gen10+ 8-Bay page\u003c\/a\u003e.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage — 24 SFF Bays + Gen4 NVMe\u003c\/h2\u003e\u003cp\u003eTwenty-four 2.5\" hot-swap bays with PCIe Gen4 NVMe backplane. At full NVMe population, Gen4 NVMe SSDs at 24 bays deliver aggregate sequential read throughput exceeding 100 GB\/s — a scale of storage performance not achievable on Gen10 platforms. Common configurations:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003evSAN ESA all-flash:\u003c\/strong\u003e 24 Gen4 NVMe drives in unified ESA storage pool. Maximum vSAN ESA capacity and IOPS per node in the DL380 Gen10+ family. ESA requires Smart Array E208i-a HBA mode for direct drive pass-through.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNVMe-oF storage targets:\u003c\/strong\u003e 24 Gen4 NVMe drives as a disaggregated storage target serving multiple compute hosts via NVMe over Fabrics. 100 GbE required to avoid network becoming the throughput ceiling.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eCeph NVMe OSD nodes:\u003c\/strong\u003e 24 Gen4 NVMe OSDs per node at maximum per-node drive density. HBA mode for direct drive access by Ceph processes.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eAll-SAS SSD or hybrid:\u003c\/strong\u003e SAS\/SATA drives continue to work on Gen10+ backplanes for shops not requiring NVMe — same 24-bay flexibility as Gen10 but with Gen10+ compute advantages.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003e\u003cstrong\u003e24-Bay vs. 16-Bay Gen10+:\u003c\/strong\u003e If 16 NVMe drives per node covers your vSAN ESA or storage design, the 16-Bay is the lower-cost choice. The 24-Bay earns its premium when maximum per-node drive count is a specific design requirement — typically for large vSAN clusters optimizing per-node storage cost\/TB or NVMe-oF targets where aggregate per-node throughput is the design variable.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eThe most capable SFF storage configuration in the HPE DL380 Gen10+ family. Justified when maximum Gen4 NVMe drive density per 2U node is the design target. For most Gen10+ deployments, the 8-Bay or 16-Bay covers the storage requirement at lower cost — the 24-Bay is for large-scale storage-primary deployments where every additional NVMe drive per node improves cluster economics.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eNavigation:\u003c\/strong\u003e Step down → \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-16-bay-build-your-own\"\u003eDL380 Gen10+ 16-Bay\u003c\/a\u003e. Gen10 equivalent → \u003ca href=\"\/products\/hpe-dl380-g10-2-5-24-bay-chassis\"\u003eDL380 Gen10 24-Bay\u003c\/a\u003e.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e\n\u003cth\u003eThis server excels at\u003c\/th\u003e\n\u003cth\u003eConsider alternatives for\u003c\/th\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ vSAN ESA maximum per-node NVMe density\u003c\/td\u003e\n\u003ctd\u003e❌ 16 bays sufficient (Gen10+ 16-Bay lower cost)\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ NVMe-oF storage targets at Gen4 bandwidth\u003c\/td\u003e\n\u003ctd\u003e❌ vSAN OSA (Gen10 24-Bay sufficient)\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Ceph Gen4 NVMe OSD nodes (24 OSDs\/node)\u003c\/td\u003e\n\u003ctd\u003e❌ LFF drives preferred\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Maximum per-node Gen4 NVMe capacity\u003c\/td\u003e\n\u003ctd\u003e❌ Budget-primary deployments\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us your storage architecture (vSAN ESA, NVMe-oF, Ceph), drive type, Ice Lake CPU preference, memory target, and quantity. Volume pricing at 5 units and above.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951283036359,"sku":"BP-012721","price":7362.74,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-gen10-24-bay-25-drives-532354.png?v=1765539707"},{"product_id":"server-design-lab-hpe-proliant-bl460c-g9-2-bay-2-5-drives","title":"HPE ProLiant BL460c Gen9 Blade Server [Gen9]","description":"\u003ch2\u003e⚠️ Gen9 Platform — Read Before Configuring\u003c\/h2\u003e\u003cp\u003eGen9 blade platform (2014) — 11–12 years old. Full generational context: \u003ca href=\"\/products\/dl380-g9-2-5-8-bay-server\"\u003eDL380 Gen9 8-Bay page\u003c\/a\u003e. This page covers the HPE ProLiant BL460c Gen9 blade server.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePlatform Overview — Blade Architecture\u003c\/h2\u003e\u003cp\u003eThe HPE ProLiant BL460c Gen9 is a half-height blade server designed for the HPE BladeSystem c7000 enclosure. Blade architecture is fundamentally different from rack servers: compute and local storage are housed in a blade module, while networking, power distribution, and management infrastructure are shared across all blades in the enclosure via the c7000 midplane. For environments already standardized on HPE BladeSystem, the BL460c Gen9 is the Gen9 compute blade for that infrastructure.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eBlade vs. rack — when blades make sense for enterprise IT procurement:\u003c\/strong\u003e Blades reduce per-server cabling and power infrastructure complexity when deployed in large quantities (10+ blades per enclosure). The c7000 enclosure provides shared power, cooling, management, and switching fabric that makes per-blade management more efficient at scale. For smaller deployments (under 8 blades), rack servers typically deliver better economics — the enclosure infrastructure cost isn't justified at low blade counts.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eCritical prerequisite:\u003c\/strong\u003e The BL460c Gen9 requires a compatible HPE BladeSystem c7000 enclosure — it does not function as a standalone server. If you don't have an existing c7000 enclosure, you need to quote both the enclosure and blades. See the \u003ca href=\"\/products\/hpe-proliant-c7000-enclosure-chassis\"\u003eHPE c7000 Enclosure page\u003c\/a\u003e for enclosure options.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eProcessors\u003c\/h2\u003e\u003cp\u003eSingle or dual Intel Xeon E5-2600 v3\/v4. v4 preferred for any production-adjacent workload. Up to 44 cores dual-socket at v4. DDR4 ceiling 2400 MT\/s. Same processor family and limitations as all Gen9 platforms.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eMemory\u003c\/h2\u003e\u003cp\u003e16 DDR4 DIMM slots — 8 per CPU in dual-socket configuration. Less than the DL380 Gen9's 24 slots — blade form factor constrains DIMM count. Maximum memory capacity: 1 TB with 64 GB LRDIMMs at full 16-slot population. For workloads requiring large memory capacity per node, rack servers (DL380 Gen9 or Gen10) provide more DIMM slots at lower cost.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eLocal Storage — 2 SFF Bays\u003c\/h2\u003e\u003cp\u003eTwo 2.5\" SAS\/SATA hot-swap bays — the local storage limitation of the half-height blade form factor. These bays are primarily for OS and application data. Primary storage in blade environments typically comes from shared SAN resources accessible through the enclosure's Flex Fabric interconnects — not from local blade drives. For workloads requiring meaningful local storage per compute node, rack servers with more drive bays are the appropriate architecture.\u003c\/p\u003e\u003cp\u003eSmart Array P244br embedded RAID for Gen9 blade storage. iLO 4 management — Advanced license required for remote KVM.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking\u003c\/h2\u003e\u003cp\u003eBlade networking is provided through the c7000 enclosure's interconnect bays — FlexFabric or FlexNetwork modules in the enclosure midplane provide 10 GbE or higher connectivity to the blade's mezzanine NICs. The blade itself has embedded 1 GbE ports for management; production traffic traverses the enclosure interconnects. Confirm interconnect module compatibility with your planned NIC mezzanine at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eThe BL460c Gen9 is appropriate for organizations with existing HPE BladeSystem c7000 enclosures looking to add Gen9 compute capacity, or for new blade deployments where the economies of blade infrastructure at scale (10+ blades) justify the enclosure investment. For smaller deployments or new infrastructure decisions, evaluate whether Gen10 rack servers (DL360 Gen10, DL380 Gen10) deliver better overall value than building a blade infrastructure on Gen9.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eUpgrade path:\u003c\/strong\u003e \u003ca href=\"\/products\/hpe-bl460c-gen10-blade-server-build-your-own\"\u003eBL460c Gen10\u003c\/a\u003e for iLO 5, Xeon Scalable, longer lifecycle. \u003ca href=\"\/products\/dl360-g10-chassis\"\u003eDL360 Gen10 8-Bay\u003c\/a\u003e if moving from blade to rack.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e\n\u003cth\u003eBL460c Gen9 is appropriate for\u003c\/th\u003e\n\u003cth\u003eConsider alternatives for\u003c\/th\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Expanding existing c7000 Gen9 blade infrastructure\u003c\/td\u003e\n\u003ctd\u003e❌ No existing c7000 enclosure (need rack servers)\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Large-scale blade deployments (10+ blades) at Gen9 pricing\u003c\/td\u003e\n\u003ctd\u003e❌ Local storage-primary workloads (only 2 bays)\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ SAN-connected compute in blade form factor\u003c\/td\u003e\n\u003ctd\u003e❌ Production running 3+ years\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eBlade configurations require c7000 enclosure compatibility verification. Tell us your existing enclosure generation, interconnect modules, and required blade count. Our team responds within 24 hours. Volume pricing at 5 units and above.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951283265735,"sku":"BP-012740","price":126.01,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-bl460c-g9-2-bay-25-drives-499403.png?v=1765539707"},{"product_id":"hpe-bl460c-gen10-blade-server-build-your-own","title":"HPE ProLiant BL460c Gen10 Blade Server","description":"\u003cp\u003eThe HPE ProLiant BL460c Gen10 is the current-generation half-height blade server for HPE BladeSystem c7000 enclosures — the Gen10 equivalent of the BL460c Gen9, running Intel Xeon Scalable processors (Skylake or Cascade Lake) with iLO 5, PCIe 3.0 connectivity, and the full Gen10 management and security platform. For HPE BladeSystem environments that have already invested in c7000 enclosure infrastructure, the BL460c Gen10 is the upgrade path that preserves enclosure compatibility while moving to Gen10 compute.\u003c\/p\u003e\u003cp\u003eFor blade architecture fundamentals — when blades make sense vs. rack servers, c7000 enclosure prerequisites, networking through enclosure interconnects — see the \u003ca href=\"\/products\/server-design-lab-hpe-proliant-bl460c-g9-2-bay-25-drives\"\u003eBL460c Gen9 page\u003c\/a\u003e. All of that framing applies to the Gen10 blade as well. This page covers what changes in Gen10 and when the upgrade from Gen9 is worth making.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eCritical prerequisite:\u003c\/strong\u003e The BL460c Gen10 requires a compatible HPE BladeSystem c7000 enclosure. It cannot function as a standalone server. If you don't have an existing c7000 enclosure, see the \u003ca href=\"\/products\/hpe-proliant-c7000-enclosure-chassis\"\u003eHPE c7000 Enclosure page\u003c\/a\u003e.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eGen10 vs. Gen9 Blade — What Changes\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eiLO 5 vs. iLO 4:\u003c\/strong\u003e The Gen10 blade ships with iLO 5 — Silicon Root of Trust, firmware integrity monitoring, improved REST API, Active Health System v2. The same iLO 5 vs. iLO 4 security gap as the rack server comparison. For compliance environments and longer-lifecycle blade deployments, iLO 5 is a meaningful improvement.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eIntel Xeon Scalable (Skylake\/Cascade Lake):\u003c\/strong\u003e Up to 28 cores per CPU (vs. 22 on Gen9 Broadwell v4), higher DDR4 memory speeds (up to 2933 MT\/s vs. 2400 MT\/s on Gen9), hardware-level speculative execution mitigations on Cascade Lake.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePCIe 3.0 connectivity:\u003c\/strong\u003e Same as the DL380 Gen10 — compatible with current-generation mezzanine cards and interconnect modules in the c7000 enclosure.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePlatform longevity:\u003c\/strong\u003e Gen10 blades will remain in HPE's support window significantly longer than Gen9. For blade deployments intended to run 3–5 years, Gen10 is the right generation investment.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eProcessors\u003c\/h2\u003e\u003cp\u003eSingle or dual Intel Xeon Scalable 1st or 2nd Generation (Skylake or Cascade Lake). v2 (Cascade Lake) preferred for production deployments — hardware mitigations, faster DDR4, better IPC. Up to 56 cores dual-socket with 28-core Cascade Lake SKUs. TDP range from 85W Silver through 205W Platinum.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eMemory\u003c\/h2\u003e\u003cp\u003eUp to 24 DDR4 DIMM slots — 12 per CPU in dual-socket configuration. Matches the DL380 Gen10 rack server's DIMM count — more than the BL460c Gen9's 16 slots. Maximum capacity: 3 TB with LRDIMMs. DDR4 speed at 2 DPC: 2666 MT\/s on most Cascade Lake SKUs — consistent with Gen10 rack platform behavior.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eLocal Storage\u003c\/h2\u003e\u003cp\u003eTwo 2.5\" SAS\/SATA hot-swap bays — same local storage limitation as the Gen9 blade. Primary storage in blade environments is SAN-attached through the enclosure's Flex Fabric interconnects. Local blade drives are typically used for OS and application data only. For storage-primary workloads, rack servers with higher local drive counts are the appropriate architecture.\u003c\/p\u003e\u003cp\u003eSmart Array P204i-b (no-cache, Gen10 embedded) for basic RAID. For production storage requiring write cache, evaluate SAN-attached storage through the enclosure. M.2 SATA boot may be available on some Gen10 blade configurations — confirm at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking Through the c7000\u003c\/h2\u003e\u003cp\u003eThe BL460c Gen10 supports 10 GbE and 25 GbE mezzanine NICs — confirm compatibility with the interconnect modules installed in your c7000 enclosure. Gen10 blades require Gen10-compatible Virtual Connect or FlexFabric interconnect modules for full feature access. If your c7000 enclosure is populated with Gen9-era interconnects, confirm compatibility before ordering Gen10 blades. Our team can assist with interconnect compatibility validation at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eManagement — iLO 5\u003c\/h2\u003e\u003cp\u003eiLO 5 Standard ships on all BL460c Gen10 units. iLO 5 Advanced license required for remote KVM console — same requirement as rack servers. For blade environments managed through HPE OneView, iLO 5 is the management foundation that OneView integrates with for Gen10 blade health, lifecycle, and configuration management.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eThe BL460c Gen10 is the right blade for HPE BladeSystem environments making a generational transition from Gen9 — better compute, more memory capacity, iLO 5, longer lifecycle. For organizations building new blade infrastructure, we recommend evaluating whether the c7000 enclosure investment is justified for the planned blade count, or whether Gen10 rack servers (DL360 Gen10 for 1U density) deliver better overall economics. Our general guidance: blade infrastructure makes financial sense at 8+ blades per enclosure in most deployments. Fewer than that, rack servers are almost always more cost-efficient.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhere to look instead:\u003c\/strong\u003e\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eNo existing c7000 enclosure?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl360-g10-chassis\"\u003eDL360 Gen10 8-Bay rack server\u003c\/a\u003e — comparable 1U compute without enclosure dependency\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed to buy enclosure too?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-c7000-enclosure-chassis\"\u003eHPE c7000 Enclosure\u003c\/a\u003e — quote enclosure + blades together\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eStaying on Gen9 blade infrastructure?\u003c\/strong\u003e → \u003ca href=\"\/products\/server-design-lab-hpe-proliant-bl460c-g9-2-bay-25-drives\"\u003eBL460c Gen9\u003c\/a\u003e — lower cost for matching existing node generation\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e\n\u003cth\u003eBL460c Gen10 is appropriate for\u003c\/th\u003e\n\u003cth\u003eConsider rack servers for\u003c\/th\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Expanding existing c7000 infrastructure with Gen10 compute\u003c\/td\u003e\n\u003ctd\u003e❌ No existing c7000 enclosure\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Replacing Gen9 blades with Gen10 in existing enclosures\u003c\/td\u003e\n\u003ctd\u003e❌ Local storage-primary workloads\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Large-scale SAN-connected compute in blade form factor\u003c\/td\u003e\n\u003ctd\u003e❌ Fewer than 8 blades planned\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ iLO 5 management upgrade from Gen9 blade fleet\u003c\/td\u003e\n\u003ctd\u003e❌ Gen10+ \/ Ice Lake required\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eBlade configurations require c7000 enclosure compatibility verification — existing enclosure generation, Virtual Connect \/ interconnect module versions, and planned mezzanine NIC. Tell us your enclosure details, required blade count, CPU and memory targets, and quantity. Our team responds within 24 hours. Volume pricing at 5 units and above.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951283396807,"sku":"BP-012742","price":270.03,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-bl460c-g10-25-blade-887711.png?v=1765539707"},{"product_id":"hpe-proliant-c7000-enclosure-chassis","title":"HPE Proliant C7000 Enclosure Chassis","description":"\u003cp\u003eThe\u003cstrong\u003e \u003c\/strong\u003eHPE BladeSystem c7000 Enclosure is a high-density, modular platform designed to house and manage HPE ProLiant and Integrity blade servers. Supporting up to 16 half-height or 8 full-height blades, it features integrated power, cooling, and networking with redundant power supplies and Active Cool fans for high efficiency. The c7000 offers flexible I\/O connectivity with up to eight interconnect bays for Fibre Channel, Ethernet, and InfiniBand modules. Combined with HPE Onboard Administrator and iLO management, it provides a scalable, cost-effective solution for enterprise data centers looking to optimize compute density and operational efficiency.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951283462343,"sku":"BP-012747","price":1530.15,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/hpe-proliant-c7000-enclosure-chassis-162709.png?v=1765539706"},{"product_id":"hpe-proliant-dl380-gen10-8-bay-build-your-own","title":"HPE ProLiant DL380 Gen10 8-Bay 2.5\" Drives","description":"\u003cp\u003eThe HPE ProLiant DL380 Gen10 is the workhorse of the HPE enterprise server lineup — a 2U dual-socket rack server that has been the most widely deployed HPE platform in enterprise datacenters worldwide for the better part of a decade. Built on Intel Xeon Scalable processors (both 1st Gen Skylake and 2nd Gen Cascade Lake depending on configuration), the DL380 Gen10 covers an exceptional range of workloads: virtualization, database serving, NAS and SAN storage, analytics, and general enterprise application hosting. If you are buying HPE and haven't narrowed down to a specific model, the DL380 Gen10 is almost always where the conversation starts.\u003c\/p\u003e\u003cp\u003eThe 8-Bay 2.5\" configuration is the compute-first variant — eight SFF hot-swap bays for local SSD storage alongside the full dual-socket DL380 platform. It's the right starting point for virtualization hosts, database servers, and compute-primary deployments where moderate local SSD storage is needed but bulk storage lives on a SAN or NAS.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eGen10 vs. Gen10+ vs. Gen9 — the positioning:\u003c\/strong\u003e Gen10 (2017–2019) is the current production-tier secondary market platform — mature, well-supported, excellent ROI. Gen10+ (2021) brings Ice Lake Xeon (3rd gen Scalable), PCIe Gen4, and extended lifecycle — at meaningfully higher acquisition cost. Gen9 (2014–2016) is the previous generation equivalent of the Dell 13th gen — significantly lower cost, but the same platform age caveats apply. We offer all three and will recommend the right one for your lifecycle and budget at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eHPE Platform Vocabulary — Key Differences from Dell\u003c\/h2\u003e\u003cp\u003eIf you're more familiar with Dell PowerEdge, the HPE equivalents are:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eiLO (Integrated Lights-Out)\u003c\/strong\u003e = iDRAC. iLO 5 is the Gen10 management controller — equivalent to iDRAC9 in capability. iLO Advanced license = iDRAC9 Enterprise (remote KVM, advanced features). iLO Standard ships by default and lacks remote console access.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eHPE Smart Array\u003c\/strong\u003e = PERC RAID controllers. P408i-a (2 GB cache) ≈ PERC H730P. P816i-a (4 GB cache) ≈ PERC H740P. E208i-a (no cache) ≈ PERC H330 \/ HBA330.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eFlexibleLOM (FlexLOM)\u003c\/strong\u003e = OCP mezzanine slot. Primary NIC connectivity goes here — same concept as Dell's OCP 3.0 slot.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eHPE Persistent Memory (NVDIMM)\u003c\/strong\u003e = Optane PMem equivalent (supported on Gen10 with 2nd Gen Xeon Scalable).\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eProcessors\u003c\/h2\u003e\u003cp\u003eDual Intel Xeon Scalable processors — the DL380 Gen10 supports both 1st Generation (Skylake, launched 2017) and 2nd Generation (Cascade Lake, launched 2019) Xeon Scalable depending on the specific configuration. Up to 28 cores per CPU on Skylake, up to 28 cores per CPU on Cascade Lake (though higher core count SKUs are available). TDP range from 85W Bronze\/Silver through 205W Platinum.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eOur recommendation:\u003c\/strong\u003e 2nd Generation Cascade Lake processors wherever the application profile justifies them — better IPC, hardware-level speculative execution mitigations, higher memory speed support (2933 MT\/s vs. 2666 MT\/s on Skylake at 1 DPC), and Optane PMem compatibility. For workloads where the generation distinction doesn't matter — file serving, backup, dev\/test — 1st Gen Skylake at lower acquisition cost is fully adequate.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eHeatsink requirement for high-TDP CPUs:\u003c\/strong\u003e Processors above 150W require high-performance heatsinks. HPE uses a different heatsink designation than Dell — confirm with our team at quote time for any configuration with 165W+ processors.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eMemory\u003c\/h2\u003e\u003cp\u003e24 DDR4 DIMM slots — 12 per CPU, six memory channels per socket. Maximum 3 TB with LRDIMMs. HPE Persistent Memory (NVDIMM-N) supported on Gen10 with 2nd Gen Xeon.\u003c\/p\u003e\u003cp\u003eFull 2 DPC population (2 DIMMs Per Channel) maximizes memory bandwidth — the same channel utilization logic as Dell R640. At 2 DPC on most Cascade Lake SKUs, speed settles at 2666 MT\/s — the bandwidth gain from all six channels running at 2666 MT\/s consistently outperforms partial population at 2933 MT\/s for memory-bound workloads. For 1st Gen Skylake configurations, maximum memory speed is typically 2666 MT\/s at 1 DPC, 2400 MT\/s at 2 DPC.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eiLO Advanced Memory Error Detection:\u003c\/strong\u003e The DL380 Gen10's iLO 5 provides per-DIMM memory error logging and predictive failure analytics — a meaningful advantage for large-memory configurations where early DIMM failure detection avoids unplanned downtime.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eStorage — 8 SFF Bays\u003c\/h2\u003e\u003cp\u003eEight 2.5\" SAS\/SATA hot-swap bays on a Smart Array backplane. Same general storage flexibility as the Dell R640\/R740 8-Bay SFF configurations — SAS SSDs for performance, SATA SSDs for mixed workloads, SAS HDDs for capacity, and mixed configurations for tiered approaches.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eHPE NVMe implementation note:\u003c\/strong\u003e The DL380 Gen10 supports NVMe via PCIe riser expansion (NVMe add-in cards) rather than native backplane NVMe in the standard 8-bay configuration. HPE introduced native backplane NVMe more comprehensively in the Gen10+ generation. For NVMe-primary storage architectures, the Gen10+ configurations or dedicated NVMe PCIe cards are the paths. We'll advise on the best NVMe approach for your specific design at quote time.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eHPE Secure Encryption:\u003c\/strong\u003e The DL380 Gen10 supports drive-level encryption through the Smart Array controller — a compliance feature worth noting for regulated data environments.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eM.2 boot drives:\u003c\/strong\u003e HPE Gen10 supports M.2 SATA\/NVMe boot drives via an optional M.2 enablement kit — the equivalent of Dell's BOSS module. We include this on builds where OS isolation from the data storage pool is a requirement. Confirm at quote time.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eSmart Array RAID Controllers\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P816i-a (4 GB Flash-backed Write Cache, FBWC):\u003c\/strong\u003e Our top recommendation for production workloads with meaningful write I\/O. The P816i-a supports up to 16 drives and uses flash-backed write cache — no battery to replace, capacitor-backed with NAND persistence. Equivalent in capability to Dell's H740P. For database workloads, vSAN with hardware RAID, and any application where write latency matters, start here.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array P408i-a (2 GB FBWC):\u003c\/strong\u003e Standard production recommendation for mixed or read-dominant workloads. Supports up to 8 drives in the internal configuration. The most common controller we quote for general-purpose DL380 Gen10 deployments.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eSmart Array E208i-a (no cache, HBA mode):\u003c\/strong\u003e For software-defined storage (vSAN, Ceph, Windows Storage Spaces) where the software layer manages redundancy. Passes drives directly to the OS without hardware RAID. Required for vSAN deployments — same reasoning as Dell's HBA330.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003e\u003cstrong\u003eHPE FBWC vs. Dell battery-backed cache:\u003c\/strong\u003e HPE uses Flash-Backed Write Cache (FBWC) — capacitor-backed with NAND persistence — instead of Dell's battery-backed NV cache. In practice, both protect cached writes through power events. FBWC has the advantage of no battery replacement cycle (typical HPE battery backup module lifespan is 3 years; FBWC capacitors are rated for the server's lifecycle). We consider them equivalent in production protection capability.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eNetworking\u003c\/h2\u003e\u003cp\u003eFlexibleLOM mezzanine slot plus PCIe expansion slots. Standard networking options:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eHPE Ethernet 10Gb 2-port 562SFP+ FLR-SFP+ Adapter:\u003c\/strong\u003e Our standard recommendation for most DL380 Gen10 deployments — dual-port 10 GbE via FlexLOM, leaving PCIe slots available for storage and other expansion.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eHPE Ethernet 25Gb 2-port 640SFP28 Adapter:\u003c\/strong\u003e For high-throughput virtualization nodes, storage-serving configurations, or environments where 10 GbE is insufficient. Recommended for vSAN all-flash nodes and NVMe-backed storage configurations.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eHPE Ethernet 10Gb 4-port 561FLR-T RJ45 Adapter:\u003c\/strong\u003e For environments requiring copper 10 GbE — common in deployments without SFP+ switching infrastructure.\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003ePower Supplies\u003c\/h2\u003e\u003cp\u003eHPE Flex Slot hot-swap redundant PSUs. Standard options for the DL380 Gen10:\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003e2x 500W Flex Slot Platinum:\u003c\/strong\u003e For Silver\/Bronze CPU configurations with moderate drive population and no GPU. Tight headroom for fully-loaded Gold\/Platinum builds.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e2x 800W Flex Slot Platinum:\u003c\/strong\u003e Our standard recommendation for dual Gold\/Platinum builds with full memory and SSD drive population. Adequate for most general-purpose configurations.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003e2x 1600W Flex Slot Titanium:\u003c\/strong\u003e For GPU configurations, high-TDP CPU combinations, or fully-loaded storage configurations. Titanium efficiency delivers measurable savings in large-scale deployments.\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003e\u003cstrong\u003ePower planning:\u003c\/strong\u003e A dual Gold 6230 (Cascade Lake) configuration with 24 DIMMs and 8x SAS SSDs draws approximately 420–520W at peak. For GPU-equipped configurations, factor in GPU TDP using the same methodology as Dell builds — CPU TDP × 2 + memory + drives + GPU TDP, sized to 70–75% PSU capacity for longevity.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eManagement — iLO 5\u003c\/h2\u003e\u003cp\u003e\u003cstrong\u003eiLO 5 Standard\u003c\/strong\u003e ships on all DL380 Gen10 units. It provides basic hardware monitoring, SNMP alerting, and SSH\/REST API access — but without remote KVM console. For production datacenter deployment, iLO 5 Advanced license is required.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eiLO 5 Advanced (required for production):\u003c\/strong\u003e Adds remote KVM console (HTML5 and Java), virtual media, HPE Intelligent Provisioning (OS deployment without physical media), Agentless Management Service integration, Active Health System logging, and Silicon Root of Trust. The equivalent of Dell iDRAC9 Enterprise. We include the iLO Advanced license on every production build we configure.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eSilicon Root of Trust:\u003c\/strong\u003e The DL380 Gen10 introduced HPE's Silicon Root of Trust — firmware signed at the silicon level, preventing unsigned firmware from running. Equivalent in concept to Dell's Silicon Root of Trust in iDRAC9, and a meaningful security advantage over Gen9 and earlier platforms.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eTrusted Platform Module (TPM):\u003c\/strong\u003e Optional TPM 2.0 module — include it. Same compliance framework requirements as Dell deployments (NIST, CMMC, FedRAMP).\u003c\/p\u003e\u003chr\u003e\u003ch2\u003ePhysical Specs\u003c\/h2\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eForm factor:\u003c\/strong\u003e 2U rack — 86.8mm H × 447mm W (slightly wider than Dell 2U), chassis depth approximately 748mm\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePCIe slots:\u003c\/strong\u003e Up to 8 PCIe 3.0 slots depending on riser configuration — comparable to the Dell R740\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eCPU hot-plug:\u003c\/strong\u003e Not supported\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003ePlatform maturity:\u003c\/strong\u003e Gen10 launched in 2017. Mature platform with stable firmware, strong parts availability, and HPE Pointnext support still available. No immediate end-of-support pressure for most configurations.\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eAccessories:\u003c\/strong\u003e HPE Ball Bearing Sliding Rail Kit (Gen8\/9\/10 2U SFF) for rack mounting; HPE Gen10 Security Bezel\u003c\/li\u003e\n\u003c\/ul\u003e\u003chr\u003e\u003ch2\u003eOur Assessment\u003c\/h2\u003e\u003cp\u003eThe DL380 Gen10 8-Bay 2.5\" is the right HPE platform for the widest range of enterprise workloads — virtualization hosts, database servers, application serving, and compute-primary deployments where moderate local SSD storage covers the need and bulk storage lives on a SAN or NAS. It's the HPE equivalent of the Dell R640, and for shops standardized on HPE infrastructure and iLO management, it's typically the default recommendation for new workloads that don't have specific requirements driving them to the DL360 (1U), DL380 Gen10+ (newer Xeon), or DL560 (4-socket).\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhere it excels:\u003c\/strong\u003e VMware vSphere and vSAN nodes, Microsoft Hyper-V clusters, SQL Server and Oracle deployments, general enterprise application serving, VDI workloads, and any compute-primary deployment where HPE is the preferred platform.\u003c\/p\u003e\u003cp\u003e\u003cstrong\u003eWhere to look instead:\u003c\/strong\u003e\u003c\/p\u003e\u003cul\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed 1U?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl360-g10-chassis\"\u003eDL360 Gen10 8-Bay\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed more SFF bays?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g10-2-5-16-bay-server\"\u003eDL380 Gen10 16-Bay\u003c\/a\u003e or \u003ca href=\"\/products\/hpe-dl380-g10-2-5-24-bay-chassis\"\u003eDL380 Gen10 24-Bay\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed LFF capacity drives?\u003c\/strong\u003e → \u003ca href=\"\/products\/hp-proliant-dl380-g10-3-5-12-bay-server\"\u003eDL380 Gen10 12-Bay 3.5\"\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eNeed Ice Lake Xeon \/ PCIe Gen4?\u003c\/strong\u003e → \u003ca href=\"\/products\/hpe-proliant-dl380-gen10-plus-8-bay-build-your-own\"\u003eDL380 Gen10+ 8-Bay\u003c\/a\u003e\n\u003c\/li\u003e  \u003cli\u003e\n\u003cstrong\u003eBudget-first, shorter lifecycle?\u003c\/strong\u003e → \u003ca href=\"\/products\/dl380-g9-2-5-8-bay-server\"\u003eDL380 Gen9 8-Bay\u003c\/a\u003e — significantly lower cost, same generational caveats as Dell 13th gen\u003c\/li\u003e\n\u003c\/ul\u003e\u003cp\u003e\u003cstrong\u003eRefurbished context for 2026:\u003c\/strong\u003e The DL380 Gen10 launched in 2017 and has been in production environments for 7–9 years. Platform maturity is excellent — HPE Pointnext support still active, firmware stable, parts plentiful. For workloads that don't require Ice Lake (Gen10+) or PCIe Gen4, the Gen10 delivers excellent ROI at secondary market pricing. We test every refurbished DL380 Gen10 through HPE's Active Health System diagnostics and verify iLO firmware, Smart Array firmware, and drive health before shipment.\u003c\/p\u003e\u003chr\u003e\u003ch2\u003eWorkload Fit\u003c\/h2\u003e\u003ctable\u003e  \u003ctr\u003e\n\u003cth\u003eThis server excels at\u003c\/th\u003e\n\u003cth\u003eConsider alternatives for\u003c\/th\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ VMware vSphere \/ vSAN nodes\u003c\/td\u003e\n\u003ctd\u003e❌ 1U form factor required (use DL360 Gen10)\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ Microsoft Hyper-V clusters\u003c\/td\u003e\n\u003ctd\u003e❌ Ice Lake \/ PCIe Gen4 needed (use Gen10+)\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ SQL Server and enterprise databases\u003c\/td\u003e\n\u003ctd\u003e❌ More than 8 SFF bays needed\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ General enterprise application serving\u003c\/td\u003e\n\u003ctd\u003e❌ LFF capacity drives required\u003c\/td\u003e\n\u003c\/tr\u003e  \u003ctr\u003e\n\u003ctd\u003e✅ VDI and high-density virtualization\u003c\/td\u003e\n\u003ctd\u003e❌ Budget-primary shorter lifecycle\u003c\/td\u003e\n\u003c\/tr\u003e\n\u003c\/table\u003e\u003chr\u003e\u003ch2\u003eReady to Configure?\u003c\/h2\u003e\u003cp\u003eTell us your workload, memory target, storage configuration, iLO Advanced licensing preference, and quantity. Our account team returns a validated configuration with formal pricing within 24 hours. Volume pricing at 5 units and above. We can quote both Gen10 and Gen10+ side-by-side if you want to evaluate the generational premium against your lifecycle requirements.\u003c\/p\u003e","brand":"HPE","offers":[{"title":"Default Title","offer_id":45951302926535,"sku":"BP-013539","price":669.87,"currency_code":"USD","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0748\/4493\/0247\/files\/server-design-lab-hpe-proliant-dl380-gen10-8-bay-25-drives-589493.png?v=1765539743"}],"url":"https:\/\/wholesaleservers.com\/collections\/hpe-servers.oembed","provider":"Wholesale Servers","version":"1.0","type":"link"}