From: Jongsoo.Kim@Intelsat.com
Date: Fri Mar 04 2005 - 18:32:09 GMT-3
You are correct and this was one painful and stupid mistake I always did in
IGP.
I am not sure what you mean by a stub rip, but it should be on all active
rip interfaces except Hub interface in hub and spoke topology.
Same for eigrp. But as you said, I will also turn on for OSPF or ISIS
protocols.
In my opinion, rip is very hard topic in igp because it has a lot of tricks
a lab writer love to use such as split-horizon, v1 and v2,
multicast,broadcast,and unicast, auto-summary, passive interface, the fact
that it doesn't require neighbor adjacency, and so on.
Regards
Jongsoo
-----Original Message-----
From: Matt White [mailto:mwhite23@gmail.com]
Sent: Friday, 04 March, 2005 3:41 PM
To: Group Study
Subject: ip split-horizon on frame-relay; link state protocols
Let's say I have encapsulation frame-relay on a physical serial
interface, ip split-horizon becomes automatically disabled. If I
assign an IP address and apply this to an OSPF process, would it be
considered best practice to re-enable split-horizon?
I understand the split-horizon has nothing to do with a link state
protocol like OSPF, but would this hurt/help in any specific
situations?
I believe it IS considered best-practice to do this on a stub RIP
frame-relay physical interface, correct?
Thanks for you help guys.
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:40 GMT-3