WEBVTT

1
00:00.000 --> 00:05.080
Now, up to this point, we've identified five segment profiles that we can use

2
00:05.080 --> 00:05.600
to control

3
00:05.600 --> 00:08.880
traffic and control behavior of what's allowed on our network segments.

4
00:08.880 --> 00:12.480
And although the edge bridge profile isn't directly a profile that we had

5
00:12.480 --> 00:13.080
applied to

6
00:13.080 --> 00:16.910
a segment, it is a super handy tool and I wanted to give you an insight onto

7
00:16.910 --> 00:17.360
what it

8
00:17.360 --> 00:18.360
does.

9
00:18.360 --> 00:22.690
So let's imagine that we are migrating over to a VMware NSX environment and let

10
00:22.690 --> 00:23.400
's imagine

11
00:23.400 --> 00:27.800
we have a dozen or so VMs on this network segment of 10, 10, zero.

12
00:27.800 --> 00:29.720
At the same time, we have a VLAN.

13
00:29.720 --> 00:34.310
Let's go ahead and take a VLAN 25 from the physical world and let's take a few
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:29.720 --> 00:34.310
Let's go ahead and take a VLAN 25 from the physical world and let's take a few

14
00:34.310 --> 00:35.320
VMs here.

15
00:35.320 --> 00:39.900
And let's imagine that we want the VMs here in VLAN 25 to be on the same

16
00:39.900 --> 00:41.240
logical network,

17
00:41.240 --> 00:45.700
the same layer two effective broadcast domain as these VMs over here on this

18
00:45.700 --> 00:47.000
overlay segment.

19
00:47.000 --> 00:48.000
So how do we do that?

20
00:48.000 --> 00:52.480
And the answer is, we create an edge bridge profile.

21
00:52.480 --> 00:55.920
We specify the edge transport nodes we want involved with that.

22
00:55.920 --> 01:01.470
And then we simply say we want to link VLAN 25 with this segment and bada bing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:55.920 --> 01:01.470
And then we simply say we want to link VLAN 25 with this segment and bada bing

23
01:01.470 --> 01:02.360
bada boom.

24
01:02.360 --> 01:07.680
We then have one large broadcast domain from an IPv4 perspective.

25
01:07.680 --> 01:11.700
So these VMs over here believe they're on the same logical network as these VMs

26
01:11.700 --> 01:12.040
over

27
01:12.040 --> 01:15.510
here and behind the scenes, the traffic is going to be tunneled through an edge

28
01:15.510 --> 01:15.960
node who

29
01:15.960 --> 01:20.200
could do that bridging between this overlay segment and this VLAN.

30
01:20.200 --> 01:21.840
So here's what I propose we do as a demo.

31
01:21.840 --> 01:23.120
We already have this segment in place.

32
01:23.120 --> 01:25.200
We already have a couple of VMs that are running here.

33
01:25.200 --> 01:26.680
We'll make sure they still are.

34
01:26.680 --> 01:28.520
We also have DHCP services right here.

35
01:28.520 --> 01:33.420
So if we created an edge bridge profile that said we want to merge, if you will
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:28.520 --> 01:33.420
So if we created an edge bridge profile that said we want to merge, if you will

36
01:33.420 --> 01:34.320
, this overlay

37
01:34.320 --> 01:37.690
segment with this VLAN, we could then go ahead and take one of these devices

38
01:37.690 --> 01:38.280
over here and

39
01:38.280 --> 01:40.120
make it a DHCP client.

40
01:40.120 --> 01:42.660
And as a result, when it goes through the discover offer request

41
01:42.660 --> 01:44.080
acknowledgement process, that

42
01:44.080 --> 01:49.560
discover would be sent also over here to this overlay segment.

43
01:49.560 --> 01:53.150
At which point the DHCP services in NSX could hand out an IP address over here

44
01:53.150 --> 01:53.520
to these

45
01:53.520 --> 01:58.620
devices over here in VLAN 25 effectively making all of this VLAN 25 and this

46
01:58.620 --> 01:59.760
overlay segment

47
01:59.760 --> 02:02.880
one logical layer to broadcast to me.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
01:59.760 --> 02:02.880
one logical layer to broadcast to me.

48
02:02.880 --> 02:05.760
And to play the part of our little client out there in VLAN 25, I'm going to

