Why do we see "TTL expired in transit" while trying to ping an IP assigned on a Red Hat Enterprise Linux host?

Solution Unverified - Updated -

Issue

  • We observed that Virtual IPs are taking longer time to resolve whenever we reboot the server or restart the cluster.
  • I get the below ping results when I try to ping the virtual host/ IPs after restarting the node:
>ping 1.1.1.2
Pinging 1.1.1.2 with 32 bytes of data:
Reply from 1.1.1.2: TTL expired in transit.
Reply from 1.1.1.2: TTL expired in transit.
Reply from 1.1.1.2: TTL expired in transit.
Reply from 1.1.1.2: TTL expired in transit.

>ping 1.1.1.3
Pinging 1.1.1.3 with 32 bytes of data:
Reply from 1.1.1.3: TTL expired in transit.
Reply from 1.1.1.3: TTL expired in transit.
Reply from 1.1.1.3: TTL expired in transit.
Reply from 1.1.1.3: TTL expired in transit.
  • What does these messages indicate?

Environment

  • Red Hat Enterprise Linux (RHEL).

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content