WEBVTT

1
00:00.000 --> 00:03.560
So in our journey, we just finished configuring the external interfaces on our

2
00:03.560 --> 00:04.460
T0 gateway.

3
00:04.460 --> 00:08.460
And next, we're going to go ahead and do the IP routing and the source net.

4
00:08.460 --> 00:11.880
So let's start with the IP routing and we'll set up a default route on the T0

5
00:11.880 --> 00:12.500
gateway,

6
00:12.500 --> 00:15.670
a default route that goes through the service provider connecting site one to

7
00:15.670 --> 00:16.300
the internet,

8
00:16.300 --> 00:19.940
and another default route for the service provider at site two.

9
00:19.940 --> 00:25.780
And those addresses of the external gateways are 23.1.2.1 for site one.

10
00:25.780 --> 00:32.230
And at site two, the default gateway address for the service provider is 24.1.2
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:25.780 --> 00:32.230
And at site two, the default gateway address for the service provider is 24.1.2

11
00:32.230 --> 00:32.660
.1.

12
00:32.660 --> 00:36.190
And the cool thing is with NSX Federation when setting up these default routes

13
00:36.190 --> 00:37.260
or any routes to that matter,

14
00:37.260 --> 00:39.980
is that we can associate those routes with a specific site.

15
00:39.980 --> 00:43.980
So we'll create the default static route here on site one with this next top

16
00:43.980 --> 00:47.100
and the default route here at site two with this next top.

17
00:47.100 --> 00:51.290
So let's head back to the global manager and let's implement those two default

18
00:51.290 --> 00:52.220
static routes.

19
00:52.220 --> 00:55.780
So to go back to the global manager, when we left off, we were at site one.

20
00:55.780 --> 00:59.020
So from the drop down here, we'll go back to the global manager.

21
00:59.020 --> 01:01.060
So currently says we're back at the global manager.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
00:59.020 --> 01:01.060
So currently says we're back at the global manager.

22
01:01.060 --> 01:03.580
Fantastic. That's also indicated right here.

23
01:03.580 --> 01:06.870
And let's click on networking right here in the interface for the global

24
01:06.870 --> 01:07.500
manager.

25
01:07.500 --> 01:10.580
So with networking in the top selected on the left on our connectivity,

26
01:10.580 --> 01:12.940
we'll click on our tier zero gateways.

27
01:12.940 --> 01:16.940
So there's our current tier zero gateway called stretch T0.

28
01:16.940 --> 01:19.940
And if we want to set up a default route for our tier zero gateway,

29
01:19.940 --> 01:23.380
we'll simply click on the three dots, click on edit from the menu,

30
01:23.380 --> 01:25.460
and then scroll down to the routing section.

31
01:25.460 --> 01:27.540
So down on the routing, we'll expand that.

32
01:27.540 --> 01:30.900
And then down here under static routes, we'll click on set.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:27.540 --> 01:30.900
And then down here under static routes, we'll click on set.

33
01:30.900 --> 01:32.820
So by default, no static routes.

34
01:32.820 --> 01:34.500
So we'll click on add static route.

35
01:34.500 --> 01:42.340
And let's call this one default or site one via ISP dash a and this little note

36
01:42.340 --> 01:42.580
there.

37
01:42.580 --> 01:45.460
That's going to be through our local VLAN 23.

38
01:45.460 --> 01:46.500
So that's just the label.

39
01:46.500 --> 01:47.780
So when we see it will know what it is.

40
01:47.780 --> 01:51.620
And then for the default route for IPV four, that's going to look like four z

41
01:51.620 --> 01:53.460
eros and a slash zero.

42
01:53.460 --> 01:55.060
And then we need to specify the next top.

43
01:55.060 --> 01:58.980
So service brother A, the next top is going to be 23.1.2.1.

44
01:58.980 --> 02:03.140
So to do that here in the column for next hops, we'll click on set right there.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
01:58.980 --> 02:03.140
So to do that here in the column for next hops, we'll click on set right there.

45
02:03.140 --> 02:05.300
And then we'll click on set next tops.

