OpManager Installation Guide

System Requirements

# of devices/interfaces	Processor	RAM	Free Hard Disk	Supported Operating System
Up to 50 devices or 300 Interfaces	1.7 GHz	1 GB	40 GB	Windows: 2003 Server, Vista, 2000 professional +SP4, XP Professional Linux: RedHat 7.x and above, Debian 3.0, Suse, Fedora & Mandrake
Up to 300 devices or 2000 Interfaces	3.4 GHz	2 GB	40 GB
Up to 1000 devices or 5000 interfaces	2 * 3.4 GHz	4 GB	80 GB
More than 1000 device or 5000 interfaces	4 * 3.4 GHz	8 GB	80 GB

Supported Browsers: Firefox 2.0 or above and IE 6.0 or above.

Installing on Windows

Steps to install:

Download OpManager for Windows.
Execute the downloaded OpManager.exe to install and follow the instructions in the installation wizard.
Click Next to begin the installation process. Go through the license agreement and click Yes to proceed to the next step.
In the subsequent steps of the wizard, select the OpManager Edition (30day trial or Free), language and the directory to install OpManager. Proceed to the next step.
If you want to install OpManager as Windows service, select Install OpManager as service option and proceed to the next step.
Select the Program folder to add the OpManager shortcuts and click Next.
Specify the port number to run OpManager Web Server and click Next.
Register for technical support by supplying your contact information such as name, email id etc.
Verify the installation details and click Next.
Select the Server Mode i.e., Primary or Standby server and click Next.
1. If selected as Standby, then enter the Primary webserver host, port and login details and complete the installation.
Select the database. OpManager supports both, MySql and MSSQL as database and click Next.
Click Finish to complete the installation process.

Note:

For Vista installations after successfully completing the installation, if there is any issue in discovering the devices, then allow the ICMP ping requests via the Firewall. This is because by default, Vista installed devices has the in-built firewall configured such that the system does not respond to IMCP requests.
Make sure that your date settings are set to current date and time before installation. If your system date is set to a future or a past date, you will not be able to start the OpManager server after installation.
A shortcut to start OpManager Server will be created on the desktop and in the Start > Programs > ManageEngine OpManager menu.
After successful installation, if you have chosen to install OpManager as Windows service, OpManager service will be started automatically and the Web client will be launched.

Enabling ICMP Ping requests in Windows Vista

From the Control Panel choose System and Maintenance.
Click on Administrative Tools.
Select Windows Firewall with Advanced Security.
Click on Inbound Rules then right click on it and choose New Rule
Click on the Custom radio button and click Next
Click on All programs and click Next
Set the Protocol Type to ICMPv4 and click the Customize… button
Select Specific ICMP types, enable Echo Request and click on the OK button
Click Next.
Verify if Any IP addresses is selected two times and click on the Next button.
Verify if the Allow the connection radio button is selected and click Next
Verify that all three rules (Domain, Private and Public) are enabled and click Next
Specify a Name, perhaps a Description and click Finish
Verify if this new rule now is Enabled and close all open windows

ICMP requests are now allowed to flow via the firewall.

Installing OpManager on Linux

Before installing OpManager in a Linux server, please verify whether the following packages are installed in it:

Following X library packages are required to be installed in Linux machines (RedHat, Suse, Debian, Fedora, Mandrake) to load the Web client pages:

XFree86
XFree86-libs
XFree86-base-fonts
XFree86-xfs
fontconfig
freetype-devel
compat-libstdc++
XFree86-compat-libs
compat-libs
If OpManager is installed in Debian machines, make sure that the iputils-ping package is installed.

This is required because OpManager uses the options of the Ping command provided by the iputils-ping package. Debian OS has two different packages, netkit-ping (installed by default) and iputils-ping. If iputils-ping package is not installed, then OpManager will not be able to ping any of the managed devices and also itself and hence reports the status of all devices to be down.

Now, to install OpManager on Linux machines, follow the steps given below:

