RE: Redistribute connected under ISIS/OSPF process

From: Scott Morris (swm@emanon.com)
Date: Mon Dec 22 2003 - 12:45:25 GMT-3


Or you consider the alternative process/thinking of the router... Which
is that connected interfaces are entered into the CLNS database. It's
not until they go out a particular interface process that they are sent
as ISIS IP updates. So they would be in the ISIS table of adjacent
neighbors, but not themselves. You have to rememeber that historically,
IP for ISIS was an afterthought. :)

At least in poking through the databases that's the behavior that I
see... Perhaps that's a bug, but I think it's more like we are looking
for an IOS workaround to the way that CLNS/ISIS works.

 
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
CISSP, JNCIS, et al.
IPExpert CCIE Program Manager
IPExpert Sr. Technical Instructor
swm@emanon.com/smorris@ipexpert.net
http://www.ipexpert.net

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Danny.Andaluz@triaton-na.com
Sent: Monday, December 22, 2003 9:59 AM
To: marvingreenlee@yahoo.com; jwongccie@yahoo.com.hk
Cc: ccielab@groupstudy.com
Subject: RE: Redistribute connected under ISIS/OSPF process

So I suppose this is a bug that was never fixed?

Danny

-----Original Message-----
From: Marvin Greenlee [mailto:marvingreenlee@yahoo.com]
Sent: Sunday, December 21, 2003 11:10 AM
To: k c
Cc: ccielab@groupstudy.com
Subject: Re: Redistribute connected under ISIS/OSPF process

This has to do with Cisco Bug CSCea40365:
"While redistributing ISIS routes into OSPF, the
directly connected routes [ISIS] are not getting
redistributed into OSPF.

Workaround: use redistribute connected under 'router
ospf'."

Regards,
Marvin Greenlee
CCIE #12237

--- k c <jwongccie@yahoo.com.hk> wrote:
> Hi group,
>
> I expect the subnet 137.10.111.0/27 should be seen
> in other ospf enabled router, but it isn't. I have
> to add redistribute connected under ospf process.
> Can I do it without "redistribute connect"?
>
> R5 (Hub)
> interface Serial5/0
> no ip address
> encapsulation frame-relay
> serial restart_delay 0
> no frame-relay inverse-arp
> frame-relay lmi-type ansi
> !
> interface Serial5/0.1 multipoint
> ip address 137.10.100.5 255.255.255.224
> ip ospf message-digest-key 1 md5 7 094F471A1A0A
> frame-relay map ip 137.10.100.2 502 broadcast
> frame-relay map ip 137.10.100.3 503 broadcast
> frame-relay map ip 137.10.100.5 502
> !
> interface Serial5/0.2 point-to-point
> !
> interface Serial5/0.3 multipoint
> ip address 137.10.111.5 255.255.255.224
> ip router isis
> frame-relay map clns 504 broadcast
> frame-relay map ip 137.10.111.4 504 broadcast
> frame-relay map ip 137.10.111.5 504
>
> router ospf 1
> log-adjacency-changes
> area 0 authentication message-digest
> area 30 authentication message-digest
> area 30 virtual-link 137.10.6.6 message-digest-key
> 1 md5 cisco
> redistribute isis level-1-2 subnets
> network 137.10.5.0 0.0.0.255 area 0
> network 137.10.25.0 0.0.0.255 area 0
> network 137.10.100.0 0.0.0.255 area 0
> network 137.10.110.0 0.0.0.255 area 30
> neighbor 137.10.100.3
> neighbor 137.10.100.2
> !
> router isis
> net 00.0001.5555.5555.5555.00
> area-password cisco
> redistribute ospf 1 metric 3 match internal
> external 1 external 2 level-1-2
>
> R4
> interface Serial2/0
> ip address 137.10.111.4 255.255.255.224
> ip router isis
> encapsulation frame-relay
> no ip mroute-cache
> logging event subif-link-status
> logging event dlci-status-change
> serial restart_delay 0
> frame-relay map clns 405 broadcast
> frame-relay map ip 137.10.111.4 405
> frame-relay map ip 137.10.111.5 405 broadcast
> frame-relay lmi-type ansi
> router isis
> net 00.0001.4444.4444.4444.00
> area-password cisco
>
>
> Shining Friends!B&n$_&n3x!B73$k&p:q...
> .v:)9aAn 1!$_3sC4
> http://ringtone.yahoo.com.hk/
>
>



This archive was generated by hypermail 2.1.4 : Sat Jan 03 2004 - 08:25:44 GMT-3