• News
  • Idefisk
  • Tools
  • Tutorials
  • Forum
  • Reviews
  • VoIP Providers
  • Archives
  • Gallery
ZOIPER softphone
AsteriskGuru Archives
Mailing List Archives
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

[Asterisk-Users] HDLC Bad FCS / HDLC Abort

 
   AsteriskGuru Archives Forum Index -> Asterisk-Users
View previous topic :: View next topic  
Author Message
alex at microlink.com.br
Guest





PostPosted: Fri Feb 18, 2005 9:13 am    Post subject: [Asterisk-Users] HDLC Bad FCS / HDLC Abort

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

Back to top
alex at microlink.com.br
Guest





PostPosted: Sat Feb 19, 2005 5:15 am    Post subject: [Asterisk-Users] HDLC Bad FCS / HDLC Abort

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:
Quote:
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

Back to top
asterisk_biz at deeptown.
Guest





PostPosted: Sat Feb 19, 2005 5:37 am    Post subject: [Asterisk-Users] HDLC Bad FCS / HDLC Abort

This is happens because of imperfect HDLC code. I am having the same in
my logs, but quite rare
and on spans which is idle. Therefore this is not an issue with PRIs itself.

I may be wrong, but telco technician checked my PRIs as well, and didn't
find any flaws.
I can tell you more. IT happens when server not being rebooted for quite
long time.
Right now I am rebooting server every day or two.


Alex G Robertson wrote:

Quote:
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.




--
All the Best!
Sergey.
=========================
Sergey Kuznetsov
President/CEO
High Intellectual Technologies, Inc.

Web: http://www.hitcalls.com
E-mail: sergey.kuznetsov@highintellect.com
Business phone: (416) 548-9700
Mobile phone: (647) 287-8448

Back to top
eric at fnords.org (Eric
Guest





PostPosted: Sat Feb 19, 2005 10:49 am    Post subject: [Asterisk-Users] HDLC Bad FCS / HDLC Abort

Yes. There are lots of messages in the mailing list archives
regarding this problem, some of them even include things to try. You
didn't see these messages when you searched the mailing list archives?

Alex G Robertson wrote:

Quote:
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.



Back to top
alex at microlink.com.br
Guest





PostPosted: Fri Feb 25, 2005 8:38 am    Post subject: [Asterisk-Users] HDLC Bad FCS / HDLC Abort

tim panton wrote:
[..]

Quote:
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

Back to top
Display posts from previous:   
   AsteriskGuru Archives Forum Index -> Asterisk-Users All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group
contact us at: support@asteriskguru.com - asterisKGuru.com © all rights reserved   |   *asterisk is registered trademark of © Digium™