...
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
...
- One load configuration architecture setup for development that exists only in the Developer ISO file! The Developer edition ISO file name will be similar to: DPOD_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) - DPOD_CentOS_<version>.iso (Can be download from PPA) - for example: DPOD_CentOS_1.0.4.iso
Non-Appliance Mode (Compressed Executable file) - DPOD_RedHat_<version>.cef (Can be download from PPA) - for example: DPOD_CentOS_1.0.3.cef
The following table lists the typical usage characteristics for each setup edition, and the physical or virtual resources it requires.
...
Customers who need to handle more than 1500 TPS will be required to install sepereated multiple nodes.
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 intel based physical servers , with hyperthreaded cpus, each with 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, 20 physical cores and storage specification as described below(5).
1 Node = 1500 TPS
7 Nodes = 10,500 TPS.
Customers who plan to use more than one node are expected to submit a sizing questionnaire.
Each DPOD environment (up to 7 nodes) will support no more than 10,000 TPS.
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
...
(5) To cater for 1500 TPS, customers are required to have 256GB memory, 20 24 Physical cores (each is HyperThreaded thus equivalent to a total of 40), 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.
Storage Recommendation
- DPOD serves as a database and should therefore be configured to use very fast disks. For this reason, DPOD installation requires 3 separate DISKS for OS , 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 installations that can utilize HW RAID services the following setup is recommend:
- RAID5 - 40GB - for OS disk
- RAID5 - 40GB - for App disk
- RAID0 - Depends on volume - for Data disk.
...