SNMP MIBs / questions

For your first question, if you log into the GUI of your BIG-IP, the very first page that shows up (The welcome screen) has the mib file link right on that page. (bottom right).

 

I don't know the answer to your second question.

The main thing I'm looking for that I haven't found yet is a way to see in SNMP if any real web servers drop out of a farm. We have some farms set up with multiple real web servers in each farm. These trees looked interesting...

.1.3.6.1.4.1.3375.2.2.10.13

.1.3.6.1.4.1.3375.2.2.10.14

... but I was expecting to see multiple "the virtual server is available" lines one for each real web server. There's also one "the virtual address is available" listed per farm but that makes sense.You can poll for the status of any pool member using OIDs under these branches:

pool_mem AvailabilityState.1.3.6.1.4.1.3375.2.2.5.3.2.1.15
pool_mem StatusReason        .1.3.6.1.4.1.3375.2.2.5.3.2.1.18.*

or you can trap on OIDs under these branches:

POOL_MEMBER_MON_STATUS snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.10"
POOL_MEMBER_MON_STATUS_UP snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.11"
NODE_ADDRESS_MON_STATUS snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.12"
NODE_ADDRESS_MON_STATUS_UP snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.13"

Also, its nothing major, but any insight as to why a virtual server that has been given a custom name gets such a weird OID? i.e. we renamed vs_200, but left vs_201 / vs_202 / vs_203 / vs_204 alone.. but it changed from a "6" to a "21" for the renamed virtual server and it has a much longer suffix after that.

.1.3.6.1.4.1.3375.2.2.10.13.2.1.1.6.118.115.95.50.48.49 = STRING: "vs_201"

.1.3.6.1.4.1.3375.2.2.10.13.2.1.1.6.118.115.95.50.48.50 = STRING: "vs_202"

.1.3.6.1.4.1.3375.2.2.10.13.2.1.1.6.118.115.95.50.48.51 = STRING: "vs_203"

.1.3.6.1.4.1.3375.2.2.10.13.2.1.1.6.118.115.95.50.48.52 = STRING: "vs_204"

.1.3.6.1.4.1.3375.2.2.10.13.2.1.1.21.118.115.95.119.119.119.46.101.114.105.116.101.115.116.105.110.103.46.99.111.109 = STRING: "vs_www.domain.com"The OIDs are ASCII translations of the characters comprising the name, and the "prefix" to the name string is the number of characters in the name string. In your case, you changed the name from a 6 char string to a 21 character one, so the prefix changed from 6 to 21. (Your vs name is only 17 characters long, though, so I'm assuming you must have sanitized the vs name before posting?)

Here are the VS names on my 9.4.3 box:

test  (4 characters)
vs_www.domain.com  (17 characters)
x123456789x123456789x123456789   (30 characters)

and some ASCII character values:

"t" is 116
"e" is 101
"s" is 115

and the corresponding OIDs:

.1.3.6.1.4.1.3375.2.2.10.13.2.1.1.4.116.101.115.116
.1.3.6.1.4.1.3375.2.2.10.13.2.1.1.17.118.115.95.119.119.119.46.100.111.109.97.105.110.46.99.111.109
.1.3.6.1.4.1.3375.2.2.10.13.2.1.1.30.120.49.50.51.52.53.54.55.56.57.120.49.50.51.52.53.54.55.56.57.120.49.50.51.52.53.54.55.56.57

You can use snmptranslate to get the VS name from an OID:

snmptranslate .1.3.6.1.4.1.3375.2.2.10.13.2.1.1.4.116.101.115.116

returns

F5-BIGIP-LOCAL-MIB::ltmVsStatusName."test"

snmptranslate .1.3.6.1.4.1.3375.2.2.10.13.2.1.1.17.118.115.95.119.119.119.46.100.111.109.97.105.110.46.99.111.109

returns

F5-BIGIP-LOCAL-MIB::ltmVsStatusName."vs_www.domain.com"

snmptranslate .1.3.6.1.4.1.3375.2.2.10.13.2.1.1.30.120.49.50.51.52.53.54.55.56.57.120.49.50.51.52.53.54.55.56.57.120.49.50.51.52.53.54.55.56.57

returns

F5-BIGIP-LOCAL-MIB::ltmVsStatusName."x123456789x123456789x123456789"

This doc (Click here) has some additional details, I think...

HTH

/deb