WEBVTT

1
00:00.000 --> 00:03.800
All right, so based on our game plan, we are now going to create a Tier 0

2
00:03.800 --> 00:08.000
gateway that's going to be stretched and available across both of our sites.

3
00:08.000 --> 00:11.410
So once again, we're going to go to our global manager and we're going to

4
00:11.410 --> 00:13.000
create that new T0 gateway.

5
00:13.000 --> 00:17.250
So here at the NSX global manager, if we go back to networking and with

6
00:17.250 --> 00:21.360
networking selected, we'll go down under connectivity and click on Tier 0 gate

7
00:21.360 --> 00:22.000
ways.

8
00:22.000 --> 00:25.860
We don't have any yet, so let's go ahead and create one by clicking here on add

9
00:25.860 --> 00:27.000
Tier 0 gateway.

10
00:27.000 --> 00:30.930
So let's go ahead and name this stretch T0 and as far as the H.A. mode, let's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:27.000 --> 00:30.930
So let's go ahead and name this stretch T0 and as far as the H.A. mode, let's

11
00:30.930 --> 00:32.000
use active standby.

12
00:32.000 --> 00:35.000
And for the failover mode, we could use non-pramptive or preemptive.

13
00:35.000 --> 00:38.500
With non-pramptive, if there's a failover event, we have to manually fail it

14
00:38.500 --> 00:39.000
back.

15
00:39.000 --> 00:41.000
So I'm going to go ahead for the lab and say preemptive.

16
00:41.000 --> 00:44.200
In that way, the device that we specify as active, if there's a problem or a

17
00:44.200 --> 00:48.470
failover issue, if it comes back online, it'll fail back to the method that we

18
00:48.470 --> 00:49.000
specify.

19
00:49.000 --> 00:52.980
So here under locations, this is how we specify where this is going to be

20
00:52.980 --> 00:56.000
stretched to. So by default, there are no locations specified.

21
00:56.000 --> 01:00.540
So under location, we use the dropdown, say we want this stretch T0 gateway to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
00:56.000 --> 01:00.540
So under location, we use the dropdown, say we want this stretch T0 gateway to

22
01:00.540 --> 01:05.250
be available at site one, and we'll click on add location and specify we also

23
01:05.250 --> 01:07.000
want it available at site two, just like that.

24
01:07.000 --> 01:10.000
And then we're going to specify which one's going to be primary.

25
01:10.000 --> 01:14.130
So for this Tier 0 gateway, let's make site one the primary and site two the

26
01:14.130 --> 01:15.000
secondary.

27
01:15.000 --> 01:17.920
And then as we go to the right, we're going to specify the edge cluster to use

28
01:17.920 --> 01:19.000
from each of the sites.

29
01:19.000 --> 01:23.270
So at site one and site two, I only have one cluster of edge nodes. So that'll

30
01:23.270 --> 01:24.000
be the one here in the list.

31
01:24.000 --> 01:29.450
So here's the lab edge cluster. That's the name of it in site one and at site

32
01:29.450 --> 01:32.000
two, I called it lab two edge cluster.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:29.450 --> 01:32.000
two, I called it lab two edge cluster.

33
01:32.000 --> 01:35.440
So we'll select those respective edge clusters. And then furthermore, if you

34
01:35.440 --> 01:39.080
want to control which edge node as part of that cluster you want to use, we

35
01:39.080 --> 01:40.000
could specify that here.

36
01:40.000 --> 01:44.490
So here at site one, I've got the edge one and edge two and a similar treatment

37
01:44.490 --> 01:47.000
for site two from the lab two edge cluster.

38
01:47.000 --> 01:51.180
I've got two choices there as well, or you can just go ahead and let it choose

39
01:51.180 --> 01:52.000
on its own.

40
01:52.000 --> 01:55.460
And the add location button is now grayed out because I only have these two

41
01:55.460 --> 01:59.000
sites. There isn't yet another site I could add here if I wanted to.

42
01:59.000 --> 02:02.000
So we'll scroll down and we'll go ahead and click on save.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:59.000 --> 02:02.000
So we'll scroll down and we'll go ahead and click on save.

