On Tuesday, 08/18/2015 at 08:50 EDT, Grzegorz Powiedziuk <gpowiedz...@gmail.com> wrote:
> Got it! Thank you so much for spending time on explanation. That definitely > helps. You're welcome. > The bottom line is - I can ?over provision? (or kind of thin provision) fcp > channels as long as I keep below 32 attached paths per chpid and make sure that > I do EQIDs vertically only - separate EQID for every set of paths on two > chpids (one on each system). That's what I would do. Then I would open an RFE to ask for CP to handle this automatically. It may be as simple as CP noting the chpid distribution on the source side and attempting to match that on the target. I.e. If guest #1 was using a PURPLE FCP on chpid X and guest #2 was using a PURPLE FCP on chpid Y, then CP could map them to PURPLE FCP subchannels on chpids X' and Y' on the target (if available). Further, remember the mapping and continue to use it. That way the guests will end up with the same subchannels-per-chpid distribution on the target. This technique also applies to OSA and HiperSockets, where separation is enforced (only) at the chpid boundary and you have explicitly chosen devices based on their chpid association. You don't want guests that were communicating on the same chpid on system A to suddenly be on separate chpids on System B. 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/
