Conference ssdevo::hsz40_product

824.0. "hsz40 and swcc questions" by HLFS00::VERKERK_R (Robert Verkerk) Fri Mar 28 1997 08:38

Collegues,

The folowing situation. Customer with different HSZ40's on different platforms:
(VMS and Windows NT). No VCS (expensive). No hardcopy console's on HSZ40's.

We are looking if Storageworks Command Console wil do the trick..

But after reading the release notes and seeing the installation video the
following questions remain:

- what does SWCC do with correctable disk errors on the serial port (like ecc
  errors). Does it trigger mail or the pager or anything else? because if you
  have an raid set the disk wich causes problems must be swapped. Not an
    other disk
- does SWCC keep a log file of the serial port of an HSZ40? and can it be seen.
- does SWCC support it if an PC has 1 serial port card with 8 COM ports. So you
  can instal it on 1 PC and monitor 8 HSZ40's.
- does SWCC support it to set up an reverse lat connection on an decserver?
- what to do if you have an dual HSZ config? connect both serial ports???

This al because the HSZ40 logs errors best to the serial port and not to the
operating system. And disk errors are logged on the HSZ40 which services that
disk at that time..

thanks for any reply's..

Robert Verkerk.. MCS gouda Holland...

-currently and near term -


SWCC is a GREAT  Raid subsystem configuration tool.


SWCC does NOTHING to help you see and understand individual drive errors.

SWCC will tell you clearly when a device has hard failed... thats all


-IF HOWEVER

....the host (and adapters and drivers) does NOT SUPPORT good host binary 
     errorlogging

-- and you want to track whats happening at the CLI, 

then... you must use hardcopy
        consoles,  or VCS type of logging!.  You have NO choice.....


The product service plans for HSZ controllers specifically states that
for WINDOWS NT based systems, you need to hang a hardcopy console on the
CLI port of all controllers, or utilize a VCS type capability.


OpenVMS fully supports great error/event logging and 
with DECevent you have the information you need. 

DIGITAL UNIX supports fairly descent error/event logging and 
with DECevent you may have the information you need, provided
patches and driver support is current.

IMHO...For WINDOWS NT,  it has yet to grow up into a real operating system
	(hi bill    8-)  )


gr