A media company has a standalone UCS C-series server and no fabric interconnects. They want that server in the Intersight inventory so its firmware is visible. What achieves the claim?
Select an answer to reveal the explanation.
Short Explanation
A standalone rack server can introduce itself to Intersight without joining a UCS domain. You claim it from the CIMC device connector, and no fabric interconnect is required for that inventory and firmware view. A SAN login or NPV mode does not register the server with Intersight.
Full Explanation
A standalone C-series server keeps its own CIMC, and CIMC includes the Intersight device connector. Claiming the server from that connector adds it to the Intersight account for inventory and firmware visibility. Fabric interconnects are not part of that path, which matters here because the media company does not have any. Intersight is not limited to servers that UCS Manager has already discovered. A fabric interconnect pair would create a UCS domain, and it is not a prerequisite for claiming this rack server. The Fibre Channel name server lists WWPNs that have logged into a SAN. A rack server can be claimed with no HBA at all, and an MDS entry does not create an Intersight device. NPV is a Fibre Channel edge mode so a switch does not take a domain ID. It does not publish servers to Intersight. Caveat: the device connector has to be able to reach the Intersight service, or the claim stays pending even though CIMC itself is up. Operational check: start the claim from CIMC, confirm the server appears in the Intersight inventory, and confirm the firmware shown there matches the server.