WEBVTT

1
00:00.000 --> 00:05.000
So based on our plan, our next step is to go ahead and assign two new

2
00:05.000 --> 00:07.800
interfaces to our Tier 0 gateway.

3
00:07.800 --> 00:11.800
And one of those interfaces is going to use the actual services of Edge 1.

4
00:11.800 --> 00:15.300
The other interface is going to be using the services of Edge 2.

5
00:15.300 --> 00:18.200
And we'll use the IP addresses of .61 and .62.

6
00:18.200 --> 00:22.030
And then for those interfaces, we'll also say that they connect to this

7
00:22.030 --> 00:23.900
external segment 192,

8
00:23.900 --> 00:28.800
which is our VLAN back segment, which in my network is the 192.61 network.

9
00:28.800 --> 00:33.330
Also, what I'd love to do is show you prior to implementing those two new
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:28.800 --> 00:33.330
Also, what I'd love to do is show you prior to implementing those two new

10
00:33.330 --> 00:34.500
interfaces on the DR

11
00:34.500 --> 00:37.000
and before we connect that effectively to the external router.

12
00:37.000 --> 00:42.430
Currently, we have no services router yet, but the moment we take our Tier 0

13
00:42.430 --> 00:43.000
gateway

14
00:43.000 --> 00:46.690
and we connect it to an external segment like this one right here, at that

15
00:46.690 --> 00:47.100
moment,

16
00:47.100 --> 00:52.400
it will also add this logical services router to our Tier 0 gateway.

17
00:52.400 --> 00:56.300
To confirm that, let's go ahead and take a look at before and then after we add

18
00:56.300 --> 00:57.000
the connectivity

19
00:57.000 --> 00:58.200
to the external network.

20
00:58.200 --> 01:03.000
So for fun, I've got the Edge 1 on the top pane here and I've got ESXIA,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:58.200 --> 01:03.000
So for fun, I've got the Edge 1 on the top pane here and I've got ESXIA,

21
01:03.000 --> 01:05.400
our host transport node here at the bottom.

22
01:05.400 --> 01:08.700
And let's just do a get gateways and press enter.

23
01:08.700 --> 01:14.470
So here we have the same three distributed routers on the host transport node

24
01:14.470 --> 01:16.000
and also on our edge.

25
01:16.000 --> 01:20.680
And also we have VRF0, which is like the routing table for the actual VM itself

26
01:20.680 --> 01:22.100
on the transport network.

27
01:22.100 --> 01:25.830
Also, if we scroll to the right a little bit, it shows us for these three gate

28
01:25.830 --> 01:26.200
ways

29
01:26.200 --> 01:28.200
that they are distributed routers.

30
01:28.200 --> 01:31.600
So distributed router for Tier 0 and there's the name over here on the left,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
01:28.200 --> 01:31.600
So distributed router for Tier 0 and there's the name over here on the left,

31
01:31.600 --> 01:35.530
then for gateway A, distributed router at Tier 1, and then gateway B also a

32
01:35.530 --> 01:36.800
distributed router at Tier 1.

33
01:36.800 --> 01:43.000
But notice there's no services router anywhere on either of these nodes.

34
01:43.000 --> 01:47.500
So our next step then is to go ahead and take this Tier 0 gateway and logically

35
01:47.500 --> 01:49.100
connect it with two new interfaces

36
01:49.100 --> 01:53.200
based on this plan and we're going to connect it to this external segment 192.

37
01:53.200 --> 01:57.000
And when we do at that moment, that's going to automatically add this logical

38
01:57.000 --> 01:58.500
services router component

39
01:58.500 --> 02:00.000
to our Tier 0 gateway.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
02:00.000 --> 02:03.920
In fact, let's do one other really cool test because the host transport node is

41
02:03.920 --> 02:05.700
not going to provide that connectivity

42
02:05.700 --> 02:08.400
to the external network and not be directly connected.

43
02:08.400 --> 02:12.830
It's not going to get a copy of the services router, but both edges will if we

44
02:12.830 --> 02:14.300
include both edges

45
02:14.300 --> 02:16.500
for the interfaces on the Tier 0 gateway.

46
02:16.500 --> 02:21.870
So they closed the window here for the ESXIA host and let me add another window

47
02:21.870 --> 02:23.100
that connects to edge two.

48
02:23.100 --> 02:26.000
All right, so we have edge one of the top edge two at the bottom and just as a

49
02:26.000 --> 02:26.700
starting point,

