Configure VLAN over a bond interface

[MikeL_4]

I am running Red Hat Version 5.3 and current have eth0 up and running as follows with two VLAN's:

# ifconfig
eth0 Link encap:Ethernet HWaddr 00:22:19:29:CB:2B
inet6 addr: fe80::222:19ff:fe29:cb2b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10396042 errors:0 dropped:0 overruns:0 frame:0
TX packets:2220350 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3444723383 (3.2 GiB) TX bytes:2573950821 (2.3 GiB)
Interrupt:169 Memory:da000000-da012100

eth0.874 Link encap:Ethernet HWaddr 00:22:19:29:CB:2B
inet addr:155.90.114.38 Bcast:155.90.114.63 Mask:255.255.255.224
inet6 addr: fe80::222:19ff:fe29:cb2b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2679178 errors:0 dropped:0 overruns:0 frame:0
TX packets:2211130 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2615788334 (2.4 GiB) TX bytes:2554623592 (2.3 GiB)

eth0.875 Link encap:Ethernet HWaddr 00:22:19:29:CB:2B
inet addr:192.168.42.38 Bcast:192.168.42.63 Mask:255.255.255.224
inet6 addr: fe80::222:19ff:fe29:cb2b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14094 errors:0 dropped:0 overruns:0 frame:0
TX packets:9163 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6888241 (6.5 MiB) TX bytes:1132646 (1.0 MiB)

I've been asked to set this up as a bond interface but have a couple of questions:

1) what does this buy for me on the server ?

2) How do I configure it ??

[Ivan Ferreira · Accepted solution]

>>> 1) what does this buy for me on the server ?

You need another network adapter.


>>> 2) How do I configure it ??

In this forum, just search for "bonding" and you will have a lot of results.

Also, check some restrictions when using VLAN tags over bonding in this link:

http://www.mjmwired.net/kernel/Documentation/networking/bonding.txt

[MikeL_4]

I have another interface that is being used, eth3, can that be used ???

eth3 Link encap:Ethernet HWaddr 00:15:17:A8:DC:53
inet addr:192.168.35.238 Bcast:192.168.35.255 Mask:255.255.255.0
inet6 addr: fe80::215:17ff:fea8:dc53/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7716538 errors:0 dropped:0 overruns:0 frame:0
TX packets:164 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:733282512 (699.3 MiB) TX bytes:24537 (23.9 KiB)
Memory:d5ea0000-d5ec0000

[Ivan Ferreira]

It could be used, but you must unconfigure the IP adress for the interface and assign them to the bond interface.

[Steven E. Protter]

Shalom,

Theoretically you can bind any ethernet adapter with any other.

In practice, if the hardware is not the same, the bonding can be touchy.

Original questions:

1) active-passive gives you better reliability. Active-active can give you that and double your transfer rates.

http://www.cyberciti.biz/tips/linux-bond-or-team-multiple-network-interfaces-nic-into-single-interface.html

http://kbase.redhat.com/faq/docs/DOC-7944

SEP