4.3

Prerequisites and compatibility

This page describes the prerequisites and compatibility for the installation of the WEKA system.

Important: The versions mentioned on the prerequisites and compatibility page apply to the WEKA system's latest minor version (4.3.X). For information on new features and supported prerequisites released with each minor version, refer to the relevant release notes available at get.weka.io.

Check the release notes for details about any updates or changes accompanying the latest releases.

In certain instances, WEKA collaborates with Strategic Server Partners to conduct platform qualifications alongside complementary components. If you have any inquiries, contact your designated WEKA representative.

CPU

CPU family/architectureSupported on backendsSupported on clients

2013 Intel® Core™ processor family and later

AMD EPYC™ processor families 2nd (Rome), 3rd (Milan-X), and 4th (Genoa) Generations

The following requirements must be met:

  • is enabled.

  • is disabled.

  • is enabled.

Memory

  • Sufficient memory to support the WEKA system needs as described in memory requirements.

  • More memory support for the OS kernel or any other application.

Operating system

WEKA will support upcoming releases of the operating systems in the lists within one quarter (three months) of their respective General Availability (GA) dates.

  • RHEL:

    • 9.4, 9.3, 9.2, 9.1, 9.0

    • 8.10, 8.9, 8.8, 8.7, 8.6, 8.5, 8.4, 8.3, 8.2, 8.1, 8.0

  • Rocky Linux:

    • 9.4, 9.3, 9.2, 9.1, 9.0

    • 8.9, 8.8, 8.7, 8.6

  • CentOS:

    • 8.5, 8.4, 8.3, 8.2, 8.1, 8.0

  • Ubuntu:

    • 24.04

    • 22.04

    • 20.04

    • 18.04

  • Amazon Linux:

    • AMI 2018.03

    • AMI 2017.09

  • Amazon Linux 2 LTS (formerly Amazon Linux 2 LTS 17.12)

    • Latest update package that was tested: 5.10.176-157.645.amzn2.x86_64

As of version 4.3.2, RHEL 7.X and CentOS 7.X are no longer supported due to their end-of-life status. If you need assistance upgrading your operating system, contact the Customer Success Team for guidance.

WEKA installation directory

  • WEKA installation directory: /opt/weka

    • /opt/weka must be a direct path. Do not use a symbolic link (symlink).

  • Boot drive minimum requirements:

    • Capacity: NVMe SSD with 960 GB capacity

    • Durability: 1 DWPD (Drive Writes Per Day)

    • Write throughput: 1 GB/s

  • Boot drive considerations:

    • Do not share the boot drive.

    • Do not mount using NFS.

    • Do not use a RAM drive remotely.

    • If two boot drives are available:

      • It is recommended to dedicate one boot drive for the OS and the other for the /opt/weka directory.

      • Do not use software RAID to have two boot drives.

  • Software required space:

    • Ensure that at least 26 GB is available for the WEKA system installation.

    • Allocate an additional 10 GB per core used by WEKA.

  • Filesystem requirement:

    • Set a separate filesystem on a separate partition for /opt/weka.

Networking

Adhere to the following considerations when choosing the adapters:

  • : LACP is supported when bonding ports from dual-port Mellanox NICs into a single Mellanox device but is not compatible when using Virtual Functions (VFs).

  • Intel E810:

    • Only supported on RHEL 8.6 and Rocky Linux 8.6. For other operating systems, consult with the Customer Success Team.

    • The ice Linux Base Driver version 1.9.11 and firmware version 4.0.0 are required.

  • It is recommended to set the MTU to at least 4k on the NICs of WEKA cluster servers and the connected switches.

  • If any network connection, irrespective of whether it’s InfiniBand or Ethernet, on a given backend possess the capability to transmit frames exceeding 4 KB in size, it is mandatory for all network connections used directly by WEKA on that same backend to have the ability to transmit frames of at least 4 KB.

  • support WEKA automatically detects and enable IOMMU for the server and PCI devices. Manual enablement is not required.

  • Mixed networks A mixed network configuration refers to a setup where a WEKA cluster connects to both InfiniBand and Ethernet networks. In such configurations, WEKA prioritizes InfiniBand for traffic management, switching to Ethernet only if issues arise with the InfiniBand network.

    RDMA (Remote Direct Memory Access) is not supported in mixed network clusters.

    Supported mixed connectivity MTU settings

    • Ethernet (9000) + InfiniBand (4K)

    Non-supported mixed connectivity MTU settings

    • Ethernet (1500) + InfiniBand (4K)

    • Ethernet (9000) + InfiniBand (2K)

  • IP addressing for dataplane NICs Exclusively use static IP addressing. DHCP is not supported for dataplane NICs.

