Title: | Ask the Storage Architecture Group |
Notice: | Check out our web page at http://www-starch.shr.dec.com |
Moderator: | SSAG::TERZA N |
Created: | Wed Oct 15 1986 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 6756 |
Total number of notes: | 25276 |
Hello, Our DECsafe system is sometime reported following errorlog. What is the "verify sanity" command? Best regards. Yasuhide Nakamura ******************************** ENTRY 65 ******************************** Logging OS 2. Digital UNIX System Architecture 2. Alpha Event sequence number 839. Timestamp of occurrence 26-MAR-1997 09:20:06 Host name oske1 System type register x0000000C AlphaServer 8x00 Number of CPUs (mpnum) x00000004 CPU logging event (mperr) x00000008 Event validity 1. O/S claims event is valid Event severity 1. Severe Priority Entry type 199. CAM SCSI Event Type ------- Unit Info ------- Bus Number 4. Unit Number xFFFF Target = 7. LUN = 7. Not Defined ------- CAM Data ------- Class x33 SIMport Adapter - KZxSA Subsystem x33 SIMport Adapter - KZxSA Number of Packets 2. ------ Packet Type ------ 258. Module Name String Routine Name spo_verify_adap_sanity ------ Packet Type ------ 256. Generic String Adapter didn't respond to 'verify sanity' command
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
6519.1 | SMURF::KNIGHT | Fred Knight | Wed Mar 26 1997 15:01 | 9 | |
The SIMport driver sends the adapter a "hey, how ya doing" command every 30 seconds or so. If it responds, we know that all is well. If not, we log the error you are seeing, and I think we reset the adapter and reissue any outstanding I/Os. The command we send is called "verify sanity". Fred | |||||
6519.2 | thanks! | TKTVFS::NAKAMURA_Y | Wed Mar 26 1997 18:04 | 4 | |
Thank you for your quick response. Yasuhide |