From: Aidan Marks (amarks@cisco.com)
Date: Sun Jan 05 2003 - 17:36:18 GMT-3
At 03:37 AM 6/01/2003, Peter van Oene wrote:
>At 11:41 AM 1/5/2003 +1100, Aidan Marks wrote:
>>Okay, theoretically, when you do this:
>>
>> interface FastEthernet0/0
>> ip address 20.0.0.1 255.0.0.0
>> ip router isis
>>
>> router ospf 100
>> redistribute isis
>
>In this case, the routes eligible for redistribution would need to exist
>in the routing table. The connected route will take precedence over the
>isis version in this case and thus the /8 will not be eligible for
>redistribution as far as I see it.
When you configure IGRP/EIGRP/RIP (and I think OSPF as well), with the
network command, a special bit gets set for the connected prefix. When
protocol X is configured to redistribute protocol Y, when evaluating if it
should redistribute a route, it looks if the owner of that route is
protocol Y *OR* if Y has the the special bit set for a route (in this case
a connected prefix which is owned by IGRP/EIGRP/RIP/OSPF). So prefixes for
interfaces configured with IGRP/EIGRP/RIP/OSPF will automatically be
redistributed into a protocol if that protocol redistributes
IGRP/EIGRP/RIP/OSPF.
Since ISIS doesn't use network commands and the special bit does not get
set, redistribution of the connected routes do not occur with the above
configuration and redistribute connected is required at this time.
Aidan
>>Then OSPF should advertise 20/8, however it doesn't.
>>
>>The particular problem is that ISIS doesn't use the network command so a
>>particular bit doesn't get set for the connected prefix which is checked
>>when redistribution happens.
>>
>>It is not consistent with IGRP, EIGRP, RIP and OSPF behaviour. An old
>>bug exists but AFAIK it is not been actively worked on. So I guess you
>>have to "redistribute connected" for the moment.
>>
>>Aidan
>>
>>At 10:54 AM 5/01/2003, OhioHondo wrote:
>>
>>>My experience is that interfaces defined to IS-IS on a redistributing router
>>>have to use the redistribute connected command. The interfaces do not
>>>redistribute if you do a "redistribute is-is" into another routing protocol.
>>>
>>>I would like to know the theory behind this.
>>>
>>>-----Original Message-----
>>>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
>>>Solomon Ghebremariam
>>>Sent: Saturday, January 04, 2003 3:54 PM
>>>To: kym blair
>>>Cc: ccielab@groupstudy.com
>>>Subject: Re: IS IS Connected network not being redistributed
>>>
>>>
>>>Kym
>>> I was trying to avoid using redistribute connected :) I thought
>>>like any protocol such as EIGRP , IS IS would transfer that link from is
>>>database to OSPF's up on redistribution??
>>>
>>>
>>>At 06:33 AM 1/4/2003 +0000, kym blair wrote:
>>> >Solomon,
>>> >
>>> >I didn't read your question carefully enough ... you were already
>>> >redistributing ISIS into OSPF, but you wanted to know how to get the R8-R5
>>> >(directly connected) link into OSPF.
>>> >
>>> >You need to redistribute connected on R8 to get the R8-R5 link into OSPF.
>>> >(Alternatively, you could add ISIS to R7, but I don't think that's what
>>> >you are looking for.)
>>> >
>>> >Separate issue, I thought only an ISIS Level-2 router could redistribute,
>>> >but your config is redistributing ISIS routes to OSPF when R8 is Level-1,
>>> >so I was wrong about that.
>>> >
>>> >Kym
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >>From: Solomon Ghebremariam <sghebrem@cisco.com>
>>> >>Reply-To: Solomon Ghebremariam <sghebrem@cisco.com>
>>> >>To: "kym blair" <kymblair@hotmail.com>
>>> >>CC: ccielab@groupstudy.com
>>> >>Subject: Re: IS IS Connected network not being redistributed
>>> >>Date: Fri, 03 Jan 2003 21:19:24 -0800
>>> >>
>>> >>Kym
>>> >>
>>> >>no luck, I changed R8 to Level-1-2 and I can see the two loopback
>>> >>interfaces in R7 as O E2 but not the segment between R8 and R5 i.e the
>>> >>147.4.85.0/24 network.
>>> >>
>>> >>
>>> >>At 03:57 AM 1/4/2003 +0000, kym blair wrote:
>>> >>>R8 needs to be ISIS Level-2 to redistribute into OSPF. If R5 is
>>> >>>Level-1, then R8 will need to be Level-1-2 to exchange routes with R5
>>> >>>AND do redistribution into OSPF.
>>> >>>
>>> >>>HTH, Kym
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>>>From: Solomon Ghebremariam <sghebrem@cisco.com>
>>> >>>>Reply-To: Solomon Ghebremariam <sghebrem@cisco.com>
>>> >>>>To: ccielab@groupstudy.com
>>> >>>>Subject: IS IS Connected network not being redistributed
>>> >>>>Date: Fri, 03 Jan 2003 18:59:23 -0800
>>> >>>>
>>> >>>> Hi All,
>>> >>>> I have :
>>> >>>>
>>> >>>>R7 --- R8 ---- R5
>>> >>>>
>>> >>>>IS IS between R8 and R5. OSPF between R7 and R8.
>>> >>>>
>>> >>>>I created a couple of loopback interfaces in R5 and put them in IS IS
>>>and
>>> >>>>I see all those routes in R8 fine. I redistribute IS IS to OSPF and
>>> vice
>>> >>>>versa. I can see all the routes (in R7) except for the segment
>>>connecting
>>> >>>>R8 and R5. I have a permit statement for that segment when I did redis.
>>> >>>>All networks are /24 except the link between R7 and R8 is /25 . How
>>> do I
>>> >>>>get the segment between R8 and R5 show up in R7 as External OSPF route
>>> >>>>besides doing redistribute connected.
>>> >>>>
>>> >>>>R8 config is:
>>> >>>>
>>> >>>>interface Ethernet1/0
>>> >>>> ip address 147.4.85.8 255.255.255.0
>>> >>>> ip router isis
>>> >>>> half-duplex
>>> >>>> isis circuit-type level-1
>>> >>>> isis priority 15
>>> >>>>!
>>> >>>>
>>> >>>>router isis
>>> >>>> redistribute ospf 8 metric 60 route-map ospf2isis metric-type
>>> external
>>> >>>>level-1
>>> >>>> net 49.8888.8888.8888.8888.00
>>> >>>> is-type level-1
>>> >>>>
>>> >>>>
>>> >>>> router ospf 8
>>> >>>> log-adjacency-changes
>>> >>>> area 0 authentication message-digest
>>> >>>> redistribute isis level-1 subnets route-map isis2ospf
>>> >>>> network 147.4.87.0 0.0.0.127 area 0
>>> >>>> neighbor 147.4.87.7 priority 1
>>> >>>>
>>> >>>>
>>> >>>>access-list 88 permit 170.3.12.0 0.0.1.255
>>> >>>>access-list 88 permit 147.4.85.0 0.0.0.255
>>> >>>>
>>> >>>>route-map isis2ospf permit 10
>>> >>>> match ip address 88
>>> >>>>!
>>> >>>>route-map ospf2isis deny 10
>>> >>>> match ip address 88
>>> >>>>!
>>> >>>>route-map ospf2isis permit 20
>>> >>>>
>>> >>>>R5's config is:
>>> >>>>
>>> >>>> interface Loopback12
>>> >>>> ip address 170.3.12.1 255.255.255.0
>>> >>>> ip router isis
>>> >>>>!
>>> >>>>interface Loopback13
>>> >>>> ip address 170.3.13.1 255.255.255.0
>>> >>>> ip router isis
>>> >>>>!
>>> >>>>
>>> >>>>interface FastEthernet0/1
>>> >>>> ip address 147.4.85.5 255.255.255.0
>>> >>>> ip router isis
>>> >>>> duplex auto
>>> >>>> speed auto
>>> >>>> isis circuit-type level-1
>>> >>>> isis priority 10
>>> >>>>!
>>> >>>>
>>> >>>>router isis
>>> >>>> net 49.8888.5555.5555.5555.00
>>> >>>> is-type level-1
>>> >>>>!
>>> >>>>
>>> >>>>Also here is my debug out put:
>>> >>>>
>>> >>>>2w2d: ISIS-Spf: (accepted)
>>> >>>>2w2d: ISIS-Spf: Add 5555.5555.5555.00-00 to TENT, metric 10
>>> >>>>2w2d: ISIS-Spf: Next hop 5555.5555.5555 (Ethernet1/0)
>>> >>>>2w2d: ISIS-Spf: Move 5555.5555.5555.00-00 to PATHS, metric 10
>>> >>>>2w2d: ISIS-Spf: Add 147.4.85.0/255.255.255.0 to IP RIB, metric 20
>>> >>>>2w2d: ISIS-Spf: Next hop 5555.5555.5555/147.4.85.5 (Ethernet1/0)
>>> >>>>(rejected)
>>> >>>>R8#
>>> >>>>2w2d: ISIS-Spf: Add 170.3.12.0/255.255.255.0 to IP RIB, metric 20
>>> >>>>2w2d: ISIS-Spf: Next hop 5555.5555.5555/147.4.85.5 (Ethernet1/0)
>>> >>>>(accepted)
>>> >>>>2w2d: ISIS-Spf: Add 170.3.13.0/255.255.255.0 to IP RIB, metric 20
>>> >>>>2w2d: ISIS-Spf: Next hop 5555.5555.5555/147.4.85.5(Ethernet1/0)
>>> >>>>(accepted)
>>> >>>>2w2d: ISIS-Spf: Aging L1 LSP 1 (5555.5555.5555.00-00), version 149
>>> >>>>2w2d: ISIS-Spf: Aging L1 LSP 3 (8888.8888.8888.00-00), version 127
>>> >>>>2w2d: ISIS-Spf: Aging L1 LSP 5 (8888.8888.8888.01-00), version 17
>>> >>>>
>>> >>>>appreciate ur help
>>> >>>>solomon
>>> >>>>.
>>> >>>_________________________________________________________________
>>> >>>MSN 8 with e-mail virus protection service: 2 months FREE*
>>> >>>http://join.msn.com/?page=features/virus
>>> >>.
>>> >_________________________________________________________________
>>> >MSN 8: advanced junk mail protection and 2 months FREE*.
>>> >http://join.msn.com/?page=features/junkmail
>>> >.
>>>.
>>>.
>>.
>.
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:42 GMT-3