...
- Cell Manager - a DPOD server (virtual or physical) that manages all Federated Cell Members (FCMs) as well as provides central providing central DPOD services such as the Web Console, reports, alerts, etc.
- Federated Cell Member (FCM) - a DPOD server (usually physical with local high speed storage) that includes Store data nodes and agents (Syslog and WS-M) for collecting, parsing and storing data. There could be one or more federated cell members per cell.
See the The following diagram shows the Cell Environment topology:
The following procedure describes the process of establishing a DPOD cell environment.
...
- DPOD cell manager and federated cell members must be with of the same version (minimum version is v1.0.8.5).
- 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 either virtual or physical.
- DPOD federated cell member (FCM) should be installed in Non-appliance Mode with High_20dv architecture type, as detailed in the Hardware and Software Requirements.
- Each cell component (manager / FCM) should have two network interfaces:
- External interface - for DPOD users to access the Web Console and for communication between DPOD and Monitored Gateways.
- Internal interface - for internal DPOD components inter-communication (should be a 10Gb Ethernet interface).
- Network ports should be opened in the network firewall as detailed below:
...
| Note |
|---|
As described in the prerequisites section, the federated cell member should have two network interfaces. |
- After DPOD's installation is complete, the user should execute the following operating system performance optimization script:
...
| Code Block | ||
|---|---|---|
| ||
/app/scripts/configure_cell_manager.sh -a <internal IP address of the cell member> -g <external IP address of the cell member> For example: /app/scripts/configure_cell_manager.sh -a 172.18.100.34 -g 172.17.100.33 |
Example
...
of a Successful Execution
| Code Block | ||
|---|---|---|
| ||
/app/scripts/configure_cell_manager.sh -a 172.18.100.36 -g 172.17.100.35 2018-10-22_16-13-16 INFO Cell Configuration 2018-10-22_16-13-16 INFO =============================== 2018-10-22_16-13-18 INFO 2018-10-22_16-13-18 INFO Log file is : /installs/logs/cell_manager_configuration-2018-10-22_16-13-16.log 2018-10-22_16-13-18 INFO 2018-10-22_16-13-18 INFO Adding new cell member with the following configuration : 2018-10-22_16-13-18 INFO Cell member internal address 172.18.100.36 2018-10-22_16-13-18 INFO Cell member external address 172.17.100.35 2018-10-22_16-13-18 INFO Syslog agents using TCP ports starting with 60000 2018-10-22_16-13-18 INFO Wsm agents using TCP ports starting with 60020 2018-10-22_16-13-18 INFO 2018-10-22_16-13-18 INFO During the configuration process the system will be shut down, which means that new data will not be collected and the Web Console will be unavailable for users. 2018-10-22_16-13-18 INFO Please make sure the required network connectivity (e.g. firewall rules) is available between all cell components (manager and members) according to the documentation. 2018-10-22_16-13-18 INFO 2018-10-22_16-13-20 INFO Please choose the IP address for the cell manager server internal address followed by [ENTER]: 2018-10-22_16-13-20 INFO 1.) 172.18.100.32 2018-10-22_16-13-20 INFO 2.) 172.17.100.31 1 2018-10-22_16-14-30 INFO Stopping application ... 2018-10-22_16-15-16 INFO Application stopped successfully. root@172.18.100.36's password: 2018-10-22_16-21-41 INFO Cell member configuration ended successfully. 2018-10-22_16-21-45 INFO Stopping application ... 2018-10-22_16-22-31 INFO Application stopped successfully. 2018-10-22_16-22-31 INFO Starting application ... |
Note that the script writes two log file, one in the cell manager and one in the cell member. The log file names are mentioned in the script's output.
Example
...
of a Failed Execution
| Code Block | ||
|---|---|---|
| ||
/app/scripts/configure_cell_manager.sh -a 172.18.100.36 -g 172.17.100.35 2018-10-22_16-05-03 INFO Cell Configuration 2018-10-22_16-05-03 INFO =============================== 2018-10-22_16-05-05 INFO 2018-10-22_16-05-05 INFO Log file is : /installs/logs/cell_manager_configuration-2018-10-22_16-05-03.log 2018-10-22_16-05-05 INFO 2018-10-22_16-05-05 INFO Adding new cell member with the following configuration : 2018-10-22_16-05-05 INFO Cell member internal address 172.18.100.36 2018-10-22_16-05-05 INFO Cell member external address 172.17.100.35 2018-10-22_16-05-05 INFO Syslog agents using TCP ports starting with 60000 2018-10-22_16-05-05 INFO Wsm agents using TCP ports starting with 60020 2018-10-22_16-05-05 INFO 2018-10-22_16-05-05 INFO During the configuration process the system will be shut down, which means that new data will not be collected and the Web Console will be unavailable for users. 2018-10-22_16-05-05 INFO Please make sure the required network connectivity (e.g. firewall rules) is available between all cell components (manager and members) according to the documentation. 2018-10-22_16-05-05 INFO 2018-10-22_16-05-06 INFO Please choose the IP address for the cell manager server internal address followed by [ENTER]: 2018-10-22_16-05-06 INFO 1.) 172.18.100.32 2018-10-22_16-05-06 INFO 2.) 172.17.100.31 1 2018-10-22_16-05-09 INFO Stopping application ... 2018-10-22_16-05-58 INFO Application stopped successfully. root@172.18.100.36's password: 2018-10-22_16-06-46 ERROR Starting rollback 2018-10-22_16-06-49 WARN Issues found that may need attention !! 2018-10-22_16-06-49 INFO Stopping application ... 2018-10-22_16-07-36 INFO Application stopped successfully. 2018-10-22_16-07-36 INFO Starting application ... |
In case of a failure, the script will try to rollback the configuration changes it made, so the problem can be fixed before rerunning re-running it again.
Cell Member Federation Post Steps
...
The services files are located on the directory /etc/init.d/ with the namea nama MonTier-es-raw-trans-Node-2 and MonTier-es-raw-trans-Node-3.
...