[cisco-voip] PRI serial "lockout"? what is SBC talking about

[Davis, Michael]

Some things I've seen cause that behavior are 1) voice-port shut down while serial and controller were up - no B-channels available 'though D-channel was happy.  2) Mis-configured NFAS backup D-channel - one side thinks there's a backup D-channel and the other thinks that channel is a B-channel so it appears locked.  
 
Yeah, hard to say in this particular case. 

	-----Original Message----- 
	From: cisco-voip-bounces at puck.nether.net on behalf of Mark Snow 
	Sent: Thu 12/8/2005 8:06 AM 
	To: 'IT'; cisco-voip at puck.nether.net 
	Cc: 
	Subject: RE: [cisco-voip] PRI serial "lockout"? what is SBC talking about
	
	

	These two look exactly as they should - but then you say the PRI is back up
	- so you probably already know that!
	
	-Mark Snow
	CCIE Voice #14073
	
	> -----Original Message-----
	> From: IT [mailto:it at cimgroup.com]
	> Sent: Wednesday, December 07, 2005 11:18 PM
	> To: Mark Snow; cisco-voip at puck.nether.net
	> Subject: RE: [cisco-voip] PRI serial "lockout"? what is SBC talking about
	>
	> The line is back up now, but here are the results of the two commands.
	> Thanks,
	> Avidan
	>
	>
	> cimgroupsanfran#show isdn status
	> Global ISDN Switchtype = primary-4ess
	>
	> %Q.931 is backhauled to CCM-MANAGER on DSL 0. Layer 3 output may not
	> apply
	>
	> ISDN Serial0/2/0:23 interface
	>         dsl 0, interface ISDN Switchtype = primary-ni
	>         L2 Protocol = Q.921  L3 Protocol(s) = CCM-MANAGER
	>     Layer 1 Status:
	>         ACTIVE
	>     Layer 2 Status:
	>         TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
	>     Layer 3 Status:
	>         0 Active Layer 3 Call(s)
	>     Active dsl 0 CCBs = 0
	>     The Free Channel Mask:  0x807FFFFF
	>     Number of L2 Discards = 0, L2 Session ID = 117
	>     Total Allocated ISDN CCBs = 0
	>
	>
	> cimgroupsanfran#show isdn service
	> PRI Channel Statistics:
	>
	> %Q.931 is backhauled to CCM-MANAGER on DSL 0. Layer 3 output may not
	> apply
	>
	> ISDN Se0/2/0: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 8=MaintPend
	> 9=OOSPend)
	>     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 2
	>
	> -----Original Message-----
	> From: Mark Snow [mailto:highspeedsnow at gmail.com]
	> Sent: Wednesday, December 07, 2005 7:19 PM
	> To: IT; Jose Quesada; cisco-voip at puck.nether.net
	> Subject: RE: [cisco-voip] PRI serial "lockout"? what is SBC talking
	> about
	>
	> Do a
	> 'sh isdn status'
	> and a
	> 'sh isdn service'
	>
	> And send us the results ....
	>
	> -Mark
	>
	> > -----Original Message-----
	> > From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-
	> > bounces at puck.nether.net] On Behalf Of IT
	> > Sent: Wednesday, December 07, 2005 6:27 PM
	> > To: Jose Quesada; cisco-voip at puck.nether.net
	> > Subject: [cisco-voip] PRI serial "lockout"? what is SBC talking about
	> >
	> > Hi,
	> >
	> > My PRI on a 2801 just died, and SBC said they were able to bring the
	> > line back up just by running a test. They said that this "rebooted"
	> the
	> > line, and when they first logged in they saw that the lines were
	> > "locked" out, and this was generally caused by my equipment. What can
	> I
	> > do to verify if this is correct? What did they mean? It's a serial
	> card,
	> > and here is the show intereface serial 0/2/0:23 output:
	> >
	> > show interfaces serial 0/2/0:23
	> > Serial0/2/0:23 is up, line protocol is up (spoofing)
	> >   Hardware is DSX1
	> >   MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
	> >      reliability 255/255, txload 1/255, rxload 1/255
	> >   Encapsulation HDLC, loopback not set
	> >   Last input 00:00:15, output 00:00:15, output hang never
	> >   Last clearing of "show interface" counters never
	> >   Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops:
	> 0
	> >   Queueing strategy: weighted fair
	> >   Output queue: 0/1000/64/0 (size/max total/threshold/drops)
	> >      Conversations  0/1/256 (active/max active/max total)
	> >      Reserved Conversations 0/0 (allocated/max allocated)
	> >      Available Bandwidth 48 kilobits/sec
	> >   5 minute input rate 0 bits/sec, 0 packets/sec
	> >   5 minute output rate 0 bits/sec, 0 packets/sec
	> >      204146 packets input, 973103 bytes, 0 no buffer
	> >      Received 0 broadcasts, 0 runts, 2 giants, 0 throttles
	> >      115437 input errors, 115437 CRC, 51503 frame, 30018 overrun, 0
	> > ignored, 85696 abort
	> >      204467 packets output, 978336 bytes, 0 underruns
	> >      0 output errors, 0 collisions, 12 interface resets
	> >      0 output buffer failures, 0 output buffers swapped out
	> >      30 carrier transitions
	> >   Timeslot(s) Used:24, SCC: 0, Transmitter delay is 0 flags
	> >
	> > ******************************************************
	> > This email may contain trade secrets and/or other information that is
	> > proprietary and/or confidential. Use of this by anyone other than the
	> > intended recipient(s) is prohibited and may be unlawful. If you are
	> not
	> > the intended recipient, delete the e-mail and notify us immediately.
	> > ******************************************************
	> >
	> >
	> > _______________________________________________
	> > cisco-voip mailing list
	> > cisco-voip at puck.nether.net
	> > https://puck.nether.net/mailman/listinfo/cisco-voip
	
	_______________________________________________
	cisco-voip mailing list
	cisco-voip at puck.nether.net
	https://puck.nether.net/mailman/listinfo/cisco-voip