WEBVTT

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


2
00:00.383 --> 00:03.050 align:middle line:90%
In this video lab, you and I are
going to do three basic things.

3
00:03.050 --> 00:06.220 align:middle line:90%
Number one, I'd like to walk
you through tweaking the log

4
00:06.220 --> 00:06.800 align:middle line:84%
messages.

5
00:06.800 --> 00:08.868 align:middle line:90%
So it's not just
a generic message

6
00:08.868 --> 00:09.910 align:middle line:84%
with limited information.

7
00:09.910 --> 00:13.040 align:middle line:90%
We can increase it, and I want
to walk through how to do that.

8
00:13.040 --> 00:16.329 align:middle line:90%
Number two, I'd like to change
the logging levels based

9
00:16.329 --> 00:18.280 align:middle line:90%
on the destination,
like to the console,

10
00:18.280 --> 00:20.620 align:middle line:84%
or to monitor, or to the buffer.

11
00:20.620 --> 00:21.340 align:middle line:84%
We can set those.

12
00:21.340 --> 00:22.960 align:middle line:90%
I'd like to walk
through how to do that.

13
00:22.960 --> 00:24.960 align:middle line:90%
And while we're at it,
let's add the destination

14
00:24.960 --> 00:28.940 align:middle line:90%
of a syslog server as one of our
destinations for log messages.

15
00:28.940 --> 00:31.060 align:middle line:90%
So we're going to do all
this work starting on R1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

15
00:28.940 --> 00:31.060 align:middle line:90%
So we're going to do all
this work starting on R1.

16
00:31.060 --> 00:32.800 align:middle line:90%
If you're logged on to
the CBT Nuggets website,

17
00:32.800 --> 00:34.425 align:middle line:90%
click on that link
for the virtual lab.

18
00:34.425 --> 00:36.530 align:middle line:84%
And let's do this together.

19
00:36.530 --> 00:37.650 align:middle line:84%
So here we are on R1.

20
00:37.650 --> 00:39.430 align:middle line:90%
And before we start
changing everything,

21
00:39.430 --> 00:41.480 align:middle line:90%
let's go ahead and actually
see what is in place.

22
00:41.480 --> 00:43.930 align:middle line:90%
We'll do a show logging, which
is a great place to start.

23
00:43.930 --> 00:46.180 align:middle line:90%
And here's what the show
logging command is revealing.

24
00:46.180 --> 00:49.240 align:middle line:90%
We are currently logging
to line console 0.

25
00:49.240 --> 00:52.000 align:middle line:90%
We're willing to log at
level 7, or debugging,

26
00:52.000 --> 00:53.650 align:middle line:90%
which from a
logging perspective,

27
00:53.650 --> 00:54.820 align:middle line:84%
debugging is level 7.

28
00:54.820 --> 00:58.150 align:middle line:84%
There's 6, 5, 4, 3, 2, 1, and 0.

29
00:58.150 --> 00:59.380 align:middle line:84%
So 8 levels.

30
00:59.380 --> 01:02.483 align:middle line:90%
So think of it like an
umbrella, that wherever
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
00:59.380 --> 01:02.483 align:middle line:90%
So think of it like an
umbrella, that wherever

31
01:02.483 --> 01:04.650 align:middle line:90%
you put the umbrella, if
it's all the way here at 7,

32
01:04.650 --> 01:07.450 align:middle line:90%
it captures everything
down below it numerically.

33
01:07.450 --> 01:09.790 align:middle line:90%
If somebody has an umbrella,
it just captures at 3.

34
01:09.790 --> 01:12.160 align:middle line:90%
It would capture-- it would
cover 3 and everything

35
01:12.160 --> 01:13.100 align:middle line:84%
below it.

36
01:13.100 --> 01:14.865 align:middle line:90%
So that's the--
debugging is level 7.

37
01:14.865 --> 01:16.240 align:middle line:90%
We'll take a look
at those levels

38
01:16.240 --> 01:18.220 align:middle line:84%
here closer in just a moment.

39
01:18.220 --> 01:20.140 align:middle line:90%
We're willing to
log to the monitor.

