Shell Commands › Server Management › set Command (Server Management)--Set Server Configuration Parameter

set Command (Server Management)--Set Server Configuration Parameter

The server set command sets a server configuration parameter.

Syntax

server set <name> <prop>=<val> [ --force ]

Options

<name>

Specifies the name of server for which to set information.

<prop>=<val>

Specifies the server parameter that you want to modify. You can set the following parameters:

hypervisor_name

Specifies the name of the hypervisor.

overcommit.cpu_sched_limit

Specifies the number of CPU cores that you want to make available for scheduling. You can specify the value as an explicit number or as a multiplier of the physical resources available (for example, 1x, 2x, and so on).

Default: If empty, the number of available cores reverts to being the same as the physical CPU resources available.

Limits: 2 through 1023

Note: Use CPU overcommitment only for special cases. If CPU is overcommitted, then requested CPU usage of appliances is scaled down based on the system load. If you overcommit CPU, then it is no longer guaranteed that the real CPU usage of an appliance is close to the requested usage.

overcommit.mem_sched_limit

Specifies the amount of memory (in bytes) to make available for scheduling on this server. You can specify the value with units of M or G. Absence of a units qualifier assumes G. You can also specify the value as a multiplier of the physical resources available (for example, 1x, 2x, and so on).

Default: If empty, the amount of available memory reverts to being the same as the physical resources available.

Limits: 2G to an upper limit of the size of the memory backing store or swap file

Note: Memory overcommitment is encouraged because it allows better usage of memory resources and makes operation of the whole system cheaper. However, depending on workload, the amount of overcommitment can degrade the system performance. Consider measuring the performance using performance monitoring software.

overcommit.bw_sched_limit

Specifies the amount of network bandwidth (in bits per second) available for scheduling on this server. You can specify the value with units of M or G. Absence of a units qualifier assumes G. You can also specify the value as a multiplier of the physical resources available (for example, 1x, 2x, and so on).

Default: If empty, the amount of available network bandwidth reverts to being the same as using the physical resources available.

Limits: 1G to 999G

--force

Skips the user verification prompt when setting a new primary server for a grid.

Examples: Set a Server Parameter

• This example sets the limit that will be used for scheduling memory on server 1 to 6 times the amount of physical memory and allow scheduling of up to 3 CPUs.

  server set srv1 overcommit.mem_sched_limit=6x overcommit.cpu_sched_limit=3
  

• This example sets the hypervisor_name to “zvm.”

  server set srv1 hypervisor_name=zvm
  

Notes:

• Network HA parameters “ha_network”, “ha_backbone”, “ha_external”, “backbone” and “external” are not useful on CA AppLogic for System z® as no external network switches are used for assembling the grid. Providing these parameters will produce a warning but they will otherwise be ignored. If they are the only parameters provided to “server set” then no action other than the warning will be taken.
• ”role=” is not useful on CA AppLogic for System z® as it is defined as a single server grid. Providing a “role=” argument to “server set” will produce a warning but it will otherwise be ignored. If it is the only parameter provided to “server set” then no action other than the warning will be taken.
• “hypervisor_lic_key” is not useful on CA AppLogic for System z® as it does not administer the z/VM license. Providing a “hypervisor_lic_key=” argument to “server set” will produce a warning but it will otherwise be ignored. If it is the only parameter provided to “server set” then no action other than the warning will be taken.
• You must be a grid maintainer to set any of the following network HA, hypervisor-related, or resource overcommitment parameters:
  • ha_network, ha_backbone, ha_external, backbone, and external
  • hypervisor_name and hypervisor_lic_key
  • overcommit.mem_sched_limit, overcommit.cpu_sched_limit, and overcommit.bw_sched_limit