Intergraph WebScale User Manual page 69

WebScale™
the network is unreachable, the dialog will encounter a temporary delay. Be sure
to use the initial license key until WebScale has been installed and network
access has been established.
Problem: Cluster does not converge.
Description: After I start the cluster hosts, they start converging but never report that
convergence has completed.
Probable cause(s) and resolution:
2. You entered either a different number of port rules or incompatible port rules on
different cluster hosts. This will inhibit convergence. Run the WebScale Setup
dialog on each cluster host and verify that all hosts have identical port rules.
Problem: Multiple default hosts.
Description: After I start the cluster hosts, they report that convergence has completed,
but more than one host is a default.
Probable cause(s) and resolution:
The cluster hosts have become subnetted so that all hosts are not reachable on the
same network. Be sure that all cluster hosts can communicate with each other.
3. Different network addresses are being used across the cluster, and the cluster's
primary IP address was not entered into the TCP/IP configuration for the
WebScale Virtual NIC. In this case, TCP/IP will not detect an address conflict,
and multiple clusters will exist. Be sure to use one cluster primary IP address and
a corresponding network address on all hosts within the same cluster, and be sure
to enter the primary IP address in the TCP/IP configuration for the WebScale
virtual NIC.
4. Different clusters are running on the same subnet. If you use different primary IP
addresses, each with unique corresponding network addresses, on various cluster
hosts, you can create multiple clusters on the same subnet. This is a not a
problem unless this behavior was not intended.
Problem: Network failure or erratic behavior for cluster hosts
Description: The network doesn't appear to work for one or more of the cluster hosts.
(For specific network problems, also see problems that follow.)
Probable cause(s) and resolution:
1. The WebScale driver did not load successfully when the system initialized. This
problem can arise because another networking driver on which WebScale
depends failed to load or because the WebScale driver file has been corrupted.
Run the webscale query command to verify that the driver loaded. If the
command reports an error, check the Windows NT Event Log to see why the
driver failed to load.
2. You may have a network problem unrelated to WebScale. To verify that
WebScale is not at fault, unbind the WebScale Virtual NIC from the TCP/IP
protocol in the Windows NT Network dialog and rebind TCP/IP directly to the
65
User's Guide