Linux on 390 Port <[email protected]> wrote on 12/15/2009 12:12:42 PM:
> Caleb C Ong <[email protected]> > Sent by: Linux on 390 Port <[email protected]> > > 12/15/2009 12:12 PM > > Please respond to > Linux on 390 Port <[email protected]> > > To > > [email protected] > > cc > > Subject > > LUN numbers for DS8000 > > > Hi, > > Is there any way to determine the LUN numbers to be used for zlinux (redhat > or suse) installation. > I have a z10 with ds8300 disk. Connected thru fcp thru a san switch. > > storage admin gave me a four digit lun number x1600. In ESS800, i just > used to add 12 zeros to it. > But that doesn't seem to work with ds8300. > > I found this hint on the "how to use fc attached scsi devices on linux z > feb 2007' > > There are three things you should be aware of when configuring the > TotalStorage system: > New mask: For the logical volume number X?abcd? the LUN ID will be: > X?40ab40cd00000000?. > > So i tried LUN number 4016400000000000 but i still cannot add zfcp disk > using the installation gui. > > I also found this redpaper on 'where are the lun number on a ds8000" . > > How to convert the LUN ID in DS8000 to the FCP LUN ID in Linux > The FCP LUN ID in Linux is written in hexadecimal and must be exactly 16 > hexadecimal digits. We use the showvolgrp command to get > every LUN ID in the DS8000 for each volume. All of our devices used only > the high-order four digits of the 16 hexadecimal digit LUN > address. We just add two zeros before the two-digit LUN ID in the DS8000, > and then add another 12 zeros behind these four digits. > Therefore, we place 16 hexadecimal digits for our FCP LUN ID into Linux. > For example, the LUN ID of logical volume 1000 is 02. After adding two > zeros before it and 12 zeros behind it, it becomes > 0x0002000000000000. We can use these 16 hexadecimal digits as our Linux FCP > mapping. > > > I don't think i understand this, if you add two zero in front, then doesn't > that limit the number of lun to just 255 for a ds8300 ? > > Maybe i am not understanding this correctly. > > Thanks. > > Caleb C. Ong Caleb, As others have mentioned... From linux you can use either san_disc or lsluns. San_disc is the old tool. Lsluns is the new tool. You'll find one or the other depending on the version of your distro. From VM you can use scsidisc. San_disc is probably the easiest to use because there is a very nice example in the manpage. All of the tools are geared towards a switched environment. The tools will work with point-to-point, but it isn't as straight forward. If a tool cannot find the DS8300 fibre channel ports, then there is probably a zoning problem. If a tool cannot display any luns, then there is probably a lun masking problem on the DS8300. IBM storage calls these host connections. mkhostconnect/lshostconnect are the dscli commands to use in this case. Some other things to consider... Are you using NPIV? Are you using WWPN zoning? Both of these increase the amount of set up. If you need to know info about your FCP channels, use lszfcp, or some of the channel problem determination panels on the SE. Regards, Ray Higgs System z FCP Development Bld. 706, B24 2455 South Road Poughkeepsie, NY 12601 (845) 435-8666, T/L 295-8666 [email protected] ---------------------------------------------------------------------- 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
