My take: you should use the one which support (or, better, provide) all the features (particularly those ones newly introduced) your network needs.
Very generic answers...yeah, I know it yet.
Some others may say that (a) is adviseable to stay on a maintenace version like the 15.16m (very conservative), (b) is adviseable to stay on a intermediate version like any between 15.18, 16.01 or 16.02 just to avoid to live on the edge or (c) is adviceable to stay on the very latest branch (so 16.03, actually).
Personally, thinking that each new branch (15.x, 16.x) is derived from a particular version (let me say first 16.(n) build is derived by first 16.(n-1) build and so on) of the previous one (see Release Notes [*] to see what I mean), why not to live on the edge to benefit from latest introduced features especially if you need them (see example below)?
The features approach is clear if you look at HPE ArubaOS-Switch Software Feature Support Matrix 16.03 published January, 6th 2017 (available only for ArubaOS-Switch based switch series) in which an updated list of Software Features is provided for 3810 (KB), 3800 (KA), 5400R zl2 (KB), 2930F (WC), 2920 (WB), 2540 (YC), 2620 (RA) and 2530 (YA/YB) indicating the minimum firmware version the considered Switch series should run to support that particular listed Software Feature or set of Software Features.
Looking at the latest one available for 16.03 you can discover that, as example, the VRRP Software Feature (with other VRRP related features) was introduced on Aruba 2930F (WC) since the WC.16.03.0003 and it was not available before on that platform (incidentally discussed here).
[*] As example:
- YA/YB.16.03.0003 was the initial 16.03 build for YA/YB.
- YA/YB.16.03.0003 was based on YA/YB.16.02.0008 plus additional software enhacements and fixes introduced with the YA/YB.16.03.0003 software release itself.
- YA/YB.16.03.0004 is the latest 16.03 build published for YA/YB as of today.
- YA/YB.16.02.0008 was the initial 16.02 build for YA/YB.
- YA/YB.16.02.0008 was based on YA/YB.16.01.0004 plus additional software enhacements and fixes introduced with the YA/YB.16.02.0008 software release itself.
- YA/YB.16.02.0018 is the latest 16.02 build published for YA/YB as of today.
- YA/YB.16.01.0004 was the initial 16.01 build for YA/YB.
- YA/YB.16.01.0004 was based on YA/YB.15.18.0007 plus additional software enhacements and fixes introduced with the YA/YB.16.01.0004 software release itself.
- YA/YB.16.01.0012 is the latest 16.01 build published for YA/YB as of today.
- YA/YB.15.18.0006 was the initial 15.18 build for YA/YB.
- YA/YB.15.18.0006 was based on YA/YB.15.17.0003 plus additional software enhacements and fixes introduced with the YA/YB.15.18.0006 software release itself.
- YA/YB.15.18.0013 is the latest 15.18 build published for YA/YB as of today.
and so on...basically it is a recurring schema (note a little discrepancy about the recurring previous build used to create the next one branch initial build between 15.18 and 15.17: 16.01.0004 is based on 15.18.0007 which isn't the very first build of the 15.18 branch since that was the 15.18.0006 based on 15.17.0003 and not the 15.18.0007).
I'm not an HPE Employee
Yep, I wrote that between the lines, above: "YA/YB.16.03.0004 is the latest 16.03 build published for YA/YB as of today." yesterday.
I'm not an HPE Employee
I'm not an HPE Employee
The new Next Gen GUI should have been yet available since the release of 16.03.0003...doesn't matter:
"Next Gen Web UI
The Next Gen Web GUI, which was experimental and available only on the 2930F, is now available on all ArubaOS-Switch platforms and includes additional troubleshooting and visualization capabilities.
Next Gen Web UI is the default Web UI from 16.03 release onwards. There is an option in the CLI to set the older GUI as the default if desired."
I'm not an HPE Employee