1230 A login has been excluded.
Explanation
A port-to-port fabric connection, or login, between the clustered system node and either a controller or another clustered system has excessive errors. Therefore, the login is excluded, and is not used for I/O operations.
User response
Determine the remote system, which might be either a controller or a clustered system. Check the event log for other 1230 errors. Ensure that all higher priority errors are fixed.
This error event is usually caused by a fabric problem. If possible, use the fabric switch or other fabric diagnostic tools to determine which link or port is reporting the errors. If there are error events for links from this node to a number of different controllers or clustered systems, then it is probably the node-to-switch link that is causing the errors. Unless there are other indications to the contrary, first replace the cable between the switch and the remote system.
- From the fabric analysis, determine the FRU that is most likely causing the error. If this FRU was recently replaced while you resolved a 1230 error, choose the next most likely FRU that was not replaced recently. Exchange the FRU for a new FRU.
- Mark the error as fixed. If the FRU replacement does not fix the problem, the error is logged again; however, depending on the severity of the problem, the error might not be logged again immediately.
- Start a cluster discovery operation to recover the login by rescanning the Fibre Channel network.
- Check the status of the disk controller or remote cluster. If
the status is not
good
, go to the Start MAP. - Go to repair verification MAP.
Possible Cause-FRUs or other:
- Fibre Channel cable, switch to remote port, (30%)
- Switch or remote device SFP connector or adapter, (30%)
- Fibre Channel cable, local port to switch, (30%)
- Cluster SFP connector, (9%)
- Cluster Fibre Channel adapter, (1%)