WEBVTT

1
00:00.000 --> 00:00.757 align:middle line:84%


2
00:00.757 --> 00:02.590 align:middle line:90%
In this video, you and
I get the opportunity

3
00:02.590 --> 00:04.757 align:middle line:90%
to take a look at several
options regarding logging,

4
00:04.757 --> 00:06.970 align:middle line:90%
how we can verify what
they are, and also

5
00:06.970 --> 00:09.460 align:middle line:90%
become aware of the
additional options or tweaks

6
00:09.460 --> 00:12.460 align:middle line:90%
that we can inject if we
need to get more information

7
00:12.460 --> 00:13.972 align:middle line:84%
from those log messages.

8
00:13.972 --> 00:16.180 align:middle line:90%
And for this discussion,
I'd like to demonstrate this

9
00:16.180 --> 00:18.028 align:middle line:84%
on router, any router will do.

10
00:18.028 --> 00:18.820 align:middle line:84%
We'll use router 1.

11
00:18.820 --> 00:20.380 align:middle line:84%
We'll do a show logging.

12
00:20.380 --> 00:21.383 align:middle line:84%
That's a great start.

13
00:21.383 --> 00:23.800 align:middle line:90%
And show logging is going to
show us a lot of good output,

14
00:23.800 --> 00:25.847 align:middle line:84%
including what the defaults are.

15
00:25.847 --> 00:27.430 align:middle line:90%
And what this is
telling us is that we

16
00:27.430 --> 00:29.740 align:middle line:90%
are logging to the console,
which is we can think

17
00:29.740 --> 00:32.530 align:middle line:90%
of that like line
console 0, and we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

17
00:29.740 --> 00:32.530 align:middle line:90%
of that like line
console 0, and we

18
00:32.530 --> 00:34.600 align:middle line:84%
are logging at level debugging.

19
00:34.600 --> 00:36.670 align:middle line:90%
So there are 8 levels
regarding log messages,

20
00:36.670 --> 00:37.888 align:middle line:84%
and they go from--

21
00:37.888 --> 00:39.430 align:middle line:90%
I'm going to start
with the most busy

22
00:39.430 --> 00:42.030 align:middle line:90%
and the most detailed and
most verbose information, 7,

23
00:42.030 --> 00:46.070 align:middle line:90%
and then it goes down
6, 5, 4, 3, 2, 1 0.

24
00:46.070 --> 00:48.370 align:middle line:90%
So 7 would give us
everything at that level

25
00:48.370 --> 00:51.430 align:middle line:90%
and numerically
lower, though if we

26
00:51.430 --> 00:53.890 align:middle line:90%
said we want to do it at
level 7, which is debugging--

27
00:53.890 --> 00:55.990 align:middle line:90%
we'll take a closer
look at those numbers

28
00:55.990 --> 00:57.190 align:middle line:84%
and labels in a moment.

29
00:57.190 --> 00:58.810 align:middle line:90%
But if we said
debugging, that means

30
00:58.810 --> 01:01.210 align:middle line:90%
anything that happens at
a level 6, 5, 4, 3, 2--
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
00:58.810 --> 01:01.210 align:middle line:90%
anything that happens at
a level 6, 5, 4, 3, 2--

31
01:01.210 --> 01:03.940 align:middle line:90%
anything lower numerically
is also included in that.

32
01:03.940 --> 01:05.870 align:middle line:90%
Think of it like an
umbrella that says,

33
01:05.870 --> 01:08.245 align:middle line:90%
hey, I'm catching everything
at this level and everything

34
01:08.245 --> 01:09.950 align:middle line:84%
numerically lower as well.

35
01:09.950 --> 01:12.880 align:middle line:90%
So by default, console
logging at level 7 is on.

36
01:12.880 --> 01:15.920 align:middle line:90%
Also monitor logging,
so what does that mean?

37
01:15.920 --> 01:19.090 align:middle line:90%
Well, if somebody's ssh-ed
or on a vty line connecting

38
01:19.090 --> 01:21.130 align:middle line:90%
to this box, that's what
that's referring to.

39
01:21.130 --> 01:26.620 align:middle line:90%
So we kind of think of monitor
logging like line vty 0

40
01:26.620 --> 01:30.250 align:middle line:90%
through whatever the high
range is for your vty lines.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
01:26.620 --> 01:30.250 align:middle line:90%
through whatever the high
range is for your vty lines.

41
01:30.250 --> 01:32.800 align:middle line:90%
And so this is willing to
send debugging of level

42
01:32.800 --> 01:35.380 align:middle line:90%
7 messages and
below to vty lines.

43
01:35.380 --> 01:36.597 align:middle line:84%
Now, the trick is--

44
01:36.597 --> 01:38.680 align:middle line:90%
this happens to a lot of
people when they're first

45
01:38.680 --> 01:40.030 align:middle line:84%
getting involved in Cisco.

46
01:40.030 --> 01:44.020 align:middle line:90%
They'll remotely connect
to a device on a vty line,

47
01:44.020 --> 01:45.520 align:middle line:90%
and they won't see
the log messages,

48
01:45.520 --> 01:47.770 align:middle line:90%
and they'll say, why am I
not seeing the log messages?

49
01:47.770 --> 01:50.410 align:middle line:90%
The answer is when we
connect on a vty line,

50
01:50.410 --> 01:51.910 align:middle line:90%
this has to be
willing to send us

51
01:51.910 --> 01:54.290 align:middle line:90%
the messages at, in
this case, level 7

52
01:54.290 --> 01:56.200 align:middle line:90%
and below, and
the customer needs

53
01:56.200 --> 02:01.300 align:middle line:90%
to type in terminal
monitor, which means
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
01:56.200 --> 02:01.300 align:middle line:90%
to type in terminal
monitor, which means

54
02:01.300 --> 02:02.955 align:middle line:84%
I would like to see those.

55
02:02.955 --> 02:04.330 align:middle line:90%
Though I can't
tell you how times

56
02:04.330 --> 02:06.080 align:middle line:90%
I've been remotely
connected and I'm like,

57
02:06.080 --> 02:08.919 align:middle line:84%
where's my log message?

58
02:08.919 --> 02:10.509 align:middle line:84%
Well, the user needs to--

59
02:10.509 --> 02:12.760 align:middle line:90%
either through automation,
through their app,

60
02:12.760 --> 02:15.390 align:middle line:90%
or manually-- type
terminal monitor,

61
02:15.390 --> 02:17.830 align:middle line:90%
so they can see those messages
coming to the vty lines.

62
02:17.830 --> 02:20.350 align:middle line:90%
Then we have the buffer
logging, and buffer logging

63
02:20.350 --> 02:21.950 align:middle line:90%
is everything down
here, where it's

64
02:21.950 --> 02:24.670 align:middle line:90%
stored in memory on this
device, and you can also

65
02:24.670 --> 02:25.870 align:middle line:84%
set the size of that.

66
02:25.870 --> 02:29.590 align:middle line:90%
So our options include we
could enable or disable these.

67
02:29.590 --> 02:31.390 align:middle line:90%
We could specify
certain levels, like we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
02:29.590 --> 02:31.390 align:middle line:90%
We could specify
certain levels, like we

68
02:31.390 --> 02:35.732 align:middle line:90%
could say for buffer logging, we
can set the level to a level 3,

69
02:35.732 --> 02:37.690 align:middle line:90%
and if we did that, it
would include everything

70
02:37.690 --> 02:39.130 align:middle line:84%
at 3 and below.

71
02:39.130 --> 02:42.130 align:middle line:90%
We wouldn't get the little
4, 5, 6, or 7 leave messages.

72
02:42.130 --> 02:43.840 align:middle line:90%
We could also
include a destination

