| 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 |
<<< MKNME$DUA1:[NOTES$LIBRARY]SNMP.NOTE;1 >>>
-< SNMP >-
================================================================================
Note 25.0 SNMP Access module, MIB extensions 1 reply
CCIIS1::ROGGEBAND "_ �hili��e _" 35 lines 4-SEP-1990 12:07
--------------------------------------------------------------------------------
Hello,
I work in the french technology ACT, where I spend 120% of time on EMA, DECmcc
and all things that revolve around network management. I have had some
questions from customers, concerning the management of TCP/IP networks, to
which I hope someone will be able to provide an answer. I am afraid my
knowledge of SNMP is not what I would like it to be, so I hope these
questions make sense.
1) Does the DECmcc SNMP access module support MIB extensions ? If we wanted to
support extensions, would that mean modifying the definition of SNMP Child
objects in the dictionnary ? Or would it be necessary to modify the AM as
well - I am thinking mainly of the dispatch tables - (in other words : no
go, DEC does not supply sources !) ?
2) In the MCC notesfile, it is mentionned that CMIP encoding routines
interface can be obtained internally for developments. If we have to develop
a specific AM for a customer to manage entities which "talk" SNMP but for
which we wish to support MIB extensions, would SNMP encoding routines be
available as a library ?
3) Finally, if we have to develop something from scratch, can you give me
some indication of the effort necessary (the mythical man-month !) to
develop an SNMP Access module ? This information will also be useful for one
context where we will have to manage some systems which support TCP/IP but
not SNMP (they have a specific protocol instead). An alternative in this
latter case may be to develop an SNMP agent on the said system... but I
don't like the idea of developping on non-DEC systems.
P.S. Is this the right place for these questions or should I cross-post
them in TOOK::MCC ?
Thanks, cordialement,
Philippe.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 305.1 | MKNME::DANIELE | Tue Sep 04 1990 14:37 | 60 | ||
<<< MKNME$DUA1:[NOTES$LIBRARY]SNMP.NOTE;1 >>>
-< SNMP >-
================================================================================
Note 25.1 SNMP Access module, MIB extensions 1 of 1
MKNME::DANIELE 54 lines 4-SEP-1990 13:31
--------------------------------------------------------------------------------
Hello Phillipe,
The general questions are certainly applicable to this conference.
Some of the DECmcc specifics are less so, but other readers may
ignore it. I'll cross-post in TOOK::MCC.
> 1) Does the DECmcc SNMP access module support MIB extensions ?
V1.0 does not support extensions.
> If we wanted to support extensions, would that mean modifying the
> definition of SNMP Child objects in the dictionnary ?
Probably adding new child entities, perhaps even global. But not
modifying existing ones, since they map to MIB I, which still exists.
> Or would it be necessary to modify the AM as well - I am thinking mainly of
> the dispatch tables - (in other words : no go, DEC does not supply sources
Yes, this too. MSL provides no way to specify object identifiers, so
at the very least, this info has to be updated within the AM.
It's just a nit, but actually the dispatch tables would not have to be
modified, there is only 1 entry point per directive.
> 2) In the MCC notesfile, it is mentionned that CMIP encoding routines
> interface can be obtained internally for developments. If we have to develop
> a specific AM for a customer to manage entities which "talk" SNMP but for
> which we wish to support MIB extensions, would SNMP encoding routines be
> available as a library ?
Version 1.1 of the access module will support extensions, I can't say
yet exactly to what extent. Current thinking is for DECmcc engineering
to handle the major players ( Wellfleet, cisco, Proteon, SynOptics,
etc. ) specifically, and leave hooks in the AM for further mods.
I don't believe an SNMP library will be required, the modifications
required will be to the mcc dictionary/parse tables, and to the
AM's table of known SNMP objects.
> 3) Finally, if we have to develop something from scratch, can you give me
> some indication of the effort necessary (the mythical man-month !) to
> develop an SNMP Access module ?
If we do it right, about a week. Assuming you know everything about
the managed system. That is, you have MSL for it.
> An alternative in this
> latter case may be to develop an SNMP agent on the said system... but I
> don't like the idea of developping on non-DEC systems.
Well, there is agent code floating about somewhere. See notes 10 & 16.
Regards,
Mike
| |||||
| 305.2 | Select | MKNME::DANIELE | Tue Sep 04 1990 14:42 | 1 | |
Hit keypad 7 to add the snmp conference. | |||||