iStorage HA works fine on Xenserver 6.5 (Creedence)

Windows iSCSI SAN, Linux iSCSI SAN, Mac OS X iSCSI SAN and Virtual Native SAN.
Post Reply
webguyz
Posts: 35
Joined: Fri Dec 07, 2012 5:50 am

iStorage HA works fine on Xenserver 6.5 (Creedence)

Post by webguyz » Tue Jan 13, 2015 2:23 pm

Xenserver 6.5 (Creedence) was released today. I upgraded one of my test servers that was connected to my iStorage HA pair running 4.05 and it was fine. I copied over the multipath.conf that I was using with Xenserver 6.2 and everything was good.

Haven't run any benchmarks but performance definitely feels zippier creating VM's and doing VM migrations.

Olivia (staff)
Posts: 205
Joined: Thu Nov 05, 2009 5:52 pm
Contact:

Re: iStorage HA works fine on Xenserver 6.5 (Creedence)

Post by Olivia (staff) » Mon Jan 19, 2015 10:41 pm

Thank you Sir,
We will now start work with XenServer 6.5.
KernSafe Support Team
iSCSI SAN, iSCSI Target, iSCSI initiator and related technological support.
[email protected]

webguyz
Posts: 35
Joined: Fri Dec 07, 2012 5:50 am

Re: iStorage HA works fine on Xenserver 6.5 (Creedence)

Post by webguyz » Thu Jan 22, 2015 7:30 pm

May have spoken too soon. When I tested 6.5 I used an existing SR. Trying to create new SR and I'm getting some weird symptoms where I am getting errors trying to copy files from other SR's after creation and also can't attach some of my hosts. I used the same multipath.conf as in 6.2.

defaults {
polling_interval 10
max_fds 8192
user_friendly_names no
}
devices{
device {
vendor "KernSafe"
product "*"
path_checker "tur"
path_grouping_policy multibus
failback immediate
}
}

.

Also, If I have multiple targets defined they are all LUN 0, correct?

Stopped trying to create new SR. Could you guys test to see if 6.5 can create a new SR and then copy files to it?

Thanks!

webguyz
Posts: 35
Joined: Fri Dec 07, 2012 5:50 am

Re: iStorage HA works fine on Xenserver 6.5 (Creedence)

Post by webguyz » Fri Jan 23, 2015 11:29 am

Never Mind. Too much going on and I had some fw rules not right.

:oops:

Post Reply