The number of device logins was reduced. One possible cause is that the
user intentionally reconfigured the system.
Action:
Check the error in the cluster error log to identify the object
ID associated with the error.
Check the availability of the failing device using the following
command line: svcinfo 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 error log and
continue with the repair verification map
If "no" or if the command lists details of the failing controller,
continue with step 3.
Check whether the device has regained connectivity.
If it has not, check the cable connection to the remote-device port.
If all logins 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.
Start a cluster discovery operation.
Check the status of the disk controller (refer to "Viewing
general details for controllers" for the user interface or Disk controller
status for the command line interface). If all disk controllers show a "good"
status, mark the error you have just repaired as "fixed." If any disk
controllers do not show "good" status, go to start map. If you return
to this step, contact the IBM support center to resolve the problem with the
disk controller.
Go to repair verification map.
Possible Cause-FRUs or other:
None
Other:
Fibre Channel network fabric (50%).
Disk drive enclosure, or disk controller, that is connected to the SAN Volume Controller (50%).