OS Hang Data Capture requirements


A. Windows Hangs

General Information
-What is the function of this server? File/print server? Database? Email?
-How many users attach to this server daily?
-Does the system seem to hang under a heavy work load or stress?
-How often does the server hang?
-Is the  server in production or in a test lab?
-Has any software been reinstalled o  this system to try and correct the hang conditions?
- Have any changes been made to this system recently?
	a. Hardware added/removed?
	b. Software added/removed?
-Was this system working fine for  a period of time, then started failing?
-Are there any other symptoms or failures to include error messages?
-Are there any other symptoms or failures to include, i.e. error messages?
-Have you reviewed and applied any ECAs or Retain Tips as applicable?
-Has there been any data corruption as a result of the hang conditions?
	If yes, how did you make this determination? How did you recover from this in the past?

Windows Specific Information
-Clearly document the version of Windows installed on the server
	a. What Service Pack version is installed, if any ?
-If the server is blue screening with a STOP error...
	a. how frequent are the traps?
	b. Are the traps the same each ti e?
	c. Document the first 5 lines of any STOP blue screen errors.
-If the server "hangs" what stops working?
	a. Does the keyboard respond?
	b. Does the mouse cursor move?
	c. Does Ctrl+ Alt+ Del  launch Task Manager?	
	d. Does the server respond to network requests?
	e. Is there a response to a PING command?
	f. What is the state of the video? 


B. Netware Hangs

0.  Capture general information stated above under Windows Hangs.
1.  Capture a config.txt.
2.  Does the keyboard respond? 
3.  Does the mouse cursor move?
4.  Can the debug mode be involved, (Alt+Alt+Shift+ESC)?


C. Linux Hangs

0.  Capture general information stated above under Windows Hangs.  
1.  Capture message logs by entering the following command.  (/var/logs/messages).

D. SCO Hangs

0.  Capture general information stated above under Windows Hangs.
1.  Capture message logs by entering the following command.  (/var/adm/messages).
2.  Capture hardware configuration by entering the following command.  (hw config -h >> filename).
3.  Capture PCI device information by entering  the following command.  (hw - rv pci >> filename).

Note that >> indicates that the information has to be piped out to a filename.

E. Unixware Hangs

0.  Capture general information stated above under Windows Hangs.
1.  Capture system logs by entering the following command.  (/var/adm/syslogs).
2.  Capture PCI device information by entering the following command.  (hw -v >> filename).

Note that >> indicates that the information has to be piped out to a filename.