HPE ProLiant DL360 Gen10 DIMM Population Rules Explained

The HPE ProLiant DL360 Gen10 is a compact, dual-socket server that can deliver substantial memory bandwidth when its modules are installed in the correct order. Its memory layout depends on the installed processor count, channel balance, DIMM technology, and supported speeds of the Intel Xeon Scalable processor. Understanding the server's DIMM population rules helps you avoid POST warnings, disabled slots, reduced performance, and incompatible upgrades. This guide explains the physical layout, supported DDR4 memory types, recommended installation sequence, capacity choices, common mistakes, and the tools Hewlett Packard Enterprise provides for verification.

How is memory arranged in the HPE ProLiant DL360 Gen10?

DIMM slots, processor sockets, and memory channels

The server has 24 DIMM slots in total, divided evenly between the two processor sockets. Each CPU controls 12 slots arranged across six memory channels, with up to two DIMMs connected to each channel. The slot labels and color coding on the system board identify the channel relationships and the preferred first position in each pair.

Memory is electrically attached to a processor rather than shared equally by the entire chassis. A DIMM installed in the first CPU's bank is controlled by CPU 1, while a DIMM connected to CPU 2 is controlled by the second processor. This arrangement makes channel balance important for bandwidth, latency, troubleshooting, and future expansion.

How the first and second CPUs affect available memory

In a single-CPU server, only the memory slots associated with the installed processor are available. Installing modules in the second processor's slots does not make that memory usable when CPU 2 is absent. A dual-socket processor configuration activates the second group of channels and enables the full 24-slot layout.

Adding a second processor therefore increases more than compute capacity. It also provides access to another 12 DIMM slots and another six memory channels. However, the two processor sides should be planned independently and populated evenly. A server with CPU 2 installed but an empty memory bank can operate, but it may not deliver the bandwidth or capacity you expected.

What are the DL360 Gen10 DIMM population rules?

The correct order for installing DIMMs

The basic rule is to install the first DIMM in every available channel before installing a second DIMM in any channel. In practical terms, follow the slot labels and the first-DIMM positions shown in the HPE service guide, populating one slot in each of the six channels connected to a processor. Only after those positions are filled should you use the companion second slot in each channel.

Use matched modules whenever possible, especially when installing a set during the same upgrade. The system board's labels and slot colors are more reliable than guessing from physical proximity. Before opening the server, record the existing arrangement, power the system down completely, and verify the supported slot sequence for the exact system board revision and processor combination.

Why balanced population matters

A balanced memory configuration gives the processor access to all of its memory channels instead of concentrating capacity in only a few. With one equal-capacity DIMM in each channel, memory transfers can be distributed across the available channel paths. This generally provides better bandwidth than placing the same total capacity into fewer channels.

For example, six 16 GB modules normally provide a better channel layout than three 32 GB modules when both capacities are supported. Balance each CPU independently, then keep the module sizes and technologies consistent across corresponding positions. Capacity is still important, but filling channels evenly should be the first performance priority.

Which DIMM types and capacities does the DL360 Gen10 support?

RDIMM versus LRDIMM

The DL360 Gen10 supports registered DIMM (RDIMM) and load-reduced DIMM (LRDIMM) technologies, subject to the relevant HPE QuickSpecs and processor generation. RDIMMs use a register to reduce electrical loading on the memory controller. LRDIMMs use additional buffering and are typically selected when a configuration requires higher per-module capacity.

RDIMM is often the practical choice for general virtualization, database, and application workloads because it is widely available and offers a straightforward cost-to-capacity balance. LRDIMM can support larger configurations, but it may have different speed, capacity, and population limits. Confirm the exact HPE-qualified part number before purchasing, rather than relying only on a module's label.

Supported DDR4 speeds and processor limitations

The server uses DDR4 memory, and supported operating speeds depend on the module type, DIMM population, and installed Intel Xeon Scalable processors. A DIMM rated for a higher speed does not guarantee that the system will run at that speed. The processor's integrated memory controller and the number of DIMMs per channel can impose a lower operating frequency.

Different Xeon Scalable generations supported by the platform can have different maximum memory speeds and addressable capacities. HPE may also qualify particular capacity points, such as 16 GB, 32 GB, 64 GB, or larger modules, differently by technology and processor. Treat the server's QuickSpecs as the final authority for a specific build.

Why mixing memory types is not supported

Do not mix RDIMM and LRDIMM modules in the same server. These technologies use different electrical buffering methods and memory controller requirements, so combining them can prevent the system from completing POST or cause the platform to reject some or all installed memory.

Keep the same memory technology across both processors when possible, and use modules with compatible ranks, capacities, and speed ratings. Even when a mixed combination appears physically compatible, HPE support and system firmware may not validate it. A matched, HPE-qualified set is safer than combining unrelated modules from multiple vendors.

How should you populate memory for performance or maximum capacity?

Recommended configurations for one DIMM per channel

The preferred starting point is one DIMM per channel. For one processor, that means six equal modules, one in each of its six channels. For two processors, use six corresponding modules on CPU 1 and six on CPU 2 when the workload and budget justify that capacity. This arrangement maximizes the number of active channel paths before adding electrical load.

