4.0.0 HP Polyserve Matrix Server Event Notification Guide (T5392-96053, March 2010)

Message and Corrective ActionID
Majority of membership partitions are unwritable, possibly due to a SAN or storage
hardware failure. As a result, disk imports and deports cannot be done, and some
servers may be unable to mount filesystems. In addition, Matrix Server’s ability to
recover from a future server failure is compromised. Such a failure would leave
Matrix Server no option but to pause some or all filesystems throughout the matrix
to preserve filesystem integrity.
Action. The servers in the matrix cannot write to the majority of the membership
partitions. Ensure that the servers can access the membership partitions and have
write access to them. If the disks containing the membership partitions have failed,
you will need to recreate the partitions. (See “Membership partitions” in the Matrix
Server administration guide for more information.)
17015
Inaccessible majority of membership partitions resolved.
Action. None. Alert 17015 is resolved.
17016
Membership partition <partition> is unwritable, possibly due to a SAN or
storage hardware failure. If other membership partitions become inaccessible,
Matrix Server’s ability to recover from a server failure will be compromised.
Action. None of the servers in the matrix can write to the specified membership
partition. Ensure that the servers can access the membership partition and that
they have write access for it. If the partition is corrupt, another alert will display
the location of the partition. (See “Membership partitions” in the Matrix Server
administration guide for more information.)
17017
Inaccessible membership partition resolved.
Action. None. Alert 17017 is resolved.
17018
<server> is unresponsive and must be rebooted ASAP. Until this reboot is done,
some or all filesystem operations may be paused throughout the matrix.
Action. The specified server did not respond to a critical request. This problem
may be caused by a severe overload or resource shortage on the server. Rebooting
the server should clear the problem.
17019
Unresponsive server <server> resolved.
Action. None. Alert 17019 is resolved.
17020
Event messages38