Re: [Xen-users] Bonded interfaces with trunk and iscsi SAN

[Donny Brooks <dbrooks@xxxxxxxxxxxxxxxx>]

On 2/16/2011 4:05 PM, Fajar A. Nugraha wrote:
> On Thu, Feb 17, 2011 at 4:45 AM, Donny Brooks<dbrooks@xxxxxxxxxxxxxxxx>  wrote:
> > On 2/16/2011 3:41 PM, Fajar A. Nugraha wrote:
> > > On Thu, Feb 17, 2011 at 4:35 AM, Donny Brooks<dbrooks@xxxxxxxxxxxxxxxx>
> > > > Ok, I added the IP information to the ifcfg-br20 file and ifdown/ifup
> > > > that
> > > > interface. I am able to ping the 192.168.130.X range but nothing in the
> > > > 192.168.131.X, 192.168.132.X, or 192.168.133.X ranges. Here is the
> > > > contents
> > > > of that file:
> > > >
> > > > DEVICE=br20
> > > > TYPE=Bridge
> > > > BOOTPROTO=static
> > > > IPADDR=192.168.130.51
> > > > NETMASK=255.255.0.0
> > > > NETWORK=192.168.0.0
> > > > ONBOOT=yes
> > > Does all host in 192.168.X.X use the same /16 (255.255.0.0) netmask?
> > > A common error is when some hosts use /16, while others use /24.
> > The only thing on that vlan is the SAN. Now that I think about it the
> > windows machine is set to a /24 on each interface. So it may be that the SAN
> > is set for /24 instead of /16. Now just to figure out how to have 4
> > "interfaces" each with a /24 subnet...... hmmmm. :)
> That's easy. ifcfg-br20:1, ifcfg-br20:2, etc. :D
I think it is getting late in the day.... I added the ifcfg-br20:1/2/3/4 
files with the contents as follows:
[root@xen-test network-scripts]# cat ifcfg-br20\:*
DEVICE=br20:1
TYPE=Bridge
BOOTPROTO=static
IPADDR=192.168.130.53
NETMASK=255.255.255.0
NETWORK=192.168.130.0
ONBOOT=yes

DEVICE=br20:2
TYPE=Bridge
BOOTPROTO=static
IPADDR=192.168.131.53
NETMASK=255.255.255.0
NETWORK=192.168.131.0
ONBOOT=yes

DEVICE=br20:3
TYPE=Bridge
BOOTPROTO=static
IPADDR=192.168.132.53
NETMASK=255.255.255.0
NETWORK=192.168.132.0
ONBOOT=yes

DEVICE=br20:4
TYPE=Bridge
BOOTPROTO=static
IPADDR=192.168.133.53
NETMASK=255.255.255.0
NETWORK=192.168.133.0
ONBOOT=yes

and when I try to ifup the first interface I get this......

[root@xen-test network-scripts]# ifup br20:1
Bridge support not available in this kernel


How is bridge support not available in the kernel when it is bridges I 
am working with already? I think I will take a step away from this for a 
bit and come back to it tomorrow.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users