WEBVTT

1
00:00.000 --> 00:04.830
In the previous video we configured HSRP, a proprietary first hopper density

2
00:04.830 --> 00:05.760
protocol from Cisco,

3
00:05.760 --> 00:09.720
and in this video we're going to focus on the configuration verification of VR

4
00:09.720 --> 00:10.800
RP, which is an

5
00:10.800 --> 00:17.060
open standard. Now, the actual logic is very, very similar between VRRP and HS

6
00:17.060 --> 00:18.240
RP, including we

7
00:18.240 --> 00:22.850
are going to use group numbers for VRRP. We are going to have priorities that

8
00:22.850 --> 00:24.080
are used to determine

9
00:24.080 --> 00:27.790
which is going to be the master and which is going to be the backup. And we

10
00:27.790 --> 00:28.880
also have the concept

11
00:28.880 --> 00:33.150
of preempt. Now, by default, the preempt option is on with VRRP. So if you want
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:28.880 --> 00:33.150
of preempt. Now, by default, the preempt option is on with VRRP. So if you want

12
00:33.150 --> 00:33.920
to turn it off,

13
00:33.920 --> 00:39.160
you can, but preempt is on by default. That means if gig 1, 0 is configured for

14
00:39.160 --> 00:39.920
VRRP with a

15
00:39.920 --> 00:45.580
priority of 102, and then we configured our one with a priority of 103, because

16
00:45.580 --> 00:46.480
preempt is on by

17
00:46.480 --> 00:50.680
default, our one would assume the role of the master and the gig 1, 0 interface

18
00:50.680 --> 00:52.000
here over on R2

19
00:52.000 --> 00:55.920
would become the backup. And the syntax for implementing VRRP is virtually

20
00:55.920 --> 00:57.120
identical to how we would

21
00:57.120 --> 01:01.710
implement HSRP except we're going to use the keyword VRRP instead of the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
00:57.120 --> 01:01.710
implement HSRP except we're going to use the keyword VRRP instead of the

22
01:01.710 --> 01:03.520
keyword standby. So with that

23
01:03.520 --> 01:08.140
in mind, let's head back to the lab and let's remove the configurations on gig

24
01:08.140 --> 01:09.600
0, 0 here and on

25
01:09.600 --> 01:14.220
gig 1, 0 here on R2. And let's replace them with fresh IP addresses and then we

26
01:14.220 --> 01:15.680
'll also add VRRP

27
01:15.680 --> 01:20.270
on top of it. And then once that's done, we can test it from PC12. And here we

28
01:20.270 --> 01:22.400
go. So let's go to R1

29
01:22.400 --> 01:27.670
first and in my notepad document, I'm going to scroll down to the VRRP section,

30
01:27.670 --> 01:28.640
which is right here.

31
01:28.640 --> 01:32.210
So in R1, we're going to go into configuration mode and default the interface
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:28.640 --> 01:32.210
So in R1, we're going to go into configuration mode and default the interface

32
01:32.210 --> 01:33.040
gig 0, 0 is just

33
01:33.040 --> 01:36.220
to wipe out anything that was there. And then we'll go into interface config,

34
01:36.220 --> 01:37.200
put back its IP

35
01:37.200 --> 01:42.940
address of 10, 12, 0, 1. And then we're going to use VRRP group 1, specify the

36
01:42.940 --> 01:44.080
IP address of 10,

37
01:44.080 --> 01:49.070
12, 0, 99, and also a priority of 99 for that group for the interface over on R

38
01:49.070 --> 01:50.080
1. And then for

39
01:50.080 --> 01:53.960
R2, similar treatment, except we'll go to the appropriate interface of gig 1, 0

40
01:53.960 --> 01:54.400
on R2,

41
01:54.400 --> 01:59.360
and then put back its IP address of 10, 12, 0, 2, and then set up VRRP group 1

42
01:59.360 --> 02:00.320
with the same virtual
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:59.360 --> 02:00.320
with the same virtual

43
02:00.320 --> 02:05.200
IP address. But this time we're going to give a priority of 105. So the default

44
02:05.200 --> 02:06.160
priority is 100,

