![]() ![]() |
#1
|
|||
|
|||
![]()
With Avaya Aura 7.0.1 - having issues with Avaya Aura Communication Manager deployed on VMware environment.
Initial problem development with degraded performance observed, SIP endpoints were disconnecting from the Session Manager. Performed a graceful shutdown of Avaya environment with degraded performance pointing to a faulty raid array drive. replacement drive put into service and the VM's were restarted on the vSphere host machine. VM's for the Utility Server, System platform, Session Manager, and SAL all restarted with minimal issues, when restarting the Communication Manager it fails to complete the Linux boot steps. gives the following message: init: rcS main process (286) terminated with status 1 telinit: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the rply, the reply timeout expired, or the network connection was broken. init: rcS post-stop process (737) terminated with status 1 ![]() Ultimately wishing not to redeploy the CM if that is possible - and am looking for solution, Support ticket with tech support has not aided in resolution. Think that the environment is not specifically related to the Communication Manager. |
![]() |
Tags |
aura cm, system platform, vsphere |
Thread Tools | Search this Thread |
Display Modes | |
|
|