DSS6 Beta and XEN server 5.5

Printable View

06-17-2009, 11:13 AM
urvik

DSS6 Beta and XEN server 5.5

Hello All,

I have XEN server 5.5 essentials and DSS6 Beta. Both are running on DELL Poweredge 2950 server.

I created target and assigned one LUN to it. When I try to attach iSCSI LUN to XEN, I am getting error "No such device. Check your settings and try again".

I can able to discover IQN and LUN on XEN server and it is showing correct IQN and LUN. But when I click finish button it is starting scanning for LVM over iSCSI SRs on IP_ADDRESS_of_DSS" and after some time it is giving me error that "No such device. Check your settings and try again".

I created iSCSI Logical volumne using file-IO. I tried with block IO also but I got same result.

I am able to connec DSS6 iSCSI LUN to windows vista with Microsoft iSCSI initiator. So is ther any issue with XEN and DSS6?

Any help is appriciated.

Thanks
06-17-2009, 02:50 PM
To-M

Thanks for the testing on this. We got your ticket from the support team :) - can you send the logs from the DSS V6 to them.
06-17-2009, 02:51 PM
To-M

What was the LUN # you used - test with LUN 1 not 0.
06-17-2009, 03:30 PM
To-M

Engineers would like to see if you can test with the IETd instead of the default SCST - to change this go to the console then enter CTRL + ALT + W then Tuning options then iSCSI daemon then iSCSI solution then select IETd - you will lose connections from a reset and you will need to reconnect from the inititator side.
06-17-2009, 04:06 PM
rogerk

hi,

try to recreate the volumes. i had the same problems with xen 5.0 and dss5.

roger
06-18-2009, 07:48 AM
urvik

After changing to IETD. I can able to access from XEN server.

Thanks for help,
Urvik
07-03-2009, 04:41 AM
tjk

Quote:

Originally Posted by urvik

After changing to IETD. I can able to access from XEN server.

Thanks for help,
Urvik

LUN0 and LUN1 still not working with latest DSS 6 and Xenserver 5.5. Any updates Todd?

Tom
07-03-2009, 08:35 AM
urvik

I was able to connect with DSS6 update3 beta with XEN5.5 without any problem. But I updated to DSS6 full version and I am able to connect to XEN 5.5 with IETD but I am not able to create any VM on the storage.
07-03-2009, 07:41 PM
To-M

If you all are using the latest version of DSS V6 with File IO and IET this should work. I want you all to send in the to support. We need to start collecting the data and run some tests then we can post on the KB once engineers are able to see what is going.
09-21-2009, 08:34 AM
kdsnice

Quote:

Originally Posted by To-M

Engineers would like to see if you can test with the IETd instead of the default SCST - to change this go to the console then enter CTRL + ALT + W then Tuning options then iSCSI daemon then iSCSI solution then select IETd - you will lose connections from a reset and you will need to reconnect from the inititator side.

Thenks, this solution is help me, but after reboot DSS V6 physcial machines, XenServer warns that the dss v6 iSCSI stroage cannot be reconnected, therefore, I try to reconnect it. But while I try to connect the iSCSI stroage, after I type in IP and discovered the target IQN, then I try to discover the LUN attached to the IQN, then it fails, the error message on XenServer console is "no LUNs were found on IP. Check your settings and try again."

The same problem with openfire server, and this problem was resolved in this http://community.citrix.com/display/...+Openfiler+2.3
But, what can i do with DSS V6?

Thanks!
09-22-2009, 03:23 PM
To-M

Engineers reviewed the link and it seems it is not related. the problem with XEN is that SCST does not work with it. IET will work properly.
09-25-2009, 10:09 AM
kdsnice

Quote:

Originally Posted by To-M

Engineers reviewed the link and it seems it is not related. the problem with XEN is that SCST does not work with it. IET will work properly.

Thank for your answer! I'm was changed "iSCSI solution type" the IETd instead of the default SCST and create new iSCSI volume with type "File I/O". In XenCenter I was added new storage repository is type iSCSI without any problem. BUT! Every time, after reboot DSS V6 server, iSCSI storage state is "BROKEN" and I can't "Rapair Storage Repository". I must go to "web_interface_dssv6server-CONFIGURATION-iSCSI target manager-Targetsiqn.2009-09:dss.target2" and press "-" action, operation was performed, press "+" action in "Target volume manager". After these actions I can "Rapair Storage Repository" in XenCenter. Help me please resolve this trouble!
09-25-2009, 04:19 PM
To-M

Can you rescan the connection from the XEN server side to reconnect when rebooting the DSS server?
09-28-2009, 08:51 AM
kdsnice

Quote:

Originally Posted by To-M

Can you rescan the connection from the XEN server side to reconnect when rebooting the DSS server?

If DSS V6 server reboot and XEN servers do not reboot, in XenCenter state of "iSCSI virtual disk storage" is OK, but it is no true! Because, any virtual computer on "iSCSI virtual disk storage" can not be started. In addition, if try reattach storage repository in in XenCenter, I get error "Scanning for LUNs on iSCSI filer DSS_SERVER_IP_ADDRES. No LUNs were found on DSS_SERVER_IP_ADDRESS. Check your settings and try again." To resolve this I must go to "web_interface_dssv6server-CONFIGURATION-iSCSI target manager-Targetsiqn.2009-09:dss.target2" and press "-" action, after operation was performed, press "+" action in "Target volume manager".
09-28-2009, 03:20 PM
To-M

Just to make sure to the following you are not using the Auto Failover and that IET is being used here. If this is the case send in the logs to support@open-e.com as there might be another initiator that could be connected to the DSS V6 preventing the XEN server to connect to the LUN.
09-28-2009, 03:53 PM
kdsnice

In "CTRL + ALT + W -> Tuning options -> iSCSI daemon options -> iSCSI solution -> IETD ISCSI" is selected.

What is " Auto Failove" where this option must be on Xen side or on DSS side?

Quote:

Originally Posted by To-M

might be another initiator that could be connected to the DSS V6 preventing the XEN server to connect to the LUN.

I am using two xen server combined in the POOl may be trouble in this...?
09-28-2009, 04:00 PM
To-M

The Auto Failover is on the DSS V6 side and I was thinking that maybe it was incorrectly setup for the SCSI ID's or Target Name and LUN# that has to match. If your not using this feature then we can then look at the logs to see if two initiators are accessing the LUN but logs would be needed to see or you can look into the test.log file and search for the session heading to see what it connected.
09-28-2009, 04:25 PM
kdsnice

Where I can find this file "test.log" and how I can take logs with DSS a server?
09-28-2009, 04:31 PM
To-M

Go to Status > Hardware > Logs and download the log file then use a program like Winrar to open there you will see the file called test.log
10-05-2009, 03:34 PM
mxcreep

I can confirm this behaviour...after rebooting the DDS V6 box the storage isn't attached to my Xenserver nodes...repairing doesn't work. I also use IETD. What works for me is resetting the iscsi connections in maintenance and repair the storage repository after that... This seems to work until now but it is a bit annoying...
11-22-2009, 05:59 PM
webguyz

Came across this post in xenserver forum and was wondering if anyone had tried it. They were referring to another san solution.

Quote:

Hi,
I was able to find workaround for this problem. If you want to use scst as iscsi solution do:

use ietd for initialization of lun and add it as SR
change from ietd to scst
it schould work, from some reasons same device under ietd can be added and initialized but not under scst, hoever once that device is added as SR you can normaly use scst.

To add any others devices you will have to change iscsi daemon to ietd.

Best regards,
Bartosz Jaskiewicz