Kaseya & Manual SNMP Identification

This document outlines step by step how to load an SNMP Object (MIB) into Kaseya, and turn it into

an SNMP SET

Tools Required

Kaseya 6.0.0.0 or greater

GetIF (Free download)

Vendor Mibs of device you wish to monitor

Assumptions

You have the IP Address of the device you want to monitor

You have SNMP Read access to the Device you wish to monitor

For the purpose of this exercise, we will look at a HP Procurve 5308XL Core Series Switch

You have GetIF Installed and familiar with the software

Finding what to measure is a time consuming process per device

Expect to spend at least an hour per device if you haven’t been exposed to SNMP / MIBS / GetIF

Process

Step 1: Get info about Device

What HP Procurve 5308XL Measurement Fan & PSU Failure Where On a customer site Collect Mibs HP-ICF-OID.mib

hpicfChassis.mib hpicfDcFan.mib hpicfDcPower.mib hpicfOid.mib RFC1155-SMI.txt RFC1213-MIB.txt RFC1271-MIB.txt rfc2578.mib rfc2579.mib rfc3411.mib

Note: The above mentioned MIBS are relevant for this device Other Devices have different MIBS, download other MIBS from Vendors

Step 2: Use GetIF, Analyse Results

Copy Mibs to “C:\Program Files\GetIF 2.3.1\Mibs” Run GetIF Parameters tab > Enter IP Address > Click Start MBrowser tab > Search for values to measure In this case

Iso.org.dod.internet. enterprise.hp.nm.icf. hpicfobjects.hpicfcommon.hpicfchassis. hpicfsensortable.hpicfsensorentry.hpicfsensorstatus

Note OID: 1.3.6.1.4.1.11.2.14.11.1.2.6.1.4

1. Fully qualified SNMP Object Name, Fully qualified SNMP Number

2. Select this to evaluate the mib

3. Note the three values inside the object

Each value will be represent by another oid

IE: Sensor status: 1.3.6.1.4.1.11.2.14.11.1.2.6.1.4

Sensor status 1 : 1.3.6.1.4.1.11.2.14.11.1.2.6.1.4.1

Sensor status 2 : 1.3.6.1.4.1.11.2.14.11.1.2.6.1.4.2

Sensor status 3 : 1.3.6.1.4.1.11.2.14.11.1.2.6.1.4.3

4. Note: i(integer) is the SYNTAX field used in step 3

What this means

Sensor Status is what we are measuring; this is the object we need to import in Kaseya

The sub values, that is, .1,.2,.3, are each individual sensor detected inside the unit.

IMPORTANT: Note how many SUB VALUES Exist, this is the SNMP Instance number in Kaseya

Step 3: Import into Kaseya

Follow these steps to import Mib Objects into Kaseya

In Kaseya > Monitor Monitor > Edit > Add SNMP Object > Load Mib > Browse Mibs Load Mibs into Kaseya from Step 2

HP-ICF-OID.mib hpicfChassis.mib hpicfDcFan.mib hpicfDcPower.mib hpicfOid.mib RFC1155-SMI.txt RFC1213-MIB.txt RFC1271-MIB.txt rfc2578.mib rfc2579.mib rfc3411.mib

In Kaseya > Monitor Monitor > Edit > Monitor Lists > Counter Objects Browse counter objects to see if your object already exists In Kaseya > Monitor Monitor > Edit > Monitor Lists > CMIB OID’s > ADD Display Name: HpICFSensorStatus Name: HpICFSensorStatus Numbered OID: 1.3.6.1.4.1.11.2.14.11.1.2.6.1.4 Char OID 1.3.6.1.4.1.11.2.14.11.1.2.6.1.4 Syntax integer Access: Read-only Description HP Sensor Status.

Step 4: Create SNMP Set

In Kaseya > Monitor Monitor > Edit > Monitor Lists > SNMP Sets Shared Folder > Add Folder > New SNMP SET > SNMP Sets > ADD (Data) Mib Object: HpICFSensorStatus SNMP Version: 1 SNMP Instance: 1-3 (Remember, in this device we have 3 sensors) Value Returned as: _total Name: HpICFSensorStatus Description: HpICFSensorStatus Collection: -1 SNMP Timeout: 2 Seconds Alarm Operator: Under Alarm Threshold: 3 Duration: 30 Seconds Ignore Additional Alarm 1 Hours <<NEED TO CHECK LOGIC – DOES ALARM UNDER 4 IMPLY SENSOR FAILURE?>>

Step 5: Assign SNMP to device:

I will assume the user will know how to do his step

Step 6: Conclusion:

If MIB Import is successful the Manual creation, and application SNMP set should be successful