Technical Note: Migrating a FortiGate or FortiWiFi 30D configuration to a 30E model

[serge_FTNT]

Description

This article discusses migrating a FortiGate or FortiWiFi 30D to a 30E model.

Since Low–end models FG-30D and FWF-30D do not support virtual domains (VDOM) their interfaces (physical, loopback, WiFi) and admin account do not belong to any VDOM.  They have to be linked to a VDOM before restoring the configuration into a 30E model.

Scope

FG-30D, FWF-30D,  FG-30E, FWF-30E

Solution

Modify the original 30D configuration before restore into the 30E model.

The example below shows the FWF-30D settings to modify before restoring to a FWF-30E running 5.4.4

1) Replace the 30D header line

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

by the following for the 30E

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

2) Add vdom to admin account

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

3) Add vdom to Virtual Access Point interfaces

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

4) Add vdom to system interfaces (physicals, loopbacks, tunnels , vap’s,…)

config system interface
edit "wan"
set vdom root
set type physical
 next
edit "Loopbk"
set 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