vMSL with vMCD keeps on crashing

[mszodiac]

Hi everyone.  Thanks for taking the time to read this post.

We have a virtual MSL with virtual Mitel Communications Director installed on an ISS server.
MSL version = 10.0
MCD 3300 ISS version = 6.0.3.7  12.0.3.15

This vMCD is mainly used as the "master sync" to run SDS share from since we have a lot of network elements.  It's been crashing from the get go.  The vMCD becomes unreachable.  Only the Linux IP is responsive with pings but not with SSH.  The only way to get it back up is by rebooting it from vsphere.  I've attached the virtual machine properties.  We have older vMSL which do not have the "virtualization" link.

Any idea why this is happening? Are the specs on the virtual machine properties enough? Any logs on the MSL that I can export that might have a clue?

Thanks.

[ralph]

I could easily be wrong on this but doesn't the machine need to have at least 4G of RAM?

Ralph

[mszodiac]

I was wondering about that too @ ralph.  The virtual machine properties on our vMAS show 4G.  I've attached the snapshot for comparison.  How do I increase the memory without rebuilding the vMSL?

[ralph]

You need to edit the VMware properties. 
Unfortunately I can't provide the step by step.

Ralph

[mszodiac]

Thanks ralph! I'm having our server guy make the change, and will take the vMCD for a test run tonight.

[martyn]

When this was deployed was it done via the OVA file?

[marcolive]

We have a bunch of vMCDs with no problem. Looks like someone modified VM hardware settings or ressource reservations.

I would definitely deploy the OVA a second time, restore data and see how it goes.

[mszodiac]

When this was deployed was it done via the OVA file?

I'll have to ask our engineering team who did the install.

We increased the memory to 4G memory as ralph suggested.  I haven't had a crash so far....

I'll keep our suggestions in mind! Thanks.  For now, I'll be keeping an eye on the vMCD.

[martyn]

If you have adjusted the resources in any way from their default when the OVA was deployed then you will have to revert them back before you would get any support from Mitel as well, as this is now in an unsupported configuration as far as they would be concerned.
You would either have to revert the settings back, or take a backup of the system and then redeploy the OVA and do a restore from there.

[mszodiac]

Just an update....

We had the server team increase the memory to 4G and so far with SDS share to 6 controllers, we haven't had any problem.  Prior to this, SDS share to one would crash it.

Thanks for the tip ralph!