50
02:26.700 --> 02:31.200
let's do a get gateways and press enter and notice that both edge one and edge
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
02:26.700 --> 02:31.200
let's do a get gateways and press enter and notice that both edge one and edge

51
02:31.200 --> 02:33.600
two have all three distributed routers

52
02:33.600 --> 02:37.600
and neither of them yet have any services router function.

53
02:37.600 --> 02:41.680
So let's change that by adding some interfaces on this Tier 0 gateway that are

54
02:41.680 --> 02:43.400
connecting to that external segment.

55
02:43.400 --> 02:46.570
So to do that, we're going to go to networking, which we're currently on, and

56
02:46.570 --> 02:49.500
then we're going to go down to our Tier 0 gateway

57
02:49.500 --> 02:52.900
and it's here the Tier 0 gateway where we're going to edit it and specify that

58
02:52.900 --> 02:54.000
for interfaces.

59
02:54.000 --> 02:59.360
We want to have an interface using edge one that's connecting us to that VLAN

60
02:59.360 --> 03:00.500
back segment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
02:59.360 --> 03:00.500
back segment.

61
03:00.500 --> 03:03.970
So we'll click on the three dots here and then for the menu, we'll click on

62
03:03.970 --> 03:04.300
edit.

63
03:04.300 --> 03:08.630
So we're editing the details for our Tier 0 gateway called our Tier 0 gateway

64
03:08.630 --> 03:09.000
zero.

65
03:09.000 --> 03:13.870
If we scroll down under interfaces, we'll expand that and then from here, we'll

66
03:13.870 --> 03:15.100
simply click on set.

67
03:15.100 --> 03:17.600
And currently we have no external interfaces.

68
03:17.600 --> 03:19.300
So we'll simply click here to add.

69
03:19.300 --> 03:23.960
So this is like taking a router and physically adding a interface is going to

70
03:23.960 --> 03:25.000
connect to a network.

71
03:25.000 --> 03:28.330
And so for this first interface, let's call this dot 61 because that's the IP

72
03:28.330 --> 03:31.000
address we want to use via edge one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
03:28.330 --> 03:31.000
address we want to use via edge one.

73
03:31.000 --> 03:34.940
And that way, when we see the name of this interface that we're adding, we'll

74
03:34.940 --> 03:40.020
know, oh, that interface called dot 61 via edge one is being provided by our

75
03:40.020 --> 03:41.700
edge one transport node.

76
03:41.700 --> 03:46.210
And then for the type, it's going to be external and then for the IP address,

77
03:46.210 --> 03:50.900
we want to use 192 dot 168 dot 1 dot 61 with a 24 bit mask.

78
03:50.900 --> 03:51.900
So we'll plug that in.

79
03:51.900 --> 03:56.100
And then if we tab over now, it's asking us, where do you want to connect this?

80
03:56.100 --> 03:58.710
And we're going to use the drop down say, you know what, we want to connect

81
03:58.710 --> 04:03.900
this to our VLAN based segment called external segment 192.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
03:58.710 --> 04:03.900
this to our VLAN based segment called external segment 192.

82
04:03.900 --> 04:05.600
And that's how these are all glued together.

83
04:05.600 --> 04:09.570
Now, there is an additional thing we need to specify and that's this if we're

84
04:09.570 --> 04:13.260
going to use edge one to support this logical interface on our tier zero

85
04:13.260 --> 04:14.100
gateway.

86
04:14.100 --> 04:18.050
We'd also want to make sure from our drop down for edge node, we choose the

87
04:18.050 --> 04:19.300
right edge device.

88
04:19.300 --> 04:22.400
So these are our two edge nodes that are in our edge cluster.

89
04:22.400 --> 04:25.400
So we'll choose edge one and we are good to go.

90
04:25.400 --> 04:27.900
So we specifically the logical name of this interface.

91
04:27.900 --> 04:30.700
We specified the type or connecting to an external network.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
04:27.900 --> 04:30.700
We specified the type or connecting to an external network.

92
04:30.700 --> 04:32.900
We specify the segment we're connecting to.

93
04:32.900 --> 04:36.480
We specify the logical IP address we want to use and the edge node that we want

94
04:36.480 --> 04:40.900
to actually do the work for us for that connectivity to the physical network.

95
04:40.900 --> 04:44.900
So with that in place, we'll go ahead and scroll down and click on save.

96
04:44.900 --> 04:48.000
All right, so we have one interface via edge one.

97
04:48.000 --> 04:49.900
Let's go ahead and create the second one.

98
04:49.900 --> 04:51.700
In fact, right here, it says uninitialized.

