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

Traceroute from a 3560 in a switched environment acts weird

HarryBrown9000
Level 1
Level 1

So, I have a mixed vendor network with a bunch of 3560s as my core, and a different vendor for the remote locations.

When I attempt to ping one of the objects at a remote location it works as expected, however traceroute produces the following result.  There is connectivity so I'm trying to understand why it works this way.

(I already checked the other posts about ping, and yes I know it works over UDP, and there's no firewalls in place here, so I struck out early googling)

Is there a different tool besides traceroute that works in a switched environment?

Output from results:

Main#ping 10.1.15.195 (Random hardware)

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.1.15.195, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/8 ms

Main#trace 10.1.15.195

Type escape sequence to abort.

Tracing the route to 10.1.15.195

  1  *  *  *

  2  *  *  *

  3  *  *  *

  4  *  *  *

  5  *  *  *

  6  *  *  *

  7  *  *  *

  8  *  *  *

  9  *  *  *

10  *  *  *

11  *  *  *

12  *  *  *

13  *  *  *

14  *  *  *

15  *  *  *

16  *  *  *

17  *  *  *

18  *  *  *

19  *  *  *

20  *  *  *

21  *  *  *

22  *  *  *

23  *  *  *

24  *  *  *

25  *  *  *

26  *  *  *

27  *  *  *

28  *  *  *

29  *  *  *

30  *  *  *

3 Replies 3

Hello

it is possible that traceroute replies have been denied for this host/network

You can enable a debug between hosts to verify this

Access- list 100 permit Icmp host x.x.x.x host y.y.y.y
Access-list 100 permit Icmp host y.y.y.y host x.x.x.x

Debug ip packets 100

traceroute 10.1.15.195

Res
Paul


Sent from Cisco Technical Support iPad App


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

anisaini
Level 1
Level 1

To begin with,Go on each hop begining to the immediately connected device to which packets are being forarded and perform debugs or ACL on input interface to see if you see hits. if yes then the packets are hitting it.

whether it switch or router generally the trace packets are process sitched as it has the ttl1, means the packet termintes on the device itslef hence it will be process switched.

generally you do not see traceoute hops if you are having some firewall or "no icmp reachable" on the interfaces downstream

reply if it helps

I think this answers my question.

The unit in question is apaprently directly connected and hence the packet would terminate on the cisco itself.

Review Cisco Networking products for a $25 gift card