Hi,

Sorry I was out for  few days for  different project.  

Thanks to both of you for the reply  . 

If I understand you correctly, you want VLAN trunking with bond0.   
Possibly more than one different VLAN (three?).

Yes,  


In that case, you create a bond0.NN where NN is the VLAN tag.   You 
can have more than one of these.  The VLAN tag is taken care of by the 
bond device rather than the bond's slaves.

I configured , the way  you have mentioned  , But did not work.   I referred  
the following
url also

http://planet.ergo-project.org/blog/jmeeuwen/2010/06/01/trunking-bonded-etherchannels-virtualization-and-storage-enterprise-linux

 bonding  , 8021q modules  are already  loaded in the server. But  one thing I 
noticed 
the bonding module is associated as follows:

 lsmod |grep -i bonding
bonding               126649  0 
ipv6                  432289  56 bonding,cnic

We are using  ipv4. But here  it is associated to ipv6.  Is it the issue?

If you can send/guide with the configuration  on three subnets under trunk , 
that will be really appreciated.

Thanks  again



 




--- On Tue, 6/22/10, John Haxby <[email protected]> wrote:

From: John Haxby <[email protected]>
Subject: Re: [rhelv5-list] Configuration bonding with trunk port
To: "Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list" 
<[email protected]>
Date: Tuesday, June 22, 2010, 5:18 AM



On 21 June 2010 21:42, Srija <[email protected]> wrote:

 Hi



This is regarding the   configuration of bonding  between  the two ports,



I have already configured with  eth0 and eth1 bonded to bond0 and it worked 
fine.



The configuration is simple and associated to one ip (configured in bond0 
configuration file ) which is communicating to eth0 and eth1. eth0 and eth1 is 
set as slave of bond0.



Now I want to configure the same eth0 and eth1 to bond0 when, eth0 is set with 
trunking and associated to three subnets.


If I understand you correctly, you want VLAN trunking with bond0.   Possibly 
more than one different VLAN (three?).


In that case, you create a bond0.NN where NN is the VLAN tag.   You can have 
more than one of these.  The VLAN tag is taken care of by the bond device 
rather than the bond's slaves.

There's more information in 
/usr/share/doc/kernel-doc-*/Documentation/networking/bonding.txt (you'll need 
to install kernel-doc for that) and also somewhere in 
/usr/share/doc/initscripts-*/* -- that documentation is a bit spotty though and 
I tend to resort to reading the actual shell scripts in 
/etc/sysconfig/network-scripts.


jch


-----Inline Attachment Follows-----

_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list



      
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to