[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] new xen guest cannot communicate with the network
- To: xen-users@xxxxxxxxxxxxx
- From: Jan Hejl <jh@xxxxxxxxxx>
- Date: Tue, 18 Feb 2014 13:55:22 +0100
- Delivery-date: Tue, 18 Feb 2014 12:56:47 +0000
- Domainkey-signature: a=rsa-sha1; c=nofws; d=excello.cz; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type; q=dns; s=default; b=e4BBhxJR7xIk1fDvTIEL3roFugS73 1dvIenGNtNe84+iCW1cc58xl9563LYOEKmS2e98roByjZzgbRWiHd7WNWCahkD37 S0H9OUGL/B8id7CgFivcD9rdB0EnxMVyx76uzwki+5NYIEgZhnQ1caNcSHmkSmOk 7AOqwIy2yfiUl8=
- List-id: Xen user discussion <xen-users.lists.xen.org>
Hello Simon,
Dne 18.2.2014 13:09, sbdcunha napsal(a):
Dear All,
I had this post earlier but just open a new one..
As I mentioned earlier the domu are not able to communicate to other
computers except dom0
let me explain
had a fresh new installation of Centos 6.5 x64 minimul edition working fine.
installed xen 4.3 . the install went fine and no issues
the server is a Cisco UCS 200 M3 Blade Servers with 2 NICs
ifconfig shows the below
--------
[root@xenserver2 scripts]# ifconfig
br0 Link encap:Ethernet HWaddr 00:25:B5:01:00:0C
inet addr:aa.aa.aa.126 Bcast:172.16.2.255 Mask:255.255.255.0
inet6 addr: fe80::225:b5ff:fe01:c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:407445 errors:0 dropped:1845 overruns:0 frame:0
TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:27709516 (26.4 MiB) TX bytes:2728 (2.6 KiB)
br1 Link encap:Ethernet HWaddr 00:25:B5:01:00:0D
inet addr:bb.bb.bb.54 Bcast:91.198.134.63 Mask:255.255.255.224
inet6 addr: fe80::225:b5ff:fe01:d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:556949 errors:0 dropped:1843 overruns:0 frame:0
TX packets:129246 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:466519471 (444.9 MiB) TX bytes:39497349 (37.6 MiB)
eth0 Link encap:Ethernet HWaddr 00:25:B5:01:00:0C
inet6 addr: fe80::225:b5ff:fe01:c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:407445 errors:0 dropped:0 overruns:0 frame:0
TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:36673306 (34.9 MiB) TX bytes:3988 (3.8 KiB)
eth1 Link encap:Ethernet HWaddr 00:25:B5:01:00:0D
inet6 addr: fe80::225:b5ff:fe01:d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:773573 errors:0 dropped:0 overruns:0 frame:0
TX packets:137373 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:494827266 (471.9 MiB) TX bytes:40644498 (38.7 MiB)
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:65536 Metric:1
RX packets:38031 errors:0 dropped:0 overruns:0 frame:0
TX packets:38031 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:25724657 (24.5 MiB) TX bytes:25724657 (24.5 MiB)
vif4.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:70 errors:0 dropped:0 overruns:0 frame:0
TX packets:195770 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:2960 (2.8 KiB) TX bytes:16697344 (15.9 MiB)
virbr0 Link encap:Ethernet HWaddr 7E:59:9C:79:56:E5
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
------
route on dom0 shows me
---------
[root@xenserver2 scripts]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
default bb.bb.bb.62 0.0.0.0 UG 0 0 0 br1
bb.bb.bb.32 * 255.255.255.224 U 0 0 0 br1
link-local * 255.255.0.0 U 1004 0 0 br0
link-local * 255.255.0.0 U 1005 0 0 br1
aa.aa.aa.0 * 255.255.255.0 U 0 0 0 br0
192.168.122.0 * 255.255.255.0 U 0 0 0
virbr0
---------------
Now from the DOM0 server i can ping the gateway which is bb.bb.bb.62 and
also my network computers which are on different networks. and also internet
brctl shows
----
bridge name bridge id STP enabled interfaces
br0 8000.0025b501000c no eth0
br1 8000.0025b501000d no eth1
vif4.0
virbr0 8000.000000000000 yes
-----
Now I created a new dom U selecting bridge br1 and assigned a ip address of
bb.bb.bb.55. now I can ping the DOM0 br1 ip that is bb.bb.bb.54. but if I
try to ping the dom0 gateway that is bb.bb.bb.62 i cannot pint it neither
any computer on the network
Do you have /proc/sys/net/ipv4/ip_forward enabled?
then I also tried to create a new domU and selected the interface as virtual
network default : NAT and then from this domU everythings works perfect.
i can ping the gateway that is bb.bb.bb.62 and also any computer on our
network and also internet works fine
Really would appreciate your kind help in troubleshooting.
Thanks nd regards
simon
Jan
--
View this message in context:
http://xen.1045712.n5.nabble.com/new-xen-guest-cannot-communicate-with-the-network-tp5721312.html
Sent from the Xen - User mailing list archive at Nabble.com.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users
Attachment:
smime.p7s
Description: Elektronicky podpis S/MIME
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users
|
