12-29-2011 12:28 AM - edited 03-07-2019 04:05 AM
What gives...does this indicate a duplicate IP somewhere? I just replaced a managed switch who IP should not be present and wasnt when I pinged it before adding new switch:
* I44-01:20 # ping 10.73.112.69
Ping(ICMP) 10.73.112.69: 4 packets, 8 data bytes, interval= 1.
16 bytes from 10.73.112.69: icmp_seq=0 ttl=30 time=70291.8 ms
16 bytes from 10.73.112.69: icmp_seq=1 ttl=30 time=69401.8 ms
16 bytes from 10.73.112.69: icmp_seq=2 ttl=30 time=68421.8 ms
16 bytes from 10.73.112.69: icmp_seq=3 ttl=30 time=67421.8 ms
16 bytes from 10.73.112.69: icmp_seq=0 ttl=30 time=150 ms (DUP!)
16 bytes from 10.73.112.69: icmp_seq=1 ttl=30 time=70 ms (DUP!)
16 bytes from 10.73.112.69: icmp_seq=2 ttl=30 time=0 ms
16 bytes from 10.73.112.69: icmp_seq=3 ttl=30 time=0 ms
--- 10.73.112.69 ping statistics ---
4 packets transmitted, 6 packets received, +2 duplicates, -- somebody's printing up packets!
round-trip min/avg/max = 0/34469.6/70291.8 ms
Its basically a fiber connection out gig interface into a another fiber gig interface.
Thanks
Solved! Go to Solution.
01-02-2012 03:29 PM
CiscoKidInVegas wrote:
What gives...does this indicate a duplicate IP somewhere? I just replaced a managed switch who IP should not be present and wasnt when I pinged it before adding new switch:
* I44-01:20 # ping 10.73.112.69
Ping(ICMP) 10.73.112.69: 4 packets, 8 data bytes, interval= 1.
16 bytes from 10.73.112.69: icmp_seq=0 ttl=30 time=70291.8 ms
16 bytes from 10.73.112.69: icmp_seq=1 ttl=30 time=69401.8 ms
16 bytes from 10.73.112.69: icmp_seq=2 ttl=30 time=68421.8 ms
16 bytes from 10.73.112.69: icmp_seq=3 ttl=30 time=67421.8 ms
16 bytes from 10.73.112.69: icmp_seq=0 ttl=30 time=150 ms (DUP!)
16 bytes from 10.73.112.69: icmp_seq=1 ttl=30 time=70 ms (DUP!)
16 bytes from 10.73.112.69: icmp_seq=2 ttl=30 time=0 ms
16 bytes from 10.73.112.69: icmp_seq=3 ttl=30 time=0 ms--- 10.73.112.69 ping statistics ---
4 packets transmitted, 6 packets received, +2 duplicates, -- somebody's printing up packets!
round-trip min/avg/max = 0/34469.6/70291.8 msIts basically a fiber connection out gig interface into a another fiber gig interface.
Thanks
Those PING RTT's in the first 4 packets indicate that there is a device *somewhere* on your network (it may be outside the boundaries of your "default gateway" which is replying to that IP address - 70000 ms (7 seconds!) RTT times indicate it's a long way away, network-wise, too!
Unplug/power down your new switch and do a traceroute - see where the packet goes and see if it matches what you expect of your local network.
Cheers.
01-02-2012 03:29 PM
CiscoKidInVegas wrote:
What gives...does this indicate a duplicate IP somewhere? I just replaced a managed switch who IP should not be present and wasnt when I pinged it before adding new switch:
* I44-01:20 # ping 10.73.112.69
Ping(ICMP) 10.73.112.69: 4 packets, 8 data bytes, interval= 1.
16 bytes from 10.73.112.69: icmp_seq=0 ttl=30 time=70291.8 ms
16 bytes from 10.73.112.69: icmp_seq=1 ttl=30 time=69401.8 ms
16 bytes from 10.73.112.69: icmp_seq=2 ttl=30 time=68421.8 ms
16 bytes from 10.73.112.69: icmp_seq=3 ttl=30 time=67421.8 ms
16 bytes from 10.73.112.69: icmp_seq=0 ttl=30 time=150 ms (DUP!)
16 bytes from 10.73.112.69: icmp_seq=1 ttl=30 time=70 ms (DUP!)
16 bytes from 10.73.112.69: icmp_seq=2 ttl=30 time=0 ms
16 bytes from 10.73.112.69: icmp_seq=3 ttl=30 time=0 ms--- 10.73.112.69 ping statistics ---
4 packets transmitted, 6 packets received, +2 duplicates, -- somebody's printing up packets!
round-trip min/avg/max = 0/34469.6/70291.8 msIts basically a fiber connection out gig interface into a another fiber gig interface.
Thanks
Those PING RTT's in the first 4 packets indicate that there is a device *somewhere* on your network (it may be outside the boundaries of your "default gateway" which is replying to that IP address - 70000 ms (7 seconds!) RTT times indicate it's a long way away, network-wise, too!
Unplug/power down your new switch and do a traceroute - see where the packet goes and see if it matches what you expect of your local network.
Cheers.
01-08-2012 07:07 AM
Thank you for your resonse, it makes total sense. But...before I install a new managed switch I ping the IP of the range thats available, to see if its responds, it did not....but maybe in the interm of me pinging to when the switch was actually intsalled another device came up with the same IP ( very doubtful, but possible ). Any other possible reason of this do you think? Sigh, the fun this is
Thanks again
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide