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? Regards, Tanuj _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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? Regards, Tanuj _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Can you post the entries to your bridge configuration files here so that we can find out if there is any error. On Fri, Dec 4, 2009 at 11:57 AM, Tanuj Bansal <bansal.tanuj83@gmail.com> wrote:> 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? > > > Regards, > > Tanuj > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- http://www.abhitech.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Do you need me the script /etc/xen/scripts/network-bridge ? Nothing has been changed there and it is default from the package. and issue on the server is not on daily basis it comes 1 time in a month On Fri, Dec 4, 2009 at 1:32 PM, Tapas Mishra <tapas@abhitech.com> wrote:> Can you post the entries to your bridge configuration files here so > that we can find out if there is any error. > > On Fri, Dec 4, 2009 at 11:57 AM, Tanuj Bansal <bansal.tanuj83@gmail.com> > wrote: > > 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? > > > > > > Regards, > > > > Tanuj > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > -- > > http://www.abhitech.com >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
anyone please help here? On Fri, Dec 4, 2009 at 11:57 AM, Tanuj Bansal <bansal.tanuj83@gmail.com>wrote:> 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? > > > Regards, > > Tanuj >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
can you post a log file entry which clearly describes the error may be we can have a clue there as what is happening. On Sat, Dec 5, 2009 at 11:31 AM, Tanuj Bansal <bansal.tanuj83@gmail.com> wrote:> anyone please help here? > > > On Fri, Dec 4, 2009 at 11:57 AM, Tanuj Bansal <bansal.tanuj83@gmail.com> > wrote: >> >> 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 issued I always restart Dom0 Network and it fixes the issue. >> >> Can anyone please let me know the cause of this? >> >> >> Regards, >> >> Tanuj > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- http://www.abhitech.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I have issue with Dom0 and DomU are working fine. Hence I checked xen logs and system logs file. xen logs have no information Dmesg: eth0: no IPv6 routers present usb 4-1.2: reset high speed USB device using ehci_hcd and address 5 eth0: no IPv6 routers present eth0: no IPv6 routers present messages: avahi-daemon[3381]: iface.c: interface_mdns_mcast_join() called but no local address available. avahi-daemon[3381]: Interface eth0.IPv4 no longer relevant for mDNS. avahi-daemon[3381]: Withdrawing address record for XXXXX on eth0. avahi-daemon[3381]: Leaving mDNS multicast group on interface eth0.IPv6 with address XXXXX. avahi-daemon[3381]: iface.c: interface_mdns_mcast_join() called but no local address available. avahi-daemon[3381]: Interface eth0.IPv6 no longer relevant for mDNS. avahi-daemon[3381]: New relevant interface eth0.IPv6 for mDNS. avahi-daemon[3381]: Joining mDNS multicast group on interface eth0.IPv6 with address XXXXXX. avahi-daemon[3381]: Registering new address record for XXXXXXX on eth0. avahi-daemon[3381]: New relevant interface eth0.IPv4 for mDNS. avahi-daemon[3381]: Joining mDNS multicast group on interface eth0.IPv4 with address yyyyyy. Regards, Tanuj On Sat, Dec 5, 2009 at 1:23 PM, Tapas Mishra <tapas@abhitech.com> wrote:> can you post a log file entry which clearly describes the error may be > we can have a clue there as what is happening. > On Sat, Dec 5, 2009 at 11:31 AM, Tanuj Bansal <bansal.tanuj83@gmail.com> > wrote: > > anyone please help here? > > > > > > On Fri, Dec 4, 2009 at 11:57 AM, Tanuj Bansal <bansal.tanuj83@gmail.com> > > wrote: > >> > >> 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 issued I always restart Dom0 Network and it fixes the issue. > >> > >> Can anyone please let me know the cause of this? > >> > >> > >> Regards, > >> > >> Tanuj > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > -- > > http://www.abhitech.com >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
offloading settings are like this # ethtool -k eth0 Offload parameters for eth0: Cannot get device rx csum settings: Operation not supported Cannot get device udp large send offload settings: Operation not supported rx-checksumming: off tx-checksumming: on scatter-gather: on tcp segmentation offload: on udp fragmentation offload: off generic segmentation offload: off # ethtool -k peth0 Offload parameters for peth0: Cannot get device udp large send offload settings: Operation not supported rx-checksumming: on tx-checksumming: on scatter-gather: on tcp segmentation offload: on udp fragmentation offload: off generic segmentation offload: off On Sat, Dec 5, 2009 at 2:29 PM, Tanuj Bansal <bansal.tanuj83@gmail.com>wrote:> I have issue with Dom0 and DomU are working fine. > Hence I checked xen logs and system logs file. > > xen logs have no information > > Dmesg: > > eth0: no IPv6 routers present > usb 4-1.2: reset high speed USB device using ehci_hcd and address 5 > eth0: no IPv6 routers present > eth0: no IPv6 routers present > > messages: > > avahi-daemon[3381]: iface.c: interface_mdns_mcast_join() called but no > local address available. > avahi-daemon[3381]: Interface eth0.IPv4 no longer relevant for mDNS. > avahi-daemon[3381]: Withdrawing address record for XXXXX on eth0. > avahi-daemon[3381]: Leaving mDNS multicast group on interface eth0.IPv6 > with address XXXXX. > avahi-daemon[3381]: iface.c: interface_mdns_mcast_join() called but no > local address available. > avahi-daemon[3381]: Interface eth0.IPv6 no longer relevant for mDNS. > avahi-daemon[3381]: New relevant interface eth0.IPv6 for mDNS. > avahi-daemon[3381]: Joining mDNS multicast group on interface eth0.IPv6 > with address XXXXXX. > avahi-daemon[3381]: Registering new address record for XXXXXXX on eth0. > avahi-daemon[3381]: New relevant interface eth0.IPv4 for mDNS. > avahi-daemon[3381]: Joining mDNS multicast group on interface eth0.IPv4 > with address yyyyyy. > > > Regards, > Tanuj > > > On Sat, Dec 5, 2009 at 1:23 PM, Tapas Mishra <tapas@abhitech.com> wrote: > >> can you post a log file entry which clearly describes the error may be >> we can have a clue there as what is happening. >> On Sat, Dec 5, 2009 at 11:31 AM, Tanuj Bansal <bansal.tanuj83@gmail.com> >> wrote: >> > anyone please help here? >> > >> > >> > On Fri, Dec 4, 2009 at 11:57 AM, Tanuj Bansal <bansal.tanuj83@gmail.com >> > >> > wrote: >> >> >> >> 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 issued I always restart Dom0 Network and it fixes the issue. >> >> >> >> Can anyone please let me know the cause of this? >> >> >> >> >> >> Regards, >> >> >> >> Tanuj >> > >> > _______________________________________________ >> > Xen-users mailing list >> > Xen-users@lists.xensource.com >> > http://lists.xensource.com/xen-users >> > >> >> >> >> -- >> >> http://www.abhitech.com >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sat, Dec 5, 2009 at 1:01 PM, Tanuj Bansal <bansal.tanuj83@gmail.com> 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 -- Fajar> > > On Fri, Dec 4, 2009 at 11:57 AM, Tanuj Bansal <bansal.tanuj83@gmail.com> > wrote: >> >> 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 Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
1. it is using static IP
2. we use routing to reach the server.
3.
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no peth0
vif0.0
xenbr1 8000.feffffffffff no peth1
vif0.1
xenbr2 8000.feffffffffff no vif4.0
vif3.0
peth2
vif0.2
xenbr3 8000.feffffffffff no vif4.1
vif3.1
peth3
vif0.3
xenbr4 8000.feffffffffff no peth4
vif0.4
xenbr5 8000.feffffffffff no peth5
vif0.5
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@fajar.net> wrote:
> On Sat, Dec 5, 2009 at 1:01 PM, Tanuj Bansal
<bansal.tanuj83@gmail.com>
> 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
>
> --
> Fajar
>
> >
> >
> > On Fri, Dec 4, 2009 at 11:57 AM, Tanuj Bansal
<bansal.tanuj83@gmail.com>
> > wrote:
> >>
> >> 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
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Wed, Dec 16, 2009 at 5:26 AM, Tanuj Bansal <bansal.tanuj83@gmail.com> wrote:> 1. it is using static IP > 2. we use routing to reach the server.> xenbr3 8000.feffffffffff no vif4.1 > vif3.1 > peth3 > vif0.3Do you know the difference between routing and bridged setup? From that output it looks like you''re using bridged setup.> when I use arping -b -I eth0 gateway on dom0, server became accesible.Then it''s just like I said:>> However my guess is your switch/router/gateway simply don''t cache your >> dom0''s arp entry.> > so where may be issue, network team says no issue there side.When it comes to arp issue, they usually say that :D Some alternatives: - try to find out why your gateway/switches can''t find your dom0 arp entry. This can be ... complicated. - put static arp entry on your gateway. This works, but not really recommended, plus your network guys may not allow such setup - setup dom0 to periodically send outgoing packets. A simple ping to gateway in crontab should be enough. This will ensure that network devices will keep up to date entry of dom0''s MAC address. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yes, we are using bridges in dom0 for setup domU but routing on network side to reach my dom0 from outside. btw thanks for the suggestion, your solution really works. On Wed, Dec 16, 2009 at 9:09 AM, Fajar A. Nugraha <fajar@fajar.net> wrote:> On Wed, Dec 16, 2009 at 5:26 AM, Tanuj Bansal <bansal.tanuj83@gmail.com> > wrote: > > 1. it is using static IP > > 2. we use routing to reach the server. > > > xenbr3 8000.feffffffffff no vif4.1 > > vif3.1 > > peth3 > > vif0.3 > > Do you know the difference between routing and bridged setup? From > that output it looks like you''re using bridged setup. > > > when I use arping -b -I eth0 gateway on dom0, server became accesible. > > Then it''s just like I said: > >> However my guess is your switch/router/gateway simply don''t cache your > >> dom0''s arp entry. > > > > > so where may be issue, network team says no issue there side. > > When it comes to arp issue, they usually say that :D > Some alternatives: > - try to find out why your gateway/switches can''t find your dom0 arp > entry. This can be ... complicated. > - put static arp entry on your gateway. This works, but not really > recommended, plus your network guys may not allow such setup > - setup dom0 to periodically send outgoing packets. A simple ping to > gateway in crontab should be enough. This will ensure that network > devices will keep up to date entry of dom0''s MAC address. > > -- > Fajar >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users