46
02:05.300 --> 02:09.700
And we'll go ahead and say the next top is going to be 23.1.2.1.

47
02:09.700 --> 02:12.420
And for the administrative distance, I'm going to put it 150.

48
02:12.420 --> 02:16.820
Now the administrative distance is only important if there's multiple default

49
02:16.820 --> 02:17.140
routes

50
02:17.140 --> 02:18.420
coming in from different sources.

51
02:18.420 --> 02:23.230
So later, if we have a default route that's being learned, for example, from

52
02:23.230 --> 02:24.260
external BGP

53
02:24.260 --> 02:28.640
or some other method and it has a lower AD, the route with the lower AD is

54
02:28.640 --> 02:29.380
going to win

55
02:29.380 --> 02:31.060
and be placed in the routing table.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:29.380 --> 02:31.060
and be placed in the routing table.

56
02:31.060 --> 02:33.140
So I'm going to use 150 here at the moment.

57
02:33.140 --> 02:35.220
It's going to be the only default route for site one.

58
02:35.220 --> 02:37.860
And then for the scope, this is also super important.

59
02:37.860 --> 02:41.860
I'm going to click here for scope and say this is going to apply just to site

60
02:41.860 --> 02:42.180
one.

61
02:42.180 --> 02:45.540
Alternatively, we could also specify specific interfaces.

62
02:45.540 --> 02:48.740
But I'm going to go ahead and say all of site one and click on add.

63
02:48.740 --> 02:51.780
And then we'll click on apply and then click on save.

64
02:51.780 --> 02:56.820
So now our tier zero gateway has a single default route via service provider A

65
02:56.820 --> 02:57.860
over at site one.

66
02:57.860 --> 02:59.380
So let's do a similar treatment.

67
02:59.380 --> 03:03.460
But for a default route through service provider B, which is over at site two.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
02:59.380 --> 03:03.460
But for a default route through service provider B, which is over at site two.

68
03:03.460 --> 03:05.380
So we'll click on add static route.

69
03:05.380 --> 03:06.420
I'm going to put the name in.

70
03:06.420 --> 03:08.900
So I just copy pasted their default for site.

71
03:08.900 --> 03:13.540
We want this to be two through ISP B as in boy.

72
03:13.540 --> 03:18.030
And that's going to be using our local VLAN 24 for access to that service

73
03:18.030 --> 03:18.500
provider.

74
03:18.500 --> 03:21.540
And then the actual route itself is going to be the 0, 0, 0, 0,

75
03:21.540 --> 03:22.420
slash zero.

76
03:22.420 --> 03:24.900
That's the syntax for a default route for IPv4.

77
03:24.900 --> 03:26.820
And then we'll click here on next tops.

78
03:26.820 --> 03:29.780
We'll click on set and click on set next tops.

79
03:29.780 --> 03:34.420
And for ISP B, it's at 24 dot 1 dot 2 dot 1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
03:29.780 --> 03:34.420
And for ISP B, it's at 24 dot 1 dot 2 dot 1.

80
03:34.420 --> 03:36.580
And then I'm also going to do the same administrative distance.

81
03:36.580 --> 03:38.740
And the scope is going to be for site two.

82
03:38.740 --> 03:40.340
So I'll specify site two there.

83
03:40.340 --> 03:42.900
Click on add and then click on apply.

84
03:42.900 --> 03:44.340
And then click on save.

85
03:44.340 --> 03:46.580
And now we have two default routes.

86
03:46.580 --> 03:51.380
And just to confirm the next tops for ISP, the next top is 23 dot 1 dot 2 dot 1

87
03:51.380 --> 03:51.380
.

88
03:51.380 --> 03:54.710
And for the default route for site two, if we click here on the hyperlink for

89
03:54.710 --> 03:55.380
next tops,

90
03:55.380 --> 03:57.140
it's 24 dot 1 dot 2 dot 1.

91
03:57.140 --> 03:59.380
And the scope is site two fantastic.

92
03:59.380 --> 04:00.660
So we'll go ahead and close that.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

92
03:59.380 --> 04:00.660
So we'll go ahead and close that.

