WEBVTT

1
00:00.000 --> 00:03.940
So based on this customer scenario where they say one of the VMs is acting

2
00:03.940 --> 00:04.400
slower,

3
00:04.400 --> 00:08.000
we may want to take a moment and just verify that's the case.

4
00:08.000 --> 00:12.200
So let's take a look at the vSphere and also the NS6 environment,

5
00:12.200 --> 00:16.780
and let's also test these VMs to verify and compare their speed as they both go

6
00:16.780 --> 00:17.600
out to the Internet.

7
00:17.600 --> 00:20.900
So here in the vSphere client, let's go to the networks tab right here

8
00:20.900 --> 00:24.000
and let's go to that segment which is blue segment 20.

9
00:24.000 --> 00:28.000
There's our two VMs and I also want to confirm which hosts they're running on.

10
00:28.000 --> 00:33.700
So ESXIA is the compute resource for mint 20A and ESXIB is the compute resource
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:28.000 --> 00:33.700
So ESXIA is the compute resource for mint 20A and ESXIB is the compute resource

11
00:33.700 --> 00:35.000
for mint 20B

12
00:35.000 --> 00:38.500
and both those VMs are connected to that same blue segment 20.

13
00:38.500 --> 00:42.300
So let's open up remote consoles to each of them and just verify the connection

14
00:42.300 --> 00:42.800
speed.

15
00:42.800 --> 00:48.400
So here is mint 20A as shown in the upper left-hand corner right here

16
00:48.400 --> 00:51.300
and let's open up a browser and let's run a speed test.

17
00:51.300 --> 00:57.000
So let's go out to fast.com and survey says we have some speeds somewhere in

18
00:57.000 --> 00:57.400
the range

19
00:57.400 --> 01:02.100
of 400 to 600 megabits per second that looks pretty decent.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:57.400 --> 01:02.100
of 400 to 600 megabits per second that looks pretty decent.

20
01:02.100 --> 01:03.900
So again, this is mint 20A.

21
01:03.900 --> 01:06.800
This is not the one that they claim is having the problem.

22
01:06.800 --> 01:09.300
So next let's go over to mint 20B.

23
01:09.300 --> 01:13.400
So here is mint 20B from the right VM right there.

24
01:13.400 --> 01:14.200
Fantastic.

25
01:14.200 --> 01:19.680
Let's also open up a browser here on mint 20B and we'll run that same speed

26
01:19.680 --> 01:20.000
test.

27
01:20.000 --> 01:21.600
So I've got a bookmark for it right here.

28
01:21.600 --> 01:22.800
There's fast.com.

29
01:22.800 --> 01:27.200
We'll click on that and it's getting somewhere between 60

30
01:27.200 --> 01:30.000
and 70 megabits per second.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:30.000 --> 01:33.000
So sure enough, we can replicate the results that the customer is experiencing

32
01:33.000 --> 01:37.880
and that is some decent access here through mint 20A and not so great here on

33
01:37.880 --> 01:39.000
mint 20B.

34
01:39.000 --> 01:44.400
So let's minimize those VMs and let's take a look at the configuration in NSX.

35
01:44.400 --> 01:49.800
So here in NSX, let's click on the networking tab and let's go to segments.

36
01:49.800 --> 01:53.200
So on the left, we'll click on segments and then here we have our blue segment

37
01:53.200 --> 01:53.700
20.

38
01:53.700 --> 01:58.100
So we'll expand that and scroll down and open up the segment profiles.

39
01:58.100 --> 02:02.000
And that looks like it's using all the defaults for IP discovery, Mac discovery
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:58.100 --> 02:02.000
And that looks like it's using all the defaults for IP discovery, Mac discovery

40
02:02.000 --> 02:02.000
,

41
02:02.000 --> 02:06.400
spoof guard, segment security and nothing applied at all for the QOS.

42
02:06.400 --> 02:09.500
And that kind of makes sense because if we had a QS policy right here,

43
02:09.500 --> 02:14.400
that same QS policy by default would be inherited by mint 20A and mint 20B.

