OpManager -

The network, server and virtualization monitoring software

Let’s Help You!
Quick Links
Resources
Product Datasheet
Know what’s included in OpManager and how it can help you monitor your network.
Live Demo
Explore OpManager on our live demo. Login as Administrator ⁄ Operator.
Screenshot Overview
A quick glance at OpManager functionality with product screenshots.
Quick Video Tour
Sit back and watch videos that tell you more about network and server monitoring capabilities of OpManager.
Case Study
Know how OpManager has helped companies to monitor and manage their network.
Whitepaper
See what experts have to share on monitoring and managing your network using OpManager.
More Resources
Other useful resources that help you monitor and manage your network.
Network monitor » Resources » Documents » System requirements

System Requirements


Essential Edition Enterprise Edition

For installing OpManager, following are the recommended hardware and software requirements*.

  Up to 500 interfaces or 100 servers 500 - 2.5K interfaces or 500 servers 2.5K - 5K interfaces or 750 servers 5K - 10K interfaces  or 1K servers
Processor(s)
2.0 GHz
Dual Core, 3.5 GHz
Quad Core, 3.5 GHz
Quad Core, 3.5 GHz
Memory
4 GB
4 GB
8 GB
16 GB
Free Hard Disk Space
20 GB
40 GB
60 GB
80 GB
NIC
10 Mbps
100 Mbps
1 Gbps
1 Gbps
Video display resolution
1024x768 or higher
OS – Supports both 32 bit and 64 bit Windows Server OSes: v7, 2008, 2008 R2, 2012, 2003 Server, Vista, XP Pro and 2000 Professional SP4

Linux: RedHat 4.x and above, Debian 3.0, Suse, Fedora and Mandrake
Database MS SQL 2000, 2005, 2008 and 2012 Or OpManager bundled PostgreSQL
Browser IE 7.0 or above, Firefox 2.0 or above and Chrome 4.0 or above

* The above recommendations are made using default polling intervals. Results depend on the number of monitored interfaces and the polling interval configured for each monitor.

Performance Tuning Tips:


 Upto 500 interfaces or 100 servers 500 - 2.5K interfaces or 500 servers
 2.5K - 5K interfaces or 750 servers
 5K -10K interfaces or 1k servers
Java Tuning
 Windows
  1. Edit the file opmanager/conf/wrapper.conf
  2. Search for java.maxmemory
  3. Set it to 1024
Linux :
  1. Edit StartOpManagerServer.sh file available under opmanager/bin
  2. Search for Xmx200m
  3. Set it to Xmx1024m
 Windows
  1. Edit the file opmanager/conf/wrapper.conf
  2. Search for java.maxmemory
  3. Set it to 2048
Linux :
  1. Edit StartOpManagerServer.sh file available under opmanager/bin
  2. Search for Xmx200m
  3. Set it to Xmx2048m
 Windows
  1. Edit the file opmanager/conf/wrapper.conf
  2. Search for java.maxmemory
  3. Set it to 4096
Linux :
  1. Edit StartOpManagerServer.sh file available under opmanager/bin
  2. Search for Xmx200m
  3. Set it to Xmx4096m
 Windows
  1. Edit the file opmanager/conf/wrapper.conf
  2. Search for java.maxmemory
  3. Set it to 4096
Linux :
  1. Edit StartOpManagerServer.sh file available under opmanager/bin
  2. Search for Xmx200m
  3. Set it to Xmx4096m
MySQL Tuning
  1. Edit the file opmanager/mysql/my-huge.cnf   (NOT INI.... file extension should be .cnf)
  2. Search for “The MySQL server”
  3. remove the entries and paste the following
bulk_insert_buffer_size=250M
innodb_buffer_pool_size=250M
innodb_flush_log_at_trx_commit = 2
key_buffer_size=1G
max_allowed_packet=100M
max_heap_table_size=112M
myisam_sort_buffer_size=500M
query_cache_size=200M
read_buffer_size=15M
read_rnd_buffer_size=15M
skip-bdb
skip-locking
sort_buffer_size=256M
skip-external-locking
skip-ndbcluster
table_cache=512
thread_cache_size=40
  1. Edit the file opmanager/mysql/my-huge.cnf   (NOT INI.... file extension should be .cnf)
  2. Search for “The MySQL server”
  3. remove the entries and paste the following
