Working with server profiles

A server profile is an instance of a server pattern that is applied to a specific server. Server profiles are generated and assigned automatically when a server pattern is deployed to one or more servers. One server profile is created for each target server. Each server profile contains the specific configuration for a single server and contains information (such as assigned name, IP addresses, and MAC addresses) that is unique for that specific server.

About this task

The server profile is activated during the baseboard-management-controller startup process. You can choose to:

Reboot the server when the pattern is deployed to activate the server profile immediately
Defer activation until the next reboot.
Defer activation until you manually activate the server profile.

Multiple server profiles can inherit from a single server pattern. After a server pattern is deployed to one or more servers, you can quickly deploy configuration changes to multiple servers by editing the parent server pattern and category patterns. The dependant server profiles are automatically updated and redeployed to their associated servers. By editing the server pattern, you can control a common configuration from a single place.

If you replace an existing server or if you install a pre-provisioned server in an empty bay in a chassis, you must activate the server profile for that new server to provision the configuration changes on the new server.

Note

You can deploy a server pattern to multiple servers; however, multiple patterns cannot be deployed to a single server.

You can change the server profile that is associated with a server in several ways, depending on the reason for the change.

If you want to move or repurpose a server:
1. Deactivate the current server profile on the current server (see Deactivating a server profile).
2. Deploy the new server pattern to the new server (see Deploying a server pattern to a server).
If a server failed and you want to use a spare server in its place:
1. Deactivate the current server profile on the failed server (see Deactivating a server profile).
2. Activate the same server profile on the spare server (see Activating a server profile).
3. When the failed server is fixed, you can repeat these steps to switch the profile again.
If a server failed and you want to replace the hardware:
1. Deactivate the current server profile on the failed server (see Deactivating a server profile).
2. Replace the failed server.
3. Activate the same server profile on the new server (see Activating a server profile).

Important

When using address virtualization, a server retains its assigned virtual MAC or WWN address until it is powered down. When deactivating a profile that has address virtualization enabled, the Power off the server checkbox is selected by default. Ensure that the original server is powered off before you activate the inactive profile on a different server to avoid address conflicts.
If you delete a profile that is not the most recently created, the virtual MAC and WWN addresses are not released from the address pool. For more information, see Deleting a server profile.
The settings on a server can become out of compliance with its server profile if settings were changed without using configuration patterns, if an issue occurred when applying a configuration pattern (for example, if the pattern was created from an earlier firmware level than what is on the server), or when applying a firmware update that changed the server configuration (for example, settings might be added or deleted, setting behaviors might change, new choices might be added, or value ranges might change).

Give documentation feedback