On 5/25/2011 2:49 PM, Harold Hallikainen wrote:
>   =20
>> What happens if you do a SNMP GET on that single OID? (.1.3.6.1.2.1.1.5.=
0)
>>
>> The app note also mentions updating SNMPGetNextIndex for dynamic
>> variables.
>>
>> "Make corresponding changes in the
>> SNMPGetVar(), SNMPGetNextIndex() and
>> SNMPSetVar() callback functions to
>> accommodate these new dynamic or sequence
>> variable IDs. Map them to the respective
>> variable's RAM value."
>>
>>     =20
> OK, I missed SNMPGetNextIndex(). This is a read only value, so I don't
> think I need SNMPSetVar().
>
> Here's some output for what I have right now:
>
> C:\Documents and Settings\GX620>snmpwalk -v 1 -c public 192.168.1.155 iso
> SNMPv2-MIB::sysDescr.0 =3D STRING: PIC
> SNMPv2-MIB::sysObjectID.0 =3D OID: SNMPv2-SMI::enterprises.17095
> DISMAN-EVENT-MIB::sysUpTimeInstance =3D Timeticks: (29307) 0:04:53.07
> SNMPv2-MIB::sysContact.0 =3D STRING: admin
> SNMPv2-MIB::sysName.0 =3D STRING: office
> SNMPv2-MIB::sysLocation.0 =3D STRING: office
> SNMPv2-MIB::sysServices.0 =3D INTEGER: 7
> SNMPv2-SMI::enterprises.17095.1.1.0 =3D STRING: "SNMPv2c Agent"
> SNMPv2-SMI::enterprises.17095.1.2.0 =3D STRING: "v5.20"
> SNMPv2-SMI::enterprises.17095.1.3.0 =3D STRING: "Apr 2009"
> SNMPv2-SMI::enterprises.17095.2.1.1.1.0 =3D INTEGER: 0
> SNMPv2-SMI::enterprises.17095.2.1.1.1.1 =3D INTEGER: 1
> SNMPv2-SMI::enterprises.17095.2.1.1.2.0 =3D INTEGER: 0
> SNMPv2-SMI::enterprises.17095.2.1.1.2.1 =3D INTEGER: 0
> SNMPv2-SMI::enterprises.17095.2.1.1.3.0 =3D IpAddress: 0.0.0.0
> SNMPv2-SMI::enterprises.17095.2.1.1.3.1 =3D IpAddress: 0.0.0.0
> SNMPv2-SMI::enterprises.17095.2.1.1.4.0 =3D Hex-STRING: 00
> SNMPv2-SMI::enterprises.17095.2.1.1.4.1 =3D Hex-STRING: 00
> SNMPv2-SMI::enterprises.17095.3.1.0 =3D INTEGER: 0
> SNMPv2-SMI::enterprises.17095.3.2.0 =3D INTEGER: 0
> SNMPv2-SMI::enterprises.17095.3.3.0 =3D INTEGER: 0
> SNMPv2-SMI::enterprises.17095.3.4.0 =3D INTEGER: 0
> End of MIB
>
> C:\Documents and Settings\GX620>snmpget -v 1 -c public 192.168.1.155
> sysDescr.0
> SNMPv2-MIB::sysDescr.0 =3D STRING: PIC
>
> C:\Documents and Settings\GX620>snmpget -v 1 -c public 192.168.1.155
> sysName.0
> Timeout: No Response from 192.168.1.155.
>
> C:\Documents and Settings\GX620>snmpget -v 1 -c public 192.168.1.155
> sysContact.0
> SNMPv2-MIB::sysContact.0 =3D STRING: admin
>
> C:\Documents and Settings\GX620>snmpget -v 1 -c public 192.168.1.155
> sysName.0
> Timeout: No Response from 192.168.1.155.
>
> C:\Documents and Settings\GX620>snmpget -v 1 -c public 192.168.1.155
> sysLocation.0
> SNMPv2-MIB::sysLocation.0 =3D STRING: office
>
> C:\Documents and Settings\GX620>snmpget -v 1 -c public 192.168.1.155
> .1.3.6.1.2.1.1.5.0
> Timeout: No Response from 192.168.1.155.
>
> C:\Documents and Settings\GX620>snmpget -v 1 -c public 192.168.1.155
> .1.3.6.1.2.1.1.4.0
> SNMPv2-MIB::sysContact.0 =3D STRING: admin
>
> I'll dig a little further.
>
> THANKS!
>
> Harold
>
>
>   =20

I think doing a "snmpget" of the specific OID will skip SNMPGetNextIndex.

BYTE ProcessGetVar(OID_INFO* rec, BOOL bAsOID,PDU_INFO* pduDbPtr

There are some condition checks in ProcessGetVar before calling SNMPGetVar.
Does it make it into ProcessGetVar?
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.