Louie,
Ok, here's the scoop. First, this is normal behaviour for a demand circuit
and there is no provision in OSPF to handle it. BUT, Cisco has a relatively
undocumented command to take care of the flapping. "no peer neighbor-route"
I only found out about it's existance by calling TAC. This works great as
long as you don't have any virtual links that traverse the ISDN link.
You'll need to filter the virtual link traffic in the dialer list also, so
the multicast traffic isn't interesting to the dialer.
I'm going to be playing with this in my lab in the next week or two. I was
thinking of trying to change the link type to non-broadcast, point-to-point,
etc. to see if this would be a better/easier setup. I'll let you know if I
dig up any more good info.
Rodgers Moore
""Louie Belt"" <[EMAIL PROTECTED]> wrote in message
000201c03e40$f4fbb6e0$[EMAIL PROTECTED]">news:000201c03e40$f4fbb6e0$[EMAIL PROTECTED]...
> While configuring and OSPF demand circuit over ISDN, I noticed that the
ISDN
> link would disconnected and immediately reconnect - because the change in
> ospf topology was triggering and LSA flood - forcing the ISDN line to
> reconnect. However, the dialer enable-timeout setting was at it's default
> of 15 seconds so the ISDN link should have been forced to wait 15 seconds
> before attempting to reconnect (and thereby giving the LSA flood time to
> pass). However, this did not happen. No matter what I set the dialer
> enable-timeout to, the redial happened immediately.
>
> Question: What am I missing? (or mis-understanding)
>
> Thanks in advance!
>
> Louie
>
>
>
>
>
>
> _________________________________
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
