WEBVTT

1
00:00.000 --> 00:08.000
So far in this skill, we have looked at some really good technologies that

2
00:08.000 --> 00:13.700
allow us to have two or more links to our service provider and then do some

3
00:13.700 --> 00:19.680
form of a failover, failback between those links in the event that one of the

4
00:19.680 --> 00:21.000
links stops functioning.

5
00:21.000 --> 00:25.840
The only problem with that is, although it gives us really good redundancy, it

6
00:25.840 --> 00:30.750
doesn't do anything to increase performance, because one of the links is active
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

6
00:25.840 --> 00:30.750
doesn't do anything to increase performance, because one of the links is active

7
00:30.750 --> 00:33.000
and the other one is on standby.

8
00:33.000 --> 00:38.810
Well, what we want to do is to help performance use both of those links at the

9
00:38.810 --> 00:40.000
same time.

10
00:40.000 --> 00:47.780
Do some form of load balancing or load sharing on those links. So in this video

11
00:47.780 --> 00:51.000
, we're going to look at two very specific ways of doing that.

12
00:51.000 --> 00:59.620
First, we're going to replace VRRP with GLBP or Gateway Load Balancing Protocol

13
00:59.620 --> 01:04.920
, so that both of our routers, in this case, routers one and two, can be active
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:59.620 --> 01:04.920
, so that both of our routers, in this case, routers one and two, can be active

14
01:04.920 --> 01:06.000
forwarders.

15
01:06.000 --> 01:10.000
That way, we can, well, load balance between them.

16
01:10.000 --> 01:14.950
Then we're going to change up our design a little bit, and we're going to bring

17
01:14.950 --> 01:20.010
routing a little bit further out towards the customer edge, where we can

18
01:20.010 --> 01:26.000
actually have multiple equal cost paths to get to the destination.

19
01:26.000 --> 01:31.290
So we're going to be doing equal cost multipath thing, and let both links be
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
01:26.000 --> 01:31.290
So we're going to be doing equal cost multipath thing, and let both links be

20
01:31.290 --> 01:34.000
active using our routing protocol.

21
01:34.000 --> 01:41.190
So let's go ahead and jump in. We'll get started with configuring GLBP on

22
01:41.190 --> 01:44.000
routers one and two.

23
01:44.000 --> 01:49.990
So the first thing we need to do before we can configure GLBP is we're going to

24
01:49.990 --> 01:52.000
want to take off VRRP.

25
01:52.000 --> 01:57.810
So we'll just paste this script in here that will take VRRP off the gigabit one

26
01:57.810 --> 01:59.000
interface.

27
01:59.000 --> 02:04.000
If we now say do show VRRP, there will not be any instances of it.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:59.000 --> 02:04.000
If we now say do show VRRP, there will not be any instances of it.

28
02:04.000 --> 02:06.000
We'll do the exact same thing on router two.

29
02:06.000 --> 02:11.000
So router two, we remove it, and we do a show of VRRP.

30
02:11.000 --> 02:17.000
So now VRRP is gone, and the clients have no default gateway.

31
02:17.000 --> 02:21.000
So now what we're going to do is put it in with GLBP instead.

32
02:21.000 --> 02:28.840
So we simply put in GLBP instance one with the virtual IP, almost exactly like

33
02:28.840 --> 02:32.000
we did VRRP, and we'll exit configuration.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

33
02:28.840 --> 02:32.000
we did VRRP, and we'll exit configuration.

34
02:32.000 --> 02:34.000
Let's go to router one.

35
02:34.000 --> 02:36.000
Same thing here.

36
02:36.000 --> 02:38.000
Then we'll do a show GLBP.

37
02:38.000 --> 02:44.070
Now one thing with GLBP, if you look at the information up here at the top,

38
02:44.070 --> 02:49.210
such as the state being standby, there's been one state change with the virtual

39
02:49.210 --> 02:52.000
IP addresses, your hello timers redirect.

40
02:52.000 --> 02:58.470
All of this stuff up at the top has to do with electing the master for the GLBP

41
02:58.470 --> 03:00.000
environment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
03:00.000 --> 03:05.750
What we're more interested in is down here at the bottom, looking at the

43
03:05.750 --> 03:07.000
forwarders.

44
03:07.000 --> 03:09.000
There are currently two forwarders.

45
03:09.000 --> 03:15.000
One of those forwarders is router one, and the other one is router two.

46
03:15.000 --> 03:20.380
Now we can sort of tell which ones which here, because forwarder one is saying

47
03:20.380 --> 03:25.560
that it's learned, which means we learned it from the other side, and we see

