Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Webcast-Catalyst9k
New Member

ISDN Troubleshooting

I am having a problem with a new ISDN line. I am not able to get the Layer 1 status to go "ACTIVE". I have had telco verify switch type and SPIDs and have had them retest the circuit. Each time they are able to test successfully. I have even followed the Layer 1 troubleshooting urls but have had no luck. My config is below as well as some other information. I have tested the hardware on another ISDN circuit and had no problems getting layers 1&2 up. Any help would be greatly appreciated...

RTRxx#

RTRxx#

RTRxx#sh run

Building configuration...

Current configuration : 1671 bytes

!

version 12.2

service nagle

no service pad

service timestamps debug datetime msec

service timestamps log datetime msec

service password-encryption

!

hostname RTRxx

!

logging queue-limit 100

enable secret xxxxx

!

username xxxxxxx

ip subnet-zero

!

!

no ip domain-lookup

!

isdn switch-type basic-ni

!

!

!

interface FastEthernet0/0

description LAN

ip address 10.20.xx.xx 255.255.255.0

speed auto

full-duplex

no cdp enable

!

interface BRI0/0

description ISDN to

ip address xx.xx.xxx.90 255.255.255.252

encapsulation ppp

no ip route-cache

no ip mroute-cache

dialer idle-timeout 300

dialer map ip xx.xx.xxx.89 name RTRBxy broadcast xxxxxx0426

dialer map ip xx.xx.xxx.89 name RTRBxy broadcast xxxxxx0258

dialer hold-queue 5

dialer load-threshold 10 either

dialer-group 1

isdn switch-type basic-ni

isdn tei-negotiation first-call (Tried first with out)

isdn spid1 xxxxxx27130101

isdn spid2 xxxxxx27810101

isdn fast-rollover-delay 2

no fair-queue

compress stac

no cdp enable

ppp authentication pap chap

ppp multilink

!

router eigrp xxxxx

network xx.xx.xx.xx

no auto-summary

!

no ip classless

ip http server

!

dialer-list 1 protocol ip permit

no cdp run

!

end

RTRxx#sh ver

Cisco Internetwork Operating System Software

IOS (tm) C2600 Software (C2600-I-M), Version 12.2(16a), RELEASE SOFTWARE (fc2)

Copyright (c) 1986-2003 by cisco Systems, Inc.

Compiled Fri 18-Apr-03 19:25 by pwade

Image text-base: 0x8000808C, data-base: 0x80A0EE84

ROM: System Bootstrap, Version 12.1(3r)T2, RELEASE SOFTWARE (fc1)

RTRxx uptime is 0 minutes

System returned to ROM by reload

System image file is "flash:c2600-i-mz.122-16a.bin"

cisco 2620 (MPC860) processor (revision 0x600) with 28672K/4096K bytes of memory.

Processor board ID JAD054807C2 (609638217)

M860 processor: part number 0, mask 49

Bridging software.

X.25 software, Version 3.0.0.

Basic Rate ISDN software, Version 1.1.

1 FastEthernet/IEEE 802.3 interface(s)

1 ISDN Basic Rate interface(s)

32K bytes of non-volatile configuration memory.

8192K bytes of processor board System flash (Read/Write)

Configuration register is 0x2102

RTRxx#conf t

Enter configuration commands, one per line. End with CNTL/Z.

RTRxx(config)#int br0/0

RTRxx(config-if)#shut

RTRxx(config-if)#

*Mar 1 00:01:31.295: %LINK-5-CHANGED: Interface BRI0/0, changed state to administratively down

*Mar 1 00:01:31.295: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to down

*Mar 1 00:01:31.295: %LINK-3-UPDOWN: Interface BRI0/0:2, changed state to down

*Mar 1 00:01:32.299: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0, changed state to down

RTRxx(config-if)#

RTRxx(config-if)#no shut

RTRxx(config-if)#

RTRxx(config-if)#

*Mar 1 00:01:37.939: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to down

*Mar 1 00:01:37.939: %LINK-3-UPDOWN: Interface BRI0/0:2, changed state to down

*Mar 1 00:01:37.991: %LINK-3-UPDOWN: Interface BRI0/0, changed state to up

RTRxx(config-if)#

RTRxx(config-if)#

RTRxx(config-if)#end

RTRxx#

*Mar 1 00:01:46.363: %SYS-5-CONFIG_I: Configured from console by console

RTRxx#

RTRxx#sh debug

RTRxx#sh isdn stat

RTRxx#sh isdn status

Global ISDN Switchtype = basic-ni

