07-24-2008 06:09 AM - edited 03-06-2019 12:26 AM
Hi,
I want to design my network such that my server can still be accessible in the event of a network interface failure (on server), cable failure or switch failure. See attached diagram.
For example - the web server is 192.168.1.1. Even if one link fails, or one network interface (on switch or server) fails, or one switch fails - the server (Linux or Windows) can still be accessibble.
What can I use to achieve this? I know there's EtherChannel - but I think it can only do dual connections to a single switch. But what if this single switch fails?
Any recommendations/suggestions?
Thanks,
Tony
Solved! Go to Solution.
07-24-2008 06:37 AM
NIC Teaming in your server. Make sure each NIC is connected to different switch and the switch are connected together.
07-24-2008 08:18 AM
07-24-2008 10:21 AM
More information on Teaming:
07-24-2008 06:37 AM
NIC Teaming in your server. Make sure each NIC is connected to different switch and the switch are connected together.
07-24-2008 10:21 AM
More information on Teaming:
07-24-2008 08:18 AM
07-25-2008 05:33 AM
If the switches are Cisco stackable (3750) switches you can use NIC teaming and create an etherchannel that has one link on each switch. In that setup, you get high availability AND you get twice the bandwidth for the server. 6509 VSS also supports this.
If not, NIC teaming supports active/passive NICs and will move the IP/MAC in case of switch or uplink failure.
Good luck,
R.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide