Eu tenho um servidor com cinco outros dispositivos conectados a um único switch. Eu posso pingar todos os dispositivos com bons tempos de ping baixo (entre 0,6ms e 0,9ms). Mas, de repente, o tempo de ping para um dos dispositivos aumenta significativamente (entre 20 a 80ms). Também vemos um comportamento anormal do dispositivo consistente com uma conectividade ruim (é uma câmera especializada) quando a taxa de ping se deteriora.
Desconectar o dispositivo do switch e conectá-lo novamente reduz o tempo de ping para 0,9 ms 'normal'. Depois de um tempo, ele pula de novo.
Não podemos identificar nenhum evento externo coincidente com o início do aumento dos tempos de ping.
Todos os cabos são estruturais cat6.
Ele 'cheira' como algum tipo de interferência elétrica, mas é estranho que funcione bem por um tempo, então vai mal, mas volta ao normal quando o cabo é desconectado e reconectado.
Qualquer ideia será muito bem vinda. Obrigado!
(Esta é a minha primeira pergunta aqui, então peça desculpas antecipadamente por qualquer novidade na pergunta)
Exemplo de saída de arping abaixo:
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.952ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.951ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.955ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.941ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.952ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.952ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.951ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.951ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.941ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.984ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.950ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.952ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.952ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.951ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.952ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.942ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.953ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.953ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.942ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.946ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.927ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.942ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 0.957ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 11.573ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 35.059ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 21.710ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 21.187ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 19.604ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 17.873ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 36.197ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 29.025ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 28.685ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 24.288ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 28.241ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 21.027ms
Unicast reply from 192.168.1.85 [00:40:7F:40:22:50] 21.241ms