Why is a legacy database file autogenerated when a controller is upgraded to ArubaOS 3.4.x.x?

Aruba Employee
Aruba Employee

Product and Software: This article applies to all Aruba controllers and ArubaOS versions.

Whenever any controller is upgrade to ArubaOS 3.4.x.x, an autogenerated database file is created in the flash. The file name is "legacy_db.udb".

Issue the 'dir' command to verify.

The generation of this file is very important. If you want to revert to the old code after you upgrade ArubaOS to 3.4.x.x, the internal-db will be not be compatible with the code.

Even if you revert to the old code, you must manually import the internal-db file, which was autogenerated after an upgrade. Hence, the name "legacy_db.udb" is relevant.

The database file is generated because the user storage encryption algorithm between ArubaOS 3.3 or earlier and 3.4.x.x is different.

Version history
Revision #:
1 of 1
Last update:
‎07-05-2014 03:12 AM
Updated by:
Labels (1)
Search Airheads
Showing results for 
Search instead for 
Did you mean: