Home / How Tos / Kbase

Kbase

  1. When to create a device template?
  2. Monitoring Disk I/O
  3. Trouble deleting an alarm
  4. AD Monitors show N/A
  5. MSSQL 2000/2005 not working - Shows N/A
  6. Enabling SNMPv3 on Windows 2003
  7. Enabling SNMPv3 on ESX Server
  8. Error: Unable to find the object
  9. Registering OpManager License
  10. Extending trial license
  11. What is a .ppm file?
  12. Resolving timezone difference problems in OpManager & NFA Plug-in
  13. Prerequisites for monitoring WAN RTT
  14. Prerequisites for MSSQL as backend DB
  15. Prerequisites to view detailed traffic reports from NFA in OpManager

When to create a device template?


    The device templates in OpManager contain predefined rules based on which a device is categorized and relevant monitors are associated soon after discovery. The ability to define custom templates for new device types or modify an existing template to accommodate yet another device type in the same template provides great flexibility to administrators.

That said, as an administrator, you will be able to make the best out of this feature if used to its full potential. For instance, some might end up defining a template for every variant of a device type instead of creating one template that can encompass all the variants.

Ideally, defining device templates before you initiate discovery helps in proper classification. Over 650 device templates are available out of the box. If SNMP is enabled on the monitored devices, and if proper credentials are configured in OpManager, most devices fall into the correct category. Modify an existing template or create a new one based on need.

1. When should I modify/update an existing template?

Assume you have purchased a new Cisco 805 router and you would like to monitor it using OpManager. OpManager already has a device template for Cisco 800 series routers with few sysOIDs in these series updated in the template. All you need to do is edit this template to include the sysOID of Cisco 805 router if it is not present already.


2. When should I create new templates?

Scenario 1

Let us now assume you have purchased a Cisco 11000 Series Content Services Switch. OpManager does not have a template yet (this is as of Build no.8721!). Just go ahead and create a new template.

Scenario 2

Assume you have a whole new set of Environment Sensors that are manageable (that supports SNMP). These devices cannot be classified under any of the default categories like servers, routers, switches etc, and deserve a separate category. The managing parameters too differ for this new device type. An ideal situation where you will define a new category view (Eg: Sensors) and define a fresh device template. You can have different models of sensors from the same vendor in a template or even combine Sensors from multiple vendors in the same template.

The steps you'd follow here would be as follows:





3. How to check for SNMP response to sysOID

Even before you proceed to add or modify a template to accomodate a new device type, make sure the device is SNMP enabled and it responds to query from OpManager. Invoke the MibBrowser utility bundled with OpManager to check for response. Let me show you how to check for SNMP response.

1. From OpManager/bin, double-click to execute MibBrowser.bat.
2. In the MibBrowser GUI, enter the device name, the SNMP port, and the read community string (default is PUBLIC).
3. RFC1213 mib is loaded by default. Expand the mib to org->dod->internet->mgmt->mib2 ->system and select sysObjectID from this table.
4. From the toolbar above, click on the Get SNMP Variable icon (7th icon from the left) to see the response in the text area to your right.


Monitoring 

Monitoring basic CPU, Memory and Disk utilization gives a fair indication of where the problem could be, but you need to monitor more than just the resource utilization to actually determine the reason for application slowness.  Multiple system resource parameters or even a single parameter can impact the performance of an application. Let's look at "Disk I/O" - one of key parameters that causes application performance related problems.

Why monitor Disk I/O:

The hard disk is one of the slowest components on a server. The hard disk drive bandwidth is around 300 times slower than that of the memory and added to that, memory latency is very low - if you do the math, memory performs around 2000 times faster than that of the hard disk drive. Check out http://nathanaeljones.com/153/performance-killer-disk-io/ for a neat explanation.

So monitoring and keeping the Disk I/O at healthy levels can prevent a lot of application performance hiccups.

Does my server have Disk I/O problems?

Depending on your server, there are different ways of finding Disk I/O. Refer to http://www.performancewiki.com/diskio-tuning.html for the Disk I/O commands on various servers.

Another simple way, and what we recommend ;), is to use OpManager. OpManager monitors Disk I/O out-of-the-box for Windows servers (see screenshot below) and with a few customizations also for Unix-based devices.


Trouble deleting an alarm

You may not be able to delete an alarm at times if the alarm message contains some special characters and url escape characters.

The problem can be worked around by manually deleting the alarm from the alert and event tables in the database. 
1. Connect to the database using this command,
C:..OpManagermysqlin>mysql -u root -P 13306 OpManagerDB
 
