WEBVTT

1
00:00.000 --> 00:06.000
So in a scenario where a customer has a lab that is set up and they've gone in

2
00:06.000 --> 00:07.000
and made some changes,

3
00:07.000 --> 00:11.000
we could go ahead and try to troubleshoot that, you know, initially.

4
00:11.000 --> 00:14.380
So for example, this is the vSphere client, let's head over to their NSX

5
00:14.380 --> 00:15.000
manager.

6
00:15.000 --> 00:19.000
So here's the NSX manager, if we click here on network topology,

7
00:19.000 --> 00:23.000
we could take a look at what they currently have, we could also bring in VMs

8
00:23.000 --> 00:27.000
that are deployed using that topology and verify if they work or not.

9
00:27.000 --> 00:30.000
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

10
00:30.000 --> 00:34.200
So then on this little VM, we could verify it has an IP address and look for

11
00:34.200 --> 00:35.000
DHCP services.

12
00:35.000 --> 00:39.000
But at the end of the day, if the customer made a whole bunch of changes

13
00:39.000 --> 00:44.000
and they configured some new gateways and new interfaces and maybe they changed

14
00:44.000 --> 00:44.000
routing

15
00:44.000 --> 00:49.000
and net rules and so forth, if the customer has a lab environment that they've

16
00:49.000 --> 00:49.000
set up

17
00:49.000 --> 00:53.000
and they've correctly backed up and have snapshots of that environment,

18
00:53.000 --> 00:56.000
at this point in the game, it probably wise to tell the customer, you know what

19
00:56.000 --> 00:56.000
,

20
00:56.000 --> 01:00.000
let's revert back to your previous state and start over.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
01:00.000 --> 01:03.630
Especially if they have no clue about many of the changes that they were

22
01:03.630 --> 01:04.000
working with

23
01:04.000 --> 01:07.000
and testing in their current test environment.

24
01:07.000 --> 01:11.290
So to facilitate that, we could go ahead and simply close the tabs for the NSX

25
01:11.290 --> 01:12.000
manager

26
01:12.000 --> 01:15.450
and close the tab for their nested lab environment and then go back to the

27
01:15.450 --> 01:17.000
parent environment right here.

28
01:17.000 --> 01:20.450
And the first thing I'd want to do is just verify that we have snapshots of all

29
01:20.450 --> 01:21.000
the VMs.

30
01:21.000 --> 01:23.000
So there's ESXIA with the snapshots tab.

31
01:23.000 --> 01:29.380
It was created at 152 today, January 1st and ESXAB, also on the 1st, ESXIA

32
01:29.380 --> 01:30.000
management VM,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

33
01:30.000 --> 01:34.400
also on the 1st, and for the NSX manager, also on the 1st, but just a few

34
01:34.400 --> 01:35.000
minutes later.

35
01:35.000 --> 01:39.280
So that one took a little bit longer to delete the existing snapshots before I

36
01:39.280 --> 01:40.000
could create the new one,

37
01:40.000 --> 01:42.000
but all these are in the right ballpark.

38
01:42.000 --> 01:46.130
So for the customer who's just made a whole bunch of changes to their test/lab

39
01:46.130 --> 01:47.000
environment,

40
01:47.000 --> 01:49.000
the best thing here would be to revert it back.

41
01:49.000 --> 01:52.000
So we go to each of the VMs, so we'll go to ESXIA and say, you know what,

42
01:52.000 --> 01:55.900
not delete all because we want to keep the existing snapshot, but this time we

43
01:55.900 --> 01:57.000
just want to click on revert.

44
01:57.000 --> 02:00.440
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

44
01:57.000 --> 02:00.440
That's going to revert back to the powered off state initially with the same

45
02:00.440 --> 02:02.000
thing for ESXIB.

46
02:02.000 --> 02:05.330
And it's lightning quick because the vSphere does not have to go ahead and

