We have a few Exchange 2003 clusters, and overall they run fine. But once in a while an issue with public NICs causes the cluster to fail-over back and forth and even cluster service to stop on both nodes, an of course Exchange gets shut down not so gracefully. Often the nodes start fighting over the disks.
The cluster nodes are Windows 2003 Ent SP1, running on HP Proliant DL380 G4 boxes with an HP MSA1000 disk array, attached with dual fiber links to each node. The cluster private NICs are connected via a crossover cable. The public NICs are connected to different switches. In the properties of the cluster, under the Network Priority tab, the Cluster Private link is on top and the Public link is on the bottom. The Cluster Private link is designated for internal cluster communications only. The Public link is designated for all communications (per cluster whitepaper recommendations) This happened once a while ago - local IT were mucking with speed/duplex setting on the public NICs and the whole cluster crashed (first ping-pong, then fighting over the disks, then cluster services stopped) And today there was a switch failure that caused the cluster to crash in the same manner. I am thinking that using the Public NICs for all communications has something to do with it and maybe I should set the public NICs for public access only. How do you set up your clusters? TIA _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
