In COMSTAR the emlxs driver is only responsible for maintaining the FC link and 
acting as a pass-through IO driver for COMSTAR.  It is not responsible for 
maintaining the SCSI Target or LUN’s.   That is the responsibility of the 
COMSTAR fct and stmf drivers.  If the driver is online and the link is up and 
you are seeing problems with LUN’s disaapearing I would suggest verifying your 
COMSTAR configuration using sbdadm and stmfadm.   COMSTAR may have disabled a 
LUN or a Target for some reason and it needs to be reinstated.

If you would like me to verify the emlxs driver, you can send me the emlxs 
debug messages along with the stmf debug messages at the time of the problem.

To obtain the complete emlxs driver debug messages just add the following line 
to your /kernel/drv/emlxs.conf file, reboot, recreate the problem and save a 
copy of the /var/adm/messages file on your host.  It will contain the driver’s 
debug messages.  You may want to empty the /var/adm/messages file before 
rebooting so the file is not too big.

log-debugs=0xFFFFFFFF;

Immediately after recreating the problem you can collect the stmf debug 
messages by entering the following command on the command line.  It will place 
a copy of the stmf debug messsages into a file called stmf.log.

echo “*stmf_trace_buf/s” | mdb –k > stmf.log

Once both files have been collected just tar and compress the two files 
together and send them to me.  If the files are too big for an email, then 
contact me by email and I can provide an ftp address for you to use.

My email address is: allen.andr...@emulex.com
-- 
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
storage-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to