Sue,
when NPIV is switched off, the zfcp adaptor has a single, general WWPN
for each virtual adapter (on the same PCHID)
Now, if you turn on NPIV, your FCP host adapter gets a bunch of
different, new WWPNs for each virtual adapter (LPAR/VM guest).
Thus, these new WWPNs have to be configured in your SAN switch - or you
encounter the problems you had.
After that, san_disc is a good tool to proceed with.
With kind regards
Thorsten Diehl
System Test Linux on System z
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschaeftsfuehrung: Erich Baier
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
Raymond Higgs schrieb am 10/07/2009 02:40 AM:
Linux on 390 Port <LINUX-390@VM.MARIST.EDU> wrote on 10/06/2009 06:33:00
PM:
Sue Sivets <ssiv...@fdrinnovation.com>
Sent by: Linux on 390 Port <LINUX-390@VM.MARIST.EDU>
10/06/2009 06:33 PM
Please respond to
Linux on 390 Port <LINUX-390@VM.MARIST.EDU>
To
LINUX-390@VM.MARIST.EDU
cc
Subject
NPIV known problems?
Does anyone know if there are any known problems with NPIV and Suse 10
SP2? We're trying to add NPIV to one of our Suse 10 test systems, and
having a spectacularly unsuccessful time.
When we turned the NPIV bit on, we lost access to all the fcp dasd that
had been working without any problems, so we turned NPIV off on the
original channel, and added another channel; all the defined fcp
devices started working again, and then we turned NPIV on for the new
channel. VM can see the new channel and the addresses that have been
dedicated to the Suse test system. Suse can see the channel, and reports
the following during boot:
scsi3 : zfcp
zfcp: The adapter 0.0.f101 reported the following characteristics:
WWNN 0x5005076400c36e0d, WWPN 0xc05076fd6b000784, S_ID 0x00701401,
adapter version 0x4, LIC version 0x70e, FC link speed 4 Gb/s
zfcp: Switched fabric fibrechannel network detected at adapter 0.0.f101.
However, when we go into yast2, the fcp function cannot (or will not)
define a new device on the new NPIV channel address. It sees the channel
address when it does the scan during startup (the address shows up in
the add a device pulldown box), but most of the time it doesn't seem to
like the WWPN, and we've tried every WWPN we've been able to find that
looked like it might work. We can see the channel and the address on the
HMC, and the switch. So far, it looks like we can see the NPIV channel
where ever we look, but that's about it.
Any ideas or suggestions would be helpful.
Thank you.
Sue Sivets
--
Suzanne Sivets
Systems Programmer
Innovation Data Processing
275 Paterson Ave
Little Falls, NJ 07424-1658
973-890-7300
Fax 973-890-7147
ssiv...@fdrinnovation.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
I would try to use san_disc to see what is in your fabric. There is a
good example in the san_disc manpage. Follow the example through "-c
PORT_LIST". If you do not see the WWPN of your storage array, then it is
probably a zoning issue.
I hope this helps.
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
----------------------------------------------------------------------
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 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
