Cisco IE-3000-8TC Message Guide - Page 35

ETHCNTR Messages - poe

Page 35 highlights

Chapter 2 Message and Recovery Procedures ETHCNTR Messages ETHCNTR Messages This section contains the Ethernet controller messages. These messages result from a failure of the switch software when trying to program the hardware and lead to incorrect switch behavior. Error Message ETHCNTR-3-HALF_DUX_COLLISION_EXCEED_THRESHOLD: Collision at [chars] exceed threshold. Consider as loop-back. Explanation The collisions at a half-duplex port exceeded the threshold, and the port is treated as a loopback. On switches that support Power over Ethernet (PoE), this message might be displayed when a device that can be powered by either a PoE switch port or by AC power is not being powered by an external AC power source and is connected to a port that has been configured with the power inline never interface configuration command. [chars] is the port where the threshold was exceeded. Recommended Action On switches that support PoE, remove the device or configure the port by entering the power inline auto, shutdown, and no shutdown interface configuration commands. No action is required on non-PoE switches. The port goes into error-disabled mode until the problem is resolved. Error Message ETHCNTR-3-LOOP_BACK_DETECTED:, Loop-back detected on [chars]. The port is forced to linkdown. Explanation This message occurs when a keepalive packet is looped back to the port that sent the keepalive. The loopback condition might be caused by a balun cable being accidentally connected to the port, or there might be a loop in the network. [chars] is the port. Recommended Action Examine the cables. If a balun cable is connected, and the loopback condition is desired, no action is required. Otherwise, connect the correct cable, and bring the port up by entering the no shutdown interface configuration command. We do not recommend using the no keepalive interface command to disable keepalives. The cause of this network loop must be found and corrected. Although disabling keepalives prevents the port from being error disabled, it does not resolve the cause of the problem and can affect network stability. See CSCea46385 for more information. Error Message ETHCNTR-3-NO_HARDWARE_RESOURCES: Not enough hardware resources. Shutting down [chars]. Explanation There are too many VLANs and routed ports (if the switch supports routed ports) configured. [chars] is the short interface name, or the VLAN name, such as VLAN0002. Recommended Action Reduce the total number of VLANs and routed ports to less than 1023. To preserve configuration and connections across reboots, save the configuration. OL-13020-01 Cisco IE 3000 Switch System Message Guide 2-21

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98

2-21
Cisco IE 3000 Switch System Message Guide
OL-13020-01
Chapter 2
Message and Recovery Procedures
ETHCNTR Messages
ETHCNTR Messages
This section contains the Ethernet controller messages. These messages result from a failure of the
switch software when trying to program the hardware and lead to incorrect switch behavior.
Error Message
ETHCNTR-3-HALF_DUX_COLLISION_EXCEED_THRESHOLD: Collision at [chars]
exceed threshold. Consider as loop-back.
Explanation
The collisions at a half-duplex port exceeded the threshold, and the port is treated as a
loopback. On switches that support Power over Ethernet (PoE), this message might be displayed
when a device that can be powered by either a PoE switch port or by AC power is not being powered
by an external AC power source and is connected to a port that has been configured with the
power
inline never
interface configuration command. [chars] is the port where the threshold was exceeded.
Recommended Action
On switches that support PoE, remove the device or configure the port by
entering the
power inline auto
,
shutdown
, and
no
shutdown
interface configuration commands.
No action is required on non-PoE switches. The port goes into error-disabled mode until the problem
is resolved.
Error Message
ETHCNTR-3-LOOP_BACK_DETECTED:, Loop-back detected on [chars]. The port
is forced to linkdown.
Explanation
This message occurs when a keepalive packet is looped back to the port that sent the
keepalive. The loopback condition might be caused by a balun cable being accidentally connected
to the port, or there might be a loop in the network. [chars] is the port.
Recommended Action
Examine the cables. If a balun cable is connected, and the loopback condition
is desired, no action is required. Otherwise, connect the correct cable, and bring the port up by
entering the
no shutdown
interface configuration command. We do not recommend using the
no
keepalive
interface command to disable keepalives. The cause of this network loop must be found
and corrected. Although disabling keepalives prevents the port from being error disabled, it does not
resolve the cause of the problem and can affect network stability. See
CSCea46385
for more
information.
Error Message
ETHCNTR-3-NO_HARDWARE_RESOURCES: Not enough hardware resources.
Shutting down [chars].
Explanation
There are too many VLANs and routed ports (if the switch supports routed ports)
configured. [chars] is the short interface name, or the VLAN name, such as VLAN0002.
Recommended Action
Reduce the total number of VLANs and routed ports to less than 1023. To
preserve configuration and connections across reboots, save the configuration.