My servers passed EMC testing as single units, so why do they still cause interference when installed together in a customer rack?

The real pain point

A rack-mount server passes radiated emission limits under CISPR 32 and conducted emission under FCC Part 15. The test report says compliant. Yet once the units ship to a customer datacenter and dozens are stacked in one cabinet, sharing a single PDU and one grounding busbar under full load, the IT team starts logging errors: link bit errors, storage packet loss, dropped out-of-band management links. One unit passed; the whole rack fails. Is the hardware defective, or did the test simply not cover how the product is actually deployed?

Key judgment: a single-unit pass is not rack compatibility

EMC testing, by its nature, evaluates one sample unit in a standardized test environment against standardized pass/fail criteria. Three premises are easy to overlook:

• The object is a single unit. Standards assume one independent sample, placed in an anechoic chamber or open-area test site with prescribed grounding and power arrangement. They do not simulate a customer topology of twenty identical units in one cabinet.
• Radiation adds as vectors. Multiple identical devices working side by side do not simply sum their emissions, but field strength scales roughly with the square root of the unit count. A single unit 6 dB under the limit can sit right at or above it when twenty are stacked together.
• The criterion covers the sample configuration, not your topology. The lab only demonstrates that this sample, in this configuration, meets the limit. It does not promise zero interference under any grounding scheme or cabling method.

Three field variables a single-unit test usually misses

Common pitfalls

• Treating CE/FCC passed as works anywhere. Compliance is the entry ticket, not a guarantee of rack-level quiet.
• Blaming single-unit rework when the rack fails. If the unit report is clean, the cause is often the rack power, grounding, and cabling discipline, not the hardware.
• Leaving rack compatibility ownership undefined in the contract. Standards do not mandate rack-level testing, so undefined ownership leads to disputes.

Conclusion

Single-unit EMC compliance is only the starting line for export. If your servers, storage, or datacenter power modules are going into production racks at scale, treat rack-level EMC pre-compliance assessment as a separate validation item. Evaluate it against the real deployment topology, cabinet count, power distribution, grounding scheme, and wireless management layout, early, and write the pass/fail boundaries into the technical agreement rather than waiting for a customer datacenter to surface the problem.