How to install OpManager in AWS?

Installing OpManager in AWS helps in ensuring world class network management for your device while eliminating the need for a physical server for monitoring.

You can use OpManager in AWS using one of the 2 methods:

 

Running OpManager from AMI

Purchase OpManager AMI from here. 

  • While purchasing, you will be prompted to select the EC2 instance of your choice based on certain preconfiguration.
  • Select the required instance and launch AMI using admin as username and instanceid as password.

Note: When you access the OpManager using the public IP/DNS address, note that the "Public IP/DNS address" changes when the instance is stopped/terminated. As in a network, devices need to forward syslogs & traps to the OpManager server, the public IP has to be updated in the end devices every time it changes. Hence it is recommended to use an elastic IP address for seamless monitoring . For more details on Elastic IP address click here.

 

Running OpManager from EC2 instance

Pre-requisites 

Before installing OpManager at AWS, ensure that you meet the following pre-requisites

  1. Say if you are planning to manage up to 250 devices using OpManager, we recommend you to have the following instance configurations
    • EC2 instance type m4.xlarge or above
    • OS - Windows 10/8/7 or Windows server 2008 or above ( upto 2019 supported ).
    • 20 GB memory space ( minimum )
  1. Note: The above specified are the minimum requirements. You may have to change the configurations according to the number of devices you are monitoring and additional integrations / modules ( such as firewall, IP address management etc ). To know more about creating instance click here.
  2. Ensure that the instance's Public IP/DNS is not blocked by any firewall and is accessible to all devices in your network.
  3. Ensure that the required security ports are available for use.

Steps to install and run amazon from EC2 instance

  1. Remotely connect to your EC2 instance
  2. In that instance, open your web browser
  3. Download and install OpManager. 
  4. Login to OpManager using username as admin and password as admin.

Important Note: 
Ensure that the following ports in your OpManager instance are not blocked for proper functioning of OpManager and its add-ons ( this step is a must for running OpManager from AMI as well as for running OpManager from an EC2 instance):

Port

Protocol 

Port Type 

Usage 

Remarks 

13306

TCP 

Static (PostgreSQL)

Database Port

Can be changed in conf/database_params.conf file.

1433

TCP

Static (MS SQL) 

Database Port 

Can be changed in conf/database_params.conf file/ dbconfiguration.bat file.

22 

TCP 

Static 

SSH Port 

 

8060

TCP 

Static 

Web Server Port 

Can be configured using ChangeWebServerPort.bat. 

161

UDP

Static 

SNMP

 

135

TCP

Static 

WMI

 

445

TCP 

Static 

WMI

 

5000 to 6000

TCP 

Dynamic

WMI

 

49152 to 65535

TCP

Dynamic

WMI

Windows 2008R2 and higher

2000

TCP

Static

Internal Communication Port

 

56328

TCP

Dynamic

ShutDown Listener Port

 

162

UDP

Static

SNMP Trap Receiver Port

 

514

UDP

Static

SYSLOG Receiver Port

SYSLOG Receiver Port can be changed via WebClient

69

UDP

Static 

TFTP Port [NCM]

 

1514

UDP

Static 

Firewall Log Receiver [FWA]

Firewall Receiver Port can be changed via WebClient

9996

TCP

 

NetFlow Listener Port [NFA]

NetFlow Listener Port can be changed via WebClient