You ask a question about why something is the way that it is. And fundamentally the answer to why is that it is the way that Cisco designed it to function.
We could talk about the merits of actually putting the ping on the wire versus just responding directly without ever putting the request on the wire. I happen to believe that it was a good design decision and that it demonstrates that the link is really working. Usually we ping something because we want to know if it is working. If IOS just directly generated a response without checking the circuit we could have a situation where ping succeeds but the link can not transmit data. I like the idea that if I ping the serial interface and get responses then I know for sure that the circuit is working.
Hi Rick, just to add, pinging on a serial interface does also points out any subnetting issue if there is any on the link, i ran through such a problem in a lab when there was a slight subnet difference between two interfaces, link was up but pinging to self ip wasnt successful so i think i also helps to narrow the problems regarding any subnet issue as well.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...