Original subtitles

>> Welcome the new saga.

We've moved out of Switching and into Routing.

And appropriately so, if you're moving to these series in order

which I really encourage you do 'cause it would be kind of weird.

It's like watching a movie out of order.

We just finished up with VLANs and we kind of have these hosts that are now

in separate worlds, they're in separate networks but we never really answered the question,

"Well what if that host wants to get out of its world?

What if it wants to get off of its VLAN?"

That's where Routing comes into plan, and this is where it all begins.

So in this nugget, we're going to look at what I would call Routing Core, as in what is Routing?

Lets' define.

Let's get it on, on paper where we go, okay.

This is the definition we get.

Then we'll look at the Cisco Routers themselves, as in let's look at the hardware.

What do they look like?

What do they feel like?

What kind of interfaces do they have?

Can I change those?

All those kinds of questions.

And then finally, I'm going to cram in here the Basic Router Configuration and I put Review

on there because it's the same thing as the Switch.

It's just now on the Router because both devices use a common IOS.

Let's start of like bringing it back to the big picture.

What is Routing?

Note until now in the series, we've been focused on this which is the Switching environment,

creating VLANs, doing the basic config, managing the Switch,

speed and duplex, all those kinds of things.

It's all sitting there within the Lan.

Now, that, you know, essentially, all of these, let me draw the square.

All of these represent one network.

As soon as you hit the Router, you've created a divide in the network.

So let's define the network.

The network is a logical thing, as in, it's based on the IP Protocol

so when I define my subnet-- my IP address range, I might say something like, "Let's go.

This site is 192.168.1.0/24.

It's like half of the homes in the world, use that.

That's so [inaudible] 'cause that's where all the, widgets you buy like, D-link,

Netgear, that's what they do by default.

So what that means is everybody that's connected to that Switch, assuming--

now, this is assuming 'cause I know we just cut down with VLANs, there's no VLANs.

So this is all VLAN 1, essentially on that Switch, you know.

This is guy is 0.50, this guy is 0.51, whatever IP addresses from that network you'd want.

Now, this guy would likely be 0.1.

It doesn't have to be but most commonly is, either the first or the last IP address

from the subnet because this guy will use, you know, or I should say both

of these guys will use that as their default gateway, 192.168.1.1.

So they're ready to get off their subnet.

They want to come over here.

Now, again, new Router interface.

This is a new network.

So this is network 1.

This is network 2.

And actually, in reality, this is network 3.

And that's the job of a Router.

It's to start moving that data between the networks.

So maybe on the right hand side, this is 192.168.2.0/24.

Again, first three octets represent the network.

So everybody realizes that's a new network.

That' the host 0.50 on there and that's 0.1-- that's 192.168.2.1 on there.

Now, what will happen is this guy will grab his-- let's say we grab a command prompt on him

and we type in the command Ping 192.168.2.50, what happens?

Well, he's going to look and he goes, "Okay, wait a second.

I am part of the 192.168.1 network.

That's not good.

That's on my network.

I just sense that since I go-- it's just like, as I could.

He's just like-- that device is not on my network."

So I realize that I'm not going to be able to send an ARP message and reach him

because that's how it normally talks.

It sense out an ARP, a broadcast to everybody saying, "Hello, who is this?"

But it-- oh, that's not going to work because he is on a completely different subnet than me.

That means I have to go through my Router.

So instead of sending an ARP for 192.168.2.50 which he knows we'll not make it.

He sends an ARP for 192.1681.1.

Now, why is he doing that?

'Cause that has been pre-configured you as an admin

or DHCP pool has pre configured that as his default gateway.

So broadcast message goes out saying, "Hello, I need the MAC address for 192.168.1.1."

This guy comes back in response.

It says, "Oh, that's me."

He goes great.

I want to use you to reach this guy over here.

So what he's going to do is assemble a packet.

So his messages are Ping, right, he's pinging the other side.

Source IP address is going to be himself, 192.168.1.50.

Destination IP address will be this guy over here.

That's where he's finally going, 192.168.2.50, right?

That's it's where it wants go.

Now, source MAC address, now, we're talking on the local network.

So I have to cross the local network to get to this.

So source MAC address will be him, whatever it is.

Let's just say it's 1111.

That will be his source.

The destination MAC address will be whatever the Router is.

