File:           SNMPWIN.TXT
Revision:       1.0.2
Date:           May 1995
Author:         Martin Bayreuther
e-mail:         maba@hpbbm.bbn.hp.com


			----------------------
			SNMP tools for Windows
			----------------------


The story
---------

After doing some work on the SNMP DOS tools, I faced a growing demand
for Windows based SNMP applications The MS Visual C++ development
environment allows for easy porting of DOS applications into so called
QuickWin applications. The biggest advantage of this approach is the
availability of a standardized network programming environment, which
is WINSOCK. The applications can use any winsock.dll that implements
the version 1.1 WinSock specifications.

The tools
---------

Under Windows, in my opinion SNMPTEST is the most useful tool as it is
interactive and does not require entering a commandline for every run.

The syntax is as follows:
-------------------------

   SNMPTEST gateway-name community-name
 
You can specify that via the File, Run sequence from Program Manager or
File Manager. If you prefer to have an Icon, include the /? paramater,
so you will be asked for the commandline parameters.

a) gateway-name:   This can be an IP-address in the standard format
		   e.g. 15.136.38.101, which is one of our UNIX servers
		   or it can be a hostname e.g. bmdwave.bbn.hp.com.

		   However, if you use hostnames instead of IP-addresses,
		   your PC must be capable of resolving the hostname and
		   translating it into an IP-address.

b) community-name: This parameter specifies the so called community, 
		   which the gateway belongs to. The default is
		   "Public". You may think of this parameter as an
		   access password to the snmpd (SNMP deamon) running on
		   the host or gateway. This is especially useful, if the
		   host is visible to an untrusted network. Your network
		   administrator will most likely change the community-name
		   of such a gateway to a non-public value. To run the SNMP
		   tools try "public" first. If this does not work on any
		   machine, ask your network administrator, whether he has
		   changed the community-name on your hosts.
	   

SNMPTEST prompt:
----------------

The command prompt allways reads "Enter variable name:". At this prompt
you can either type a variable name or a valid command.

A blank line triggers the request.

Commands for SNMPTEST:
----------------------

all commands start with the dollar sign and are not case-sensitive.

   $q    Quit      Stop the WINSOCK session. The program is shutdown
		   after this command.

   $d    Dump      Toggle PDU dump mode on/off. If packet dump is on,
		   you will see any single PDU as it comes in or goes
		   out.
   
   $g    Get       Switch to GET request mode.
   
   $n    GetNext   Switch to GETNEXT request mode.
  
   $s    Set       Switch to SET request mode.

The output appears as it would in a DOS box.

Variable names in SNMPTEST:
---------------------------
   The variable names specify, which part of the MIB you want
   to query. To get an understanding of the MIB concept, try
   "The simple book" of Marshall T. Rose.
   The MIB is a tree of network/host management information.
   The notation of this parameter can be either the numbered
   or the aliased notation. It may be relative or absolute.
   If you are not familiar with the MIB, here are some 
   examples:

	Relative numbered:           Relative alias:

	1.1.0     translates into    system.sysDescr.0
	1.2.0     translates into    system.sysObjectID.0

	Absolute numbered:           Absolute alias:

	.1        translates into    .iso
	.1.3.6    translates into    .iso.org.dod

	The relative object-id is located under  
	.iso(1).org(3).dod(6).internet(1).mgmt(2).mib(1)


Tested configurations:
----------------------
Windows 3.1 MicroSoft winsock.dll version 1.1
Windows NT 3.5  MicroSoft WinNT 16-bit winsock.dll version 1.1