HP MSA 1040 HP MSA Events Description Reference Guide (762785-001, March 2014) - Page 16

Reference Guide.

Get HP MSA 1040 PDF manuals and user guides View all HP MSA 1040 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 16 highlights

80 Info. The controller enabled or disabled the indicated parameters for one or more disks. Recommended actions • No action is required. 81 Info. The current controller has unkilled the partner controller. The other controller will restart. Recommended actions • No action is required. 83 Info. The partner controller is changing state (shutting down or restarting). Recommended actions • No action is required. 84 Warning The current controller that logged this event forced the partner controller to fail over. Recommended actions • See "Resources for diagnosing and resolving problems" (page 5). 86 Info. Host-port or disk-channel parameters have been changed. Recommended actions • No action is required. 87 Warning The mirrored configuration retrieved by this controller from the partner controller has a bad cyclic redundancy check (CRC). The local flash configuration will be used instead. Recommended actions • Restore the default configuration by using the restore defaults command, as described in the CLI Reference Guide. 88 Warning The mirrored configuration retrieved by this controller from the partner controller is corrupt. The local flash configuration will be used instead. Recommended actions • Restore the default configuration by using the restore defaults command, as described in the CLI Reference Guide. 89 Warning The mirrored configuration retrieved by this controller from the partner controller has a configuration level that is too high for the firmware in this controller to process. The local flash configuration will be used instead. Recommended actions • The current controller that logged this event probably has down-level firmware. Update the firmware in the down-level controller. Both controllers should have the same firmware versions. When the problem is resolved, event 20 is logged. 16 Event descriptions

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
16
Event descriptions
80
Info.
The controller enabled or disabled the indicated parameters for one or more disks.
Recommended actions
•
No action is required.
81
Info.
The current controller has unkilled the partner controller. The other controller will restart.
Recommended actions
•
No action is required.
83
Info.
The partner controller is changing state (shutting down or restarting).
Recommended actions
•
No action is required.
84
Warning
The current controller that logged this event forced the partner controller to fail over.
Recommended actions
•
See
“Resources for diagnosing and resolving problems” (page 5)
.
86
Info.
Host-port or disk-channel parameters have been changed.
Recommended actions
•
No action is required.
87
Warning
The mirrored configuration retrieved by this controller from the partner controller has a bad cyclic
redundancy check (CRC). The local flash configuration will be used instead.
Recommended actions
•
Restore the default configuration by using the
restore defaults
command, as described in the CLI
Reference Guide.
88
Warning
The mirrored configuration retrieved by this controller from the partner controller is corrupt. The local flash
configuration will be used instead.
Recommended actions
•
Restore the default configuration by using the
restore defaults
command, as described in the CLI
Reference Guide.
89
Warning
The mirrored configuration retrieved by this controller from the partner controller has a configuration level
that is too high for the firmware in this controller to process. The local flash configuration will be used
instead.
Recommended actions
•
The current controller that logged this event probably has down-level firmware. Update the firmware in
the down-level controller. Both controllers should have the same firmware versions.
When the problem is resolved, event 20 is logged.