Skip to main content

Support Environment

WhaTap Network Control Management System is installed on a standalone virtual machine (VM) in a standalone manner. This allows the network management system to operate independently and reliably provide all the features required for network monitoring and management.

System requirements​

The following are the recommended minimum specifications to ensure stable performance of the WhaTap Network Management System.

ItemSpecification
CPU4 core (minimum 2 core)
MemoryMinimum 16GB or more (minimum 8G)
Disk50G or more SSD recommended (minimum 30G)
Network Interface1Gbps or more

OS support​

OSPython versionSupport status
Ubuntu 22.043.10Supported, Recommended
Ubuntu 23.043.11Supported
Ubuntu 24.043.12Supported
Rocky 9.43.9Supported, Recommended
Rocky 8.103.11Supported
Redhat 8.103.11Supported, Recommended

Python version support​

Support is available depending on the Python version regardless of the OS type. However, it is recommended to use the recommended OS whenever possible.

FamilySupported Python versions
Debian familyPython 3.10, 3.11, 3.12
Redhat familyPython 3.9, 3.10, 3.11, 3.12

TCP/UDP ports used​

The specified TCP and IP port numbers are the default ports used by the service and can be changed to suit the customer's environment.

CategoryTCPUDPDescriptionDirectionNotes
SNMP-161pollingOutboundDefault port
SNMP Trap-162trap messageInboundDefault port
syslog-514syslog messageInboundDefault port
manager U/I5000(http)
8443(https)		-NMS Control Manager GUIInboundDefault http, requires port 8443 permission when using https
whatap collection server6600-Data transmissionOutbound-
ICMP--ICMP health Check-ICMP protocol permission required
TCP--TCP-based health CheckIn/OutMonitoring target TCP port number connection permission required (Options)

Firewall​

The WhaTap agent must be able to access the collection server through TCP port 6600. Allow access to the collection server address that is closest to the monitored target.

Source: WhaTap agent

CloudDestinationDestination IPPort
AWSWhaTap collection server (Seoul)13.124.11.223 / 13.209.172.35TCP 6600
WhaTap collection server (Tokyo)52.68.36.166 / 52.193.60.176TCP 6600
WhaTap collection server (Singapore)18.138.0.93 / 18.139.67.236TCP 6600
WhaTap Jakarta collection server108.136.91.69 / 108.137.158.44TCP 6600
WhaTap collection server (Mumbai)13.127.125.69 / 13.235.15.118TCP 6600
WhaTap collection server (California)52.8.223.130 / 52.8.239.99TCP 6600
WhaTap Virginia collection server107.23.220.101 / 54.236.221.105TCP 6600
WhaTap collection server (Frankfurt)3.125.142.162 / 3.127.76.140TCP 6600
AzureWhaTap collection server (Seoul)52.231.66.38 / 20.194.5.115TCP 6600
WhaTap collection server (Tokyo)52.246.169.54 / 20.210.27.232TCP 6600
KakaoWhaTap collection server (Seoul)61.109.237.237 / 61.109.238.166TCP 6600

If the agent cannot directly access the collection server, use the provided proxy module to access it.

Proxy

Main service components and ports​

NMS Control Manager Web-Based U/I​

uvicorn.service is a management UI and API service that runs in a local environment, providing overall operational management functions such as NMS configuration management, system status check, and configuration backup and recovery.

  • Ports used: HTTP 5000, HTTPS 8443 (when configured)

  • Service start and stop: You can start, stop, or restart uvicorn.service with the following command.

    systemctl {start|restart|stop} uvicorn.service
Note

Please contact the WhaTap technical team for manager access information.

NMS engine​

nmscore.service is a service that acts as the engine of the Network Management System (NMS). It provides network device and traffic monitoring, management, and event processing functions.

  • Ports used:

    • SNMP Trap: UDP 162 (default)
    • Syslog: UDP 514 (default)

  • Service start and stop: You can start, stop, or restart nmscore.service with the following command.

    systemctl {start|restart|stop} nmscore.service

Health Check​

icmptcphealthd.service performs ICMP and TCP-based Health Check on network devices and continuously monitors device availability and connection status through periodic status checks.

  • Service start and stop: You can start, stop, or restart icmptcphealthd.service with the following command.

    systemctl {start|restart|stop} icmptcphealthd.service
Last updated on