PowerVM/VIOS FCA_ERR4/FCA_ERR12 errors on unused fibrechannel ports

How To

Summary

Usually when there are unused ports on FC adapters, it is possible to disable those ports on the adapters and stop cfgdev/cfgmgr from configuring the devices, and this will stop all the error log messages.

Objective

Prevent "FCA_ERR12: 29FA8C20" and "FCA_ERR4: 7BFEEA1F" errors.

*The steps and information provided below are intended to disable ports that are not connected and are intended to be not connected, if the errors are logged against ports that should be connected or should be in the "Available" status, please troubleshoot those adapters accordingly.

Symptoms;

The below errors maybe found on errpt;

LABEL: FCA_ERR12

IDENTIFIER: 29FA8C20

LABEL: FCA_ERR4

IDENTIFIER: 7BFEEA1F

Environment

AIX

PowerVM/VIOS

AIX 7.2 TL5 with 32 GB/s FC NVMe adapters

Steps

We need to disable the unused ports on the adapters and stop cfgdev/cfgmgr from configuring the devices and this will stop all the error log messages.

A- As padmin;

Remove the fcs# device and all child devices.

> rmdev -dev fcs# -recursive -ucfg

Set the fscsi# device to not autoconfigure.

> chdev -dev fscsi# -attr autoconfig=defined

fscsi# changed

At a future date when you need to use the port, you can enable it;

> chdev -dev fscsi# -attr autoconfig=available

fscsi# changed

Then run cfgdev to configure the devices.

> cfgdev

B- Or, as root:

Put the adapter in defined state

#rmdev -l fscsiX -R

To turn off FC protocol driver (thus error logs)

#chdev -l fscsiX -a autoconfig=defined

And to turn on FC protocol driver (thus error logs)

#chdev -l fscsiX -a autoconfig=available

C- It can also be done via Smitty;

To disable;

smitty devices ----> FC adapter ----> FC SCSI I/O Controller
Protocol Device --->Disable a FC
SCSI Protocol Device ----> Pick fscsiX device to disable

And to enable;

smitty devices ----> FC adapter ----> FC SCSI I/O Controller
Protocol Device --->Enable a FC
SCSI Protocol Device ----> Pick fscsiX device to disable

D- Or, in case of multiple servers or similar situations where a script might be needed, the below script may be run to achieve the same function, bearing in mind that all the adapters that are not connected are intended and meant to be so, so the script would not unconfigure adapters that should be connected but have the wrong status for other reasons;

disable_fcs_ent_adapters_0.txt

*Note;

For AIX 7.2 TL5, with 32 GB/s FC NVMe adapters, the procedure is done as follows;

rmdev -Rl fcnvmeX
chdev -l fcnvmeX -a autoconfig=defined

Additional Information

You can check the autoconfig attribute to determine whether it is set to "Available" or "Defined";

- On VIO 3.1.0,X;

$ lsdev -dev fscsi# -attr

attribute    value     description                           user_settable

attach       none      How this adapter is CONNECTED         False
autoconfig   available Configuration State                   True
dyntrk       yes       Dynamic Tracking of FC Devices        True+
fc_err_recov fast_fail FC Fabric Event Error RECOVERY Policy True+
scsi_id                Adapter SCSI ID                       False
sw_fc_class 3         FC Class for Fabric                   True

- As oem_setup_env(root)

# lsattr -El fscsi#

attach       none      How this adapter is CONNECTED         False
autoconfig   available Configuration State                   True
dyntrk       yes       Dynamic Tracking of FC Devices        True+
fc_err_recov fast_fail FC Fabric Event Error RECOVERY Policy True+
scsi_id                Adapter SCSI ID                       False
sw_fc_class 3         FC Class for Fabric                   True

SUPPORT
If you require more assistance, use the following step-by-step instructions to contact IBM to open a case for software with an active and valid support contract. 1. Document (or collect screen captures of) all symptoms, errors, and messages related to your issue. 2. Capture any logs or data relevant to the situation. 3. Contact IBM to open a case: -For electronic support, see the IBM Support Community: https://www.ibm.com/mysupport -If you require telephone support, see the web page: https://www.ibm.com/planetwide/ 4. Provide a clear, concise description of the issue. - For more information, see: Working with IBM AIX Support: Describing the problem. 5. If the system is accessible, collect a system snap, and upload all of the details and data for your case. - For more information, see: Working with IBM AIX Support: Collecting snap data

Click here to submit feedback for this document.

Author: Ahmed Deif

Related Information

lsattr Command

Configuring NPIV via HMC

Assigning the virtual Fibre Channel adapter to a physical Fibre Channel adapter

Document Location

Worldwide

Operating System

AIX:All operating systems listed

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG10","label":"AIX"},"Component":"","Platform":[{"code":"PF002","label":"AIX"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]

Tips