Does anyone know what these errors mean? We started getting them on
some systems after installing ECC. If I shut down ECC I don't get the
errors. I found a few hits on google but no solutions.

LABEL: FSCSI_ERR4
IDENTIFIER: 3074FEB7

Date/Time: Fri Jun 2 15:01:12 CDT
Sequence Number: 9507
Class: H
Type: TEMP
Resource Name: fscsi1
Resource Class: driver
Resource Type: efscsi
Location: U7879.001.DQD0594-P1-C5-T1

Description
ADAPTER ERROR

Probable Causes
ADAPTER HARDWARE OR CABLE
ADAPTER MICROCODE
FIBRE CHANNEL SWITCH OR FC-AL HUB

Failure Causes
ADAPTER
CABLES AND CONNECTIONS
DEVICE

Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
CHECK CABLES AND THEIR CONNECTIONS
VERIFY DEVICE CONFIGURATION

Detail Data
SENSE DATA
0000 0000 0000 002A 0000 0000 0200 0000 0000 0000 0000 0000 0000 0000
0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0061 2013
0000 0000
0061 7313 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000
0000 0000 260D 0100 0100 0002 0000 0103 0101 0000 0000 0000 0000 0000
0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001
5006 0482
C095 10CA 5006 0482 C095 10CA 0200 0000 0000 0000 0000 0000 0000 0000
0000 0000
3528 E000

"Steve Stewart" <sstewart14_noway_@kc.rr.com> schreef in bericht
news:%EDgg.16399$GM.1658@tornado.rdc-kc.rr.com...
> Does anyone know what these errors mean? We started getting them on some
> systems after installing ECC. If I shut down ECC I don't get the errors.
> I found a few hits on google but no solutions.
>
> LABEL: FSCSI_ERR4
> IDENTIFIER: 3074FEB7
>
> Date/Time: Fri Jun 2 15:01:12 CDT
> Sequence Number: 9507
> Class: H
> Type: TEMP
> Resource Name: fscsi1
> Resource Class: driver
> Resource Type: efscsi
> Location: U7879.001.DQD0594-P1-C5-T1
>
> Description
> ADAPTER ERROR
>
> Probable Causes
> ADAPTER HARDWARE OR CABLE
> ADAPTER MICROCODE
> FIBRE CHANNEL SWITCH OR FC-AL HUB
>
> Failure Causes
> ADAPTER
> CABLES AND CONNECTIONS
> DEVICE
>
> Recommended Actions
> PERFORM PROBLEM DETERMINATION PROCEDURES
> CHECK CABLES AND THEIR CONNECTIONS
> VERIFY DEVICE CONFIGURATION
>
> Detail Data
> SENSE DATA
> 0000 0000 0000 002A 0000 0000 0200 0000 0000 0000 0000 0000 0000 0000 0000
> 0000
> 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0061 2013 0000
> 0000
> 0061 7313 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
> 0000
> 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
> 0000
> 0000 0000 260D 0100 0100 0002 0000 0103 0101 0000 0000 0000 0000 0000 0000
> 0000
> 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 5006
> 0482
> C095 10CA 5006 0482 C095 10CA 0200 0000 0000 0000 0000 0000 0000 0000 0000
> 0000
> 3528 E000

Steve,

Are you sure after installing ECC?
ECC does only install an agent on the host, nothing else.
This seems to be a hardware failure.

Greez,
Geert

"Steve Stewart" <sstewart14_noway_@kc.rr.com> wrote in message
news:%EDgg.16399$GM.1658@tornado.rdc-kc.rr.com...
> Does anyone know what these errors mean? We started getting them on some
> systems after installing ECC. If I shut down ECC I don't get the errors.
> I found a few hits on google but no solutions.
>
> LABEL: FSCSI_ERR4
> IDENTIFIER: 3074FEB7
[...]

I have the same errors on a couple of machines - they started to show up
after upgrading firmware on our fc switches...

R.

