You are in the process of upgrading your UCS M3 Server to a newer UCS M4 Server. You associate the Service Profile to the new UCS Server, but it fails to boot You suspect of a failed boot hard drive.

Question

Options

• AThe newer Cisco UCS M4 Server is using flash drives, not hard drives
• BThe newer Cisco UCS M4 Server is using disks of larger capacity than the previous UCS M3
• CA misconfiguration on the Service Profile Local Boot Policy
• DA misconfiguration on the Service Profile Local Disk Policy

• A
  80% (20)
• B
  4% (1)
• C
  4% (1)
• D
  12% (3)

Explanation

Option A is correct because Cisco UCS M4 servers use flash (SSD) drives rather than the spinning hard disk drives found in M3 servers. When you reassociate the Service Profile, the boot process fails because the hardware has fundamentally changed - the system is looking for HDDs that no longer exist, yet UCS Manager reports no RAID errors because the flash drives themselves aren't faulty; they're simply a different storage medium the existing configuration doesn't account for.

B is wrong because disk capacity differences don't block a server from booting - UCS handles varying capacities without issue. C is wrong because a Local Boot Policy misconfiguration would typically produce explicit boot order errors or different failure symptoms, not a silent hardware mismatch. D is wrong (and is the trickiest distractor) - while you may eventually need to update the Local Disk Policy, the root cause is the physical hardware difference between generations, not a policy error; the policy didn't break, the underlying hardware changed.

Memory tip: Link "M4 = More modern = Flash forward" - each UCS generation stepped toward flash-first storage, so any M3→M4 migration should prompt you to verify flash/SSD compatibility before associating the Service Profile.

No community discussion yet for this question.