IPV6 redistributing "include-connected"

From: Rik Guyler (rik@guyler.net)
Date: Mon Apr 14 2008 - 18:52:26 ART


Working on a lab where I am mutually redistributing IPV6 OSPF into IPV6
EIGRP. According to the docs the "include-connected" option should
redistribute the directly connected interfaces that the source routing
protocol is running on. However, in my scenario that option didn't live up
to its description. Of course I was able to manually redistribute the
connected interfaces into both routing protocols and make it work that way
but I'm stumped as to why it wouldn't work the way it's supposed to. I've
scoured the docs for a better explanation but coming up empty. Anybody have
some insight why this might be happening? Maybe something I've missed?

Here is a partial config from the router performing mutual redistribution:

interface Loopback0
 no ip address
 ipv6 address 2003::6/128
 ipv6 enable
 ipv6 ospf 1 area 0
!
interface Loopback1
 no ip address
 ipv6 address 2020::6/128
 ipv6 enable
 ipv6 eigrp 1
!
interface GigabitEthernet0/0
 no ip address
 duplex auto
 speed auto
 ipv6 address 2001::6/64
 ipv6 enable
 ipv6 ospf 1 area 0
!
interface GigabitEthernet0/1
 no ip address
 duplex auto
 speed auto
 ipv6 address 2010::6/64
 ipv6 enable
 ipv6 eigrp 1

ipv6 router eigrp 1
 router-id 6.6.6.6
 no shutdown
 redistribute ospf 1 metric 1000 1000 255 1 1500 route-map OSPF>EIGRP-IPV6
include-connected
!
ipv6 router ospf 1
 log-adjacency-changes
 redistribute eigrp 1 metric 200 tag 690 include-connected

Here are the IPV6 routes from an EIGRP router:

R2#sh ipv6 ro
IPv6 Routing Table - 12 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
       U - Per-user Static route
       I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
       O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
       ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
O 2001::/64 [110/65]
     via FE80::20D:BCFF:FE0B:A4C0, Serial0/0
C 2002::/64 [0/0]
     via ::, Serial0/0
L 2002::2/128 [0/0]
     via ::, Serial0/0
C 2003::/64 [0/0]
     via ::, Loopback0
O 2003::1/128 [110/64]
     via FE80::20D:BCFF:FE0B:A4C0, Serial0/0
L 2003::2/128 [0/0]
     via ::, Loopback0
O 2003::5/128 [110/64]
     via FE80::20F:F7FF:FED5:3980, Serial0/0
O 2003::6/128 [110/65]
     via FE80::20D:BCFF:FE0B:A4C0, Serial0/0
OE2 2020::4/128 [110/200], tag 690
     via FE80::20D:BCFF:FE0B:A4C0, Serial0/0
OE2 2021::/64 [110/200], tag 690
     via FE80::20D:BCFF:FE0B:A4C0, Serial0/0
L FE80::/10 [0/0]
     via ::, Null0
L FF00::/8 [0/0]

Now I have the "redistribute connected" under each protocol and the
connected routes show up fine:

R2#sh ipv6 ro
IPv6 Routing Table - 14 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
       U - Per-user Static route
       I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
       O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
       ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
O 2001::/64 [110/65]
     via FE80::20D:BCFF:FE0B:A4C0, Serial0/0
C 2002::/64 [0/0]
     via ::, Serial0/0
L 2002::2/128 [0/0]
     via ::, Serial0/0
C 2003::/64 [0/0]
     via ::, Loopback0
O 2003::1/128 [110/64]
     via FE80::20D:BCFF:FE0B:A4C0, Serial0/0
L 2003::2/128 [0/0]
     via ::, Loopback0
O 2003::5/128 [110/64]
     via FE80::20F:F7FF:FED5:3980, Serial0/0
O 2003::6/128 [110/65]
     via FE80::20D:BCFF:FE0B:A4C0, Serial0/0
OE2 2010::/64 [110/200]
     via FE80::20D:BCFF:FE0B:A4C0, Serial0/0
OE2 2020::4/128 [110/200], tag 690
     via FE80::20D:BCFF:FE0B:A4C0, Serial0/0
OE2 2020::6/128 [110/200]
     via FE80::20D:BCFF:FE0B:A4C0, Serial0/0
OE2 2021::/64 [110/200], tag 690
     via FE80::20D:BCFF:FE0B:A4C0, Serial0/0
L FE80::/10 [0/0]
     via ::, Null0
L FF00::/8 [0/0]
     via ::, Null0

--
Rik

Pass the CCIE in six weeks, Guaranteed! http://www.certscience.com/CCIE



This archive was generated by hypermail 2.1.4 : Thu May 01 2008 - 08:25:51 ART