WEBVTT

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


2
00:01.400 --> 00:03.920 align:middle line:90%
Debugging is a wonderful tool
that we can have in our tool

3
00:03.920 --> 00:05.810 align:middle line:90%
belt. And we're going
to use it sparingly,

4
00:05.810 --> 00:08.420 align:middle line:90%
because it does take, especially
if we're doing lots of debug

5
00:08.420 --> 00:10.490 align:middle line:90%
informations, all coming
to the console, that

6
00:10.490 --> 00:11.787 align:middle line:84%
takes a lot of CPU.

7
00:11.787 --> 00:13.370 align:middle line:90%
So we're going to
use debug sparingly.

8
00:13.370 --> 00:14.870 align:middle line:90%
And also, I'd like
to share with you

9
00:14.870 --> 00:17.180 align:middle line:90%
the option of a
conditional debug, which

10
00:17.180 --> 00:20.000 align:middle line:90%
can, for some
protocols, help reduce

11
00:20.000 --> 00:22.870 align:middle line:90%
the strain and the output on
that device by that much more.

12
00:22.870 --> 00:25.370 align:middle line:90%
So with debugging, the first
thing we would want to consider

13
00:25.370 --> 00:27.920 align:middle line:90%
is the destinations
of the output.

14
00:27.920 --> 00:29.900 align:middle line:90%
Now, by default, we
saw in our previous lab

15
00:29.900 --> 00:34.160 align:middle line:90%
that the destinations are
the console, the buffer,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

15
00:29.900 --> 00:34.160 align:middle line:90%
that the destinations are
the console, the buffer,

16
00:34.160 --> 00:36.970 align:middle line:90%
and the monitor, the VTY
lines that are connected

17
00:36.970 --> 00:38.870 align:middle line:84%
full force, at Level 7.

18
00:38.870 --> 00:41.420 align:middle line:90%
So if you want to control
where all that is going,

19
00:41.420 --> 00:43.720 align:middle line:90%
we might want to
constrain that, and maybe

20
00:43.720 --> 00:47.120 align:middle line:90%
do Level 7 as a buffer,
which is great, as a default.

21
00:47.120 --> 00:49.490 align:middle line:90%
And maybe we take
level of the console

22
00:49.490 --> 00:51.290 align:middle line:90%
and we tell it
Level 6 and below.

23
00:51.290 --> 00:53.650 align:middle line:90%
That way, we're not going
to overwhelm the console,

24
00:53.650 --> 00:55.400 align:middle line:90%
because that does take
a lot of direct CPU

25
00:55.400 --> 00:58.630 align:middle line:90%
to send those console
messages to the console,

26
00:58.630 --> 01:00.560 align:middle line:90%
line console 0, as
opposed to buffer.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
00:58.630 --> 01:00.560 align:middle line:90%
line console 0, as
opposed to buffer.

27
01:00.560 --> 01:03.912 align:middle line:90%
Memory is a lot faster than
it is sending it to your CLA.

28
01:03.912 --> 01:05.870 align:middle line:90%
So that's one option that
you want be aware of.

29
01:05.870 --> 01:08.840 align:middle line:90%
Secondly, when you do a debug,
do as granular of a debug

30
01:08.840 --> 01:09.750 align:middle line:84%
as we can.

31
01:09.750 --> 01:11.840 align:middle line:90%
So if we want to
debug, instead, like,

32
01:11.840 --> 01:17.660 align:middle line:90%
debug the entire protocol,
maybe debug the specific part,

33
01:17.660 --> 01:20.690 align:middle line:90%
like hello messages or
some piece of that protocol

34
01:20.690 --> 01:22.190 align:middle line:90%
that you're trying
to troubleshoot.

35
01:22.190 --> 01:23.930 align:middle line:90%
Because that's going to help
you in troubleshooting, also,

36
01:23.930 --> 01:26.180 align:middle line:90%
by looking at just detailed
information that comes in.

37
01:26.180 --> 01:28.040 align:middle line:90%
Instead of, like, an
ocean of information,

