HPE Superdome Flex Server Partitioning Guide

Part Number: 10-200002-Q222

Published: April 2022
Edition: 7
HPE Superdome Flex Server Partitioning Guide
Abstract
Partition configurations and procedures for HPE Superdome Flex Server.
Part Number: 10-200002-Q222
Published: April 2022
Edition: 7

© Copyright 2018-2022 Hewlett Packard Enterprise Development LP

Notices
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise 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. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained
herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR
12.211 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.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is
not responsible for information outside the Hewlett Packard Enterprise website.

Acknowledgments
Intel ®, Xeon ®, and Optane ™ are trademarks of Intel Corporation in the U.S. and other countries.
Redfish ® is a trademark of Distributed Management Task Force, Inc.
Microsoft ® and Windows ® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Java® and Oracle® are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

Revision history

Part number Publication date Edition Summary of changes

10-200002-Q222 March 2022 7 Updated Creating an nPartition and Modifying an nPartition.

10-200002-Q122 October 2021 6 Updated Creating an nPartition, Modifying an nPartition, and
Viewing nPartition details.
P07051-005 October 2020 5 Added support for special 8-chassis partition configurations.

P07051-004 December 2019 4

P07051-003 August 2019 3 Revised partition boot options for clarity

Minor editorial updates

P07051-002 May 2019 2 Added checklist for nPartition hardware requirements

Added an example of an nPartition configuration
Revised information on partitionable and nonpartitionable
systems
Updated nPartition creation and management procedures

P07051-001 August 2018 1 Initial release

 Table of contents

1 Overview of Superdome Flex Server partitions

1.1 Features of Superdome Flex Server partitions
1.2 Software licensing using Superdome Flex Server partitions
2 Requirements for Superdome Flex Server partitions
2.1 Checklist: Verifying nPartition hardware requirements
2.2 Standard nPartition configuration guidelines
2.3 Chassis and RMC location requirements
2.4 Supported standard nPartition configurations
2.5 Example of a standard nPartition configuration
3 Creating and managing nPartitions in a Superdome Flex server
3.1 Creating an nPartition
3.2 Modifying an nPartition
3.3 Removing an nPartition
3.4 Saving and restoring nPartition configuration
3.5 Viewing nPartition details
3.6 Viewing Superdome Flex Server complex details
3.7 Connecting to an nPartition
3.8 Controlling nPartition power and reset
3.9 Rebooting an nPartition
3.9.1 Partition boot options
4 Special eight-chassis nPartition configurations
4.1 Supported special eight-chassis system nPartition configurations
5 HPE Persistent Memory on HPE Superdome Flex Server
6 Websites
7 Support and other resources
7.1 Accessing Hewlett Packard Enterprise Support
7.2 Accessing updates
7.3 Remote support
7.4 Customer self repair
7.5 Warranty information
7.6 Regulatory information
7.7 Documentation feedback
Overview of Superdome Flex Server partitions
HPE Superdome Flex Server supports HPE nPartition configurations.
The following image shows the chassis numbering and fabric zones for a partitionable Superdome Flex Server single rack complex
containing eight chassis.

Figure 1: Partitionable single rack chassis numbering and fabric zones

Item Description

A Lower fabric zone

B Upper fabric zone (not present if the complex contains four or fewer chassis)

Overview of Superdome Flex Server partitions 5

A Superdome Flex Server complex is a set of hardware designed and delivered as a complete standalone system, managed by a single
management subsystem. A complex is made up of all the chassis connected to a Rack Management Controller (RMC) in Superdome Flex
Server.
An nPartition is a set of Superdome Flex Server chassis defined to work together to form a single computer system, capable of running a
bare metal OS. It is electrically isolated from other nPartitions in the complex.
A fabric zone is the set of chassis cabled together by Superdome Flex Grid. It is possible to have multiple fabric zones in one Superdome
Flex Server complex. However, only particular correct configurations are supported.
Once created, an nPartition behaves as an independent server, and can also be managed as an independent server. It has its own console
for OS and can be independently reset and power-cycled. The RMC manages all nPartitions in the complex and management access
remains the same as nPartitions are created, modified, or deleted.

Nonpartitionable systems
NOTE:
The information in this guide is not applicable to nonpartitionable systems.

