On 03/11/2011 01:04 PM, Collins, Kevin [BEELINE] wrote: > Second, are all your physical hosts in a cluster? If not, why can > they see all the SAN LUNs? That is what SAN zoning and security is > for! You don't want a server to be able to see LUNs that aren't for > use by that server.
I'm struggling to be clear here, but failing apparently. The problem can be demonstrated by the following: 1. create new LUN(s) that will be used as a virtual machine disk 2. create the virtual machine, and set up the logical volumes, punching the SAN devices through into the VM. 3. reboot the physical machine (suspending or shutting down the vms too) 4. volumes intended for the VM are now instead active on the host. Hope that helps. No amount of zoning is going to fix that. And actually I do want each of my physical servers to see all the LUNs. The reason is that I need to be able to migrate virtual machines from host to host as needed. But like I say that's kind of beside the point. The real problem exists on just one server! > And if they are clustered, I would think you should be using a > cluster-aware volume manager to deal with that. Could be. Would be super simple if I could prevent the physical hosts from autoconfiguring the volumes on the SAN. _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
