- We're gonna start adding some configuration
to these devices.
So we're gonna add IP addresses and static routes.
By the time we're done with this particular section
we still will not have end-to-end connectivity,
because we haven't completed our VLAN configuration
and spanning tree yet,
so we will not have end-to-end connectivity
at the end of this section yet.
So let's go ahead and add our IP addresses,
and static routes where they need to be.
So, let's bring our topology diagram back in to play.
And in case you had not already taken a screen shot of this,
you will want to,
because these are the IP addresses
we're gonna want to implement.
Now once again, when you're building this,
you can use whatever IP addressing you want,
I just chose this to make it simple.
Okay, so I'm going to start with,
let's start just working from left to right.
I'll start with router-1,
and I will turn him on.
I've got quite a few devices in this topology
so I may not want to turn them on.
Let's see here actually I've only got one, two, three, four,
I've got five IOS devices, so it's probably
pretty safe to turn them all on at once.
Okay, so let's go ahead and go into router-1 now.
As that's coming up, it's gonna be fast ethernet 0/0
on this particular router that we're gonna want to configure
as an 802.1q trunk.
So we're basically configuring what's called a router
on a stick as this point.
The interface fast ethernet 0/0.
All we have to do here is no shut.
But before I do that,
I'm gonna wanna create my sub-interfaces.
And I'm supporting VLAN's four and five, so I'll do
subinterface four to begin with.
It could be any number I want, I'm just choosing that.
Encapsulation dot1q 4,
That makes sure that he understands that 802.1q tags,
and that anything that arrives with a tag
value of four, or needs to leave with a tag value of four,
the VLAN of four, will use this particular sub-interface.
And then select the correct IP address.
Alright, and then rinse and repeat.
Do the same thing for our next sub-interface.
I'm just using the up arrow here
to go through my command history.
Just making slight changes as we go along.
Okay, now before I leave this,
I also need to put in a static route,
and then the last thing I'll do
is bring up that physical interface.
Alright so static route.
Why don't we just create a single default route in this guy?
Because really there's only one way out on him,
he doesn't have multiple egress points.
So IP route 0.0.0.0 0.0.0.0,
that says anything you don't know about,
let's have him go to...
Well he's got two possible people he could go to,
VLAN-4, or VLAN-5 on his
counterpart which is router-2.
So doesn't really matter, we'll just select one of them.
Let's select in this particular case...
Let's do it this way.
Let's bring in this drawing here.
Let's configure Router-1 so that if he's trying to get
to the 2.3.2 network,
he'll go across VLAN-4,
and if he's trying to get the 3.2.3 network,
he'll go across VLAN-5.
So that will necessitate two different
static routes in router-1.
Alright so, to get to the 2.3.2 network,
your next hop is gonna be 1.2.4.2
and to get to the 3.2.3 network,
your next hop will be 1.2.5.2,
and now the last thing is we need to go back into his
physical interface and bring it up.
Save our configuration.
Okay so we are done with that router.
I can get rid of him.
Now as far as IP addressing is concerned,
let's go over to the far right,
and go to router-3.
Configure router-3.
It's gonna be pretty much the same
kind of thing as we did in router-1.
So I'll just start by configuring my static routes,
IP route 1.2.4.0
255 255 255 0
and we want that to go to the next hop of 2.3.2.2,
an IP route of 1.2.5.0,
we want that to go to 3.2.3.2.
Okay that'll accomplish load balancing on that side,
and then go to interface fast ethernet 0/0,
let's make sure it really was 0/0,
yep 0/0,
okay so we're dealing VLANs two and three here,
so I'll make this sub-interface-2 ,
encapsulation dot1q 2,
IP address 2.3.2.3
and then we'll create a sub-interface vlan-3.
3.2.3.3
and then lastly
we'll bring up our physical interface.
And save that configuration.
Okay, so we're done with router-3.
Now let's go over and configure the IP addressing
on router-2 here in the middle.
Okay, so let's start with his fast ethernet 0/1,
so we're not trunking on these two interfaces,
these are just regular routed ports
with just a single subnet.
So, interface fast ethernet 0/1
that's going to be IP address of 2.3.2.2,
no shut,
and the other one if fast ethernet 1/0,
IP address 3.2.3.2,
no shut.
Okay, and now we have to configure fast ethernet 0/0
as a trunk.
Now before we do that,
at this point we should have end-to-end IP connectivity
between router-2 and router-3,
we already previously created the VLANs
and created the trunks in switch-1,
now we've completed our router on a stick
over here on router-3,
and we've configured our IP addresses on router-2,
so we should be able to ping our directly connected routers
across that link,
let's see if we can.
If not we have we'll have to
do a little bit of troubleshooting.
So I'm on router-2 right now,
ping 2.3.2.3
he's arping for it,
great, success,
ping 3.2.3.3,
he's arping for it,
and success.
Wonderful.
Okay so now we just have one little step left
on router-2 we gotta configure this side over here
as a router on a stick,
by making a trunk.
So interface fast ethernet 0/0.4
to support vlan-4,
encapsulation dot1q 4,
IP address 1.2.4.2,
and sub-interface for vlan-5,
which will be 1.2.5.2,
okay, save the configuration.
Now in this particular case
there are no static routes necessary on router-2
because every single subnet in this topology,
he's directly connected to.
There's no subnets here that he's not actually
connected to on some kind of interface,
so we don't need any kind of static routes
configured on him.
And that concludes this particular section,
this section was focused on adding IP addresses
and static routes and we have done that,
so now in the next sections,
we're really gonna get into the meat
of configuring switching commands
on our EtherSwitch routers.