Onderwerp: xen3 guest os soms geen netwerk response

Ik heb een xen server draaien met een bond op mijn 2 netwerk interfaces.
Ik heb xenbr0 een IP en bond0 als bridge toegevoegd.
Nu heb ik netwerk verkeer van het local lan/www met de guest maar als ik bv een ping start stopt deze heel even en gaat daarna weer verder.
Het is alsof de guest even op pauze gaat en daarna weer verder, echter kan ik in de "pauze" wel gewoon werken met de guest maar geen enkele netwerk functie werkt dan.

Iemand een idee wat dit kan zijn?

Eventueel in de xen config je mac adres vast zetten, helpt dit?
Verder in de VPS alle configs zoals gateway, nameservers, subnet, netwerkadres etc goed ingesteld?

Hierbij mijn config:

Code:

#
#  Configuration file for the Xen instance status, created on
# Tue Jun 17 19:21:45 2008.
#


#
#  Kernel + memory size
#
kernel  = '/boot/vmlinuz-2.6.18-6-xen-vserver-amd64'
ramdisk = '/boot/initrd.img-2.6.18-6-xen-vserver-amd64'

memory  = '1024'


#
#  Disk device(s).
#
root    = '/dev/sda1 ro'

disk    = [ 'file:/data/xen/domains/status/disk.img,sda1,w', 'file:/data/xen/domains/status/swap.img,sda2,w' ]

#
#  Hostname
#
name    = 'status'


#
#  Networking
#
vif  = [ 'ip=192.168.2.30,bridge=xenbr0' ]

#
#  Behaviour
#
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'

Als ik de MAC vastzet geeft dit hetzelfde probleem.
Op de Dom0 heb ik de volgende network config:

Code:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo xenbr0
iface lo inet loopback

iface bond0 inet manual
pre-up modprobe bond0
pre-up ifconfig bond0 up
slaves eth0 eth1

iface xenbr0 inet static
        pre-up ifup bond0
        address 192.168.2.22
        netmask 255.255.255.0
        network 192.168.2.0
        gateway 192.168.2.1
        broadcast 192.168.2.255
        dns-nameservers 192.168.3.2 192.168.3.3
        dns-search leftclick.local
        bridge_ports bond0

De file xend-config.sxp:

Code:

##
# To bridge network traffic, like this:
#
# dom0: fake eth0 -> vif0.0 -+
#                            |
#                          bridge -> real eth0 -> the network
#                            |
# domU: fake eth0 -> vifN.0 -+
#
# use
#
(network-script network-bridge)
#
# Your default ethernet device is used as the outgoing interface, by default.
# To use a different one (e.g. eth1) use
#
# (network-script 'network-bridge netdev=eth1')
#
# The bridge is named xenbr0, by default.  To rename the bridge, use
#
# (network-script 'network-bridge bridge=<name>')
#
# It is possible to use the network-bridge script in more complicated
# scenarios, such as having two outgoing interfaces, with two bridges, and
# two fake interfaces per guest domain.  To do things like this, write
# yourself a wrapper script, and call network-bridge from it, as appropriate.
#
(network-script network-dummy)

# The script used to control virtual interfaces.  This can be overridden on a
# per-vif basis when creating a domain or a configuring a new vif.  The
# vif-bridge script is designed for use with the network-bridge script, or
# similar configurations.
#
# If you have overridden the bridge name using
# (network-script 'network-bridge bridge=<name>') then you may wish to do the
# same here.  The bridge name can also be set when creating a domain or
# configuring a new vif, but a value specified here would act as a default.
#
# If you are using only one bridge, the vif-bridge script will discover that,
# so there is no need to specify it explicitly.
#
(vif-script vif-bridge)

#(vif-script     vif-route)


## Use the following if network traffic is routed with NAT, as an alternative
# to the settings for bridged networking given above.
#(network-script network-nat)
#(vif-script     vif-nat)


# Dom0 will balloon out when needed to free memory for domU.
# dom0-min-mem is the lowest memory level (in MB) dom0 will get down to.
# If dom0-min-mem=0, dom0 will never balloon out.
(dom0-min-mem 196)

# In SMP system, dom0 will use dom0-cpus # of CPUS
# If dom0-cpus = 0, dom0 will take all cpus available
(dom0-cpus 0)

# Whether to enable core-dumps when domains crash.
#(enable-dump no)

# The tool used for initiating virtual TPM migration
#(external-migration-tool '')

# The interface for VNC servers to listen on. Defaults
# to 127.0.0.1  To restore old 'listen everywhere' behaviour
# set this to 0.0.0.0
(vnc-listen '0.0.0.0')

Is dit correct?

Alles heb ik wel goed ingesteld, kwa ip gegevens en gateway etc.

Hierbij de ifconfig van de dom0:

Code:

bond0     Link encap:Ethernet  HWaddr 00:30:48:C2:E3:20
          inet6 addr: fe80::230:48ff:fec2:e320/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:6567 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14629 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:574806 (561.3 KiB)  TX bytes:1246184 (1.1 MiB)

eth0      Link encap:Ethernet  HWaddr 00:30:48:C2:E3:20
          inet6 addr: fe80::230:48ff:fec2:e320/64 Scope:Link
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:6224 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9330 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:540833 (528.1 KiB)  TX bytes:815306 (796.1 KiB)
          Base address:0x2000 Memory:d8020000-d8040000

eth1      Link encap:Ethernet  HWaddr 00:30:48:C2:E3:21
          inet6 addr: fe80::230:48ff:fec2:e321/64 Scope:Link
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:343 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5299 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:33973 (33.1 KiB)  TX bytes:430878 (420.7 KiB)
          Base address:0x2020 Memory:d8060000-d8080000

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:26 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2072 (2.0 KiB)  TX bytes:2072 (2.0 KiB)

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  MTU:1500  Metric:1
          RX packets:2581 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2901 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:180583 (176.3 KiB)  TX bytes:259964 (253.8 KiB)

xenbr0    Link encap:Ethernet  HWaddr 00:30:48:C2:E3:20
          inet addr:192.168.2.22  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::230:48ff:fec2:e320/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5169 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4502 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:357927 (349.5 KiB)  TX bytes:542724 (530.0 KiB)

Er draait op dit moment 1 domU

Heb het probleem gevonden, als je de bond0 op mode5 of 6 zet dan gaat het fout.
Nu aangepast naar mode 1 en draait vlekkeloos.
Welke optie gebruiken jullie veelal?

active/backup hier, we hebben gemerkt dat bij teaming waarbij beide adapters actief zijn het grote aantal mac wisselingen (1 IP met 2 mac adressen) nog wel eens voor problemen kan zorgen.