- [Narrator] All right.
We're gonna run out to the corp router
and configure static routing
then we'll run out to San Francisco and LA
and do a default route which is easy.
I don't even need a figure for that one.
But with static routing,
you are well aware that we need a figure.
In this case here,
the corp router is connected to
subnets one, six, seven and eight.
San Francisco's connected to subnet two on the far end
and LA to subnet three.
So the corp router needs a static route to subnet two
and to subnet three, so just two static routes
because I'm not using the loop backs by the way,
and then the LA and San Francisco routers
just need a default route.
So let's run out to corp and put in a route to subnet two
and a route to subnet three.
So here at my corp, we'll say ipv6 route
and we'll say 2001:db8:3c4d
and I wanna go to colon two
so ipv6 route destination network
and I'm putting in a network ID
so my host IDs are all zero here.
And I'm gonna use the exit interface, right, so ipv6 route.
I could use the next hop,
but why would I wanna type all that in
on a serial point-to-point link?
That makes it really easy.
Wow, I just did a static route with ipv6
to this San Francisco router using my exit interface,
serial zero one one.
Now I'm gonna just up arrow, change the subnet and say,
"Hey, well, to get to network, we wanna get to network three
"and I'm gonna go out serial zero zero one."
Wow, I'm done.
Let's do this, do show ipv6 route.
Let's see what we see.
All right, looking at the third from the top,
we have our connected, our link,
and then we have two static routes,
one to subnet two and one to subnet three.
They look exactly like an ipv4 output expect they're ipv6.
We still have the administrative distance slash metric
and via the exit interface
and that they're showing up as directly connected
because I used my exit interface.
Had I used the next hop,
it wouldn't have shown up as directly connected.
Now that we have our static routes configured
on the corp router going to the remote LANs for
San Francisco and LA,
let's run out to San Francisco and LA
and let me show you how easy it is to do default routing.
Since this is our stub network and we're directly connected,
we can just say config t ipv6 route colon colon all zeroes
mask of zero and then my exit interface of zero one one.
I am done with routing on San Francisco.
Now two things, I'm a stub router
and I'm directly connected to the corp
and using my exit interface.
I wouldn't wanna do this if I wasn't.
All right, now, that's how easy it is
for something like this though.
Telnet LA and I have to use the word telnet here
or the command telnet because there's a command
that starts with LA, then it does recognize it.
All right, same thing here, ipv6 route all zeroes,
zero mask and I can use either one of my exit interfaces.
That looks right and we're done.
So let's go ahead and take a look at a couple of things.
Show ipv6 interface brief
and I can see my IP addresses very simple.
They just have a colon colon one.
I actually didn't allow it to make it up.
I could use the EUI 64, but I just went ahead
and gave it to the interfaces.
So we can see it for the fast Ethernet serial
and so if I did a show ipv6 route,
I'll be able to now see the static route up on top
via my exit interface which shows directly connected.
Let's go back to the corp router and let's ping
and that's colon colon one for subnet three
is the subnet off of the LA router
and let's see what happened, boom, right.
So pretty simple.
You're like, "How do you remember that?"
Well, I just had the host IDs as colon colon one
and my prefix is always the same.
All right, one last thing and then we're gonna go ahead
and wrap this up, but here's want I wanna do.
Interface f zero zero, I wanna show you how to do RIPng.
I know that's not part of the objectives,
but a lot of times they throw things in anyways.
I just want you to be familiar with it.
Notice I'm on an interface level,
ipv6 rip, a process ID and then enable.
That's it.
There's no network command, nothing.
I'm done.
So now I'm just gonna choose my other interfaces.
I'm on the corp router so which means serials are one one
and then up arrow twice
and then interface serial zero zero one
and interface s zero one zero.
I've now configured RIPng.
This is another reason I showed you.
It's fast, it's easy, just as easy as static routing
in this case and I'm done.
Now, I've already configured RIPng
on the San Francisco and LA routers,
but it didn't work because I was using static routing
with a lower administrative distance, right?
So as soon as I turn this on, we should see show ipv6 route.
If I didn't have my static routes in there,
I would have rip routes.
But because, if we look at this, the first static route here
2001 db8 3c4d colon two colon colon slash 64 one zero says
administrative distance of one.
Unless I go and take those out,
the RIPng isn't going to work.
But I just wanted to show you how easy it was to do that.
So in this section,
we saw how easy it was to configure a static route
on the corporate router to San Francisco and LA
and then a default route on each of my other stub routers.
It's important to understand that without a network map,
this wouldn't have occurred.