A media company wants Intersight inventory and virtual KVM for a standalone UCS C-series rack server, and no fabric interconnects are installed. How should that server be brought into Intersight?
Select an answer to reveal the explanation.
Short Explanation
A standalone rack server can still have a cloud landlord. You claim it from the CIMC device connector so Intersight can inventory it and open KVM without a fabric interconnect. Building a UCS Manager cluster is a different project than this media company described.
Full Explanation
A C-series server that is not attached to fabric interconnects still runs CIMC, and CIMC includes a device connector that can claim the server into Intersight. Once claimed, Intersight can show inventory and open the virtual KVM for that standalone server. No fabric interconnect domain is required for this path, which matches the media company. UCS Manager exists only on a fabric interconnect cluster. Intersight can see a claimed standalone rack server without that cluster, so building fabric interconnects is not the step this request is asking for. An MDS management address configures Fibre Channel switching. It does not claim a rack server into Intersight, and the server is not a storage array target. A VIC is the server adapter that presents interfaces to the host. It is not converted into a fabric extender, and a fabric extender is not how a standalone rack server reaches Intersight. Caveat: a later move into a fabric interconnect domain changes the management path, and the same server should not be fought over by two management models. Operational check: confirm the device connector shows the claim, then open KVM from Intersight and match the serial to this rack server.