Note, that your OIDs are 1.3.6.1.4.1.5003.9.10.1.1.4.1.1.17.0 and 1.3.6.1.4.1.5003.9.10.1.1.4.1.1.17.1 ... so of course 1.3.6.1.4.1.5003.9.10.1.1.4.1.1.17 is bad ...
To see if Zenoss is going to get an OID, use snmpget ... -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University cdillardhsp wrote, On 7/2/2009 1:55 PM: > I think we're getting closer. I added 'trapuser' to the zProperties of our > AudioCodes card in the zSnmpSecurityName and zSnmpCommunities fields since > that is what's listed in the card's web management UI and now when I test the > SNMP check from within the Template setup page in Zenoss I get the following > results. > > Executing command > snmpwalk -cmexico -v2c 192.168.168.198 1.3.6.1.4.1.5003.9.10.1.1.4.1.1.17 > against RDU-IVRcard1 > SNMPv2-SMI::enterprises.5003.9.10.1.1.4.1.1.17.0 = INTEGER: 2 > SNMPv2-SMI::enterprises.5003.9.10.1.1.4.1.1.17.1 = INTEGER: 1 > DONE in 0 seconds > > Zenoss still reports Error reading value for "ISDN-Line" on RDU-IVRcard1 (oid > .1.3.6.1.4.1.5003.9.10.1.1.4.1.1.17 is bad) in the Events for the card though. > > Now I think I have to determine how to proceed from here to get Zenoss to > alert on the state (which I think is what this OID references) if it is other > than up/good.[/b] > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=36628#36628 > > -------------------- m2f -------------------- > > > > _______________________________________________ > zenoss-users mailing list > zenoss-users@zenoss.org > http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list zenoss-users@zenoss.org http://lists.zenoss.org/mailman/listinfo/zenoss-users
