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

Conference netcad::hub_mgnt

Title:	DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:	Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:	NETCAD::COLELLADT

Created:	Wed Nov 13 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4455
Total number of notes:	16761

1986.0. "DECserver 900TM - Fatal Bugcheck 913 - Question ?" by GIDDAY::STANISLAUS () Thu Feb 09 1995 01:59

	Also posted in Terminal Server notes conference.
	------------------------------------------------
 

       <<< TOOK::WORK$40:[NOTES$LIBRARY]TERMINAL_SERVERS.NOTE;32767 >>>
                             -< Terminal Servers >-
================================================================================
Note 2216.0         DECserver 900TM Fatal Bugcheck - Question         No replies
GIDDAY::STANISLAUS                                   51 lines   9-FEB-1995 01:39
--------------------------------------------------------------------------------


	DECserver900TM crash problem but not dump file
	----------------------------------------------

	The following messages appear on port 1 of DS900TM units installed in 
	a DEChub900. There are 2 x DS900TMs and both of them have this problem.

	Since there is no dump file, can some clues be obtained from the
	PC, SP, SR, below:

	Local -020- Logged out port 1 on server CC9901
	Local -913- Fatal Bugcheck, PC=078609F8  SP=0795E574 SR=0000 M=00000000
				     C=1186
	Local -957- [MOP] Requesting Dump to host AA-00-04-00-6A-04
	Local -914- [MOP] Dump failure, timeout
	Local -957- [MOP] Requesting Dump to host AA-00-04-00-6A-04
	Local -914- [MOP] Dump failure, timeout
	Local -957- [MOP] Requesting Dump to host AA-00-04-00-6A-04
	Local -914- [MOP] Dump failure, timeout
	Local -957- [MOP] Requesting Dump to host AA-00-04-00-6A-04
	Local -914- [MOP] Dump failure, timeout
	Local -954- [MOP] Attempting to locate dump host [ISO8802]
	Local -954- [MOP] Attempting to locate dump host [ETHERNET]
	Local -965- Dump failed


	Local -901- Initializing DEcserver 900TM 08-00-2B-A2-AD-56 FW V5.0-0 
								   HW 1.6
	Local -960- Available Memory 4 Mbytes
	Local -969- Requesting Specified Software: WWENG2
	Local -991- LOAD channel set to Thinwire
	Local -953- [MOP] Attempting to locate load host [ISO8802]
	Local -953- [MOP] Attempting to locate load host [ETHERNET]
	Local -955- [MOP] Host AA-00-04-00-01-04 located [ETHERNET]
	Local -956- [MOP] Requesting load from host AA-00-04-00-01-04
	Local -903- [MOP] Loading from host AA-00-04-00-01-04
	Local -904- Image load complete

	Local - Telnet listener failed to bind socket
	Local - No internet addresss - SNMP not enabled
	Local -040- Software initialization complete


	While all the above happened there were DECrepeater 900TM units with PCs
	connected to them and those PCs did not miss a beat communicating with
	the hosts on the backbone. All the modules in the hub just talk to the
	thinwire only.


	Alphonse

T.R Title User Personal
Name Date Lines

1986.1 Deja, PRSSOS::PEYRACHE Jean-Yves Peyrache Country Support Group France Thu Feb 09 1995 06:23 29

T.R	Title	User	Personal Name	Date	Lines
1986.1	Deja,	PRSSOS::PEYRACHE	Jean-Yves Peyrache Country Support Group France	`Thu Feb 09 1995 06:23`	29
	Which version of NAS currenlty installed ? this kind of crash have been solved in V1,4 of NAS, see below an extract of release notes. jean-yves PS:since yesterday V1.5 is available 6.1 DECserver crashes with 1186 code An 1186 code indicates that the server has been requested to trans- mit host data out an asynchronous port but was unable to verify that the port had a connection to a host. Several different causes for th crash were identified and corrected. In most cases the crash occurred when the server's RESUME command was used to resume a dormant LAT se sion. The crash would be set-up by a dormant session receiving a DAT A or DATA_B slot followed by a STOP slot. In this situation the ses- sion could not be terminated until the DATA slot had been processed and the DATA slot could not be processed until the session became ac- tive. Executing the RESUME command would start a chain of events whi would result in the session being improperly terminated causing the server to crash. There was also a situation where starting and stopping Multisessions on a port would cause a similar crash. If a Multisessions terminal s ified a service name in it's OPEN session command but sent a CLOSE s sion before the connection was established the server would crash.


 Which version of NAS currenlty installed ?
 this kind of crash have been solved in V1,4 of NAS, see below an extract
  of release notes.

  jean-yves

  PS:since yesterday V1.5 is available

           6.1  DECserver crashes with 1186 code
           
           An 1186 code indicates that the server has been requested to trans-
           mit host data out an asynchronous port but was unable to verify that
           the port had a connection to a host. Several different causes for th
           crash were identified and corrected. In most cases the crash occurred
           when the server's RESUME command was used to resume a dormant LAT se
           sion. The crash would be set-up by a dormant session receiving a DAT
           A or DATA_B slot followed by a STOP slot. In this situation the ses-
           sion could not be terminated until the DATA slot had been processed
           and the DATA slot could not be processed until the session became ac-
           tive. Executing the RESUME command would start a chain of events whi
           would result in the session being improperly terminated causing the
           server to crash.

           There was also a situation where starting and stopping Multisessions
           on a port would cause a similar crash. If a Multisessions terminal s
           ified a service name in it's OPEN session command but sent a CLOSE s
           sion before the connection was established the server would crash.