93
04:00.660 --> 04:01.540
That all looks good.

94
04:01.540 --> 04:05.220
And we'll click on close and it'll scroll down and click on close editing.

95
04:05.220 --> 04:08.740
And we should also be able to verify that at either of our edges as well.

96
04:08.740 --> 04:13.220
So let me go ahead and SSH back over to edge one at site one.

97
04:13.220 --> 04:15.300
And from here, let's do a gate gateways.

98
04:15.300 --> 04:19.060
So it's VRF 13 for our stretch tier zero services router.

99
04:19.060 --> 04:23.770
So what we'll do is type in VRF 13 to go into that VRF and let's do a get route

100
04:23.770 --> 04:24.740
and press enter.

101
04:24.740 --> 04:29.060
And we should have a default route with the next top of 23 dot 1 dot 2 dot 1,

102
04:29.060 --> 04:29.940
which we do.

103
04:29.940 --> 04:34.260
We could also see the same information with a get forwarding just like that,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
04:29.940 --> 04:34.260
We could also see the same information with a get forwarding just like that,

104
04:34.260 --> 04:36.580
which also confirms that we have our default route.

105
04:36.580 --> 04:40.020
And we already verified in a previous video that we can ping that address.

106
04:40.020 --> 04:42.980
However, since we're here, let's just verify once again that we can ping 23 dot

107
04:42.980 --> 04:44.260
1 dot 2 dot 1.

108
04:44.260 --> 04:45.780
And that looks good.

109
04:45.780 --> 04:48.740
And if the service provider has everything else set up for us to reach the

110
04:48.740 --> 04:48.980
internet,

111
04:48.980 --> 04:52.580
we should be able to from this VRF for our services router for the tier zero

112
04:52.580 --> 04:52.980
gateway.

113
04:52.980 --> 04:54.500
We should be able to go out to the internet.

114
04:54.500 --> 04:57.540
Let's try a ping out to 8888.

115
04:57.540 --> 04:58.820
And that is work.

116
04:58.820 --> 05:00.260
It's we'll do a control C.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

116
04:58.820 --> 05:00.260
It's we'll do a control C.

117
05:00.260 --> 05:02.980
And let's also do a trace route out to 8888.

118
05:02.980 --> 05:05.860
Just to verify we really are going out to the internet.

119
05:05.860 --> 05:08.260
And that trace route didn't look too happy.

120
05:08.260 --> 05:14.340
So let's go ahead and source that from our 23 dot 1 dot 2 dot and edge 1 is at

121
05:14.340 --> 05:15.060
dot 61.

122
05:15.060 --> 05:17.220
Let's see if that gives us any better success.

123
05:17.220 --> 05:17.860
Ah, there we go.

124
05:17.860 --> 05:19.700
I'll cancel that.

125
05:19.700 --> 05:22.660
So apparently initially when I traded it without specifying the actual source

126
05:22.660 --> 05:23.460
address,

127
05:23.460 --> 05:25.300
it was using an address that wasn't reached.

128
05:25.300 --> 05:27.620
We'll back through that same service provider.

129
05:27.620 --> 05:32.780
However, when I told to explicitly use the edge node address 231261, it worked
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

129
05:27.620 --> 05:32.780
However, when I told to explicitly use the edge node address 231261, it worked

130
05:32.780 --> 05:33.460
no problem.

131
05:33.460 --> 05:36.260
So another we have our IP routing set up with a default route.

132
05:36.260 --> 05:38.100
We tested it through service provider one.

133
05:38.100 --> 05:41.410
We could also verify that from an edge node over here at site two is very

134
05:41.410 --> 05:41.700
likely

135
05:41.700 --> 05:45.060
of the same success in going out to 24 dot 1 dot 2 dot 1.

136
05:45.060 --> 05:47.380
Our next step is to implement source net.

137
05:47.380 --> 05:51.220
And that's so that when these clients eventually, once we build the segment and

138
05:51.220 --> 05:52.340
the tier 1 gateway,

139
05:52.340 --> 05:55.700
when their traffic hits the tier zero, we want to go ahead and net it over.

