Fortigate 600D without Serial-Number

[billwong]

i got a Fortigate 600D, the FortiOS is unable to identify the unit's Serial-Number.... the get system status showing as below -- FortiGate-600D # get system status Version: FortiGate-600D v5.6.0,build1449,170330 (GA) Virus-DB: 1.00123(2015-12-11 13:18) Extended DB: 1.00000(2012-10-17 15:46) Extreme DB: 1.00000(2012-10-17 15:47) IPS-DB: 6.00741(2015-12-01 02:30) IPS-ETDB: 6.00741(2015-12-01 02:30) APP-DB: 6.00741(2015-12-01 02:30) INDUSTRIAL-DB: 6.00741(2015-12-01 02:30) Serial-Number: IPS Malicious URL Database: 1.00001(2015-01-01 01:01) Botnet DB: 1.00000(2012-05-28 22:51) BIOS version: 05000003 Log hard disk: Available Hostname: FortiGate-600D Operation Mode: Transparent Current virtual domain: root Max number of virtual domains: 10 Virtual domains status: 0 in NAT mode, 1 in TP mode Virtual domain configuration: disable FIPS-CC mode: disable Current HA mode: standalone Branch point: 1449 Release Version Information: GA FortiOS x86-64: Yes System time: Mon Jun 29 14:11:20 2093 -- the FortiOS running fine, the hardware running fine, it operate well with all functions.. but the Web GUI is not working... it looks if the FortiOS is unable to identify the unit SN, then the web GUI is unable to load... below the the crashlog --- FortiGate-600D # diagnose debug crashlog read 1: 2093-06-25 10:35:54 the killed daemon is /bin/httpsd: status=0x100 2: 2093-06-25 10:35:56 the killed daemon is /bin/httpsd: status=0x100 3: 2093-06-25 10:35:59 the killed daemon is /bin/httpsd: status=0x100 4: 2093-06-25 10:36:02 the killed daemon is /bin/httpsd: status=0x100 5: 2093-06-25 10:36:05 the killed daemon is /bin/httpsd: status=0x100 6: 2093-06-25 10:36:08 the killed daemon is /bin/httpsd: status=0x100 7: 2093-06-25 10:36:11 the killed daemon is /bin/httpsd: status=0x100 8: 2093-06-25 10:36:14 the killed daemon is /bin/httpsd: status=0x100 9: 2093-06-25 10:36:17 the killed daemon is /bin/httpsd: status=0x100 10: 2093-06-25 10:36:20 the killed daemon is /bin/httpsd: status=0x100 11: 2093-06-25 10:36:23 the killed daemon is /bin/httpsd: status=0x100 12: 2093-06-25 10:36:26 the killed daemon is /bin/httpsd: status=0x100 13: 2093-06-25 10:36:29 the killed daemon is /bin/httpsd: status=0x100 14: 2093-06-25 10:36:32 the killed daemon is /bin/httpsd: status=0x100 15: 2093-06-25 10:36:35 the killed daemon is /bin/httpsd: status=0x100 16: 2093-06-25 10:36:38 the killed daemon is /bin/httpsd: status=0x100 17: 2093-06-25 10:36:41 the killed daemon is /bin/httpsd: status=0x100 18: 2093-06-25 10:36:44 the killed daemon is /bin/httpsd: status=0x100 19: 2093-06-25 10:36:47 the killed daemon is /bin/httpsd: status=0x100 20: 2093-06-25 10:36:50 the killed daemon is /bin/httpsd: status=0x100 21: 2093-06-25 10:36:53 the killed daemon is /bin/httpsd: status=0x100 ============== any idea how i can fix it? either make the web GUI working or how i can manually assign the Serial Number into the FortiOS system, (i have the SN# sticker on the box)

[emnoc]

Downgrade to 5.4 does that show the serial#? Your running 5.6 so I expect issues, contact  FTNT-support and open a case

[billwong]

hi emnoc,

running with 5.4.x got the same. any possible solution to get it fix eg. assign the SN# which i got from machine label? or so...

as i don't have a valid contract, so it's unable to create a fortigate support case.

[Fullmoon]

billwong wrote:

as i don't have a valid contract, so it's unable to create a fortigate support case.

you may contact your local reseller or if you have other Fortigate unit with active subscriptions you can use that to raise ticket.