From: Brian (signal@xxxxxxxxxx)
Date: Fri Jun 15 2001 - 17:12:28 GMT-3
That unicast is odd. What code version did you work this on Padhu? I see
no reason for a unicast.
Brian
On Fri, 15 Jun 2001, Padhu (LFG) wrote:
> David,
>
> When using dialer interfaces instead of physical, i see 2 things happening :
>
> 1. The summary for the BRI gets installed with metric 20 even when the isdn
> line is down.( I like this)
> 2. There is periodic unicast from local dialer i/f to dialer i/f ip. Debug
> dialer packet and debug ip packet shows this... I started clean with just 2
> routers ..no redistribution involved to eliminate the no of variables . But
> i still see this happening...So i had to filter on the caling side to deny
> ip 172.16.1.1 0.0.0.0 172.16.1.2 0.0.0.0 log and bind that to dialer-list...
>
> I still don't know why ...Could't see a whole lot even with debug ip ospf
> spf and debug ip ospf lsa gen running.
>
> Cheers,Padhu
>
> -----Original Message-----
> From: David Anderson [mailto:dma@cisco.com]
> Sent: Friday, June 15, 2001 1:47 PM
> To: ccielab@groupstudy.com
> Subject: Dialer profiles
>
>
> Hi everyone,
>
> Just a few more days until fun Day #1
>
> I have a question about Dialer profiles. I am having some trouble with my
> ISDN line staying down when using dialer profiles instead of the physical
> BRI interface. It is not because of filtering problems because when using
> the physical interface it works fine, but when I use dialer interfaces with
> what I believe is the correct config:
>
> calling router
> R1#
> interface Dialer0
> ip address 133.1.100.5 255.255.255.252
> no ip directed-broadcast
> encapsulation ppp
> ip ospf message-digest-key 1 md5 cisco
> ip ospf demand-circuit
> dialer remote-name router3
> dialer pool 1
> dialer idle-timeout 20
> dialer string 5552221
> dialer load-threshold 128 outbound
> dialer-group 1
> no peer neighbor-route
> pulse-time 0
> ppp authentication chap callin
> ppp multilink
> end
>
> called router
> R2#
> interface Dialer0
> ip address 133.1.100.6 255.255.255.252
> no ip directed-broadcast
> encapsulation ppp
> ip ospf message-digest-key 1 md5 cisco
> ip ospf demand-circuit
> dialer remote-name router5
> dialer pool 1
> dialer idle-timeout 20
> dialer string 5554441
> dialer load-threshold 128 outbound
> dialer-group 1
> no peer neighbor-route
> pulse-time 0
> ppp authentication chap
> ppp multilink
> end
>
> The line will not stay down and the cause is destination 224.0.0.5 . Can
> you not use ip ospf demand circuit on a dialer interface?
> Remember, when I take the dialer interfaces away and just use the physical
> BRI interfaces, it works fine. Any thoughts?
>
> Thanks,
> David
> David Anderson
> Network Design Engineer
> Enterprise Solutions Architecture & Design
> (408) 853-5515
> dma@cisco.com
> | |
> ..:|||||||:...:|||||||:..
> C I S C O S Y S T E M S
> **Please read:http://www.groupstudy.com/list/posting.html
> **Please read:http://www.groupstudy.com/list/posting.html
-----------------------------------------------
I'm buying / selling used CISCO gear!!
email me for a quote
Brian Feeny,CCDP,CCNP+VAS Scarlett Parria
signal@netjam.net scarlett@netjam.net
318-213-4709 318-213-4701
Netjam, LLC http://www.netjam.net
333 Texas St. VISA/MC/AMEX/COD
Suite 1401 30 day warranty
Shreveport, LA 71101 Cisco Channel Partner
toll free: 866-2NETJAM
phone: 318-212-0245
fax: 318-212-0246
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:24 GMT-3