cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Error - "%ETHCNTR-3-LOOP_BACK_DETECTED" Catalyst switch that runs Cisco IOS® Software

38846
Views
15
Helpful
1
Comments

 

Introduction

The user receives the "%ETHCNTR-3-LOOP_BACK_DETECTED" error message on a Cisco Catalyst switch that runs Cisco IOS® Software.

Core issue

The %ETHCNTR-3-LOOP_BACK_DETECTED:loop-back detected error message is recorded in the syslog. In addition, the interface in question goes into an administratively down state without manual configuration.

This issue can occur on Cisco Catalyst 2940, 2950, 2950-LRE, 2955, 2970, 3550, 3560, 3750 and other fixed configuration Catalyst switches under one of these conditions:

  • The wrong cable is accidentally plugged into the port.
  • The keepalive packet is looped back to the port that sent the keepalive.

Resolution

If the incorrect type of cable is connected and the loopback condition is desired, no action is required.

Otherwise, connect the correct cable. Issue the no shutdown command in interface configuration mode to bring the port up.

If the keepalive packet is looped back to the port that sent the keepalive, issue the no keepalive interface command to disable keepalives. This prevents the port from being disabled.

 Keepalive packets are used for Balun detection on copper interfaces and are enabled by default on all interfaces.

Disabling keepalives on fiber interfaces should reduce the likelihood of a temporary loop causing part of the network to go down.

The issue has been reported, and keepalives are disabled by default from 12.2x SE code.

This issue is documented in Cisco bug ID CSCea46385.

Reference

ETHCNTR-3-LOOP_BACK_DETECTED: Loop-back detected on gig0/2 - CSCea46385

Description

Symptom:

An interface on a Catalyst switch is error disabled after detecting a loopback.

Mar 7 03:20:40: %ETHCNTR-3-LOOP_BACK_DETECTED: Loop-back detected on

GigabitEthernet0/2. The port is forced to linkdown.

Mar 7 03:20:42: %LINK-5-CHANGED: Interface GigabitEthernet0/2, changed state

to administratively down

Mar 7 03:20:43: %LINEPROTO-5-UPDOWN: Line protocol on Interface

GigabitEthernet0/2, changed state to down

Conditions:

This might be seen on a Catalyst 2940, 2950, 2950-LRE, 2955, 2970, 3550, 3560

or 3750 switch running 12.1EA or 12.2SE based code.

Workaround:

Disable keepalives by using the no keepalive interface command. This

will prevent the port from being errdisabled, but it does not resolve the root

cause of the problem. Please see section below for more information.

Additional Information:

The problem occurs because the keepalive packet is looped back to the port that

sent the keepalive. There is a loop in the network. Although disabling the

keepalive will prevent the interface from being errdisabled, it will not remove

the loop.

The problem is aggravated if there are a large number of Topology Change

Notifications on the network. When a switch receives a BPDU with the Topology

Change bit set, the switch will fast age the MAC Address table. When this

happens, the number of flooded packets increases because the MAC Address table

is empty.

Keepalives are sent on the Catalyst 2940, 2950, 2950-LRE, 2955, 2970, 3550,

3560 or 3750 switch to prevent loops in the network. The primary reason for

the keepalives is to prevent loops as a result of Type 2 cabling. For more

information, see:

http://www.cisco.com/en/US/netsol/ns340/ns394/ns74/ns149/networking_solutions_white_paper09186a00800a3e16.shtml

Keepalives are sent on ALL interfaces by default in 12.1EA based software.

Starting in 12.2SE based releases, keepalives are NO longer sent by default on

fiber and uplink interfaces.

PSIRT Evaluation:

The Cisco PSIRT has evaluated this issue and does not meet the criteria for PSIRT ownership or involvement.

This issue will be addressed via normal resolution channels.

If you believe that there is new information that would cause a change in the severity of this issue,

please contact psirt@cisco.com for another evaluation.

Additional information on Cisco's security vulnerability policy can be found at the following URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

Comments
Beginner

Hi TCC

I have the problem loopback because of keepalive..we are planning to disable to keepalive on our switch port. May i know what impact if we disable the keepalive..any downtime need? or any intruption? 

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards