Thanks for your help! I'll continue to look for a solution also and report back if I figure it out. So much fun learning so much new stuff all at once! Not.
Member
Thanks for your help! I'll continue to look for a solution also and report back if I figure it out. So much fun learning so much new stuff all at once! Not.
Member
success!
God I hate computers! No really!
Turned out to be a Xenserver issue all along... I had bonded nics for both VM traffic and storage traffic before I got around to pooling the hosts, and xenserver complained about the primary management interface being bonded, so I broke those bonds but left the storage traffic bond in place while I pooled them.
I noticed some 'weirdness' centered around those bonded interfaces when it was done pooling the hosts, but I just took care of it so that it 'looked' correct. I say looked, because in reality the storage interface on the non pool master members was in place but not functional (ah, thank God for ping!), which is why the SR wouldn't build right. I broke the bond and recreated it, and all is good now.
The NFS share will indeed work with all the pool member IPs listed as both allow and write, and in fact Xenserver won't build the SR with a /24 block as allow and all the pool IPs as write. Well, it will work if all your network interfaces actually work.
Chalk another one up to hard learned experience!
Genius
cool
good to know
Posting Permissions
Reply With Quote