140
05:55.700 --> 06:01.940
And so for a game plan, let's net all the traffic here to 23 dot 1 dot 2 dot 60
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

140
05:55.700 --> 06:01.940
And so for a game plan, let's net all the traffic here to 23 dot 1 dot 2 dot 60

141
06:01.940 --> 06:01.940
.

142
06:01.940 --> 06:05.460
Let's imagine that's an IP address that we're allowed to use here between us

143
06:05.460 --> 06:06.020
and our service

144
06:06.020 --> 06:12.660
provider and for site two, let's use 24 dot 1 dot 2 dot 60 as the net address.

145
06:12.660 --> 06:16.810
And for conditions, we'll say anybody coming in from the source address of 10,

146
06:16.810 --> 06:17.460
anything,

147
06:17.460 --> 06:20.260
go ahead and do that same thing for this net rule here.

148
06:20.260 --> 06:24.260
So once again, we're taking this common stretched tier zero gateway and we're

149
06:24.260 --> 06:25.540
creating two net

150
06:25.540 --> 06:29.340
rules, one that would be used if traffic is going out through service provider

151
06:29.340 --> 06:30.900
A over here at site one,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

151
06:29.340 --> 06:30.900
A over here at site one,

152
06:30.900 --> 06:34.530
and one that would be used if traffic is going out through service provider B

153
06:34.530 --> 06:35.300
through site two.

154
06:35.300 --> 06:38.850
So once again, we'll go back to our global manager and let's create our two net

155
06:38.850 --> 06:39.380
rules.

156
06:39.380 --> 06:43.090
So back at the global manager, what we'll do is on the left, we're going to go

157
06:43.090 --> 06:43.780
down to

158
06:43.780 --> 06:48.000
net under network services. And then here, the main pane, if we had multiple T

159
06:48.000 --> 06:48.820
zero gateways,

160
06:48.820 --> 06:52.200
we could choose when we went to apply it to. So we only have one stretched T

161
06:52.200 --> 06:52.820
zero gateway,

162
06:52.820 --> 06:55.290
and that's the one right here. So let's like it. And then we'll click right

163
06:55.290 --> 06:57.060
here and add net rule.

164
06:57.060 --> 07:00.770
So we'll click on add net rule, and let's go ahead and collapse the left hand
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

164
06:57.060 --> 07:00.770
So we'll click on add net rule, and let's go ahead and collapse the left hand

165
07:00.770 --> 07:01.460
column to give us a

166
07:01.460 --> 07:05.420
little more room. And I'll call it a site one s net. And then the type is going

167
07:05.420 --> 07:06.580
to be source net.

168
07:06.580 --> 07:10.020
And then for the source IP address field right here, let's say any traffic that

169
07:10.020 --> 07:10.740
is source from

170
07:10.740 --> 07:14.740
10, anything. So we'll put 10 zero zero zero slash eight to represent we only

171
07:14.740 --> 07:15.540
care about matching on

172
07:15.540 --> 07:19.300
that first octet, the 10. And that way, if we have additional subnets under the

173
07:19.300 --> 07:20.020
10 network,

174
07:20.020 --> 07:24.180
those will be matched by this rule. And then let's also specify the translated

175
07:24.180 --> 07:24.980
IP address we want to

176
07:24.980 --> 07:29.760
use, which based on our plan was 23 dot 1 dot 2 dot 60. And then this becomes

177
07:29.760 --> 07:30.340
super important
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

177
07:29.760 --> 07:30.340
super important

178
07:30.340 --> 07:34.420
here. We want to go ahead and apply this only to the interfaces associated with

179
07:34.420 --> 07:35.460
site one. So in

180
07:35.460 --> 07:39.310
the apply to column here, we'll click on set. And then with site one selected,

181
07:39.310 --> 07:40.100
let's go ahead and

182
07:40.100 --> 07:44.830
choose the interfaces where we want to apply this. Now we could say apply rule

183
07:44.830 --> 07:45.860
to all entities of