48
03:25.560 --> 03:32.000
that the active router for that is 10.10.10.3, which is router two.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
03:25.560 --> 03:32.000
that the active router for that is 10.10.10.3, which is router two.

49
03:32.000 --> 03:38.000
Then we see for forwarder two, this router, meaning router one, is the active,

50
03:38.000 --> 03:42.000
and you see where it says the active is local.

51
03:42.000 --> 03:47.390
If we were to go look at router two, this will be the opposite on the forward

52
03:47.390 --> 03:48.000
ers.

53
03:48.000 --> 03:55.310
For order one, this router is active for and for forwarder two, it's listen. So

54
03:55.310 --> 04:01.210
both of our routers are active forwarders for their respective MAC addresses,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
03:55.310 --> 04:01.210
both of our routers are active forwarders for their respective MAC addresses,

55
04:01.210 --> 04:07.000
which means if we go out to our two workstations, let's start with workstation

56
04:07.000 --> 04:07.000
one.

57
04:07.000 --> 04:14.000
We can see that workstation one is going to router two as its first hop.

58
04:14.000 --> 04:17.000
Let's see what workstation two does.

59
04:17.000 --> 04:22.030
So if we do our trace here on workstation two, notice that this is now going to

60
04:22.030 --> 04:26.000
router one, then the router three, and to the final destination.

61
04:26.000 --> 04:31.560
So this is GLBP load sharing between the two win links, and we see that work
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

61
04:26.000 --> 04:31.560
So this is GLBP load sharing between the two win links, and we see that work

62
04:31.560 --> 04:37.000
station one is going one way, and workstation two is going the other.

63
04:37.000 --> 04:41.000
Next, let's take a look at equal cause multipathting.

64
04:41.000 --> 04:45.790
So for this, we're going to be changing things around a bit. So what we're

65
04:45.790 --> 04:50.140
going to be doing is we're going to be bringing up OSPF on the link between

66
04:50.140 --> 04:56.030
router one and switch one, as well as the link between router two and switch

67
04:56.030 --> 04:57.000
one.

68
04:57.000 --> 05:02.580
And we're going to move our default gateway. So the gateway for the 10 dot 10
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

68
04:57.000 --> 05:02.580
And we're going to move our default gateway. So the gateway for the 10 dot 10

69
05:02.580 --> 05:08.310
dot 10 dot zero slash 24, which is currently the dot one that we're using with

70
05:08.310 --> 05:09.000
GLBP.

71
05:09.000 --> 05:13.000
We're actually going to move that over here to the switch.

72
05:13.000 --> 05:17.080
So the switch is actually going to become the default gateway, and the switch

73
05:17.080 --> 05:23.280
is going to have equal paths to get to the destination over here of 10 dot 10

74
05:23.280 --> 05:26.000
dot 20 dot zero slash 24.

75
05:26.000 --> 05:29.230
So the things that we're going to change, we of course have to turn on IP

76
05:29.230 --> 05:33.440
routing on the switch we're going to have to turn on OSPF, and we're going to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
05:29.230 --> 05:33.440
routing on the switch we're going to have to turn on OSPF, and we're going to

77
05:33.440 --> 05:40.000
have to change both of these interfaces to be layer three interfaces and give

78
05:40.000 --> 05:41.000
them some IP addresses.

79
05:41.000 --> 05:45.740
Now this is going to be some fairly basic configuration here. What we really

80
05:45.740 --> 05:50.740
want to do is look at the results. So I'm just going to use a script on router

81
05:50.740 --> 05:53.000
one router two and switch one.

82
05:53.000 --> 05:57.890
I'll include those scripts below this video, so you can change your environment

83
05:57.890 --> 06:00.000
to match what we're doing here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
06:00.000 --> 06:05.410
So let's jump in and put those scripts on our three devices. So first on router

85
06:05.410 --> 06:06.000
one.

86
06:06.000 --> 06:11.390
So as you can see what we're doing here is we're taking GLBP off the interface,

87
06:11.390 --> 06:15.660
changing the IP address to be a different subnet. We're just going to use 172

88
06:15.660 --> 06:22.000
dot 16 dot 11 here, and we're enabling OSPF on this link.

89
06:22.000 --> 06:32.490
We'll do the same thing here on router two. Again, it's of course a different
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

89
06:22.000 --> 06:32.490
We'll do the same thing here on router two. Again, it's of course a different

90
06:32.490 --> 06:34.000
subnet here we're using 172 dot 16 dot 12 dot two. Now let's go do switch one.

