[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-API] Dual nic issues on xcp 1 rc3 that do not occur on xenserver 5.6.0
- To: xen-api@xxxxxxxxxxxxxxxxxxx
- From: Chris Percol <chris.percol@xxxxxxxxx>
- Date: Fri, 26 Aug 2011 12:08:26 +0100
- Delivery-date: Fri, 26 Aug 2011 04:12:10 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=Aps4wsvFbg6cP7E9vboBqOWsw1wpTzJsycLxMZJXRYE=; b=m1ic60UBEHAGnq4qFrAV2ZlZhnqPnnNahU90KX1Zue3uDLF7ZUbcjxqwKfPKI+Q0XC vH3oSeQj3bSiRdZy/kveEUqFVk15+EG7PdGHmVGo+erlOdwNHTyR4w24dlNZGzAq2/ap O5GCAhR2b7C20NgWwuDI1BzB33eK0Nc5P9+A0=
- List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
I have been discussing some problems I have been having with a dual nic host on the list but I have started this new message as I misunderstood the actual problem.
I can confirm that xcp 1 rc3 does not function properly using the following nics on a Dell Poweredge T105.
Embedded, Netxtreme BCM5722 Gigabit PCI-e
Card, RTL8111/8168b PCI-e
Both nics are connected to separate physical networks. I can only ever use eth0, Nextxtreme, as the management interface successfully. It is not possible to use eth1, RTL8111, as the management interface. Although eth1 will allow me to configure an ip address for itself and successfully ping that address it cannot ping it's gateway.
This behaviour does not occur in Xenserver 5.6.0 using the same setup.
Any thoughts would be appreciated as I am keen to run with XCP.
xen-api mailing list