Deploying Partition Templates in HMC

Managing multiple IBM POWER systems can be time-consuming and error prone when every deployment is done manually. The Hardware Management Console (HMC) Enhanced UI simplifies and standardizes system provisioning through System Templates and Partition Templates.

HMC (Hardware Management Console):

Centralized management interface for IBM Power servers.

Functions:

• Creates, configures, and manages logical partitions (LPARs) and VIOS partitions.
• Monitors system health, events, and firmware updates.
• Connects to the Managed Host over a Management Network (TCP/IP).
• UI: Provides both graphical (GUI) and command-line (CLI) tools.

Managed System (Power Server):

This is the physical Power system that houses processors, memory, and network adapters. It’s managed by the HMC and partitioned into multiple LPARs (logical systems).

Physical NICs:

SR-IOV Adapters: Allow direct assignment of virtual NICs to LPARs for high performance.

HEA (Host Ethernet Adapter): Firmware-level virtual adapter that provides network connectivity to LPARs through firmware virtualization.

Dedicated Physical I/O: Entire network or storage adapters can be assigned to a single partition.

CPU / Memory:

LMBs (Logical Memory Blocks): Basic unit of memory allocation to partitions.

Shared Processor Pools: Allow dynamic CPU sharing among partitions.

Dedicated Processors: Assigned exclusively to one LPAR.

VIOS (Virtual I/O Server) Partitions:

VIOS partitions act as intermediaries between the physical hardware and client LPARs. They virtualize network and storage I/O, allowing client partitions to share physical resources.

Virtual Network:

Virtual Ethernet Adapters: Internal network interfaces connecting client LPARs through the PowerVM hypervisor.

Link Aggregation (EtherChannel): Combines multiple physical NICs for redundancy and bandwidth.

SEA (Shared Ethernet Adapter): Bridges the virtual Ethernet (from clients) to the physical network, enabling external connectivity.

Virtual Storage:

Virtual SCSI (vSCSI): Exports physical disks or SAN LUNs from VIOS to client LPARs.

Shared Storage Pools (SSP): Pool of storage shared among multiple systems for flexible allocation.

NPIV (N-Port ID Virtualization): Allows client LPARs to have direct Fibre Channel (SAN) access via virtual WWPNs through VIOS.

Type of Template:

System Template — a blueprint for a managed system + its VIOS partitions. Includes processor pools, Logical Memory Blocks (LMBs), physical I/O capture, VIOS definitions, virtual network and storage settings.

Partition Template — a blueprint for client partitions (AIX, Linux, IBM i): CPU, memory, vNICs, vSCSI, and IPL parameters.

Starter templates — built into HMC; convenient base templates (read‑only). You can copy them to create editable user templates.

User‑captured templates — capture a working system or partition to reproduce identical configurations on other hardware.

Benefits: consistency across environments, faster deployments, fewer manual errors, documented configurations for dev/test/prod.

You can launch the wizard from two places:
Template Library (HMC Management → Templates and OS Images → System Template) — right‑click a template → Deploy.
All Systems View — select an existing managed system → Action → View All Actions → Deploy System From Template.

The wizard runs through four stages:
System Configuration — CPU, LMBs, physical I/O mapping, VIOS creation.
VIOS Installation — Install VIOS via NIM, From HMC or Local NIM.
Virtual Network Configuration — Create bridges, link aggregation, assign IPs.
Virtual Storage Configuration — Assign VIOS to clusters, Create device pools and media repositories.

The Deploy System Template wizard

You can launch the wizard from two places:

1. Template Library (HMC Management → Templates and OS Images → System Template) — right‑click a template → Deploy.
2. All Systems View — select an existing managed system → Action → View All Actions → Deploy System From Template.

The wizard runs through four stages:

1. System Configuration — CPU, LMBs, physical I/O mapping, VIOS creation.
2. VIOS Installation — install VIOS via NIM, Local MC, or Local NIM.
3. Virtual Network Configuration — create bridges, link aggregation, assign IPs.
4. Virtual Storage Configuration — assign VIOS to clusters, create device pools and media repositories.

Create, copy, or import templates:

