ALUA is not something you reset, it's an array side feature, sounds to me you might have configured the wrong persona type on the array for the hosts or the hosts have not been correctly configured for multipathing.
If you look at the persona types :
showhost -listpersona
Persona_Id Persona_Name Persona_Caps
1 Generic UARepLun,SESLun
2 Generic-ALUA UARepLun,SESLun,ALUA
6 Generic-legacy --
7 HPUX-legacy VolSetAddr,Lun0SCC
8 AIX-legacy NACA
9 EGENERA SoftInq
10 ONTAP-legacy SoftInq
11 VMware SubLun,ALUA
12 OpenVMS UARepLun,RTPG,SESLun,Lun0SCC
13 HPUX UARepLun,VolSetAddr,SESLun,ALUA,Lun0SCC
15 WindowsServer UARepLun,SESLun,ALUA,WSC
ALUA allows the array to send notificationsa to the host that there have been things like path changes to VLUNs and also which paths are the best to use when accessing a vlun.
UARepLun lets the array notify the host that there are VLUN changes (vluns added or removed)
SESLun adds a VLUN 254 to allow host explorer to register hosts with the array
SubLun addes VLUN 256 which allows VMware to send commands to the array .. used for VVols etc
VolSetAddr lets HPUX hosts work .. cause HPUX is a PITA for storage
and the others I can't remember.
You need to make sure you follow the host connectivity guides for connecting your server+OS to the 3PAR to the leter. Older versions of OSs may need different persona settings to newer, get it wrong and things go weird.