[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

2421.0. "What are the sources for MIB information ?" by EEMELI::VALTONEN (Ken tiet�is tulevaisuuden) Wed Feb 26 1992 05:22

    Is a list of "supported" MIBs available from a source or another ?
    
    (supported = formally supported by DEC or vendor or found working
    with a specific DEC/vendor software version)
    
    Thanks, 	Olli
T.RTitleUserPersonal
Name
DateLines
2421.1Separate note or whole conference for MIB lists?EEMELI::VALTONENKen tiet�is tulevaisuudenFri Feb 28 1992 06:406
    I would think this as important as AM availability lists (note 3.*).
    
    Finding any informations with title search from MCC is just waste of
    time - note file have grown too huge already!
    
    Olli
2421.2MCDOUG::MCPHERSONSave a tree: kill an ISO working group.Fri Feb 28 1992 09:0465
>    Is a list of "supported" MIBs available from a source or another ?
>    
>    (supported = formally supported by DEC or vendor or found working
>    with a specific DEC/vendor software version)
>    

    Using your definition of "supported", the only MIBs that are supprted
    are those written by DEC.   Those that either the SNMP AM developers or
    the SVP group have been able to compile & check with the SNMP MTU will
    be included on the SNMP AM kit.

    I very much understand the desire to have a repository of MIBs that
    also includes information about the vendor devices|versions|agents
    supported.    It'd be great if we were able to give everybody the 'warm
    and fuzzy' feeling that Digital knows everything that every SNMP vendor
    is doing  and we have the latest SNMP agent support for them... 
     
    Unfortunately, there are Sagans and Sagans of companies out there who
    do agent code changes/release  as often as some people change
    underwear.   Changes in agents (usually) mean changes in MIBs.  Of
    course, these vendors come running to DEC to let nice old DEC know that
    they've changed their MIBs...  NOT!!

    Putting together a list & repository is probably about one
    person-month's worth of work.   *Maintaining*   said repsitory (of
    "supported" MIBs/AMs) is AT LEAST a full-time time job for one engineer
    and likely some sort of admin ass't.

>    
>    I would think this as important as AM availability lists (note 3.*).
>    

    Maintaining a list of MMs may be _slightly_ easier, due simply to the
    fact that there are fewer of them than MIBs and most have been written
    within DEC.    However, there is STILL the problem of certifying the
    *correctnes* of the MMs (i.e. Do they have an MRM?   Are all their
    codes registered with the DSSR?)   These things are IMPORTANT.  You can
    shoot  yourself inf the foot (and probably not know it immediately) if
    you have people using codes willy-nilly in their MMs. 

    Managing a MM repository if probably ANOTHER full-time engineer's job.

    Having said all these negative-sounding things, maybe I can put a
    positive spin on it...    It is possible to use something along the
    lines of the TOOLSHED concept for MMs or MIBs.   I.e. the people
    submitting 'tools' (i.e. MIBs or AMs) are responsible for maintaining
    them and the TOOLSHED providers just provide a 'clearinghouse' service. 
    Note that this says nothing about DEC supporting all the tools; just a
    clearinghouse. Caveat Emptor.

    The tools to build this service exist now, and are reasonably
    well-understood.    However, as I said earlier: someone will STILL need
    to come up with the resources ($$/systems/engineers) to provide this
    clearinghouse service.   As far as I know, this is not in the cards for
    either the Frameworks or the Management Applications group...

>    Finding any informations with title search from MCC is just waste of
>    time - note file have grown too huge already!

    This is your opinion and you are certainly entitled to it.  I disagree. 
    Some familiarity with NOTES features, a bit of patience and a dash of
    cleverness will go a long way toward making information searches more
    fruitful.  Oh yeah: using descriptive titles help a lot, too.

    /doug
2421.3You are right with effort - who pays for it ?EEMELI::VALTONENKen tiet�is tulevaisuudenFri Feb 28 1992 10:5452
    .re: .2
    
>    Using your definition of "supported", the only MIBs that are supprted
>    are those written by DEC.   Those that either the SNMP AM developers or
>    the SVP group have been able to compile & check with the SNMP MTU will
>    be included on the SNMP AM kit.

    Perhaps I was too tight in defining supported. Even list of existing
    MIBs with some status indicators (who has succesfully used the MIB
    for example) is enough. I understand also the troubles with 
    incompatible versions...

>    Putting together a list & repository is probably about one
>    person-month's worth of work.   *Maintaining*   said repsitory (of
>    "supported" MIBs/AMs) is AT LEAST a full-time time job for one engineer
>    and likely some sort of admin ass't.

    I'm probably spending almost two-three days to answer all MIB related
    questions from this customer. If similar RFIs are received in dozen's
    or hundreds this would have some business reasons...

>    Having said all these negative-sounding things, maybe I can put a
>    positive spin on it...    It is possible to use something along the
>    lines of the TOOLSHED concept for MMs or MIBs.   I.e. the people
>    submitting 'tools' (i.e. MIBs or AMs) are responsible for maintaining
>    them and the TOOLSHED providers just provide a 'clearinghouse' service. 
>    Note that this says nothing about DEC supporting all the tools; just a
>    clearinghouse. Caveat Emptor.

>    The tools to build this service exist now, and are reasonably
>    well-understood.    However, as I said earlier: someone will STILL need
>    to come up with the resources ($$/systems/engineers) to provide this
>    clearinghouse service.   As far as I know, this is not in the cards for
>    either the Frameworks or the Management Applications group...

    How about Network Marketing looking at this ?
    
    About slowness of MCC notes access:
    
>    This is your opinion and you are certainly entitled to it.  I disagree. 
>    Some familiarity with NOTES features, a bit of patience and a dash of
>    cleverness will go a long way toward making information searches more
>    fruitful.  Oh yeah: using descriptive titles help a lot, too.
    
    Perhaps I'm too negative because of the long distance and low speed
    lines - I'm just several 64 kbps hops away from all 2 mbps links to the
    US. I've to do my notes title searches in batch mode and even
    then it may take hours per one run. Somehow NOTED is lot worse than
    systems in Merrimack for example... 
    
    Olli
2421.4MIB source ?EEMELI::VALTONENKen tiet�is tulevaisuudenThu Mar 05 1992 06:316
    Back to rephrased question:
    
    where I can find the MIBs, somewhere in Easynet or Internet ?
    I mean also so called MIB drafts (FDDI, Frame Relay, RMON?)...
    
    Thanks,	Olli                                              
2421.5See 2126.10EEMELI::VALTONENKen tiet�is tulevaisuudenTue Mar 10 1992 07:081
    2126.* contains more info on MIBs in Easynet.