mujzeptu wrote:
I just got told my node reboots are caused by 3.3.1 MU1 with latest patches and I need to update to MU2. Anyone aware of said issue or know what the specific issue is? I feel like 3PAR support has been telling me for the past several years, "a fix is coming!"
Check out the release notes, there are several node reboot fixes listed, hopefully some are applicable to what you're seeing.
We went through similar issues with 3.2.2, it was at MU2 by time I started running it but wasn't till MU4 that I was happy to roll it out across all our arrays. HPE did promise to do better next time (i.e. 3.3.1) so I am hoping MU2 will be stable (previous to 3.2.2 I'd been happy with 3PAR code by time it reached MU2).