Question

Time to live exceeded for some IPs on switch


Hello! We have a problem with two switchs.

So, we have a switch (IP 172.16.35.254) extreme x440 that is a gateway and in a port 20 of this switch we have a proxy server (IP 172.16.32.51) and in another port 48 we have other switch extreme x440 (IP 172.16.35.211). When I try to ping the proxy server on gateway switch, I received this:
SW-DataCenter.24 # ping 172.16.32.51
Ping(ICMP) 172.16.32.51: 4 packets, 8 data bytes, interval 1 second(s).
44 bytes from 172.16.35.254: icmp_seq=0 Redirect Host
44 bytes from 172.16.35.254: icmp_seq=0 Redirect Host
44 bytes from 172.16.35.254: icmp_seq=0 Time to live exceeded
44 bytes from 172.16.35.254: icmp_seq=1 Redirect Host
44 bytes from 172.16.35.254: icmp_seq=1 Time to live exceeded
44 bytes from 172.16.35.254: icmp_seq=2 Redirect Host
44 bytes from 172.16.35.254: icmp_seq=2 Time to live exceeded
44 bytes from 172.16.35.254: icmp_seq=3 Redirect Host
44 bytes from 172.16.35.254: icmp_seq=3 Time to live exceeded

And, when I run a traceroute I have this:
SW-DataCenter.25 # traceroute 172.16.32.51
traceroute to 172.16.32.51, 30 hops max
1 172.16.35.211 2 ms 2 ms 5 ms
2 172.16.35.254 2 ms 3 ms 1 ms
3 172.16.35.211 1 ms 2 ms 7 ms
4 172.16.35.254 1 ms 2 ms 14 ms
5 *
5 172.16.35.211 11 ms *
6 172.16.35.254 1 ms 2 ms 1 ms
7 172.16.35.211 13 ms * 4 ms
8 172.16.35.254 4 ms 14 ms 1 ms
9 172.16.35.211 5 ms * 13 ms
10 172.16.35.254 12 ms 19 ms 1 ms
11 *
11 172.16.35.211 13 ms *
12 172.16.35.254 6 ms 2 ms 1 ms
13 172.16.35.211 11 ms 10 ms *
14 172.16.35.254 2 ms 4 ms 5 ms
15 172.16.35.211 4 ms * 3 ms
16 172.16.35.254 2 ms 10 ms 2 ms
17 172.16.35.211 14 ms * 7 ms
18 172.16.35.254 3 ms 3 ms 14 ms
19 *
19 172.16.35.211 1 ms *
20 172.16.35.254 1 ms 12 ms 26 ms
21 172.16.35.211 8 ms 19 ms *
22 172.16.35.254 1 ms 11 ms 23 ms
23 172.16.35.211 5 ms * 20 ms
24 172.16.35.254 4 ms 2 ms 11 ms
25 *
25 172.16.35.211 14 ms 3 ms
26 172.16.35.254 7 ms 8 ms 17 ms
27 *
27 172.16.35.211 15 ms *
28 172.16.35.254 6 ms 21 ms 1 ms
29 172.16.35.211 5 ms * 4 ms
30 172.16.35.254 5 ms 5 ms 15 ms

What is happening? Someone can help to solve this?

Thanks!!!

7 replies

Hi,

Not sure if you have ready the following, but this could be your issue.

https://community.extremenetworks.com/extreme/topics/time_to_live_exceeded

Ian
Ian Worms wrote:

Hi,

Not sure if you have ready the following, but this could be your issue.

https://community.extremenetworks.com/extreme/topics/time_to_live_exceeded

Ian

No, it is not. I saw this topic, but my problem is different...
Userlevel 6
Hello Andrei

Do both 440s have ipforwarding turned on for that segment? Can you do a show IPR and past the information of both switches here?

It looks like they are pointing to each other or to another router that has a route to each of them allowing for them to just pass the packet back and forth.

The redirect is when one router knows that there is a second router with that route and redirects it to that second router.

Thanks

P
Paul Russo wrote:

Hello Andrei

Do both 440s have ipforwarding turned on for that segment? Can you do a show IPR and past the information of both switches here?

It looks like they are pointing to each other or to another router that has a route to each of them allowing for them to just pass the packet back and forth.

The redirect is when one router knows that there is a second router with that route and redirects it to that second router.

Thanks

P

take a look:

