19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ATM-NTWK (ATM Network Error)<br />

d. Error Type 769: ATM CLP (Cell Loss Priority) Bit Errors<br />

The ATM cell header has a bit called the cell loss priority (CLP) bit. The bit indicates one of<br />

two states: the cell is eligible for discarding, or it is not. In an ATM configuration, every cell<br />

is transmitted into the ATM network with the CLP bit set to 0 indicating that these cells are<br />

NOT eligible for discarding. Should the system ever receive a cell from the ATM network<br />

with the CLP bit set to 1 (discard eligible), an entity in the ATM network modified the bit<br />

during transit. Generally, an ATM network switch sets the CLP bit to 1 (discard eligible)<br />

only if the cell fails to conform to the cell rate specified in the traffic contract for the VC.<br />

However, Communication Manager cell emissions conform with the VC traffic contract.<br />

Therefore, the presence of a non-conforming cell implies that something else in the ATM<br />

network switch is setting the CLP bit in some cells, the ATM switch can also be policing out<br />

(discarding) cells which do not conform to the traffic contract. This <strong>error</strong> can occur together<br />

with other <strong>error</strong>s such as:<br />

“Excessive AAL-5 CRC <strong>error</strong>s” or<br />

“Excessive LAP-D retransmissions”<br />

These <strong>error</strong>s affect SVCs with Variable Bit Rate (VBRnt) traffic contracts. VBR SVCs<br />

transport system links such as EAL, PACL, <strong>and</strong> PRI links. Again, this indicates problems<br />

with cell transmissions in the ATM network.<br />

If cell discard is happening generically in the ATM network, other symptoms can affect the<br />

Constant Bit Rate (CBR) SVCs including audible artifacts in talk paths, failure of modems<br />

over voice lines, <strong>and</strong> “Cell Underruns” - see note (f).<br />

e. Error Type 1025: ATM Congestion Bit Errors<br />

The ATM cell header has a bit called the congestion bit. In Communication Manager ATM,<br />

every cell is transmitted into the ATM network with the congestion bit set to 0 (congestion<br />

not experienced). Should the system ever receive a cell from the ATM network with the<br />

congestion bit set to 1 (congestion experienced), an entity in the ATM network modified the<br />

bit during transit. It simply indicates that the ATM network is experiencing heavy traffic.<br />

During periods of congestion, the ATM network can choose to discard cells even though<br />

those cells conform to their traffic contracts. Should the ATM network discard cells, <strong>error</strong>s<br />

such as the following can occur:<br />

“Excessive AAL-5 CRC <strong>error</strong>s”<br />

“Excessive LAP-D retransmissions”.<br />

These <strong>error</strong>s affect SVCs with Variable Bit Rate (VBRnt) traffic contracts. VBR SVCs<br />

transport system links such as EAL, PACL, <strong>and</strong> PRI links. Symptoms that can affect the<br />

Constant Bit Rate (CBR) SVCs include audible artifacts in talk paths, failure of modems<br />

over voice lines, <strong>and</strong> “cell Underruns” – see note (f).<br />

f. Error Type 1281: ATM Cell Underruns<br />

Communication Manager ATM monitors for cell underrun conditions on SVCs with<br />

Constant Bit Rate (CBR) traffic contracts or on ATM CES trunks. In either case, cells are<br />

expected to arrive at a fixed rate. If cells arrive below that rate, an underrun condition<br />

exists. The most likely cause of cell underruns is a problem with cell transmission through<br />

the ATM network.<br />

Issue 5 May 2009 155

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!