Hello,  mgmtd memory leak has been a very common culprit for causing SP reboots on codes before MR3SP1.1.  You are right. Restarting mgmtd process at the right time does help us avoid the reboot. On code MR3SP1.1, the implemented workaround actually restarts mgmtd process if it consumes more than 1GB of memory.  However, code MR4 provides a more definitive solution to the problem. Upgrading to MR4 avoids the condition in which mgmtd would consume so much memory (prevents the memory leak).  Regards, Shardul
Recently We have experienced memory leak error in ECOM (unisphere) which caused sotrage servers connected to SPB restart.  We were informed that it's bug in current code we are using and suggested to perform the upgrade. Meanwhile, Is there any way that we can monitor the cache limit on unisphere and restart management servers once cache threshold is reached.  Thanks
VNXe memory leak bug in code / Monitoring cache limit in unisphere