In this page:

Supported DataPower Gateways

The following DataPower gateways can be monitored and managed by DPOD:

• DataPower Gateway firmware v2018.4.x, v10.0.x, v10.5.x and v10.6.x.

• DataPower Gateway operator v1.8.x-v1.12.x (for the DPOD Cloud Agent component to monitor containerized DataPower gateways in Kubernetes).

• API Connect v2018.4.x and v10.0.x.

• DPOD only supports gateways with supported firmware levels that meet the minimum system requirements for DataPower Gateway.

• The DataPower Gateway language must be set to English.

Supported Hypervisors

DPOD can be installed on a virtual infrastructure (hypervisor). The following hypervisors are supported for running a DPOD installation:

• VMWare ESXi v7.x-v8.x with Intel processors.

• VMWare Workstation/Player v16.x-v17.x with Intel processors.

• VMware Fusion v12.x-v13.x on Mac with Intel processors.

• AWS EC2 Instance (Virtual Machine) with Intel processors (using Non-Appliance installation only).

• Microsoft Azure Virtual Machine with Intel processors (using Non-Appliance installation only).

Supported Physical Hardware

DPOD can be installed on physical servers with Intel processors, especially when the load is high and the performance requires so. See the resources requirements listed below for more information.

Physical hardware should be purchased according to specifications provided by the DPOD support team in a short sizing process.

Supported Kubernetes Versions

See Cloud Agent Prerequisites for supported Kubernetes / OpenShift Container Platform (OCP) versions for deploying the DPOD Cloud Agent component.

Operating System Requirements (only applicable to Non-Appliance mode)

• RHEL v8.3-v8.10, v9.4 - x86-64 bit only on supported HW or Hypervisor as stated above.

• Rocky Linux v8.3-v8.10, v9.4 - x86-64 bit only on supported HW or Hypervisor as stated above.

• Some maintenance or advanced configuration tasks requires root or a user capable of running the sudo command (e.g. installation, upgrade, backup and restore of the DPOD application).

• Review the Operating System Requirements for Non-Appliance Mode and work with your Linux team to configure the OS properly.

• Third-party software such as antivirus, cybersecurity, monitoring, APM, endpoint protection, backup, etc. might significantly decrease the performance of DPOD and impact its functionality. During the resolution of issues, DPOD support will ask the customer to disable any 3rd party software in order to isolate the issues and verify their source. Support cannot be provided if the 3rd party tools are not disabled.

Resources Requirements and Deployment Profiles

The required resources depend on the type of installation, the expected TPS (Transactions Per Second) rate and the duration of the retention period. Make sure you are familiar with DPOD’s Installation Scenarios before choosing a deployment profile.

Please consider the following rules of thumb for sizing:

• For up to 120 TPS (across all devices), choose one of the Developer/Standard options from the table below.

• For over 120 TPS (across all devices), complete a sizing process by opening a support ticket with IBM Support.

• A single installation of a DPOD cell environment with 7 physical cell members can process up to ~20,000 TPS (assuming ~50 Syslog records per transaction on average). For a higher load, consider creating several installations.

Note:

• It is not possible to change the deployment profile after DPOD is installed. In order to change from one deployment profile to another, a new installation of DPOD is required, discarding the old data collected so far.

• Virtual deployments performance cannot be guaranteed. Virtual deployments performance depends on the server hosting the VM (ESX), its configuration, the overall load it is experiencing at any given time from any of its VMs, and especially the performance of the remote storage. This may result with a lower or higher performance for the same resources in different environments.

• It is recommended to conduct a performance test to determine the actual performance on your specific environment.

⁽¹⁾ The hosting server (e.g. ESXi) CPU utilization should not exceed 80%. To ensure best indexing performance, the virtual machine configuration should be set to have reserved CPUs.

⁽²⁾ Local SSD preferred - should be located on a data store separated from the other disks.

⁽³⁾ To ensure best query performance, the virtual machine configuration should be set to have reserved memory.

⁽⁴⁾ The TPS is the maximum total transactions load across all devices/domains connected to DPOD. If the TPS is too high and DPOD is unable to process all the incoming messages, some will be dropped, causing DPOD to show unreliable data (some transactions might not appear, some errors might not be displayed, some data such as latency might be missing from some of the transactions, etc.). When messages are dropped, an internal alert is generated and displayed in DPOD Web Console (under DPOD Health → Internal Alerts).

⁽⁵⁾ Customers will be provided with specifications after a short sizing process with support L3 team.

⁽⁶⁾ Using a single disk is possible by specifying a special command line option. For more information, consult your DPOD SME that supports the POC/evaluation process.

Storage Requirements

• DPOD is I/O intensive, as it needs to persist all logs and information at very high rates. Therefore, for most of the installations, it needs to be configured with very fast disks, and with at least 3 separate disks (OS, app/logs, data).

• Some configurations, such as the Cell environment, require additional data disks.

• Usage of slow disks will impact the maximum TPS that DPOD can process, the performance of queries and the amount of time between the creation of transaction logs and the availability of the data on DPOD's dashboards.

• For each 1 TB of data 64 GB of RAM is recommended for responsive queries (dashboards and filters).

• NFS is not supported for the data disk, as the Store relies on file system behavior that NFS does not supply. Data corruption and other problems can occur.

• Software RAID (such as RHEL built-in software RAID) is not supported.

• The data disk retention is automatically managed by DPOD. For each type of data (transactional, resources, payload, etc.), once its quota is full, old data will be discarded to make room for new data of the same type. A bigger disk size will hold a longer history.

Network Requirements

• DPOD requires at least one network interface for accessing DPOD's User Interface and communications with Gateway's Management Interface.

• Some configurations, such as the Cell environment, require two network interfaces.

• Firewall requirements are detailed in Firewall Requirements.

Client Requirements

DPOD's Web Console requires the following for administration and end-users:

• A minimum screen resolution of 1280x720 pixels.

• Supported web browsers are:

  • Firefox - latest 2 versions

  • Chrome - latest 2 versions

  • Safari -  latest 2 versions

  • Microsoft Edge Chromium - latest 2 versions

Utility Software for Administrators

• An SSH client to connect to the DPOD server once installed.

• An FTP Client software to upload/edit files in the server when required.