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 6 CPU, Memory, and I/O Resources (A.05.xx)

Memory: Setting the Granularity Values (Integrity)

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

Syntax

The syntax for setting granularity unit size is:

-g ILM|CLM:unit[:y|n]

where:

-g

is granularity

ILM|CLM

specifies whether the unit size is applied to ILM or CLM

unit

is the granularity unit size in MBs

This value must be an integral power of 2 (in other words, 2^X) and be greater than or equal to 64.

y|n

specifies whether granularity unit size should be written to firmware. The default is n.

[vparcreate only; Integrity only]

The default memory granularity for CLM and ILM is based on the total memory in the nPartition. The minimum default value is 128 MB. However, if the memory in the nPartition is too large to fit into the supported number of memory granules for the nPartition, then the vPars commands will choose the next higher supported memory granularity value as the default memory granularity.

The default memory granularity is determined by the vPars software when the vPars database is created for the first time. Default memory granularity based on the total memory on the system is not applied to the database when an alternate database is specified by the user on the command line. When new memory is added to the hard partition, memory granularity is not automatically recalculated.

NOTE: In certain scenarios, the vPars commands may not be able to calculate the default granularities accurately. In these cases, a default of 128 MB will be chosen and a warning message asking the user to validate the granularity manually will be issued.

Commands

There are two commands that can set the granularity values: vparenv and vparcreate. Both are available at the HP-UX shell level and use the -goption:

  1. vparenv -g ...

    writes the granularity values to the firmware only. Note that vparenv is applicable only on Integrity.

  2. vparcreate -g ...

    writes the granularity values to the vPars database and also can (using the update firmware option [:y]) write these values to firmware.

vparenv

# vparenv -g ILM|CLM:unit

writes the unit granularity value to firmware. This takes effect for the nPartition on the next nPartition boot. For example, to set the granularity unit size in firmware for ILM to 512 MB and for CLM to 256 MB:

# vparenv -g ILM:512 -g CLM:256

Note that this does not set the granularity value in the vPars database. Only vparcreate sets the granularity value in the vPars database. Typically, you would change the granularity with vparenv rather than vparcreate if you have more than one database with differing granularities, and wish to switch to a database with different granularity during the next vPar Monitor boot.

CAUTION: The granularity values in firmware must match those in the vPars database used during the next boot of the vPars Monitor. If the granularity values in firmware do not match those in the vPars database, the virtual partitions of that database will not boot.

vparcreate

# vparcreate -p vpar1_name [-g ILM:unit[:y]][-g CLM:unit[:y]]

If you specify the above command without the :y, vparcreate only writes the unit granularity value to the vPars database; it does not write the value to firmware.

If you specify the above command with the :y, vparcreate writes the unit granularity value to both the vPars database and to firmware.

When using this method, note that the -g option must be performed when creating the vPars database (in other words, when performing the initial vparcreate command). If you choose not to set a value, or if you set the value incorrectly using the initial vparcreate command, you cannot adjust it later. You must re-create the vPars database.

Usage Scenarios

vparcreate with the :y option  The following is a scenario where you would want to use vparcreate with the -g option and the:yspecification:

  1. In nPars mode, you create your first virtual partition with a 256 MB granularity value for ILM. The command is

    # vparcreate -g ILM:256:y -p keira1 ...

  2. This writes the ILM granularity value to both the vPars database and to firmware. Since the default CLM granularity value is 128, this also writes the CLM granularity value of 128 to both the vPars database and to firmware. Because the values in both the vPars database and firmware match, you can boot this vPars database immediately after setting the nPartition for vPars mode and rebooting the nPartition.

    # vparenv -m vPars 1 # shutdown -r 2
    1

    Set the mode for the next nPartition reboot.

    2

    Reboot the system.

vparcreate without the :y option and vparenv  The following is a scenario where you would want to use vparcreate with the -g option but without the :yspecification. It also shows where you need to use vparenv to set the granularity value in the firmware. Note that this scenario would only occur on Integrity systems.

  1. You are in a vPars environment, running the default vPars database of /stand/vpdb that uses the 128 MB granularity values for ILM and CLM. Because the virtual partitions have been booted successfully, this means the current firmware also has granularity values of 128 MB.

  2. You create an alternate database /stand/vpdb.alt with a granularity value of 512 MB for ILM and 256 MB for CLM.

    # vparcreate -D /stand/vpdb.alt -g ILM:512 -g CLM:256 -p keira1 ...

  3. This writes the granularity value to the vPars database but not to firmware, which allows you to continue using the active vPars database /stand/vpdb with its 128 MB granularity value.

    When you wish to load /stand/vpdb.alt, you must then set the granularity value in firmware using vparenv, reboot the nPartition, and load the alternate database.

    # vparenv -g ILM:512 -g CLM:256 1 MON> reboot 2 ... HPUX> boot vpmon -D /stand/vpdb.alt 3
    1

    Set granularity value in firmware.

    2

    Reboot the nPartition.

    3

    Load the alternate vPars database.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.