Solution:
Case 1:storage Processor dials home ' 7403 ' event code
This is a more conventional error, but it does not in itself explain the cause of the problem. This event indicates an SP failure, and only the alarm or analysis Spcollect in Unisphere is the key to finding the source of the problem. Check that the problem requires spcollect on both sides of the SP and must be collected after the problem occurs (ensure that the problem event is included), and then upload the log to service center or Powerlink. For information on how to obtain Spcollect, see: How to collect CLARiiON SP logs using SP collect to improve the efficiency of problem diagnosis
Case 2:storage Processor dials home ' 20c0 ' event code
This event indicates that the SP is busy and cannot respond to at least one critical event. It is a timeout event, typically associated with an SP reboot. The event itself does not explain the cause of the problem. Only the alarm or analysis spcollects in Unisphere is the key to finding the root of the problem. Check that this issue requires spcollect on both sides of the SP, must be collected after the problem occurs (make sure that the problem event is included), and then upload the log to service center or Powerlink.
Case 3:storage Processor dials home ' A23 ' event code
B 11/04/12 06:42:55 sp A A23 Peer sp down. 3 0 0
This error indicates a peer SP failure, possibly due to suspension, downtime, bugcheck (equivalent to a blue screen of Windows). The hardware for the Peer SP still exists but is offline, and communication between Spa and SPB is interrupted. This event causes the system error led to light up and if the host failover software is configured correctly, all active LUNs should be switched to the other sp.
This event indicates that the peer SP is faulted and can be ignored if the cause of the SP reboot is known (for example, flare upgrade). Otherwise, the Spcollect and dump files (if bugcheck reboot) are required to be collected and analyzed by the technical support staff.
Case 4:storage Processor dials home ' 944 ' event code
B... SP A A23 Peer sp down. 3 0 0
B... SP B 944 Hard Peer bus Error 2 0 0
This error represents "Hard Peer bus error", which means that communication between the two SPS has been interrupted, often indicating that the Peer SP (not the SP reporting the error) has been restarted or panic. If the cause of the SP reboot is known, the event can be ignored. Otherwise, the Spcollect and dump files (if bugcheck reboot) are required to be collected and analyzed by the technical support staff. Check that the problem requires spcollect on both sides of the SP (if a dump file also needs to be uploaded), it must be collected after the problem occurs (ensure that the problem event is included), and then upload the log to service center or Powerlink.
Case 5:storage Processor is faulted (event code 7127CA2 ...) "
B flaredrv 7127ca2a SPA is faulted. Fault code:0. fru:cpu Module-part number:303-113-400b should be replaced.
A flaredrv 7127ca2b SPB is faulted. Fault code:62. Fru:cpu Module-part number:100-561-090, Fru:all Dimms-part number:unavailable is should.
A flaredrv 7127ca2c SPB is faulted. The fault cannot be isolated. Fault code:41, ' Can ' t access disks '.
A flaredrv 7127ca2d SPB is in a hung state. The state code is:45. Last state entered was: ' O/S running '.
These errors indicate that a failure was found by the peer SP and that one or more parts of the SP need to be replaced, and in the current flare and vnx OE versions, the problematic SP is logged in the error, but the event itself is logged by the normal sp. For example, in the first example, a SPA has a failure, SPB recording events. These errors are reported when the "peer SP's flare driver has started and the SP is still in the process of rebooting." Check that this issue requires spcollect on both sides of the SP, must be collected after the problem occurs (make sure that the problem event is included), and then upload the log to service center or Powerlink.