We have two switches connected back to back SW-A and SW-B.
SW-B is connected to other upstream switches. When the uplink to upstream switch flaps in SW-B, im seeing the below logs in SW-A and the link between SW-A and SW-B also flaps. The link is automatically put into ERR DISABLE in SW-A because of the reason LoopBack.
When searched in Cisco, it says SW-A receives the same keep alive packet it sent on the same port and it is putting into ERRDISABLE. The link will automatically come after the ERR DISABLE recovery period or we need to manually shut/no shut the link.
I would like to know the possible causes of "loopback error" . There is no problem in Layer 1 apart from link flap. Will link flap will cause the loopback error.
Note: Link between SW-A and SW-B is not running any STP or VTP. It's just a open trunk port. But Uplink of SW-B connected to upstream switches are running MSTP.
there was another thread about this issue some days ago.
It looks like that in some platforms with some IOS releases for a known and solved bug the coming back of interface keepalives is misunderstood as a sign of a loop and not as a sign of an healthy link and the port is placed in errordisabled.
This problem is not related to STP or STP loop guard.
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...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...