38
01:28.040 --> 01:29.870 align:middle line:90%
whether it's coming live at
you at the console, which

39
01:29.870 --> 01:32.270 align:middle line:90%
is a pain in the rear, or
whether it's coming to buffer.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:29.870 --> 01:32.270 align:middle line:90%
is a pain in the rear, or
whether it's coming to buffer.

40
01:32.270 --> 01:35.720 align:middle line:90%
Also, at the console, what I
always do, before I do a debug,

41
01:35.720 --> 01:39.510 align:middle line:90%
is I will do a undebug space
all before I do the debug.

42
01:39.510 --> 01:41.510 align:middle line:90%
Because that way, I can
hit the up arrow key one

43
01:41.510 --> 01:44.950 align:middle line:90%
time, press Enter, and
I can do an undebug

44
01:44.950 --> 01:46.790 align:middle line:90%
to go ahead and bring
back the previous--

45
01:46.790 --> 01:48.558 align:middle line:84%
I guess, two up arrows.

46
01:48.558 --> 01:50.850 align:middle line:90%
Because the previous command
would be the debug itself.

47
01:50.850 --> 01:52.290 align:middle line:90%
So I want to have
that in my history,

48
01:52.290 --> 01:54.707 align:middle line:90%
so I can hit the up arrow key
a couple of times and do it.

49
01:54.707 --> 01:57.560 align:middle line:90%
So practicing those skills
of getting out of danger

50
01:57.560 --> 01:58.490 align:middle line:84%
are important as well.

51
01:58.490 --> 02:02.420 align:middle line:90%
All right, so one other option
I'd like to share with you
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
01:58.490 --> 02:02.420 align:middle line:90%
All right, so one other option
I'd like to share with you

52
02:02.420 --> 02:07.790 align:middle line:90%
is the option of a
conditional debug.

53
02:07.790 --> 02:10.639 align:middle line:90%
So let's imagine-- and it
goes something like this.

54
02:10.639 --> 02:12.540 align:middle line:90%
Let's imagine we're
debugging OSPF,

55
02:12.540 --> 02:14.577 align:middle line:90%
and we are debugging
the hello messages.

56
02:14.577 --> 02:16.410 align:middle line:90%
We're interested in
looking at those, that's

57
02:16.410 --> 02:18.210 align:middle line:84%
pretty granular to begin with.

58
02:18.210 --> 02:20.310 align:middle line:90%
But this router is
receiving hello messages

59
02:20.310 --> 02:23.507 align:middle line:90%
and processing hello
messages here and here.

60
02:23.507 --> 02:25.590 align:middle line:90%
And if we had other
interfaces, elsewhere as well.

61
02:25.590 --> 02:27.390 align:middle line:90%
With conditional debugs,
we could actually

62
02:27.390 --> 02:29.790 align:middle line:90%
say-- we could set up
a condition and say,

63
02:29.790 --> 02:32.640 align:middle line:90%
only, the debug that's
currently running, only
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:29.790 --> 02:32.640 align:middle line:90%
only, the debug that's
currently running, only

64
02:32.640 --> 02:35.670 align:middle line:90%
have it apply for a
specific interface.

65
02:35.670 --> 02:39.000 align:middle line:90%
And so if we pointed
to this Interface 6,

66
02:39.000 --> 02:41.130 align:middle line:90%
the hello messages
that happened over here

67
02:41.130 --> 02:44.070 align:middle line:90%
would not be included in
our debug, in the output.

68
02:44.070 --> 02:47.292 align:middle line:90%
Now, there's good news and bad
news about conditional debugs.

69
02:47.292 --> 02:49.500 align:middle line:90%
Well, first, a couple of
other details, and then I'll

70
02:49.500 --> 02:51.150 align:middle line:90%
share with you the
good news and bad news.

71
02:51.150 --> 02:52.358 align:middle line:84%
So you can set up conditions.

72
02:52.358 --> 02:56.800 align:middle line:90%
So if we say the
condition is Interface 6,

