WEBVTT

1
00:00.000 --> 00:02.920
So let's begin with our QOS segment profile.

2
00:02.920 --> 00:05.120
So let's use a little VM over here.

3
00:05.120 --> 00:07.200
Let's go ahead and grab Mint 10.

4
00:07.200 --> 00:09.760
We'll make sure it's on the green segment right here

5
00:09.760 --> 00:11.360
that it has access to the internet.

6
00:11.360 --> 00:13.400
And before we implement QOS,

7
00:13.400 --> 00:16.640
I'd like to do a couple of baseline tests regarding this VM.

8
00:16.640 --> 00:18.520
So here I'll jot down before,

9
00:18.520 --> 00:21.600
and then we can go afterwards and take a look at the results after,

10
00:21.600 --> 00:23.600
meaning after we apply the QOS segment profile.

11
00:23.600 --> 00:27.680
So before, what we would expect to see for the traffic being sent by this VM,

12
00:27.680 --> 00:31.760
as far as the differentiated services code point or DSCP markings,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:27.680 --> 00:31.760
as far as the differentiated services code point or DSCP markings,

13
00:31.760 --> 00:32.800
they should all be zeros.

14
00:32.800 --> 00:36.880
So there's six bits that are being used for these markings in the IP header,

15
00:36.880 --> 00:38.880
and they should all be zeros by default.

16
00:38.880 --> 00:42.560
And as far as bandwidth is concerned from this VM, getting up to the internet,

17
00:42.560 --> 00:43.520
there's no restrictions.

18
00:43.520 --> 00:46.560
So whatever the bandwidth limitations that are currently in place,

19
00:46.560 --> 00:49.840
either through my service provider or through other congestion in the network,

20
00:49.840 --> 00:52.320
the bandwidth is going to be up to the max.

21
00:52.320 --> 00:54.800
Or at least within this environment right here,

22
00:54.800 --> 00:59.450
whatever this maximum capacity is that can be provided by my little nested NSX

23
00:59.450 --> 01:00.560
environment right here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:59.450 --> 01:00.560
environment right here.

24
01:00.560 --> 01:02.640
So let's set this up for Mint 10.

25
01:02.640 --> 01:05.920
So our first order of business is to make sure that Mint 10 is on the right

26
01:05.920 --> 01:06.400
segment.

27
01:06.400 --> 01:07.440
This is the vSphere client,

28
01:07.440 --> 01:09.760
and also to make sure that it's powered on.

29
01:09.760 --> 01:10.720
So let's take a look real quick.

30
01:10.720 --> 01:12.400
We'll right click on Mint 10.

31
01:12.400 --> 01:14.320
We'll click on edit settings,

32
01:14.320 --> 01:17.200
and it is connected to the green segment 10.

33
01:17.200 --> 01:18.560
So I don't need to change that.

34
01:18.560 --> 01:22.560
We'll cancel that, and let's power it up by clicking on the power on icon here.

35
01:22.560 --> 01:25.040
And now that it's powering up, let's also right click,

36
01:25.040 --> 01:27.120
and let's open up a remote console.

37
01:27.120 --> 01:30.400
So here is that little VM it is still booting up.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

37
01:27.120 --> 01:30.400
So here is that little VM it is still booting up.

38
01:30.400 --> 01:33.280
So for this Mint 10 computer, which is on our green segment,

39
01:33.280 --> 01:35.360
let's go ahead and open up a browser.

40
01:35.360 --> 01:38.400
And I've got a shortcut for a speed test at fast.com.

41
01:38.400 --> 01:40.960
So we'll launch that from the bookmarks there.

42
01:40.960 --> 01:44.000
And that is now going out to the live internet.

43
01:44.000 --> 01:47.760
We have somewhere between, I don't know, 400 and 600 megabits per second.

44
01:47.760 --> 01:49.040
It looks like fantastic.

45
01:49.040 --> 01:52.160
So that's uninhibited as far as the bandwidth is concerned.

46
01:52.160 --> 01:54.160
So we go ahead and close that.

47
01:54.160 --> 01:56.160
And then next, let me open up a command prompt.

48
01:56.160 --> 01:59.120
And let's do a ping out to 888.