40
01:20.140 --> 01:22.600 align:middle line:90%
That's VTY lines who
are connected also

41
01:22.600 --> 01:25.600 align:middle line:90%
at the same level and below,
and also to the buffer, which

42
01:25.600 --> 01:27.230 align:middle line:84%
is the memory on the system.

43
01:27.230 --> 01:27.790 align:middle line:84%
Fantastic.

44
01:27.790 --> 01:30.805 align:middle line:90%
So if we wanted to change that
or disable those, we could.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
01:27.790 --> 01:30.805 align:middle line:90%
So if we wanted to change that
or disable those, we could.

45
01:30.805 --> 01:33.180 align:middle line:90%
Let's go ahead and take a look
at exactly how to do that.

46
01:33.180 --> 01:34.965 align:middle line:84%
Oh, oh!

47
01:34.965 --> 01:35.590 align:middle line:84%
I'm so excited.

48
01:35.590 --> 01:36.680 align:middle line:84%
I got ahead of myself.

49
01:36.680 --> 01:39.070 align:middle line:90%
Before we tweak these,
let me share with you

50
01:39.070 --> 01:42.725 align:middle line:90%
how we can modify the actual
log messages themselves.

51
01:42.725 --> 01:45.100 align:middle line:90%
And let's do a demonstration
of what it looks like first.

52
01:45.100 --> 01:49.066 align:middle line:90%
So do show-- let's go to
Configuration mode, config t,

53
01:49.066 --> 01:50.675 align:middle line:84%
and end.

54
01:50.675 --> 01:51.800 align:middle line:84%
And here's the log message.

55
01:51.800 --> 01:53.170 align:middle line:84%
Boom!

56
01:53.170 --> 01:54.130 align:middle line:84%
Very minor.

57
01:54.130 --> 01:55.180 align:middle line:84%
Not a lot of detail here.

58
01:55.180 --> 01:57.280 align:middle line:90%
And that's because for the lab,
I usually just strip it away.

59
01:57.280 --> 01:59.190 align:middle line:90%
And I don't put all
the juicy details,

60
01:59.190 --> 02:01.350 align:middle line:90%
like the date, and
time, and year,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
01:59.190 --> 02:01.350 align:middle line:90%
like the date, and
time, and year,

61
02:01.350 --> 02:03.070 align:middle line:90%
and the millisecond
sequence number,

62
02:03.070 --> 02:05.570 align:middle line:90%
because I just wanted to not
clutter up the screen too much.

63
02:05.570 --> 02:07.870 align:middle line:90%
But for troubleshooting,
holy cow, we need it.

64
02:07.870 --> 02:10.419 align:middle line:90%
So let me walk you through
the service timestamp

65
02:10.419 --> 02:12.700 align:middle line:90%
command for our logged
messages and debugs

66
02:12.700 --> 02:15.160 align:middle line:90%
where we can customize
what we want to see.

67
02:15.160 --> 02:17.020 align:middle line:90%
So we'll go into
configuration mode.

68
02:17.020 --> 02:19.600 align:middle line:90%
And the command is
service space timestamps.

69
02:19.600 --> 02:22.060 align:middle line:90%
And then we can adjust
these for log messages,

70
02:22.060 --> 02:23.515 align:middle line:84%
and also for debug messages.

71
02:23.515 --> 02:24.640 align:middle line:84%
And you can do it for both.

72
02:24.640 --> 02:26.598 align:middle line:90%
You can use the same for
both if you wanted to.

73
02:26.598 --> 02:28.090 align:middle line:84%
Let's start off with log.

74
02:28.090 --> 02:30.220 align:middle line:90%
So we're going to throw
the kitchen sink here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
02:28.090 --> 02:30.220 align:middle line:90%
So we're going to throw
the kitchen sink here.

75
02:30.220 --> 02:32.290 align:middle line:84%
We don't-- uptime, not great.

76
02:32.290 --> 02:35.440 align:middle line:90%
Uptime shows timers,
like how long it's been

77
02:35.440 --> 02:37.030 align:middle line:84%
since the router's rebooted.

