So based on this customer scenario where they say one of the VMs is acting
slower,
we may want to take a moment and just verify that's the case.
So let's take a look at the vSphere and also the NS6 environment,
and let's also test these VMs to verify and compare their speed as they both go
out to the Internet.
So here in the vSphere client, let's go to the networks tab right here
and let's go to that segment which is blue segment 20.
There's our two VMs and I also want to confirm which hosts they're running on.
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
So ESXIA is the compute resource for mint 20A and ESXIB is the compute resource
for mint 20B
and both those VMs are connected to that same blue segment 20.
So let's open up remote consoles to each of them and just verify the connection
speed.
So here is mint 20A as shown in the upper left-hand corner right here
and let's open up a browser and let's run a speed test.
So let's go out to fast.com and survey says we have some speeds somewhere in
the range
of 400 to 600 megabits per second that looks pretty decent. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
of 400 to 600 megabits per second that looks pretty decent.
So again, this is mint 20A.
This is not the one that they claim is having the problem.
So next let's go over to mint 20B.
So here is mint 20B from the right VM right there.
Fantastic.
Let's also open up a browser here on mint 20B and we'll run that same speed
test.
So I've got a bookmark for it right here.
There's fast.com.
We'll click on that and it's getting somewhere between 60
and 70 megabits per second. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So sure enough, we can replicate the results that the customer is experiencing
and that is some decent access here through mint 20A and not so great here on
mint 20B.
So let's minimize those VMs and let's take a look at the configuration in NSX.
So here in NSX, let's click on the networking tab and let's go to segments.
So on the left, we'll click on segments and then here we have our blue segment
20.
So we'll expand that and scroll down and open up the segment profiles.
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
And that looks like it's using all the defaults for IP discovery, Mac discovery
,
spoof guard, segment security and nothing applied at all for the QOS.
And that kind of makes sense because if we had a QS policy right here,
that same QS policy by default would be inherited by mint 20A and mint 20B.
Now because it's mint 20B that seems to be having the problem,
let's also go ahead and scroll to the right here for the segment blue segment
20
and let's click right here on the link for ports slash interfaces
and that would be our mint 20A and mint 20B.
So we'll click that and here's our mint 20B. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we'll click that and here's our mint 20B.
Now it's showing us mint 20 without the B this because I renamed it after the
fact.
So that's our VM in question.
Let's expand that and scroll down.
Let's expand the segment port profiles and scroll down and sure enough,
it has at the VM level.
It has a QOS segment profile applied to it.
So let's take a look at what's in there.
So to see that from right here, we can just click on the three dots,
click on edit and then scroll down to the QOS and then click on the three dots
here
and click on view.
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
And here's showing us that we do have some bandwidth restrictions that are in
place,
including limiting inbound and outbound traffic to 75 megabits per second.
So if we want to change this behavior for this specific VM,
what we can do is simply not associate this QOS segment profile with that VM.
So I'll go ahead and say, let's inherit from the parent and on the parent,
there currently isn't a QOS segment profile.
So we'll click on save, click on close and let's go back and now do our test
once again.
So here is Mint 20A, which before was doing quite well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here is Mint 20A, which before was doing quite well.
And I would expect if we refresh that, it's still going to do quite well.
And sure enough, it's in the 500 megabit range and now let's bring up Mint 20B.
So here is Mint 20B, which previously didn't do that well.
And we'll go ahead and run the test again by clicking and refresh there.
And now I'm showing a throughput of somewhere between 450 and 600 megabits per
second,
which is basically the capacity of my lab environment.
So it's no longer being restricted at the VM level by a QOS segment profile
that previously was applied to that VM. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that previously was applied to that VM.
So thanks for joining me in this set of videos regarding segment profiles in
the world of NSX.
And I'll see you, my friend, in another skill very, very soon.
Until then, I hope this has been informative and I'd like to thank you for
viewing.