RE: ISIS Question

From: Michael Snyder (msnyder@revolutioncomputer.com)
Date: Thu Feb 26 2004 - 10:24:43 GMT-3

Exactly, which will break other protocol`s directly connected routes.

Example.

Rip---->ospf
Isis--->ospf

Rip has a connected route, isis has a connected route. Normal behavior
isis can't redistribute the connected route, so you do it by hand.

The rip connected route will disappear.

-------------------------------------

(Cut and paste from last weeks post)

Here's what I was doing, the local isis interface didn't get
redistributed, which is normal.

I use tags, so I included the local interface (s0.24 136.10.24.0/29)
with the proper tag for isis into ospf, fixing what isis should have
done. (step 1)
 
Immediately my rip (s1 136.10.12.0/24) connected route which was
perfectly stable dropped out of ospf. (step 2)

I did nothing to effect the redistribution between rip and ospf! It is
some logic being turned off by a specific redistribute connected cmd
being present in the ospf config.

To fix it, I added another statement to my route-map using the right tag
for rip, and the route came back. (step 3)

Remote router watching ospf routes

Step 1) -

RT: add 136.10.24.0/29 via 136.10.56.5, ospf metric [110/1065]

Step 2)

RT: del 136.10.12.0/24 via 136.10.56.5, ospf metric [110/1065]

RT: delete subnet route to 136.10.12.0/24

Step 3)

RT: add 136.10.12.0/24 via 136.10.56.5, ospf metric [110/1065]

------------------------------------------------------------------------ 

----

Step 1)

redistribute connected metric 1000 metric-type 1 subnets route-map
connectedisis

route-map connectedisis permit 10

 match interface Serial0.24

 set tag 444

Step 3)

route-map connectedisis permit 15

 match interface Serial1

 set tag 111

-----Original Message-----
From: Yasser Aly [mailto:blackyeyes00@hotmail.com] 
Sent: Thursday, February 26, 2004 6:03 AM
To: ashoverm@cisco.com; ccielab@groupstudy.com
Subject: RE: ISIS Question

Hi Ashok,

  When redistributing ISIS into another routing protocol, connected 
interfaces in the ISIS will not be redisributed. You will need to use in

addition the redistribute connected command to redistribute ISIS
connected 
interfaces in another routing protocol.

Regards,
Yasser

>From: "Ashok Verma (ashoverm)" <ashoverm@cisco.com>
>Reply-To: "Ashok Verma (ashoverm)" <ashoverm@cisco.com>
>To: <ccielab@groupstudy.com>
>Subject: ISIS Question
>Date: Thu, 26 Feb 2004 19:02:04 +0900
>
>Hi All,
>
>                                                       136.10.24.0/29
>136.10.100.0/27
>                          136.10.4.4/24
>-------R4---------------------R2-----------------------R5--------136.10
.
>5.5/24
>                                                                  isis
>ospf
>
>
>In above topology R4 and R2 are running isis Where R4 is level-1-2
>router and R2 is Level 2 router only. And between R5 and R2 ospf area 0
>is running .When I do redistribution of isis in to ospf and ospf to
>isis. I am getting R5's network(136.10.5.5/24 and 136.10.100.0/27)on
>R4.But on R5  I am getting only 136.10.4.4/24 network and not receiving
>136.10.23.0/ 29 network.Which is a directly connected network of the
R2,
>Is it a normal behaviour with isis or some more config is required.
>
>Thanx in advance.
>
>Ashok Kumar Verma
>CCIP,CCDP,CCNP
>Network Consulting Engineer
>Customer Advocacy Advanced Service Dep.
>Service Provider AS Div.2
>Cisco Systems, K.K.Japan.
>
>Tel: +81-3-5324-4583
>e-mail: ashoverm@cisco.com
>
>_______________________________________________________________________
>Please help support GroupStudy by purchasing your study materials from:
>http://shop.groupstudy.com
>
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html

This archive was generated by hypermail 2.1.4 : Fri Mar 05 2004 - 07:13:57 GMT-3