ISDN BRI0/0 interface

dsl 0, interface ISDN Switchtype = basic-ni

Layer 1 Status:

ACTIVATING

Layer 2 Status:

TEI = 255, Ces = 1, SAPI = 0, State = ESTABLISH_AWAITING_TEI

TEI Not Assigned, ces = 1, state = 1(terminal down)

spid1 configured, no LDN, spid1 NOT sent, spid1 NOT valid

TEI Not Assigned, ces = 2, state = 1(terminal down)

spid2 configured, no LDN, spid2 NOT sent, spid2 NOT valid

Layer 3 Status:

0 Active Layer 3 Call(s)

CCB:callid=8019, sapi=0, ces=1, B-chan=1, calltype=DATA

Active dsl 0 CCBs = 1

The Free Channel Mask: 0x80000002

Total Allocated ISDN CCBs = 1

RTRxx#sh isdn status

Global ISDN Switchtype = basic-ni

ISDN BRI0/0 interface

dsl 0, interface ISDN Switchtype = basic-ni

Layer 1 Status:

ACTIVATING

Layer 2 Status:

TEI = 255, Ces = 1, SAPI = 0, State = ESTABLISH_AWAITING_TEI

TEI Not Assigned, ces = 1, state = 1(terminal down)

spid1 configured, no LDN, spid1 NOT sent, spid1 NOT valid

TEI Not Assigned, ces = 2, state = 1(terminal down)

spid2 configured, no LDN, spid2 NOT sent, spid2 NOT valid

Layer 3 Status:

0 Active Layer 3 Call(s)

CCB:callid=801A, sapi=0, ces=1, B-chan=1, calltype=DATA

Active dsl 0 CCBs = 1

The Free Channel Mask: 0x80000002

Total Allocated ISDN CCBs = 1

RTRxx#sh isdn status

Global ISDN Switchtype = basic-ni

ISDN BRI0/0 interface

dsl 0, interface ISDN Switchtype = basic-ni

Layer 1 Status:

DEACTIVATED

Layer 2 Status:

Layer 2 NOT Activated

TEI Not Assigned, ces = 1, state = 1(terminal down)

spid1 configured, no LDN, spid1 NOT sent, spid1 NOT valid

TEI Not Assigned, ces = 2, state = 1(terminal down)

spid2 configured, no LDN, spid2 NOT sent, spid2 NOT valid

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 0 CCBs = 0

The Free Channel Mask: 0x80000003

Total Allocated ISDN CCBs = 0

RTRxx#sh isdn status

Global ISDN Switchtype = basic-ni

ISDN BRI0/0 interface

dsl 0, interface ISDN Switchtype = basic-ni

Layer 1 Status:

ACTIVATING

Layer 2 Status:

TEI = 255, Ces = 1, SAPI = 0, State = ESTABLISH_AWAITING_TEI

TEI Not Assigned, ces = 1, state = 1(terminal down)

spid1 configured, no LDN, spid1 NOT sent, spid1 NOT valid

TEI Not Assigned, ces = 2, state = 1(terminal down)

spid2 configured, no LDN, spid2 NOT sent, spid2 NOT valid

Layer 3 Status:

0 Active Layer 3 Call(s)

CCB:callid=801B, sapi=0, ces=1, B-chan=1, calltype=DATA

Active dsl 0 CCBs = 1

The Free Channel Mask: 0x80000002

11 REPLIES

Re: ISDN Troubleshooting

When the provider tested the circuit, did a tech come to the site to do testing , or did they do it remotely? While testing where they able to loop the demarc and the equipment, or only the demarc ?

Give a show controller bri and paste the output for further troubleshooting.

Try clearing the bri interface using "clear int bri 0" and see if the problem still persists.

Ask theprovider to loop your equipment and see if they are able to see your equipment.

New Member

Re: ISDN Troubleshooting

Yes there was a tech out and he tested it at the demarc. They have not tried to loop the demarc or equipment.

RTR#sh controllers br 0/0

BRI unit 0:BRI unit 0 with U interface:

Layer 1 internal state is DEACTIVATED

Layer 1 U interface is DEACTIVATED.

ISDN Line Information:

Last C/I from ISDN transceiver:

DC:Deactivation Confirmation

Last C/I to ISDN transceiver:

DI:Deactivation Indication

Current EOC commands:

RTN - Return to normal

Received overhead bits: AIB=1, UOA=1, FEBE=1, DEA=1, ACT=1

Errors: Receive [NEBE]=0, Transmit [FEBE]=0