So we'll say he's 2222.

That will be the destination.

So essentially, from a Switch perspective which only looks at layer 2 information,

the Switch you see is "Okay, you are 1111 going 2222.

So it takes him from here to here.

Now, the Router gets that and he goes, "Okay, you're trying to reach me.

I see that based on the MAC address.

Great! So I'll process you but I'm noticing that you're not trying to really get to me.

You're trying to go through me.

Not to me.

You're going to 192.168.2.50."

Now, we come to a concept which will be big for us as we expand Routing.

He looks at his Routing table and he's going to say,

"Do I know how to get to 1922.168.2 network?

Do I know how to get there?"

If he doesn't, that's the end of our story.

It's rather short.

[laughter] And the Router's like, "I don't know how to get there."

Drop, drop, drop, he starts dropping those packets.

But hopefully, someone-- that's you.

You would've gotten involved at some point and told him, "Hey,

to get to the 192.168.2 network, you need to go to this guy."

Now, enter network 3.

We'll just say, let's just make it for doing something way different.

We'll say network 3 is 10.1.1.0/24-- maybe he's 0.1, he's 0.2.

So in my Routing table, I would've put some kind of entry.

I would've educated my Router to know, to get this 192.1682 network.

He needs to go to 10.1.1.2 as a destination IP address.

So this guy will then say, "Okay, well I'm going to send it to you now."

Now remember, there's a whole MAC address story that we've left behind in the Switching world.

He's actually going to take the original source and destination MAC and get rid of it, right,

because that's only valid right here.

Now, he's on a new network so he's going to fill in the source MAC address from this interface

and the destination MAC address of this interface, you know, right there.

So we'll have new ones get to this guy.

Once again, this guy gets-- its like, "Oh, oh a message for me."

And because he's looking at the MAC address, he's like "Oh, wait a second.

No, it's not for me.

It's for 192.168.2.50.

And he looks at his Routing table and he pulls it up and he goes,

"Well, wait a second, 192.1682.50.

Wait a second.

I'm plugged into that network."

That's connected right out fast to 10.0/0 will Sam is saying, and so he goes, "Well great.

Then I'm going to again, strip off the source and destination MAC address a second time

and replace it with the source and destination MAC address to allow this communication.

Now, obviously, I haven't drawn it in there but that line represents a Switch.

That's connecting.

These guys don't just have lines that connect them.

So they're going through the Switch and "Poof, we have communication.

We have one side talking to another and hopefully, back.

Now remember this guy has to have in his Routing table that we started up here.

He needs to know how to get back ton 192.168.1.0.

He needs to know how to get here in order for full communication to happen.

And I know it's easy-- well, that doesn't he-- isn't he smart enough to say "Well,

if it came from that direction, I must have to go back that direction."

Nope! [laughs] He's not.

You have to go in and educate this router either manually.

I'm going to give you some previews of where we're going.

That's called static routing where I can manually go in and tell where it to go

or we allow them to kind of figure it

out themselves using a routing protocol that's called Dynamic Routing

and the Routers will build their Routing tables, kind of by themselves but there's a lot

of thought that has to go in to that.

So this is what Routing is.

It's the process of moving packets between them and yet isolating them.

So all the broadcast on this network stay there.

All the broadcast here-- they won't be many of them but they stay there.

All of the broadcast here that we've separated the networks

and we can even put security boundaries in there.

We can put on things like access control list to say,

"Well this guy can get across but this guy can't."

So we put these dividing lines between these networks and really say, "Okay,

this Router has the authority and control of that entire network.

He is the manager of that network," so all of these routing is facilitated by a Cisco Router.

And the last thing I've mentioned, they are IOS-powered which-- we now know the IOS.

It's what we've been working in all along this operating system but they are CEF-enhanced.

What's that mean?

Well, I put that statement in there, IOS-powered,

to convey the fact that routers run on software.

The IOS is the brain behind the router.

They don't really have that much hardware to help them out.

Now, I'm kind of a enunciating my words because when we talk about switches,

there is that magically-- you remember this?

ASIC world, Application Specific Integrated Circuitry,

that's the hardware inside that's making those things move and move fast.

So packets are coming in at wire speed that switch can-- it's going like lightning.

Now, you hit the router.

The router does not have the same ASICs that a switch does

