Re: communicate with ME102

On Thursday 05 April 2007 10:53, Dave Shield wrote:
> On 04/04/07, Michael Renner <[email protected]> wrote:
> > > What about just fetching sysDescr.0?
> >
> > well, I got an answer, but no value:
> > snmpget -v1 -c public 192.168.5.11 sysDescr.0
> > Error in packet
> > Reason: (noSuchName) There is no such variable name in this MIB.
> > Failed object: SNMPv2-MIB::sysDescr.0
>
> That's unusual, but sort-of-reasonable.
> If the box doesn't implement this particular MIB object, then
> that would be the correct response.

I was told to use the 'private' MIB, but how can this be done? I found a file 
with these definitons: At76c510A1.mib

sysCtrlGRP OBJECT IDENTIFIER ::= {atmelSys 1}

sysDescr OBJECT-TYPE
    SYNTAX  DisplayString (SIZE (0..255))
    ACCESS  read-only
    STATUS  mandatory
       DESCRIPTION
         "A textual description of the entity.  This value
          should include the full name and version
          identification of the system's hardware type,
          software operating-system, and networking
          software.  It is mandatory that this only contain
          printable ASCII characters."
        ::= { sysCtrlGRP 1 }

.....

Now I'm looking for a chance to tell snmpwalk to use this file with the 
private MIB instead of the other. But I did not found a switch to configure 
an other source for the definiton?

Greetings


> > > snmpget -c public -v2c 192.168.5.11 1.3.6.1.2.1.1.1.0
> >
> > I get a timeout. This device is some years old, maybe 'V 1' only.
>
> Quite possible.
>
> > OK, it seems to me, that the '-d' switch makes the same output
> > like tcpdump does.
>
> Basically, yes.
> tcpdump shows what is actually going over the network.
> The -d option shows what the SNMP application is sending
> and/or receiving.   These ought to be the same (unless
> something *very* strange is happening!)
>
> > snmpget -v1 -d -c public 192.168.5.11 sysDescr.0
> > Sending 43 bytes to UDP: [192.168.5.11]:161
>
>    [snip]
>
> > Received 43 bytes from UDP: [192.168.5.11]:161
>
>    [snip]
>
> > Error in packet.... (noSuchName)
>
> That's normal.
>
> > cassiopeia:~# snmpwalk -v1 -d -c public 192.168.5.11
> >
> > Sending 40 bytes to UDP: [192.168.5.11]:161
>
>     [snip]
>
> > Resending 40 bytes to UDP: [192.168.5.11]:161
>
>     [snip]
>
> That's not.
> The agent ought to to return *something* - even if it's
> just another 'noSuchName' error.
>
>
> Can you try running tcpdump while you issue the 'ap-mrtg'
> command, and see exactly what this is sending?
> If you issue the exact same "snmpget" request, this
> should return the information you require, even if
> snmpwalk et al don't.
>
> Dave

-- 
|Michael Renner      E-mail: [email protected]  |
|D-81541 Munich      Germany        ICQ: #112280325 |
|Germany             Don't drink as root!      ESC:wq

-------------------------------------------------------------------------
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