Rather than guessing, look at it from the bottom up.
If the Linux box has a head on it load Wireshark and its GUI there.
If not then capture the session with tcpdump and move the file to a machine=
 with the Wireshark GUI.



-----Original Message-----
>From: TPCpiclist@mklab.ph.rhul.ac.uk
>Sent: Dec 3, 2014 11:17 AM
>To: piclist@mit.edu
>Cc: tpcpiclist@mklab.ph.rhul.ac.uk
>Subject: [PIC] Problem using Unix net-snmp tools with snmpv3_nvm_mpfs demo=
 on	PIC32 ESK board (part no. DM320004) [reposted with subject prefix]
>
>Dear All,
>        I am attempting to create a device running an SNMP agent.  As a=20
>start I have built the snmpv3_nvm_mpfs demo app under MPLAB Harmony and=20
>can access its web and SNMP interfaces.  With the device connected to a=20
>dual boot PC, under Windows 7 I can properly interrogate the SNMP agent=20
>using the iReasoning browser recommenced by Microchip in the MPLAB Harmony=
=20
>documentation.  In particular I can read the push-button status and turn=20
>the board's LEDs on and off.
>
>Under Linux, using the snmpwalk, snmpget & snmpset command line tools=20
>there are problems.  Snmpwalk returns only a small fraction of the agent's=
=20
>name-space, eg.
>
>root@RM:/home/tom# snmpwalk -On -c public -v 1 mechpboard_e
>.1.3.6.1.2.1.1.1.0 =3D STRING: Microchip Harmony
>.1.3.6.1.2.1.1.2.0 =3D OID: .1.3.6.1.4.1.17095.1
>.1.3.6.1.2.1.1.3.0 =3D Timeticks: (60130) 0:10:01.30
>.1.3.6.1.2.1.1.4.0 =3D STRING: admin
>.1.3.6.1.2.1.1.5.0 =3D STRING: Microchip
>.1.3.6.1.2.1.1.6.0 =3D STRING: office
>.1.3.6.1.2.1.1.7.0 =3D INTEGER: 7
>
>Specifying the OID reported by the iReasoning browser running under=20
>Windows for one of the board's LEDs with snmpset; or a push-button using=20
>snmpget always fails.
>
>I also tried the net-snmp toolkit's tkmib browser which loops with an=20
>error and again does not find the agent's LED or push-button hardware.
>
>I have copied the mchip.mib and snmp.mib MIB files into (at different=20
>times) both /usr/share/snmp/mibs/ and ~/.snmp/mibs but without effect.
>
>Similarly specifying SNMP v1 or v2c on the command line makes no=20
>difference.
>
>I really don't want to be tied to Windows for development and more=20
>importantly I need the device to work with the Unix or any other SNMP
>client.  Can anyone explain what might be wrong or supply working examples=
=20
>of net-snmp commands to access the board's push-button/LEDs?  Please let=20
>me know if I've omitted anything pertinent.
>
>Many thanks
>Tom Crane
>
>
>Linux system details:
> Distro: Slackware current
> Architecture: i686
> Kernel: 3.14.12
> IDE: MPLAB IDE v2.20
> MPLAB Harmony framework: v1.00
> PIC Compiler: XC32 (v1.33) [free download]
>
>Apologies for the earlier subject prefix-less post.
>--=20
>Tom Crane, Dept. Physics, Royal Holloway, University of London, Egham Hill=
,
>Egham, Surrey, TW20 0EX, England.=20
>Email:  T.Crane@rhul.ac.uk
>Fax:    +44 (0) 1784 472794
>--=20
>http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
>View/change your membership options at
>http://mailman.mit.edu/mailman/listinfo/piclist



--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.