 |
 |
Observing same issues here pinging same route severs from any source netblock in AS16842. -Tk > On Oct 5, 2015, at 4:10 PM, James Stahr <[log in to unmask]> wrote: > > The exchange *seems* fine, but I can't reliably ping the route servers right now. My BGP sessions to them are up and stable, but ICMP isn't operating "normally" - has anything changed? This started at 15:24 CDT today: > > [stahr@ctg-bastion ~]$ ping -c 10 206.108.255.1 > PING 206.108.255.1 (206.108.255.1) 56(84) bytes of data. > 64 bytes from 206.108.255.1: icmp_seq=7 ttl=59 time=7.06 ms > > --- 206.108.255.1 ping statistics --- > 10 packets transmitted, 1 received, 90% packet loss, time 9000ms > rtt min/avg/max/mdev = 7.062/7.062/7.062/0.000 ms > [stahr@ctg-bastion ~]$ ping -c 10 206.108.255.2 > PING 206.108.255.2 (206.108.255.2) 56(84) bytes of data. > 64 bytes from 206.108.255.2: icmp_seq=2 ttl=59 time=7.13 ms > 64 bytes from 206.108.255.2: icmp_seq=6 ttl=59 time=6.98 ms > 64 bytes from 206.108.255.2: icmp_seq=7 ttl=59 time=6.94 ms > 64 bytes from 206.108.255.2: icmp_seq=10 ttl=59 time=7.05 ms > > --- 206.108.255.2 ping statistics --- > 10 packets transmitted, 4 received, 60% packet loss, time 9001ms > rtt min/avg/max/mdev = 6.942/7.028/7.135/0.093 ms > [stahr@ctg-bastion ~]$ ping -c 10 206.108.255.52 > PING 206.108.255.52 (206.108.255.52) 56(84) bytes of data. > 64 bytes from 206.108.255.52: icmp_seq=1 ttl=61 time=14.0 ms > 64 bytes from 206.108.255.52: icmp_seq=2 ttl=61 time=14.5 ms > 64 bytes from 206.108.255.52: icmp_seq=3 ttl=61 time=14.0 ms > 64 bytes from 206.108.255.52: icmp_seq=4 ttl=61 time=13.6 ms > 64 bytes from 206.108.255.52: icmp_seq=5 ttl=61 time=13.0 ms > 64 bytes from 206.108.255.52: icmp_seq=6 ttl=61 time=12.7 ms > 64 bytes from 206.108.255.52: icmp_seq=7 ttl=61 time=12.2 ms > 64 bytes from 206.108.255.52: icmp_seq=8 ttl=61 time=11.7 ms > 64 bytes from 206.108.255.52: icmp_seq=9 ttl=61 time=11.2 ms > 64 bytes from 206.108.255.52: icmp_seq=10 ttl=61 time=11.9 ms > > --- 206.108.255.52 ping statistics --- > 10 packets transmitted, 10 received, 0% packet loss, time 9002ms > rtt min/avg/max/mdev = 11.289/12.913/14.502/1.052 ms > [stahr@ctg-bastion ~]$ > > > Any new policing policy applied today? I seem to be able to ping normally if I use my 206.108.255.x address, but not reliably from any other address: > > r-pop-min-1#ping 206.108.255.1 repeat 100 source gig0/0/5 > Type escape sequence to abort. > Sending 100, 100-byte ICMP Echos to 206.108.255.1, timeout is 2 seconds: > Packet sent with a source address of 206.108.255.26 > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > Success rate is 100 percent (100/100), round-trip min/avg/max = 1/1/1 ms > r-pop-min-1#ping 206.108.255.2 repeat 100 source gig0/0/5 > Type escape sequence to abort. > Sending 100, 100-byte ICMP Echos to 206.108.255.2, timeout is 2 seconds: > Packet sent with a source address of 206.108.255.26 > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > Success rate is 100 percent (100/100), round-trip min/avg/max = 1/1/1 ms > r-pop-min-1#ping 206.108.255.1 repeat 100 source loop1 > Type escape sequence to abort. > Sending 100, 100-byte ICMP Echos to 206.108.255.1, timeout is 2 seconds: > Packet sent with a source address of 205.173.182.62 > ...!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > Success rate is 97 percent (97/100), round-trip min/avg/max = 1/1/1 ms > r-pop-min-1#ping 206.108.255.2 repeat 100 source loop1 > Type escape sequence to abort. > Sending 100, 100-byte ICMP Echos to 206.108.255.2, timeout is 2 seconds: > Packet sent with a source address of 205.173.182.62 > ...!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > Success rate is 97 percent (97/100), round-trip min/avg/max = 1/1/2 ms > r-pop-min-1# > > > -James