1
00:00:00,000 --> 00:00:03,437
[AUDIO LOGO]

2
00:00:03,437 --> 00:00:08,840

3
00:00:08,840 --> 00:00:12,360
Congratulations on
completing another skill.

4
00:00:12,360 --> 00:00:17,010
Now it's time for a review
in the form of a quiz.

5
00:00:17,010 --> 00:00:21,340
So let's go ahead and jump
in with our first question.

6
00:00:21,340 --> 00:00:23,790
Which of the
following are methods

7
00:00:23,790 --> 00:00:25,800
to set the weight on the router?

8
00:00:25,800 --> 00:00:31,880

9
00:00:31,880 --> 00:00:36,530
So let's go down our list here,
and see which ones are viable.

10
00:00:36,530 --> 00:00:40,450
So answer number one
is to set it globally

11
00:00:40,450 --> 00:00:43,000
with a policy route.

12
00:00:43,000 --> 00:00:45,680
There's actually two
problems with this statement.

13
00:00:45,680 --> 00:00:48,520
The first is that
it says globally

14
00:00:48,520 --> 00:00:51,460
and we don't set
this globally, and it

15
00:00:51,460 --> 00:00:55,840
says with a policy
route, which possibly

16
00:00:55,840 --> 00:01:01,460
is referring to PBR or policy
based routing, maybe it's not.

17
00:01:01,460 --> 00:01:05,180
But policy route is
not really a thing.

18
00:01:05,180 --> 00:01:08,810
So 1 would be an
incorrect answer.

19
00:01:08,810 --> 00:01:14,890
Number 2 is to set it directly
on the neighbor configuration.

20
00:01:14,890 --> 00:01:17,740
And we actually saw when we
went through our demonstration,

21
00:01:17,740 --> 00:01:23,500
that that is possible, so 2
definitely a correct answer.

22
00:01:23,500 --> 00:01:27,010
Number 3 and 4, If we
look at both of these,

23
00:01:27,010 --> 00:01:28,670
they're very similar.

24
00:01:28,670 --> 00:01:33,100
It's just one of them is on an
outbound route map or policy

25
00:01:33,100 --> 00:01:36,130
and the other one is inbound.

26
00:01:36,130 --> 00:01:39,730
Well, remember that we are
talking about the weight

27
00:01:39,730 --> 00:01:45,220
attribute here, and the weight
attribute is only local.

28
00:01:45,220 --> 00:01:48,220
There would be no
reason at all to set

29
00:01:48,220 --> 00:01:51,640
this on an outbound
route map because it

30
00:01:51,640 --> 00:01:53,920
doesn't get sent to neighbors.

31
00:01:53,920 --> 00:01:57,850
So the correct answer here
would, of course, be 4.

32
00:01:57,850 --> 00:02:01,360
We could set it in an
inbound route map or route

33
00:02:01,360 --> 00:02:04,720
policy, just not outbound.

34
00:02:04,720 --> 00:02:10,310
Therefore, our two correct
answers here are 2 and 4.

35
00:02:10,310 --> 00:02:12,090
Next question.

36
00:02:12,090 --> 00:02:17,180
Name any advantages to
using soft reconfiguration

37
00:02:17,180 --> 00:02:18,965
over route-refresh?

38
00:02:18,965 --> 00:02:25,050

39
00:02:25,050 --> 00:02:27,850
So once again, let's
go down our list.

40
00:02:27,850 --> 00:02:32,940
Number 1 says that it has
an unaltered BGP table that

41
00:02:32,940 --> 00:02:35,310
can be useful for
troubleshooting,

42
00:02:35,310 --> 00:02:38,430
and we did discuss
that, that is true.

43
00:02:38,430 --> 00:02:42,570
Having that unaltered copy of
the BGP table from the neighbor

44
00:02:42,570 --> 00:02:46,350
can be very, very helpful
again, particularly

45
00:02:46,350 --> 00:02:48,840
for that troubleshooting aspect.

46
00:02:48,840 --> 00:02:54,450
Number 2, soft reconfiguration
is the default behavior.

47
00:02:54,450 --> 00:02:56,710
This is definitely not true.

48
00:02:56,710 --> 00:03:01,110
We actually saw that on
both iOS XE and iOS XR,

49
00:03:01,110 --> 00:03:06,060
they will both default actually
to doing route-refresh.

50
00:03:06,060 --> 00:03:11,650
Number 3 soft
reconfiguration is faster.

51
00:03:11,650 --> 00:03:14,400
Well, it may be an
incredibly small maybe even

52
00:03:14,400 --> 00:03:16,120
unmeasurable advantage.

53
00:03:16,120 --> 00:03:20,310
However, it is just doing
a local replay out of RAM,

54
00:03:20,310 --> 00:03:23,850
therefore, it would
be faster than getting

55
00:03:23,850 --> 00:03:26,580
the information resent
over the network

56
00:03:26,580 --> 00:03:30,030
again, even though it
may not be measurable.

57
00:03:30,030 --> 00:03:37,030
Number 4 soft reconfiguration
uses less bandwidth overall.

58
00:03:37,030 --> 00:03:40,500
Now keep in mind we're
talking about bandwidth here.

59
00:03:40,500 --> 00:03:43,320
Now either way,
the prefixes need

60
00:03:43,320 --> 00:03:45,090
to be sent from the neighbor.

61
00:03:45,090 --> 00:03:47,370
But what this is
referring to, is

62
00:03:47,370 --> 00:03:50,520
when you actually do the
soft reconfiguration or route

63
00:03:50,520 --> 00:03:51,540
refresh.

64
00:03:51,540 --> 00:03:53,880
This is going to
take less bandwidth,

65
00:03:53,880 --> 00:03:56,790
since it's a local replay.

66
00:03:56,790 --> 00:04:01,290
And, of course, 5 is going for
the whole less memory concept.

67
00:04:01,290 --> 00:04:04,050
Well, it's not going to
take less memory because we

68
00:04:04,050 --> 00:04:06,510
are storing that local copy.

69
00:04:06,510 --> 00:04:09,580
So 5 would also be incorrect.

70
00:04:09,580 --> 00:04:13,270
It actually takes
more RAM or memory,

71
00:04:13,270 --> 00:04:17,950
so our correct answers
here are 1, 3, and 4.

72
00:04:17,950 --> 00:04:22,330
Final question, which of
the following is correct?

73
00:04:22,330 --> 00:04:28,320

74
00:04:28,320 --> 00:04:31,850
So basically, if we analyze
our answers, two of them

75
00:04:31,850 --> 00:04:35,210
have to do with local
preference and two of them

76
00:04:35,210 --> 00:04:36,770
have to do with weight.

77
00:04:36,770 --> 00:04:41,300
And both of them have to do
with whether it's the entire AS

78
00:04:41,300 --> 00:04:43,980
or only the local router.

79
00:04:43,980 --> 00:04:46,850
So let's go down our
list then, and figure out

80
00:04:46,850 --> 00:04:49,140
which one is actually correct.

81
00:04:49,140 --> 00:04:51,620
So number one is saying
that the local preference

82
00:04:51,620 --> 00:04:54,050
can affect the entire AS.

83
00:04:54,050 --> 00:04:57,950
This is definitely true,
because local preference

84
00:04:57,950 --> 00:05:01,020
gets sent in our BGP updates.

85
00:05:01,020 --> 00:05:04,160
So that would mean that
2 is not going to be true

86
00:05:04,160 --> 00:05:06,530
since they're opposites.

87
00:05:06,530 --> 00:05:11,330
Number 3, weight can
affect the entire AS.

88
00:05:11,330 --> 00:05:14,610
Again, weight does not
get sent in BGP updates,

89
00:05:14,610 --> 00:05:18,830
so it cannot be used to
effect the entire AS.

90
00:05:18,830 --> 00:05:21,080
Once again them
being opposites, that

91
00:05:21,080 --> 00:05:23,720
would make 4 correct
for weight, it

92
00:05:23,720 --> 00:05:26,370
can only affect
the local router.

93
00:05:26,370 --> 00:05:31,230
So that makes 1 and 4
our correct answers.

94
00:05:31,230 --> 00:05:33,340
And that concludes this quiz.

95
00:05:33,340 --> 00:05:36,360
If you find that you are missing
any of the information needed

96
00:05:36,360 --> 00:05:38,520
to answer these
questions, I would

97
00:05:38,520 --> 00:05:41,340
encourage you to go back
and review the reference

98
00:05:41,340 --> 00:05:44,200
sources on each question.

99
00:05:44,200 --> 00:05:47,910
Otherwise, congratulations
on completing Implementing

100
00:05:47,910 --> 00:05:50,860
Outbound BGP Path Selection.

101
00:05:50,860 --> 00:05:53,280
I hope this has been
informative for you,

102
00:05:53,280 --> 00:05:56,420
and I'd like to thank
you for viewing.

103
00:05:56,420 --> 00:05:59,467