If a SNMP MIB cannot be found to be imported into the DIS MIB Tool for Visual Studios, is there some easy procedures to copy OIDs found in an SNMP walk into Visual Studio while creating a connector
Randy Ulvenes [SLC] [DevOps Advocate] Selected answer as best 27th May 2021
Hi Randy,
Without a MIB or at least an indication of what each OID represents it will be very difficult to easily create a connector. An SNMP walk only contains the value for each OID at the time you took the walk, but doesn’t contain any information about the description, unit, possible options, range,…
DIS doesn’t have any other functionality to generate SNMP parameters than loading the necessary MIBs and generating from that. The only alternative is to manually created the parameters and link their OID.
Randy Ulvenes [SLC] [DevOps Advocate] Selected answer as best 27th May 2021
Thank you Joey and Miguel!
Hi Randy,
Just to give additional information, normally in a raw SNMP walk you will receive the following information:
– SNMP OID
– Data type: octetstring, integer, etc..
– Raw value
Although we could still create manually the parameters based on this information (based on the data type and raw value), I believe that you will have a problem mapping OIDs that belong to column parameters. For example, giving the following OID:
– 1.3.6.1.2.1.2.2.1.10.1
This OID corresponds to the ifInOctets column from the Interface table. Without the MIB file you will not know what part corresponds to the SNMP OID (InOctets) and which part corresponds to the index of the table. In some cases the last digit will represent the index (like the example above), but there is no rule about it (some vendors use more than one digit for indices)
For single OIDs, you will notice that the last digit will be always ‘0’