cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
244
Views
0
Helpful
3
Replies

Traceroute problem

csco12083784
Beginner
Beginner

While doing traceroute to 8.8.8.8 from inside device( cisco Nexus switch). I got very suspicious output.

CORE.SW# traceroute 8.8.8.8


traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 40 byte packets
 1  8.8.8.8 (8.8.8.8)  3.018 ms  2.205 ms  2.318 ms
 2  8.8.8.8 (8.8.8.8)  4.936 ms  2.284 ms  2.468 ms
 3  8.8.8.8 (8.8.8.8)  2.462 ms  6.406 ms  8.497 ms
 4  8.8.8.8 (8.8.8.8)  9.12 ms  8.511 ms  8.915 ms
 5  8.8.8.8 (8.8.8.8)  8.913 ms  9.797 ms  7.852 ms
 6  8.8.8.8 (8.8.8.8)  8.914 ms  8.731 ms  9.278 ms
 7  8.8.8.8 (8.8.8.8)  8.52 ms  8.726 ms  12.84 ms
 8  8.8.8.8 (8.8.8.8)  9.03 ms  10.675 ms  9.312 ms
 9  8.8.8.8 (8.8.8.8)  10.129 ms  9.11 ms  12.599 ms

Network Diagram

NX-Switch --- Cisco ASA --- Loadbalancer --- Internet

can any one give some update on this.

3 Replies 3

Zach S
Beginner
Beginner

Here's a post of a similar problem/situation: https://supportforums.cisco.com/discussion/11880981/tracert-same-ip-multiple-hops

paul driver
VIP Expert VIP Expert
VIP Expert

Hello

Not sure why this is - however I am aware by default traceroute performs dns resolution and this can be negated 2 ways

no ip domian-lookup
or
traceroute x.x.x.x numeric

res

Paul


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

Hi  paul,

The command traceroute x.x.x.x numeric is fine for ASA,but in Nexus same suspicious output.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers