|
|
Name These Little Nuts for my Server Cabinet?
05-15-2013
Name These Little Nuts for my Server Cabinet?
|
|
parmodify(1M) parmodify(1M) NAME
parmodify - modify an existing partition SYNOPSIS
PartitionNumber [celltype]use_on_next_boot][failure_usage][ [celltype]use_on_next_boot]failure_usage] [celltype]use_on_next_boot]failure_usage][ [celltype]use_on_next_boot]failure_usage] cell cell]... cell cell]... flag] username IPaddress path path path PartitionName s_lock:p_lock } DESCRIPTION
The command is used to modify the attributes of an existing partition. By default the target partition is the local partition. Either the or the option can be specified to allow this command to modify any other partition in the (local or remote) complex. This command can mod- ify the following attributes: Partition name Cell assignment: Add cells to the partition Delete cells from the partition Attributes of existing cells: celltype use_on_next_boot failure_usage clm_value (cell local memory) Core cell choices Primary boot path HA Alternate boot path Secondary boot path Partition's IP address By the nature of its operation, this command can modify the configuration of its target complex. Operation can be affected by the state of the target complex's nPartition Configuration Privilege. If the nPartition Configuration Privilege is unrestricted (the default), or the complex is accessed using the option, all operations are allowed. Otherwise any of the operations below causes the command to fail: o add cells to any partition in the complex o delete cells from any partition in the complex o modify the CLM parameters of any cell in the complex The option is unaffected by the state of the nPartition Configuration Privilege. Note: The state of the nPartition Configuration Privilege can only be changed at the service processor's Command menu. Superuser permission is required to run this command on the local partition. If the option is used to access a remote partition or com- plex, superuser permission is not required on the local system, and the local system need not exist on an nPartition. If the option is specified, username on the remote host must have superuser permission or the command will fail. Refer to the for a description of the partition management terms used in this man page. Options and Arguments recognizes the following command line options and arguments: Specifies the partition to be modified. PartitionNumber specifies the unique number (integer) assigned to the partition when it was created. Note: The parti- tion which is specified to be modified is called the target partition. The partition in which the command is executing is called the local partition. One or more of the following options must be specified with the option: Assigns the specified cell to the target partition. To assign multiple cells to the partition, multiple options should be used. cell specifies the cell id. It can be specified either in the local (cabinet#/slot#) or global (cell#) format. For example, the cell located in cabinet 0, slot 1 is identified in the local format as 0/1 or in the global format as 1. celltype specifies the type of the cell. The valid celltype values for a cell are: This is the default if celltype is not specified. A floating cell in a partition does not participate in interleaved memory (all of the cell's memory is used as CLM). A floating cell cannot be a partition's core cell. use_on_next_boot specifies whether the cell will participate in a reboot and allows online operations. The valid val- ues for use_on_next_boot are: participate in reboot and allow cell online operation to be performed. Refer to the parolrad(1M) manpage for more information. This is the default. However if the slot is missing, or the cell does not exist, or the cell is powered off, then it defaults to do not participate in reboot. failure_usage field is used by system firmware when a partition is booted. If a CPU selftest failure or a DIMM de- allocation occurs during the power-on self-test process then this flag is used by the system firmware to determine whether or not and how the cell should be integrated into the partition at boot time. The valid failure_usage value for cells is: reactivate with memory interleave. Specifies to integrate the cell as it would normally be integrated. This is the default for base cells. this is the default value for floating cells. If the user specifies ri for a floating cell, the command outputs an error and exits. deconfigure. no interleave. clm_value specifies the amount of the memory that will be configured as local (non-interleaved) memory for the cell. The command issues a warning if the specified clm_value exceeds the total memory of the cell. Note: On PA platforms, the amount of memory allocated for CLM may not match the amount of CLM requested due to some memory being reserved exclusively by the operating system. If no clm_value is specified, maximum interleaved memory (no clm) is assumed for cells. The command will issue a warn- ing if 100% CLM is specified for all the cells in the partition. The clm_value can be expressed in two forms: o As a percentage (ratio). The percent number can be any number in the range 0 - 100 with a suffix of "%". This num- ber will be rounded up to 12.5%, 25%, 37.5%, 50%, 62.5%, 75%, 87% or 100%. If the cell contains less than 4 GB mem- ory, then the percentage will be rounded to 25%, 50%, 75% or 100%. The specified percentage is applied each time the partition boots, thus resulting in a different value if the working memory in the cell is different. For exam- ple, a cell in a partition has 8 GB memory and the user specifies 4 GB CLM. When the partition boots 4 GB of that cell's memory will be used as CLM. Later the user shuts down the partition, adds another 8 GB memory to that cell. When the partition is booted again, the cell now has 16 GB of memory, so 8 GB (50%) is allocated as CLM. o As an absolute number (default). This can also be optionally suffixed by "GB". The clm_value is interpreted as an absolute number of gigabytes of memory. Numbers other than integers and halves are rounded up to the nearest 0.5 GB. For example: 2.5 GB will not be rounded up. However 2.3 GB will be rounded up to 2.5 GB. For example, a cell in a partition has 8 GB memory and the user specifies 50% CLM. When the partition boots 4 GB of that cell's memory will be used as CLM. Later the user shuts down the partition, adds another 8 GB memory to that cell. When the par- tition is booted again, the cell now has 16 GB of memory, but the CLM is still 4 GB. Specifies to reboot the partition now. The default is not to boot. If this option is specified and the partition to be modified is not the local partition, then the command proceeds only if the specified partition is not active. Also this option is useful only if the option or the option or a clm_value has been specified. Specifies the primary boot path. path specifies a physical hardware path. Note: On Itanium-based platforms, only boot paths of the local partition can be modified. Delete the specified cell(s) from the partition. If the cell which is being deleted is an active cell then after the execution of the command the user must shutdown the parti- tion using the command for the configuration change to take effect. If the option is also specified then the partition will boot up to the command prompt. If the option is not specified then the partition will have to be booted manually from the service processor. Deletion of inactive cells does not require a shutdown of the partition. A cell can be specified either in the local (cabinet#/slot#) or global (cell#) format. For example, the cell located in cabinet 0, slot 1 is identified in the local format as 0/1 or in the global format as 1. Allows access to the complex specified by the option. The accessed complex is then considered the target complex. Access is through the service processor's LAN port. The option is required if this option is used. If this option is specified, the command prompts for the password. If an error is reported when you attempt to connect using this option, check to see that IPMI LAN access has not been disabled on the remote service processor. Access to the complex through IPMI over LAN can be enabled or disabled by logging on to the service processor and using the command from the Command Menu. The and options are mutually exclusive. This option should only be used in combination with either the option. IPaddress|hostname specifies the IP address or hostname of the target partition or complex Specifies the IP address that should be used by management tools such as to address the target partition. This value must be consistent with the IP address that is assigned to the partition once HP-UX is installed and networking is configured. Specifies the lock keys provided by for the Stable Complex Configuration Data and Partition Configuration Data. The lock keys should always be specified in pairs. If either lock key is not available should be specified as a placeholder. For example: if the s_lock is available but the p_lock is not available, then it should be specified as Note: The option is intended for use by system management tools which invoke the command programmatically. Command line users should avoid this option. Modify attributes of cell(s) already assigned to the target partition. Please refer to the explanation of the option for details of the different fields in this option argument. Note: o The use_on_next_boot field of the last cell containing core I/O cannot be modified to o If modifying the CLM value of a cell in any partition other than the local partition, it is preferable to use the option. Specifies the name of the partition. The characters which can appear in a valid partition name are (dash), (underscore), " " (space) and (period). If the partition name includes a space then the name should be enclosed in double quotes. The partition name can have a maximum of 64 characters; it should not start with a dash Specifies the core cell choices. A core cell choice is a configured cell which has attached core I/O. If the core cell of a partition is deleted then the firmware will select the first core cell choice as the next core cell. One to four core cell choices can be specified. The first cell specified is the first core cell choice, the second cell specified is the second core cell choice, the third cell specified is the third core cell choice and the fourth cell specified is the fourth core cell choice. Use of this option will override previ- ous core cell choices. So, if the order of a given cell is changing, all of the core cell choices should be specified in the new order. A cell can be specified either in the local (cabinet#/slot#) or global (cell#) format. For example, the cell located in cabinet 0, slot 1 is identified in the local format as 0/1 or in the global format as 1. Specifies the secondary boot path. path specifies a physical hardware path. Note: On Itanium-based platforms, only boot paths of the local partition can be modified. Specifies that whether Hyper-Threading should be enabled or not (only if cell support this feature). If this option is not specified, Hyper-Threading property will not be changed. The valid values for flag are: enables Hyper-Threading, which allows multiple threads to run concurrently on each CPU. disables Hyper-Threading. Specifies the alternate boot path. path specifies a physical hardware path. Note: On Itanium-based platforms, only boot paths of the local partition can be modified. Specifies the required authorization to access a partition other than the local system (but can also be used as a loopback access to the local partition). The option is required if this option is used. If this option is specified, the command prompts for the password. username specifies a configured user name on the target partition. Note: This command is a Web-Based Enterprise Management (WBEM) Client Application. The option accesses the target par- tition using a Secure Sockets Layer (SSL) connection. If errors are reported, check that the conditions described in the section are satisfied. Mapping of Global Cell Numbers to Local Cell Numbers The cabinets in a complex are numbered starting from 0. The cell slots in each cabinet are also numbered starting from 0. Each cabinet can have a maximum of 8 cells. For example, the cells located in cabinet 0 will have the following cell numbers in global format: 0, 1, 2, 3, 4, 5, 6, 7. The cell numbers in corresponding local format will be 0/0, 0/1, 0/2, 0/3, 0/4, 0/5, 0/6, 0/7. Similarly the cells located in cabinet 1 will have the following cell numbers in global format: 8, 9, 10, 11, 12, 13, 14, 15. The cell numbers in corresponding local format will be 1/0, 1/1, 1/2, 1/3, 1/4, 1/5, 1/6, 1/7. From the above convention the cell located in cabinet 1, slot 0 is identified in the local format as 1/0 or in the global format as 8. The command will display the above cell as "cab1,cell0". The cell located in cabinet 1, slot 4 is identified in the local format as 1/4 or in the global format as 12. The command will display the above cell as "cab1,cell4". RETURN VALUE
The command exits with one of the following values: Successful completion. Error condition occurred. EXAMPLES
Add a new cell in cabinet 0 slot 5 to the existing Partition 2. Activate the added cell online. Delete a cell in cabinet 0 slot 5 from the existing Partition 2. WARNINGS
On a partition whose hardware resources are managed under an Instant Capacity (iCAP) license, the command fails if a configuration change would take the partition out of compliance. Examples of such actions include: o Assigning an iCAP cell to a partition, specifying "y" for the cell's use_on_next_boot field. o Changing an iCAP cell's use_on_next_boot field to "y" after assigning it to a partition. o Assigning a cell containing iCAP-licensed CPUs to a partition that is not running, or that does not have the iCAP software installed. For more information about actions that are restricted on iCAP partitions, refer to the located at DEPENDENCIES
This command uses the Web-Based Enterprise Management (WBEM) product and some of its configuration settings. If you encounter connection errors when using the option, check that the following two conditions are satisfied: o Use the command (see cimconfig(1M) in the WBEM product documentation) to verify (and correct if necessary) the setting of the following two variables: o o o The target partition's digital certificate has been appended to the local partition's Shared Authentication Store. For the nPartition commands, the Shared Authentication Store is stored in the file: This file is used by all the clients, which use SSL based certificates. If these clients trust a target partition, then the nPartition commands will also trust the target partition. Refer to the WBEM documents specified in the section below for further information. AUTHOR
was developed by the Hewlett-Packard Company. SEE ALSO
fruled(1), parstatus(1), cplxmodify(1M), frupower(1M), parconfig(1M), parcreate(1M), parmgr(1M), parolrad(1M), parremove(1M), parun- lock(1M), partition(5). on on on parmodify(1M)