From: Brad Hedlund (BHedlund@xxxxxxxxxxxxxxxxxxx)
Date: Tue Jan 11 2000 - 15:47:55 GMT-3
Are you sure that your scenario is EXACTLY like Darrel's?
Meaning, is your summary-address command summarizing a loopback that is
directly connected to R2 and a loopback that is being advertised from R1?
Both Darrel and I had identical results, the summary-route would go away
after a 'clear ip ro *'
and not come back. I waited several minutes and even reload, and it still
did not come back.
However, to solve the problem I removed the loopback on R2 from the ospf
routing proccess?
My summary still go created, and it always came back after a 'clear ip ro
*'.
R3 could still ping R1 and R2's loopback.
It appears to me that ospf has difficulty with the summary-address command
when it is summarizing a directly connected network that is in the ospf
proccess.
-Brad
>
> You can do an clear ip router * but you have to wait for a
> while until it come
> back.
>
>
>
>
> Brad Hedlund <BHedlund@LifeTimeFitness.com> on 11/01/2000 12:34:58 PM
>
> To: Jaime Salazar/Mexico/AMERICAS/Equant@Equant
> cc: "'ccielab@groupstudy.com'" <ccielab@groupstudy.com>
>
> Subject: RE: VLSM ---> FLSM or OSPF --> IGRP
>
>
>
>
> Be careful, if you reload it wont work anymore!
> Using Darrel's original scenario, if you 'clear ip ro *' or
> reload R2 ...
> the summary route goes away and doesnt come back.
>
> Try it out, see if you can find a solution.
>
> -Brad
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:22:44 GMT-3