Supported network adapters

The following table provides the supported network adapters along with their supported features for backends and clients, and clients-only.

For more information about the supported features, see WEKA networking.

Supported network adapters for backends and clients

AdapterProtocolSupported features

Amazon ENA

Ethernet

  • SRIOV VF

Broadcom BCM957508-P2100G

  • Dual-port (2x100Gb/s)

Ethernet

  • Shared networking

  • SRIOV VF

  • HA

  • Routed network

Broadcom BCM957608-P2200G

  • Dual-port (2x200Gb/s)

Ethernet

  • Shared networking

  • SRIOV VF

  • HA

  • Routed network

Intel E810 2CQDA2

Ethernet

  • Shared networking

  • HA

  • Routed network

NVIDIA Mellanox CX-7 single-port

InfiniBand

  • Shared networking

  • rx interrupts

  • RDMA

  • HA

  • PKEY

  • IOMMU

NVIDIA Mellanox CX-7 dual-port

InfiniBand

  • LACP

  • Shared networking

  • rx interrupts

  • RDMA

  • HA

  • PKEY

  • IOMMU

NVIDIA Mellanox CX-7-ETH single-port

Ethernet

  • LACP

  • Shared networking

  • HA

  • Routed network (ETH only)

  • IOMMU

NVIDIA Mellanox CX-7-ETH dual-port

Ethernet

  • LACP

  • Shared networking

  • HA

  • Routed network (ETH only)

  • IOMMU

NVIDIA Mellanox CX-6 LX

Ethernet

  • Shared networking

  • rx interrupts

  • HA

  • Routed network (ETH only)

  • IOMMU

NVIDIA Mellanox CX-6 DX

Ethernet

  • LACP

  • Shared networking

  • rx interrupts

  • RDMA

  • HA

  • Routed network (ETH only)

  • IOMMU

NVIDIA Mellanox CX-6

Ethernet InfiniBand

  • Mixed networks

  • Shared networking

  • rx interrupts

  • RDMA

  • HA

  • IOMMU

NVIDIA Mellanox CX-5 EX

Ethernet InfiniBand

  • Mixed networks

  • RDMA (IB only)

  • HA

  • PKEY (IB only)

  • IOMMU

NVIDIA Mellanox CX-5 BF

Ethernet

  • Mixed networks

  • HA

  • IOMMU

NVIDIA Mellanox CX-5

Ethernet InfiniBand

  • Mixed networks

  • rx interrupts

  • RDMA (IB only)

  • HA

  • PKEY (IB only)

  • Routed network (ETH only)

  • IOMMU

NVIDIA Mellanox CX-4 LX

Ethernet InfiniBand

  • Mixed networks

  • rx interrupts

  • HA

  • Routed network (ETH only)

  • IOMMU

NVIDIA Mellanox CX-4

Ethernet InfiniBand

  • Mixed networks

  • rx interrupts

  • HA

  • Routed network (ETH only)

  • IOMMU

VirtIO

Ethernet

  • HA

  • Routed network

Supported network adapters for clients-only

The following network adapters support Ethernet and SRIOV VF for clients only:

  • Intel X540

  • Intel X550-T1 (avoid using this adapter in a single client connected to multiple clusters)

  • Intel X710

  • Intel X710-DA2

  • Intel XL710

  • Intel XL710-Q2

  • Intel XXV710

  • Intel 82599ES

  • Intel 82599

Ethernet drivers and configurations

  • Supported Mellanox OFED versions for the Ethernet NICs:

    • 24.04-07.0.0

    • 23.10-0.5.5.0

    • 23.04-1.1.3.0

    • 5.9-0.5.6.0

    • 5.8-1.1.2.1 LTS

    • 5.8-3.0.7.0

    • 5.7-1.0.2.0

    • 5.6-2.0.9.0

    • 5.6-1.0.3.3

    • 5.4-3.5.8.0 LTS

    • 5.4-3.4.0.0 LTS

    • 5.1-2.6.2.0

    • 5.1-2.5.8.0

    Note: Subsequent OFED minor versions are expected to be compatible with Nvidia hardware due to Nvidia's commitment to backwards compatibility.

  • Supported ENA drivers:

    • 1.0.2 - 2.0.2

    • A current driver from an official OS repository is recommended

  • Supported ixgbevf drivers:

    • 3.2.2 - 4.1.2

    • A current driver from an official OS repository is recommended

  • Supported Intel 40 drivers:

    • 3.0.1-k - 4.1.0

    • A current driver from an official OS repository is recommended

  • Supported ice drivers:

    • 1.9.11

