After analyzing the information and sympton, we can see that the load balancing is causing the problem:
When there is no eth-trunk the frames which belong to a certain flow can arrive its destination in the correct order because there is only one physical connection between both devices. If we use multiple physical links in eth-trunk, the frames can arrive its destination in an incorrect order.
The reason is that the frames are transmitted through different links. If the first frame is transmitted over one link and the second frame over the other link, the second frame may arrive its destination before the first one
TO avoid disorder in the frames, we can use a mechanism of paquet forwarding to guarantee the correct order of the frames which belong to a certain data flow. This mechanism clasifies the frames based on MAC address or IP address. The frames which belong to the same data flow are transmitted over only one physical link.
After changing the load balance mode from load balance per paquet to load balance per flow, the problem is solved, we can see the KPI image, the value goes to 0 after the change: