HPE Cray Supercomputing Programming Environment Installation Guide: HPE Cray XD2000 Systems (26.03) S-8012

About the HPE CPE installation guide: HPE Cray XD2000 systems

The HPE Cray Supercomputing Programming Environment (CPE) for HPE Cray XD2000 systems is distributed as a collection of RPM packages. This publication documents the installation of RPMs and related files on these systems.

This publication is intended for system administrators receiving their first release of this product or upgrading from a previous release. The information in this guide assumes that the administrator understands Linux system administration.

IMPORTANT: Be sure to always employ the latest installation instructions. To check for the latest version and revisions of this CPE guide, go to the HPE Support Center website, and perform a search on the part number of this document (S-8012).

For information on how to use CPE or details regarding CPE components and modules, see the CPE Online Documentation website web page. See also the Documentation and support chapter for additional CPE resources and information.

Release information

This publication supports the installation of the HPE CPE 26.03 release on XD2000 systems running:

Management Software & Version

Operating System

Architecture

HPCM 1.15

RHEL 8.10

X86

This release also supports v21.0.0 of the HPE Cray Compiler Environment (CCE).

IMPORTANT: CPE versions 25.03 (and earlier) previously supported MOFED versions 5.8 (or earlier) as directed in installation instructions. However, with CPE 25.09 (and later)releases, HPE recommends that MOFED/DOCAFED-dependent users with HPE Slingshot 10 (SS10) refrain upgrading CPE beyond the 25.03 CPE release. HPE observed a system bug, the Extended Reliable Connection (XRC) bug in MOFED. This system bug adversely affects CPE and SS10 functionality. The bug was introduced by NVIDIA in early 2023, and HPE reported details of the bug to NIDIA in April 2023. The bug is currently unresolved and is not expected to be fixed during the transition from MOFED to DOCA OFED. Until a resolution or workaround is introduced, CPE users should not upgrade past the CPE 25.03 release.

See the CPE 26.03 Release Announcements on the CPE Online Documentation website for other supported dependencies.

Variable substitutions

Variable substitutions to be used throughout this guide include:

  • <CPE_RELEASE> = 26.03

  • <CPE_VERSION> = 26.03.X (where X is the third digit of the actual three-digit version number of an official and HPE-supported version number)

  • <AOCC_VERSION> = 5.0.0

  • <INTEL_VERSION> = 2025.2.1

  • <MOFED_VERSION> = Not Supported

  • <IMAGE_ROOT> = /opt/clmgr/image/images/<IMAGE_NAME>, where your site chooses the <IMAGE_NAME>

Record of revision

New in the CPE 26.03 publication

New in the CPE 25.09 (Rev. A) publication

New in the CPE 25.09 publication

New in the CPE 25.03 publication

New in the CPE 24.11 publication

New in the CPE 24.07 publication

Publication Title

Date

HPE Cray Supercomputing Programming Environment for the HPE Cray XD2000 System Installation Guide (26.03) S-8012

March 2026

HPE Cray Supercomputing Programming Environment for the HPE Cray XD2000 System Installation Guide (25.09) S-8012

September 2025

HPE Cray Programming Environment for the HPE Cray XD2000 System Installation Guide (25.03) S-8012

March 2025

HPE Cray Programming Environment for the HPE Cray XD2000 System Installation Guide (24.11) S-8012

January 2025

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (24.07) S-8012

August 2024

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (24.03) S-8012

May 2024

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (23.12) S-8012

December 2023

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (23.09) S-8012

September 2023

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (23.05) S-8012

June 2023

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (23.02-Rev. A) S-8012

March 2023

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (23.02) S-8012

February 2023

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (22.12) S-8012

December 2022

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (22.11) S-8012

November 2022

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (22.10) S-8012

October 2022

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (22.09) S-8012

September 2022

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (22.08) S-8012

August 2022

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (22.06) S-8012

June 2022

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (22.05) S-8012

May 2022

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (22.04) S-8012

April 2022

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (22.03) S-8012

March 2022

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (22.02) S-8012

February 2022

