Both of the controllers are active however, the controllers do not automatically move volumes to the other controller for IO purposes but for example when you create the 1st volume it will get assigned to controller A. When you create a second volume it then gets assigned to Controller B. Now if Volume 1 is high IO and you create a 3rd Volume it will also be assigned to Controller A and it also is high IO then you will have both high IO volumes on the same controller. In Storage Manager you can map a volume to use a specific controller which will help in this kind of a situation.
Above is the link to the Storage Center 6.2 Admin Guide and if you go to page 69 you will see where it talks about Advanced Mapping Options. I hope this helps but if you need anything else please feel free to let me know.
Noted. However in my POC, the 2nd volume did not automatically assigned to Controller B. All new volumes I created always went to Controller A.
If I checked under the Controllers, Controller A is the leader. Could the configuration was setup wrongly?
I tried to access the link you provided, it prompted user name and password. I tried to use Anonymous, but it didn't work. Any idea?
I also have another question: I noticed that I cannot power on single controller only during initial boot up. Both controllers must be powered on together. Otherwise, it won't work. Is that the correct behavior?
I spoke with Dell representative here, and he told me that's the behavior. Both must be turned on together.
I am thinking of a situation where it is not possible to turn both controller (e.g.: due to power failure/controller failure) and only single controller that can be turned on. With current situation, I won't be able to use my storage then.
In the Compellent Architecture, both controllers are active. Failover is done at either the port or controller level depending on how the system was installed. Volumes are "owned" by a specific controller for the purposes of mapping to servers. Changing the owning controller can be done - but it does take a volume down. The controller generates the choices for mapping based on the topology database that it has built based on connections to the server. If there is a setup problem such that one controller can not see a server, then it wont choose that path as an option by default (this might also indicate a setup problem since its a dual path - dual controller environment you should be able to see the server from both controllers. Views from the same volume object will be owned by the same controller. So if you create a gold master boot and use Replays to deploy it to 20-30 servers - all of their boot volumes will come from the same controller.
It is possible to turn on a single Compellent controller to bring a system back online. If the controller you turn on was not the leader pre-shutdown, you may have to ask CoPilot to help you with the command to promote it. Different versions of Compellent firmware work differently in this case - its how split brain is handled.