49
02:05.760 --> 02:06.040
use my

50
02:06.040 --> 02:09.880
top of rack switch, which is currently supporting VLAN 25.

51
02:09.880 --> 02:13.540
And once we set up the edge bridge profile, we'll simply create a logical

52
02:13.540 --> 02:14.280
interface on

53
02:14.280 --> 02:18.530
my multi layer switch and say, you know what, for VLAN 25, be a DHCP client and

54
02:18.530 --> 02:19.120
we can then

55
02:19.120 --> 02:23.440
verify we can get an IP address via DHCP on the multi layer switch.

56
02:23.440 --> 02:26.240
So let's begin on the outside physical network.

57
02:26.240 --> 02:30.240
And this is a 3750 top of rack switch that I have in my lab environment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:26.240 --> 02:30.240
And this is a 3750 top of rack switch that I have in my lab environment.

58
02:30.240 --> 02:33.360
And so currently these are our logical layer three interfaces.

59
02:33.360 --> 02:37.520
And you'll notice we do not have a layer three interface for VLAN 25.

60
02:37.520 --> 02:41.280
So I'm going to go ahead and create one by typing interface VLAN 25.

61
02:41.280 --> 02:44.480
Let me also do a terminal monitor so I can actually see the console messages as

62
02:44.480 --> 02:44.760
they

63
02:44.760 --> 02:45.760
come up.

64
02:45.760 --> 02:49.330
So now if we do a show IP interface brief, exclude unassigned interface, VLAN

65
02:49.330 --> 02:50.000
25 still

66
02:50.000 --> 02:52.160
doesn't show up because we don't have an IP address.

67
02:52.160 --> 02:56.930
So let's go ahead and now that we're in interface VLAN 25, let's do an IP

68
02:56.930 --> 02:58.800
address, DHCP press

69
02:58.800 --> 02:59.800
enter.

70
02:59.800 --> 03:04.000
And that effectively is making this logical layer three interface in VLAN 25.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
02:59.800 --> 03:04.000
And that effectively is making this logical layer three interface in VLAN 25.

71
03:04.000 --> 03:06.280
It's making it a DHCP client.

72
03:06.280 --> 03:09.480
So we did a show IP interface brief and press enter.

73
03:09.480 --> 03:11.200
There's our interface VLAN 25.

74
03:11.200 --> 03:12.520
It's currently unassigned.

75
03:12.520 --> 03:15.720
It needs a DHCP server to basically hand out information.

76
03:15.720 --> 03:18.620
And then on this multi layer switch, we could do a debug just to see the

77
03:18.620 --> 03:19.520
details regarding

78
03:19.520 --> 03:23.750
DHCP activity, just to verify in the background that it is doing the discover

79
03:23.750 --> 03:24.480
looking for

80
03:24.480 --> 03:27.840
a DHCP server, but nobody's there to answer that call.

81
03:27.840 --> 03:31.560
And so fantastic unknown DHCP problem, no allocation possible.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
03:27.840 --> 03:31.560
And so fantastic unknown DHCP problem, no allocation possible.

82
03:31.560 --> 03:32.560
All right.

83
03:32.560 --> 03:35.830
So after a few seconds, I'm going to type in undibug all to turn off the

84
03:35.830 --> 03:36.640
debugging.

85
03:36.640 --> 03:40.700
So what's showing us is that this multi layer switch is setting a broadcast on

86
03:40.700 --> 03:42.040
the VLAN 25

87
03:42.040 --> 03:45.730
interface, effectively asking if there's any DHCP servers, in which case if

88
03:45.730 --> 03:46.400
there was a

89
03:46.400 --> 03:51.060
DHCP server or relay on that network segment, a DHCP server could respond back

90
03:51.060 --> 03:51.640
and this

91
03:51.640 --> 03:53.520
multi layer switch could get a IP address.

92
03:53.520 --> 03:58.540
However, at the moment, we have no binding or no connectivity between VLAN 25

93
03:58.540 --> 03:59.000
in the

94
03:59.000 --> 04:01.920
physical world and our logical segment 10.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
03:59.000 --> 04:01.920
physical world and our logical segment 10.

95
04:01.920 --> 04:05.810
So we're going to solve that right now by going to NSX manager and creating an

96
04:05.810 --> 04:06.160
edge