91
06:34.000 --> 06:38.000
Switch one has a little more going on so we'll do this one in pieces.

92
06:38.000 --> 06:42.000
First we'll configure OSPF with its router ID.

93
06:42.000 --> 06:47.810
Next, we'll configure its two interfaces. First we do no switch port to turn

94
06:47.810 --> 06:50.000
them into layer three interfaces.

95
06:50.000 --> 06:55.360
Then we put the IP addresses on them and we configure OSPF for area zero

96
06:55.360 --> 07:01.370
network type point to point and we change our hello and dead intervals to match
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
06:55.360 --> 07:01.370
network type point to point and we change our hello and dead intervals to match

97
07:01.370 --> 07:03.000
routers one and two.

98
07:03.000 --> 07:09.060
Finally, we'll create the SVI that's going to be needed as the default gateway

99
07:09.060 --> 07:14.920
will bring that into OSPF and will make it a passive interface and OSPF since

100
07:14.920 --> 07:17.000
there's no neighbors.

101
07:17.000 --> 07:21.850
There's only a workstation out that interface. If all of this has worked

102
07:21.850 --> 07:23.000
correctly.

103
07:23.000 --> 07:33.380
We can do a show IP OSPF neighbors. Here we see that we are in fact neighbors
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
07:23.000 --> 07:33.380
We can do a show IP OSPF neighbors. Here we see that we are in fact neighbors

104
07:33.380 --> 07:35.980
with router one and router two, and most importantly, if we do a show IP route

105
07:35.980 --> 07:42.450
for OSPF, we see that towards the destination 10 dot 10 dot 20 dot zero slash

106
07:42.450 --> 07:43.000
24.

107
07:43.000 --> 07:49.220
It is in fact load sharing with the next top of 11 dot one for router one and

108
07:49.220 --> 07:52.000
12 dot two for router two.

109
07:52.000 --> 07:57.830
If we look at more detailed information on that route, we see that each next

110
07:57.830 --> 08:03.980
hop is actually getting a traffic share count of one, meaning it's equally load
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

110
07:57.830 --> 08:03.980
hop is actually getting a traffic share count of one, meaning it's equally load

111
08:03.980 --> 08:06.000
sharing between the two.

112
08:06.000 --> 08:13.700
If we look at a show IP protocol specifically for OSPF, we can see right here

113
08:13.700 --> 08:21.000
iOS will load share up to a maximum of four paths for OSPF by default.

114
08:21.000 --> 08:25.780
So in order to do equal cost load balancing, we actually don't have to

115
08:25.780 --> 08:30.000
configure anything as long as we have four paths or less.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

116
08:30.000 --> 08:34.440
Now of course, let's verify our load sharing let's go back over to workstation

117
08:34.440 --> 08:35.000
one.

118
08:35.000 --> 08:39.000
So here on workstation one will do our trace again.

119
08:39.000 --> 08:42.900
Here we're going to be looking of course for the second hop, because the first

120
08:42.900 --> 08:45.000
hop is of course going to be the switch.

121
08:45.000 --> 08:50.320
So the second hop in this case is 11 dot one, which we know is router one. Let

122
08:50.320 --> 08:53.000
's look at workstation two.

123
08:53.000 --> 08:59.350
On workstation two, we see that the second hop is 12 dot two, which means we

124
08:59.350 --> 09:05.040
are now load sharing across the two links going out to the cloud using our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
08:59.350 --> 09:05.040
are now load sharing across the two links going out to the cloud using our

125
09:05.040 --> 09:07.000
routing protocol.

126
09:07.000 --> 09:12.810
So in this video, we saw how to increase our performance a bit here by not

127
09:12.810 --> 09:19.160
having one link be active and the other be inactive, but rather to have both

128
09:19.160 --> 09:26.160
links forwarding traffic using either GLBP on the first hop, or extending our

129
09:26.160 --> 09:31.000
routing protocol out a little bit further and letting it do equal cost multi
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

129
09:26.160 --> 09:31.000
routing protocol out a little bit further and letting it do equal cost multi

130
09:31.000 --> 09:31.000
path thing.

131
09:31.000 --> 09:36.460
But either way, we ended up with both links forwarding traffic towards the

132
09:36.460 --> 09:39.000
cloud on behalf of our clients.

133
09:39.000 --> 09:44.000
So that's everything that we need to cover in this two part skill.

134
09:44.000 --> 09:48.000
So that being said, it's time to do our final challenge.

135
09:48.000 --> 09:53.000
So go ahead and give that a shot, and I'll see you on the other side.