78
02:37.030 --> 02:39.730 align:middle line:90%
We want dates, and times,
and accurate information.

79
02:39.730 --> 02:42.807 align:middle line:90%
So for production environments,
we would include datetime.

80
02:42.807 --> 02:44.890 align:middle line:90%
And then I'm going to throw
the kitchen sink here.

81
02:44.890 --> 02:46.803 align:middle line:90%
Let's go ahead and
use the localtime.

82
02:46.803 --> 02:48.220 align:middle line:90%
And this is also
something-- let's

83
02:48.220 --> 02:51.100 align:middle line:90%
say you're using NTP,
which is delivered in UTC.

84
02:51.100 --> 02:53.240 align:middle line:90%
And then there's an offset
for the local time zone.

85
02:53.240 --> 02:54.850 align:middle line:90%
So if you've set up for the
local time zone correctly

86
02:54.850 --> 02:56.930 align:middle line:90%
and you're using NTP,
that's all very important

87
02:56.930 --> 02:58.430 align:middle line:90%
if you want to see
the correct time.

88
02:58.430 --> 03:00.940 align:middle line:90%
So I'm doing log
datetime localtime.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

88
02:58.430 --> 03:00.940 align:middle line:90%
So I'm doing log
datetime localtime.

89
03:00.940 --> 03:03.880 align:middle line:84%
Let's include show-timezone.

90
03:03.880 --> 03:05.530 align:middle line:84%
Let's include year.

91
03:05.530 --> 03:07.180 align:middle line:84%
Let's include milliseconds.

92
03:07.180 --> 03:09.360 align:middle line:90%
Now, if we get a whole
bunch in rapid succession,

93
03:09.360 --> 03:12.100 align:middle line:90%
we can say, oh, that one
came in a few milliseconds

94
03:12.100 --> 03:13.190 align:middle line:84%
before the other message.

95
03:13.190 --> 03:14.982 align:middle line:90%
And let's see if there's
any other options.

96
03:14.982 --> 03:15.700 align:middle line:84%
No.

97
03:15.700 --> 03:16.510 align:middle line:84%
No, there isn't.

98
03:16.510 --> 03:21.750 align:middle line:90%
However, I believe there's a
service if I can type service.

99
03:21.750 --> 03:24.880 align:middle line:90%
There is an option
for sequence numbers,

100
03:24.880 --> 03:26.880 align:middle line:84%
which I want to add as well.

101
03:26.880 --> 03:28.290 align:middle line:90%
So sequence-numbers
is just going

102
03:28.290 --> 03:29.450 align:middle line:84%
to add sequence numbers as well.

103
03:29.450 --> 03:30.585 align:middle line:90%
So if you weren't
looking at milliseconds,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
03:29.450 --> 03:30.585 align:middle line:90%
So if you weren't
looking at milliseconds,

104
03:30.585 --> 03:33.030 align:middle line:90%
the sequence numbers
would help you identify

105
03:33.030 --> 03:34.280 align:middle line:84%
which one came in first.

106
03:34.280 --> 03:36.310 align:middle line:90%
So I'm going to throw
it on there as well.

107
03:36.310 --> 03:39.195 align:middle line:90%
And now that we've done
that, if we type in end,

108
03:39.195 --> 03:40.320 align:middle line:84%
check out this log message.

109
03:40.320 --> 03:41.460 align:middle line:84%
This is great stuff.

110
03:41.460 --> 03:42.930 align:middle line:84%
I mean, fantastic.

111
03:42.930 --> 03:45.450 align:middle line:90%
So it's showing us a
sequence number here.

112
03:45.450 --> 03:46.620 align:middle line:84%
That is the date.

113
03:46.620 --> 03:47.820 align:middle line:84%
That is the time.

114
03:47.820 --> 03:52.140 align:middle line:90%
That is a message that I'm
going to remove off my screen.

115
03:52.140 --> 03:54.372 align:middle line:90%
There is the lack of the
time zone that I've set.

116
03:54.372 --> 03:56.580 align:middle line:90%
I just took the default
settings to set the time zone

117
03:56.580 --> 03:57.630 align:middle line:84%
on this device.

