With the newer 4gig HBA release, Sun and QLogic have support for the scli and
SANsurfer utilities to perform some limited operations on qlc driver controlled
HBAs. Now those two utilities use a passthrough IOCTL to communicate with
devices visible through the HBAs.
I would check to see if the scli package is installed:
# pkginfo -l QLScli
If the scli utility is being run, it will send SCSI commands to any devices the
HBAs have access to. Make sure that scli is not being executed at the time the
SAN errors are seen.
Also check for the SANsurfer agent on this host. The process name is qlremote.
If it is running, then shut it down for some time as a test:
# /etc/rc3.d/S99qlremote stop
You could also check for any other processes that are using the SNIA HBA
interface using this ksh snippet:
for i in $(nawk -F'"' '/qlc/{ print $2 }' /etc/path_to_inst|egrep -v
"fp|sd|st|ses") ; do
fuser /devices${i}:devctl
done
If qlremote is running, the ksh snippet will list the process id of qlremote.
-- Lyle --
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
