[K12OSN] K12OSN Digest, Vol 75, Issue 9

[Sean Harbour]

I don't believe the method you are attempting will work the way you think it will. When bonding, you generally need to pipe all of the bonded NICs into the same switch, which will generally have a 1Gb capable up link port. If you really wanted to try bonding, you could try putting them all into the same switch, then tagging the other two switches off the first switch just for additional clients. If it worked, you would effectively have 300Mb available on the first switch, and 100Mb on the second and third switch. However, this is an oddball setup.

 The recommended solution in this case is to not bond. Plug each switch into a dedicated NIC on the server like you were going to do originally, and assign them IP addresses sequentially next to the existing client NIC (Assuming you already have a 2 NIC setup, and want to make it a 4 NIC setup). Then, configure your DHCP service on the server to service the new NICs. That should do it. Each cluster of 16 ports will have a dedicated 100Mb path back to the server. Eazy peazy. You shouldn't have to set up a separate DHCP subnet pool for each switch either. There are several write ups on how to do this already, but I think all you should have to do is modify the section of your DHCP server config like this:

# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
#    Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACES="eth1 eth2 eth3"

Thanks,

Sean Harbour
Senior Network Engineer
Northwest Regional Education Service District
Hillsboro, OR 97124
sharbour at nwresd.k12.or.us
503-614-1448
________________________________________
From: k12osn-bounces at redhat.com [k12osn-bounces at redhat.com] On Behalf Of k12osn-request at redhat.com [k12osn-request at redhat.com]
Sent: Wednesday, May 19, 2010 9:00 AM
To: k12osn at redhat.com
Subject: K12OSN Digest, Vol 75, Issue 9

Send K12OSN mailing list submissions to
        k12osn at redhat.com

To subscribe or unsubscribe via the World Wide Web, visit
        https://www.redhat.com/mailman/listinfo/k12osn
or, via email, send a message with subject or body 'help' to
        k12osn-request at redhat.com

You can reach the person managing the list at
        k12osn-owner at redhat.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of K12OSN digest..."


Today's Topics:

   1. Bonding 3 networkcards and 3 switches. (jan nilsen)


----------------------------------------------------------------------

Message: 1
Date: Wed, 19 May 2010 08:42:48 +0200
From: jan nilsen <jannilsen.nilsen at googlemail.com>
To: k12osn at redhat.com
Subject: [K12OSN] Bonding 3 networkcards and 3 switches.
Message-ID:
        <AANLkTimwlpOKp_H7zNfKoVKWMayzsVIRL-psaCOiTiHZ at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

So, I have a server with a 1gbit NIC, and 3 16-ports switches (all
100mbit ports), that are linked togheter the old switch-in-switch
style, and I have about 45 clients (mix of thinclients, workstations
and laptops).

When most of the machines are in use, I notice that having only
100mbit out of the server is not enough.

So I can either buy myself a 48 port switch with 1gbit uplink with
money we don't have (we realy don't have any money),
or I thought I could try this "bonding" thing.

I can put 3 network cards in the server, and connect each of those
networkcards with it's own 16-port switch, that way I would have
300mbit out of the server.

What kind of bonding mode should I choose?

Or is there some other way?

jan



------------------------------

_______________________________________________
K12OSN mailing list
K12OSN at redhat.com
https://www.redhat.com/mailman/listinfo/k12osn

End of K12OSN Digest, Vol 75, Issue 9
*************************************