IPv6 route redistribution
I thought I had IPv6 working great. However, like an idiot, I was pinging from R4 so it was a bad test.
Every router in OSPF6 can ping every interface running that protocol.
Every switch in RIP_ZONE can ping every interface running that protocol.
I can't ping from R1 -> anything past 2026::34:2. This tells me I have an issue with redistribution. Originally I had redistribution pretty simple, I was just doing OSPF to RIP and RIP to OSPF but no route-map or anything. I thought maybe that was the issue so I've added a convoluted route-map going each way. It's still not working...anyone see what's wrong?
Here are the config files for R3, R4, DSW1 and DSW2.
Every router in OSPF6 can ping every interface running that protocol.
Every switch in RIP_ZONE can ping every interface running that protocol.
I can't ping from R1 -> anything past 2026::34:2. This tells me I have an issue with redistribution. Originally I had redistribution pretty simple, I was just doing OSPF to RIP and RIP to OSPF but no route-map or anything. I thought maybe that was the issue so I've added a convoluted route-map going each way. It's still not working...anyone see what's wrong?
Here are the config files for R3, R4, DSW1 and DSW2.
Comments
-
errtime Member Posts: 7 ■□□□□□□□□□I am too lazy to lab this up, but if R-4 has all the RIPng and OSPFv3 routes in it's RIB, you perform the mutual redistribution with the metrics set for OSPF routes redistributed into RIPng + add the "include-connected" keyword in both redistributions, u should have a full IPv6 reachability
-
Nuul Member Posts: 158Thanks. I just added include-connected on the RIP redistribution, I can't believe I forgot that. That adds 2026::2:0 to the RIB. I still can't ping past 2026::2:1 though which makes no sense. You'd think that since I have the prefixes in the RIB I'd be able to ping them. Maybe I'm missing a metric or something in the redistribution to make RIP reachable in OSPF.
R1#sh ipv6 route
IPv6 Routing Table - 7 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route, M - MIPv6
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
D - EIGRP, EX - EIGRP external
OI 2026::1:0/122 [110/128]
via FE80::C003:8FF:FEC2:0, Serial0/0.12
OE2 2026::2:0/122 [110/20]
via FE80::C003:8FF:FEC2:0, Serial0/0.12
OE2 2026::3:0/122 [110/20]
via FE80::C003:8FF:FEC2:0, Serial0/0.12
C 2026::12:0/122 [0/0]
via ::, Serial0/0.12
L 2026::12:1/128 [0/0]
via ::, Serial0/0.12
OI 2026::34:0/122 [110/11239]
via FE80::C003:8FF:FEC2:0, Serial0/0.12
L FF00::/8 [0/0]
via ::, Null0 -
errtime Member Posts: 7 ■□□□□□□□□□as we can see, the redistribution into OSPFv3 works as expected. So the redistribution into RIPng is not successful. I believe you haven't specified the metric
Just show the R-4 configuration. -
Nuul Member Posts: 158I have turned off OSPF redist into RIPng so I could eliminate one problem at a time. Once RIP->OSPF is working I'll start working on OSPF->RIP
DSW1#sh ipv6 route
IPv6 Routing Table - Default - 5 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, R - RIP, D - EIGRP, EX - EIGRP external
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
C 2026::2:0/122 [0/0]
via FastEthernet0/1, directly connected
L 2026::2:2/128 [0/0]
via FastEthernet0/1, receive
C 2026::3:0/122 [0/0]
via Port-channel12, directly connected
L 2026::3:1/128 [0/0]
via Port-channel12, receive
L FF00::/8 [0/0]
via Null0, receive
DSW2#sh ipv6 route
IPv6 Routing Table - Default - 4 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, R - RIP, D - EIGRP, EX - EIGRP external
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
R 2026::2:0/122 [120/2]
via FE80::222:56FF:FE1A:B0C7, Port-channel12
C 2026::3:0/122 [0/0]
via Port-channel12, directly connected
L 2026::3:2/128 [0/0]
via Port-channel12, receive
L FF00::/8 [0/0]
via Null0, receive
DSW2#sh ipv6 rip
RIP process "RIP_ZONE", port 521, multicast-group FF02::9, pid 301
Administrative distance is 120. Maximum paths is 16
Updates every 30 seconds, expire after 180
Holddown lasts 0 seconds, garbage collect after 120
Split horizon is on; poison reverse is off
Default routes are not generated
Periodic updates 2709, trigger updates 10
Interfaces:
Port-channel12
Redistribution:
None
DSW2#sh ipv6 protocols
IPv6 Routing Protocol is "connected"
IPv6 Routing Protocol is "rip RIP_ZONE"
Interfaces:
Port-channel12
Redistribution:
None -
Nuul Member Posts: 158as we can see, the redistribution into OSPFv3 works as expected. So the redistribution into RIPng is not successful. I believe you haven't specified the metric
Just show the R-4 configuration.
I thought it was working, however, even though I can see the rip routes in the OSPFv3 routers the prefixes are unreachable by anyone but R4 (and the switches obviously).
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R4
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
ip cef
!
!
!
!
ipv6 unicast-routing
ipv6 cef
!
multilink bundle-name authenticated
!
!
archive
log config
hidekeys
!
!
interface Tunnel34
no ip address
ipv6 address 2026::34:2/122
ipv6 ospf 6 area 34
tunnel source 10.1.1.10
tunnel destination 10.1.1.9
!
interface FastEthernet0/0
ip address 10.1.4.5 255.255.255.252
speed 100
full-duplex
ipv6 address 2026::2:1/122
ipv6 rip RIP_ZONE enable
!
interface Serial0/0
no ip address
encapsulation frame-relay IETF
clock rate 2000000
frame-relay lmi-type ansi
!
interface Serial0/0.34 point-to-point
ip address 10.1.1.10 255.255.255.252
snmp trap link-status
frame-relay interface-dlci 403
!
interface FastEthernet0/1
ip address 10.1.4.9 255.255.255.252
speed 100
full-duplex
!
interface Serial0/1
no ip address
shutdown
clock rate 2000000
!
router eigrp 10
redistribute ospf 1 route-map OSPF->EIGRP
network 10.1.4.4 0.0.0.3
network 10.1.4.8 0.0.0.3
default-metric 2000 2000 255 1 1500
no auto-summary
!
router ospf 1
log-adjacency-changes
area 34 nssa
redistribute eigrp 10 subnets route-map EIGRP->OSPF
network 10.1.1.8 0.0.0.3 area 34
!
ip forward-protocol nd
!
!
no ip http server
no ip http secure-server
!
access-list 10 permit 10.2.1.0 0.0.0.255
access-list 10 permit 10.2.2.0 0.0.0.255
access-list 10 permit 10.1.4.4 0.0.0.3
access-list 10 permit 10.1.4.8 0.0.0.3
access-list 10 permit 192.168.1.128 0.0.0.31
access-list 10 permit 10.2.4.12 0.0.0.3
access-list 20 permit 0.0.0.0
access-list 20 permit 10.1.1.0 0.0.0.3
access-list 20 permit 10.1.1.4 0.0.0.3
access-list 20 permit 10.1.1.8 0.0.0.3
ipv6 router ospf 6
log-adjacency-changes
redistribute rip RIP_ZONE include-connected
!
ipv6 router rip RIP_ZONE
!
!
!
!
route-map EIGRP->OSPF permit 10
match ip address 10
!
route-map OSPF->EIGRP permit 10
match ip address 20
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
!
line con 0
logging synchronous
line aux 0
line vty 0 4
login
!
!
end -
burbankmarc Member Posts: 460I'm pretty sure it's the return traffic that's giving you issues. The RIPng -> OSPFv3 looks fine, so you can keep that setting. Redistribute OSPFv3 -> RIPng and check out the rip databases on your L3 switches.
-
errtime Member Posts: 7 ■□□□□□□□□□burbankmarc wrote: »I'm pretty sure it's the return traffic that's giving you issues. The RIPng -> OSPFv3 looks fine, so you can keep that setting. Redistribute OSPFv3 -> RIPng and check out the rip databases on your L3 switches.
Nuul, u can ping from R-4 the whole RIPng domain successfully because most prolly the ICMP packets are sourced from R-4 interface which belongs to the RIPng domain.
The R-4 configuration reveals that you did not set the metric for routes redistributed into RIPng.(config-router)redistribute ospf 6 metric 5 include-connected
should do the trick
p.s. im wondering how did u manage to pass CCIE written and BSCI -
Nuul Member Posts: 158
(config-router)redistribute ospf 6 metric 5 include-connected
should do the trick
Yup, that did it. I make dumb mistakes like that with IPv6. For some reason my brain treats it as something entirely new and forgets that everything else still applies. I mean really...return packets tripped me up on this one wtf. *facepalm*p.s. im wondering how did u manage to pass CCIE written and BSCI
Heh. I think it's because I'm awesome :P
Thanks for the help everyone -
errtime Member Posts: 7 ■□□□□□□□□□sh1t happens. I believe every1 sometimes feels the same.
Glad to help -
burbankmarc Member Posts: 460how was the difficulty of the CCIE written compared to the BSCI?
*EDIT*
Apologies for the thread hijack. -
TenisuBaka Member Posts: 46 ■■□□□□□□□□Do you mind if I ask you why you are doing RIP instead of EIGRP? Did the TSHOOT topology change recently??
-
Nuul Member Posts: 158No worries. 350-001 was easier imo; I absolutely destroyed that test. I think I got an 890 or something ridiculous. They drill you more on things like timers etc, but overall it felt like less detail. My guess is that they don't care about the written so much since you'll get your ass handed to you by the lab if you're not ready.
I wasn't originally planning on taking any of the CCNP exams. I read the CCIE Routing and Switching Exam Certification Guide for about 2-3 months then went and passed the written. However, about that time they changed the lab and for a long time no one passed it. So while I waited for IPexpert to update their training and labs to v4 I started on my CCNP to pass the time and keep sharp for the IE. -
Nuul Member Posts: 158TenisuBaka wrote: »Do you mind if I ask you why you are doing RIP instead of EIGRP? Did the TSHOOT topology change recently??
Did it? I hadn't caught that, can you link the topology where you see that? -
TenisuBaka Member Posts: 46 ■■□□□□□□□□When I open the pdf, it says EIGRP 10 for the switch network up to the first router. Are you saying when you open the pdf, it says RIPng??? How weird is that!?!
-
TenisuBaka Member Posts: 46 ■■□□□□□□□□Never mind. I got it now. I missed that RIPng for the IPv6 part, just assumed it was using EIGRP for both the v4 and v6 parts.