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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

us. This <strong>error</strong> indicates an on-board problem related to the packet implementation of the<br />

TDM D-Chel. This <strong>error</strong> is logged only.<br />

r. Error Type 3586: each port can support up to three Terminal Endpoint Identifiers (TEIs).<br />

Each chel on the port can request a TEI assignment from the switch if it supports ISDN-BRI<br />

TEI assignment procedures. If switch services gets a request for a fourth TEI on a port, it<br />

reports this event to maintenance software <strong>and</strong> initiates TEI check procedures on the port.<br />

Check to see if the correct number of chels are administered for this port.<br />

The user side supports automatic TEI assignment by the network. Both fixed <strong>and</strong><br />

automatic TEI assignment are supported on the network side.<br />

s. Error Type 3587: Service Profile IDentifier (SPID) value is invalid or is a duplicate of<br />

another SPID that is already initialized at Layer 3 on the port. SPIDs are not used on the<br />

circuit pack. However there will be related events.<br />

t. Error Type 3588: the board receives D-chel data from the bus faster than it can process the<br />

data. The FIFO RAM buffers overflowed. This <strong>error</strong> occurs occasionally due to the statistical<br />

sizing of the buffers; however, frequent occurrences may indicate a LAPD parameter<br />

mismatch between the two endpoints of a packet-switched connection. Run the long <strong>test</strong><br />

sequence, <strong>and</strong> note the results of the Receive FIFO Error Counter Test (#625).<br />

u. Error Type (3589: the BRI Port Local LAN Looparound Test (#618) failed. Run the long <strong>test</strong><br />

sequence, <strong>and</strong> note the results of Test #618.<br />

v. Error Type 3590: an activated BRI port receives a frame containing a DLCI over a D-chel<br />

for which it does not have a translation. This <strong>error</strong> normally indicates an off-board problem<br />

related to a state mismatch between the far end <strong>and</strong> the switch. This <strong>error</strong> is logged only.<br />

w. Error Type 3591: the circuit pack received a frame containing a DLCI over the TDM D-chel<br />

for which it does not have a translation. This <strong>error</strong> occurs only on a system that switches the<br />

packet implementation of the D-chel over the TDM bus, <strong>and</strong> indicates an off-board problem<br />

related to the state mismatch between the board <strong>and</strong> the packet implementation of the TDM<br />

D-chel. This <strong>error</strong> is logged only.<br />

x. Error Type 3592: the port is generating too many uplinks <strong>and</strong> is taken out of service for a<br />

period of time.<br />

y. Error Types 3841–3942: Table 256: Aux Data Values for Error 3841–3942 contains the<br />

received ISDN cause values for Errors 3841–3942 that are recorded in the <strong>error</strong> log. Unless<br />

946 Maintenance Alarms for Communication Manager, Media Gateways <strong>and</strong> Servers

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

Saved successfully!

Ooh no, something went wrong!