Re: No hrSWRunPath in HOST-RESOURCES-MIB

Dave Shield <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
2009/3/27 Mike Ayers <[email protected]>:
>        Are you sure they're not deliberately eliding the data for security reasons?

Even if they are blocking individual instances within the hrSWRunPath
(which frankly, I doubt), that shouldn't break a walk of this object.
Remember that an snmpget on selected individual instances (e.g.
4049 - cron) *does* work.   But snmpget on process 2 (kthreadd)
returns noSuchInstance.

It feels suspiciously that this missing instance (whether deliberate or
accidental) is causing the GETNEXT processing to move on to the next
MIB object, rather than skipping this particular instance and returning
the next.

Kamal,
   can you please confirm whether
      snmpgetnext    ...  hrSWRunPath.4048
                 returns /usr/bin/cron  (as expected)

Also, what does
      snmpgetnext  .... hrSWRunPath.2
             return?

More generally, is the missing instance #2 an isolated example,
one of a small handful of similar cases, or the norm?

The simplest approach is probably to walk one of the other columns
in this table, and catch the output in a text file.   Then convert this
file into a shell script, containing a sequence of "snmpget" commands
on the specific hrSWRunPath instances.
   OK - some of those will be transient processes, that will no longer
be around when you run the snmpget script.  But it should be reasonably
clear which hrSWRunPath instances ought to be present but are not.

What sort of patterns do you see?

Dave

------------------------------------------------------------------------------
_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.