On Friday, 10/28/2016 at 06:05 GMT, Christer Solskogen <christer.solsko...@gmail.com> wrote: > But we are changing the target SAN disks as well. And new SAN switches.
Let me emphasize what Steffen said. Assuming guest Linux A uses two NPIV FCP subchannels (zWWPN_A1, zWWPN_A2) and every storage server has two FC ports (sWWPN1 and sWWPN2), and Linux guest A has two LUNs on that storage server (LUN_A1, LUN_A2), the following relationships exist for EACH guest: One the SAN switch(es): - SAN_zone(zWWPN_A1, sWWPN1) - SAN_zone(zWWPN_A1, sWWPN2) - SAN_zone(zWWPN_A2, sWWPN1) - SAN_zone(zWWPN_A2, sWWPN2) On the storage server - LUN_mask(zWWPN_A1, LUN_A1) - LUN_mask(zWWPN_A2, LUN_A1) - LUN_mask(zWWPN_A1, LUN_A2) - LUN_mask(zWWPN_A2, LUN_A2) In Linux - LUN_define(sWWPN1, LUN_A1) (could be WWID or LUN #) - LUN_define(sWWPN2, LUN_A1) - LUN_define(sWWPN1, LUN_A2) - LUN_define(sWWPN2, LUN_A2) If you change the z WWPNs, you have to update 8 relationships per guest. If you change the storage WWPNs, you have to change another 8 per guest. And if you are actually migrating data to a new storage server and get new WWIDs, then the process of migration is more involved.. But if the Linux, SAN and storage admin teams are willing, go for it! :-) Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems & Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
