Home » HP Manuals » Servers » HP Integrity Superdome 2 16-socket » Manual Viewer

HP Integrity Superdome 2 16-socket HP Superdome 2 Partitioning Administrator G - Page 22

Blade resource attributes, option is applied to all the blades

View all HP Integrity Superdome 2 16-socket manuals

Add to My Manuals
Save this manual to your list of manuals

Page 22 highlights

SLM can be specified as a blade resource attribute when creating nPartitions. The remaining available memory after specifying SLM is specified automatically as Interleaved Memory (ILM). For more information, see "Blade resource attributes" (page 22). Blade resource attributes With HP Superdome 2 nPartitions, blade attributes are specified using the parcreate and parmodify commands. The blade resource attributes are: • blade_path Specifies the blade resource path. It can be specified in short, medium, or long format. For example, the blade located in enclosure 1, slot 3 is identified in the short format as 1/3, in the medium format as blade:1/3, or in the long format as enclosure1/blade3. • blade_type Specifies the type of the blade. At initial release, the only valid blade_type value for blades is base. • use_on_next_boot Specifies whether the blade participates in the next reboot. The valid values for use_on_next_boot are: y Participates in reboot. This is the default value. n Does not participate in reboot. • failure_usage This field is used by the system firmware when an nPartition is booted. If a CPU self-test failure or a DIMM de-allocation failure occurs during blade activation, this flag is used by the system firmware to determine whether or not, and the manner in which the blade must be integrated into the nPartition at boot time. The valid failure_usage values for blades are: ri deconfig Reactivates with memory interleave. Specifies to integrate the blade as it would normally be integrated. This is the default value. Reactivates the nPartition with the blade excluded from activation. • slm_value Specifies the amount of memory that will be configured as SLM for the blade. An slm_value specified using the -a or -c option takes precedence over the slm_value specified using the -L option. The slm_value specified by the -L option is applied to all the blades for which an slm_value is not specified with the -a or -c options. If slm_value is not specified, the operating system specific default is applied. The size of SLM allocated is the best attempt to meet the user requested value. In addition, some amount of ILM might be allocated even when 100% SLM is requested. The slm_value can be expressed in the following forms: ◦ As a percentage The percent number can be any number in the range 0 to 100 with the % suffix. The number is rounded up to 12.5%, 25%, 37.5%, 50%, 62.5%, 75%, 87%, or 100%. If the blade contains less than 4 GB memory, the percentage will be rounded to 25%, 50%, 75% or 100%. The specified percentage is applied each time the nPartition boots, thus resulting in a different value if the working memory in the blade is different. For example, a blade in an nPartition has 8 GB memory and the user specifies 50% SLM. When the nPartition boots, 4 GB of that blade's memory will be used as SLM. Consider that the 22 Getting started with nPartitions

