Accessing Network Configuration Manager on AWS


Running Network Configuration Manager on AWS helps in ensuring world class network configuration management for your network while eliminating the need for a physical server.

You can use Network Configuration Manager in AWS using one of the 2 methods:

By purchasing and running Network Configuration Manager AMI from AWS store

Before you begin, please purchase Network Configuration Manager AMI from here.

  • After the purchase of the AMI, you will be required to launch an EC2 instance from this AMI. For more information on how to do this, please check this page. While creating the instance, ensure that the following metrics meet the required criteria:

 

MetricCriteria
EC2 Instance Typem4.xlarge or above
Operating SystemWindows 10/8/7 (or) Windows Server 2008 and newer (Supported up to 2019 )
Storage20 GB (minimum)
  • Once the instance is launched from the given AMI, you need to initiate an RDP session of the particular instance. To learn more about this action, please check this page.
  • Use the RDP session to log into the instance.
  • After logging in to the instance, go to the Services app. To do this, type "Services" into the Windows search bar, and click on the Services app result.
  • In the Services app, check whether the following service is running: ManageEngine Network Configuration Manager .
  • If ManageEngine Network Configuration Manager service is in a running state, go to your browser and connect to Network Configuration Manager's console using either of these two ports:

(a) http://<ec2_instance_public_dns>:8060 (for http connection)

(b) https://<ec2_instance_public_dns>:8061 (for https connection)

  • Log in to Network Configuration Manager using the following credentials:

Username: admin

Password: --Instance ID--

Note: When you access the Network Configuration Manager 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 Network Configuration Manager 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.

By installing Network Configuration Manager in a separate EC2 instance

Pre-requisites

Before installing Network Configuration Manager in AWS, ensure that you meet the following pre-requisites

  1. Say if you are planning to manage up to 250 devices using Network Configuration Manager , 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 (up to 2019 supported )
    • 20 GB memory space (minimum)

    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 Network Configuration Manager .
  4. Login to Network Configuration Manager using username as admin and password as admin.

Important Note:
Ensure that the following ports are not blocked for the proper functioning of Network Configuration Manager (this step is a must for running Network Configuration Manager from AMI as well as for running Network Configuration Manager from an EC2 instance):

PortProtocolPort TypeUsageRemarks
13306TCP Static (PostgreSQL)Database PortCan be changed in conf/database_params.conf file.
1433TCPStatic (MS SQL) Database Port Can be changed in conf/database_params.conf file/ dbconfiguration.bat file.
22 TCP Static SSH Port  
8060TCP Static HTTP Web Server Port Can be configured using ChangeWebServerPort.bat. 
8061TCP Static HTTPS Web Server Port Can be configured using ChangeWebServerPort.bat. 
161UDPStatic SNMP 
2000TCPStaticInternal Communication Port 
56328TCPDynamicShutDown Listener Port 
514UDPStaticSYSLOG Receiver PortSYSLOG Receiver Port can be changed via WebClient
69UDPStatic TFTP Port [NCM] 

 

Thank you for your feedback!

Was this content helpful?

We are sorry. Help us improve this page.

How can we improve this page?
Do you need assistance with this topic?
By clicking "Submit", you agree to processing of personal data according to the Privacy Policy.