IPv6 redistribution

image

IPv6 redistribution is almost identical to the IPv4 version, expect IPv6 redistribution doesn’t include the connected interfaces by default

In the above topology, the setup is quite simple R1-R2 are running RIP and R1-R3 are running OSPFv3

Configurations

R1

interface Loopback0
 ipv6 address 2001:1:1::1/64
 ipv6 rip RIP enable
!
interface FastEthernet0/0
 ipv6 address FE80::1 link-local
 ipv6 address FC00:12:12::1/64
 ipv6 rip RIP enable

R2

interface Loopback0
 ipv6 address 2001:2:2::2/64
 ipv6 rip RIP enable
!
interface FastEthernet0/0
 ipv6 address FE80::2 link-local
 ipv6 address FC00:12:12::2/64
 ipv6 rip RIP enable
!
interface FastEthernet0/1
 ipv6 address FE80::2 link-local
 ipv6 address FC00:23:23::2/64
 ipv6 ospf 1 area 0

!
ipv6 router ospf 1
 router-id 2.2.2.2

R3

interface Loopback0
 ipv6 address 2001:3:3::3/64
 ipv6 ospf 1 area 0
!
interface FastEthernet0/0
 ipv6 address FE80::3 link-local
 ipv6 address FC00:23:23::3/64
 ipv6 ospf 1 area 0

ipv6 router ospf 1
 router-id 3.3.3.3

With this basic setup, we should have connectivity between R1-R2 and R2-R3

R1#show ipv6 route rip
IPv6 Routing Table - 7 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
      D - EIGRP, EX - EIGRP external
R   2001:2:2::/64 [120/2]
     via FE80::2, FastEthernet0/0

R2#show ipv route rip | in R
IPv6 Routing Table - 9 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
              D - EIGRP, EX - EIGRP external
R   2001:1:1::/64 [120/2]
     via FE80::1, FastEthernet0/0

R2#show ipv route ospf  | in O
       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:3:3::3/128 [110/1]
     via FE80::3, FastEthernet0/1

Ok all looks good, now let’s mutual redistribute between RIP and OSPF on R2

ipv6 router ospf 1
 router-id 2.2.2.2
 log-adjacency-changes
 redistribute rip RIP
ipv6 router rip RIP
 redistribute ospf 1

Now let’s check the routes on R1 and R3

R1

R1#sh ipv6 route rip  | in R
IPv6 Routing Table - 7 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
       D - EIGRP, EX - EIGRP external
R   2001:2:2::/64 [120/2]
R   2001:3:3::3/128 [120/2]

R3

R3#show ipv6 route ospf | in O      
       O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
       ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
OE2  2001:1:1::/64 [110/20]]

As you may have noticed, the transit links between R1-R2 and R2-R3 were not included in the redistribution. in IPv4 we would have seen the R1-R2 subnet in OSPF routes on R3 and the R2-R3 subnet in R1 RIP table, this is not the case in IPv6, needless to say we need to source our traffic from the loopback interfaces on R1 and R3 if we want to have reachability between the two routers

R3#ping 2001:1:1::1                 

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

R3#ping 2001:1:1::1 source loopback 0

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:1:1::1, timeout is 2 seconds:
Packet sent with a source address of 2001:3:3::3
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/40/44 ms

We can override the default behaviour by using the include-connected on R2 when we are preforming the redistribution

on R2

ipv6 router rip RIP
redistribute ospf 1 include-connected
!                     
ipv6 router OS 1
redistribute rip RIP include-connected 

we should see the transit links on R1 and R3 after including the connected on R2

R1#sh ipv6 route rip  | in R
IPv6 Routing Table - 8 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
       D - EIGRP, EX - EIGRP external
R   2001:2:2::/64 [120/2]
R   2001:3:3::3/128 [120/2]
R   FC00:23:23::/64 [120/2]


R3#show ipv6 route ospf | in O
       O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
       ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
OE2  2001:1:1::/64 [110/20]
OE2  2001:2:2::/64 [110/20]
OE2  FC00:12:12::/64 [110/20]

Excellent that worked, also we can verify on R2

R2#sh ipv6 protocols
IPv6 Routing Protocol is "connected"
IPv6 Routing Protocol is "static"
IPv6 Routing Protocol is "rip RIP"
  Interfaces:
    Loopback0
    FastEthernet0/0
  Redistribution:
   Redistributing protocol ospf 1 include-connected
IPv6 Routing Protocol is "ospf 1"
  Interfaces (Area 0):
    FastEthernet0/1
  Redistribution:
    Redistributing protocol rip RIP include-connected

Comments

Post a Comment

Popular posts from this blog

BPDU Filter vs BPDU Guard

        Today we will try to explore the difference between these 2 options, BPDU guard and BPDU filter We know that BPDU are used to communicate between switches in L2 networks  to ensure loop free topology. BPDU Guard is used to protect our access (or trunks incase of servers) ports from receiving undesired BPDU packets, this feature is helpful in enforcing your network boundary in access layer BPDU Guard can be enabled on global configuration as well as under the interface configuration BPDU Filter on the other hand is used to filter BPDU packets outbound when configured  in global configuration (after sending 11 BPDU out ) and will filter BPDU inbound/outbound when configured under the interface level To better understand these two features, let’s use this simple topology R1 is connected to SW1 through F0/0 to have R1 send and receive BPDU we will simple configure bridging group 1 on the router and we will join the bridge group when desired to test our configuration BPDU
Read more

BGP Weight Attribute

Image
Before we start the lab let's see the BGP path selection process If the path specifies a next hop that is inaccessible, drop the update. •Prefer the path with the highest weight. •If the weights are the same, prefer the path with the largest local preference. •If the local preferences are the same, prefer the path that was originated by BGP running on this router. •If no route was originated, prefer the route that has the shortest AS_path. •If all paths have the same AS_path length, prefer the path with the lowest origin code (where IGP is lower than EGP, and EGP is lower than incomplete). •If the origin codes are the same, prefer the path with the lowest MED attribute. •If the paths have the same MED, prefer the external path over the internal path. •If the paths are still the same, prefer the path through the closest IGP neighbor. •Prefer the path with the lowest IP address, as specified by the BGP router ID. I read this on CCIE Pursuit blog We Love Oranges As O
Read more

OSPF–Point To Multipoint Non-Broadcast

Image
Using same setup that we have been using in the last 3 posts, we will change the network type to point-to-multipoint Non-Broadcast we will also add a Ethernet link between R2 and R3 and enable OSPF on it Our final configuration should be something like this R1 interface Serial0/0   no ip address   encapsulation frame-relay   no frame-relay inverse-arp ! interface Serial0/0.123 multipoint   ip address 10.1.123.1 255.255.255.0   ip ospf network point-to-multipoint non-broadcast   ip ospf 1 area 0   frame-relay map ip 10.1.123.2 102   frame-relay map ip 10.1.123.3 103 !          router ospf 1   router-id 1.1.1.1   log-adjacency-changes   neighbor 10.1.123.2   neighbor 10.1.123.3 R2 interface Serial0/0   no ip address   encapsulation frame-relay   no frame-relay inverse-arp ! interface Serial0/0.123 multipoint   ip address 10.1.123.2 255.255.255.0   ip ospf network point-to-multipoint non-broadcast   ip ospf 1 area 0   frame-relay map ip 10.1.123.1 201 R3 interface
Read more