From: Derek Fage (DerekF@xxxxxxxxxxx)
Date: Fri Jun 18 1999 - 13:18:56 GMT-3
If you look at the configs, I have got the map statements in, but it still
does not work.
Derek...
> -----Original Message-----
> From: Mark, Detrick [SMTP:mdetrick@cisco.com]
> Sent: 18 June 1999 17:17
> To: Derek Fage; ccielab@groupstudy.com
> Subject: Re: ISIS Routing issues
>
> I have read Jeff Doyle's book and he makes a statement that IS-IS (really
> CLNS) can't be done over a point-to-multipoint interface. However, he is
> not correct. What will make it work are map statements. Instead of
> mapping
> IP addresses, map the CLNS address to the DLCI.
>
> Mark Detrick
> DSL Business Unit
> Cisco Systems
> 2569 McCabe Way
> Irvine, CA 92614
> ----- Original Message -----
> From: Derek Fage <DerekF@itexjsy.com>
> To: <ccielab@groupstudy.com>
> Sent: Friday, June 18, 1999 6:58 AM
> Subject: ISIS Routing issues
>
>
> > Hi there,
> >
> > I'm now playing with IS-IS routing for IP in my lab (attempting to
> replace
> > an OSPF configuration).
> >
> > The links are a mixture of ethernet and serial (Frame Relay).
> >
> > I have no problems with ethernet links, F/R physical or point-to-point
> > links, but I do not seem to be able to get a link between a F/R
> > point-to-point link on one router to form an adjacency with an F/R
> > multipoint link on another router.
> >
> > On the point-to-point link, the adjacency appears to form (show clns
> neigh
> > displays the remote router as being Up), but on the multipoint router
> the
> > clns neigh seems to stay in Init state.
> >
> > I cannot find anything talking about F/R issues in the Cisco
> documentation,
> > and just want to check that I'm not attempting to flog a dead horse
> here.
> > Should this configuration work ?
> >
> > Extract from configs at end of email
> >
> > Regards,
> >
> > Derek...
> >
> > R1-multipoint-----point-to-point-R1-ethernet-----ethernet-R5
> > |
> > | f/r point-ro-point
> > |
> > |
> > | f/r physical
> > |
> > R3
> >
> > R1
> > clns routing
> > int s0.1 multipoint
> > ip address 172.16.254.1 255.255.255.0
> > ip router isis
> > frame map ip 172.16.254.2 102 broadcast
> > frame map clns 102 broadcast
> > int s0.2 point-to-point
> > ip address 172.16.253.1 255.255.255.0
> > frame-relay interface-dlci 104
> > ip router isis
> > router isis
> > net 00.0002.1111.1111.1111.00
> >
> > R2
> > clns routing
> > int e 0
> > ip address 172.16.5.2 255.255.255.0
> > ip router isis
> > int s0.1 point-to-point
> > ip address 172.16.254.2 255.255.255.0
> > frame-relay interface-dlci 201
> > ip router isis
> > router isis
> > net 00.0002.2222.2222.2222.00
> >
> > R5
> > clns routing
> > int e 0
> > ip address 172.16.5.5 255.255.255.0
> > ip router isis
> > router isis
> > net 00.0002.5555.5555.5555.00
> >
> > R3
> > clns routing
> > int s0
> > ip address 172.16.253.3 255.255.255.0
> > encaps frame-relay
> > frame-relay map ip 172.16.253.1 103 broadcast
> > frame-relay map clns 103 broadcast
> > ip router isis
> > router isis
> > net 00.0004.4444.4444.4444.00
> >
> >
> >
> >
> >
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:39 GMT-3