topic SmartMove - Fortigate issue in SmartMove

SmartMove - Fortigate issue

pwillekens — Fri, 11 Sep 2020 11:50:08 GMT

Does anyone had a similar issue

Re: SmartMove - Fortigate issue

Ofir_Shikolski — Sun, 13 Sep 2020 05:51:19 GMT

Are you using VDOM ? in case yes , you will need to export it per domain and not global

Which Fortinet version it is ?

Please send the 5 first lines in the configure file , example:

#config-version=FOSVM1-5.6.1-FW-build1484-170727:opmode=0:vdom=1:user=admin
#conf_file_ver=97710506006743
#buildno=1484
#global_vdom=0:vd_name=root/root
config system interface

Re: SmartMove - Fortigate issue

pwillekens — Mon, 14 Sep 2020 13:04:07 GMT

#config-version=FG200E-6.2.2-FW-build1010-191008:opmode=0:vdom=0:user=AD Admins
#conf_file_ver=31506110564135435
#buildno=1010
#global_vdom=1
config system global

Re: SmartMove - Fortigate issue

Ofir_Shikolski — Tue, 15 Sep 2020 11:49:40 GMT

issue was:

incorrect fqdn format.

we expect to get FQDN with the below format :

next
edit "login.microsoft.com"
set uuid b4184474-3dbf-51ea-c227-d5ffa3efefe1
set type fqdn
set fqdn "login.microsoft.com"

We got:

edit "login.microsoft.com"
set uuid b4184474-3dbf-51ea-c227-d5ffa3efefe1
set type fqdn

This caused to expected isuse .

There are 2 solutions :

1. fix it on froti side and export again

2. fix it on the export file