Where is AOS 6.1.3 for AP9630 NMCs?

[BillP]

This question was originally posted by Kumba on APC forums on 3/19/2014

---

Checking for updates to the AP9630 network management card that I have in my SmartUPS SUA1000, and I see there is a major firmware update to the 6.x.x series of SUMX/AOS.  However, I notice a warning to read KB FA176047 before upgrading.  As I am on AOS 5.1.7 right now, I read that, and several of the other KB articles referenced by FA176047.  In short, there seem to be a lot of problems with the 6.0.6 release that is available for download for the AP9630, and the KB articles even suggest that if these problems are too much, to stay at 5.x.x or downgrade back to 5.x.x.  It also states that many of these issues were fixed in AOS 6.1.3

However, I cannot find AOS 6.1.3 *anywhere*.  The latest available AOS release for AP9630 (or for any NMC it seems) is AOS 6.0.6 (and I assume, SUMX 6.0.6 and BootMon 1.0.2).  Seeing as the various KBs are all from Jan 2014, is AOS 6.1.3 available anywhere else?  I dug through the old APC FTP site and didn't find anything.  Is it still in beta testing?  Is it hidden at the end of the rainbow?  Do I have to dance for it?  Where can I find it?

[BillP]

This reply was originally posted by Angela on APC forums on 4/9/2014

---

I updated the kbase a bit last week to try and add the chart like you suggested.

As it stands now, I hope to see a next fairly large bug release for sumx and sy applications around late July-ish but that could very well change.

[BillP]

This reply was originally posted by Kumba on APC forums on 3/20/2014

---

Checking for updates to the AP9630 network management card that I have in my SmartUPS SUA1000, and I see there is a major firmware update to the 6.x.x series of SUMX/AOS.  However, I notice a warning to read KB FA176047 before upgrading.  As I am on AOS 5.1.7 right now, I read that, and several of the other KB articles referenced by FA176047.  In short, there seem to be a lot of problems with the 6.0.6 release that is available for download for the AP9630, and the KB articles even suggest that if these problems are too much, to stay at 5.x.x or downgrade back to 5.x.x.  It also states that many of these issues were fixed in AOS 6.1.3

However, I cannot find AOS 6.1.3 *anywhere*.  The latest available AOS release for AP9630 (or for any NMC it seems) is AOS 6.0.6 (and I assume, SUMX 6.0.6 and BootMon 1.0.2).  Seeing as the various KBs are all from Jan 2014, is AOS 6.1.3 available anywhere else?  I dug through the old APC FTP site and didn't find anything.  Is it still in beta testing?  Is it hidden at the end of the rainbow?  Do I have to dance for it?  Where can I find it?

[BillP]

This reply was originally posted by Angela on APC forums on 3/20/2014

---

I write the knowledge base articles for Network Management Cards

Each device (Rack PDU, Smart UPS, Symmetra, etc) comes with both an AOS and an application file. For AP9630/AP9631 UPS Network Management Cards and the sumx and sy applications for Smart UPS, or Symmetra respectively, the latest AOS is 6.0.6 still, but 6.1.1 is coming (barring no problems), within a week to fix kbase FA175981 and FA176048 only. The Rack PDU devices that use rpdu2g application, have AOS 6.1.3 already with their app so the issues are fixed there. You cannot unfortunately update just the AOS - it has to be with an application it has been released with or else lots of these headaches would already be a non-issue.

So, AOS 6.1.3 (or higher) for sumx and sy apps won't be available until later this year. Maybe I need to clarify in the knowledge base articles that the user needs to verify for their particular application if AOS 6.1.3 is available or not. I was just trying to avoid having to update it for every single application and leave it more general.

Let me know if you have any questions.

[BillP]

This reply was originally posted by Kumba on APC forums on 3/20/2014

---

Hi Angela,

I would agree that more emphasis is needed on the availability of AOS 6.1.x for various NMC model numbers.  In the master FA for 6.x problems, I would create a table that lists each affected NMC part number, and for each P/N, list the highest-available AOS/SUMX release, along with which FA's are resolved by updating to the highest release, and which FA's still remain unresolved.  By placing it in the master FA, you create a one-stop-shop of information for anyone who decides to look this up.  Especially if the advice might include holding off on an update until 6.1.3 eventually becomes available.

Example for the AP9630:

P/N	Highest AOS Release	Resolved FA's	Unresolved FA's
AP9630/31	6.1.1	FA175981, FA176048	FA175980, FA175982, FA177701, FA177263

Other curious question: Why so long for a release?  Is it the amount of testing done to the code to make sure all bugs are covered and no new bugs were introduced?  Also, I take it AOS is the operating system running on the NMC (some kind of RTOS I assume?  Kernel only?), while SUMX is the application(s)/userland?  I.e., does SUMX provide the HTTP, telnet, SSH, and SMTP functionality?

Thanks!

[BillP · Accepted solution]

This reply was originally posted by Angela on APC forums on 3/21/2014

---

Hi Kumba,

Thank you for taking the time to provide feedback. Let me quickly touch up the articles to make them a little more clear immediately and then long term see what I can do for the master article over the next few weeks. I tried to keep it a little general because we have so many different applications and certain bugs will either be a part of the AOS or the application module and I didn't want to update it every week when a new application comes out. I am also in the loop for majority of applications but sometimes one or two sneak out that I miss depending on the product group.

And yes, the AOS is the "APC Operating System" which contains the backbone Operating System stuff which are items like - Web functions, telnet, FTP, RADIUS, SMTP, etc and then the application module (sumx, sy, rpdu2g, sypx, etc) typically contains the information in order to communicate to the particular UPS or other device type. There are a couple areas where they overlap a little bit, such as with config.ini and notification set up. They are developed on separately so while an AOS might be available for an application, it does not get released until the application development and testing is complete.

It generally takes a while because of the amount of testing done, to verify that bugs are fixed and yes, no new bugs are created. We also have so many variables - different types of UPS models, PowerChute Network Shutdown integration, etc.  We are working on doing shorter release periods. My vote is fix less stuff per release but have more releases so at least they get out quicker and for new issues, there is light at the end of the tunnel instead of waiting for a release forever. I have also highlighted the long release times negatively impact our users. I firmly believe once we get AOS 6.1.3 and higher that the system will be a LOT more stable.

Please let me know if you have any other questions or concerns.