because it supports all the features.

While the switches are lightning fast,

they can't do all the kind of stuff that a router can.

They can't do stuff like NAT, Network Address Translation.

They're very limited on, for instance, the kinds of quality of service or access list

that they can support, if they can even do it at all.

You have to have a really expensive and bigger switch to do those kinds of features

but when you come to a router, you get all the features.

You can do routing protocols, you can do NAT, you can that, you know, fill in the blank.

They can do all of the key routing functions that we need but they do it via the IOS,

meaning they do it via software-- software processing.

Now, software.

Anytime you talk about software processing, it's always slower than hardware, always.

That's why, I mean, that's why we, you know, those of you gamers out there,

that's why you buy those big old 500 dollar video cards, right,

that make your video games go much faster because you've off loaded a lot

of your video processing to the hardware rather than your processor

or in your software trying to do it itself.

Same concept here, we've off loaded or I should say the IOS is

that software base plus it's slower.

So Cisco say, "We got to enhance that."

So they came out with this method called CEF where they move as much into hard wares,

as much into kind of cache processing.

CEF stands for Cisco Express Forwarding.

It's a way that a router runs.

We'll talk a little bit more about CEF later to try and optimize this routing table

so that it doesn't bug down the whole network.

But frankly, a router will never-- well, I shouldn't never--

a Router is not as fast as a switch because it doesn't have those same ASICs.

And just like with the switch, before we dive deep into the configuration of routers,

I want to like get you physically familiar them to where you can look at them, identify them,

understand what they're connecting to,

kind of like we saw how the cablings runs through the wall.

You have to patch panel and all that, right?

So what I'm looking at here is the Cisco 2800 series.

It's not the latest series of Cisco routers but it's the only one

that I could find a really good picture of online where they show a little stack of them.

And Cisco has all kinds of different router series that are available,

each one having different capacity, different sizes so.

I mean, you, as you go up in model numbers, you go up in price

but what you gain is increase capacity like it can handle more traffic going through it.

Also increase capacity in terms of modules.

It's like for instance, this guy right here-- I love that router.

I have one.

That was my lab router from years ago where it's a 1U, that means if you look in a rack,

you've got one unit of space that is consumed.

Usually typical racks, they range on the maximum but around 42U is a maximum size of rack.

So they don't eat up much space and then they have four modules.

Now, I know it's tiny but this is a picture of a 2801 without any modules installed.

So you can over here-- that mean this is a close up view, you see like the FAST ethernet,

the console portal, that kind of stuff.

And then there's four blank plates to where you can install your modules.

Now, just to give you an idea in terms of price, when you look at the Cisco router,

you're looking at the price, you're like, "Oh, yeah, it's kind of costly but it's not too bad.

I'll just wait.

[laughs] I'll just wait until you price out the modules.

Now, the one I just circled right there is there's a very old module but a lot

of these routers, I mean, you will likely eclipse the price of the router

by purchasing the modules for the router.

That's where-- I think a lot of functionally comes in.

So typical routers, it will say most Cisco router will have two, sometimes more but most

of the time two ethernet interfaces, meaning they have-- right here, you can see this is FAST

or GIG ethernet depending on the model of router you have.

And usually, they will be identified as FAST ethernet 0/0 and then FAST ethernet 0/1.

Now, I'm giving you generalities, every router is different.

And that, I mean, just getting used, I mean, some of these routers,

if you were to flip these guys around, they don't all have these little slots.

Some of them-- well like if-- if you took one of those guys and flip around,

a lot of these big modules, you know like, you know, take the-- this is like a 2U Router,

so double the size of this and it just has this big, open slots to where you can put

in a card that hosts these modules.

So you could have-- let me show you.

Not that my art is lacking by any means but if you would look

at this like here-- let me grab that.

It's look like a good picture.

So you can see.

This is a big-- see this-- this things right here.

These are kind of WIC modules.

That's what they call Wan Interface Cards or VIC, Voice Interface Cards

where you can put small, little modules inside.

That's what I'm showing you right here.

These are all those small little modules right there.

But on this bigger routers, you can get essentially these big modules that,

for instance, you can see this one module has two built-in.

It looks like I can't see but like FAST ethernet of Gigabit ethernet ports.

And then right here are two modules that you can slide in on top of that.

Maybe that give you serial ports and all of that.

