WEBVTT

1
00:00.000 --> 00:09.820
For this challenge, we're asked to answer a few questions here to verify our

2
00:09.820 --> 00:10.860
understanding

3
00:10.860 --> 00:13.360
of the content in this skill.

4
00:13.360 --> 00:17.880
So let's go ahead and jump in with our first question.

5
00:17.880 --> 00:24.880
Which command will turn off all debugging on an iOS XE router?

6
00:24.880 --> 00:29.890
So this answer is really just sort of about remembering what the answer is, and

7
00:29.890 --> 00:30.640
it's certainly
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

7
00:29.890 --> 00:30.640
it's certainly

8
00:30.640 --> 00:37.040
not debug all off, it's not debug disable, and it's not debug none.

9
00:37.040 --> 00:42.760
So that leaves us with undibug all as being the correct answer.

10
00:42.760 --> 00:47.880
Now just for a note here, I really do not recommend it.

11
00:47.880 --> 00:55.050
However, you can also say no debug all, but the reason I don't like that one is

12
00:55.050 --> 00:55.660
if you

13
00:55.660 --> 01:01.540
accidentally forget to type no, well then you're turning on debug all.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:55.660 --> 01:01.540
accidentally forget to type no, well then you're turning on debug all.

14
01:01.540 --> 01:05.860
Of course, by that argument, if you forget to put the un-in front of undibug,

15
01:05.860 --> 01:06.340
you're

16
01:06.340 --> 01:08.220
also typing debug all.

17
01:08.220 --> 01:16.220
But the advantage to undibug all honestly is that you can shorten it to you all

18
01:16.220 --> 01:16.360
, and

19
01:16.360 --> 01:21.090
Cisco has made it purposefully so no other command begins with the letter U,

20
01:21.090 --> 01:21.740
making this

21
01:21.740 --> 01:27.400
real quick and easy to do, and that way you're not even typing debug at all.

22
01:27.400 --> 01:34.000
So UAll is actually the command that I prefer to turn off all of the debugging.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
01:27.400 --> 01:34.000
So UAll is actually the command that I prefer to turn off all of the debugging.

23
01:34.000 --> 01:41.030
Next question, which trace option will cause the device not to attempt DNS

24
01:41.030 --> 01:42.640
resolution on

25
01:42.640 --> 01:44.440
each hop?

26
01:44.440 --> 01:48.730
So this again is just sort of a matter of memorization, but let's go ahead and

27
01:48.730 --> 01:49.200
go down

28
01:49.200 --> 01:50.400
our list.

29
01:50.400 --> 01:53.080
It is not no name.

30
01:53.080 --> 01:55.720
It is not IP address.

31
01:55.720 --> 01:59.000
It is not DNS disable.

32
01:59.000 --> 02:04.320
So that leaves us with numeric as our correct answer.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:59.000 --> 02:04.320
So that leaves us with numeric as our correct answer.

33
02:04.320 --> 02:08.270
Remember the way this works is you simply say trace, put in the IP address that

34
02:08.270 --> 02:08.680
you want

35
02:08.680 --> 02:13.960
to trace to, and then say numeric, and on the output of a trace, it will not

36
02:13.960 --> 02:14.920
display the

37
02:14.920 --> 02:21.580
DNS names, which can be a little bit quicker, and b, a little bit cleaner to

38
02:21.580 --> 02:22.680
read if you're

39
02:22.680 --> 02:27.480
not trying to do it by DNS name resolution.

40
02:27.480 --> 02:30.880
So that makes numeric our correct answer.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
02:27.480 --> 02:30.880
So that makes numeric our correct answer.

41
02:30.880 --> 02:38.280
Final question, assuming BGP inbound soft reconfiguration is enabled.

42
02:38.280 --> 02:44.640
What will the command show IP BGP neighbor, the neighbor's address received

43
02:44.640 --> 02:45.720
dash routes

44
02:45.720 --> 02:48.320
allow you to diagnose.

45
02:48.320 --> 02:51.240
So let's go ahead and go down our answers.

