2nd Network for Faster Server Comm / Backup

I want to add a 2nd NIC to all my servers and connect them to a 2nd
(different) network so that they can communicate with each other (and for
Backups) and not slow down the main network.

1) How do I rout the traffic for just the server to the 2nd network without
affecting the communication of the servers to the rest of the network clients?
2) I know I can use Port filtering on the 2nd NIC but what if you do not
know what port the software uses (like NTBACKUP)?

Thanks for all the Help.
Ryan

"Ryan" <(E-Mail Removed)> wrote in message
news:9F3D3195-26A0-4855-A54B-(E-Mail Removed)...
> 1) How do I rout the traffic for just the server to the 2nd network
> without
> affecting the communication of the servers to the rest of the network
> clients?
> 2) I know I can use Port filtering on the 2nd NIC but what if you do not
> know what port the software uses (like NTBACKUP)?

There is no filtering, and that wouldn't work even if there was.
The path is determined by where the destination is (destination IP#). Your
"target" has to be on the "other" network. The machine will be smart enough
to know which nic to use to get there because the target and the source nic
will be in the same IP segment.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------

To accomplish what you desire you need a managed switch with VLAN support.
You would create two vlans. One public and one private. You put everyone
on the public vlan as well as the servers. The second nic in each server is
connected via the private vlan. This way server to server communcation never
touches the public communication. To learn more google vlans

Phillip thanks for you help but maybe I did not make myself clear.

The Servers are in both Networks. 1 Network has all the clients and Servers
and the 2nd network would just have the Servers in it. I need to know how to
route server to server traffic over the 2nd network so it would not affect
the network woth the clients.

Thanks,
Ryan

"Phillip Windell" wrote:

>
> "Ryan" <(E-Mail Removed)> wrote in message
> news:9F3D3195-26A0-4855-A54B-(E-Mail Removed)...
> > 1) How do I rout the traffic for just the server to the 2nd network
> > without
> > affecting the communication of the servers to the rest of the network
> > clients?
> > 2) I know I can use Port filtering on the 2nd NIC but what if you do not
> > know what port the software uses (like NTBACKUP)?
>
> There is no filtering, and that wouldn't work even if there was.
> The path is determined by where the destination is (destination IP#). Your
> "target" has to be on the "other" network. The machine will be smart enough
> to know which nic to use to get there because the target and the source nic
> will be in the same IP segment.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
>
>
>

Thanks Joshua I will look into VLANS.

Ryan

"Joshua Bolton" wrote:

> To accomplish what you desire you need a managed switch with VLAN support.
> You would create two vlans. One public and one private. You put everyone
> on the public vlan as well as the servers. The second nic in each server is
> connected via the private vlan. This way server to server communcation never
> touches the public communication. To learn more google vlans

It's entirely dependant on IP address. If you have two different networks then
Windows will know which NIC to use based on the destination IP address. If
you're using WINS or DNS then you need separate entries/names for each NIC. For
example, server1-e1 & server1-e2 (NIC1 & NIC2 names.)

"Ryan" <(E-Mail Removed)> wrote in message
news:069A886B-E523-4832-9DBB-(E-Mail Removed)...
> Phillip thanks for you help but maybe I did not make myself clear.
>
> The Servers are in both Networks. 1 Network has all the clients and Servers
> and the 2nd network would just have the Servers in it. I need to know how to
> route server to server traffic over the 2nd network so it would not affect
> the network woth the clients.
>
> Thanks,
> Ryan
>
> "Phillip Windell" wrote:
>
>>
>> "Ryan" <(E-Mail Removed)> wrote in message
>> news:9F3D3195-26A0-4855-A54B-(E-Mail Removed)...
>> > 1) How do I rout the traffic for just the server to the 2nd network
>> > without
>> > affecting the communication of the servers to the rest of the network
>> > clients?
>> > 2) I know I can use Port filtering on the 2nd NIC but what if you do not
>> > know what port the software uses (like NTBACKUP)?
>>
>> There is no filtering, and that wouldn't work even if there was.
>> The path is determined by where the destination is (destination IP#). Your
>> "target" has to be on the "other" network. The machine will be smart enough
>> to know which nic to use to get there because the target and the source nic
>> will be in the same IP segment.
>>
>> --
>> Phillip Windell [MCP, MVP, CCNA]
>> www.wandtv.com
>> -----------------------------------------------------
>>
>>
>>

"Ryan" <(E-Mail Removed)> wrote in message
news:069A886B-E523-4832-9DBB-(E-Mail Removed)...
> Phillip thanks for you help but maybe I did not make myself clear.

Yes, you did.

> The Servers are in both Networks. 1 Network has all the clients and
> Servers
> and the 2nd network would just have the Servers in it. I need to know how
> to
> route server to server traffic over the 2nd network so it would not affect
> the network woth the clients.

Same answer as last time.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

VLans don't fit your situation.

You have duel-homed servers. That makes it a physical LAN not a VLAN. You
want the server to communication over the "backup" Nics. VLANs don't help
with wire saturation because the VLANs share the same wire.

Just use the right IP# as the "target" of the communication,...all
done,...no magic, ..no voodoo.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"Ryan" <(E-Mail Removed)> wrote in message
news:EEABC5DA-F964-4A51-A060-(E-Mail Removed)...
> Thanks Joshua I will look into VLANS.
>
> Ryan
>
> "Joshua Bolton" wrote:
>
>> To accomplish what you desire you need a managed switch with VLAN
>> support.
>> You would create two vlans. One public and one private. You put
>> everyone
>> on the public vlan as well as the servers. The second nic in each server
>> is
>> connected via the private vlan. This way server to server communcation
>> never
>> touches the public communication. To learn more google vlans

Ryan,

This is not easy to set up, but Mike has given you the info you need.
You are not "routing" any traffic in the normal sense of the word. You want
one set of NICs to be used for one purpose and the other set to be used for
another. The only way to get this to work is to have two names for each
server and have each name bound to a particular IP address. If the machines
are known by the "right" names they will use the "right" NICs.

When an application needs to send info to another machine, it does so by
using the other machine's name. This name is then resolved to an IP address.
This is the target address. If the target address is in the same IP subnet
an one of the host machine's NICs, then the info will be sent directly over
the network. The host machine will do an ARP request to get the MAC address
of the NIC of the target and then send the data.

In practical terms this means that the backup program must know the
servers by their "backup" name, while the client machines must know them by
their "server" name. This is really the key to getting this setup to work.

"Bill Grant" <not.available@online> wrote in message
news:(E-Mail Removed)...
> Ryan,
>
> This is not easy to set up, but Mike has given you the info you need. You
> are not "routing" any traffic in the normal sense of the word. You want one
> set of NICs to be used for one purpose and the other set to be used for
> another. The only way to get this to work is to have two names for each server
> and have each name bound to a particular IP address. If the machines are known
> by the "right" names they will use the "right" NICs.
>
> When an application needs to send info to another machine, it does so by
> using the other machine's name. This name is then resolved to an IP address.
> This is the target address. If the target address is in the same IP subnet an
> one of the host machine's NICs, then the info will be sent directly over the
> network. The host machine will do an ARP request to get the MAC address of the
> NIC of the target and then send the data.
>
> In practical terms this means that the backup program must know the servers
> by their "backup" name, while the client machines must know them by their
> "server" name. This is really the key to getting this setup to work.

One other comment: If the destination IP is NOT on one of the two local networks
then it will use the NIC with a default gateway setting (there should only be
one.)