Mitel Sx 200 Ml Pabx Lightware 16 Instructions Guide

							Reports Level Functions 
The information in Table 5-6 is displayed for information only; it cannot be altered from 
the terminal. 
Table 5-6 Definition Of Maintenance Terminal Display 
Display Meaning 
DSTi Data ST bus input (32 channels 24 active). 
DSTo Data ST bus Output (32 channels 24 active). 
CSTi Control ST bus Input (32 channels 25 active). 
CSTo Control ST bus Output (32 channels 2.5 active). 
SYNC SYNC indicates whether there is synchronization to the RECEIVED DSl link, 
SLIP This bit changes state once a slip condition occurs between the RECEIVED DSI data 
and the ST-BUS data. 
BPV 
xsi This bit changes state after 256 bipolar violations, other than the B8ZS code, within a 
sample period of 200 ms. 
This EXTERNAL SCAN POINT bit contains the data sampled at the XSl pin once per 
frame. 
RxY LW RxYLW indicates that a yellow alarm is being received on the RECEIVED DSl link. 
XCTL XCTL indicates whether the link is active or not (act, inact). 
B8ZS B8ZS bit value in control register. 
8KHZ 8KHz bit value in control register. If 1, then the 8khz pin is low for received channels 1 to 
1.5 and high for channel 16 to the S-bit. 
TxY lw TxYlw indicates whether a yellow alarm is being sent down the link. 
DAC The current value being written to the DAC. The DAC is on the Tl Clock lntetface Module. 
Its purpose is to provide the ability to adjust the system clock. This is accomplished by 
writing a 12-bit word to the DAC. 
SRCE This field gives the current SYNC source (Bay/slot). 
MODE This is the current mode of operation. There are three modes: AUTO (AUTO), FREERUN 
(FREE), or MANUAL (MANU). 
AUTO - the Tl process is adjusting the system clock to lock on to the incoming 1.544 
Mhz signal. The link that the process looks at for an external source is based on the order 
of the links in the network synchronization form. 
FREERUN -the system clock is not being adjusted to lock on to the incoming 1.544 Mhz 
signal. The reason is that there is nothing programmed in the network sync form or the 
links all exceed the error threshold. 
MANUAL -the Tl process is forced via maintenance to look at a particular link as an 
external source. The system clock is adjusted to this link and locks to this source. The 
Tl process will automatically switch externalsourcesafter24 hoursoriftheerrorthreshold 
has been exceeded. 
TX This is the current data sample forthe transmit side of the channel that is being monitored. 
Rx This is the current data sample forthe receive side of the channel that is being monitored. 
TxA, TxB TxA and TxB are the transmit A and B bits used for controlling channels on the DSl link. 
Page 1 of 2 
March 1997 Issue 1 Revision 0  
						

							RS-232 Maintenance Terminal 
1 
I 
Table 5-6 Definition Of Maintenance Terminal Display (continued) 
Display Meaning 
TxPD The per channel transmit attenuation control bits. 
RxA, RxB RxA and RxB are the receive A and B bits used for monitoring channels on the DSl link. 
1 RxPD 1 The per channel receive attenuation control bits. 
I 
LPBK LPBK indicates whether any loopbacks have been activated: 
no -there are none 
Ext - External loopback has been activated for the card 
lnt - Internal loopback has been activated for this card 
dig - digital loopback has been activated for this channel (is not seen if the card is in 
analog loopback). 
Page 2 of 2 
5-18 
Issue 1 Revision 0 March 1997  
						

							Reports Level Functions 
