GroupStudy.com GroupStudy.com - A virtual community of network engineers
 Home  BookStore  StudyNotes  Links  Archives  StudyRooms  HelpWanted  Discounts  Login
Re: ISIS over frame-relay troubles..... posted 01/13/2001
[Chronological Index] [Thread Index] [Top] [Date Prev][Date Next] [Thread Prev][Thread Next]


ISIS has two network types,broadcast and point-to-point.  
The broadcast type works between frame-relay physical to physical
or to multipoint interfaces.  You do need to put in a frame-relay
map clns broadcast statement if there is not a clns dynamic map.
I did a simple frame relay physical to physical on three routers to
demonstrate this with output in-line below.

The point-to-point works between frame relay p-t-p subinterfaces or
other
pt-t-pt circuits.

If the types are mixed there is no command similiar to the ospf network
command.  This is the case in the Doyle example.  In this case use a
tunnel.
A tunnel works in the other cases also but is unnecessary.

Output from sample frame relay physical to physical (will also work
physical to multipoint or multipoint-to-multipoint):

r1#sh frame map
Serial0 (up): CLNS dlci 102(0x66,0x1860), static,
              broadcast, CISCO, status defined, active
Serial0 (up): ip 172.16.1.2 dlci 102(0x66,0x1860), dynamic,
              broadcast,, status defined, active
Serial1 (up): CLNS dlci 103(0x67,0x1870), static,
              broadcast, CISCO, status defined, active
Serial1 (up): ip 172.16.3.2 dlci 103(0x67,0x1870), dynamic,
              broadcast,, status defined, active
r1#sh ip rou
Codes: <clipped>
Gateway of last resort is not set

     172.16.0.0/30 is subnetted, 2 subnets
C       172.16.1.0 is directly connected, Serial0
C       172.16.3.0 is directly connected, Serial1
r1#sh clns nei

System Id      Interface   SNPA                State  Holdtime  Type
Protocol
2222.2222.2222 Se0         DLCI 102            Up     9         L1L2
IS-IS
3333.3333.3333 Se1         DLCI 103            Up     7         L1L2
IS-IS
============================================================================
r2#sh frame map
Serial0 (up): CLNS dlci 102(0x66,0x1860), static,
              broadcast, CISCO, status defined, active
Serial0 (up): ip 172.16.1.1 dlci 102(0x66,0x1860), dynamic,
              broadcast,, status defined, active
r2#sh clns nei

System Id      Interface   SNPA                State  Holdtime  Type
Protocol
1111.1111.1111 Se0         DLCI 102            Up     29        L1L2
IS-IS
r2#sh ip rou
Codes:<clipped>
Gateway of last resort is not set

     172.16.0.0/30 is subnetted, 2 subnets
C       172.16.1.0 is directly connected, Serial0
i L1    172.16.3.0 [115/20] via 172.16.1.1, Serial0
================================================================================
r3#sh frame map
Serial1 (up): ip 172.16.3.1 dlci 103(0x67,0x1870), dynamic,
              broadcast,, status defined, active
Serial1 (up): CLNS dlci 103(0x67,0x1870), static,
              broadcast, CISCO, status defined, active
r3#sh clns nei

System Id      Interface   SNPA                State  Holdtime  Type
Protocol
1111.1111.1111 Se1         DLCI 103            Up     23        L1L2
IS-IS
r3#sh ip rou
Codes:<clipped>
Gateway of last resort is not set

     172.16.0.0/30 is subnetted, 2 subnets
i L1    172.16.1.0 [115/20] via 172.16.3.1, Serial1
C       172.16.3.0 is directly connected, Serial1
r3#

Cheers, Fred.

Kevin Baumgartner wrote:
> 
>  Trying using point-to-point subinterfaces with isis. ISIS will not work
> with multipoint (physical or subinterface) type interfaces over Framerelay.
> 
>  Kevin
> 
> >
> > Hi All,
> >            I'm just trying to get a handle on ISIS over frame relay.  It =
> > would seem that because there's no comparable command to the "ip ospf =
> > network" under ISIS that this limits the configuration options over =
> > frame-relay.  It's noted that cisco serial interface with frame-relay =
> > encapsulation defaults to a multi-point interface. For some reason I =
> > can't get ISIS neighbor adjacencies being formed using a full mesh =
> > frame-relay cloud.=20
> >
> > I'm using the configuration example in Doyle's Routing TCP/IP, pg. 652.  =
> > I replaced the ethernet segment between the L2 devices(London, Rome, and =
> > Brussels) with frame-relay.  In my frame-relay configurations I'm able =
> > to ping all points of the cloud but I'm unable to get adjacencies to =
> > form.  All routers are configured with physical interface(multi-point, =
> > being the default) but I still get encapsulation failure when observing =
> > the "debug isis adj-packets".  Now I've got this to work when the =
> > devices are configured using  point-to-point sub-interfaces in a partial =
> > mesh(hub and spoke topology) and the  hub configured for individual =
> > p-t-p's for each pvc.
> >
> > I am however trying to simulate the ethernet segment I'm replacing.. I'm =
> > I thinking way "out the box" here or is this possible"
> >
> > For reference there's a basic example on pg. 678 of Doyle's book that =
> > covers the frame-relay issue I'm trying to resolve...
> >
> >
> > Thanks All,
> >
> > Nigel.
> >
> > _______________________________________________________
> > To unsubscribe from the CCIELAB list, send a message to
> > majordomo@xxxxxxxxxxxxxx with the body containing:
> > unsubscribe ccielab
> >
> 
> _______________________________________________________
> To unsubscribe from the CCIELAB list, send a message to
> majordomo@xxxxxxxxxxxxxx with the body containing:
> unsubscribe ccielab

_______________________________________________________
To unsubscribe from the CCIELAB list, send a message to
majordomo@xxxxxxxxxxxxxx with the body containing:
unsubscribe ccielab