Re: OSPF aggreation question [7:26091]

2001-11-15 Thread Mark Paterson
Ok Here it is, this is how we tackled the OSPF Aggregation problem. To properly aggregate addresses within an internal type OSPF advertisement you must use the Area x range statement, this would not work because of the multi area setup and non-contiguous addresses. Stabilization of area 0

Re: OSPF aggreation question [7:26091]

2001-11-14 Thread Chris White
7500's can handle it...I would want RSP4's at a minimum. 200 routers can be in a full mesh and a single IGP area if you wanted. You probably only want to mesh your core and depending on the pysical configuration use RRs for the access layer...Unless all your access routers are on the same

OSPF aggreation question [7:26091]

2001-11-13 Thread Mark Paterson
All, I have a question that may have several answers, I have tried a few with varying results and would just like to see if anyone else has any suggestions. We run a Large Telco Data Backbone, most of which has been run on OSPF and BGP. Our distribution and access layers contain layer three

Re: OSPF aggreation question [7:26091]

2001-11-13 Thread VoIP Guy
Good old-fashioned re-addressing. Once you re-address, summarize at the abr's. Mark Paterson wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... All, I have a question that may have several answers, I have tried a few with varying results and would just like to see if anyone

Re: OSPF aggreation question [7:26091]

2001-11-13 Thread Mark Paterson
Can't re-address, these a public routable addresses, remember this is a Telco Service provider, If it where that easy we would have done it that way, this network also makes an enterprise look small by comparison. You need to really think about this one. Message Posted at:

Re: OSPF aggreation question [7:26091]

2001-11-13 Thread VoIP Guy
You have to readdress. ATT does it, so can you. I never said it was going to be fun. Mark Paterson wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Can't re-address, these a public routable addresses, remember this is a Telco Service provider, If it where that easy we would

Re: OSPF aggreation question [7:26091]

2001-11-13 Thread Chris White
Use IBGP for customer routes and OSPF only for reachability (loopbacks and links between routers). Your primary concern with OSPF at that point will be the number of routers in a given area and link instability. If you have enough routers that summarization is still reqired. it is much easier

Re: OSPF aggreation question [7:26091]

2001-11-13 Thread Chris Cindy Watson
Why go away from EIGRP? Are you putting in No'tell or something? (WARNING! 2 cents: If aint broke.) It seems that you may be able to place some those discontiguous nets into some stub or NSSA's. My gut thought is to limit the core router and one interface hop as part of Area 0 and then

Re: OSPF aggreation question [7:26091]

2001-11-13 Thread [EMAIL PROTECTED]
In a message dated 11/13/01 4:57:36 PM Central Standard Time, [EMAIL PROTECTED] writes: Subj: Re: OSPF aggreation question [7:26091] Date: 11/13/01 4:57:36 PM Central Standard Time From: [EMAIL PROTECTED] (Mark Paterson) Sender:[EMAIL PROTECTED] Reply-to: [EMAIL PROTECTED] (Mark

Re: OSPF aggreation question [7:26091]

2001-11-13 Thread Mark Paterson
Excellent suggestion, That is our end goal. And considering we are running a number of 12012's that can handle lots of peering sessions, BPG would be an excellent solution. However if you had smaller routers at the core, say 7500's could this still work. The network has 200 access routers, that

Re: OSPF aggreation question [7:26091]

2001-11-13 Thread Mark Paterson
Your a funny guy :-) come on are you not going for your CCIE, There is a way of doing this with out BGP or Re numbering. Mark Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=26183t=26091 -- FAQ, list archives, and subscription