Conference azur::mcc

5322.0. "Chipcom MIB problem" by TRKWSH::COMFORT (Here beside the rising tide) Fri Jul 09 1993 12:15

    
    I am having problems with the CHIPCOM_HUB3_BRG_10BT_MIBDEF.TXT MIB. 
    First I got an undefined variable error that terminated the compile,
    which I tracked down and changed:
    
      $ MTU = "$ SYS$SYSTEM:MCC_TCPIP_MTU.EXE"
    
                                       * * *
    
    (Now processing file # 1 out of a list of 1 file(s) ...)
    
    Beginning Phase 1 for file DKB0:[MCC]CHIPCOM_HUB3_BRG_10BT_MIBDEF.TXT;4
    
       9-JUL-1993 10:43:33
    Now starting to run the MIB Translator ...
    This may take approximately 1-5 minutes.
    Issuing following command:
      $ MTU DKB0:[MCC]CHIPCOM_HUB3_BRG_10BT_MIBDEF.TXT;4
==> Variable chipEchoResponseCount in trap defn. chipPing not previously
    defined
    An error occurred while running the MIB Translator.
    Check file CHIPCOM_HUB3_BRG_10BT_MIBDEF.LIS,
      if it exists, for any further information.
    Files CHIPCOM_HUB3_BRG_10BT_MIBDEF.MS and
    CHIPCOM_HUB3_BRG_10BT_MIBDEF_ENUM.MS
      may also have been created; delete these files, as appropriate.
    
       9-JUL-1993 10:43:59
    
    Procedure terminated in error.
    $
    
    The actual variable definition was chipEchoResponseCounts  with the s. 
    After the change the MIB did compile, but when I go to augment the
    dictionary :
    
    Issuing following command:
      $ MANAGE/TOOLKIT/SPECIFICATION CHIPCOM_HUB3_BRG_10BT_MIBDEF.MS
    DECmcc Management Specification Language Translation Tool
                   Version V1.3.0
    
    %MCCMSL-I-MSLLOCATION, Line: 444, File:
    CHIPCOM_HUB3_BRG_10BT_MIBDEF.MS;,
    %MCCMSL-E-ID_CONFLICT, Object name or code conflicts with another object
            at the same location in the dictionary
    %MCCMSL-E-ERROR, MSL did not complete successfully, please see previous
    error
    An error occurred while running the MSL Translator.
    Check file CHIPCOM_HUB3_BRG_10BT_MIBDEF.LOG, if it exists, for any
    further information.
    
       9-JUL-1993 11:11:22
    
    Procedure terminated in error.
    %NONAME-E-NOMSG, Message number 04EFB05A
    $ ty CHIPCOM_HUB3_BRG_10BT_MIBDEF.LOG
    %TYPE-W-SEARCHFAIL, error searching for DKB0:[MCC]CHIPCOM_HUB3_BRG_10BT_MIBDEF.LOG;
    -RMS-E-FNF, file not found
    $
    
    
    Anyone know what's wrong?
    
    Thanks,
    
    Dave
    

	The chipcom mib has duplicate trap IDs which cannot be handled
	by DECmcc SNMP AM. Commenting them out is a work-around. I remember
	doing it for the mib which ships with the V1.3 kit, which is what
	you might want to use (unless they have changed the mib).

	Rahul.