Sorry, Paul - this is nothing to do with scalar instances, or the difference between "snmpget" and "snmpwalk" It's down to the particular MIB object(s) involved
> If I an snmpwalk -O n (blah blah), it returns: > .1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.8072.3.2.3 In other words: SNMPv2-MIB::sysObjectID = NET-SNMP-TC::solaris which means "The identify of this particular agent is a solaris version of the Net-SNMP agent" Note that the *value* NET-SNMP-TC::solaris is associated with a particular MIB object (SNMPv2-MIB::sysObjectID) But: > snmpget -v 1 -c public -m ALL localhost 1.3.6.1.4.1.8072.3.2.3 > Reason: (noSuchName) There is no such variable name in this MIB. NET-SNMP-TC::solaris does not have a value associated with it. It is *not* a MIB object itself - it's simply a "named value". Compare the two MIB definitions: sysObjectID OBJECT-TYPE SYNTAX .... ::= { system 2 } solaris OBJECT IDENTIFIER ::= { netSnmpAgentOIDs 3 } They are very different styles of definition. Only OBJECT-TYPE definitions have a value associated with them. As far as "snmpget" and friends are concerned, you can ignore anything other than OBJECT-TYPE definitions. Dave ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ 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