Title: | HSZ40 Product Conference |
Moderator: | SSDEVO::EDMONDS |
Created: | Mon Apr 11 1994 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 902 |
Total number of notes: | 3319 |
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
859.1 | SMURF::KNIGHT | Fred Knight | Fri May 02 1997 13:20 | 15 | |
I know of 2 options: 1) The SWCC product. It is an online monitor for the HSZ* much like the SWXCRMON program. It does require a Windows or NT system on the network (last I knew anyway). 2) Look at the Digital UNIX error log. As of V4.0A virtually all HSZ events are put into the error log (you do need DECevent to understand them however; uerf just dumps the HSZ data in hex). For V3.2G and earlier, then get the latest cam_disk.o patches (which includes this new logging code as well). Fred Knight | |||||
859.2 | SSDEVO::T_GONZALES | Fri May 02 1997 16:45 | 4 | ||
I agree with fred, the unix error logging will show errors that occur on devices on the hsz, even if they are part of a raid set. you could use tip, but it is very expensive in terms of cpu. | |||||
859.3 | Thanks for your inputs... | LEMAN::MARTIN_A | Be vigilant... | Mon May 05 1997 10:03 | 10 |
Thanks for your inputs. The cam_disk.o patch was provided a few days ago, hope it'll fit my customer needs, he'll run emergency tests soon so I'll update this note if we encounter any surprise by then ... Cheers, ============================ Alain MARTIN/SSG Switzerland |