I'm trying to troubleshoot some weird issues going on with our network and have been using MTR in part to try and see what's going on. I'm running MTR from my desktop to a server in the data center. My PC to the SVI on the Core router, then a fiber P2P interface to the DC Router, to the server within. MTR initially looks fine:
My traceroute [vUNKNOWN] my.pc (my.ip) 2018-12-22T11:51:03-0500 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. (SVI) 0.0% 75 0.7 2.9 0.4 47.9 8.2 2. (DC P2P Int) 0.0% 74 0.5 2.2 0.4 89.0 10.5 3. (server) 0.0% 74 0.7 0.5 0.4 0.7 0.1
After a few more tries, the server shows up again just after the SVI:
My traceroute [vUNKNOWN] my.pc (my.ip) 2018-12-22T11:52:02-0500 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. (SVI) 0.0% 132 0.4 4.6 0.4 86.9 12.7 (server) 2. (DC P2P Int) 0.0% 132 0.5 3.5 0.4 89.0 11.9 3. (server) 0.0% 132 0.5 0.5 0.4 0.7 0.1
And after a bit more, it shows up once more, after the P2P link again:
my.pc (my.ip) 2018-12-22T11:53:28-0500 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. (SVI) 0.0% 217 0.6 6.4 0.4 192.1 20.8 (server) 2. (DC P2P Int) 0.0% 217 3.5 5.6 0.4 252.1 25.3 (server) 3. (server) 0.0% 217 0.6 0.5 0.4 0.7 0.1
It seems to be happening completely at random. There don't seem to be any OSPF updates between the Core and DC Router. It does the same thing doing a TCP MTR instead of ICMP.
Any thoughts or input are appreciated. I'm likely going to contact TAC soon to get additional help, but I wanted to see what everyone here thought as well.
No comments:
Post a Comment