45
02:06.160 --> 02:10.390
so 105 will be higher than the default. It'll also be higher than R1. And

46
02:10.390 --> 02:11.280
because preempt is on

47
02:11.280 --> 02:15.100
by default, once we configure R2, it should take over the master role. So to

48
02:15.100 --> 02:15.840
start off, let's go ahead

49
02:15.840 --> 02:19.990
and copy the config here for R1. We'll copy that into my buffer, go to the

50
02:19.990 --> 02:21.840
right router, which is R1.

51
02:21.840 --> 02:24.760
We'll paste that in and then we'll give it a moment. Oh, and here it has a

52
02:24.760 --> 02:25.600
duplicate address

53
02:25.600 --> 02:30.110
in this because R2 is still acting as the, as the, it's just RP router over
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
02:25.600 --> 02:30.110
in this because R2 is still acting as the, as the, it's just RP router over

54
02:30.110 --> 02:33.040
there for its interface,

55
02:33.040 --> 02:37.280
gig 1, 0. So let's actually go over to R2 and let me just default the interface

56
02:37.280 --> 02:38.480
for gig 1, 0,

57
02:38.480 --> 02:43.130
over on R2. And that way it won't complain. So we'll go to R2 right click. We

58
02:43.130 --> 02:44.480
'll default the interface

59
02:44.480 --> 02:48.080
fantastic. And then we'll go back to R1 and I'm going to put R1's configuration

60
02:48.080 --> 02:49.280
back in. So right click

61
02:49.280 --> 02:55.680
copy, go to R1, paste it in. And here we go. So VRP is going from init to

62
02:55.680 --> 02:56.880
backup. And then it went

63
02:56.880 --> 03:01.520
from backup to master as shown right there. So if we do a show, VRP and press
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:56.880 --> 03:01.520
from backup to master as shown right there. So if we do a show, VRP and press

64
03:01.520 --> 03:02.640
enter is showing that

65
03:02.640 --> 03:06.250
this router, router one is currently the master. There's the virtual IP address

66
03:06.250 --> 03:07.280
. There's the virtual

67
03:07.280 --> 03:11.380
MAC address, ending in 010. Preemptions enabled by default. There's the

68
03:11.380 --> 03:12.960
priority that we manually set.

69
03:12.960 --> 03:17.760
And the master router is 10.12.0.1. That's us. That's R1's interface address.

70
03:17.760 --> 03:19.360
And its priority is 99.

71
03:19.360 --> 03:24.000
So if we were to go back to PC12 and here on PC12's do a show, ARP. So if we

72
03:24.000 --> 03:24.480
look at the ARP

73
03:24.480 --> 03:27.800
cache, it has the correct MAC address. So that's timing out. But will we also

74
03:27.800 --> 03:28.960
just do a nice clean slate,

75
03:28.960 --> 03:32.490
we could do a clear ARP, press enter. And then let's do a show, ARP just to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

75
03:28.960 --> 03:32.490
we could do a clear ARP, press enter. And then let's do a show, ARP just to

76
03:32.490 --> 03:33.120
verify the ARP

77
03:33.120 --> 03:38.630
cache is empty. And let's say ping to 4.4.4.4. Now before we press enter, that

78
03:38.630 --> 03:40.320
should cause PC12

79
03:40.320 --> 03:44.040
to realize, oh, I'm trying to reach a network that's not local. I need to know

80
03:44.040 --> 03:44.560
the layer 2

81
03:44.560 --> 03:48.410
address of my default gateway, which is .99. So I can go ahead and learn the

82
03:48.410 --> 03:49.680
layer 2 address for that.

83
03:49.680 --> 03:52.810
And then forward the frame at layer 2 to my default gateway. And then my

84
03:52.810 --> 03:53.600
default gateway can make

85
03:53.600 --> 03:58.800
a routing decision. So at the moment, R1 is the only router configured with VRP

86
03:58.800 --> 03:59.200
to support

87
03:59.200 --> 04:04.140
that IP address. And that is working great. And if we go back to the switch and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
03:59.200 --> 04:04.140
that IP address. And that is working great. And if we go back to the switch and