nPartitions are inherent in the architecture of Superdome Flex Server systems. A monolith, single system version of Superdome Flex
Server (a Base Chassis plus zero or more Expansion Chassis ) will show that it has one nPartition defined, consisting of all the chassis in
the complex. Those systems only support a single configuration of one monolithic nPartition.
Note that a monolith (nonpartitionable) system contains all Superdome Flex Server chassis in a single nPartition but is not capable of
being divided into nPartitions. A monolith (nonpartitionable) system uses different chassis and cabling configurations that do not
support any other nPartition configurations.

Overview of Superdome Flex Server partitions 6

Features of Superdome Flex Server partitions
A Superdome Flex Server complex contains one or more Superdome Flex Server chassis in a rack that each contain individual compute,
memory, networking, and storage resources. An nPartition is created and managed using the Rack Management Controller (RMC).
There are three types of Superdome Flex Server chassis:
Base Chassis
A chassis that includes BaseIO in the hardware that provides drive bays, network ports, and USB ports. Each partitionable or
nonpartitionable server is required to have a single Base Chassis. It must be placed in the lowest U-position in the rack, and it must
always contain BaseIO. HPE tracks warranty of your server against this chassis.
Partitionable Chassis
An add-on chassis to scale-up the capacity of a partitionable system. Each additional nPartition after the first requires at least one
Partitionable Chassis. Each partitionable chassis add compute resources plus BaseIO features for booting an nPartition. Once
installed, Partitionable Chassis may be flexibly grouped to create multiple nPartitions within the system without recabling.
Expansion Chassis
An add-on chassis to scale-up the capacity of a nonpartitionable system. Expansion Chassis adds more compute capacity but no
BaseIO features. This chassis cannot host a new nPartition, but can be converted to a Partitionable Chassis with additional
hardware and cabling.
Each nPartition contains one or more chassis, and the chassis in the nPartition located in the lowest U-position in the rack is called the
monarch chassis for that nPartition. The monarch must be a Base Chassis or Partitionable Chassis type. Additional chassis assigned to
the nPartition must be in the same fabric zone as the monarch. Supported configurations require that all chassis in an nPartition are
adjacent.
A partitionable Superdome Flex Server complex can consist of one or more fabric zones. Each fabric zone consists of four chassis
interconnected with Flex Grid cables.
A nonpartitionable Superdome Flex Server complex consists of a Base Chassis and one to seven Expansion Chassis in a single fabric zone.
Reconfiguring nPartitions, or defining more than one nPartition is not supported in a nonpartitionable Superdome Flex Server.

More information
Requirements for Superdome Flex Server partitions

Features of Superdome Flex Server partitions 7

Software licensing using Superdome Flex Server partitions
For software licensing, each nPartition is assigned a universally unique identifier (UUID) and uses the serial number of the nPartition
monarch chassis. The UUID is created based on system information including the system serial number and nPartition number.

NOTE:
No additional hardware licensing is required to configure an nPartition on a Superdome Flex Server. nPartition support
is dependent on meeting the hardware requirements for chassis in a Superdome Flex system.

More information
Requirements for Superdome Flex Server partitions

Software licensing using Superdome Flex Server partitions 8

Requirements for Superdome Flex Server partitions
Partitions on Superdome Flex Server must meet specific hardware requirements, requirements for chassis locations in a rack, and be
configured with a supported combination of chassis.

More information
Standard nPartition configuration guidelines
Special eight-chassis nPartition configurations

Requirements for Superdome Flex Server partitions 9

Checklist: Verifying nPartition hardware requirements
To support nPartitions, HPE Superdome Flex Server hardware must meet the following requirements.
Procedure

Systems with Intel Xeon 61xx and 81xx (Skylake) processors have firmware version 2.5.x or later.

Systems with Intel Xeon 62xx and 82xx (Cascade Lake) processors have firmware version 3.0.x or later.

Every socket in an nPartition uses the same processor model.

Every chassis in an nPartition has the same DIMM configuration.

All chassis in an nPartition contain the same model of Superdome Flex ASIC board.

In each nPartition, the chassis that is located in the lowest U-position in the rack is a Base Chassis (has BaseIO).

The Superdome Flex Grid cables are configured appropriately to support a partitionable server. (Normally cables are configured
during Superdome Flex Server hardware installation.)

