Download  Print this page

HP Integrity Superdome 2 16-socket Administrator's Manual

Superdome 2 partitioning administrator guide.
Hide thumbs


HP Superdome 2 Partitioning Administrator
HP-UX 1 1i v3
HP Part Number: 5900- 1 801
Published: August 201 1
Edition: 2.0


Table of Contents

   Related Manuals for HP Integrity Superdome 2 16-socket

   Summary of Contents for HP Integrity Superdome 2 16-socket

  • Page 1 HP Superdome 2 Partitioning Administrator Guide HP-UX 1 1i v3 HP Part Number: 5900- 1 801 Published: August 201 1 Edition: 2.0...
  • Page 2 © Copyright 201 1 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 1 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
  • Page 3: Table Of Contents

    Contents 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...
  • Page 4 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...
  • Page 5 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...
  • Page 6 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 Index.......................109 Contents...
  • Page 7: Introduction

    1 Introduction The HP Integrity Superdome 2 servers (HP Superdome 2) are scalable systems based on blade system architecture. HP Superdome 2 systems support HP nPartitions and HP-UX Virtual Partitions (vPars v5). This administrator guide describes the steps to plan, create, and manage partitions – nPartitions and virtual partitions –...
  • Page 8: Hp Superdome 2 Terminology

    You can manage partitions on HP Superdome 2 systems using the following methods: From the OA: The OA Graphical User Interface (GUI) and Command Line Interface (CLI) support partition management user interfaces. NOTE: The initial release of HP Superdome 2 does not support iCAP CLIs on the OA. From the partitions: The operation system based (Legacy) partition management command interfaces are supported from the partition OS instance, until these operations are targeted to that vPar instance.
  • Page 9: Partitioning In Hp Superdome 2

    2 Partitioning in HP Superdome 2 Onboard Administrator and Partition Management This chapter provides information on managing partitions – hard partitions (nPartitions) and virtual partitions (vPars v5) – using the Onboard Administrator. The OA supports both a GUI as well as a CLI. You can log in to the OA GUI by entering the appropriate URL in the web browser.
  • Page 10: Managing Partitions - Basics

    Figure 1 OA GUI Login Screen Enter the OA Administrator password. NOTE: The original Administrator password is available on a sticker on the OA module. Managing Partitions – basics The partition management architecture on HP Superdome 2 is designed to adapt to the new hardware and firmware architecture.
  • Page 11: Virtual Partitions (vpars)

    Boot an existing nPartition. Remove an nPartition. Rename an nPartition. Reset an nPartition. Assign and unassign resources such as blades and I/O bays. You can define many possible configurations for an nPartition complex, and then control the configurations or partitions that can exist at any given point in time. This is possible by using partition specifications.
  • Page 12: Commands: Partition Commands Logging

    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.
  • Page 13: Cases Where Logging Occurs

    Cases where logging occurs Logging occurs when the commands either change or affect the state of partitions. The commands include parcreate, parmodify, parremove, vparboot, vparcreate, vparenv, vparremove, vparmodify, and vparreset. Constraints and restrictions to logging The command line text will be logged on only the partition from which the command was executed.
  • Page 14: Related Software Licensing

    NOTE: HP Integrity servers running the new HP sx3000 chipset are quad core (4 cores per processor or per socket), but HP-UX licensing is per socket or per processor. Therefore, one per socket software license is required for each quad-core processor. The processor and the socket represent a processing unit, and includes 4 cores.
  • Page 15 NOTE: Use the getconf command or the confstr() call to obtain the unique identifiers. Do not use the uname -i command, which does not report unique IDs for nPartition systems. To guarantee compatibility on current and future platforms, use the interfaces to getconf(1) and confstr(3C) to retrieve unique machine identifiers.
  • Page 16 Example 1 Determining if an OS instance is running on Superdome 2 hardware Example 1 illustrates how the 'model' and 'getconf' commands can be used to determine whether an OS is running on Superdome 2 hardware. # /usr/bin/getconf MACHINE_MODEL ia64 hp Superdome2 16s # /usr/bin/model ia64 hp Superdome2 16s In both the examples, the presence of “Superdome 2”...
  • Page 17: Getting Started With Npartitions

    3 Getting started with nPartitions HP Superdome 2 with sx3000 processors uses c-Class technology for the architecture of the system. The HP Superdome 2 is managed by an OA with enhanced firmware. The OA has partitioning capabilities, both for hard partitions (nPartition) and for virtual partitions (vPar). You can manage the nPartitions and vPars through the OA without installing the software on any disk.
  • Page 18: Npartition Resources

    Table 2 nPartition Commands (continued) Command Description Configures partition configuration privilege for nPartitions and vPars . For more information, see help parperm parperm. NOTE: The parperm command is available only from the onboard administrator. Removes an existing nPartition. For more information, see help parremove. parremove Displays nPartition information and hardware details for a server complex.
  • Page 19: Assigned Or Unassigned Blades And I/o Bays

    [Blade] Enclosure/ Usage/ Memory Par Pending Blade Status* (GB) Num Deletion Indicted/ OK/ Next Deconf/ Indicted/ Boot Deconf ========== ======================= ========= =============== ==== === ======== Inactive Base /OK 8/0/0/8 128.0/0.0/0.0 Inactive Base /OK 8/0/0/8 128.0/0.0/0.0 Inactive Base /OK 8/0/0/8 128.0/0.0/0.0 Inactive Base /OK 8/0/0/8 128.0/0.0/0.0...
  • Page 20: Active And Inactive Blades

    Active and inactive blades Blades that are assigned to an nPartition and have been booted are active blades whose resources (processors, memory, and on-board I/O) can be actively used by software running in the nPartition. Blades that are Inactive are either not assigned to an nPartition (recognized by the empty Par Num field against the blades in the parstatus command output) or are assigned to an nPartition that is not yet powered on (partition status Inactive/DOWN in the parstatus command output).
  • Page 21: Partition Names

    Partition names Specifies the name of the nPartition. The parcreate —P name command is used to create an nPartition with a name associated with it. An nPartition name must have at least one of the following non-numeric characters: a-z, A-Z, dash (-), under-score (_), or period (.). An nPartition name with the same format as the default name can only be specified if the specified name matches the nPar number.
  • Page 22: Blade Resource Attributes

    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.
  • Page 23 user shuts down the nPartition, and adds 8 GB memory to that blade. When the nPartition is booted again, the blade has 16 GB of memory; so 8 GB (50%) is allocated as SLM. As an absolute number (default) ◦ This can also be optionally suffixed by "GB".
  • Page 24 parstatus -C [Blade] Enclosure/ Usage/ Memory Use On Pending Blade Status* (GB) Next Deletion Indicted/ Boot Deconf Indicted Deconf =============== ========== ============= ===== ===== ====== InActive Base/OK 8/0/0/8 16.0/0.0/0.0 Inactive Base/OK 8/0/0/8 16.0/0.0/0.0 D-Degraded I-Indicted parstatus -I [IO Bay] Enclosure/ Usage/ Par Pending IO Bay...
  • Page 25: Operating System Specific Default Values For Npartition Attributes

    ILM granule size at next boot : 1024 MB SLM granule size : 1024 MB SLM granule size at next boot : 1024 MB Max number of ILM granules possible : 1024 Max number of SLM granules possible : 1024 User Specified Max number of blades Max number of blades at next boot User Specified Max number of vpars...
  • Page 26: Partition State And Runstates

    ILM granule size : 1024 MB SLM granule size : 1024 MB : Enabled Partition State and RunStates Each nPartition has a State, and a RunState. The nPartition state indicates whether the nPartition has booted and represents the power state of nPartition. The nPartition runstate indicates the state of the nPartition with respect to OS instances.
  • Page 27 parstatus -P [Partition] Par State/ Status* # of # of ILM/ Partition Name Num RunState Blades IOBays SLM (first 15 (GB)** characters) === ======================= ======= ====== ====== ============= =============== Active /EFI 14.0/112.0 nPar0001 Inactive /DOWN 16.0/112.0 nPar0002 Active /RUN_VPARS 126.0/0.0 nPar0003 D-Degraded ** Actual allocated for Active and User requested for Inactive partitions...
  • Page 28: Partition Specifications (parspec)

    Table 3 RunStates for nPartition Runstate Description DOWN The partition is inactive and powered off. ACTIVATING A boot operation has been initiated for this partition. FWBOOT The boot process is in the firmware boot phase for this partition and the partition has transitioned into the active status.
  • Page 29: Creating A Partition Specification

    Creating a Partition specification You can create a parspec using the following command in the OA CLI: parcreate -C PartitionSpec:[:create_partition_flag] Where PartitionSpec is the name of the parspec to be created. The create_partition_flag can take the following values: ◦ y – the corresponding nPartition is created. ◦...
  • Page 30 Figure 3 Viewing Partitition Specification Information Getting started with nPartitions...
  • Page 31: Planning Npartitions

    4 Planning nPartitions This chapter describes how to plan nPartition configurations. It also describes the nPartition configuration requirements and recommendations. This chapter discusses the following topics: “Recommended HP Superdome 2 nPartition configurations” (page 31) “HP Superdome 2 Partitioning choices” (page 31) “Sample procedure for creating nPartitions”...
  • Page 32 Figure 4 Partition Rules — 32s Details on possible uses of the alternative loading options: The alternative two cell blade partition with cell blades in slots 7 and 8 in enclosure 1 (shown in the light blue) is provided to allow 2 3-blade partition and 1 2-blade partition to co-exist in the same enclosure.
  • Page 33 Figure 5 Partition Rules — 16s Alternative options are provided in the event that a smaller partition is combined with a larger partition. For example, if a 3 blade partition is the only thing loaded, the blades are loaded in slots 1, 3 and 5.
  • Page 34: Superdome 2 Cpu / Cpu Module Support

    Figure 6 Partition Rules — 8s NOTE: The loading rules for the SD2-8S are very similar to those for the SD2- 1 6s except that no partitions larger than 4 blades are supported. This is a firmware limitation imposed on the SD2-8s. However, as seen from the loading options, all 8 blade slots can be populated in a SD2-8s.
  • Page 35: Cpu Mixing Support

    CPU mixing support The following are the rules for mixing processors in Superdome 2: Mixing of processor families within an nPartition is not supported Processors running at different frequencies or different cache sizes within the same nPartition are not supported The processor modules on a blade must have the same revision, frequency, and cache size.
  • Page 36 [Enclosure] Enclosure Enclosure Num Enclosure Type Blades IOBays Slots Name ========= ========= ====== ====== ===== ========= Compute stanley [Blade] Enclosure/ Usage/ Memory Par Pending Blade Status* (GB) Num Deletion Indicted/ OK/ Next Deconf/ Indicted/ Boot Deconf ========== ======================= ========= =============== ==== === ======== Inactive Base /OK 8/0/0/8 32.0/0.0/0.0...
  • Page 37 [Partition] Par State/ Status* # of # of ILM/ Partition Name Num RunState Blades IOBays SLM (first 15 (GB)** characters) === ======================= ======= ====== ====== ============= =============== D-Degraded ** Actual allocated for Active and User requested for Inactive partitions Create an nPartition with one blade and one I/O bay using the following command: parcreate -P nPar0002 -a blade:1/2:::: -a io:5/1:: Command succeeded The following output is displayed:...
  • Page 38: Creating And Configuring Npartitions

    5 Creating and configuring nPartitions This chapter describes the procedure to create, configure, and manage nPartitions on the HP Superdome 2 server. This chapter discusses the following topics: “Tools for configuring nPartitions” (page 38) “Granting permission for an OS to manage nPartitions” (page 38) “Task summaries for creating and configuring nPartitions”...
  • Page 39: Task Summaries For Creating And Configuring Npartitions

    Task summaries for creating and configuring nPartitions Table 5 nPartition Boot and Reset Task Summaries Task Summary Partition Default Attributes (page 39). Create new nPartition (page 40). Verifying the nPartitions using CLI (page 41) Verifying the nPartitions using GUI (page 42).
  • Page 40: Creating A New Npartition

    Creating a new nPartition This section describes the procedure to create an nPartition using the OA CLI and the GUI. Creating a new nPartition using the OA CLI Use the parcreate command to create a new nPartition on HP Superdome 2. The command takes the specified blades and I/O bays and assigns them to the new nPartition.
  • Page 41: Verifying Newly Created Npartitions Using The Cli

    Verifying newly created nPartitions using the CLI To verify that the partitions are defined as desired, perform either of the following steps: The parstatus P command displays the summary data, as shown: parstatus -P [Partition] Par State/ Status* # of # of ILM/ Partition Name...
  • Page 42: Verifying Newly Created Npartitions Using The Oa Gui

    [Blade] Enclosure/ Usage/ Memory Par Pending Blade Status* (GB) Num Deletion Indicted/ OK/ Next Deconf/ Indicted/ Boot Deconf ========== ======================= ========= =============== ==== === ======== Active Base /OK 8/0/0/8 128.0/0.0/0.0 Active Base /OK 8/0/0/8 128.0/0.0/0.0 * D-Deconfigured I-Indicted [IOBay] Enclosure/ Usage/ Par Pending IOBay Status*...
  • Page 43: Removing (deleting) An Npartition Using The Oa Gui

    parspec and can be reused later. If the -Z option is specified, the command removes the current parspec when the nPartition is removed. To remove an nPartition, use the parremove command: parremove -p nPartition_id [-Z] [-F] For example: parremove -p 2 Removing (Deleting) an nPartition using the OA GUI To remove an inactive nPartition, select the check box corresponding to the nPartition name from the Complex nPartitions table, and then click Delete.
  • Page 44: Assigning Blades And I/o Bays To An Npartition Using The Oa Gui

    For more information, see the OA help, help parcreate and help parmodify . To add I/O bay 1 in enclosure 6 to the existing nPartition 2: parmodify -p 2 -a io:6/1: Assigning blades and I/O bays to an nPartition using the OA GUI To assign blades and I/O Bays to an nPartition using the OA GUI: Select the nPartition from the left navigation pane, and then click Modify nPartition.
  • Page 45: Removing Blades And I/o Bays From An Npartition

    Figure 10 IOX Resources Option Select the I/O bay. Click Apply to commit your configuration changes. To cancel an operation, navigate away from the Modify nPartition screen. The blades and I/O bay are assigned to the nPartition. Removing blades and I/O bays from an nPartition This section describes the procedure to unassign or remove blades and I/O bays from an nPartition.
  • Page 46: Removing Blades And I/o Bays From An Npartition Using The Oa Gui

    Removing blades and I/O bays from an nPartition using the OA GUI To unassign blades and I/O bays from an nPartition using the OA GUI: Select the nPartition from the left navigation pane, and then click modify nPartition. Expand the Blade Resources option. Figure 9 (page 44) shows the blade resource screen.
  • Page 47: Renaming A Server Complex

    Figure 12 IOX Resources Option Clear the I/O bay(s) that you want to unassign. Click Apply. The blades and I/O resources are unassigned from the nPartition. Renaming a server complex To rename a server complex using the CLI, run the following command from the OA: set complex name <complex name>...
  • Page 48: Setting Blade Attributes Using The Oa Cli

    Setting blade attributes using the OA CLI You can set the blade attributes using the parcreate or parmodify commands. For more information about the parcreate command, see help parcreate. For more information about the parmodify command, see help parmodify. For example: To add the blade in enclosure 1 slot 5 with non-default attributes to the existing nPartition nPar0001: parmodify -p nPar0001 -a blade:1/5:base:n:ri:50% The example overrides the default value for use_on_next_boot to n.
  • Page 49 Select the appropriate attributes. Click Apply. The blade attributes are set. Setting blade attributes...
  • Page 50: Booting And Resetting Partitions (npartitions And Vpars)

    6 Booting and resetting Partitions (nPartitions and vPars) This chapter introduces Partition system boot and reset concepts, configuration options, and procedures for booting and resetting Partitions. This chapter covers boot details for HP-UX 1 1i v3 operating system and the OA CLI and GUI. This chapter discusses the following topics: “Overview of Partition system booting”...
  • Page 51: Booting From The Cli

    Booting from the CLI To activate a partition from the command line, you can either use the poweron partition {identifier} command, the bo command, or the pe command. poweron partition 2 Poweron request sent to partition 2. Operation initiated successfully. Please run PARSTATUS/VPARSTATUS or SHOW SYSLOG OA to determine the completion status of the operation.
  • Page 52: Booting From The Gui

    The bo command without arguments prompts you to select a partition to boot: bo This command controls power enable to a partition. Partition Partition Number Name --------- --------- nPar0001 nPar0001:vPar1 nPar0001:vPar0002 nPar0001:we nPar0001:vPar0005 1:21 nPar0001:vPar0021 nPar0002 nPar0002:vPar0001 hard_partition nPar0004 nPar0005 Quit Select partition number:2:1 Poweron request sent to partition 2:1.
  • Page 53 Figure 15 nPartition Status Information Figure 16 vPar Status information Select the Virtual Devices tab, and then click on the Momentary Press button. Booting to UEFI and preparing for Operating System installation...
  • Page 54 Figure 17 nPartition Virtual Devices tab Figure 18 vPar Virtual Devices tab Navigate to the status tab to see the run state of the partition. Figure 19 Active/vPars Mode State of an nPartition Booting and resetting Partitions (nPartitions and vPars)
  • Page 55: Getting A Console Using The Cli

    Figure 20 Active/EFI prompt State of vPar Getting a Console using the CLI To access the system console of a partition using the command line, run the CO command. It can be used either with the partition’s ID or without it as shown: Partition Partition Number...
  • Page 56: Uefi I/o Device Connection Solution

    Figure 21 Remote Console Tab (nPar) Figure 22 Remote Console Tab (vPar) UEFI I/O device connection solution On platforms like Superdome 2, connecting all UEFI drivers to all the devices might take a very long time to complete, and this level of device connection is typically not needed. Similar to the sx2000 Superdome product, the default behavior on Superdome 2 does not force the connection of all UEFI I/O drivers to all devices.
  • Page 57: Device Connection Policies

    Figure 23 UEFI Front Page From the UEFI Shell, the ‘search’ command is available to manually connect devices in a specific I/O bay or even a specific I/O slot. Other device connection commands like ‘connect’ and ‘reconnect’ are also available from the UEFI Shell. Considering that device connection policies are retained in the default settings (see Device Connection Policies), in a second boot scenario (reset from UEFI or OS) with fast_init ON, I/O devices are not connected before displaying the UEFI Front Page.
  • Page 58: Confirming The Installed Io Cards

    I/O bay for the partition, and the boot option value. The expanded policy can be changed, if a user wants to reduce or increase the amount of devices connected when launching one of the UEFI user interfaces. NOTE: If the expanded policy is changed from the default, and the partition configuration is changed (Example: replace lowest numbered I/O bay), UEFI does not automatically update the policy to take into account the configuration change.
  • Page 59: Getting Mac Addresses For Ignite-ux

    PCI DEVICE INFORMATION Enc/ SubVendorID Bay/ Seg/ Dev/ VendorID/ SubSystemID Slot Func DeviceID RevisionID (dec) (hex) (hex) (hex) (hex) Description ------ ----- ----- --------- ------------ ----------- 1/2/1 05/00 00/00 103C/402F ----/----/11 Bridge Device - PCI/PCI bridge 1/2/2 05/00 02/00 103C/402F ----/----/11 Bridge Device - PCI/PCI bridge 1/2/3 00/08 00/00 103C/402F ----/----/11 Bridge Device - PCI/PCI bridge 1/2/4 04/00 00/00 103C/402F ----/----/11 Bridge Device - PCI/PCI bridge 1/2/4 04/01 00/00 14E4/1650 103C/7105/00 Network Controller - Ethernet control...
  • Page 60: Task Summaries For Rebooting And Resetting Partitions

    M 003 Mac(002655A9CA32) PcieRoot(0x3)/Pci(0x2,0x0)/Pci(0x0,0x0)/MAC(002655A9CA32,0x0) 004 Mac(002655A9CA36) PcieRoot(0x3)/Pci(0x2,0x0)/Pci(0x0,0x1)/MAC(002655A9CA36,0x0) Task Summaries for Rebooting and Resetting Partitions Table 6 describes the main nPartition boot and reset tasks and provides brief summaries and references for detailed procedures. You can perform the nPartition boot tasks in Table 6 (page 60) using either the OA CLI or the OA GUI.
  • Page 61: Poweroff Partition

    POWEROFF PARTITION From the CLI Command: POWEROFF PARTITION {{nPartition number or name} [:vPartition number or name] [FORCE] [OVERRIDE] | ALL [FORCE]} Description: Gracefully shuts down any OS running on the specified nPartition or vPar and brings it to an inactive state. The active blades and IO interconnects in the nPartition are powered off if the specified target is an nPartition.
  • Page 62 Figure 24 Status Information of an nPartition Figure 25 Status Information of a vPar Select the Virtual Devices tab. For force poweroff, click the Press and Hold button. For graceful poweroff, click the Momentary Press button. Booting and resetting Partitions (nPartitions and vPars)
  • Page 63 Figure 26 Graceful and Force Poweroff (nPartition) Figure 27 Graceful and Force Poweroff (vPar) Navigate to the status tab to see the run state of the partition. Task Summaries for Rebooting and Resetting Partitions...
  • Page 64: Poweron Partition

    NOTE: When an nPartition is active in vPars mode, the power operations require the OVERRIDE option to change the mode. POWERON PARTITION From the CLI Command: POWERON PARTITION {{nPartition number or name} [:vPartition number or name][OVERRIDE]} Description: If an nPartition is specified, this command powers on the blades and IO interconnects in the nPartition and boots the nPartition to EFI.
  • Page 65: Set Partition Dvd

    Access level/Bay level: OA Administrator, OA Operator Restriction: You must be connected to the monarch OA. From the GUI For information on rebooting the partition, see “From the GUI”. SET PARTITION DVD From the CLI Command: SET PARTITION DVD {CONNECT | DISCONNECT}{nPartition number or name}[:vPartition number or name] [ENCLOSURE {enclosure number}] Description: Connect or disconnect the specified partition from the specified URL or local enclosure DVD...
  • Page 66 Figure 28 Connecting an enclosure DVD to an nPartition Figure 29 Connecting an enclosure DVD to a vPar NOTE: A vPar can make a DVD/vmedia connection only if it owns the I/O slot 7 of a server blade (an assigned resource of the containing nPar). When you want to connect or disconnect DVD to a vpar, make sure that you have assigned I/O slot 7 (iLO slot) of a blade.
  • Page 67: Show Partition Dvd

    Figure 30 Virtual Media Screen NOTE: Each nPar or vPar has its own Virtual media applet window, servicing the virtual media connection. When there are multiple applet windows opened, switching back and forth between the partition pages and applet windows, the virtual media connection may get disconnected. You must reconnect the partition to the virtual media if you encounter this problem.
  • Page 68 Figure 31 SHOW Partition DVD for an nPartition Figure 32 SHOW Partition DVD for vPar Booting and resetting Partitions (nPartitions and vPars)
  • Page 69: Show Partition Info

    SHOW PARTITION INFO Command: SHOW PARTITION INFO {{nPartition number or name} [:vPartition name or number]|ALL} Description: Displays information about the specified partitions. Access level/Bay level: OA Administrator, OA Operator Restriction: You must be connected to the monarch OA. Force System Reset and Crash Dump (TOC) PARTITION From the CLI Command: TOC PARTITION {nPartition number or name}[:vPartition number or...
  • Page 70: Update Npartition

    Figure 33 TOC nPartition Figure 34 TOC vPar UPDATE NPARTITION IMPORTANT: This command is not available if you are using complex firmware that is earlier than the Online Firmware Update release. To update firmware for all partitions, see “UPDATE FIRMWARE” (page 72).
  • Page 71 monarch enclosure. This flash image is used to update the firmware for HP Superdome 2 cell blades within the specified partitions. ◦ The <uri> must be formatted as usb://<path> for USB installations. Use the SHOW USBKEY command to obtain the <path>. The supported protocols for network installations are HTTPS, HTTP, TFTP, and FTP.
  • Page 72: Update Show Npartition

    Figure 35 Firmware Summary Information UPDATE FIRMWARE Command: UPDATE FIRMWARE { <uri> } [ FORCE ] [ REINSTALL ] [ ALL ][ NOEXECUTE Description: Updates the Superdome system's firmware (except I/O firmware) Access level/Bay level: OA Administrator, OA Operator Restriction: You must be connected to the monarch OA.
  • Page 73: Hp Superdome 2 Boot Support

    To view Firmware Summary information, click the Firmware Summary link. Figure 36 Firmware Summary HP Superdome 2 Boot Support This section provides details of the accessories supported by HP Superdome 2 for booting purposes. The only supported local disk is fibre channel – P2000 FC G3 array. Up to 12 LFF or 24 SFF SAS HDDs per array (SATA is available but not supported) Expandable up to 149 HDDs Suggest dedicated (per partition) 15K drives in Raid 1 configuration for performance or...
  • Page 74: Local Boot

    Local Boot Up to 4 boot paths are supported per P2000 FC G3 array. P2000 FC G3 array can support up to two dual port array controllers Each controller supports up to two 8GB FC links Considerations for Local Boot Minimum configuration ◦...
  • Page 75: Npartition And Resource Health Status

    You must consider the following for a SAN boot: Dual paths to SAN/storage is recommended for all partitions Allows online updates of switch and array firmware ◦ Two hops or less is strongly recommended No factory installation of operating environment is available nPartition and vPar definition is available and is independent of the installation of an ◦...
  • Page 76 OEM Manufacturer: N/A Total number of partitions present: 0 [Enclosure] Enclosure Enclosure Num Enclosure Type Blades IOBays Slots Name ========= ========= ====== ====== ===== ========= Compute stanley [Blade] Enclosure/ Usage/ Memory Par Pending Blade Status* (GB) Num Deletion Indicted/ OK/ Next Deconf/ Indicted/...
  • Page 77: Viewing Partition And Resource Health Status Using The Oa Gui

    [Partition] Par State/ Status* # of # of ILM/ Partition Name Num RunState Blades IOBays SLM (first 15 (GB)** characters) === ======================= ======= ====== ====== ============= =============== D-Degraded ** Actual allocated for Active and User requested for Inactive partitions Viewing Partition and Resource Health Status Using the OA GUI To view the partition and resource health status using the OA GUI, select the nPartition from the left navigation pane.
  • Page 78 For an nPartition, blades and I/O bays are activated only if they are reported as healthy by the Health management subsystem on the OA. Additionally, there is also a user specified attribute “failure_usage” for a blade and I/O bay. You can set this attribute to indicate whether the partition to which the nPartition resource or blade or I/O bay is assigned should be activated or not if it is found faulty.
  • Page 79: Planning Your System For Virtual Partitions

    7 Planning Your System for Virtual Partitions Planning Your Virtual Partitions A virtual partition is created by specifying the resources needed for the vPar. The resources that can be assigned to a vPar are: CPU-cores - You must either specify the number of CPU-cores that are part of the vPar, or specify the resource paths of individual CPU-cores, or specify the socket resource paths and quantity from where the CPUs are to be assigned.
  • Page 80: Minimal Hardware Configuration

    Minimal Hardware Configuration Every bootable virtual partition must have at least: 1 CPU-core On HP Integrity Superdome 2, by default, a vPar is created with zero CPU-cores. Such a vPar cannot boot. System memory (sufficient for HP-UX and the applications in that partition) A boot disk (when using a mass storage unit, check your hardware manual to verify that it can support a boot disk) Although it is not required for booting a virtual partition, you can add a LAN card for networking.
  • Page 81: Cpu-core: Adding And Deleting By Total

    NOTE: On an HP Integrity Superdome 2 system, a vPar is created with zero CPUs by default. Therefore, the default cpu:::[min] value is zero. The default cpu::::[max] value is the total number of CPUs in the nPartition. The virtual partition must be in the “Down” state to set the minimum or maximum value. The total count of CPUs in the virtual partition must always be greater than or equal to min and less than or equal to max.
  • Page 82: Cpu-core: Adding Or Deleting By Socket Local Processor (slp)

    Example To create a virtual partition with 3 CPUs, set num to 3: vparcreate -N nParID -p vParID -a cpu::3 vparcreate -p nparID:vParID -a cpu::3 vparmodify With the vparmodify command, you can use: -a option to add num CPUs to the virtual partition, -d option to delete num CPUs from the virtual partition, -m option to modify (set) to num the number of CPUs assigned to the partition.
  • Page 83: Cpu-core: Adding Or Deleting By Resource Path

    Examples To create a virtual partition using 2 CPU-cores from socket 0 on blade 1: vparcreate -N <nPar name> -p <vPar name> -a socket:1/1/0:cpu::2 To increase the number of CPU-cores by 2 using the CPU-cores from socket 0 on blade 1: vparmodify -N <nPar name>...
  • Page 84: Deleting Cpu-cores Summary

    Deleting CPU-cores Summary If you want to control which CPU-core is deleted, use the same method—by SLP, by resource path, or by count-on your deletion command line that you used on your addition command line. CPU Allocation On HP Integrity Superdome 2, the parstatus command provides all the required CPU information from the OA without installing or booting to the nPar mode.
  • Page 85: Assigning Memory To A Vpar

    NOTE: The memory granules are not the actual memory DIMMs. You can specify the granularity for SLM and ILM separately. However, the following applies to both types of memory: Memory granularity is specified during the creation of nPartition. Any modification thereafter requires you to reboot the nPartition.
  • Page 86: Syntax, Rules, And Notes

    # ioscan -m resourcepath | grep 9/1/3 48/0/0/2/0/0 0x90001000203ff85 ioslot-9/1/3 To get the IO details, this result is used in a second call to ioscan. ioscan -kf -H 48/0/0/2/0 Class H/W Path Driver S/W State H/W Type Description ============================================================================ 48/0/0/2/0 PCItoPCI CLAIMED BUS_NEXUS...
  • Page 87: Counts Summary

    Table 9 Resource syntax summary Resource Forms Options # times/command cpu:cpu_path -a, -d Multiple cpu::num -a, -m, -d Once cpu:::{min}:{max} Once socket:socket_id:cpu::num -a, -d, -m Once per socket_id -- or -- core:core_path -a, -d Multiple core::num -a, -d, -m Once core:::{min}:{max} Once socket:socket_id:core::num...
  • Page 88 configuration to use the available healthy CPU-cores. The following are some of the cases where the partition controller may not allow the when parspec change policy is disabled: There is a deconfigured or deactivated CPU, which has been reserved for the partition as part of the total (cpu::num) request and partition controller does not have any free CPUs with which to replace it.
  • Page 89: Managing And Booting Virtual Partitions

    8 Managing and Booting Virtual Partitions This chapter addresses the following topics: “Modes: Switching between nPars and vPars Modes ” (page 89) “Managing: Creating a Virtual Partition” (page 93) “Booting a Virtual Partition” (page 93) ◦ ◦ “Managing: Modifying Attributes of a Virtual Partition” (page 94) ◦...
  • Page 90 Figure 38 Setting mode using the OA GUI Managing and Booting Virtual Partitions...
  • Page 91: Setting The Mode Using The Oa Cli

    Setting the mode using the OA CLI parmodify -p <npar_name> [-N] next_boot_mode where: has the value of either vPars or nPars next_boot_mode Specifies whether the nPartition has to be booted as a single partition (nPars mode) capable of running only a single operating system (OS) instance or as one or more virtual partitions (vPars mode) as defined in the virtual partition database in the partition specification, each capable of running its own OS instance.
  • Page 92: Getting The Vpar Console

    Figure 39 Booting vPar from the GUI Getting the vPar Console You can use either the command line or the GUI to access the system console of the virtual partition. From the CLI Use the co command with or without the partition ID. Example 5 Example Partition Partition...
  • Page 93: Managing: Creating A Virtual Partition

    Figure 40 Remote Console NOTE: On HP Integrity Superdome 2, vpmon is not supported. If you attempt booting vpmon from the ISL prompt the following error message is displayed: ERROR: Unsupported boot environment for vpar monitor! Booting vpmon not supported on this platform Resetting the system! Managing: Creating a Virtual Partition You can create a virtual partition using the vparcreate command.
  • Page 94: Managing: Modifying Attributes Of A Virtual Partition

    Booting from the CLI To set the vPars environment, you must set the nPartition into vPars mode so that the next nPartition boot allows you to boot into vPars mode. To set the nPartition mode: Set the nPartition in vPar mode. # parmodify p <npar_name>...
  • Page 95: Commands: Displaying Vpars Resource Information (vparstatus)

    To delete 1 GB of Socket Local Memory on enclosure 1, blade 2, socket 0 from the same virtual partition: vparmodify -N nPar0001 -p vPar0001 -d socket:1/2/0:mem::1024 To add the I/O card in IOX 6, I/O bay 2, slot 3 to the virtual partition (io and ioslot syntax): vparmodify -N nPar0001 -p vPar0001 -a io:6/2/0/0/2 vparmodify -N nPar0001 -p vPar0001 -a ioslot:6/2/3 Commands: Displaying vPars Resource Information (vparstatus)
  • Page 96: Vparstatus: Summary Information

    Table 1 1 RunStates of an active Virtual Partition (continued) State Description DEACTIVATING This run-state is displayed while a shutdown/reboot of a virtual partition is being processed. RESETTING This run-state is displayed while a reset of a virtual partition is being processed. An MCA occurred in the virtual partition and is being processed.
  • Page 97 nPartition name: nPar0001 Current boot mode: vpars Next boot mode: vpars To display the detailed attributes and resources of vpar1 in machine-readable format: vparstatus -M -p1:1 vPar0001;1:DOWN;Inactive::::0/8;;;;;0;6;:6/2/0/0/2;6/2/3:;4096;;;4096;1024;;;;1024:N/A;N/A;N/A:N:1;nPar0001;vpars;vpars To display the CPU-core configuration information: vparstatus -d -N 1 Config Assigned to Sibling Information path Status Num Name...
  • Page 98: Shutting Down Or Rebooting A Virtual Partition

    vparstatus -r Partition Management Software Revision: 1.0 For details on the state and run-state of the virtual partition, see “Virtual Partition States” (page 95). NOTE: The information about the configured vPars in the SD2 complex can be obtained from the OA irrespective of the runstate of the nPartition or the vPars. You can use the vparstatus -N <nParId>...
  • Page 99: Shutting Down All Virtual Partitions

    NOTE: This is a graceful shutdown and allows the OS to transition through the shutdown process. To poweroff a virtual partition from the OA prompt, do one of the following: For graceful shutdown type: ◦ poweroff partition 1:1 ◦ For ungraceful shutdown (required whenever the partition is at the UEFI prompt) type: poweroff partition 1:1 force To reset a virtual partition invoked from the OA: vparreset -f -N 1 -p 1...
  • Page 100: Boot Options Management For Partitions

    # vparstatus -N 1 # shutdown -h After the virtual partition is in the down state, remove the virtual partition vPar0001: vparremove -N nPar0001 -p vPar0001 -f CAUTION: Involuntary use of this command leads to unforeseen consequences. Therefore, you must confirm the operation with the -f (force) option. Boot options management for partitions On HP Superdome 2 servers, each virtual partition has its own instance of UEFI.
  • Page 101: Installing Or Removing The Vpars Product From The Os

    9 Installing or Removing the vPars product from the OS This chapter addresses the following topics: Before You Install the vPars Software “Installing vPars” (page 101) “Bundle Names” (page 103) “Ignite-UX Cookbook” (page 103) “Removing the vPars Product” (page 103) Before You Install the vPars Software You must have a complete understanding of vPars before attempting installation.
  • Page 102 Installing through a Network with non-directed LAN boot (using an Ignite server). Requires boot server to respond to client request. Enter lanboot select at the UEFI shell. Select the desired LAN, for example, 01. Wait for the boot server to reply, and load the boot file (For Example: nbp.efi), then choose the operating system you want to install.
  • Page 103: Bundle Names

    Installing a vPar is similar to installing an nPar. For the next steps on vPars product installation on HP-UX, see the HP-UX Installation and Update Guide at: To disconnect the DVD drive, use the set partition dvd disconnect npar:vpar command.
  • Page 104: 10 Support And Other Resources

    10 Support and other resources Contacting HP Before you contact HP Be sure to have the following information available before you call contact HP: Technical support registration number (if applicable) Product serial number Product model name and number Product identification number Applicable error message Add-on boards or hardware Third-party hardware or software...
  • Page 105: Typographic Conventions

    Table 12 Documentation and its location Documents Website HP Superdome 2 Onboard Administrator User Guide lang=en&cc=us&prodTypeId=15351&prodCatId=321933 HP Superdome 2 Onboard Administrator Command Line Interface User Guide Virtual Partition documentation HP-UX System documentation Partition commands Partition Management Techniques for HP Superdome 2 Typographic conventions...
  • Page 106 IMPORTANT This alert provides essential information to explain a concept or to complete a task NOTE A note contains additional information to emphasize or supplement important points of the main text. 106 Support and other resources...
  • Page 107: A Partition Commands

    A Partition commands This appendix contains a summary of the Partition commands and descriptions of their use. Table 13 Partition Commands Descriptions Command Description Creates a new nPartition. parcreate Displays or changes default values of certain nPartition attributes. pardefault Modifies an existing nPartition. parmodify Configure partition configuration privilege for nPartitions and vPars.
  • Page 108: Glossary

    Glossary assignable The resources that a customer can designate to be assigned to a partition. resource Blade A board that contains CPUs, memory, slots for C-class mezzanine cards, and onboard NICs. A blade is the equivalent of a cell in terms of being the unit of assignment for defining nPartitions. complex A collection of blade enclosures and IOXs cabled together and under the control of a single active, monarch OA (ignoring OA failures).
  • Page 109: Index

    Index creating, example plan, adding cpu to a partition, I/O, attributes, minimal hardware configuration, modifying attributes of, names of, boot processor, obtaining information about, booting removing, one partition, removing cpu resources, rebooting a partition, states of, Partitions product manpages, commands planning partitions, HP-UX shell commands setboot,...
  • Page 110 vparenv, vparmodify cpu, 80, 81, 82, vparstatus, 1 10 Index...

Comments to this Manuals

Symbols: 0
Latest comments: