A regional hospital built Intersight server profiles for a new UCS X-series domain. Deployment fails because no domain profile has been deployed to the fabric interconnects. What has to happen first?
Select an answer to reveal the explanation.
Short Explanation
The domain profile is the building permit. You deploy it to the fabric interconnects before the server profiles have ports, VLANs, and VSANs to stand on. CIMC on a single node is not the front door for this X-series domain.
Full Explanation
In Intersight Managed Mode the domain profile carries the fabric interconnect personality: port roles, VLANs, VSANs, and the other domain policies. Server profiles for the X-series nodes depend on that personality. Deploying server profiles first, with no domain profile on the interconnects, fails because the domain has not been told what it is. CIMC is the local controller on a standalone rack server. It is not how you push an Intersight server profile onto X-series nodes in a managed domain. Ethernet switching mode is a forwarding behavior of a fabric interconnect toward the LAN. It does not accept or deploy Intersight profiles. A UCS Manager full-state backup restores a UCS Manager domain. It is not an Intersight domain profile and it does not deploy one. Caveat: the interconnects also have to be claimed and actually running in Intersight Managed Mode, or there is no domain for the profile to land on. Operational check: deploy the domain profile, wait until the interconnects report it deployed, and only then deploy one server profile to a compute node.