Server profiles

Server profiles are generated automatically when a server pattern is deployed. One profile is created for each target compute node. Each server profile represents the specific configuration of a single compute node and contains system-unique information (for example, assigned IP addresses and MAC addresses).

System profile management

When a pattern is deployed, an individual system profile is generated for each target system. You can edit a pattern and save changes, and any dependent system profiles are automatically updated and redeployed to their associated systems. You can move an existing profile from one system to another by unassigning the profile, and then redeploying the profile to another system.

Important: Systems retain their identification information (for example, hostname, IP address, virtual MAC address) when a profile is unassigned. To avoid name and address conflicts, any identification information on the original system should be cleared before the unassigned profile is deployed to a different system.

Server profiles

Each server profile represents the specific configuration of a single compute node and contains information that is unique to a compute node. The server profile is activated as part of the IMM startup process. Once a server profile is activated for a compute node, any subsequent configuration changes are done by editing the appropriate server pattern or category pattern associated with the profile. This enables you to control a common configuration pattern from a single place.

If a compute node needs to be moved or re-purposed, you can reassign a server profile from one compute node to another.

You can deploy a server pattern to a compute node or to an empty chassis bay. In either case, the profile is associated with the chassis bay. If you replace an existing compute node, you must redeploy the server profile associated with that bay to activate the profile on the new compute node. If you first deploy a server pattern to an empty bay, then you must redeploy the server profile associated with that bay after a compute node is installed.

Note: To ensure that your configuration patterns are not lost if the management node fails, back up the management software after you create or modify configuration patterns.