Unisphere for VMAX - application keeps crashing

Question

Hi All,

hoping someone can help. I have a Windows 2003 server running Unisphere 1.6.2.4 and SE 7.6.2.8. The server has 2 quad core processors and 12GB RAM.

Since the weekend, Unisphere service keeps stopping and I can't find any reason for it. We were running version 1.5.1.1 so I decided to upgrade it to 1.6.2.4 in the hope that it would resolve the problem. After the upgrade I was able to log in but after 10-15 minutes it stopped again. Server has been rebooted several times but no joy.

When I restart Unisphere, the log on screen appears. I then enter my details and it seems to try and log me in for about 10 minutes before giving stating that there was a connection error.

No changes have been made in our environment over the weekend so not sure what's happening. I've tried accessing Unisphere from both the browser on my PC and on the server that it's installed on. no joy.

Any suggestions are much appreciated.

echolaughmk · Answer

This solution looks to fit the picture you included: https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA1700000000gHP

Here is the original KB with what looks to be the same error code you are hitting: https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA1700000000ktB

Not sure if it relates or not given the DMX variable. This solution also relates to the same issue, all of which look to utilize a symavoid file of some sort to rule out the trouble array discovery: https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA17000000014AQ

When this happens, I would check to see if your SMAS service and SMASDB services are currently running or if they stop all of a sudden. It might be key to also note that Windows 2003 is not officially support per the UNI install guide for 1.6.2 and that in your 12GB of RAM on the machine, you will want to make sure the available RAM is 4GB with no performance or 8GB with performance analyzer. This won't be the total amount of memory configured, but rather what is free when the application starts. So if you have 12GB allocated, but only shows 2GB free when the server boots....then you might want to allocate more memory. Not sure if this is the case, but figured I would throw it out there as a check.

MarkyP99 · Answer

Thanks for your reply. We only have VMAX arrays attached to this server, no DMX.

Also, the full 12GB is available to the applications on this server. The KB suggests that this was fixed in SE 7.6.1 and as I mentioned we are running 7.6.2.8

VMAX

Unisphere for VMAX - application keeps crashing

Was this post helpful?