Dear:
kindly complete the rest of of the IPV6 with video solution
IPv6 OSPFv3
Scenario:
After waking up from cryosleep the year appears to be 2020 and there is not a single IPv4 address left on the planet. The last thing you remember are the stories about the end of IPv4 and the migration plans for IPv6...now it seems this is all reality! It's up to you to configure OSPFv3 and make the network operational...resistance is futile ;)
Goal:
- You are not allowed to use IPv4 addresses.
- You are not allowed to use any IPv6 global unicast addresses except the ones on the loopback interfaces.
- Use the MAC-address for the last 64 bits of the IPv6 addresses required for the FastEthernet links.
- Configure OSPFv3 and achieve full connectivity between the networks on the loopback interfaces.
IOS:
c3640-jk9s-mz.124-16.bin
Topology:
Video Solution:
You need to register to download the GNS3 Topology File. (Registration is Free!)
- Related Articles
Only registered users can write comments!
Comments (6)
-
Kaage 2011-07-30 12:27:55Not probably the best idea to have overlapping subnets in loopback interfaces.
-
ReneMolenaar 2011-08-01 21:47:36@Kaage you are so right......stupid mistake ;D just fixed it by using /128 for the loopbacks.
-
fliprich 2011-10-18 12:31:28Great! Thanks for the help Renee.
-
fliprich 2011-10-18 10:38:08
I actually did some additional experimenting with this lab to answer some questions that I had. But I have one more:
Is it natural for dynamically learned routes to use link-local addresses as next hops? I actually configured some global addresses on the f0/0 interfaces between Vulcan and Romulan but the routing table still had link-local next hop addresses for the loopbacks. Is this a natural thing? It still works, but I was just curious.
-
ReneMolenaar 2011-10-18 11:59:34
Hello Fliprich,
Good question. IPv6 uses link-local addresses for the next hop so the behavior you see is normal. This means you don't need any global unicast IPv6 addresses anymore on point-to-point links.