88
04:04.140 --> 04:05.120
here on the switch,

89
04:05.120 --> 04:10.080
if we do a show MAC address table, there's that address ending in 0101 that's

90
04:10.080 --> 04:10.880
associated with port

91
04:10.880 --> 04:15.010
gig 01. And that's the connection that goes down to R1. Now let's go ahead and

92
04:15.010 --> 04:16.160
configure R2.

93
04:16.160 --> 04:19.470
It's gig 1 0 when we're placing when we do that. And when we give it a higher

94
04:19.470 --> 04:20.400
priority, it will

95
04:20.400 --> 04:23.700
then become the master router for the segment. And the switch should believe

96
04:23.700 --> 04:24.560
that same MAC address

97
04:24.560 --> 04:29.020
ending in 0101 is reachable off gig 02. And that's because R2 when it becomes

98
04:29.020 --> 04:29.520
the master

99
04:29.520 --> 04:32.520
in gig 1 0 is going to send some frames into the network. And the source
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

99
04:29.520 --> 04:32.520
in gig 1 0 is going to send some frames into the network. And the source

100
04:32.520 --> 04:33.280
addresses are going to

101
04:33.280 --> 04:38.060
have that layer 2 address ending in 0101. So let's go to R2. Let's go to our

102
04:38.060 --> 04:39.360
text document. And here's

103
04:39.360 --> 04:42.640
what we'll configure. We're going to default the interface, give it its IP

104
04:42.640 --> 04:43.520
address back, and then

105
04:43.520 --> 04:48.780
set up the virtual IP address of 10.12.0.99. And set up a priority that's 105.

106
04:48.780 --> 04:49.840
So we'll copy that,

107
04:49.840 --> 04:54.380
put it in my buffer. We'll go to R2, right click, and away we go. All right, so

108
04:54.380 --> 04:54.960
it went from

109
04:54.960 --> 04:59.540
a knit to backup. It should go from backup to master right there. And now R2 is

110
04:59.540 --> 05:00.720
the master router for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

110
04:59.540 --> 05:00.720
the master router for

111
05:00.720 --> 05:06.560
VRRP group number one. So if we did a show VRRP here in press dinner, here

112
05:06.560 --> 05:08.080
shows the state is master,

113
05:08.080 --> 05:11.710
there's our virtual IP address, there's the virtual MAC address. And here it

114
05:11.710 --> 05:12.560
confirms that the

115
05:12.560 --> 05:17.320
master router is 10.12.02. That's us locally. And our priority is 105. So if we

116
05:17.320 --> 05:18.000
went back to the

117
05:18.000 --> 05:22.210
switch and this confirm what port we're connected to. So R2 on its gig 1 0

118
05:22.210 --> 05:23.440
interfaces connected to

119
05:23.440 --> 05:27.260
gig 0 slash 2 on the switch. So if we went into the switch and hit the up your

120
05:27.260 --> 05:28.080
key into the show

121
05:28.080 --> 05:31.980
MAC address table, check it out. That MAC address ending in 0101 is now
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

121
05:28.080 --> 05:31.980
MAC address table, check it out. That MAC address ending in 0101 is now

122
05:31.980 --> 05:34.080
associated with gig 0 slash 2.

123
05:34.080 --> 05:38.400
So if we went back to PC 12 and still a quick show ARP. So it still believes

124
05:38.400 --> 05:39.600
the MAC address associated

125
05:39.600 --> 05:43.060
with default gateway is 0101. That's great, great, great. So let's do a ping to

126
05:43.060 --> 05:46.000
4.4.4.4. No worries.

127
05:46.000 --> 05:50.280
And that's R2 that's providing that default gateway functionality. So if we did

128
05:50.280 --> 05:52.560
a trace to 4.4.4.4,

129
05:52.560 --> 05:58.180
that would confirm our first top is R2 and then R3 and then onto R4. So if we

130
05:58.180 --> 05:59.200
went to R2 and let's

131
05:59.200 --> 06:03.150
confirm the interface we're dealing with. So on R2, if we shut down gig 1 slash
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

