For NMIS to function, certain network ports must be enabled for communication.
Network Management Traffic for NMIS
The following table shows the traffic required for using NMIS and complementary applications, e.g. using opConfig for configuration collection.
Port # | Protocol | Service name | Connection Initiation | Application | Notes |
161 | UDP | SNMP | Server to Device | NMIS |
|
162 | UDP | SNMP Traps | Device to Server | NMIS |
|
123 | UDP | NTP | Device to NTP Server | NMIS |
|
514 | UDP/TCP | syslog | Device to syslog Server | NMIS | syslogd, syslog-ng |
22 | TCP | SSH | Server to Device | opConfig |
|
23 | TCP | Telnet | Server to Device | opConfig |
|
389 | TCP | LDAP | Server to LDAP Server | NMIS | NMIS Authentication |
49 | TCP | TACACS+ | Device to TACACS Server | NMIS | NMIS Authentication |
123 | UDP | NTP | NMS Server to NTP Server | NMIS |
|
80 or 443 | TCP | HTTP or HTTPS | NMIS Master to NMIS Slave | NMIS opHA |
|
Network Management User Traffic for NMIS
The following table shows the traffic required for a user to communicate with NMIS or for NMIS to communicate to the user.
User | Port | Protocol | Service Name | Direction (of |
Customer | 80/443 | TCP | HTTP/HTTPS | Customer to NMIS Server |
NOC User | 80/443 | TCP | HTTP/HTTPS | NOC to NMIS Server |
NOC Admin | 22 | TCP | SSH | NOC to Server |
Email Notifications | 25 or 465 or 587 | TCP | SMTP or SMTP/SSL | NMIS Server to Mail Server |