Forum Discussion
Hamish
Aug 09, 2012Cirrocumulus
Mm... The OID shouldn't change. And doesn't in 10.2.4 (As the index is poolname.ipv4.ipaddress.port).
But I'm not sure we're looking at the same thing. Obviously your OID's won't work on my system as the pools and poolmembers aren't the same. I've tested on 10.2.4 and 11.2.0 (Sorry, don't have an 11.1.0).
Can you try dumping the whole table from both. e.g. using snmpwalk and the OID
.1.3.6.1.4.1.3375.2.2.5.6.2.1.5
On 11.2 you'd get something like
F5-BIGIP-LOCAL-MIB::ltmPoolMbrStatusAvailState."/Common/wat__pool".18.47.67.111.109.109.111.110.47.109.101.109.98.101.114.116.101.115.116.444 = INTEGER: red(3)
F5-BIGIP-LOCAL-MIB::ltmPoolMbrStatusAvailState."/Common/wat__pool".19.47.67.111.109.109.111.110.47.49.48.46.50.48.46.52.49.46.49.52.80 = INTEGER: red(3)
F5-BIGIP-LOCAL-MIB::ltmPoolMbrStatusAvailState."/Common/hsl-log-01".25.47.67.111.109.109.111.110.47.99.97.99.116.105.46.110.101.116.46.108.99.104.46.99.111.109.514 = INTEGER: blue(4)
F5-BIGIP-LOCAL-MIB::ltmPoolMbrStatusAvailState."/Common/wat__aaa_srvr_pool".19.47.67.111.109.109.111.110.47.49.48.46.50.48.46.55.49.46.51.54.1812 = INTEGER: blue(4)
F5-BIGIP-LOCAL-MIB::ltmPoolMbrStatusAvailState."/Common/wat__aaa_srvr_pool".19.47.67.111.109.109.111.110.47.49.48.46.50.48.46.55.49.46.51.55.1812 = INTEGER: blue(4)
But the returned information doesn't match what you think it should either. Because that OID table returns the STATUS of the poolmember. Which is an integer where 1==green (UP), 3==red (DOWN), 4==blue (UNCHECKED) etc...
H