118
03:57.630 --> 04:00.598 align:middle line:90%
And then this is the facility,
where it's coming from.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

118
03:57.630 --> 04:00.598 align:middle line:90%
And then this is the facility,
where it's coming from.

119
04:00.598 --> 04:01.890 align:middle line:84%
What's generating this message?

120
04:01.890 --> 04:03.420 align:middle line:84%
Is it an OSPF process?

121
04:03.420 --> 04:04.680 align:middle line:84%
Is it that SNMP?

122
04:04.680 --> 04:07.560 align:middle line:90%
Is it system because somebody
just exited configuration mode?

123
04:07.560 --> 04:08.280 align:middle line:84%
Yes.

124
04:08.280 --> 04:10.090 align:middle line:90%
And then this is
the severity level,

125
04:10.090 --> 04:12.580 align:middle line:90%
which is a 5, which
is notification level.

126
04:12.580 --> 04:14.670 align:middle line:90%
And then this is
also giving us a clue

127
04:14.670 --> 04:16.350 align:middle line:84%
regarding why it came up.

128
04:16.350 --> 04:18.480 align:middle line:90%
And it was a
configuration-related item.

129
04:18.480 --> 04:21.120 align:middle line:90%
And then this is some just
like text, easy to read,

130
04:21.120 --> 04:23.910 align:middle line:90%
so we can kind of get a clue
on what exactly happened there.

131
04:23.910 --> 04:26.790 align:middle line:90%
And all these additional details
that were not there before

132
04:26.790 --> 04:29.010 align:middle line:90%
are included now because we
did the service timestamp

133
04:29.010 --> 04:30.112 align:middle line:84%
command for logs.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

133
04:29.010 --> 04:30.112 align:middle line:84%
command for logs.

134
04:30.112 --> 04:32.070 align:middle line:90%
And if we wanted to, we
could do the same thing

135
04:32.070 --> 04:34.333 align:middle line:84%
for debug messages as well.

136
04:34.333 --> 04:36.000 align:middle line:90%
So if we go back into
configuration mode

137
04:36.000 --> 04:38.520 align:middle line:90%
and we hit the Up Arrow
key a couple of times,

138
04:38.520 --> 04:40.080 align:middle line:90%
and we go back to
service timestamps,

139
04:40.080 --> 04:43.380 align:middle line:90%
this time instead
of saying for log,

140
04:43.380 --> 04:45.515 align:middle line:90%
we'll go ahead
and say for debug.

141
04:45.515 --> 04:46.890 align:middle line:90%
That way they'll
also be included

142
04:46.890 --> 04:49.610 align:middle line:84%
in debug messages as well.

143
04:49.610 --> 04:50.160 align:middle line:84%
Great.

144
04:50.160 --> 04:52.640 align:middle line:90%
Task number one, tweaking
the actual log messages.

145
04:52.640 --> 04:53.380 align:middle line:84%
Done.

146
04:53.380 --> 04:53.880 align:middle line:84%
Number two.

147
04:53.880 --> 04:56.380 align:middle line:90%
Let's tweak the levels that are
sent to a given destination.

148
04:56.380 --> 04:59.970 align:middle line:90%
And we can see our destinations
by doing a show logging.

149
04:59.970 --> 05:03.360 align:middle line:90%
And we currently have
console, monitor, and buffer.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

149
04:59.970 --> 05:03.360 align:middle line:90%
And we currently have
console, monitor, and buffer.

150
05:03.360 --> 05:04.380 align:middle line:84%
So let's do this.

151
05:04.380 --> 05:07.890 align:middle line:90%
Let's tweak the monitor
down to a lower level.

152
05:07.890 --> 05:09.460 align:middle line:90%
They're all at
debugging by default.

153
05:09.460 --> 05:11.250 align:middle line:90%
Also, when you tweak
a level, it also

154
05:11.250 --> 05:12.960 align:middle line:90%
shows you in the
context sensitive help

155
05:12.960 --> 05:16.110 align:middle line:90%
what those levels are, and also
what the associated names are,

156
05:16.110 --> 05:17.450 align:middle line:84%
which is quite helpful as well.

