Beruflich Dokumente
Kultur Dokumente
Table of contents Introduction ..................................................................................................................................3 What are nPars and vPars? ...........................................................................................................3 Superdome 2 partition management overview .................................................................................3 nPar new features in Superdome 2 .................................................................................................5 Finer socket granularity ..............................................................................................................5 Integrated nPar/vPar management ..............................................................................................5 Partition specifications or parspecs..............................................................................................5 OS-agnostic resource paths ........................................................................................................6 Improved partition run-states .......................................................................................................7 OS specific default values for nPar attributes ................................................................................7 Improved h/w diagnostic display................................................................................................7 vMedia/DVD support ................................................................................................................8 Memory granularity is now an nPar attribute ................................................................................8 nPars differences in Superdome 2 from legacy implementation ..........................................................8 Resource specifications use new OS-agnostic resource paths ..........................................................8 Transition from chassis/cell (or global cell) usage to enclosure/blades ............................................8 Assigning I/O to nPars ..............................................................................................................9 Finding the resource path of I/O ................................................................................................9 OA CLI for partition operations ...................................................................................................9 Force and override option for OA CLI .........................................................................................9 Partition configuration from the Superdome 2 OA GUI ................................................................10 Root permissions needed for status display commands ................................................................10 Remote complex management through partition commands no longer used ...................................10 Socket local memory instead of cell local memory .......................................................................10 Blade online addition, deletion, or replacement (Blade OL*) no longer used ..................................10 VFP no longer used .................................................................................................................10 Obsolete nPar commands (fruled, frupower, cplxmodify, parunlock) .............................................10 Parconfig command for configuring LORA partitions no longer used .............................................10 HT is enabled for HP-UX by default ...........................................................................................10 No interleave blade failure usage policy is not supported .........................................................11 Core cell no longer used .......................................................................................................11 Obsolete partition command IP address .....................................................................................11 Unique partition names ............................................................................................................11 Change in reboot for reconfiguration method .............................................................................11 Genesis partition no longer used...............................................................................................11 Complex Profile no longer used ................................................................................................11 ILM/SLM ratio ........................................................................................................................11 vPars new features in Superdome 2 vPars ......................................................................................12 Integrated nPar/vPar management ............................................................................................12 Max 16 vPars per nPar ............................................................................................................12 Maximum of 4 vPars/blade as opposed to 8 vPars/cell ..............................................................12 Separate console for vPars .......................................................................................................12 vMedia/DVD support ..............................................................................................................12 vPar management through the Superdome 2 OA ........................................................................12
vPars differences in Superdome 2 from legacy implementation .........................................................13 No vPars monitor or vPar monitor commands .............................................................................13 Booting all vPars simultaneously ................................................................................................13 OA commands for vPar operations ...........................................................................................13 vPar commands from OA need to specify the nPar context ...........................................................13 OS-agnostic resource paths ......................................................................................................13 Transition from chassis/cell usage to enclosure/blades................................................................14 Transition from SBA/LBA to iohub/rootcomplex/rootport as well as ioslot usage ............................14 vPar configuration files (vPar database) reside on the Superdome 2 OA (not on HP-UX) ..................14 vPar boot follow nPar boot conventions .....................................................................................14 vPar install is now the same as how nPars are installed ...............................................................14 Memory granularity no longer a vPar attribute ............................................................................15 Change in default memory granularity .......................................................................................15 Change in minimum memory granularity....................................................................................15 vPar permissions management from the OA ...............................................................................15 Socket local resources instead of cell local resources ...................................................................15 vPar EFI shell ..........................................................................................................................15 Memory range support no longer used ......................................................................................15 vPars created with zero CPUs by default ....................................................................................15 Addition/deletion of CPU by path increases CPU count ...............................................................15 PIM data retrieval ...................................................................................................................16 OS version display in vparstatus ...............................................................................................16 Changes in mode switch functionality ........................................................................................16 Obsolete commands................................................................................................................16 Memory distribution among vPars .............................................................................................16 Partition state and run-states .....................................................................................................16 Change in reboot for reconfiguration method .............................................................................16 Support only for HP-UX versions that run on Superdome 2 nPars ...................................................17 Default values for SLM/ILM ratio following a mode switch ...........................................................17 Parspec change policy.............................................................................................................17 Both cpu and core keywords supported with the -a option ...................................................17 vPar numbers..........................................................................................................................17 Interactive commands no longer used ........................................................................................17 New Features in the Dynamic Cores release of Superdome 2 firmware .............................................18 Dynamic Cores .......................................................................................................................18 Core migration across vPars .....................................................................................................18 Core activation/deactivation in nPars........................................................................................19 Intended Active parameter (IA) .................................................................................................20 Difference in core migration behavior on Superdome 2 compared to legacy Superdome.................20 LORA ....................................................................................................................................20
Introduction
HP Superdome servers are scalable, cell-based systems, which support HP nPartitions (nPars) and HP-UX Virtual Partitions (vPars). This paper discusses the differences in managing partitions on the next-generation of HP Superdome servers, referred to as Superdome 2, as compared to the previous generation of HP Superdome, rx8640, and rx7640 servers, sometimes referred to as legacy systems. Legacy Superdome systems are referred to as SD1 in this paper. This document is primarily targeted toward users who have prior nPar and vPar experience.
Note: On servers prior to Superdome 2, partition configuration management software primarily ran on the system processors on the partition side. Hence, in order to ease the transition to the new management model, legacy partition management command interfaces with minor modifications are still supported from the partition side.
The partition management aspects described in this document covers the management tools available for partition configuration/reconfiguration operations and partition start/stop related operations.
Remote System
SMH gWLM
An nPar or vPar
Superdome 2 Complex
IPMI
OA
OA CLI + nPar, vPar, iCAP CLIs iCAP Usage Rights Mgr Can use network or serial connection between the users desktop and the MP
Figure 1 depicts the different ways a user can interact with the system to manage partitions. There are primarily three ways users can do partition management on Superdome 2 servers. 1. From the Superdome 2 OA OA GUI for all nPar and many vPar uses OA CLI for all nPar and all vPar commands 2. From the partitions Legacy (SD1 and earlier) partition management command interfaces are still supported from the partition side 3. From a data center management environment such as HP Systems Insight Manager (SIM) Get health information for the entire Superdome 2 complex and each partition Click down into the Superdome 2 OA to access the Superdome 2 partition management tools
Every parspec defines only one nPar. Multiple nPars must be described in multiple parspecs. An nPar can be created from a specified parspec. Every nPar that exists has a parspec associated with it (referred to as a current parspec), and there can be only one
current parspec for a given nPar.
Any parspec not associated with an existing nPar is an alternate parspec. Every parspec has a unique name (scope of uniqueness is a complex). Parspecs can be managed through the partition commands. The vPar configuration information (legacy vPar database) resides within a parspec. Parspecs are stored in the OA, and are therefore available regardless of the partition state. Parspecs change policy attributes allow customers to specify a modification behavior should a parspec not be able
to attach all the resources requested in the definition.
Save nPar configurations Modify nPar configurations Create nPars Maintain alternate partition definitions for use at different times of the day, week, or month Quickly restore or reconfigure a system from tested nPar definitions
For more details on parspec, refer to the parspec manpage [parspec (5)] or the appropriate section in the HP Superdome 2 Partitioning Administrator Guide.
For more details on resource paths, refer to the resource path manpage [resource path (5)] or the appropriate section in the HP Superdome 2 Partitioning Administrator Guide.
Typically, you can see that an inactive partition is in a defined, down, or activating run-state. But there may be rare occasions where you can notice an inactive partition to be in deactivating, resetting, MCA, or INIT run-states. This can happen if a partition is subjected to these operations while the partition was in the activating run-state.
vMedia/DVD support
Previous Superdome systems required an external DVD-ROM be attached to each partition. In Superdome 2, the Integrity iLO 3 Virtual Media (vMedia) built into every cell blade provides a virtual DVD-ROM/USB key. Using vMedia commands provided in the Superdome 2 OA, a partition can be given use of the physical DVD-ROM, which is built into every Superdome 2 enclosure. Alternatively, the OA web GUI can be used to connect to a remote DVD-ROM or iso image located in the GUI users PC. This allows an Superdome 2 partition to boot and use standard media without having to purchase and attach a separate physical DVD-ROM to each partition. A physical DVD-ROM may still be attached to a partition by use of the USB port provided on the SUV cable. This is a temporary attachment to an individual blade.
10
ILM/SLM ratio
On previous platforms, an nPar created was by default configured with 100 percent ILM. On Superdome 2 servers, the default ILM/SLM ratio is determined by the OS type for which the nPar is created. Use the pardefault command to see the default values for each OS type. It is also worthwhile to note that on Superdome 2 servers, even when the user has specifically requested 100 percent SLM for an nPar, some amount of ILM may still be configured.
11
vMedia/DVD support
As described in the nPar new features section, Superdome 2 uses iLO vMedia to attach a virtual DVD-ROM/USB key to either an nPar or a vPar. For vPars vMedia assignment, vMedia can be attached to the vPar which has been assigned the cell blade iLO port. In Superdome 2 systems, there is one physical Integrity iLO 3 management processor built into every cell blade. Since there is only one iLO per cell blade, the number of vMedia/DVDs available for vPars is limited to the number of cell blades (the number of iLOs) in the nPar. The IO paths (rootports) having iLO capability are displayed by the parstatus c {blade} V command. vPar commands can be used to assign the rootport or IO slot hosting the iLO to a vPar, similar to assigning any other IO to a vPar. To get access to the enclosure DVD drive from a vPar, in addition to assigning the rootport having iLO capability to the vPar, the set partition dvd OA command (or the OA GUI) should be used to connect the DVD to a vPar.
12
13
vPar configuration files (vPar database) reside on the Superdome 2 OA (not on HP-UX)
Prior to Superdome 2 servers, the vPar configuration file or database (vpdb) was a binary file that resided on /stand in an HP-UX OS image and contained configuration definitions for all vPars in the nPar. On Superdome 2 servers, with the OA-based partition management that supports an integrated nPar/vPar management in an OS-agnostic way, the vPar configuration is part of the parspec that describes an nPar. The parspec resides on the OA and is created/managed through the partition commands. So a /stand/vpdb file, if seen on HP-UX, does not have any relevance on Superdome 2 servers. On Superdome 2 servers, there is no concept of a vpdb as it existed previously. Each parspec stores the vPar definitions in addition to the nPar configuration. The equivalent of an alternate vpdb now refers to the vPar definitions in an alternate parspec. Consequent to that behavior, there is no -D option supported in vPar commands, instead users have to use the -Z option to target an alternate parspec.
14
15
Obsolete commands
Some vPar commands are no longer required in the OA based partition management solution supported on Superdome 2 servers. They are either not relevant in the new architecture or are replaced by other commands providing equivalent functionality. These commands are vparefiutil, vparutil, vparconfig, vparextract, vpardump, vparadmin, vpardbprofile.
16
vPar numbers
On Superdome 2 servers, vPars can be specified either by the partition number or the partition name similar to nPars. Any partition command accepts either vPar name or number to denote a target partition. From the OA, a vPar can also be addressed using a combination of nPar and vPar identification as explained earlier. On previous platforms, vPars could only be addressed by names.
17
18
(ii) Using OA-based commands Adding cores to a vPar (add 2 cores from socket 1/1/0) vparmodify -p 1:2 -a socket:1/1/0:core::2 vparmodify -p 1:2 -a socket:1/1/0:cpu::2 Deleting cores from a vPar (delete 2 cores from socket 1/1/) vparmodify -p 1:2 -d socket:1/1/0:core::2 vparmodify -p 1:2 -d socket:1/1/0:cpu::2 Path based Note: Path-based additions are possible only through the vparmodify interface. It is not supported in the icapmodify interface Examples (i) Using OS-based commands Adding cores to a vPar vparmodify -p 2 -a cpu:1/1/0/1 vparmodify -p 2 -a core:1/1/0/1 Deleting cores from a vPar vparmodify -p 2 -d cpu:1/1/0/1 vparmodify -p 2 -d core:1/1/0/1
19
LORA
With the DC release, the assignment of cores to a vPar either during boot or online core addition is done such that the core distribution is as close as possible to the memory localities owned by the vPar. This helps keep latencies (due to larger distance of cores from the sockets on which memory has been drawn) minimal.
HP Superdome servers are scalable, cell-based systems, which support HP nPars and vPars. To know more, visit www.hp.com/go/Superdome2 and www.hp.com/go/integrity.
Copyright 20102011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. 4AA2-0619ENW, Created July 2010; Updated November 2011, Rev. 3