Siemens 2091 read-only registers:

ISTA 0 MOR FF MOSR 0 CIRI 3F CIRU 3F

Siemens 2091 write-only registers - last values written:

MASK 96 STCR 15 MOX FF DWU FF ADF2 28 RSVD 0 WB1U 0 WB2U 0

WB1I 0 WB2I 0 MOCR A0 DWI FF CIWU FF CIWI FF ADF 10 SWST D

D Channel Information:

idb at 0x8104FB84, driver data structure at 0x810BB114

Siemens Chip Version 0x3

SIEMENS Registers:

Status Register [STAR]=0x4A, Mode Register [MODE]=0xCA

Serial Port Control Register [SPCR]=0x0

Additional Feature Register [ADF2]=0x80

RX Buffer Descriptor is at 0x810BB4B4, Buffer size 1524

pak=0x8105552C data_ptr=0x1DA5154 partial_size=0x0

TX Buffer Descriptor is at 0x810BB4F8

pak=0x0 data_ptr=0x0 partial_size=0x0

0 missed datagrams, 0 overruns

0 bad datagram encapsulations, 0 memory errors

0 transmitter underruns 0 d channel collisions

B1 Channel Information:

idb at 0x81052B9C, driver data structure at 0x810BB760

SCC Registers:

General [GSMR]=0x2:0x00000000, Protocol-specific [PSMR]=0x8

Events [SCCE]=0x0000, Mask [SCCM]=0x0000, Status [SCCS]=0x00

Transmit on Demand [TODR]=0x0, Data Sync [DSR]=0x7E7E

Receive Ring

rmd(68012830): status 9000 length 60C address 1C48124

rmd(68012838): status 9000 length 60C address 1C47AA4

rmd(68012840): status 9000 length 60C address 1C47424

rmd(68012848): status 9000 length 60C address 1C66B64

rmd(68012850): status 9000 length 60C address 1C664E4

rmd(68012858): status 9000 length 60C address 1C65E64

rmd(68012860): status 9000 length 60C address 1C657E4

rmd(68012868): status 9000 length 60C address 1C65164

rmd(68012870): status 9000 length 60C address 1C64AE4

rmd(68012878): status 9000 length 60C address 1C64464

rmd(68012880): status 9000 length 60C address 1C63DE4

rmd(68012888): status 9000 length 60C address 1C63764

rmd(68012890): status 9000 length 60C address 1C630E4

rmd(68012898): status 9000 length 60C address 1C62A64

rmd(680128A0): status 9000 length 60C address 1C623E4

rmd(680128A8): status B000 length 60C address 1C61D64

Transmit Ring

tmd(680128B0): status 0 length 0 address 0

tmd(680128B8): status 0 length 0 address 0

tmd(680128C0): status 0 length 0 address 0

tmd(680128C8): status 0 length 0 address 0

tmd(680128D0): status 0 length 0 address 0

tmd(680128D8): status 0 length 0 address 0

tmd(680128E0): status 0 length 0 address 0

tmd(680128E8): status 0 length 0 address 0

tmd(680128F0): status 0 length 0 address 0

tmd(680128F8): status 0 length 0 address 0

tmd(68012900): status 0 length 0 address 0

tmd(68012908): status 0 length 0 address 0

tmd(68012910): status 0 length 0 address 0

tmd(68012918): status 0 length 0 address 0

tmd(68012920): status 0 length 0 address 0

tmd(68012928): status 2000 length 0 address 0

SCC GENERAL PARAMETER RAM (at 0x68013C00)

Rx BD Base [RBASE]=0x2830, Fn Code [RFCR]=0x18

Tx BD Base [TBASE]=0x28B0, Fn Code [TFCR]=0x18

Max Rx Buff Len [MRBLR]=1548

Rx State [RSTATE]=0x0, BD Ptr [RBPTR]=0x0

Tx State [TSTATE]=0x4000, BD Ptr [TBPTR]=0x0

SCC HDLC PARAMETER RAM (at 0x68013C38)

CRC Preset [C_PRES]=0xFFFF, Mask [C_MASK]=0xF0B8

Errors: CRC [CRCEC]=0, Aborts [ABTSC]=0, Discards [DISFC]=0

Nonmatch Addr Cntr [NMARC]=0

Retry Count [RETRC]=0

Max Frame Length [MFLR]=1608

Rx Int Threshold [RFTHR]=0, Frame Cnt [RFCNT]=0

User-defined Address 0000/0000/0000/0000

User-defined Address Mask 0x0000

