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