WEBVTT

1
00:00.000 --> 00:07.930
So, for this challenge, the first thing we need to do is set our lab back to

2
00:07.930 --> 00:09.200
the defaults

3
00:09.200 --> 00:12.480
that it was at the beginning of this skill.

4
00:12.480 --> 00:16.520
We're going to be starting with our baseline configuration.

5
00:16.520 --> 00:19.600
Then we're given three tasks to perform.

6
00:19.600 --> 00:22.160
So let's just go through them in order.

7
00:22.160 --> 00:29.800
The first one is to configure a first hop redundancy protocol between R1 and R2

8
00:29.800 --> 00:29.960
, so

9
00:29.960 --> 00:34.920
much that both are active forwarders on your network.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:29.960 --> 00:34.920
much that both are active forwarders on your network.

10
00:34.920 --> 00:41.020
Well if we start with a show run for interface Gigabit 1, we see that in our

11
00:41.020 --> 00:42.880
baseline configuration,

12
00:42.880 --> 00:49.480
Gigabit 1 is actually running VRRP, which of course cannot be active active.

13
00:49.480 --> 00:56.640
So all we need to do for this task is replace VRRP with GLBP.

14
00:56.640 --> 01:01.280
It doesn't give us any specifics about how GLBP should be configured, so we can
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:56.640 --> 01:01.280
It doesn't give us any specifics about how GLBP should be configured, so we can

15
01:01.280 --> 01:01.880
just sort

16
01:01.880 --> 01:04.480
of configure it generic.

17
01:04.480 --> 01:07.600
So here we'll simply put in our configuration.

18
01:07.600 --> 01:12.320
So we simply turn off VRRP and enable GLBP.

19
01:12.320 --> 01:16.450
Now if we do a show GLBP right now, we're not going to see a whole lot because

20
01:16.450 --> 01:16.800
there's

21
01:16.800 --> 01:20.720
only going to be one forwarder so far, the local router.

22
01:20.720 --> 01:26.240
Now it hasn't actually elected itself as the local router yet, but it will.

23
01:26.240 --> 01:31.380
We do the exact same configuration on router 2, and if we let this sit for just
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
01:26.240 --> 01:31.380
We do the exact same configuration on router 2, and if we let this sit for just

24
01:31.380 --> 01:32.200
a second,

25
01:32.200 --> 01:35.800
we should see both forwarders configured correctly.

26
01:35.800 --> 01:40.240
So if we look now at our forwarders, we see that we're now aware of both

27
01:40.240 --> 01:41.360
forwarders.

28
01:41.360 --> 01:47.500
Router 2 in this case is the active forwarder for forwarder 2, and it's in

29
01:47.500 --> 01:48.640
listen mode for

30
01:48.640 --> 01:54.320
forwarder 1 because router 1 is the active for forwarder 1.

31
01:54.320 --> 01:57.720
So that's GLBP working correctly.

32
01:57.720 --> 02:04.190
The next thing we're to configure is OSPF on both router 1 and router 2 should
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:57.720 --> 02:04.190
The next thing we're to configure is OSPF on both router 1 and router 2 should

33
02:04.190 --> 02:04.880
detect

34
02:04.880 --> 02:10.800
a communication issue across the WAN in 150 milliseconds.

35
02:10.800 --> 02:17.190
So this is going to clearly involve using bi-directional forwarding detection

36
02:17.190 --> 02:18.040
or BFD.

37
02:18.040 --> 02:23.390
Now routers 3 and 4 are already configured for BFD, so all we have to do is

38
02:23.390 --> 02:24.240
configure

39
02:24.240 --> 02:29.780
router 1 and router 2, and so we can see this coming up and such, we'll go

40
02:29.780 --> 02:30.440
ahead and turn
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
02:29.780 --> 02:30.440
ahead and turn

41
02:30.440 --> 02:35.600
on logging for the console as well since that's also disabled in our baseline

42
02:35.600 --> 02:36.920
configuration.

43
02:36.920 --> 02:40.480
So since we're already here on router 2, we'll just start here.

44
02:40.480 --> 02:44.240
So once again, we'll simply paste in our configuration.

45
02:44.240 --> 02:49.730
We see BFD going up here with router 4 in this case because this is router 2,

46
02:49.730 --> 02:50.440
and this

47
02:50.440 --> 02:56.280
is a reminder here, all we really set to make the 150 milliseconds work is we

48
02:56.280 --> 02:57.280
set the interval

49
02:57.280 --> 03:00.600
to 50 and the multiplier to 3.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
02:57.280 --> 03:00.600
to 50 and the multiplier to 3.

50
03:00.600 --> 03:05.310
So that means that BFD will detect a failure in 150 milliseconds, and then of

51
03:05.310 --> 03:05.960
course we

52
03:05.960 --> 03:09.960
had to enable this under the OSPF process.

53
03:09.960 --> 03:13.080
Exact same configuration on router 1.

