Question 370
A data center administrator identifies the following risk: A blade replacement is delayed because the team assumes MAC addresses and server identities must remain bound to the failed physical blade. What preventive control would best avoid repeating this fault?
Explanation
Correct Answer
This safeguard addresses ucs service profile server identity: The server identity has not been abstracted through approved UCS service profile and identity-pool associations. The appropriate prevention is: Maintain service profile templates and identity pools independent of individual server serial numbers. Other subsystem controls would not address the specified recurring failure.
Incorrect Answers
The vHBA WWPN allocation violates uniqueness requirements across server storage initiators. “Audit WWPN pool ranges and identity assignment for uniqueness before UCS service profile deployment” would address that alternative cause, not the condition in this question: the server identity has not been abstracted through approved UCS service profile and identity-pool associations.
“Validate failover semantics against the host operating system teaming configuration before production use” responds to this separate finding: the UCS vNIC fabric placement and failover policy do not provide the intended redundant network path. This question instead needs “Maintain service profile templates and identity pools independent of individual server serial numbers”, so the alternative does not meet the stated condition.
The virtual HBA path is not participating in the intended Fibre Channel VSAN end to end. “Check UCS vHBA VSAN mapping and the upstream storage fabric when provisioning SAN boot” applies to that separate problem. The observed case is a blade replacement is delayed because the team assumes MAC addresses and server identities must remain bound to the failed physical blade; choosing this alternative would address the wrong failure mode.