1. Open HMC Management → Templates and OS Images → Template Library.
2. Choose the System Template or Partition Template tab.
3. To create an editable template from a starter: right‑click a starter template → Copy → give it a descriptive name (e.g., vios-sriov-template, webserver-prod-v1).
4. To capture an existing system: use the Capture function on a managed system or partition to create a user template.
5. Edit the copied or captured template: adjust CPU pools, LMB sizes, virtual network definitions, virtual storage configuration, SR‑IOV/HEA settings, and IPL parameters. Save with a version name (e.g., v1.0‑prod).
6. Export / Import if you need to transfer templates between HMCs.

Tip: maintain named versions for different environments (dev/test/prod) and include a short description of intended hardware families and compatibility notes.

Stage 1 — System Configuration (detailed)
Validate before you start. Use the wizard’s Reset or validation checks to ensure the target system is compatible. Be aware that starting the workflow may delete existing LPARs or VIOS on the target—take backups.
1. Select Template — pick your prepared system template.
2. Select Target System — choose the managed host to configure. Click Reset to re‑validate current partitions and adapters.
3. Captured I/O option:

Enabled: the template’s physical I/O mapping is applied verbatim. Fast but prone to Hardware Mismatch errors if target server hardware differs.
Disabled: manually map adapters to template VIOS definitions so you can adapt to differing hardware.
4. SR‑IOV Adapter settings:
If captured I/O is enabled, SR‑IOV mappings are read‑only.
If disabled, you may select physical ports, set speeds/duplex, create logical SR‑IOV ports and map them to VIOS.
Note: HMC may default to shared mode for SR‑IOV ports — change to dedicated only if your hardware and use case require it.
5. VIOS Configuration Summary — review VIOS names and key settings. Only the VIOS name is changeable at this point.
6. Physical I/O Mapping — map physical adapters (including SR‑IOV logical ports and HEA ports) to the VIOS definitions in the template.
7. Start System Configuration — click Start. HMC creates partitions, assigns CPU/memory (LMB), and configures basic VIOS objects.

Failure modes: if the wizard cannot obtain adapter information the process halts with "Unable to obtain network adapter information". Fix adapter assignments or finish VIOS setup manually.

Stage 2 — VIOS Installation

1. Choose installation method: NIM, Local MC, or Local NIM. NIM is common for automated network installs.
2. NIM server parameters (if using NIM): NIM server IP, network port, target VIOS IP, netmask, and gateway.
3. Start Installation — click Start and monitor progress in the wizard.
4. After install completes, check Accept License and continue.

Troubleshooting: If install fails, verify network connectivity to the NIM server, correct image selection, and that routing/firewall rules permit access.

Stage 3 — Virtual Network Configuration

1. Configure a network bridge for each VIOS by selecting assigned network interface(s).
2. Optionally enable Link Aggregation — Choose Create Link Aggregation Device and add member NICs.
3. Assign IPs to VIOS if required by the chosen installation method.
4. Click Start to apply network configuration and watch the progress.

Note: the wizard requires a suitable adapter assigned to each VIOS. If none is available, the wizard won’t progress.

Stage 4 — Virtual Storage Configuration

1. Assign VIOS to a cluster (optional) or choose Do not assign now.
2. Create / Reserve a Device Pool if needed for dedicated virtual disk provisioning.
3. Configure the media repository for storing virtual images and vSCSI mappings.
4. Click Start and monitor the wizard for I/O creation and device assignment messages.

Post‑deploy validation checklist:

• Confirm logical partitions exist and match the template (CPU, LMB, storage).
• Validate each VIOS boots correctly and that bridges and vNICs are present.
• From the HMC, verify assigned physical adapters and SR‑IOV logical ports are mapped to the expected VIOS.
• Check device pools and media repository accessibility for virtual storage.
• Apply any OS updates, firmware patches, and HMC updates as necessary.

Deploy a VIOS with SR‑IOV logical ports:

1. Copy a starter System Template and name it vios-sriov-template.
2. Edit the template: enable 1 VIOS, add 4 SR‑IOV logical ports under the VIOS → Physical I/O tab.
3. Save and export to the target HMC if you operate multiple HMCs.
4. From All Systems view → Select System → Action → Deploy System From Template → choose vios-sriov-template.
5. On Physical IO mapping: map the correct physical port(s) to the SR‑IOV logical ports and pick shared/dedicated mode.
6. Proceed with VIOS install (NIM) and configure network bridge + storage.

Checklist before Start: backups, template version, adapter mapping, NIM accessibility, firmware and HMC compatibility.