0 missed datagrams, 0 overruns

0 bad datagram encapsulations, 0 memory errors

0 transmitter underruns 0 d channel collisions

B2 Channel Information:

idb at 0x81056540, driver data structure at 0x810BBBB0

SCC Registers:

General [GSMR]=0x2:0x00000000, Protocol-specific [PSMR]=0x8

Events [SCCE]=0x0000, Mask [SCCM]=0x0000, Status [SCCS]=0x00

Transmit on Demand [TODR]=0x0, Data Sync [DSR]=0x7E7E

Interrupt Registers:

Config [CICR]=0x00367F80, Pending [CIPR]=0x04000002

Mask [CIMR]=0x00200000, In-srv [CISR]=0x00000000

Command register [CR]=0x5C0

Port A [PADIR]=0x00C0, [PAPAR]=0x01C0

[PAODR]=0x0040, [PADAT]=0xFFFF

Port B [PBDIR]=0x0000F, [PBPAR]=0x0000E

[PBODR]=0x00000, [PBDAT]=0x3FFFD

Port C [PCDIR]=0x00C, [PCPAR]=0x800

[PCSO]=0x000, [PCDAT]=0x7F2, [PCINT]=0xFFF

Receive Ring

rmd(68012B30): status 9000 length 60C address 1C616E4

rmd(68012B38): status 9000 length 60C address 1C61064

rmd(68012B40): status 9000 length 60C address 1C609E4

rmd(68012B48): status 9000 length 60C address 1C60364

rmd(68012B50): status 9000 length 60C address 1C5FCE4

rmd(68012B58): status 9000 length 60C address 1C5F664

rmd(68012B60): status 9000 length 60C address 1C5EFE4

rmd(68012B68): status 9000 length 60C address 1C5E964

rmd(68012B70): status 9000 length 60C address 1C5E2E4

rmd(68012B78): status 9000 length 60C address 1C5DC64

rmd(68012B80): status 9000 length 60C address 1C5D5E4

rmd(68012B88): status 9000 length 60C address 1C5CF64

rmd(68012B90): status 9000 length 60C address 1C5C8E4

rmd(68012B98): status 9000 length 60C address 1C5C264

rmd(68012BA0): status 9000 length 60C address 1C5BBE4

rmd(68012BA8): status B000 length 60C address 1C5B564

Transmit Ring

tmd(68012BB0): status 0 length 0 address 0

tmd(68012BB8): status 0 length 0 address 0

tmd(68012BC0): status 0 length 0 address 0

tmd(68012BC8): status 0 length 0 address 0

tmd(68012BD0): status 0 length 0 address 0

tmd(68012BD8): status 0 length 0 address 0

tmd(68012BE0): status 0 length 0 address 0

tmd(68012BE8): status 0 length 0 address 0

tmd(68012BF0): status 0 length 0 address 0

tmd(68012BF8): status 0 length 0 address 0

tmd(68012C00): status 0 length 0 address 0

tmd(68012C08): status 0 length 0 address 0

tmd(68012C10): status 0 length 0 address 0

tmd(68012C18): status 0 length 0 address 0

tmd(68012C20): status 0 length 0 address 0

tmd(68012C28): status 2000 length 0 address 0

SCC GENERAL PARAMETER RAM (at 0x68013F00)

Rx BD Base [RBASE]=0x2B30, Fn Code [RFCR]=0x18

Tx BD Base [TBASE]=0x2BB0, Fn Code [TFCR]=0x18

Max Rx Buff Len [MRBLR]=1548

Rx State [RSTATE]=0x0, BD Ptr [RBPTR]=0x0

Tx State [TSTATE]=0x4000, BD Ptr [TBPTR]=0x0

SCC HDLC PARAMETER RAM (at 0x68013F38)

CRC Preset [C_PRES]=0xFFFF, Mask [C_MASK]=0xF0B8

Errors: CRC [CRCEC]=0, Aborts [ABTSC]=0, Discards [DISFC]=0

Nonmatch Addr Cntr [NMARC]=0

Retry Count [RETRC]=0

Max Frame Length [MFLR]=1608

Rx Int Threshold [RFTHR]=0, Frame Cnt [RFCNT]=0

User-defined Address 0000/0000/0000/0000

User-defined Address Mask 0x0000

0 missed datagrams, 0 overruns

0 bad datagram encapsulations, 0 memory errors

0 transmitter underruns 0 d channel collisions

I have tried clearing the interface many times but to no avail...

I will definately have them try to loop my equipment.

Thanks

New Member

