Guest

Cisco IGX 8400 Series Switches

IGX 8400 NTM Trunk Error Definitions

Document ID: 10876



Contents

Introduction
Before You Begin
      Conventions
      Prerequisites
      Components Used
NTM Trunk Alarm Types
Related Information

Introduction

This document defines trunk errors reported by the Cisco IGX 8400 Series Switch network trunk module (NTM). The trunk errors are similar to those reported by the IPX network trunk card (NTC) for Cisco WAN Switching System Software Release 9.1 and earlier. The IPX is not supported by switch software release 9.2 and later.

To use this document, select the link from the table below to go to the target trunk error pages, which provide the definitions and troubleshooting steps.

Statistical Alarms

Integrated Alarms

Bipolar Errors

Comm Fail Errors

Out of Frames

Loss of Signal (Red)

Loss of Signal

AIS (Blue)

Frame Bit Errors

Out of Frames (Red)

CRC Errors

Remote Out of Frames (Yellow)

Tx Voice Packet Drop

Packet Out of Frames (Red)

Tx TS Packet Drop

Remote Alarms (Yellow)

Tx Non-TS Packet Drop

 

Tx CC Packet Drop

 

Tx Bdata A Packet Drop

 

Tx Bdata B Packet Drop

 

Packet Error

 

Use the following commands to troubleshoot trunk problems.

dsptrks

A current view of all trunks and their status at the node.

dsptrkerrs

A current and historical view of status for all trunks at the node. To ensure a current view, use the clrtrkerrs command.

dsptrkerrs <slot_number>

A current and historical view of specified trunk status at the node. To ensure a current view, use the clrtrkerrs <slot_number> command. Before troubleshooting, use the clrtrkerrs <slot_number> command to ensure error counters are registering current events.

Before You Begin

Conventions

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

Prerequisites

There are no specific prerequisites for this document.

Components Used

This document is not restricted to specific software and hardware versions.

NTM Trunk Alarm Types

Statistical Alarms are displayed in the left-hand column and Integrated Alarms are displayed in the right-hand column of a dsptrkerrs screen as follows:

labigx       TN    StrataCom       IGX 8420  9.2.34    Nov. 6 2000  23:13 GMT 



TRK 10              Clear - OK                           Clrd:11/06/00 23:13:01

Statistical Alarm Count ETS   Status    Integrated Alarm  Count ETS   Status

Bipolar Err           0     0           Comm Fails            0     -

Out of Frms           0     0           Loss of SIG (RED)     0     -

Loss of SIG           0     0           AIS         (BLUE)    0     -

Frame BitErrs         0     0           Out of Frms (RED)     0     -

CRC Err               0     0           Rmt OOF     (YEL)     0     -

TX Voice Pkt Drp      0     0           Packet Oofs (RED)     0     -

TX TS Pkt Drp         0     0           Rmt Alarms  (YEL)     0     -

TX Non-TS Pkt Drp     0     0           VTRK Path Fails       0     -

TX CC Pkt Drp         0     0          

TX BData A Pkt Drp    0     0          

TX BData B Pkt Drp    0     0          

Packet Err            0     0          

Packet Oofs           0     0           Last failure time: Date/Time Not Set

                                                                                

Last Command: dsptrkerrs 10

If dsptrks shows the trunk as Clear-OK, no immediate action is required. Increasing error counts in the Statistical Alarm column typically cause minor alarms. Such alarms indicate that the trunk is experiencing errors but has not failed.

If error counts in the Statistical Alarm column exceed the threshold specified in the cnflnalm display, then a major alarm will be declared and the trunk will be removed from service. All connections are routed off the trunk or fail if no alternate trunk is available. Errors in the Integrated Alarm column typically cause major alarms.

If a new trunk experiences persistent Integrated Alarms, use the cnftrk <slot number> command to verify the trunk configuration.

Note: Virtual trunks are not supported by the NTM. Therefore, the VTRK Path Fails integrated alarm is not applicable and is not defined.


Related Information



Updated: Apr 30, 2009 Document ID: 10876