Versions Compared

Version Old Version 58 New Version Current
Changes made by

Assaf Cohen

Hanan Kenan

Saved on

Key

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

...

Client Requirements

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

  • The Web Console is quite detailed and works with screen resolutions no less than requires a minimum screen resolution of 1280 X 720.
  • Supported user web browsers are FireFox Firefox , Internet Explorer 11+ , Chrome 50+ , Safari 43+

Monitored Device (DataPower) Requirements 

  • DPOD supports only the supported firmware - 7.1.0.10+, 7.2.0.6+, 7.5.0.2+ ,7.5.1+ ,7.5.2.4+, 7.6.1+
    • However some functionalities are available starting a specific firmware level. For more details please see release notes.
  • If any of the the monitored

...

  • devices attached to DPOD

...

  • is to be upgraded to firmware versions 7.6.+ you MUST upgrade to DPOD 1.0.5.0+ before the firmware upgrade in order to be able to browse

...

  • transactions from this

...

  • device.
  • DPOD supports only

...

  • DataPower with language set to

...

  • English.

Server Requirements

Physical HW or Hypervisor 

DPOD can be installed on both 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 that suitable for hypervisor (virtual environment)  The , the virtual appliance is supported on the following VMware hypervisors:

  • VMWare ESX  v5.5 , v6.0 
  • VMWare Player - v12.0 , v12.5
  • VMWare Workstation - v12.0 , v12.5 
  • VMware Fusion v8.0
  • 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

...

Resource Requirements

DPOD offers 6 basic load configuration setups.

  • One load configuration architecture setup for development that exists only in the Developer ISO file file!  The Developer edition ISO file name will be similar to: IBM_DataPower_OpDashboard_Dev<version>.isois DPOD-Developer-CentOS-<version>.iso (Can be download from Fix Central)

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

    • Appliance Mode (ISO file) - IBMDPOD_DataPower_OpDashboardCentOS_<version>.iso (Can be download from PPA) - for example: DPOD_CentOS_1.0.4.iso 

    • Non-Appliance Mode (Compressed Executable file) :- IBMDPOD_DataPower_OpDashboard_RH_<version>RedHat_<version>.cef (Can be download from PPA) - for example: DPOD_CentOS_1.0.3.cef


The following table lists the typical usage characteristics of 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)

Storage (GB)

Developer

Development

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

restricted license

2-3

Yes

2

3 GB

All: 20GB

Standard

Minimal

POCs and Evaluation.

Limited history period to reduce memory requirements

5

Yes

4

18 GB

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

Standard

Low

Environment with low load levels

40

Yes

6

32 GB

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

Standard

Medium

Environment with Moderate load

80

Yes

8

64GB

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

Standard

High

Environment with High load

120

Yes, but not recommended

12

128GB

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

Standard

High_20dv

Environment with Medium load

200

Can be increased to 1500 TPS(5) 

No. required to Must be install installed on a physical server

16 (Physical)

200GB

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

Standard

High_20dv


Environment with High load

1500 TPS(5) 


20 (Physical)(5) 

256GB

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

Customer with Customers who need to handle more than 1500 TPS will be required to have install sepereated multiple nodes.For example: a

High Load capacity plan sizing example

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

This customer will need to have 7 physical servers , with 2 sockets and 2 Intel based , with cpu hyperthreaded, each with 256 GB memory , 20 physical cores 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.

Customers that plan to use more than one node are expected to submit sizing questionnaire.

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

Customer Customers with higher load still are expected to create separate environments that , 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

...

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

IBM DataPower Operations Dashboard is Dashboard may also available to 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 reach cater for 1500 TPS customer requires , customers are required to have 256GB memory + 20 , 24 Physical cores (each is HyperThreaded thus brings equivalent to a total of 40) + , Local storage with RAID0 with across 4-8 SSD Disks (SAS 6GBs) - each support 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.


  

Storage Recommendation

  • DPOD serves as a database and should therefore be configured to use very fast disks. ThereforeFor this reason, DPOD installation requires 3 separate DISKS  for OS , Install, Installatio and Data.
  • Usage of slow disks is not recommended and will impact the amount of time between creation of transaction logs and the availability of the data on DPOD's dashboards.
  • For Physical hardware installation installations that can utilize HW RAID services we recommend the the following setup is recommend:
    • RAID5 - 40GB - for OS disk
    • RAID5 - 40GB - for App disk
    • RAID0 - Depends on volume - for Data disk. 

Warning
titleRAID Support

DPODs DPOD does not support the CentOS built-in RAID (Software Raid). The only supported RAID that we can support is the one handled by a controller

Network Requirements

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

Operating System Requirements - Only applicable to Non Appliance mode

  • CentOS 7.2.0 - x86-64 bit or RHEL 7.2.0 - x86-64 bit only .
  • Server OS must be a fresh install without any other installed products .
  • In non Non Appliance mode the OS support is not covered but recommendation recommendations will be provided.
  • The existence of other Other 3rd party SW software products for backups, security and monitoring can be accepted but because of the diversity we can not know their impact.When an unwanted situation occurs with DPOD, Support will be provided if customer agreed to disable this 3rd party tools effects so we can know this is only the DPOD issuemay be installed. However, due to diversity their impact is unknown.
  • During resolution of issues, DPOD support will ask the customer to disable these 3rd party tools, so that issues may be isolated and DPOD verified as their source. Support will not be provided if the 3rd party tools are not disabled.

Utility Software for Administrators

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

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

...