73
02:56.800 --> 02:58.380 align:middle line:84%
then, like, condition Number 1.

74
02:58.380 --> 03:00.180 align:middle line:90%
And then we can
say, also, I want
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
02:58.380 --> 03:00.180 align:middle line:90%
And then we can
say, also, I want

75
03:00.180 --> 03:03.450 align:middle line:90%
to pay attention to a certain IP
address or a certain something

76
03:03.450 --> 03:03.950 align:middle line:84%
else.

77
03:03.950 --> 03:08.270 align:middle line:90%
We could have IP, that
can be condition Number 2.

78
03:08.270 --> 03:10.010 align:middle line:84%
And then we can actually group--

79
03:10.010 --> 03:11.120 align:middle line:84%
keep adding conditions.

80
03:11.120 --> 03:14.090 align:middle line:90%
And what will happen
is, they have to match.

81
03:14.090 --> 03:16.310 align:middle line:90%
Anything that doesn't
match in your conditions

82
03:16.310 --> 03:18.930 align:middle line:90%
won't be included as part
of your output for debug.

83
03:18.930 --> 03:21.920 align:middle line:90%
So you can include multiple
conditions for the debug.

84
03:21.920 --> 03:25.760 align:middle line:90%
So that's the good news, is it's
very granular and really cool,

85
03:25.760 --> 03:27.530 align:middle line:84%
but here's--

86
03:27.530 --> 03:28.770 align:middle line:84%
let me go to the big screen.

87
03:28.770 --> 03:30.830 align:middle line:84%
The problem is-- oh, my gosh.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
03:28.770 --> 03:30.830 align:middle line:84%
The problem is-- oh, my gosh.

88
03:30.830 --> 03:32.960 align:middle line:90%
So as I'm brushing up
for this, I labed it up

89
03:32.960 --> 03:34.490 align:middle line:84%
in a emulated environment.

90
03:34.490 --> 03:39.765 align:middle line:90%
And I just did some basic bugs
and then I did conditions,

91
03:39.765 --> 03:40.640 align:middle line:84%
and it wasn't taking.

92
03:40.640 --> 03:42.740 align:middle line:90%
It was like, everything's
still coming in.

93
03:42.740 --> 03:47.030 align:middle line:90%
And then I tried a different
set of virtual gear,

94
03:47.030 --> 03:49.170 align:middle line:84%
different iOSs, same problem.

95
03:49.170 --> 03:51.170 align:middle line:90%
Then I said, great, I'll
fire up some live gear,

96
03:51.170 --> 03:53.870 align:middle line:90%
fired up the live
gear, same problems.

97
03:53.870 --> 03:56.390 align:middle line:90%
These conditional
debugs, they don't

98
03:56.390 --> 03:59.360 align:middle line:90%
apply to every possible debug
that you're going to be doing.

99
03:59.360 --> 04:01.340 align:middle line:90%
So I would recommend
before you think
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

99
03:59.360 --> 04:01.340 align:middle line:90%
So I would recommend
before you think

100
04:01.340 --> 04:03.770 align:middle line:90%
you're going to try one,
like, debug IP packet,

101
04:03.770 --> 04:05.470 align:middle line:90%
and then say, just
this interface,

102
04:05.470 --> 04:07.610 align:middle line:90%
you might want to test
that out on the gear

103
04:07.610 --> 04:09.803 align:middle line:90%
that you would want to
use that on before you're

104
04:09.803 --> 04:10.970 align:middle line:84%
in a production environment.

105
04:10.970 --> 04:15.070 align:middle line:90%
Because I discovered, on
three different sets of gear,

106
04:15.070 --> 04:18.890 align:middle line:90%
two virtual, one physical,
that it doesn't always

107
04:18.890 --> 04:23.510 align:middle line:90%
function for every single debug
that's in the debug arsenal.

108
04:23.510 --> 04:26.120 align:middle line:90%
All right, having said
that, in this hands on lab,

109
04:26.120 --> 04:28.130 align:middle line:90%
let me walk you
through a scenario that

