Skip to main content
BeeGFS on NetApp with E-Series Storage

Set up file nodes and block nodes

Contributors netapp-jolieg mcwhiteside iamjoemccormick netapp-jsnyder
PDFs

While most software configuration tasks are automated using the NetApp-provided Ansible collections, you must configure networking on the baseboard management controller (BMC) of each server and configure the management port on each controller.

Set up file nodes

  1. Configure networking on the baseboard management controller (BMC) of each server.

    To learn how to configure networking for the validated Lenovo SR665 V3 file nodes, see the Lenovo ThinkSystem Documentation.

    Note A baseboard management controller (BMC), sometimes referred to as a service processor, is the generic name for the out-of-band management capability built into various server platforms that can provide remote access even if the operating system is not installed or accessible. Vendors typically market this functionality with their own branding. For example, on the Lenovo SR665, the BMC is referred to as the Lenovo XClarity Controller (XCC).

  2. Configure the system settings for maximum performance.

    You configure the system settings using the UEFI setup (formerly known as the BIOS) or by using the Redfish APIs provided by many BMCs. The system settings vary based on the server model used as a file node.

    To learn how to configure the system settings for the validated Lenovo SR665 file nodes, see Tune system settings for performance.

  3. Install Red Hat 9.3 and configure the host name and network port used to manage the operating system including SSH connectivity from the Ansible control node.

    Do not configure IPs on any of the InfiniBand ports at this time.

    Note While not strictly required, subsequent sections presume that host names are sequentially numbered (such as h1-hN) and refer to tasks that should be completed on odd versus even numbered hosts.

  4. Use RedHat Subscription Manager to register and subscribe the system to allow installation of the required packages from the official Red Hat repositories and to limit updates to the supported version of Red Hat: subscription-manager release --set=9.3. For instructions, see How to register and subscribe a RHEL system and How to limit updates.

  5. Enable the Red Hat repository containing the packages required for high availability.

    subscription-manager repo-override --repo=rhel-9-for-x86_64-highavailability-rpms --add=enabled:1

  6. Update all HCA firmware to the version recommended in Technology requirements.

    This update can be done by downloading and running a version of the mlxup tool that bundles the recommended firmware. You can download this tool from mlxup - Update and Query Utility (user guide).

Set up block nodes

Set up the EF600 block nodes by configuring the management port on each controller.

  1. Configure the management port on each EF600 controller.

    For instructions on configuring ports, go to the E-Series Documentation Center.

  2. Optionally, set the storage array name for each system.

    Setting a name can make it easier to refer to each system in subsequent sections. For instructions on setting the array name, go to the E-Series Documentation Center.

Note While not strictly required, subsequent topics presume storage array names are sequentially numbered (such as c1 - cN) and refer to the steps that should be completed on odd versus even numbered systems.