From: Roger RPF (rpf@bluemail.ch)
Date: Thu Jun 05 2008 - 06:14:52 ART
Hi Chris,
You're right, the same happens when I do it with RIP. So is this the default
behaviour? Hmmmm...I was thinking that it is not explicit necessary to
specify a metric when redistributing into OSPF.
Somehow I could not find a documentation describing this behaviour.
Can someon explain that? Is that really the default behaviour of OSPF? How
does it exactly work with the connected networks of another routing
protocol, redistributing into OSPF?
Thanks
Roger
-----Urspr|ngliche Nachricht-----
Von: Chris Gray [mailto:chris.gray@ozonenetworks.net]
Gesendet: Donnerstag, 5. Juni 2008 09:41
An: 'Roger RPF'; ccielab@groupstudy.com
Betreff: RE: redistribute connected
Hi Roger,
I saw this behaviour also when redistributing Rip into OSPF, It didn't carry
the Rip connected route.
I fixed this be specifying a metric when redistributing. E.g
Router ospf 10
Redistribute rip subnets metric 200
Regards
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Roger RPF
Sent: 05 June 2008 07:53
To: ccielab@groupstudy.com
Subject: redistribute connected
Hi group,
I have a question regarding redistribute connected. Following scenario:
---<R1 OSPF>----<R2 OSPF and EIGRP>----<R3 EIGRP>----
The links connecting the routers are configured as network statement in the
related protocol.
On R2, if I redistribute EIGRP into OSPF, I do not see the R2-R3 link (EIGRP
directly connected) in the R1 routing table. On R2 I additionally have to
configure redistribute connected under the OSPF process.
If I do the other way: On R2, redistribute OSPF into EIGRP, I can see the
network R1-R2 (OSPF directly connected) in the routing table of R3.
My question, is this default behaviour of OSPF? I need to use the
redistribute connected in order to get the directly connected network of the
other protocol (in this case EIGRP) into OSPF, even if I have configured
this particular network in EIGRP?
Would be very thankful for clarification
Roger
This archive was generated by hypermail 2.1.4 : Tue Jul 01 2008 - 06:23:20 ART