Conference vaxaxp::vmsnotes

233.0. "The official 'system crash -> CANASTA' topic" by HAN::HALLE (Volker Halle MCS @HAO DTN 863-5216) Fri Feb 21 1997 03:20

    
    This note will be used to try to explain the usage of CANASTA as the
    first step during system crash analysis. Instead of adding replies to
    every CLUE file posting, I'm using this topic to 'spread the word'
    about CANASTA.
    
    Volker.
    
    
    +++++ CANASTA is a Digital-internal Crashdump Analysis tool. It can 
    
    	- parse OpenVMS Alpha and OpenVMS VAX CLUE files
    	  (and UNIX crash-data files -> topic TURRIS::DIGITAL_UNIX #8919)
    
    	- match crash footprints against a 'knowledge database' of known
    	  crashes (providing solutions or workarounds from CANASTA 'rules').
    	  There are currently 367 OpenVMS Alpha and 1791 OpenVMS VAX rules.
    
    	- provide a list of 'cases' with the SAME crash footprint (some of
    	  those might have been escalated as IPMTs, QARs etc.). There are 
    	  currently crash footprints from 
    
    			25647 OpenVMS VAX crashes
    			 6566 OpenVMS Alpha crashes
    
    	  in the CANASTA world-wide crash database.
    	
    
    +++++ Using CANASTA for crash analysis is as easy as sending mail...
    
    	  Whenever you get a system crash problem, please obtain the associated
    	  CLUE file and mail it to the CANASTA Mail server:
    
    	    [email protected]	or    XOCOMP::CAN_SERVER
    
    	  Use a mail subject string of:
    
    	    DIAGNOSE CASE=log-number
    
    	  where	log-number	is your call handling system log-number
    			   	(e.g. C970202-12345   for CHAMP,
    			              12345003551NGY  for NICE,
    				      MGO123456       for IPMT Request ID,
    				      QAR_012345      for QAR number)
    				If you don't have any kind of reference number,
    				omit the CASE=log-number parameter.
    				For additional information, please see note
    				SPECXN::CANASTA #222.3
    
    	  Example:
    
    $ MAIL clue-file XOCOMP::CAN_SERVER/SUBJECT="DIAGNOSE CASE=12345"
    
    	  You will find the CLUE file on the crashed system in:
    
    	  OpenVMS VAX:		CLUE$OUTPUT:CLUE$LAST_node.LIS
    	  OpenVMS Alpha:	CLUE$COLLECT:CLUE$node_ddmmyy_hhmm.LIS
    
    	  You can generate CLUE files from system dump files (or even CLUE
    	  history file on OpenVMS VAX). See note SPECXN::CANASTA #204 for
    	  more information on how to obtain CLUE files):
    
    	  OpenVMS Alpha:	$ ANAL/CRASH dumpfile
    				SDA> SET OUTPUT clue-file
    				SDA> CLUE CRASH
    				SDA> EXIT
    
    	  OpenVMS VAX:		$ CLUE:==$CLUE
    	  			$ CLUE/OUT=SYS$DISK:[]clue-file  dumpfile
    
    
    +++++ Additional information about CANASTA Mail Server
    
    	  Additional information about the CANASTA Mail Server can be obtained
    	  by sending mail with a subject string of 'HELP' or reading notes
    	  SPECXN::CANASTA #222
    
    
    +++++ Automating crash analysis with 'AutoCLUE for OpenVMS'
    
    	  Customer's with DSNlink for OpenVMS could take advantage of the
    	  'AutoCLUE for OpenVMS' software. This software will be invoked
    	  during boot after a system crash and will automatically send the
    	  CLUE file to the Digital DSNlink Host, where it can be automatically
    	  analyzed through CANASTA. Information about 'AutoCLUE for OpenVMS'
    	  can be found in notes CSC32::AUTOCLUE or in the STARS article:
    
    		[AutoCLUE] Pave the Way for Automatic Crash Analysis
    
    
    +++++ CANASTA Mail Server via Internet Mail
    
    	  Sending AutoCLUE (CLUE) mails to the CANASTA Mail Server via
    	  Internet from a CUSTOMER SYSTEM is also possible, but no replies will
    	  currently be sent back to any address outside the Digital domain
    	  DEC.COM. If desired, the CANASTA Mail Server reply can be
    	  automatically (on a per-customer domain name basis) forwarded to
    	  a Digital-internal mail address (for explanation and registration
    	  see note CSC32::AUTOCLUE #72).