| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
We are in the final stages of a large Program that requires our ULTRIX
based server implement an SNMP host agent (per RFC 1157) that will
respond to the SNMP get commands for the MIB II variable listed in RFC
1158 that are appropriate for host class network devices.
We are required to transmit and receive these MIB entities from the network
using ASN.1 techniques described in the Structure and Identification of
Management Information for TCP/IP-based internet, RFC 1155.
We are also asked to tuppor the optional authentication and
authorization schemes associated with "community name" techniques
described in RFC 1157.
The server is a DECsystem 5000 Model 240 with Ultrix 4.2.
Any assistance in describing how we can address these issues would be
appreciated.
Mitch Hall
Harris Account Manager
DTN: 360-7415
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2004.1 | common agent on Ultrix | TOOK::MATTHEWS | Thu Jan 02 1992 11:05 | 13 | |
You have several options. The most preferable is to use the common
agent for Ultrix (please contact DECWET::NEWKERK or DECWET::FRIES
for details). I believe you will find that it handles MIB II for
you and reduces your effort to providing management object routines
for MIB extensions only. If you are in an OS environment or are
using a non DEC TCP implementation, you can get the SNMP protocol
stack from the common agent people and develop your own agent.
I strongly suspect that the common agent on Ultrix is unknown to you.
It is definitely the preferred route to go.
wally
| |||||