Is there any way to process ascii oid values to string values in a table
calculation?
The name is not stored as a string value in the MIB. The name is a pretty
important field to decode in this example, and it has to be decoded from the
oid itself.
mplsVpnVrfTable, .1,
TABLE, "mplsVpnVrfTable for ${deviceaddress}"
mplsVpnVrfTable/mplsVpnVrfNameLen, mplsVpnVrfDescription[0:1],
DEFAULT, "Name Length"
mplsVpnVrfTable/mplsVpnVrfName, mplsVpnVrfDescription[1:],
DEFAULT, "Name"
Example:
mplsVpnVrfDescription[0:] =4.84.101.115.116
mplsVpnVrfNameLen => 4 characters long
mplsVpnVrfName =>84.101.115.116 this equates to "Test"
This is second time in two weeks if have had to deal with ascii encoded oids
with Intermapper snmp probes.
So this encoding technique is obviously used by multiple vendors.
BigIP F5 load balancers uses the same technique to access it tables, but at
least have an equivalent string for display purposes.
It would be nice if Intermapper offered parameter string to oid conversion for
probe parameters which would mean better end user usability not having to
create magical string of numbers for probes.
ie Test => 4.84.101.115.116
This allows one to create probes that can access a row (rows with probe
grouping) in a table which can be graphed.
David Thomas
Network Engineer
University of South Australia
-------------------- m2f --------------------
Read this topic online here:
http://forums.intermapper.com/viewtopic.php?p=4090#4090
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [email protected]