InfiniBand drivers and configurations

WEKA supports the following Mellanox OFED versions for the InfiniBand adapters:

  • 24.04-07.0.0

  • 23.10-0.5.5.0

  • 23.04-1.1.3.0

  • 5.9-0.5.6.0

  • 5.8-1.1.2.1 LTS

  • 5.8-3.0.7.0

  • 5.7-1.0.2.0

  • 5.6-2.0.9.0

  • 5.6-1.0.3.3

  • 5.4-3.5.8.0 LTS

  • 5.4-3.4.0.0 LTS

  • 5.1-2.6.2.0

  • 5.1-2.5.8.0

Note: Subsequent OFED minor versions are expected to be compatible with Nvidia hardware due to Nvidia's commitment to backwards compatibility.

Required ports

When configuring firewall ingress and egress rules the following access must be allowed.

Right-scroll the table to view all columns.

PurposeSourceTargetTarget PortsProtocolComments

WEKA server traffic for bare-metal deployments

All WEKA backend IPs

All WEKA backend IPs

14000-14100 (drives) 14200-14300 (frontend) 14300-14400 (compute)

TCP and UDP TCP and UDP TCP and UDP

These ports are the default for the Resources Generator for the first three containers. You can customize the ports.

WEKA client traffic

Client host IPs

All WEKA backend IPs

14000-14100 (drives) 14300-14400 (compute)

TCP and UDP TCP and UDP

These ports are the default. You can customize the ports.

WEKA backend to client traffic

All WEKA backend IPs

Client host IPs

14000-14100 (frontend)

TCP and UDP

These ports are the default. You can customize the ports.

WEKA SSH management traffic

All WEKA backend IPs

All WEKA backend IPs

22

TCP

WEKA server traffic for cloud deployments

All WEKA backend IPs

All WEKA backend IPs

14000-14100 (drives)

15000-15100 (compute)

16000-16100 (frontend)

TCP and UDP TCP and UDP TCP and UDP

These ports are the default. You can customize the ports.

WEKA client traffic (on cloud)

Client host IPs

All WEKA backend IPs

14000-14100 (drives)

15000-15100 (compute)

TCP and UDP TCP and UDP

These ports are the default. You can customize the ports.

WEKA backend to client traffic (on cloud)

All WEKA backend IPs

Client host IPs

14000-14100 (frontend)

TCP and UDP

These ports are the default. You can customize the ports.

WEKA GUI access

All WEKA management IPs

14000

TCP

User web browser IP

NFS

NFS client IPs

WEKA NFS backend IPs

2049 <mountd port>

TCP and UDP TCP and UDP

You can set the mountd port using the command: weka nfs global-config set --mountd-port

NFSv3 (used for locking)

NFS client IPs

WEKA NFS backend IPs

46999 (status monitor) 47000 (lock manager)

TCP and UCP

SMB/SMB-W

SMB client IPs

WEKA SMB backend IPs

139 445

TCP TCP

SMB-W

WEKA SMB backend IPs

2224

TCP

This port is required for internal clustering processes.

SMB/SMB-W

WEKA SMB backend IPs

All Domain Controllers for the selected Active Directory Domain

88

389 464 636 3268 3269

TCP and UDP TCP and UDP TCP and UDP TCP and UDP TCP and UDP TCP and UDP

These ports are required for SMB/SMB-W to use Active Directory as the identity source. Furthermore, every Domain Controller within the selected AD domain must be accessible from the WEKA SMB servers.

SMB/SMB-W

WEKA SMB backend IPs

DNS servers

53

TCP and UDP

S3

S3 client IPs

WEKA S3 backend IPs

9000

TCP

This port is the default. You can customize the port.

wekatester

All WEKA backend IPs

All WEKA backend IPs

8501 9090

TCP TCP

Port 8501 is used by wekanetperf.

WEKA Management Station

User web browser IP

WEKA Management Station IP

80 <LWH>

443 <LWH>

3000 <mon>

8760 <deploy>

8090 <snap>

8501 <mgmt> 9090 <mgmt>

9091 <mon> 9093 <alerts>

HTTP

HTTPS

TCP

TCP

TCP

TCP TCP

TCP TCP

Cloud WEKA Home, Local WEKA Home

All WEKA backend IPs

Cloud WEKA Home or Local WEKA Home

80 443

HTTP HTTPS

Open according to the directions in the deployment scenario: - WEKA server IPs to CWH or LWH. - LWH to CWH (if forwarding data from LWH to CWH)