49
01:59.120 --> 02:00.880
Now the reason I want to do this is because in the background,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
01:59.120 --> 02:00.880
Now the reason I want to do this is because in the background,

50
02:00.880 --> 02:04.640
I'm doing a packet capture, and it's really easy to filter on just IC and P

51
02:04.640 --> 02:05.120
traffic.

52
02:05.120 --> 02:09.280
And that way we can take a close look at the markings for those packets

53
02:09.280 --> 02:11.280
as they're being sent over the green segment.

54
02:11.280 --> 02:14.160
So we'll go ahead and do that ping, and that ping is working.

55
02:14.160 --> 02:15.760
So we'll do a control C there.

56
02:15.760 --> 02:18.320
So next, let's take a look at a packet capture of that traffic

57
02:18.320 --> 02:20.480
and take a look at the DSCP markings.

58
02:20.480 --> 02:22.080
So here is the packet capture.

59
02:22.080 --> 02:24.720
Let me go ahead and do a display filter just for ICMP.

60
02:24.720 --> 02:30.480
And there is our Mint VM computer at 1010 0183 going out to 888.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
02:24.720 --> 02:30.480
And there is our Mint VM computer at 1010 0183 going out to 888.

61
02:30.480 --> 02:35.120
So everything up to here is just the environment setting the packets using GRE

62
02:35.120 --> 02:37.440
over to my management computer so we can see them right here.

63
02:37.440 --> 02:39.280
And then we had the details about what's being sent.

64
02:39.280 --> 02:41.760
So this is traffic from 1111, et cetera.

65
02:41.760 --> 02:45.840
That's ES6IA going to our edge node edge one at 3333.

66
02:45.840 --> 02:47.200
That's the set of line points involved.

67
02:47.200 --> 02:50.000
Here's our layer four protocol, UDP going to the well-known port

68
02:50.000 --> 02:52.160
for Geneva of 6081.

69
02:52.160 --> 02:54.320
And here's our Geneva header information.

70
02:54.320 --> 02:56.560
And then within that, we have yet another IP header.

71
02:56.560 --> 02:59.910
So in this IP header right here, the one that's going over the transport

72
02:59.910 --> 03:00.480
network,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
02:59.910 --> 03:00.480
network,

73
03:00.480 --> 03:03.600
if we go down here to the differentiated services field right there

74
03:03.600 --> 03:05.920
and expand that, they are all zeros.

75
03:05.920 --> 03:09.440
So there's the six bits right there that are being used for DSCP.

76
03:09.440 --> 03:13.920
So for the transport network journey from ES6IA over to edge one,

77
03:13.920 --> 03:15.680
all those bits are set to zero.

78
03:15.680 --> 03:19.920
And if we look down at the IP header that's being carried in that payload,

79
03:19.920 --> 03:22.000
we'll expand that and scroll down.

80
03:22.000 --> 03:26.600
You'll notice here that the DSCP information is the same, all zeros, as shown

81
03:26.600 --> 03:27.440
right here.

82
03:27.440 --> 03:31.120
So regarding these six bits as part of the DSCP header information,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

82
03:27.440 --> 03:31.120
So regarding these six bits as part of the DSCP header information,

83
03:31.120 --> 03:33.920
if we line those up, there's all six of them right there.

84
03:33.920 --> 03:39.360
They have the decimal values of 1, 2, 4, 8, 16 and 32.

85
03:39.360 --> 03:43.840
So if we specify for our QOS segment profile that we want to modify

86
03:43.840 --> 03:49.450
the existing DSCP bits, and let's say for example that we set it to 46 in

87
03:49.450 --> 03:50.080
decimal.

88
03:50.080 --> 03:54.800
Behind the scenes, what that would do, it would set these bits to 46 minus 32.

89
03:54.800 --> 03:59.130
There's 14, there'll be a zero there, and then 8 goes into 14, there'll be a 1

90
03:59.130 --> 03:59.360
there,

91
03:59.360 --> 04:00.480
so minus the 8.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
03:59.360 --> 04:00.480
so minus the 8.

92
04:00.480 --> 04:03.520
And that's the remainder of 6 and 4 goes into that one time.

