Versions Compared

Old Version 93

changes.mady.by.user Hanan Kenan

Saved on

compared with

New Version Current

changes.mady.by.user Amit Munwes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Monitored Device (DataPower Gateway) Requirements

  • Supported

    DataPower Gateway firmware

    level is

    10.5.x, 10.0.x and 2018.4.x.
    Some functionalities are also available for lower firmware levels. For more details please

    see

    see Release Notes.

  • Supported

    API Connect

    version is

    10.0.x, 2018.4

    (compatibility mode) or API GW Service or API Connect

    .x and 5.0.8

    .X.

    .x.

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

  • The DataPower Gateway language must be set to English.

...

Supported Hypervisors

DPOD can be installed on either a Virtualized Environment (Hypervisors) or Physical server (Intel(C) based CPUs and supporting CentOS 7.x OS). Consult the table below for information to support this decision.

Hypervisor SW

For a production environment suitable for hypervisor (virtual environment), the virtual appliance is supported on the following VMware hypervisors:

...

virtual infrastructure (hypervisor). The following hypervisors are supported for running a DPOD production installation:

  • VMWare ESX - v6.0, v6.5

    VMWare Player - 

    , v6.7, v7.0

  • VMWare Workstation/Player - v14, v15

    VMWare Workstation - v14

    ,

    v15

    v16

  • VMware Fusion - v11.0, v11.5, v12.x

  • PureApp (only on Intel Processors) - no pattern yet available, can be provided only as an imported OVA

    .For Hyper V support - contact your IBM sales representatives

    .

Hyper-V

DPOD is NOT currently tested on Hyper-V, and there are currently no plans to add such testing in the future. Therefore it cannot be guaranteed that the installation of DPOD on Hyper-V works, nor can the performance of such an installation be guaranteed. If a customer decides to install DPOD on Hyper-V:

  1. The support will be limited to application bugs and issues that affect other hypervisors as well (issues that are not specific to Hyper-V).

  2. The customer might be asked to install DPOD on a supported infrastructure (such as VMware or physical servers) to prove that the issue is not specific to Hyper-V, in order to get support.

Note: DPOD can also be installed on physical servers (it might even be required for high loads), which can provide an alternative for customers that only own Hyper-V for virtualization. More information is available below.

Supported Physical Hardware

DPOD can be installed on physical servers (with Intel(C) based CPUs), 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 support L3 team in a short sizing process.

Resources Requirements

DPOD offers 6 basic load configuration setups.

...

deployment profiles:

  • A development deployment profile (exists only in the Developer Edition ISO file

    !  The Developer edition

    ).
    The Developer Edition ISO file name is DPOD-Developer-CentOS-<version>.

    iso (Can be download

    iso, and can be downloaded from Fix Central

    )

    Five load configuration architecture setups that exist for the Standard Edition are available in: .

  • Five Standard Edition deployment profiles, available as:

    • Appliance Mode (ISO file) -

    •  DPOD

    •  DPOD_CentOS_<version>.iso

    • (Can

    • - can be

    • download

    • downloaded from PPA

    • ) - for example: DPOD_CentOS_1.0.8.5

    • .

    • iso 

    • Non-Appliance Mode (Compressed Executable file) -

    •  DPOD

    •  DPOD_RedHat_<version>.

    • cef (Can be download from PPA) - for example: DPOD_CentOS_1.0.8.5.cef

The following table lists the typical usage characteristics for each setup edition, and the physical or virtual resources it requires.

...

Availability in

Edition

...

Load Configuration Architecture Setup

...

Goal

...

    • cef - can be downloaded from PPA.

  • 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.

Please consider the following rules of thumb for sizing:

  • Customers that expect a load of up to 120 TPS (across all devices, including future growth) may choose one of the options from the table below.

  • Customers that expect a load of over 120 TPS (across all devices, including future growth) are required to complete a sizing process by opening a support ticket with IBM Support.

  • Currently a single installation of DPOD cell environment with 7 physical cell members can process up to ~20,000 TPS (assuming ~35 Syslog records per transaction on average). Customers with higher load than that may create several installations, each can handle up to ~20,000 TPS.

Available in Edition

Deployment Profile

Goal

TPS Limit(4)

Supports Virtual

Env

Cores (1)

Memory (3)

Storage (GB)

Environment

Cores

RAM

Storage

Developer

Development

Developers only. In rare cases can be used for functional POCs.

Under restricted license.

2-3

Yes

TPS

Can be virtual (5)

2 cores (1)

4 GB (3

GB

)

All

Single disk:

25GB

30GB

Standard

Minimal

POCs and

Evaluation

evaluation.
Limited history period to reduce memory requirements.

5

Yes

4

18 GB

OS: 40
Install: 40
Data(2): 100+

TPS

Can be virtual (5)

4 cores (1)

18 GB (3)

Single disk: 200-400 GB

Standard

Low

Environment with low load levels

40

Yes

6

TPS

Can be virtual (5)

6 cores (1)

32 GB (3)

OS: 40 GB
Install: 40 GB
Data(2): 100

+

-1000 GB

Standard

Medium

Environment with

Moderate

moderate load

80

Yes

8

64GB

TPS

Can be virtual (5)

8 cores (1)

64 GB (3)

OS: 40 GB
Install: 40 GB
Data(2): 300

+Standard

High

