similar to: [Fwd: Xen, NIC bonding, ARP problem]

CentOS 5.5 Xen "standard" Xen Installation. I have two nics. I just put the second one to DHCP and modified the ifcfg-et01 and so far I am holding, but I am not confident. Prior they were sequential IP Addrs on same subnet. arpwatch has indicated flip flips. I can find no rhyme or reason to predict them. I know I missed I must have missed a step somewhere. I want to keep the

I have nic bonding (mode=802.3ad) setup on 2 servers, both running Centos 5.5 In the "Active Aggregator Info", on one reports 4 ports - which is correct - but the other only reports 3 ports. It's always eth0 that shows a different aggregator ID. Changing the cables around so it hits a different port on the switch makes no difference. The switch is correctly configured for the port

I have nic bonding (mode=802.3ad) setup on 2 servers, both running Centos 5.5 In the "Active Aggregator Info", on one reports 4 ports - which is correct - but the other only reports 3 ports. It''s always eth0 that shows a different aggregator ID. Changing the cables around so it hits a different port on the switch makes no difference. The switch is correctly configured for the

Hi all, my dom0 is centos5.2 and domU paravirtualized is centos5.1 I can play sound on dom0 but not in domU (name: gasphar), moreover I use wifi as my inet connection and on installing domU cento5.1, I used virt-manager. I know that libvirtd made virbr0 and when changing to xenbr0, I cannot connect to internet but ssh to dom0 is fine! so how do I enable sound device on domU and changing to

Hi Gerhard; I'm pretty new to this list too but I think this may be a bonding issue. What bonding mode are you using in /etc/modprobe.conf? You should have a couple of lines in there: alias bond0 bonding options bond0 miimon=x mode=x What kind of switch are you connecting to and have you done any specific configuration to the switch to support your bonding mode? (depends on the mode).

I am experiencing strange network behavior from several DomU''s. I can ssh from DomU to any host on the local lan/vlan, I can ping those hosts. However when I go to resolve a hostname DNS fails. I have verified that three other DomU''s are exhibiting the same behavior. I have also verified that Dom0 is functioning properly and can resolve hostnames and access hosts outside of the

Hello I have two linux machines connected via 2 dsl lines (bonded) 192.168.0.1-eth0-dsl---2Mbit---dsl-eth0-192.168.0.2 ^-eth1-dsl---2Mbit---dsl-eth1-^ so the final figure is something like this: 192.168.0.1-bond0---4Mbit---bond0-192.168.0.2 I can only use arp monitoring for fail checking - if one dsl line fails - automatically use only the other one. I set up everything correctly (i

I think the diagram here: http://wiki.xensource.com/xenwiki/XenNetworking#line-474 should be more like this: http://pastebin.com/cjxbXrJW I''ve asked Stephen for edit rights on the wiki but wanted to ask for confirmation before editing it. Notes: The connections at the top are switch ports bond1 has eth2 and eth3 eth0 maps to bond0.100 and eth1 maps to bond1.200

Hello, I have problems with installation of my second DomU. I cannot ping it from the outside world and I cannot access outside world from this domain. I see it from Dom0 and my first DomU, same as my second DomU can ping Dom0 and my first DomU. I use xen 3.0.3 on ubuntu 6 LTS. DomU is running on debian. I also network-bridge script in the xend config.

Hi, I''ve set up identical (what I think) machines using SLES 10 x86_64, but a new one of those is saying frequently in /var/log/messages: kernel: bond0: received packet with own address as source address A short summary of ifconfig looks like this: bond0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 eth0

I''m attempting to put together a Xen box, which has multiple VLANs running into it, on one bridged interface. I mostly copied the way it was done here: http://renial.net/weblog/2007/02/27/xen-vlan/ I basically have: bond0 is the bond device (composed of eth0 and eth1), vlan757 is the vlan device for vlan 757 on bond0, and "xen757" is a bridge created by the above scripts,

I have a server running Centos 5.2 as a Xen host. A problem that's shown up recently is that at boot, the dom0 interface eth0 doesn't come up properly, with the result that the host is only accessible via remote console. If I execute 'service network restart', eth0 comes up normally, with an IP address and the correct routing. Three guests have been created via virt-manager

Hello everyone, I''m trying to get multiple guests to connect their networks to the Xen network bridge xenbr0 that''s tied to two bonded interfaces. My current dom0 network looks like this: (eth0 + eth1) => bond0 -> pbond0 -> xenbr0 eth0 and eth1 are bonding under Red Hat EL5, and Xen is configured to use bond0 as the main network device. Xend-config is set to use the

Hello, The basic details of my host and XEN configuration and network configuration all appear below. Whilst I have come this far, a lot of it has been intuitive so I now have plenty of questions. Firstly I would like some help and clarification with regard to ebtables and especially how it works in a Virtualized environment on Novell SUSE 10 SP1 (1) ebtables Installation ebtables was not

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

Hi guys, Greetings for the new year The problem faced by me is simple, I cannot get channel bonding to work perfectly with Xen. I am trying to boost the bandwidth of guest domains by using link aggregation (a.k.a channel bonding). I have tried round robin (mode 0) and high availability (mode 1). I know that mode 1 will not give me bandwidth boost. But strangely once i try mode 1 for the guest, I

Hi guys, Greetings for the new year The problem faced by me is simple, I cannot get channel bonding to work perfectly with Xen. I am trying to boost the bandwidth of guest domains by using link aggregation (a.k.a channel bonding). I have tried round robin (mode 0) and high availability (mode 1). I know that mode 1 will not give me bandwidth boost. But strangely once i try mode 1 for the guest, I

Hi folks, I have a server where I have solved the well known problem with a bonding interface as netdev on Xen/Centos 5.x (current: 5.2) - the problem is, that in mode=1 (active-passive) the slave interfaces are de-/activated round robin at least once a second. "network-bridge stop netdev=bond0" stops this nonsense and makes the bonded interface work well again. I had to do change 3

Hi folks, I read quite some posts about "Destination host unreachable" problems before, but none could help me to solve my issue. So here we go: This is what I am using: SUSE Linux Enterprise Desktop 10 SP1 - Current with all updates Network configuration of my dom0: foobar:~ # ip a 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd