If you create a single RAID1 volume, there will be two hypers created on two disks.  The size of the hypers will be the size of the volume asked for.  If you create an 9GB volume with RAID5 3+1, you will create 4 hypers on 4 disks each with 3GB.  So you need to figure out how many volumes to create so all 30 disks have the same number of volumes on them.   Somewhere around 8 hypers will be optimal for performance.  Even numbers are good for the RAID1 volumes.  Each DA has two ports.  Each DA has a partner that is used for failover.  Both are active with every other disk being assigned to a specific DA by default.  A given DAE is cabled to a specific DA CPU.  You can get the DA assignments by doing a symdisk list command.  It shows the Director, CPU letter, and interface (port) the disks are connected to.
We are in the process of purchasing a new VMAX array for which we have to do some POC, hence I was doing some research and had the following questions Is there any kind of information in powerlink showing how the cabling is done on the backend?  I found a couple of threads which talk about dividing a disk into 255 splits (some say planning for this 255 number is not good and 128 is a better number)but what I would like to know is that if there is anything wrong in configuring only let’s say 10 or 20 or 30 splits per disk and still utilize the total space of the disk.   Any kind of input is much appreciated.
Backend and Hyper question for VMAX