[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

4721.0. "DH90_MIB + DEC_Elan20_MIB , MTU Problem" by NBOFS1::HKLEIN () Fri Mar 19 1993 04:04

MCC V 1.2.0 SNMP-AM 1.2

I tried to load DH90_MIB.TXT using MTU V1.2,

That is DEC's private MIB extension for DECAgent90.

But I had loaded also the dec_elan20_MIB some time before.


So I used augment option, but it failed, with error message that 
subclass ema is already defined.


Later I used DAP to "load" the com-files, but first I deleted subclass ema
and subclass dec.

That worked with only one extension. 
Trying to load the second com-file, I was told that ema already is defined. 


Taking the update option replaced all definitions below subclass ema.



So my question:

Is there a successfull installation of DH90_MIB + dec_elan20_MIB 

and how did you get it ?

Is there anywhere a merged MIBdef.TXT of DH90_MIB and dec_elan20_MIB ?
 
Thank you

Hermann

T.R Title User Personal
Name Date Lines

4721.1 Appending is required for 1.2 VCSESU::WADE Bill Wade, VAXc Systems & Support Eng Fri Mar 19 1993 13:38 17

T.R	Title	User	Personal Name	Date	Lines
4721.1	Appending is required for 1.2	VCSESU::WADE	Bill Wade, VAXc Systems & Support Eng	`Fri Mar 19 1993 13:38`	17
	Append the DH90_MIB to the DEC_Elan20_MIB. Delete the end statement from the DEC_Elan20_MIBs and delete the following from the DH90_MIB dec OBJECT IDENTIFIER ::= { enterprises 36 } ema OBJECT IDENTIFIER ::= { dec 2 } decMIBextension OBJECT IDENTIFIER ::= { ema 18 } Also I'm not sure but I thinkk you'll have to take the import statement from the DH90_MIB and move it to the DEC_Elan20_MIB replacing the import statement in that MIB. We had to do the same thing for the GIGAswitch MIB and DECmcc V1.2.

    
    Append the DH90_MIB to the DEC_Elan20_MIB. Delete the end statement 
    from the  DEC_Elan20_MIBs and delete the following from the DH90_MIB
    
     	    dec             OBJECT IDENTIFIER ::=  { enterprises 36 }
            ema             OBJECT IDENTIFIER ::=  { dec 2 }
            decMIBextension OBJECT IDENTIFIER ::=  { ema 18 }
            
    Also I'm not sure but I thinkk you'll have to take the import
    statement from the DH90_MIB and move it to the  DEC_Elan20_MIB
    replacing the import statement in that MIB.
    
    We had to do the same thing for the GIGAswitch MIB and DECmcc V1.2.