pri-group timeslots issue

Unanswered Question
Aug 23rd, 2010

Hello, collegues,

on my PRI E1 controller I see following: pri-group timeslots 1-12,16

but from telco we get 30 channels, so I tried to configure it:

no pri-group timeslots 1-12,16

pri-group timeslots 1-14,16-31

after that I get via debug isdn q931  periodically:

isdn BAD FRAME()

.....

and #sh isdn status

shows  that Layer 1 Status:         DEACTIVATED

I can change this situation only by reloading router. Why I can't set all time slots (excluding D-channel #15)?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3.3 (4 ratings)
Loading.
Paolo Bevilacqua Mon, 08/23/2010 - 05:46

You should configure:

pri-group

No other options are necessary.

Bad frames may be due to transmission errors. Send "show controllers E1".

Andrey128 Mon, 08/23/2010 - 06:09

after changing:

show controllers E1
E1 0/2/0 is up.
  Applique type is Channelized E1 - balanced
  No alarms detected.
  alarm-trigger is not set
  Version info Firmware: 20051006, FPGA: 20, spm_count = 0
  Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
  CRC Threshold is 320. Reported from firmware  is 320.
  Data in current interval (131 seconds elapsed):
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 31 Unavail Secs
  Total Data (last 3 15 minute intervals):
     0 Line Code Violations, 1 Path Code Violations,
     25 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
     26 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 8 Unavail Secs

--------------------------------------------------------------------------------------------------------------------------

show isdn status

Global ISDN Switchtype = primary-net5
ISDN Serial0/2/0:15 interface
        dsl 0, interface ISDN Switchtype = primary-net5
    Layer 1 Status:
        ACTIVE
    Layer 2 Status:
        TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 0 CCBs = 0
    The Free Channel Mask:  0xBFFF3FFF
    Number of L2 Discards = 0, L2 Session ID = 0

--------------------------------------------------------------------------------------------------------------------------

debug isdn q931

periodically shows following:

#BAD FRAME()
#BAD FRAME()
#BAD FRAME()
#BAD FRAME()
#BAD FRAME()
#BAD FRAME()
ISDN Se0/2/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2

--------------------------------------------------------------------------------------------------------------------------

before changing:

sh controllers E1
E1 0/2/0 is up.
  Applique type is Channelized E1 - balanced
  No alarms detected.
  alarm-trigger is not set
  Version info Firmware: 20051006, FPGA: 20, spm_count = 0
  Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
  CRC Threshold is 320. Reported from firmware  is 320.
  Data in current interval (699 seconds elapsed):
     0 Line Code Violations, 0 Path Code Violations
     0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
  Total Data (last 2 15 minute intervals):
     0 Line Code Violations, 1 Path Code Violations,
     25 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
     26 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

Paolo Bevilacqua Mon, 08/23/2010 - 06:25

Configure

network-clock-select 1 e1 0/2/0

You should also update IOS, what you have is very old.

ADAM CRISP Mon, 08/23/2010 - 06:09

Hi Andrey,

Our E1 controllers look like this in the UK

controller E1 0/0/0
pri-group timeslots 1-31
!

and the ISDN timers set :

interface Serial0/0/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn timer T309 400000
isdn incoming-voice voice
isdn T309-enable
isdn send-alerting
isdn sending-complete
isdn reject cause 34
no cdp enable
!

Adam

Andrey128 Mon, 08/23/2010 - 07:02

Adam, I used that configuration it did'n change the situation.

I'll update IOS, I think it will help.

Thanks for assistance!

ADAM CRISP Mon, 08/23/2010 - 07:08

OK. But I'd be surprised if the IOS revision upgrade helps, ISDN has been around a while.

You could try switching off CRC:

controller E1 0/0/0
framing NO-CRC4
pri-group timeslots 1-31

regards

Paolo Bevilacqua Mon, 08/23/2010 - 07:23

OK. But I'd be surprised if the IOS revision upgrade helps, ISDN has been around a while.

It helps quite often indeed.

You could try switching off CRC:

If he does that, circuit will not come up at all.

Note: your config example as few unnecessary commands.

Steven Holl Mon, 08/23/2010 - 07:25

It looks like L2 is down.  You should collect 'debug isdn q921' and look at the output to get a detailed insight as to what is specifically occurring at that layer.

Verify ISDN switch type is correct, and make sure the other side is set to network side (which if this is a provider, they should be).  You can set this side to network side, if needed, with 'isdn protocol-emulate network' under the D channel.

-Steve

Andrey128 Mon, 08/23/2010 - 08:05

actually

framing no-crc4