93
04:03.520 --> 04:06.840
So I'll take that other's 2 left and there'll be 1 here and then there'll be a

94
04:06.840 --> 04:07.360
0 here.

95
04:07.360 --> 04:11.350
So what we would expect is if we go in and we specify as part of our QOS

96
04:11.350 --> 04:12.320
segment profile

97
04:12.320 --> 04:16.080
that we want to change the DSCP bits to 46,

98
04:16.080 --> 04:20.320
behind the scenes for each of the packets coming from that VM, or for any VMs

99
04:20.320 --> 04:21.200
on that segment.

100
04:21.200 --> 04:25.370
If the QOS profile says that the DSCP to 46, each of the packets coming from

101
04:25.370 --> 04:26.000
those VMs

102
04:26.000 --> 04:28.160
is going to have this sequence of ones and zeros.

103
04:28.160 --> 04:31.520
And again, these sequences of ones and zeros mean pretty much nothing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
04:28.160 --> 04:31.520
And again, these sequences of ones and zeros mean pretty much nothing

104
04:31.520 --> 04:35.480
to the rest of the network unless the other routers have been trained to take a

105
04:35.480 --> 04:36.000
peek

106
04:36.000 --> 04:41.120
at that DSCP value and based on congestion, giving preferential treatment

107
04:41.120 --> 04:43.360
to traffic with those bits.

108
04:43.360 --> 04:47.280
Also, it's important to note that if we have traffic on the same ESXi host,

109
04:47.280 --> 04:52.440
for example, we have ESXi A here and we have, let's say, VM1 here and VM2 right

110
04:52.440 --> 04:52.960
here,

111
04:52.960 --> 04:55.840
if there's traffic that the hypervisor is routing itself,

112
04:55.840 --> 04:58.640
it's not really going to matter what we have in our DSCP bits because this can

113
04:58.640 --> 04:59.120
be super

114
04:59.120 --> 05:02.320
passed on the backplane here of the ESXi host.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

114
04:59.120 --> 05:02.320
passed on the backplane here of the ESXi host.

115
05:02.320 --> 05:06.480
However, when we need to send traffic to another host like ESXi B,

116
05:06.480 --> 05:10.080
or we need to send it up to an edge node such as edge one,

117
05:10.080 --> 05:13.440
when it's going over the tunnel network, at that point, that's when those DSCP

118
05:13.440 --> 05:14.480
bits will be set

119
05:14.480 --> 05:16.400
based on our QOS segment profile.

120
05:16.400 --> 05:21.040
So with that in mind, let's go to the NSX manager, let's create a QOS segment

121
05:21.040 --> 05:21.680
profile

122
05:21.680 --> 05:25.040
and apply it to our green segment and then we'll compare and contrast.

123
05:25.040 --> 05:28.640
So here in the NSX manager, we're going to go to the networking tab

124
05:28.640 --> 05:32.560
and let's start by going to our segments on the left, we'll click on segments
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
05:28.640 --> 05:32.560
and let's start by going to our segments on the left, we'll click on segments

125
05:32.560 --> 05:35.920
and let's go down to our green segment 10, which is right here

126
05:35.920 --> 05:38.160
and let's take a look at what's currently in place.

127
05:38.160 --> 05:42.320
So we expand green segment 10 and then if we go down to segment profiles and

128
05:42.320 --> 05:44.000
expand that even further,

129
05:44.000 --> 05:49.280
here are the four default segment profiles that are applied for IP discovery,

130
05:49.280 --> 05:51.760
spoof guard, Mac discovery and segment security.

131
05:51.760 --> 05:56.000
However, you'll notice that for QOS, there isn't one by default.

132
05:56.000 --> 05:58.480
So what we could do is we could go up to profiles right here.

133
05:58.480 --> 06:02.880
So that's networking segments profiles and then click on the sub tab here for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

133
05:58.480 --> 06:02.880
So that's networking segments profiles and then click on the sub tab here for

134
06:02.880 --> 06:03.760
segment profiles

135
06:03.760 --> 06:08.060
and simply create a new one and then apply that or we could just go back to the

136
06:08.060 --> 06:09.040
segment itself

