Guest

Cisco WAN Switching Modules

BPX TX BIP-16 Errors

Document ID: 10811

Updated: Oct 04, 2005

   Print

Introduction

The bit-interleaved parity with sixteen bit errors (BIP-16) is generated when the BFrame is created on the ingress and which stays with it until the cell is extracted on the egress of the switch. The TX BIP-16 error count is taken at the BIF-TX as the BFrame is transmitted onto the backplane.

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.

TX BIP-16 Error Description

Because the data path up to the BIF-TX is on a single card, TX BIP-16 errors indicate an error on the reporting card, which makes isolating the fault easy. The errors indicate corruption of the BFrame which should appear as either BFrame Parity or Payload errors on the trunk or port statistics of the receiving card.

Clearing the Errors

Follow the instructions provided below to clear TX BIP-16 errors:

  1. Replace the card on which the Tx BIP-16 errors occur.

    A hardware problem usually results in the maximum rate count being logged, but can occur only if traffic flows through the card. If less than the maximum rate is seen, it is possible that the configuration of the BFrame header for one particular channel may be incorrect. However, a hardware failure could cause this as well.

  2. If replacing the card does not resolve the errors, or if errors are occurring on multiple cards, use the switchcc command to isolate the source of the error if the backplane or crosspoint matrix are involved.

    TX BIP-16 errors on multiple cards have been linked to specific configuration and heavy data loads for BPX Controller Card-3 (BCC-3) and BCC-3-32 processor cards. Upgrading both processors to BCC-4V, which allows for faster performance, can resolve the errors.

Related Information

Updated: Oct 04, 2005
Document ID: 10811