Hi,       Thank you for posting your question in EMC forum. Please find article understanding available space in storage pool  If most of the space is already been allocated to one storage processor, even after creating new iSCSI server on other SP doesn't give option to create storage on other SP.  As you mentioned that all storage was created on SPB that means most of the total space available in global pool was allocated to SPB. In this case VNXe doesn't give option to create storage on SPA.  It certainly depends how much storage is created on SPB and what kind of provisioning was configured.  Could you provide details of storage pool?  - Total space on storage pool - Allocated space on storage pool - Subscription level on storage pool  These information will give us clear indication why you are not able to create storage on SPA.  Regards, Swapnil
I'm hoping someone is more familiar with the EMC VNXe 3100 to tell me if this is normal behaviour, I am changing the storage around a bit and creating a new Hyper-V cluster so I have been making a few changes.  I originally had one ISCSI server setup that was attached to storage processor B, this is still active.  The storage NICs on both SPs are aggregated.  I created two new ISCSI servers ISCSIServerA (Storage Processor A) and ISCSIServerB (Storage Processor B) with the intention of spreading the load between the SPs however, when I go to add a new LUN I only ever get a choice of attaching them to the two ISCSI servers that are on SPB and not ISCSIServerA of SPA.  So I'm wondering is this normal behaviour or am I missing something ?
EMC VNXe ISCSI Server selection for new LUN behaviour