99
04:51.700 --> 04:53.800
We can click on a little refresh there and there it is.

100
04:53.800 --> 04:54.500
Good to go.

101
04:54.500 --> 04:59.900
Let's create one more for dot 62 as a second interface connected at same

102
04:59.900 --> 05:00.400
segment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
04:59.900 --> 05:00.400
segment.

103
05:00.400 --> 05:03.700
But this time we'll use edge to four fault tolerance purposes.

104
05:03.700 --> 05:05.400
So we'll click on add interface.

105
05:05.400 --> 05:10.400
We'll call it dot 62 via edge dash to the type is going to be external for the

106
05:10.400 --> 05:11.400
external connection.

107
05:11.400 --> 05:15.900
And then we'll choose the segment ext seg 192, which is our VLAN base segment.

108
05:15.900 --> 05:21.010
So the IP address we want to use for the second interface is 192.168.1.62 with

109
05:21.010 --> 05:25.090
a 24 bit mask will plug it in and then from the edge node will click on the

110
05:25.090 --> 05:27.700
drop down and now showing us the remaining edge node.

111
05:27.700 --> 05:31.120
We only have two of them, so we'll pick edge to this going to support this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
05:27.700 --> 05:31.120
We only have two of them, so we'll pick edge to this going to support this

112
05:31.120 --> 05:33.200
logical interface on our gateway.

113
05:33.200 --> 05:36.700
So we'll scroll down, click on save and that looks good.

114
05:36.700 --> 05:41.250
So we'll click on close, then we'll scroll down and click on close editing and

115
05:41.250 --> 05:43.000
we can collapse all this.

116
05:43.000 --> 05:47.800
So now we have our tier zero gateway and it has two linked tier one gateways.

117
05:47.800 --> 05:49.400
That's gateway and gateway B.

118
05:49.400 --> 05:53.200
If we expand it, it's now showing us here under interfaces that we have two

119
05:53.200 --> 05:54.100
interfaces.

120
05:54.100 --> 05:56.800
And if we click here, it'll confirm what those are.

121
05:56.800 --> 06:01.660
So we've got the two interfaces with the IP addresses, 192, once it's 81 and 62
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

121
05:56.800 --> 06:01.660
So we've got the two interfaces with the IP addresses, 192, once it's 81 and 62

122
06:01.660 --> 06:02.600
respectively.

123
06:02.600 --> 06:06.640
There is their names and each of them are being supported if we expand those by

124
06:06.640 --> 06:08.400
a respective edge node.

125
06:08.400 --> 06:10.400
So this one is being supported by edge one.

126
06:10.400 --> 06:13.490
And if you look at the other one and scroll down, it's being supported by edge

127
06:13.490 --> 06:17.930
two and they're both connected to our external VLAN back segment called ext seg

128
06:17.930 --> 06:18.500
192.

129
06:18.500 --> 06:22.350
So we'll close that and then just for confirmation, let's click on network top

130
06:22.350 --> 06:22.800
ology.

131
06:22.800 --> 06:28.910
Let's zoom in on our T zero gateway and notice that it has two interfaces here,

132
06:28.910 --> 06:33.500
the 192, Wednesday, 161 and 192, Wednesday, 162.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

132
06:28.910 --> 06:33.500
the 192, Wednesday, 161 and 192, Wednesday, 162.

133
06:33.500 --> 06:38.200
And if we double click on this tier zero gateway, it's going to show us the

134
06:38.200 --> 06:40.200
details behind the scenes of what's supporting that.

135
06:40.200 --> 06:45.200
So currently edge one is active and edge two is the standby.

136
06:45.200 --> 06:46.500
So that looks great.

137
06:46.500 --> 06:48.300
Let me go back to our tier zero gateway.

138
06:48.300 --> 06:52.460
Let me remove one of those interfaces because I want to show you and compare in

139
06:52.460 --> 06:54.600
contrast edge one versus edge two.

140
06:54.600 --> 06:56.400
So we'll go back to this gateway.

141
06:56.400 --> 06:58.000
We'll click on the three dots.

142
06:58.000 --> 07:02.250
We'll click on edit and we'll say, you know what, for interfaces, we're just
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

142
06:58.000 --> 07:02.250
We'll click on edit and we'll say, you know what, for interfaces, we're just

143
07:02.250 --> 07:03.600
going to give you one for the moment.

144
07:03.600 --> 07:07.910
So I'll go back into interfaces and then I'm going to take the one via edge two

145
07:07.910 --> 07:12.000
and simply delete it and then click on delete and then click on refresh.

