Troubleshooting
Problem
AIX NPIV LPAR do not discover storage devices on the SAN.
Symptom
- Error LABEL: VIOS_VFC_CLIENT_FAI IDENTIFIER: D119376C logged in VIOS errpt log.
$ oem_setup_env
# errpt -a -j D119376C
LABEL: VIOS_VFC_CLIENT_FAIIDENTIFIER: D119376C
Date/Time: Tue Sep 16 13:21:46 2025Sequence Number: 754Machine Id: 00XXXXXXXXXXNode Id: vios1 Class: SType: TEMPWPAR: GlobalResource Name: vfchost1
DescriptionMisbehaved Virtual FC Client
Probable CausesBad IU, or Protocol Violation
Failure CausesBad IU, or Protocol Violation
Recommended Actions
Remove Virtual FC Client, then Configure the same instance
Detail DataERNUM0000 0185ABSTRACTInvalid MAD command sent before Fabric LoginAREAInitiatorBUILD INFOBLD: 2508 21-12:33:12LOCATIONFilename:npiv_cmd.c Function:npiv_mad Line:2104DATAmad->opcode = 0x00000200 proto_idx = 0x00000000proto->state = 0x0000000000270000 state = 0x00000010
Async link_down event reported on AIX NPIV LPAR (Error Number: VFC_ERR_LOC_242) and client
fcsadapter is unable to discover storage devices on the SAN (error LABEL: FCP_ERR12, errnum 0xA5 rc=ENXIO).
# errpt -a -j
LABEL: FCP_ERR12IDENTIFIER: 26623394
Date/Time: Tue Sep 16 13:21:47 2025Sequence Number: 8719Machine Id: 00XXXXXXXXXXNode Id: lpar1Class: HType: TEMPWPAR: GlobalResource Name: fscsi1Resource Class: driverResource Type: emfscsiLocation:
DescriptionCOMMUNICATION PROTOCOL ERROR
Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail DataSENSE DATA0000 0020 0000 00A5 0000 0006 0X0X 0X0X XXXX XXXX XXXX XXXX0000 000X 00XX XXX
0000 0000 0000 XXXX 0000 0000 0000 XXXX 0000 0000 0000 XXXX 0X00 0000 0000 00000000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00000000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00000000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00000000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00000000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 000000FF FFFC 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000...
LABEL: VFC4_ERR3IDENTIFIER: FE3E6B3B
Date/Time: Tue Sep 16 13:21:47 2025Sequence Number: 8718Machine Id: 00XXXXXXXXXXNode Id: lpar1Class: SType: PERMWPAR: GlobalResource Name: fcs1
DescriptionTransport event while requests are active
Probable CausesVIOS closed the CRQVIOS has crashed
Failure CausesPROCESSOR
Recommended Actions
Investigate VIO Server Partition
Detail DataError LocationFilename:vfc_sm.c Error Number:VFC_ERR_LOC_242 Function:vfc_sm Line:511 RC:0VIO Server Partition Namevios1Virtual Host Adaptervfchost1Physical Adapter Location CodeUXXXX.XX0.XXXXXXX-XX-XX-XXPhysical Adapter DRC NameUXXXX.XXX.XXXXXXX-XX-XXXXN Port ID of this adapter0000 0000 00XX XXXXAdapter State0000 0000Adapter Flags
00A0 1080Adapter Max transfer size0010 0000Number of Channels Configured0000 0008DMA size Per Channel0200 0000VFC Log DataNoDetailed Data0000 0X00 0000 0242 000X 0000 0000 0000 0000 0000 0000 0000 0000 0000 XXX0 0000...
Environment
- AIX NPIV LPAR - All Versions
- PowerVM VIOS - All Versions
- HBA with the following feature codes / CCIN's on VIOS:
FC EN0Y &EN12; CCIN ENOY
FC EN0F & EN0G; CCIN 578D
FC 5708 & 5270; CCIN 2B3B
FC EN1E, EN1F; CCIN 579A
FC EN1J, EN1K; CCIN 579C
FC EN1G, EN1H; CCIN 579B
FC EN2N, EN2P; CCIN 2F05
FC EN2L, EN2M; CCIN 2F06
Diagnosing The Problem
The summ diagnostic tool for decoding and summarizing AIX I/O error messages, aid in diagnosing storage array or SAN fabric-related problems by providing the source of the error.
The tool is used by IBM Support worldwide, and is considered safe to run in a production environment.
- VIOS:
$ oem_setup_env
# errpt -a |summ -te | grep FAI
Sep 16 13:21:46 vfchost1 T VIOS_VFC_CLIENT_FAI 00000185: NPIV_ERR_0185 Misbehaved Virtual FC Client Invalid MAD command sent before Fabric Login
- AIX NPIV LPAR
# errpt -a |summ -te|more
Sep 16 13:21:47 fscsi1 T FCP_ERR12 ioctl() send seq failure for FFFFFC; ENXIO [scsi_state LINK_DOWN| [tgt 0xFFFFFCSep 16 13:21:47 fcs1 P VFC4_ERR3 VFC_ERR_LOC_242 vios1 vfchost1 vfc transport failed or de-registered; sending async link_down
Alternatively, verify the error details as explained in the 'Symptom' section of the current document.
sw_prli_rjt.$ lsmap -vadapter vfchost1 -npiv| grep "FC name"FC name:fcs1 FC loc code:XXXXX.00X.XXXXXXX-XX-XX-XX
$ lsdev -dev fcs1 -vpd|grep Feature
Feature Code/Marketing ID...EN1G
$ oem_setup_env
# echo "cvfcs" | kdb |grep fcs1
fcs1 0xF1000XXXXXXXX000 0x00000014 0x02 (fabric) 0x00000001 0x01 0x00018E0A
Use the fcs device address from the output and execute the next command.
# echo "cvfcs -d 0xF1000XXXXXXXX000" | kdb | grep sw_prli_rjt
char sw_prli_rjt = 0x0
An effective value of 0x0 enables unrestricted self-login as well as unsolicited login activity to the port, which may prevent NPIV LPARs from discovering SAN-attached storage devices.
If all symptoms match, proceed to next step.
Resolving The Problem
sw_prli_rjt to yes (0x1)$ chdev -dev fcs1 -perm -attr sw_prli_rjt=yes
$ oem_setup_env
# bosboot -ad /dev/ipldevice
# exit
$ shutdown -restart
- Provide a good description of your issue and if any changes were made to the system.
- Collect and upload logs as instructed in Must-Gather Data for AIX I/O Device Drivers + MPIO Issues.
Related Information
Was this topic helpful?
Document Information
Modified date:
07 February 2026
UID
ibm17260048