Versions Compared

Key

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

...

  1. Before installing a cell environment, make sure to complete the sizing process with IBM Support Team to get recommendations for the hardware and architecture suitable for your requirements.
  2. DPOD cell manager and federated cell members must be of the same version (minimum version is 1.0.8.6).
  3. DPOD cell manager is usually virtual and can be installed in both Appliance Mode or Non-Appliance Mode with Medium Load architecture type, as detailed in the Hardware and Software Requirements.
  4. DPOD federated cell members (FCMs) can be one of the following:
    1. Physical servers installed in Non-appliance Mode (based on RHEL) with High_20dv architecture type, as detailed in the Hardware and Software Requirements.
      Physical servers are used when the cell is required to process high transactions per second (TPS) load.
    2. Virtual servers installed in Non-appliance Mode with Medium architecture type or higher, as detailed in the Hardware and Software Requirements.
      Virtual servers are used when the cell is required to process moderate transactions per second (TPS) load, or when the cell is part of a non-production environment where the production cell uses physical servers (to keep environments architecture similar).
  5. All DPOD cell members must be identical - only physical or only virtual (cannot mix physical and virtual cell members in the same cell), and with the same resources (CPUs, RAM, disk type and storage capacity).
  6. Physical federated cell members with 4 CPU sockets and NVMe disks require special disks and mount points configuration to ensure performance. See Configuring Cell Members with 4 CPU Sockets and NVMe Disks.
  7. Each cell component (manager / FCM) should have two network interfaces:
    1. External network interface - for DPOD users to access the Web Console (on the cell manager) and for communication between DPOD and Monitored Gateways (on both the cell manager and the members).
    2. Internal network interface - for internal DPOD components inter-communication (should be a 10Gb Ethernet interface).
    3. This design allows separation between the two types of communications which may be used to enhance the security (e.g.: deny end-users from being able to access the inter-cell communication).
    4. We recommend having 2 different VLANs with different subnet masks subnets as this makes it easier to configure the servers without using static routing and to configure the network firewall rules.
  8. Network ports should be opened in the network firewall as detailed below:

Anchor
Network Ports
Network Ports

From

To

Ports (Defaults)

Protocol

Usage

DPOD Cell Manager (external IP address)

Each Monitored Device

5550 (TCP)

HTTP/S

Monitored device administration management interface.
If the SOMA port is different than 5550 - the port should be changed accordingly.

DPOD Cell

Manager

Manager (external IP address)

DNS Server

TCP and UDP 53

DNS

DNS services. Static IP address may be used.

DPOD Cell

Manager

Manager (external IP address)

NTP Server

123 (UDP)

NTP

Time synchronization

DPOD Cell

Manager

Manager (external IP address)

Organizational mail server

25 (TCP)

SMTP

Send reports by email

DPOD Cell

Manager

Manager (external IP address)

LDAP

TCP 389 / 636 (SSL).

TCP 3268 / 3269 (SSL)

LDAP

Authentication & authorization. Can be over SSL.

DPOD Cell
Manager
Manager (internal IP address)Each DPOD Federated Cell Member443 (TCP)HTTP/SCommunication (data + management)
DPOD Cell
Manager
Manager (internal IP address)Each DPOD Federated Cell Member22 (TCP)TCPSSH root access is needed for the cell installation and for admin operations from time to time.
DPOD Cell
Manager
Manager (internal IP address)Each DPOD Federated Cell Member9300-9305 (TCP)ElasticSearchElasticSearch Communication (data + management)
DPOD Cell
Manager
Manager (External IP address)Each DPOD Federated Cell Member60000-60003 (TCP)TCPSyslog keep-alive data
DPOD Cell Manager (External IP address)Each DPOD Federated Cell Member60020-60023 (TCP)TCPHTTP/S WS-M keep-alive data

NTP Server

DPOD Cell Manager (External IP address)

123 (UDP)

NTP

Time synchronization

Users IPs         

DPOD Cell Manager (External IP address)

443 (TCP)

HTTP/S

DPOD's Web Console

Admins IPs         

DPOD Cell Manager (External IP address)

22 (TCP)

TCP

SSH

Each DPOD Federated Cell Member  (internal IP address)DPOD Cell Manager443 (TCP)HTTP/SCommunication (data + management)
Each DPOD Federated Cell Member  (internal IP address)DPOD Cell Manager9200, 9300-9400ElasticSearchElasticSearch Communication (data + management)

Each DPOD Federated Cell Member (External IP address)

DNS Server

TCP and UDP 53

DNS

DNS services

Each DPOD Federated Cell Member (External IP address)

NTP Server

123 (UDP)

NTP

Time synchronization

Each Monitored Device

Each DPOD Federated Cell Member (External IP address)

60000-60003 (TCP)

TCP

SYSLOG Data

Each Monitored Device

Each DPOD Federated Cell Member (External IP address)

60020-60023 (TCP)

HTTP/S

WS-M Payloads

NTP Server

Each DPOD Federated Cell Member (External IP address)

123 (UDP)

NTP

Time synchronization

Admins IPs         

Each DPOD Federated Cell Member (External IP address)

22 (TCP)

TCP

SSH


Cell Manager Installation

...