184
07:45.860 --> 07:49.610
a selected site. However, as we get to the DHCP section, I'm going to create an

185
07:49.610 --> 07:50.260
additional

186
07:50.260 --> 07:53.660
interface where I don't want to use net on that interface. So I'm going to say

187
07:53.660 --> 07:54.580
don't apply it to

188
07:54.580 --> 07:59.140
everywhere, but do apply it to these two interfaces, which are at site one. So

189
07:59.140 --> 08:00.020
with those two interfaces
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

189
07:59.140 --> 08:00.020
with those two interfaces

190
08:00.020 --> 08:03.890
selected, we'll click on apply, then we'll scroll down, click on save. And now

191
08:03.890 --> 08:04.980
we have this new site

192
08:04.980 --> 08:09.220
one source net rule, and we'll create a similar rule for the benefit of site

193
08:09.220 --> 08:10.260
two, except for the

194
08:10.260 --> 08:15.790
translated address, we'll choose the 24 dot 1 dot 2 dot 60, instead of 23. And

195
08:15.790 --> 08:16.740
for the applies to,

196
08:16.740 --> 08:20.440
we'll choose the two interfaces associated with site two. So we'll click on add

197
08:20.440 --> 08:21.220
net rule,

198
08:21.220 --> 08:25.700
we'll call it site two source net. And for the type, we want to do source net.

199
08:25.700 --> 08:26.180
And for the source

200
08:26.180 --> 08:30.180
IP address, we'll use the same condition and a source traffic starting with 10,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

200
08:26.180 --> 08:30.180
IP address, we'll use the same condition and a source traffic starting with 10,

201
08:30.180 --> 08:30.900
anything would

202
08:30.900 --> 08:35.990
qualify. And for the translated address, we're use 24 dot 1 dot 2 dot 60. And

203
08:35.990 --> 08:37.300
then we want to use

204
08:37.300 --> 08:41.790
the apply to column here, click on set. And we want to associate this with the

205
08:41.790 --> 08:42.740
two interfaces

206
08:42.740 --> 08:46.500
over at site two. So with site two selected, we'll go ahead and choose those

207
08:46.500 --> 08:47.300
two interfaces,

208
08:47.300 --> 08:51.580
and click on apply, and we'll scroll down and click on save. All right, so now

209
08:51.580 --> 08:52.660
we have two

210
08:52.660 --> 08:57.020
source net rules, one for site one, one for site two. So any traffic source

211
08:57.020 --> 08:58.100
from 10, anything that's

212
08:58.100 --> 09:01.440
going up to the internet, if it's going through site one out through service
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

212
08:58.100 --> 09:01.440
going up to the internet, if it's going through site one out through service

213
09:01.440 --> 09:02.180
provider A, it's

214
09:02.180 --> 09:04.960
going to be natted to this address. And if it's going out to the internet

215
09:04.960 --> 09:06.260
through site two,

216
09:06.260 --> 09:10.820
it's going to be natted to 24 dot 1 dot 2 dot 60. So in our journey, we are at

217
09:10.820 --> 09:11.620
this point right

218
09:11.620 --> 09:16.730
here, we have the t zero created, we have the external interfaces on each site

219
09:16.730 --> 09:17.140
associated with

220
09:17.140 --> 09:21.280
that t zero gateway, we set up static default routes at site one and site two

221
09:21.280 --> 09:22.340
with their respective

222
09:22.340 --> 09:26.470
service providers. And we also set up source net rules for both site one and

223
09:26.470 --> 09:27.540
site two. So our

224
09:27.540 --> 09:30.790
next step in the journey is then to go ahead and create the stretch t one that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

224
09:27.540 --> 09:30.790
next step in the journey is then to go ahead and create the stretch t one that

225
09:30.790 --> 09:31.700
's connected to the

226
09:31.700 --> 09:35.880
t zero, we'll also go ahead and create this segment right here. And we get to

227
09:35.880 --> 09:37.060
do that configuration of

228
09:37.060 --> 09:41.720
adding this t zero gateway in the next video. So I'll see you there in just a

229
09:41.720 --> 09:42.260
moment.