Hi everybody,
I just installed asterisk, but this NOTICE dont stop appearing on my log file;;
Feb 17 18:30:11 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary
D-channel of span 4
Feb 17 18:29:42 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary D-channel
of span 4
Feb 17 18:29:41 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary D-channel
of span 4
Feb 17 18:29:41 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary
D-channel of span 4
Feb 17 18:27:11 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary D-channel
of span 4
Feb 17 18:26:51 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary
D-channel of span 4
Feb 17 18:25:11 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary
D-channel of span 4
Feb 17 18:24:41 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary D-channel
of span 4
Feb 17 18:22:21 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary D-channel
of span 4
Feb 17 18:21:16 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary
D-channel of span 4
Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary
D-channel of span 4
Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary
D-channel of span 4
Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary
D-channel of span 4
Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary D-channel
of span 4
Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary
D-channel of span 4
Feb 17 18:21:14 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary
D-channel of span 4
Feb 17 18:21:14 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary
D-channel of span 4
Feb 17 18:21:14 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary
D-channel of span 4
Feb 17 18:21:13 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary D-channel
of span 4
Feb 17 18:21:12 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary
D-channel of span 4
Feb 17 18:21:11 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary
D-channel of span 4
Feb 17 18:21:01 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary
D-channel of span 4
And from time to time this is happening....
-- B-channel 0/1 successfully restarted on span 4
-- B-channel 0/2 successfully restarted on span 4
-- B-channel 0/3 successfully restarted on span 4
-- B-channel 0/4 successfully restarted on span 4
[...]
-- B-channel 0/29 successfully restarted on span 4
-- B-channel 0/30 successfully restarted on span 4
-- B-channel 0/31 successfully restarted on span 4
And the conversation stops.
Telco, with a traffic analyzer, says that the clock is sliding.
Does anybody knows what can it be? Hardware, software, transmission (conectors)
etc.... ?
Thanks in advance.
--
Alex G Robertson
NOC - Microlink
Some news..... It is not caused by transmission lines, conectors or anything like that. The telco tecnician just came here and analyzed the circuit and he got no erros! He sugested me to loop my PRI port in the balum attached in my asterisk box. And.... Surprise... I got the same errors! The error is on my hardware/software. []s Alex Robertson Alex G Robertson wrote:> Hi everybody, > > I just installed asterisk, but this NOTICE dont stop appearing on my log > file;; > > > Feb 17 18:30:11 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary > D-channel of span 4 > Feb 17 18:29:42 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary > D-channel of span 4 > Feb 17 18:29:41 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary > D-channel of span 4 > Feb 17 18:29:41 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary > D-channel of span 4 > Feb 17 18:27:11 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary > D-channel of span 4 > Feb 17 18:26:51 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary > D-channel of span 4 > Feb 17 18:25:11 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary > D-channel of span 4 > Feb 17 18:24:41 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary > D-channel of span 4 > Feb 17 18:22:21 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary > D-channel of span 4 > Feb 17 18:21:16 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary > D-channel of span 4 > Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary > D-channel of span 4 > Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary > D-channel of span 4 > Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary > D-channel of span 4 > Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary > D-channel of span 4 > Feb 17 18:21:15 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary > D-channel of span 4 > Feb 17 18:21:14 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary > D-channel of span 4 > Feb 17 18:21:14 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary > D-channel of span 4 > Feb 17 18:21:14 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary > D-channel of span 4 > Feb 17 18:21:13 NOTICE[1336]: PRI got event: HDLC Abort (6) on Primary > D-channel of span 4 > Feb 17 18:21:12 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary > D-channel of span 4 > Feb 17 18:21:11 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary > D-channel of span 4 > Feb 17 18:21:01 NOTICE[1336]: PRI got event: HDLC Bad FCS (8) on Primary > D-channel of span 4 > > > And from time to time this is happening.... > > -- B-channel 0/1 successfully restarted on span 4 > -- B-channel 0/2 successfully restarted on span 4 > -- B-channel 0/3 successfully restarted on span 4 > -- B-channel 0/4 successfully restarted on span 4 > [...] > -- B-channel 0/29 successfully restarted on span 4 > -- B-channel 0/30 successfully restarted on span 4 > -- B-channel 0/31 successfully restarted on span 4 > > And the conversation stops. > > > Telco, with a traffic analyzer, says that the clock is sliding. > > Does anybody knows what can it be? Hardware, software, transmission > (conectors) etc.... ? > > > Thanks in advance.-- Alex G Robertson NOC - Microlink
Eric Wieling
2005-Feb-22 06:59 UTC
[ nocadm ] Re: [Asterisk-Users] HDLC Bad FCS / HDLC Abort
Alex G Robertson wrote:>> >> Did you confirm you are not running graphics? (X, frame buffer, etc). >> Did you confirm you have unmasked IDE interrupts (-u1 to haparm)? > > > Yes and Yes. ;-) > > > # hdparm -i /dev/hd[ac] > > /dev/hda: > > Model=SAMSUNG SP1203N, FwRev=TL100-24, SerialNo=0836J1FX419316 > Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs } > RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4 > BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16 > CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=234493056 > IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120} > PIO modes: pio0 pio1 pio2 pio3 pio4 > DMA modes: mdma0 mdma1 mdma2 > UDMA modes: udma0 udma1 udma2 *udma3 udma4 udma5 > AdvancedPM=no WriteCache=enabled > Drive conforms to: (null):Try hdparm -v /dev/hda
Alex G Robertson
2005-Feb-22 07:05 UTC
[ nocadm ] Re: [Asterisk-Users] HDLC Bad FCS / HDLC Abort
>> Try hdparm -v /dev/hda > Here it is.... # hdparm -v /dev/hd[ac] /dev/hda: multcount = 16 (on) IO_support = 1 (32-bit) unmaskirq = 1 (on) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 8 (on) geometry = 14596/255/63, sectors = 234493056, start = 0 /dev/hdc: multcount = 16 (on) IO_support = 1 (32-bit) unmaskirq = 1 (on) using_dma = 1 (on) keepsettings = 0 (off) readonly = 0 (off) readahead = 8 (on) geometry = 14596/255/63, sectors = 234493056, start = 0 []s -- Alex G Robertson NOC - Microlink
tim panton wrote: [..]> Good luck with it. >I think I am lucky! ;-) We resolved the problem changing the Mother board to one with an Intel chipset. The first one had Via chipset. 1) At first, we changed the mother board by another with Intel chipset. This one can set udma2 (or udma3) from BIOS. It is set up to udma2. # ChannelBank 1 - T1 span=1,0,0,esf,b8zs fxoks=1-24 # ChannelBank 2 (Empty) - T1 span=2,0,0,esf,b8zs fxoks=25-48 # Empty - T1 span=3,0,0,esf,b8zs fxoks=49-72 # Telco E1/PRI span=4,0,0,ccs,hdb3 bchan=73-87 dchan=88 bchan=89-103 The messages "HDLC Bad FCS" and "HDLC Abort" stopped! 2) After that, we set up span 3 and 4 (3rd and 4th ports on the card) as E1. We are going to use 2 E1s/PRI (different Telcos) and 2 T1s (channelbank). [...] # Telco1 span=3,0,0,ccs,hdb3 bchan=... dchan=... bchan=... # Telco2 span=4,0,0,ccs,hdb3 bchan=... dchan=... bchan=... -> The jumpers were set to E1 and the channels were also correct. -> After each modification it was necessary to reboot and take off the power cable for modifications to take effect. What timing/clock configuration do you recomend us? Zero for everyone? span=1,0,0,esf,b8zs # T1 ChannelBank1 span=2,0,0,esf,b8zs # T1 ChannelBank2 span=3,0,0,ccs,hdb3 # E1 Telco1 span=4,0,0,ccs,hdb3 # E1 Telco2 By the way, could you explain in a better way what does these timing options (0, 1, 2) mean? -- Alex G Robertson NOC - Microlink