Re: discepancy between v1 and v2c
"Dave Shield" <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
On 05/10/06, Mathew Bielejeski <[email protected]> wrote: > snmpget.exe -c public -v1 192.168.1.1 1.3.6.1.2.1.2.2.1.10.6 > Error in packet > Reason: (noSuchName) There is no such variable name in this MIB. > Failed object: IF-MIB::ifInOctets.6 > snmpget.exe -c public -v2c 192.168.1.1 1.3.6.1.2.1.2.2.1.10.6 > IF-MIB::ifInOctets.6 = No Such Instance currently exists at this OID > Why does snmpv1 return an error while snmpv2c does not? Because that's how the two protocols are defined as working. [Sorry Wes - read the question again] The only way that can SNMPv1 report non-existent instances (or objects) is via the error 'noSuchName'. SNMPv2c extended this handling to introduce two "exceptions" (noSuchInstance, and noSuchObject). These don't count as full SNMP errors (so the agent can report partial results). Dave ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users