2.Use this query to delete the alarm,
delete from alert where source like %<device name>%';

To remove a particular alarm use the query below:
MYSQL:
mysql>delete from alert where mmessage like '%alarmmessage%';

Example:
mysql>delete from alert where mmessage like 'Þvice not responding%';

For SQL database, connect to SQL query analyzer and execute the below query.

delete from alert where mmessage like '%alarmmessage%'

Example:
delete from alert where mmessage like 'Êche hit ratio%'
This problem could due to the following reasons:

1)WMI is not configured properly in OpManager (OpManager uses WMI credential to monitor AD servers).
2)Required Monitors are not associated to the device  in OpManager.
3)WMI might not be responding to the OpManager WMI request
4)WMI is not working properly on the device itself.

1)WMI is not configured properly in OpManager (OpManager uses WMI credential to monitor AD servers).

Solution: Configuring WMI for multiple devices at a time :

1.Go to Admin --> Credential Settings
2.Click New
3.Configure the following parameters and click Add to add the credentials:

Credential Type: Windows

Name: Configure a name for the credential and also provide the description.

configure the Domain NameU ID  and the password  (Example:- TestDomainTestUser  Testpassword) > Click on "Add".

Associate the above credential using Quick Configuration Wizard to multiple devices:-

   1. From the Admin tab, select Quick Configuration Wizard.
   2. Select the option Associate a credential to several devices and click Next.
   3. All the available Credentials are listed. Select the Credential (the one you created above ).
   4. Select the devices to which you want to assign the credential from the left column  and move them to the right.
   5. Click Finish. The Credential is associated to the selected devices.

Configuring WMI credential using device snap shot page(Single device):

Go to device snap shot page > Click on "Click here to change" option besides Passwords >select "Use the below credential for the device" option >Type in the username (Ex:domainnameuame)  and Password > Click on Test credential (make sure its gets passed) and then Ok to save it.

In case  OpManager itself is going to be AD server then leave the username and password blank and click OK as we do not require credential for the local host.

2)Required Monitors are not associated to the device  in OpManager.

Solution: Adding monitors for AD Monitors:-

Make sure the Category is selected as Domain controller  to have the AD monitors associated automatically to the device.

In case if the monitors are absent go to spacer Active Directory Monitors  section of the device snapshot page  and add the required AD monitors (Network Monitors ,Database Monitors  NTFRS Process Monitors , System Monitors, Performance Counters Monitors and LSASS Process Monitors ).
 
3)WMI might not be responding to the OpManager WMI request

Solution:Use the wmiadap utility to update the WMI performance classes from the performance libraries. Running wmiadap updates all the performance classes. The /f switch in the below command  forces an update of the WMI classes from the performance libraries.

Step 1:

1. Go to the monitored device.
2. Click Start-->Run,
    For Windows 2000 winmgmt /resyncperf' command.
    For Windows XP and 2003 'wmiadap /f' command.
3. After running this command about 4 times, wait for an hour and check whether  AD monitors shows data.

Step: 2

1. Go to the monitored device.
2. Click Start-->Run-->services.msc
3. Restart WMI service

4)WMI is not working properly on the device itself.

Solution: Still if you do not see the counter values, verify  whether OpManager server is able to pull up AD counters information  by executing the following queries.If you are able to pull the information for the following queries OpManager should be able to show the information in the dashboard.

If some of the below query gets the output and some of them not then the respective counters information associated with the non working classes will not be shown on the dash board.

1. From OpManager command prompt go to <OpManagerconfapplicationscripts>
2. Execute the following commands and make sure we get the output from the device.

cscript wmiget.vbs devicename domainnameuame password "ROOTCIMV2" "SELECT * from Win32_PerfRawData_PerfNet_Server"
cscript wmiget.vbs devicename domainnameuame password "ROOTCIMV2" "SELECT * from Win32_Processor"
cscript wmiget.vbs devicename domainnameuame password "ROOTCIMV2" "SELECT * from Win32_PerfRawData_PerfOS_System"
cscript wmiget.vbs devicename domainnameuame password "ROOTCIMV2" "SELECT * from Win32_PerfRawData_PerfOS_Memory"
cscript wmiget.vbs devicename domainnameuame password "ROOTCIMV2" "SELECT * from Win32_PerfRawData_NTDS_NTDS"
cscript wmiget.vbs devicename domainnameuame password "ROOTCIMV2" "SELECT * from Win32_PerfRawData_PerfProc_Process"
cscript wmiget.vbs devicename domainnameuame password "ROOTCIMV2" "SELECT * from Win32_OperatingSystem"
cscript wmiget.vbs devicename domainnameuame password "ROOTCIMV2" "SELECT * from Win32_LogicalDisk"
cscript wmiget.vbs devicename domainnameuame password "ROOTCIMV2" "SELECT * from Win32_PerfRawData_PerfOS_Processor"

