Packet loss between a Cisco switch C3560 and Linux server running on CentOs

I am working in a network environnement where I have some Cisco Switch WS-C3560X-48 and Linux Servers running CentOS 7.7.

The linux servers are connected 3 times on my switches : one admin link, one production link and one ILO link because they are running on HP hardware.

When I try to ping the servers on the admin LAN from my Cisco switch, I get the following result :

SWTCisco#ping 10.x.x.x repeat 25

Type escape sequence to abort.
Sending 25, 100-byte ICMP Echos to 10.x.x.x, timeout is 2 seconds:
!!!!!!.!!!!!!.!!!!!!.!!!!
Success rate is 88 percent (22/25), round-trip min/avg/max = 1/1/8 ms

As you can see, I have a pattern, I always lose a packet on the 7th ping. On server side, I can see with tcpdump that the icmp request is received but the icmp reply is not sent. On the exemple below, I pingued 8 times the server and we can see 2 request following each other.

root@CentOSserver:/etc/sysconfig/network-scripts# tcpdump -i eno1 host 10.x.x.X -nn
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eno1, link-type EN10MB (Ethernet), capture size 262144 bytes
11:37:04.770292 IP SwitchCisco > LinuxServer: ICMP echo request, id 134, seq 0, length 80
11:37:04.770354 IP LinuxServer > SwitchCisco: ICMP echo reply, id 134, seq 0, length 80
11:37:04.772624 IP SwitchCisco > LinuxServer: ICMP echo request, id 134, seq 1, length 80
11:37:04.772644 IP LinuxServer > SwitchCisco: ICMP echo reply, id 134, seq 1, length 80
11:37:04.774394 IP SwitchCisco > LinuxServer: ICMP echo request, id 134, seq 2, length 80
11:37:04.774411 IP LinuxServer > SwitchCisco: ICMP echo reply, id 134, seq 2, length 80
11:37:04.776592 IP SwitchCisco > LinuxServer: ICMP echo request, id 134, seq 3, length 80
11:37:04.776606 IP LinuxServer > SwitchCisco: ICMP echo reply, id 134, seq 3, length 80
11:37:04.789083 IP SwitchCisco > LinuxServer: ICMP echo request, id 134, seq 4, length 80
11:37:04.789099 IP LinuxServer > SwitchCisco: ICMP echo reply, id 134, seq 4, length 80
11:37:04.791466 IP SwitchCisco > LinuxServer: ICMP echo request, id 134, seq 5, length 80
11:37:04.791483 IP LinuxServer > SwitchCisco: ICMP echo reply, id 134, seq 5, length 80
11:37:04.793669 IP SwitchCisco > LinuxServer: ICMP echo request, id 134, seq 6, length 80
11:37:04.822159 ARP, Request who-has SwitchCisco tell 10.123.213.144, length 46
11:37:06.793024 IP SwitchCisco > LinuxServer: ICMP echo request, id 134, seq 7, length 80
11:37:06.793068 IP LinuxServer > SwitchCisco: ICMP echo reply, id 134, seq 7, length 80

I reproduce the issue when I try to ping the production LAN.
I reproduce the issue when I try to ping from another Cisco 3560 so it’s not an hardware issue.
I reproduce the issue on another CentOS 6.10 server.
I do not reproduce the issue when I try to ping the ILO.
I do not reproduce the issue when I try to ping a Windows server in the same network.
I do not reproduce the issue when I try to ping the Linux server from a HP or Aruba switch.
Also, there is no dropped/lost/error packet on the switch port or on the linux server port.
The link is barely used so no congestion

The only difference I see between Cisco and HP/Aruba switch is that HP/Aruba switch have a natural interval between each ping. They will wait for 1 sec before sending a new ping request, even if they have received the reply of the previous one. Cisco switch will send new icmp-request as soon as they receive the reply of the previous one, resulting in an important rate of pings.

To me, the problem is on the Linux server side. I checked if there was some ICMP burst limitations on iptables but there is no such things. To be 100% sure, I temporarily disabled iptables but the problem was still there.

So, I don’t know how to explain this. It does not have an impact on my services but I would like to find an explanation on this one.

I am not very good with Linux so I may be missing something here. Any help would be appreciated.