Skip to main content
Has anyone upgraded to AOS 5.10.3.1 yet? Have you experienced any issues?



We are trying to determine if we should upgrade to AOS 5.10.2 or AOS 5.10.3.1...any feedback would be appreciated.
i am planning for the same too, from 5.10.2 to 5.10.3.1

feedback will be appreciated
We are on 5.10.2 and I don't see much benefit in grading up right now. Upgrading on our clusters always means cleaning up /home/nutanix manually before the one-click fun takes off.
How has AOS 5.10.2 been?
How has AOS 5.10.2 been?

it is stable without any noticed issues from my side.

i had a huge memory consumption and some errors about cluster reachability on Prism Central so that i am starting to update it to 5.10.3 today and check the performance before raising tickets


How has AOS 5.10.2 been?it is stable without any noticed issues from my side.

i had a huge memory consumption and some errors about cluster reachability on Prism Central so that i am starting to update it to 5.10.3 today and check the performance before raising tickets




Let us know how the AOS 5.10.3.1 upgrade goes. We should start upgrading a few of our clusters tomorrow.




How has AOS 5.10.2 been?it is stable without any noticed issues from my side.

i had a huge memory consumption and some errors about cluster reachability on Prism Central so that i am starting to update it to 5.10.3 today and check the performance before raising tickets
Let us know how the AOS 5.10.3.1 upgrade goes. We should start upgrading a few of our clusters tomorrow.


i tried to start upgrading Prism Central, but i have a weird issue of Epsilon Service down which prevents the upgrade, and now the web ui is totally unreachable.

a case has been just raised to check what is going on.
We upgraded two of our clusters to 5.10.3.1 last week. So far there hasn't been any problems. We are closely monitoring. We had a couple of issues on 5.10.1.1 that we hope are resolved in this version.


i tried to start upgrading Prism Central, but i have a weird issue of Epsilon Service down which prevents the upgrade, and now the web ui is totally unreachable.

a case has been just raised to check what is going on.




We are experiencing the same problem. Have you solved Epsilon service down?



Regards
We upgraded two of our clusters to 5.10.3.1 last week. So far there hasn't been any problems. We are closely monitoring. We had a couple of issues on 5.10.1.1 that we hope are resolved in this version.



Hello,



I am curious to know what issues you were experiencing prior?

Did one happen to be Servers 2012 hanging during reboot on the splash screen?


We upgraded two of our clusters to 5.10.3.1 last week. So far there hasn't been any problems. We are closely monitoring. We had a couple of issues on 5.10.1.1 that we hope are resolved in this version.Hello,



I am curious to know what issues you were experiencing prior?

Did one happen to be Servers 2012 hanging during reboot on the splash screen?




We actually fixed the "Windows Server 2012 hanging during reboot on the splash screen" issue buy using the latest version of the VirtIO drivers.



We think we were having broadcast storms in our environment. We haven't seen anything like that since the upgrade.


i tried to start upgrading Prism Central, but i have a weird issue of Epsilon Service down which prevents the upgrade, and now the web ui is totally unreachable.

a case has been just raised to check what is going on.
We are experiencing the same problem. Have you solved Epsilon service down?



Regards




We didn't have any Epsilon issues during the upgrade...


i tried to start upgrading Prism Central, but i have a weird issue of Epsilon Service down which prevents the upgrade, and now the web ui is totally unreachable.

a case has been just raised to check what is going on.
We are experiencing the same problem. Have you solved Epsilon service down?



Regards


i tried everything but failed, so i raised a support case and they find an issue with CALM that that has service IP of an old cluster that has been completely removed and cleaned up from Prism Central.

as i do not use CALM yet i asked to completely disable and reset CALM.

after that Epsilon service issue has been resolved.

i upgraded both AOS and Prism Central and everything looks smooth now.

despite a strange bug of giving me unknown NCC in the software upgrade although i have the latest one, tried to download and re-install and it shows the same unknown and suggest to download the latest "which is already installed".




i tried to start upgrading Prism Central, but i have a weird issue of Epsilon Service down which prevents the upgrade, and now the web ui is totally unreachable.

a case has been just raised to check what is going on.
We are experiencing the same problem. Have you solved Epsilon service down?



Regards
We didn't have any Epsilon issues during the upgrade...


as i discussed with the support engineer, Epsilon was introduced recently with calm, if you do not use Calm you wont find it in "cluster status" output.