54
03:13.080 --> 03:18.900
So if we put the configuration on router 1, we see BFD coming up with router 3

55
03:18.900 --> 03:19.800
as well.

56
03:19.800 --> 03:25.960
So now we have BFD enabled to detect a failure in 150 milliseconds.

57
03:25.960 --> 03:32.810
Our final step is to configure R1 and R2 to generate a syslog message in the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
03:25.960 --> 03:32.810
Our final step is to configure R1 and R2 to generate a syslog message in the

58
03:32.810 --> 03:33.600
event that

59
03:33.600 --> 03:37.120
pings start failing across the WAN link.

60
03:37.120 --> 03:40.280
So this is actually going to require two moving parts.

61
03:40.280 --> 03:46.190
We're going to need an IPSLA monitor for ping, and we're going to need an EEM

62
03:46.190 --> 03:46.840
script

63
03:46.840 --> 03:49.720
to generate the syslog message.

64
03:49.720 --> 03:51.920
So let's go ahead and put these in.

65
03:51.920 --> 03:56.320
First, here on router 1, we create the IPSLA.

66
03:56.320 --> 03:58.720
It's for an ICMP echo.

67
03:58.720 --> 04:02.530
The challenge didn't really tell us what timers to use, so I just did a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
03:58.720 --> 04:02.530
The challenge didn't really tell us what timers to use, so I just did a

68
04:02.530 --> 04:03.320
threshold of

69
04:03.320 --> 04:07.840
1000, a timeout of 1000, and a frequency of 1.

70
04:07.840 --> 04:13.610
Then don't forget that we have to set up our configuration reactions so that E

71
04:13.610 --> 04:13.960
EM can

72
04:13.960 --> 04:15.960
actually monitor this.

73
04:15.960 --> 04:20.510
Now as you can see, some of these commands get a little bit long, so I will put

74
04:20.510 --> 04:20.800
router

75
04:20.800 --> 04:27.840
1's configuration down below, so you have it as a reference for the solution.

76
04:27.840 --> 04:30.920
Next we're simply going to put in the EEM script.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
04:27.840 --> 04:30.920
Next we're simply going to put in the EEM script.

77
04:30.920 --> 04:35.130
Once again, some of these commands get long, so reference the text below to see

78
04:35.130 --> 04:35.680
the full

79
04:35.680 --> 04:42.060
script, but this is going to create an event manager applet called WAN monitor,

80
04:42.060 --> 04:42.520
and in

81
04:42.520 --> 04:49.520
the event that IPSLA has a reaction type of timeout to our pings, it's going to

82
04:49.520 --> 04:50.320
trigger

83
04:50.320 --> 04:54.320
this syslog message with a priority of warnings.

84
04:54.320 --> 05:00.100
Again, the task didn't say what level to use here, so whatever level you use is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
04:54.320 --> 05:00.100
Again, the task didn't say what level to use here, so whatever level you use is

85
05:00.100 --> 05:00.880
fine.

86
05:00.880 --> 05:06.080
It also didn't specify a message, so we just put a message in here.

87
05:06.080 --> 05:11.790
Let's exit configuration, and let's test to see if this works by shutting down

88
05:11.790 --> 05:12.120
the

89
05:12.120 --> 05:15.400
WAN interface on router 3.

90
05:15.400 --> 05:19.520
So we'll shut this down, we'll go back over to router 1.

91
05:19.520 --> 05:23.930
Now of course we see BFD and OSPF going down here, but the important thing is

92
05:23.930 --> 05:24.440
right here

93
05:24.440 --> 05:30.040
at the bottom where we see the WAN monitor sending the syslog message that the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
05:24.440 --> 05:30.040
at the bottom where we see the WAN monitor sending the syslog message that the

94
05:30.040 --> 05:30.720
WAN link

95
05:30.720 --> 05:35.080
is dropping pings exactly as we configured it to do.

96
05:35.080 --> 05:40.050
Now I didn't show the configuration on router 2 here, it would be exactly the

97
05:40.050 --> 05:40.640
same except

98
05:40.640 --> 05:47.000
for the IP address that the IPSLA monitor is actually trying to ping.

99
05:47.000 --> 05:51.840
But otherwise we solved all three sections of this challenge.

100
05:51.840 --> 05:54.480
So that does complete this challenge.

101
05:54.480 --> 05:58.100
If you find that you were unable to perform any parts of this, I would

102
05:58.100 --> 05:58.920
encourage you to

103
05:58.920 --> 06:04.120
go back and review those sections throughout this skill.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
05:58.920 --> 06:04.120
go back and review those sections throughout this skill.

104
06:04.120 --> 06:09.480
Otherwise congratulations on completing performance and redundancy technologies

105
06:09.480 --> 06:10.120
, I hope this

106
06:10.120 --> 06:13.800
This has been informative for you, and I'd like to thank you for viewing.

107
06:13.800 --> 06:21.360
[BLANK_AUDIO]