43
02:02.000 --> 02:06.510
So since we also want to add some interfaces, let's click on yes to continue

44
02:06.510 --> 02:10.790
our configuration. And now for the stretched tier zero gateway, let's go ahead

45
02:10.790 --> 02:12.000
and add some interfaces.

46
02:12.000 --> 02:15.560
So I'm going to expand the interfaces section. And before we start configuring

47
02:15.560 --> 02:18.000
interfaces, let's take a look at our game plan.

48
02:18.000 --> 02:22.480
So for our game plan here at site one, I want to use these two interfaces, one

49
02:22.480 --> 02:27.050
on each edge for the tier zero gateway and over at site two, I want to use

50
02:27.050 --> 02:31.000
these two interfaces, again, leveraging the extra segment 23 here at site one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
02:27.050 --> 02:31.000
these two interfaces, again, leveraging the extra segment 23 here at site one.

51
02:31.000 --> 02:35.340
And the external segment using VLAN 24 at site two. So for the naming

52
02:35.340 --> 02:39.650
convention, it'll remind us of which site we're at, which edge node, which VLAN

53
02:39.650 --> 02:42.000
and the last octet of the IP address.

54
02:42.000 --> 02:47.490
So over here at site one for that external connection is 23.1.2.0. That's the

55
02:47.490 --> 02:55.230
subnet. And over here at site two, the external segment on VLAN 24 is 24.1.2.0

56
02:55.230 --> 02:56.000
with the 24-bit mask.

57
02:56.000 --> 03:00.180
And the router on the physical network is at dot one. And then what we'll do is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:56.000 --> 03:00.180
And the router on the physical network is at dot one. And then what we'll do is

58
03:00.180 --> 03:05.000
we'll have edge one over here, use dot 61, edge two over here, use dot 62.

59
03:05.000 --> 03:09.740
And then over here at site two, we'll have edge one used dot 61 on the 24.1 to

60
03:09.740 --> 03:13.000
network and edge two use dot 62 on that same network.

61
03:13.000 --> 03:17.290
So let's add those four interfaces to this stretch T zero gateway. So to give

62
03:17.290 --> 03:19.550
us a little more room here, I'm going to go ahead and collapse the left hand

63
03:19.550 --> 03:20.000
column.

64
03:20.000 --> 03:25.220
And let's go to work. So under interfaces for our tier zero gateway, let's go

65
03:25.220 --> 03:29.000
ahead and click on set under interfaces and click on add.

66
03:29.000 --> 03:35.000
So for the first one is going to be site one edge one VLAN 23 and using dot 61.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
03:29.000 --> 03:35.000
So for the first one is going to be site one edge one VLAN 23 and using dot 61.

67
03:35.000 --> 03:37.000
So that'll be the name of this interface.

68
03:37.000 --> 03:42.500
And the IP address is going to be 23.1.2.61 with a 24-bit mask. So we'll put

69
03:42.500 --> 03:45.550
that in. Notice here for the segment, we can't choose that yet because we haven

70
03:45.550 --> 03:49.000
't specified which location we want this to be at.

71
03:49.000 --> 03:53.330
So under location, we'll choose site one. And then it should show us any of our

72
03:53.330 --> 03:57.000
VLAN back segments over at site one. So we'll use the drop down.

73
03:57.000 --> 04:01.270
And sure enough, there it is site one external VLAN 23. So let's choose that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
03:57.000 --> 04:01.270
And sure enough, there it is site one external VLAN 23. So let's choose that

74
04:01.270 --> 04:05.000
segment. And then as we continue down for the edge node, we use the drop down

75
04:05.000 --> 04:08.000
and let's use edge one based on our plan.

76
04:08.000 --> 04:12.040
We do the name right there, E1 representing edge one and we'll scroll down and

77
04:12.040 --> 04:15.810
click on save. All right. So there's one interface for site one. Let's add a

78
04:15.810 --> 04:19.000
second one for site one and they'll be using edge two.

79
04:19.000 --> 04:22.420
So I'm going to go ahead and copy that syntax so I can replicate it pretty

