Page Comparison

...

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

...