Pete's Packet

R7(config-if)#ipv add 2000:1:1:7700::/64
% 2000:1:1:7700::/64 should not be configured on Loopback0, a subnet router anycast

solution =   eui-64   Use eui-64 interface identifier = “The host portion of the IPv6 addresses

should be based partly off of their interfaces’ respective MAC addresses.”

Loopback0                  [up/up]
FE80::20D:BCFF:FE0F:D100
2000:1:1:7700::
2000:1:1:7700:20D:BCFF:FE0F:D100
!
interface Loopback0
ip address 200.0.0.7 255.255.255.255
ipv6 address 2000:1:1:7700::/64 **** this was not deleted when I deleted it earlier!!!
ipv6 address 2000:1:1:7700::/64 eui-64
!

RIPng
Enable globally and on the interface:
ipv6 unicast-routing
ipv6 router rip cisco67 <——————

interface Loopback0
ip address 200.0.0.6 255.255.255.255
ipv6 address 2000:1:6600::/64 eui-64
ipv6 rip cisco67 enable <—————–

========================

ipv6 over ip GRE tunnel
r2 – cisco12 RIPng is already enabled.

interface Tunnel26
no ip address
ipv6 address 2000:1:1:78::7/64
ipv6 rip cisco12 enable
tunnel source 150.50.100.2
tunnel destination 150.50.100.6
tunnel mode ipv6ip

r6 – need to add the RIPng routing process in global(cisco12)

interface Tunnel26
no ip address
ipv6 address 2000:1:1:26::6/64
ipv6 rip cisco12 enable
tunnel source 150.50.100.6
tunnel destination 150.50.100.2
tunnel mode ipv6ip

Check to make sure the RIPng is enable globally and on the interace.
===================================

ipv6 router rip cisco67
redistribute rip cisco12
!
ipv6 router rip cisco12

R6(config-rtr)#ipv6 router rip cisco67
do sho run | be ipv6 router

ipv6 router rip cisco67
redistribute rip cisco12
!
ipv6 router rip cisco12
<————————where is the command I just entered? Odd Can I only add it once under a routing process? When I add the redistribute with a metric then I do see it on both process’.
solution:
ipv6 router rip cisco67
redistribute rip cisco12 metric 4
!
ipv6 router rip cisco12
redistribute rip cisco67 metric 4

R7(config-if)# do ping 2000:1:1:1100::1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2000:1:1:1100::1, timeout is 2 seconds:
….. <——————————–can ping it?
Success rate is 0 percent (0/5)
–> same as with IPV4 we are missing our connected routes during redistribution. Since R7′s source address will be the Ethernet between R6 and R7 (2000:1:1:67/64), R1′s routing table won’t have that information. (R1 does not have a route to 2000:1:1:67/64. But it does have a route to R7′s loopback (R   2000:1:1:7700::/64 [120/6]) This is because when we redistributed cisco12 and cisco67 we only redistributed what was in the routing table for those two process’.

R1 does not see 2000:1:1:6600::/64  because that’s a connected interface on R6, the redistributing router. R1 does not see R7 f0/0  2000:1:1:67::7 because it’s a connected interface on R6  2000:1:1:67::6 and that is not redistributed. r6 and r7 will not have rip routes to each others directly connected 2000:1:1:67::/64 interfaces.
When redistributing the connected interfaces will need to be redistributed. Your only redistributing routing information.

* The solution is to redistribute the connected interfaces under both routing process’ on R6

ipv6 router rip cisco67
redistribute connected route-map Myconnect
redistribute rip cisco12 metric 4
!
ipv6 router rip cisco12
redistribute connected route-map Myconnect
redistribute rip cisco67 metric 4
!
route-map Myconnect permit 10
match ipv6 address Mine
!
!
ipv6 access-list Mine
permit ipv6 2000:1:1:6600::/64 any
sequence 30 remark this is r6 loopback0
permit ipv6 2000:1:1:67::/64 any
remark 2000:1:1:67::/64 is the ethernet
permit ipv6 2000:1:1:26::/64 any
remark 2000:1:1:26::/64 is tunnel26

Or on R6 tun26 and e0/0 we could have said ipv6 rip [cisco12 |cisco67]cisco default-information

originate
===================================================

? config r7 so that r1 (cisco12),r2 (cisco12/67),and r6(cisco12/67) can ping 2000:1:1:8800::8/64 do not redistribute and RIPng instances.

solution:
R7
interface fa 0/0
ipv6 rip cisco67 default-information originate

interface Serial0/0
ipv6 rip cisco8 default-information originate

1. config both the ipv6 address and the link-local address (preferably do that link local matches the router, eg fe80::5 link local)
2. When configuring frame maps config both ipv6 and the link local.
3. don’t forget the router id in ospfv3
4. you need ipv router ospf 1 and interf ipv6 osp 1 a 0
5. don’t forget to set up your frame maps ( should be the same as in ipv4 int cfg)
6. ipv6 treats misconfiguration ip addresses as secondary ip’s so double check with sh run int  to see if you have any mistakes and extra IP’s.
7. don’t forget to add fram maps and virtual-links where needed. (draw it out)
8. sh bgp ipv6 unicast summary = sh ip bgp sum.
9. IPV4 we are missing our connected routes during redistribution. Since R7′s source address will be the Ethernet between R6 and R7 (2000:1:1:67/64), R1′s routing table won’t have that information. (R1 does not have a route to 2000:1:1:67/64. But it does have a route to R7′s loopback (R   2000:1:1:7700::/64 [120/6]) This is because when we redistributed cisco12 and cisco67 we only redistributed what was in the routing table for those two process’. R1 does not see 2000:1:1:6600::/64  because that’s a connected interface on R6, the redistributing router. R1 does not see R7 f0/0  2000:1:1:67::7 because it’s a connected interface on R6  2000:1:1:67::6 and that is not redistributed. r6 and r7 will not have rip routes to each others directly connected 2000:1:1:67::/64 interfaces.
   When redistributing the connected interfaces will need to be redistributed. Your only redistributing routing information.

   * The solution is to redistribute the connected interfaces under both routing process’ on R6