From: Lee Donald (Lee.Donald@t-systems.co.uk)
Date: Fri Apr 22 2005 - 05:46:18 GMT-3
Ricky,
A good troubleshooting method for ISDN is to test that it's working each
step of the way.
For instance, perform a test call or ping in this case, when you have the
bare minimum config like
interface BRI0/0
ip address 167.3.45.4 255.255.255.0
encapsulation ppp
dialer map ip 167.3.45.5 name Rack3R5 broadcast 5272035
dialer-group 1
isdn switch-type basic-ni
isdn spid1 5272034
After which, add each bit of config at a time testing connectivity each time
and put the authentication on last.
Apart from which, your config might not be wrong, I've seen ISDN not work
when the config is perfect ! Reboot the router and everything works, explain
that !!
Try that methodology.
Regards
Lee.
-----Original Message-----
From: Ricky Martin [mailto:rickycool@gmail.com]
Sent: 22 April 2005 09:20
To: Cisco certification
Subject: PPP callback
This seemed to be simple at the start. But i am doing my lab now and i
am not able to get this thing working. Maybe i am missing something.
Could u guys spot whats wrong with the config
R4--ISDN---R5
1.legacy ISDN DDR between R4 and R5
2.Intresting traffic is icmp ping
3.idle timeoute is 60 either
4.ISDN calls should be originated from R4. configure your network so
that when R5 calls R4, R4 initiates PPP callback
5.To ensure the authenticity of the device which calls R5 back,
configure your network so that R5 issues a PPP authentication
challenge after receiving back
6.R4 should respond to R5's challege with the username ROUTER4 and a
hash value of the password CISCO
7.R5 should not issue this authentication challenge when it is calling R4
My config
R4
username Rack3R5 password 0 CISCO
interface BRI0/0
ip address 167.3.45.4 255.255.255.0
ip router isis
encapsulation ppp
dialer idle-timeout 60 either
dialer map ip 167.3.45.5 name Rack3R5 class CALLBACK broadcast 5272035
dialer callback-secure
dialer-group 1
isdn switch-type basic-ni
isdn spid1 5272034
ppp callback accept
ppp authentication chap
ppp chap hostname ROUTER4
end
map-class dialer CALLBACK
dialer callback-server username
!
access-list 100 permit icmp any any echo
dialer-list 1 protocol ip list 100
!
R5
username ROUTER4 password 0 CISCO
interface BRI0/0
ip address 167.3.45.5 255.255.255.0
ip router isis
encapsulation ppp
dialer idle-timeout 60
dialer map ip 167.3.45.4 name ROUTER4 broadcast 5272034
dialer-group 1
isdn switch-type basic-ni
isdn spid1 5272035
ppp callback request
ppp authentication chap callin
!access-list 100 permit icmp any any echo
dialer-list 1 protocol ip list 100
!
The error i get is authentication failure
Rack3R4#ping 167.3.45.5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 167.3.45.5, timeout is 2 seconds:
..
*Mar 1 00:36:15.213: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to up
*Mar 1 00:36:15.221: BR0/0:1 PPP: Using dialer call direction
*Mar 1 00:36:15.221: BR0/0:1 PPP: Treating connection as a callout
*Mar 1 00:36:15.221: BR0/0:1 PPP: Authorization NOT required
*Mar 1 00:36:15.241: BR0/0:1 CHAP: O CHALLENGE id 9 len 28 from "ROUTER4"
*Mar 1 00:36:15.253: BR0/0:1 CHAP: I CHALLENGE id 7 len 28 from "Rack3R5"
*Mar 1 00:36:15.257: BR0/0:1 CHAP: Using hostname from interface CHAP
*Mar 1 00:36:15.257: BR0/0:1 CHAP: Using password from AAA
*Mar 1 00:36:15.257: BR0/0:1 CHAP: O RESPONSE id 7 len 28 from "ROUTER4"
*Mar 1 00:36:15.281: BR0/0:1 CHAP: I FAILURE id 7 len 25 msg is
"Authentication
failed"
*Mar 1 00:36:15.337: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to
52
72035 .
*Mar 1 00:36:15.337: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to
down.
.
Success rate is 0 percent (0/5)
Rack3R4#
TIA for any input
Ricky
This archive was generated by hypermail 2.1.4 : Tue May 03 2005 - 07:55:06 GMT-3