T1 Circuit Hista Error

[RICHTz]

i have T1 Tie with Avaya system, the circuit is working but suddenly circuit is down

i get from HISTA this error


F5413 E8 N3258 STATIST BPA CIRCUIT L2 SPOR ERROR 17-03-12 08:31:15
ALARM CLASS:SWU-PER:001
** :LTG1 :LTU2 :121: 00 : 0 Q2226-X200 DIUT2-T1 BST:01 PLS:-08
FORMAT:22 DEVICE NAME: S1CONN
0200000149FFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFF

F5413 E8 N3259 STATIST BPA CIRCUIT L2 SPOR ERROR 17-03-12 08:31:19
ALARM CLASS:SWU-PER:001
** :LTG1 :LTU2 :121: 00 : 0 Q2226-X200 DIUT2-T1 BST:01 PLS:-08
FORMAT:22 DEVICE NAME: S1CONN
0200000147FFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFF

F5413 E8 N3260 STATIST BPA CIRCUIT L2 SPOR ERROR 17-03-12 08:32:55
ALARM CLASS:SWU-PER:001
** :LTG1 :LTU2 :121: 00 : 0 Q2226-X200 DIUT2-T1 BST:01 PLS:-08
FORMAT:22 DEVICE NAME: S1CONN
0200000147FFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFF

Can anyone tell me what the reason of this error,

note: if i make a restart for DIUT2 board the circuit is working again.

Thanks

 

[Moriendi]

All three messages indicate error in Layer 2 LAPD protocol, and unsuccessful retransmissions. So the circuit is already in error state. It doesn't tell you the cause of the problem.

 

[RICHTz]

YES FROM alfe MANUAL I GET ALSO THE SAME DESCRIPTION BUT WHATS THE MEANING, WHERE IS THE PROBLEM IN THE MEDIA BETWEEN TWO SITES OR WHATS YOUR OPENION

 

[Moriendi]

My opinion is that for a single event, forget about it.

Unify will say it's Avaya and Avaya will say it's Unify.

If the basic config was wrong I expect you'd have found out by now and you'd have bigger problems than this. But 4K is complaining about retransmissions, so either Avaya is not receiving, locked up, not transmitting. Cannot say. But one end should be clock master, the other slave, so you should check that at least.

You can change refta and set the error counter to 0, then check it later and see if ERROR is increasing. If it is, you have a problem to solve.

If you have a spare slot on a DIU you could move the Avaya circuit to a new board, new cable, see if the problem follows the move.

Check hista for that PEN as far back as you can, check if you get hista output even when users report no errors.

This kind of problem often needs an ISDN tester for unbiased finger pointing, it should show you which end died first.

 

[donb01]

On a T1 board you should be able to say DIS-BSSU and enter the PEN of the board. That should have peg counts for a variety of errors such as FS for frame slips, ESF for extended superframe errors, etc. It's not unusual to have a few of those errors, but if it's in the thousands (max is 65535) or the next time you look it has increased significantly you have some kind of circuit error. Normally in that case I would blame the provider (and lie and say I already checked all my stuff - otherwise they blame you back), they find the problem and it goes away, but in your case you ARE the provider....

You can also clear the BSSU stats so you can have a fresh start. Note those stats are accumumalted over a rolling 24 hours.

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[RICHTz]

my question is this error is related for the media because i have fiber & HDSL or this error due to any configuration from unify or avaya

make sure that this link is active may be for two days after that is get failure when i make a restart for DIUT2 card the circuit is working again and after may be one day is disconnect....


for dis-bssu;
DISPLAY-BSSU:LTG=1,LTU=2,SLOT=121;
H500: AMO BSSU STARTED
CIRCUIT 0 :
+==============================================================================+
| 24 HOUR TOTAL STATISTICS FOR TMDN/DIU2U LTG.LTU.EBT : 1 .2 .121
+------------------------------------------------------------------------------+
| ESF 2492 |
| ES 0 FS 5400 |
| BES 0 OES 2198 |
| US 0 DS 0 |
+------------------------------------------------------------------------------+
| LOOPBACK STATUS: |
| |
| LOCAL : SET PAYLOAD : CLEAR |
| REMOTE REQUEST : CLEAR |
+------------------------------------------------------------------------------+
| |
| ALARM STATUS : NO ERRORS(GREEN) |
+------------------------------------------------------------------------------+
CIRCUIT 1 :
+==============================================================================+
| 24 HOUR TOTAL STATISTICS FOR TMDN/DIU2U LTG.LTU.EBT : 1 .2 .121
+------------------------------------------------------------------------------+
| ESF 1 |
| ES 1 FS 0 |
| BES 0 OES 1 |
| US 0 DS 0 |
+------------------------------------------------------------------------------+
| LOOPBACK STATUS: |
| |
| LOCAL : CLEAR PAYLOAD : SET |
| REMOTE REQUEST : CLEAR |
+------------------------------------------------------------------------------+
| |
| ALARM STATUS : NO ERRORS(GREEN) |
+------------------------------------------------------------------------------+

AMO-BSSU -111 BOARD SWITCH, SWITCHING UNIT
DISPLAY COMPLETED;

any suggestion.

 

[donb01]

Yeah - You're definitely taking errors. I never know where these errors come from because I yell at AT&T and they fix it. My assumption is poor signal quality / data loss on the circuit.

You could check all your connections - if you have a CSU in between and it has settings for circuit distance on it you might check that. I have keys, and the first thing I will do if I'm taking errors is reseat the smart jack for the circuit in question and see if it clears - or if you have a smart jack make sure all the lights on the front are green and no amber - if there are amber lights report it to your carrier...



Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[LoPath]

I get lots of ESF errors, but never any serious enough to take the circuit down.
Frame slips (FS) are typically indicative of a clocking problem. I don't know a whole lot about how all of that is configured in the 4K, but I'd check that out. DIS-REFTA will show how the clocking is setup.


LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4, Xpressions, Contact Center

 

[donb01]

I know if the system has a PRI circuit for CO trunking it is typically best to use that for your clocking signal. In absence of that, if you have a circuit where one side is Master and the other is Slave you should take the clocking from the Master side.

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[RICHTz]

Hello All,

find display REFTA for the circuit which has the error.

<DISPLAY-REFTA:TYPE=CIRCUIT,PEN=1-2-121-0;
DISPLAY-REFTA:TYPE=CIRCUIT,PEN=1-2-121-0;
H500: AMO REFTA STARTED
+-------------------------------------------------------------------------+
| R E F E R E N C E C L O C K C I R C U I T S |
+--------------+---------+----------+---+------+------+------+-----+------+
| PEN | MODULE | DEVICE |PRI|ERROR |BLOCK |SUPP. |READY|SRCGRP|
| | | | | | | |BUT | |
| | | | | | | |ASYN.| |
+--------------+---------+----------+---+------+------+------+-----+------+
| 1- 2-121- 0 | DIUT2-M | S1CONN | 0| 9785| N | | N | 1|
+--------------+---------+----------+---+------+------+------+-----+------+

AMO-REFTA-111 REFERENCE CLOCK TABLE
DISPLAY COMPLETED;
<

Thanks