[Xen-API] Interpretation of Xen / Xapi network setup (Linux bridge)

[niklas.hofmann@xxxxxxxxxxxxxxxx]

Hi!

Is the following interpretation of a simple Linux-bridge-based Xen/Xapi
network setup valid? What is your opinion?

http://www.chimos.de/stuff/2012-06-07_Xen-XCP-Networking_Bridge_V3.pdf

niklas@queenmary:~$ brctl show xenbr0
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.902b3433e9bc       no              eth0
                                                        vif1.0
                                                        vif2.0
                                                        vif3.0

niklas@queenmary:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 90:2b:34:33:e9:bc 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:27501 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12712 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:25937301 (25.9 MB)  TX bytes:1265922 (1.2 MB)
          Interrupt:5 Memory:fb700000-fb720000

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:180 errors:0 dropped:0 overruns:0 frame:0
          TX packets:180 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:41811 (41.8 KB)  TX bytes:41811 (41.8 KB)

vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff 
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP PROMISC  MTU:1500  Metric:1
          RX packets:114 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5748 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:14345 (14.3 KB)  TX bytes:1241193 (1.2 MB)

vif2.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff 
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP PROMISC  MTU:1500  Metric:1
          RX packets:50 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5650 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:6000 (6.0 KB)  TX bytes:1227446 (1.2 MB)

vif3.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff 
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP PROMISC  MTU:1500  Metric:1
          RX packets:76 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5671 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:9416 (9.4 KB)  TX bytes:1226533 (1.2 MB)

xenbr0    Link encap:Ethernet  HWaddr 90:2b:34:33:e9:bc 
          inet addr:192.168.2.134  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::922b:34ff:fe33:e9bc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:26454 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12742 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:25154731 (25.1 MB)  TX bytes:1218071 (1.2 MB)

niklas@queenmary:~$ sudo xe vm-list
uuid ( RO)           : 8737fbb3-8e76-937c-d252-f16cf4bf94c2
     name-label ( RW): test02
    power-state ( RO): running


uuid ( RO)           : 1f27536c-5524-2d03-dc07-19b2c4ef44ca
     name-label ( RW): Control domain on host: queenmary
    power-state ( RO): running


uuid ( RO)           : 802a80f9-6b8f-0782-f8ca-7edf1a7465f0
     name-label ( RW): test03
    power-state ( RO): running


uuid ( RO)           : 48df7380-bfe8-e9a9-c0e7-e7e676ed4b10
     name-label ( RW): test01
    power-state ( RO): running

niklas@queenmary:~$ sudo xe vif-list
uuid ( RO)            : 61999a83-2dee-df1b-d0b8-449521f2d9c6
         vm-uuid ( RO): 8737fbb3-8e76-937c-d252-f16cf4bf94c2
          device ( RO): 0
    network-uuid ( RO): fda72334-7f6c-029b-79b8-d1f9749ce2a1


uuid ( RO)            : fb151bc7-e2be-d315-8ae8-e992e6f9fc16
         vm-uuid ( RO): 48df7380-bfe8-e9a9-c0e7-e7e676ed4b10
          device ( RO): 0
    network-uuid ( RO): fda72334-7f6c-029b-79b8-d1f9749ce2a1


uuid ( RO)            : 7b347364-2e7e-caa8-2bc7-a02ad2cb0f1a
         vm-uuid ( RO): 802a80f9-6b8f-0782-f8ca-7edf1a7465f0
          device ( RO): 0
    network-uuid ( RO): fda72334-7f6c-029b-79b8-d1f9749ce2a1


I drafted two alternative interpretations - probably both wrong:
http://www.chimos.de/stuff/2012-06-07_Xen-XCP-Networking_Bridge_V1.pdf
http://www.chimos.de/stuff/2012-06-07_Xen-XCP-Networking_Bridge_V2.pdf

Thanks!

Niklas

-- 
End Of Message


_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api