If you are getting "Invalid class" error message for the above queries then either the corresponding wmi classes are absent or corrupted on the AD server.

Please refer the link below to re-register or rebuild the WMI classes.

http://windowsxp.mvps.org/repairwmi.htm

MSSQL 2000/2005 not working - Shows N/A

This problem could due to the following reasons:

1)WMI is not configured properly in OpManager (OpManager uses WMI credential to monitor MSSQL servers).
2)Required Monitors are not associated to the device  in OpManager.
3)WMI might not be responding to the OpManager WMI request
4)WMI is not working properly on the device itself.

1)WMI is not configured properly in OpManager (OpManager uses WMI credential to monitor MSSQL servers).

Solution: Configuring WMI for multiple devices at a time :

1.Go to Admin --> Credential Settings
2.Click New
3.Configure the following parameters and click Add to add the credentials:
  • Credential Type: Windows
  • Name: Configure a name for the credential and also provide the description.
  • Configure the Domain NameU ID  and the password  (Example:- TestDomainTestUser  Testpassword) > Click on "Add".
Associate the above credential using Quick Configuration Wizard to multiple devices:-

   1. From the Admin tab, select Quick Configuration Wizard.
   2. Select the option Associate a credential to several devices and click Next.
   3. All the available Credentials are listed. Select the Credential (the one you created above ).
   4. Select the devices to which you want to assign the credential from the left column  and move them to the right.
   5. Click Finish. The Credential is associated to the selected devices.

Configuring WMI credential using device snap shot page(Single device):

Go to device snap shot page > Click on "Click here to change" option besides Passwords >select "Use the below credential for the device" option >Type in the username (Ex:domainnameuame)  and Password > Click on Test credential (make sure its gets passed) and then Ok to save it.

In case  OpManager itself is going to be MSSQL server then leave the username and password blank and click OK as we do not require credential for the local host.

2)Required Monitors are not associated to the device  in OpManager.

Solution: Adding monitors for MSSQL Monitors:-

Here are the steps to associate the MSSQL monitors to a device:

   1.Go to the snapshot page of a device.
   2.Scroll down and select the Monitors tab.
   3.Click on Performance Monitors. The monitors are listed on the right.
   4.Click the Add Monitor button on the right. A list of monitors is displayed.
   5.Click the MSSQL Monitors button on top of this list. The monitors of all the MSSQL parameters are displayed.
   6.From this list, select the required MSSQL Monitors and click on  Add > List of MSSQL databases will be listed for which you want to
      associate Monitors
   7.Check mark all the required databases and click on OK , Now you will get a dash board for MSSQL and data will be populated after
      some time.

3) WMI might not be responding to the OpManager WMI request

Solution:Use the wmiadap utility to update the WMI performance classes from the performance libraries. Running wmiadap updates all the performance classes. The /f switch in the below command  forces an update of the WMI classes from the performance libraries.

Step 1:

1. Go to the monitored device.
2. Click Start-->Run,
    For Windows 2000 winmgmt /resyncperf' command.
    For Windows XP and 2003 'wmiadap /f' command.
3. After running this command about 4 times, wait for an hour and check whether MSSQL monitors shows data.

Step: 2

1. Go to the monitored device.
2. Click Start-->Run-->services.msc
3. Restart WMI service

4)WMI in the device is not working properly.

Solution: Still if you do not see the counter values, verify  whether OpManager server is able to pull up MSSQL counters information  by executing the following queries.If you are able to pull the information for the following queries OpManager should be able to show the information in the dashboard.

If some of the below query gets the output and some of them not then the respective counters information associated with the non working classes will not be shown on the dash board.

1. From OpManager command prompt go to <OpManagerconfapplicationscripts>
2. Execute the following commands and make sure we get the output from the device.

cscript wmiget.vbs <Devicename or IP> <DomainnameUame> <Password> ROOTCIMV2 "select *  from Win32_PerfRawData_MSSQLSERVER_SQLServerBufferManager " 

