In environments which do not have NTP server, we usually prefer Fortigate to announce time to related interfaces. However, I recently bumped into an interesting problem.
With this fortigate, time is set manually and it has never been connected to the internet. When ntp server to specific, directly connected, vlans is enabled. Even if it seems to be working none of the clients could reach out and grab time from fortigate time server.
I could not find any related info at the knowledgebase and documentation. Is there anybody who has experienced such a problem?
FYI: Fortigate should be kept offline and connection to the internet even for a brief second is not possible.
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
From the configuration command is stated that : "server-mode" Enable/disable FortiGate NTP Server Mode. Your FortiGate becomes an NTP server for other devices on your network. The FortiGate relays NTP requests to its configured NTP server.
So practically if your haven't configured a NTP server it doesn't have a destination to relay the requests on.
In my opinion this limitation has to do with NTP stratum and the local time is considered stratum 16 and the NTP server can't offer a valid time to the clients.
You can check the debug commands if they give a more detailed explanation:
diag debug application ntpd -1
diag debug enable
or
diagnose sys ntp status
In my experience, if you have any other network devices, some of them support lowering the stratum of hardware clock (for ex. 4) and present it as a valid NTP server. There are hardware NTP appliances that get the time from GPS or if you have any servers you can create a NTP server that is feed by the hypervisor/hw clock
From the configuration command is stated that : "server-mode" Enable/disable FortiGate NTP Server Mode. Your FortiGate becomes an NTP server for other devices on your network. The FortiGate relays NTP requests to its configured NTP server.
So practically if your haven't configured a NTP server it doesn't have a destination to relay the requests on.
In my opinion this limitation has to do with NTP stratum and the local time is considered stratum 16 and the NTP server can't offer a valid time to the clients.
You can check the debug commands if they give a more detailed explanation:
diag debug application ntpd -1
diag debug enable
or
diagnose sys ntp status
Hello Emirjon,
Thank you for this is enlightening explanation.
Unfortunately, my problem stands. Is there any way to hack fw to provide time to network?
In my experience, if you have any other network devices, some of them support lowering the stratum of hardware clock (for ex. 4) and present it as a valid NTP server. There are hardware NTP appliances that get the time from GPS or if you have any servers you can create a NTP server that is feed by the hypervisor/hw clock
Unfortunately (or not), there is no "hack" to make a FGT be time server.
The reason has been mentioned earlier, the FGT's clock is not precise enough - for NTP standards ("stratum 16").
One possible solution would be to integrate a time source into your network, like a clock device connected via USB or LAN, which the FGT may use as a time source.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1663 | |
1077 | |
752 | |
446 | |
220 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.