The problem we have been experiencing is as follows :-
When connecting to the SQL Resource IP address from the Web Server, very basic test using ping, occasionally the web server will lose connectivity,when connectivity is lost the following conditions are true
1.The server cannot ping the SQL resource IP address
2.The server is unable to make a TCP connection to the server (tested using and ODBC to TCP Port 1433)
3.The server can ping the Windows cluster address, and the individual servers IP addresses
4.The servers arp cache (arp -a) shows that the SQL resource IP address has been given a MAC address from a card on the passive SQL server.
5.If you delete the arp cache (arp -d *) sometimes the sever will get connectivity back sometime not (I am presuming you have a 2/4 chance of getting a MAC address on the active SQL server.
6.If you add a static arp entry (arp -s ??-??-??-??-??-??) to set SQL resource IP address to a MAC address of a card on the active SQL server you get connectivity back.
When connecting to the SQL Resource IP address from the Web Server, very basic test using ping, occasionally the web server will lose connectivity,when connectivity is lost the following conditions are true
1.The server cannot ping the SQL resource IP address
2.The server is unable to make a TCP connection to the server (tested using and ODBC to TCP Port 1433)
3.The server can ping the Windows cluster address, and the individual servers IP addresses
4.The servers arp cache (arp -a) shows that the SQL resource IP address has been given a MAC address from a card on the passive SQL server.
5.If you delete the arp cache (arp -d *) sometimes the sever will get connectivity back sometime not (I am presuming you have a 2/4 chance of getting a MAC address on the active SQL server.
6.If you add a static arp entry (arp -s ??-??-??-??-??-??) to set SQL resource IP address to a MAC address of a card on the active SQL server you get connectivity back.