Example:OpManagerconfapplicationscripts>cscript wmiget.vbs MSSQLSERVER1 TestUame Password  ROOTCIMV2 "select *  from Win32_PerfRawData_MSSQLSERVER_SQLServerBufferManager "

cscript wmiget.vbs <Devicename or IP> <DomainnameUame> <Password> ROOTCIMV2 "select *  from Win32_PerfRawData_MSSQLSERVER_SQLServerCacheManager "

cscript wmiget.vbs <Devicename or IP> <DomainnameUame> <Password> ROOTCIMV2 "select *  from Win32_PerfRawData_MSSQLSERVER_SQLServerPlanCache "

cscript wmiget.vbs <Devicename or IP> <DomainnameUame> <Password> ROOTCIMV2 "select *  from Win32_PerfRawData_MSSQLSERVER_SQLServerDatabases"

cscript wmiget.vbs <Devicename or IP> <DomainnameUame> <Password> ROOTCIMV2 "select *  from Win32_PerfRawData_MSSQLSERVER_SQLServerGeneralStatistics "

cscript wmiget.vbs <Devicename or IP> <DomainnameUame> <Password> ROOTCIMV2 "select *  from Win32_PerfRawData_MSSQLSERVER_SQLServerReplicationAgents "

cscript wmiget.vbs <Devicename or IP> <DomainnameUame> <Password> ROOTCIMV2 "select *  from Win32_PerfRawData_MSSQLSERVER_SQLServerLocks"

cscript wmiget.vbs <Devicename or IP> <DomainnameUame> <Password> ROOTCIMV2 "select *  from Win32_PerfRawData_MSSQLSERVER_SQLServerMemoryManager"

cscript wmiget.vbs <Devicename or IP> <DomainnameUame> <Password> ROOTCIMV2 "Select *  from Win32_PerfRawData_MSSQLSERVER_SQLServerGeneralStatistics"

If you are getting "Invalid class" error message for the above queries then either the corresponding wmi classes are absent or corrupted on the MSSQL server.

Please refer the link below to reregister or rebuild the WMI classes.

http://windowsxp.mvps.org/repairwmi.htm

Enabling SNMPv3 on Windows 2003

In Windows 2003 Server, SNMP service is available which supports onlySNMP version v1 and v2c. If you want to add SNMPv3 support, you need toinstall snmpv3 supported agent. Download the Net-Snmp Agent tosupport the same.

Please follow the below steps to install snmpv3 agent.

1. First Download the Active Perl from the below link

http://downloads.activestate.com/ActivePerl/Windows/5.10/ActivePerl-5.10.0.1002-MSWin32-x86-283697.msi

2. Install the Active perl first. Also you need to install the OpenSSL.

3. Download the exe of NetSnmp Agent from the below link
http://sourceforge.net/project/showfiles.php?group_id=12694&package_id=162885

4. Install the Net-Snmp Agent.

5.After installing the netsnmp agent. Herewith I have attached the conffile, Please rename the snmp.conf.txt as snmp.conf and snmpd.conf.txtas snmpd.conf. Copy the the snmpd.conf and snmp.conf under thedirectory c:utcsnmp

6. Then register the agent by executing registeragent.bat file and run the below command in command line to start the agent.
net start "net-snmp agent"

7. Now the agent is started at port 8001.

Releated Links:

http://www.netadmintools.com/art487.html

 

Enabling SNMP on ESX Server

 

 

To enable SNMP on ESX Server version 3.5:

1. Login as root
2. Edit the snmpd.conf file and add "rocommunity xxxx" where xxxx is your read-only community string). The file is usually located in /etc/snmpd.
3. While you're editing the snmpd.conf file, also add "dlmod SNMPESX /usr/lib/vmware/snmp/libSNMPESX.so"
4. Restart the SNMP daemon - /etc/init.d/snmpd restart

In some cases, you may also need to edit the firewall settings on the ESX server to allow the SNMP traffic through. To do this:

Login as root and issue the following commands:
2. esxcfg-firewall -e snmpd
3. chkconfig snmpd on
4. service snmpd start

For more information, visit the VM Ware page on how to configure SNMP on the ESX Server.

 

Error: Unable to find the object

 

 

Registering OpManager License

 

1. In the Client window, click Register link on the menu bar.

2. Browse and select the Registered License file (AdventNetLicense.xml) provided to you and click Register.

3. Verify the licensing details displayed in the page and click Close.


If you are applying the Registered License after expiry of the evaluation license then do the following:

