Datasource development challenge
Anyone have any ideas about how to solve this challenge?
We'd like to collect dhcp relay stats from our Juniper routers, not necessarily for minute-by-minute graphs and alerts but to be able to show patterns of longer term trends (hourly, daily, monthly) I've got the list of OIDs for the counts of DORA plus Naks, Informs, total lease count and total drops.
The kicker is that they are stored on a per routing instance (ie VRF) basis and the OIDs aren't structured like #WILDVALUE (routing instance name or ID)#.n.n.n Instead, all routing instances use the same OIDs, and to query them you issue a get at each OID with [routing instance name@(snmp community)] as the snmp community; the output returned corresponds to the name of the routing instance.
Somehow this has to possible, but it may be a situation where the effort to achieve and/or sustain it is going to exceed the value of the data it would provide.
- Anonymous5 years ago
In 15 years of SNMP monitoring, I've never seen it done that way. Somebody got needlessly creative. Just to be sure, you do make the SNMP get to the same address, regardless of VRF, right?
So, you could switch to groovy and make the SNMP queries custom. Looks like both the Snmp.get() and Snmp.walk have the ability to get specify the community string at runtime. So, if you have the list of VRF names and you have the base community string, you could construct the concatenated version and make the query using a different "community string" for each VRF.