Triggers for Loopback - ErrDisable

Unanswered Question
Sep 28th, 2008

Hi All,

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.

Thanks in advance.


Arun Kumar

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
arun kumar Mon, 09/29/2008 - 00:50

Hi Andrew,

Yes we disabled STP by configuring "bpdu-filter enable". There is no other link between swa and swb.


Arun Kumar


bpdu-filter enable stops the switch from "listening" for STP BPDU's.

Does not stop the switch from "Sending" BPDU's for STP.

Did you configure BPDU on both ends of the link between swa & swb?

Also why does the connection between them need to be a trunk port, just change it to a switch port?

Why do you not want to run spanning tree on swa?

Giuseppe Larosa Mon, 09/29/2008 - 11:39

Hello Arun,

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.

I make a search...


the bug id is:

Cisco bug ID CSCea46385

Hope to help



This Discussion