[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

6092.0. "MCC to Agent - High query count" by CUJO::BROWN (Dave Brown) Tue Aug 23 1994 18:34

    
    
    	I have just had a customer report a problem with the extensible Common 
    Agent interacting with V1.3 of DECmcc. This is what they did:
    
    	1) Add some extensions to the agent
    
    	2) Update the MCC dictionary to support the extensions
    
    	3) Interact with the agent from MCC
    
    	  a. Network analyzer indicates that MCC is querying the agent 
    	     three times per request.
    
    	  b. Within MCC, deregister and reregister the node running the
    	     agent. Network analyzer now indicates one MCC to agent
             query per request.    
    
    	This problem, due to the elevated network traffic in 3a above, was
    of major concern to the customer until they discovered the workaround
    in 3b. They wanted me to bring this up for resolution; they beleive
    that MCC should not query the agent 3 times per request nor do
    they beleive that they should be forced to deregister/reregister the
    node to bring the query per request count to 1.
    
    	Any ideas? Why should MCC query the agent 3 times per request until
    the agent node is deregistered/reregistered?
    
    
    	Thanks!
    
    	Dave

T.R	Title	User	Personal Name	Date	Lines
6092.1	NEI - Not enough Information	SCCA::Dave	You think I know something about Netview?	`Wed Aug 24 1994 09:58`	7
	Some more information would be helpfull, like what protocols we are talking about here. Is it NCL, or SNMP? If its NCL, what types of objects did they add? what did they use for class codes? What is the DYNAMIC parameter? If its SNMP, where did they put it in the MIB tree. Did that part of the the already have something registered in it? Is this a new decendent under 1.2.....enterprise?
6092.2	What is the CLD number that was assigned?	SCCA::Dave	You think I know something about Netview?	`Wed Aug 24 1994 09:59`	5
	PS: If it is a customer problem, file a CLD.
6092.3	Answers to .1	CUJO::BROWN	Dave Brown	`Wed Aug 24 1994 14:48`	24
	To answer the questions in .1 - > Is it NCL, or SNMP? SNMP > If its SNMP, where did they put it in the MIB tree? .1.3.6.1.4.1.303.4.1.2 > Did that part of the the already have something registered in it? No > Is this a new decendent under 1.2.....enterprise? Should be answered above If you'd like a CLD for this problem, we can probably arrange that. Any additional information would be appreciated. Thanks! Dave
6092.4	As designed. its a tradeoff with other features.	SCCA::Dave	You think I know something about Netview?	`Thu Aug 25 1994 17:27`	16
	If you dont like the way it works, you should file the CLD, else it will never get changed. From what you said, it is working as designed. When you register a SNMP node, the MIB extension trees that are on the node and in the dictionary are recorded to save the AM from having to figure out if the mib is there. (on the system) It also uses this information to prune the list of options displayed if you do a "look into" in the iconic map. There is no easy way (that I know of) to change this, you are going to have to de-register / re-register the SNMP stuff. But, of course, due to your far seeing insight, you (like everyone else in the world) has an update registration script, and its just a matter of letting it run overnight!!!! Right????
6092.5	Perhaps the customer has done something correctly	CUJO::BROWN	Dave Brown	`Thu Aug 25 1994 23:00`	4
	We'll see how forward thinking the customer is - I'll ask. Dave