From: Todd, Douglas M. (DTODD@PARTNERS.ORG)
Date: Tue Feb 27 2007 - 17:21:43 ART
Thanks for your reply.
I suspected I need to modify the route-map which will allow the route to be
redistributed via connected. This is why when I removed the redistribute
connected all worked. Thus the redistribute connected is breaking the
redistribute ospf -> eigrp.
My problem which is that I have the route already installed in ospf. I should
not have to modify my route-map to include an interface I do not want
redistributed via the connected command. If I want to redistribute a route from
ospf to eigrp I should be able to do this with out worrying if my redistribute
connected is blocking/breaking my redistribute ospf->eigrp.
If I have a task which asks me to create the configuration I just sent out
(loopback is in OSPF) AND I have a redistribute connected, I must make sure that
I include all interfaces which are locally connected and in a different protocol
(ospf) because they will not show up in the eigrp topology table. Thus if I a
connection goes down and my only path to my loopback (in ospf) is through eigrp
it will be unreachable unless I include it in my acl (via redis connected).
This is where I started, when I was testing redundancy, my loopback and serial
interfaces were unavaible because they are locally connected and in ospf, but
are being blocked via the redistributed connected.
Just seems very backwords and broken...The issue is when I am looking for an an
address which should be redistributed via ospf-eigrp it's acutally
redistributed via connected-eigrp because of this "feature.".
and yes - I spent a lot of time trying to figure out WHY this was happening. It
was a very good exercise in database debugging.... :)
If I really want to find out I could just open a TAC case and ask...
Anyway that is the way it is, lesson learned.
thanks for you input all.
DMT
> -----Original Message-----
> From: Brian Dennis [mailto:bdennis@internetworkexpert.com]
> Sent: Tuesday, February 27, 2007 2:43 PM
> To: Todd, Douglas M.; ccielab@groupstudy.com
> Subject: Re: Disfunctional redistribution:
>
> Basic route redistribution on a single router is a two step
> process. The first step is to bring in the routes from the
> routing table for the protocol being redistributed (show ip
> route <protocol>). The second step is to bring in the
> connected interfaces that the protocol is enabled on (i.e.
> network statements).
>
> When you manually redistribute connected with a route-map you
> are breaking the second step that the router is doing for you
> automatically. This second step was done when you
> redistributed, in your case, OSPF into EIGRP. You need to
> match the interfaces that the router was bringing in for you
> automatically in your route-map.
>
> If you remember these two steps it will save you a lot of
> headaches going forward ;-)
>
> --
>
> Brian Dennis, CCIE4 #2210 (R&S/ISP-Dial/Security/SP)
> bdennis@internetworkexpert.com
>
> Internetwork Expert, Inc.
> http://www.InternetworkExpert.com
> Toll Free: 877-224-8987
> Direct: 775-745-6404 (Outside the US and Canada)
>
>
>
> On 2/27/07 10:06 AM, "Todd, Douglas M." <DTODD@PARTNERS.ORG> wrote:
>
> > Hi all:
> >
> > I have a problem with redistribution and I am hoping
> someone can help
> > me understand what is going wrong.
> > Basic:
> > If I redistribute connected in eigrp why don't my ospf
> networks (which
> > are the connected interfaces) show up in the eigrp table when I
> > redistribute ospf into eigrp?
> >
> > To illustrate:
> >
> > Lets say I have a eigrp and ospf configuration of the following:
> > !
> > router eigrp 100
> > redistribute connected metric 100000 20000 255 1 1500 route-map
> > conn-eigrp network 136.9.23.2 0.0.0.0 no auto-summary eigrp
> > router-id 198.9.2.2 redistribute ospf 1 default-metric
> 10000 100 255
> > 1 1500 !
> > router ospf 1
> > router-id 198.9.2.2
> > log-adjacency-changes
> > auto-cost reference-bandwidth 20000
> > redistribute eigrp 100 metric-type 1 subnets route-map eigrp-ospf
> > network 136.9.245.2 0.0.0.0 area 0 network 198.9.2.2
> 0.0.0.0 area 0
> > distance 171 198.9.1.1 0.0.0.0 1
> >
> >
> > I see within the ospf domain my loopback of 198.9.2.2 as well as the
> > 136.9.245.2. Now I look too see what the eigrp topology
> table looks like. sh
> > ip ei top 198.9.2.0 255.255.255.0 (since this is a /24
> w/ospf network P-T-P
> > under the loopback). I do not see the route. Now I remove
> the redistributed
> > connected from the eigrp process. I do a sh ip ei top
> 198.9.2.0 255.255.255.0
> > and the route is there now.
> >
> > My question, why is eigrp blocking the redistributed route
> only when I have
> > redistributed connected with the route-map. If I remove
> the route-map I see
> > the
> > route, but it's not coming from the ospf process, but from
> the redistributed
> > process. If I remove the redist connected I see the route,
> but this is not
> > what
> > I want.
> >
> > The system is filtering where it shouldn't, it's filting
> routes coming from
> > the
> > ospf process AND the connected.
> >
> > Ideas?
> >
> > Douglas Todd
> > Partners HealthCare, Inc.
> > Network Engineering East
> > Master Network Engineer
> > Charlestown Navy Yard
> > Building 149 (MGH East)
> > 13th Street
> > Charlestown, MA 02129
> >
> >
> >
> >
> >
> >
> > The information transmitted in this electronic
> communication is intended only
> > for the person or entity to whom it is addressed and may
> contain confidential
> > and/or privileged material. Any review, retransmission,
> dissemination or other
> > use of or taking of any action in reliance upon this
> information by persons or
> > entities other than the intended recipient is prohibited.
> If you received this
> > information in error, please contact the Compliance
> HelpLine at 800-856-1983
> > and properly dispose of this information.
> >
> >
> ______________________________________________________________
> _________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
>
The information transmitted in this electronic communication is intended only for the person or entity to whom it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this information in error, please contact the Compliance HelpLine at 800-856-1983 and properly dispose of this information.
This archive was generated by hypermail 2.1.4 : Thu Mar 01 2007 - 07:38:48 ART