When calling UCS instantiate-from-template, how must the script address the template and destination org?
Select an answer to reveal the explanation.
Short Explanation
UCS methods want the full street address—org-root/ls-name style DNs—not the nickname on the mailbox.
Full Explanation
UCS instantiate-from-template addressing uses distinguished names: the template dn and inTargetOrg in org-…/ls-… form (and related DN paths), not bare GUI labels. The XML/SDK methods resolve managed objects by DN under the org tree, so municipal scripts must pass the full address the fabric understands.
Using only the friendly GUI label without an org-…/ls-… DN path fails when duplicate display names exist across orgs or when the API requires the DN field specifically. Addressing objects with Intersight Moids on the UCS Manager XML endpoint fails because Moids are Intersight identifiers and are not valid UCS Manager DN arguments. Targeting the fabric-interconnect CLI hostname instead of org and template DNs fails by confusing management reachability with managed-object addressing inside the UCS information model.
Exam caveat: DN strings are brittle—trailing segments, org nesting, and ls- versus org- prefixes must match exactly; a one-character typo often surfaces as “not found” rather than a clear auth error.
Operational check: resolve the template and target org by DN immediately before instantiate, print both DNs in the job transcript, and reject the run if either resolve returns empty so the city never instantiates against an ambiguous friendly name.