So depending on the model of router you get, I mean, you really can duck these things out

and expand them and grow them with all kinds of different cards.

And the cards are where your functionality is.

The cards are, you know, your connections.

Sometimes, you'll have a card that's like a, for instance, they have a unity express module,

it's called CUE, Cisco Unity Express.

That's a voice mail module for a phone system to where it literally--

on a card, that slides in a router, they have a full blown voicemail system

or a security system.

I mean you get all kind-- the cards are where the functionality is at.

So that's where those fit.

So these routers will typically have two built-in,

ethernet interface is not always but most of the time.

So that alone just with no modules at all allow them to connect, you know, one network.

Here's a switch up here plugging into the FAST ethernet 0/0.

And then they can have another one connected to, you know, another switch up here or maybe,

a Cox [phonetic] or Quest or something, you know, brings in an internet connection

that you've plug in to FAST ethernet 0/1 and that can connect you to the cloud

or the internet, I should say, and then,

you kind of route between your internal network and the rest of a cloud.

Now, some of these are, for instance, like T1 interfaces, they're getting fewer and fewer

and fewer as, you know, new connection types are out there but I would say for a long time,

these kinds of interfaces will be out there.

They are technically serial interfaces.

This was the original old school.

Let me show how WAN connections look, right?

I mean, logically this is what we're doing.

We draw them like this.

We're like, "Okay."

Well, the office in Arizona is connected and we have this magic lightning bolt, right,

that connects over here to office in Colorado.

And we're like yeah, and that magic lightning bolt what happens.

Well, what's with the magic lightning bolt?

I mean tell me what's behind that domain.

Well if you were to really dig into it, you have service providers that are out there,

you know, here's the United States, right.

[laughs] So I'm just grabbing United States, that's horrific,

you know, over here is California.

I'm giving you some bearings, right.

Here's me in Arizona, and you have service routers that their job is to go

around the county, dig in, they've got shovels and that's what they do, they dig and they put

in cable and they put in cable and they put in cable and they put in cable,

they put in satellite dishes, they put in, you know,

things that allow you to reach things overseas.

They put in-- that's their job.

Now, I, you know, I don't want to have to, you know, if a buy an office in California

and I'm in Arizona, I don't want to have to get my shovel out and start digging holes

in the ground and running cable from my office to California.

It's just not efficient.

I'm going to pay somebody else to use their cable.

Welcome to the idea of a service provider.

So a service provider, let' say here's my Arizona office.

That line represents dry wall, right.

Outside of my office is this nice little patchy grass lawn

and little tree and all the kind of stuff.

I order-- I say, "Okay, I just got an office in California.

I call up service provider X and I say, "Hey, I'd like to buy a T1 line from you.

I'd like to-- I guess-- technically, I'd like to least--

that'd be more accurate, a T1 line from you.

I'd like least to use your cable that you've pulled out your shovel and you've dug

to California or you've dug maybe halfway to California and then partnered

with another service provider who dug the rest of the way.

I mean, there's all kinds of, you know, partnerships and this guy connects to that guy

and they pay him, blah, blah, blah, blah, all right.

So, you know, a service provider-- X comes in, he's like, sure thing, you know, that they say,

"That'll be, you know, what's a T1 cost,

maybe 250 dollars a month to get that connection going.

I say, "Okay, that sounds good."

So this is our truck.

They pull up.

They start walking across, they dig a little trench into your premises, and they put a line,

a wall jack right there and the say, "Okay, that wall jack represents our Demarc."

Now, I know, that's-- for some of you are like, "Ah, I know that word" some of you maybe not.

Demarcation point, what is that?

That's where the point of responsibility passes.

If something on that side of the demarc breaks, you pay for it.

If something on-- actually, I should be a real world.

If something on this side of the land breaks, they convince you that it's on that side

and you pay for it, but technically, you're supposed to--

they're supposed to pay for everything on that side of line, right?

But that's beside the point.

That's technically not ours.

So in the wall, we then take this line.

Now, let's talk about the old days.

In the old days, there would be-- we would take this line and plug it

in to this special device called a CSU/DSU.

And it was just-- think of it like a line converter because every vendor used

to have their own kind of interface that they would use.

There's actually, I think, five different types of serial connections

and this would convert the line coming in from the service provider which looks