Data Fault Analysis Procedures 
’ 5.7 Generic information and procedures for analyzing datasets and data-related 
problems is provided here; refer to it for troubleshooting problems before referring to 
specific data device troubleshooting charts. 
Table 5-7 Possible Causes Of Data-related Errors 
ERROR POSSIBLE CAUSE 
CALL STATE DATASET CABLI DX DLC DTE / DCE 
NG 
CRCERR ANY Yes Yes Yes Yes No 
(DNICIHDLC) (DNlC/HDLC) 
RESETS ANY Yes Yes Yes Yes Yes 
LINK CALL Yes Yes Yes Yes No 
FAILURES SETUP OR 
TALKING 
LINK ABORTS CALL Yes Yes Yes Yes Yes 
SETUP OR 
TALKING 
PARITY ANY Yes (UART) No No No Yes 
(Connectors) 
OVERFLOW TALKING No No No No Yes 
OVERRUN TALKING No No No No Yes 
FRAMING TALKING No No No No Yes 
NOSYNC ANY Yes Yes No Yes No 
CRC Error: A CRC (Cyclic Redundancy Check) error will be logged whenever the 
HDLC chip reports a CRC ERROR, FIFO OVERFLOW, or FRAME ABORT. They are 
recorded on both the B and the 
D channel. The probable cause is a hit on the 
transmission line; the protocol usually recovers gracefully. If the errors become so bad 
that the protocol cannot continue to run, then a link reset will occur. If the link resets, 
the link reset may not be successful - if the dataset is on the B-channel, it will return 
to the D-channel with a disconnect reason of link abort. 
CRC errors happen on one end of a call if the dataset at the other end is unplugged. 
The connected dataset records a large number of CRC errors, followed by a link reset, 
and then a link abort. 
Link Resets: A link reset occurs when the dataset sends a message, does not receive 
a response, retransmits the message more times, and still cannot get a response. At 
this point, the dataset will log a link reset, and then try to re-establish communication 
by sending SABMs (Set Asynchronous Balance Mode) to the far end. Link resets can 
occur on both B and D channels. 
March 1997 Issue 1 Revision 0 5-19  
						

							RS-232 Maintenance Terminal 
5-20 
Link Aborts: A link abort occurs when the dataset, after sending a SABM 8 times, 
cannot get a valid response from the far end. Thus, a link abort often follows a link 
reset (specifically when the link reset happened because of many transmission line 
errors, set unplugged, or circuit switch path broken). 
Link aborts can also occur just after the dataset is sent to the B-channel. The dataset 
will send up to 64 SABMs in an attempt to achieve communication; if it does not receive 
a valid response, a link abort will occur, and the dataset will return to the D channel. 
There will NOT be an associated link reset (because the link was never in a “normal” 
state). 
Link Failures: There are two events which occur on the B-channel that can cause a 
link failure: 
l If the dataset is connected on the B-channel, in “normal” mode (NOT go-ahead 
mode), and the dataset receives an idle “1”s pattern rather than flags for more 
than 0.5 second, the dataset will disconnect from the B-channel, with a B-to-D 
reason of link failure. 
l If the dataset is connected on the B-channel in go-ahead mode, and the dataset 
does NOT receive a go-ahead after transmitting flags, the dataset will return to 
the D-channel, and report a link failure. 
Overflows: Overflows occur when the device attached to the dataset sends data to 
the dataset faster than the dataset can send 
it off to the far end. Two scenarios are: 
l Dataset A is at a high baud rate, dataset B is at a lower baud rate, and flow control 
is NOT enabled on the datasets. In this case, overflows will occur in dataset A. 
This should NEVER happen; software should not allow two datasets at different 
baud rates to communicate unless flow control is enabled. 
l Dataset A and dataset B both have flow control enabled. The device attached to 
dataset A is transmitting a large amount of information. The device attached to 
dataset B flow-controls dataset B. Dataset B stores up as much data from A as it 
can, then tells A to stop transmitting. Dataset A sends a flow control character to 
the attached device, but the device ignores it and continues to transmit. Overflows 
occur. Overflows can happen as a result of a defective attached device, an at- 
tached device not having flow control enabled, or the dataset using different flow 
control characters or kind of flow control (e.g., CTS) than the device is expecting. 
l/F Framing Errors: Framing errors occur because the device is set at a different baud 
rate from the dataset. A common cause is that the user changes the terminal baud 
rate during a session (or while idle, if the dataset is not programmed for autobaud 
operation). One possible scenario is: 
l A user establishes a call at 1,200 baud. 
l The user decides that is too slow. 
l The user then sets his terminal baud rate to 9,600. 
Framing errors occur and the user cannot communicate, because the dataset is still 
at 1,200 baud. The only recovery is to disconnect the call and start over. 
NOSYNC Errors: NOSYNC errors occur when the dataset has lost synchronization 
with the SX-ZUU ML PABX; loss of synchronization usually occurs when a dataset has 
been powered off or a data connection has been broken. 
Issue 1 Revision 0 March 1997  
						

							Reports Level Functions 
