From: Brian Dennis (brian@xxxxxx)
Date: Thu Apr 12 2001 - 19:01:12 GMT-3
Corey,
You don't have a network entity title (net) defined on R5 so R1 thinks he's
talking to an end system not an intermediate system. I bet if you do a "show
clns neighbor" on R1 you'll see the protocol as ES-IS not IS-IS. I'm
assuming you don't want to advertise R1's loopback 5 interface because you
don't have ISIS enabled on it. Also as a side note your masks don't match on
the tunnel interfaces.
Brian Dennis
CCIE #2210 (R&S)(ISP/Dial)
CCSI #98640
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Corey M. Ellis
Sent: Thursday, April 12, 2001 2:24 PM
To: CCIE Mailist
Subject: Tunneling ISIS
Hi,
I am trying to tunnel ISIS through and ospf environment. This is what I have
done. The layout is r1 -- r4 -- r5. r1 -- r4 is EIGRP; r4 -- r5 is OSPF
via frame link. I am doing mutual redistribution, and all routes are seen.
Now I have created a loopback on r1 and a loopback on r5 which are not in
any routing process. I want to create a tunnel between r1 -- r5 and be able
to ping these loopbacks via ISIS.
What I have done
R1
clns routing
router isis
net 49.0001.1111.1111.1111.00
interface Loopback4
ip address 1.1.1.1 255.255.255.0
int lo5
ip addr 10.2.2.2 255.255.255.0
interface Tunnel1
ip address 10.0.0.2 255.255.255.0
ip router isis
tunnel source 1.1.1.1
tunnel destination 5.5.5.5
R5
clns routing
router isis
interface Loopback0
ip address 5.5.5.5 255.255.255.0
interface Loopback1
ip address 10.1.1.1 255.255.255.0
ip router isis
interface Tunnel3
ip address 10.0.0.1 255.255.255.252
ip router isis
tunnel source 5.5.5.5
tunnel destination 1.1.1.1
Keep in mind other stuff is in the config, I pulled out the appropriate
info. I expected to see a ISIS route on these routers with the loopback
there. Once I got this working, I was going to try to encrypt the traffic.
Can someone explain the problem, am I missing something.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:45 GMT-3