[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

1484.0. "Performance Analyser and DR200/DR250" by WELLIN::MCCALLUM () Wed Sep 11 1991 14:36

    
    Hello,
    
    Is there any good reason why the Performance Analyser in V1.1 does
    not work with DECrouter 200 and 250 async lines ? Or is it just that we
    didn't have time to do it.
    
    Is there going to be any chance of any PA work for the DR200 before
    V1.2 ?
    
    I have a customer who wants to use DECmcc to manage his net and he has
    over 10 DR200s - he was not impressed when I told him it wouldn't work
    on his asynch lines, as they are the ones with the most error rates!
    
    David McCallum.

T.R	Title	User	Personal Name	Date	Lines
1484.1	How about DECnet VAX Asynch lines?	WELLIN::MCCALLUM		`Mon Sep 16 1991 07:48`	9
	I also tried it on the asynch circuit from DECnet VAX and got an error "Cannot locate services required information for computing statistics" Is this circuit not supported with the PA also ? Dave
1484.2	Not a good reason, but....	TOOK::CAREY		`Mon Sep 16 1991 13:37`	31
	RE: .0: Not a good reason, but.... The DNA4_AM doesn't currently maintain enough 'tween thread context to recognize that it is the guy tying up the management link to a remote system that only supports a single link. The DR200 and DR250 only allow one management connection at a time. PA FM tries to start a couple of threads making requests through the AM, the AM tries to honor them, the remote agent rejects them. In DECmcc V1.2, we are enhancing the AM to handle this case of multiple concurrent attempts at an agent that only allows a single management link to be outstanding. We will force these links to occur sequentially. RE: .2: Hmmm. Different problem here, definitely. Anwar can tell for sure, but the error you are reporting can occur when the "Line Speed" attribute has not been set for a line when line or circuit statistics are requested. The hardware seldom reports its bitrate, so the network manager is constrained to enter that information. Hope this helps -Jim
1484.3	Protocol or type not available.	TOOK::ANWARUDDIN	Anwar	`Wed Sep 18 1991 11:06`	12
	re .1 >> I also tried it on the asynch circuit from DECnet VAX and got an error >> "Cannot locate services required information for computing statistics" >> Is this circuit not supported with the PA also ? One of the reasons you get the error message is that an attribute which PA needs in order to lookup the services required to compute statistics is not being returned by the AM. For instance, in this case the attribute "protocol" or "type" is probably not being returned. This problem will be fixed in the next version of the MM.
1484.4	Please make messages more meaningful.	NSSG::R_SPENCE	Nets don't fail me now...	`Thu Sep 19 1991 14:17`	4
	I hope "fixed" in this case means the system will TELL you which attribute needs to be set? s/rob