I have a bladecenter utilizing 4 eth cards.
I currently have bonding setup for all 4.

This is the setup I have:

Bond0 will handle traffic for my 51 network.
ifcfg-bond0
DEVICE=bond0
IPADDR=43.145.x1.xx
GATEWAY=43.145.xx.xxx
NETMASK=255.255.255.0
NETWORK=43.145.xxx.0
USERCTL=no
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet

Bond1 will handle traffic for my 14 network

ifcfg-bond1
DEVICE=bond0
IPADDR=43.145.x4.xx
GATEWAY=43.145.x.xxx
NETMASK=255.255.255.0
NETWORK=43.145.xxx.0
USERCTL=no
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet

I have eth0 & 2 configured to use bond0 and I have eth1 & 3 configured to use Bond1....

Here is the problem... The /etc/sysconfig/network file contains the GATEWAY Address of the 51 network which is what I want...

But if I dont comment out (#) the gateway line in the Bond1 file, it sets the default gateway of the machine to the 14 network.

If I run a route -n the default gateway comes back as the 14 address, if I comment out the GATEWAY line in Bond1 and restart networking, run a route -n, the default comes back as 51 network which is what i want, but then traffic for 14 network is unroutable...

Man I hope this makes sense....

What Im looking to achieve is a default gateway of 51 and still have the GATEWAY listed in Bond1 file be available for 14 traffic.

Any ideas would be much appreciated...

Thanks,
mkono

In the description you gave above of your ifcfg-bondx files, are these cut-n-paste or did you type them out?
Both have the line: DEVICE=BOND0
Is this a typo in the post, or a typo in your config. files?
Shouldn't one be DEVICE=BOND0 and one be DEVICE=BOND1 having 2 NIC's attached to bond0 and 2 NIC's attached to bond1 ?

The second test I would try, is remove all the "network" statements from your ifcfg and ../sysconfig/network files. Take them all out. I don't generally use them, and I can't recall having my routes messed up.

If the above doesn't work, another way would be to statically manipulate the routes (e.g. add to /etc/rc.local) to force 1 network out 1 ifdev and 1 out the other. e.g.:
route add -net 43.145.xxx.0 netmask 255.255.255.0 dev ifcfg-bond1
route add -net 43.145.x1.xx netmask 255.255.255.0 dev ifcfg-bond0
route add default gw 43.145.xx.xxx
(naturally you would adjust the above lines by filling in your correct IP's where you have "x"'s)
You could also use a "route del" command to remove dynamically added routes so that the above take preference. Take a look at "man route" as there are some useful examples.

zQUEz,
Thanks again for your help on the issues im experiencing.

The "bond" file stanzas reflected the correct device#. That was just a typo in my post.

I eliminated my network routes as you suggested. I don't see why they would be needed if I am directing traffic with a proper subnet and gateway.

I attempted to run the route add and received the following errors.

route add -net 43.145.xxx.0 netmask 255.255.255.0 dev ifcfg-bond1
SIOCADDRT: No such device

I did successfully run a route add gw .... and it looks as if that may have worked.

I will keep you posted. Again, I appreciate your responses, they are the exactly what Im looking for.

Thanks,
Mkono