switch 172.16.35.254:
SW-DataCenter.2 # show ipr
Ori Destination Gateway Mtr Flags VLAN Duration
#s Default Route 172.16.32.2 1 UG---S-um--f- Servidores 0d:6h:9m:34s
#s 10.1.0.0/21 172.16.35.211 1 UG---S-um--f- Gerenciamento 1d:1h:42m:46s
#s 10.50.0.0/25 172.16.35.211 1 UG---S-um--f- Gerenciamento 1d:1h:42m:46s
#s 10.250.250.0/24 172.16.35.211 1 UG---S-um--f- Gerenciamento 1d:1h:42m:46s
#s 172.16.0.0/22 172.16.35.211 1 UG---S-um--f- Gerenciamento 1d:1h:42m:46s
#d 172.16.32.0/24 172.16.32.254 1 U------um--f- Servidores 1d:1h:42m:48s
#s 172.16.32.51/32 172.16.35.211 1 UG---S-um--f- Gerenciamento 1d:1h:42m:46s
#d 172.16.33.0/24 172.16.33.254 1 U------um--f- BlocoA-D 1d:1h:42m:48s
#d 172.16.34.0/24 172.16.34.254 1 U------um--f- BlocoH 1d:1h:42m:48s
#d 172.16.35.0/24 172.16.35.254 1 U------um--f- Gerenciamento 1d:1h:42m:48s
#d 172.16.36.0/24 172.16.36.254 1 U------um--f- BlocoG 1d:1h:42m:48s
#d 172.16.37.0/24 172.16.37.254 1 U------um--f- BlocoB 1d:1h:42m:48s
#d 172.16.38.0/24 172.16.38.254 1 U------um--f- lab-energia 1d:1h:42m:48s
#d 172.16.39.0/24 172.16.39.254 1 U------um--f- CENAFLOR 1d:1h:42m:48s
#d 172.16.40.0/25 172.16.40.126 1 U------um--f- wireless 1d:1h:42m:48s
#d 172.16.40.128/25 172.16.40.254 1 U------um--f- treinamento 1d:1h:42m:48s
#d 172.16.41.0/24 172.16.41.254 1 U------um--f- w-celular 1d:1h:42m:49s
#d 172.16.42.0/24 172.16.42.254 1 U------um--f- visitante 1d:1h:42m:49s
#s 172.17.0.0/16 172.16.35.211 1 UG---S-um--f- Gerenciamento 1d:1h:42m:47s
#s 172.18.0.0/16 172.16.35.211 1 UG---S-um--f- Gerenciamento 1d:1h:42m:47s
#s 172.19.0.0/21 172.16.35.211 1 UG---S-um--f- Gerenciamento 1d:1h:42m:47s
d 192.168.100.0/29 192.168.100.1 1 -------um---- Firewall 1d:1h:42m:49s
#d 192.168.130.0/24 192.168.130.1 1 U------um--f- Storage 1d:1h:42m:49s
#s 192.168.255.0/30 172.16.35.211 1 UG---S-um--f- Gerenciamento 1d:1h:42m:47s
#s 200.130.19.17/32 172.16.35.211 1 UG---S-um--f- Gerenciamento 1d:1h:42m:47s
#s 200.130.19.24/32 172.16.35.211 1 UG---S-um--f- Gerenciamento 1d:1h:42m:47s
#s 200.130.19.26/32 172.16.35.211 1 UG---S-um--f- Gerenciamento 1d:1h:42m:47s