157
05:17.450 --> 05:19.100 align:middle line:90%
So let's go to
configuration mode.

158
05:19.100 --> 05:21.843 align:middle line:84%
Let's do a logging.

159
05:21.843 --> 05:23.260 align:middle line:90%
And let's play
with the VTY lines.

160
05:23.260 --> 05:26.960 align:middle line:90%
Logging monitor,
Question Mark, and let's

161
05:26.960 --> 05:30.140 align:middle line:84%
specify level 3 right here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

161
05:26.960 --> 05:30.140 align:middle line:84%
specify level 3 right here.

162
05:30.140 --> 05:33.350 align:middle line:90%
So level 3 is errors,
which will include level 3

163
05:33.350 --> 05:37.250 align:middle line:90%
and below, numerically
below, 3, 2, 1, and 0.

164
05:37.250 --> 05:39.570 align:middle line:90%
And now if we do
a do show logging,

165
05:39.570 --> 05:41.070 align:middle line:90%
now it's showing
us monitor logging.

166
05:41.070 --> 05:42.720 align:middle line:84%
Think of that like VTY lines.

167
05:42.720 --> 05:47.360 align:middle line:90%
It's now set at level
3 or the error's level.

168
05:47.360 --> 05:48.280 align:middle line:84%
So let's test this.

169
05:48.280 --> 05:51.070 align:middle line:90%
Let's go to type
in the end here.

170
05:51.070 --> 05:53.960 align:middle line:90%
Let me just show
ip interface brief.

171
05:53.960 --> 05:55.190 align:middle line:84%
And let's telnet to this guy.

172
05:55.190 --> 05:57.940 align:middle line:90%
Now, R2, we should be
able to telnet to 1.1.1.1.

173
05:57.940 --> 05:59.160 align:middle line:84%
Let's go to R2.

174
05:59.160 --> 06:01.460 align:middle line:90%
I just want to verify
via VTY line access
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

174
05:59.160 --> 06:01.460 align:middle line:90%
I just want to verify
via VTY line access

175
06:01.460 --> 06:03.710 align:middle line:90%
that we're getting the
appropriate level of messages

176
06:03.710 --> 06:04.700 align:middle line:84%
coming back in.

177
06:04.700 --> 06:09.790 align:middle line:90%
So on router 2, we'll
do a telnet to 1.1.1.1.

178
06:09.790 --> 06:11.140 align:middle line:84%
Password required, but none set.

179
06:11.140 --> 06:12.015 align:middle line:84%
More troubleshooting.

180
06:12.015 --> 06:12.515 align:middle line:84%
OK.

181
06:12.515 --> 06:13.090 align:middle line:84%
Let's do it.

182
06:13.090 --> 06:14.710 align:middle line:84%
So we'll go back to R1.

183
06:14.710 --> 06:23.010 align:middle line:90%
And on R1, we'll say show
run pipe section line.

184
06:23.010 --> 06:26.040 align:middle line:90%
So for the line VTY
0 through 4 login.

185
06:26.040 --> 06:27.150 align:middle line:84%
So there's no password.

186
06:27.150 --> 06:28.500 align:middle line:84%
Let's tweak it.

187
06:28.500 --> 06:31.812 align:middle line:84%
Config line vty 0 through 4.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

187
06:28.500 --> 06:31.812 align:middle line:84%
Config line vty 0 through 4.

188
06:31.812 --> 06:33.270 align:middle line:90%
And it's going to
let it wide open.

189
06:33.270 --> 06:36.420 align:middle line:90%
No login, meaning
no login required.

190
06:36.420 --> 06:40.290 align:middle line:90%
And we'll do-- while we're at
it, privilege level 15, just

191
06:40.290 --> 06:42.810 align:middle line:90%
to give ourselves a
little more easy access.

192
06:42.810 --> 06:43.560 align:middle line:84%
Excellent.

193
06:43.560 --> 06:46.330 align:middle line:84%
And then we'll go back to R2.

194
06:46.330 --> 06:50.950 align:middle line:84%
And we'll connect to 1.1.1.1.

