[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

3211.0. "SNMP source code generator" by PRSSUD::CARRAYROU () Fri Jun 19 1992 07:59

    Two different customers  ( OEM DEC ) want developp SNMP Agents 
    
    their are looking for tools 
                             tools
    from: ASN1 MIB description   --------> to: C source code agent
    
    
    the customers know "ISODE" ( product from UK )
    
    the DEC NETSYSTEM service offers a lot of SNMP agents 
    What tools were used to develop these agents
    
    does DEC developp or use the kind of tools
    
    Thanks
    Didier
    
T.RTitleUserPersonal
Name
DateLines
3211.1Common Agent MOM GeneratorTOOK::DENSMOREDirty deeds done dirt cheapMon Jun 22 1992 11:3550
    re .0:
    
    This discussion really belongs in the Common Agent conference but I
    provide a brief answer here as well.  The Common Agent conference is on
    DECWET::DOCD$:[NOTES$LIBRARY]COMMON-AGENT.
    
    There is a tool for generating managed object modules (MOMs) for the
    Common Agent.  It will take a MIB II description and generate most of
    the C code needed for the agent.  The developer will only have to add code
    for specific access to the object (eg; perform a set on the actual
    object using information passed from a manager through the Common Agent
    into a standard C structure.
    
    The tool (MOM Generator) is currently working on VMS, using MSL and the
    MCC Dictionary for generating object specific code.  I am porting the
    generator to Ultrix and adding some SNMP specifics like get-next and
    such.  The code is shared so both versions will be able to produce
    DNA/OSI and SNMP type MOMs.
    
    The Ultrix version will work as follows:
    
    	1. Write a MIB II description of your object.
    	2. Run the description through the MIB-MSL Translator (it will be
    	   supplied as part of the developer's kit).
    	3. Compile the resulting MS file into the MIR (the Common Agent's
    	   dictionary.)  NOTE: this is the only way MSL is used and the
    	   developer need not learn the language to use the Generator.
    	4. Create a simple info (parameter) file for the MOM Generator
    	   which lists the objects (class, parent and a prefix string) and
    	   such things as developer name, company (for copyright info),
    	   etc.
    	5. Run the MOM Generator ( % momgen -i infofilename ).  You will
    	   then have all the modules you need to start your development. 
    	   The amount of additional work will depend upon the complexity of
    	   your object.  The kinds of things you will need to do are:
    
    		- perform any object specific initialization required when
    		  the MOM is started
    		- perform retrieval of data from the object (eg; kernel
    		  calls)
    		- perform modifications of data in the object
    
    	   The generated code has markers to tell you where to make your
    	   modifications.  You are pretty much insulated from the Common
    	   Agent's API so the work requires mostly a knowledge of your
    	   object and C.
    
    Documentation is still under development but should be available soon.
    
    						Mike