Section	Page
HP Superdome 2 Partitioning Administrator Guide	1
Contents	3
1 Introduction	7
Overview	7
HP Superdome 2 terminology	8
2 Partitioning in HP Superdome 2	9
Onboard Administrator and Partition Management	9
Accessing the OA	9
OA CLI	9
OA GUI	9
Managing Partitions – basics	10
nPartitions	10
Virtual Partitions (vPars)	11
Commands: Partition Help pages	11
Commands: Partition commands logging	12
Log file location and log format	12
Cases where no logging occurs	12
Cases where logging occurs	13
Constraints and restrictions to logging	13
Ordering and licensing	13
nPartitions licensing	13
Virtual Partitions licensing	13
Related software licensing	14
Ordering vPars	14
nPartition and Virtual Partition unique identifiers	14
3 Getting started with nPartitions	17
Administration tool for nPartitions	17
Onboard Partition Manager	17
Commands for configuring nPartitions	17
nPartition resources	18
Assigned or unassigned blades and I/O bays	19
Active and inactive blades	20
I/O Enclosures and I/O bays	20
Finding the resource path of I/O	20
nPartition properties	20
Partition names	21
Partition numbers	21
Hyperthreading	21
Enabling or disabling Hyperthreading on HP Superdome 2 using the GUI	21
Enabling or disabling Hyperthreading on HP Superdome 2 using the CLI	21
Socket Local Memory	21
Blade resource attributes	22
Operating system specific default values for nPartition attributes	25
Partition State and RunStates	26
Partition specifications (parspec)	28
Creating a Partition specification	29
Creating an nPartition from a Partition specification	29
Removing a Partition specification	29
Saving the current configuration of nPartition and switch to an alternate configuration	29
Identifying Partition specification using the OA GUI	29
4 Planning nPartitions	31
Recommended HP Superdome 2 nPartition configurations	31
HP Superdome 2 Partitioning choices	31
Superdome 2 CPU / CPU module support	34
CPU mixing support	35
HP Superdome 2 memory support	35
Sample procedure for creating nPartitions	35
5 Creating and configuring nPartitions	38
Tools for configuring nPartitions	38
Commands to configure nPartitions	38
Granting permission for an OS to manage nPartitions	38
Task summaries for creating and configuring nPartitions	39
Partition default attributes	39
Creating a new nPartition	40
Creating a new nPartition using the OA CLI	40
Creating a new nPartition using the OA GUI	40
Verifying newly created nPartitions using the CLI	41
Verifying newly created nPartitions using the OA GUI	42
Removing an nPartition	42
Removing an nPartition using the OA CLI	42
Removing (Deleting) an nPartition using the OA GUI	43
Renaming an nPartition	43
Renaming an nPartition using the OA CLI	43
Renaming an nPartition using the OA GUI	43
Assigning blades and I/O bays to an nPartition	43
Assigning blades and I/O bays to an nPartition using the OA CLI	43
Assigning blades and I/O bays to an nPartition using the OA GUI	44
Removing blades and I/O bays from an nPartition	45
Removing blades and I/O bays from an nPartition using the OA CLI	45
Removing blades and I/O bays from an nPartition using the OA GUI	46
Renaming a server complex	47
Setting blade attributes	47
Setting blade attributes using the OA CLI	48
Setting blade attributes using the OA GUI	48
6 Booting and resetting Partitions (nPartitions and vPars)	50
Overview of Partition system booting	50
Booting to UEFI and preparing for Operating System installation	50
Booting from the CLI	51
Booting from the GUI	52
Getting a Console using the CLI	55
Getting a Console using the GUI	55
UEFI I/O device connection solution	56
Device Connection Policies	57
Confirming the Installed IO cards	58
Getting MAC Addresses for Ignite-UX	59
Task Summaries for Rebooting and Resetting Partitions	60
POWEROFF PARTITION	61
POWERON PARTITION	64
REBOOT PARTITION	64
SET PARTITION DVD	65
SHOW PARTITION DVD	67
SHOW PARTITION INFO	69
Force System Reset and Crash Dump (TOC) PARTITION	69
UPDATE NPARTITION	70
UPDATE SHOW NPARTITION	72
UPDATE FIRMWARE	72
UPDATE SHOW FIRMWARE	72
HP Superdome 2 Boot Support	73
Local Boot	74
Considerations for Local Boot	74
Boot from local SAN	74
Boot from External SAN	74
nPartition and Resource Health Status	75
Viewing Partition and Resource Health Status Using the CLI	75
Viewing Partition and Resource Health Status Using the OA GUI	77
Resource health policy	77
7 Planning Your System for Virtual Partitions	79
Planning Your Virtual Partitions	79
Virtual Partitions Layout Plan	79
Virtual Partition Names	79
Minimal Hardware Configuration	80
CPU-core	80
CPU-core: Boot Processor Definitions	80
CPU-core: Specifying Min and Max Limits	80
CPU-core: Adding and Deleting by Total	81
vparcreate	81
vparmodify	82
CPU-core: Adding or Deleting by Socket Local Processor (SLP)	82
CPU-core: Adding or Deleting by Resource Path	83
CPU: Summary Information	83
Deleting CPU-cores Summary	84
CPU Allocation	84
Memory	84
Assigning Memory to a vPar	85
I/O	85
Assigning I/O at the rootport or I/O slot Level	85
Syntax, Rules, and Notes	86
Counts Summary	87
Parspec change policy	87
A note on Deconfiguration	87
8 Managing and Booting Virtual Partitions	89
Modes: Switching between nPars and vPars Modes	89
Modes	89
Setting the mode using the OA GUI	89
Setting the mode using the OA CLI	91
Getting the vPar Console	92
Managing: Creating a Virtual Partition	93
Booting a Virtual Partition	93
Managing: Modifying Attributes of a Virtual Partition	94
Commands: Displaying vPars Resource Information (vparstatus)	95
Virtual Partition States	95
vparstatus: Summary Information	96
Shutting Down or Rebooting a Virtual Partition	98
Shutting Down All Virtual Partitions	99
Managing: Removing a Virtual Partition	99
Boot options management for partitions	100
9 Installing or Removing the vPars product from the OS	101
Before You Install the vPars Software	101
Installing vPars	101
Bundle Names	103
vPars Product Bundles	103
Ignite-UX Cookbook	103
Removing the vPars Product	103
10 Support and other resources	104
Contacting HP	104
Before you contact HP	104
HP contact information	104
Subscription service	104
Documentation feedback	104
Related information	104
Typographic conventions	105
A Partition commands	107
Glossary	108

