Prepare for UAN Product Installation

Perform this procedure to ready the HPE Cray Supercomputing EX system for HPE Cray Supercomputing UAN product installation.

Install and configure the HPE Cray Supercomputing COS product before performing this procedure.

If the HPE Cray Supercomputing EX system contains Compute Nodes (CNs) that will be repurposed as UANs, those CNs must be configured as CNs first. The HPE Cray Supercomputing User Access Node (UAN) Administrator Guide (S-8033) provides instructions for reconfiguring a CN as UAN after product installation.

  1. Verify that the management network switches are properly configured.

    See the switch configuration procedures in the HPE Cray System Management Documentation.

  2. Ensure that the management network switches have the proper firmware.

    See the procedure “Update the Management Network Firmware” in the HPE Cray EX hardware documentation.

  3. Ensure that the host reservations for the UAN CAN/CHN network have been properly set.

    See the procedure “Add UAN CAN IP Addresses to SLS” in the HPE Cray Supercomputing EX hardware documentation.

    1. For systems where UANs are going to host UAIs, identify a block of IP addresses for the services running in K3s. Please see Configuring a UAN for K3s (Technical Preview) for information on reserving a block of IP addresses on CAN/CHN for K3s MetalLB use.

      Note: The identification of IP addresses for the services running in K3s should be made at system installation time to avoid the possibility of IP collisions with CSM services.

  4. Configure the BMC for UANs with iLO

  5. Configure the BIOS of an HPE UAN

  6. Verify that the firmware for each UAN BMC meets the specifications.

    Use the System Admin Toolkit firmware command to check the current firmware version on a UAN node.

    ncn-m001# sat firmware -x BMC_XNAME

  7. Repeat the previous six Steps for all UANs.

  8. Unpackage the file.

    ncn-m001# tar zxf uan-PRODUCT_VERSION.tar.gz

  9. Navigate into the uan-PRODUCT_VERSION/ directory.

    ncn-m001# cd uan-PRODUCT_VERSION/

  10. Run the pre-install goss tests to determine if the system is ready for the UAN product installation.

    This step requires that goss is installed on the node running the tests.

    ncn# ./validate-pre-install.sh
...............

Total Duration: 1.304s
Count: 15, Failed: 0, Skipped: 0

  11. Ensure that the cray-console-node pods are connected to UANs so that they are monitored and their consoles are logged.

    1. Obtain a list of the xnames for all UANs (remove the --subrole argument to list all Application nodes).

      ncn# cray hsm state components list --role Application --subrole UAN --format json | jq -r .Components[].ID | sort
x3000c0s19b0n0
x3000c0s24b0n0
x3000c0s31b0n0

    2. Obtain a list of the console pods.

      ncn# PODS=$(kubectl get pods -n services -l app.kubernetes.io/name=cray-console-node --template '{{range .items}}{{.metadata.name}} {{end}}')

    3. Use conman -q to scan the list of connections conman is monitoring (only UAN xnames are shown for brevity).

      ncn# for pod in $PODS; do kubectl exec -n services -c cray-console-node $pod -- conman -q; done
x3000c0s19b0n0
x3000c0s24b0n0
x3000c0s31b0n0

      If a console connection is not present, the install may continue, but a console connection should be established before attempting to boot the UAN.

Next, install the UAN product by performing the procedure Install the UAN Product Stream.