[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::fddi

Title:FDDI - The Next Generation
Moderator:NETCAD::STEFANI
Created:Thu Apr 27 1989
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2259
Total number of notes:8590

1616.0. "FDDI ring init with Silicon Graphics Computers" by 51847::JENS () Thu Mar 09 1995 05:02

	Hi there !

	I have a customer , who has a problem with FDDI -ring initiali-
	zation. The ring consist of a DECBRIDGE 900 a alfa 2100 and 3
	Silicon Graphics system's. The Alpha 2100 is running version 
	3.0 of OSF and is logging these errors on the console. It is hap-
	pening 2-5 times a day ( systems are not booting or leaving the ring
	voluntary )

	Quistion-time :

	Is there any way to detect who is causing the ring to initialize on
	Alpha or via Hubwatch ?

	

	Best regards and
	thanks for any input


	Jens Bondo , MCS-comms 





                                  
T.RTitleUserPersonal
Name
DateLines
1616.1NETCAD::B_CRONINThu Mar 09 1995 15:0317
    
    You can check the ring inits initiated counters on the DEC boxes, and
    that will tell you whether any of them are the source of the inits. 
    
    You might also put an analyzer into the ring, and see who starts
    claiming. But you will have to move the analyzer around so that you 
    catch the claim initiator, not just the station with the lowest 
    value of T_Req as seen at your observation point. This is not an 
    easy job......
    
    Also, make sure that no one is rebooting these systems when you aren't 
    looking. That has often been the source of similar complaints. 
    
    Why are they sensitive to this? Is it cauing them problems, or is it 
    just that they see the counter ticking, and start to wonder what is
    happening? Someone powering off a system before going home would
    have a similar effect.
1616.2Silicon Graphics machines is the cause51847::JENSMon Mar 13 1995 02:538
 	Hi again !

	Thanks for the answers. It turned out that the It was the Silicon-
	Graphics machines that were the cause. They have to get a patch for
	this. 


	Regards Jens
1616.3NETCAD::B_CRONINTue Mar 14 1995 10:286
    Glad the problem is found.
    
    If you find out the reason for the patch please post it here. It
    helps me and others to know what the bugs are.