Versions Compared

Old Version 92

changes.mady.by.user Amit Munwes

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 Gateway firmware level is levels are 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 2018.4 (compatibility mode) or API GW Service.versions are 10.0.x, 2018.4.x and 5.0.8.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.

Physical HW or

...

Hypervisor

DPOD can be installed on either a Virtualized Environment virtual environment (Hypervisorshypervisors) or Physical server physical servers (Intel(C) based CPUs and supporting CentOS/RedHat 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:

  • VMWare ESX  ESX - v6.0, v6.5VMWare Player -  , v6.7
  • VMWare Workstation/Player - v14, v15VMWare Workstation - v14, v15v16
  • VMware Fusion - v11.0, v11.5, v12.0, v12.1
  • 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.

Resources Requirements

DPOD offers 6 basic load configuration setups. :

  • One load configuration architecture setup architecture for development that (exists only in the Developer Edition ISO file!  The Developer edition ).
    The Developer E    dition 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 architectures for the Standard Edition are available in, available as: 

    • Appliance Mode (ISO file) - 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_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

...

TPS Limits recommended(4)

...

Supports Virtual Env

...

Cores (1)

...

Memory (3)

    • cef - can be downloaded from PPA.


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

Load Configuration Architecture

Goal

TPS Limit

Supports Virtual 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

Standard

Minimal

POCs and

Evaluation

evaluation.
Limited history period to reduce memory requirements.

5

Yes

4

TPS

Can be virtual (5)

4 cores (1)

18 GB (3)

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

+

-300 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

+

-2,000 GB

Standard

High

Environment with

High

moderate load

120 TPS

Yes

Can be virtual, but not recommended

12

128GB

 (5)

16 cores (1)

128-256 GB (3)

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

,000+

-8 TB

Standard

High_20dv

Environment with

Medium

medium to high load

200

Can be increased to 1500 TPS(5) 

No.

-1500 TPS (6)

Must be installed on a physical server

16

Needs sizing (

PhysicalOS: 40
Install: 40
Data(2): 2,000

6)

200GB

Needs sizing (6)

Needs sizing (6)

StandardHigh_20dvEnvironment with
High
very high load
1500 TPS
2750 TPS (
5
6)
 
No.
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)
StandardFederated ArchitectureEnvironment with very high load>2750 TPS - TBD (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 ( in 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.

(1) These could be cores on an 80% utilized ESXi

...

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 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 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 for 2750 TPS, customers will be provided with specification .

(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 sizing process with L3.

  

...

Storage Requirements

...

  • DPOD serves as a database and should therefore be should, therefore, be configured to use very fast disks. For this reason, DPOD installation requires 3 separate DISKS  for OS, Installation, Installation and and Data.
  • Usage of slow disks is not recommended and . It 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 recommendrecommended:
    • 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 1GB RAM : 32GB DISK 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.

Network Requirements

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

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 9 - x86-64 bit only on supported HW or Hypervisor as stated above 1253868448. (7.3 is not Supported. 7.2 will be out of support in 2019H2 )
  • Server OS must be a fresh install without any other installed products.
  • In Non-Appliance mode 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 as

    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 7201280x720 pixels.
  • Supported user web browsers are:
    • Firefox - latest 2 versions
    , Internet Explorer 11+ (not Edge) ,
    • Chrome - latest 2 versions
    ,
    • Safari -  latest 2 versions

...

    • Microsoft Edge Chromium - latest 2 versions
    • Internet Explorer 11+ (not Edge)

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.

...