Traceroute latency values for traffic hitting 4506 SupIV SVI's
We have noticed in that icmp echo-replies and traceroutes that hit the real ip (rip) of the SVI on our 4506 supervisor have unusually high response times, but traces and pings through the switch respond with normal/expected latency values.
It is my understanding that the Supervisor IV engine places a lower value on processing packets to an svi than it does through the svi, but I need some documentation confirming this to appease our delvelopers, or any other solutions that may eliminate this delay.
Re: Traceroute latency values for traffic hitting 4506 SupIV SVI
The design of the switch processes is such a way that "ICMP" gets low priority when compared with other proceses. So ping to the switch itself is not a good idea. Unfortunately there is no document that backs this. There are lot of threads on internet which talk about this, you can find a good explanation on this previous post.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...