ipMonitor 11.0 system requirements
SolarWinds strongly recommends that you install ipMonitor on a server that is protected from unauthorized access by the public. If your use of ipMonitor does not need to be public or internet-facing, install it on a server that is neither public, nor internet-facing. To learn about best practices for configuring your ipMonitor installation securely, see Best practices to secure SolarWinds Products.
See the following sections for the minimum supported requirements:
For additional information, see the ipMonitor 11.0 Release Notes.
Hardware requirements
Set up your SolarWinds ipMonitor server using the following minimum hardware requirements.
Hardware or Software | Requirements |
---|---|
CPU | Single core 2.0 GHz |
Memory | 512 MB |
Hard drive space | 240 MB |
Software requirements
Set up your SolarWinds ipMonitor server using the following software requirements.
Software | Requirements |
---|---|
Operating system |
Windows Server 2012 with .NET Framework 4.5 Windows Server 2012 R2 Windows Server 2016 Windows Server 2019 Windows 8 Windows 10 |
Web browser |
Apple Safari Google Chrome Microsoft Internet Explorer (IE) 11 or later Mozilla Firefox |
Port requirements
Below are the local and monitor port requirements for ipMonitor.
Local ports
Port | Protocol | Service / Process |
---|---|---|
8080 | HTTP | Default port |
443 | HTTPS | SSL or administrator assigned |
Monitor ports
The following table provides the various ports that are used in ipMonitor, depending on which monitor is enabled.
ipMonitor supports up to 2,500 monitors.
Port | Protocol | Service / Process | Monitor |
---|---|---|---|
389 | TCP | Active Directory | ACTIVE DIRECTORY |
161 | UDP | Bandwidth | BANDWIDTH USAGE |
161 | UDP | Battery | BATTERY |
161 | UDP | Processor Usage | CPU USAGE |
N/A |
SMB NFS |
Directory Usage | DIRECTORY MONITOR |
53 | TCP | Quality Assurance Domain Name Service | DNS-QA |
53 | TCP | Domain Name Service - Transmission Control Protocol | DNS-TCP |
53 | UDP | Domain Name Service - User Datagram Protocol | DNS-UDP |
161 | UDP | Drive Space Availability | DRIVE SPACE |
N/A | N/A | NT Event Log Monitor | EVENT LOG |
N/A | N/A | Microsoft® Exchange Server | EXCHANGE SERVER |
N/A | N/A | Executable File | EXTERNAL PROCESS |
161 | UDP | Fan Status | FAN MONITOR |
N/A |
SMB NFS |
Any File Type | FILE PROPERTY |
N/A |
SMB NFS |
Any File Type | FILE WATCHING |
79 | TCP | Finger Information Server | FINGER |
21 | TCP | File Transfer Protocol | FTP |
21 | TCP | Quality Assurance File Transfer Protocol | FTP-QA |
70 | TCP |
Menu driven front end to resource service, such as anonymous FTP |
GOPHER |
80 | TCP | HyperText Transfer Protocol | HTML / ASP |
80 | TCP | HyperText Transfer Protocol | HTTP |
80 | TCP | Quality Assurance HyperText Transfer Protocol | HTTP-QA |
443 | TCP | Hypertext Transfer Protocol Secure | HTTPS |
161 | UDP | Humidity Levels | HUMIDITY |
143 | TCP | Internet Message Access Protocol | IMAP4 |
143 | TCP | Quality Assurance Internet Message Access Protocol | IMAP4-QA |
80 443 |
TCP | ipMonitor | IPMONITOR |
6667 | TCP | Internet Relay Chat | IRC |
88 | UDP | Kerberos 5 | KERBEROS 5 |
389 | UDP | Lightweight Directory Access Protocol | LDAP |
80 | TCP | Quality Assurance Link | LINK-QA |
1352 | TCP | Lotus Notes™ Transport | LOTUS NOTES |
N/A | N/A | Microsoft Messaging Application Program Interface | MAPI-QA |
161 | UDP | Physical Memory (RAM) | MEMORY USAGE |
19 | TCP | Speed or Bandwidth Monitor | NETWORK SPEED |
119 | TCP | Network News Transfer Protocol | NNTP |
123 | UDP | Network Time Protocol | NTP |
N/A | ICMP | Packet InterNet Groper | PING |
110 | TCP | Post Office Protocol | POP3 |
110 | TCP | Quality Assurance Post Office Protocol | POP3-QA |
1812 | UDP | Remote Authentication Dial-In User Service Protocol | RADIUS |
4343 | TCP | Recursive WhoIs Information Server | RWHOIS |
N/A | NT Specific | Windows NT Service Monitor | SERVICE |
25 | TCP | Simple Mail Transfer Protocol | SMTP |
161 | TCP | Simple Network Management Protocol | SNMP |
161 | UDP | Quality Assurance Simple Network Management Protocol | SNMP-QA |
162 | UDP | Simple Network Management Protocol Traps | SNMP TRAP-QA |
444 | TCP | Simple Network Pager Protocol | SNPP |
N/A | NT Specific | Structured Query Language: ActiveX Data Objects | SQL: ADO |
N/A | NT Specific | Structured Query Language: ActiveX Data Objects | SQL: ADO-QA |
N/A | NT Specific | Structured Query Language Server | SQL SERVER |
23 | TCP | Remote Terminal Protocol | TELNET |
161 | UDP | Temperature Levels | TEMPERATURE |
43 | TCP | WhoIs Information Server | WHOIS |
ipMonitor traps
Any agent you configure to send traps to ipMonitor must use the same IP address and port combination.
If the Windows SNMP Trap Service is enabled on the ipMonitor host computer, it may conflict with the ipMonitor SNMP Trap Listener. Both are bound by default to port 162.
The POP3 User Experience monitor delivers an email to the SMTP server on port 25 for the recipient address you specify. The monitor then logs in to the POP3 Mail Server on port 110 and retrieves the LIST of queued mail.