Installation Guide for RHEL
Overview
This document provides step-by-step instructions to install Motadata ObserveOps on supported Red Hat Enterprise Linux (RHEL) versions.
Follow the appropriate tab based on your operating system version:
- RHEL 10.1
Minimum System Requirements for Motadata ObserveOps Server
Before installing and running Motadata ObserveOps, please ensure that your server meets the minimum system requirements of 12 vCPU, 12 GB of RAM, and 500 GB of disk storage for Observability edition to ensure optimal performance and functionality.
Prerequisites
Before starting the installation, ensure the following prerequisites are met:
- Configure servers based on the sizing requirements of the chosen component.
- Download the Motadata ObserveOps installation TAR.
- RHEL 10.1 is installed.
- The
/motadatadirectory is mounted and added tofstab. You can verify the mount using:df -Th - The
motadatauser hasNOPASSWDsudo access. Verify that switching to root usingsuworks as expected. OBSERVEOPS-RHEL.tar.gzpackage is available.- RHEL 10.1 ISO is accessible.
- VAPT compliance requirements are available (if applicable).
- Network Port should be open in Network Firewall and respective servers as defined below:
Set a valid hostname on each Linux server before installation. Use only lowercase letters (a–z), digits (0–9), and hyphens (-). Do not start or end the hostname with a hyphen. Each label between dots must be 63 characters or fewer.
Network Port Specifications
| Port Name | Port Number | Port Type | Direction | Port To Be Opened At | Purpose |
|---|---|---|---|---|---|
| Motadata Manager | 9440, 9441 | TCP | Bidirectional | Application Server | Facilitates communication with Motadata Manager |
| Motadata Application | 9433, 9455, 9456, 9457, 9477 | TCP | Bidirectional | Motadata Application | Establishes communication for Motadata Application. This port needs to be opened only when the application and database reside on different servers. |
| Event Publisher | 9444 to 9448 | TCP | Bidirectional | Application Server | Facilitates communication between MotaAgent and the Application Server. Typically, 9444 and 9445 ports are mandatory, but multiple ports may need to be open to support load balancing when a significant number of agents are used. |
| Event Subscriber | 9449 to 9453 | TCP | Bidirectional | Application Server | Facilitates communication between MotaAgent and the Application Server. Typically, 9449 and 9450 ports are mandatory, but multiple ports may need to be open to support load balancing when a significant number of agents are used. |
| Database | 9000 TCP, 8123 HTTPS | TCP, HTTPS | Bidirectional | Database Server | Establishes communication between application and database. |
| TCP Log Listener | 5140 | TCP | Bidirectional | Application Server or Collector | Used to ingest logs into Motadata in an encrypted format for secure data transfer. Ensure this port is open on the collector if logs need to be ingested at the collector level. |
| UDP Log Listener | 514 | UDP | Inbound | Application Server or Collector | Used to ingest logs into Motadata. Ensure this port is open on the collector if logs need to be ingested at the collector level. |
| Flow Listener (netflow) | 2055 | UDP | Inbound | Application Server or Collector | Used to ingest flow data into Motadata. Ensure this port is open on the collector if flow data needs to be ingested at the collector level. |
| Flow Listener (sflow) | 6343 | UDP | Inbound | Application Server or Collector | Used to ingest flow data into Motadata. Ensure this port is open on the collector if flow data needs to be ingested at the collector level. |
| Trap Listener (v1/v2) | 1620 | UDP | Inbound | Application Server | Used to ingest trap into Motadata. |
| Trap Listener (v3) | 1630 | UDP | Inbound | Application Server | Used to ingest trap into Motadata. |
| Event Processor | 9443 | TCP | Bidirectional | Application Server | Processes event messages, offloading the processing load from the application server. |
| Web UI | 443 | HTTPS | Bidirectional | Application Server | Enables user interface access from the browser. |
| Upgrade/Restore | 8080 | HTTPS | Bidirectional | Application Server | Used for upgrading Motadata artifacts from the UI |
Motadata ObserveOps (APP, DB, Collector) – Antivirus Whitelist Guidelines
Motadata does not recommend applying Antivirus on Application (APP), Datastore (DB) or Collector components. However, in cases where client compliance mandates Antivirus installation, please carefully follow the guidelines below.
General Considerations
Resource Utilization: Installing antivirus on Motadata components will significantly add resource overhead which may lead to abnormal monitoring activity. Consider increasing resources to compensate this overhead.
VM Snapshot: Before applying Antivirus, take a VM snapshot of all components: APP, DB, and Collector.
Monitoring: Keep the environment under observation after applying the Antivirus with the below prerequisites configured.
Folders & Files to Whitelist
Whitelist the following directory and executables from real-time and scheduled Antivirus scans:
Directory Path: /motadata
Executables (whitelist all matching 'motadata*')
Also, make sure to exclude all listed directory and executables from both real-time scanning and scheduled scans and ensure security agents/firewalls allow continuous communication over the specified ports. Then, apply these rules for both on-premises deployments and remote/endpoint devices running Motadata Agents.
Step 1: Mount RHEL 10.1 ISO
Create mount directory:
mkdir -p /mnt/repo
If ISO is attached via CD-ROM (Recommended):
While setting up the Motadata ObserveOps VM, ensure the CD-ROM ISO checkbox is selected so the RHEL ISO is attached as a virtual CD-ROM. This is required to mount the ISO using /dev/sr0 when you follow the CD-ROM based ISO mount steps.
mount -o loop /dev/sr0 /mnt/repo/
If ISO file exists on server:
mount -o loop {RHEL_Filename}.iso /mnt/repo/
RHEL_Filename can be like rhel-10.1-x86_64-dvd.iso
Step 2: Copy and Extract ObserveOps Package
cd /motadata
tar -xf ObserveOps-RHEL.tar.gz
Then, confirm the ObserveOps-RHEL directory was created:
ls -l
Step 3: Run RHEL 10 Installation Script
cd ObserveOps-RHEL
chmod +x install-rhel-10.sh
sudo ./install-rhel-10.sh
Step 4: Run ObserveOps Post-Install Script
Execute ObserveOps post-install script as mentioned below.
cd ObserveOps-RHEL
chmod +x postinstall.sh
sudo ./postinstall.sh
Further post-installation steps are same as Linux for Standalone, Distributed, HA, DR, Collector, and HA over WAN deployments.
For Standalone Deployment follow the steps mentioned after step 7 mentioned in the Installation Guide for Single-Box Standalone Deployment
For Distributed Deployment follow the steps mentioned after step 7 mentioned in the Installation Guide for Distributed Standalone Deployment
For HA Deployment follow the steps mentioned after step 7 mentioned in the Installation Guide for High Availability Deployment
For DR Deployment follow the steps mentioned after step 4 mentioned in the Installation Guide for Disaster Recovery Deployment
For Collector Deployment follow the steps mentioned after step 7 mentioned in the Installation Guide for Collector Deployment
For HA Over WAN Deployment follow the steps mentioned after step 7 mentioned in the Installation Guide for High Availability Over WAN