146
07:12.000 --> 07:13.800
And that just has one interface.

147
07:13.800 --> 07:17.900
So we click on close and close and we collapse that's just for tightiness.

148
07:17.900 --> 07:21.800
We go back to network topology and take a look at the top here and scroll up.

149
07:21.800 --> 07:26.010
Now our tier zero gateway only has one connection and if we double click on it

150
07:26.010 --> 07:28.700
is showing that it's going to be supported here just by edge one.

151
07:28.700 --> 07:31.920
Now the reason for that too is I want to show you the differences on edge one
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

151
07:28.700 --> 07:31.920
Now the reason for that too is I want to show you the differences on edge one

152
07:31.920 --> 07:32.900
versus edge two.

153
07:32.900 --> 07:36.180
So if we look at edge one because we're now connected to an external segment

154
07:36.180 --> 07:40.400
here, edge one is going to have a services router component running on it and

155
07:40.400 --> 07:43.650
edge two because it's not directly connected or used to connect to the physical

156
07:43.650 --> 07:43.700
.

157
07:43.700 --> 07:47.180
Network and not providing that service edge to is not going to have the

158
07:47.180 --> 07:48.800
services router as a result.

159
07:48.800 --> 07:51.500
So here are edge one and edge two from our output before.

160
07:51.500 --> 07:54.000
So we'll do a get gateways again press enter.

161
07:54.000 --> 07:59.320
So check this out edge one now has this SR services router component with its

162
07:59.320 --> 08:03.820
own UUID has its own VRF and there's the name and you'll notice edge to does
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

162
07:59.320 --> 08:03.820
own UUID has its own VRF and there's the name and you'll notice edge to does

163
08:03.820 --> 08:07.950
not have a copy of that services router function because at the moment edge to

164
08:07.950 --> 08:11.700
is not being used as part of that connectivity from the tier zero gateway to

165
08:11.700 --> 08:12.700
the physical network.

166
08:12.700 --> 08:17.180
So if we went back and we changed that we go back to our tier zero gateway we

167
08:17.180 --> 08:21.580
go back and we edit our tier zero gateway once again and then we go down to

168
08:21.580 --> 08:26.110
interfaces and we click here on the link for interfaces and then we add the

169
08:26.110 --> 08:27.300
interface back in.

170
08:27.300 --> 08:31.810
We'll call it dot 62 via edge to make sure that we're selecting edge to be used
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

170
08:27.300 --> 08:31.810
We'll call it dot 62 via edge to make sure that we're selecting edge to be used

171
08:31.810 --> 08:35.840
as part of this looks like the external segment and then we'll put in the IP

172
08:35.840 --> 08:40.170
address here and then we'll scroll down and click on save and we'll confirm our

173
08:40.170 --> 08:40.800
work here.

174
08:40.800 --> 08:43.840
We'll refresh that make sure it says success that looks great will click on

175
08:43.840 --> 08:44.300
close.

176
08:44.300 --> 08:48.370
So now if we go to network topology for our tier zero gateway it once again has

177
08:48.370 --> 08:52.380
two interfaces and if we double click on the tier zero gateway to look at the

178
08:52.380 --> 08:56.800
fabric is now showing us the edge one and edge to are both participating.

179
08:56.800 --> 08:59.400
So this is active it says edge to unknown.

180
08:59.400 --> 09:03.200
So in a moment or two that'll turn to standby and show as standby.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

180
08:59.400 --> 09:03.200
So in a moment or two that'll turn to standby and show as standby.

181
09:03.200 --> 09:06.730
However now that edge to is involved as a logical interface and providing

182
09:06.730 --> 09:10.670
connectivity or could provide connectivity to the external network on this tier

183
09:10.670 --> 09:14.200
zero gateway edge to will also now have a copy of that services router.

184
09:14.200 --> 09:16.200
So we click on refresh that looks better.

185
09:16.200 --> 09:20.570
So there's edge one active edge to standby and let's take a look at the CLI as

186
09:20.570 --> 09:21.200
well.

187
09:21.200 --> 09:24.940
So back at the CLI for both those two a moment ago just edge one had the

188
09:24.940 --> 09:29.200
services router component for the tier zero gateway and edge to do not.

189
09:29.200 --> 09:33.170
So if we have the upper key and do get gateways again now they both have a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

189
09:29.200 --> 09:33.170
So if we have the upper key and do get gateways again now they both have a

190
09:33.170 --> 09:37.200
services router function associated with our tier zero gateway zero.

191
09:37.200 --> 10:00.000
[no audio]