ISDN SBus link fails for Dialer Maps

From: James Ramsay (JRamsay@xxxxxxxxxxx)
Date: Tue Sep 21 1999 - 05:03:55 GMT-3


   
Hi All

I am trying to get two routers working together on ISDN Sbus using the
Dialer Map command.

I have a topology of:

Ethernet 10.10.10.0 /24------> R5 <------ISDN SBUS 10.30.10.0 /24 -----> R3
<-------10.20.10.0 /24

Yes it looks simple and I got it to work with Dialer string command but it
fails now I have changed to a dialer map configuration.

A ping fails from either end, with debug ip packet reporting encap errors.

My 'sh dialer map' looks good and the configs look in line with every bit of
doc I can find., but the router who should be responding to the ping is
failing to make a connection.

The line is configured for multipoint support and I know it to be good
(worked earlier for Dialer String config)

Any Clues?

Thanks

------------------------------------
hostname R3
!
!
no ip domain-lookup
isdn switch-type basic-nznet3
!
interface Ethernet0
 ip address 10.20.10.10 255.255.255.0
!

!!
interface BRI0
 ip address 10.30.10.3 255.255.255.0
 encapsulation ppp
 isdn answer1 3560085:3
 dialer map ip 10.30.10.5 name R5 3560085:5
 dialer-group 5
!
no ip classless
ip route 10.10.10.0 255.255.255.0 10.30.10.5
!
dialer-list 5 protocol ip permit
!!
end

--------------------------------

hostname R5
!
enable password cisco
!
no ip domain-lookup
isdn switch-type basic-nznet3
!
!
interface Ethernet0
 ip address 10.10.10.10 255.255.255.0
 no keepalive
!
interface Serial0
 no ip address
 no fair-queue
!
interface Serial1
 no ip address
!
interface BRI0
 ip address 10.30.10.5 255.255.255.0
 encapsulation ppp
 isdn answer1 3560085:5
 dialer map ip 10.30.10.3 name R3 3560085:3
 dialer-group 4
!
no ip classless
ip route 10.20.0.0 255.255.0.0 10.30.10.3
access-list 1 permit any
!
dialer-list 4 protocol ip list 1
!
!
end

----------------------------------------------------------------------

R5#sh dialer map
Static dialer map ip 10.30.10.3 name R3 (3560085:3) on BRI0

R3#sh dialer map
Static dialer map ip 10.30.10.5 name R5 (3560085:5) on BRI0
R3#
------------------------------------------------------------------------

This shows the dialer successful for the guy sending the ping (R5), but
failed for the R3 who shows up encapsualrion failures - why would the
connection fail...?

R5#sh dialer

BRI0 - dialer type = ISDN

Dial String Successes Failures Last called Last status
3560085:3 1 0 00:00:23 successful
0 incoming call(s) have been screened.

BRI0:1 - dialer type = ISDN
Idle timer (120 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is data link layer up
Dial reason: ip (s=10.30.10.5, d=10.20.10.10)
Time until disconnect 104 secs
Connected to 3560085:3 (R3)

BRI0:2 - dialer type = ISDN
Idle timer (120 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is idle

R3#sh dialer

BRI0 - dialer type = ISDN

Dial String Successes Failures Last called Last status
3560085:5 0 1 00:00:33 failed
0 incoming call(s) have been screened.

BRI0:1 - dialer type = ISDN
Idle timer (120 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is idle

BRI0:2 - dialer type = ISDN
Idle timer (120 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is data link layer up
Time until disconnect 84 secs



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:51 GMT-3