Re: [c-nsp] IS-IS route separation/filtering

2009-08-31 Thread Oliver Boehmer (oboehmer)
Jared Gillis mailto:jared.a.gil...@gmail.com wrote on Monday, August 10, 2009 21:05: Oliver Boehmer (oboehmer) wrote: Well.. not sure how large you want to grow your L1 area, but you could investigate advertise-passive-only to only adveritse the loopbacks (all customer routes should be in BGP

Re: [c-nsp] IS-IS route separation/filtering

2009-08-10 Thread Jared Gillis
Oliver Boehmer (oboehmer) wrote: Well.. not sure how large you want to grow your L1 area, but you could investigate advertise-passive-only to only adveritse the loopbacks (all customer routes should be in BGP if you need to plan for growth), and you'll be fine, even with a 1000 nodes in the

Re: [c-nsp] IS-IS route separation/filtering

2009-08-07 Thread Oliver Boehmer (oboehmer)
Jared Gillis wrote on Thursday, August 06, 2009 20:48: Daniel Verlouw wrote: On Wed, 2009-08-05 at 15:02 -0700, Jared Gillis wrote: Hm, interesting though. Unfortunately, it doesn't seem to pan out in the lab. The LSPs don't seem to get flooded, but the routes do get passed through Router A

Re: [c-nsp] IS-IS route separation/filtering

2009-08-06 Thread Daniel Verlouw
On Wed, 2009-08-05 at 15:02 -0700, Jared Gillis wrote: Hm, interesting though. Unfortunately, it doesn't seem to pan out in the lab. The LSPs don't seem to get flooded, but the routes do get passed through Router A to all the stub routers, regardless of how I set up the mesh-groups. right.

Re: [c-nsp] IS-IS route separation/filtering

2009-08-06 Thread Jared Gillis
Daniel Verlouw wrote: On Wed, 2009-08-05 at 15:02 -0700, Jared Gillis wrote: Hm, interesting though. Unfortunately, it doesn't seem to pan out in the lab. The LSPs don't seem to get flooded, but the routes do get passed through Router A to all the stub routers, regardless of how I set up the

Re: [c-nsp] IS-IS route separation/filtering

2009-08-06 Thread Jared Gillis
Here's a thought: If I change Router A to L2 and Routers B and C to L2/L1, I can put B and C in different areas, but because they are L2/L1, they learn all the routes to all the areas, just as L2 routes instead of L1 routes. This gets me each stub router and everything behind it into different

[c-nsp] IS-IS route separation/filtering

2009-08-05 Thread Jared Gillis
Hello all, I'm trying to accomplish something with an IS-IS network, and I'm starting to think it may not be possible, but I'm hoping someone here might have a suggestion to help. Basically, what I'm trying to accomplish is to have two routers subtended off an aggregation router. So, say Router A

Re: [c-nsp] IS-IS route separation/filtering

2009-08-05 Thread Daniel Verlouw
On Aug 5, 2009, at 9:57 PM, Jared Gillis wrote: Basically I'm trying to replicate the concept of an OSPF totally-stubby-not-so-stubby-area in IS-IS, and I'm starting to question whether it can be done. My network design is fairly flexible at this point (the only requirements are that it run

Re: [c-nsp] IS-IS route separation/filtering

2009-08-05 Thread Jared Gillis
Daniel Verlouw wrote: have a look at IS-IS mesh-groups. Although designed for a different purpose, it might work. Stick router A and all of its stub routers into the same L1 area. On router A, put all interfaces towards the stub routers in the same mesh-group. Hm, interesting though.