A media company already uses CIMC for virtual KVM on a standalone C-series server. They now want a UCS Manager service profile and vNIC templates to own that server. What does that management model require?
Select an answer to reveal the explanation.
Short Explanation
CIMC is the local workshop, and a service profile is a work order from the domain. You integrate this rack server with a fabric interconnect before UCS Manager can assign that profile and its vNIC templates. A second management address does not create the profile.
Full Explanation
CIMC on a standalone C-series provides local KVM, virtual media, and BIOS settings for that server. A UCS Manager service profile, including vNIC templates, exists only in a fabric interconnect domain. The media company has to integrate the rack server with a fabric interconnect before UCS Manager can own it with a service profile. A second CIMC address is just another way to reach the same controller. It does not create service profiles. An MDS zoneset controls Fibre Channel communication. It does not install Ethernet vNIC templates on a server. Guest shell is an on-box Linux environment on Nexus switches. It does not push UCS service profiles into CIMC. Caveat: claiming the same standalone server in Intersight is a different management path and still does not create a UCS Manager service profile on a fabric interconnect that was never installed. Operational check: after the server is integrated and discovered, confirm it appears under the fabric interconnect and associate a test service profile rather than opening CIMC for that policy.