Jason Kwon wrote:
Fajar A. Nugraha wrote:
On Thu, Sep 3, 2009 at 8:57 AM, Jason Kwon<jason.kwon@xxxxxxxxxxxx>
wrote:
I have static IP addresses assigned to each NIC. Simple network
activity like ping or ssh works on all three physical links.
What does your network setup looks like? Are all three NICs on the
same network? Is the client on the same networks as one of the three
NICs?
eth0 is on one network (let's call it network A). eth1 and eth2 are two
ports of a dual-port 10GbE NIC, and they are directly connected to the
client machine (I assigned class C addresses to eth1/eth2). The client
can reach the Xen server either through network A, or through the two
direct 10GbE links.
I have not started any DomU guests on this machine. If I turn off
network bridging in the Xen configuration, then everything returns to
normal (I can run nuttcp/NFS across all three links at normal speed), so
something with the bridging and renaming of the physical links is
affecting network behavior.
You can try creating bridges manually (or using
/etc/sysconfig/network-scripts/ifcfg-*) and see if it makes a
difference.
Thanks, I'll try that next.
Jason
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
I've done a few more experiments, and it appears the problem has to do
with bridging the 10GbE link, and not due to the bridging of multiple
NICs. When I disabled all NICs except one 10GbE link on the Xen host, I
still had problems. I used the following setup:
Machine A: Xen CentOS 5.3 host, single 10GbE NIC
Machine B: Xen Fedora 10 guest, running on Machine A
Machine C: non-Xen CentOS 5.3 host, 10GbE NIC
I have a direct fiber link between Machine A and Machine C, and class C
addresses assigned to all three machines. If I bridge the 10GbE link on
Machine A using network-bridge, I see the following results:
Machine A nuttcp client connecting to Machine C nuttcp server - Works.
Machine B nuttcp client connecting to Machine C nuttcp server - Works.
Machine C nuttcp client connecting to Machine A nuttcp server - Fails.
Machine C nuttcp client connecting to Machine B nuttcp server - Fails.
If instead of using network-bridge, I manually create a bridge on
Machine A for the 10GbE interface, I get the following behavior:
Machine A nuttcp client connecting to Machine C nuttcp server - Works.
Machine B nuttcp client connecting to Machine C nuttcp server - Works.
Machine C nuttcp client connecting to Machine A nuttcp server - Works.
Machine C nuttcp client connecting to Machine B nuttcp server - Fails.
In this case, physical host-to-physical host traffic works in both
directions. In the network-bridge case, host-to-host traffic only works
in one direction. In both cases, Xen guest traffic only works in the
outbound direction. When nuttcp fails, it gives the "server not ACKing
data" error message mentioned before.
Is it not possible to bridge a direct-connected link such as what I've
got? Traffic size also seems to matter, because ping and ssh work
across all links; larger operations like NFS file copy and nuttcp fail.
Thanks,
Jason
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home