44
02:14.400 --> 02:18.100
Now because it's mint 20B that seems to be having the problem,

45
02:18.100 --> 02:21.920
let's also go ahead and scroll to the right here for the segment blue segment

46
02:21.920 --> 02:22.500
20

47
02:22.500 --> 02:25.700
and let's click right here on the link for ports slash interfaces

48
02:25.700 --> 02:28.200
and that would be our mint 20A and mint 20B.

49
02:28.200 --> 02:30.800
So we'll click that and here's our mint 20B.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
02:28.200 --> 02:30.800
So we'll click that and here's our mint 20B.

50
02:30.800 --> 02:34.360
Now it's showing us mint 20 without the B this because I renamed it after the

51
02:34.360 --> 02:34.600
fact.

52
02:34.600 --> 02:36.600
So that's our VM in question.

53
02:36.600 --> 02:38.900
Let's expand that and scroll down.

54
02:38.900 --> 02:43.300
Let's expand the segment port profiles and scroll down and sure enough,

55
02:43.300 --> 02:45.400
it has at the VM level.

56
02:45.400 --> 02:48.500
It has a QOS segment profile applied to it.

57
02:48.500 --> 02:49.800
So let's take a look at what's in there.

58
02:49.800 --> 02:52.600
So to see that from right here, we can just click on the three dots,

59
02:52.600 --> 02:57.300
click on edit and then scroll down to the QOS and then click on the three dots

60
02:57.300 --> 02:57.800
here

61
02:57.800 --> 02:59.200
and click on view.

62
02:59.200 --> 03:02.810
And here's showing us that we do have some bandwidth restrictions that are in
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
02:59.200 --> 03:02.810
And here's showing us that we do have some bandwidth restrictions that are in

63
03:02.810 --> 03:03.300
place,

64
03:03.300 --> 03:08.400
including limiting inbound and outbound traffic to 75 megabits per second.

65
03:08.400 --> 03:11.400
So if we want to change this behavior for this specific VM,

66
03:11.400 --> 03:16.400
what we can do is simply not associate this QOS segment profile with that VM.

67
03:16.400 --> 03:19.500
So I'll go ahead and say, let's inherit from the parent and on the parent,

68
03:19.500 --> 03:22.400
there currently isn't a QOS segment profile.

69
03:22.400 --> 03:26.200
So we'll click on save, click on close and let's go back and now do our test

70
03:26.200 --> 03:27.000
once again.

71
03:27.000 --> 03:30.500
So here is Mint 20A, which before was doing quite well.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
03:27.000 --> 03:30.500
So here is Mint 20A, which before was doing quite well.

72
03:30.500 --> 03:34.300
And I would expect if we refresh that, it's still going to do quite well.

73
03:34.300 --> 03:38.500
And sure enough, it's in the 500 megabit range and now let's bring up Mint 20B.

74
03:38.500 --> 03:41.700
So here is Mint 20B, which previously didn't do that well.

75
03:41.700 --> 03:44.900
And we'll go ahead and run the test again by clicking and refresh there.

76
03:44.900 --> 03:49.280
And now I'm showing a throughput of somewhere between 450 and 600 megabits per

77
03:49.280 --> 03:49.800
second,

78
03:49.800 --> 03:52.600
which is basically the capacity of my lab environment.

79
03:52.600 --> 03:57.900
So it's no longer being restricted at the VM level by a QOS segment profile

80
03:57.900 --> 04:00.400
that previously was applied to that VM.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
03:57.900 --> 04:00.400
that previously was applied to that VM.

81
04:00.400 --> 04:03.900
So thanks for joining me in this set of videos regarding segment profiles in

82
04:03.900 --> 04:05.200
the world of NSX.

83
04:05.200 --> 04:08.900
And I'll see you, my friend, in another skill very, very soon.

84
04:08.900 --> 04:13.190
Until then, I hope this has been informative and I'd like to thank you for

85
04:13.190 --> 04:13.900
viewing.