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

IPv6 EIGRP

Image
In this post we will try to configure IPv6 EIGRP see the different options for the protocol and how these options are almost identical to the IPv4 version of EIGRP configuration R1 ipv6 unicast-routing interface lo0 ipv6 address 2001:1:1::1/64 interface FastEthernet0/0   ipv6 address FE80::1 link-local   ipv6 address FC00:1:12::1/64 ! interface FastEthernet0/1   ipv6 address FE80::1 link-local   ipv6 address FC00:1:13::1/64 !          R2 ipv6 unicast-routing interface lo0 ipv6 address 2001:2:2::2/64 interface FastEthernet0/0   ipv6 address FE80::2 link-local   ipv6 address FC00:1:12::2/64 ! interface FastEthernet0/1   ipv6 address FE80::2 link-local   ipv6 address FC00:1:23::2/64 R3 ipv6 unicast-routing interface lo0 ipv6 address 2001:3:3::3/64 interface lo1 ipv6 address 2001:3:4::3/64 interface lo2 ipv6 address 2001:3:5::3/64 interface FastEthernet0/0   ipv6 address FE80::3 link-...
Read more

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...
Read more

Private VLANS and protected ports

Image
In this post we will try to learn two layer 2 technologies, private vlans and protected ports Private vlans is used to segregate the layer 2 domain within the same vlan so we don’t waste any IP addresses, think about as sub-vlans within the same vlan that share the same layer 3 address. These sub-vlans can be of two kinds                      1- Community 2- Isolated The difference between community and isolated sub-vlans that hosts within community vlan can communicate together however hosts within isolated vlans con’t communicate to each others, also note that hosts from different community vlans can’t communicate/isolated vlans can’t communicate together. The question is how these hosts in community/isolated vlans communicate to the outside world, and the answer is they communicate through the promiscuous port which is part of parent vlan but this port is allowed to communicat...
Read more