73
02:43.840 --> 02:47.080 align:middle line:90%
of a syslog server, which is
very, very good thing to do.

74
02:47.080 --> 02:50.350 align:middle line:90%
We can specify a syslog server
and what level of messages

75
02:50.350 --> 02:53.380 align:middle line:90%
via the trap command we want
to send to that syslog server,

76
02:53.380 --> 02:54.880 align:middle line:90%
and that way, you
can store messages

77
02:54.880 --> 02:58.067 align:middle line:90%
from multiple devices in one
central repository as well.

78
02:58.067 --> 03:00.650 align:middle line:90%
The other option I would like
to chat with you about regarding
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

78
02:58.067 --> 03:00.650 align:middle line:90%
The other option I would like
to chat with you about regarding

79
03:00.650 --> 03:02.260 align:middle line:84%
syslog messages is this.

80
03:02.260 --> 03:06.963 align:middle line:90%
Let's go ahead and type in
config t, then type in exit.

81
03:06.963 --> 03:09.130 align:middle line:90%
And what it did, it just
generated this log message.

82
03:09.130 --> 03:13.180 align:middle line:90%
Now, this log message
is totally configurable.

83
03:13.180 --> 03:16.400 align:middle line:90%
In the labs, what I normally
do is I tweak it way down.

84
03:16.400 --> 03:19.540 align:middle line:90%
It's not including timestamps,
date stamps, milliseconds,

85
03:19.540 --> 03:21.510 align:middle line:90%
a lot of details
that could be there.

86
03:21.510 --> 03:22.900 align:middle line:90%
So if we're doing
troubleshooting

87
03:22.900 --> 03:25.900 align:middle line:90%
and we want to see sequence
numbers and the milliseconds

88
03:25.900 --> 03:28.240 align:middle line:90%
and the year and
the time zone, we

89
03:28.240 --> 03:30.310 align:middle line:90%
can include all that
regarding log messages
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

89
03:28.240 --> 03:30.310 align:middle line:90%
can include all that
regarding log messages

90
03:30.310 --> 03:32.170 align:middle line:90%
and debug messages,
and we can use that

91
03:32.170 --> 03:34.240 align:middle line:90%
with these service
timestamps command, which

92
03:34.240 --> 03:36.715 align:middle line:90%
we'll have an opportunity do
in the next video and lab.

93
03:36.715 --> 03:38.590 align:middle line:90%
So those are some of
the defaults and options

94
03:38.590 --> 03:40.400 align:middle line:90%
that we have regarding where
we're going to, first of all,

95
03:40.400 --> 03:42.670 align:middle line:90%
send logs, at what
level, and what detail

96
03:42.670 --> 03:44.240 align:middle line:84%
do we want to include in them.

97
03:44.240 --> 03:46.977 align:middle line:90%
So with that in mind, in
the next video and lab,

98
03:46.977 --> 03:48.310 align:middle line:84%
here's what you and I get to do.

99
03:48.310 --> 03:49.893 align:middle line:90%
What we're going to
do is we are going

100
03:49.893 --> 03:53.142 align:middle line:90%
to configure custom logging
levels for certain destinations

101
03:53.142 --> 03:54.850 align:middle line:90%
and then verify that
they're working out.

102
03:54.850 --> 03:57.308 align:middle line:90%
I also want to walk you through
with the service timestamps

103
03:57.308 --> 03:59.500 align:middle line:90%
command, tweaking
the log messages, so

104
03:59.500 --> 04:02.290 align:middle line:90%
that when you need that detailed
information, you can get it.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

104
03:59.500 --> 04:02.290 align:middle line:90%
that when you need that detailed
information, you can get it.

105
04:02.290 --> 04:03.820 align:middle line:90%
We'll do all that
in the next video.

106
04:03.820 --> 04:06.010 align:middle line:90%
Meanwhile, I hope this has
been informative for you,

107
04:06.010 --> 04:09.270 align:middle line:90%
and I'd like to thank
you for viewing.