1.Start the server. You will see the message "Trial Period has Expired".

2. Click OK to enter the License details.

3. Browse and select the Registered License file (AdventNetLicense.xml) provided to you and repeat the steps mentioned above.

 

Extending trial license

 

You need to procure the extended trial license from Manageengine. This is provided purely on discretion. Send an email request to sales@manageengine.com

 

What is a .ppm file?

 

It is an abbreviation for Package for Patch Manager and has nothingto do with Perl. The File with .ppm extension is known to work with theUpdate Manager tool which is bundled with AdventNet Products. This toolhelps to upgrade to the newer version keeping the data intact.  InOpManager, you can access this tool using Start -> Programs ->ManageEngine OpManager -> Update Manager. Alternatively, you canalso invoke the tool from /opmanager/bin/UpdateManager.bat/sh.

 

Resolving timezone difference problems in OpManager & NFA Plug-in

 

 

Some of you may face the problem of the time on OpManager being different from the Server time. If this is the case, please follow the steps to fix the issue.

1. Save the attached file and rename it to time.jar and place it under OpManager folder.

2. Open a command prompt and go to OpManager folder and execute the command below by providing your exact time zone difference from the GMT.

cmd:/> jreinjava -Duser.timezone=GMT-9:00 -cp time.jar Time

Modify the query according to the time zone difference in your region. Here I am executing the query for changing the OpManager time to Alaska Time zone which is GMT -9.

3. Take a back up of wrapper.conf located under OpManagerconf folder.

4. Open the wrapper.conf and search for Java Additional Parameters and at the end of the additional parameters, add the entry below.


wrapper.java.additional.12=-Duser.timezone=GMT-9:00

After modifying it, the changes will look as below.

# Java Additional Parameters
wrapper.java.additional.1=-Dcatalina.home=apache/tomcat
wrapper.java.additional.2=-Dmysql.home=mysql
#wrapper.java.additional.3=-Dwebserver.port=80
#wrapper.java.additional.4=-Dresource_check="80,8009"
wrapper.java.additional.3=-Djava.library.path=lib
wrapper.java.additional.4=-Dwebserver.rootdir=apache
wrapper.java.additional.5=-Djava.rmi.server.codebase=apache/tomcat/conf/workers.properties
wrapper.java.additional.6=-Dcom.adventnet.me.opmanager.showprogress=true
wrapper.java.additional.7=-Dcom.adventnet.me.opmanager.service=true
wrapper.java.additional.12=-Duser.timezone=GMT-9:00

5. Save it and start OpManager as a service which will fix the problem.

Note: 1. The above changes will be in effect only if OpManager is started as a Service.
         2. "wrapper.java.additional.12=-Duser.timezone=GMT-9:00" - This line needs to be place at the end of the file and also change the line number(eg: 12) accordingly.


Steps to correct the time difference issue in OpManager-NFA plugin


1. Goto OpManagerNetflowin folder and edit the "run.bat" in a text editor and search for the following line:

 

set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME% -Djboss.server.type=com.adventnet.j2ee.deployment.system.AdventNetServerImpl

 

Change the above line as follows:

 

set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME% -Duser.timezone=GMT-9:00 -Djboss.server.type=com.adventnet.j2ee.deployment.system.AdventNetServerImpl

 

 

 

2. Restart OpManager service and the Netflow module would show the correct time.


Note:GMT-9:00 timezone is shown as an example.Please modify it as per your timezone.
Attached Files : time.jar 606 B
Prerequisites for monitoring WAN RTT

Prerequisites for MSSQL as backend DB
OpManager can create a database and its tables only if the MSSQL account has DBOwner privilege. 

It connects to MSSQL server using SQL username and password.  So have to enable SQL authentication.

For default MSSQL instance,port number will be 1433.
http://msdn.microsoft.com/en-us/library/ms177440.aspx
http://support.microsoft.com/kb/823938
For named instance, DB host should be entered as hostnameinstancename

Prerequisites to view detailed traffic reports from NFA in OpManager

 

To view the detailed traffic report from Netflow Analyzer, the prerequisites are,

  1. Netflow Analyzer must be up and running in your network

  2. The interface whose traffic you would like to monitor must be discovered in both, OpManager and Netflow Analyzer.

  3. The NetFlow Analyzer settings must be configured properly in OpManager

 



    Post a comment

    Your Name or E-mail ID (mandatory)

     

    Note: Your comment will be published after approval of the owner.



    		 RSS of this page