Per advice from TheWitness, I set "Maximum OIDs Per GET Request" to 1 and that solved the problem. Apparently the Netscaler was not returning results in the same order in which snmp had asked for them.
Thanks!
--
Cody
Search found 4 matches
- Sat Feb 13, 2010 5:03 pm
- Forum: Help: Linux/Unix Specific
- Topic: Spine not polling correct OIDs from Netscaler
- Replies: 4
- Views: 1843
- Tue Feb 09, 2010 6:14 pm
- Forum: Help: Linux/Unix Specific
- Topic: Spine not polling correct OIDs from Netscaler
- Replies: 4
- Views: 1843
- Tue Feb 09, 2010 2:19 pm
- Forum: Help: Linux/Unix Specific
- Topic: Spine not polling correct OIDs from Netscaler
- Replies: 4
- Views: 1843
- Tue Feb 09, 2010 2:05 pm
- Forum: Help: Linux/Unix Specific
- Topic: Spine not polling correct OIDs from Netscaler
- Replies: 4
- Views: 1843
Spine not polling correct OIDs from Netscaler
We are seeing a very peculiar issue when graphing our Citrix Netscaler VIPs. We graph in/out bytes via a COUNTER SNMP OID for each VIP. This has always worked great, until a recent upgrade to the Citrix boxes. Now it appears that Spine is somehow mangling the OID that I specify for the data source. ...