[caiu] Perda de comunicação ASN 28588 via ATM PTT-SP

Braian pbraian em tcheturbo.com.br
Qui Jul 20 15:13:00 BRT 2017


Aqui também estamos com bastante perda via ATM para esse destino.

ping 187.16.222.204
   SEQ HOST                                     SIZE TTL TIME STATUS
     0 187.16.222.204                             56 255 31ms
     1 187.16.222.204                             56 255 15ms
     2 187.16.222.204                             56 255 16ms
     3 187.16.222.204                             56 255 15ms
     4 187.16.222.204                             56 255 15ms
     5 187.16.222.204                             56 255 15ms
     6 187.16.222.204                             56 255 15ms
     7 187.16.222.204                             56 255 15ms
     8 187.16.222.204                             56 255 15ms
     9 187.16.222.204                             56 255 15ms
    10 187.16.222.204                             56 255 15ms
    11 187.16.222.204                             56 255 15ms
    12 187.16.222.204                             56 255 15ms
    13 187.16.222.204                             56 255 17ms
    14 187.16.222.204                             56 255 17ms
    15 187.16.222.204 timeout
    16 187.16.222.204 timeout
    17 187.16.222.204 timeout
    18 187.16.222.204 timeout
    19 187.16.222.204                             56 255 17ms
     sent=20 received=16 packet-loss=20% min-rtt=15ms avg-rtt=16ms 
max-rtt=31ms
   SEQ HOST                                     SIZE TTL TIME STATUS
    20 187.16.222.204                             56 255 42ms
    21 187.16.222.204                             56 255 196ms
    22 187.16.222.204                             56 255 196ms
    23 187.16.222.204                             56 255 15ms


Em 20/07/2017 09:42, Rodrigo Gavioli escreveu:
> Bom dia,
>
> Mais alguém enfrentando perda de comunicação via ATM.
>
>   PING 187.16.222.204: 56  data bytes, press CTRL_C to break
>     Reply from 187.16.222.204: bytes=56 Sequence=1 ttl=255 time=1 ms
>     Reply from 187.16.222.204: bytes=56 Sequence=2 ttl=255 time=1 ms
>     Reply from 187.16.222.204: bytes=56 Sequence=3 ttl=255 time=16 ms
>     Reply from 187.16.222.204: bytes=56 Sequence=4 ttl=255 time=186 ms
>     Request time out
>     Request time out
>     Request time out
>     Reply from 187.16.222.204: bytes=56 Sequence=8 ttl=255 time=197 ms
>     Reply from 187.16.222.204: bytes=56 Sequence=9 ttl=255 time=147 ms
>     Request time out
>     Reply from 187.16.222.204: bytes=56 Sequence=11 ttl=255 time=2 ms
>     Reply from 187.16.222.204: bytes=56 Sequence=12 ttl=255 time=1 ms
>     Reply from 187.16.222.204: bytes=56 Sequence=13 ttl=255 time=2 ms
>     Reply from 187.16.222.204: bytes=56 Sequence=14 ttl=255 time=1 ms
>     Reply from 187.16.222.204: bytes=56 Sequence=15 ttl=255 time=1 ms
>     Reply from 187.16.222.204: bytes=56 Sequence=16 ttl=255 time=2 ms
>     Reply from 187.16.222.204: bytes=56 Sequence=17 ttl=255 time=1 ms
>     Reply from 187.16.222.204: bytes=56 Sequence=18 ttl=255 time=1 ms
>
>   --- 187.16.222.204 ping statistics ---
>     18 packet(s) transmitted
>     14 packet(s) received
>     22.22% packet loss
>     round-trip min/avg/max = 1/39/197 ms
>
>



Mais detalhes sobre a lista de discussão caiu