FC Target

[To-M]

Disregard "Then use the FC Initiator from the QLogic" this was meant for the Setup > FC for selecting I (initiator from the QLogic) or T (Target) - Typo for got to delete it..

I have asked our engineers to look into this as others are receiving the same issue. Hopefully next week we can resolve this.

[gharding]

Thanks for all your help, I have tried many things none of which have worked I will wait for your the engineers to look at it. One question when creating a FC volume must it be initialized or is this only relevant to iscsi volumes. I have noticed that when creating new iscsi volumes the performance for clients already connected to iscsi volumes decreases substantially while the new volume is initialized.

E.g using iometer we are getting a combined read write of 145MB/s but when running the same test while creating a new iscsi volume the performace drops to 15MB/s. Just thought I would share my experiance.

Gavin

[To-M]

Try to allow the initialization to complete first before tests. Also what was the system status from CPU readings.
When systems saw performance issues was the GUI of the DSS slow or not. Many times overhead or bottlenecks could be some other area. Send in the logs to engineering to verify speeds of drives are other cause. iSCSI and FC Volumes are given the choice to use the Initialization.

Notes from manual:

This option is available when creating iSCSI volume(s), its for security reasons. iSCSI volume will be initialized after creation process. When iSCSI volume is initializing then 'enque' button will show up. With this button you can send iSCSI volume that is initializing to the back of the initialization queue. Every volume that is waiting in queue for initialization can be also send to the back of queue, the same as volume that is already initializing.

[paul2kl]

Was this ever resolved, only i can't get it to work...
Open-e creates the Lun, and presents it.

Trying to get vmware esx 3.01 to see it, but it never see's the Lun at all.. Not using a FC switch at present so it is a direct connection between the boxes.

paul

[To-M]

Not yet as the issue is with 4GB FC cards. We need more time but the 1 and 2GB work.

[gharding]

Just to let you know we have the Fibre channel target working in DSS but had to down grade our Fibre cards to 23xx 2GB cards. I have been told that the 4GB cards are being tested and fingers crossed there may be a fix at some point in the near future maybe august sometime.

The performance we are getting at the moment is very good we are getting an average combined read/write of 265MB/s using iometer/10 workers/ 10 outstanding io's we ran the same test on a dell AX150 FC and the peformance was poor compared to open-e.

Cant wait for the four GB card to be available.

Cheers

Gavin

[To-M]

Thanks for update!!! This is great when you report these stats!

[tjk]

Garvin,

Any special tricks? I'm having a heck of a time using the latest DSS demo CD to talk to a esx 3.0.2 cluster using a qla2342 controller in the dss server (dual port 2gb). I've got the ports set to target (although my sanbox switch shows them as initiator, seems odd), the lun presented in fc manager, and my esx nodes defined in the wwn manager section.

I got iSCSI working fine without problems. I wanted to redo the testing using 2gb FC cards, I just cannot get the dss luns to show up on the esx nodes, they are all zoned properly, etc.

Any ideas?

Tom

Just to let you know we have the Fibre channel target working in DSS but had to down grade our Fibre cards to 23xx 2GB cards. I have been told that the 4GB cards are being tested and fingers crossed there may be a fix at some point in the near future maybe august sometime.

The performance we are getting at the moment is very good we are getting an average combined read/write of 265MB/s using iometer/10 workers/ 10 outstanding io's we ran the same test on a dell AX150 FC and the peformance was poor compared to open-e.

Cant wait for the four GB card to be available.

Cheers

Gavin