From: Mike Wang (mike_wang51@xxxxxxxxxxx)
Date: Fri Sep 10 1999 - 13:53:54 GMT-3
Alex,
Still doesn't work. And I am sure it is not a PPP auth problem because I did
debug and server can get client updates.
Mike
>From: "Alex Dean" <Alex.Dean@telecom.co.nz>
>To: ccielab@groupstudy.com
>CC: mike_wang51@hotmail.com
>Subject: Re: snapshot over ISDN BRI w/ RIP problem
>Date: Fri, 10 Sep 1999 17:56:03 +1200
>
>Mike
>
>Try putting a dialer map snapshot... statement on R2.
>Also, I have encountered some odd behaviour with PPP CHAP if I haven't
>included the name parameter on my dialer maps.
>
>Good luck.
>
>Cheers
>Alex.
>
> >>> "Mike Wang" <mike_wang51@hotmail.com> 10/09/99 15:40:37 >>>
>Hi,
>
>I built a simple ISDN Snapshot routing over ISDN BRI scenario, but
>client
>side can not get RIP update during active period. Please help. Thanks,
>Mike
>
>Server could get RIP update of network 172.18.0.0. But Client could not
>get
>RIP update of network 172.17.0.0. Debug IP Packet on server side
>shows:
>
>RIP: Update queued
>RIP: sending v1 update to 255.255.255.255 via Ethernet0 (172.17.2.1)
>RIP: Update sent via BRI0
>IP: s=192.68.1.5 (local), d=255.255.255.255 (BRI0), len 32, sending
>broad/multicast
>IP: s=192.68.1.5 (local), d=255.255.255.255 (BRI0:1), len 32,
>encapsulation
>failed
>
>Server config:
>R2#wr t
>Building configuration...
>
>Current configuration:
>!
>version 11.2
>no service password-encryption
>no service udp-small-servers
>no service tcp-small-servers
>!
>hostname R2
>!
>!
>username R3 password 0 cisco
>username R4 password 0 cisco
>no ip domain-lookup
>isdn switch-type basic-5ess
>!
>interface Ethernet0
>ip address 172.17.2.1 255.255.255.0
>!
>interface Serial0
>ip address 172.16.1.5 255.255.255.252
>bandwidth 1544
>shutdown
>no fair-queue
>clockrate 1300000
>!
>interface Serial1
>no ip address
>shutdown
>!
>interface Serial2
>no ip address
>shutdown
>!
>interface Serial3
>no ip address
>shutdown
>!
>interface BRI0
>ip address 192.68.1.5 255.255.255.0
>encapsulation ppp
>dialer map ip 192.68.1.6 broadcast 1003
>dialer-group 1
>snapshot server 5 dialer
>no fair-queue
>ppp authentication chap
>!
>router rip
>network 172.17.0.0
>network 192.68.1.0
>!
>no ip classless
>!
>dialer-list 1 protocol ip permit
>!
>line con 0
>exec-timeout 0 0
>line aux 0
>line vty 0 4
>login
>!
>
>Client config:
>R3#wr t
>Building configuration...
>
>Current configuration:
>!
>version 11.2
>no service password-encryption
>no service udp-small-servers
>no service tcp-small-servers
>!
>hostname R3
>!
>!
>username R2A password 0 cisco
>username R2 password 0 cisco
>no ip domain-lookup
>isdn switch-type basic-5ess
>!
>interface Serial0
>ip address 172.16.1.6 255.255.255.252
>bandwidth 1544
>no fair-queue
>!
>interface Serial1
>ip address 172.16.2.1 255.255.255.0
>bandwidth 1544
>clockrate 1300000
>!
>interface Serial2
>no ip address
>shutdown
>!
>interface Serial3
>no ip address
>shutdown
>!
>interface TokenRing0
>ip address 172.18.1.1 255.255.255.0
>ring-speed 16
>!
>interface BRI0
>ip address 192.68.1.6 255.255.255.0
>encapsulation ppp
>dialer idle-timeout 5
>dialer map ip 192.68.1.5 broadcast 1002
>dialer map snapshot 60 1002
>dialer-group 1
>snapshot client 5 8 suppress-statechange-update dialer
>no fair-queue
>ppp authentication chap
>!
>interface Dialer1
>no ip address
>encapsulation ppp
>ppp authentication chap
>pulse-time 0
>!
>router rip
>network 192.68.1.0
>network 172.18.0.0
>!
>no ip classless
>!
>dialer-list 1 protocol ip permit
>!
>line con 0
>exec-timeout 0 0
>line aux 0
>line vty 0 4
>login
>!
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:50 GMT-3