like a normal ethernet cable, into a serial port that plugs in there.

And it does other things.

It's not just a converter, it does like diagnostics on the line,

making sure the line's okay, you know, measuring drops and traffic.

It does some stuff.

It's just a fancy modem.

It's really all it is and that-- that's how we do it in the old days.

Now, CSU/DSUs are all but gone from most places.

And now, this, you'll actually, if you look really close,

a lot of them say integrated CSU/DSU because, you know, technology has evolved.

We no longer need this big old box on the outside to convert it.

We can just run this line directly into our router, and now, we have a serial.

So this one might be like-- you notice, oh, you can't see that.

I can't see that.

It says, I think it says slot, two slot one, maybe not, so maybe--

maybe this is-- it's hard to see.

Slot-- [laughs] It's a slot number.

So let's just pretend that that says slot one.

So, you know, we plug it into, we'll say, that line right there

and that's now going to be serial one.

That's module 1/0.

So that's that port.

So we can give that an IP address and if we actually were to, you know,

fast forward over here in California, there's their dry wall, there's their wall jack

and they've got, you know, a router that's plugged in there.

So physically, that's kind of how it looks, you know, to where, you know,

that Router will then connect and, you know, go across that cable.

Now, we can talk to Arizona.

Is that-- is that makes sense.

It's kind of the, you know, so obviously, you don't want to draw trees and grass

and small insects and things like that.

So people just say "That's the lightning bolt."

So when you see a lightning bolt between two routers, you know,

if we're to kind of like expand that, that's what the lightning bolt really is.

Okay, what I want to wrap up with is the base configuration of a Cisco router.

Now, first thing I want to do is orient you to what kind of Router this is.

I've got 2621XM Router which-- what a great lab router that is.

So let me show you a picture so you can see what we're configuring.

And this a picture from Ebay because this is a very-- it's very old--

very old, let's say 2621MX probably, 2002-2003 but still very good.

I mean, usually, when you talk about technology that old, it's like,

"Well, that can be worth anything."

Well, actually it is.

It's a really good router.

There's still lot of them in production today but most people will use this as lab routers.

So you can see built in, right here,

I've got two ethernet ports, that's FAST ethernet 0/0, 0/1.

And there's my console port, the blue one.

The aux port is the black one, that's if I want to cut-- plug in a modem.

Switches don't have those, by the way.

Then up here, I have two little modules to where I've got slot one, slot two.

Those are for the little WIC modules WAN Interface Cards.

Now, I've got a big module where I can put all kinds of functionality, you know,

I can get one of this, that's an EtherSwitch module where you can kind of turn it

into a swarouter [phonetic] to where we've got, you know, we can actually run a whole office.

Like if it's a small office, you're like, "Hey, we've got 10 people

at this office" then you can just one of these little modules for the router and now,

you've got, you know, ten people that are able to plug in

and use all-- kind of all in one device.

Those things are pricey though I found, compared to buying just a normal switch.

So, you know, power supply.

I mean it's just a basic router.

So that's what we're going to start with.

And you might look at the slide and go, "Well, this looks familiar."

It is. It's almost exactly the same slide as the switch

because the base configuration between the two is the same.

So some of this will be new, some of it will be review.

So let's take a look.

So I just plugged in to the console port as router, no config on here.

First thing, I'm going to start of with actually a verification command.

Something I do often-- well, first off,

let's do show IP interface brief and get that that on the table.

So we can see, okay, this router I'm looking down at it right now.

It's got a couple of-- as you saw it from the image, FAST ethernet 0 and 01

and then I've got two serial ports in them.

One is actually, the new style that we saw on the last page.

Actually we saw both styles-- excuse me.

We saw the new style that with the integrated CSU/DSU and then there was an old style one,

I've got one of each sitting there.

That's 0, 0/0 and 0/1.

But notice first off something very different from a switch,

all of them on a router are shut down by defaults.

That's the norm.

A switch, it works out of the box.

A router will not work at all out of the box.

You have to configure it to get it running

because the Cisco doesn't know what you want to do with this thing.

So the second verification command and this is what I was going to show you.

Show version tells me what I'm working on.

I look and I go, "Okay, I've got a Cisco 2600 series software.

I see the version of software that this is running, how long it's been running for.

You hit space key and then right down here--

