So let's imagine the customer, they started the NAP automation, they did that
by deploying
the automation VM, making sure they had the plug in here as part of the NSX
manager,
and then as they were going through, it stopped working. So let's consider
together some of the
recommendations that we would have for them. One of our first recommendations
would be to check
the basic functionality of the network where they're deploying the NAP,
including making sure they
have correct name resolution from any devices on these network segments for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
have correct name resolution from any devices on these network segments for
both internal resources
like the vCenter server appliance and the NSX manager, and also making sure
that the devices
on these networks can actually get up to the internet. Also, if they have any
type of firewall
and restrictions between these various network segments, they'd want to make
sure that based
on the prereqs for the deployment that they are permitting the required
protocols, ports, and services.
So let's presume that we help them in verifying all of that and their network
infrastructure was
solid. Additional things to check would be to verify that on the cluster where WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
solid. Additional things to check would be to verify that on the cluster where
they're going to be
deploying the NAP, we'd want to make sure that that cluster is already set up
for HA and DRS.
Because when we deployed initially, it went out and checked and enabled HA on
that cluster,
but then when I went to deploy the VM, the HA proxy, I don't think the HA
cluster was quite
fully baked and ready and ready to go. And so then when we went back to the
wizard and we reset
everything, we went through it again, because the HA and the DRS was already
set up and functioning, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
set up and functioning,
it's at that point it was able to deploy the HA proxy. Now it may not just be
at the HA proxy
where we have a problem or an issue, it could be at any one of the steps in the
deployment process.
So the key would be to identify where it failed, and then go back and look at
the resources available,
whether they're log files or recent events or the events inside of vSphere to
see exactly what
failed, resolve that problem, and then move forward and continue on to the next
step. And we may have
to rerun that wizard as part of the automation VM, we may have to run that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to rerun that wizard as part of the automation VM, we may have to run that
multiple times. As we
identify problems, correct them, and then continue to move forward. So our end
goal is to make sure
that the NSX application platform is fully deployed, and then we can start
using it once it's ready.
So thanks for joining me in this set of videos regarding using the NAP
automation. And now that
we have this NSX application platform in our environment, in the next skill, we
'll take a look
at how do we actually use the NSX application platform that's now been deployed
. So I'll see you
soon for that next set of videos. Until then, I hope this has been informative WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
soon for that next set of videos. Until then, I hope this has been informative
and I'd like to.
Thank you for viewing.