From: Kurt E. Radecki (kradecki@xxxxxxxxx)
Date: Sun May 06 2001 - 01:02:20 GMT-3
Summarization helps, but the ISDN link is in area 0. There are quite a few
other networks in the backbone as well. So, even if I summarized, there are
still networks that create a topology change.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
fwells12
Sent: Saturday, May 05, 2001 10:34 PM
To: CCIE newsgroup (E-mail)
Subject: Re: ccie bootcamp lab 8
Typically you would use summarization to prevent topology changes from
affecting your OSPF network. Take a look at your topology and see if you
can summarize it to prevent your problem.
----- Original Message -----
From: K. Radecki <kradecki@yahoo.com>
To: <ccielab@groupstudy.com>
Sent: Saturday, May 05, 2001 6:41 PM
Subject: ccie bootcamp lab 8
> I've copmlete lab 8, but still have an issue with
> Section 2 Task 3 Part 1. It states "...The ISDN
> connection should only come up if the ethernet
> connectivity is broken..."
>
> I have the IDSN link configured as an ospf-demand
> circuit, so Hellos and periodic updates don't keep the
> line active. Also, I've filtered IGRP from
> redistributing OSPF-learned routes back into OSPF, so
> there's no issue there. The problem I'm having is that
> the line comes up as soon as the there's a topology
> change in OSPF, ie I take down an interface in the
> network that OSPF advertises, even if the ethernet
> network is active.
>
> Based on the way ospf demand-circuit works, that
> doesn't surprise me. And, in a stable OSPF network,
> the link never comes up. Does the task assume a stable
> network? The way I read it, it doesn't. But, I don't
> know how to keep the link from activating using just
> demand-circuit. And, in the configuration they provide
> as the solution, they only use ospf-demand circuit.
>
> Thanks,
> Kurt
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:34 GMT-3