[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Re: RE : XEN Two NICS Two Bridges


  • To: "Pozzi, Jean-Paul" <jean-paul.pozzi@xxxxxxxxxxxxx>
  • From: Jorge Constán <jorqejcv@xxxxxxxxx>
  • Date: Thu, 12 Feb 2009 15:01:10 +0000
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 12 Feb 2009 07:04:31 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=rfnbNTSKB5hZE/L+ruXNPRCa7a92RYR1EM4RwXlqt18LglxXJeCO7oRGldCbVlod69 OrHGXxYg5/9OYr7vzticFfR0w/UZ76j2nsbXUXiR88IvPDc17/NXwxABUhrW8tI2qLsA OPSP1bZa8H7sUo8qFh0S0//yQCYbsOVFhsWHs=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello Jean.

First of all thank you for your help.

I followed your instructions. I used the network-multinet script instead of the network-bridge (I download network-multinet and xend script from http://thepenguinpriest.com/linux/scripts/network-multinet.html).

When I runs network-multinet script everything was fine but only picked up the first physical card (eth0).

I had to modify the xend script to seized the physical card 2. I modified this in xend script:
-----------------------------------------------------------------

NETWORK_LIST="bridge,0,eth0,,,dhcp-off bridge,1,eth1,,,dhcp-off"

BRIDGE_NETDEV_LIST="eth0 eth1"

LOCAL_BRIDGE_LIST=""
-----------------------------------------------------------------

Now when I launch the network-multinet script believe that is correct (two physical interfaces,two virtual bridge and two virtual interfaces). However when I launch the dums can not detect the eth1 (which is catching want for the network 10.0.0.0). Also if I put the REAL mac.

I do not know what else to do to get it working.

Could you be kind enough to pass an instance of your configuration?

Thanks in advance.


P.D. This is the result from network-multinet status:

sever# /etc/xen/scripts/network-multinet status

============================================================
Configuring Virtual Bridge: xenbr0
using-  Physical Interface: eth0
         Virtual Interface: vif0
============================================================

============================================================
6: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
    link/ether 00:13:72:57:7b:ae brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.10/24 brd 192.168.0.255 scope global eth0
    inet6 fe80::213:72ff:fe65:b6ae/64 scope link
       valid_lft forever preferred_lft forever
21: xenbr0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
    inet6 fe80::200:ff:fe00:0/64 scope link
       valid_lft forever preferred_lft forever

bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif0.0
                                                        peth0
xenbr1          8000.feffffffffff       no              vif0.1
                                                        peth1
                                                        vif9.0
xenbr2          8000.feffffffffff       no              vif0.2
xenbr3          8000.feffffffffff       no              vif0.3
xenbr4          8000.000000000000       no

192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.10
172.22.0.0/16 dev veth2  proto kernel  scope link  src 172.22.0.1
172.23.0.0/16 dev veth3  proto kernel  scope link  src 172.23.0.1
10.0.0.0/8 dev eth1  proto kernel  scope link  src 10.0.0.10
default via 10.0.0.5 dev eth1
default via 192.168.0.3 dev eth0

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
172.22.0.0      0.0.0.0         255.255.0.0     U     0      0        0 veth2
172.23.0.0      0.0.0.0         255.255.0.0     U     0      0        0 veth3
10.0.0.0        0.0.0.0         255.0.0.0       U     0      0        0 eth1
0.0.0.0         10.0.0.5        0.0.0.0         UG    0      0        0 eth1
0.0.0.0         192.168.0.3     0.0.0.0         UG    0      0        0 eth0
============================================================


============================================================
Configuring Virtual Bridge: xenbr1
using-  Physical Interface: eth1
         Virtual Interface: vif1
============================================================

============================================================
8: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
    link/ether 00:13:72:57:7b:af brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.10/8 brd 10.0.0.255 scope global eth1
    inet6 fe80::213:72ff:fe65:b6af/64 scope link
       valid_lft forever preferred_lft forever
22: xenbr1: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
    inet6 fe80::200:ff:fe00:0/64 scope link
       valid_lft forever preferred_lft forever

bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif0.0
                                                        peth0
xenbr1          8000.feffffffffff       no              vif0.1
                                                        peth1
                                                        vif9.0
xenbr2          8000.feffffffffff       no              vif0.2
xenbr3          8000.feffffffffff       no              vif0.3
xenbr4          8000.000000000000       no

192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.10
172.22.0.0/16 dev veth2  proto kernel  scope link  src 172.22.0.1
172.23.0.0/16 dev veth3  proto kernel  scope link  src 172.23.0.1
10.0.0.0/8 dev eth1  proto kernel  scope link  src 10.0.0.10
default via 10.0.0.5 dev eth1
default via 192.168.0.3 dev eth0

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
172.22.0.0      0.0.0.0         255.255.0.0     U     0      0        0 veth2
172.23.0.0      0.0.0.0         255.255.0.0     U     0      0        0 veth3
10.0.0.0        0.0.0.0         255.0.0.0       U     0      0        0 eth1
0.0.0.0         10.0.0.5        0.0.0.0         UG    0      0        0 eth1
0.0.0.0         192.168.0.3     0.0.0.0         UG    0      0        0 eth0
============================================================


============================================================
xenbr4          8000.000000000000       no
============================================================

============================================================
============================================================





2009/2/11 Pozzi, Jean-Paul <jean-paul.pozzi@xxxxxxxxxxxxx>

Hello,

I use Xen servers 2 with XEN 3.0, 1 with XEN 3.2 with many NICS and # 40 VMs.

 In fact each server has 4 Nics on 4 different subnets. I encounter many problems with

the "standard" scripts until I find a "good" script. You can try the "network-multinet"

script which fit perfectly my use.

It can be found on Internet, if you cannot find it I can send it.

 

Regards

JP Pozzi

 

>Hello everyone.

>I just installed Xen 3.0.3 in a debian etch box.

>Linux server1.example.com 2.6.18-6-xen-686 #1

>This server1 has two real nic (eth0 with real MAC 00:13:72:57:7B:AE and eth1 with real MAC00:13:72:57:7B:AF).

> I made a network-bridge custom like this:


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.