An RMC (not an eRMC) is used for managing the Superdome Flex Server complex.

For standard nPartition configurations, all chassis in an nPartition are in the same fabric zone.

Each fabric zone has a minimum of one nPartition and a maximum of four nPartitions.

All chassis in an nPartition are in adjacent rack locations.

Checklist: Verifying nPartition hardware requirements 10

Standard nPartition configuration guidelines
A single chassis contains four sockets and can only be included in a single nPartition. The supported standard nPartition sizes are:
Four socket (4S)

Eight socket (8S)

Twelve socket (12S)

Sixteen socket (16S)

Superdome Flex Server systems can contain different nPartition configurations, depending on the number of chassis included in the
system.
When creating an nPartition, the following rules apply:

Each nPartition must meet all hardware configuration requirements provided in the checklist.

Do not put a larger nPartition on top of a smaller nPartition. That is, do not create an nPartition that contains more chassis than an
nPartition below it in the rack.

More information
Special eight-chassis nPartition configurations

Standard nPartition configuration guidelines 11

Chassis and RMC location requirements
The rack must have open space for all chassis and the RMC. The following table lists the standard chassis and RMC locations supported
for service, cabling, and installation. Figure 2: Rack positions for systems with one, two, three, and eight chassis shows examples of some
of the supported chassis installations.

12
Number of chassis Base Chassis location Other chassis locations RMC location

1 U11 None U16

2 U06 U11 U16
3 U01 U06, U11 U16
4 U01 U06, U11, U16 U21
5 U01 U06, U11, U16, U23 U21
6 U01 U06, U11, U16, U23, U28 U21
7 U01 U06, U11, U16, U23, U28, U33 U21
8 U01 U06, U11, U16, U23, U28, U33, U21
U38

1
2 An RMC is required in partitionable systems.
In 1-chassis and 2-chassis nonpartitionable configuration, the RMC can be omitted. The Base Chassis BMC will provide eRMC
functionality with the same features as RMC, but nPartitioning is not supported.

Figure 2: Rack positions for systems with one, two, three, and eight chassis

NOTE: By default, RMC commands report any issues with chassis and cable locations based on the factory-standard
locations.
For custom installations that do not use the factory-standard locations, you must configure the custom RMC, eRMC, and
chassis locations by using the add location command.

Chassis and RMC location requirements 12

Supported standard nPartition configurations
The supported standard configurations for one to six chassis are shown in One to six chassis nPartition configurations .
The supported standard nPartition configurations for seven to eight chassis are shown in Seven to eight chassis nPartition
configurations.
Each nPartition uses the same color and number to indicate which chassis are included in the nPartition.

Figure 3: One to six chassis standard nPartition configurations

Figure 4: Seven to eight chassis standard nPartition configurations

Supported standard nPartition configurations 13

More information
Checklist: Verifying nPartition hardware requirements

Supported standard nPartition configurations 14

Example of a standard nPartition configuration
Figure 5: Six chassis complex with two nPartitions shows a six chassis system configured with two nPartitions and a single unassigned
chassis. The right side of the illustration shows how each partition combines the resources of each included chassis.

Figure 5: Six chassis complex with two nPartitions

In this example, chassis 1, 2, and 3 are all part of a single nPartition. The nPartition includes all the processor, memory, and I/O resources
in each chassis.
Chassis 5 and 6 are part of a second nPartition, and chassis 4 is not currently included in any nPartition.
Chassis 4 can be used to create an nPartition by itself following nPartition guidelines, or can be assigned to the nPartition including
chassis 1, 2, and 3.
Chassis 4 cannot be assigned to the nPartition including chassis 5 and 6 because chassis 4 is in the lower fabric zone and chassis 5 and 6
Example of a standard nPartition configuration 15
are in the upper fabric zone. For standard nPartition configurations, an nPartition may not span fabric zones.

More information
Checklist: Verifying nPartition hardware requirements

Example of a standard nPartition configuration 16

Creating and managing nPartitions in a Superdome Flex server
You use the RMC to perform the tasks for creating and managing nPartitions.
For more information on accessing the RMC, see HPE Superdome Flex Server User Guide .

Creating and managing nPartitions in a Superdome Flex server 17

Creating an nPartition
An nPartition is composed of one or more chassis included in a Superdome Flex Server complex. All chassis included in the nPartition
must meet hardware requirements.
For more information, enter the command help create npar .
Prerequisites

Chassis must be powered down before they can be added to an nPartition.

Chassis must be unassigned from any existing nPartition before they can be added to a new nPartition, unless the default or
all option is used.

Chassis must meet all hardware requirements.

Procedure

1. Determine which chassis to include in the nPartition.

2. Obtain the GEOID for each chassis to include in the nPartition by using the show complex command.

The GEOID identifies the rack number and the chassis U position within the rack.

For example, GEOID r001i06b identifies the chassis in rack number 1 with U position 6.

3. Enter the command create npar and use the chassis option to specify the chassis to include in the nPartition.

The all option assigns all chassis in a single fabric zone to a single nPartition. All existing nPartitions are removed when this
option is used.

NOTE:
The all option fails if used in a complex with multiple fabric zones. When the all is used, no other
chassis options are allowed.

The unassigned option assigns all chassis in the fabric zone not already included in an nPartition.

NOTE:
The unassigned option fails if used in a complex with multiple fabric zones. When the unassigned
option is used, no other chassis options are allowed.

create npar pnum=PARTITION_ID [hthread={on,off}] [ras={on,hpc}] [memrefreshrate={x1,x2}]

[pmem_auto_fwu={on,off,matchbios}][secure_boot={on,off}] [boot_slots={none,3,5,8}]
chassis={GEOID [GEOID ...],all,unassigned}

For more information about the create npar command, see HPE Superdome Flex Server Administration Guide .

a. NOTE:

create npar default

create npar pnum=PARTITION_ID chassis=all

These commands remove any existing nPartition configuration. It is unnecessary for chassis to be unassigned
before using these options.

To create an nPartition containing all the available chassis in a fabric zone, enter the command create npar default . If
unassigned chassis are available in more than one fabric zone, a single nPartition is created in each fabric zone containing
unassigned chassis.

For example, in a eight chassis system with all chassis unassigned, using the create npar default command creates two
nPartitions each containing four chassis.

4. You may view details of the newly created partition by entering the show npar or show npar verbose command.

More information

Creating an nPartition 18
Requirements for Superdome Flex Server partitions

Creating an nPartition 19
Modifying an nPartition
An existing nPartition can be modified to add or remove additional chassis.
Prerequisites
To modify an nPartition by adding a chassis:

An nPartition must be powered down before it can be modified.

The chassis must be powered off.

The chassis cannot be assigned to another nPartition.

The chassis must comply with all hardware requirements.

Procedure

1. Determine which chassis to add or remove from the existing nPartition.

2. Obtain the GEOID of the chassis to add or remove by using the show complex command.

3. Enter the command modify npar .

modify npar pnum=PARTITION_ID [hthread={on,off}] [memrefreshrate={x1,x2}] [pmem_auto_fwu=

{on,off,matchbios}] [ras={on,hpc}]
[secure_boot={on,off}] [boot_slots={none,3,5,8}] [add_chassis={GEOID [GEOID ...],unassigned}]
[remove_chassis=GEOID [GEOID ...]]

To add one or more chassis to the specified nPartition, use the add_chassis argument.

To remove one or more chassis from the specified partition, use the remove_chassis argument. A removed chassis
automatically becomes unassigned.

NOTE:
For more information, enter the command help modify npar .

4. You may view details of the modified partition by entering the show npar or show npar verbose command.

More information
Requirements for Superdome Flex Server partitions

Modifying an nPartition 20
Removing an nPartition
An existing nPartition can be removed to reassign chassis included in the removed nPartition to another nPartition. All chassis included
in the nPartition will be considered unassigned.

IMPORTANT:
Removing an nPartition cannot be undone.
Before removing an nPartition, you can preserve the nPartition configuration by using the RMC upload npar
config command.

Prerequisites
The nPartition must be powered down before it can be removed.
Procedure

1. Enter the command show npar to determine which nPartition to remove.

2. Enter the command remove npar .

remove npar pnum=PARTITION_ID

NOTE:
For more information, enter the command help remove npar .

More information
Saving and restoring nPartition configuration

Removing an nPartition 21
Saving and restoring nPartition configuration
The current configuration of nPartitions in a Superdome Flex Server complex can be saved to a file and uploaded to a local computer. The
configuration file can be downloaded to the RMC to restore the saved nPartition configuration for the same complex.

