Ethernet (BaseT) down: poll driven or event driven?
when detaching a cable from a BaseT port there is a certain delay before the "interface down" message shows up in the log . Does this explain with the fact that according to IEEE standards the "interface down" status for BaseT interfaces is poll driven instead of event driven (like, for example, for fiber GigEth ports) ?
If so, what is the polling interval on Cisco switches?
Re: Ethernet (BaseT) down: poll driven or event driven?
thank you for your answer, my question though was a little different, I'll try to make myself clearer . Let's say the event is "I missed some keepalives in a row" and this happens at T0: Is the "interface down" message displayed at T0 (event driven) or do we have to wait for a polling process to check the status of all the interfaces and declare the interface down (poll driven)? In this case the "interface down" message would be displayed at T0+the time needed for the polling process to verify the interface status.
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...