110
04:28.130 --> 04:29.810 align:middle line:90%
does work in the
virtual environment

111
04:29.810 --> 04:32.060 align:middle line:90%
and also would work in a
physical environment as well.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
04:29.810 --> 04:32.060 align:middle line:90%
and also would work in a
physical environment as well.

112
04:32.060 --> 04:33.890 align:middle line:90%
So you can kind of
get a taste and a feel

113
04:33.890 --> 04:37.010 align:middle line:90%
for working with
conditional debugs.

114
04:37.010 --> 04:38.930 align:middle line:90%
And to do that in his
lab that I've provided,

115
04:38.930 --> 04:42.740 align:middle line:90%
we are going to use Router 2,
let's do a show IP protocols,

116
04:42.740 --> 04:44.850 align:middle line:84%
see what he's running.

117
04:44.850 --> 04:48.030 align:middle line:90%
And he's got OSPF
and BGP, that's

118
04:48.030 --> 04:49.710 align:middle line:84%
fantastic, more than enough.

119
04:49.710 --> 04:52.890 align:middle line:90%
And let's do a show
IP OSPF neighbor.

120
04:52.890 --> 04:55.620 align:middle line:90%
All right, we've got some
neighbors, fantastic.

121
04:55.620 --> 05:00.370 align:middle line:90%
Let's do a debug
of IP OSPF hello.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

121
04:55.620 --> 05:00.370 align:middle line:90%
Let's do a debug
of IP OSPF hello.

122
05:00.370 --> 05:03.620 align:middle line:90%
There we go, so we are
sitting, let's do a do--

123
05:03.620 --> 05:06.570 align:middle line:84%
let's do a show logging.

124
05:06.570 --> 05:09.180 align:middle line:90%
Though currently, we're
logging to the console monitor

125
05:09.180 --> 05:12.990 align:middle line:90%
and buffer at Level 7, which
includes Level 7 and below.

126
05:12.990 --> 05:16.290 align:middle line:90%
And we go show
users, I'm currently

127
05:16.290 --> 05:18.150 align:middle line:84%
sitting at the console, great.

128
05:18.150 --> 05:19.890 align:middle line:84%
So we're seeing those messages.

129
05:19.890 --> 05:22.800 align:middle line:90%
And I'm seeing interfaces
involved of gig 2/0,

130
05:22.800 --> 05:27.380 align:middle line:84%
and gig 1/0, and gig 0/0, great.

131
05:27.380 --> 05:30.650 align:middle line:90%
So let me turn that
off for a moment,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

131
05:27.380 --> 05:30.650 align:middle line:90%
So let me turn that
off for a moment,

132
05:30.650 --> 05:33.770 align:middle line:90%
so you can see the typing
roll up as it happens.

133
05:33.770 --> 05:35.810 align:middle line:90%
I've also got a
logging synchronous

134
05:35.810 --> 05:39.170 align:middle line:90%
on the console line, that way
it repaints the line for me,

135
05:39.170 --> 05:40.220 align:middle line:84%
which is--

136
05:40.220 --> 05:41.640 align:middle line:84%
we've done that forever.

137
05:41.640 --> 05:44.150 align:middle line:90%
So let's go ahead and
set up a condition.

138
05:44.150 --> 05:47.630 align:middle line:90%
And the syntax is right
here in privilege mode,

139
05:47.630 --> 05:50.353 align:middle line:84%
debug condition.

140
05:50.353 --> 05:52.020 align:middle line:90%
And then we set up
the condition that we

141
05:52.020 --> 05:56.880 align:middle line:90%
want, we have Mac address,
IP address, interface.

142
05:56.880 --> 06:01.170 align:middle line:90%
And we'll do an interface, and
let me scroll up a little bit,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

142
05:56.880 --> 06:01.170 align:middle line:90%
And we'll do an interface, and
let me scroll up a little bit,

143
06:01.170 --> 06:02.640 align:middle line:84%
see what interfaces we had.

144
06:02.640 --> 06:04.098 align:middle line:90%
And here's what
I'd like to do, I'm

