configpatterns apply

This command applies (deploys) a server pattern to one or more managed servers. You can also deploy a server pattern to one or more empty bays in a chassis that is managed by Lenovo XClarity Administrator or in a placeholder chassis. Deploying a server pattern before the server is installed reserves management IP addresses, reserves virtual Ethernet or Fibre Channel addresses, and pushes the network setting to the relative switch internal ports.

Syntax

configpatterns apply  -h

configpatterns apply  {-i <pattern_ID> | -n <pattern_name>} -r <activation_time>
                       -e <server_UUIDs> -t <server_type> [-v <filter>]

Options

{-h | --help}
Displays the syntax and brief usage information for this command.
{-i | --id} <pattern_ID>
Specifies the ID of the server pattern. You must specify either the –id or –name parameter.
{-e | --endpoint} <server_UUID>
Specifies the UUIDs of one or more target servers. If a target is an empty bay, specify the location ID; otherwise, specify the server UUID.
{-n | --name} <pattern_name>
Specifies the name of the server pattern. You must specify either the –id or –name parameter..
{-r | --restart} <activation_time>
Identifies when to activate the configurations. This can be one of the following values:
  • defer. Activate management-controller settings but do not restart the server. UEFI and server settings are activated after the next restart of the server.
  • immediate. Activate all settings and restart the server immediately.
  • pending. Generate a profile for the server with the settings for review, but do not activate settings on the server. To activate the settings, you must manually activate the server profile and restart the server.
{-t | --type} <server_type>
Type of the server. This can be one of the following values.
  • flex.

  • node. Flex System compute node

  • rack. Stand-alone rack server

  • tower. Stand-alone tower server

{-v | --view} <filter>
Identifies the view to use for the returned data. If a filter is not specified, the default view is used.

You can also create custom views (see Creating custom views).

Examples

The following example deploys a server pattern to two rack servers and immediately activates the pattern on the servers.
connect --url https://192.0.2.0 --user ADMIN --noverify
configpatterns apply -i 48 -r immediate -t rack 
               -e AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA,BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
The following example deploys a server pattern to a Flex System server but does not not activate settings on the server until the server is manually restarted.
connect --url https://192.0.2.0 --user ADMIN --noverify
configpatterns apply –n pattern_C -r pending -t node -e CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC

Related links