IPOSE 12.0 deployed on VMWare 2

[William C290]

Hi ,,,

I have IPO Server Edition R12.0 deployed on VMWare. When rebooting either the primary or secondary IPO, the server is stuck and not back-operational, and either web control or web management is not working.
When accessing the server console and rebooting it, it runs again.
this is a strange issue because IPO is a service on servers and it should be working well when rebooting.

 

[derfloh]

Do you get any error messages?

 

[William C290]

@derfloh: No, Everything is going normally.

 

[Mo. Abdullah]

i am facing the same issue here with primary and secondary too.
i will try to re-deploy the 2 VMs again and re-ignite them and will open a ticket with Avaya id i still have the issue.

will update ASAP.

 

[William C290]

@Mo. Abdullah: I create a ticket too.
it seems that Avaya has introduced these Rls without testing them, Look, another issue I face on J100 phones, is configuring the screensaver on it, when it's working, the clock stops and does not work, which means if the screensaver starts at 12:05 AM, it's stuck there and not updated. have you seen this before ???

 

[Mo. Abdullah]

you are right bro. it is really seems that this new rocky Linux product not tested yet.
i didn't face this issue yet. i will try to test it.

send me the steps to update.

 

[William C290]

@Mo. Abdullah: The Problem is that when rebooting the system add the default route (0.0.0.0 being added to eth1), removing it from VMWare solves the issue.

The engineer check another issue regarding Rls 12:0

" when the server is rebooted from Web Control or Manager client application, there was another issue observed on our session regarding the system entering into Emergency mode.
I also mentioned on our call earlier, that this issue has been occurring randomly for some users on VM ware, where the IPO reboots into Emergency mode and some settings of the system are defaulted for the solution. For example, in this case, I could see the additional HDD path being removed.
In this case, the only next actions recommended from our end would be to wait for and upgrade to IPO version 12.1 (releasing by the end of November 1st week).
Since this case is occurring randomly for some systems and the solution is already available- to upgrade to version 12.1 and not reboot the IPO server till then, there is no other workaround or solution confirmed for version 12.0 "

 

[Mo. Abdullah]

thanks for the update william.
do you mean that i should remove the default ip route 0.0.0.0 for the primary and secondary from the Manager app ?

 

[digital12188]

Seems we may have a similar issue with 12.0 deployed in VMware environment. I have 2 out of 5 system that were either upgraded to 12.0 or spun up as 12.0 and if rebooted they do not come back up. We have to go to console and restart.
I am trying to look at similarities for the ones that don't recover but, so far I haven't found anything.
Has Avaya responded to any tickets that have been open with them?

 

[digital12188]

I did see something on the support site about support for Nutanix but, we are not using that.

 

[digital12188]

So is the solution mentioned above to remove the route or disable/remove Eth1?

 

[R3LzX]

was this an iso install or an ova install I had other issues with the iso

 

[digital12188]

These are a Mix of new OVA installs and some systems that was upgrade from 11.1 to 12.0.
Further troubleshooting confirmed The Problem is that when rebooting the system add the default route (0.0.0.0 being added to eth1).

The fix so far has been to remove the Nic for Eth1. Once done requires a rehost of the licenses since it changes Host ID.

Weird thing though it isn't on all the systems just some. Not sure what the commonality of the ones that have issue are yet.

 

[William C290]

@Mo. Abdullah @digital12188

Below is a quick summary of the issue that has been reported and the resolution we have given for your reference.


Issue Reported: IPO Server Edition R12.0 deployed on VMWare. When rebooting the primary or secondary IPO, the server is stuck and not operational, and neither web control nor web management is working. When accessing the server console and rebooting it, it runs again.

Resolution Given: Issues with Emergency mode can only be resolved with R12.1, while the problem with blank IP route being added after rebooting- was resolved after removing network adapter 2 from VMware machine settings.

 

[derfloh]

Thanks for sharing.