From: Coyle, Jack (Jack.Coyle@REXHEALTH.COM)
Date: Thu Jul 31 2003 - 18:25:43 EDT
Before you go tearing into the configuration, one thing you might want to
carefully check is your connections. By virtue of the fact that you have
identified a 2105-F20 and a SAN and 6228 cards, somewhere in your fibre
connectivity you must have SC-LC converter cables. When we rolled in our
2105 expansion cabinet, the very act of rolling that behemoth across the
raised floor caused a SC-LC connector to become "slightly loose" and we saw
random ERR2's and ERR4's. I went into the switch cabinet and "seated" all of
the converter connections (did NOT take any apart - just ensured they were
thoroughly mated) and our errors disappeared. May not be applicable to your
situation, but it is worth a try.
Regards,
Jack Coyle
Rex Healthcare
(919) 784-3792
jack.coyle@rexhealth.com
> ----------
> From: James Jackson[SMTP:James.Jackson@MAIL.STATE.AR.US]
> Reply To: IBM AIX Discussion List
> Sent: Thursday, July 31, 2003 6:09 PM
> To: aix-l@Princeton.EDU
> Subject: Re: Errors on fiber channel adapter.
>
> No LUN sharing, though this is a non-concurrent HACMP config. The problem
> is coincident with some work done on the SAN this past week-end. I'm
> trying to get more info on the SAN changes/upgrades etc.
>
> thx,
>
> JJackson
>
> -----Original Message-----
> From: Adams Kevin J [mailto:kevin.adams@PHS.COM]
> Sent: Thursday, July 31, 2003 4:53 PM
> To: aix-l@Princeton.EDU
> Subject: Re: Errors on fiber channel adapter.
>
>
> You're not sharing LUNs between hosts are you?
>
> Jjust having an hdisk seen by more than one host can cause these
> symptoms when not using the right verion of SDD.
>
> Kevin Adams
> PacifiCare Behavioral Health
> Principal Systems Analyst
> AIX Certified Advanced Technical Expert
>
> -----Original Message-----
> From: James Jackson [mailto:James.Jackson@MAIL.STATE.AR.US]
> Sent: Thursday, July 31, 2003 2:21 PM
> To: aix-l@Princeton.EDU
> Subject: [aix-l] Errors on fiber channel adapter.
>
>
>
> Gurus,
>
> I have an M80 with a pair of 6228 FC adapters. One of the
> adapters is sending periodic FSCSI_ERR2's accompanied by occasional
> SC_DISK_ERR4's from its child "hdisks". The adapters are connected to an
> F20 ESS via a SAN. I'm using SDD for path redundancy, and I have a single
> volume group which contains two vpaths. Each vpath has six "hdisks",
> three from each 6228. I need to run diag on the flaky 6228, but I don't
> want to varyoff the volume group. Does anyone know if the following
> procedure will work as a means of getting the 6228 in a state that'll
> support diag?
>
> * run "datapath set adapter 1 offline", which will
> cease SDD I/O to adapter 1, setting its hdisks' state to "DEAD".
> * run "rmdev -l" on the child hdisks and fscsi1
> device.
> *
>
> If this works, will the following procedure get everything
> back to normal?
>
> * run "cfgmgr -l fcs1".
> * run "datapath set adapter 1 online".
> *
>
> TIA,
>
> James Jackson
>
> Confidentiality Notice: The information contained in this
> email message and any attachment(s) is the property of the State of
> Arkansas and may be protected by state and federal laws governing
> disclosure of private information. It is intended solely for the use of
> the entity to whom this email is addressed. If you are not the intended
> recipient, you are hereby notified that reading, copying or distribution
> of this transmission is STRICTLY PROHIBITED. The sender has not waived any
> applicable privilege by sending the accompanying transmission. If you have
> received this transmission in error, please notify the sender by return
> e-mail and delete the message and attachment(s) from your system.
>
>
>
> This electronic message transmission, including any attachments,
> contains information from PacifiCare Health Systems Inc. which may be
> confidential or privileged. The information is intended to be for the use
> of the individual or entity named above. If you are not the intended
> recipient, be aware that any disclosure, copying, distribution or use of
> the contents of this information is prohibited.
>
> If you have received this electronic transmission in error, please
> notify the sender immediately by a "reply to sender only" message and
> destroy all electronic and hard copies of the communication, including
> attachments.
>
>
>
>
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:06 EDT