[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

520.0. "GIGAswitch vs DH90 MIB definition problem?" by CAATS::MURRAY (Geoff Murray - CAATS Team - DTN 638-6925) Wed Nov 24 1993 22:28

    ****************************************************************************
    	Cross posted in GIGAswitch notes conference
    ****************************************************************************
    
    The GIGAswith MIB definition seems to conflict with both DEChub90 MIB
    definitions I have seen. The first DEChub90 MIB definition is the one
    that is distributed with MCC V1.3 (OpenVMS version). The second
    DEChub90 definition is an updated version available through the
    HUB_MGMNT conference (5-nov-1993 version).
    
    Extract from the DEChub 90 definition:
    
    	dec                     OBJECT IDENTIFIER ::=  { enterprises 36 }
    	ema                     OBJECT IDENTIFIER ::=  { dec 2 }
    	emaSystem               OBJECT IDENTIFIER ::=  { ema 15 }
    	bridges                 OBJECT IDENTIFIER ::=  { emaSystem 3 }
    
    Extract from the GIGAswitch definition:
    
    	dec             OBJECT IDENTIFIER ::= { enterprises 36 }
    	ema             OBJECT IDENTIFIER ::= { dec 2 }
    	sysobjid        OBJECT IDENTIFIER ::= { ema 15 }
    	bridges         OBJECT IDENTIFIER ::= { sysobjid 3 }
    	gigaswitch      OBJECT IDENTIFIER ::= { bridges 3 }
    
    Perhaps I am missing something about the way the DECmcc dictionary
    works. I have tried to add these both to the dictionary by using an
    AUGMENT, not REPLACE.
    
    I tried to add the DEChub90 definition after adding the GIGAswitch
    definition. It failed on the creation of the emaSystem portion. I
    believe it's because it's trying to give the same identifier value to
    two different names. 
    
    Is there a workaround for this? 
    
    I'm going to try editing the DEChub90 module and replace the emaSystem
    name with the sysobjid name, to see if it gets any farther. 
    
    Doesn't Digital have a registry for these values? Are these out of
    sync?
    
    Any help appreciated.
    
    Thanks,
    Geoff.
T.RTitleUserPersonal
Name
DateLines
520.1A workaround...CAATS::MURRAYGeoff Murray - CAATS Team - DTN 638-6925Fri Nov 26 1993 18:298
    I changes the emaSystem name in the DEChub MIB to sysobjid, to make it
    consistent with the GIGAswitch MIB. It seemed to compile, and I can see
    both sets in my MCC dictionary.
    
    Does anyone know which value is correct? emaSystem or sysobjid?
    
    Cheers,
    Geoff.
520.2It's either sysobjids or sysobjid.QUIVER::GALLAGHERSun Nov 28 1993 18:4114
Geoff,

The DEChub90 definition "emaSystem" is incorrect.  I will notify the 
maintainers of this MIB so that it can be fixed in the next version.

>    Doesn't Digital have a registry for these values? Are these out of
>    sync?
 
Yes and yes.  In fact, the registry has "sysobjids" rather than "sysobjid".
I'll be working to resolve these discrepancies in the DEChub90 and DEChub900
MIBs.

Thanks for pointing this out.
						-Shawn