137
06:09.040 --> 06:11.920
and here in the segment, we could edit the details for that segment.

138
06:11.920 --> 06:15.360
So I'll click on the three dots, we'll click on edit and then for green segment

139
06:15.360 --> 06:15.840
10,

140
06:15.840 --> 06:19.600
if we scroll down and take a look at the segment profiles from here, we can go

141
06:19.600 --> 06:20.240
ahead and simply

142
06:20.240 --> 06:23.600
create one by clicking on the three dots next to QOS.

143
06:23.600 --> 06:27.190
And if we had an existing QOS segment profile, we could click on view, but

144
06:27.190 --> 06:27.840
there isn't one.

145
06:27.840 --> 06:30.640
So we could go ahead and simply create one right here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

145
06:27.840 --> 06:30.640
So we could go ahead and simply create one right here.

146
06:30.640 --> 06:34.640
So we'll click on create new, we'll call this our QOS segment profile and I'm

147
06:34.640 --> 06:34.960
putting on a

148
06:34.960 --> 06:39.020
leading period just so that when we sort in the output, it'll be at the very

149
06:39.020 --> 06:40.160
top and easy to find

150
06:40.160 --> 06:44.900
and for DSCP value, instead of saying just trust what is currently on the

151
06:44.900 --> 06:45.840
actual IP header

152
06:45.840 --> 06:49.470
information for the DSCP value, I'm going to say untrusted and then let's go

153
06:49.470 --> 06:51.040
ahead and change it.

154
06:51.040 --> 06:55.600
So for priority, I'm going to put 46 in decimal, which in binary for those six

155
06:55.600 --> 06:56.240
bits

156
06:56.240 --> 07:00.240
is going to map out to the 101, 110 as we looked at a moment ago.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

156
06:56.240 --> 07:00.240
is going to map out to the 101, 110 as we looked at a moment ago.

157
07:00.240 --> 07:02.800
So the priority is referring to the DSCP bits.

158
07:02.800 --> 07:06.320
And then for the bandwidth reduction, currently our VM was getting close to

159
07:06.320 --> 07:07.280
like 500 megabits

160
07:07.280 --> 07:11.240
per second. Let's go ahead and set up some limitations regarding how much

161
07:11.240 --> 07:11.840
bandwidth that

162
07:11.840 --> 07:15.680
client is able to use. This would also apply to any other VMs on that segment.

163
07:15.680 --> 07:20.720
So for ingress, Neagress, let's go ahead and use an average of 10 megabits per

164
07:20.720 --> 07:21.200
second.

165
07:21.200 --> 07:24.390
So I'll put 10 for both of those. And then for the peak, let's go ahead and

166
07:24.390 --> 07:25.600
specify 20

167
07:25.600 --> 07:28.900
megabits per second for each of those. And then for the burst, in case they

168
07:28.900 --> 07:29.280
have something

169
07:29.280 --> 07:31.630
they need to send really quick and we don't want it all to be killed, let's go
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

169
07:29.280 --> 07:31.630
they need to send really quick and we don't want it all to be killed, let's go

170
07:31.630 --> 07:32.560
ahead and limit that

171
07:32.560 --> 07:37.050
to 30. So for the values for inbound and outbound traffic from the VM's

172
07:37.050 --> 07:37.840
perspective,

173
07:37.840 --> 07:41.300
we're going to limit it pretty much to an average of 10 megabits per second

174
07:41.300 --> 07:42.000
with the ability for

175
07:42.000 --> 07:45.430
short period of time to burst if needed. And what we'll do is we'll click on

176
07:45.430 --> 07:45.920
save.

177
07:45.920 --> 07:48.960
So once we click on save here, we're now going to be effectively applying this

178
07:48.960 --> 07:50.240
QOS policy

179
07:50.240 --> 07:54.530
to all the VMs on that segment. So we'll click on save, and then we'll scroll

180
07:54.530 --> 07:54.720
down,

181
07:54.720 --> 07:58.880
click on close editing, and then just to confirm, we'll expand green segment 10

182
07:58.880 --> 07:58.880
,

183
07:59.280 --> 08:02.850
scroll down, and then under segment profiles, we'll expand that just to confirm
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

