|
Hello Mary,
The problem you are reporting was first brought to my notice
by Colin *before* we started EFT. While it is true that
there is a bug in some WAVE 1 implementations of Phase V
DECNET, I took care of the problem by providing a time
out logic in Autoconfig. The changes were tested extensively
to make sure we handle the bug "gracefully". I am now surprised to
see that you are still having some problem about lingering links.
I know its too late but by any chance, do you remember the
node that did not respond? If you are still having a problem
let me know.
To answer your question Colin, yes I did send mail to
(Pete Carlson?) way back when we were having the problems.
I did not get any response.
I do apologize though I have not followed it up after that.
There is just so much one brain can do :-)
- Anil
<<< NOTED::DISK$NOTES4:[NOTES$LIBRARY_4OF5]MCC.NOTE;1 >>>
-< DECmcc Network Management Product Family >-
================================================================================
Note 2074.0 DECnet AutoConfig & Wave1 1 reply
PARZVL::KENNEDY "this ain't no party" 18 lines 10-JAN-1992 13:31
--------------------------------------------------------------------------------
Any known problems with Auto-Config and nodes running DECnet-VAX Extensions?
I was running, asking for all nodes in a given area, using adjacency search.
Left in the evening when the process had reached " Executing registration
script ...".
Came in the next day, it hadn't completed. Eventually discovered I had an
NML link to one node since last last night. Talked to the system manager, we
determined that the NML process on his end had been doing nothing most of
that time (over 12 hours connect & about 6 (or .6) seconds of CPU. The only
notable thing was that the node is running DECnet-VAX Extensions (and so
is the machine I'm running DECmcc on).
I finally disconnected the link and AutoConfig is continuing (based on NCP
links being set up and different com files being opened in the autoconfig
directory).
_Mek
================================================================================
Note 2074.1 DECnet AutoConfig & Wave1 1 of 1
TOOK::STRUTT "Management - the one word oxymoron" 8 lines 14-JAN-1992 11:20
--------------------------------------------------------------------------------
I observed the same problem (many times) during system test of v1.2.
I discovered that the problem was with DECnet and not MCC - I could get
the same failure using NCP! This was reported to Anil as it showed
up under autoconfig most often. Anil - did this ever get reported to
the DECnet group, and do we know the result?
Colin
|
| Anil,
Very sorry to be so late in responding. The node which did not respond is
SKIP:: (55.892). I did actually try some NCP commands to it and was unable
to reproduce it.
What's more embarassing is that the next day I discovered that a program
written by my colleague, which was not using DECmcc, was exhibiting the
same problem (tho' to a different system whose name I don't recall), so I
did discover that it was more likely to be a DECnet problem.
Regards,
_Mek
|