Download OpManager for Linux .
Login as root user.
Assign the executable permission to the downloaded file using the following command:
chmod a+x OpManager.bin
Execute ./OpManager.bin. The installation wizard pops up.
Click Next to begin the installation process. Go through the license agreement and proceed to the next step.
In the subsequent steps of the wizard, select the OpManager Edition (Professional or Free), language, the directory to install OpManager, and the port number to run OpManager Web Server. Proceed to the next step.
Verify the installation details and click Next.
Click Finish to complete the installation process.

It is recommended to install OpManager in the opt folder. By default, OpManager is installed in the /opt/AdventNet/ME/OpManager directory.

If you choose a different directory (outside opt), perform the following steps before starting the server:

Execute the command chmod -R 755 <OpManager Home>. You should specify the absolute path for <OpManager Home> in this command.

Then execute the command chmod 755 <directory_name> for each of the directory in the absolute path including root directory.

Select the port number to run OpManager Web Server. Proceed to the next step.

Verify the installation details and click Next. This installs the product in your system.

Click Finish to complete the installation process.

Uninstalling OpManager

To uninstall from a Windows machine, try Start > Programs > ManageEngine OpManager > Uninstall OpManager.
To uninstall from a Linux machine, execute the command ./uninstaller.bin from the /bin/_uninst directory under OpManager installation.

Upgrading OpManager

Different types of OpManager upgrades are periodically released. These include Service Packs, Upgrade Packs, Hot Fixes, and Migration Packs.

Following is the URL where the latest upgrades are hosted for download:

http://www.manageengine.com/products/opmanager/service-packs.html

Shut down OpManager. If OpManager is running as a Windows service, stop the service from Control Panel > Services window. Take a backup of the data and configurations in OpManager.
Take a backup of the data and configurations in OpManager.
Make sure all the processes that are running in the system are killed. Open "Task Manager" and ensure that there are no java, mysql, apache processes are running. Also terminate if any anti-virus software is running.
Open the Update Manager tool
For Windows installations: Click Start > Programs > ManageEngine OpManager > Update Manager.
For Linux installations: Execute the script /bin/UpdateManager.sh
[If the Update Manger UI does not open, then click here to upgrade via console mode]
Click Install and then click Browse to select the upgrade pack file (file with.ppm extension).
Click Finish. This installs the service pack for OpManager.
Start OpManager Server.

Reverting Upgrades

It is recommended not to revert any patches using the same open instance of UpdateManager. Exit UpdateManager if open and invoke again to revert the applied patches. Here are the steps to revert:

Shut down OpManager. If OpManager is running as a Windows service, stop the service from Control Panel > Services window.
pen the Update Manager tool
For Windows installations: Click Start > Programs > ManageEngine OpManager > Update Manager.
For Linux installations: Execute the script /bin/UpdateManager.sh
[If the Update Manger UI does not open, then click here to upgrade via console mode]
Select the ppm file to be uninstalled from the Installed Service Pack list and click Uninstall. This will uninstall the service pack for OpManager.
Start OpManager Server.

Use Cases

The following use cases help you to confirm the flawless working of OpManager post upgrade:

Check the build number [From OpManager webclient, click the About link available at the top right to view the build number]. It should show the number to which you have upgraded
Check whether all the tabs are available for Admin user
Just do a random check to ensure whether the devices are correctly classified under respective categories. For example servers are grouped under Servers, routers under routers etc.
Do a test monitor for a device to ensure whether OpManager collects and displays data [from the device snapshot page, click on edit icon of a monitor and click Test Monitor button]
Just generate any availability/health report of a device
Verify whether the dashboard displays alerts, health status of devices
Verify the mail server and sms server settings
Add a device into OpManager and ensure whether it is getting added into OpManager
Randomly verify the threshold settings of some monitors
Perform the routine tasks done by an admin/user after 1 hour
Restart the windows server on which OpManager is running and check whether OpManager starts up as a service correctly
If DB replication is enabled, then check the status of the replicated DB

Refer to the Quick Start Guide to help you get started with configuring OpManager to monitor your network. Feel free to drop a line to us at our Support Portal incase of any queries or clarifications.