Cluster problem in Win 2003

[Muhammad Shamroze]

Hello, Im using Two node clustering with MSA 500 G@ as shared storage one node is PROD A and another one PROD AB....as my clustering was working fine but after few days there is problem on PROD AB node as my package is on PROD A and PROD A is active node but when i want to shift the package to PROD AB...Error occurs as there is Two IP assign to Both nodes ....on PROD AB there is Public IP i.e 160.1.0.1 and Heart beat IP is 192.168.10.1 and on PROD A Public IP i.e 160.1.0.2 and Heart beat IP is 192.168.10.2 and the package IP is 160.1.0.3 but the problem is as in Cluster administration the node PROD AB is showing red cross sign and the PROD AB node Public IP and Heart Beat IP status is unavialable in Cluster Admin software ..as the PROD A node Public IP and Heart beat IP status is available and working fine and also cluster and package is working fine but the problem is on PROD AB..so my question is what should be done so that my Public IP and Heart beat IP status available on PROD AB..?

One thing more to add as both node Public and Heart Beat IP's and plus the Package IP(virtual IP) are pinging on both nodes but when using Cluster Administration Software to start the cluster on PROD AB is giving error and both Public IP and Heart Beat IP showing status unavailable so ...i want these IP Available so that my cluster also start on PROD AB the failover node ...kindly help me in this regards

[Rune J. Winje]

The IP's look good. The Heartbeat and public are on different network segments like they should be.

Also check the following:
* That the cabling is correct.
- to test this: disconnect a cable on the PROD AB and see that the corresponding NIC looses connection in Network Connections.
- check that you are not able to ping the disconnected NIC's IP from the other node.

* Check that the Heartbeat card is configured for "Internal Cluster communication only"

* Check that the Heartbeat card has disabled NETBIOS and DNS registration.


Cheers,
Rune