183
07:59.280 --> 08:02.850
scroll down, and then under segment profiles, we'll expand that just to confirm

184
08:02.850 --> 08:03.520
that we have

185
08:03.520 --> 08:07.230
our QOS segment profile right there, which we do. All right, so now that we

186
08:07.230 --> 08:08.000
have that QOS

187
08:08.000 --> 08:11.750
segment profile in place, let's test it out. Let's start off by going back to

188
08:11.750 --> 08:12.960
that same computer.

189
08:12.960 --> 08:18.190
This is mint 10. We'll open a browser once again, and we'll go to fast.com once

190
08:18.190 --> 08:18.880
again.

191
08:18.880 --> 08:22.640
And this time we should be limited to somewhere around 10 megabits per second

192
08:22.640 --> 08:23.360
because of the

193
08:23.360 --> 08:27.770
QOS segment profile that we have associated with the green segment. All right,

194
08:27.770 --> 08:28.560
so we've been

195
08:28.560 --> 08:33.340
limited there. And let's also go ahead and do a ping out to Google.com. And I
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

195
08:28.560 --> 08:33.340
limited there. And let's also go ahead and do a ping out to Google.com. And I

196
08:33.340 --> 08:33.920
'll capture that

197
08:33.920 --> 08:37.920
traffic in the background so we can take a look at the change in those DSCP

198
08:37.920 --> 08:39.440
values in the IP headers.

199
08:39.440 --> 08:42.960
So back at our client, let's go ahead and do that ping again on his one or two

200
08:42.960 --> 08:43.920
ICMP packets.

201
08:43.920 --> 08:48.320
Fantastic. And let's go take a look at those in the packet capture. So here is

202
08:48.320 --> 08:48.960
that packet

203
08:48.960 --> 08:51.980
capture. I mean, make that a little bit bigger. And let's go ahead and grab

204
08:51.980 --> 08:52.800
this first one right

205
08:52.800 --> 08:55.960
here. That's from our client going out to 888. And so for the part here

206
08:55.960 --> 08:56.880
regarding saying the

207
08:56.880 --> 09:00.790
traffic to my computer and using GRE, that's all about wrapping up the traffic
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

207
08:56.880 --> 09:00.790
traffic to my computer and using GRE, that's all about wrapping up the traffic

208
09:00.790 --> 09:01.680
and shipping it over

209
09:01.680 --> 09:04.560
to this management machine that we're sitting at right here. So as we look at

210
09:04.560 --> 09:05.360
the tunnel traffic

211
09:05.360 --> 09:10.790
here from ESXIA over to edge one based on the tunnel endpoint addresses. Now if

212
09:10.790 --> 09:11.280
we take a look

213
09:11.280 --> 09:16.050
at the DSCP field and we expand that check it out, we have it set effectively

214
09:16.050 --> 09:17.440
to 46. So here's what

215
09:17.440 --> 09:21.500
that means. As this packet goes out into the real world and real routers see it

216
09:21.500 --> 09:22.640
. If those routers

217
09:22.640 --> 09:26.020
have been trained to pay attention to those markings, they can then based on

218
09:26.020 --> 09:26.800
their policies,

219
09:26.800 --> 09:30.560
implement preferential treatment for those packets as they're being forwarded.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

219
09:26.800 --> 09:30.560
implement preferential treatment for those packets as they're being forwarded.

220
09:30.560 --> 09:31.200
And most of the time

221
09:31.200 --> 09:35.170
is trying to prioritize certain types of traffic because it's real time like

222
09:35.170 --> 09:36.160
voice over IP or

223
09:36.160 --> 09:40.480
something else that really doesn't work well if there's tons of delay or jitter

224
09:40.480 --> 09:41.360
. So that information

225
09:41.360 --> 09:44.920
is the header for the traffic as it went over the tunnel. It's also applied to

226
09:44.920 --> 09:45.760
the inner header

227
09:45.760 --> 09:49.290
right here as well. So if we open up the payload here inside the tunnel and we

228
09:49.290 --> 09:50.480
go down to DSCP

229
09:50.480 --> 09:53.870
one more time right here and expand it, once again we have those same bits

