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

The RAID metadata level of the two controllers does not match, which indicates that the controllers

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 22 highlights

162 Warning The host WWNs (node and port) previously presented by this controller module are unknown. In a dual-controller system this event has two possible causes: • One or both controller modules have been replaced or moved while the system was powered off. • One or both controller modules have had their flash configuration cleared (this is where the previously used WWNs are stored). The controller module recovers from this situation by generating a WWN based on its own serial number. Recommended actions • If the controller module was replaced or someone reprogrammed its FRU ID data, verify the WWN information for this controller module on all hosts that access it. 163 Warning The host WWNs (node and port) previously presented by the partner controller module, which is currently offline, are unknown. This event has two possible causes: • The online controller module reporting the event was replaced or moved while the system was powered off. • The online controller module had its flash configuration (where previously used WWNs are stored) cleared. The online controller module recovers from this situation by generating a WWN based on its own serial number for the other controller module. Recommended actions • If the controller module was replaced or someone reprogrammed its FRU ID data, verify the WWN information for the other controller module on all hosts that access it. 166 Warning The RAID metadata level of the two controllers does not match, which indicates that the controllers have different firmware levels. Usually, the controller at the higher firmware level can read metadata written by a controller at a lower firmware level. The reverse is typically not true. Therefore, if the controller at the higher firmware level failed, the surviving controller at the lower firmware level cannot read the metadata in disks that have failed over. Recommended actions • If this occurs after a firmware update, it indicates that the metadata format changed, which is rare. Update the controller with the lower firmware level to match the firmware level in the other controller. 167 Warning A diagnostic test at controller bootup detected an abnormal operation, which might require a power cycle to correct. Recommended actions • See "Resources for diagnosing and resolving problems" (page 5). 22 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
22
Event descriptions
162
Warning
The host WWNs (node and port) previously presented by this controller module are unknown. In a
dual-controller system this event has two possible causes:
•
One or both controller modules have been replaced or moved while the system was powered off.
•
One or both controller modules have had their flash configuration cleared (this is where the previously
used WWNs are stored).
The controller module recovers from this situation by generating a WWN based on its own serial number.
Recommended actions
•
If the controller module was replaced or someone reprogrammed its FRU ID data, verify the WWN
information for this controller module on all hosts that access it.
163
Warning
The host WWNs (node and port) previously presented by the partner controller module, which is currently
offline, are unknown.
This event has two possible causes:
•
The online controller module reporting the event was replaced or moved while the system was
powered off.
•
The online controller module had its flash configuration (where previously used WWNs are stored)
cleared.
The online controller module recovers from this situation by generating a WWN based on its own serial
number for the other controller module.
Recommended actions
•
If the controller module was replaced or someone reprogrammed its FRU ID data, verify the WWN
information for the other controller module on all hosts that access it.
166
Warning
The RAID metadata level of the two controllers does not match, which indicates that the controllers have
different firmware levels.
Usually, the controller at the higher firmware level can read metadata written by a controller at a lower
firmware level. The reverse is typically not true. Therefore, if the controller at the higher firmware level
failed, the surviving controller at the lower firmware level cannot read the metadata in disks that have
failed over.
Recommended actions
•
If this occurs after a firmware update, it indicates that the metadata format changed, which is rare.
Update the controller with the lower firmware level to match the firmware level in the other controller.
167
Warning
A diagnostic test at controller bootup detected an abnormal operation, which might require a power cycle
to correct.
Recommended actions
•
See
“Resources for diagnosing and resolving problems” (page 5)
.