From: Matt Mullen (mullenm@gmail.com)
Date: Wed Mar 16 2005 - 22:20:42 GMT-3
Yes, that worked! So it looks like for ISIS to form adjacency over
a multipoint subinterface you cannot use the frame-relay
interface-dlci command on the subinterface, you must use frame-relay
map statements instead. Good to know, but why does it not work using
the frame-relay inteface-dlci command?
Thanks,
Matt
On Wed, 16 Mar 2005 13:38:56 +1100, Paresh Khatri
<Paresh.Khatri@aapt.com.au> wrote:
> Matt,
>
> Try the following:
>
> R2:
> interface Serial0.246 multipoint
> ip address 138.10.100.2 255.255.255.224
> ip router isis
> no frame-relay interface-dlci 104 ! get rid of this
> no frame-relay interface-dlci 106 ! get rid of this
> frame-relay map clns 104 broadcast
> frame-relay map clns 106 broadcast
> frame-relay map ip 138.10.100.4 104 broadcast
> frame-relay map ip 138.10.100.6 106 broadcast
> end
>
> R4:
> interface Serial0/0
> ip address 138.10.100.4 255.255.255.224
> ip router isis
> encapsulation frame-relay
> no fair-queue
> frame-relay traffic-shaping
> frame-relay map clns 401 broadcast
> frame-relay map ip 138.10.100.2 401 broadcast
> frame-relay map ip 138.10.100.6 401 broadcast
> no frame-relay inverse-arp
>
> R6:
> interface Serial0
> ip address 138.10.100.6 255.255.255.224
> ip router isis
> encapsulation frame-relay
> frame-relay map clns 601 broadcast
> frame-relay map ip 138.10.100.2 601 broadcast
> frame-relay map ip 138.10.100.4 601 broadcast
> no frame-relay map ip 138.10.100.6 601 broadcast ! get rid of this,
> no frame-relay inverse-arp
> frame-relay lmi-type cisco
> end
>
> HTH,
> Paresh.
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Matt Mullen
> Sent: Wednesday, 16 March 2005 12:10 PM
> To: Group Study
> Subject: ISIS neighbors stuck in init
>
> Hello all, i'm working on a lab scenario where R2 is the hub with a
> multipoint f/r subinterface. R4 and R6 are the spokes and are using
> the physical interface. R4 and R6 should from an adjacency with R2,
> but R2 is getting an encapsulation failure when sending the hello
> packets on interface s0.246. Here's the configs and relevant debug
> output:
>
> R2:
>
> interface Serial0.246 multipoint
> ip address 138.10.100.2 255.255.255.224
> ip router isis
> frame-relay interface-dlci 104
> frame-relay interface-dlci 106
> end
>
> router isis
> net 49.0024.0000.0000.0002.00
>
> sh debug
> CLNS:
> IS-IS Adjacency related packets debugging is on
> R2#
> 02:10:33: ISIS-Adj: Encapsulation failed for L1 LAN IIH on Serial0.246
>
> R2#sh clns ne
>
> System Id Interface SNPA State Holdtime Type Protocol
> 0000.0000.0006 Se0.246 DLCI 106 Init 27 L1L2 IS-IS
> 0000.0000.0004 Se0.246 DLCI 104 Init 28 L1 IS-IS
>
> R4:
>
> interface Serial0/0
> ip address 138.10.100.4 255.255.255.224
> ip router isis
> encapsulation frame-relay
> no fair-queue
> frame-relay traffic-shaping
> frame-relay map clns 401 broadcast
> frame-relay map ip 138.10.100.2 401 broadcast
> frame-relay map ip 138.10.100.6 401 broadcast
> no frame-relay inverse-arp
>
> router isis
> net 49.0024.0000.0000.0004.00
> is-type level-1
>
> R6:
>
> R6#show run int s0
> Building configuration...
>
> Current configuration : 343 bytes
> !
> interface Serial0
> ip address 138.10.100.6 255.255.255.224
> ip router isis
> encapsulation frame-relay
> frame-relay map clns 601 broadcast
> frame-relay map ip 138.10.100.2 601 broadcast
> frame-relay map ip 138.10.100.4 601 broadcast
> frame-relay map ip 138.10.100.6 601 broadcast
> no frame-relay inverse-arp
> frame-relay lmi-type cisco
> end
>
> router isis
> net 49.0024.0000.0000.0006.00
>
> R4 and R6 do not see R2 as a neighbor at all, while R2 sees both R4
> and R6 but shows them both in an Init state. Can anyone point out
> what might be going on here?
>
> TIA,
> Matt
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> ------------------------------------------------------------------------------
> This communication, including any attachments, is confidential. If
> you are not the intended recipient, you should not read it - please
> contact me immediately, destroy it, and do not copy or use any part of
> this communication or disclose anything about it.
>
> ------------------------------------------------------------------------------
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:46 GMT-3