Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > IP Address Manager (IPAM) > IPAM Installation Guide > Stand-alone IPAM installation > IPAM system requirements

IPAM system requirements

Updated: June 1, 2017

IPAM can be installed as a stand-alone product or as a module to Network Performance Monitor (NPM), Server & Application Monitor (SAM), or User Device Tracker (UDT). SolarWinds recommends installing your Orion product on its own server, with the IPAM database hosted separately on its own SQL Server. Installations of multiple IPAM servers using the same database are not supported.

If installing IPAM in an existing Orion Platform environment, see Multi-module system guidelines.

  • Beginning with Orion Platform 2016.1, you can only install on Windows Server 2008 R2 SP1, 2012, and 2012 R2.
  • SolarWinds does not support installing SolarWinds Orion on domain controllers.
  • SolarWinds neither recommends nor supports the installation of any Orion product on the same server or using the same database server as a Research in Motion (RIM) Blackberry server.

Software requirements

The following table lists minimum software requirements and recommendations for your server.

Software

Requirements

Operating System

  • Windows Server 2012 and 2012 R2

Windows Server 2008 R2 SP1 is now deprecated for Orion products.

IIS and Windows 2012 must be installed. SolarWinds recommends that IPAM administrators have local administrator privileges to ensure full functionality of local Orion tools. Accounts limited to use of the IPAM Web Console do not require administrator privileges.

Web Server

Microsoft Internet Information Services (IIS), version 7.5 or later, in 32‑bit mode

DNS specifications require that host names be composed of alphanumeric characters (A-Z, 0-9), the minus sign (-), and periods (.). Underscore characters (_) are not allowed. For more information, see RFC 952.

.NET Framework

.NET 4.5

Compatible with 4.6.1

SNMP Trap Services

Windows operating system management and monitoring tools component.

Web Console Browser

  • Microsoft Internet Explorer version 11 or later with Active scripting
  • Microsoft Edge
  • Firefox 45.0 or later (Toolset Integration is not supported on Firefox)
  • Chrome 49.0 or later
  • Safari for iPhone

IPAM versions 4.3.0, 4.3.1, and 4.3.2 only support English language regional browsers settings.

Hardware requirements

The following table lists minimum hardware requirements and recommendations for your Orion server.

Hardware

IP1000 or IP4000

IP16000

IPX

CPU Speed

2.0 GHz

2.4 GHz

3.0 GHz

Dual processor, dual core is recommended.

Hard Drive Space

2 GB

5 GB

20 GB

Memory

4 GB

8 GB

8 GB

Because Orion uses SNMP to monitor your network, if you are unable to dedicate a network interface card to your Orion server, you may experience gaps in monitoring data because of the low priority generally assigned to SNMP traffic.

SQL database requirements

The Orion Installation wizard installs the following required components if they are not found on your Orion database server:

  • SQL Server System Common Language Runtime (CLR) Types. Orion products use secure SQL CLR stored procedures for selected, non-business data operations to improve overall performance.
  • Microsoft SQL Server Native Client
  • Microsoft SQL Server Management Objects

Because of I/O requirements, your SQL Server should be hosted on a separate physical server configured as RAID 1+0. RAID 5 is not recommended for the SQL Server hard drive.

The following table lists software and hardware requirements for your Orion database server (SQL Server).

requirements

IP1000 or IP4000

IP16000

IPX

SQL Server

SolarWinds supports Express, Standard, or Enterprise versions of the following:

SQL Server 2008, 2008 SP1, 2008 SP2, 2008 SP3, or 2008 SP4

SQL Server 2008 R2, 2008 R2 SP1, 2008 R2 SP2, or 2008 R2 SP3

SQL Server 2012, 2012 SP1, 2012 SP2, or 2012 SP3 (also with AlwaysOn Availability Groups)

SQL Server 2014 (also with AlwaysOn Availability Groups) or 2014 SP1

SQL Server 2016

  • Because of latency, SolarWinds does not recommend installing your SQL Server and your IPAM server or additional polling engine in different locations across a WAN. See Install SolarWinds software and SolarWinds database (SQL Server) across a WAN for more information.
  • Either mixed-mode or SQL authentication must be supported.
  • If you are managing your Orion database, SolarWinds recommends that you install the SQL Server Management Studio component.
  • If your Orion IPAM product installs SQL Server System CLR Types, a manual restart of the SQL Server service for your Orion database is required.
  • Use the following database select statement to check your SQL Server version, service pack or release level, and edition:
    select SERVERPROPERTY ('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

SQL Server Collation

  • English with collation setting SQL_Latin1_General_CP1_CI_AS
  • English with collation setting SQL_Latin1_General_CP1_CS_AS
  • German with collation setting German_PhoneBook_CI_AS
  • Japanese with collation setting Japanese_CI_AS
  • Simplified Chinese with collation setting Chinese_PRC_CI_AS

SolarWinds supports CI database on an CS SQL Server.

SolarWinds does not support case-sensitive databases.

CPU Speed

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

5 GB

20 GB

Memory

4 GB

8 GB recommended

8 GB

16 GB recommended

16 GB

32 GB recommended

Port requirements

RPC ports are dynamically assigned above 1024. To configure RPC dynamic port allocations, see How to configure RPC dynamic port allocation to work with firewalls.

Port Protocol Direction Description Encryption
22 SSH Bidirectional Required to access devices through the CLI Device-based
53 TCP

Bidirectional

Used for zone transfers, DNS record polling

 
161 UDP Bidirectional Statistics collection  
17777 TCP Bidirectional

Orion module traffic. Open the port to enable communication from your poller to the Orion Web Console, and from the Orion 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 Orion Web Console and the poller.

RSA handshake, AES 256 communication using WCF

17778 HTTPS and TCP Inbound to the Orion server

Required to access the SolarWinds Information Service API and agent communication

SolarWinds Information Service API

SSL

Upgrade paths and instructions

For detailed instructions upgrading IPAM, see the IPAM Upgrade Guide.

SolarWinds Orion modules and stand-alone products are compatible with the specific versions of SolarWinds Network Performance Monitor (NPM), Network Configuration Monitor (NCM), and Server & Application Monitor (SAM). You must use the upgrade path if you are installing IPAM into an existing Orion Platform.

See Compatibility of SolarWinds Orion products for installation and upgrade and End of Life Support for the latest updates.

Last modified
12:07, 25 May 2017

Tags

Classifications

Public