that's what where I can see the exact model number, as well as, you know,

kind of a quick summary of what interfaces are inside of there.

Now, I didn't tell you this but I also do have voice interfaces.

Not part of this series at all but I actually use this as voice over IP routers

with something called FXS, Foreign Exchange Station interfaces in there as well.

I can see how much FLASH 32 megabytes of flash.

And this just-- you can kind of piece this together.

That's 128 megabytes or so you add those numbers up.

128 megabytes of memory.

For a router, that's decent.

I mean, it's not an offer that you're thinking

like Window 7 needs five Gigs or Windows 8 or whatever.

You know, it needs insane amount of the memory.

Well, routers don't, you know, they don't run Microsoft Office.

They just route packets.

So I'm kind of orienting.

I feel good now.

Okay, let's go in and start the configuration.

So first off Hostname, I'm going to type hostname.

We'll just call the CBT Router just like we have CBT Switch.

Immediately the Hostname changes.

Console password, telnet password, enable password, let's just fly through those.

Line console 0, password Cisco unless require some logins on there or login.

Let's do exact time out of 0 space 0 so I don't get kicked off if I'm idle.

Logging synchronous and I'm so glad the tab key works 'cause I would probably fumble

through the spelling of synchronous.

And then, let's go under the VTY ports.

That's our telnet ports.

Now, look at that, insanity.

This guy supports 181 simultaneous sessions at a time.

Well, good 26:3.

I don't expect 181 administrators to all beyond my router at once, would you?

Good. So what I would do is I would just say, "Well, let's just configure the number

that I would expect, maybe just 0 through 4.

I only expect-- I wouldn't even expect 5 people to be on this router at the same but, "Hey,

let's just do it 'cause that was the norm before.

So I'm going to type in password Cisco and you-- oops-- Cisco.

And you remember, let's doa show, run and let's you begin with a line.

And by the way, you will feel a lot slower on the router.

It takes a little longer for it to execute some of these commands.

So you can see that I've got VTY 0 space 4 log in, you remember was the default.

I don't have to type in login under here whereas I did under the console port

because logins are always required or should always be required for telnet sessions.

So I get out of there and now we want to do our enable secret, right?

Enable secret Cisco protects our privileged mode.

Now, we jump over to the right hand side with the IP address.

And we start getting into some of the default gate, I mean, now,

first off, I change this from the switch.

It used to say management IP address.

Now, we just have IP address.

This is where you got-- you've got to get into your planning side

of things like what is this router?

What is this device do?

What does it connect to?

So, you know, if I connect-- maybe that I'm using is for a home network.

I'm kind of, you know, and I would encourage you to do this, you know,

replace your little Netgear device that you use at home

or whatever you use with a real Cisco router.

There's no better way to start learning just actually make it real and make it consequential

like if I can't figure this out, my internet connection

at my house doesn't work, my spouse will be mad.

So you can add, you know, a little pressure to yourself to get this thing going and--

so there's a lot, lot to be gained by that.

So let's say we're configuring it for our home.

So maybe we want this FAST ethernet 0/0 to be 192.168.1.1 with a classy subnet mask, right.

Maybe that's what we want, maybe, you know, maybe its corporate network,

maybe we've got internet connection, all that kind of stuff.

So, in this nugget, I'm not going to dive deep into all the possibilities.

That's going to be what the rest of the series is about.

But for now, let's just give it one IP address.

So I'm going to go, let's do a show IP interface brief.

See the interfaces.

And let's just say that I plugged no click FAST ethernet 0/0 into my home network.

That's would plug into the switch.

So I would go into interface, FAST ethernet 0/0 and I throw that in there, IP address 192.168.

Now, I've assigned an IP address but it's still shut down so I need

to do a no shutdown and power that back up.

Now as of right now, it's a base configuration so it's not actually plugged into anything

so what it's going to tell me is it's going to say, "Hey, I'm up like physically, I'm okay.

I'm a working port but you know what, there's no electrical signal.

There's nothing at layer 2.

No communication."

So 'cause I don't have a cable attached.

Now we come to this big question.

A Default gateway.

Most of the time, a router will not have a default gateway because it's a router.

It is a default gateway, you know.

People right here are saying, "Hey, I go to you to get elsewhere.

You are my default gateway."

So the reason I'd left this on there from the switch side is you can't--