Geert wrote:
> "Steve Stewart" <sstewart14_noway_@kc.rr.com> schreef in bericht
> news:%EDgg.16399$GM.1658@tornado.rdc-kc.rr.com...
>
>>Does anyone know what these errors mean? We started getting them on some
>>systems after installing ECC. If I shut down ECC I don't get the errors.
>>I found a few hits on google but no solutions.
>>
>>LABEL: FSCSI_ERR4
>>IDENTIFIER: 3074FEB7
>>
>>Date/Time: Fri Jun 2 15:01:12 CDT
>>Sequence Number: 9507
>>Class: H
>>Type: TEMP
>>Resource Name: fscsi1
>>Resource Class: driver
>>Resource Type: efscsi
>>Location: U7879.001.DQD0594-P1-C5-T1
>>
>>Description
>>ADAPTER ERROR
>>
>>Probable Causes
>>ADAPTER HARDWARE OR CABLE
>>ADAPTER MICROCODE
>>FIBRE CHANNEL SWITCH OR FC-AL HUB
>>
>>Failure Causes
>>ADAPTER
>>CABLES AND CONNECTIONS
>>DEVICE
>>
>>Recommended Actions
>>PERFORM PROBLEM DETERMINATION PROCEDURES
>>CHECK CABLES AND THEIR CONNECTIONS
>>VERIFY DEVICE CONFIGURATION
>>
>>Detail Data
>>SENSE DATA
>>0000 0000 0000 002A 0000 0000 0200 0000 0000 0000 0000 0000 0000 0000 0000
>>0000
>>0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0061 2013 0000
>>0000
>>0061 7313 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
>>0000
>>0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
>>0000
>>0000 0000 260D 0100 0100 0002 0000 0103 0101 0000 0000 0000 0000 0000 0000
>>0000
>>0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 5006
>>0482
>>C095 10CA 5006 0482 C095 10CA 0200 0000 0000 0000 0000 0000 0000 0000 0000
>>0000
>>3528 E000
>
>
> Steve,
>
> Are you sure after installing ECC?
> ECC does only install an agent on the host, nothing else.
> This seems to be a hardware failure.
>
> Greez,
> Geert
>
>
>
I agree, it does look like a hardware error, but I only get them when
the agent is running.

Probably it's related with more workload?
The agent takes some resourcese perhaps the error comes up at that time.


"Steve Stewart" <sstewart14_noway_@kc.rr.com> schreef in bericht
news:3e5hg.12371$3q2.11205@tornado.rdc-kc.rr.com...
> Geert wrote:
>> "Steve Stewart" <sstewart14_noway_@kc.rr.com> schreef in bericht
>> news:%EDgg.16399$GM.1658@tornado.rdc-kc.rr.com...
>>
>>>Does anyone know what these errors mean? We started getting them on some
>>>systems after installing ECC. If I shut down ECC I don't get the errors.
>>>I found a few hits on google but no solutions.
>>>
>>>LABEL: FSCSI_ERR4
>>>IDENTIFIER: 3074FEB7
>>>
>>>Date/Time: Fri Jun 2 15:01:12 CDT
>>>Sequence Number: 9507
>>>Class: H
>>>Type: TEMP
>>>Resource Name: fscsi1
>>>Resource Class: driver
>>>Resource Type: efscsi
>>>Location: U7879.001.DQD0594-P1-C5-T1
>>>
>>>Description
>>>ADAPTER ERROR
>>>
>>>Probable Causes
>>>ADAPTER HARDWARE OR CABLE
>>>ADAPTER MICROCODE
>>>FIBRE CHANNEL SWITCH OR FC-AL HUB
>>>
>>>Failure Causes
>>>ADAPTER
>>>CABLES AND CONNECTIONS
>>>DEVICE
>>>
>>>Recommended Actions
>>>PERFORM PROBLEM DETERMINATION PROCEDURES
>>>CHECK CABLES AND THEIR CONNECTIONS
>>>VERIFY DEVICE CONFIGURATION
>>>
>>>Detail Data
>>>SENSE DATA
>>>0000 0000 0000 002A 0000 0000 0200 0000 0000 0000 0000 0000 0000 0000
>>>0000 0000
>>>0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0061 2013
>>>0000 0000
>>>0061 7313 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
>>>0000 0000
>>>0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
>>>0000 0000
>>>0000 0000 260D 0100 0100 0002 0000 0103 0101 0000 0000 0000 0000 0000
>>>0000 0000
>>>0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001
>>>5006 0482
>>>C095 10CA 5006 0482 C095 10CA 0200 0000 0000 0000 0000 0000 0000 0000
>>>0000 0000
>>>3528 E000
>>
>>
>> Steve,
>>
>> Are you sure after installing ECC?
>> ECC does only install an agent on the host, nothing else.
>> This seems to be a hardware failure.
>>
>> Greez,
>> Geert
>>
>>
>>
> I agree, it does look like a hardware error, but I only get them when the
> agent is running.

