On any of my 2501's or 2502's, I activate "debug cdp adjacency" or "debug cdp events" shortly after booting up. I see no debug output when a new cdp neighbor comes online; neither before nor after that neighbor appears in the sh cdp neighbors command.
Also I can do a debug ip ospf events and it will notify me of every single hello packet going out. I don't consider a hello packet to be an "event." An "event" is like a Zeppelin concert or something of that magnitude.
Isn't there a way to keep something as mundane as hello traffic out of the debug output?
And, is there something wrong with the cdp facilities on these routers that they don't announce new adjacencies when they are asked to?
So, you're telling me it's possible for EXEC to accept the "debug cdp adj" or "debug cdp events" commands without issuing any error messages, even if those debug facilities are in fact not supported on the router?
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...