Did things change from NPIV to non-NPIV (or vice-a-versa)? Scott Rohling
On Mon, Sep 21, 2015 at 12:05 PM, Raymond Higgs <rayhi...@us.ibm.com> wrote: > Hi Chris, > > Config off, on from the HMC will free up the resources that those messages > are talking about, but I don't think it will help. Based your original > email, I think your zoning changed. It looks like everything is in a > single, giant zone, and you're running out of resources because all ports > can see all other ports. > > Regards, > > Ray Higgs > System z IO Firmware Development > Bld. 706, B42 > 2455 South Road > Poughkeepsie, NY 12601 > (845) 435-8666, T/L 295-8666 > rayhi...@us.ibm.com > > Linux on 390 Port <LINUX-390@VM.MARIST.EDU> wrote on 09/21/2015 12:29:06 > PM: > > > From: "VANDER WOUDE, PETER" <pwo...@harristeeter.com> > > To: LINUX-390@VM.MARIST.EDU > > Date: 09/21/2015 12:55 PM > > Subject: Re: Having issues attaching to LUNs after Brocade mode change > > Sent by: Linux on 390 Port <LINUX-390@VM.MARIST.EDU> > > > > Will, > > > > I would try taking the fcp port offline. The physical port is what > > get's the initial port id and the config offline back online would > > be the only way, I think, to have the plogi sequence operate correctly. > > > > Regards, > > Peter > > > > > > > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf > > Of Will, Chris > > Sent: Monday, September 21, 2015 12:24 PM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: Having issues attaching to LUNs after Brocade mode change > > > > We have shutdown, deactivated the LPAR, activated and IPLd z/VM and > > are still having issues. Would it help to offline the FCP port on > > the HMC? It looks like it attaches and then timesout. > > > > Sep 20 23:13:12 omgdb2prd1 multipathd: 8:32: mark as failed Sep 20 > > 23:13:12 omgdb2prd1 multipathd: mpvol28: remaining active paths: 1 > > Sep 20 23:13:12 omgdb2prd1 kernel: sd 0:0:0:2: [sdc] Medium access > > timeout failure. Offlining disk! > > Sep 20 23:13:12 omgdb2prd1 kernel: sd 0:0:0:2: [sdc] Result: > > hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK Sep 20 23:13:12 > > omgdb2prd1 kernel: sd 0:0:0:2: [sdc] CDB: Read(10): 28 00 01 3e 61 > > 58 00 00 20 00 Sep 20 23:13:12 omgdb2prd1 kernel: end_request: I/O > > error, dev sdc, sector 20865368 Sep 20 23:13:12 omgdb2prd1 kernel: > > device-mapper: multipath: Failing path 8:32. > > Sep 20 23:13:17 omgdb2prd1 multipathd: mpvol28: sdc - tur checker > > reports path is down Sep 20 23:13:22 omgdb2prd1 multipathd: mpvol28: > > sdc - tur checker reports path is down > > > > Chris Will > > Systems Software > > (313) 549-9729 Cell > > cw...@bcbsm.com > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf > > Of VANDER WOUDE, PETER > > Sent: Monday, September 21, 2015 12:03 PM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: Having issues attaching to LUNs after Brocade mode change > > > > Chris, > > > > Have you tried to force the zfcp channels to do a port login (i.e. > > plogi)? After changing the brocade interopmode, you must do this, > > otherwise your system is probably trying to use it's previous port > > id mappings, which the interopmode change changes. > > > > Peter > > > > > > > > > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf > > Of Will, Chris > > Sent: Monday, September 21, 2015 11:17 AM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Having issues attaching to LUNs after Brocade mode change > > > > We recently had a Brocade mode change and when the channel came back > > we were flooded with the following messages and have not been able > > to attach any LUNs to this channel (they attach and then timeout). > > Our zoning should only allow us to see/discover one port. > > > > Sep 19 20:58:45 edidb2prd1 kernel: zfcp.ac341f: 0.0.0404: The local > > link has been restored Sep 19 20:58:45 edidb2prd1 kernel: qdio: 0.0. > > 0404 ZFCP on SC 0 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A Sep 19 > > 20:59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0x5000144280501200 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0x50001442903b0910 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0x50001442804ecf00 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031005b41 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e0310014e8 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e0310014dc Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001460 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e0310014a4 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e0310014ec Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001454 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001408 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001344 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001404 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001348 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001420 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001458 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031005701 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0x50000973001411b4 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0x5000144280501200 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0x50001442903b0910 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0x50001442804ecf00 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0x50001442903c5210 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031005b41 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e0310014e8 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e0310014dc Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001460 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e0310014a4 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e0310014ec Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001454 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001408 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001344 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001404 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001348 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001420 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031001458 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0xc05076e031005701 Sep 19 20: > > 59:00 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP > > adapter resources to open remote port 0x50000973001411b4 Sep 19 20: > > 59:01 edidb2prd1 kernel: zfcp.10efb5: 0.0.0404: Opening WKA port > > 0xfffffc failed Sep 19 20:59:01 edidb2prd1 kernel: zfcp.10efb5: 0.0. > > 0404: Opening WKA port 0xfffffc failed Sep 19 20:59:01 edidb2prd1 > > kernel: qdio: 0.0.0404 ZFCP on SC 0 using AI:1 QEBSM:1 PRI:1 TDD:1 > > SIGA: W A Sep 19 20:59:08 edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: > > Not enough FCP adapter resources to open remote port > > 0x5000097300141138 Sep 19 20:59:08 edidb2prd1 kernel: zfcp.9b70c0: > > 0.0.0404: Not enough FCP adapter resources to open remote port > > 0x5000097300141178 Sep 19 20:59:08 edidb2prd1 kernel: zfcp.10efb5: > > 0.0.0404: Opening WKA port 0xfffffc failed Sep 19 20:59:08 > > edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP adapter > > resources to open remote port 0x50000973001411f4 Sep 19 20:59:08 > > edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP adapter > > resources to open remote port 0x21000024ff5724d3 Sep 19 20:59:08 > > edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP adapter > > resources to open remote port 0x21000024ff580fee Sep 19 20:59:08 > > edidb2prd1 kernel: zfcp.9b70c0: 0.0.0404: Not enough FCP adapter > > resources to open remote port 0x21000024ff574572 . > > . > > . (this goes on for many pages) > > > > Any help would be appreciated. > > > > > > > > Chris Will > > Systems Software > > (313) 549-9729 Cell > > cw...@bcbsm.com > > > > > > > > The information contained in this communication is highly > > confidential and is intended solely for the use of the individual(s) > > to whom this communication is directed. If you are not the intended > > recipient, you are hereby notified that any viewing, copying, > > disclosure or distribution of this information is prohibited. Please > > notify the sender, by electronic mail or telephone, of any > > unintended receipt and delete the original message without making any > copies. > > > > Blue Cross Blue Shield of Michigan and Blue Care Network of > > Michigan are nonprofit corporations and independent licensees of the > > Blue Cross and Blue Shield Association. > > > > ---------------------------------------------------------------------- > > 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/ > > > > ________________________________ > > > > CONFIDENTIALITY NOTICE: This e-mail message and all attachments may > > contain legally privileged and confidential information intended > > solely for the use of the addressee. If the reader of this message > > is not the intended recipient, any reading, dissemination, > > distribution, copying, or other use of this message or its > > attachments is prohibited. If you have received this communication > > in error, please notify the sender immediately by telephone at 704. > > 844.3100 and delete this message and all copies and backups > thereof.Thank you. > > > > ---------------------------------------------------------------------- > > 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/ > > > > > > The information contained in this communication is highly > > confidential and is intended solely for the use of the individual(s) > > to whom this communication is directed. If you are not the intended > > recipient, you are hereby notified that any viewing, copying, > > disclosure or distribution of this information is prohibited. Please > > notify the sender, by electronic mail or telephone, of any > > unintended receipt and delete the original message without making any > copies. > > > > Blue Cross Blue Shield of Michigan and Blue Care Network of > > Michigan are nonprofit corporations and independent licensees of the > > Blue Cross and Blue Shield Association. > > > > ---------------------------------------------------------------------- > > 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/ > > > > ________________________________ > > > > CONFIDENTIALITY NOTICE: This e-mail message and all attachments may > > contain legally privileged and confidential information intended > > solely for the use of the addressee. If the reader of this message > > is not the intended recipient, any reading, dissemination, > > distribution, copying, or other use of this message or its > > attachments is prohibited. If you have received this communication > > in error, please notify the sender immediately by telephone at 704. > > 844.3100 and delete this message and all copies and backups > thereof.Thank you. > > > > ---------------------------------------------------------------------- > > 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/ > > > > > > ---------------------------------------------------------------------- > 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/ > ---------------------------------------------------------------------- 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/
