Sizing for Standalone Installations

The following are suggested sizing guidelines for your Open Manage Network Manager system.

Operating System / Disks / RAM / Hardware

Network Size

Devices2

Application Constraints3

Installation Changes to Heap (RAM) Settings

64-bit OS with 6GB RAM

 

All below are 64-bit OS’s:

<5 Users

<20

<2Mbs Internet egress and a 1:1000 sample rate

Use defaults: (1 or 2GB appli­cation server heap (32 v. 64-bit) 512M database4, 768M Synergy

8GB RAM, single disk, con­sumer level PC

Single-site, less than 10 concurrent users

<100

<2Mbs Internet egress and a 1:1000 sample rate

3GB application server heap, 2GB database, 1G Synergy

12GB RAM, single disk, busi­ness level PC

Single-site, less than 25 concurrent users.

< 500

< 10Gbs Internet egress and a sample rate of 1:1000

4GB application server heap, 3GB database, 3G Synergy

16GB RAM, multi-disk, server level PC

Medium-large network, up to 50 concurrent users

< 1,000

< 50Gbs Internet egress and a sample rate of 1:1000

5G application server heap, 4G database, 4.5G Synergy

32GB RAM, multi-disk, server level PC, recommend fast disk array or SSD drive array for the many database actions

Large network, up to 100 concurrent users

< 2,000

< 200Gbs Internet egress and a sample rate of 1:1000

10G application server heap, 8G database, 9G Synergy

1 Assumptions: Servers have at least four cores (3.0GHz or better) and are no more than four years old. As memory and usage increases, the number of CPU cores increase. Two cores can work for the most basic installations, but are not recommended.

2 Each device is equivalent to a L2 or L3 switch with a total of 48 interfaces per device being monitored. For each of devices not being monitored for 48 interfaces, one can add another 50 devices to the overall inventory for ICMP-only monitoring.

3 Application Constraints are most relevent to Traffic Flow Analysis, Peformance Management, and Event Manage­ment.

Traffic Flow Analysis ratings map to constant throughput divided by sample rate, as in bandwidth / sample rate. 20G / 2000 is easier to manage than 20G / 1000. 20G / 1 is a thousand times more demanding than 20G / 1000. Best practice is to avoid such high sample rates. The bandwidth the hardware your Open Manage Network Manager instal­lation can support is dramati­cally lower in such cases. Best practice is to sample a maximum of one traffic flow for every 1000 (1:1000). Higher sam­pling rates degrade data­base performance and increase network traffic without add­ing any significant statistical information.

Performance Management can support 600 inserts per sec­ond using a single disk (SSD) Drive. 1 insert = 1 monitored attribute. Expect better performance as you add more drives (and worse performance with slower drives).

Event Management can support a sustained 1200 traps /sec using a single (SSD) drive. Expect better performance as you add more drives (and worse performance with slower drives).

4 Database memory settings increase as the number of data­base hits increases. At the 32GB level best practice is to use an SSD drive or fast disk array because of the large number of database actions possible.

You can start and stop the client portion of the software without impacting the application server. Device monitoring stops when you stop the application server or turn off its host machine. The client can also be on a different machine than the application server.

See Starting Web Client for more information about using web access to this software.