HP AD510A HP StorageWorks 1500 Modular Smart Array maintenance and service gui - Page 43

Redundancy, Halted Firmware, Cloned, Lockup, Failed Out Of, Memory, Failed I/o Request, Error

Get HP AD510A - StorageWorks Modular Smart Array 1500 cs 2U Fibre Channel SAN Attach Controller Shelf Hard Drive PDF manuals and user guides
UPC - 829160218625
View all HP AD510A manuals
Add to My Manuals
Save this manual to your list of manuals

Page 43 highlights

Message 48 REDUNDANCY HALTED FIRMWARE CLONED 49 REDUNDANCY FAILED FIRMWARE LOCKUP 50 REDUNDANCY FAILED OUT OF MEMORY 51 REDUNDANCY FAILED I/O REQUEST ERROR Type Informational Error Error Error Description Action Both array controllers must run the same version of firmware for them to successfully enter redundant mode. A process called firmware cloning has been successfully completed in order to make them both the same firmware level. The standby array controller is restarted automatically so they can attempt to achieve redundancy again. While either attempting to enter redundant mode or already operating in redundant mode, one of the array controllers encountered a critical condition resulting in a firmware lockup. Redundancy is disabled at this time. If the MSA is currently involved in host I/O, remove the standby array controller, wait 10 seconds, and then reinsert it, ensuring that it is fully seated in the chassis. If this does not resolve the issue, wait until downtime is available. Power off the MSA, remove both array controllers, and reinsert them, ensuring they are fully seated in the chassis. Should the issue persist, contact HP support. While either attempting to enter redundant mode or already operating in redundant mode, one of the array controllers failed to allocate required memory. Redundancy is disabled at this time. If the MSA is currently involved in host I/O, remove the standby array controller, wait 10 seconds, and then reinsert it ensuring that it is fully seated in the chassis. If this does not resolve the issue, wait until downtime is available. Power off the MSA, remove both array controllers, and reinsert them, ensuring they are fully seated in the chassis. Should the issue persist, contact HP support. While either attempting to enter redundant mode or already operating in redundant mode, one of the array controllers encountered an error while sending I/O between the two array controllers over the communication channel between them. Redundancy is disabled at this time. If the MSA is currently involved in host I/O, remove the standby array controller, wait 10 seconds, and then reinsert it, ensuring that it is fully seated in the chassis. If this does not resolve the issue, wait until downtime is available. Power off the MSA, remove both array controllers, and reinsert them, ensuring they are fully seated in the chassis. Should the issue persist, contact HP support. maintenance and service guide 43

  • 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
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
Message
Type
Description
Action
48 REDUNDANCY
HALTED FIRMWARE
CLONED
Informational
Both array controllers
must run the same version
of
fi
rmware for them to
successfully enter redundant
mode. A process called
fi
rmware cloning has been
successfully completed in
order to make them both
the same
fi
rmware level.
The
standby
array controller
is restarted automatically so
they can attempt to achieve
redundancy again.
49 REDUNDANCY
FAILED FIRMWARE
LOCKUP
Error
While either attempting
to enter redundant mode
or already operating in
redundant mode, one
of the array controllers
encountered a critical
condition resulting in
a
fi
rmware lockup.
Redundancy is disabled at
this time.
If the MSA is currently
involved in host I/O, remove
the
standby
array controller,
wait 10 seconds, and then
reinsert it, ensuring that it is
fully seated in the chassis.
If this does not resolve the
issue, wait until downtime
is available. Power off the
MSA, remove both array
controllers, and reinsert
them, ensuring they are fully
seated in the chassis.
Should the issue persist,
contact HP support.
50 REDUNDANCY
FAILED OUT OF
MEMORY
Error
While either attempting
to enter redundant mode
or already operating in
redundant mode, one of the
array controllers failed to
allocate required memory.
Redundancy is disabled at
this time.
If the MSA is currently
involved in host I/O, remove
the
standby
array controller,
wait 10 seconds, and then
reinsert it ensuring that it is
fully seated in the chassis.
If this does not resolve the
issue, wait until downtime
is available. Power off the
MSA, remove both array
controllers, and reinsert
them, ensuring they are fully
seated in the chassis.
Should the issue persist,
contact HP support.
51 REDUNDANCY
FAILED I/O REQUEST
ERROR
Error
While either attempting
to enter redundant mode
or already operating in
redundant mode, one
of the array controllers
encountered an error while
sending I/O between the
two array controllers over
the communication channel
between them. Redundancy
is disabled at this time.
If the MSA is currently
involved in host I/O, remove
the
standby
array controller,
wait 10 seconds, and then
reinsert it, ensuring that it is
fully seated in the chassis.
If this does not resolve the
issue, wait until downtime
is available. Power off the
MSA, remove both array
controllers, and reinsert
them, ensuring they are fully
seated in the chassis.
Should the issue persist,
contact HP support.
maintenance and service guide
43