From: Nick Tucker (kitt@vnet.net)
Date: Mon Jun 21 2004 - 11:49:44 GMT-3
> > > > I've been doodling with ISIS some. Topology is this:
> > > >
> > > > / ---R2
> > > > R4----Ethernet-----R1------Frame --|
> > > >
> \---R3-----Ethernet----R5-----Ethernet-----R6
> > > >
Appreciate all the responses so far, hopefully I answer all the ?'s asked
so far in this email.
I have admended the above topology to what I replicated last nite.
I tried it by hardcoding the is-levels to 2 only, to level1-2, same
results Interestingly enough, when I changed
R4/R1 to level1 only - I lost all communication between r4/r1 ,but thats
another horse to beat another day.
I have all of my lab configs up at http://tofguild.org/cisco/isislab.txt
and if anyone wants to take a look. BUT:
I'm not going to paste them here, because after reading 1 comment this
morning, I see something jumping out at me.
The route for the ethernet between r1--r4 is not in r2's or any other
router in my topology. I just know I've read something (and
this morning about making sure the eth route was in the others tables) on
this group in the archives something along the l
ines of isis not redisitributed connected interfaces by default, and it
looks like I've just become another victim of it.
This is my network between r1 - r4 :
C 21.1.1.0 is directly connected, Ethernet0/0
Let me lab this up again today to make sure I got punked, before I stick my
foot in my mouth anymore.
Thanks guys
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:46 GMT-3