[asterisk-users] Data provided by pri show spans and dahdi_tool do not match

[Olivier]

Hello,

On a 4 BRI Euro-ISDN TE/PtmP production system (Asterisk 1.6.1.18, Dahdi
2.5.0, Libpri 1.4.12), I sudently got the console cluttered with messages
like this:
PRI got event: HDLC Abort(6) on Primary D-Channel of span <foo>

Then a flow of messages (twice per second) like this:
PRI got event: HDLC Overrun(7) on Primary D-Channel of span 2

Contrary to the first one which concerned all of the 4 spans, the second
message type only concerned one span (span2).

So I stopped dahdi and asterisk, disabled span 2 and restarted everything.

No I see :
PRI span 1/0: Provisioned, Up, Active
PRI span 3/0: Provisioned, In Alarm, Up, Active
PRI span 4/0: Provisioned, Up, Active

With dahdi_tool main screen, I can exactly read
Alarms                         Span
OK                              HA8-0000
UNCONFIGURED         HA8-0000
OK                              HA8-0000
RED                            HA8-0000

With "pri intensive debug span 3", I'm getting:

[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: t203_expire
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c:
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: > TEI: 75 State
7(Multi-frame established)
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: > V(A)=3, V(S)=3, V(R)=1
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: > K=1, RC=0, l3_initiated=0,
reject_except=0, ack_pend=0
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: > T200_id=0, N200=3,
T203_id=0
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: > [ 00 97 01 03 ]
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: > Supervisory frame:
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: > SAPI: 00  C/R: 0 EA: 0
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: >  TEI: 075        EA: 1
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: > Zero: 0     S: 0 01: 1  [
RR (receive ready) ]
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: > N(R): 001 P/F: 1
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: > 0 bytes of data
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: -- Starting T200 timer
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c:
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: < TEI: 75 State 8(Timer
recovery)
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: < V(A)=3, V(S)=3, V(R)=1
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: < K=1, RC=0, l3_initiated=0,
reject_except=0, ack_pend=0
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: < T200_id=16384, N200=3,
T203_id=0
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: < [ 02 97 01 07 ]
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: < Supervisory frame:
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: < SAPI: 00  C/R: 1 EA: 0
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: <  TEI: 075        EA: 1
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: < Zero: 0     S: 0 01: 1  [
RR (receive ready) ]
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: < N(R): 003 P/F: 1
[Dec  6 10:32:58] VERBOSE[11461] chan_dahdi.c: < 0 bytes of data

With dahdi_scan :
dahdi_scan
[1]
active=yes
alarms=OK
description=HA8-0000
name=WCBRI/0/0
manufacturer=Digium
devicetype=HA8-0000
location=PCI Bus 04 Slot 07
basechan=1
totchans=3
irq=20
type=digital-TE
syncsrc=0
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=B8ZS,AMI,HDB3
framing_opts=ESF,D4,CCS,CRC4
coding=AMI
framing=CCS
[2]
active=yes
alarms=UNCONFIGURED
description=HA8-0000
name=WCBRI/0/1
manufacturer=Digium
devicetype=HA8-0000
location=PCI Bus 04 Slot 07
basechan=4
totchans=3
irq=20
type=digital-TE
syncsrc=0
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=B8ZS,AMI,HDB3
framing_opts=ESF,D4,CCS,CRC4
coding=
framing=CAS
[3]
active=yes
alarms=OK
description=HA8-0000
name=WCBRI/0/2
manufacturer=Digium
devicetype=HA8-0000
location=PCI Bus 04 Slot 07
basechan=7
totchans=3
irq=20
type=digital-TE
syncsrc=0
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=B8ZS,AMI,HDB3
framing_opts=ESF,D4,CCS,CRC4
coding=AMI
framing=CCS
[4]
active=yes
alarms=RED
description=HA8-0000
name=WCBRI/0/3
manufacturer=Digium
devicetype=HA8-0000
location=PCI Bus 04 Slot 07
basechan=10
totchans=3
irq=20
type=digital-TE
syncsrc=0
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=B8ZS,AMI,HDB3
framing_opts=ESF,D4,CCS,CRC4
coding=AMI
framing=CCS




I'm trying to understand what is going on.

My questions are:

1. Am I correct observing span status provided by pri show spans and
dahdi_tool, differ:
pri show spans says span 3 is in Alarm while dahdi_tool (and dahdi_scan)
say that span 4 is in Alarm.

2. Which tool would give me the most accurate reason why a Dahdi span is in
RED Alarm ?

3. Does the "pri intensive debug span 3" output above really belongs to
span 3 and to an In Alarm span ?

4. Suggestions ? Comments ?

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20111206/5fa3cd78/attachment.htm>