Posted Tue, 28 Aug 2018 15:29:37 GMT by Corwin Dawe

 I need to create a custom probe , and no MIB file is available. I do have the OID's that are required. I can use the OID's and get the values from the device using SNMP get command, but when i create a custom probe it   shows N/A.

This is the Probe below.   Hope someone can offer some help.

 

<!--
FlexScada FlexQ4 probe for InterMapper - http://intermapper.com
Copy this text and save as a file named: com.dartware.snmp.flexscadaflexq4.txt
Then import it using File -> Import -> Probe...

This is an InterMapper SNMP probe that monitors several variables for InterMapper.
... You can add more commentary if it would be useful ...


As you make modifications, be sure to update the Revision history below:

Revisions:
8/27/2018 Generated by Interactive SNMP Probe Builder page, version 1.0a1,
at: http://intermapper.com/probebuilder.aspx

-----------------------------------------------------------------------------------

Please feel free to use this file as a base for further development.
Read the Developer Guide to learn more about InterMapper Probes. The Guide is at:
http://dartware.com/go.php?to=intermapper.devguide
-->

-- The <description> section contains the text that will appear in the Set Probe... window.
-- It gives you a chance to describe how the probe works, what the parameters are, and how to
-- how to set it up.

<description>

\gb\FlexScada FlexQ4\p\

Probe to View Voltages and relay status using FlexScada FlexQ4
</description>

-- The <header> section determines the probe's unique name, what kind of probe it is,
-- its Human Name, and its place in the probe picker hierarchy, and other assorted attributes.

<header>

"type" = "custom-snmp"
"package" = "com.dartware"
"probe_name" = "snmp.flexscadaflexq4"
"human_name" = "FlexScada FlexQ4"
"display_name" = "Experimental/FlexScada FlexQ4"
"version" = "1.0"
"address_type" = "IP,AT"
"port_number" = "161"

</header>

-- <snmp-device-properties> are flags that alter the InterMapper probe's behavior.
-- You generally do not need to use these, but they can be useful for devices that don't
-- work as expected. For more information, see the <snmp-device-properties> section of the
-- Developer Guide's at: http://dartware.com/support/docs/index.html

<snmp-device-properties>
-- none required
</snmp-device-properties>

-- Parameters are user-settable values that the probe uses for its comparisons.
-- Specify the default values here. The customer can change them and they will be retained for each device.

<parameters>

-- No parameters specified.

</parameters>

-- InterMapper retrieves the <snmp-device-variables> using the OID or variable names from the MIB.
-- Specify the variable name, the MIB name or OID, the format (usually DEFAULT) and a short description.

<snmp-device-variables>

oid_1_3_6_1_4_1_4128_1, 1.3.6.1.4.1.4128.1, DEFAULT, "1.3.6.1.4.1.4128.1"
oid_1_3_6_1_4_1_4128_2, 1.3.6.1.4.1.4128.2, DEFAULT, "1.3.6.1.4.1.4128.2"
oid_1_3_6_1_4_1_4128_3, 1.3.6.1.4.1.4128.3, DEFAULT, "1.3.6.1.4.1.4128.3"
oid_1_3_6_1_4_1_4128_4, 1.3.6.1.4.1.4128.4, DEFAULT, "1.3.6.1.4.1.4128.4"
oid_1_3_6_1_4_1_4128_5, 1.3.6.1.4.1.4128.5, DEFAULT, "1.3.6.1.4.1.4128.5"
oid_1_3_6_1_4_1_4128_6, 1.3.6.1.4.1.4128.6, DEFAULT, "1.3.6.1.4.1.4128.6"
oid_1_3_6_1_4_1_4128_7, 1.3.6.1.4.1.4128.7, DEFAULT, "1.3.6.1.4.1.4128.7"
oid_1_3_6_1_4_1_4128_8, 1.3.6.1.4.1.4128.8, DEFAULT, "1.3.6.1.4.1.4128.8"
oid_1_3_6_1_4_1_4128_9, 1.3.6.1.4.1.4128.9, DEFAULT, "1.3.6.1.4.1.4128.9"
oid_1_3_6_1_4_1_4128_10, 1.3.6.1.4.1.4128.10, DEFAULT, "1.3.6.1.4.1.4128.10"
oid_1_3_6_1_4_1_4128_11, 1.3.6.1.4.1.4128.11, DEFAULT, "1.3.6.1.4.1.4128.11"
oid_1_3_6_1_4_1_4128_12, 1.3.6.1.4.1.4128.12, DEFAULT, "1.3.6.1.4.1.4128.12"
oid_1_3_6_1_4_1_4128_13, 1.3.6.1.4.1.4128.13, DEFAULT, "1.3.6.1.4.1.4128.13"
oid_1_3_6_1_4_1_4128_14, 1.3.6.1.4.1.4128.14, DEFAULT, "1.3.6.1.4.1.4128.14"
oid_1_3_6_1_4_1_4128_15, 1.3.6.1.4.1.4128.15, DEFAULT, "1.3.6.1.4.1.4128.15"

