A regional hospital wants a rack server that is managed only from CIMC today to receive a service profile from the existing UCS Manager domain. What does that design require?
Select an answer to reveal the explanation.
Short Explanation
The server has its own front desk, and the hospital wants it on the main building's directory. You integrate the rack server with the fabric interconnects so UCS Manager can discover it and assign a service profile. A cloud claim that leaves the server off those interconnects does not create that UCS Manager profile.
Full Explanation
UCS Manager service profiles are objects in a fabric interconnect domain. A rack server that is opened only through CIMC is standalone, and CIMC cannot host a UCS Manager service profile. The hospital design requires the rack server to be cabled to and discovered by the fabric interconnects so the domain can associate a profile to it. Claiming the same server in Intersight, while leaving it off the interconnects, registers it with a different management plane. That claim does not create a profile inside the existing UCS Manager domain. A WWNN pool supplies Fibre Channel node names to vHBAs that already belong to a profile. Putting a BIOS identity in that pool does not convert a CIMC session into a service profile. NPV is a Fibre Channel mode that keeps an edge from taking a domain ID. It does not push a service profile onto a standalone rack server. Caveat: once the server is integrated, local CIMC management gives way to the domain, so the cutover should be planned before the profile is associated. Operational check: cable the server to the fabric interconnects, confirm UCS Manager discovers it, and associate a service profile from that domain rather than from the CIMC page.