What OID(s) are failing? What platform are you trying to poll? What exactly is happening? Are you getting an error, or no data?
I'm trying to monitor CISCO-IPSEC-FLOW-MONITOR-MIB OIDs, 220.127.116.11.18.104.22.168.22.214.171.124.1.4 for example.
I'm trying to poll a Cisco device, c7200-ik9s-mz.124-25c.bin to be exact.
When I poll through the Universal Device Poller program, I get an error which says "This OID is not supported."
this statement means that the device does not respond to this OID. I would do a snmp walk on your device and then look for this OID. You will see if it is supported by your device or not.
I did an SNMP walk and got the same results. I thought that if a router supported a MIB, it supported all OIDs in the MIB. I guess it seems weird that table OIDs, specifically, are not supported even though other OIDs in the same MIB are. Why might a router exclusively support non-table OIDs?
Lauren, I am thinking the same thing that the device should support the entire MIB, though there could possibly be something hardware specific...as in specific to having a certain module installed. I also wonder if it is merely a coincidence that the OIDs not working are tables.
Are you applying any SNMP views in the device's configuration? if a view is configured, it could be blocking the ability to poll specific OIDs.
That's a good idea, but I'm not applying any views. You might be right that its just a coincidence... I did a test on another MIB (ENTITY_MIB),
OID=.126.96.36.199.188.8.131.52.184.108.40.206.27, Type=Integer, Value=2
OID=.220.127.116.11.18.104.22.168.22.214.171.124.28, Type=Integer, Value=1
OID=.126.96.36.199.188.8.131.52.184.108.40.206.29, Type=Integer, Value=2
OID=.220.127.116.11.18.104.22.168.22.214.171.124.30, Type=Integer, Value=2
OID=.126.96.36.199.188.8.131.52.184.108.40.206.31, Type=Integer, Value=1
OID=.220.127.116.11.18.104.22.168.22.214.171.124.32, Type=Integer, Value=2
OID=.126.96.36.199.188.8.131.52.184.108.40.206.33, Type=Integer, Value=2
OID=.220.127.116.11.18.104.22.168.22.214.171.124.34, Type=Integer, Value=1
OID=.126.96.36.199.188.8.131.52.184.108.40.206.35, Type=Integer, Value=2
OID=.220.127.116.11.18.104.22.168.22.214.171.124.36, Type=Integer, Value=2
OID=.126.96.36.199.188.8.131.52.184.108.40.206.37, Type=Integer, Value=1
OID=.220.127.116.11.18.104.22.168.22.214.171.124.38, Type=Integer, Value=1
OID=.126.96.36.199.188.8.131.52.184.108.40.206.13.0, Type=OID, Value=220.127.116.11.18.104.22.168.1.1.1
OID=.22.214.171.124.126.96.36.199.188.8.131.52.14.0, Type=OID, Value=184.108.40.206.220.127.116.11.1.1.2
OID=.18.104.22.168.22.214.171.124.126.96.36.199.26.0, Type=OID, Value=188.8.131.52.184.108.40.206.1.1.3
OID=.220.127.116.11.18.104.22.168.22.214.171.124.27.0, Type=OID, Value=126.96.36.199.188.8.131.52.1.1.4
OID=.184.108.40.206.220.127.116.11.18.104.22.168.29.0, Type=OID, Value=22.214.171.124.126.96.36.199.1.1.5
OID=.188.8.131.52.184.108.40.206.220.127.116.11.30.0, Type=OID, Value=18.104.22.168.22.214.171.124.1.1.6
OID=.126.96.36.199.188.8.131.52.184.108.40.206.32.0, Type=OID, Value=220.127.116.11.18.104.22.168.1.1.7
OID=.22.214.171.124.126.96.36.199.188.8.131.52.33.0, Type=OID, Value=184.108.40.206.220.127.116.11.1.1.8
OID=.18.104.22.168.22.214.171.124.126.96.36.199.35.0, Type=OID, Value=188.8.131.52.184.108.40.206.1.1.9
OID=.220.127.116.11.18.104.22.168.22.214.171.124.36.0, Type=OID, Value=126.96.36.199.188.8.131.52.1.1.10
184.108.40.206.220.127.116.11.1.1.1 is a table, as well as 18.104.22.168.22.214.171.124.3.2.1, and it seems to scan them fine. The odd thing is that there's a table in between the two, 126.96.36.199.188.8.131.52.2.* that it just completely skips over. Maybe that "skipping over OIDs" thing is the real problem here.
Not sure if that helps. I'd be happy to run more tests if you can think of some that would help!
It was a coincidence that table OIDs weren't found. Turns out IPSec tunnels don't show up in any sort of tunnel MIB until the tunnel is active (aka traffic has gone through it). This explains why I wasn't getting any results for the tunnel tables even though I'd created policies.
Thanks for all your help!
you can create custom poller to poll particular row in table.
First you need to make sure that OID is supported by device. Sometimes the device support SNMP, but you need to upload the MIB to device or update it.
- Check with Test button if table OID is supported and there is reply with rows and values.
- If for example I want particular row from table for OID 184.108.40.206.220.127.116.11.1.8, add dot with RowID .18.104.22.168. The final OID would look 22.214.171.124.126.96.36.199.188.8.131.52.250.2
- SNMP Get Type change to: GET, Polling type: Node
Also on polling table have influence SNMP version. If you have trouble with polling table OID you can try to us SNMPv1. (SNMPv2 uses GET BULK request which may be not supported by some devices.)
- Open node details in Orion web console for node where UnDP is assigned
- Click Edit Node
- Change SNMP Version from SNMPv2 to SNMPv1
- Click Submit
Picture how to poll particular row from table:
Thank you very much for the helpful picture!
I walked through those steps, testing with both SNMPv1 and 2c, but with the same results.
Good suggestion though!