Network Management

Hi all :) 
So I'm a little new to Aruba so this will no doubt be a very simple question for someone. 
Looking to get some clarity on how the primary and seconday partitions work within the contollers, Mobility masters and Airwave etc..
In short, when preforming a system upgrade to the backup partition does it also bring over the current running device configuration? Or does it just "install" the firmware/OS ?

My senario is i have a single Mobility master with 4x controllers.  The current backup parition on each respective node hasnt been upgraded in quite a while and previous admins have continued upgrading the primary partitions. I'm wanting to get the backup partition version up to date (or previous running config for roll back purposes) so as to have a cleaner system. Can i simply run the firmware upgrade process on the seconday/backup partition and boot to that with it also maintining the current running configurations of the controller? Or do you have to transfer licences and running configuartion to what is now the new primary partition once the upgrade process is completed? Apologies as this is no doubt a noob question. Does the running config live accross both partitions ?  or does the upgrade process save and install the current running configuration/state of the controller  into the new partition whilst also upgrading the firmware. 

Thanks for any advise in advance :)

Cheers
Luke

In short, when preforming a system upgrade to the backup partition does it also bring over the current running device configuration? Or does it just "install" the firmware/OS ?  YES.  Upgrading either partition will use the same shared configuration.

Can i simply run the firmware upgrade process on the seconday/backup partition and boot to that with it also maintining the current running configurations of the controller? YES

Apologies as this is no doubt a noob question. Does the running config live accross both partitions ?  or does the upgrade process save and install the current running configuration/state of the controller  into the new partition whilst also upgrading the firmware.
YES.  The firmware is the OS.  It is separate from the configuration, which is used(shard) by either partition that you boot into.  The secondary partition just makes it easier to quickly upgrade or downgrade the OS by setting a boot partition.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
------------------------------

Original Message:
Sent: Nov 02, 2022 09:03 AM
From: Luke John
Subject: System Upgrades and Patitions

Hi all :)
So I'm a little new to Aruba so this will no doubt be a very simple question for someone.
Looking to get some clarity on how the primary and seconday partitions work within the contollers, Mobility masters and Airwave etc..
In short, when preforming a system upgrade to the backup partition does it also bring over the current running device configuration? Or does it just "install" the firmware/OS ?

My senario is i have a single Mobility master with 4x controllers.  The current backup parition on each respective node hasnt been upgraded in quite a while and previous admins have continued upgrading the primary partitions. I'm wanting to get the backup partition version up to date (or previous running config for roll back purposes) so as to have a cleaner system. Can i simply run the firmware upgrade process on the seconday/backup partition and boot to that with it also maintining the current running configurations of the controller? Or do you have to transfer licences and running configuartion to what is now the new primary partition once the upgrade process is completed? Apologies as this is no doubt a noob question. Does the running config live accross both partitions ?  or does the upgrade process save and install the current running configuration/state of the controller  into the new partition whilst also upgrading the firmware.

Thanks for any advise in advance :)

Cheers
Luke

Thanks for clarifiing @cjoseph​ :) Legend!
Original Message:
Sent: Nov 11, 2022 02:14 PM
From: Colin Joseph
Subject: System Upgrades and Patitions


In short, when preforming a system upgrade to the backup partition does it also bring over the current running device configuration? Or does it just "install" the firmware/OS ?  YES.  Upgrading either partition will use the same shared configuration.

Can i simply run the firmware upgrade process on the seconday/backup partition and boot to that with it also maintining the current running configurations of the controller? YES

Apologies as this is no doubt a noob question. Does the running config live accross both partitions ?  or does the upgrade process save and install the current running configuration/state of the controller  into the new partition whilst also upgrading the firmware.
YES.  The firmware is the OS.  It is separate from the configuration, which is used(shard) by either partition that you boot into.  The secondary partition just makes it easier to quickly upgrade or downgrade the OS by setting a boot partition.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card

Original Message:
Sent: Nov 02, 2022 09:03 AM
From: Luke John
Subject: System Upgrades and Patitions

Hi all :)
So I'm a little new to Aruba so this will no doubt be a very simple question for someone.
Looking to get some clarity on how the primary and seconday partitions work within the contollers, Mobility masters and Airwave etc..
In short, when preforming a system upgrade to the backup partition does it also bring over the current running device configuration? Or does it just "install" the firmware/OS ?

My senario is i have a single Mobility master with 4x controllers.  The current backup parition on each respective node hasnt been upgraded in quite a while and previous admins have continued upgrading the primary partitions. I'm wanting to get the backup partition version up to date (or previous running config for roll back purposes) so as to have a cleaner system. Can i simply run the firmware upgrade process on the seconday/backup partition and boot to that with it also maintining the current running configurations of the controller? Or do you have to transfer licences and running configuartion to what is now the new primary partition once the upgrade process is completed? Apologies as this is no doubt a noob question. Does the running config live accross both partitions ?  or does the upgrade process save and install the current running configuration/state of the controller  into the new partition whilst also upgrading the firmware.

Thanks for any advise in advance :)

Cheers
Luke