Packet Path Troubleshoot
PREVIEW — for evaluation, not the live site

Troubleshoot › Error Decoder › %ETHCNTR-3-LOOP_BACK_DETECTED

Decoder

What does %ETHCNTR-3-LOOP_BACK_DETECTED mean?

Loop-back detected: the switch heard its own voice come back

%ETHCNTR-3-LOOP_BACK_DETECTED: Loop-back detected on GigabitEthernet1/0/10. The port is forced to stay in errdisable state.
In plain English: The switch sends itself small keepalive frames on every port.

Platform: Cisco IOS / IOS XE. Values shown are the documented defaults — confirm them on your platform with the check commands below.

What it means

The switch sends itself small keepalive frames on every port. On this port, a keepalive came back — the wire leaving the port loops back into the same switch, or the far device is reflecting frames. The switch shuts the port because a loop like that, left open, copies traffic endlessly and can drown the whole LAN in a broadcast storm within seconds.

Likely causes, in order

Check, in order

  1. show interfaces status err-disabledConfirm the port and the loopback reason, and whether a second port shows the same — loops usually involve two ports.
  2. show mac address-table vlan 10One MAC address appearing on two ports, or moving rapidly between them, is the loop's footprint in the table.
  3. Physically trace the cableThis fault lives in the physical world: follow the patch lead at both ends before changing any configuration.

The fix

Did this fix it for you? One tap — anonymous, nothing to type, and nothing you send is ever published.

Full case: this error is one stop in a bigger fault. Work the complete playbook: Port Keeps Going Err-Disabled — checks, ranked causes, the fix, and verification.

Sources

More error messages

Decoder

%PM-4-ERR_DISABLE

Port shut itself off (err-disabled): link-flap

Decoder

%PORT_SECURITY-2-PSECURE_VIOLATION

Port security violation: port shut down

Decoder

%BGP-5-ADJCHANGE

BGP neighbor went down (or came up)