Table
Problem | Probable Cause | Corrective Action |
|
|
|
You are prompted to configure | The TCP/IP configuration is | The |
one network instead of two | incorrect. | network must be assigned static IP |
during MSCS installation. |
| addresses on different subnets. See |
|
| "Assigning Static IP Addresses to Your |
|
| Cluster Resources and Components" for |
|
| information about assigning the |
|
| network IPs. |
| The private | Ensure that both systems are powered on |
| network is disconnected. | so that both network adapters in the |
|
| private network are available. |
|
|
|
Client systems are dropping off | With MSCS, the service | The time that the service is temporarily |
of the network while the cluster | provided by the recovery | unavailable varies depending on the |
is failing over. | group becomes temporarily | application. Contact the application |
| unavailable to clients during | program vendor for more information. |
| failover. Clients may lose |
|
| their connection if their |
|
| attempts to reconnect to the |
|
| cluster are too infrequent or |
|
| if they end too abruptly. |
|
|
|
|
Only one network segment | Public and private networks | Place all installed network adapters in a |
appears during Cluster Service | segments are not unique. | cluster node on separate IP networks. |
installation. |
|
|
|
| Ensure that the same network segments |
|
| that were used for each network adapter |
|
| are identical on the second cluster node. |
Troubleshooting
89