Dell PowerVault NX1950 Panduan Instalasi dan Pemecahan Masalah - Halaman 35

Jelajahi secara online atau unduh pdf Panduan Instalasi dan Pemecahan Masalah untuk Server Dell PowerVault NX1950. Dell PowerVault NX1950 48 halaman. For vmware esx server software
Juga untuk Dell PowerVault NX1950: Panduan Penyebaran (34 halaman), Panduan Informasi Penting (26 halaman), Memulai (49 halaman), Panduan Penyebaran (38 halaman), Panduan Peningkatan (18 halaman), Panduan Referensi (4 halaman), Menyiapkan (2 halaman), Menggunakan (2 halaman), Panduan Konfigurasi (11 halaman)

Halaman Cetak
Dell PowerVault NX1950 Panduan Instalasi dan Pemecahan Masalah

Troubleshooting

®
Microsoft
Windows
cluster troubleshooting. To access this Help and Support content:
→
1 Click Start
2 The Help and Support window appears. Search for content related to
Cluster Troubleshooting.
In the search results, locate and select the Troubleshooting: Server Cluster
option. This section gives you information about general cluster
troubleshooting.
This section contains common issues you may encounter on your
Dell™ PowerVault™ NX1950 cluster solution.
Table A-1. General Cluster Troubleshooting
Problem Area
Network
Communication
The nodes cannot
access the storage
system, or the cluster
software is not
functioning with the
storage system.
®
Unified Data Storage Server 2003 provides general
Help and Support.
Probable Cause
The storage system is not
cabled properly to the
nodes or the cabling
between the storage
components is incorrect.
One of the cables or
connectors is faulty.
The TCP/IP
configuration is
incorrect.
IP addresses not
configured correctly.
Corrective Action
Ensure that all external
cables are securely attached
to the external connectors on
your system. For an example
of supported cabling
configuration, see "Other
Documents You May Need"
on page 13.
Ensure that the cables or
connectors are not damaged.
Ensure that the cluster nodes
are on the same subnet to
prevent network
communication errors.
The cluster heartbeat IP
address should be on a
different subnet than the
cluster IP address.
Troubleshooting
A
35