80
04:22.420 --> 04:26.740
easily. And let's click on add interface. I'll go ahead and paste that name in

81
04:26.740 --> 04:28.000
and then I'll edit it.

82
04:28.000 --> 04:31.980
So this is site one. This is going to be edge two still be then 23 and the IP
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

82
04:28.000 --> 04:31.980
So this is site one. This is going to be edge two still be then 23 and the IP

83
04:31.980 --> 04:35.000
address is going to be dot 62. And that way when we see these interface names,

84
04:35.000 --> 04:37.000
the reminder is based on the naming convention.

85
04:37.000 --> 04:41.300
Exactly where they are. So then for the location, this is going to be site one

86
04:41.300 --> 04:45.730
also for the IP address. This is going to be 23 dot one dot two dot 62 with a

87
04:45.730 --> 04:47.000
24 bit mask.

88
04:47.000 --> 04:50.280
And for the segment, we're going to be connecting to that site one external V

89
04:50.280 --> 04:54.310
LAN 23. And then for the edge node, we only have one other one there and that's

90
04:54.310 --> 04:58.000
edge two. So we'll select that and we'll scroll down and click on save.

91
04:58.000 --> 05:02.140
So there's the two edge node interface addresses that we're using on the tier
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
04:58.000 --> 05:02.140
So there's the two edge node interface addresses that we're using on the tier

92
05:02.140 --> 05:05.800
zero gateway over at site one. Let's repeat that process. But for the two

93
05:05.800 --> 05:09.000
interfaces for the tier zero gateway over at site two.

94
05:09.000 --> 05:13.170
So we'll click on add interface. I'll click on paste and let's update this. So

95
05:13.170 --> 05:17.440
for the names can be s two for site two. The edge is going to be edge one at

96
05:17.440 --> 05:20.000
site two. It's going to be VLAN 24.

97
05:20.000 --> 05:24.020
And the last octet is going to be 61 and this can be on the 24 dot one dot two

98
05:24.020 --> 05:28.340
network. So we'll put a dot 61 there with the 24 bit mask and the location for

99
05:28.340 --> 05:30.000
this is going to be site two.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

100
05:30.000 --> 05:34.060
And then we'll use the dropdown for the segment and it's showing us the VLAN

101
05:34.060 --> 05:39.000
back segments over at site two. So there's our site to external VLAN 24.

102
05:39.000 --> 05:42.630
And for the edge nodes, it's going to show us the two edge nodes over there at

103
05:42.630 --> 05:46.450
site two. So for this first one, it'll be the IP address associated with edge

104
05:46.450 --> 05:49.000
one and we'll scroll down and click on save.

105
05:49.000 --> 05:53.350
And then we'll repeat that process for the second edge node at site two. So I'm

106
05:53.350 --> 05:57.230
going to copy that name. They'll save me a little bit of typing. And then we'll

107
05:57.230 --> 05:59.000
click on add interface and we'll paste.

108
05:59.000 --> 06:03.120
And then I'll go ahead and update this to be edge two and the IP address is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

108
05:59.000 --> 06:03.120
And then I'll go ahead and update this to be edge two and the IP address is

109
06:03.120 --> 06:07.590
going to be dot 62 location is going to be site two IP address is going to be

110
06:07.590 --> 06:11.000
24 dot one dot two dot 62 with a 24 bit mask.

111
06:11.000 --> 06:14.600
And for the external segment over at site two, use the dropdown. Here's our

112
06:14.600 --> 06:18.690
site to external VLAN 24 segments will select that. And then for the edge node

113
06:18.690 --> 06:22.630
for this one, our only remaining edge node over there at site two is lab two

114
06:22.630 --> 06:24.000
edge two so select that.

115
06:24.000 --> 06:30.000
And we'll scroll down, click on save, and then we are going to check our work.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

116
06:30.000 --> 06:33.940
So let me go ahead and check status on each of these. And let me check out the

117
06:33.940 --> 06:40.600
IP address real quick. So 23 dot 1 dot 2 61 62 24 12 61 62 that part looks good