</snmp-device-variables>

-- The 'autorecord' section specifies the variables that
-- will be saved to the InterMapper Database.
-- No 'autorecord' variables specified.

-- Specify rules for setting the device into Alarm or Warning state.
-- The rules are tested top-to-bottom, and stop when one matches.

<snmp-device-thresholds>

-- No thresholds specified.

</snmp-device-thresholds>

-- The <snmp-device-display> section specifies the text that will be appended
-- to the device's Staus Window.

<snmp-device-display>
\B5\FlexScada FlexQ4\P0\
\4\ 1.3.6.1.4.1.4128.1:\0\ $oid_1_3_6_1_4_1_4128_1 \3G\1.3.6.1.4.1.4128.1\M0\
\4\ 1.3.6.1.4.1.4128.2:\0\ $oid_1_3_6_1_4_1_4128_2 \3G\1.3.6.1.4.1.4128.2\M0\
\4\ 1.3.6.1.4.1.4128.3:\0\ $oid_1_3_6_1_4_1_4128_3 \3G\1.3.6.1.4.1.4128.3\M0\
\4\ 1.3.6.1.4.1.4128.4:\0\ $oid_1_3_6_1_4_1_4128_4 \3G\1.3.6.1.4.1.4128.4\M0\
\4\ 1.3.6.1.4.1.4128.5:\0\ $oid_1_3_6_1_4_1_4128_5 \3G\1.3.6.1.4.1.4128.5\M0\
\4\ 1.3.6.1.4.1.4128.6:\0\ $oid_1_3_6_1_4_1_4128_6 \3G\1.3.6.1.4.1.4128.6\M0\
\4\ 1.3.6.1.4.1.4128.7:\0\ $oid_1_3_6_1_4_1_4128_7 \3G\1.3.6.1.4.1.4128.7\M0\
\4\ 1.3.6.1.4.1.4128.8:\0\ $oid_1_3_6_1_4_1_4128_8 \3G\1.3.6.1.4.1.4128.8\M0\
\4\ 1.3.6.1.4.1.4128.9:\0\ $oid_1_3_6_1_4_1_4128_9 \3G\1.3.6.1.4.1.4128.9\M0\
\4\1.3.6.1.4.1.4128.10:\0\ $oid_1_3_6_1_4_1_4128_10 \3G\1.3.6.1.4.1.4128.10\M0\
\4\1.3.6.1.4.1.4128.11:\0\ $oid_1_3_6_1_4_1_4128_11 \3G\1.3.6.1.4.1.4128.11\M0\
\4\1.3.6.1.4.1.4128.12:\0\ $oid_1_3_6_1_4_1_4128_12 \3G\1.3.6.1.4.1.4128.12\M0\
\4\1.3.6.1.4.1.4128.13:\0\ $oid_1_3_6_1_4_1_4128_13 \3G\1.3.6.1.4.1.4128.13\M0\
\4\1.3.6.1.4.1.4128.14:\0\ $oid_1_3_6_1_4_1_4128_14 \3G\1.3.6.1.4.1.4128.14\M0\
\4\1.3.6.1.4.1.4128.15:\0\ $oid_1_3_6_1_4_1_4128_15 \3G\1.3.6.1.4.1.4128.15\M0\

</snmp-device-display>

Posted Tue, 28 Aug 2018 18:47:49 GMT by Mike Maki

Hello Corwin,

The OIDs you're showing, 1.3.6.1.4.1.4128.1 - 1.3.6.1.4.1.4128.15, translate to enterprises.4128.1 - enterprises.4128.15, where  4128 is the private enterprise ID for the vendor, in this case ARM Ltd, apparently.

The individual subids for enterprises.arm could be defined traps, or MIB branches, or scalar objects.If it were a table, there would be a table object and entry object that aren't showing.

Maybe the easiest thing to try is to assign an SNMP traffic probe to the device, right-click it and use SNMPWalk with the SNMP Object ID field set to 1.3.6.1.4. That will show all objects available in the private enterprise branch of the device MIB that the SNMP agent on the device will export (assuming SNMP is enabled and you're using the correct SNMP version and community or other authentication).

Objects with values returned for them can be used as probe variables and you should get responses for them.

Please let me know the response you get, in the open support ticket CAS-0010112506. Just email [email protected] with that Case ID in the subject line.

best regards,

Mike Maki

InterMapper Support

You must be signed in to post in this forum.