Hardware Requirement

Hi,

We are planning to monitor our infra through solarwinds product. Please suggest the hardware requirement keeping in view below specifications along with details as to which two tools can be clubbed together to save upon hardware without suffering performance.

1). 50 IP SLA and 3000 IP phones VNQM

2). IPAM 16000 IPs

3). 500 nodes: NCM, 1243 NPM, 1000 Netflow exporter

4). Device Tracker upto 10000 ports

5). Data retention period is 180 days for all above tools.

Thanks

Sumit

Find more posts tagged with

hardware_requirements

Accepted answers

All comments

mrs.alterego

If you visit our Library & Support page, you will see links to each product's page that will provide you information such as system requirements, how-to's, upgrade advisor, etc. You should be able to find what you're looking for on these pages.

I would start with this link that will take you to the Orion requirements. Hope this helps!

FormerMember

Hi Alterego,

Thanks for quick response. However, This information suggests minimum h/w requirement that too when application is individually deployed. However, I need to know, keeping in view above scope, what all applications should be kept on same system sharing same database and what all separately.

For Example: NPM and NCM can be hosted together keeping in view the number of devices. However, Not sure whether device tracker and IPAM can also be clubbed together. In addition, NTA should be built altogether separate keeping in view the volume or should be set along with any other application. This at the same time should maintain the high availability also and retention period of data 180 days.

Please help me on this.

Thanks

Sumit

mrs.alterego

We usually recommend keeping all the products together on one database, exept the NTA product. This one you will want separate, as you've already read; however, NPM, NCM, IPAM and UDT should be together. As for the reports, when you set up your reports in the product, you can select your timeframe, so 180 days is possible, but I'm not sure exactly what information you need as the 180 day report would be a summary.

If you're looking for a high availability solution, have you discussed an active/active approach with your sales rep?

FormerMember

Hi Alterego,

Oh..I missed clarifying upon180 days, I have mentioned this to suggest upon the database size keeping in view above mentioned count.

However, My concern here is , if keeping all component npm, ncm, ipam and UDT on same system then report may suffer performance. Should we configure reports separately? In addition, when we set up extra poller to accomodate incremented element, then all these components(IPAM and UDT) can also be polled separately through separate poller.

No, We couldn't discuss on this HA part. However, Tried Exploring if installed in active-active then whether we will have setup load balancer with fail-engine in between on separate system pointing towards two system. But in this case fail over-engine system will remain without HA. However, In case of Active-Passive, We suffer functionality of NTA in Fail-over. Please suggest.

Thanks

Sumit

GoldTipu

The following is a SAMPLE recommendation so you can add or subtract these according to your own needs.

Hardware Recommendations for Orion Servers
> NPM SLX /NCM DLX /IPSLA 25 Server
CPU                       Quad Core Processor 3GHz or better
HD Space             20 GB
Memory              8GB

> NPM SLX /NCM DLX Server
CPU                       Quad Core Processor 3GHz or better
HD Space             20 GB
Memory              8GB

> NPM SLX Server
CPU                       Quad Core Processor 3GHz or better
HD Space             20 GB
Memory              8GB

> Each Additional Polling Engine Server
CPU                       Quad Core Processor 3GHz or better
HD Space             20 GB
Memory              8GB

Hardware Recommendations for SQL Servers
>SQL DB for NPM SLX /NCM DLX /IPSLA 25 Server/10 x APE
CPU                       Quad Core Processor 3GHz or better
HD Space             20 GB
Memory              8-12GB
Mirrored drives for OS and 6 disks Raid 1+0 for database data files

>SQL DB for NPM SLX /NCM DLX Server/10 x APE
CPU                       Quad Core Processor 3GHz or better
HD Space             20 GB
Memory              8-12GB

>SQL DB for NPM SLX Server/10 x APE
CPU                       Quad Core Processor 3GHz or better
HD Space             20 GB
Memory              8-12GB

**SQL Server Hardware Recommendation**

3 GHz, dual core processor or better. This will work for all size licenses. Do not use
less than a 2 GHz processor for any Orion SQL server.

Best Practice use RAID 10
2 x Raid 1 disk (Mirroring) For operating system
2 x Raid 1 disk (Mirroring) Place pagefile here and also can be used for applications and ad hoc Stuff
4 x RAID 1 +0 Stripping and mirroring for database files (2 partitions 1 for Data File and 1 for Log File)

WINDOWS 2012, SQL 2012, SQL 2014 AND SOLARWINDS PRODUCTS

https://thwack.solarwinds.com/community/solarwinds-community/product-blog/blog/2013/12/11/windows-2012-and-sql-2012-and-solarwinds-products

For more details please find Orion Admin Guide .

http://www.solarwinds.com/documentation/orion/docs/orionnpmadministratorguide.pdf

Server 2: Primary Database Server

Software Installed:

- Microsoft SQL Server 2012, or 2008 R2 Standard Edition.

Recommended Deployment specs (Physical server recommended)

Dual Quad Core Processor 3 GHz or better
64 GB RAM
Hardware RAID Controller with a battery backed-up write back cache
Disk Subsystem 1 Array 1: 2 x 146GB 15K disks RAID 1 (mirroring) Operating system
Disc Subsystem 2 Array 2: 2 x 146GB 15K disks RAID 1 (Pagefile + Extra Storage)
Disk Subsystem 3 Array 3: with 6x 15k 146GB or 300GB Disks configured in a RAID 1+0 arrays to allow for maximum write performance. This is for your SQL MDF AND FILEGROUPS
Disk Subsystem 4 Array 4: with 4x 15k 146GB or 300GB Disks configured in a RAID 1+0 arrays to allow for maximum write performance. This is for your SQL LDF Transaction LOG File
1Gbit LAN port.
Windows 2008 R2 Server (64-bit)