[c-nsp] Problem with ISDN backup (stuck CCBs in 12.3(11)T?)

[Josh Duffek]

What does "sh isdn stat" say?

josh duffek    network engineer
consultantjd16 at ridemetro.org

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> bounces at puck.nether.net] On Behalf Of piestaga
> Sent: Monday, November 15, 2004 5:04 PM
> To: cisco-nsp at puck.nether.net
> Subject: RE: [c-nsp] Problem with ISDN backup (stuck CCBs in
12.3(11)T?)
> 
> Hi
> 
> I would like to come back to the problem I described within this
threat
> week
> ago.
> 
> I relocated the whole config to router 1603 (where bri is an build-in
> interface) and I configured the bacap capalility using only the bri
> interface (without dialer interface)
> 
> 
> After finishing the config on LAC and LNS everything seemed perfect.
> 
> The bri config includes the following lines:
> 
> interface BRI0
>  ip address 3.3.3.10 255.255.255.252
>  encapsulation ppp
>  dialer idle-timeout 30
>  dialer string 1234567
>  dialer-group 1
>  isdn switch-type basic-net3
>  ppp authentication pap
>  ppp pap sent-username USERNAME password 0 PASSWORD
> 
> 
> /routing to watched address 99.99.99.99 via BRI0
> primary links are within OSPF so the metric here must be >110/
> 
> ip route 99.99.99.99 255.255.255.255 BRI0 3.3.3.9 200
> 
> access-list 177 permit ip 50.50.50.0 0.0.0.255 host 99.99.99.99
> dialer-list 1 protocol ip list 177
> 
> 
> and it WORK !!!!
> 
> The BRI dial to ALC where after preauthentication proccess, the cal
lis
> terminated and next the L2TP from LAC to LNS is establish. THe LAN
> terminates L2TP and ppp session from CPE.
> 
> I enabled and disabled both primary links and backup prefectly comes u
> pand
> down each time.
> 
> So I decided to relocate the config to 1751 (with the WIC-1B-S/T card
> instead the build-in one).
> 
> And it stopped working.
> 
> 
> Exactly the same behaviour.
> The BRI tries to dial-up but the following message appeares:
> 
> host_disconnect_ack: Unfound B-channel on Disconnect_Ack call id
0x800D
> 
> The command "clear int bri0/0" did no t help.
> The only things that hel pis reload or (what is strange) entering the
> command:
> 
> no encapsulation hdlc
> (despite the fact that ppp is entered in interface config).
> 
> Unfortunatellu that remove the lines:
> 
> ppp authentication pap
> ppp pap sent-username USERNAME password 0 PASSWORD
> 
> out of the config. So I need put them again.
> 
> 
> Additionally, except the BRI triggered by the access list 177 (network
> 50.50.50.0 is still pinging 99.99.99.99) the established ISDN call did
not
> clear the idle timeout !!!!
> 
> Show dialer command entred during the active backup call shows that
the
> idle
> timeout is continously countered down.
> So (in my case) every 30 sec the call is reestablished.
> 
> 
> Guys please, any help because I am out of ideas what can be wrong.
> I thought that it is the config issue, but since the same config works
on
> other platform, I started susspecting the WIC or the way the WIC is
> supported on 12.3.(11T)
> 
> Regards
> Piestaga
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Mark Johnson [mailto:mljohnso at cisco.com]
> Sent: Monday, November 08, 2004 6:25 PM
> To: Josh Duffek; piestaga; cisco-nsp at puck.nether.net
> Cc: cisco-nas at puck.nether.net
> Subject: Re: [cisco-nas] RE: [c-nsp] Problem with ISDN backup (stuck
CCBs
> in
> 12.3(11)T?)
> 
> At 08:51 AM 11/8/2004 -0600, Josh Duffek wrote:
> 
> > > Global ISDN Switchtype = basic-net3
> > > ISDN BRI0/0 interface
> > >         dsl 0, interface ISDN Switchtype = basic-net3
> > >     Layer 1 Status:
> > >         ACTIVE
> > >     Layer 2 Status:
> > >         Layer 2 NOT Activated
> > >     Layer 3 Status:
> > >         0 Active Layer 3 Call(s)
> > >         CCB:callid=8097, sapi=0, ces=1, B-chan=1, calltype=DATA,
> > > hdlctype=HDLC-TRUNK
> > >         CCB:callid=8098, sapi=0, ces=1, B-chan=2, calltype=DATA,
> > > hdlctype=HDLC-TRUNK
> > >     Active dsl 0 CCBs = 2
> > >     The Free Channel Mask:  0x80000000
> > >     Total Allocated ISDN CCBs = 2
> 
> This is your problem; the question is what's causing it.  As Josh
says,
> the CCB's are hung (either the initial calls were not cleared
correctly,
> or they were but we still didn't clean up after ourselves).
> 
> VRF Dialer-Watch support was added in 12.3(7)T, but I'm not sure this
> new functionality would cause this problem.  It's more likely DW/ISDN
> related.
> 
> I don't see any bugs that seem relevant.  If possible, I would suggest
> you reproduce the problem, doing the following:
> 
> debug dialer
> debug isdn q931
> debug isdn code (hidden)
> debug isdn event
> sh isdn stat
> primary(s) down, dialer up
> primary(s) up, dialer down
> sh isdn stat
> und all
> 
> Thanks,
> 
> mark
> 
> 
> 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/