From: miken (miken@sisna.com)
Date: Mon Dec 08 2003 - 01:30:11 GMT-3
Ken,
I don't see where anyone has tackled this one yet. Do you have both sides
configured with "either"?
Mike Nygard CCIE#12602
----- Original Message -----
From: <Ken.Farrington@barclayscapital.com>
To: <ccielab@groupstudy.com>
Sent: Sunday, December 07, 2003 12:09 PM
Subject: ISDN Stimulators "wait for isdn carrier timeout"
> Hi guys,
>
> I have an ISDN "stimulator" (it's great fun).
> I am trying to make a call using the "dialer-load threshold 64 either"
> command
> Send some packets over the the first channel comes up. from the debug
> below, you
> can see that I get the dreaded "wait for isdn carrier timeout" command
when
> the bri0/0:1
> hits the threshold at 67%.
>
> Could this be my "stimulator" or is it the IOS ?
>
> Many thx,
>
> ps. everyone should have a stimulator ;-)
>
>
> R5#ping
> Protocol [ip]:
> Target IP address: 155.195.10.2
> Repeat count [5]: 1000
> Datagram size [100]: 2000
> Timeout in seconds [2]:
> Extended commands [n]:
> Sweep range of sizes [n]:
> Type escape sequence to abort.
> Sending 1000, 2000-byte ICMP Echos to 155.195.10.2, timeout is 2 seconds:
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> etc etc etc
>
>
> So
>
>
> R5#sh int bri 0/0:1
> BRI0/0:1 is up, line protocol is up
> Hardware is PQUICC BRI
> MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
> reliability 255/255, txload 59/255, rxload 59/255
> Encapsulation PPP, loopback not set
> Keepalive set (10 sec)
> Time to interface disconnect: idle 00:00:29
> LCP Open
> Open: IPCP, CDPCP
> Last input 00:00:00, output 00:00:00, 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/2/16 (active/max active/max total)
> Reserved Conversations 0/0 (allocated/max allocated)
> Available Bandwidth 48 kilobits/sec
> 5 minute input rate 15000 bits/sec, 5 packets/sec
> 5 minute output rate 15000 bits/sec, 5 packets/sec
> 6663 packets input, 1102039 bytes, 0 no buffer
> Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
> 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
> 6375 packets output, 1131433 bytes, 0 underruns
> 0 output errors, 0 collisions, 0 interface resets
> 0 output buffer failures, 0 output buffers swapped out
> 1003 carrier transitions
> R5#
> R5#
> 09:45:54: BR0/0 DDR: rotary group to 384000 overloaded (67)
> 09:45:54: BR0/0 DDR: Attempting to dial 384000
> 09:45:54: BRI0/0: wait for isdn carrier timeout, call id=0x8164
> 09:46:24: BR0/0 DDR: rotary group to 384000 overloaded (91)
> 09:46:24: BR0/0 DDR: Attempting to dial 384000
> 09:46:24: BRI0/0: wait for isdn carrier timeout, call id=0x8165
> 09:46:54: BR0/0 DDR: rotary group to 384000 overloaded (115)
> 09:46:54: BR0/0 DDR: Attempting to dial 384000
> 09:46:54: BRI0/0: wait for isdn carrier timeout, call id=0x8166
> 09:47:24: BR0/0 DDR: rotary group to 384000 overloaded (123)
> 09:47:24: BR0/0 DDR: Attempting to dial 384000
> 09:47:24: BRI0/0: wait for isdn carrier timeout, call id=0x8167
> 09:47:54: BR0/0 DDR: rotary group to 384000 overloaded (123)
> 09:47:54: BR0/0 DDR: Attempting to dial 384000
> 09:47:54: BRI0/0: wait for isdn carrier timeout, call id=0x8168
> 09:48:24: BR0/0 DDR: rotary group to 384000 overloaded (123)
> 09:48:24: BR0/0 DDR: Attempting to dial 384000
> 09:48:24: BRI0/0: wait for isdn carrier timeout, call id=0x8169
> 09:48:54: BR0/0 DDR: rotary group to 384000 overloaded (123)
> 09:48:54: BR0/0 DDR: Attempting to dial 384000
> 09:48:54: BRI0/0: wait for isdn carrier timeout, call id=0x816A
>
>
>
> ------------------------------------------------------------------------
> For more information about Barclays Capital, please
> visit our web site at http://www.barcap.com.
>
>
> Internet communications are not secure and therefore the Barclays
> Group does not accept legal responsibility for the contents of this
> message. Although the Barclays Group operates anti-virus programmes,
> it does not accept responsibility for any damage whatsoever that is
> caused by viruses being passed. Any views or opinions presented are
> solely those of the author and do not necessarily represent those of the
> Barclays Group. Replies to this email may be monitored by the Barclays
> Group for operational or business reasons.
>
> ------------------------------------------------------------------------
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Jan 03 2004 - 08:25:37 GMT-3