valutazioni - 0, GPA: 0
(
)
)
|
da questo dispositivo ha anche altre istruzioni :
Facilità d'uso
Chapter 3: Event Messages
36
ID
Message and Corrective Action
17005
This matrix is unable to take control of SAN, because the servers are unable
to perform fencing operations, possibly due to a networking or fencing
hardware failure or misconfiguration. As a result, some or all filesystem
operations may be paused throughout the matrix. In addition, filesystem
mounts and unmounts and disk imports and deports can not be performed.
Action. Matrix Server is unable to exclude servers that have become
unresponsive, or to verify the fencing of servers that were previously fenced
and have not yet been rebooted. Possibly the fencing device is not
responding to the fencing request or the Ethernet connection to the
FibreChannel switch has failed. Also check for other networking or SAN
hardware problems. The servers should be rebooted as soon as possible.
17006
This matrix takes control of SAN failure resolved.
Action. None. Alert 17005 is resolved.
17007
This matrix unable to take control of SAN, because the servers are unable to
write to a majority of the membership partitions, possibly due to a SAN
hardware failure or misconfiguration and/or because some servers have
been excluded from the SAN. As a result, some or all filesystem operations
may be paused throughout the matrix. In addition, filesystem mounts and
unmounts and disk imports and deports cannot be performed.
Action. Check the matrix configuration and add the server if it is not
currently a member. Also ensure that the server can access the membership
partitions and has write access to them, and check for any SAN hardware
problems.
17008
This matrix takes control of SAN failure resolved.
Action. None. Alert 17007 is resolved.
17009
This matrix unable to take control of SAN, because a majority of the
membership partitions cannot be written or are corrupt, possibly due to a
SAN hardware failure or misconfiguration and/or because servers have
been excluded from the SAN. As a result, some or all filesystem operations
may be paused throughout the matrix. In addition, filesystem mounts and
unmounts and disk imports and deports cannot be performed.
Action. Ensure that all servers can access the membership partitions and
have write access to them. If a membership partition is corrupt, another alert
will specify its location. See “Membership Partitions” in the PolyServe Matrix
Server Administration Guide for corrective actions.
...