195
06:50.950 --> 06:53.160 align:middle line:84%
I guess no.

196
06:53.160 --> 06:55.170 align:middle line:84%
So we'll telnet to 1.1.1.1.

197
06:55.170 --> 06:55.980 align:middle line:84%
Great.

198
06:55.980 --> 06:56.700 align:middle line:84%
Now we're at R1.

199
06:56.700 --> 06:58.200 align:middle line:84%
We'll just show users.

200
06:58.200 --> 07:00.390 align:middle line:84%
Another command for that is who.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

200
06:58.200 --> 07:00.390 align:middle line:84%
Another command for that is who.

201
07:00.390 --> 07:01.050 align:middle line:84%
Same thing.

202
07:01.050 --> 07:02.940 align:middle line:90%
And we are connected
on the VTY line.

203
07:02.940 --> 07:10.030 align:middle line:90%
So now we do a debug ip
packet and press Enter,

204
07:10.030 --> 07:11.340 align:middle line:84%
we just turned on debugging.

205
07:11.340 --> 07:13.530 align:middle line:84%
But they're all at level 7.

206
07:13.530 --> 07:15.680 align:middle line:90%
So we aren't likely
to see them here.

207
07:15.680 --> 07:18.180 align:middle line:90%
Actually, we're not likely to
see them here for two reasons.

208
07:18.180 --> 07:20.030 align:middle line:90%
Let's go back to
R1 for a second.

209
07:20.030 --> 07:22.030 align:middle line:90%
The console, so there's
the debug messages.

210
07:22.030 --> 07:24.416 align:middle line:84%
They're like, rah!

211
07:24.416 --> 07:25.850 align:middle line:84%
Who turned on that debug?

212
07:25.850 --> 07:26.903 align:middle line:84%
Let's track that down.

213
07:26.903 --> 07:28.570 align:middle line:90%
But there's actually
a couple of reasons

214
07:28.570 --> 07:29.570 align:middle line:84%
why we're not seeing it.

215
07:29.570 --> 07:32.990 align:middle line:90%
Back here at R1-- let's
do an un debug all.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

215
07:29.570 --> 07:32.990 align:middle line:90%
Back here at R1-- let's
do an un debug all.

216
07:32.990 --> 07:40.130 align:middle line:90%
And let's do a show-- let's do
a config t, and do show logging.

217
07:40.130 --> 07:44.160 align:middle line:90%
And let's set the logging
back up to like a level 7.

218
07:44.160 --> 07:44.945 align:middle line:84%
Let's do that.

219
07:44.945 --> 07:46.540 align:middle line:84%
Set it back to 7.

220
07:46.540 --> 07:50.140 align:middle line:90%
So logging, monitor,
and we'll go ahead

221
07:50.140 --> 07:54.130 align:middle line:90%
and say 7, which is everything
7 debugging level and below.

222
07:54.130 --> 07:55.600 align:middle line:90%
Now that that's
set, we'll go back

223
07:55.600 --> 07:58.990 align:middle line:90%
to R2, who has telnetted
in on the R2 tab.

224
07:58.990 --> 08:01.240 align:middle line:90%
We'll do a debug
IP packet again.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

224
07:58.990 --> 08:01.240 align:middle line:90%
We'll do a debug
IP packet again.

225
08:01.240 --> 08:03.120 align:middle line:84%
And I don't see any packets.

226
08:03.120 --> 08:06.970 align:middle line:90%
If we go back to R1, they're
happening at the console.

227
08:06.970 --> 08:11.320 align:middle line:90%
But from the terminal
session, we do a show logging.

228
08:11.320 --> 08:14.050 align:middle line:90%
This says that we're monitor
logging, level debugging.

229
08:14.050 --> 08:16.050 align:middle line:90%
Why are we not seeing
these messages?

230
08:16.050 --> 08:20.060 align:middle line:90%
And the answer is, as far
as troubleshooting, this.

231
08:20.060 --> 08:22.310 align:middle line:90%
We have to be willing at the
terminal we're sitting at

232
08:22.310 --> 08:23.690 align:middle line:84%
to say, I want to see this.

