ADOM downgrade

Hi Simon, (as in previous times, thank you for taking time to respond),

scao_FTNT wrote:

but why you need "downgrade"? want to keep the old ADOM db config? you can just leave the old ADOM there and create a new 5.0 ADOM?

What will be the advantage of keeping the old ADOM? AFAIK, I cannot copy the ADOM database between ADOMs, so, I'd still need to import the devices into the new ADOM and at least for one of the devices, I'd need to imports its configuration in order to populate the ADOM - correct?

R's, Alex

scao_FTNT wrote:

for now, we only support ADOM version upgrade, which is based on FOS upgrade logic to convert old version config to new version config, we also support 5.0 ADOM package config install to 5.2 FGT, using same upgrade logic for the convert, but no support for downgrade case.

 

and for your case, you need to create 5.0 ADOM, add 5.0 device and do the import, to import 5.0 device config to ADOM db for its policy package

In my case, I have an existing 5.2 device, which I have previously used with a 5.2 ADOM. Now, I need to add a a new 5.0 device.

I created a new 5.0 ADOM and added both devices (VDOMs, actually, which were automatically removed from the 5.2 ADOM!)

The 5.0 ADOM has empty Policy Package and I wanted to import Policies from the 5.2 (since it's populated from 5.2 ADOM I previously had the device in), but I got "Cannot run import because device's firmware version is different than ADOM version."

So, it seems that I cannot import Policies from 5.2 device into a 5.0 ADOM (but I can install Policies Package from 5.0 ADOM to 5.2 device) correct?