TTL expires in transit -- How to solve this Pls Help urgently...

Dipesh Patel · ‎10-30-2009

Dear Experts,

I have found :

C:\Documents and Settings\Deepeshp>tracert -d 1

Tracing route to 172.20.34.2 over a maximum of

1 7 ms <1 ms <1 ms 150.0.148.2

2 <1 ms <1 ms <1 ms 150.0.150.100

3 <1 ms <1 ms <1 ms 172.20.34.2

4 <1 ms <1 ms <1 ms 150.0.150.100

5 <1 ms <1 ms <1 ms 172.20.34.2

6 <1 ms <1 ms <1 ms 150.0.150.100

7 <1 ms <1 ms <1 ms 172.20.34.2

8 <1 ms <1 ms <1 ms 150.0.150.100

9 <1 ms <1 ms <1 ms 172.20.34.2

10 <1 ms <1 ms <1 ms 150.0.150.100

11 1 ms <1 ms <1 ms 172.20.34.2

12 <1 ms <1 ms <1 ms 150.0.150.100

13 1 ms 1 ms 1 ms 172.20.34.2

14 <1 ms <1 ms <1 ms 150.0.150.100

15 1 ms 1 ms 1 ms 172.20.34.2

16 <1 ms <1 ms <1 ms 150.0.150.100

17 1 ms 1 ms 1 ms 172.20.34.2

18 <1 ms <1 ms <1 ms 150.0.150.100

19 1 ms 1 ms 1 ms 172.20.34.2

20 1 ms <1 ms <1 ms 150.0.150.100

21 1 ms 1 ms 1 ms 172.20.34.2

22 1 ms 1 ms 1 ms 150.0.150.100

23 1 ms 1 ms 1 ms 172.20.34.2

.

Here Backbone switch has : Ip route 172.20.34.0 255.255.255.0 150.0.150.107

and Dist l3 SW :

IP route is :

0.0.0.0 0.0.0.0 150.0.150.100

and inter vlan routing is done by IP RIP enable .

Pls help what's the prob.

Dipesh P.

Peter Paluch · ‎10-31-2009

Hello Dipesh,

What exactly is the machine 172.20.34.2? Is it a router or a PC? According to your tracert output posted here, the machine 172.20.34.2 actually receives the packet addressed to it but it decides to send it to its default gateway which in turn resends the packet back to it. If the tracert output is correct (i.e. no addresses have been changed while posting it here) then this seems to be a seriously wrong routing or TCP/IP settings on the 172.20.34.2 machine.

If it is a Windows, I can imagine that something/somebody has tampered with its routing table settings - this could be verified by looking into the route print output on that machine. However, if that is a different device, I am at loss what could force it to route away packet that is destined to the machine itself.

Best regards,

Peter

Dipesh Patel · ‎10-31-2009

Dear Peter,

It is Le Switch and IP address is for mgmt vlan.

Dipesh P

Peter Paluch · ‎10-31-2009

Hello Dipesh,

Is it possible for you to post the configuration of that switch here? There seems to be something strange going on.

Best regards,

Peter

Peter Paluch · ‎10-31-2009

Dipesh,

One more thing. This traceroute stuff is one thing. However, are you able to ping the switch or telnet/ssh into it from the same machine you are now doing traceroute from?

Best regards,

Peter

Dipesh Patel · ‎10-31-2009

Dear Peter,

It is nortel switch.

And If I ping this IP than I will get reply from 150.0.150.11 TTL expires in transit.

.

One more thing I can not Ping this IP from the switch where this vlan is created. but I can ping other Vlan created on this sw.

This sw is L3 sw.

Dipesh P.

Peter Paluch · ‎11-01-2009

Hello Dipesh,

Let me ask you: is it possible to ping or traceroute successfully to any other IP address within the IP network where the 172.20.34.2 belongs? If you can ping, for example, the 172.20.34.3 or any other address in that IP subnet then you will have determined that the routing works properly. Of course, that IP be alive. Then, it will be only a matter of configuration on that Nortel switch.

This seems to me as if the switch was not aware that this IP address is his IP - as if the interface was not activated or was not declared as management interface - I am just guessing now. I don't have experiences with Nortel switches.

Try pinging some other IP in that network if possible.

Best regards,

Peter

Dipesh Patel · ‎11-01-2009

Dear,

This IP 172.20.34.2 is the Mgmt Gateway. I m going to assign mgmt Ips to all switch and all access switches have this IP ( 172.20.34.2) is as a Default gateway.

Yes You are right I can not ping this IP from which SW it is connected.

I m also new on Nortel SW.

I had worked only on Cisco SW.

Dipesh P.