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 12

Commands: Partition commands logging, Log file location and log format, Cases where no logging occurs

View all HP Integrity Superdome 2 16-socket manuals

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

Page 12 highlights

NOTE: - Run the help command at the OA prompt, to view the current list of Partition Help pages. - The Partition Help pages are: ◦ nPartition Commands parcreate, parmodify, pardefault, parremove, parstatus, and parperm ◦ vPartition Commands vparcreate, vparmodify, vparreset, vparremove, vparstatus, vparresources, resourcepath and vecheck ◦ vparresources and resourcepath are not commands. vparresources provides an overview of the vPar assignable resources in the complex and resourcepath provides an overview of the resourcepath specifications for the complex resources in various forms. Commands: Partition commands logging On the OA, the Partition commands executed are logged into the OA syslog file. The contents of the OA syslog file is displayed by show syslog OA at the OA prompt. On the OS side, the Partition commands executed from the HP-UX shell are logged to the local syslog file (the syslog file of the partition from which the partition command was executed). Log file location and log format The default syslog file on HP-UX systems is/var/adm/syslog/syslog.log. The format of the log entries is date hostname vPars_command_name[pid]: user username: vPars_command_line_text date hostname vPars_command_name[pid]: exit status exit_status where: • vPars_command_name is the name of the vPars command that sends messages to syslog. • username is the name returned by getlogin(). If no username is given by getlogin(), the effective username or ID will be used. • vPars_command_line_text is the vPars command line text as typed by the user. • pid is the Process ID of the command invocation. The PIDs shown will be the same for both the command invocation syslog entry and the exit status syslog entry. This allows matching the exit status with its corresponding command invocation. Below are examples of vPars syslog entries. Oct 29 19:47:47 Oslo2 vparmodify[2962]: user root: /sbin/vparmodify -p Oslo3 -a cpu::1 Oct 29 19:47:47 Oslo2 vparmodify[2962]: exit status 1 Cases where no logging occurs You can access the syslog file contents using the show syslog OA command from the OA prompt. Logging does not occur in the following cases (and no changes are made): • A non-root user in an OS attempting a Partition command. • Syntax, usage, or other Partition commands errors. • Commands which do not affect the state of the other partitions such as parstatus, vparstatus and vecheck. 12 Partitioning in HP Superdome 2

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

NOTE:

—

Run the

help

command at the OA prompt, to view the current list of Partition Help pages.

—

The Partition Help pages are:

◦

nPartition Commands

parcreate

parmodify

pardefault

parremove

parstatus

, and

parperm

◦

vPartition Commands

vparcreate

vparmodify

vparreset

vparremove

vparstatus

vparresources

resourcepath

and

vecheck

◦

vparresources and resourcepath are not commands. vparresources provides an overview

of the vPar assignable resources in the complex and resourcepath provides an overview

of the resourcepath specifications for the complex resources in various forms.

Commands: Partition commands logging

On the OA, the Partition commands executed are logged into the OA syslog file. The contents of

the OA syslog file is displayed by

show syslog OA

at the OA prompt. On the OS side, the

Partition commands executed from the HP-UX shell are logged to the local syslog file (the syslog

file of the partition from which the partition command was executed).

Log file location and log format

The default syslog file on HP-UX systems is

/var/adm/syslog/syslog.log

The format of the log entries is

datehostnamevPars_command_name

[

pid

]: user

username

vPars_command_line_text

date hostname vPars_command_name

[

pid

]: exit status

exit_status

where:

•

vPars_command_name

is the name of the vPars command that sends messages to

syslog

•

username

is the name returned by

getlogin

(). If no username is given by

getlogin

(),

the effective username or ID will be used.

•

vPars_command_line_text

is the vPars command line text as typed by the user.

•

pid

is the Process ID of the command invocation. The PIDs shown will be the same for both

the command invocation

syslog

entry and the exit status

syslog

entry. This allows matching

the exit status with its corresponding command invocation.

Below are examples of vPars

syslog

entries.

Oct 29 19:47:47 Oslo2 vparmodify[2962]: user root: /sbin/vparmodify -p Oslo3 -a cpu::1

Oct 29 19:47:47 Oslo2 vparmodify[2962]: exit status 1

Cases where no logging occurs

You can access the syslog file contents using the

show syslog OA

command from the OA prompt.

Logging

does not

occur in the following cases (and no changes are made):

•

A non-root user in an OS attempting a Partition command.

•

Syntax, usage, or other Partition commands errors.

•

Commands which do not affect the state of the other partitions such as

parstatus

vparstatus

and

vecheck

Partitioning in HP Superdome 2