[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

2023.0. "Node 'Counter Creation Time' query " by WELTM1::CRIDDLE (Graham Criddle, DS Tech Consultant, 853-4015) Fri Jan 03 1992 11:36

Hi...

I have been trying to use MCC 1.1 to record node information so that I can
generate historical node level statistics.
Unfortunately, it does not work all the time due to a 'quirk' in the way in
which DECnet-VAX seems to maintain exec counters.

Specifically MCC complains about not being able to find the 'Counter Creation
Time' which relates to the NCP 'seconds since last zeroed' information.

My tests show that this counter is not started on the node exec counters until
the node in question has established a logical link to itself.
(This has been seen on VMS 5.4-3 and 5.5 - I do not know if this has always
been the case)

Is this how it is supposed to work as far as DECnet is concerned?

How should MCC cope with this situation?

Rgds,
Graham

Cross posted in MCC and DECNETVAX conferences

T.R	Title	User	Personal Name	Date	Lines
2023.1	If you can get that fixed, your a better man than I Gunga Din	BLUMON::SYLOR	Architect = Buzzword Generator	`Mon Jan 06 1992 12:45`	7
	What you've described is a "well known" bug in DECnet-VAX. Its been around for at least 7-8 years. I guess that classifies it as a "feature" :-). In any case, there should be a Seconds Since Last Zeroed counter for the executor node from the start. Mark
2023.2	yes, known behavior	TOOK::JEAN_LEE		`Mon Jan 06 1992 16:42`	23
	Graham, Yes, this is a known behavior of DECnet. Node4 sees itself as both the Executor node and as a Remote Node. There is a set of counters that are returned only when the Executor Node views itself as a remote (destination) node, such as seconds since last zeroed, user bytes received, connects received...etc. In order for those counters to start incrementing, the node4 must have had a connection to itself. Examples for setting up a logical link to itself are: MCC> show node4 <exec node> or NCP> tell <exec node> show exec An attempt was made during the V1.1 development cycle to modify this behavior to show the whole set of counters, but was vetoed on the grounds that it would not be consistent with NCP. Jean
2023.3		WELTM1::CRIDDLE	Graham Criddle, DS Tech Consultant, 853-4015	`Tue Jan 07 1992 04:23`	14
	Hi, again... Thanks for the response... It would appear from these comments (and from the DECnetVAX conference) that every one agrees that DECnet VAX is at fault here, but that it is unlikely to change... Does this not cause major problems when trying to perform node level stats on remote VMS DECnet implementations over which you may have no control? Rgds, Graham
2023.4	Can you force them to start?	TOOK::R_SPENCE	Nets don't fail me now...	`Wed Jan 08 1992 09:48`	6
	Could this be gotten around by adding something like $ DIR 0:: to the system startup procedure of each system to force the counters to start? s/rob
2023.5	Yup	BLUMON::SYLOR	Architect = Buzzword Generator	`Mon Jan 13 1992 08:24`	2
	Yes Rob, that's the work around - any connection from the node to itself causes the counters to appear.