Conference azur::mcc

3439.0. "Internal MIB Walker" by FOUR62::LICAUSE (Al Licause (338-5661)) Mon Jul 27 1992 16:42

In an effort to pass along information that may not have gotten to the right
groups, I found this note in the SNMP notes files.  

I'm not all that familiar with SNMP, but this sounds like something that would
be useful to DECmcc.

It is my understanding that one of the competing network management products
has something similar.

Would this by any chance help with those nasty new  MIBDEF's that don't seem to
compile correctly?

Al
---------------------------------------------------------------------------------






              <<< MKNME::MKNME_USER:[NOTES$LIBRARY]SNMP.NOTE;2 >>>
                                   -< SNMP >-
================================================================================
Note 87.0     whaddya_know: a simple mib walker for ascii terminals   No replies
NOHOST::LEVIN "Bryan, LENaC Engineering, MLO3-3/U39"  58 lines  27-JUL-1992 09:11
--------------------------------------------------------------------------------
I put together a quickie utility that walks any agent, and display the returned
var names, instances, and values, and types, in printable ASCIZ format.  The
output is suitable for piping and grep-ing.

It needs a RISC station (binary was cut for a DS5000-series, but 3100 should
work as well.)  Not for VAXes, and certainly NOT for VMS ;-)

It reverse translates returned OIDs to symbolic names, whenever possible. 
Else, it prints the OID 'pure'.

It currently does not understand enum types (up=1, down=2, etc).  It also does
not know the 'egp' group of MIB-2 (everything else in MIB-2 is there, including
the newly re-rooted CHAR, RS232, and BRIDGE).  It obviously knows about the
DECagent 90 MIB, as well.


There are two files: 'whaddya_know' and 'whaddya_know.mib'

The first is the executable, and the second is an ASCIZ MIB database (cat it
and you'll see.)  This utility was designed with the new SNMP 'callable
interface' from our friends at ASDS (and is based on Jeff Case's latest
non-secure SNMP code).  Note that it does _NOT_ require ANY knowledge of MSU
(not even the $NMS_DIR env variable).  To run, copy these from my DECnet
account, and place in any directory, as long as both files are in the same 
dir.  

For the command line, whaddya_know does not accept IP symbolic names, just IP
addresses in dotted format.  It assumes 'public' as the access community. 
Timeout and retries are defaulted, but can be overridden if specified.  CLI
parms are:

% whaddya_know <ip_address> <community> <timeout> <retries>


For example, to walk our DECagent 90, you can try:

% whaddya_know 16.123.96.51 public 5 1


I hope to enhance this utility later on, but right now, it suits my need, and
hopefully, is useful to others.  For feedback, mail to NOHOST::LEVIN.


To copy using DECnet-Ultrix:

    % mkdir know
    % cd know
    % dcp -v -i snmpd::'whaddya_know*' .


(NOTE!  SNMPD:: has recently changed addresses.  It used to be known as NOC1::
        with a DECnet address of 25.760.  Please use whatever name is 
        associated with 25.760 when copying...)


cheers,

.bl

What about oids?  adding the oid to the output would help a bunch
for those of us who need to peek at it.  MCC_TCPIP_MQ will display the oid
and the value, but not the other stuff.  makes it a pain to merge the two.

thanks.