Technical requirements
To implement the BeeGFS on NetApp solution, make sure your environment meets the technology requirements.
Hardware requirements
The following table lists the hardware components that are required to implement a single second-generation building block design of the BeeGFS on NetApp solution.
The hardware components used in any particular implementation of the solution might vary based on customer requirements. |
Count | Hardware component | Requirements |
---|---|---|
2 |
BeeGFS file nodes. |
Each file node should meet or exceed the following configuration to achieve expected performance. Processors:
Memory:
PCIe Expansion: Four PCE Gen4 x16 slots:
Miscellaneous:
Lenovo SR665:
|
8 |
Mellanox ConnectX-6 HCAs (for file nodes). |
|
8 |
1m HDR InfiniBand cables (for file/block node direct connects). |
The length can be adjusted to account for longer distances between the file and block nodes if required. |
8 |
HDR InfiniBand cables (for file node/storage switch connections) |
Requires InfiniBand HDR cables (QSFP56 transceivers) of the appropriate length to connect file nodes to storage leaf switches. Possible options include:
|
2 |
E-Series block nodes |
Two EF600 controllers configured as follows:
|
Software requirements
For predictable performance and reliability, releases of the BeeGFS on NetApp solution are tested with specific versions of the software components required to implement the solution.
Software deployment requirements
The following table lists the software requirements deployed automatically as part of the Ansible-based BeeGFS deployment.
Software | Version | ||
---|---|---|---|
BeeGFS |
7.2.6 |
||
Corosync |
3.1.5-1 |
||
Pacemaker |
2.1.0-8 |
||
OpenSM |
opensm-5.9.0 (from mlnx_ofed 5.4-1.0.3.0)
|
Ansible control node requirements
The BeeGFS on NetApp solution is deployed and managed from an Ansible control node. For more information, see the Ansible documentation.
The software requirements listed in the following tables are specific to the version of the NetApp BeeGFS Ansible collection listed below.
Software | Version |
---|---|
Ansible |
2.11 |
Python |
3.9 |
Additional Python packages |
Cryptography-35.0.0, netaddr-0.8.0 |
BeeGFS Ansible Collection |
3.0.0 |
File node requirements
Software | Version | ||
---|---|---|---|
RedHat Enterprise Linux |
RedHat 8.4 Server Physical with High Availability (2 socket).
|
||
Linux Kernel |
4.18.0-305.25.1.el8_4.x86_64 |
||
InfiniBand / RDMA Drivers |
Inbox |
||
ConnectX-6 HCA Firmware |
FW: 20.31.1014 |
||
PXE: 3.6.0403 |
UEFI: 14.24.0013 |
EF600 block node requirements
Software | Version |
---|---|
SANtricity OS |
11.70.2 |
NVSRAM |
N6000-872834-D06.dlp |
Drive Firmware |
Latest available for the drive models in use. |
Additional requirements
The equipment listed in the following table was used for the validation, but appropriate alternatives can be used as needed. In general, NetApp recommends running the latest software versions to avoid unanticipated issues.
Hardware component | Installed software |
---|---|
|
|
1x Ansible control node (virtualized):
|
Installed Ansible and Python versions match those in the table above. |
10x BeeGFS Clients (CPU nodes):
|
|
1x BeeGFS Client (GPU node):
This system is based on NVIDIAs HGX A100 platform and includes four A100 GPUs. |
|