James, I hate to give such a poorly researched answer, but I did quite a bit of experimenting with ISIS a few months back. I don't have time to verify this for sure right now, but here is what I remember:
ISIS knows nothing of NBMA. It only know serial point-to-point and multi-access LANs. So I would replace those interface-dlci statements on your hub with frame-relay map ip statements and I would also add the broadcast keyword to EVERYTHING. I don't remember all of the nuances of DIS vs. DR, but I do seem to recall that in a broadcast LAN environment, all routers need to see one another. I am fairly sure that there are subtle but important differences in the way an ISIS LAN and an OSPF LAN behave. If this doesn't work, I'll make some time to try to refresh my memory. Regards, Scott James Haynes wrote: > > I've been working on a home lab scenario involving ISIS and > it's been > driving me crazy. The behavior appears to be a split horizion > issue even > though ISIS(like OSPF) is a link state protocol and shouldn't > have a problem > with this. The scenario involves a hub router R4 and two spoke > routers > r2,r3. R4 is connected via a multipoint sub-interface to the > physical frame > relay interfaces on r2 and r3. There a various routers behind > both of the > spoke routers and the hub router. R4 sees all routes on the > network as do > the routers located behind R4. R2 see's all routes on the > network except > those behind r3 and r3 sees all routes except for those behind > r2. In this > setup ISIS sends out multicasted LAN hellos that are picked up > by other > routers. > I thought perhaps that like the OSPF neighbor command that I've > used in hub > and spoke setup's I could use the clns is-neighbor interface > command, but > all I get are messages saying you cannot put static IS or ES > mappings on a > Frame Relay interface. Anyway, what follows are the relevant > config's. I was > hoping someone may spot something I haven't seen. > > R4# > > interface Serial0.2 multipoint > ip address 10.10.234.4 255.255.255.240 > no ip directed-broadcast > ip router isis 0 > no ip split-horizon > clns router isis 0 > isis priority 127 > frame-relay map clns 102 broadcast > frame-relay map clns 103 broadcast > frame-relay interface-dlci 102 > frame-relay interface-dlci 103 > > > > router isis 0 > net 49.0000.0000.0000.0004.00 > > > r2# > > interface Serial1/0 > ip address 10.10.234.2 255.255.255.240 > ip router isis 0 > encapsulation frame-relay > clns router isis 0 > frame-relay map clns 104 broadcast > frame-relay map ip 10.10.234.3 104 > frame-relay map ip 10.10.234.4 104 broadcast > > router isis 0 > net 49.0000.0000.0000.0002.00 > > > r3# > > interface Serial1/0 > ip address 10.10.234.3 255.255.255.240 > ip router isis 0 > encapsulation frame-relay > clns router isis 0 > frame-relay map clns 104 broadcast > frame-relay map ip 10.10.234.2 104 > frame-relay map ip 10.10.234.4 104 broadcast > > > router isis 0 > net 49.0000.0000.0000.0003.00 > > > > > > > > > > > > > > > > > > > > -- > James Haynes > Network Architect > Cendant IT > A+,MCSE,CCNA,CCDA,CCNP,CCDP, > CQS-SNA/IPSS > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=33109&t=33096 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
