Token Ring

Document ID: 27322

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
HAWKEYE-3-MAC_CMD_Q_OVERFLOW Message
      Troubleshooting Steps
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document discusses the reasons that may lead to HAWKEYE-3-MAC_CMD_Q_OVERFLOW error messages appearing on Cisco routers with Token Ring interfaces. This document provides troubleshooting steps that should be taken to remedy this condition.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

• Hawkeye is the name of chipset existing in onboard Token Ring interfaces of Cisco 2612, Cisco 2613 and Cisco 36X0, Cisco 37X5 with NM-1FE1R2W module and PA-4R-DTR port adapter. Minimum software versions for these routers are: 11.3(4)T, 12.0(1)T, 12.0(1), 12.0(3)T, 12.0(5)XK, 12.0(7)T, 12.0(7)XK, 12.1(1)T, 12.1(1), 12.1(5)YB, 12.1(5)YD, 12.2(1), 12.2(2)T, 12.2(2)XT, 12.2(11)YT, and 12.3(1). Please use Cisco Software Advisor ( registered customers only) .

• All releases are minimum versions and may not be available; for a given train (for example, Cisco IOS® 12.2T), please download the most recent maintenance release.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

HAWKEYE-3-MAC_CMD_Q_OVERFLOW Message

Typically, HAWKEYE-3-MAC_CMD_Q_OVERFLOW messages appear on the router console or in the log-in this format: %HAWKEYE-3-MAC_CMD_Q_OVERFLOW : HAWKEYE ([dec]/[dec]), MAC command queue overflow .

The command queue of the interface was full when the device driver attempted to send a command to the interface hardware. This message may occur if the device driver software sends commands faster than the interface hardware can process them. This condition is usually not a critical error; the interface should continue to function normally. If the error message recurs frequently, however, it may indicate a more serious problem.

Troubleshooting Steps

Complete these steps:

1. Check CSCdw46846; try to apply these workarounds:

   1. You may resolve the syslog messages by issuing the clear interface token x command.

      The message means that the Hawkeye MAC processor on the Token Ring interface has gotten wedged. This could possibly happen if the ring is in really bad shape (lots of MAC errors). If the interface still seems to pass traffic, the most immediate impact is that interface statistics are not being updated (this is the CMD that you are trying to send to the interface every ten seconds). Issuing the clear interface command should help also, but this will be traffic disruptive

   2. Issue the lnm disable command in the global configuration mode. This may also clear this issue, provided that LAN Network Manager (LNM) functionality is not needed (or used) in the network. Disabling LNM, helps to reduce the traffic in the Token Ring network.

   3. Disable Cisco Discovery Protocol (CDP) which helps to reduce traffic. CDP determines if the Token Ring is busy.

      Note: Disabling or enabling CDP on a Token Ring interface is disruptive, and can cause the Token Ring interface to re-initialize.

   4. If the router is configured for DLSw, and if you have issued the source-bridge proxy-explorer command configured under this Token Ring interface, it is necessary to remove proxy-explorer since DLSw has this functionality by default. Refer to RSRB Migration and Multivendor Interoperability for more information.

   5. Test the physical components of the interface itself and make sure that the hardware components are still functioning as expected. You can do this by issuing the test interface X command. Sample output is below. If there are any fails, there is a hardware issue. You will need to replace the hardware.

      B14_2600#test interfaces tokenRing 0/0
      !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Passed
      1 interfaces: 1 passed, 0 failed, 0 skipped, 0 untestable
      B14_2600#
      
      

   6. Try to reload the router.

2. If these workarounds do not help, collect this command output and contact the Cisco Technical Assistance Center (TAC):

   • show tech-support

   • show logging

   • show lnm interface tokenRing x/y

   • show ip arp tokenRing x/y

   • show rifshow source-bridge

   • show rif

   • show source-bridge

3. Insert a Token Ring sniffer analyzer into the ring and capture a sniffer trace for all the traffic in that ring. Do this when you see the messages.

NetPro Discussion Forums - Featured Conversations

Related Information

• Token Ring Switching Support
• Technical Support - Cisco Systems