Networks

General discussion

Gravatar
Locked

NIC Teaming or seperate subnet?

By buschman_007 ·
Okay so I'm trying to do some config changes to reduce network traffic between a few servers that seems to drag my entire LAN down.

the primary focus of this questions about setting up a pair of NICs. For this example, let's say I have Server A, Server B, Primary Gigaswitch and an optional Backbone Gigaswitch.

So a massive data transfer like a backup runs over the network Pulling info from ServerB to ServerA over the Primary Gigaswitch. When this happens all users experience a significant slow down in the LAN. Both Servers are Win 2K3 and have a pair of identical Intel 100Pro GigaNICs. But only one is up and running right now.

My options are these:

- Team the NICs together. Use Network Load Balencing to share the bandwidth between two GigaNICs. Then setup a VLAN in the Primary GigaSwitch and remove unneccessary broadcast traffic. If you feel this is the best method how should the NICs be configured to work together? I can figure out the VLAN, but am not sure on the proper way to configure the NICs for best performance.

- Setup NICs on seperate subnets. Have the secondary NICs go to a Backbone GigaSwitch. Then use some sort of internal routing to ensure only traffic destined for another server on the backbone is routed through the secondary NIC. Or perhaps IP filtering to insure only certain ports go through the backbone, like the ports Veritas uses. Again, if you feel this is the best option how would you configure the NICs in this scenerio?

- Have two NICs both going to the primary Giga Switch and with IPs on the same subnet, but use VLAN to seperate traffic. Again, if this is the option you feel best how would you config the NICs?

None of these options cost me anything extra since I have all the parts inhouse. Just looking for the best option to allow LAN traffic to maintain high performance in the midst of massive data transfer between Servers A & B. And then of course how do I setup the NICs in that option.

Thanks,
Mike

This conversation is currently closed to new comments.

21 total posts (Page 1 of 3)   01 | 02 | 03   Next
+ Follow this Discussion ·
| Thread display: Collapse - | Expand +

All Comments

gravatar
Collapse -

by buschman_007 In reply to NIC Teaming or seperate s ...

Sorry I lost track of my thoughts. Option three should be to use a crossover cable between servers. Similar to the second option, but without the backbone switch.

gravatar
Collapse -

by CG IT In reply to NIC Teaming or seperate s ...

you could schedule backups after hours or use 1 day full and then differential backups which would reduce the need for huge data transfers.

you don't mention the backup schedules or types of backups you use.

gravatar
Collapse -

by CG IT In reply to

with gigabit connections and even 100 full duplex on the switches, you have to have a LOT of data from a LOT of users and servers moving around the network at the same time to bring the LAN throughput down. very large graphics files can do this but then scheduling such moves on off hours reduces the network bandwidth load.

gravatar
Collapse -

by buschman_007 In reply to

Well I didn't want to bring the backup schedule into it as I was trying to keep the scope of the question managable. The problem is we have over seas offices and the network is in use pretty much 24 hours a day. Not to mention the sheer amount of data we are trying to backup is close to 400 GBs. it takes a while to move all that data and get it to tape. meanwhile my LAN and WAN are taking a hit. Just trying to focus on how to move that data without taking a hit to the user's performance. But thank you for the suggestion.

Mike

gravatar
Collapse -

by CG IT In reply to NIC Teaming or seperate s ...

Initially you mentioned large data transfers from Server A to Server B. If server A is a different site from where server B is, ought to consider some topology changes. Since network performance is critical in any large network, might consider delegation of the backup to individual sites or consider a 3rd party online backup storage solution.

gravatar
Collapse -

by buschman_007 In reply to

Sorry I didn't mention sites. Both servers are on the same site. But I'm just trying to focus on NIC config for this question. I'm just not sure what the best practices are for NIC teaming or even if NIC teaming is the best config for my situation. Perhaps a VLAN or totally seperate subnet is the answer. But I'm trying to focus this question on the NICs and not so much the backup typology.

Thanks for the reply though. I do appreciate the help.

Mike

gravatar
Collapse -

by Chris910 In reply to NIC Teaming or seperate s ...

I'm just thinking outloud.
--The crossover cable would clearly Isolate your network traffic and backups from interfearing with each other. --If you where to try and Vlan the traffic the switches would still see the summ of traffic on both vlans plus the overhead of running the vlan. As for how to configure the nics Microsoft calls what you want to do "Multihomed" and doing a knowlegebase search yealded a bunch of potential problems as well as configuration information. Here is one I considered pertinant. http://support.microsoft.com/default.aspx?scid=kb;en-us;262397

gravatar
Collapse -

by buschman_007 In reply to

Good thought! You know I had read about Multihoming in my search for an answer. I actually read that very KB article. Here's a sentence that tripped me up. "When two network adapters are present in a computer (multihomed), a default gateway should only be assigned to one of the network adapter's TCP/IP properties." I read that to mean the primary NIC gets the gateway and the secondary gets none. Which is good cause when every i try and set a gateway on the secondary Windows barks and frankly if I'm using a crossover or dummy switch, i'm not sure what to make the gateway anyways. So I tried setting the secondary NIC on it's own subnet (192.168.22.X as oppsed to 192.168.2.X for my primary) and running the backup there. Veritas even has a way to specific which NIC to use, which I did. however when the backup started, data still flowed over the primary NIC and LAN performance took a hit. I didn't add a route add statement to windows cause I just wasn't sure how the packets would be routed and at the time I also wasn't sure if this would interrupt users currently logged into the system. Any thoughts on that?

Thanks for posting the link, very insiteful.

Mike

gravatar
Collapse -

by Sardukkan In reply to NIC Teaming or seperate s ...

Since your not using the second gig nic in each system. to a seperate Cheap gig switch. Add another NIC to your backup solution so ALL of the backup reated traffic is off the Primary and the backbone switches.

gravatar
Collapse -

by buschman_007 In reply to

Again just to keep the convo going I've marked this unacceptable, but I think you're onto something. Your thought is the same one I had. but some threads have said to set up the secondary NICs on a different subnet and not to use a gateway. I guess if the secondary NICs are using a crossover or cheap Gigaswitch I'm not exactly sure how the gateway and DNS should be configured.

Do I need to add a route table? So Windows knows if you are trying to reach this server go through this NIC, otherwise everything else uses the primary NIC. Never set anything like that up, so any advice or link there would be appreciated.

Thanks for taking time to help me out!

Mike

Back to Networks Forum
21 total posts (Page 1 of 3)   01 | 02 | 03   Next

Start or search

Related Discussions

Related Forums