NOTE:
A saved nPartition configuration created by a Superdome Flex Server complex cannot be used to restore a nPartition
configuration in a different complex.

Prerequisites

A target computer for upload or download must be accessible on the local network using sftp or scp .

All nPartitions must be powered down before an nPartition configuration file can be restored.

All nPartitions must be removed before an nPartition configuration file can be restored.

Procedure

1. To save the current nPartition configuration, enter the command upload npar config or save npar config .

upload npar config (url=URL | file=FILENAME)

save npar config (url=URL | file=FILENAME)

The URL is the full file path to a local computer, using sftp or scp . If no URL is specified, the configuration file is saved
on the RMC.

The following examples show the supported formats:

sftp://user@localhost/path

scp://user@localhost/path

The FILENAME is the filename of the configuration file created. It is automatically appended with a .npar suffix.

For example, the command upload npar config file=xyz creates a configuration file with the filename
xyz.npar on the RMC.

For more information about the upload npar config or save npar config commands, see HPE Superdome Flex
Server Administration Guide .

2. To restore a saved nPartition configuration, enter the command download npar config .

download npar config (url=URL | file=FILENAME)

The URL is the full file path to a local computer, using sftp or scp . If no URL is specified, the command uses a
configuration file on the RMC.

The following examples show the supported formats:

sftp://user@localhost/path

scp://user@localhost/path

The FILENAME is the filename of the configuration file to download and restore.

For more information about the download npar config command, see HPE Superdome Flex Server Administration Guide .

Saving and restoring nPartition configuration 22

Viewing nPartition details
Information about an individual nPartition can be viewed using the RMC.
Procedure

1. Determine the nPartition to view.

2. Enter the command show npar .

show npar [pnum=PARTITION_ID] [verbose]

Sample output:

RMC cli>
show npar pnum=2

Partitions: 1

Par Run Health Chassis CPUs CPU Cores DIMMs Memory (GiB) IO Cards
Num State Status OK/In OK/In OK/In OK/In RAM/PMem OK/In
==== ========== ========== ======= ===== ========= ======= ============ ========
p2 Off OK 1/1 4/4 1536/1536 48/48 1535/0 0/0

* OK/In = OK/Installed

3. To view information about each configured nPartition, enter the command show npar without any partition ID.

4. To view detailed information about each configured nPartition, enter the command show npar verbose without any partition
ID.

Sample output:

cli>
show npar verbose

This system is nPartition capable

Partitions: 1

Partition 2:
Run State : Off
Health Status : OK
Chassis OK/In : 1/1
CPUs OK/In : 4/4
Cores OK/In : 112/112
DIMMs OK/In : 48/48
IO Cards OK/In : 0/0
Hyper-Threading : On
RAS : On
Boot Chassis : r001i11b
Boot Slots : 3,5
Secure Boot : Off
Memory Refresh Rate : Refreshx1
Memory Refresh Rate Next : Refreshx1
PCH SATA Interface Mode : RAID
PCH SATA Interface Mode Next : RAID
Secure Boot Next : Off
Volatile Memory : 1535 GiB
Persistent Memory : 0 GiB

* OK/In = OK/Installed

NOTE:

Viewing nPartition details 23

For more information, enter the command help show npar .

Viewing nPartition details 24

Viewing Superdome Flex Server complex details
Information about the Superdome Flex Server complex can be viewed using the RMC.
Procedure
Enter the command show complex .

show complex

Sample output:
cli>
show complex

This system is nPartition capable

SSN: 5UF7123456

RMCs: 1
r001i21c RMC-UV400

BMCs: 4
r001i01b IP147-BASEIO P001
r001i06b IP147-BASEIO P001 BASEIO-DISABLED
r001i11b IP147-BASEIO P002
r001i16b IP147-BASEIO ---- BASEIO-DISABLED

Partitions: 2
partition001 BMCs: 2
r001i01b
r001i06b
partition002 BMCs: 1
r001i11b
unassigned BMCs: 1
r001i16b

NOTE:
For more information, enter the command help show complex .

Viewing Superdome Flex Server complex details 25

Connecting to an nPartition
You can initiate a console session to an individual nPartition to perform maintenance functions.
Procedure

1. Determine the nPartition to connect with a console session by using the show complex command.

