Many thanks to Roger, Alan and Roberto for pointing me in the right direction.
The actual solution to getting the needed info was as simple as the following line of commands:
dia | grep -i cam | more
or you could do the following:
dia | grep -i cam > scsicam.err
so you could review the data output at a later time if needed.
Alan's reply was so good, I wanted to include it as part of the summary:
"
Most device drivers write their errors (indirectly) to a
binary error log file in /var/adm. To format the error
log you can use DECevent (the dia command) or uerf. Uerf
stopped being supported around the time the first 2100
was released, but it can format errors from the SCSI driver.
For HS family subsystems it won't be able to decode some
of the more interesting messages though. DECevent, where
available, is on one of the Associated Products CDROMs.
Some new systems use an error log format that neither
DECevent nor uerf can untangle. On these systems you
have to use Compaq Analyze, which should also be on one
of the Associated Products CDROMs.
If you use uerf to format the error log, be sure to use
the option "-o full". All the default format tells you
is that there was an error and what bus, target and LUN
it was on."
Thank You,
Dennis Peacock
> -----Original Message-----
> From: dpeaco - Dennis Peacock
> Sent: Thursday, March 23, 2000 1:17 PM
> To: Managers Tru64 Unix (E-mail)
> Subject: SCSI CAM Errors
>
> I am new to Tru64 and Digital Equipment. I am needing to find out
> how to monitor or check on scsi cam errors. I am sure I am missing
> something simple here but I can't seem to get over the "hump".
> Running 4.0f on an Alpha 8400 server with 3TB of StorageWorks DASD.
> I will post the summary once the answer is received.
>
> dpeaco_at_acxiom.com
>
> Thank You,
> Dennis Peacock
>
Received on Thu Mar 23 2000 - 20:07:01 NZST