1630: The number of device logins was reduced.

Explanation

The number of port to port fabric connections, or logins, between the node and a storage controller has decreased. This situation might be caused by a problem on the SAN or by a deliberate reconfiguration of the SAN.

The 1630 error code is reported for a number of different error IDs. The error ID indicates more specifics about the problem. The data reported in an event log entry indicates where the condition was found.

010045 Number of Device paths from the controller site allowed accessible nodes has reduced

• The controller now has fewer logins from the controller site that allocated accessible nodes to the storage controller.
• The error data indicates the WWNN or IP address of the disk controller, and the current path count from each node.
• A controller fault or a Fibre Channel network fabric fault might cause this condition.

User Response

1. Check the error in the cluster event log to identify the object ID associated with the error.
2. Check the availability of the failing device using the following command line: lscontroller object_ID. If the command fails with the message "CMMVC6014E The command failed because the requested object is either unavailable or does not exist," ask the customer if this device was removed from the system.
   • If "yes", mark the error as fixed in the cluster event log and continue with the repair verification MAP.
   • If "no" or if the command lists details of the failing controller, continue with the next step.
3. Check whether the device has regained connectivity. If it has not, check the cable connection to the remote-device port.
4. If all attempts to log in to a remote-device port have failed and you cannot solve the problem by changing cables, check the condition of the remote-device port and the condition of the remote device.
5. Start a cluster discovery operation by rescanning the Fibre Channel network.
6. Check the status of the disk controller. If all disk controllers show a "good" status, mark the error that you have just repaired as "fixed". If any disk controllers do not show "good" status, go to the start MAP. If you return to this step, contact the support center to resolve the problem with the disk controller.
7. Go to repair verification MAP.

Possible Cause-FRUs or other:

• None

Other:

• Fibre Channel network fabric fault (50%)
• Enclosure/controller fault (50%)