I'm trying to find a possible cause for momentary loss of trunking on a Gig Interface. There's no apparent Layer 1 loss and the other end of the connection doesn't experience any impact to it's trunking. Here's the log entry.
Apr 8 15:25:13.413 EST: %DTP-5-NONTRUNKPORTON: Port Gi0/12 has become non-trunk
Apr 8 15:25:13.564 EST: %DTP-5-TRUNKPORTON: Port Gi0/12 has become dot1q trunk
...if you do care to keep trunk negotiation on and the utilization looks normal, you can try checking for line errors and collisions on the trunk ports on both ends of the trunk. Such errors can be caused by a degraded connection (bad hardware) or a duplex mismatch. The duplex mismatch will speciifically cause collisions.
Just a quick note...if you do determine that the speed and duplex settings are mismatched, just set both ends to auto-negotiate. Auto-negotiation sometimes causes a problem, depending on the manufacturer of the hardware and the default behavior of the hardware and drivers, but auto-negotiation for the gigebitethernet standard is pretty robust and defaults to 1000/full on all Catalyst switches anyway.
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...