Bone-headed error on my part.... :( No IP address assigned to the bond
on the XenServer.
The mis-leading error message didn't help, but I accept the blame for
this one.
Helluva way to get started on the mailing list, huh!
Ron
On 12/10/2013 8:31 PM, Ron Gage wrote:
Thanks for replying!
The Xenserver is a new install and the NFS server has not been set up
on the Xenserver.
Ron
On 12/10/2013 8:28 PM, Ahmad Emneina wrote:
Sounds like the primary storage is already connected to the host. You
can
either add it as a pre-setup in cloudstack, or remove it from the
xenserver
hosts and add it back through cloudstack.
On Tue, Dec 10, 2013 at 5:24 PM, Ron Gage <r...@rongage.org> wrote:
Greetings from Detroit Michigan!
I am trying to set up a small cloud for personal training. My current
issue is that attempting to add primary storage returns the error
message
"Failed to delete storage pool on host".
Setup:
CS 4.2.0
Primary NFS is on the CS server
CS server is dual homed (1 x gig on mgmt network, 2 x gig on storage
network)
storage network is LACP, MTU 9000, switch shows that the LACP bond
is up
to the host as well as to storage
Host: Xenserver 6.2
Question 1: is it ok/appropriate to use XenCenter to set up the bond on
the server for the storage network?
Question 2: How do I get past the "failed to delete" message when
setting
up primary storage?
Thanks!
Ron
