cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1675
Views
0
Helpful
4
Replies

New E1 Bouncing Up/Down

martin.j.davies
Level 1
Level 1

Hi,

I'm currently configuring a new ISDN circuit which is to be user for dial in access, which I can't get to stay up.  It constantly cycles between the following (Sh isdn status) AWAITING_ESTABLISHMENT > TEI_ASSIGNED and will every minute or 2 change to MULTIPLE_FRAME_ESTABLISHED but within 5 seconds changes to TIMER_RECOVERY.

It's configured the same as another router (at a different location) which works fine but the circuit is provided via a different provider, both router has same IOS version 15.0(1)M4.  This circuit has been tested in another device (server) and proved to work both dialing in and out.

Any help would be very much appreciated as I've run out of ideas........

Config is as follows. .....

network-clock-participate wic 0


isdn switch-type primary-net5


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

interface Serial0/0/0:15
ip unnumbered Loopback0
encapsulation ppp
dialer rotary-group 1
dialer-group 1
no snmp trap link-status
isdn switch-type primary-net5
isdn incoming-voice modem 64
isdn disconnect-cause 47
no fair-queue
no cdp enable

Log Show

*Apr 27 13:45:51.155: %CSM-5-PRI: delete PRI at 0/0/0:15 (index 0)
*Apr 27 13:45:51.155: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to down
*Apr 27 13:46:45.811: %CSM-5-PRI: add PRI at 0/0/0:15 (index 0)
*Apr 27 13:46:45.811: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to up

debug isdn q921

*Apr 27 13:47:01.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:02.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:03.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:04.815: %CSM-5-PRI: delete PRI at 0/0/0:15 (index 0)
*Apr 27 13:47:04.815: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to down
*Apr 27 13:47:09.815: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME
*Apr 27 13:47:09.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:10.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:11.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:12.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:18.815: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME
*Apr 27 13:47:18.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:19.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:20.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:21.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:27.815: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME
*Apr 27 13:47:27.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:28.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:29.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:30.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:36.815: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME
*Apr 27 13:47:36.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:37.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:38.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:39.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:45.815: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME
*Apr 27 13:47:45.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:46.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:47.475: ISDN Se0/0/0:15 Q921: User RX <- SABMEp sapi=0 tei=0
*Apr 27 13:47:47.475: ISDN Se0/0/0:15 Q921: User TX -> UAf sapi=0 tei=0
*Apr 27 13:47:47.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:48.471: ISDN Se0/0/0:15 Q921: User RX <- SABMEp sapi=0 tei=0
*Apr 27 13:47:48.471: ISDN Se0/0/0:15 Q921: User TX -> UAf sapi=0 tei=0
*Apr 27 13:47:48.815: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:49.475: ISDN Se0/0/0:15 Q921: User RX <- SABMEp sapi=0 tei=0
*Apr 27 13:47:49.475: ISDN Se0/0/0:15 Q921: User TX -> UAf sapi=0 tei=0
*Apr 27 13:47:50.479: ISDN Se0/0/0:15 Q921: User RX <- SABMEp sapi=0 tei=0
*Apr 27 13:47:50.479: ISDN Se0/0/0:15 Q921: S4_SABME: Sending UA
*Apr 27 13:47:50.479: %CSM-5-PRI: add PRI at 0/0/0:15 (index 0)
*Apr 27 13:47:50.479: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to up
*Apr 27 13:47:50.479: ISDN Se0/0/0:15 Q921: User TX -> UAf sapi=0 tei=0
*Apr 27 13:47:50.479: ISDN Se0/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=0 nr=0
*Apr 27 13:47:50.479: ISDN Se0/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=1 nr=0
*Apr 27 13:47:50.479: ISDN Se0/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=2 nr=0
*Apr 27 13:47:50.479: ISDN Se0/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=3 nr=0
*Apr 27 13:47:50.479: ISDN Se0/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=4 nr=0
*Apr 27 13:47:50.479: ISDN Se0/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=5 nr=0
*Apr 27 13:47:50.479: ISDN Se0/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=6 nr=0
*Apr 27 13:47:51.479: ISDN Se0/0/0:15 Q921: S7_T200_EXPIRY: VA = 0, VS = 7
*Apr 27 13:47:51.479: ISDN Se0/0/0:15 Q921: User TX -> INFOp sapi=0 tei=0, ns=6 nr=0
*Apr 27 13:47:52.479: ISDN Se0/0/0:15 Q921: User TX -> INFOp sapi=0 tei=0, ns=0 nr=0
*Apr 27 13:47:53.479: ISDN Se0/0/0:15 Q921: User TX -> INFOp sapi=0 tei=0, ns=0 nr=0
*Apr 27 13:47:54.479: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME
*Apr 27 13:47:54.479: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:55.479: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:56.479: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:57.479: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:47:58.479: %CSM-5-PRI: delete PRI at 0/0/0:15 (index 0)
*Apr 27 13:47:58.479: %ISDN-6-LAYER2DOWN: Layer 2 for Interface Se0/0/0:15, TEI 0 changed to downu al
*Apr 27 13:48:03.479: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME
*Apr 27 13:48:03.479: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Apr 27 13:48:04.479: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0l


Many Thanks

Martin

4 Replies 4

martin.j.davies
Level 1
Level 1

Apologies forgot to add

E1 0/0/0 is up.
  Applique type is Channelized E1 - balanced
  Description: xxxxxxxxx

  No alarms detected.
  alarm-trigger is not set
  Version info FPGA Rev: 08121917, FPGA Type: PRK1
  Framing is CRC4, Line Code is HDB3, Clock Source is Line.
  International Bit: 1, National Bits: 11111
  Data in current interval (402 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

Hi Martin,

Connection is bouncing at layer 2 level. Please add network-clock-select 1 E1 0/0/0 and "isdn tei-negotiation first-call" under Serial interface. Now on the debugs we see S7_T200_EXPIRY: VA = 0, VS = 7, which basically is a timer used by IOS to re-connect the session (session is timing out for some reason nr=0). Looks like ISDN Switch is not  ACK our frames.

Regards.

Thanks for the reply, I had previously enabled "network-clock-select 1 E1 0/0/0", it doens't solve the issue.  I don't have the option to apply the command "isdn tei-negotiation first-call"

router(config-if)#int serial 0/0/0:15

router(config-if)#isdn t?
T-Activate  T306              T309-enable  T310
timer       transition-delay  transparent

Any ideas?

Hi Martin,

That command is for BRIs only. The problem here is what I mentioned on my previous post, a layer 2 issue, ISDN Switch is not Acknowleding your layer 2 frames, check with them and ask if they see your router's frames. "network-clock-select" command is needed on this case.

Regards.