Page Comparison

...

1. DPOD cell manager and federated cell members must be with the same version (minimum version is v1.0.9.0).
2. DPOD cell manager can be installed in both Appliance Mode or Non-Appliance Mode with Medium Load architecture type, as detailed in the Hardware and Software Requirements. The manager server can be both virtual or physical.
3. DPOD federated cell member (FCM) should be installed in Non-appliance Mode with High_20dv with High Load architecture type, as detailed in the Hardware and Software Requirements.
4. Each cell component (manager / FCM) should have two network interfaces:
   
   1. External interface - for DPOD users to access the Web Console and for communication between DPOD and Monitored Gateways.
   2. Internal interface - for internal DPOD components inter-communication (should be a 10Gb Ethernet interface).
5. Network ports should be opened in the network firewall as detailed below:

...

• DPOD federated cell member (FCM) should be installed in Non-appliance Mode with High_20dv with High Load architecture type, as detailed in the Hardware and Software Requirements.
• The following software packages (RPMs) should be installed: iptables, iptables-services, numactl
• The following software packages (RPMs) are recommended for system maintenance and troubleshooting, but are not required: telnet client, net-tools, iftop, tcpdump

Installation

DPOD

...

Installation

• Install DPOD in Non-Appliance Mode: Installation procedure

...

...

Preparing Cell Member for Federation

...

Preparing Mount Points

The cell member is usually a "bare metal" server with NVMe disks for maximizing server throughput.

Each of the Store's logical node (service) will be bound to a specific physical processor, disks and memory using NUMA (using NUMA technology → Non-uniform memory access )Uniform Memory Access) technology.

The default cell member configuration assume assumes 6 NVMe disks which will serve 3 Store data logical nodes (2 disks per node).

The following OS mount points should be configured by the user before federating the DPOD installation cell member to "the cell member"environment.

note - colored table cells Empty cells in the following table should be completed by the user, based on his their specific hardware.:

How to

...

Identify Disk OS

...

Path and Disk

...

Serial

1. To identify which of the server's NVMe disk bay bays is bound to which of the CPU CPUs, use the hardware manufacture documentation.
   Also, write down the disk's serial number by visually observing the disk.

2. In order to identify the disk os OS path (example e.g.: /dev/nvme01n) and the disk serial the user should , install the NVMe disk utility software provided by the hardware supplier. Example For example: for Intel-based NVMe SSD disks, install the "Intel® SSD Data Center Tool"   (isdct).
   Example output of the Intel SSD DC tool:

   Code Block
   theme RDark
   isdct show -intelssd - Intel SSD DC P4500 Series PHLE822101AN3PXXXX - Bootloader : 0133 DevicePath : /dev/nvme0n1 DeviceStatus : Healthy Firmware : QDV1LV45 FirmwareUpdateAvailable : Please contact your Intel representative about firmware update for this drive. Index : 0 ModelNumber : SSDPE2KE032T7L ProductFamily : Intel SSD DC P4500 Series SerialNumber : PHLE822101AN3PXXXX

   
   

3. Use the disks disk bay number and the disk serial number (visually identified) and correlate them with the output of the disk tool to identify the disk os OS path.

...

Example for Mount Points and Disk Configurations

Example

...

for LVM Configuration

pvcreate -ff /dev/nvme0n1
vgcreate vg_data2 /dev/nvme0n1
lvcreate -l 100%FREE -n lv_data vg_data2
mkfs.xfs -f /dev/vg_data2/lv_data

pvcreate -ff /dev/nvme1n1
vgcreate vg_data22 /dev/nvme1n1
lvcreate -l 100%FREE -n lv_data vg_data22
mkfs.xfs /dev/vg_data22/lv_data

The /etc/fstab file:

/dev/vg_data2/lv_data    /data2                   xfs     defaults        0 0
/dev/vg_data22/lv_data   /data22                   xfs     defaults        0 0
/dev/vg_data3/lv_data    /data3                   xfs     defaults        0 0
/dev/vg_data33/lv_data   /data33                   xfs     defaults        0 0
/dev/vg_data4/lv_data    /data4                   xfs     defaults        0 0
/dev/vg_data44/lv_data   /data44                   xfs     defaults        0 0

...

Example for the Final Configuration for 3 Store's nodes

# lsblk

NAME                MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
nvme0n1             259:0    0   2.9T  0 disk
└─vg_data2-lv_data  253:6    0   2.9T  0 lvm  /data2
nvme1n1             259:5    0   2.9T  0 disk
└─vg_data22-lv_data 253:3    0   2.9T  0 lvm  /data22
nvme2n1             259:1    0   2.9T  0 disk
└─vg_data3-lv_data  253:2    0   2.9T  0 lvm  /data3
nvme3n1             259:2    0   2.9T  0 disk
└─vg_data33-lv_data 253:5    0   2.9T  0 lvm  /data33
nvme4n1             259:4    0   2.9T  0 disk
└─vg_data44-lv_data 253:7    0   2.9T  0 lvm  /data44
nvme5n1             259:3    0   2.9T  0 disk
└─vg_data4-lv_data  253:8    0   2.9T  0 lvm  /data4

...

Preparing Local OS Based Firewall

Most Linux-based OS uses a local firewall service (e.g.: iptables / firewalld).

The OS for "non Since the OS of the Non-Appliance Mode " DPOD installation is provided by the user and its , it is under the user's responsibility to allow needed connectivity to and from the server.

User should make sure needed connectivity detailed on table 1 in Network Ports Table is allowed on the OS local firewall service.

...