PowerMAX vVol Status inaccessible when VASA Provider configured in multiple vCenter

I'm not pretty sure whether its flaw or design while configuring the VASA providers of PowerMAX with VMware.

While building the VxRail - PowerMAX vVol, its observed that the vVol reported inaccessible across two different vCenter.

Per customer requirement, single PowerMAX 8500 has been configured to provide storage for two different VxRail clusters managed by two different vCenters. Though PowerMAX got two VP links (Active VP with IP 10.xxx.xxx.58 / Standby VP with IP 10.xxx.xxx.57).

First cluster reported no issues for its vVol irrespective of the VP link when VASA provider was configured over single link. And also, it did not report any issues when the second VASA provider link was configured (note, its irrespective of the VASA provider state on PowerMAX).

While configuring the VASA provider on second vCenter, it was observed that the vVol on first vCenter reported inaccessible. it remained in the same state as inaccessible when the second VP link configured. 

Since it was new build, removed the VASA provider links on both vCenter, tried adding the PowerMAX end active state VP followed the Standby state VP link. It worked.

The concern is, what would be the behavior of vVol during failover or in case of any component failure that affects the VASA provider service.

Is this how it should be configured? First the active followed standby.

Why the PowerMAX VP State isn't learned irrespective of the VP link addition order.