Re: FCP SCSI support on z/VM in basic mode
Hi Don, What you have looks fine, though I have a few minor points to offer: - Newer IBM DASD contains an Access Control List that identifies which HOST WWPNs (associated with the FCP CHPID) can access which LUNs within the box, so you won't always be able to get to every LUN in the box as you have described below. - Newer processors (I'm thinking z9 here) can have a unique WWPN per FCP subchannel, such that the aforementioned ACL can restrict LUNs to a particular guest rather than everyone using the same CHPID. See http://www.redbooks.ibm.com/abstracts/redp4125.html for more information on this feature. - The LOADDEV command also exists as a CP directory statement. So you could bypass the IPL of CMS by putting the LOADDEV information in the directory entry for your Linux guest, and have it IPL the FCP subchannel instead of 190. What you have will work, but you don't need to fire up CMS to get there. Hope this helps you out some. Good luck! Regards, Eric Eric Farman z/VM I/O Development IBM Endicott, NY (607)429-4958 (tie 620)
Re: FCP SCSI support on z/VM in basic mode
I think I'm beginning to understand the use of a SCSI formatted SHARK. If I'm correct, the devices defined in the IOCP for the FCP chpids are actua lly just communications paths to the SHARK. Any address defined on the chpid can access any LUN on the SHARK. I think my steps would be: 1) Attach the SHARK through a fiber switch to the processor. 2) Configure the SHARK with Luns that are set up as VM Host. 3) Get the WWPN from the SHARK configuration panel. 3) Update the IOCP to reflect 240 addresses on the FCP chpids. 4) Vary on the 240 addresses associated with the SHARK to VM. 5) Dedicate any unique address from the 240 addresses to the LINUX guest. 6) Update the LINUX guest with the address and WWPN. 7) If the LINUX guest is to IPL from the SCSI configured SHARK, make sure the processor has the appropriate feature installed. 8) In the CMS profile exec on the LINUX guest, set the LOADDEV with the SHARK SCSI information. 9) IPL using the dedicated address. Please feel free to correct me if I have missed significant steps or have something wrong.
Re: FCP SCSI support on z/VM in basic mode
Are you running this direct or through a SAN switch? It doesn't make all that much difference, but a SAN switch also gives you direct access to Fibre connected tapes and such. (If your OS supports them.) I have this on a z800 - don't know if would help you much on a z9* machine though. Also, check out Steve Wilkins page. Kind of VM specific, but VERY helpful. http://www.vm.ibm.com/devpages/wilkinss/ -Paul --- Begin Message --- I'm working on setting up a SHARK connected via fiber (FCP)on a z900 as a SCSI device. Our z900 runs in basic mode (no LPARs). Is this feasible or do you have to run in LPAR mode. Also, do you have to define an EDEVICE or just set the loaddev? I've looked at several redbooks but haven't found exactly what I'm looking for. Is there an example somewhere that shows setting this up from start to end? Just a simple example showing the IOCP, HMC screens, VM CONFIG, directory entry, etc. --- End Message ---
Re: FCP SCSI support on z/VM in basic mode
There is no redbook (yet) that includes native z/VM SCSI support. However, check out the WAVV (May) 2005 SCSI presentation on http://www.vm.ibm.com/devpages/WILKINSS/ as a guide. You can get more details on the commands and utilities mentioned (in my presentation) in the CP Command and Utility Reference. There is also a chapter on our VM SCSI support in the VM CP Planning and Administration Guide that would be good to look at. If you don't define the EDEVICE in system config, a single path EDEVICE will be created for your SYSRES. If you want a multipath device (for your SYSRES), you must define the EDEVICE in the system config file. Either way, you must give an EDEVICE number for the system to use on the SAPL PDVOL parameter as explained in the WAVV presentation. My peers tell me that the support will work in basic mode. Regards, Steve. Steve Wilkins IBM z/VM Development "Don W." <[EMAIL PROTECTED] COM> To Sent by: The IBM IBMVM@LISTSERV.UARK.EDU z/VM Operating cc System <[EMAIL PROTECTED] Subject ARK.EDU> FCP SCSI support on z/VM in basic mode 02/21/2007 04:12 PM Please respond to The IBM z/VM Operating System <[EMAIL PROTECTED] ARK.EDU> I'm working on setting up a SHARK connected via fiber (FCP)on a z900 as a SCSI device. Our z900 runs in basic mode (no LPARs). Is this feasible or do you have to run in LPAR mode. Also, do you have to define an EDEVICE or just set the loaddev? I've looked at several redbooks but haven't found exactly what I'm looking for. Is there an example somewhere that shows setting this up from start to end? Just a simple example showing the IOCP, HMC screens, VM CONFIG, directory entry, etc.
FCP SCSI support on z/VM in basic mode
I'm working on setting up a SHARK connected via fiber (FCP)on a z900 as a SCSI device. Our z900 runs in basic mode (no LPARs). Is this feasible or do you have to run in LPAR mode. Also, do you have to define an EDEVICE or j ust set the loaddev? I've looked at several redbooks but haven't found exactl y what I'm looking for. Is there an example somewhere that shows setting th is up from start to end? Just a simple example showing the IOCP, HMC screens , VM CONFIG, directory entry, etc.