Troubleshooting by the Customer Success Team (CST)

All WEKA backend IPs

CST remote access

4000 4001

TCP TCP

HA

See High Availability (HA).

SSDs

  • The SSDs must support PLP (Power Loss Protection).

  • WEKA system storage must be dedicated, and partitioning is not supported.

  • The supported drive capacity is up to 30 TB.

  • IOMMU mode is not supported for SSD drives. If you need to configure IOMMU on WEKA cluster servers, for instance, due to specific applications when running the WEKA cluster in converged mode, contact our Customer Success Team for assistance.

  • The ratio between the cluster's smallest and the largest SSD capacity must not exceed 8:1.

To get the best performance, ensure TRIM is supported by the device and enabled in the operating system.

Object store

  • API must be S3 compatible:

    • GET

      • Including byte-range support with expected performance gain when fetching partial objects

    • PUT

      • Supports any byte size of up to 65 MiB

    • DELETE

  • Data Consistency: Amazon S3 consistency model:

    • GET after a single PUT is strongly consistent

    • Multiple PUTs are eventually consistent

Certified object stores

  • Amazon S3

    • S3 Standard

    • S3 Intelligent-Tiering

    • These storage classes are ideal for remote buckets where data is written once and accessed in critical situations, such as during disaster recovery:

      • S3 Standard-IA

      • S3 One Zone-IA

      • S3 Glacier Instant Retrieval

      Remember, retrieval times, minimum storage periods, and potential charges due to object compaction may apply. If unsure, use S3 Intelligent-Tiering.

  • Azure Blob Storage

  • Google Cloud Storage (GCS)

  • Cloudian HyperStore (version 7.3 and higher)

  • Dell EMC ECS (version 3.5 and higher)

  • HCP Classic V9.2 and up (with versioned buckets only)

  • HCP for Cloud-Scale V2.x

  • IBM Cloud Object Storage System (version 3.14.7 and higher)

  • Lenovo MagnaScale (version 3.0 and higher)

  • Quantum ActiveScale (version 5.5.1 and higher)

  • Red Hat Ceph Storage (version 5.0 and higher)

  • Scality Ring (version 7.4.4.8 and higher)

  • Scality Artesca (version 1.5.2 and higher)

  • SwiftStack (version 6.30 and higher)

  • Dell PowerScale S3 (version 9.8.0.0 and higher)

Virtual Machines

This section outlines the use of virtual machines (VMs) with WEKA, covering backends, clients, VMware platforms, and cloud environments. While VMs can be used in certain configurations, there are specific limitations and best practices to follow.

Backends

Virtual machines may be used as backends for internal training purposes only and are not recommended for production environments.

WEKA provides best-effort support for backends deployed on virtual machines, but full support is not guaranteed. Additionally, WEKA does not guarantee support for components or configurations outside of our documented and supported cloud environments, and performance may vary.

Clients

Virtual Machines (VMs) can be used as clients. Ensure the following prerequisites are met for each client type:

  • UDP clients:

    • Reserve CPU resources and dedicate a core to the client to prevent CPU starvation of the WEKA process.

    • Ensure the root filesystem supports a 3K IOPS load for the WEKA client.

  • DPDK clients:

    • Meet all the requirements for UDP clients.

    • Additionally, verify that the virtual platform (hypervisor, NICs, CPUs, and their respective versions) fully supports DPDK and the required virtual network drivers.

VMware platform (client only)

When using vmxnet3 devices, do not enable the SR-IOV feature, because it disables the vMotion functionality. Each frontend process requires a dedicated vmxnet3 device and IP address, with an additional device and IP for each client VM to support the management process.

Core dedication is required when using vmxnet3 devices.

VMs and instances on cloud environments

Refer to the cloud deployment sections for the most up-to-date list of supported virtual machines and instances in various cloud environments.

Related topics

AWS: Supported EC2 instance types using Terraform

Azure: Supported virtual machine types

GCP: Supported machine types and storage

Related information

For additional information and how-to articles, search the WEKA Knowledge Base in the WEKA support portal or contact the Customer Success Team.

KMS

  • HashiCorp Vault (version 1.1.5 up to 1.14.x)

  • KMIP-compliant KMS (protocol version 1.2 and higher)

    • The KMS must support encryption-as-a-service (KMIP encrypt/decrypt APIs)

    • KMIP certification has been conducted with Equinix SmartKey (powered by Fortanix KMS)

PreviousGlossaryNextWEKA cluster installation on bare metal servers

Last updated