- [Narrator] We're going to go ahead and continue on
and configure our interfaces and our passwords.
But before you can do that,
you have to understand your prompts.
So, first plug-in, I'm going to be in user mode.
I type the command enable, and end up in privileged mode.
To configure the device, you type "configure terminal",
with our router switch.
Now, I usually just type "config t".
I've been doing that for 20 years, config t.
This takes me to something called global config.
Now, I can type end or control z and get back
to privileged mode, but from here I can type anything
I want, like interface e zero,
which would take me to the config if prompt.
Tell me I'm at an interface.
Or configure an interface.
I can also create logical interfaces,
and I would say config sub if,
and we'll see those in later configs.
Now, if I was configuring a line, like my console,
my prompt would say config line.
And if I was configuring a routing protocol,
such as RIP or OSPF, it would say config router.
To configure the name of a hoster switch, very simple.
From global config I say hosting, and the name I want.
The minute you press enter it takes effect,
because I'm changing the running config,
the act of configuration file when I'm in global config.
To configure my passwords on my console,
on auxiliary lines.
The console allows me to get out of band access in there.
It doesn't matter if the network is up or down,
I'm not going through the network,
so we're calling it out of band.
I choose the line that I want and notice my prompt changes
to config line.
I set my password and enable the login process.
We'll go through a couple different processes on logging in,
but this is saying the password is in the running config
underneath the console configuration in the active
configuration file running config.
Three steps.
Choose your line, set your password,
enable your login process.
I'll do the same thing for the auxiliary port.
And the auxiliary port is the same thing as a
console port, but allows me to put in modem commands
so I can dial up a modem and get a console connection
out of them if I need to go somewhere remote.
So I don't need to fly out there and console in, right?
Again, three steps of setting it.
Choose your line, set your password, and enable
the login process.
We'll enable this login process in a minute in the CLI.
The virtual terminal password, so I can get in through
Telnet or Secure Shell.
I'm going to choose my lines.
Line vty zero four on my default lines.
There might be many more.
The way to find out is do zero space question mark.
Instead of the four, do line vty zero space question mark,
and it will show you your last line number.
I recommend typing in all line numbers.
Choose your lines, set your password,
enable the login process.
Now, I don't recommend this, but you could
type in, "no login".
And that would mean you could Telnet into a Cisco router
or a switch and not be prompted for a password.
Please don't do this in production.
But at your home network, absolutely, it makes it easier.
So, in a lab environment, it will make things easier,
because you don't always have to be
typing in your passwords.
Now, those were just giving us our user mode access.
To get into privileged mode, we want to set
some passwords, and there's two of them.
There's the enable password, which is not encrypted.
So, in production, just set the enable secret,
which is encrypted, and supersedes the enabled password.
So it's just an enabled secret global net in this example.
To configure an IP address on an interface,
pretty straightforward.
Choose the interface.
You have to know what your interfaces are.
Interface s zero zero zero, or I spelled out the
whole thing here.
IP address, and I have to put a different subnet
on each interface.
So, now I have to type out the whole mask.
For example, I couldn't do a slash 24.
It won't allow me to.
I have to type out the full mask.
Once I put different subnets on each interface,
I can then go and enable the interfaces.
The way to enable an interface on a router
is the no shutdown command.
So I choose my interface, and then do the no shutdown.
Understand that all interfaces on a router
are shut down by default.
All interfaces on a switch are enabled by default.
So, to disable a port that's enabled,
I will do the shutdown command.
To enable it, no shutdown.
And lastly, we want to verify our interfaces
with my favorite command.
We're going to use this in our labs over and over again,
because it's my favorite command.
Notice I'm at what prompt?
The user mode.
I don't even have to be in privilege mode.
Show IP interface brief.
It shows me my interface as the post test found.
Their IP addresses have set.
The method manually means they were set.
Ecstatically I went in there and typed them in.
Or this may say something like DHCP.
Now, this is my layer one and two status, so
I'm going to say this is layer one and this is layer two.
So it's telling me my layer one and two status.
I don't know if my layer three status is working.
That's something that I would have to use Ping for
and then verify my IP addresses on each end.
So, in addition to the show IP interface brief commands,
we're also going to use show IP interface
and show protocols in our labs.