Conference azur::mcc

Denis:

  Question/problem #1:

    The dictionary error that you are getting seems to indicate that the some
    parent of SUBCLASS CHBACKPLANETABLE has not been created before the 

      Command: CREATE CLASS SNMP SUBCLASS CABLETRON SUBCLASS MIBS
               SUBCLASS CHASSIS SUBCLASS CHBACKPLANETABLE CODE 1

    was executed.  Thus the 

      "%MCC-E-NOENTITY, no corresponding entity instance exists" 

    message.

    Sorry I can't tell you which one from this error message, but you can go
    into DAP (or better yet the Dictionary Browser and expand all the subclasses
    of SNMP to find out what's there and what's missing.

                                                                      - Jerry

	Questions :

		Did you already have a cabletron mib loaded ?
		Did you chose the "augment" or "replace" option in MTU ?

>>The second problem is....

	The SNMP AM does a GetNext operation on the root mib object (in your
	case the cabletron enterprise object). According to the 
	SNMP protocol the GetNext operation should return the first supported
	object in the mib. If the agent does return such an object then
	the mib is added to the list of mibs supported by the entity.
	Seems like that the agent is not returning the first available 
	object correctly. If this is indeed the case, then there is nothing
	we can do. Mib filtering will work only if the agent implements 
	the protocol properly.

>>The third issue is :	

	This is a real issue. The user should be able to figure which mib groups
	are supported by an agent once, and preserve this information for use
	in subsequent operations. Unfortunately, I don't think this is possible
	through MCC at the moment.

>>And last but not least synoptics....

	I am really curious to hear more about this one.

	Rahul.

	

    Hi Rahul,
    
    You and I had a similar discussion back in note 1921 about the 
    Cabletron stuff. Actually it's the same customer.
    Anyway in answer to your questions:
    Yes there was a cabletron mib already loaded, and I tried BOTH
    options to the compiler. First I loaded "cabletron_comn_mibdef.txt"
    with the Augment option. After that bombed out I tried to reload
    it again this time with the Replace option. The compile finished
    although the same error message occurred(i.e the one mentioned in .0).
    The funny thing is that we could manage these boxes ok in V1.2.
    In the meantime I've loaded the cabletron mibs on my office workstation
    and guess what ? - the same error occurs. So I figured I would try to
    load them on a VMS workstation and see what happens. Well as fate
    would have it they all compiled error free on the VMS node
    and it's running DECmcc V1.3 as well. So now I'm really stuck. This
    seems to indicate that the mibs are ok -  at least as far as syntax is
    concerned.
    Like I said I have not seen the synoptics phenomenon with my own eyes
    as yet but after my next site visit I'll tell you more.
    cheers,
    Denis

    Hi again,
    
    CORRECTION CORRECTION CORRECTION
    
    in .3 I made the claim that the mib compiler barfs no matter
    which of the options (Augment or Replace) you pass it.
    This is NOT the case. With the "replace" option I don't get
    the error.
    Sorrrrrrrry........
    
    Denis

	Denis,
		There are 5 cabletron mibs shipped with DECmcc V1.3. If
	you need to load more than one of them, then do the following.
	Choose the REPLACE option in MTU while loading the first mib,
	and for subsequent mibs choose the AUGMENT option.

		From the log it is evident that all the mibs compiled
	cleanly, but the errors occurred when the MTU command procedure
	tried loading the mib in the dictionary. You might want to delete
	the Cabletron child entity (under SNMP global entity) through
	DAP and start from scratch.

	Rahul.

    Hi again,
    
    Ok I'll try to delete the MIB altogether via DAP as Rahul
    suggested and then I'll post the results here
    
    Denis
    

    Hi Rahul,
    
    The problem I mentioned earlier with Synoptics manifested itself
    in the following way:
    After loading the new Synoptics (and also Cabletron mibs) we 
    received the following error while trying to open a domain that
    contained either one of these entities - 
    " Entity class 5045 is not in the dictionary". As it turned out
    this was apparently refering to an object type in the map file.
    Anyway the domain could not be opened. The only thing we could do
    was delete the appropriate object from the map file using our 
    favourite editor and then the domain could be opened again. Why
    this happened I have no idea - since we had other domains with
    exactly the same graphics in them and they worked ok. But.....
    there are other problems as well:
    e.g. Clicking into cabletron objects sometimes produces the error:
    "Software error: invalid in_entity(input entity) parameter"
    or:
    After selecting an snmp entity from the map we attempted to use
    the "test" function from the operations menu and it will not
    work at all - we receive the error:
    "Internet communications device error" - however after clicking down into 
    the entity one can see  the sub entities and perform operations on them. 
    It says in the mcc "messages" chapter that this is because UCX is not 
    running on the management station......but the management station is 
    an Ultrix machine !! Is is possible that only one CAbletron mib can be 
    loaded and all these problems are the results of confusion caused by
    loading all five mibs ? It sure as hell looks that way. 
    One other thing before I stop whining ... is it possible to configure
    the iconic map in such a way as to prevent the lock from being opened ?
    
    cheers,
    Denis