|
As of 22.1b, FortiCloud has recently introduced a new feature where the server automatically pushes geolocation data to FortiGate. This feature prevents issues where users may have been unable to push the data to FortiGate for any reason after modifying the geolocation on FortiCloud, such as in cases where the tunnel was down or the push failed. Now, when the tunnel is re-established, the server will automatically push geolocation information down to FortiGate.
Run the following commands to confirm that this log is the expected behavior:
sh full-configuration | grep gui-device-latitude
dia sys waninf
Example log output:
date=2023-08-01 time=10:24:57 eventtime=1690864798286264442 tz="+0545" logid="0100044546" type="event" subtype="system" level="information" vd="root" logdesc="Attribute configured" user="FortiGateCloud" ui="fgfm_tunnel" action="Edit" cfgtid=693370880 cfgpath="system.global" cfgattr="gui-device-latitude[->27.717250]gui-device-longitude[->85.323960]" msg="Edit system.global " utmref=0:1690864798
Example output of the command:
sh full-configuration | grep gui-device-latitude
set gui-device-latitude "27.717250"
dia sys waninfo
Public/WAN IP: <<REDACTED.>>
Location:
Latitude: 27.717251
Longitude: 85.323959
<<Rest of command redacted.>>
As seen above, the output of the command matches both latitudes as well as longitudes. This confirms that it was an update pushed from FortiCloud.
|