HPE Cray Programming Environment for the Apollo 2000 Gen10 Plus (x86) System Installation Guide (21.02 - 21.12) S-8012

Feb - Dec 2021

Document conventions

This section defines the documentation conventions used throughout the guide, including typographic styles for code, commands, paths, and the backslash as the shell line-continuation character. It explains command-prompt notation, showing how the host and account are indicated (root prompts end with #, non-root prompts use account@hostname>) and lists node abbreviations (CN, NCN, AN, UAN) with example prompts for specific node types and Kubernetes contexts. This section also provides a simple three-step workflow and a reminder to verify pasted commands.

Typographical and command prompt conventions

This section provides background information about typographical and command prompts used in this guide and describes how they are delineated throughout this guide.

Typographical conventions

Type

Convention Description

This style

Indicates program code, reserved words, library functions, command-line prompts, screen output, file/path names, variables, and other software constructs.

\ (backslash)

When inserted at the end of a command line, indicates the Linux shell line continuation character (lines joined by a backslash are parsed as a single line).

Command prompt conventions

Host name and account in command prompts: The host name in a command prompt indicates where the command must be run. The account that must run the command is also indicated in the prompt.

  • The root or super-user account always has the # character at the end of the prompt.

  • Any non-root account is indicated with account@hostname>. A user account that is not root or crayadm is seen as user.

Command Prompt

Definition

user@login>

Run the command on any login node as any non-root user.

hostname#

Run the command on the specified system as root.

user@hostname>

Run the command on the specified system as any non-root user.

Copying and pasting text from this document

Using the Copy and Paste functions from a PDF is unreliable. Although copying and pasting a command line typically works, copying and pasting formatted file content (for example, JSON, YAML) typically fails. To ensure that file content is copied and pasted correctly while performing the procedures in this guide:

  1. Copy the content from the PDF.

  2. Paste it to a neutral editing form and add the necessary formatting.

  3. Copy the content from the neutral form and paste it into the console.

Tip: As a best practice, double-check copied/pasted commands for correctness, as some commands may not render correctly in the PDF.

Downloading HPE Cray Supercomputing EX software

To download HPE Cray Supercomputing EX software, refer to the HPE Support Center or download it directly from My HPE Software Center. The HPE Support Center contains a wealth of documentation, training videos, knowledge articles, and alerts for HPE Cray Supercomputing EX systems. It provides the most detailed information about a release as well as direct links to product firmware, software, and patches available through My HPE Software Center.

Downloading the software through the HPE Support Center

HPE recommends downloading software through the HPE Support Center because of the many other resources available on the website.

  1. Visit the HPE Cray Supercomputing EX product page on the HPE Support Center.

  2. Search for specific product info, such as the full software name or recipe name and version.

    For example, search for “Slingshot 2.1” or “Cray System Software with CSM 24.3.0.”

  3. Find the desired software in the search results and select it to review details.

  4. Select Obtain Software and select Sign in Now when prompted.

    If a customer’s Entitlement Order Number (EON) is tied to specific hardware rather than software, the software is available without providing account credentials. Access the software instead by selecting Download Software and skip the next step in this procedure.

  5. Enter account credentials when prompted and accept the HPE License Terms.

    To download software, customers must ensure their Entitlement Order Number (EON) is active under My Contracts & Warranties on My HPE Software Center. If customers have trouble with the EON or are not entitled to a product, they must contact their HPE contract administrator or sales representative for assistance.

  6. Choose the needed software and documentation files to download and select curl Copy to access the files.

    Just like the software files, the documentation files change with each release. In addition to the official documentation, valuable information for a release is often available in files that include the phrase README in their name. Be sure to select and review these files in detail.

    HPE recommends the curl Copy option, which downloads a single text file with curl commands to use on the desired system. You must run the curl commands within 24 hours of downloading them or download new commands if more than 24 hours have passed.

    To validate the security of the downloads, you can later compare the files on the desired system against the checksums provided by HPE underneath each selected download.

  7. Save the text file to a central location.

  8. On the system where the software will be downloaded, run a shell script to execute the text file that includes the curl commands.

    For example:

    ncn-m001# bash -x <TEXT_FILE_PATH>

    The -x option in this example tracks the download progress of each curl command in the text file.

Downloading the software directly from the My HPE Software Center

Users already familiar with a release can save time by downloading software directly from My HPE Software Center.

  1. Visit My HPE Software Center and select Sign in.

  2. Enter account credentials when prompted and select Software in the left navigation bar.

  3. Search for specific product info, such as the full software name or recipe name and version.

    For example, search for “Slingshot 2.1” or “Cray System Software with CSM 24.3.0.”

  4. Find the desired software in the search results and review details by selecting Product Details under the Action column.

    Image of Product Detailsoption

  5. Select Go To Downloads Page and accept the HPE License Terms.

    To download software, customers must ensure their Entitlement Order Number (EON) is active under My Contracts & Warranties. If customers have trouble with the EON or are not entitled to a product, they must contact their HPE contract administrator or sales representative for assistance.

  6. Choose the needed software and documentation files to download and select curl Copy to access the files.

    Just like the software files, the documentation files change with each release. In addition to the official documentation, valuable information for a release is often available in files that include the phrase README in their name. Be sure to select and review these files in detail.

    HPE recommends the curl Copy option, which downloads a single text file with curl commands to use on the desired system. You must run the curl commands within 24 hours of downloading them or download new commands if more than 24 hours have passed.

    To validate the security of the downloads, you can later compare the files on the desired system against the checksums provided by HPE underneath each selected download

  7. Save the text file to a central location.

  8. On the system where the software will be downloaded, run a shell script to execute the text file that includes the curl commands.

    For example:

    ncn-m001# bash -x <TEXT_FILE_PATH>

    The -x option in this example tracks the download progress of each curl command in the text file.

Installing HPE CPE on HPE Cray XD2000 Systems with HPCM

Use this procedure to install CPE into an image on the HPE Cray XD2000 system using HPCM.

Prerequisites

  • A cluster image for use with CPE must already be present on the system. You can optionally clone the current cluster image to a new one to be used by CPE or save a revision of the current cluster image before continuing with this procedure. Consult the HPE Performance Cluster Manager Administrator’s Guide for more information on HPCM management commands.

  • The glibc-devel package must be installed.

  • Mellanox OFED must be updated to <MOFED_VERSION> version. See Release Information for additional details.

  • If you are using Lua modulefiles, the RHEL CodeReady Builder repository must be enabled before installing cray-lmod.

Before you begin

  1. Obtain the cpe-<CPE_ISO_VERSION>-<RHELX-X>-<ARCH>.iso ISO files. For example:

    cpe-26.3.1-rhel-8-10-x86_64.iso

  2. Download and enable required OS repositories (for the installation of cpe-support), including:

    • RHEL BaseOS

    • RHEL AppStream

    • EPEL

    • USS WLM Support

  3. Note that to use UCX with HPE Cray-MPICH:

    • HPE Cray-MPICH using the UCX netmod is supported on RHEL 8.10 systems with the HPCM installer.

    • HPE does not distribute UCX directly.

    • Mellanox provides a UCX solution as a part of their HPC-X software toolkit. This solution is the recommended path. Open source and Linux distribution packages provide a functional, although not necessarily performant, alternative.

Building the CPE image

  1. Add the CPE repository from the ISO media:

    mgmt1# cm repo add <PATH_TO_ISO> --priority 99

  2. Confirm the CPE repository is available, and note the name of the repository:

    mgmt1# cm repo show | grep CPE
CPE-<CPE_ISO_VERSION>-rhel-8-10-x86_64 : /opt/clmgr/repos/cm/CPE-<CPE_ISO_VERSION>-rhel-8-10-x86_64

  3. Select the CPE repository using the name shown in the previous command:

    mgmt1# cm repo select \
CPE-<CPE_ISO_VERSION>-rhel-8-10-x86_64

  4. Create a copy of cpe.rpmlist located in the CPE repository:

    admin# cp /opt/clmgr/repos/cm/CPE-<CPE_ISO_VERSION>-rhel-8-10-x86_64/cpe.rpmlist \
${HOME}/cpe.rpmlist

  5. (Optional) Modify the rpmlist to include or exclude necessary components. Additional compiler programming environments can be added by un-commenting the existing subsections in the rpmlist:

    admin# vim ${HOME}/cpe.rpmlist

    Subcomponents predefined in the provided rpmlist, include (but are not limited to):

    # # --- Base ---
cpe-gcc-native-12.2
cpe-gcc-native-13.1
...

# # --- CCE ---
cce-19.0.0
cce-19.0.0-binutils
...

# # --- CSML ---
cray-fftw-3.3.10.9
cray-hdf5-1.14.3.3
...

# # --- MPT ---
cray-dsmml-0.3.0
cray-mpich-8.1.31-cray180
...

# # --- TOOLS ---
atp-3.15.5
cray-ccdb-5.0.5
...

# # --- PrgEnv-aocc ---
#cpe-descriptive-manifest-aocc
#cpe-prgenv-aocc
...

# # --- PrgEnv-intel ---
#cpe-descriptive-manifest-intel
#cpe-prgenv-intel
...

  6. Install CPE content into the desired image from the cpe.rpmlist:

    mgmt1# cm image dnf -i <IMAGE_NAME> install cpe-profile \
$(cat ${HOME}/cpe.rpmlist | egrep -v "^#" | tr '\n' ' ')

  7. Update the cpe-profile configuration if a different CPU target is required in cray-pe-configuration.sh and cray-pe-configuration.csh (for example, craype-x86-milan):

    mgmt1# chroot /opt/clmgr/image/images/<IMAGE_NAME> \
sed -i 's/craype-x86-rome/craype-x86-milan/' /etc/cpe-profile.d/cray-pe-configuration.*sh

  8. (Optional) Generate the modulefiles for AOCC and Intel oneAPI compilers, as applicable. Note that CPE does not contain the AOCC or the Intel oneAPI compiler itself; the compiler must be installed separately.

    mgmt1# chroot /opt/clmgr/image/images/<IMAGE_NAME> 
mgmt1(chroot)# . /opt/cray/pe/modules/default/init/bash
mgmt1(chroot)# module load craypkg-gen
mgmt1(chroot)# craypkg-gen -m /opt/AMD/aocc-compiler-<AOCC_VERSION>
mgmt1(chroot)# craypkg-gen -m /opt/intel/oneapi/compiler/<INTEL_VERSION>
mgmt1(chroot)# exit

  9. (Optional) To use Lmod as the default module handling system instead of Environment modules, update the cpe-profile configuration:

    mgmt1# chroot /opt/clmgr/image/images/<IMAGE_NAME> sed -i 's/"environment modules"/"lmod"/' \
/etc/cray-pe.d/cray-pe-configuration.*sh

  10. Set the release default:

    mgmt1# chroot <IMAGE_ROOT> /opt/cray/pe/cpe/<CPE_RELEASE>/set_default_cpe_<CPE_RELEASE>

  11. Stage the image on the desired nodes:

    mgmt1# cm node provision -i <IMAGE_NAME> --stage --nodes n0*

  12. Reboot the nodes to use the image:

    mgmt1# cm power reset -t node n0*

Creating Modulefiles for Third-Party Products

Use the procedures in this section to create modulefiles for third-party products. These instructions use craypkg-gen to create a modulefile for a specific version of a supported third-party product. This process allows a site to set a specific version as default. These tasks are necessary and can be embedded in a script where a third-party product is being installed.

Prerequisites

Third-party packages must be downloaded and installed.

Procedure

  1. Load craypkg-gen module:

    source /opt/cray/pe/modules/default/init/bash
module use /opt/cray/pe/modulefiles
module load craypkg-gen

  2. Generate module and set default scripts for products:

    AMD Optimizing C/C++ Compiler: (requires craypkg-gen >= 1.3.16)

    craypkg-gen -m /opt/AMD/aocc-compiler-<AOCC_VERSION>/

    Intel OneAPI

    craypkg-gen -m /opt/intel/oneapi/compiler/<INTEL_VERSION>/

  3. Run a set default script:

    /opt/admin-pe/set_default_craypkg/set_default_<MODULE_NAME>_<MODULE_VERSION>

About the Lmod Custom Dynamic Hierarchy

Lmod enables a user to dynamically modify their user environment through Lua modules. CPE capitalizes on the Lmod hierarchical structure, including the Lmod module auto-swapping functionality. This functionality allows module dependencies to determine the branches of the tree-like hierarchy. Lmod allows static and dynamic hierarchical module paths. Lmod provides full support for static paths, which build the hierarchy based on the current set of modules loaded. Alongside static paths, CPE implements dynamic paths for a subset of the Lmod hierarchy (compilers, networks, CPUs, and MPIs). Dynamic paths give an advanced level of flexibility for detecting multiple dependency paths and allow custom paths to join the existing CPE Lmod hierarchy without modifying customer modulefiles.

Static Lmod hierarchy

Modules dependent on one or more modules being loaded are not visible to a user until their prerequisite modules are loaded. When the prerequisite modules are loaded, it adds the static paths of the dependent modules to the MODULEPATH environment variable, thereby exposing the dependent modules to the user. For more detailed information on Lmod static module hierarchies, please consult User Guide for Lmod.

Dynamic Lmod hierarchy

The CPE custom dynamic Lmod hierarchy abbreviates the overall Lmod hierarchy tree by relying on compatibility and not directly on a prerequisite version. Therefore, dependent modules do not need to exist in a new branch every time their prerequisite modules change versions. Instead, dynamic paths use a compatibility version that increases when a new prerequisite module version breaks compatibility in some way. The number following the module path alias (for example, 1.0 in x86-rome/1.0 and ofi/1.0) identifies the compatible version.

Module Path Aliases and Current Compatibility Versions

Compatible versions listed in the following tables include the minimum supported versions.

Compiler

RHEL Module Alias/Compatible Version

amd

amd/7.0

cce

crayclang/21.0

aocc

aocc/4.1

intel

intel/2023.2

gcc

gnu/10.0

nvidia

nvidia/20

Network

Module Alias/Compatible Version

craype-network-infiniband

infiniband/1.0

craype-network-ofi

ofi/1.0

craype-network-ucx

ucx/1.0

CPU

Module Alias/Compatible Version

craype-broadwell

broadwell/1.0

craype-x86-milan

x86-milan/1.0

craype-x86-rome

x86-rome/1.0

craype-x86-skylake

x86-skylake/1.0

craype-x86-cascadelake

x86-cascadelake/1.0

craype-x86-icelake

x86-icelake/1.0

MPI

Module Alias/Compatible Version

cray-mpich

cray-mpich/8.0

cray-mpich-abi

cray-mpich/8.0

cray-mpich-abi-pre-intel-5.0

cray-mpich/8.0

cray-mpich-ucx

cray-mpich/8.0

cray-mpich-ucx-abi

cray-mpich/8.0

cray-mpich-ucx-abi-pre-intel-5.0

cray-mpich/8.0

Custom dynamic hierarchy

The CPE custom dynamic hierarchy extension allows custom module paths to join the existing CPE Lmod hierarchy implementation without modifying customer modulefiles. The custom dynamic module types that CPE supports include:

  • Compiler

  • Network

  • CPU

  • MPI

  • Compiler/Network

  • Compiler/CPU

  • Compiler/Network/CPU/MPI

As each custom dynamic module type loads, a handshake occurs using special pre-defined environment variables. When all hierarchical prerequisites are met, the paths of the dependent modulefiles are added to the MODULEPATH environment variable, thereby exposing the dependent modules to the user.

For Lmod to assist a user optimally, load the compiler, network, CPU, and MPI module. Lmod cannot detect modules hidden in dynamic paths without one of each type of module being loaded.

Creating a custom dynamic hierarchy

For the CPE custom dynamic hierarchy to detect the desired Lmod module path, one or more custom dynamic environment variables must be created according to the requirements defined within this procedure.

Prerequisites

Set Lmod as the default module handling system before initiating this procedure.

Procedure

To create a custom dynamic environment variable:

  1. Begin the environment variable name with LMOD_CUSTOM_.

  2. Append the descriptor of the module type that the environment variable will represent. The module types and descriptors are:

    Module Type

    Descriptor

    Compiler

    COMPILER_

    Network

    NETWORK_

    CPU

    CPU_

    MPI

    MPI_

    Compiler/Network

    COMNET_

    Compiler/CPU

    COMCPU_

    Compiler/Network/CPU/MPI

    CNCM_

    Example: The custom dynamic environment variable for the combined compiler and CPU module begins with LMOD_CUSTOM_COMCPU_.

  3. Following the descriptor, append all prerequisite module aliases along with their respective compatible versions. See the Module Path Aliases and Current Compatibility Versions section of this guide for more information. The format of the module path alias/compatible version string for each module type is shown below. Note that due to publishing issues, long module alias/compatible version strings are split across two lines as indicated below.

    Module Type: Module Path Alias/Compatible Version String

    Compiler: <compiler_name>/<compatible_version>

    Network: <network_name>/<compatible_version>

    CPU: <cpu_name>/<compatible_version>

    MPI:

    <compiler_name>/<compatible_version>/<network_name>/<compatible_version>/

    <mpi_name>/<compatible_version>

    Compiler/Network: <compiler_name>/<compatible_version/<network_name>/<compatible_version>

    Compiler/CPU: <compiler_name>/<compatible_version>/<cpu_name>/<compatible_version>

    Compiler/Network/CPU/MPI:

    <compiler_name>/<compatible_version>/<network_name>/<compatible_version>/

    <cpu_name>/<compatible_version>/<mpi_name>/<compatible_version>

    To create an acceptably formatted environment variable name, replace all slashes and dots in the module alias/compatible version string with underscores. Also, all letters must be in uppercase format.

    Example Module Path Alias/Compatible Version Strings:

    • Compiler = cce

      The path alias/compatible version string (values found in Module Path Aliases and Current Compatibility Versions section of this guide) is crayclang/10.0; therefore, the text added to the environment variable name is:

      CRAYCLANG_10_0

    • Network = craype-network-ofi

      The path alias/compatible version string is ofi/1.0; therefore, the environment variable text is:

      OFI_1_0

    • CPU = craype-x86-rome

      The path alias/compatible version string is x86-rome/1.0; therefore, the environment variable text is:

      X86_ROME_1_0

    • MPI = cray-mpich

      cray-mpich has two prerequisite module types (compiler and network). Therefore, the environment variable must include the alias/compatible version for the desired compiler, network, and MPI. For a cray-mpich module dependent on cce and craype-network-ofi, the path alias/compatible version string is crayclang/10.0/ofi/1.0/cray_mpich/8.0; therefore, the environment variable text is:

      CRAYCLANG_10_0_OFI_1_0_CRAY_MPICH_8_0.

    • Compiler/Network = cce with craype-network-ofi

      The path alias/compatible version string is crayclang/10.0/ofi/1.0; therefore, the environment variable text is:

      CRAYCLANG_10_0_OFI_1_0

    • Compiler/CPU = cce with craype-x86-rome

      The path alias/compatible version string is crayclang/10.0/x86-rome/1.0; therefore, the environment variable text is:

      CRAYCLANG_10_0_X86_ROME_1_0

    • Compiler/Network/CPU/MPI = cce, craype-network-ofi, craype-x86-rome, and cray-mpich

      The path alias/compatible version string is crayclang/10.0/ofi/1.0/x86-rome/1.0/cray-mpich/8.0; therefore, the environment variable text is:

      CRAYCLANG_10_0_OFI_1_0_X86_ROME_1_0_CRAY_MPICH_8_0

  4. Append _PREFIX following the final module/compatibility text instance:

    Example: Network = craype-network-ofi

    The custom dynamic environment variable is LMOD_CUSTOM_NETWORK_OFI_1_0_PREFIX.

    Creation of the custom dynamic environment variable is now complete.

  5. Add the custom dynamic environment variable to the user environment by exporting it with its value set to the Lmod module path:

    # export LMOD_CUSTOM_NETWORK_OFI_1_0_PREFIX=<lmod_module_path>

    Example: Network = craype-network-ofi

    All modulefiles in <lmod_module_path> are shown to users whenever craype-network-ofi is loaded.

Support matrices for previous releases

This chapter lists CPE-supported components, third-party software, and modules supported for applicable and previous releases of the CPE software. This information is provided for reference purposes.

CPE release matrices for XD2000 and Apollo 2000 HPC Cray Supercomputing systems

CPE is supported on HPE Cray Supercomputing EX XD2000 systems with HPCM. Below are product components, modules, third-party software versions supported with previous CPE releases with this configuration.

(D) represents the default version installed at installation.

Product / Release

25.09

25.03

24.11

24.07

Product / Release

XD2000

XD2000

XD2000

Apollo 2000

HPCM

1.13

1.12

1.11

aocc

5.0.0

4.2.0

4.2.0

atp

3.15.7 (D)

3.15.6 (D)

3.15.5 (D)

3.15.4 (D)

cce

20.0.0

19.0.0 (D)

18.0.1 (D)

18.0.0 (D)

cpe-gcc-native

10.3

10.3

10.3

10.3

cpe-gcc-native

11.2

11.2

11.2

11.2

cpe-gcc-native

12.2

12.2

12.2

12.2

cpe-gcc-native

13.2 (D)

13.2 (D)

13.2 (D)

13.2 (D)

cpe-prgenv-aocc

8.6.0 (D)

8.6.0 (D)

8.4.0 (D)

8.4.0 (D)

cpe-prgenv-cray

8.6.0 (D)

8.6.0 (D)

8.4.0 (D)

8.4.0 (D)

cpe-prgenv-gnu

8.6.0 (D)

8.6.0 (D)

8.4.0 (D)

8.4.0 (D)

cpe-prgenv-intel

8.6.0 (D)

8.6.0 (D)

8.4.0 (D)

8.4.0 (D)

cray-R

4.4.0 (D)

4.4.0 (D)

4.4.0 (D)

4.4.0 (D)

cray-ccdb

5.0.7 (D)

5.0.6 (D)

5.0.5 (D)

5.0.4 (D)

cray-cdst-support

2.14.6 (D)

2.14.5 (D)

2.14.3 (D)

cray-cti

2.20.0 (D)

2.19.1 (D)

2.19.0 (D)

2.18.4 (D)

cray-dsmml

0.2.2 (D)

0.2.2 (D)

0.2.2 (D)

0.2.2 (D)

cray-dwarf

2.0.0 (D)

0.11.1 (D)

0.11.0 (D)

0.9.2 (D)

cray-dyninst

12.3.6 (D)

12.3.5 (D)

12.3.4 (D)

12.3.2 (D)

cray-fftw

3.3.10.11 (D)

3.3.10.10 (D)

3.3.10.9 (D)

3.3.10.8 (D)

cray-hdf5

1.14.3.7 (D)

1.14.3.5 (D)

1.14.3.3 (D)

1.14.3.1 (D)

cray-libsci

25.09.0 (D)

25.03.0 (D)

24.11.0 (D)

24.07.0 (D)

cray-lmod

8.7.60

8.7.55

8.7.31

8.7.31

cray-modules

3.2.11.7 (D)

3.2.11.7 (D)

3.2.11.5 (D)

3.2.11.5 (D)

cray-mpich

8.1.33

8.1.32 (D)

8.1.31 (D)

8.1.30 (D)

cray-mpich

9.0.1 (D)

cray-mrnet

5.1.6 (D)

5.1.5 (D)

5.1.4 (D)

5.1.3 (D)

cray-netcdf

4.9.2.1 (D)

4.9.0.17 (D)

4.9.0.15 (D)

4.9.0.13 (D)

cray-openshmemx

11.4.0.beta (D)

11.4.0.beta (D)

11.4.0.beta (D)

11.4.0.beta (D)

cray-pals

1.3.2 (D)

1.3.2 (D)

1.3.2 (D)

1.3.2 (D)

cray-papi

7.2.0.2 (D)

7.2.0.1 (D)

7.1.0.4 (D)

7.1.0.2 (D)

cray-parallel-netcdf

1.12.3.19 (D)

1.12.3.17 (D)

1.12.3.15 (D)

1.12.3.13 (D)

cray-pe-profile-ofi-milan

1.3

1.3

1.3

1.3

cray-pe-profile-ofi-rome

1.3

1.3

1.3

1.3

cray-pe-profile-ofi-skylake

1.3

1.3

1.3

1.3

cray-pe-set-default

3.3 (D)

3.3 (D)

3.1 (D)

3.1 (D)

cray-pmi

6.1.16 (D)

6.1.15 (D)

6.1.15 (D)

6.1.15 (D)

cray-pmi-devel

6.1.16 (D)

6.1.15 (D)

6.1.15 (D)

6.1.15 (D)

cray-pmi-doc

6.1.16 (D)

6.1.15 (D)

6.1.15 (D)

6.1.15 (D)

cray-python

3.11.7 (D)

3.11.7 (D)

3.11.7 (D)

3.11.7 (D)

cray-stat

4.12.6 (D)

4.12.5 (D)

4.12.4 (D)

4.12.3 (D)

cray-zmqnet

1.3.2 (D)

1.3.0 (D)

1.0.0 (D)

craype

2.7.35 (D)

2.7.34 (D)

2.7.33 (D)

2.7.32 (D)

craype-dl-plugin-py3

21.02.1.3 (D)

21.02.1.3 (D)

21.02.1.3 (D)

craype-targets

1.7.0 (D)

1.6.0 (D)

1.5.0 (D)

1.4.0 (D)

craypkg-gen

1.3.36 (D)

1.3.35 (D)

1.3.34 (D)

1.3.33 (D)

gdb4hpc

4.16.5 (D)

4.16.4 (D)

4.16.3 (D)

4.16.2 (D)

intel

2025.0.0

2024.2.0

2024.0.1

libfabric

1.13.1 (D)

1.13.1 (D)

1.13.1 (D)

1.13.1 (D)

libzmq5

4.3.3 (D)

4.3.3 (D)

4.3.3 (D)

4.3.3 (D)

lmod_scripts

3.2.1 (D)

3.2.1 (D)

3.2.0 (D)

3.2.0 (D)

Mellanox OFED

5.8 (or later)

5.8

5.8

perftools

25.09.0 (D)

25.03.0 (D)

24.11.0 (D)

24.07.0 (D)

sanitizers4hpc

1.1.6 (D)

1.1.5 (D)

1.1.4 (D)

1.1.3 (D)

totalviewsup

2024.4.0

2024.1.21

2024.1.21

valgrind4hpc

2.13.6 (D)

2.13.5 (D)

2.13.4 (D)

2.13.3 (D)

Documentation and support

Documentation is available as a resource for using and managing CPE. This chapter provides details for obtaining CPE support and accessing available resources.

CPE installation and getting started guides

HPE CPE documentation comprises user and installation guides:

Title

Document Part Number

HPE Cray Supercomputing Programming Environment Installation Guide: CSM on HPE Cray Supercomputing EX Systems

S-8003

HPE Cray Supercomputing Programming Environment Installation Guide: HPCM on HPE Cray Supercomputing EX and HPE Cray Supercomputing Systems

S-8022

HPE Cray Supercomputing Programming Environment Installation Guide: HPE Cray XD2000 Systems

S-8012

HPE Cray Supercomputing Programming Environment Getting Started User Guide: HPE Cray Supercomputing EX Systems

S-9934

HPE Cray Supercomputing Programming Environment Getting Started Administrator Guide: HPE Cray Supercomputing EX Systems

S-9935

Other documentation resources

HPE provides CPE documentation and support through various online sources:

Published: April 2026