2. Enter the command connect npar and specify the partition ID.

connect npar pnum=PARTITION_ID [clear] [full] [nocache] [notty] [kill] [spy | steal]

clear - Clear cached output

full - Full output (default is since last reset)

nocache - Do not return cached output

notty - Disables tty interventions

kill - Kill all other uvcon sessions

spy - Connect to the console in read-only mode

steal - Connect to nPartition console in read/write mode by forcing previous read/write console user to read-only

NOTE:
For more information, enter the command help connect .

3. To disconnect, press
ctrl- ] q
.

Connecting to an nPartition 26
Controlling nPartition power and reset
An individual nPartition can be powered on or powered off. Power can be reset on an individual nPartition. Boot options can be specified
after reset.
For more information, enter the command help power .
Procedure

1. Determine the nPartition to power on, power off, reset, or cycle.

2. To power on an nPartition:

a. If you want to specify a boot option, use the bootopt argument.

b. Enter the command power on npar .

power on npar pnum=PARTITION_ID [bootopt=BOOTOPT]

3. To power off an nPartition, enter the command power off npar . This command performs a graceful OS shutdown and then
removes power from the specified nPartition with no user confirmation. If force is specified, the command performs an OS
immediate (non-graceful) shutdown instead.

power off npar pnum=PARTITION_ID [force]

4. To restart an nPartition:

a. If you want to specify a boot option, use the bootopt argument.

b. Enter the command power reset npar . This command performs a graceful OS shutdown then restarts the specified
nPartition. If force is specified, it performs an OS immediate (non-graceful) shutdown instead. This command is invalid if
power is off; you must use power on npar instead.

power reset npar pnum=PARTITION_ID [bootopt=BOOTOPT] [force]

5. To cycle power on an nPartition:

a. If you want to specify a boot option, use the bootopt argument.

b. Enter the command power cycle npar . This command performs an OS immediate (non-graceful) shutdown and
momentarily removes power from the specified nPartition. Then the command turns on partition power and starts the nPartition.
If force is specified, no user confirmation occurs.

power cycle npar pnum=PARTITION_ID [bootopt=BOOTOPT] [force]

NOTE:
For more information about power commands, see HPE Superdome Flex Server Administration Guide .

More information
Partition boot options

Controlling nPartition power and reset 27

Rebooting an nPartition
An nPartition can be rebooted without impacting other configured partitions in the complex.
Procedure

1. Determine the nPartition to be rebooted.

2. To reboot the nPartition:

a. To specify boot options, use the bootopt argument.

b. Enter the command reboot npar . This command performs an OS graceful shutdown, then restarts the specified nPartition.
If force is specified, the command instead performs an OS immediate (nongraceful) shutdown. This command is invalid if
power is off. Use the power on npar command instead.

reboot npar pnum=PARTITION_ID [bootopt=BOOTOPT] [force]

NOTE:
For more information on the reboot command, see HPE Superdome Flex Server Administration Guide .

More information
Partition boot options

Rebooting an nPartition 28
Partition boot options
The following boot options are available:
None - No boot option specified. Boots from default source.

no_oprom - One time boot option that causes UEFI to boot without loading the default option ROMs.

BiosSetup - Boot to BIOS setup.

Cd - Boot from existing UEFI boot option entries that correspond to CD/DVD drives of any connection type (such as SATA and USB).

Hdd - Boot from existing UEFI boot option entries that correspond to local hard disk drives, excluding USB drives.

Pxe - Boot from existing UEFI boot option entries that correspond to PXE.

RemoteDrive - Boot from existing UEFI boot option entries that correspond to remote (FibreChannel or iSCSI) hard disk drives.

SDCard - Boot from existing UEFI boot option entries that correspond to SD cards.

Shell or UefiShell - Boot to UEFI Shell.

UefiHttp - Boot from existing UEFI boot option entries that correspond to HTTP boot.

Usb - Boot from existing UEFI boot option entries that correspond to USB disk drives.

Partition boot options 29

Special eight-chassis nPartition configurations

CAUTION:
Hewlett Packard Enterprise supports special eight-chassis partitionable Superdome Flex Server configurations by
special customer order only. These special configurations may have nPartition sizes as large as eight chassis. Some
special, nonstandard configurations are supported, and special eight-chassis Superdome Flex Grid cabling is required.

