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

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.

Isolation is the difficult part with these errors because of a long
path through multiple cards. This is unique to a particular slot-to-slot
transmission. Use all information available to minimize the number of pieces of
hardware that you suspect cause the error. If multiple cards report the errors,
there is a good chance that a transmit path problem exists. One clue to the
source might be a particular card or port which does not show any errors, since
it is less likely to send to itself.

Broadband Network Interface (BNI) trunks can be tested using the
tstber command to generate traffic from the BCC to
that BNI. It goes out of the trunk, then in the other end of the BNI. It is
sent to the BCC on the remote node and looped back there. This is a long path,
so errors do not necessarily point to the culprit. However, if the traffic also
seems to increase the BIP-16 errors reported by the BCC, you might have found
the cause of the problem. You can use the switchcc
command to vary which backplane traces and crosspoint are used. This allows you
to see if any of those components of the data path are the problem.