I'm just going to leave this here in case anyone else runs in to this problem.
When adding the 3par array as a VASA provider, you must ensure that your array vasa self-signed CA CN field matches EXACTLY with the output of showvasa
Example:
san01 cli% showvasa
-Service- --------VASA_API2_URL--------- -MemUsage(MB)- -Version-
Enabled https://ip-address:9997/vasa 87 2.2.9
san01 cli% createcert vasa -selfsigned CN ip-address
If they do not match, you'll still be allowed to initially connect and register, but the array will show offline and standby in the provider list. The documentation provided by 3par instead uses a SAN in the cert field for the ip address, but it's all dependent on your listening hostname. Use the CN only.
sps.log on the appliance will show the following during registration:
java.io.IOException: HTTPS hostname wrong: should be <ip-address>