Power Up Self Test Causing the Dataset to be Busied Out: 
If a dataset fails its power 
up self test, it will be busied out. Maintenance logs will have two log entries: the busied 
out log and the power up self test failure reason. If a new dataset is installed that passes 
the power up self test, the device will be returned to service, without an installer using 
a maintenance command. 
Error Reports 
Show Errors 
5.8 The Error Reports provide the maintenance user with an up-to-date record of all the 
transmission checksum errors that have occurred since the system was initialized, or 
since they were last cleared (see Clearing Error). 
To obtain an error report, press the following softkeys: 
SHOW 
ERRORS 
DEVICE-TYPE 
At this point the following softkeys are presented for device selection: 
DIGITAL-SETS 
HDLC 
CONSOLE 
DATASETS 
Tl-TRUNK 
ENTER 
The system outputs the error data in the applications area of the screen. In cases 
where the data requires more space than is available on the screen, the user is 
prompted asfollows: 
. Select the MORE softkey for more data. 
OR 
9 Select the CANCEL softkey to cancel the output. 
Examples of error reports follow. 
March 1997 Issue 1 Revision 0 5-2 1  
						

							RS-232 Maintenance Terminal 
Digital Set Errors 
m 
~HIIU ERRIIR~ 
DIG1 T FIL-SET s 
l- 2- 
3- 4- 5- CWlCEL 
6- 
7- 8- 9- 0- 
Figure 5-5 Example of Digital Set Error Report 
Explanation of error types: 
No 
Sync: A synchronization signal is sent between the digital circuit and the set. The 
digital circuit monitors the physical line for the presence of this signal. Synchronization 
is lost when a set is unplugged or when a line is very noisy (external interference or 
bad connection). A loss of synchronization increments the ‘no sync’ counter; however, 
maintenance reports are updated only after every 25 occurrences. 
In normal operation, this counter will not exceed about 50 for the operating life of a 
set. A set will get about 25 occurrences each time the set is unplugged or the system 
is reset. 
Investigate a set that gets 50 or more ‘no sync.9 a day: 
- check tip/ring connection (remove bridge taps, proximity to noise sources, 
loop length) 
- swap set 
- swap circuit card. 
Link Reset: A link reset will occur when communications between a digital set and 
circuit is torn down. In most cases, the reset is because a set was unplugged or the 
system was reset; however, it can also occur because of a protocol violation. 
In most cases, a set will get only one link reset during its life. In a 24-hour period, 20 
or more link resets may affect set operation and the problem should be investigated. 
5-22 Issue 1 Revision 0 March 1997  
						

							Reports Level Functions 
Retransmits: The retransmit counter increments each timeadigital circuit has to resend 
just sent information to a set. If the set has not responded to having received the just 
sent information, the circuit resends. 
This problem can be caused by: 
- a noisy line 
- bad set 
- bad circuit 
- software error (protocol violation). 
In most cases, a set will have no retransmits in a 24-hour period; however this counter 
can be influenced by the amount of traffic to the set. The more messages sent to a 
set, the greater the possibility that a message may not make it to that set and will have 
to be retransmitted. Investigate more than 50 retransmits in a 24 hour period although 
the user will probably not observe any problem at this rate. 
HDLC Link Errors 
2:34 Ptl 10-ml+37 alarm status = I’40 flLflRll 
HDLC LINK T #-ERR RX-ERR UJRFLU CRCERR IWIIRT S IIIIIIPKT RET RFibl 
llc to l3a.J 1 5s 0 # 0 0 0 0 
2 
1 
r- SH#U ERRORS HDLC 
l- 2- 3- 4- 5 UIHCEL 
6- 7- #- 9- 0- 
March 1997 
Figure 5-6 Example of HDLC Link Error Statistics Report 
Issue 1 Revision 0 5-23  
						

							RS-232 Maintenance Terminal 
