This is one of multiple videos discussing IP version six routing.
In this example, rather, one and router two are connected via a serial interface.
These routers have just booted up and have no configuration apart from a default Janus three configuration.
So as an example, if we use the command show IP interface brief.
We don't see any IP addresses configured on the routers.
And all interfaces on the routers are shut down.
Show IPV six route shows no routes in the IP version six routing table.
Because no IP version six addresses have been configured on the rider and we can see that by using the
command show IP Version six Interface Brief.
Output gives us similar information to what we would see using show IP.
Interface brief.
All interfaces are shut down.
So on rata one, I'm going to enable IP version six unicast routing.
And then go into the serial interface and know shut the interface and configure an IP version six address
of 2001.
Colon one.
Colon.
Colon one slash 64.
Now when we look at the IP version six routing table.
We see that a.
Connected Network exists as well as a local network.
The local network is the IP address configured on that interface.
So this is the IP address that's configured on the Serial Zero interface, which we can see as follows.
We're using a slash 64 mask, so the connected network is displayed with a slash 64 mask, but the 128
bit IP address is shown in the output as well.
Routers will create IP version six routes based on the unicast IP version six address configured on
the interface.
So this command results in this network appearing in the routing table.
The router also creates the host route or local route using 128 bit prefix for the IP version six address
configured on the interface.
If we shut that interface down.
And then look at the routing table again.
You can see that the IP address has been removed from the routing table.
So in the same way as we have with IP version four.
The rot only appears in the routing table when the interface comes up.
So interface serial to slash zero is now up up so we have the subnet or connected route and to the local
route or host route added to the routing table.
If the interface goes down, the route is removed from the routing table.
I'll create a loopback address on this router with an IP version six address of 2001 face colon one
colon colon one slash 64.
So show IPV six route should show us that that route is added.
Here it is.
There's the Connected Network and there's the local or router IP address on Ryder two.
We still don't have any IP addresses configured, so show IPV IPv6 route shows us no routes in the IP
version six routing table.
I'll enable IP version six unicast routing and then go into the serial interface and no, shut it.
And configure an IP version six address on the interface of 2001.
Colon one.
Colon.
Colon two.
Slash 64.
While I'm here, I'll configure the loopback address.
As you can see, the serial interfaces now come up on both sides.
So the loopback interface will be 2001 colon face colon to colon.
Colon one.
So show IPV six root.
We can see multiple routes in the routing table.
Here's the connected route for the serial connected route for the loop back local route or rather route.
For the serial and loopback.
Now Wall rather to be able to ping rather one on the serial interface.
Answer is yes, and that's because they directly connected to one another and they are configured in
the same subnet.
So rather one can also ping rather to.
We can prove that by doing a debug.
Commands are very similar to IP version four.
So debug IPv6 ICMP.
When we do the ping, we can see the output here in a similar way to IP version four.
Notice IP version four shows no ruts in the routing table because we haven't configured any IP version
for addresses on these routers.
This network is running a pure IPv6 implementation wool router to be able to ping the loopback of router
one.
What do you think?
We'll write it to be able to ping the loopback of router one.
Debug IP packet will show us the result.
So let's ping the loopback of right of one.
A request is being sent and I did the wrong debug there.
Be careful of that mistake.
Let's use debug IPV six packet rather.
And see what happens now.
So this is better.
We can see an echo is being sent.
Just stop that ping now.
So an echo is being sent.
The Rudd has picked this address as the source address.
In other words, the serial interface or outgoing interface is used as the source address for ICMP traffic.
Something very similar will happen in IP version four.
So it's trying to send an echo to that address using this local IP address.
With a destination set to that and the important piece is noticed.
Route is not found.
Again.
Rot is not found.
The rudder cannot send traffic to that destination network because it doesn't appear in their IP version
six routing table.
So what we need to do here is configure static routes in this example because we're using a serial interface
we can configure.
A route using the local outgoing interface.
So very similar to IP version four, we're going to use the IPV six Route Command.
And specify the destination right.
Which is 2001 face colon one.
Colon.
Colon A64 and the local outgoing interface is going to be serial to slash zero.
So now.
Can we ping that network?
Yes, we can.
We're getting a lot of debug information.
So I'll turn off the debug.
Scrolling up.
You can see that the ping succeeded.
And if we do that again, notice we can ping the loopback of router one.
Now rather one doesn't know.
About the loopback of router two, so we need to configure that.
So IPV six route destination is 2001.
Colon Face colon two.
Colon.
Colon one.
Slash 64.
Out going into face is going to be serial 2/0.
So sho IPV six root.
We can see that route added to the routing table.
And we should be able to ping 2001 face to colon colon one.
And that works.
So again, just like with IP version four, you need to have a route in the routing table to be able
to reach a destination network.
In this example, we've added routes using study grants to the IP version six routing table and using
the local outgoing interface rather than next hop address.
So show run pipe include rat shows us that we are using the outgoing local interface to get to the destination
network that works well in a point to point serial connection such as this, but won't work well when
using Ethernet.
When using Ethernet, you should use the next hop IP address.
Now these routers are using CE 3725 software version 12.4 of the iOS.
In a subsequent video, I'll configure static route using next hop IP address, but I'll use version
15 software and I'll use viral images to do that.
I hope you've enjoyed this video.
If you have, please like it and please subscribe to my YouTube channel.
I wish you all the very best.