145
06:04.098 --> 06:05.680 align:middle line:84%
going to do gig 0/0 and 1/0.

146
06:05.680 --> 06:07.680 align:middle line:90%
So either one of those
will match the condition,

147
06:07.680 --> 06:09.280 align:middle line:90%
but we shouldn't
see any gig 2/0,

148
06:09.280 --> 06:12.100 align:middle line:90%
regarding IP OSPF
hellos after that.

149
06:12.100 --> 06:17.920 align:middle line:90%
So I'll interface gig 0/0,
and there's one condition set,

150
06:17.920 --> 06:20.175 align:middle line:84%
and we'll also do 1/0.

151
06:20.175 --> 06:21.550 align:middle line:90%
And to see that,
we're just going

152
06:21.550 --> 06:24.683 align:middle line:90%
to do a show debug
condition, and it'll

153
06:24.683 --> 06:25.600 align:middle line:84%
show us what they are.

154
06:25.600 --> 06:28.960 align:middle line:90%
So condition 1 is looking for
that interface, condition 2.

155
06:28.960 --> 06:30.610 align:middle line:84%
So any debugs that we do now--
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

155
06:28.960 --> 06:30.610 align:middle line:84%
So any debugs that we do now--

156
06:30.610 --> 06:32.672 align:middle line:90%
I shouldn't say any,
because some debugs don't

157
06:32.672 --> 06:34.630 align:middle line:90%
give a hoot about filtering
based on interface,

158
06:34.630 --> 06:37.240 align:middle line:84%
but the IP OSPF hellos do.

159
06:37.240 --> 06:40.360 align:middle line:90%
They will only pay
attention to those hellos

160
06:40.360 --> 06:43.450 align:middle line:90%
and show up messages if
it's regarding 0/0 or 1/0,

161
06:43.450 --> 06:45.190 align:middle line:84%
2/0 is not going to show up.

162
06:45.190 --> 06:50.130 align:middle line:90%
So I'll do a debug, IP OSPF
hello, and there it goes.

163
06:50.130 --> 06:51.630 align:middle line:90%
So we're going to
get some messages,

164
06:51.630 --> 06:56.640 align:middle line:90%
we're looking for 0/0,
1/0, but no 2/0, they just

165
06:56.640 --> 06:57.897 align:middle line:84%
shouldn't show up anymore.

166
06:57.897 --> 06:59.480 align:middle line:90%
If you want, we can
link it up to 1/0.

167
06:59.480 --> 07:05.070 align:middle line:90%
So let's go ahead and do
a show debug conditions,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

167
06:59.480 --> 07:05.070 align:middle line:90%
So let's go ahead and do
a show debug conditions,

168
07:05.070 --> 07:07.880 align:middle line:90%
and we can say, no
debug condition.

169
07:07.880 --> 07:09.450 align:middle line:90%
And let's take off
debug condition 2.

170
07:09.450 --> 07:11.610 align:middle line:90%
You can actually type out
what the condition was,

171
07:11.610 --> 07:13.410 align:middle line:90%
but it's a lot
easier to do the 2.

172
07:13.410 --> 07:15.240 align:middle line:90%
So I'll take out
debug condition 2,

173
07:15.240 --> 07:18.410 align:middle line:90%
so now it should
be just gig 0/0.

174
07:18.410 --> 07:21.410 align:middle line:90%
So there's a send on 0/0,
there's a hello on 0/0,

175
07:21.410 --> 07:22.070 align:middle line:84%
it's a party.

176
07:22.070 --> 07:27.120 align:middle line:90%
But it's only a party for
gig 0/0, because of this,

177
07:27.120 --> 07:28.900 align:middle line:84%
show debug conditions.

178
07:28.900 --> 07:30.900 align:middle line:90%
Also, it's important to
know for troubleshooting
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

178
07:28.900 --> 07:30.900 align:middle line:90%
Also, it's important to
know for troubleshooting

179
07:30.900 --> 07:33.970 align:middle line:90%
that, if you have these
conditions in place,

