Installing Network Configuration Manager in 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:
Purchase Network Configuration Manager AMI from here.
Note: When you access 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 managing . For more details on Elastic IP address click here.
Pre-requisites
Before installing Network Configuration Manager at AWS, ensure that you meet the following pre-requisites
Important Note:
Ensure that the following ports in your Network Configuration Manager instance are not blocked for proper functioning of Network Configuration Manager and its add-ons ( this step is a must for running Network Configuration Manager from AMI as well as for running Network Configuration Manager 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. |
162 |
UDP |
Static |
SNMP Trap Receiver Port |
|
514 |
UDP |
Static |
SYSLOG Receiver Port |
SYSLOG Receiver Port can be changed via WebClient |
1514 |
UDP |
Static |
Secondary SYSLOG Receiver Port |
SYSLOG Receiver Port can be changed via WebClient |