118
06:40.600 --> 06:42.000
site one site two.

119
06:42.000 --> 06:45.680
The naming convention looks good as well. If we expand each one, this is for

120
06:45.680 --> 06:48.000
edge one fantastic that should be edge two.

121
06:48.000 --> 06:53.350
Then for site two, that's edge one and the second edge is edge two. That all

122
06:53.350 --> 06:58.150
looks great. So we'll go ahead and click on close, scroll down, click on close

123
06:58.150 --> 06:59.000
editing.

124
06:59.000 --> 07:02.190
And now if we scroll down interfaces, it's showing us that we have two
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
06:59.000 --> 07:02.190
And now if we scroll down interfaces, it's showing us that we have two

125
07:02.190 --> 07:05.000
interfaces for site one and two interfaces for site two.

126
07:05.000 --> 07:08.110
Now, what I'd like to do just for a moment is pop over and just give you a bird

127
07:08.110 --> 07:11.270
's eye view of what this looks like from the topology from the perspective of

128
07:11.270 --> 07:12.000
site one.

129
07:12.000 --> 07:16.020
So we click here on site one from the drop down. It just took us over to site

130
07:16.020 --> 07:19.000
one and furthermore, click on network topology.

131
07:19.000 --> 07:22.840
It's now showing us the details from the local manager of site one, which says,

132
07:22.840 --> 07:27.000
hey, I've got this tier zero gateway and I've got these two logical interfaces.

133
07:27.000 --> 07:33.230
231261 and 231262. And if we double click on the tier zero gateway here, they
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

133
07:27.000 --> 07:33.230
231261 and 231262. And if we double click on the tier zero gateway here, they

134
07:33.230 --> 07:36.730
'll show us the fabric view to confirm for us which edges are being used for

135
07:36.730 --> 07:38.000
that functionality.

136
07:38.000 --> 07:44.000
So here's edge one with 231261 and edge two with 231262. Fantastic.

137
07:44.000 --> 07:47.760
I'd also like to take a moment and just confirm from the perspective of edge

138
07:47.760 --> 07:52.080
one here at site one that it really does have access to this 2312 network and

139
07:52.080 --> 07:53.000
then my VLANs are all set up correctly.

140
07:53.000 --> 07:57.590
So let's just go SSH over to edge one for a moment and verify we can ping the

141
07:57.590 --> 08:03.000
external router on that same VLAN, which should be at 23.1.2.1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

141
07:57.590 --> 08:03.000
external router on that same VLAN, which should be at 23.1.2.1.

142
08:03.000 --> 08:06.570
So let me confirm the IP address of this edge node. So we're still here at site

143
08:06.570 --> 08:10.630
one. So on site one, if we go to system by clicking on the system tab right

144
08:10.630 --> 08:14.000
here and then on the left expand fabric and then click on nodes.

145
08:14.000 --> 08:21.000
Here it can confirm for us the IP addresses. So edge one is at 192.168.1.191.

146
08:21.000 --> 08:25.560
So let's open up an SSH session and just verify basic connectivity. So here's

147
08:25.560 --> 08:28.000
my secure CRT as my terminal emulator.

148
08:28.000 --> 08:31.920
And I've got an entry right here for 191. So we'll go ahead and connect and it
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

148
08:28.000 --> 08:31.920
And I've got an entry right here for 191. So we'll go ahead and connect and it

149
08:31.920 --> 08:36.000
's not connecting. Oh, I may not have enabled SSH on that edge node.

150
08:36.000 --> 08:40.890
Have no fear. We can check and correct that if that's the case. So back at the

151
08:40.890 --> 08:45.290
site one local manager. So we got there by starting at the NSX global manager

152
08:45.290 --> 08:47.000
and choosing site one.

153
08:47.000 --> 08:51.130
And so here logically at site one, if we go to this edge and select it, I want

154
08:51.130 --> 08:55.080
to click on actions and let's go ahead and click right here on change node

155
08:55.080 --> 08:56.000
settings.

156
08:56.000 --> 08:59.950
And that should allow us to enable SSH. So again, from actions for that edge

