A SaaS platform created Intersight server profiles for UCS X-series nodes, and the profiles do not associate. 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 opening, and the server profiles are desk assignments. You deploy the domain profile first so the fabric interconnects have port, VLAN, and VSAN policy and the nodes can accept a server profile. A full-state file from UCS Manager mode is a different management system than the one this platform is using.
Full Explanation
In Intersight Managed Mode a domain profile programs the fabric interconnects: ports, VLANs, VSANs, and the rest of the domain policy. Server profiles associate to discovered nodes in that domain. With no domain profile deployed, the interconnects are not set up for those nodes, so the SaaS server profiles have nothing ready to associate to. Deploying the domain profile is the step that has to happen first. A UCS Manager full-state backup is a binary snapshot from UCS Manager mode. Intersight Managed Mode does not use that file as the way it stores X-series profiles. Grid is a chassis power redundancy choice in UCS Manager domains. It is not the management plane, and it does not associate Intersight server profiles. An MDS zoneset controls Fibre Channel communication between logged-in devices. Server profile association does not wait on a zone, and zoning the array later will not deploy the domain. Caveat: after the domain profile deploys, the chassis still has to be discovered and the server profile still has to be associated to a specific node. Operational check: deploy the domain profile, confirm the interconnects show the port and VLAN policy, and then associate one server profile to a discovered node.