Match case Limit results 1 per page

SLM can be specified as a blade resource attribute when creating nPartitions. The remaining

available memory after specifying SLM is specified automatically as Interleaved Memory (ILM).

For more information, see

“Blade resource attributes” (page 22)

Blade resource attributes

With HP Superdome 2 nPartitions, blade attributes are specified using the

parcreate

and

parmodify

commands.

The blade resource attributes are:

•

blade_path

Specifies the blade resource path. It can be specified in short, medium, or long format. For

example, the blade located in enclosure 1, slot 3 is identified in the short format as

1/3

, in

the medium format as

blade:1/3

, or in the long format as

enclosure1/blade3

•

blade_type

Specifies the type of the blade. At initial release, the only valid

blade_type

value for blades

base

•

use_on_next_boot

Specifies whether the blade participates in the next reboot. The valid values for

use_on_next_boot

are:

Participates in reboot. This is the default value.

Does not participate in reboot.

•

failure_usage

This field is used by the system firmware when an nPartition is booted. If a CPU self-test failure

or a DIMM de-allocation failure occurs during blade activation, this flag is used by the system

firmware to determine whether or not, and the manner in which the blade must be integrated

into the nPartition at boot time. The valid

failure_usage

values for blades are:

Reactivates with memory interleave. Specifies to integrate the blade as it

would normally be integrated. This is the default value.

Reactivates the nPartition with the blade excluded from activation.

deconfig

•

slm_value

Specifies the amount of memory that will be configured as SLM for the blade. An

slm_value

specified using the

-a

-c

option takes precedence over the

slm_value

specified using

the

-L

option. The

slm_value

specified by the

-L

option is applied to all the blades for

which an

slm_value

is not specified with the

-a

-c

options. If

slm_value

is not specified,

the operating system specific default is applied. The size of SLM allocated is the best attempt

to meet the user requested value. In addition, some amount of ILM might be allocated even

when 100% SLM is requested. The

slm_value

can be expressed in the following forms:

◦

As a percentage

The percent number can be any number in the range 0 to 100 with the % suffix. The

number is rounded up to 12.5%, 25%, 37.5%, 50%, 62.5%, 75%, 87%, or 100%. If

the blade contains less than 4 GB memory, the percentage will be rounded to 25%, 50%,

75% or 100%. The specified percentage is applied each time the nPartition boots, thus

resulting in a different value if the working memory in the blade is different. For example,

a blade in an nPartition has 8 GB memory and the user specifies 50% SLM. When the

nPartition boots, 4 GB of that blade’s memory will be used as SLM. Consider that the

Getting started with nPartitions