Hi Lokanadham,

There's something wrong in solaris fcoe target messages,
we get some data frames that belong to non-existent exchanges.

Would you like to tell me your setup and topology?
I'd like to reproduce the problem in our lab, too.

Thanks,
-Reed

Lokanadham P-TLS,Chennai wrote:

Hi reed & Robert,

 

            Thanks for your reply.

 

            With solaris target (BUILD 121) data traffic is working fine.

 

            We did the verification of data traffic by using dd command and the data verification was successful.

            dd bs=64k count=10000 if=/dev/urandom of=/tmp/patt

dd bs=64k if=/tmp/pattrect of=/dev/sdb oflag=direct

dd bs=64k if=/dev/sdb of=/tmp/read count=10000 iflag=direct

cmp /tmp/patt /tmp/read.

           

Robert:  I enabled the pause by using ethtool.

 

Out put of the ./dcbcheck.sh is:

                        Unable to communicate with the DCB daemon (dcbd) or DCB capable driver.

 

           

            I did the make file system on the discovered LUN. But we are unable to mount the discovered LUN.  

            Initiator and target dmesg outputs are attached with this mail.

           

           

 

Thanks

Lokanadham


<<attachment: Reed_Liu.vcf>>

_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to