Geert wrote:
> Probably it's related with more workload?
> The agent takes some resourcese perhaps the error comes up at that time.
>
>
> "Steve Stewart" <sstewart14_noway_@kc.rr.com> schreef in bericht
> news:3e5hg.12371$3q2.11205@tornado.rdc-kc.rr.com...
> > Geert wrote:
> >> "Steve Stewart" <sstewart14_noway_@kc.rr.com> schreef in bericht
> >> news:%EDgg.16399$GM.1658@tornado.rdc-kc.rr.com...
> >>
> >>>Does anyone know what these errors mean? We started getting them on some
> >>>systems after installing ECC. If I shut down ECC I don't get the errors.
> >>>I found a few hits on google but no solutions.
> >>>
> >>>LABEL: FSCSI_ERR4
> >>>IDENTIFIER: 3074FEB7
> >>>
> >>>Date/Time: Fri Jun 2 15:01:12 CDT
> >>>Sequence Number: 9507
> >>>Class: H
> >>>Type: TEMP
> >>>Resource Name: fscsi1
> >>>Resource Class: driver
> >>>Resource Type: efscsi
> >>>Location: U7879.001.DQD0594-P1-C5-T1
> >>>
> >>>Description
> >>>ADAPTER ERROR
> >>>
> >>>Probable Causes
> >>>ADAPTER HARDWARE OR CABLE
> >>>ADAPTER MICROCODE
> >>>FIBRE CHANNEL SWITCH OR FC-AL HUB
> >>>
> >>>Failure Causes
> >>>ADAPTER
> >>>CABLES AND CONNECTIONS
> >>>DEVICE
> >>>
> >>>Recommended Actions
> >>>PERFORM PROBLEM DETERMINATION PROCEDURES
> >>>CHECK CABLES AND THEIR CONNECTIONS
> >>>VERIFY DEVICE CONFIGURATION
> >>>
> >>>Detail Data
> >>>SENSE DATA
> >>>0000 0000 0000 002A 0000 0000 0200 0000 0000 0000 0000 0000 0000 0000
> >>>0000 0000
> >>>0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0061 2013
> >>>0000 0000
> >>>0061 7313 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
> >>>0000 0000
> >>>0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
> >>>0000 0000
> >>>0000 0000 260D 0100 0100 0002 0000 0103 0101 0000 0000 0000 0000 0000
> >>>0000 0000
> >>>0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001
> >>>5006 0482
> >>>C095 10CA 5006 0482 C095 10CA 0200 0000 0000 0000 0000 0000 0000 0000
> >>>0000 0000
> >>>3528 E000
> >>
> >>
> >> Steve,
> >>
> >> Are you sure after installing ECC?
> >> ECC does only install an agent on the host, nothing else.
> >> This seems to be a hardware failure.
> >>
> >> Greez,
> >> Geert
> >>
> >>
> >>
> > I agree, it does look like a hardware error, but I only get them when the
> > agent is running.




I chase these around on my servers all the time. My storage people tell
me as long as powermt display looks good not to worry. I think they
must be traffic congestion out on the switches. Last week I replaced a
failed HBA on one node of a 2-node standby cluster and the fcs on the
corresponding FA port on the OTHER node began throwing these errors ...
every 4 hours .. exactly every 4 hours. .. at 37 minutes after the
hour.

I downgraded all the firmware from the 1.90 level back to the 1.81x3;
no effect at all.. Next step will be to swap that card and see if the
error goes away or moves.

We have had times when several hosts will throw Temp disk errs in
unison; when we checked into that ; we found they were plugged into a
common blade in the fibre switch.

Anybody got any experiences with this? We have pretty good EMC
support but they don't seem to be able to manage traffic thru the
switches very well; just at the endpoints; which are never very
stressed, being big DMX's.

jthomp1515@yahoo.com wrote:
> Geert wrote:
> > Probably it's related with more workload?
> > The agent takes some resourcese perhaps the error comes up at that time.

>From the IBM website: search was: FSCSI_ERR4
http://www-1.ibm.com/support/docview...id=swg1IC36979

Extract from the note:
....
Unsupported ports respond with a link
services reject (LS_RJT ) to flag that this command is not
supported by the firmware they are running. The HBA then logs it
in the AIX error log mechanism.
...
These messages are class 4 errors, are harmless and do not
impact the disk I/O. AIX suggests that these can be ignored
safely.
....

In my understanding the scanner issues a call to the hba the get san
information but the hba driver/firmware does not support it. Thus the
error message.
So i would ask the ECC ( Whatever ECC is ) how the agent / with which
calles the agent does queries the hba driver/firmware and check if the
hba driver/firmware does support this call.

hth
Hajo

