Robert, Here's a sample /etc/zfcp.conf file 0.0.0315 0x00 0x5006048ad5f09e01 0x00 0x0010000000000000 0.0.0315 0x00 0x5006048ad5f09e01 0x01 0x0011000000000000 0.0.0315 0x00 0x5006048ad5f09e01 0x02 0x0012000000000000 0.0.0315 0x00 0x5006048ad5f09e01 0x03 0x0013000000000000 0.0.0315 0x00 0x5006048ad5f09e01 0x04 0x0014000000000000 0.0.0315 0x00 0x5006048ad5f09e01 0x05 0x0025000000000000 0.0.0325 0x01 0x5006048ad5f09e0e 0x00 0x0010000000000000 0.0.0325 0x01 0x5006048ad5f09e0e 0x01 0x0011000000000000 0.0.0325 0x01 0x5006048ad5f09e0e 0x02 0x0012000000000000 0.0.0325 0x01 0x5006048ad5f09e0e 0x03 0x0013000000000000 0.0.0325 0x01 0x5006048ad5f09e0e 0x04 0x0014000000000000 0.0.0325 0x01 0x5006048ad5f09e0e 0x05 0x0025000000000000
There are 6 LUN's on two paths. The first field is the zfcp subchannel (we code 300-31F on first chpid, 320-32F on second chpid, for example). Second field is 0x00 for first adapter, 0x01 for second adapter, 0x02 for third adapter, etc. The third field identifies the WWPN of the SCSI adapter (two in this example). Fourth field is the LUN sequence (0 thru 5 for six LUN's). Fifth is the LUN ID that I got from the SCSI vendor SE. Betsie -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Wednesday, August 13, 2008 1:48 PM To: [email protected] Subject: Finally getting into zFCP... We¹re finally getting back around to ³playing² with zFCP, and I¹ve run into a possible bug.... We¹re able to get things up and running by hand, and we¹re now trying to set things up to happen during the boot of the system. Everything points back around to a file called /etc/zfcp.conf, but there¹s very little on what¹s really required in the file (i.e. What the five fields really mean / where to go to get the information to fill them out). I think we¹ve figured them out, but it would have been more reassuring to have found some detailed documentation. Or maybe even a man page? Also, there¹s a script called /sbin/zfcpconf.sh, that appears to be entirely wrong. It lops the 0x off the front of the device address, and uses it in the /sys directory path, but fails to add the ³0.0.² to the front of it. Could it have ever worked? I¹m not sure I see how... Adding in the ³0.0.² into the paths used in the script seems to make it work correctly. The second question is, does this script actually get envoked during the boot? Or do we have to slip it in somewhere in the /etc/init.d path? -- Robert P. Nix Mayo Foundation .~. RO-OE-5-55 200 First Street SW /V\ 507-284-0844 Rochester, MN 55905 /( )\ ----- ^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
