Table 5%9. Interpretation of EL Loopback Test Bits

 

 

Bit Setting

Interpretation

 

 

NR = 1

The loopback test packet was not received by the LANIC card.

 

 

D = 1

The loopback test packet was deferred from transmission (for example, due

 

to a busy network) for a period that exceeded a preset firmware timeout

 

(approximately 1 second).

 

 

B = 1

On transmission, the number of valid packet bytes was exceeded and

 

detected by the Link Controller chip (a •babble" error).

 

 

H = 1

The LANIC card's MAU did not return a heartbeat signal.

 

 

M = 1

The LANIC card memory subsystem could not be accessed by the Link

 

Controller chip on the card.

 

 

BT = 1

The LANIC card transmit buffer was not properly accessed by the Link

 

Controller chip.

 

 

U = 1

A transmit data underflow into the Link Controller chip occurred causing faulty

 

or incomplete transmission.

 

 

L = 1

On packet transmit, a collision occurred after the allowed slot time for normal

 

collision detection (•Late Collision").

 

 

LC = 1

The LANIC card lost the carrier signal of the transmit packet, that is, LAN

 

medium voltage levels fell below prescribed limits.

 

 

R = 1

A collision was detected on each attempt to transmit the packet.

 

 

F = 1

Framing error. An integral number of bytes was not received.

 

 

O = 1

For the received packet, a data overflow into the Link Controller chip

 

occurred.

 

 

CR = 1

For the received packet, a CRC error occurred.

 

 

BR = 1

Buffer error on the received data, or the received packet data did not match

 

the transmit packet data.

 

 

EL Command Examples

The following examples illustrate command entry and response of the •Do External Loopback to MAU" command.

Example 1. Successful External Loopback Test

NM> EL<RETURN>

 

Do External Loopback on node

08-00-09-00-02-5A.... [ok]

NM>

In Example 1, an external loopback packet was transmitted from the node whose Station Address is 08"00"09"00"02"5A. Successful completion is indicated by the •[ok]" message.

Using Node Manager 5%39