Yes. Atleast one link on each router has connectivity issue with directly connected interface. So, i wanted to rule out one link and from that i can figur out other.
root@R4# run ping 172.27.0.17 source 172.27.0.18 rapid PING 172.27.0.17 (172.27.0.17): 56 data bytes ..... --- 172.27.0.17 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss [edit] root@R4# run ping 172.27.0.22 source 172.27.0.21 rapid PING 172.27.0.22 (172.27.0.22): 56 data bytes ..... --- 172.27.0.22 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss [edit] root@R4# run ping 172.27.0.10 source 172.27.0.9 rapid PING 172.27.0.10 (172.27.0.10): 56 data bytes !!!!! --- 172.27.0.10 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/stddev = 79.976/139.008/160.430/30.386 ms root@R2> ping 172.27.0.1 source 172.27.0.2 rapid PING 172.27.0.1 (172.27.0.1): 56 data bytes ..... --- 172.27.0.1 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss
Similar behaviour on R1 :
root@R1> ping 172.27.0.9 source 172.27.0.10 rapid PING 172.27.0.9 (172.27.0.9): 56 data bytes !!!!! --- 172.27.0.9 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/stddev = 37.564/69.413/78.672/15.942 ms root@R1> ping 172.27.0.2 source 172.27.0.1 rapid PING 172.27.0.2 (172.27.0.2): 56 data bytes ..... --- 172.27.0.2 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss root@R1> ping 172.27.0.13 source 172.27.0.14 rapid PING 172.27.0.13 (172.27.0.13): 56 data bytes !!!!! --- 172.27.0.13 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/stddev = 1.318/1.542/1.814/0.202 ms
I'm not sure if i can run packet capture on Junosphere. I never did traffic capture on Junosphere and not sure how can i do that.