Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

routing with source issue

Hi wise ones.

I have a routing issue. I am attempting to setup a monitoring tool on the monitoring PC(192.80.175.139)

but the PC is unable to see the interface(72.19.255.41)

When i attempted a trace route, it stops at this router(192.80.175.136)

And here's the funny part

gateway#trace 72.19.255.41

Type escape sequence to abort.

Tracing the route to 72.19.255.41

  1 192.80.162.6 0 msec 0 msec 0 msec

  2 10.10.20.10 [MPLS: Label 45 Exp 0] 4 msec 0 msec 4 msec

  3 10.10.20.130 0 msec *  0 msec

sttpgw4#trace 72.19.255.41 so 192.80.175.136

Type escape sequence to abort.

Tracing the route to 72.19.255.41

  1  *  *  *

  2  *  *  *

And the monitoring PC is as such

NMS-R#trace 172.19.255.241

Type escape sequence to abort.

Tracing the route to 172.19.255.241

  1 202.80.175.136 0 msec 0 msec 0 msec

  2  *  *  *

What is the issue here? The interface, 72.19.255.41 is able to trace all the way to the monitoring PC

router2#trace 202.80.175.4

Type escape sequence to abort.

Tracing the route to 202.80.175.4

  1 10.10.20.129 180 msec 200 msec 0 msec

  2 10.10.30.1 0 msec 4 msec 4 msec

  3 10.10.10.9 0 msec 0 msec 4 msec

  4 192.80.162.5 0 msec 0 msec 4 msec

  5 192.80.175.139 4 msec 4 msec 0 msec

4 REPLIES
Purple

routing with source issue

Hi,

can you post your topology diagram please.

Regards.

Alain

Don't forget to rate helpful posts.
New Member

routing with source issue

192.80.175.139 -> 192.80.162.5 -> 192.80.162.6 -> 10.10.20.10 -> 10.10.20.130 / 72.19.255.41 -> 72.19.255.42

routing with source issue

Sharin,

When you traced back to the monitoring PC, you used ip: 202.80.175.4. Is this the NATed ip for

192.80.175.139 or its another interface of the same PC?

Another point I would like to make is: you need to trace Monitoring PC using the source as 72.19.255.41, because by default it will use WAN interface as the source ip.

And based on the Trace outputs towards 72.19.255.41, it seems that the MPLS cloud is not aware of this 192.80.175.139 subnet/ip. Are you running BGP or any other routing protocol with the MPLS provider? And have you advertised your LAN in the cloud?

Hope it helps.

Neeraj

New Member

routing with source issue

202.80.175.4 is the public IP, which is directly connected to 192.80.175.139. ergo, you need to pass through 192.80.175.139 before hitting 202.80.175.4

yes, tried tracing from 72.19.255.241 all the way to 202.80.175.4. it works. only it doesn't work as mentioned above.

yes, the 192.80.175.139 is on a different network, connected between 192.80.162.5 -> 192.80.162.6

297
Views
0
Helpful
4
Replies