180
07:33.970 --> 07:35.470 align:middle line:90%
and you're done
with your debug, you

181
07:35.470 --> 07:36.985 align:middle line:90%
go home, whatever,
you come back,

182
07:36.985 --> 07:38.360 align:middle line:90%
these conditions
are still there.

183
07:38.360 --> 07:40.000 align:middle line:90%
So if you do a
debug in the future,

184
07:40.000 --> 07:41.945 align:middle line:90%
and that condition
is still present,

185
07:41.945 --> 07:43.570 align:middle line:90%
you may be filtering
some of the output

186
07:43.570 --> 07:46.450 align:middle line:90%
that you would otherwise
expect to go ahead and see.

187
07:46.450 --> 07:51.805 align:middle line:90%
So if we did a no
debug condition,

188
07:51.805 --> 07:53.930 align:middle line:90%
and I'm going to take off
condition 1, right there,

189
07:53.930 --> 07:55.410 align:middle line:84%
because it's stated as 1.

190
07:55.410 --> 07:57.080 align:middle line:90%
It's going to give me a warning,
this is your last condition,

191
07:57.080 --> 07:58.100 align:middle line:90%
are you sure you
want to remove them?

192
07:58.100 --> 07:59.975 align:middle line:90%
You're not going to have
any conditions left.

193
07:59.975 --> 08:00.980 align:middle line:84%
I'll say, yes.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

193
07:59.975 --> 08:00.980 align:middle line:84%
I'll say, yes.

194
08:00.980 --> 08:03.870 align:middle line:90%
And now if we do a debug IP OSPF
hello, there's no conditions,

195
08:03.870 --> 08:06.210 align:middle line:90%
so any hello in a
storm is going to do.

196
08:06.210 --> 08:10.680 align:middle line:84%
That includes 0/0, 1/0, and 2/0.

197
08:10.680 --> 08:13.500 align:middle line:90%
Because when those hellos show
up, the debug is triggered,

198
08:13.500 --> 08:16.040 align:middle line:90%
and it's going to show
us that information.

199
08:16.040 --> 08:18.313 align:middle line:90%
So I'm going to turn it
off with the undebug all,

200
08:18.313 --> 08:19.230 align:middle line:84%
and there you have it.

201
08:19.230 --> 08:21.703 align:middle line:90%
Conditional debugging, make
sure you practice with it,

202
08:21.703 --> 08:23.245 align:middle line:90%
with the gear that
you're going to be

203
08:23.245 --> 08:26.370 align:middle line:90%
using in production to know
what the behaviors are before.

204
08:26.370 --> 08:29.400 align:middle line:90%
you just expect that, oh,
if I limit it to gig, like,

205
08:29.400 --> 08:33.350 align:middle line:90%
1/0, that means everything else,
other than that one interface,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

205
08:29.400 --> 08:33.350 align:middle line:90%
1/0, that means everything else,
other than that one interface,

206
08:33.350 --> 08:34.350 align:middle line:84%
is going to be excluded.

207
08:34.350 --> 08:38.039 align:middle line:90%
And for most of the debugs that
I tried in setting this up,

208
08:38.039 --> 08:41.333 align:middle line:90%
most of the debugs don't give
a hoot about that condition.

209
08:41.333 --> 08:42.750 align:middle line:90%
So in this video
and hands on lab,

210
08:42.750 --> 08:46.470 align:middle line:90%
we've had the opportunity to
discover, practice, and verify

211
08:46.470 --> 08:49.533 align:middle line:90%
the use of debugging
conditions on a Cisco router.

212
08:49.533 --> 08:51.450 align:middle line:90%
So thanks for joining
me in this set of videos

213
08:51.450 --> 08:53.610 align:middle line:90%
regarding logging and I'll
see you in the next set.

214
08:53.610 --> 08:56.100 align:middle line:90%
Meanwhile, I hope this has
been informative for you,

215
08:56.100 --> 08:59.420 align:middle line:90%
and I'd like to thank
you for viewing.