Tshoot: A network was not shown in OSPFv3 routing table

Reference topology

Refer to IPv6 Layer 3 topology.

Reference explanation.

While I was doing IPv6 redistribution from ripng to OSPFv3, I found that OSPFv3 routing table did not include the 2026::2:/122 network which is in the RIPng domain between DSW1 and R4. DSW1 however has all the RIPng external routes but cannot ping to 2026::1:/122 network.

The reason is because when RIPng was redistributed into OSPFv3, only the route of show ipv6 route rip was redistributed and the route of show ipv6 route connected was not redistributed.

Before adding include-connect keyword under ospfv3 routing process

1841-1#sh ipv6 route

OI  2026::1:0/122 [110/1562]
via FE80::EA04:62FF:FEDC:5DC4, Serial0/1/0.12
OE2 2026::3:0/122 [110/10]
via FE80::EA04:62FF:FEDC:5DC4, Serial0/1/0.12
C   2026::12:0/122 [0/0]
via Serial0/1/0.12, directly connected
L   2026::12:1/128 [0/0]
via Serial0/1/0.12, receive
OI  2026::34:0/122 [110/12673]
via FE80::EA04:62FF:FEDC:5DC4, Serial0/1/0.12
L   FF00::/8 [0/0]
via Null0, receive

There’s no 2026::2:/122 network.

Before adding include-connect keyword under RIPng routing process

3560-1#sh ipv6 route

R   2026::1:0/122 [120/2]
via FE80::213:60FF:FE01:D4A0, FastEthernet0/1
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-channel1, directly connected
L   2026::3:1/128 [0/0]
via Port-channel1, receive
R   2026::12:0/122 [120/2]
via FE80::213:60FF:FE01:D4A0, FastEthernet0/1
R   2026::34:0/122 [120/2]
via FE80::213:60FF:FE01:D4A0, FastEthernet0/1
L   FF00::/8 [0/0]
via Null0, receive

Has all the RIPng external routes but cannot be ping, because there’s no return path back to the source.

Ping results from DSW1 to RIPng external routes

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2026::1:1, timeout is 2 seconds:
…..
Success rate is 0 percent (0/5)
3560-1#ping 2026::12:1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2026::12:1, timeout is 2 seconds:
…..
Success rate is 0 percent (0/5)
3560-1#
3560-1#ping 2026::34:2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2026::34:2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/0 ms
3560-1#ping 2026::34:1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2026::34:1, timeout is 2 seconds:
…..
Success rate is 0 percent (0/5)

2026::34:2 was successful because this is the tunnel interface address of 2651-2 which is R4, R4 has a route back to the source. Others were not successful.

After adding include-connected keyword under the ospfv3 process of 2651-2 (aka R4)

2651-2(config)#ipv6 router ospf 6
2651-2(config-rtr)#redistribute rip rip_zone metric 10 include-connected

1841-1#sh ipv6 route
OI  2026::1:0/122 [110/1562]
via FE80::EA04:62FF:FEDC:5DC4, Serial0/1/0.12
OE2 2026::2:0/122 [110/10]
via FE80::EA04:62FF:FEDC:5DC4, Serial0/1/0.12
OE2 2026::3:0/122 [110/10]
via FE80::EA04:62FF:FEDC:5DC4, Serial0/1/0.12
C   2026::12:0/122 [0/0]
via Serial0/1/0.12, directly connected
L   2026::12:1/128 [0/0]
via Serial0/1/0.12, receive
OI  2026::34:0/122 [110/12673]
via FE80::EA04:62FF:FEDC:5DC4, Serial0/1/0.12
L   FF00::/8 [0/0]
via Null0, receive

2026::2:/122 appears.

1841-1#ping 2026::2:2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2026::2:2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 96/96/100 ms

DSW1 routed interface fa0/1 was reachable.

Ping test from DSW1 to all RIPng external routes

All RIPng external routes were reachable.

Advertisements
This entry was posted in IPv6, OSPF, Route, Tshoot and tagged , , , , , , . Bookmark the permalink.

One Response to Tshoot: A network was not shown in OSPFv3 routing table

  1. Pingback: ASA: Lab it up — Topology Explained | Lufayo

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s