Hi,

Occasionally for a day our server will through lots of HDLC errors in the log and the PRI card with go into alarm.
I have done some searching and this seems to mostly caused from Hardware incompatibilities / IRQ sharing / Faulty card / Telco problem

The card will generally run for weeks at a time with no issues and then it has a bad day... and then good for some weeks or so.
I am trying to find which one is the cause of my problems.

169: 1399921290 1667044798 1646568485 1544999181   IO-APIC-level  wcte12xp0, wctdm24xxp0

Above is the line of my IRQ related to my cards (Full IRQ dump below). Does the above mean that my two Digium cards share the 169 IRQ?
I take it this is bad?

We have these cards in our asterisk server:
AEX2451E (Analogue lines)
TE121B (PRI ISDN line)

Thanks for your help.

LOG:
[Feb 25 16:05:22] NOTICE[26570] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Feb 25 16:05:22] NOTICE[26570] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
[Feb 25 16:05:22] NOTICE[26570] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
[Feb 25 16:05:36] NOTICE[26570] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Feb 25 16:05:36] NOTICE[26570] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Feb 25 16:05:37] NOTICE[26570] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Feb 25 16:05:37] NOTICE[26570] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Feb 25 16:05:37] NOTICE[26570] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Detected alarm on channel 1: Red Alarm
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Unable to disable echo cancellation on channel 1
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Detected alarm on channel 2: Red Alarm
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Unable to disable echo cancellation on channel 2
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Detected alarm on channel 3: Red Alarm
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Unable to disable echo cancellation on channel 3
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Detected alarm on channel 4: Red Alarm
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Unable to disable echo cancellation on channel 4
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Detected alarm on channel 5: Red Alarm
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Unable to disable echo cancellation on channel 5
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Detected alarm on channel 6: Red Alarm
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Unable to disable echo cancellation on channel 6
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Detected alarm on channel 7: Red Alarm
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Unable to disable echo cancellation on channel 7
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Detected alarm on channel 8: Red Alarm
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Unable to disable echo cancellation on channel 8
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Detected alarm on channel 9: Red Alarm
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Unable to disable echo cancellation on channel 9
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Detected alarm on channel 10: Red Alarm
[Feb 25 16:05:39] WARNING[26571] chan_zap.c: Unable to disable echo cancellation on channel 10
[Feb 25 16:05:39] NOTICE[26570] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 1
[Feb 25 16:05:39] WARNING[26570] chan_zap.c: No D-channels available!  Using Primary channel 16 as D-channel anyway!
[Feb 25 16:05:44] WARNING[26570] chan_zap.c: No D-channels available!  Using Primary channel 16 as D-channel anyway!
[Feb 25 16:06:28] NOTICE[26571] chan_zap.c: Alarm cleared on channel 1
[Feb 25 16:06:28] NOTICE[26571] chan_zap.c: Alarm cleared on channel 2


asterisk:~# cat /proc/interrupts
           CPU0       CPU1       CPU2       CPU3      
  0:       1472  743060701        114        112    IO-APIC-edge  timer
  1:        405          2          1          3    IO-APIC-edge  i8042
  8:          0          0          0          0    IO-APIC-edge  rtc
  9:          1          0          0          0   IO-APIC-level  acpi
 12:       1076        691          2          0    IO-APIC-edge  i8042
 14:         83          0          0          1    IO-APIC-edge  libata
 15:          0          0          0          0    IO-APIC-edge  libata
 74:          0          0          0          0   IO-APIC-level  uhci_hcd:usb1, uhci_hcd:usb3, ehci_hcd:usb5
 90:          0          0          0          0   IO-APIC-level  uhci_hcd:usb2, uhci_hcd:usb4
106:  115263410   86839619   38832711   22340356         PCI-MSI  eth0
114:   40956818   41973260   57827186   15209426         PCI-MSI  eth1
169: 1399921290 1667044798 1646568485 1544999181   IO-APIC-level  wcte12xp0, wctdm24xxp0
177:    2024852    1865838     574172          0   IO-APIC-level  aacraid
NMI:          0          0          0          0
LOC:  742903315  742903315  742899749  742899739
ERR:          0
MIS:          0


Regards

--
Daniel Johnson
Systems Administrator / Systems Development
Scanning Systems Australia

Scanning Systems Australia

Office: +61 7 3387 5555
Facsimile: +61 7 3387 5588
E-mail: da...@scanningsystems.com.au
Website: http://www.scanningsystems.com.au

_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to