Conference azur::mcc

5879.0. "DecHub90 mib & DecHu900 mib problems" by EVTOC2::MCC_EASYNET () Thu Feb 24 1994 09:03

    
    
    Hye,
    
    
    I would like to get some details about the TCP/IP Translator Utility
    because i don't understand why the conversion of the new DecHub90 
    private mib ( Updated: January 20, 1994 17:00 EST ) in msl file has
    failed during the Phase 1.
    
    In fact, an error occurred while running MIB translator :
    
       Variable charPortIndex in trap defn. srvrPortStatusChange not
    previously defined
       An error occured while running the MIB translator.
       Check file DH90_MIB.LIS,
         if it exists, for any further information.
       Files DH90_MIB...
    
    The problem is identical for the following variables in the same mib :
    
            - charPortOperStatus (Character Mib like charPortIndex)
            - ifIndex (Mib II)
            - ifOperStatus (Mib II)
    
    
    So, i ask me if the Mib translator can import of mib objects from
    mib II (or form other mibs like Character MIB...)
    
    Moreover, i found in the HUGHES_GENR_MIBDEF.TXT file (but i don't know 
    if it is good) the following text :
    
    crcError TRAP-TYPE
            ENTERPRISE hls
    --        VARIABLES  { ifIndex }  (MTU cannot handle import of mib 2 oids)
             DESCRIPTION...
    
    
    Is this remark good ?
    I am wondering myself because I read in the note 5093.1 that it seems
    possible to import of mib objects from mib II.
    
    So, Can you tell me if the note 5093.1 is correct ?
    If it is correct, what is my problem ?
    
    (The Decmcc dictionary seems me right - correct childs of SNMP global
    entity )
    
                              >-----------------------<
    
    Have you news about the yacc stack overflow ?
    In fact, an error occurs during the MSL Translator running when i try
    to translate the DEC-HUB900-ERPTR-MIB-V1-0.MS file in dictionary loadable
    file.
    
    $manage/tool/spec DEC-HUB900-ERPTR-MIB-V1-0.MS
    
    DECmcc Management Specification Language Translation Tool
                   Version V1.3.0
                                      
    $manage/tool/spec DEC-HUB900-ERPTR-MIB-V1-0.MS
    
    DECmcc Management Specification Language Translation Tool
                   Version V1.3.0
    
    %MCCMSL-I-MSLLOCATION, Line: 174, File: DEC-HUB900-ERPTR-MIB-V1-0.MS;,
    %MCCMSL-E-PARSER, yacc stack overflow: The value "1" is not expected
    %MCCMSL-E-ERROR, MSL did not complete successfully, please see previous
    error
    
    
    
    Thanks for your help,
                        
    
    Jacques Meersman 
    
    
    
    
    
    
    
    
    

	You are correct in assuming that the mib translator in its
	current form cannot import objects from other mibs into the
	trap definitions. (However, it can import only MIB II objects
	in the INDEX clause). So, you will have to comment out the
	VARIABLE clause in the TRAP-TYPE declaration.

	If the MS you are trying to run through the MSL translator is nested
	too deep, then you might see the yacc stack oveflow. The max
	stack size has to be increased in the MSL translator. 

	Rahul.

>        If the MS you are trying to run through the MSL translator is nested
>        too deep, then you might see the yacc stack oveflow. The max
>        stack size has to be increased in the MSL translator. 

Already done. The new MSL translator is on

	BIKINI::MCC_DISK:[BMS013.VMS.MSL]
	BIKINI::MCC_DISK:[BMS013.ULTRIX.MSL]

*Robert