I'm experiencing problems when creating a clustered pool and volume on
OES2 SP3. After assigning a new FC LUN which is available on all nodes
I'm using iManager to create a new pool and volume on the master node as
described in the documentation. However, at some point in the procedure
the master starts killing other nodes. Inspection with nssmu shows that
the new pool is just available on some nodes. After a reboot everything
is working nicely.
Should I send the cluster to maintenance mode prior to adding a new
volume? How can I force OES2 to scan for new pools other than rebooting
the system? Is there a known problem or a TID for this behavior?