Technical Note: How to migrate a FortiGate / FortiWiFi 30D configuration to a 30E model

[serge_FTNT]

Description

Migrating a FortiGate or FortiWiFi 30D configuration to a '30E' model.

Since Low–end models FGT-30D and FWF-30D do not support virtual domains (VDOM's) their interfaces (physical, loopback, WiFi) and the admin account does not belong to any VDOM.

Theses parameters have to be linked to a VDOM before restoring the configuration into a 30E model.

Scope

FortiGate configuration migration.

Solution

Modify the original FortiGate/FortiWiFi 30D configuration before restoring it into the 30E model.

The following example gives the FWF-30D settings to modify before restoring to a FWF-30E running 5.4.4.

1) Replace the FWF-30D header line:

#config-version=FWF30D-5.04-FW-build1117-170209:opmode=0:vdom=0:user=admin

by the following for the FWF-30E:

#config-version=FWF30E-5.04-FW-build1117-170209:opmode=0:vdom=0:user=admin

2) Add VDOM to the admin account:

        config system admin
        edit "admin"
        set vdom "root"

3) Add VDOM to the Virtual Access Point interfaces:

        config wireless-controller vap
        edit "wifi"
        set vdom root 
        next

4) Add VDOM to the system interfaces (physicals, loopbacks, tunnels , VAP’s, etc):

        config system interface
        edit "wan"
        set vdom root
        set type physical 
        next
        edit "Loopbk"
        st vdom root
        set type loopback
        next
        edit "wifi"
        set vdom "root"
        set type vap-switch
        next
        edit "ssl.root"
        set vdom "root"
        set type tunnel
        next