Re: ISDN Troubleshooting

The things that jump out at me are: no local phone# on SPIDs, also EIGRP does not like ISDN connections("HELLOs"), might want to use passive-interface and use static routes to remote site/default routes back to core. OSPF can use Demand-Circuit that suppresses hellos/LSAs, not sure about EIGRP.

Hope this helps!

Silver

Re: ISDN Troubleshooting

Your router is not communicating with the switch . Have the provider dispatched to the site and plug his test set in to the demarc . If he tests good have him plug in to cable that is attached to the router .

Also you find out if there is an extended demarc. If there is the Lec is only going to test from where the line is brought in to the building . Usually the line are brought in to the basement. If this is the case and the equipment is on another floor you most likely have a problem on the extended demarc

New Member

Re: ISDN Troubleshooting

The provider has been out several times and is always able to test successfully to the jack.

They have tested all the way to the router connection and are able to always able to get connected. One thing that is different from all the ISDN circuits we currently use (other than it is a totally different provider) is when you dial either SPID they are always busy, until telco comes out and connects. They are able to place voice calls but assure me the line is provisoned for voice and data. I can take the router and plug it into the ISDN at the corporate site and always get layers 1&2 up.

Thanks

Bronze

Re: ISDN Troubleshooting

I have had problems like this that did not clear up until the router was rebooted. Have you been able to try that?

New Member

Re: ISDN Troubleshooting

When ever I have a isdn issue I always dispatch a tech to the site with an external isdn tester and verify the spids an try to make a call if it cannot make a call it will give you a message no circuit available and so on.

hth

Dennis

Silver

Re: ISDN Troubleshooting

turn on debug bri , this is not intrusive at all , then bounce the bri , and paste in the results. I beleive the card may be faulty

New Member

Re: ISDN Troubleshooting

I would agree with you; however I thought the same thing and brought it back to the office and was able to get connected to an ISDN circuit we have and connected on layers 1&2. I will paste that in this afternoon.

Thanks

New Member

Re: ISDN Troubleshooting

Here is the exact equip plugged into a different ISDN line. I didn't change any settings, that is why the SPIDs aren't valid

RTR#sh isdn stat

Global ISDN Switchtype = basic-dms100

ISDN BRI0/0 interface

dsl 0, interface ISDN Switchtype = basic-dms100

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 80, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

I_Queue_Len 0, UI_Queue_Len 0

TEI 80, ces = 1, state = 4(await init)

spid1 configured, spid1 sent, spid1 NOT valid

TEI Not Assigned, ces = 2, state = 1(terminal down)

spid2 configured, spid2 NOT sent, spid2 NOT valid

Layer 3 Status:

0 Active Layer 3 Call(s)

CCB:callid=0, sapi=0, ces=1, B-chan=0, calltype=INTERNAL (BR0/0) SPC Call

Active dsl 0 CCBs = 1

The Free Channel Mask: 0x80000003

Here is the output from the router with proper SPIDS on the other circuit...

RTRB#sh isdn stat

Global ISDN Switchtype = basic-dms100

ISDN BRI0/0 interface

dsl 0, interface ISDN Switchtype = basic-dms100

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 80, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

I_Queue_Len 0, UI_Queue_Len 0

TEI = 89, Ces = 2, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

I_Queue_Len 0, UI_Queue_Len 0

TEI 80, ces = 1, state = 5(init)

spid1 configured, spid1 sent, spid1 valid

Endpoint ID Info: epsf = 0, usid = 0, tid = 1

TEI 89, ces = 2, state = 5(init)

spid2 configured, spid2 sent, spid2 valid

Endpoint ID Info: epsf = 0, usid = 1, tid = 1

Layer 3 Status:

2 Active Layer 3 Call(s)

CCB:callid=8042, sapi=0, ces=1, B-chan=1, calltype=DATA

CCB:callid=5, sapi=0, ces=1, B-chan=2, calltype=DATA

Active dsl 0 CCBs = 2

The Free Channel Mask: 0x80000000

The switch type is still wrong in the second isdn stat but the hardware appears to be working. I was able to place test calls on the second ISDN circuit with only the SPID changes. I would greatly appreciate any additional thoughts or ideas.

Thanks

New Member

Re: ISDN Troubleshooting

Thanks for everyones help. I finally got a tech out that knew a little more about ISDN circuits. He keeped telling me it just didn't look right even after he was able to dial out. He kep testing the line when foond the problem, the line came up and it is working great.

576
Views
0
Helpful
11
Replies
CreatePlease to create content