So let's compare notes
regarding these four questions from the validation section.
So the first question asks, how is the functionality
of the NSX manager that we're gonna log into
to provide the management plane as well as the control plane
for all of our transport nodes?
How is that implemented?
That also ties into the next question, which is
where does the NSX manager run?
So the NSX manager is implemented as a vm,
so it can run here on this ESXI host,
or pretty much any ESXI host
that has the computing resources
to provide services for that vm. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to provide services for that vm.
And then the next question is,
how many NSX managers should be in a
cluster for fault tolerance?
And the answer is ideally three.
We'd want to have three of those
so we can have a virtual IP address in front of all that.
So we can connect to the virtual IP address for management.
And then one of the NSX managers in the cluster would take
responsibility for that.
And in the background, each
of the NSX managers are actually taking a responsibility
for a portion of the transport nodes.
So maybe this has responsibility for 10 of our host WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So maybe this has responsibility for 10 of our host
or edge transport nodes.
This has responsibility for 10,
and let's say we have 30 nodes altogether,
and this has responsibility for the other 10.
But in either case, that division of work behind the scenes
for the cluster is done automatically by the NSX manager.
So all we need to do is connect to the VAP
or to the IP address of any of the existing managers,
specify what we want to happen.
And then in the background, they divvy up the work as far
as the management of the NSX devices.
And then they're using corfu and the corfu database
to synchronize all the details
that are happening across all three WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that are happening across all three
of these NSX managers inside the cluster.
So ideally, we should have at least three NSX
managers in our cluster.
And then the last question is, how do you control
how much RAM and or CPU are used by an NSX management node?
So for the initial deployment of our NSX manager,
when we deploy the template,
we're gonna specify the size we want, we want extra small,
small, medium, or large.
And then based on that, that's gonna correspond to
how much CPU and RAM are being consumed by that NSX manager. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
how much CPU and RAM are being consumed by that NSX manager.
And then for the second and third NSX manager,
we simply deploy them
after we've logged into the initial NSX manager.
And there's an option there from within NSX manager
to deploy the second
and third NSX managers as part of the cluster.
So thanks for taking a few minutes to consider some
of the answers to these questions
and then reviewing them here with me together.
And then before we go,
I've got one final poll question for you right below.
And then once you're done with that, you're done
with this specific skill.
So until the next one, I hope this has been informative
and I'd like to thank you for viewing. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and I'd like to thank you for viewing.