Question 390
A Nexus, UCS or MDS operations team encounters this issue: A UCS rack server remains pingable but begins memory error correction bursts, while monitoring checks only network availability and misses hardware faults. Which corrective change best resolves this problem?
Explanation
Correct Answer
The root problem is that The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. The selected change addresses it directly: Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend. Verify the outcome: Intersight records the hardware fault and resolution, while workload stability returns after repair.
Incorrect Answers
This action concerns ucs updating service profile templates, where The configuration process bypasses the intended reusable UCS service profile template inheritance model. The reported failure instead stems from The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history.
This action concerns ucs bios virtualization extensions, where The BIOS policy disables required CPU virtualization support expected by the approved hypervisor. The corrective response here is “Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend”; this alternative does not provide that response.
This action concerns ucs c series virtual disk raid policy, where The server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy. The stem reports a UCS rack server remains pingable but begins memory error correction bursts, while monitoring checks only network availability and misses hardware faults; this control addresses a different failure condition.