Re: IPL from SAN

2016-02-29 Thread Rothman, Peter 
Thank you very much. The SCSIDISC tool helped.
The system is now running.

The tool actually showed 6 different WWPNs per FCP device (2000 and 3000) but 
the output was only 'complete' for 1 of these with UUID/vendor/PROD etc filled 
out in the SCSIDISC OUT file.
I used the info for the 1 complete WWPN and the system IPLed.

Our linux guy also says that only the 3000 device appeared in zipl.conf - he 
says the installer built the file.
Can he manually add the equivalent 2000 device info?

Anyway thanks again. We obviously have some internal stuff to sort out.

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Steffen 
Maier
Sent: Monday, February 29, 2016 8:48 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: IPL from SAN

On 02/29/2016 02:21 PM, Rothman, Peter wrote:
> This is per our Linux sysadmin.
> I have asked him about the WWPN - FYI this was the posted.

We need the target WWPN which typically the storage and or SAN admin knows 
about.

> The loaddev portname looks like the initiator WWPN of your local 
> FCP=20 device 0.0.2000, so the open port fails as expected.
> Portname should be (one of) the storage target WWPN(s) behind which 
> your =
>
> LUN is reachable (it must be the LUN that contains the "zipl 
> target",=20 which is /boot with RHEL, and thus the zipl boot record).
>
> Is there a way I can query the wwpn 'behind' the LUN?

 From the host / Linux perspective, the LUNs are behind the target port WWPN.

In a running Linux, you can use "lszfcp -P" to see all target ports that zfcp 
could discover 
[http://www-01.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.lgdd/lgdd_t_fcp_wrk_pinfo.html
http://www-01.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ldsg/ldsg_r_scsiipl_sanaddr.html]
If you don't have Linux running, you could use the z/VM tool SCSIDISC to 
discover target ports 
[http://www-01.ibm.com/support/knowledgecenter/SSB27U_6.3.0/com.ibm.zvm.v630.hcpb7/scsidisc.htm],
or you can use "FCP SAN Explorer" on the HMC/SE [presentation I referenced in 
an earlier mail].

Depending on your zoning and LUN masking you need to chose the correct target 
port if multiple ports were discovered.

Earlier you wrote that you could successfully install and reboot.
Alternatively, you can use such a running Linux instance and run "lsreipl" to 
figure out the necessary FCP addressing parameters for a manual IPL. The Linux 
distribution installer figured this out already.
[http://www-01.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.lgdd/lgdd_r_lsreipl_cmd.html]

> Our storage guys always zone the storage to/for the WWPN that CP displays via 
> the Q FCP command.

The zone also contains the storage target port(s) which the host / initiator 
needs for accessing the LUNs.


-- 
Mit freundlichen Grüßen / Kind regards
Steffen Maier

Linux on z Systems Development

IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

--
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/


___ 

*** This is an EXTERNAL email. Exercise caution. DO NOT open attachments or 
click links from unknown senders or in unexpected email.

This message has been analyzed for malware by Cloud Email Security.
To report this as spam please attach this email to an email addressed to 
a...@websense.com.
___

--
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/

Re: IPL from SAN

2016-02-29 Thread Steffen Maier 

On 02/29/2016 02:21 PM, Rothman, Peter wrote:

This is per our Linux sysadmin.
I have asked him about the WWPN - FYI this was the posted.


We need the target WWPN which typically the storage and or SAN admin 
knows about.



The loaddev portname looks like the initiator WWPN of your local FCP=20
device 0.0.2000, so the open port fails as expected.
Portname should be (one of) the storage target WWPN(s) behind which your =

LUN is reachable (it must be the LUN that contains the "zipl target",=20
which is /boot with RHEL, and thus the zipl boot record).

Is there a way I can query the wwpn 'behind' the LUN?


From the host / Linux perspective, the LUNs are behind the target port 
WWPN.


In a running Linux, you can use "lszfcp -P" to see all target ports that 
zfcp could discover

[http://www-01.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.lgdd/lgdd_t_fcp_wrk_pinfo.html
http://www-01.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ldsg/ldsg_r_scsiipl_sanaddr.html]
If you don't have Linux running, you could use the z/VM tool SCSIDISC to 
discover target ports

[http://www-01.ibm.com/support/knowledgecenter/SSB27U_6.3.0/com.ibm.zvm.v630.hcpb7/scsidisc.htm],
or you can use "FCP SAN Explorer" on the HMC/SE
[presentation I referenced in an earlier mail].

Depending on your zoning and LUN masking you need to chose the correct 
target port if multiple ports were discovered.


Earlier you wrote that you could successfully install and reboot.
Alternatively, you can use such a running Linux instance and run 
"lsreipl" to figure out the necessary FCP addressing parameters for a 
manual IPL. The Linux distribution installer figured this out already.

[http://www-01.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.lgdd/lgdd_r_lsreipl_cmd.html]


Our storage guys always zone the storage to/for the WWPN that CP displays via 
the Q FCP command.


The zone also contains the storage target port(s) which the host / 
initiator needs for accessing the LUNs.



--
Mit freundlichen Grüßen / Kind regards
Steffen Maier

Linux on z Systems Development

IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

--
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/

Re: IPL from SAN

2016-02-29 Thread Rothman, Peter 
My apologies if this email starts a new thread. I did not receive any replies 
but saw on the web that there were two.
Hopefully my "linux-390" options are now correct.

There were questions about the LUN number and the bootprog.
The LUN of zeroes is correct and I have changed the bootprog to  0.
This is per our Linux sysadmin.
I have asked him about the WWPN - FYI this was the posted.

The loaddev portname looks like the initiator WWPN of your local FCP=20
device 0.0.2000, so the open port fails as expected.
Portname should be (one of) the storage target WWPN(s) behind which your =

LUN is reachable (it must be the LUN that contains the "zipl target",=20
which is /boot with RHEL, and thus the zipl boot record).

Is there a way I can query the wwpn 'behind' the LUN?

We do use SAN here for 'regular' storage but this is our first attempt at 
IPLing.
Our storage guys always zone the storage to/for the WWPN that CP displays via 
the Q FCP command.

FYI - we are using an IBM SVC

--
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/

Re: IPL from SAN

2016-02-26 Thread Steffen Maier 

On 02/26/2016 06:39 PM, Rothman, Peter wrote:

We completed a kickstart 'to SAN' with RHLE 7.2.
A linux 'shutdown reboot' worked OK but now a IPL from the FCP device fails.
What am I missing?

Here is the console:
q loaddev
PORTNAME C05076E4 5D1CLUN   BOOTPROG 2


The loaddev portname looks like the initiator WWPN of your local FCP 
device 0.0.2000, so the open port fails as expected.
Portname should be (one of) the storage target WWPN(s) behind which your 
LUN is reachable (it must be the LUN that contains the "zipl target", 
which is /boot with RHEL, and thus the zipl boot record).


If you want to boot zipl menu entry 2, then the bootprog setting is OK; 
otherwise you may want to try the default zipl menu entry with "bootprog 0".



BR_LBA    

SCPDATA
  0+1+2+3+4+
 NORESUMENORESUMENORESUMENORESUMENORESUMENORESUMENO
0050 RESUMENORESUME


the scpdata looks funny, so once the SCSI loader will work with a proper 
loaddev, this could cause kernel boot issues (or it just ignores it as 
unknown kernel parameter)



  q fcp attach dztpc001
00: FCP  FE07 ATTACHED TO DZTPC001 2000 CHPID 52
00:  WWPN C05076E45D1C



00: MLOFCP009E: Unable to open target port with WWPN 0xc05076e45d1c (d_id 0x
00: 00035519) on adapter 0.0.2000.


--
Mit freundlichen Grüßen / Kind regards
Steffen Maier

Linux on z Systems Development

IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

--
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/

Re: IPL from SAN

2016-02-26 Thread Mark Post 
>>> On 2/26/2016 at 12:39 PM, "Rothman, Peter" 
wrote: 
> We completed a kickstart 'to SAN' with RHLE 7.2.
> A linux 'shutdown reboot' worked OK but now a IPL from the FCP device fails.
> What am I missing?
> 
> Here is the console:
> q loaddev
> PORTNAME C05076E4 5D1CLUN   BOOTPROG 2
> BR_LBA    

I'm suspicious of a LUN number of all zeros.  Is that correct?  Also, the 
BOOTPROG of 2 is possibly alright, but that means you're selecting option 2 
from /etc/zipl.conf.  Is that really what you want?


Mark Post

--
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/

IPL from SAN

2016-02-26 Thread Rothman, Peter 
We completed a kickstart 'to SAN' with RHLE 7.2.
A linux 'shutdown reboot' worked OK but now a IPL from the FCP device fails.
What am I missing?

Here is the console:
q loaddev
PORTNAME C05076E4 5D1CLUN   BOOTPROG 2
BR_LBA    

SCPDATA
 0+1+2+3+4+
 NORESUMENORESUMENORESUMENORESUMENORESUMENORESUMENO
0050 RESUMENORESUME
Ready; T=0.01/0.01 12:38:50
 q fcp attach dztpc001
00: FCP  FE07 ATTACHED TO DZTPC001 2000 CHPID 52
00:  WWPN C05076E45D1C
00: FCP  FE47 ATTACHED TO DZTPC001 3000 CHPID 53
00:  WWPN C05076E45D9C
Ready; T=0.01/0.01 12:39:14
 id
DZTPC001 AT WSPLX1   VIA RSCS 02/26/16 12:39:17 EST  FRIDAY
Ready; T=0.01/0.01 12:39:17
 ipl 2000
00: HCPLDI2816I Acquiring the machine loader from the processor controller.
00: HCPLDI2817I Load completed from the processor controller.
00: HCPLDI2817I Now starting the machine loader.
01: HCPGSP2630I The virtual machine is placed in CP mode due to a SIGP stop and
store status from CPU 00.
00: MLOFCP009E: Unable to open target port with WWPN 0xc05076e45d1c (d_id 0x
00: 00035519) on adapter 0.0.2000.
00: MLOEVL012I: Machine loader up and running (version v2.4.5).
00: MLOEVL005E: No SCSI device found on adapter 0x2000 with WWPN 0xc05076e45d000
00: 01c and LUN 0x.
00: MLOEVL010E: IPL failed.
00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000  0002885E

Peter Rothman
Senior Systems Engineer
T +1 (404) 322 4079
M +1 (404) 723 6144

peter.roth...@travelport.com
www.travelport.com

[redefining_email_signature]


--
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/