Domain Profile
IntersightA Domain Profile binds a set of fabric policies to a physical UCS Domain (Fabric Interconnect pair), identified by the serial numbers of the two FIs. It can be created standalone with direct policy assignments, or derived from a Domain Template which pre-wires the policies.
Location in Intersight GUI:
Profiles » UCS Domain Profiles
Diagram
Section titled “Diagram”Classes
Section titled “Classes”compute
Section titled “compute”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| intersight | Class | intersight | No |
intersight (compute)
Section titled “intersight (compute)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| organizations | List | organizations | No |
organizations (compute.intersight)
Section titled “organizations (compute.intersight)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| profiles | Class | profiles | No |
profiles (compute.intersight.organizations)
Section titled “profiles (compute.intersight.organizations)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| domain | List | domain | No |
domain (compute.intersight.organizations.profiles)
Section titled “domain (compute.intersight.organizations.profiles)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[a-zA-Z0-9_ | Yes | |
| description | String | No | ||
| managed | Boolean | true, false | No | true |
| tags | List | tags | No | |
| target_platform | Choice | UCS Domain, Unified Edge | No | UCS Domain |
| action | Choice | none, sync, deploy, sync_and_deploy, unassign | No | none |
| serial_numbers | List | String | No | |
| ucs_ | String | No | ||
| switch_ | String | No | ||
| switch_ | String | No | ||
| switch_ | String | No | ||
| system_ | String | No | ||
| vlan_policy | String | No | ||
| vsan_policy | String | No | ||
| ntp_policy | String | No | ||
| snmp_policy | String | No | ||
| syslog_policy | String | No | ||
| network_ | String | No | ||
| ldap_policy | String | No |
tags (compute.intersight.organizations.profiles.domain)
Section titled “tags (compute.intersight.organizations.profiles.domain)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| key | String | Yes | ||
| value | String | No | ||
| type | Choice | KeyValue, PathTag | No |
Action Attribute
Section titled “Action Attribute”The action attribute controls what Terraform does beyond creating and assigning the domain profile. It applies at the cluster level and cascades to both Fabric Interconnects.
Every domain profile with a ucs_domain_template is created from its template’s current policies, whatever the action value. This matches deriving a profile from a template in the Intersight GUI. Changing ucs_domain_template derives the profile again from the new template.
After that, action decides whether Terraform picks up later template changes and whether it deploys to hardware. With none or deploy, later template changes are not pulled in, and the profile shows as Out-of-Sync in Intersight with no Terraform plan diff.
action has five values:
| Value | Picks up later template changes | Deploys to hardware | Safe to leave permanently |
|---|---|---|---|
none (default) | No | No | Yes |
sync | Yes, on every apply | No | No — set temporarily |
deploy | No | Once, when created, template changed, or action set to deploy | Yes |
sync_and_deploy | Yes, on every apply | Yes, on every apply | No — maintenance window only |
unassign | No | Detaches both switch profiles from their Fabric Interconnects | No — set temporarily |
The template-related columns only apply when the profile has a ucs_domain_template. Both switch profiles follow the domain template’s switch templates.
none — Terraform creates the domain profile from its template and assigns the switch profiles to the FI pair, then stops. No configuration is pushed to hardware. Use this to stage profiles for operator review before committing.
sync — Terraform syncs the profile with its template on every apply, so it picks up template changes. No hardware interaction occurs. Use it temporarily: set sync, apply, review the changes on the profile in Intersight, then set action back. While sync is set, every terraform plan shows the sync as a pending change.
deploy — Terraform deploys the current profile state to both Fabric Interconnects. It does not automatically pull in template changes — if the template was updated and the profile is Out-of-Sync, the existing profile configuration is deployed as-is. Safe to leave permanently because Terraform only deploys when the profile is created, its template changes, or action is changed to deploy; not on later applies or when the template contents change.
sync_and_deploy — Terraform first syncs the profile with the latest template, then deploys to both FIs. This is the only value that automatically propagates template changes to the physical domain. While it is set, every terraform plan shows a pending sync and deploy. Use only during a declared maintenance window — VLAN, port, or switch control policy changes can disrupt fabric traffic across the domain.
unassign — Terraform sends an explicit Unassign command to both switch profiles, detaching them from their Fabric Interconnects. action has no one-shot marker for this value — it is sent on every apply where it is set at the cluster level, cascading to both switch profiles, so set it, apply, then set action back to none (or remove the attribute); leaving unassign set has no further effect beyond the first apply, since Intersight’s unassign is idempotent, but it is still not a standing configuration to leave in place. See the warning below before using this: in most cases, removing the domain profile’s entry from the data model entirely (so Terraform destroys both switch profiles) is the better path, since destroy now also waits for the same Unassign workflow.
Warning: Commenting out or removing entries from
serial_numbersdoes not unassign the switch profiles in Intersight.assigned_switchis a provider-managed (optional + computed) attribute — when its underlying config block disappears, Terraform has no opinion on it and simply keeps the provider’s last-known value, so no detach is ever sent. The GUI continues to show the switch profiles bound to their original Fabric Interconnects even thoughterraform applysucceeds cleanly. To actually detach the hardware, either setaction: unassign(above) or remove the domain profile’s entire entry so Terraform destroys both switch profiles (destroy now waits for the Unassign workflow, since this module setswait_for_completion = trueon both switch profile resources).
Note: After an apply that syncs a profile with its template, the next
terraform planshowsWarning: BulkMoMerger object <moid> not found. Removing from statefile. Intersight deletes the sync request once it has run, and Terraform drops it from state. Nothing on the profile or hardware is affected. Withnoneordeploy, the plan still reports no changes and the warning appears once. Withsyncorsync_and_deploy, it appears after every apply, alongside the pending sync.
Reboot warning:
deployandsync_and_deploycan trigger a Fabric Interconnect reboot or a brief fabric-wide disruption if the profile includes port or switch control policy changes. Verify the assigned policies before runningterraform applywith either of these values.
Note:
wait_for_completionis not supported for domain profiles.terraform applyalways waits until the switch profile workflows have finished afterdeploy,sync_and_deploy, orunassign, which can take several minutes. Destroying a domain profile waits for the Unassign workflow in the same way. The deploy is sent through a second resource for each switch profile, so each switch profile also appears underdomain_switch_profile_deployin the Terraform state.
Examples
Section titled “Examples”Example-1: Domain profile derived from a template, assigned to a physical FI pair with environment tags.
compute: intersight: organizations: - name: MyOrg profiles: domain: - name: prod-ucs-01 description: Production UCS Domain ucs_domain_template: prod-domain-template serial_numbers: - FCH2344ABCD - FCH2344EFGH tags: - key: env value: prodExample-2: Standalone domain profile with direct policy assignments (no template).
compute: intersight: organizations: - name: MyOrg profiles: domain: - name: lab-ucs-01 switch_a_port_policy: lab-fi-a-ports switch_b_port_policy: lab-fi-b-ports switch_control_policy: lab-switch-control system_qos_policy: lab-qos vlan_policy: lab-vlans ntp_policy: global-ntp snmp_policy: global-snmp serial_numbers: - FDO2312ABCD - FDO2312EFGHExample-3: Maintenance window deployment — sync with the latest template and deploy to both FIs.
compute: intersight: organizations: - name: MyOrg profiles: domain: - name: prod-ucs-02 ucs_domain_template: prod-domain-template # Apply only during the declared change window — cascades to both FIs action: sync_and_deploy serial_numbers: - FCH2344IJKL - FCH2344MNOPExample-4: Detaching a domain profile from its Fabric Interconnect pair — set action: unassign, apply, then set action back to none (or remove it). Both switch profiles are detached; the profiles and the data model entry remain.
compute: intersight: organizations: - name: MyOrg profiles: domain: - name: prod-ucs-01 ucs_domain_template: prod-domain-template action: unassign serial_numbers: - FCH2344ABCD - FCH2344EFGH