RE: ISIS over Frame Relay

From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Thu May 12 2005 - 09:48:08 GMT-3


Below are three common IS-IS over Frame-Relay configurations. The first
is a multipoint interface to a multipoint interface. The second is a
point-to-point interface to a point-to-point interface. The third is a
point-to-point interface to a multipoint interface utilizing the "isis
network point-to-point" command.

<FIRST>
Rack2R1#sho run int s0/0.1
Building configuration...

Current configuration : 175 bytes
!
interface Serial0/0.1 multipoint
 ip address 10.12.12.1 255.255.255.0
 ip router isis
 frame-relay map clns 102 broadcast
 frame-relay map ip 10.12.12.2 102 broadcast
end

Rack2R1#

Rack2R2#sho run int s0/0
Building configuration...

Current configuration : 217 bytes
!
interface Serial0/0
 ip address 10.12.12.2 255.255.255.0
 ip router isis
 encapsulation frame-relay
 frame-relay map clns 201 broadcast
 frame-relay map ip 10.12.12.1 201 broadcast
 no frame-relay inverse-arp
end

Rack2R2#
</FIRST>

<SECOND>
Rack2R1#sho run int serial0/0.2
Building configuration...

Current configuration : 133 bytes
!
interface Serial0/0.2 point-to-point
 ip address 10.13.13.1 255.255.255.0
 ip router isis
 frame-relay interface-dlci 103
end

Rack2R1#

Rack2R3#sho run int s1/0.1
Building configuration...

Current configuration : 133 bytes
!
interface Serial1/0.1 point-to-point
 ip address 10.13.13.3 255.255.255.0
 ip router isis
 frame-relay interface-dlci 301
end

Rack2R3#
</SECOND>

<THIRD>
Rack2R1#sho run int serial0/0.3
Building configuration...

Current configuration : 133 bytes
!
interface Serial0/0.3 point-to-point
 ip address 10.14.14.1 255.255.255.0
 ip router isis
 frame-relay interface-dlci 104
end

Rack2R4#sho run int s0/0.1
Building configuration...

Current configuration : 228 bytes
!
interface Serial0/0.1 multipoint
 ip address 10.14.14.4 255.255.255.0
 ip router isis
 isis network point-to-point
 frame-relay map clns 401 broadcast
 frame-relay map ip 10.14.14.1 401 broadcast
end

Rack2R4#
</THIRD>

Here is the output of R1's routing table showing the loopback interfaces
of the other routers (R2, R3, and R4) learned across the Frame Relay
network via IS-IS.

Rack2R1#sho ip rout isis
     150.2.0.0/32 is subnetted, 4 subnets
i L1 150.2.4.4 [115/10] via 10.14.14.4, Serial0/0.3
i L1 150.2.3.3 [115/10] via 10.13.13.3, Serial0/0.2
i L1 150.2.2.2 [115/10] via 10.12.12.2, Serial0/0.1
Rack2R1#

Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)

bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Marakalas
Sent: Thursday, May 12, 2005 4:06 AM
To: ccielab@groupstudy.com
Subject: ISIS over Frame Relay

Hi guys, I'm busy configuring ISIS across a F/R cloud
in the lab environment. However, I'm getting
encapsulation errors when debugging. What I did was to
configure frame-relay map clns 412 broadcast. This is
on the multipoint interfaces. What should be
configured on the point-to-point interfaces to have
ISIS working between two neighbours?

Thanks in advance.

                
Yahoo! Mail
Stay connected, organized, and protected. Take the tour:
http://tour.mail.yahoo.com/mailtour.html



This archive was generated by hypermail 2.1.4 : Fri Jun 03 2005 - 10:11:57 GMT-3