Event ID — 2137
Description | Communication |
Severity | Warning / |
Cause and | Cause: The controller is unable to communicate with an enclosure. There are |
Action | several reasons why communication may be lost. For example, there may be a bad |
| or loose cable. An unusual amount of I/O may also interrupt communication with |
| the enclosure. In addition, communication loss may be caused by software, |
| hardware, or firmware problems, bad or failed power supplies, and enclosure |
| shutdown. |
| When viewed in the alert log, the description for this event displays several |
| variables. These variables are: controller and enclosure names, type of |
| communication problem, return code, and SCSI status. |
| Action: Check for problems with the cables. See the online help for more |
| information on checking the cables. You should also check to see if the enclosure |
| has degraded or failed components. To do so, select the enclosure object in the |
| tree view and click the Health subtab. The Health subtab displays the status of the |
| enclosure components. Verify that the controller has supported driver and |
| firmware versions installed and that the EMMs are each running the same version |
| of supported firmware. |
Related Alert | Clear Alert Number: 2162 |
Information | Related Alert Number: None |
| Local Response Agent (LRA) Number: 2090 |
SNMP Trap | 853 |
Numbers |
|
Event ID — 2138 | |
Description | Enclosure alarm enabled. |
Severity | OK / Normal / Informational |
Cause and | Cause: A user has enabled the enclosure alarm. This alert is for informational |
Action | purposes. |
| Action: None |
Related Alert | Clear Alert Number: None |
Information | Related Alert Number: None |
| Local Response Agent (LRA) Number: None |
SNMP Trap | 851 |
Numbers |
|
86
