Re: Mapping an Emulated DASD device to an SVC LUN number
Thank you all for your response, but it looks as though this one was the winner!!! Special thanks to Mr. Romanowski and yes, the mystery lies within the SCSI_id and just converting that number to hex. Thanks again, Mark Wiggins University of Connecticut -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Romanowski, John (OFT) Sent: Tuesday, May 25, 2010 10:32 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Mapping an Emulated DASD device to an SVC LUN number The SVC command line command svcinfo lshostvdiskmap might list the information you're looking for. Look online for the manual IBM TotalStorage SAN Volume ControllerCommand-Line Interface User's Guide Here's sample output (probably folded across two lines); the SCSI_id column is the LUN's hex id in decimal (decimal 102 below is hex LUN id 0066) svcinfo lshostvdiskmap Z10_P1-T1Linux id name SCSI_idvdisk_id vdisk_name wwpn vdisk_UID 240 Z10_P1-T1Linux102186 Z_TZ2BF152_V2 5005076401E2893A 60050768018180762800062F 240 Z10_P1-T1Linux103667 Z_TZ2BF152_V3 5005076401E2893A 600507680181807628000633 (the SVC's SCSI_id column is not to be confused with the value given by linux's scsi_id command. I found that prefixing 3 to the SVC's vdisk_UID is the same value returned by linux's scsi_id command)
Mapping an Emulated DASD device to an SVC LUN number
We're looking to migrate to a new z/10 and we've come up with an issue that hoping someone out there knows how to resolve. A while back when we installed our SVC (2145) we lost the ability to see the real LUN number that was being assigned to our z/VM system as an emulated (9336) device. On the SVC side on things you see a 16 character LIN id like this; 013D (which we'd only use the last 4 of 015E). When you run the SCSIDISC command on z/VM, the LUN that shows up in z/VM in just the next number in sequential order (e.g. if it was the 11 LUN allocated, it would have a LUN id of 000A). Are there any commands from z/VM that can be issued to give you the LUN id as defined within the SVC? A command like q edev e011 details shows EDEV E011 TYPE FBA ATTRIBUTES 2145 VENDOR: IBM PRODUCT : 2145 REVISION: BLOCKSIZE: 512 NUMBER OF BLOCKS: 83886080 PATHS: FCP_DEV: A200 WWPN: 50050768011035EE LUN: 000A PREF CONNECTION TYPE: SWITCHED Mark Wiggins University of Connecticut 860-486-2792
Re: Mapping an Emulated DASD device to an SVC LUN number
Hi, Mark. Have you thought about maybe installing one of the free Linux distros for the z Architecture (openSuSE, maybe) and using its set of SCSI commands (lsluns, lszfcp, etc.) to get the information you need? DJ On 05/25/2010 02:45 PM, Wiggins, Mark wrote: We're looking to migrate to a new z/10 and we've come up with an issue that hoping someone out there knows how to resolve. A while back when we installed our SVC (2145) we lost the ability to see the real LUN number that was being assigned to our z/VM system as an emulated (9336) device. On the SVC side on things you see a 16 character LIN id like this; 013D (which we'd only use the last 4 of 015E). When you run the SCSIDISC command on z/VM, the LUN that shows up in z/VM in just the next number in sequential order (e.g. if it was the 11 LUN allocated, it would have a LUN id of 000A). Are there any commands from z/VM that can be issued to give you the LUN id as defined within the SVC? A command like q edev e011 details shows EDEV E011 TYPE FBA ATTRIBUTES 2145 VENDOR: IBM PRODUCT : 2145 REVISION: BLOCKSIZE: 512 NUMBER OF BLOCKS: 83886080 PATHS: FCP_DEV: A200 WWPN: 50050768011035EE LUN: 000A PREF CONNECTION TYPE: SWITCHED Mark Wiggins University of Connecticut 860-486-2792 -- Dave Jones V/Soft www.vsoft-software.com Houston, TX 281.578.7544
Re: Mapping an Emulated DASD device to an SVC LUN number
Hi Mark, When you say the real LUN number, are you referring to the SVC's MDISK LUN ID, which is representing the backing storage? If so, I do not believe any host OS has the ability to see these identifiers, as the SVC only uses that internally, as part of his MDISK-to-VDISK mapping. This is because the data itself can be moved from one (or more) physical LUNs to others as part of data migration or balancing or what-have-you, and so these LUN identifiers are not interesting to the host. (For the record, MDISK is SVC's term for Managed Disk. It is not to be confused with the minidisk definition of MDISK that is common in VM.) The VDISKs themselves are mapped to the connected hosts, and it is the resulting LUN identifier for these devices that the OS will see in the form of x000A or whatever. In the VDISK-to-Host mapping panel of the SVC console, there is a SCSI ID column (at least in the version I have available to me), that is the **decimal** value of that LUN ID. Regards, Eric Eric Farman z/VM I/O Development IBM Endicott, NY (607)429-4958 (tie 620) From: Wiggins, Mark mark.wigg...@uconn.edu To: IBMVM@LISTSERV.UARK.EDU Date: 05/25/2010 03:46 PM Subject: Mapping an Emulated DASD device to an SVC LUN number Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU We’re looking to migrate to a new z/10 and we’ve come up with an issue that hoping someone out there knows how to resolve. A while back when we installed our SVC (2145) we lost the ability to see the “real” LUN number that was being assigned to our z/VM system as an emulated (9336) device. On the SVC side on things you see a 16 character LIN id like this; 013D (which we’d only use the last 4 of “015E”). When you run the SCSIDISC command on z/VM, the LUN that shows up in z/VM in just the next number in sequential order (e.g. if it was the 11 LUN allocated, it would have a LUN id of 000A). Are there any commands from z/VM that can be issued to give you the LUN id as defined within the SVC? A command like “q edev e011 details” shows EDEV E011 TYPE FBA ATTRIBUTES 2145 VENDOR: IBM PRODUCT : 2145 REVISION: BLOCKSIZE: 512 NUMBER OF BLOCKS: 83886080 PATHS: FCP_DEV: A200 WWPN: 50050768011035EE LUN: 000A PREF CONNECTION TYPE: SWITCHED Mark Wiggins University of Connecticut 860-486-2792
Re: Mapping an Emulated DASD device to an SVC LUN number
On 5/25/2010 at 04:38 PM, Dave Jones d...@vsoft-software.com wrote: Have you thought about maybe installing one of the free Linux distros for the z Architecture (openSuSE, maybe) openSUSE is not available for System z. and using its set of SCSI commands (lsluns, lszfcp, etc.) to get the information you need? It would have the same problem as z/VM. The SAN Volume Controller is, get ready for it, virtualizing all the SCSI devices attached to it, and presenting a consistent interface to the systems on the other side. If there is some sort of API on the SVC, then that might be a different story, but strictly from a user viewpoint, that type of information is being hidden. Mark Post
Re: Mapping an Emulated DASD device to an SVC LUN number
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 05/25/2010 03:45:56 PM: Wiggins, Mark mark.wigg...@uconn.edu Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 05/25/2010 03:45 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Mapping an Emulated DASD device to an SVC LUN number We?re looking to migrate to a new z/10 and we?ve come up with an issue that hoping someone out there knows how to resolve. A while back when we installed our SVC (2145) we lost the ability to see the ?real? LUN number that was being assigned to our z/VM system as an emulated (9336) device. On the SVC side on things you see a 16 character LIN id like this; 013D (which we?d only use the last 4 of ?015E?). When you run the SCSIDISC command on z/VM, the LUN that shows up in z/VM in just the next number in sequential order (e.g. if it was the 11 LUN allocated, it would have a LUN id of 000A). Are there any commands from z/VM that can be issued to give you the LUN id as defined within the SVC? A command like ?q edev e011 details? shows EDEV E011 TYPE FBA ATTRIBUTES 2145 VENDOR: IBM PRODUCT : 2145 REVISION: BLOCKSIZE: 512 NUMBER OF BLOCKS: 83886080 PATHS: FCP_DEV: A200 WWPN: 50050768011035EE LUN: 000A PREF CONNECTION TYPE: SWITCHED Mark Wiggins University of Connecticut 860-486-2792 Mark, I agree with the others. I think you need to use the SVC's GUI, command line interface, or CIM interfaces to get info about managed disks. The CLI is probably the easiest because it only requires an ssh client. CIM probably requires writing some code, and the GUI needs a browser. Regards, Ray Higgs System z FCP Development Bld. 706, B24 2455 South Road Poughkeepsie, NY 12601 (845) 435-8666, T/L 295-8666 rayhi...@us.ibm.com
Re: Mapping an Emulated DASD device to an SVC LUN number
The SVC command line command svcinfo lshostvdiskmap might list the information you're looking for. Look online for the manual IBM TotalStorage SAN Volume ControllerCommand-Line Interface Users Gu ide Here's sample output (probably folded across two lines); the SCSI_id colu mn is the LUN's hex id in decimal (decimal 102 below is hex LUN id 0066) svcinfo lshostvdiskmap Z10_P1-T1Linux id name SCSI_idvdisk_id vdisk_na me wwpn vdisk_UID 240 Z10_P1-T1Linux102186 Z_TZ2BF152_V2 5005076401E2893A 60050768018180762800062F 240 Z10_P1-T1Linux103667 Z_TZ2BF152_V3 5005076401E2893A 600507680181807628000633 (the SVC's SCSI_id column is not to be confused with the value given by linux's scsi_id command. I found that prefixing 3 to the SVC's vdisk_UID is the same value returned by linux's scsi_id command)
