2503 BRI0:1 hardly ever dials.

2503 BRI0:1 hardly ever dials.

Post by Ken Kirk » Sun, 15 Jun 1997 04:00:00



We have a 2503 connected to a Ascend MAX4000. The 2503 has 14K/2K memory and
of course 8mb FRAM.

The IOS version is 11.2(1)

!
! Last configuration change at 15:57:22 AET Fri Jun 13 1997
! NVRAM config last updated at 21:29:57 AET Thu Jun 12 1997
!
version 11.2
service timestamps debug datetime localtime
service timestamps log datetime localtime
!
hostname huakere
!
boot system flash
enable secret 5 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
!
username kakapo password xxxxxxxxxxxxxxxxxxxxxx
no ip source-route

ip domain-name terrigal.net.au
ip name-server 203.16.244.89
ip name-server 203.16.244.85
ip name-server 203.16.244.91
ip name-server 203.16.244.90
ip name-server 203.12.176.130
ip name-server 203.12.176.145
isdn switch-type basic-ts013
clock timezone AET 10
clock summer-time AEST date Nov 1 1995 20:00 Apr 1 1996 19:59
!
interface Ethernet0
 description Local Ethernet
 ip address 203.16.244.z 255.255.255.0
 bridge-group 1
!
interface Virtual-Template1
 ip unnumbered Ethernet0
 no cdp enable
 ppp multilink
!
interface Serial0
 no ip address
 shutdown
 no fair-queue
!
interface Serial1
 no ip address
 shutdown
!
interface BRI0
 description Terrigal-Net #2 ISDN
 ip address 10.1.170.10 255.0.0.0
 ip access-group 101 in
 ip access-group 102 out
 ip tcp header-compression
 encapsulation ppp
 dialer idle-timeout 200000
 dialer enable-timeout 5
 dialer wait-for-carrier-time 15
 dialer string 0299285800
 dialer load-threshold 40 either
 dialer-group 1
 no fair-queue
 ppp multilink
!
router rip
 network 10.0.0.0
 network 203.16.244.0
!
no ip classless
ip route 0.0.0.0 0.0.0.0 10.1.170.10 (ip addresses of others changed,
so might not have masks right)

On call disconnection, BRI re-establishes itself with first BRI0:1 then
BRI0:2, but once BRI0:2 is established, BRI0:1 drops out.

However occassionally BRI0:1 will dial, and then the call hangs in there
for the dialer idle-timeout period. When this happens (good) show dialer
reason for BRI0:1 ppp multilink bundle overload ( which shows the BRI0
rotary group is working),and BRI0:2 shows the cause of dialing as the static
route to 10.1.170.0

This config used to work fine on two other links, but on this its a puzzle.
Is it the lack of ppp authentication, that causes it. We believe we have
callerid enabled on our lines. Cant understand why it kicks in sometimes. Is
the dialer load-threshold not working.

Any help will be welcome.

--
Ken Kirkby
K. J. Kirkby and Associates Pty Ltd.
Real-Time Computer Engineering Hardware & Software.
Internet Providers to the NSW Central Coast.

http://www.terrigal.net.au/~kjka fx 61-43-853720

 
 
 

1. BRI0/0 vs. BRI0:1 vs. BRI0:2

I realize that BRI0:1 and BRI0:2 are the first and second B channels
respectively.

Is BRI0/0 the D channel?  I thought I read somewhere that the D
channel stays up at all times.  If that is the case then why do I have
154 carrier transitions in 15 hours?

Inquiring minds want to know...

Thanks!

Greg

2. Deploying Access 2K app on Win 2000

3. Dynamic ip to 2503's bri0

4. Most realistic Practice Exams

5. cisco 2503 Bri0 - Robert Kiessling

6. Context menu on tree Node

7. Why doesn't my 2503 passes ipx packets from e0 to BRI0?

8. Sun Memory Nice Price!

9. Dial on demand without accept dial-in on Cisco 2503

10. 2503(boot) Prompt on a 2503 Router

11. 2503 connect 2503 ???

12. CABLE Question : I need a 2503-2503 serial cable

13. Cisco Enterprise 2503 vs. Cisco Pro 2503