47
02:05.330 --> 02:08.000
merge disk images or anything else.

48
02:08.000 --> 02:11.000
Instead, it's just saying, you know what, everything in the Delta disks gone.

49
02:11.000 --> 02:14.240
All I care about is the initial state for the snapshot and that's what it's

50
02:14.240 --> 02:15.000
returning to.

51
02:15.000 --> 02:18.660
So if we click on recent tasks here and I'll go ahead and say running recent

52
02:18.660 --> 02:19.000
tasks.

53
02:19.000 --> 02:24.000
And then for this last NSX manager VM, we click on revert and click on revert.

54
02:24.000 --> 02:27.000
Notice here it's doing the reversion and it is done.

55
02:27.000 --> 02:32.000
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

55
02:27.000 --> 02:32.000
So if we look at the history here for recent tasks, I'll click on show all.

56
02:32.000 --> 02:35.000
It's just reverted those four VMs to their snapshot state.

57
02:35.000 --> 02:38.640
And at this point, what we could do is just take those VMs that we want to kick

58
02:38.640 --> 02:41.000
off again and select them here.

59
02:41.000 --> 02:43.000
So those are the four that we're concerned about.

60
02:43.000 --> 02:49.000
Right click power and power them on and then in about 15 to 20 minutes.

61
02:49.000 --> 02:53.000
That environment should be up and ready for them once again.

62
02:53.000 --> 02:56.440
Also, just be aware that when we're powering on the VMs for a while, it may

63
02:56.440 --> 02:58.000
take a few minutes because for example,

64
02:58.000 --> 03:03.580
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

64
02:58.000 --> 03:03.580
the NSX manager, it's running two edge nodes as nested VMs inside of it along

65
03:03.580 --> 03:05.000
with the vCenter.

66
03:05.000 --> 03:09.000
And then for the NSX manager, this is a very common message right here.

67
03:09.000 --> 03:12.000
So this one and very similar to this one.

68
03:12.000 --> 03:15.000
And that's not a death knell for the NSX manager.

69
03:15.000 --> 03:19.000
That just means, hey, give it a few more minutes for it to fully initialize.

70
03:19.000 --> 03:22.510
So if you see this, when you try to log on to the NSX manager, either directly

71
03:22.510 --> 03:24.000
to the IP address under NSX manager,

72
03:24.000 --> 03:28.240
if you only have one or to the virtual IP address for the NSX manager, in

73
03:28.240 --> 03:29.000
either case,

74
03:29.000 --> 03:32.040
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

74
03:29.000 --> 03:32.040
if you see this message, just give it a few additional minutes and you should

75
03:32.040 --> 03:33.000
be right as right.

76
03:33.000 --> 03:36.000
So let me go ahead and minimize that message.

77
03:36.000 --> 03:40.000
And again, with these four VMs just powering up in about 10 to 15 minutes,

78
03:40.000 --> 03:42.000
depending on the environment that's supporting them.

79
03:42.000 --> 03:46.000
In this case, I have three physical ESXi hosts that are doing the work.

80
03:46.000 --> 03:50.510
I've got ESXi one, two, and three that are providing the compute and backend

81
03:50.510 --> 03:51.000
resources for those.

82
03:51.000 --> 03:54.060
And as a result, they should be up and running and ready to go in about 10 to

83
03:54.060 --> 03:55.000
15 minutes.

84
03:55.000 --> 03:59.070
So thanks for joining me in this set of videos regarding building and working

85
03:59.070 --> 04:01.000
with a home lab environment for NSX.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
03:59.070 --> 04:01.000
with a home lab environment for NSX.

86
04:01.000 --> 04:04.000
And I'll see you, my friend, in another skill very, very soon.

87
04:04.000 --> 04:08.510
Until then, I hope this has been informative and I'd like to thank you for

88
04:08.510 --> 04:09.000
viewing.

89
04:09.000 --> 04:09.840
for viewing.