Origin(Ori): (b) BlackHole, (be) EBGP, (bg) BGP, (bi) IBGP, (bo) BOOTP,
(ct) CBT, (d) Direct, (df) DownIF, (dv) DVMRP, (e1) ISISL1Ext,
(e2) ISISL2Ext, (h) Hardcoded, (i) ICMP, (i1) ISISL1 (i2) ISISL2,
(is) ISIS, (mb) MBGP, (mbe) MBGPExt, (mbi) MBGPInter, (mp) MPLS Lsp,
(mo) MOSPF (o) OSPF, (o1) OSPFExt1, (o2) OSPFExt2,
(oa) OSPFIntra, (oe) OSPFAsExt, (or) OSPFInter, (pd) PIM-DM, (ps) PIM-SM,
(r) RIP, (ra) RtAdvrt, (s) Static, (sv) SLB_VIP, (un) UnKnown,
(*) Preferred unicast route (@) Preferred multicast route,
(#) Preferred unicast and multicast route.

Flags: (b) BFD protection requested, (B) BlackHole, (c) Compressed, (D) Dynamic,
(f) Provided to FIB, (G) Gateway, (H) Host Route, (l) Calculated LDP LSP,
(L) Matching LDP LSP, (m) Multicast, (p) BFD protection active, (P) LPM-routing,
(R) Modified, (s) Static LSP, (S) Static, (t) Calculated RSVP-TE LSP,
(T) Matching RSVP-TE LSP, (u) Unicast, (U) Up, (3) L3VPN Route.

MPLS Label: (S) Bottom of Label Stack
Mask distribution:
1 default routes 2 routes at length 16
2 routes at length 21 1 routes at length 22
12 routes at length 24 3 routes at length 25
1 routes at length 29 1 routes at length 30
4 routes at length 32

Route Origin distribution:
14 routes from Direct 13 routes from Static

Total number of routes = 27
Total number of compressed routes = 0

-----------------------------------------------------------------------
Switch 172.16.35.211:

Slot-1 SW-SFB-BlocoG.1 # show ipr
Ori Destination Gateway Mtr Flags VLAN Duration
#s Default Route 192.168.255.1 1 UG---S-um--f- MMA 3d:5h:57m:42s
#s 172.16.32.0/20 172.16.35.254 1 UG---S-um--f- Gerenciamento 1d:5h:19m:37s
#d 172.16.35.0/24 172.16.35.211 1 U------um--f- Gerenciamento 3d:5h:57m:44s
#d 192.168.255.0/30 192.168.255.2 1 U------um--f- MMA 3d:5h:57m:44s

Origin(Ori): (b) BlackHole, (be) EBGP, (bg) BGP, (bi) IBGP, (bo) BOOTP,
(ct) CBT, (d) Direct, (df) DownIF, (dv) DVMRP, (e1) ISISL1Ext,
(e2) ISISL2Ext, (h) Hardcoded, (i) ICMP, (i1) ISISL1 (i2) ISISL2,
(is) ISIS, (mb) MBGP, (mbe) MBGPExt, (mbi) MBGPInter, (mp) MPLS Lsp,
(mo) MOSPF (o) OSPF, (o1) OSPFExt1, (o2) OSPFExt2,
(oa) OSPFIntra, (oe) OSPFAsExt, (or) OSPFInter, (pd) PIM-DM, (ps) PIM-SM,
(r) RIP, (ra) RtAdvrt, (s) Static, (sv) SLB_VIP, (un) UnKnown,
(*) Preferred unicast route (@) Preferred multicast route,
(#) Preferred unicast and multicast route.

Flags: (b) BFD protection requested, (B) BlackHole, (c) Compressed, (D) Dynamic,
(f) Provided to FIB, (G) Gateway, (H) Host Route, (l) Calculated LDP LSP,
(L) Matching LDP LSP, (m) Multicast, (p) BFD protection active, (P) LPM-routing,
(R) Modified, (s) Static LSP, (S) Static, (t) Calculated RSVP-TE LSP,
(T) Matching RSVP-TE LSP, (u) Unicast, (U) Up, (3) L3VPN Route.

MPLS Label: (S) Bottom of Label Stack
Mask distribution:
1 default routes 1 routes at length 20
1 routes at length 24 1 routes at length 30

Route Origin distribution:
2 routes from Direct 2 routes from Static

Total number of routes = 4
Total number of compressed routes = 0
-----------------------------
Do you know what I need to do?

Thank you!!
Userlevel 6
Hey Andrei

Here's your issue. On switch one you have the a direct route for the 32 subnet but you also have a static entry pointing it to switch 2

#d 172.16.32.0/24 172.16.32.254 1 U------um--f- Servidores 1d:1h:42m:48s
#s 172.16.32.51/32 172.16.35.211 1 UG---S-um--f- Gerenciamento 1d:1h:42m:46s

on switch 2 you have a static entry that says if you need to go to 32.x to send it to switch one
#s 172.16.32.0/20 172.16.35.254 1 UG---S-um--f- Gerenciamento 1d:5h:19m:37s

I would get rid of the static entry on the first switch and try it since it has a direct interface on that segment

Let me know if that helps

Thanks
P
Paul Russo wrote:

Hey Andrei

Here's your issue. On switch one you have the a direct route for the 32 subnet but you also have a static entry pointing it to switch 2

#d 172.16.32.0/24 172.16.32.254 1 U------um--f- Servidores 1d:1h:42m:48s
#s 172.16.32.51/32 172.16.35.211 1 UG---S-um--f- Gerenciamento 1d:1h:42m:46s

on switch 2 you have a static entry that says if you need to go to 32.x to send it to switch one
#s 172.16.32.0/20 172.16.35.254 1 UG---S-um--f- Gerenciamento 1d:5h:19m:37s

I would get rid of the static entry on the first switch and try it since it has a direct interface on that segment

Let me know if that helps

Thanks
P

Oh my god!!! I didn't see this... I was testing some routes, and forgot to delete.... But, I'm have this problems with others IPs and I only can solve when I reboot my switch... Now, because I rebooted, i don't have this problem, but sometimes this problem shows up...
Have you some idea?

Thank for the help!!!
Userlevel 6
Paul Russo wrote:

Hey Andrei

Here's your issue. On switch one you have the a direct route for the 32 subnet but you also have a static entry pointing it to switch 2

#d 172.16.32.0/24 172.16.32.254 1 U------um--f- Servidores 1d:1h:42m:48s
#s 172.16.32.51/32 172.16.35.211 1 UG---S-um--f- Gerenciamento 1d:1h:42m:46s

on switch 2 you have a static entry that says if you need to go to 32.x to send it to switch one
#s 172.16.32.0/20 172.16.35.254 1 UG---S-um--f- Gerenciamento 1d:5h:19m:37s

I would get rid of the static entry on the first switch and try it since it has a direct interface on that segment

Let me know if that helps

Thanks
P

In regards to the other switches it is hard to say doing the show IPR ihelps to track it. Rebooting just changes the route table so hard to say what it is doing as everything gets cleared

P

Reply