97
04:06.160 --> 04:07.600
bridge profile.

98
04:07.600 --> 04:11.130
So here in the NSX manager, we're going to click on the networking tab once

99
04:11.130 --> 04:11.720
again.

100
04:11.720 --> 04:15.320
And then on the left, we're going to click on segments under connectivity.

101
04:15.320 --> 04:18.180
And then once we've clicked on segments, we're going to use the sub tab under

102
04:18.180 --> 04:18.640
segments

103
04:18.640 --> 04:21.680
over here in the main pane and click on profiles.

104
04:21.680 --> 04:24.950
And here are the segment profiles that we've been playing with up to this point

105
04:24.950 --> 04:25.040
.

106
04:25.040 --> 04:28.800
But we also have as a sub tab here the edge bridge profile.

107
04:28.800 --> 04:33.130
And that's what's going to bind an overlay segment with one or more of our VLAN
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

107
04:28.800 --> 04:33.130
And that's what's going to bind an overlay segment with one or more of our VLAN

108
04:33.130 --> 04:33.440
s.

109
04:33.440 --> 04:37.220
So with the edge bridge profile selected, we're going to click on add to add

110
04:37.220 --> 04:37.680
one.

111
04:37.680 --> 04:41.160
So for the name, let's call this our BP for our bridge profile.

112
04:41.160 --> 04:43.960
We'll select the edge cluster we want to use.

113
04:43.960 --> 04:46.760
And inside that edge cluster, there's edge one and edge two.

114
04:46.760 --> 04:49.800
So for the primary node, we'll pick on edge one for the backup node.

115
04:49.800 --> 04:52.720
We'll pick edge two and then we'll click on safe.

116
04:52.720 --> 04:56.170
So now we have this bridge profile that when called upon is going to be using

117
04:56.170 --> 04:56.640
our edge

118
04:56.640 --> 05:01.000
one and edge two to bridge the overlay segment and the VLAN together.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

118
04:56.640 --> 05:01.000
one and edge two to bridge the overlay segment and the VLAN together.

119
05:01.000 --> 05:04.720
And to specify which segment and which VLAN we're going to go back to the NSX

120
05:04.720 --> 05:05.120
sub tab

121
05:05.120 --> 05:06.600
here for segments.

122
05:06.600 --> 05:08.680
And let's go ahead and choose segment 10.

123
05:08.680 --> 05:12.080
This is the segment 10 that we have a couple of VMs connected to.

124
05:12.080 --> 05:15.960
So we'll click on the three dots, we'll click on edit to edit our segment.

125
05:15.960 --> 05:18.120
We'll scroll down and check it out right here.

126
05:18.120 --> 05:20.240
We have a section called additional settings.

127
05:20.240 --> 05:21.440
We're going to expand that.

128
05:21.440 --> 05:25.480
And then here under additional settings, we have an option for edge bridges.

129
05:25.480 --> 05:30.000
We'll click on set and then we'll simply go ahead and click on add edge bridge.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

130
05:30.000 --> 05:31.560
We'll specify the profile.

131
05:31.560 --> 05:33.400
So here's our bridge profile right there.

132
05:33.400 --> 05:34.400
We'll select that.

133
05:34.400 --> 05:36.400
Then we're going to specify our transport zone.

134
05:36.400 --> 05:40.040
And that transport zone is not limited to specific VLANs.

135
05:40.040 --> 05:42.240
So we can include VLAN 25 as part of that.

136
05:42.240 --> 05:45.530
And then over here in the VLAN section, we'll specify the actual VLAN that we

137
05:45.530 --> 05:46.040
wanted it

138
05:46.040 --> 05:47.040
to be a part of.

139
05:47.040 --> 05:50.890
So effectively, this overlay segment and this VLAN 25 are going to be

140
05:50.890 --> 05:52.040
effectively merged

141
05:52.040 --> 05:53.840
together by the edge nodes.

142
05:53.840 --> 05:56.970
So we'll click on add, we'll click on apply, and then we'll scroll down, we'll

143
05:56.970 --> 05:57.480
click on

144
05:57.480 --> 05:58.480
save.

145
05:58.480 --> 06:01.280
And let me bring back my terminal over to our switch.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

145
05:58.480 --> 06:01.280
And let me bring back my terminal over to our switch.

