On Sat, 9 Oct 2010, Smith W. Stacy wrote:
I think you misunderstood. My example in no way requires virtual/logical
routers. I simply used them because I only had access to a single
physical router and wanted to create a more complex topology to verify
the solution to your redistribution questi
In my configs and example topology, the only traffic that would transit abr2
would be traffic originating/terminating on abr2 (as long as abr1 and it's
interfaces were up). Traffic from isis2 to ospf2, for example, would take the
isis2->isis1->abr1->ospf1->ospf2 path. This is due to the 'metric
PM
To: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] Joining OPSF & IS-IS areas via 2 ABRs
Smith W. Stacy says
> Hi Clarke,
>
> I believe I have an answer for you...
>
Smith: I really want to thank you for the full diagram and thoughtful config.
That's a great solu
Smith W. Stacy says
Hi Clarke,
I believe I have an answer for you...
Smith: I really want to thank you for the full diagram and thoughtful
config. That's a great solution. Your use of logical tunnel interfaces
to bring the different "logical" routers together is a clean way to do it,
a
Hi Clarke,
I believe I have an answer for you...
Given this example topology:
+-+ +-+
|ospf1| .1 .2 |ospf2|
| 10.0.0.1 +---+ 10.0.0.2 |
| | 10.0.1.0/30 |
Offlist it was suggested to me that my typology is not very clear.
Perhaps a config snippet will help. Essentially, my two "ABRs" have one
foot in the OSPF world and the other foot in the IS-IS world. If needed,
I could run OSPF directly between the two ABRs. Both ABRs have direct
connection
I have an ISIS/OSPF area joining problem that I am trying to solve,
wondering if JUNOS policy can help.
Let's say that I have a bunch of routers in an IS-IS Level2 domain. I
also have a few routers in an OSPF area (area 0.0.0.0). The two "areas"
are joined via two Area Border Routers (ABR1 a
7 matches
Mail list logo