From: William Lijewski (ccie8642@hotmail.com)
Date: Sun Sep 07 2003 - 04:51:07 GMT-3
ISIS will not work with mismatched interface types, there is no way to
change the network types like there is in OSPF. If you are going to use a
POINT-TO-POINT sub-interface on one side, and there are no restrictions
against it, use a POINT-TO-POINT sub-interface on the other side.
If you are not allowed to use a sub-interface on one side of the link, but
you must use a sub-interface on the other side, make the sub-interface
multipoint. A physical interface is considered multipoint so the interface
types would match. If you are using a physical or multipoint sub you must
map the CLNS protocol across the frame or it will not work.
frame-relay map CLNS <dlci> broadcast
William Lijewski
CCIE #8642
>From: SN K38U <youshungang@hotmail.com>
>Reply-To: SN K38U <youshungang@hotmail.com>
>To: ccielab@groupstudy.com
>Subject: isis neighbor adj problem
>Date: Sun, 07 Sep 2003 06:27:44 +0000
>
>Hi group#,when I worked on a lab recently,I encountered a problem about
>isis neighbor adj.
>Here is my topology:
>r3-s1--(frame-relay)--s0-r4-| e0
>|
>s0
>
>below is the detailed config:
>
>r3:
>interface Serial0
>no ip address
>encapsulation frame-relay
>frame-relay lmi-type ansi
>!
>interface Serial0.1 point-to-point
>ip address 10.13.1.2 255.255.0.0
>ip router isis frame-relay interface-dlci 301 !
>interface Serial1
>ip address 10.34.1.1 255.255.0.0
>ip router isis encapsulation frame-relay
>frame-relay interface-dlci 304
>frame-relay lmi-type ansi
>!
>router isis net 01.3333.3333.3333.00
>
>r4:
>interface Ethernet0
>ip address 10.4.1.1 255.255.0.0
>ip router isis !
>interface Serial0
>ip address 10.34.1.2 255.255.0.0
>ip router isis encapsulation frame-relay
>frame-relay interface-dlci 403
>frame-relay lmi-type ansi
>!
>router isis net 01.4444.4444.4444.00
>
>I found that r3 and r4 cannot form isis neighbors.
>When i debug the isis neighbor adj,here is the output:
>r3#debug isis adj
>IS-IS Adjacency related packets debugging is on
>r3#
>00:03:14: ISIS-Adj: Encapsulation failed for L1 LAN IIH on Serial1
>00:03:15: ISIS-Adj: Encapsulation failed for L2 LAN IIH on Serial1
>on r4,there is the same problem.
>
>That confused me.The s0 should send serial IIH instead of LAN IIH since it
>is not a lan interface.Why the interface s0 does not behave normally? What
>cause this situation?
>Who can help out the problem? I wasted too much time on it.
>Please clarify it. Thanks a lot for any help!
>
>_________________________________________________________________
>OmSCJ@=gIOWn4s5D5gWSSJ<~O5M3!* MSN Hotmail!# http://www.hotmail.com
>
>
>_______________________________________________________________________
>You are subscribed to the GroupStudy.com CCIE R&S Discussion Group.
>
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Oct 01 2003 - 07:24:24 GMT-3