All systems, both standard and special configurations, must meet the same set of nPartition hardware requirements.
By special customer order, the eight-chassis partitionable Superdome Flex Server configurations are allowed with the following
configuration restrictions:
Only eight-chassis Superdome Flex Server systems, with special cabling, are allowed.

Smaller partitionable systems of seven, six, or five chassis are not supported. Four-chassis and smaller partitionable systems are only
supported as standard nPartition configurations.

All nPartitions must contain contiguous chassis.

Each nPartition may be configured anywhere in the group of eight chassis.

Each nPartition must have its base chassis (active BaseIO) in the lowest U location.

Performance differences may arise as a result of the special cabling for eight-chassis partitionable Superdome Flex Server
configurations.

Only volatile memory DIMMs (DDR4 memory) are supported, not HPE Persistent Memory (PMMs).

GPUs are not permitted to be installed in I/O slots.

The supported eight-chassis partitionable Superdome Flex Server configurations are listed in Supported special eight-chassis system
nPartition configurations.

More information
Checklist: Verifying nPartition hardware requirements
Standard nPartition configuration guidelines

Special eight-chassis nPartition configurations 30

Supported special eight-chassis system nPartition configurations

CAUTION:
Hewlett Packard Enterprise supports special eight-chassis partitionable Superdome Flex Server configurations by
special customer order only. These special configurations may have nPartition sizes as large as eight chassis. Some
special, nonstandard configurations are supported, and special eight-chassis Superdome Flex Grid cabling is required.

The supported special nPartition configurations for eight-chassis system are shown in the following figures.
Figure 6: Special eight-chassis system nPartition sizes (16s to 32s)

Figure 7: Special eight-chassis system nPartition sizes (12s)

Figure 8: Special eight-chassis system nPartition sizes (4s and 8s)

Figure 6: Special eight-chassis system nPartition sizes (16s to 32s)

Supported special eight-chassis system nPartition configurations 31

Figure 7: Special eight-chassis system nPartition sizes (12s)

Supported special eight-chassis system nPartition configurations 32

Figure 8: Special eight-chassis system nPartition sizes (4s and 8s)

Supported special eight-chassis system nPartition configurations 33

Supported special eight-chassis system nPartition configurations 34
HPE Persistent Memory on HPE Superdome Flex Server
Hewlett Packard Enterprise supports HPE Persistent Memory on Superdome Flex Server with Intel Xeon 62xx and 82xx (Cascade Lake)
processors.
For details on supported PMM configurations and related administration and maintenance tasks, see HPE Persistent Memory Guide for
HPE Superdome Flex Server .

HPE Persistent Memory on HPE Superdome Flex Server 35

Websites
HPE Superdome Flex Server websites
HPE Superdome Flex Server product page
www.hpe.com/support/superdome-flex-product
HPE Superdome Flex Server customer documentation

www.hpe.com/support/superdome-flex-docs
HPE Superdome Flex Server software

www.hpe.com/support/superdome-flex-software
HPE Superdome Flex Server Software Delivery Repository

https://downloads.linux.hpe.com/SDR/project/hpe-foundation/

Server operating systems and virtualization software

www.hpe.com/us/en/servers/server-operating-systems.html
HPE Superdome Flex Server QuickSpecs

www.hpe.com/support/superdome-flex-quickspecs
HPE Foundation Software (HFS) and Linux version support matrix

https://downloads.linux.hpe.com/SDR/project/hpe-foundation/SD-Flex-LinuxSupportTables.html
HPE Superdome Flex Server spare parts list
www.hpe.com/support/superdome-flex-spareparts
HPE Superdome Flex Server release sets (support matrix)
www.hpe.com/support/superdome-flex-release-sets

HPE Superdome Flex Server support documentation

HPE Superdome Flex Server documentation for support specialists is available at www.hpe.com/support/superdome-flex-docs-restricted
by signing in to the Hewlett Packard Enterprise Support Center with an entitled account.

Related product websites

HPE 9361-4i RAID Controller (Q2N11A)
1. Go to the Broadcom MegaRAID SAS 9361-4i product page.

https://www.broadcom.com/products/storage/raid-controllers/megaraid-sas-9361-4i

2. Select the Documentation tab.

3. Under User Guide select:

