Installation Guide for High Availability Over WAN
Overview
This installation guide provides step-by-step instructions for installing Motadata AIOps in a High Availability Deployment Over WAN, covering the installation process for High Availability Architecture:
- Single-Box High Availability Over WAN
- Distributed High Availability Over WAN
The installation process begins with common steps for all the scenarios, followed by deployment-specific steps. It is crucial to follow the instructions carefully to ensure a successful installation.
Minimum System Requirements for Motadata AIOps Server
Before installing and running Motadata AIOps, please ensure that your server meets the following minimum system requirements to ensure optimal performance and functionality. Refer Hardware Sizing document for detailed information for the same.
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 AIOps installation ISO.
- Network Port should be open in Network Firewall and respective servers as defined below:
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 | 9455, 9456, 9457 | TCP | Bidirectional | Motadata Application | Establishes communication for Motadata Application with MotaStore. 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. |
MotaStore | 9464, 6060, 6061 | TCP | Bidirectional | Database Server | Facilitates remote troubleshooting of MotaStore. These ports need to be opened only when troubleshooting is required for MotaStore. |
TCP Log Listener | 5140 | TCP | Bidirectional | 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. |
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 | Biredirectional | 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 |
High Availability | 9458, 9459 | TCP | Bidirectional | Application Server and Motadata Observer | Facilitates syncing of ConfigDB with Application Server |
Installation Steps
Create a virtual machine (VM).
Map the downloaded ISO to the VM datastore.
Boot the VM from the ISO to initiate the installation process.
Obtain sudo permissions by running the following command:
sudo su
The Installation steps will vary based on the deployment type you wish to configure, whether Single-Box HA Over WAN or Distributed HA Over WAN. Let us look into them one after the other.
Single-Box High Availability Over WAN
Navigate to the opt folder using the following command:
cd /opt
Check for the existence of the installation script (post-install.sh) using the following command:
ls
Run the installation script:
./post-install.sh
After you run the installation script, you will be asked to select the Deployment Type out of the following:
- Single-Box
- Distributed
- Collector
Select the Deployment Type (in this case, 1. Single-Box) that you want to configure and then follow the steps further as demonstrated below.
Select the Deployment Architecture(in this case, 4. High Availability over WAN) that you want to configure and then follow the steps further as demonstrated below.
For Single-Box HA Over WAN, you need to configure three servers, one as an observer, one as the primary server and another one as the secondary server.
Select the option 1. Observer if you want to start the installation for the Observer.
Select the option 2. Primary Server in the next step if you want to start the installation for the primary server.
Select the option 3. Secondary Server in the next step if you want to start the installation for the secondary server.
After selecting an option in 10th step above, move to the respective tab below to continue the installation based on the component that you have selected.
- Observer
- Primary Server
- Secondary Server
11. Change the root password by providing and confirming a new password.
12. Configure the static IP address, default gateway, and DNS servers. You can change the default DNS servers as per your requirement.
13. Configure the hostname.
14. Configure the timezone by selecting the region and timezone where you are installing the Motadata AIOps Observer.
15. The Observer is now successfully installed.
11. Change the root password by providing and confirming a new password.
12. Configure the static IP address, default gateway, and DNS servers. You can change the default DNS servers as per your requirement.
13. Configure the hostname.
14. Configure the timezone by selecting the region and timezone where you are installing the Primary Server.
15. Enter the Virtual IP/ FQDN address.
16. Enter the Observer IP address to establish the connection of the Primary Server with the Observer.
- Once the installation process is complete, Motadata AIOps application is accessible using the link specified below:
11. Change the root password by providing and confirming a new password.
12. Configure the static IP address, default gateway, and DNS servers. You can change the default DNS servers as per your requirement.
13. Configure the hostname.
14. Configure the timezone by selecting the region and timezone where you are installing the Secondary Server.
15. Enter Primary Server IP that you have already configured.
16. Enter the virtual IP address.
17. Enter the Observer IP address to establish the connection of the Secondary Server with the Observer.
18. The Secondary Server is now configured.
After installing all components, detach the ISO from the virtual machine to complete the installation.
Distributed High Availability Over WAN
Navigate to the config folder using the below-mentioned command:
cd /motadata/motadata/config
Type or copy and paste the below-mentioned commands in Motadata.JSON file:
"ha.mode" : "ACTIVE", //Primary App Server
"ha.mode" : "PASSIVE", //Secondary App Server
"ha.failover.nodes": 3 //All App Servers
Go back to the Root directory and navigate to the opt folder using the following command:
cd /opt
Check for the existence of the installation script (post-install.sh) using the following command:
ls
Run the installation script:
./post-install.sh
After you run the installation script, you will be asked to select the Deployment Type out of the following:
- Single-Box
- Distributed
- Collector
Select the Deployment Type(in this case, 2. Distributed) that you want to configure and then follow the steps further as demonstrated below.
Select the Deployment Architecture(in this case, 4. High Availability Over WAN) that you want to configure and then follow the steps further as demonstrated below.
For Distributed HA, you need to configure five servers : Observer, Primary App server, Primary DB server, Secondary App server, Secondary DB.
- Select the option 1. Observer if you want to start the installation for the Observer.
- Select the option 2. Primary App Server in the next step if you want to start the installation for the Primary Application Server.
- Select the option 3. Primary DB Server in the next step if you want to start the installation for the Primary Database Server.
- Select the option 4. Secondary App Server in the next step if you want to start the installation for the Secondary Application Server.
- Select the option 5. Secondary DB Server in the next step if you want to start the installation for the Secondary Database Server.
After selecting an option in 10th step above, move to the respective tab below to continue the installation based on the component that you have selected.
- Observer
- Primary App Server
- Primary DB Server
- Secondary App Server
- Secondary DB Server
13. Change the root password by providing and confirming a new password.
14. Configure the static IP address, default gateway, and DNS servers. You can change the default DNS servers as per your requirement.
15. Configure the hostname.
16. Configure the timezone by selecting the region and timezone where you are installing the Motadata AIOps Observer.
17. The Observer is now successfully installed.
13. Change the root password, providing and confirming a new password.
14. Configure the static IP address, default gateway, and DNS servers. You can change the default DNS servers as per your requirement.
15. Configure the hostname.
16. Configure the timezone by selecting the region and the timezone where you are installing the Primary Application Server.
17. Configure the virtual IP address.
18. Configure the Observer IP address to establish the connection of the Primary Application Server with the Observer.
19. Once the installation process is complete, Motadata AIOps application is accessible using the link specified below:
https://[IP]
where [IP] is the virtual IP you configured.
13. Change the root password by providing and confirming a new password.
14. Configure the static IP address, default gateway, and DNS servers. You can change the default DNS servers as per your requirement.
15. Configure the hostname.
16. Configure the timezone by selecting the region and the timezone where you are installing the Primary DB Server.
17. Configure the virtual IP address.
18. Once the installation process is complete, the Primary Database is now configured.
13. Change the root password, providing and confirming a new password.
14. Configure the static IP address, default gateway, and DNS servers. You can change the default DNS servers as per your requirement.
15. Configure the hostname.
16. Configure the timezone by selecting the region and the timezone where you are installing the Secondary Application Server.
17. Enter the Primary Application Server IP.
18. Enter the virtual IP address.
19. Enter the Observer IP address to establish the connection of the Secondary Application Server with the Observer.
Once the installation process is complete, the Secondary Application is now installed on the server
13. Change the root password by providing and confirming a new password.
14. Configure the static IP address, default gateway, and DNS servers. You can change the default DNS servers as per your requirement.
15. Configure the hostname.
16. Configure the timezone by selecting the region and the timezone where you are installing the Secondary Database Server.
17. Enter the Virtual IP that you have configured.
18. Once the installation process is complete, the Secondary Database is configured.
After installing all components, detach the ISO from the virtual machine to complete the installation.