Hajo Ehlers wrote:
> jthomp1515@yahoo.com wrote:
>
>>Geert wrote:
>>
>>>Probably it's related with more workload?
>>>The agent takes some resourcese perhaps the error comes up at that time.
>
>
>>From the IBM website: search was: FSCSI_ERR4
> http://www-1.ibm.com/support/docview...id=swg1IC36979
>
> Extract from the note:
> ...
> Unsupported ports respond with a link
> services reject (LS_RJT ) to flag that this command is not
> supported by the firmware they are running. The HBA then logs it
> in the AIX error log mechanism.
> ..
> These messages are class 4 errors, are harmless and do not
> impact the disk I/O. AIX suggests that these can be ignored
> safely.
> ...
>
> In my understanding the scanner issues a call to the hba the get san
> information but the hba driver/firmware does not support it. Thus the
> error message.
> So i would ask the ECC ( Whatever ECC is ) how the agent / with which
> calles the agent does queries the hba driver/firmware and check if the
> hba driver/firmware does support this call.
>
> hth
> Hajo
>
Thanks Hajo, I will check with EMC to try to find out what they are
doing. I have seen hits on this error for years, so I assume if it was
a valid call IBM would have implemented it by now. It may be a bug in
ECC, which is software to monitor SAN use and identify unused freespace.

Thanks again.

Hajo Ehlers wrote:
> jthomp1515@yahoo.com wrote:
> > Geert wrote:
> > > Probably it's related with more workload?
> > > The agent takes some resourcese perhaps the error comes up at that time.
>
> >From the IBM website: search was: FSCSI_ERR4
> http://www-1.ibm.com/support/docview...id=swg1IC36979
>
> Extract from the note:
> ...
> Unsupported ports respond with a link
> services reject (LS_RJT ) to flag that this command is not
> supported by the firmware they are running. The HBA then logs it
> in the AIX error log mechanism.
> ..
> These messages are class 4 errors, are harmless and do not
> impact the disk I/O. AIX suggests that these can be ignored
> safely.
> ...
>
> In my understanding the scanner issues a call to the hba the get san
> information but the hba driver/firmware does not support it. Thus the
> error message.
> So i would ask the ECC ( Whatever ECC is ) how the agent / with which
> calles the agent does queries the hba driver/firmware and check if the
> hba driver/firmware does support this call.
>
> hth
> Hajo

You are correct Hajo. I turned this problem in to EMC years ago. Final
resolution:

These are innocuous errors and can be ignored. I have seen this message
on Symmetrix systems running EMC Control Center and Clariion systems
running Navisphere. (typically after system reboots, sporadically for
an hour or so, then no more
errors, until the next reboot, or path fail over, or backup path status
changes)

from the dictionary: innocuous

1.) producing no injury, harmless
2.) not likely to give offense or arouse strong feelings or hostility

Most system admins can probably agree on #1, #2 debatable

Geert schrieb:

> "Steve Stewart" <sstewart14_noway_@kc.rr.com> schreef in bericht
> news:%EDgg.16399$GM.1658@tornado.rdc-kc.rr.com...
> > Does anyone know what these errors mean? We started getting them on some
> > systems after installing ECC. If I shut down ECC I don't get the errors.
> > I found a few hits on google but no solutions.
> >
> > LABEL: FSCSI_ERR4
> > IDENTIFIER: 3074FEB7
> >
> > Date/Time: Fri Jun 2 15:01:12 CDT
> > Sequence Number: 9507
> > Class: H
> > Type: TEMP
> > Resource Name: fscsi1
> > Resource Class: driver
> > Resource Type: efscsi
> > Location: U7879.001.DQD0594-P1-C5-T1
> >
> > Description
> > ADAPTER ERROR
> >
> > Probable Causes
> > ADAPTER HARDWARE OR CABLE
> > ADAPTER MICROCODE
> > FIBRE CHANNEL SWITCH OR FC-AL HUB
> >
> > Failure Causes
> > ADAPTER
> > CABLES AND CONNECTIONS
> > DEVICE
> >
> > Recommended Actions
> > PERFORM PROBLEM DETERMINATION PROCEDURES
> > CHECK CABLES AND THEIR CONNECTIONS
> > VERIFY DEVICE CONFIGURATION
> >
> > Detail Data
> > SENSE DATA
> > 0000 0000 0000 002A 0000 0000 0200 0000 0000 0000 0000 0000 0000 0000 0000
> > 0000
> > 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0061 2013 0000
> > 0000
> > 0061 7313 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
> > 0000
> > 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
> > 0000
> > 0000 0000 260D 0100 0100 0002 0000 0103 0101 0000 0000 0000 0000 0000 0000
> > 0000
> > 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 5006
> > 0482
> > C095 10CA 5006 0482 C095 10CA 0200 0000 0000 0000 0000 0000 0000 0000 0000
> > 0000
> > 3528 E000
>
> Steve,
>
> Are you sure after installing ECC?
> ECC does only install an agent on the host, nothing else.
> This seems to be a hardware failure.
>
> Greez,
> Geert

Hi Geert,

You could try the following ways to fix this issue:

A. Install the hba driver updates:
- AIX52: APAR IY81001,
- AIX53: APAR IY80999

B. Use McData firmware 8.1.1 or higher

Best regards,

Swen