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

Error, Warning

Page 56 highlights

479 Error The controller reporting this event was unable to flush data to or restore data from non-volatile memory. This mostly likely indicates a CompactFlash failure, but it could be caused by some other problem with the controller module. The Storage Controller that logged this event will be killed by its partner controller, which will use its own copy of the data to perform the flush or restore operation. Recommended actions • If this is the first time this event has been logged, restart the killed Storage Controller. • If this event is then logged again, replace the controller module. 480 Error An IP address conflict was detected for the indicated iSCSI port of the storage system. The indicated IP address is already in use. Recommended actions • Contact your data-network administrator to help resolve the IP address conflict. 481 Error The periodic monitor of CompactFlash hardware detected an error. The controller was put in write-through mode, which reduces I/O performance. Recommended actions • Restart the Storage Controller that logged this event. • If this event is logged again, shut down the Storage Controller and replace the controller module. 482 Warning One of the PCIe buses is running with fewer lanes than it should. This event is the result of a hardware problem that has caused the controller to use fewer lanes. The system works with fewer lanes, but I/O performance is degraded. Recommended actions • Replace the controller module that logged this event. 483 Error An invalid expansion-module connection was detected for the indicated disk channel. An egress port is connected to an egress port, or an ingress port is connected to an incorrect egress port. Recommended actions • Visually trace the cabling between enclosures and correct the cabling. 56 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

56
Event descriptions
479
Error
The controller reporting this event was unable to flush data to or restore data from non-volatile memory.
This mostly likely indicates a CompactFlash failure, but it could be caused by some other problem with the
controller module. The Storage Controller that logged this event will be killed by its partner controller,
which will use its own copy of the data to perform the flush or restore operation.
Recommended actions
If this is the first time this event has been logged, restart the killed Storage Controller.
If this event is then logged again, replace the controller module.
480
Error
An IP address conflict was detected for the indicated iSCSI port of the storage system. The indicated IP
address is already in use.
Recommended actions
Contact your data-network administrator to help resolve the IP address conflict.
481
Error
The periodic monitor of CompactFlash hardware detected an error. The controller was put in
write-through mode, which reduces I/O performance.
Recommended actions
Restart the Storage Controller that logged this event.
If this event is logged again, shut down the Storage Controller and replace the controller module.
482
Warning
One of the PCIe buses is running with fewer lanes than it should.
This event is the result of a hardware problem that has caused the controller to use fewer lanes. The
system works with fewer lanes, but I/O performance is degraded.
Recommended actions
Replace the controller module that logged this event.
483
Error
An invalid expansion-module connection was detected for the indicated disk channel. An egress port is
connected to an egress port, or an ingress port is connected to an incorrect egress port.
Recommended actions
Visually trace the cabling between enclosures and correct the cabling.