230
09:53.870 --> 09:54.400
being set.

231
09:54.400 --> 09:59.600
And also before I forget I want to go ahead and take off that QOS segment

232
09:59.600 --> 10:00.720
profile because
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

232
09:59.600 --> 10:00.720
profile because

233
10:00.720 --> 10:03.510
in the future, if I'm sending traffic from the green segment, I'm going to

234
10:03.510 --> 10:04.400
wonder why I'm only

235
10:04.400 --> 10:07.950
getting 10 megabits per second. So I'm going to go ahead and we'll go back to

236
10:07.950 --> 10:08.880
our green segment,

237
10:08.880 --> 10:12.980
click on the three dots, click on edit and scroll down, expand the segment

238
10:12.980 --> 10:14.000
profiles if it isn't

239
10:14.000 --> 10:17.810
already. And then for our QOS segment profile, I'll go ahead and from the drop

240
10:17.810 --> 10:18.800
down, choose none,

241
10:18.800 --> 10:23.520
click on save and then click on close editing and just for sanity purposes,

242
10:23.520 --> 10:27.080
let's also just test from our VM once again to make sure we have all the

243
10:27.080 --> 10:28.400
bandwidth that's available

244
10:28.400 --> 10:33.040
to it. So we'll go back to fast.com and I'm looking for something over 10 megab
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

244
10:28.400 --> 10:33.040
to it. So we'll go back to fast.com and I'm looking for something over 10 megab

245
10:33.040 --> 10:34.320
its. Fantastic.

246
10:34.320 --> 10:39.040
So that looks like it is no longer being constrained by our QOS segment profile

247
10:39.040 --> 10:40.320
. Also as one other

248
10:40.320 --> 10:45.280
note, if we wanted to override for a specific VM, the details regarding QOS,

249
10:45.280 --> 10:45.920
what we could do is

250
10:45.920 --> 10:49.320
we could go to this green segment 10, expand it. And then if we scroll to the

251
10:49.320 --> 10:50.160
right a little bit,

252
10:50.160 --> 10:53.120
here we have a column for ports slash interface. Let me go ahead and collapse

253
10:53.120 --> 10:53.760
the left hand side,

254
10:53.760 --> 10:56.720
gives a little more room here. So that's referring to who's currently connected

255
10:56.720 --> 10:57.600
. So if we click right

256
10:57.600 --> 11:00.940
here on this hyperlink for two, it's going to show us that we have two VMs that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

256
10:57.600 --> 11:00.940
here on this hyperlink for two, it's going to show us that we have two VMs that

257
11:00.940 --> 11:01.760
are currently

258
11:01.760 --> 11:06.090
connected. So here's our mint 10 machine right here. And if we expand that and

259
11:06.090 --> 11:07.040
scroll down here,

260
11:07.040 --> 11:11.140
it's showing us if we expand the segment port profiles that it's inheriting the

261
11:11.140 --> 11:11.760
settings

262
11:11.760 --> 11:14.540
from the actual segment. So if we wanted to override it, what we could do is we

263
11:14.540 --> 11:15.440
could go ahead

264
11:15.440 --> 11:18.910
and click on edit by clicking here in the three dots, clicking on edit

265
11:18.910 --> 11:19.680
scrolling down,

266
11:19.680 --> 11:23.330
instead of inheriting it from the parent, we want to go ahead and assign it. So

267
11:23.330 --> 11:23.600
that's how

268
11:23.600 --> 11:27.460
you could override which segment port profile they're going to be using. So in

269
11:27.460 --> 11:27.920
this case,

270
11:27.920 --> 11:30.240
I don't want to do that for this VM. I don't want to limit it. So I'm going to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

270
11:27.920 --> 11:30.240
I don't want to do that for this VM. I don't want to limit it. So I'm going to

271
11:30.240 --> 11:31.120
say inherit.

272
11:31.120 --> 11:34.070
In fact, I'm going to click on cancel here. I just wanted to share with you

273
11:34.070 --> 11:35.040
where you would go to

274
11:35.040 --> 11:39.920
set the individual overrides regarding a segment profile for a specific VM.

275
11:39.920 --> 11:49.920
[BLANK_AUDIO]