| Solution |
From v7.2.4 and v7.4.1, a unified function to check the priority of geographic coordinate update has been implemented, in which the priorities are:
- Priority 0, (highest), gui/json: set by the user on FortiManager.
This data is set on purpose, and should not be overridden.
- Priority 1, config(unset): set by user on FortiGate.
gui-device-latitude and gui-device-longitude in FortiGate 'config system global' would be used. If those values are valid (even as '0.0'), the location_from would be 'config', if it is an unset command, the location_from would be 'unset', while the original data would be kept.
- Priority 2, gps_lte: GPS data by JSON status response of LTE modem.
- Priority 3, gps_fext; GPS data by JSON status response of FortiExtender.
- Priority 4, diag; by FortiGate CLI: diagnose system waninfo; If location_from is empty, or 'unset', the location data of this diagnose command would be used, with location_from set to be 'diag'.
Example of coordinates in FortiGate configuration:
config system global
set alias "FortiGate-80F"
set gui-device-latitude "52.070498"
set gui-device-longitude "4.3007"
set hostname "CDR1-CUST2-SPOKE02-04"
The following are FortiManager CLI commands to get a list of geographic coordinates stored in the device database, clear geographic coordinates in the device database, and update geographic coordinates in the device database from FortiGate:
diagnose dvm device coordinate list <device id|name>
diagnose dvm device coordinate clear <device id|name>
diagnose dvm device coordinate update <device id|name>
Notes:
- Using the 'Refresh Device' from GUI (which runs command /dvm/cmd/update/dev-list) will not trigger the process of 'diag sys waninfo', while /dvm/cmd/update/device will. Users can run /dvm/cmd/update/device by 'Retrieve' device, or run the diagnose coordinate update command mentioned above.
- Geographic coordinates are updated from the Retrieve config action, and also via the CLI command 'diagnose dvm device coordinate update'. That means please retrieve the config and then check the coordinates and if still not updated then use the CLI command to diagnose DVM device coordinate update.
|