146
06:01.280 --> 06:02.280
So here's our switch.

147
06:02.280 --> 06:06.520
And in just a moment, when this guy does a broadcast again to discover a DHCP

148
06:06.520 --> 06:07.200
server,

149
06:07.200 --> 06:08.720
this time there should be a response.

150
06:08.720 --> 06:11.640
So I'm going to put back on the debug for DHCP detail.

151
06:11.640 --> 06:13.360
And then we can see the play by play.

152
06:13.360 --> 06:16.280
The moment this multi-layer switch tries again.

153
06:16.280 --> 06:20.140
Another option would be to go to that logical VLAN 25 interface, shut it down,

154
06:20.140 --> 06:20.600
bring it

155
06:20.600 --> 06:22.480
back up, and that would trigger it as well.

156
06:22.480 --> 06:23.640
All right, and there it goes.

157
06:23.640 --> 06:26.600
Let me do an undibug all to turn off the debugging.

158
06:26.600 --> 06:28.320
And let's look at the play by play.

159
06:28.320 --> 06:29.640
So if we scroll up here.

160
06:29.640 --> 06:33.040
So here we have the discover made by the multi-layer switch.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

160
06:29.640 --> 06:33.040
So here we have the discover made by the multi-layer switch.

161
06:33.040 --> 06:34.480
And then we received an offer.

162
06:34.480 --> 06:36.680
And in that offer, it said, hey, here's the details.

163
06:36.680 --> 06:40.800
Here's the default gateway address, the DNS server, the mask.

164
06:40.800 --> 06:45.320
And here's the IP address that I want to go ahead and hand out to you, the 101

165
06:45.320 --> 06:45.840
52, at

166
06:45.840 --> 06:49.690
which point if we scroll down, the multi-layer switch did a request, say, yep,

167
06:49.690 --> 06:50.360
I'd love to

168
06:50.360 --> 06:51.360
take it.

169
06:51.360 --> 06:55.640
And then that got followed up with an acknowledgement, which is right here,

170
06:55.640 --> 06:56.840
which is our NSX DHCP

171
06:56.840 --> 07:00.920
services, feeding back a confirmation saying, yep, I know you got to enjoy it.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

171
06:56.840 --> 07:00.920
services, feeding back a confirmation saying, yep, I know you got to enjoy it.

172
07:00.920 --> 07:04.640
So now if we did a show IP interface brief, and then if we asked it to exclude

173
07:04.640 --> 07:05.240
any output

174
07:05.240 --> 07:08.340
that has the word unassigned in it, then it'll just show us the interfaces with

175
07:08.340 --> 07:09.160
IP addresses.

176
07:09.160 --> 07:12.680
So there's our VLAN 25 at 1010152.

177
07:12.680 --> 07:16.800
And we do have ping over to 10.10.0.1.

178
07:16.800 --> 07:18.240
That's our default gateway.

179
07:18.240 --> 07:19.800
That works no problem.

180
07:19.800 --> 07:23.000
And if we ping another VM on that same subnet, in fact, let's go grab a little

181
07:23.000 --> 07:23.960
VM right here.

182
07:23.960 --> 07:25.600
We'll do an IF config.

183
07:25.600 --> 07:28.200
So it's at 1010151.

184
07:28.200 --> 07:33.970
So if we try to ping to 10151, this is our top of rack multi-layer switch on V
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

184
07:28.200 --> 07:33.970
So if we try to ping to 10151, this is our top of rack multi-layer switch on V

185
07:33.970 --> 07:34.780
LAN 23

186
07:34.780 --> 07:40.260
pinging directly the client on segment 10 at 10151.

187
07:40.260 --> 07:44.810
And on a Cisco device that initial ping, for example, right there and right

188
07:44.810 --> 07:45.400
there, that's

189
07:45.400 --> 07:47.360
being consumed during the ARP request.

190
07:47.360 --> 07:49.980
So if we did it again, we should get five out of five.

191
07:49.980 --> 07:53.400
And that's the magic of an edge bridge profile to bind together, to bridge

192
07:53.400 --> 07:54.140
together into

193
07:54.140 --> 07:58.980
one layer two broadcast domain, overlay segments, and external VLANs where

194
07:58.980 --> 08:00.000
physical clients
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

195
08:00.000 --> 08:00.620
may exist.