157
08:59.950 --> 09:04.000
node clicking on change node settings and we'll give that just a moment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

157
08:59.950 --> 09:04.000
node clicking on change node settings and we'll give that just a moment.

158
09:04.000 --> 09:07.000
And from here, we want to go ahead and specify that we want to allow SSH login.

159
09:07.000 --> 09:11.420
So I rebuilt my lab a few days ago and I failed to enable that when I deployed

160
09:11.420 --> 09:12.000
the edge of nodes.

161
09:12.000 --> 09:16.180
So I'll go ahead and say yes to that scroll down. Then we'll click on save. So

162
09:16.180 --> 09:21.000
now that's updating. Let's go ahead and try the SSH session again.

163
09:21.000 --> 09:25.210
So back at secure CRT will try that connection and that looks a lot better. All

164
09:25.210 --> 09:30.000
right. So we are logged on to edge one at site one and let's do a get gateways.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

165
09:30.000 --> 09:35.150
So there's our T zero services router. It's in VRF 13. So the test connectivity

166
09:35.150 --> 09:38.000
to the outside world, which that T zero router should have.

167
09:38.000 --> 09:43.680
Let's go into that VRF by typing in VRF space 13. And then from here, let's do

168
09:43.680 --> 09:46.000
a get route just to verify our routes.

169
09:46.000 --> 09:50.940
So there is our T zero connected network with 23.12 and we could also get

170
09:50.940 --> 09:55.000
forwarding. So currently we are directly connected to this network.

171
09:55.000 --> 10:00.970
So we should be able to ping 23.1.2.1, which is the external gateway on that V
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

171
09:55.000 --> 10:00.970
So we should be able to ping 23.1.2.1, which is the external gateway on that V

172
10:00.970 --> 10:06.000
LAN 23. So we'll do a ping to 23.1.2.1 and press enter.

173
10:06.000 --> 10:10.540
And sure enough, that is flying fantastic. So we'll do a control C. So that's a

174
10:10.540 --> 10:14.140
great way to confirm from a connectivity perspective that we really are

175
10:14.140 --> 10:15.000
connected to the right.

176
10:15.000 --> 10:18.660
VLAN and we have access to that external gateway by the interface on the T zero

177
10:18.660 --> 10:21.000
gateway that's being provided by edge one.

178
10:21.000 --> 10:25.140
Let me go ahead and minimize that. So now we have our tier zero gateway. We

179
10:25.140 --> 10:30.000
also have our external interfaces configured for both site one and site two
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

180
10:30.000 --> 10:35.000
using these VLANs respectively and the edge nodes at those sites.

181
10:35.000 --> 10:39.220
And our next logical step would be to configure the routing. So with NSX

182
10:39.220 --> 10:44.090
Federation, what is not supported is OSPF. So we couldn't use OSPF between the

183
10:44.090 --> 10:47.000
edge routers and our tier zero gateways.

184
10:47.000 --> 10:51.220
But we could use BGP or we could use data crowds. So what I propose we do in

185
10:51.220 --> 10:54.790
the next video, let's go to our tier zero gateway and set up two default routes

186
10:54.790 --> 10:55.000
.

187
10:55.000 --> 10:58.960
One that says, Hey, your default route goes up to service provider A over here

188
10:58.960 --> 11:05.000
through site one. That's a 23.1.2.1 and at site two for that T zero gateway.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

188
10:58.960 --> 11:05.000
through site one. That's a 23.1.2.1 and at site two for that T zero gateway.

189
11:05.000 --> 11:10.090
It's default route. She's the next top of 24.1.2.1. So we'll set up a static

190
11:10.090 --> 11:13.370
default route. Also, while we're there, let's also set up source net for

191
11:13.370 --> 11:16.000
traffic that's trying to go out to the external world.

192
11:16.000 --> 11:19.660
And we'll do that as well here at site one as well as at site two, both for

193
11:19.660 --> 11:23.810
that T zero gateway. So we'll do both of those in the next video. So I'll see

194
11:23.810 --> 11:26.000
you there in just a moment.