Explanation of HDLC Link Error types: 
HDLC Link errors are explained following: 
ERROR BAY TO MC MC TO BAY Error Rate 
Expected 
TX-ERR Transmitter underrun. Transmitter underrun. none 
RX-ERR Undefined error. Undefined error. none 
OVRFLW Bay HDLC receiver fifo overflowed. 
Main HDLC receiver fifo none 
overflowed, 
ABORTS Bay received HDLC ABORT Main received HDLC ABORT see note 1 
sequence from main. sequence from main. 
ODDPKT Bay received packet with odd Main received packet with odd num- see note 2 
number bytes. ber bytes. 
RETRAN Bay retransmitted packet. Main retransmitted packet. see note 2 
Note: 1. 
Dependent upon message traffic on a main-bay link, but should be low, less than 10. 
2a Dependent upon message traffic on a main-bay link, but should be low, generally less than 
30 per 24 hours. 
Console Errors 
El: 13 PH l@-JRN-3? al am St at us = N0 RLflRtl 
PL1i.l EXT .# IIE’JI CE NO-SfNC RESET 3 RET RRN3 IIHEIZZYJN 
1 # 3 I 1#03 rZ0N30LE 25 8 8 0 
1 
3HtrU ERROR3 rZ0NSlLE 
l- 2- 3- 4- 5- IZRNIZEL 
6- ?- #- 3- e- 
Figure 5-7 Example of Console Error Report 
5-24 Issue 1 Revision 0 March 1997  
						

							Reports Level Functions 
Explanation of error types: 
No Sync: 
A synchronization signal is sent between a digital circuit and a console. The 
digital circuit monitors the physical line for the presence of this signal. Synchronization 
is lost when a console is unplugged or when a line is very noisy (external interference 
or bad connection). A loss of synchronization increments the ‘no sync’ counter; 
however, maintenance reports are updated only after 25 occurrences. 
In normal operation, this counter will not exceed about 50 for the operating life of a 
console. A console will get about 25 occurrences each time the console is unplugged 
or the system is reset. 
Investigate a console that gets 50 or more ‘no syncs’ a day. 
- check tip/ring connection (remove bridge taps, proximity to noise sources, 
loop length) 
- swap console 
- swap circuit card. 
Link Reset: A link reset will occur when communications between a digital console 
and circuit is torn down. in most cases, the reset is because a console was unplugged 
or the system was reset; however, it can also occur due to a protocol violation. 
In most cases, a console will get only one link reset during its life. In a 24-hour period, 
20 or more link resets may affect console operation; investigate the problem. 
Retransmits: The retransmit counter increments each time a digital circuit has to resend 
just sent information to a console. if the console has not responded to having received 
the just sent information, the circuit resends. 
This problem can be caused by: 
- a noisy line 
- bad console 
- bad circuit 
- software error (protocol violation). 
In most cases, a console will have no retransmits in a 24 hour period; however this 
counter can be influenced by the amount of traffic to the console. The more messages 
sent to a console, the greater the possibility that a message may not make it to that 
console and will have to be retransmitted. Investigate more than 50 retransmits in a 
24-hour period although the user will probably not observe any problem at this rate. 
Checksum: Bad checksum in CONSOLE ROM will report error to maintenance. 
March 1997 Issue 1 Revision 0 5-25  
						

							RS-232 Maintenance Terminal 
DATASET Errors 
1:16 PH 14-JfiH-97 alam status q tW MWl 
PLIR EXT.# FRILRS RENIRTS CRCERR RESETS PRRITY RURFLU tlWftiC 
1 8 1 2 13888 0 0 El 0 0 0 1 
I SHMI ERRURS DRTRSETS 
I 
l- 2- 3- 4- 5-CRtlCEl 
6- 7- 
8- 9- 0- 
Figure 5-8 Example of DATASET Errw Statistics Report 
Explanation of error types: 
FAIL%: The dataset sends flags requesting communication but does not receive 
acknowledgment from the Digital 
Line Card; the HDLC on the DLC is time-shared with 
up to 12 datasets, and sends “go-aheads” to each dataset when it is ready to 
communicate; if the HDLC is busy with one dataset for too long, other datasets will not 
receive “go-ahead”. 
This error can also apply to situations which involve link layer errors such as failing to 
achieve link reset after 64 tries. 
Check the dataset and the Digital Line Card. 
ABORTS: The link is up but the command - response exchange (Set Asynchronous 
Balance Mode - Unnumbered Acknowledgment) does not succeed. The SABM-UA 
could happen between the dataset and the SX-2OCJ ML PABX when they are 
programmed as DTRX, or between the two datasets. 
This error can also apply to situations such as received idle HDLC linkwhen flags were 
expected. 
Check the dataset and the Digital Line Card. 
CRCERR: number of retransmissions on the link; this value is set to zero when DNIC 
synchronization is lost. 
The line is noisy or of poor quality. 
5-26 Issue 1 Revision 0 March 1997