Dell AX4-5 - Manual (Page 64)

64
Troubleshooting
Attempts to connect
to a cluster using
Cluster Administrator
fail. • The Cluster Service
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.
The cluster network
name is not
responding on the
network because the
Internet Connection
Firewall is enabled on
one or more nodes. Configure the Internet Connection
Firewall to allow communications
that are required by WSFC and the
clustered applications or services.
You are prompted to
configure one network
instead of two during
WSFC installation. The TCP/IP
configuration
is incorrect. The node-to-node network and
public network must be assigned
static IP addresses on different
subnets. See "Assigning Static IP
Addresses to Cluster Resources and
Components" on page 22 for
information about assigning the
network IPs.
The private (point-to-
point) network is
disconnected. Ensure that all systems are powered
on so that the NICs in the private
network are available.
Table A-1. General Cluster Troubleshooting (continued)
Problem Probable Cause Corrective Action