A logistics Windows host must list server profiles for a UCS X domain that runs only in Intersight Managed Mode. UCS Manager is not running on those fabric interconnects. Which automation path can list the profiles?
Select an answer to reveal the explanation.
Short Explanation
You are knocking on a ticket window that this building boarded up. Intersight Managed Mode has no UCS Manager, so a PowerTool session aimed at the fabric interconnect cannot list those profiles. The Intersight PowerShell module talks to the Intersight account that holds them.
Full Explanation
PowerShell automation follows the management plane that actually owns the servers. For this domain that plane is Intersight, and the Intersight PowerShell module opens a session to that account and can list server profiles. UCS Manager PowerTool speaks to UCS Manager on a fabric interconnect. There is no UCS Manager on an Intersight Managed Mode pair, so that session has nothing to query. The on-box Python cli module runs show commands inside NX-OS. It does not read Intersight server profiles. A Terraform plan evaluates desired state against a state file. By itself it does not log in and list live Intersight profiles. Caveat: the Intersight account and role still have to be allowed to see that organization, or the module returns an empty view of a profile that exists. Operational check: connect the Intersight module and list the server profile by name before you try the fabric interconnect address. If the same Windows host also automates an older UCS Manager domain, keep that PowerTool session pointed at the older pair and do not reuse it for this Intersight domain.