We were seeing the following errors on the VIO Servers at regular intervals and when we ran the cfgdev command to scan for new storage. The full text of the errors is at the end of this post for reference.
> errlog | more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
29FA8C20 0713105217 I O fcs3 Additional FC Adapter Information
29FA8C20 0713105217 I O fcs1 Additional FC Adapter Information
7BFEEA1F 0713105217 T H fcs3 LINK ERROR
7BFEEA1F 0713105217 T H fcs1 LINK ERROR
You may also see this error when running cfgdev.
Method error (/usr/lib/methods/cfgemfscsi -l fscsi3 ):
0514-061 Cannot find a child device.
We have the 2-Port 16Gb FC Adapter (df1000e21410f103) installed but at this time only the 1st port on each adapter is cabled to the SAN fabric. The 2nd port is being reserved for future use.
It is possible to disable the 2nd port on the adapter and stop cfgdev from configuring the devices and this will stop all the error log messages.
Remove the fcs? device and all child devices.
> rmdev -dev fcs3 -recursive -ucfg
sfwcomm3 Defined
fscsi3 Defined
fcs3 Defined
Set the fscsi? device to not autoconfigure.
> chdev -dev fscsi3 -attr autoconfig=defined
fscsi1 changed
At a future date when you need to use the port, you can enable it.
> chdev -dev fscsi3 -attr autoconfig=available
fscsi3 changed
Then run cfgdev to configure the devices.
> cfgdev
Detailed Error Log Entries - Note some data removed.
> errlog -ls | more
LABEL: FCA_ERR12
IDENTIFIER: 29FA8C20
Date/Time: Thu Jul 13 10:52:04 EET 2017
Sequence Number: 192243
Machine Id:
Node Id:
Class: O
Type: INFO
WPAR: Global
Resource Name: fcs3
Description
Additional FC Adapter Information
Recommended Actions
WAIT FOR ADDITIONAL MESSAGE BEFORE TAKING ACTION
Detail Data
SENSE DATA
0000 0020 0000 0C04 0000 0000 0000 0000 0000 0023 0000 0000
0000 0000 0000 0071 0000 0000 0000 002F 2CF0 0080 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 012C 0000 0000 0000 0000 0000 0000 0000 000A 0000 07D0
LABEL: FCA_ERR4
IDENTIFIER: 7BFEEA1F
Date/Time: Thu Jul 13 10:52:04 EET 2017
Sequence Number: 192241
Machine Id:
Node Id:
Class: H
Type: TEMP
WPAR: Global
Resource Name: fcs3
Resource Class: adapter
Resource Type: df1000e21410f10
Location: -P1-C7-C1-T2
VPD:
Part Number.................00E3495
Serial Number...............
EC Level....................D77535
Customer Card ID Number.....577F
Manufacturer................001A
FRU Number..................00E3496
Device Specific.(ZM)........3
ROM Level.(alterable).......100300
Network Address.............
Device Specific.(Z0)........0000000B
Device Specific.(Z1)........00000030
Device Specific.(Z2)........00000000
Device Specific.(Z3)........08090000
Device Specific.(Z4)........01010001
Device Specific.(Z5)........2E323532
Device Specific.(Z6)........2E323532
Device Specific.(Z7)........C0022B40
Device Specific.(Z8)........
Device Specific.(Z9)........10.2.252.1919
Device Specific.(ZA)........10.2.252.1919
Device Specific.(ZB)........00000000
Device Specific.(ZC)........00040000
Device Specific.(ZD)........000000FF
Description
LINK ERROR
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail Data
SENSE DATA
0000 0020 0000 0E45 0000 0005 0000 0000 0000 0023 0000 0000
0000 0008 0000 0071 0000 0000 0000 002F 2CF0 0080 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 012C 0000 0000 0000 0000 0000 0000 0000 000A 0000 07D0
We are using the same EN0B card direct connect to SAN. But failed to connect to. I thought you are using the fabric to 16b FC SAN. Could you share the AIX and SAN OS Model?
Thanks