Required Ports to Open in Firewalls
Table 1 lists the ports that need to be opened between the client and the server so that the client and server are able to communicate with each other. Most of the port numbers can be configured to user-defined port numbers if needed during the installation process.
Table 1: Required Ports to Open in Firewalls for Servers
Default Port Number | Used For |
---|---|
TCP 7000 | Connection to IP/MPLSView server |
TCP 5672 | Connection for IP/MPLSView to NorthStar Controller traffic |
TCP 3389 | LDAP (user login and administration) |
TCP 8091 | Webserver (HTTP) |
TCP 8443 | Webserver, SSL (HTTPS) |
TCP 2099 | Task Manager (RMI registry) |
TCP 1856 | JMS JNDI / RMI, JMS Bi-Socket (traffic collection) |
TCP 8093, 8094 | Telnet Proxy (connect to device) |
TCP 1098, 1099, 3873, 7911 | JNDI, RMI, EJB (used for SNMP, CLI, processes, and client-server file access). |
7077 | Event post Pport |
27017 | MongoDB application server |
Table 2: Required Ports to Open in Firewalls for Protocols
Default Port Number | Used For |
---|---|
TCP 22 | SSH |
TCP 23 | Telnet |
UDP 161 | SNMP GET |
UDP 162 | SNMP trap |
For HTTP tunneling, if there is a firewall between the client and server, the external IP address should also be configured in the Advanced Configuration Settings. For more information, see Additional Steps for Installing IP/MPLSView in a NAT Environment.
For more information about SSH tunneling, see Setting Up Port Forwarding for Secure Communications.
Port Map
Figure 1 illustrates the required ports and direction in a completely distributed environment using all server packages.
![]() | Note: The illustrations shows data flows, not physical connections. |
Figure 1: Port Map

Key
In the illustration:
- Base Ports are a group of ports used for offline and online networks.
- Clients are a group of ports used for performance management and fault management features using a client connection to the application server or Viewserver. The features marked with an asterisk (*) are only available for clients connected to the application server.
- Online Networks are a group of ports used for online networks.
Basic Configuration
- The Application Server is the main data processing and simulation server. The default installation setting installs the Database, LDAP, and Traffic Data Collector program packages on the application server. If these packages are not specified as distributed, then the port and direction along those paths can be ignored.
- The Client is the client machine running either Windows or Java Web Start.
- The Traffic Data Collector can be used to distribute the traffic collection.
Advanced Configuration
- The Viewserver complements the application server by offering a streamlined client for network operators and planners who don’t require the full capabilities of the application server. Only network administrators need the full capabilities of the client connected to the application server. Using the Viewserver offloads users and system resources from the application server.
- The Distributed Database server can be used for data storage on a server other than the application server.
- The Collection Server can be used for the remote VLAN autodiscovery module and remote data collection.
- The External LDAP server can be used for user administration and authentication on a server other than the application server. For more information, see the Security Management chapter in the IP/MPLSView Java-based Management and Monitoring Guide.
- The Backup Application server can be used with Rsync packages for redundancy.
- The Backup Database server can be used with Rsync and Replication packages for redundancy.
Port Table
Table 3 lists the required ports and direction by suite, module, or package for clients.
Table 3: IP/MPLSView Port Table For Clients
Source > Destination | Usage | Destination Port | Modules |
---|---|---|---|
Client > Application and Viewserver | Simulation Engine | 7000 | Management, Provision, Design Essentials |
Client > Application and Viewserver | Task Manager | 2099 | Management, Provision, Design Essentials |
Client > Application and Viewserver | Web Server | 8091 | Management Essentials, Web |
Client > Application and Viewserver | Web Server SSL | 8443 | Optional Secure Web |
Client > Application and Viewserver | Live Network | 2099, 1098, 1099 | Management, Provision Essentials |
Client > Application and Viewserver | Telnet Proxv | 8093, 8094 | Management, Provision Essentials |
Client > Application and Viewserver | View Live | 3873, 7911 | Performance Management |
Client > Application and Viewserver | MIB Browser | 3873 | MIB Browser |
Client > Application and Viewserver | Event Browser | 1856 | Fault Management |
Client > Application and Viewserver | Web Event Browser | 1856 | Fault Management |
Client > Application and Viewserver | User Admin | 3389 | Security Management |
Client > External LDAP | User Admin | 3389 | Security Management |
Table 4 lists the required ports and direction by suite, module, or package for the application client only.
Table 4: IP/MPLSView Port Table for the Application Client
Source > Destination | Usage | Destination Port | Modules |
---|---|---|---|
Client > Application | Traffic Manager | 1856 | Performance Management |
Client > Application | Event Subscription | 1856 | Fault Management |
Client > Application | Threshold Editor | 1856 | Threshold Crossing Alerts |
Table 5 lists the required ports and direction by suite, module, or package for the application and Viewserver.
Table 5: IP/MPLSView Port Table for the Application and Viewserver
Source > Destination | Usage | Destination Port | Modules |
---|---|---|---|
Application and Viewserver > Network | SNMP Get | 161 | Performance Management |
Application and Viewserver > Network | SSH | 22 | Management, Provision Essentials |
Application and Viewserver > Network | Telnet | 23 | Management, Provision Essentials |
Network > Application and Viewserver | SNMP Trap | 162 | Fault Management |
Application and Viewserver > Database | Rsync | 22 | Rsync and Replication |
Application and Viewserver > Database | MySQL | 3333 | Distributed Database |
Traffic Data Collector > Application and Viewserver | Traffic Data Collection | 1856 | Performance Management |
Table 6 lists the required ports and direction by suite, module, or package for the Traffic Data Collector.
Table 6: IP/MPLSView Port Table for the Traffic Data Collector
Source > Destination | Usage | Destination Port | Modules |
---|---|---|---|
Traffic Data Collector > Network | SNMP Get | 161 | Performance Management |
Traffic Data Collector > Network | SSH | 22 | Performance Management |
Traffic Data Collector > Network | Telnet | 23 | Performance Management |
Network > Traffic Data Collector | FTP, SFTP Bulkstats | 21, 22 | Performance Management |
Table 7 lists the required ports and direction by suite, module, or package for the primary and backup application servers.
Table 7: IP/MPLSView Port Table for the Primary and Backup Servers
Source > Destination | Usage | Destination Port | Modules |
---|---|---|---|
Primary Application > Backup Application | Rsync | 22 | Rsync and Replication |
Primary Database > Backup Database | Rsync | 22 | Rsync and Replication |
Backup Database > Primary Database | MySQL | 3333 | Rsync and Replication |
Table 8 lists the required ports and direction by suite, module, or package for the Remote Collection Server.
Table 8: IP/MPLSView Port Table for the Remote Collection Server
Source > Destination | Usage | Destination Port | Modules |
---|---|---|---|
Remote Collection Server > Application | Data Collection | 1856 | Management Essentials |
Remote Collection Server > Application | SNMP Trap | 162 | Management Essentials |
Application > Remote Collection Server | Task Manager | 2099 | Management Essentials |
Application > Remote Collection Server | Proxy Relay | 7911 | Management Essentials |