From: Fred Ingham (fningham@xxxxxxxxxxxxxxxx)
Date: Mon Jul 31 2000 - 01:16:45 GMT-3
You can add the command clns router isis to the interfaces in addition
to the ip router isis command but I don't think that will solve your
problem. Configure your interfaces as point-to-point subinterfaces
instead of using the physical
interfaces. See Doyle p.678, Integrated isis on nbma networks.
HTH
"D. J. Jones" wrote:
>
> Could you please explain why not? thanks.
>
> ----- Original Message -----
> From: "Feliz, Edgar" <Edgar.Feliz@BTNA.com>
> To: "Ryan Hoffman" <ryan.hoffman@telus.com>; <ccielab@groupstudy.com>
> Sent: Sunday, July 30, 2000 7:07 AM
> Subject: RE: ISIS inarp issue...
>
> > You can not have both CLNS, and ISIS configured on an interface at the
> same
> > time.
> >
> > EF
> >
> > -----Original Message-----
> > From: Ryan Hoffman [mailto:ryan.hoffman@telus.com]
> > Sent: Monday, July 24, 2000 9:49 PM
> > To: 'ccielab@groupstudy.com'
> > Subject: ISIS inarp issue...
> >
> >
> > Caslow pg 111 indicates fr inarp for iso clns is supported. I can't get
> the
> > following to bring up dynamic map entries. Is it supported for osi clns
> > routing only, not isis?
> >
> >
> > hostname r1
> > !
> > interface Serial0
> > ip address 10.0.3.1 255.255.255.248
> > encapsulation frame-relay
> > ip router isis
> > !
> > router isis
> > net 05.0000.0000.0001.00
> >
> > hostname r3
> > !
> > interface Serial0
> > ip address 10.0.3.3 255.255.255.248
> > encapsulation frame-relay
> > ip router isis
> > !
> > router isis
> > net 05.0000.0000.0003.00
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:59 GMT-3