233
08:23.690 --> 08:25.380 align:middle line:84%
And now we do terminal monitor.

234
08:25.380 --> 08:27.842 align:middle line:90%
Well now go ahead and
see that information.

235
08:27.842 --> 08:30.050 align:middle line:90%
So we've taken a look at
how to configure the logging
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

235
08:27.842 --> 08:30.050 align:middle line:90%
So we've taken a look at
how to configure the logging

236
08:30.050 --> 08:31.500 align:middle line:84%
level for a destination.

237
08:31.500 --> 08:34.650 align:middle line:90%
We also take a look firsthand
at telnetting in, and also

238
08:34.650 --> 08:36.289 align:middle line:84%
troubleshooting some VTY access.

239
08:36.289 --> 08:38.570 align:middle line:90%
But telnetting in and
doing the terminal monitor.

240
08:38.570 --> 08:41.710 align:middle line:90%
And if we're going to turn
it off, it's terminal--

241
08:41.710 --> 08:44.960 align:middle line:90%
oh my gosh--
terminal no monitor.

242
08:44.960 --> 08:47.500 align:middle line:90%
Probably one of the
toughest commands to do.

243
08:47.500 --> 08:49.000 align:middle line:90%
So terminal no
monitor right there.

244
08:49.000 --> 08:50.170 align:middle line:84%
It turns off that feature.

245
08:50.170 --> 08:51.462 align:middle line:84%
But the debug is still running.

246
08:51.462 --> 08:53.180 align:middle line:90%
So we've got to
turn it off as well.

247
08:53.180 --> 08:55.460 align:middle line:90%
So un debut all will
certainly do that.

248
08:55.460 --> 08:57.190 align:middle line:84%
And I will type in exit.

249
08:57.190 --> 08:59.890 align:middle line:90%
And we'll exit out of
the VTY connection.

250
08:59.890 --> 09:04.150 align:middle line:90%
One last thing I'd love to
do is do a show logging.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

250
08:59.890 --> 09:04.150 align:middle line:90%
One last thing I'd love to
do is do a show logging.

251
09:04.150 --> 09:06.453 align:middle line:90%
In this lab, let's
add a syslog server.

252
09:06.453 --> 09:07.870 align:middle line:90%
And the way we're
going to do that

253
09:07.870 --> 09:09.670 align:middle line:84%
is go to configuration mode.

254
09:09.670 --> 09:12.040 align:middle line:90%
We know what the IP address
is of our syslog server.

255
09:12.040 --> 09:14.990 align:middle line:84%
And we do logging, host.

256
09:14.990 --> 09:17.013 align:middle line:84%
And let's say it's 1.2.3.4.

257
09:17.013 --> 09:17.680 align:middle line:84%
That's our host.

258
09:17.680 --> 09:19.040 align:middle line:84%
Great.

259
09:19.040 --> 09:19.990 align:middle line:84%
Boom.

260
09:19.990 --> 09:22.870 align:middle line:90%
And then we can also specify
the level of messages

261
09:22.870 --> 09:24.730 align:middle line:84%
to send to that destination.

262
09:24.730 --> 09:28.420 align:middle line:90%
So logging trap, and then
the level we want to send.

263
09:28.420 --> 09:30.560 align:middle line:84%
So there's your levels again.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

263
09:28.420 --> 09:30.560 align:middle line:84%
So there's your levels again.

264
09:30.560 --> 09:33.370 align:middle line:90%
So if we want to send level
7 and below to that syslog

265
09:33.370 --> 09:34.745 align:middle line:84%
destination, we can.

266
09:34.745 --> 09:36.370 align:middle line:90%
That's what I'm going
to do right here.

267
09:36.370 --> 09:40.450 align:middle line:90%
Now, if we just showed logging,
and go down just a little bit,

268
09:40.450 --> 09:43.780 align:middle line:90%
now it's showing us that we're
doing logging to a destination

269
09:43.780 --> 09:45.598 align:middle line:84%
server at 1.2.3.4.

270
09:45.598 --> 09:47.140 align:middle line:90%
There's the default
port we're using.

271
09:47.140 --> 09:48.890 align:middle line:90%
If it's not working,
make sure that port's

