Well if this is in a lab where you cannot break anything then your best bet to see stuff happening is to use your debug commands and you can see almost everything going with the eigrp process . You have to be very careful with debug commands in a live network as this can bury a cpu if used incorrectly but in a lab situation with little traffic it would be a good way to really see what is going on . There is a lot of info that will come across the screen but it is no worse that going thru screens of sniffer captures.
thanks for your advice, debug would be a backup method to use, since the output is not as readable (and manoeverable) as wireshark sniffings. OK, you can get used to it, but in direct comparison I noticed my students are faster getting the concepts when using a GUI based analyzer.
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...