[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

5062.0. "Click/Crash problem." by VCSESU::WADE (Bill Wade, VAXc Systems & Support Eng) Thu May 13 1993 17:42

    From the IMPM, what determines when the agent is actually queried?
    
    For example -
    
    	if I double-click on an SNMP global entity, is the agent queried
    	to determine the child entities?  
    	
    	Does it take an actual SHOW command for communication with the
    	agent to take place?
      
    The reason I ask is I'm working a problem where double-clicking on a 
    global entity icon caused the device that was represented by the icon to 
    crash but, I didn't think there was any communicatioin with the agent at 
    that point.
    
    Thanks,
    Bill
T.RTitleUserPersonal
Name
DateLines
5062.12582::YAHEY::BOSEFri May 14 1993 11:0911
>>    	if I double-click on an SNMP global entity, is the agent queried
>>    	to determine the child entities?  
  
	No. The querying is done at the time of registration.
  	
>>    	Does it take an actual SHOW command for communication with the
>>    	agent to take place?
  
	Yes.

	rb.
5062.2V1.2.0 or later?MOLAR::MOLAR::BRIENENNetwork Management Applications!Mon May 17 1993 15:097
Wasn't there a change in behavior between V1.2.0 and later releases?

Specifically V1.2.0, as a result of the double-click, would query an
entity for its children, whereas later versions (e.g. V1.2.3, V1.3) would
store child entity information when the entity was REGISTERed ?

						Chris
5062.3MOLAR::YAHEY::BOSETue May 18 1993 14:425
	You are right Chris. I was assuming the user is running the latest 
	version (1.3).

	Rahul.
5062.4More infoBACHUS::VANDENBERGHEMon Jun 28 1993 13:0764
    A clue is requested,
    
    On a customer site I have exactely the same problem.
    Unfortunately I can not reproduce here on my test environment.
    
    The problem is the following:
    
    Trying to display  (Map) a SNMP child entity on the entity map using 
    either the Toolbox to look into the SNMP sub-Entities until the desired 
    child or by directely creating the entity through the full definition at
    the SNMP entity level, the user interface is CRASHING !!.
    
    SNMP
         Chipcom
                 Chipmib02 
              		olConc
    				olNet		
   		 			olEnet
                				    olEnetStatsModTable   <--
    	 	
    	Crash while selecting that one via the tool box or entering
        xxx Chipcom .... olEnetStatsModTable (3,1) from the SNMP Entity
    
    
    	I can't reproduce that on my system and the reason is I think the
        level of sub-entities.
    
    	On the customer system the chipcom MIB version for Emm V3.2 was only
    	enrolled once.  
    	On my system running, previous version of Chipcom mibs were already
    	enrolled but the last one is the same as the cutomer one.
    
    	Looking on my system with the Dictionnary browser, I have only three
        levels:
    
   	 SNMP
     		 Chipcom
       			Chipmib02
                		olConc
    	      			olNet		
   				olEnet
               			olEnetStatsModTable 
    	       			....................
    And I have no problem to Map a child entity
    
    On the customer system the child entities are as mentionned above.
    
    On the customer system I had no problem to MAP the Interface SNMP child
    Entity which is again just one level under Interface.
    
    So the questions:
    Is it possible that there is a limitation to MAP child entities on
    the MAP function of the level it occupied in the entity tree?
    
    Why is the MIB enrolled with different level from one system to another?
    	
    What is the possible work-around.
    
    Thanks in advance,
    Robert
    
    
    
    
5062.5Is it just your window manager that dies?CUJO::HILLDan Hill-Net.Mgt.-Customer ResidentFri Jul 02 1993 02:465
    If it is your window manager dying, this is a Motif problem that has
    since been resolved.  Contact the CSC 18005257104   for the proper
    patch.
    
    -Dan
5062.6VERNA::V_GILBERTTue Jul 06 1993 13:0712
Re .4

Robert,

What version and operating system of DECmcc are you using?

We know of a problem with V1.3 with greater than 9 levels of classes, but 
did not think it occurred with fewer than nine.  However we have fixed this
problem for the mup release, so if you send me mail (took::v_gilbert), I can
give you a pointer to an exe to try and see if it fixes your problem.

Verna