- [Instructor] All right, let's run back out
the corp router here and let's configure a couple things.
The network time protocol and syslog.
Network time protocol is pretty simple.
UVP port 123.
Very easy to configure, very easy to use.
Cisco routers and switches are notoriously bad
at keeping time right?
So we want to connect up to an atomic clock
and the way that we do this, ntp server
and there are lots of options here
if you were to press, you know, the help key.
Question mark.
And we're also going to run the latest version.
You can press enter there but it's option
version two or three or four
and typically you're always going to run version four.
Now I'm not an ntp server.
I'm connecting to this.
This is connecting to an atomic clock,
so I want to get the correct time.
A Cicso device downstream for me
can put in my IP address and use me as their server.
Typically I will configure all Cisco devices downstream
to the same server.
However you can have them connect up
as I just mentioned to their pair.
Now to verify ntp,
show ntp and you're going to see status and associations.
So once you connect up to your server,
then you're going to go ahead and see
how far you are from that server,
if you're more than one pair away for example,
and the status.
Very important to check that every once in a while.
Now, let's get into something a little more in depth
and that's in the syslog
and we're going to be doing logging.
So it's not syslog isn't the command.
There's no syslog command.
It's logging and I'll give you logging host.
Lots of commands under logging
because I can logging console, right?
Logging buffers and so on.
Anyways, logging syslog, so I can just type it in
or logging host, same command.
So why do the extra typing?
Okay, I now have my syslog server
and figure I'm sending local seven information out.
That's everything up to debugging to this syslog server.
Now I can change that by doing logging trap.
Check this out guys.
So I can see the eight different severities
from local zero to local seven level.
Again, local seven is your default.
So I want to probably change that maybe.
Maybe you do maybe you don't.
But I'm going to say like informational,
hit my tab key, press enter.
Right, and now I'm only sending zero through six.
One last thing I want to show you
is if you're going to send syslog messages,
into bugging and see what's going on
in the middle of the night,
maybe that's why you're setting this,
it's important to set your time.
So service, and then time stamp.
Notice I'm using my tab key.
And then if you look there's two different ones.
Log is just basic traps, right?
And then I'm going to do date time.
Now you don't type in the date time.
These are the actual commands, right?
Date, time, and then I can do
msec so even down to the millisecond.
So give me the date, time, and millisecond for each trap.
And the other thing I'm going to do,
I'm going to up arrow here and then come back over here.
Debug, now you can do the same thing.
This is very typical right here what I'm doing, msec.
And now my syslog traps, any of them that are set,
are sent with the date time all the way
down to the millisecond.
It's very important if you are going to use this log
to set your ntp server.
Before or after doesn't matter.
Make sure your ntp server's working.
And then also remember that local seven
is your syslog trap level by default.
You may want to change that if you're getting too much,
but this is extremely helpful
and it is a huge CCNET objective,
so make sure and memorize your different types of alerts
and also be able to configure syslog.