This could be the way VMAX3 calculates the blocks differently. I have seen this difference when i tried to map VMAX devices to VPLEX.

would be interested to hear from others on this topic

This is expected behavior. All devices on VMAX3 must be created with an whole number of Cylinders. On VMAX3 1 cyl = 1920KB. So all devices must be sized in 1920KB increments.

In this case 517894 MB = 276210.1333 Cyl.

So we must round up to the next whole cyl:

517895.6MB = 276211 cyl.

(when solutions enabler reports this capacity it is rounding up to the nearest MB)