This sounds so stupid: How is that we have tons of MIBs and OIDs in UnDP but still when tested it shows "OID not supported" though we choose the right one? why is that?
The device your testing the OID against has to support it. i.e. if you test a Cisco OID against a HP Switch it wont work...
Also some devices don't support all the OID's, the Cisco Fan status example within UnDP only work on larger switches such as the 6500 series and not on the smaller ones like 2960's
If you check the manufacturers web site you can check the valid mib's against the devices...#
Hope this makes sense
Matt Jenkins
I've also seen cases where you will get oid not supported if there is no data in the table. I've seen devices that only populate things when there is a reason to and the rest of the time it is empty.
Yes sir. It is easier to search IOD on the device website if supported or not rather than searching it through UnDP but the thing is, although it is supported UnDP still not recognizing IOD.
There are three basic step to verify why the UnDP when test it failed
1. Check community string
2. MIb/OID should be supported, can be check on vendor's documentation or website
3. Confirm if the device can responding to icmp and snmp requests.
Done this but still with no avail
What I usually do is hit an OID that I know works correct to verify proper connection to the device. Then I go after my targeted OID.
In my cause, we get traps sent when data is in the table so after getting the trap I checked it and got the data I was looking for. I checked later and got "OID not supported."
You could also do an MIB walk and browse to the area of interest. This helped me recently with a UPS OID I was looking for.
