There is an enhancement added in the 21.2.1 release in which the LEF connection will go in force to suspend the state if we only have the LTE link as a single WAN link to reach the controller to avoid overutilization on LTE.
In this case, only high priority data will be sent towards analytics i.e. alarm logs. All low and medium priority data will get dropped when the LEF connection is in a force suspend state.
admin@Branch-01-cli> show orgs org-services Org1 lef collectors LEF-Collector-log_collector1 status
VSN SOURCE SOURCE DESTINATION DESTINATION ROUTING PENDING LAST
ID IP PORT IP PORT INSTANCE STATUS MSGS FLAPS FLAPPED
--------------------------------------------------------------------------------------------------------
15 10.0.0.4 1025 10.0.0.0 1234 Org1-Control-VR Force-Suspend 0 0 1w0d20h
Above would be an expected behavior when we have LTE as the only transport to reach the Controllers.
If we need to fix this then we can change the circuit-media type to ethernet or any for LTE interface using below command. e.g showing below CLI option.
admin@Branch-2-cli(config)% set system sd-wan site wan-interfaces vni-0/100.0 circuit-media ?
Description: WAN access circuit media
Possible completions:
DSL LTE T1 T3 any cable ethernet
admin@Branch-2-cli(config)% commit