[nv-l] Teach me to fish

Just before I increased the logging, for grins I added a "community public" and the madness stopped! This is a band-aid but not the solution. I can now dig without going insane.

I bumped up with logging and came out with some pretty good stuff (see below). I don't have any MIBs loaded to go digging deeper than .1.3.6.1.4.1.2.2 (ibmResearch)(??) so I'll go hunting for MIBs to see what could be having a problem.

Thanks so much for everyone help - as always this list is GREAT. Thanks Paul!

Steve

=== snmp.log snip =====================================
08/23/04 09:23:07 TRACE:
{
   version 0,
   community "public",
   data {
      get-request {
         request-id 1,
         error-status 0,
         error-index 0,
         variable-bindings {
            VarBind {
               name 1.3.6.1.4.1.2.2.1.1.1.0,
               value {
                  empty NULL
               }
            }
         }
      }
   }
}
08/23/04 09:23:07 EXCEPTIONS: authentication error: invalid community name: public

-----Original Message-----
From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT com]On Behalf Of Stamper, Steve
Sent: Monday, August 23, 2004 9:21 AM
To: 'nv-l AT lists.us.ibm DOT com'
Subject: RE: [nv-l] Teach me to fish

Good idea - this one I'm going to chase. I'll let everyone know what I find.

Thanks for the thought.
Steve

-----Original Message-----
From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT com]On
Behalf Of Paul
Sent: Monday, August 23, 2004 9:09 AM
To: nv-l AT lists.us.ibm DOT com
Subject: Re: [nv-l] Teach me to fish

Steve,
Increase your loglevel to 3(debug, I think) and increase the size of
the file, both in the snmpd.conf file. Then restart snmp and watch
the log. I should think you should get some good information from
that.
Paul

<snip>

[nv-l] Teach me to fish - Step 2