131
05:59.200 --> 06:03.150
confirm the interface we're dealing with. So on R2, if we shut down gig 1 slash

132
06:03.150 --> 06:04.160
0. So we'll do that.

133
06:04.160 --> 06:08.450
We'll go into configuration mode, interface gig 1 slash 0. And let's say shut

134
06:08.450 --> 06:09.680
down and press center.

135
06:09.680 --> 06:12.290
Or we're going to lose the OSPF neighbor ship. But check this out. If you go

136
06:12.290 --> 06:13.600
back to PC 12,

137
06:13.600 --> 06:18.510
it still has, if we look at the ARP cache here, it still believes that .99 is

138
06:18.510 --> 06:19.440
associated with that

139
06:19.440 --> 06:23.060
same layer to address. But this time it's going to be R1 that's supporting it.

140
06:23.060 --> 06:24.000
So if we go to R1

141
06:24.000 --> 06:28.000
and we do a show and right there it has the VRRP message went from backup to

142
06:28.000 --> 06:29.520
master. So we do a show

143
06:29.520 --> 06:33.690
VRRP in press center. It's now showing that router 1 is the master along with
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

143
06:29.520 --> 06:33.690
VRRP in press center. It's now showing that router 1 is the master along with

144
06:33.690 --> 06:34.640
the virtual IP address

145
06:34.640 --> 06:38.520
and the virtual MAC. And if we go back to the switch and we get the up arrow

146
06:38.520 --> 06:39.600
key, a moment ago,

147
06:39.600 --> 06:44.160
this MAC address was associated with gig 0 slash 2 going over to R2. But now if

148
06:44.160 --> 06:44.480
we do a show

149
06:44.480 --> 06:48.330
MAC address table, that MAC address is now associated with gig 0 slash 1, which

150
06:48.330 --> 06:49.840
goes down to R1. And if we

151
06:49.840 --> 06:55.320
go to PC 12 and we try to ping, for example, to 4.4.4.4 just to verify

152
06:55.320 --> 06:56.800
connectivity. And then

153
06:56.800 --> 07:02.260
furthermore, let's do a trace to 4444. So earlier we did it and the first top
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

153
06:56.800 --> 07:02.260
furthermore, let's do a trace to 4444. So earlier we did it and the first top

154
07:02.260 --> 07:03.600
was R2. And now if we do

155
07:03.600 --> 07:08.120
that same trace, now the first top is R1. Based on that last octet, then going

156
07:08.120 --> 07:09.920
to R3, then going to R4.

157
07:09.920 --> 07:13.070
And we're going to get rid of the port unreachable message. We can do a dash

158
07:13.070 --> 07:13.840
capital P space

159
07:13.840 --> 07:17.540
protocol 1 and then we'd use ICMP, but the path is going to be the same. Going

160
07:17.540 --> 07:19.200
from R1 to R3 to R4.

161
07:19.200 --> 07:23.340
And because I don't want to leave the network broken, let me go back to R2 and

162
07:23.340 --> 07:24.720
we'll do a no shutdown.

163
07:24.720 --> 07:28.560
And then once that comes up, it'll form the OSPMFJs and C. It'll become the

164
07:28.560 --> 07:30.320
master for the segment
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

164
07:28.560 --> 07:30.320
master for the segment

165
07:30.320 --> 07:35.900
regarding VRP. And once again, we go back to our client, which is PC 12. And we

166
07:35.900 --> 07:36.560
hit the up arrow key

167
07:36.560 --> 07:42.320
and do a trace to 4444 press center. The first top is now R2 and then goes to R

168
07:42.320 --> 07:43.680
3 and then to R4.

169
07:43.920 --> 07:48.180
So so far, so great. We've now configured HSRP and verified it. We've

170
07:48.180 --> 07:50.480
configured VRP and verified it.

171
07:50.480 --> 07:54.290
And in the next video, I'd like to walk you through the configuration and

172
07:54.290 --> 07:55.120
verification

173
07:55.120 --> 07:58.960
of Gateway Load Balancing Protocol. So I'll see you there in just a moment.