Skip to main content

Installation Guide for RHEL

Overview​

This document provides step-by-step instructions to install Motadata AIOps on supported Red Hat Enterprise Linux (RHEL) versions.

Follow the appropriate tab based on your operating system version:

  • RHEL 9.4
  • RHEL 10.1

Minimum System Requirements for Motadata AIOps Server​

Before installing and running Motadata AIOps, 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.
  • Network Port should be open in Network Firewall and respective servers as defined below:

Network Port Specifications​

Port NamePort NumberPort TypeDirectionPort To Be Opened AtPurpose
Motadata Manager9440, 9441TCPBidirectionalApplication ServerFacilitates communication with Motadata Manager
Motadata Application9433, 9455, 9456, 9457, 9471, 9472, 9473, 9474, 9475, 9477TCPBidirectionalMotadata ApplicationEstablishes communication for Motadata Application with MotaStore. This port needs to be opened only when the application and database reside on different servers.
Event Publisher9444 to 9448TCPBidirectionalApplication ServerFacilitates 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 Subscriber9449 to 9453TCPBidirectionalApplication ServerFacilitates 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.
MotaStore9464, 6060, 6061TCPBidirectionalDatabase ServerFacilitates remote troubleshooting of MotaStore. These ports need to be opened only when troubleshooting is required for MotaStore.
TCP Log Listener5140TCPBidirectionalApplication Server or CollectorUsed 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 Listener514UDPInboundApplication Server or CollectorUsed 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)2055UDPInboundApplication Server or CollectorUsed 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)6343UDPInboundApplication Server or CollectorUsed 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)1620UDPInboundApplication ServerUsed to ingest trap into Motadata.
Trap Listener (v3)1630UDPInboundApplication ServerUsed to ingest trap into Motadata.
Event Processor9443TCPBiredirectionalApplication ServerProcesses event messages, offloading the processing load from the application server.
Web UI443HTTPSBidirectionalApplication ServerEnables user interface access from the browser.
Upgrade/Restore8080HTTPSBidirectionalApplication ServerUsed for upgrading Motadata artifacts from the UI
Important

Motadata AIOps (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

  1. 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.

  2. VM Snapshot: Before applying Antivirus, take a VM snapshot of all components: APP, DB, and Collector.

  3. 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-*'):

  • motadata-agent.exe
  • motadata-manager.exe
  • motadata-upgrade.exe
  • motadata-manager_m.exe
  • motadata-log-agent.exe
  • motadata-metric-agent.exe
  • motadatadb
  • nfacctd
  • sfacctd
  • datastorebroker
  • aiopsengine
  • gopluginengine

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.

Further, each version has specific deployment constraints and prerequisites. Ensure you follow the correct procedure strictly as defined.

note

Prerequisites for RHEL 9.4​

While installing RHEL 9.4, you also need to ensure:

  • RHEL 9.4 is installed and accessible.
  • You have root or sudo privileges.
  • The file AIOPS-RHEL.tar.gz is available.
  • The RHEL 9.4 ISO is accessible for mounting.

Installation Steps​

Step 1: Mount RHEL 9.4 ISO​

Create mount directory:

mkdir -p /mnt/repo

If ISO is attached via CD-ROM (Recommended):

info

While setting up the Motadata AIOps 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 (example: rhel-9.4-x86_64-dvd.iso):

mount -o loop rhel-9.4-x86_64-dvd.iso /mnt/repo/

Step 2: Extract AIOps Package​

Copy AIOPS-RHEL.tar.gz to any location and extract:

tar -xf AIOPS-RHEL.tar.gz

Step 3: Run Installation Script​

cd AIOPS-RHEL
./install.sh

You can also reboot the server by running below command:

reboot

Step 4: Run Post Installation Script​

After installation completes:

cd /opt/
./post-install.sh

Step 5: Start Motadata Service​

sudo motadata service start
info

Further post-installation steps are same as Linux for Distributed, HA, DR, Collector, and HA over WAN deployments.