VMware Cloud Community
boydd
Champion
Champion
Jump to solution

ESX 3.0.1 Path Selection when using IBM SVC?

This is a quick question:

What Path type selection should I be using if we are connecting ESX 3.0.1 to IBM's SVC?

I know that I would use "Fixed" if I was connecting directly to a DS8100/4100, EVA or Sym and "MRU" for CX etc....

Since there is no official documentation or support out there in regards to this - I was just curious as to what others were doing.

DB

DB
Reply
0 Kudos
1 Solution

Accepted Solutions
williambishop
Expert
Expert
Jump to solution

We've looked at the technology, but not played with it yet. Interested in your review. That said, logically, it would seem like a fit for "fixed" since all of the actual work is done "behind" the svc. Of course, I'm can be(and probably am) wrong.

--"Non Temetis Messor."

View solution in original post

Reply
0 Kudos
12 Replies
williambishop
Expert
Expert
Jump to solution

We've looked at the technology, but not played with it yet. Interested in your review. That said, logically, it would seem like a fit for "fixed" since all of the actual work is done "behind" the svc. Of course, I'm can be(and probably am) wrong.

--"Non Temetis Messor."
Reply
0 Kudos
davidbarclay
Virtuoso
Virtuoso
Jump to solution

We just got an RPQ for a SVC/VM3.01 installation happening by a collegue of mine.

I'll try and find out how he is going with it and report back if i can.

Dave

boydd
Champion
Champion
Jump to solution

We just got an RPQ also. So far, testing has gone fairly well accept for an issue with the vmware-hostd process(es) going a little hay-wire during certain times during a rescan process. I'm thinking that us using "MRU" may be the culprit. We are working with IBM right now to see what the best config should be. I'm assuming it should be "Fixed" but want to know from IBM what will be supported - SVC is a different animal than just using the standard DS config for ESX.

DB

DB
Reply
0 Kudos
Jwoods
Expert
Expert
Jump to solution

Been using 3.0.1 with SVC and an 8300 since December. I use Fixed paths to the disk. Have not had any issues and it works quite well. I actually wondered this originally assuming the final answer would be fixed paths. Testing with MRU mainly brought lun to lun copy issues. Every now and then a lun would drop from the host. However, I was also behind in the SVC firmware so this didn't help.

Fixed paths has been quite stable. I just wish VMware would speed up the certification of SVC.

davidbarclay
Virtuoso
Virtuoso
Jump to solution

I just forwarded this thread on to my collegue for comment. He isn't a VMware engineer, but has extensive storage/svc experience.

If he has something to add I am sure he will. Don't be shy Rob Smiley Happy

Dave

Reply
0 Kudos
boydd
Champion
Champion
Jump to solution

I just got my answer from IBM via our RPQ - "Fixed" pathing is correct choice. ESX 3.0.1 should treat the SVC just as if it were connecting to a DS. Looks like we'll be switching things around today from MRU to Fixed. Smiley Happy

Thanks for everyone's input.

DB

DB
Reply
0 Kudos
MBrownHenn
Contributor
Contributor
Jump to solution

We have an RPQ in with IBM as well regarding the supportability of ESX 3.0.1 connecting to SAN storage through SVC. VMware says it is not supported, but they are working on it. IBM also says they are working on it and should have a GA release this summer.

How it is affecting us: randomly during either manual or DRS vmotion migrations there is a disk lock error, the receiving host cannot open the .vmdk file to the VM and the migration fails.

Reply
0 Kudos
boydd
Champion
Champion
Jump to solution

Hmmm - haven't seen this (yet). What build of ESX 3.0.1 are you using under the RPQ?

DB

DB
Reply
0 Kudos
davidbarclay
Virtuoso
Virtuoso
Jump to solution

This might be helpful on the SVC. Procedure from IBM on VI3 support on SVC:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\~~

Process to Obtain Support for SVC with VMware ESX 3

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\~~

We are announcing that, pending full GA-level support in VMware ESX 3, IBM and VMware have agreed to an RPQ process to support SVC with VMware ESX 3 configurations.

Support for our joint customers will be granted on a per customer per configuration basis through the IBM SVC RPQ process. No "general" or "blanket" approvals will be granted. VMware will participate with the SVC team in the RPQ process for the approval of each customer request and will have the RPQ approval number and customer name for their records.

At this time, RPQ approvals will be given only for SVC configurations with VMware ESX 3, Windows 2003 guest hosts, and QLogic HBAs. Other guest OS versions and HBAs will be added to the supported configurations as testing is completed: we will issue further flashes to keep you informed.

Configuration restrictions will be listed in the RPQ approval notice, which will also direct customers to the appropriate place to pick up the VMware ESX 3 patches to use until GA-level support is available.

Until GA-level support is available from VMware, all customer service for SVC configurations with VMware ESX 3 should be requested via the IBM Support Center, using the customer's approved RPQ number even if the customer believes the problem is with VMware ESX and not with SVC.

Customers will be expected to migrate to the final VMware product version that contains all fixes for use with SVC within 90 days of its GA. The GA of this support will terminate the interim RPQ support described above. VMware tell us that they expect GA-level support to be available in early 3Q2007. VMware has made this migration a requirement for continued customer support following their GA release.

Account teams should use the SVC RPQ process to request support for exact configurations of SVC with VMware ESX 3 including specifically the guest OS version and HBA. Existing RPQs for SVC/VMware support do not need to be resubmitted: they will be processed and account teams will be contacted if more information is needed.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\~~

Dave

Reply
0 Kudos
meistermn
Expert
Expert
Jump to solution

Can SVC now be used over two location, which have a 30 KM distance.

Laste time in Sep. 2006 IBM told us I cannot do this, like the netapp metrocluster can do this.

Reply
0 Kudos
MBrownHenn
Contributor
Contributor
Jump to solution

David,

thanks for the information. Could you post a link to an official announcement where you found this information? We have an RPQ with IBM, so we will work with them for support of our file locking issues.

Thanks,

Mike

Reply
0 Kudos
davidbarclay
Virtuoso
Virtuoso
Jump to solution

It was actually an email from IBM to partners. Talk to your IBM rep is my best guess.

Dave

Reply
0 Kudos