A six-module set can be built from the capacity that fits your workload, such as six 16 GB modules for 96 GB on one CPU or six 32 GB modules for 192 GB. These examples are illustrative, not universal guarantees. Confirm the module capacity and processor support in HPE's configuration rules before ordering.

When to add a second DIMM per channel

Add a second DIMM to a channel only after the first position in every channel is occupied. This approach is useful when you need more capacity but want to preserve a balanced layout. The additional modules may also cause the memory controller to operate at a lower supported speed, depending on DIMM type, rank structure, and processor model.

For capacity-focused systems, two modules per channel can be appropriate for virtualization hosts, in-memory databases, and large analytics workloads. Do not add modules randomly to whichever slots are easiest to reach. Expand in complete channel sets when possible, and use equal-capacity modules in the second positions to maintain predictable behavior.

Capacity planning for single- and dual-processor systems

A single-processor system is limited to the 12 slots and six channels attached to CPU 1. A dual-processor system can use all 24 slots, but its maximum supported capacity depends on the processors, RDIMM or LRDIMM choice, DIMM capacities, firmware, and HPE qualification rules.

Plan for the workload's future growth rather than filling every slot immediately. Larger modules can leave slots available for expansion, while smaller modules may provide a lower initial cost and more granular upgrades. Also account for operating-system limits, hypervisor licensing, and the memory reserved for firmware and hardware.

What happens when DIMMs are installed incorrectly?

Unsupported combinations and boot or POST warnings

An unsupported combination can produce a failed POST, a memory-related warning, disabled modules, or a system that reports less usable RAM than expected. Common triggers include mixing RDIMM and LRDIMM, exceeding the processor's supported capacity, using incompatible ranks, or installing memory in slots controlled by an absent processor.

Read the Integrated Management Log and any message shown during startup before changing parts. A warning does not always mean the DIMM is defective. It may indicate an invalid population order, a speed reduction, an unrecognized spare module, or a configuration that firmware has deliberately disabled.

Reduced memory speed and unbalanced channels

Even a configuration that boots can operate below the DIMM's advertised rating. The memory controller selects a common supported speed based on the processor, module type, rank arrangement, and number of modules per channel. Adding a second DIMM per channel commonly increases capacity while reducing the maximum validated frequency.

Unbalanced channels can also reduce bandwidth. For example, placing several modules on two channels while leaving the remaining channels empty may provide the desired capacity but prevents the processor from using all available paths evenly. Rearranging the same modules into a balanced pattern can improve throughput without buying additional memory.

Common installation mistakes

Frequent mistakes include installing modules in visually convenient slots, forgetting that CPU 2 controls a separate memory bank, mixing capacities without checking the guide, and overlooking a partially inserted DIMM latch. Static discharge, handling modules by the contacts, and failing to update firmware can create additional troubleshooting problems.

Before reseating memory, remove power according to the service procedure and use proper electrostatic protection. Check that each module is fully locked into its slot, compare the physical arrangement with the system board diagram, and test changes one step at a time. Keep the original modules available so you can isolate a failed part from a population error.

How can you verify a DL360 Gen10 memory upgrade?

Checking DIMM status in HPE iLO 5

HPE iLO 5 provides a convenient first check after an upgrade. In the iLO web interface, review the memory inventory and health information for each processor and slot. The page can show the detected capacity, module status, speed information, and whether a location has reported an error.

Use the slot-by-slot view to compare the installed pattern with your intended design. If a module is missing from inventory, check whether it belongs to CPU 2, whether that processor is installed and enabled, and whether the module is seated correctly. iLO event logs can also reveal corrected errors or configuration warnings that are not obvious during normal operation.

Confirming capacity and speed in the system utilities

During startup, enter the HPE System Utilities or UEFI memory information screen to confirm total installed capacity and the operating memory speed. The operating system and hypervisor should then report a matching, usable amount after accounting for normal hardware reservations.

Compare the reported speed with the module label carefully. A 2933 MT/s-rated module may run at a lower speed when the processor or population rules require it. What matters is whether the reported speed is expected for the complete configuration, not whether it matches the highest number printed on the DIMM.

Using HPE documentation and SmartMemory validation

HPE SmartMemory is Hewlett Packard Enterprise's qualified memory program for supported ProLiant systems. SmartMemory modules can provide identification, configuration, and health information that helps the server firmware apply validated settings and report issues more clearly than generic memory.

For final verification, compare your exact server model, processor generation, DIMM type, capacity, and population pattern with the HPE QuickSpecs and maintenance guide. Firmware updates may improve compatibility, but they do not make every mixed or unsupported combination valid. If errors remain, test modules individually or in a known-good matched set.

Successful memory expansion in the DL360 Gen10 starts with the channel layout, not simply the amount of RAM you want to install. Populate one module in every available channel first, keep RDIMM and LRDIMM technology separate, and account for the processor's memory limits. After installation, verify every slot through HPE iLO 5, the system utilities, and the relevant HPE documentation. A balanced, qualified configuration gives you the best combination of capacity, bandwidth, stability, and future upgrade flexibility.