'Re: Having issues attaching to LUNs after Brocade mode change'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-390
Subject:    Re: Having issues attaching to LUNs after Brocade mode change
From:       Raymond Higgs <rayhiggs () us ! ibm ! com>
Date:       2015-09-22 15:41:02
Message-ID: 201509221541.t8MFfB0V024002 () d03av03 ! boulder ! ibm ! com
[Download RAW message or body]

Hi Peter,

Linux will not remember the portid that the channel had.  Port disable at 
the switch causes loss of light on the fibre channel link.  This event is 
an implicit logout.  It causes all addressing information and service 
parameters to be discarded.  We have automated testing for this, and Linux 
and VM handle it properly.

Port disable, enable were manual steps in that procedure.  I think it is 
more likely that someone missed a port.

I'm sorry you had problems with AIX.  I'm not familiar with their design 
and can't say much.

Regards,

Ray Higgs
System z IO Firmware Development
Bld. 706, B42
2455 South Road
Poughkeepsie, NY 12601
(845) 435-8666,  T/L 295-8666
rayhiggs@us.ibm.com

Linux on 390 Port <LINUX-390@VM.MARIST.EDU> wrote on 09/22/2015 09:44:40 
AM:

> From: "VANDER WOUDE, PETER" <pwoude@harristeeter.com>
> To: LINUX-390@VM.MARIST.EDU
> Date: 09/22/2015 09:46 AM
> Subject: Re: Having issues attaching to LUNs after Brocade mode change
> Sent by: Linux on 390 Port <LINUX-390@VM.MARIST.EDU>
> 
> I agree that that "should" take care of the issue.
> 
> What complicates matters is if the o/s keeps the portid for the 
> connection.  We ran into a problem with AIX, due to the multipathing
> having a bug, that did not correctly handle the portid change, even 
> though aix's parm of dyntrk was set.
> 
> Does linux do the same type of thing?  Or VM?
> 
> Regards,
> Peter
> 
> 
> 
> 
> -----Original Message-----
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf 
> Of Raymond Higgs
> Sent: Monday, September 21, 2015 6:17 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Having issues attaching to LUNs after Brocade mode change
> 
> Here is a Brocade procedure for changing interop mode:
> 
>  Solution Guide: Migrating from McData Fabric or Open Fabric Mode (IM2 
or
> IM3) to Brocade Native Fabric Mode (IM0)
> 
> http://community.brocade.com/dtscp75322/attachments/dtscp75322/
> fibre/2767/1/Migrating+from+McData+Fabric+or+Open+Fabric+Mode+%
> 2528IM2+or+IM3%2529+to+Brocade+Native+Fabric+Mode+%2528IM0%2529.pdf
> 
> No actions are required on the FCP channels because it includes 
> disabling, reenabling ports at the switch.  This is enough to cause 
> the channels to refresh their addressing information.  Part of this 
> process is re-logging in.
> 
> Also, it clearly states that all zoning information will be lost. 
> It has some steps for backing it up and restoring it.  I'm not 
> surprised that Chris is having problems.  I hope you figure things 
> out without too much more trouble!
> 
> Regards,
> 
> Ray Higgs
> System z IO Firmware Development
> Bld. 706, B42
> 2455 South Road
> Poughkeepsie, NY 12601
> (845) 435-8666,  T/L 295-8666
> rayhiggs@us.ibm.com
> 
> Linux on 390 Port <LINUX-390@VM.MARIST.EDU> wrote on 09/21/2015 12:02:30
> PM:
> 
> > From: "VANDER WOUDE, PETER" <pwoude@harristeeter.com>
> > To: LINUX-390@VM.MARIST.EDU
> > Date: 09/21/2015 01:15 PM
> > Subject: Re: Having issues attaching to LUNs after Brocade mode change
> > Sent by: Linux on 390 Port <LINUX-390@VM.MARIST.EDU>
> >
> > 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
> > cwill@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 LISTSERV@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 LISTSERV@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 LISTSERV@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 LISTSERV@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 LISTSERV@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/
[prev in list] [next in list] [prev in thread] [next in thread]
Configure | About | News | Add a list | Sponsored by KoreLogic