1. it is using static IP
2. we use routing to reach the server.
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no peth0
xenbr1 8000.feffffffffff no peth1
xenbr2 8000.feffffffffff no vif4.0
xenbr3 8000.feffffffffff no vif4.1
xenbr4 8000.feffffffffff no peth4
xenbr5 8000.feffffffffff no peth5
xenbr6 8000.000000000000 no
xenbr7 8000.000000000000 no
xenbr8 8000.000000000000 no
xenbr9 8000.000000000000 no
4. yes, dom0 ping the gateway
5. yes, domU ping the gateway
My all domU are fine and accessible thoughout.
when I use arping -b -I eth0 gateway on dom0, server became accesible.
so where may be issue, network team says no issue there side.
On Sat, Dec 5, 2009 at 5:51 PM, Fajar A. Nugraha <fajar@xxxxxxxxx>
On Sat, Dec 5, 2009 at 1:01 PM, Tanuj Bansal <bansal.tanuj83@xxxxxxxxx> wrote:
> anyone please help here?
You're being to vague, asking for help but not providing any
additional info. Like the simple ones:
- do you use static IP or DHCP
- which networking setup you use, bridged or routing
- what does your bridge setup looks like (output of "brctl show")
- can dom0 ping the gateway
- can domU ping the gateway
etc, etc. ...
However my guess is your switch/router/gateway simply don't cache your
dom0's arp entry. Next time this happens, try using arping from dom0.
So if your dom0 interface is on eth0, and your gateway is 192.168.10.1
(just an example), you can try running (as root)
arping -b -I eth0 192.168.10.1
> On Fri, Dec 4, 2009 at 11:57 AM, Tanuj Bansal <bansal.tanuj83@xxxxxxxxx
>> I am using Xen on Para virtualization and sometimes my dom0 having network
>> issue while at the same moment I am able to access all DomU from network.
>> to fix the issue I always restart Dom0 Network and it fixes the issue.
>> Can anyone please let me know the cause of this?
Xen-users mailing list