So in a scenario where a customer has a lab that is set up and they've gone in
and made some changes,
we could go ahead and try to troubleshoot that, you know, initially.
So for example, this is the vSphere client, let's head over to their NSX
manager.
So here's the NSX manager, if we click here on network topology,
we could take a look at what they currently have, we could also bring in VMs
that are deployed using that topology and verify if they work or not.
Let's open up a browser and let's try to go to VMware.com. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So then on this little VM, we could verify it has an IP address and look for
DHCP services.
But at the end of the day, if the customer made a whole bunch of changes
and they configured some new gateways and new interfaces and maybe they changed
routing
and net rules and so forth, if the customer has a lab environment that they've
set up
and they've correctly backed up and have snapshots of that environment,
at this point in the game, it probably wise to tell the customer, you know what
,
let's revert back to your previous state and start over. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Especially if they have no clue about many of the changes that they were
working with
and testing in their current test environment.
So to facilitate that, we could go ahead and simply close the tabs for the NSX
manager
and close the tab for their nested lab environment and then go back to the
parent environment right here.
And the first thing I'd want to do is just verify that we have snapshots of all
the VMs.
So there's ESXIA with the snapshots tab.
It was created at 152 today, January 1st and ESXAB, also on the 1st, ESXIA
management VM, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
also on the 1st, and for the NSX manager, also on the 1st, but just a few
minutes later.
So that one took a little bit longer to delete the existing snapshots before I
could create the new one,
but all these are in the right ballpark.
So for the customer who's just made a whole bunch of changes to their test/lab
environment,
the best thing here would be to revert it back.
So we go to each of the VMs, so we'll go to ESXIA and say, you know what,
not delete all because we want to keep the existing snapshot, but this time we
just want to click on revert.
That's going to revert back to the powered off state initially with the same WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
That's going to revert back to the powered off state initially with the same
thing for ESXIB.
And it's lightning quick because the vSphere does not have to go ahead and
merge disk images or anything else.
Instead, it's just saying, you know what, everything in the Delta disks gone.
All I care about is the initial state for the snapshot and that's what it's
returning to.
So if we click on recent tasks here and I'll go ahead and say running recent
tasks.
And then for this last NSX manager VM, we click on revert and click on revert.
Notice here it's doing the reversion and it is done.
So if we look at the history here for recent tasks, I'll click on show all. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we look at the history here for recent tasks, I'll click on show all.
It's just reverted those four VMs to their snapshot state.
And at this point, what we could do is just take those VMs that we want to kick
off again and select them here.
So those are the four that we're concerned about.
Right click power and power them on and then in about 15 to 20 minutes.
That environment should be up and ready for them once again.
Also, just be aware that when we're powering on the VMs for a while, it may
take a few minutes because for example,
the NSX manager, it's running two edge nodes as nested VMs inside of it along WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the NSX manager, it's running two edge nodes as nested VMs inside of it along
with the vCenter.
And then for the NSX manager, this is a very common message right here.
So this one and very similar to this one.
And that's not a death knell for the NSX manager.
That just means, hey, give it a few more minutes for it to fully initialize.
So if you see this, when you try to log on to the NSX manager, either directly
to the IP address under NSX manager,
if you only have one or to the virtual IP address for the NSX manager, in
either case,
if you see this message, just give it a few additional minutes and you should WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
if you see this message, just give it a few additional minutes and you should
be right as right.
So let me go ahead and minimize that message.
And again, with these four VMs just powering up in about 10 to 15 minutes,
depending on the environment that's supporting them.
In this case, I have three physical ESXi hosts that are doing the work.
I've got ESXi one, two, and three that are providing the compute and backend
resources for those.
And as a result, they should be up and running and ready to go in about 10 to
15 minutes.
So thanks for joining me in this set of videos regarding building and working
with a home lab environment for NSX. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
with a home lab environment for 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.
for viewing.