Q
Problem solve Get help with specific problems with your technologies, process and projects.

NIC teaming for interconnect

We have a three-node 9.2 cluster on Windows 2000 that we will be moving onto new hardware to be a two-node 9.2 cluster on Windows 2003, and I was interested in your thoughts on NIC teaming for the interconnect, as I haven't found much at all out there on what is recommended/certified and what is not.

Hopefully a relatively quick one -- we have a three-node 9.2 cluster on Windows 2000 that we will be moving onto new hardware to be a two-node 9.2 cluster on Windows 2003, and I was interested in your thoughts on NIC teaming for the interconnect, as I haven't found much at all out there on what is recommended/certified and what is not. We have teaming in place for the current setup using Intel's PROSet software. Do you recommend it versus just a single cable? If so do you always do cable pull tests ahead of go-live to ensure that it works as expected? If you could send through any links you know of on this topic that would be great.
NIC teaming is supported and highly recommened over a single cable, otherwise you have an unacceptable single point of failure.

I always pull the cable and ping through the private address as part of my QA testing before going live.

Here is a white paper sponsored by Dell, Oracle and Microsoft that sounds very similar to what you plan on doing. They document the installation of 9i RAC on Windows 2003 and use PROset to team their NICs.

Good luck,
Bill

Dig Deeper on Oracle database availability

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close