Environment with High load

120

Yes, but not recommended

12

128GB

OS: 40
Install: 40
Data(2): 1,000+

-2,000 GB

Standard

High

_20dv

Environment with

Medium

moderate load

200

120 TPS

Can be

increased to 1500 TPS

virtual (5)

16 cores 

No. Must be installed on a physical server

16 (Physical)

200GB

(1)

128-256 GB (3)

OS: 40 GB
Install: 40 GB
Data(2):

2,000

1-8 TB

Standard

High_20dv

Environment with

High No.

medium to very high load

1500 TPS(5) 

200-2750 TPS (6)

Must be installed on a physical server

24

Needs sizing (

Physical

6)

Needs sizing (

5

6)

 

256GB

OS: 40
Install: 40
Data(2+5): 8,000

StandardHigh_20dvEnvironment with Very High load2750 TPS

Needs sizing (6)

Standard

Federated Architecture

Environment with very high load that requires several DPOD servers

>2750 TPS (6)

No.

Must be installed on

a

physical

server

servers

Physical

Needs sizing (6)

TBD

Needs sizing (6)

TBD(6)

Customers who need to handle more than 1500 TPS will be required to use a Federated Architecture.

Customers who expect to handle load over 200 TPS will require to start a sizing process by open ticket to IBM Support - L2.

High Load capacity plan sizing example

A customer wants to attach a pool of appliances to DPOD. This pool generates a peak of circa 10,000 TPS (on average about 35 Syslog records per transaction).

This customer will need to have 7 servers with 2 sockets and 2 Intel-based CPUs - each with 12 physical cores of 2.6 GHz (non-turbo) and with hyper-threaded Support.  Each server requires 256GB of memory, and storage specification as described below(5).

1 Node = 1500 TPS

7 Nodes = 10,500 TPS.

Each DPOD environment will support no more than 10,000 TPS and up to 7 nodes.

Customers with higher load still are expected to create separate environments, each can handle up to 10,000 TPS.

Customers who plan to use more than one node or above 1,000 TPS are expected to submit a sizing questionnaire available to IBM technical sales teams.

...

Needs sizing (6)

(1) 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.

(2) Local SSD preferred - should be located on a data store separated from the other disks.

(3) Best query performance is achieved by using reserved memory configuration To ensure best query performance, the virtual machine configuration should be set to have reserved memory.

(4) The TPS is the maximum total transaction transactions load across all devices/domains connected to DPOD

IBM DataPower Operations Dashboard may also be installed as a custom distributed edition (not All-in-One) that allows installation on several servers located across separate geographical locations.

This normally requires creating a custom architecture based on a sizing process.  

(5) To cater for 1500 TPS, customers are required to have 256GB memory, 24 Physical cores (each is Hyper-Threaded thus equivalent to a total of 48), Local storage with RAID0 across 4-8 SSD Disks (SAS 6GBs) - each supporting at least 80K Random Write IOPS 4KiB and write avg latency of less than 35 uSec. Two controllers will be required to be attached to each CPU. Please keep the ratio between RAM and Data storage size to be 1GB RAM: 16GB Data Disk (recommended) and no more than 1 GB RAM:32GB DISK (minimal).

(5) To cater to 2750 TPS, customers . 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).

(5) 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.

(6) Customers will be provided with specifications after a short sizing process with support L3 team.

  

Storage Recommendation

...

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

    is not recommended and

    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

    Physical hardware installations that can utilize HW RAID services the following setup is recommended:
  • RAID5 - 40GB - for OS disk
  • RAID5 - 40GB - for App disk
    • RAID0 - Depends on volume - for Data disk. 
    For

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

    Please keep the ratio between RAM and Data storage size to be 1GB RAM: 16GB Data Disk (recommended) and no more than 1 GB RAM:32GB DISK (minimal).

...

titleRAID Support

  • 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 CentOS built-in 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.

Operating System Requirements

...

(only applicable to Non-Appliance mode)

  • CentOS 7.

    6/

    7-7.

    7

    9 - x86-64 bit only on supported HW or Hypervisor as stated above.

  • RHEL 7.

    6/7.7

    7-7.9, 8.3-8.5 - x86-64 bit only on supported HW or Hypervisor as stated above

    15692006622. (7.3 is not Supported. 7

    .

    2 will be out of support in 2019H2 )Server

  • The OS must be a fresh install, without any other installed products.

  • In Non-Appliance mode the

    The OS support is not covered, but recommendations will be provided.

  • Other 3rd

    Third-party software

    products for backups, security, and monitoring may be installed. However, due to diversity their impact is unknown.During

    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

    these

    any 3rd party

    tools, so that issues may be isolated and DPOD verified to

    software in order to isolate the issues and verify their source. Support

    will not

    cannot be provided if the 3rd party tools are not disabled.

Client Requirements

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

  • The Web Console requires a

    A minimum screen resolution of

    1280 X 720

    1280x720 pixels.

  • Supported

    user

    web browsers are:

    • Firefox - latest 2

    versions ,

    • versions

    • Chrome - latest 2 versions

    • Safari -  latest 2 versions

    • Microsoft Edge Chromium - latest 2 versions

    • Internet Explorer 11+ (not Edge)

    , Chrome - latest 2 versions , Safari -  latest 2 versions

Utility

...

Software for Administrators

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

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

...