If a server exposes only half its installed DDR5 DIMM capacity, check what the reported figure measures, whether the firmware recognizes every module, and which memory mode is active. When enabled on a platform that supports the exact configuration, full memory mirroring can account for a halving, but the ratio alone does not establish the cause. A receiving and acceptance record should distinguish the modules delivered from the total physical memory exposed to the operating system; neither is the same as memory currently available to applications.
1 Identify which capacity figure is lower
Build the RFQ around a complete order code such as MTC40F2046S1RC56BD1, rather than a description that says only DDR5 DIMM RAM. Keep the label information, quantity, and applicable documentation with that record. A catalog entry identifies a part for discussion; it does not establish qualification on a particular server, support for a memory mode, or compatibility with the modules already installed.
| Capacity measure | What to record | What it does not establish |
|---|---|---|
| Installed rated capacity | Module capacity and physical quantity | That the OS can use the entire sum |
| Firmware inventory | Recognized capacity and status by slot | That every recognized byte is exposed |
| OS-visible total memory | Physical memory made available to the OS | That it must equal the label sum |
| Runtime available memory | Memory available to applications at that time | The amount of hardware delivered |
The word available is particularly easy to misread. An operating-system inventory field can describe the total memory accessible to the OS, while a monitoring panel uses available for a changing runtime resource. Record the application, exact field name, unit, and collection time before comparing screenshots. Microsoft documents TotalVisibleMemorySize separately from FreePhysicalMemory; those properties answer different questions. A process limit or a virtual machine's assigned memory is also not a physical server inventory.
Normalize units before calculating a shortfall, and compare like fields from the same machine and configuration. Keep the original reports alongside any conversion. This avoids treating an application workload, a different reporting scope, or a display-unit difference as evidence that the supplier shipped fewer DIMMs.
2 Check mirroring against the exact platform configuration
Full memory mirroring maintains duplicate data for redundancy, reducing the capacity exposed for system use. Partial mirroring covers a selected range, so a blanket fifty-percent deduction is inappropriate. An ECC description on a DIMM does not show whether the server has enabled mirroring. Confirm the actual firmware setting and the platform documentation instead of inferring the mode from a label or a convenient ratio.
Support depends on the platform's documented conditions, including processor capability, module organization, supported options, and population. Do not transfer a slot diagram from another server or assume that every DDR5 RDIMM combination offers the same RAS features. OEM-specific option requirements also remain relevant: a manufacturer's generic module order code is not, by itself, proof of approval as an OEM option. No platform qualification is asserted for the example part in this article.
For a capacity illustration, assume a platform supports the chosen modules, population, and full-mirroring mode. Eight modules rated at 64 GB each total 512 GB of installed capacity. Mirroring that entire capacity gives a 256 GB capacity budget before other reservations and reporting differences. This arithmetic is not a recommended eight-module layout, a part-specific compatibility statement, or a promise that an OS will display exactly 256 GB.
A half-sized total is therefore a reason to check the configuration, rather than an automatic pass or failure. If firmware does not recognize the expected modules, investigate those unrecognized modules separately. Mirroring cannot be used as a general explanation for a module that is absent from the inventory or disabled following an error.
3 Define capacity acceptance before placing the order
A request for 512 GB of server memory leaves a material question unanswered: does the buyer mean the installed module total, or the OS-visible total under the required memory mode? Put that distinction in the RFQ before comparing quotations. Otherwise, two quotations can describe different deliverables even when both list the same installed capacity.
Record the server or board model, processor configuration, relevant firmware version, proposed module list, and intended population. Use the DIMM upgrade quantity and population guide to organize the quantity discussion, then document the capacity effect of the selected memory mode separately. Module count and OS-visible capacity should not be treated as interchangeable purchasing requirements.
| Order item | Records to specify before acceptance |
|---|---|
| Delivered hardware | Complete order codes, quantity, labels, and permitted substitutions |
| Operating configuration | Exact platform, active memory mode, and applicable support documentation |
| Capacity requirement | Installed total, OS-visible total, reporting field, and explained reservations |
| Exception handling | Slot inventory, firmware events, investigation owner, and disposition terms |
Agree sample approval, batch release, and return conditions in writing rather than treating a general checklist as a supplier guarantee. Specify who confirms the system configuration and who resolves an unexplained difference. Any allowed reservation should have an explanation tied to the platform or OS; an arbitrary percentage tolerance can conceal a real discrepancy.
An acceptance clause can state that the order covers the named modules and quantity, while system capacity is checked on the named platform in the agreed memory mode. It should identify the report used, who confirms it, and what happens if the result differs. Leave an unconfirmed capacity target open for engineering confirmation rather than filling it from a catalog value. This is a suggested way to write the requirement, not a universal acceptance standard.
If the project requires a particular OS-visible capacity with mirroring retained, first work through the supported module and population options. Simply doubling an order may exceed the platform's limits or create an unsupported arrangement. Capacity planning belongs with the required redundancy policy and documented system limits, before a volume commitment.
4 Investigate the evidence before replacing modules
During receiving inspection, preserve the initial configuration and reports before making changes. Compare physical quantities with firmware inventory, confirm the active memory mode, and then examine the OS-visible total. If labels and software reports identify different parts, use the DIMM label, SPD, and system-report checks to resolve identity separately from capacity. A successful identification check does not itself establish system compatibility.
When an expected DIMM is not recognized, memory is disabled, or firmware records an error, follow the diagnostic procedure for that exact platform. Preserve the slot identifiers and events for the investigation. Do not declare a particular DIMM defective, genuine, or counterfeit from the capacity ratio alone. Equally, an unexplained shortfall should not be signed off merely because mirroring is a possible explanation.
When comparing pre-delivery and receiving reports, check that the processor configuration, firmware, and population are unchanged. If they differ, document the difference before interpreting the capacity change. A comparison between different machines or operating modes does not isolate the DIMM as the cause.
Assess conformity with the order after confirming the identities of the delivered modules, the reporting scope, and the operating conditions. Disabling mirroring changes the redundancy policy. Have the project owner approve any such change and follow the platform's maintenance procedure; increasing a displayed number is not sufficient reason to remove a required protection. Retain the revised configuration and capacity evidence with the acceptance record.
For this DIMM requirement, include the complete order code, installed quantity, intended memory mode, and required OS-visible capacity in the BOM notes. Check candidate modules against platform support documentation, population requirements, and the agreed capacity acceptance method. For a SUNTEC quotation, send those details with the purchase quantity and requested delivery date so the hardware being quoted is clearly defined.
Prepared by the SUNTEC Technical Team at Suzhou SUNTEC Electronics Co., Ltd.