bulk_insert_buffer_size=250M
innodb_buffer_pool_size=500M
innodb_flush_log_at_trx_commit = 2
key_buffer_size=2G
max_allowed_packet=100M
max_heap_table_size=112M
myisam_sort_buffer_size=500M
query_cache_size=200M
read_buffer_size=15M
read_rnd_buffer_size=15M
skip-bdb
skip-locking
sort_buffer_size=256M
skip-external-locking
skip-ndbcluster
table_cache=512
thread_cache_size=40
  1. Edit the file opmanager/mysql/my-huge.cnf   (NOT INI.... file extension should be .cnf)
  2. Search for “The MySQL server”
  3. remove the entries and paste the following
bulk_insert_buffer_size=250M
innodb_buffer_pool_size=1000M
innodb_flush_log_at_trx_commit = 2
key_buffer_size=4G
max_allowed_packet=100M
max_heap_table_size=112M
myisam_sort_buffer_size=500M
query_cache_size=200M
read_buffer_size=15M
read_rnd_buffer_size=15M
skip-bdb
skip-locking
sort_buffer_size=256M
skip-external-locking
skip-ndbcluster
table_cache=512
thread_cache_size=40
  1. Edit the file opmanager/mysql/my-huge.cnf   (NOT INI.... file extension should be .cnf)
  2. Search for “The MySQL server”
  3. remove the entries and paste the following
bulk_insert_buffer_size=250M
innodb_buffer_pool_size= innodb_flush_log_at_trx_commit = 2
key_buffer_size=4G
max_allowed_packet=100M
max_heap_table_size=112M
myisam_sort_buffer_size=500M
query_cache_size=200M
read_buffer_size=15M
read_rnd_buffer_size=15M
skip-bdb
skip-locking
sort_buffer_size=256M
skip-external-locking
skip-ndbcluster
table_cache=512
thread_cache_size=40

Besides the configuration tweaks suggested above, you can consider any one of the following alternatives if you are monitoring over 10,000 interfaces for better scalability and performance

Steps to move MySQL databse to a dedicated server
  1. Install a supported MySQL version on the dedicated server.
  2. Edit the file /opmanager/conf/database_params.conf
  3. Configure the host name and the MySQL port number for the url parameter as follows:
    url jdbc:mysql:// <name of the server where mysql is installed> : <mysql port> /OpManagerDB

    Example: url jdbc:mysql://database1-server:3306/OpManagerDB

Steps to move PostgreSQL to a dedicated server

  1. Install PostgreSQL version 9.2.1 on the dedicated server. After successfully installing it,
    1. Go to data directory of PostgreSQL installation.
    2. Open pg_hba.conf - PostgreSQL Client Authentication configuration file, and go to the bottom of it.
    3. By default, under IPv4 local connections, we have the following:
      #host all all 127.0.0.1/32 md5/trust - md5/trust or someother is available as last option
      1. Change the 127.0.0.1/32 to all
    4. By default, under IPv6 local connections, we have the following:
      #host all all ::1/128 md5/trust - md5/trust or someother is available as last option
      1. Change the ::1/128 to all
    5. Save the File.
    6. Open Services window and restart the PostgreSQL server running in the machine to effect the changes.
  2. Edit the file /opmanager/conf/database_params.conf.
  3. Configure the host name and the PostgreSQL port number for the url parameter as given below:
    url jdbc:postgresql:// <name of the server where postgresql is installed> : <postgresql port> /OpManagerDB

    Example: url jdbc:postgresql://database1-server:5432/OpManagerDB
  4. If you wish to enable password, un-comment the password line and set the new password.

How can I find the number of devices and interfaces monitored in OpManager?
  • In OpManager Web Client click the "About" link on top right of the page.
  • Search for the ‘Total Monitored Devices’ & ‘Total Monitored Interfaces’ among the product details listed.
  • Check the following image guide, to locate the number of monitored devices and interfaces.
Opmanager About Screen

Need help?

Have questions regarding system requirements? Please contact OpManager Support.