Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX Virtual Partitions Administrator’s Guide > Chapter 9 nPartition Operations

Configuring CLM for an nPartition

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

ILM memory can be re-configured to be CLM using the parmodify command. Then, you can assign existing available CLM to a virtual partition.

For complete information on CLM and configuring cells and nPartitions, see the nPartition’s Guide.

parmodify syntax

The syntax for the parmodify command is

parmodify -pnPar_num -mcell:[type]:[use]:[fail][:clm]

where

nPar_num

is the nPartition number

cell

is the cell to be modified. this can be either the global format (cell_number) or hardware format (cabinet/slot)

type

is the cell type. base is the only valid value and is the default.

use

is the use-on-next-boot value. this is either a y or n. The default is y. Use y if the cell is to be an active member of the nPartition or n if the cell is to be an inactive member

fail

is the cell failure usage. the only valid value is ri (reactivate with interleave) and is the default

clm

is the amount of memory that will be configured as cell local memory for the cell. this value can either be an absolute (the default) or percentage value. The absolute value is a number, which represents the amount of memory in gigabytes; the percentage value is any number followed by the character %.

Example

  • To configure 1 GB of memory as CLM on cell 6 of nPartition 0, the command is

    # parmodify -p0 -m 6::::1

    For the parmodify change to take effect, you need to reboot the nPartition. This can be done by MON> reboot.

Configuring CLM Notes

IMPORTANT: The HP-UX operating system does not support a 100% CLM configuration in an nPartition. Some memory must be configured as ILM to support HP-UX (whether in a vPars environment or not).
  • It is possible that a server’s NVRAM (non-volatile RAM) values for ILM and CLM can change due to a firmware update or a previous systems administrator. Verify the NVRAM values.

  • Any memory that is not configured as CLM remains ILM.

  • You need to be sure to leave enough ILM memory for your virtual partitions to boot, as specified in your vPars database. Also, on PA-RISC not all memory can be configured as CLM in an nPartition. You need to allow ILM memory for the vPars Monitor to boot and for all the OS kernels to boot; excluding the first granule, a portion of which is used by the vPars Monitor, there must be at least one entire granule that exists below the 2 GB limit for each virtual partition. These granules below the 2 GB limit are used by the kernel of each virtual partition.

  • nPartition configuration rules limit the minimum amount of configured CLM memory for a cell. If you have any CLM on a cell, it must be at least 512 MB.

  • When performing parmodify commands within a vPars environment, you will see only the cells that are within the nPartition running vPars. If you wish to add cells from outside the nPartition, you will need to be in standalone (PA-RISC) or nPars (Integrity) mode to see the other cells.

CAUTION:
  • If you reduce the ILM amount below that configured for all the virtual partitions in your vPars database, one or more of the virtual partitions may not boot. Be sure that there is enough CLM and ILM configured in the nPartition so that the sum of ILM and CLM memory of all your virtual partitions does not exceed the ILM and CLM in the nPartition.

  • New servers should be set with 100% ILM and 0% CLM. However, a firmware update or even another systems administrator can change these values. You should check your NVRAM configuration before configuring vPars. Also, if you need to set an equal amount of ILM across all cells (see the HP-UX Virtual Partitions Release Notes for A.04.01), you should set your NVRAM configuration to 100% ILM and 0% CLM, then perform the CLM calculations and operations to get the equal amounts of ILM.

    To check the existing ILM/CLM configuration, use parstatus. For example, to check the ILM and CLM configuration in nPartition 2:

    keira# parstatus -V -p 2 [Partition] Partition Number : 2 Partition Name : Partition 2 - HPUX Status : Active IP Address: Primary Boot Path : 12/0/3/1/0.0.0 Alternate Boot Path : HA Alternate Boot Path : PDC Revision : 3.66 IODCH Version : ffff Cell Architecture : Itanium(R)-based CPU Compatibility : BCF-640 CPU Speed : 1600 MHz Core Cell : cab1,cell4 Core Cell Choice [0] : cab1,cell4 Total Good Memory Size : 40.0 GB Total Interleave Memory: 1.0 GB Total Requested CLM : 40.0 GB Total Allocated CLM : 39.0 GB

    The parstatus output shows the current configuration of 1 GB ILM and 39 GBs of CLM.

    Assuming nPartition 2 consists of cells 12 and 14, to change values of ILM to 100% and CLM to 0%, set the value of CLM to 0% (any memory not configured as CLM becomes ILM):

    keira# parmodify -p 2 -m 12::::0% -m 14::::0% keira# shutdown -R

    After the nPartition is rebooted, the parstatus output should show all memory configured as ILM:

    keira# parstatus -V -p 2 [Partition] Partition Number : 2 Partition Name : Partition 2 - HPUX Status : Active IP Address: Primary Boot Path : 12/0/3/1/0.0.0 Alternate Boot Path : HA Alternate Boot Path : PDC Revision : 3.66 IODCH Version : ffff Cell Architecture : Itanium(R)-based CPU Compatibility : BCF-640 CPU Speed : 1600 MHz Core Cell : cab1,cell4 Core Cell Choice [0] : cab1,cell4 Total Good Memory Size : 40.0 GB Total Interleave Memory: 40.0 GB Total Requested CLM : 0.0 GB Total Allocated CLM : 0.0 GB
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.