Dell PowerVault 775N (Rackmount NAS Appliance) User Manual
Page 82
time to join the cluster.
due to a cabling or hardware failure.
Long delays in node-to-node
communications may be normal.
to-node interconnection and the public network
are connected to the correct network adapters.
Verify that the nodes can communicate with each
other by running the ping command from each
node to the other node. Try both the host name
and IP address when using the ping command.
You are prompted to configure
one network instead of two
during MSCS installation.
The TCP/IP configuration is incorrect.
The private (point-to-point) network is
disconnected.
The node-to-node network and public network
must be assigned static IP addresses on different
subnets. See "
Assigning Static IP Addresses to
Your Cluster Resources and Components
" for
information about assigning the network IPs.
Ensure that both systems are powered on so that
both network adapters in the private network are
available.
Client systems are dropping
off of the network while the
cluster is failing over.
With MSCS, the service provided by the
recovery group becomes temporarily
unavailable to clients during failover.
Clients may lose their connection if
their attempts to reconnect to the
cluster are too infrequent or if they end
too abruptly.
The time that the service is temporarily
unavailable varies depending on the application.
Contact the application program vendor for more
information.
Only one network segment
appears during Cluster Service
installation.
Public and private networks segments
are not unique.
Place all installed network adapters in a cluster
node on separate IP networks.
Ensure that the same network segments that
were used for each network adapter are identical
on the second cluster node.
Attempts to connect to a
cluster using Cluster
Administrator fail.
The Cluster Service (MSCS) has not
been started.
A cluster has not been formed on the
system.
The system has just been booted and
services are still starting.
Verify that the Cluster Service is running and that
a cluster has been formed. Use the Event Viewer
and look for the following events logged by the
Cluster Service:
Microsoft Cluster Service successfully
formed a cluster on this node.
or
Microsoft Cluster Service successfully
joined the cluster.
If these events do not appear in Event Viewer,
see the Microsoft Cluster Service Administrator's
Guide for instructions on setting up the cluster on
your system and starting the Cluster Service.
Using Microsoft Windows
NT® 4.0 to remotely
administer a Windows Storage
Server 2003, Enterprise
Edition cluster generates error
messages.
Normal. Some resources in
Windows Storage Server 2003,
Enterprise Edition are not supported in
Windows NT 4.0.
Dell strongly recommends that you use Windows
XP Professional or Windows Storage Server 2003,
Enterprise Edition for remote administration of a
cluster running Windows Storage Server 2003,
Enterprise Edition.
MSCS does not show any
available shared disks during
installation.
The PERC drivers are not installed in
the operating system.
Disks are configured as dynamic disks.
Install the drivers. See the PERC documentation
for more information.
Change disks to "basic" before cluster installation.
See "
" for more
information on configuring dynamic disks as basic
disks.
One of the nodes can access
one of the shared hard drives,
but the second node cannot.
If MSCS is installed, this
situation is normal.
If MSCS is installed, only the node that owns the
disk resource will be able to access the disk. The
other node will show the disk resource as offline
in Windows Disk Management.