IPAM 2025.1 system requirements
IPAM RC documentation - The following content is a draft for a release candidate. All content subject to change. Some links might not function yet.
RC release date: December 12, 2024
SolarWinds strongly recommends that you install the SolarWinds Platform on a server that is neither public, nor internet-facing. To learn about best practices for configuring your SolarWinds Platform installation securely, see Secure Configuration for the SolarWinds Platform.
These system requirements define the minimum requirements for IPAM 2025.1 and its integration with the IPAM as a single installed product.
For additional information on requirements and configurations, see the Multi-module system guidelines. You should also review your product administration guides and release notes for the exact product requirements beyond these minimums.
We also recommend reviewing the IPAM 2024.4 Release Notes and the SolarWinds Platform 2024.4 Release Notes.
- Software requirements
- Account privileges
- Port requirements
- Hardware requirements
- Database requirements
- Amazon Web Service requirements
- Microsoft Azure requirements
Software requirements
The following table lists software requirements and recommendations for a SolarWinds installation on both physical and virtual computers.
Account privileges
SolarWinds recommends that SolarWinds administrators have local administrator privileges on the SolarWinds server to ensure full functionality of local SolarWinds tools.
SolarWinds user accounts limited to the SolarWinds Platform Web Console do not require local administrator privileges.
Server port requirements
SolarWinds does not recommend the use of HTTP (Port 80). Please use HTTPS (Port 443) to ensure that any web-related connections are secure.
PORT | PROTOCOL | DIRECTION | DESCRIPTION | ENCRYPTION |
---|---|---|---|---|
22 | TCP | bidirectional | SSH (secure shell) | |
23 | TCP | bidirectional | Telnet (non-secure) | |
53 | TCP |
|
Used for zone transfers, DNS record polling |
|
135 | TCP | bidirectional | WMI (Windows) | |
161 | UDP | bidirectional | Statistics collection | |
443 | TCP | bidirectional | Infoblox (web API) | |
445 | TCP | bidirectional | WMI (Windows) | |
dynamic, random, greater than 1024 |
TCP | bidirectional | (DCE/Microsoft RPC Locator service) Microsoft EPMAP, only if you monitor nodes via WMI. This port is used by the SolarWinds Job Engine v2 service to communicate with Windows nodes. See WMI portocalypse on THWACK. | |
17777 | TCP | bidirectional |
SolarWinds module traffic. Open the port to enable communication from your poller to the SolarWinds Web Console, and from the SolarWinds Web Console to your poller. High Availability Service. Used for communication between the main server and pool members. Job Engine V2, Collector Service, Business Layer, and Information Service v2,23. Used for communication between the services. The port used for communication between the SolarWinds Web Console and the poller. |
RSA handshake, AES 256 communication using WCF |
17778 | TCP |
Required to access the SolarWinds Information Service API and agent communication SolarWinds Information Service API |
SSL |
Port requirements for vRealize Orchestrator can be found here (© 2017 VMware, available at https://kb.vmware.com/, obtained 02/12/2020).
Hardware requirements
The following table lists minimum hardware requirements and recommendations for a single standalone instance of IPAM. If you have other SolarWinds SolarWinds Platform products this will change the requirements.
IP1000/4000 | IP16000 | IPX | |
---|---|---|---|
CPU Speed Dual processor, dual core is recommended. |
2.0 Ghz | 2.4 GHz | 3.0 GHz |
Hard drive space | 2 GB | 5 GB | 20 GB |
Memory | 4 GB | 8 GB | 8 GB |
Because SolarWinds Platform uses SNMP to monitor your network, if you are unable to dedicate a network interface card to your SolarWinds server, you may experience gaps in monitoring data because of the low priority generally assigned to SNMP traffic.
Database server (SQL Server) requirements
The following table lists software and hardware requirements for your SolarWinds Platform database server using SolarWindsNPM license levels.
The SolarWinds server and the SolarWinds Platform database must use separate servers.
If you install on a virtual machine, you must maintain your SQL Server database on a separate, physical drive.
As of SolarWinds Platform 2019.2, you can use Azure SQL as your database server.
As of SolarWinds Platform 2018.2, you can use Amazon RDS as your database server.
IP1000 |
IP16000 |
IPX |
|
---|---|---|---|
SQL Server |
Express, Standard, or Enterprise versions of the following:
For evaluation only:
|
||
End-of-support notice: SolarWinds Platform products are no longer compatible with SQL Server 2012, 2012 SP1, 2012 SP2, 2012 SP3, and 2012 SP4. Recommendations
|
|||
SQL Server collation |
We support CI database on an CS SQL Server. We do not support case-sensitive databases. |
||
CPU |
Dual quad core processor, 3.0 GHz or better |
Dual quad core processor, 3.0 GHz or better |
Dual quad core processor. 3.0 GHz or better |
Hard drive space |
2 GB minimum |
5 GB minimum |
20 GB minimum |
|
|||
Memory |
4 GB minimum 8 GB recommended |
8 GB minimum 16 GB recommended |
16 GB minimum 32 GB recommended |
Authentication |
Either mixed-mode or Windows authentication. If you require SQL authentication, you must enable mixed mode on your SQL server. |
||
Other software |
SolarWinds recommends you install the SQL Server Management Studio component on your SolarWinds server. The Installation wizard installs the following required x86 components if they are not found on your SolarWinds database server:
You cannot share the SolarWinds database with Microsoft SharePoint, Microsoft Exchange, and with Research in Motion (RIM) BlackBerry servers. |
Amazon Web Service (AWS deployments)
For requirements for deploying SolarWinds products to the Amazon cloud, see the IPAM system requirements.
Microsoft Azure
For requirements for deploying SolarWinds products to the Azure cloud, see the IPAM system requirements.
Linux servers
SolarWindsIPAM 2025.1 supports DHCP and DNS servers running:
- Linux Ubuntu 14.x up to 18.04 LTS
- Linux Debian 8, 9, and 10
- RHEL and Centos 6, 7, and 8