RE: serial channels not available = busy signal after cold boot

From: Young, Jason (Jason.Young@anheuser-busch.com)
Date: Thu May 24 2001 - 16:06:36 EDT


Well, then desynchronization is almost certainly your issue. You perceive all
your channels as out-of-service, and the telco wouldn't try and send you a call
on a channel that's out of service. Your AS5300 correctly (from its perspective)
rejects the call on that channel. When the line goes up, the telco typically
instructs the AS5300 to place all the channels in service (IIRC). You'll see
this in q931 debug.

Make sure you shutdown the "controller t1 X" interface, not the serial. I don't
think shutting down the serial would be sufficient to get the switch's attention
about the line having been down and needing a reset. The virtual-template will
always be down, its status is meaningless.

It's rather strange that it's persisting in this state. Leave it off for a bit
if necessary, a few minutes. Really the trick is to somehow beat some sense into
the switch on the other end. You could try setting a loopback on the controller
if shutting it down doesn't work. Having the telco test the line would hopefully
do the job, as a last resort.

If nothing on your end works, shutdown the controller, set debugging of q921 and
q931 (931 is more useful than the 921), turn it back on and capture what happens
when you turn the interface on. Send that to me if you like and I'll see if I
can make sense of it.

Jason Young
CNS - Network Design, Anheuser-Busch
(314)577-4597

> -----Original Message-----
> From: Dave VanAuken [mailto:dave@hawk-systems.com]
> Sent: Thursday, May 24, 2001 3:01 PM
> To: cisco-nsp@puck.nether.net
> Cc: Young, Jason
> Subject: RE: serial channels not available = busy signal
> after cold boot
>
>
> Tried to no avail. All IDSN channels are in outofservice status
>
> as0#show isdn service
> PRI Channel Statistics:
> ISDN Se0:23, Channel [1-24]
> Configured Isdn Interface (dsl) 0
> Channel State (0=Idle 1=Proposed 2=Busy 3=Reserved 4=Restart
> 5=Maint_Pend)
> Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
> State : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3
> Service State (0=Inservice 1=Maint 2=Outofservice)
> Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
> State : 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
>
> the Virtual-Template is also down, but I think this is a symptom not a
> cause...
>
>
> >-----Original Message-----
> >From: Young, Jason [mailto:Jason.Young@anheuser-busch.com]
> >Sent: Thursday, May 24, 2001 3:31 PM
> >To: 'Dave VanAuken'; cisco-nsp@puck.nether.net
> >Cc: Scott Madley; George Robbins
> >Subject: RE: serial channels not available = busy signal
> >after cold boot
> >
> >
> >
> >I've seen this when, for lack of a better term, the AS5300 becomes
> >"desynchronized" with the phone switch. I've had this happen
> >a lot when you hose
> >the router for an extended period of time like when you
> >overload the console
> >with debugging and the router stops temporarily. The telco
> >thinks the PRI/BRI is
> >in a certain state, your AS5300 thinks it's in a different
> >state. I suppose this
> >could happen if the power cycle of the router was very rapid.
> >
> >Shutting down the interface for a minute or so and then
> >turning it back on would
> >likely deal with the issue.
> >
> >Jason Young
> >CNS - Network Design, Anheuser-Busch
> >(314)577-4597
> >
> >
>



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:38 EDT