Firmware Groups
Location in GUI: Admin » Firmware » Nodes
Diagram
Section titled “Diagram”Classes
Section titled “Classes”node_policies (apic)
Section titled “node_policies (apic)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| update_groups | List | [update_groups] | No |
nodes (apic.node_policies)
Section titled “nodes (apic.node_policies)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| update_group | String | Regex: ^[a-zA-Z0-9_.:-]{1,64}$ | No |
update_groups (apic.node_policies)
Section titled “update_groups (apic.node_policies)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[a-zA-Z0-9_.:-]{1,64}$ | Yes | |
| scheduler | String | Regex: ^[a-zA-Z0-9_.:-]{1,64}$ | No | default |
| target_version | String | Regex: n\d+-\d+\.\d+\(\w+\) | No |
Examples
Section titled “Examples”Example-1: this example demonstrates a basic update group MG1, where node 101 is associated to the relevant group.
apic: node_policies: update_groups: - name: MG1 nodes: - id: 101 update_group: MG1Example-2: this example demonstrates a typical ACI deployment setup, with the ODD_NODES group for odd nodes, and the EVEN_NODES group for even nodes. Assuming all devices connected to ACI are dual-homed for redundancy, this enables the ACI fabric to upgrade with minimal to no service interruption. The upgrade groups also define the target_version attribute to specify the firwmare image of n6-0.9(e), meaning APIC release 6.0(9e).
apic: node_policies: update_groups: - name: ODD_NODES target_version: n6-0.9(e) - name: EVEN_NODES target_version: n6-0.9(e) nodes: - id: 201 role: leaf update_group: ODD_NODES - id: 202 role: leaf update_group: EVEN_NODES