was used before any changes (telco confirmed this isdn-parametr, I tried with command "framing crc4", it doesn't work).

I got

debug isdn q921 detail

(if smb. wants to read this bunch of data ) :

ISDN  Q921d: isdn_from_driver_process: QUEUE_EVENT
ISDN Se0/2/0:15 Q921: User RX <- BAD FRAME(0x00017F)
ISDN Se0/2/0:15 Q921d: process_rxdata: Frame sent to L2
ISDN  Q921d: isdn_from_driver_process: event_count 1
ISDN Se0/2/0:15 Q921d: srl_send_l2_pak:
        source_id = Q.921 0x0000, dest_id = ME 0x0700, prim = MDL_ERR_IND 0x0691
        priv_len = 4 int_id = 0x66DCE980 datasize = 17
ISDN Se0/2/0:15 Q921d: data =
   66DCE980070000000691041400010000
    4C

ISDN  Q921d: isdn_from_driver_process: QUEUE_EVENT
ISDN Se0/2/0:15 Q921: User RX <- BAD FRAME(0x00017F)
ISDN Se0/2/0:15 Q921d: process_rxdata: Frame sent to L2
ISDN  Q921d: isdn_from_driver_process: event_count 1
ISDN Se0/2/0:15 Q921d: srl_send_l2_pak:
        source_id = Q.921 0x0000, dest_id = ME 0x0700, prim = MDL_ERR_IND 0x0691
        priv_len = 4 int_id = 0x66DCE980 datasize = 17
ISDN Se0/2/0:15 Q921d: data =
    66DCE980070000000691047400010000
    4C

ISDN Se0/2/0:15 Q921d: handle_mail: setting pkt to NULL
ISDN Se0/2/0:15 Q921: L2_EstablishDataLink: sending SABME
ISDN  Q921d: isdn_l2d_srq_process: QUEUE_EVENT
ISDN Se0/2/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
ISDN  Q921d: isdn_l2d_srq_process: event_count 1
ISDN  Q921d: l2_timer: timer (0x671795DC), timer_type (0x1240)
ISDN  Q921d: isdn_l2d_srq_process: QUEUE_EVENT
ISDN Se0/2/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
ISDN  Q921d: isdn_l2d_srq_process: event_count 1

ISDN  Q921d: isdn_from_driver_process: QUEUE_EVENT
ISDN Se0/2/0:15 Q921: User RX <- BAD FRAME(0x00017F)
ISDN Se0/2/0:15 Q921d: process_rxdata: Frame sent to L2
ISDN  Q921d: isdn_from_driver_process: event_count 1
ISDN Se0/2/0:15 Q921d: srl_send_l2_pak:
        source_id = Q.921 0x0000, dest_id = ME 0x0700, prim = MDL_ERR_IND 0x0691
        priv_len = 4 int_id = 0x66DCE980 datasize = 17
ISDN Se0/2/0:15 Q921d: data =
    66DCE980070000000691044300010000
    4C

ISDN  Q921d: l2_timer: timer (0x671795DC), timer_type (0x1240)
ISDN Se0/2/0:15 Q921d: S5_T200_EXPIRY: dlcb->N200=3 dlcb->RC=1
ISDN  Q921d: isdn_l2d_srq_process: QUEUE_EVENT
ISDN Se0/2/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
ISDN  Q921d: isdn_l2d_srq_process: event_count 1
ISDN  Q921d: isdn_from_driver_process: QUEUE_EVENT
ISDN Se0/2/0:15 Q921: User RX <- BAD FRAME(0x00017F)
ISDN Se0/2/0:15 Q921d: process_rxdata: Frame sent to L2
ISDN  Q921d: isdn_from_driver_process: event_count 1
ISDN Se0/2/0:15 Q921d: srl_send_l2_pak:
        source_id = Q.921 0x0000, dest_id = ME 0x0700, prim = MDL_ERR_IND 0x0691
        priv_len = 4 int_id = 0x66DCE980 datasize = 17
ISDN Se0/2/0:15 Q921d: data =
   66DCE980070000000691047400010000
    4C

Steven Holl Mon, 08/23/2010 - 08:14

L2 isn't coming up, because the outbound SABME is not getting a UA response from the other side.  Or it is responding, and the frame is getting corrupt before it reaches the router.

* sh controller e1 reports no errors now, through this, right?  Everything shows all 0's?

* Ensure that the other side of this circuit is configured for network side (recieve SABME and respond with UA).

* Worth a shot to try confiugring your router for network side, just to see what happens.

* Call provider, and have them read off to you what linecoding, framing, and ISDN protocol type is being used.  Make sure these settings match what you have configured on your side.

Can the provider come on site with a T1 tester and see if they are able to establish L2 on this circuit?

Paolo Bevilacqua Mon, 08/23/2010 - 08:17

Steven is right above (post rated), likely your telco has somethign very wrong on their side.

They will claim that is not the case, you must stand firm until they come onsite if necessary.

Note: I would not recommend you set network-side even for a test, as that is NEVER necessary on a normal telco-user circuit, and is not your responsability to correct their mistakes.

Actions

This Discussion