[comp.protocols.tcp-ip] SGMP

espo@bpa.BELL-ATL.COM (Bob Esposito) (11/04/87)

	Does anyone know where I can get info concerning SGMP (Simple
	Gateway Mgmt. Protocol)?  Anything would be helpful.

	Thanks in Advance,


-- 
===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===
 Bob Esposito,  Bell of Pennsylvania - espo@bpa.bell-atl.com - (215) 466-6831
===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===

yeongw@NISC.NYSER.NET.UUCP (11/08/87)

>	Does anyone know where I can get info concerning SGMP (Simple
>	Gateway Mgmt. Protocol)?  Anything would be helpful.
The RFC-to-be can be obtained by anonymous ftp from nisc.nyser.net
128.213.1.13 in pub/simple-mon.rfc. There is an sgmp mailing list,
simple-umon@nisc.nyser.net for sgmp developers.

Wengyik Yeong
yeongw@nisc.nyser.net
..!rutgers!nysernic!yeongw

postel@VENERA.ISI.EDU (11/09/87)

SGMP = Simple Gateway Mgmt Protocol = RFC-1028

schoff@NISC.NYSER.NET.UUCP (11/13/87)

    
    	Does anyone know where I can get info concerning SGMP (Simple
    	Gateway Mgmt. Protocol)?  Anything would be helpful.

    	Thanks in Advance,


    -- 
    ===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===
   -===
     Bob Esposito,  Bell of Pennsylvania - espo@bpa.bell-atl.com - (215) 466-68
   31
    ===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===-===
   -===

why don't you call the NYSERNet NISC at 518-283-8860 and ask
for either Mark Fedor or myself, (we're two of the authors of the RFC).

Marty

satz@CLASH.CISCO.COM (08/23/88)

The RPI SGMP tools are available for anonymous ftp from clash.cisco.com
(192.31.7.24). The file you want is sgmp.tar.Z. It is a compressed tar file
containing the most recent working sources with bug fixes made at cisco and
Rutgers. Please note that this software is being provided as is without any
assertion as to its quality, usefulness or correctness. This code will make
core files for you if you push it too hard. However it is quite useful as
an introduction to ASN.1 and SGMP if you are persistant enough. Any bug
reports sent to me will be politely ignored. However, if you fix a bug,
please send it back for inclusion in the distribution.

Greg Satz
cisco Systems

PS. requests for sending this through the mail cannot be honoured so please
do not ask.

schoff@BEAR-MOUNTAIN.NYSER.NET ("Marty Schoffstall") (08/24/88)

    The usual recommendation for SGMP is to talk to the folks at Nysernet.
    An initial implementation was done at RPI.  It's more or less public
    (not public domain, but freely distributable).  Nysernet cleaned it up
    a good deal, and is selling it for a minimal cost (not enough to make
    money -- just enough to cause everybody maximal administrative
    overhead).

Actually we rewrote it from scratch and saved the "look and feel" of
the applications.  Additionally we added about 10 more applications
including a BSD/UNIX agent/server.  We followed the CMU model
for Tektronix/VMS/TCP administratively, becaue we heard it worked,
time will tell though.  However we have distributed a LOT of university/
non-profit licenses (source) so far, and we release a new version
about every quarter so its not an orphan.  These are important due to the
growing network management needs in terms of more complex and useful tools.

    (By the way, I don't know who to contact at these Nysernet or
    Berkeley, so please don't ask.  At cisco, you might contact
    customer-service@mathom.cisco.com.)

snmplisc@nisc.nyser.net does work for people who are interested.

Marty

yeongw@C.NYSER.NET (08/24/88)

For information on NYSERNet's SGMP distribution, please contact

		Edward Nadeau,
		NYSERNet Inc.,
		165 Jordan Road,
		Troy, NY 12180
		nadeaut@nisc.nyser.net
		(518) 283-8860

Our SNMP (IDEA0011-02) distribution is not available for public distribution
yet.


Wengyik

auerbach@CSL.SRI.COM (Karl Auerbach) (08/27/88)

My company, Epilogue Technology, is developing a set of tools for SNMP
(the sucessor to SGMP).

These include a complete SNMP agent which is both highly portable
and small.  The same tools could support an SNMP management station.

Target date for completion is September 15.

These tools have been updated to conform to RFC1065/1066/1067.

For further information, please contact Epilogue Technology at 415/594-1141.

			--karl--

kzm@TWG.COM (Keith McCloghrie) (08/27/88)

There is some question about how long SGMP will be around.  It is
being replaced by SNMP, the specification for which has just been
published as RFC 1067.  Yesterday's official annoucement (from Jon 
Postel/Joyce Reynolds) stated :

  "This memo specifies a draft standard for the Internet community. 
  TCP/IP implementations in the Internet which are network manageable 
  are expected to adopt and implement this specification."

The concept of a "draft" standard is new to the Internet community,
but the latter sentence leaves no room for doubt about what conformant
TCP/IP vendors must do.

Note that whereas SGMP (as its name implies) was aimed at managing 
IP gateways, SNMP uses the set of variables (called the MIB - the
Management Information Base) specified by RFC-1065/1066.  This set
not only includes just about all the gateway-specific and common 
variables of SGMP, but also adds an initial set of host-specific 
variables (e.g. TCP and UDP objects).  As a result, many more 
vendors are already implementing SNMP for gateways and for hosts, 
than ever implemented SGMP.

Keith.

aglew%vger@XENURUS.GOULD.COM (Andy-Krazy-Glew) (08/28/88)

..> Software for SGMP monitoring

My wife wrote some stuff to collect statistics from SGMP gateways
working for the University of Illinois' CSO. I'm forwarding your note
to her, and you can send her email at irvan@uxc.cso.uiuc.edu.


Andy "Krazy" Glew. Gould CSD-Urbana.    1101 E. University, Urbana, IL 61801   
    aglew@gould.com     	- preferred, if you have nameserver
    aglew@gswd-vms.gould.com    - if you don't
    aglew@gswd-vms.arpa 	- if you use DoD hosttable
    aglew%mycroft@gswd-vms.arpa - domains are supposed to make things easier?
   
My opinions are my own, and are not the opinions of my employer, or any
other organisation. I indicate my company only so that the reader may
account for any possible bias I may have towards our products.