You can think about snmp as a tree.
snmpwalk displays recursivly all the OIDS beneath a given node.
OIDS are structured similiar to IP-numbers (which can be also represented by a tree) by a string consisting of dots and numbers.
There are informations in this tree which are in common on many different devices (such as printer, router, switches, hosts, raid-arrays or uninteruptible power supplies). They are stored in a standard subtree. An example for this is the system subtree which contains information about sys-location or sys-contact.
Other information is more vendor specific. It is stored in the enterprise subtree and enterprises may reserve there an numeric value for their own vendor-specific information.
The clue point in using snmp is to find out which OIDS you want. Therefore you could use snmpwalk and try to guess the meaning of specific OIDS. This is easy if you want to retrieve the information which is displayed on the LCD of your networked printer but very difficult if you want inoctets of some network device on a switch. Therefore you might need a MIB (Message Information Base) which is a file containing alphanumerical translations of the numerical OIDS (like DNS does for IP-Numbers). In addition a MIB-file contains also explanations on OIDS. Those MIB-Files are usually provided by the manufacturer of your device or (concerning the standard tree) by the vendor of your snmp software (By vendor I mean the Open Source community, do not use buggy and expensive software here)
Using snmpwalk to retrieve information isn't a good idea. You get lots of bullshit you do not want because the SNMP tree is a very large thing (you will also produce a lot of network traffic).
Usually you want to get specific information on each interface of your cisco Therefore you might want to get system.iftable with snmptable (I am sorry, I am at home without access to our high security network to make sure I am giving you the correct OID)
If you explain the complete problem I could probably give you some more assistance.

Regards...

In reply to Re: snmpwalk using net::snmp by very empty
in thread snmpwalk using net::snmp by c

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.