Troubleshooting EIGRP Neighbor Adjacency

Hello Ajmal

Depending on what you want to examine, you should choose your debug commands accordingly. First of all, make sure that you have terminal monitor configured so that all debug output will appear on the command line. You can do this by simply issuing the following command:

R2#terminal monitor

Next, the debug ip packet command will monitor packets that are processed by the router’s routing engine, and not those processed by fast switching. If the router is fast switching, or using CEF, no output will appear. If you want to see packets routed using CEF, then use the following command:

R2#debug ip cef

Remember that all of these commands will output information for each and every packet that is being routed, so don’t use these on a production network. If you must, then use access lists that will match the traffic you are interested in and debug only those. You can see how to do this in the following Cisco documentation:

Now if you want to debug only EIGRP packets, then you will have to choose your debug commands accordingly. A useful list of commands for troubleshooting EIGRP can be found at this Cisco documentation.

I hope this has been helpful!

Laz

1 Like