Votos - 0, Puntuación media: 0
(
)
)
|
Otros manuales para este modelo:
Resumen del manual
Chapter 3: Event Messages
31
ID
Message and Corrective Action
13907
Reboot
and may be dirty, but attempts to exclude it from the SAN were
unsuccessful. Rebooting it will allow normal cluster operation to continue.
Alternatively, if the server cannot be rebooted, but can be confirmed to have
no access to the SAN, run ‘mx server markdown
cluster operation.
Action. HP Clustered File System cannot fence a server that is no longer
communicating with the cluster. Either reboot the server or run the mx
server markdown command to restore normal operations. Before using mx
server markdown, be sure that the server is physically down. If the
command is run on a server that is not down, filesystem corruption can
occur. See “Server Cannot Be Fenced” in the HP StorageWorks Clustered File
System Administration Guide for more information about the mx server
markdown command.
13908
Server
Action. None. Alert 13907 is resolved.
13909
Membership partitions are corrupt or inaccessible, preventing SAN access.
Action. Determine the state of each membership partition. Open the
Configure Cluster window and go to the Storage Settings tab, which shows
the state of each partition. If a single membership partition is corrupt, use
the Repair feature to resilver the partition while the cluster is online. If two
partitions are corrupt, shut down the cluster on all nodes and then resilver
the partitions. If all of the membership partitions are corrupt, you will need
to restore the partitions from a backup.
If the state for a partition is NOT FOUND or INACCESSIBLE, there may be
a problem with the disk containing the partition or with another SAN
component. When the problem is repaired, the status should return to OK.
13910
Inaccessible membership partition resolved.
Action. None. Alert 13909 is resolved.
13911
DiskImportError:
When the cluster configuration was imported to the server, it was not able to
access the specified disk. The filesystems on the disk were not mounted on
the server.
Action. To correct this problem, first verify that the server has physical
access to the disk in question and that the disk is not experiencing hardware
problems. Then attempt a reboot. If the same error occurs after one reboot,
contact HP Support.
...Otros modelos de este manual:
datos de dispositivos de procesamiento - HP DL380-SL Clustered Gateway (604.47 kb)
datos de dispositivos de procesamiento - HP ProLiant DL380G5-WSS Storage Server Clustered Gateway (604.47 kb)
datos de dispositivos de procesamiento - HP ProLiant DL380G5-WSS Storage Server Initial Cluster (604.47 kb)
datos de dispositivos de procesamiento - HP 3PAR StoreServ File Controller v2 Storage (604.47 kb)