[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

2824.0. ""Managing non-snmp entities"" by NEWPRT::MOREH_JA (fork() a child,end up with a zombie) Wed Apr 22 1992 16:23

    Hi Folks,
    	A custmer has a system with DECmcc director talking to another
    system with an SNMP agent(managed object).  The director can clearly
    ask the managed object about its MIB variables.  Is there any way that the
    managed object can pass non-MIB data to the director.  For example, if
    a director wants to see the status of a printer attached to the managed
    object, how would it do it.  Is an extensible SNMP agent the answer?
    
    Thanks
    Jahan, Los Angeles
T.RTitleUserPersonal
Name
DateLines
2824.1"SNMP access modules"NEWPRT::MOREH_JAfork() a child,end up with a zombieWed Apr 22 1992 18:348
    Having thought about this, I think MIB extenstions are in fact the
    answer.  Now the next question is this: if an MCC director talks to an
    SNMP managed object and gathers standard MIB and extension MIB data,
    can the director display all of this data as if it were standard MIB. 
    Namely, do the SNMP access modules support additions to standard MIB's?
    
    Thanks
    Jahan
2824.2If you can describe it w/RFC1212 you're in.TOOK::MCPHERSONSave a tree: kill an ISO working group.Wed Apr 22 1992 19:0720
>    Having thought about this, I think MIB extenstions are in fact the
>    answer.  Now the next question is this: if an MCC director talks to an
>    SNMP managed object and gathers standard MIB and extension MIB data,
>    can the director display all of this data as if it were standard MIB. 
>    Namely, do the SNMP access modules support additions to standard MIB's?

    MIB extensions must be describeed a priori to the DECmcc director
    (accomplisehd via the MIB Translator utility).   This allows the DECmcc
    system to appropriately encode/decode the SNMP PDUs using the services
    of the SNMP AM.   In that respect, the SNMP AM is generic and there is
    only 1 SNMP AM on the DECmcc system for many SNMP entities and their
    private extensions.

    This means that the problem is not with the DECmcc SNMP AM.  Rather the
    issues are:
    	1) that the Agent on the managed object is able to encode/decode
    	   the 'special' extensions
    	2) that the Agent developers provide an RFC1212-compliant
    	   MIB definition of their extensions for teh DECmcc MIB
     	   Translator.