272
09:48.890 --> 09:51.700 align:middle line:90%
available over the network
to that destination.

273
09:51.700 --> 09:54.670 align:middle line:90%
And we are logging at
level debugging based

274
09:54.670 --> 09:55.840 align:middle line:84%
on what we said right there.

275
09:55.840 --> 09:57.340 align:middle line:90%
And one last thing
while we're here,

276
09:57.340 --> 09:59.750 align:middle line:90%
if you want to disable
logging to a destination,

277
09:59.750 --> 10:00.730 align:middle line:84%
we can do that, too.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

277
09:59.750 --> 10:00.730 align:middle line:84%
we can do that, too.

278
10:00.730 --> 10:03.970 align:middle line:90%
If we've got to turn off logging
to the monitor altogether

279
10:03.970 --> 10:09.518 align:middle line:90%
for VTY lines, just
do no logging monitor.

280
10:09.518 --> 10:11.060 align:middle line:90%
And that is one way
to turn that off.

281
10:11.060 --> 10:14.070 align:middle line:84%
Show logging.

282
10:14.070 --> 10:15.940 align:middle line:84%
It is disabled right there.

283
10:15.940 --> 10:20.100 align:middle line:90%
On some IOSs, if you try to
turn off logging everywhere,

284
10:20.100 --> 10:21.993 align:middle line:90%
the console will
still do some logging.

285
10:21.993 --> 10:23.660 align:middle line:90%
It's like, I've got
to say it somewhere.

286
10:23.660 --> 10:24.870 align:middle line:84%
I've got to tell somebody.

287
10:24.870 --> 10:27.140 align:middle line:90%
Some versions of
IOS, some devices,

288
10:27.140 --> 10:28.890 align:middle line:90%
just will not let you
turn everything off.

289
10:28.890 --> 10:29.670 align:middle line:84%
Others will.

290
10:29.670 --> 10:32.640 align:middle line:90%
So this is how you could turn it
off on a particular destination
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

290
10:29.670 --> 10:32.640 align:middle line:90%
So this is how you could turn it
off on a particular destination

291
10:32.640 --> 10:33.815 align:middle line:84%
just by saying no.

292
10:33.815 --> 10:35.940 align:middle line:90%
So in this video and lab,
we've had the opportunity

293
10:35.940 --> 10:38.107 align:middle line:90%
to tweak the log message
in the format of what we're

294
10:38.107 --> 10:40.710 align:middle line:90%
going to see in those
messages, to configure

295
10:40.710 --> 10:43.290 align:middle line:90%
additional destinations,
like another syslog server,

296
10:43.290 --> 10:46.020 align:middle line:90%
and we've also had the
opportunity to tweak the levels

297
10:46.020 --> 10:47.670 align:middle line:90%
that we're going
to use to assign

298
10:47.670 --> 10:48.940 align:middle line:84%
for our various destinations.

299
10:48.940 --> 10:50.565 align:middle line:90%
In the example we
used, we tweaked what

300
10:50.565 --> 10:52.050 align:middle line:84%
was being sent to the monitor.

301
10:52.050 --> 10:55.290 align:middle line:90%
And we also verified that if
you don't do terminal monitor

302
10:55.290 --> 10:57.030 align:middle line:90%
on your VTY end,
you're not going

303
10:57.030 --> 10:59.040 align:middle line:90%
to see the log
messages regardless

304
10:59.040 --> 11:00.390 align:middle line:84%
of what's being permitted.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

304
10:59.040 --> 11:00.390 align:middle line:84%
of what's being permitted.

305
11:00.390 --> 11:02.057 align:middle line:90%
So I'll see you in
the next video, where

306
11:02.057 --> 11:04.440 align:middle line:90%
we'll take a look at some
conditional debugging, which is

307
11:04.440 --> 11:05.910 align:middle line:84%
some pretty cool stuff as well.

308
11:05.910 --> 11:08.400 align:middle line:90%
Until then, I hope this has
been informative for you.

309
11:08.400 --> 11:11.600 align:middle line:90%
And I'd like to thank
you for viewing.