From: James.Jackson@broadwing.com
Date: Fri Mar 28 2003 - 05:09:11 GMT-3
"frame-relay map clns" statements are missing...
-----Original Message-----
From: Robert Yee [mailto:robert@bluespud.com]
Sent: Friday, March 28, 2003 12:16 AM
To: ccielab@groupstudy.com
Subject: ISIS Adjacency failure between 2 frame relay multipoint
itnerfaces
Hi all,
I have a problem that I cannot seem to see the solution to.
I am attempting the configure ISIS between 2 routers on a frame relay
network. The hub router is using a multipoint interface and the spoke router
is using the serial interface.
According to CCO, both types of interfaces are considered 'broadcast' and
the debug indicate that they are attempting to send LAN IIH packets.
Here are the configs:
Router 2 (hub)
interface Serial0.2 multipoint
ip address 150.50.1.2 255.255.255.0
ip router isis
frame-relay map ip 150.50.1.2 105 broadcast
frame-relay map ip 150.50.1.5 105 broadcast
frame-relay map ip 150.50.1.6 106 broadcast
!
!
router isis
net 49.0001.2222.2222.2222.00
is-type level-1
Here is the debug from Router 2:
00:06:23: ISIS-Adj: Encapsulation failed for L1 LAN IIH on Serial0.256
============================================================================
Router 5 (spoke)
interface Serial0/0
ip address 150.50.1.5 255.255.255.0
ip router isis
frame-relay map ip 150.50.1.2 501 broadcast
frame-relay map ip 150.50.1.5 501 broadcast
frame-relay map ip 150.50.1.6 501 broadcast
!
!
router isis
net 49.0001.5555.5555.5555.00
is-type level-1
And the debug:
00:22:23: ISIS-Adj: Encapsulation failed for L1 LAN IIH on Serial0/0
All my HDLC point-to-point adjacencies are up. Am I missing something in my
config?
Thanks,
Robert
+++The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and destroy any copies of this
document.+++
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:45 GMT-3