It doesn't make sense.
Most of the time I copy the running software from primary to secondary, so the versions are equal.
After that I update the primary images with a new one and reboot the the switch or stack from the primary image.
If it fails, you can boot from secondary with the old software version.
But you can also first update the secondary .. and later on the primary. Your choice..
I never broke down a switch with an update, but new versions ... sometimes some new bugs, yes ;-)
- Make a copy of your config before update, so you can always rollback .. ;-)
- since version 15/16 software versions, Aruba recommends to update in small updates steps, max. 2 software subversions between each update.
So 16.03 can be updates to 16.05 and so on ...
Suc6!