Conference 7.286::fddi

556.0. "Decnet Jerky, Pathworks crashing." by KERNEL::LEATEA (Veni,Vidi..well, two out of three...) Tue May 05 1992 10:12

This note is posted on both MDF and FDDI notes files.

Hi,

	I am involved with a recently installed FDDI VaxCluster (MDF).
	
	There are two 6xxx systems on each of two lobes, each connected to 
a Deconcentrator 500. Both of these lobes have a DecBridge 510 connecting 
the FDDI to the main backbone. A third lobe connects its ethernet backbone 
via a DecBridge 520.

	VMS V5.4-3
	Decnet Extensions with 16-March patches (but original NETACP and 
NETDRIVER).
	Pathworks 4.1
	Lat and LATmaster patches from CSCPAT_0511030.

	Decnet, LAT and SCA are all running on the 6xxx system over the FDDI 
interface (DEMFA). LAST is running over the Ethernet controllers.

	Since utilising the FDDI hardware, the cluster has been 
experiencing a number of problems which I am having trouble getting to the 
bottom of. These problems did not occur when running with the MDF system disks 
but not utilising FDDI.

	1/ When setting host over the FDDI, terminal response can be 
"jerky", and sometimes appears to hang for up to three seconds at a time 
during output to screen. This is not 100% reproducable, and so far seems to 
occur only when setting host from an ethernet based system (i.e. over a 
Decbridge 510). LAT traffic can also seem jerky, but this is far less 
tangeable. The jerky Decnet behaviour has also been experienced during quiet 
times, i.e. users gone home, no Backups running, no shadow set 
merging/copying, so does not appear to be load related. I have the same 
bridge counter activity as is noted by Gary Malloy in note 547 of the FDDI 
notes file, and I have the same module/firmware revision levels (and I am 
just as confused about what they should be!!!).

	
	2/ The LAD$KERNEL process keeps dissappearing! Even though LAST is 
not set up to run over the FDDI controllers, this problem has only started 
since the FDDI was connected. No LAD$KERNEL process dump is created. I am 
currently arranging for Accounting to catch the process termination to see 
if the termination status reveals anything.


	If anyone else is seeing any similar problems, or can throw any 
light on these failures, please let me know.


Regards
Adrian Leate