46
02:51.240 --> 02:54.480
First inbound BGP filters.

47
02:54.480 --> 02:59.620
Now this sounds like a really good answer because received routes will show us

48
02:59.620 --> 03:00.120
what we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
02:59.620 --> 03:00.120
what we

49
03:00.120 --> 03:02.000
received from the neighbor.

50
03:02.000 --> 03:08.300
And of course we can just do a regular show IP BGP to see what's in our BGP

51
03:08.300 --> 03:08.680
table, compare

52
03:08.680 --> 03:14.260
those two, and that'll allow us to see if our inbound BGP filters are

53
03:14.260 --> 03:15.840
preventing updates

54
03:15.840 --> 03:18.440
from getting into our BGP table.

55
03:18.440 --> 03:24.440
So inbound BGP filters is a really good answer, but let's verify the other ones

56
03:24.440 --> 03:24.520
first.

57
03:24.520 --> 03:26.720
BGP neighbor failures.

58
03:26.720 --> 03:32.020
Well, I guess you could sort of say that because if you try to say show IP BGP
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

58
03:26.720 --> 03:32.020
Well, I guess you could sort of say that because if you try to say show IP BGP

59
03:32.020 --> 03:33.240
neighbor, whatever

60
03:33.240 --> 03:38.540
received routes and that neighbor doesn't exist or is down, it won't display

61
03:38.540 --> 03:39.560
anything,

62
03:39.560 --> 03:42.720
but that's not really what that command is for.

63
03:42.720 --> 03:48.540
And it's not really what it's for diagnosing for BGP neighbor failures show IP

64
03:48.540 --> 03:49.480
BGP summary

65
03:49.480 --> 03:52.440
would be a much better command.

66
03:52.440 --> 03:56.700
This one unfortunately is not going to show us anything about outbound filters

67
03:56.700 --> 03:57.040
for this

68
03:57.040 --> 04:03.320
one, we would want to do the show IP BGP neighbor address and then advertised
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

68
03:57.040 --> 04:03.320
one, we would want to do the show IP BGP neighbor address and then advertised

69
04:03.320 --> 04:04.320
routes.

70
04:04.320 --> 04:09.000
So that's a different command that we could use to verify our outbound filters.

71
04:09.000 --> 04:14.440
Finally, list the BGP updates received from the neighbor.

72
04:14.440 --> 04:20.020
Now this is an interesting one because this actually tells us exactly what that

73
04:20.020 --> 04:20.680
command

74
04:20.680 --> 04:24.200
does, but that's not the question.

75
04:24.200 --> 04:27.000
The question wasn't what does this command do.

76
04:27.000 --> 04:33.610
The question is what does it allow us to diagnose and what it allows us to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
04:27.000 --> 04:33.610
The question is what does it allow us to diagnose and what it allows us to

77
04:33.610 --> 04:34.600
diagnose

78
04:34.600 --> 04:38.440
is the inbound BGP filters.

79
04:38.440 --> 04:42.160
So we do have commands for these other answers.

80
04:42.160 --> 04:46.740
And the last answer does tell us what the command does, but not what it helps

81
04:46.740 --> 04:48.480
us to diagnose.

82
04:48.480 --> 04:55.730
So inbound BGP filters would be our best answer and therefore our correct

83
04:55.730 --> 04:56.160
answer.

84
04:56.160 --> 05:01.040
So that does conclude this challenge and therefore this skill.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
04:56.160 --> 05:01.040
So that does conclude this challenge and therefore this skill.

85
05:01.040 --> 05:04.450
If you find that you were missing any of the information necessary to complete

86
05:04.450 --> 05:05.720
this challenge,

87
05:05.720 --> 05:10.480
I would encourage you to go back and review the necessary sections above.

88
05:10.480 --> 05:15.450
Otherwise, congratulations on completing troubleshooting IPsec cloud

89
05:15.450 --> 05:16.680
connectivity.

90
05:16.680 --> 05:20.840
I hope this has been informative for you and I'd like to thank you for viewing.

91
05:20.840 --> 05:29.440
[BLANK_AUDIO]