I posted earlier this week about a few issues I was having with the COMSTAR FC target. Sumit mentioned that the Emulex target driver was repeatedly logging in and out of the fabric. Here is a snippet of one of the stmf trace buffers that shows this behavior:
emlxs0:0429609: Posting unsol ELS 5 (LOGO) rp_id=11500 lp_id=11100 emlxs0:0429609: Processing unsol ELS 5 (LOGO) rp_id=11500 emlxs0:0429619: Posting unsol ELS 3 (PLOGI) rp_id=11500 lp_id=11100 emlxs0:0429619: Processing unsol ELS 3 (PLOGI) rp_id=11500 emlxs0:0429619: Posting unsol ELS 20 (PRLI) rp_id=11500 lp_id=11100 emlxs0:0429619: Processing unsol ELS 20 (PRLI) rp_id=11500 emlxs0:0429619: Posting unsol ELS 52 (ADISC) rp_id=11500 lp_id=11100 emlxs0:0429619: Processing unsol ELS 52 (ADISC) rp_id=11500 These events match up with the client failures I am seeing, and I am curious if anyone from the Emulex team happens to know what would cause these? The latest stmf trace buffer is attached. Thanks for any insight, - Ryan -- http://prefetch.net
stmftrace.txt.gz
Description: GNU Zip compressed data
_______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
