|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Alex Zinin (azinin
NEXSI.COM)Date: Thu Jul 05 2001 - 14:54:40 CDT
Michael,
First, there's no route summarization within an area.
Second, the OSPF spec does not include any mechanism
for dynamic route deaggregation (does not mean implementations
cannot have it).
I guess you would either need you bridges talk OSPF and
announce separate subnets or have each connected to a single
router and have one router announce one subnet.
-- Alex ZininWednesday, July 04, 2001, 4:22:53 PM, Michael Yeung wrote:
> Hi all, > As I understand from RFC2328, address range is > supported only at the ABR. What I like to do is to be > able to advertise selective individual subnets and > hosts on a given LAN without using ABR. Consider the > following:
> LAN1 > <------10.1.0.0------>
> 10.1.1.0 10.1.2.0 > R2-------R1----- bridge1 -------bridge2-----R3 > \ / > \ / > ------------bridge3--------------- > 20.1.0.0 > LAN2
> LAN1 includes bridge1 and bridge2 > LAN2 includes bridge3 > bridge1 covers subnet 10.1.1.0 > bridge2 covers subnet 10.1.2.0 > bridge3 covers subnet 20.1.0.0 > LAN1 covers subnet 10.1.0.0 > LAN2 covers subnet 20.1.0.0
> What I need: > - When connection between bridge1 and bridge2 is okay, > both R1 and R3 advertise 10.1.0.0 to R2 > - When connection between bridge1 and bridge2 FAILED, > R1 advertise 10.1.1.0 to R2, R3 advertise 10.1.2.0 to > R2
> Given all routers are within a single OSPF area, > address range is not feasible.
> In what form should R1 advertise 10.1.1.0 to R2? > - external route??? > - address range but R1 is not ABR???
> Any suggestion is greatly appreciated.
> thanx in advance, > Michael
> __________________________________________________ > Do You Yahoo!? > Get personalized email addresses from Yahoo! Mail > http://personal.mail.yahoo.com/
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]