You can see this in the walk data vs the text version
ASCII
47.67.111.109.109.111.110.47   
CHAR
/Common/

Once I had worked that out, monitoring F5's and Netscaler's became much, much easier. Having it indexed would be even better.

Lots of other things are like this - CISCO blade centre blades and thinks like that.

From the archives: - ascii to char conversion
https://ee.hawaii.edu/~tep/EE160/Book/chap4/subsection2.1.1.1.html

I use CITRIX now, but for F5 snmp monitoring - it is  reasonable well documented here ==?  https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-external-monitoring-implementations-13-1-0/13.html

The only problem is that the mib with the indexed oids are in F5-BIGIP-LOCAL-MIB.txt - which they do not explain how to do the conversion - but they do explain everything else.

The challenge here is that we selectively monitored the server / vserver / node tables for specifics such as UP or DOWN and if membership was 100%.

Perhaps include a SNMP wizard that walks the mib, builds the various tables (ltmPoolMember is one example of a table we used), allowing the user to select which items in the table to monitor.

Our way?  - walk the  whole mib - copy our virtual server name / paste into ascii converter - then copy the ascii string - paste it onto the end of the OID for that table that we wanted to monitor -