12Gb/s MegaRAID SAS RAID Controllers User Guide

12Gb/s MegaRAID SAS Software User Guide

HPE 3154-8e RAID Controller (Q6M15A)

HPE Smart Storage Administrator User Guide

Microsemi Adaptec Smart HBA & RAID - Installation And User's Guide
1. Go to the Microsemi Adaptec SmartRAID 3154-8e product page.

https://storage.microsemi.com/en-us/support/raid/sas_raid/asr-3154-8e/

2. Select the Documentation tab and download the guide.

General websites
Hewlett Packard Enterprise Information Library
www.hpe.com/info/EIL

For additional websites, see Support and other resources.

Websites 36
Support and other resources

Support and other resources 37

Accessing Hewlett Packard Enterprise Support
For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:

https://www.hpe.com/info/assistance

To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website:

https://www.hpe.com/support/hpesc

Information to collect
Technical support registration number (if applicable)

Product name, model or version, and serial number

Operating system name and version

Firmware version

Error messages

Product-specific reports and logs

Add-on products or components

Third-party products or components

Accessing Hewlett Packard Enterprise Support 38

Accessing updates
Some software products provide a mechanism for accessing software updates through the product interface. Review your product
documentation to identify the recommended software update method.

To download product updates:

Hewlett Packard Enterprise Support Center

https://www.hpe.com/support/hpesc

Hewlett Packard Enterprise Support Center: Software downloads

https://www.hpe.com/support/downloads

My HPE Software Center

https://www.hpe.com/software/hpesoftwarecenter

To subscribe to eNewsletters and alerts:

https://www.hpe.com/support/e-updates

To view and update your entitlements, and to link your contracts and warranties with your profile, go to the Hewlett Packard
Enterprise Support Center More Information on Access to Support Materials page:

https://www.hpe.com/support/AccessToSupportMaterials

IMPORTANT:
Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise
Support Center. You must have an HPE Passport set up with relevant entitlements.

Accessing updates 39
Remote support
Remote support is available with supported devices as part of your warranty or contractual support agreement. It provides intelligent
event diagnosis, and automatic, secure submission of hardware event notifications to Hewlett Packard Enterprise, which initiates a fast
and accurate resolution based on the service level of your product. Hewlett Packard Enterprise strongly recommends that you register
your device for remote support.
If your product includes additional remote support details, use search to locate that information.

HPE Get Connected

https://www.hpe.com/services/getconnected

HPE Pointnext Tech Care

https://www.hpe.com/services/techcare

HPE Complete Care

https://www.hpe.com/services/completecare

Remote support 40
Customer self repair
Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it
will be shipped directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your Hewlett Packard
Enterprise authorized service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider.

Customer self repair 41

Warranty information
To view the warranty information for your product, see the links provided below:

HPE ProLiant and IA-32 Servers and Options

https://www.hpe.com/support/ProLiantServers-Warranties

HPE Enterprise and Cloudline Servers

https://www.hpe.com/support/EnterpriseServers-Warranties

HPE Storage Products

https://www.hpe.com/support/Storage-Warranties

HPE Networking Products

https://www.hpe.com/support/Networking-Warranties

Warranty information 42
Regulatory information
To view the regulatory information for your product, view the Safety and Compliance Information for Server, Storage, Power,
Networking, and Rack Products, available at the Hewlett Packard Enterprise Support Center:
https://www.hpe.com/support/Safety-Compliance-EnterpriseProducts

Additional regulatory information

Hewlett Packard Enterprise is committed to providing our customers with information about the chemical substances in our products as
needed to comply with legal requirements such as REACH (Regulation EC No 1907/2006 of the European Parliament and the Council). A
chemical information report for this product can be found at:

https://www.hpe.com/info/reach

For Hewlett Packard Enterprise product environmental and safety information and compliance data, including RoHS and REACH, see:

https://www.hpe.com/info/ecodata

For Hewlett Packard Enterprise environmental information, including company programs, product recycling, and energy efficiency, see:
https://www.hpe.com/info/environment

Regulatory information 43
Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, use
the Feedback button and icons (located at the bottom of an opened document) on the Hewlett Packard Enterprise Support Center portal
(https://www.hpe.com/support/hpesc) to send any errors, suggestions, or comments. All document information is captured by the
process.

Documentation feedback 44