OID for Availability

[simmibansal]

We use ehealth to create network reports by polling our devices for data, the reports have been coming back with 0 availability for one of our router interfaces when we know it has not been down (its also showing BW IN as 0 which we also know is not the case). The software vendor advises the mib is ok, they got the same result from the mib dump we sent them, they advise its a problem with the router. We want to query the availability and/or BW IN using snmp walk instead to see if we get a value different to 0 (just to make sure it isn't an issue with the reporting software), does anyone know what the OID for availability/BW IN is?

[yjdabear]

It's not a simple OID value. EH uses various formulae for calculating the reported values. To find out, first locate the element (in this case, the router interface) on the left pane of the Organization tab. Click on the element name, and wait for the right pane ("Report List") to refresh. Then locate the row of four icons at the lower right corner of that pane. The last (4th) icon should have the label "Run an element variable report" when you mouse-over it. Do that. That should produce a report of what OIDs/variables eHealth use for that particular element. For example:

Availability = ((AvailableTime*100.0))/deltaTime

Bandwidth Utilization In = (decode($(speedIn),0.00,0.00,(((ifHCInOctets*8)*100.0)/NULLIF($(speedIn),0))))/deltaTime

These are on the first page: Trend Variables. The "next page" is "MIB Variables".

[simmibansal]

Thanks, we thought it was a calculated value but had no idea how. We don't actually have an Organization tab, we're using ehealth 5.7 so maybe that's why? There appears to be no option to run an element variable report either.

If I tell you more about the overall problem you might be able to help. The availability was reporting ok for a particular element until there was an outage on the element, literally only for a few seconds, the element came back up ok, but ehealth continued to show the availability as being 0 (as well as BW IN and a couple other reporting stats). We rebooted the router and the availability came back correctly, a few weeks later there was a brief outage again and ehealth again continued to report the availability as 0. The software support guys advise it isn't a fault with ehealth as it is reporting what it is seeing from the router when it polls it, so they advised to contact the device vendor (which is cisco). None of our other routers are having this problem and they're the same router model and using the same IOS. So we wanted to gather the data using SNMP walk instead to see if it saw zero as well, as if it saw a different value it would confirm the device is actually ok. The element in question is an ATM interface.