you can make the router have a default gateway by going it back out to-- oops, Caps Lock--

to global config and doing IP default gateway just like you did on the switch.

And then you type in the IP address of where it goes to get to you,

but that's not normally what we do for a router.

It's a router.

It's not-- it doesn't need a default gateway.

Instead, what you'll start doing is static routes.

Now, I'm going to throw one at you.

Not really expound too much on it but let's just imagine that we had an internet connection here

and this is FAST ethernet 0/1, you know, it's our cable modem or DSL

or whatever we're bringing in right here.

If we have that kind of situation, I can say "I want to set a default route.

It's not a default gateway because it's router-- A default route.

It's actually a type of static route

that just send everything you don't know about to the internet.

It's almost like default gateway.

So the way I could do that is first off, I would go into interface FAST ethernet 0/1,

maybe that's connected to my internet service router.

Now, maybe I am using this at home.

Maybe I have, you know, whatever cable modem provider.

They don't even give me a static IP address.

That's okay.

Cisco allows you to type an IP address and DHCP

to where I can have this router get an IP address on FAST ethernet 0/1

from a DHCP server, from my internet service router.

And trust me, I'm going to put a whole big picture together of this

when we get deeper in the series.

But then I would do a no shutdown, you know, bring that interface up,

it would grab its IP address, whatever it is, and then I would do an IP route.

Now-- remember, this is-- I'm not really getting into static routing here.

I'm just giving you the command just so you can see it,

kind of cycle it through your mind but we will cover it fully.

So we're telling the router, "I want to route."

And router goes, "Yes, where you going?

What's your destination that you're trying reach?

And we could, you know, we could type in like, you know, I want to reach everything starting

with the number 10 or I want to reach some other 192.168.5 network.

You know, what destination are you trying to go to?

Well, if I want to say, "You know what, I want to route anything,

essentially if there's something out there.

I want to send at this direction.

It's called the default route.

That means all zeros.

And it says, "Okay, what's the subnet mask of that?

Now, if we were doing a real static route, we would, you know, well, 255--

well, I'm doing a default route which says, send everything out this direction.

So it's actually all zeros for the IP address, all zero for the subnet mask and I'll say,

"In this case and again, more to unpack letter, send it out FAST ethernet 0/1.

So what that tells the router is you have an IP address here and if somebody calls you,

if somebody tries to send information to that's going to the internet, and, you know,

you won't know exactly where to send it but just go in and throw it out that interface,

FAST ethernet 0/1 and send it off to the service provider, okay, at more, more,--

I 'm done saying, more on that later, right.

So last couple things.

Shut down, we've already seen that, no shutdown and shut down.

Banner. We do the-- same command Banner MOTD, Message of the day,

and we would, you know, save caret.

And I'm going to change my character each when we go through

and I don't know why I do this asterisk thing, I just want to do.

And we'll say asterisk, asterisk and this is a secure Cisco router.

And then we will end it with caret.

And so I now got my logon Banner in there.

Last thing is saving my configuration.

Copy, run, start.

Now, I know when your first saw, wow, we're going to squeeze in what is routing

and the base configuration of the router, you're going to like,

"That's going to be a long explanation."

Well, not really because everything that we've see here-- almost everything we've seen before,

it's the same configuration of the switch just now applied to a router.

And honestly the configuration is almost secondary to me, you know, I look at that at

and I'm like "Okay, you guys knew that part already and we will get far more oriented

with static routes and everything else that we started throwing there.

Later the big thing that I wanted you to grab and I want you to walk away with,

from this nugget, s what is routing.

At that-- like that first bullet is everything to me because that's going to be what we grow in

and as we go through the rest of the series, you know, if that piece doesn't quite click,

all the other stuff will become like "Yeah

but it just won't ever feel good and warm and fuzzy to you.

So if you're not 100 percent of what is router, I encourage you go back.

Just run through the first ten or so minutes of the nugget and review that.

But we did see that.

We saw the look and feel of Cisco routers, they look across the board.

If you're really curious, hit the Cisco website and just click on the router product lines

and you'll be able to see all kinds of different looks, sizes, feels, prices,

modules that you can put inside of them that do different things.

And then finally, we'll look at the basic router configuration.

I hope this has been informative for you and I'd like to thank you for viewing.