[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-API] dual nic host
- To: xen-api@xxxxxxxxxxxxxxxxxxx
- From: Chris Percol <chris.percol@xxxxxxxxx>
- Date: Fri, 26 Aug 2011 11:24:58 +0100
- Delivery-date: Fri, 26 Aug 2011 03:26:56 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=NhMtRINd3LQZ1ckjGAvQ/iY74MKS18bJyViasWfvtJ8=; b=TUAsC//6+SSJz595Vn0r8Ks0lbcvh8EXBJPHAYE9TX2mFOczDqKYpg+uJcU3nEcBe3 Q3xk0MokKaWG63+/9dZ/T7EdMkPHxWpeDrL8IKg9wWYZbwknJEHV+WGQUAgXTA40jAwI 6QX5R/vif+xZ5dHva/h6ibPnC+oU9Q+8nc8T8=
- List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
I'm still having problems but I am coming to the conclusion the issue is related to network cards.
Does the following ring any bells for anyone?
I don't have a problem using the embedded ethernet port (netxtreme bcm5722 gigabit pci-e) as theÂmanagementÂinterface on eth0.
eth1 allows me to configure it (rtl8111/8168b pci-e card) as the management interface, ping itself, but not ping the default gateway. The same gateway eth0 is happy to use.
So is it a case of a bum card or is there some gotcha using embedded and card based pci-e I am unaware of, or issues with conflicting drivers?
On Thu, Aug 25, 2011 at 7:58 PM, George Shuklin <george.shuklin@xxxxxxxxx>
Well, if you do really wish to connect hosts (to be exactly, dom0)
to different networks, then create a separate vif's. This can sounds
strange, but you can create vifs and connect them to requited
networks. Control domain is same domain as normal virtual machines,
so you can connect vifs/vbds to them.
'physical' network interfaces (pifs) are used only for bridging.
On 25.08.2011 22
:07, Chris Percol wrote:
Thanks, but in another environment we have a similar
setup and I am struggling to see why this scenario is a problem?
In the otherÂenvironmentÂwe have a host with one nic
connected to a switch then router/gateway, 10.10.0.1. Another
nic in the same host is connected to a separate switch which is
connected to a san with a gateway of 172.16.0.1. Both nics have
addresses on their respective networks and the host can happily
talk to either network .
However, in the new environment we are working on we can not
get xenbr1 on a 192.168.100.0 network to talk to the gateway on
the same network, 192.168.100.1. The xenbr0 connected to
separate physical network of 192.168.1.0 has no problem Âtalking
to the 192.168.1.1 gateway and clients.
I tried adding a route for the 192.168.100.1 which was added
to the route table but still no joy.
Can anyone shed any light?
On Thu, Aug 25, 2011 at 2:40 PM, George
I think this is a task for router.
If you are asking about direct interconnetion between
networks on host,
this is possible, but not supported.
Ð ÐÑ., 25/08/2011 Ð 11:50 +0100, Chris Percol ÐÐÑÐÑ:
> I have a dual nic host running xcp 1 rc3 with each
nic connected to a
> separate physical network/broadband connection,
xenbr0 and xenbr1.
> How do I go about enabling a workstation to ping
xenbr1, which is on
> the same physical network, when the host's gateway
is being set by
> Here's my current setup...
> xenbr0, 192.168.100.3, gateway 192.168.100.1
> xenbr1, 192.168.1.3, (gateway 192.168.1.1)
> Many thanks,
> xen-api mailing list
xen-api mailing list
xen-api mailing list