For EMC vmax1 and vmax2 san we have 2 fcp addresses dedicated to the server/guest id (1 on each of 2 facbrics) 1 zfcp_disk_configure command for each lun - 1 for each fcp address So 2 total zfcp_disk_configure commands - 1 per zfcp device - 1 per fabric
For IBM XIV the doc I have found indicates XIV supports 3 paths - not sure what you mean by 6 interface modules- but If still have 2 zfcp devices - does that mean I can do 3 zfcp_disk_configure's per zfcp device ? We are not NPIV (wish we were) Also - Mark I've never used yast for san configuration Have had issues with yast and Hipersockets with SLES11 (have not had time to debug and call in - have to verify not caused by bad statements in SLES10 configs before upgraded to 11) But really was sticking with commands partly due to need to recover san at DR site (DR tests use lun snap copies with different hex lun values). Of course I wonder if XIV will be same- I need to talk to san support folks . We have no test san luns - which does not help - trying to get one. Maybe you know something I don't know (I am sure you do). Maybe there is a way to use yast (we can't use YaST any more) to define san at primary and DR sites - I am open for suggestions on that too. Ann Smith -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Offer Baruch Sent: Tuesday, September 23, 2014 12:52 PM To: [email protected] Subject: Re: SLES and XIV san One more thing... When using xiv it is important to utilize all 6 interface modules (if you have all 6 of them). Meaning 6 paths to the xiv. 3 from each fabric. Use at least 2 zfcp devices... 1 from each fabric Offer Baruch On Sep 23, 2014 7:42 PM, "Offer Baruch" <[email protected]> wrote: > Hi... > If you are using npiv you can use the following zfcp module parameter: > zfcp.allow_lun_scan=1 > This will automatically add the zfcp luns automatically. > All you need is to set the zfcp device online and all luns that are > available through the san will be there dynamically. > > Really no need to define them one by one. > > Offer Baruch > On Sep 23, 2014 5:13 PM, "Mark Post" <[email protected]> wrote: > >> >>> On 9/23/2014 at 08:45 AM, "Smith, Ann (CTO Service Delivery)" >> <[email protected]> wrote: >> > We need to migrate all san luns from EMC vmax2 to IBM XIV. >> > I've been looking for doc on how to configure XIV luns with SLES11. >> > For example - are multiple zfcp_disk_configure commands required? >> >> I would say that if you're going to be adding (and eventually >> removing) a fair number of LUNs from each guest, then using the YaST >> dialog would probably be more efficient for you. If ti's only one or >> two, then manually running a zcfp_disk_configure command for each of them >> won't be too bad. >> >> > How many fcp addresses are dedicated to VM guest? >> >> Only you can decide how many there should be, or discover how many >> there are currently. >> >> > I am a bit confused about the additional paths. >> >> Which additional paths are you referring to? >> >> >> Mark Post >> >> --------------------------------------------------------------------- >> - For LINUX-390 subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO LINUX-390 >> or visit >> http://www.marist.edu/htbin/wlvindex?LINUX-390 >> --------------------------------------------------------------------- >> - For more information on Linux on System z, visit >> http://wiki.linuxvm.org/ >> > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ************************************************************ This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. ************************************************************
