Telemetry connection between FortiClient and FortiOS updates
In 6.2.2, if EMS does not send a Telemetry gateway list to FortiClient, FortiClient does not display options related to FortiGate Telemetry. FortiClient also does not automatically attempt connection to the default gateway when all gateway IP addresses from EMS are not available or reachable.
If the administrator configured the FortiClient installer with an on-premise EMS IP address or FortiClient Cloud invitation code, FortiClient automatically connects to either EMS after installation. Otherwise, FortiClient does not automatically connect to any device. The end user must provide an on-premise EMS IP address or FortiClient Cloud invitation code to connect FortiClient to.
The EMS administrator can still create a Telemetry gateway list that includes FortiGate IP addresses. If FortiClient receives the list, it autoconnects to one of the configured FortiGate IP addresses by going through the list, starting with the default gateway, if present. If the EMS administrator removes the Telemetry gateway list, FortiClient disconnects from the FortiGate and remains connected to EMS. If FortiClient is disconnected from EMS, it remains disconnected and does not attempt connection to any device.
The following shows FortiClient when it is first installed and has not connected to EMS. Providing a FortiGate IP address in the EMS IP or Join FortiClient Cloud field fails to establish a connection.
The following shows FortiClient when it is managed by EMS and connected to a FortiGate. FortiClient has established a connection to the FortiGate using a Telemetry gateway list that EMS has sent to FortiClient via an endpoint policy.
When all FortiGate IP addresses in the received Telemetry gateway list are not reachable or available, FortiClient displays a Not reachable status. In this case, FortiClient does not automatically connect to the default gateway.
