DEVNET.

GRE Tunnel IP Facing Latency But Destination Address Doesn’t

According to the customer, when he pings the GRE tunnel ip address a latency of 300-400ms is receiving but the latency of destination address of tunnel is 40ms. Really such a weird issue and ping outputs are phenomenal. During the analysis, we find backbone is having two equal cost path and destination based packet forwarding is configured. After running show ip cef exact route , we find that the packet forwading is occuring from the second path which is very less utilize and ist path is fully choked. But not able to check the same results with GRE ip address. There after, per packet based forwarding is configured and problem completely vanishes.
Does anyone know how to check the cef exact route for GRE tunnel address?

Share:

Share on facebook
Facebook
Share on twitter
Twitter
Share on linkedin
LinkedIn

Leave a Reply

Your email address will not be published. Required fields are marked *

Become a member

Full Access to 739 Lessons. New Lessons Added Every Week!

Awesome Deal! Get 2 Months for FREE!

No Obligations. Cancel At Any Time!