CrystalSet
Aug 09, 2012Nimbostratus
OID changes afte config changes.
Running 11.1.0 Build 2027.32
We did an SNMPwalk on the OID to find the OIDs for some real server status variables we want to monitor in PRTG. We found the OIDs and they return a text string "Pool member is available". The PRTG sensor looks in the returned string for the word "available".
We have two LTMs in a pair and the OID for the node was the same on both.
After making and unrelated change to the configuration of the F5 (adding an iRule to unrelated VIP) the sensor went down. Running another snmp walk showed that the OID had changed on the active LTM but not on the secondary.
So my questions are
1. Has anyone else seen this problem?
2. How do we stop the OID from changing if other configurations is changed?
3. How do we keep the OIDs in sync between the two LTMs in the cluster?
Not sure if this is a bug - I know Cisco interfaces can change OIDs after a reboot which is a similar problem, and that can be fixed with a configuration on the switch.