WEBVTT

1
00:00.000 --> 00:04.960
So our very first step is to verify our existing topology here in NSX

2
00:04.960 --> 00:09.360
and also do a little bit of cleanup from the previous NSX cloud

3
00:09.360 --> 00:12.950
that we implemented as part of the advanced load balancer in the previous skill

4
00:12.950 --> 00:12.960
.

5
00:12.960 --> 00:16.720
So for the cleanup, let's start here at the controller for the advanced load

6
00:16.720 --> 00:17.440
balancer.

7
00:17.440 --> 00:20.640
So here is our topology down here in the bottom right hand corner,

8
00:20.640 --> 00:24.650
just for reference and we're currently at the controller for the advanced load

9
00:24.650 --> 00:25.360
balancer.

10
00:25.360 --> 00:28.960
So with the applications tab selected here and the dashboard,

11
00:28.960 --> 00:30.640
currently we have no virtual services.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:28.960 --> 00:30.640
currently we have no virtual services.

12
00:30.640 --> 00:33.600
I must have deleted that after the last skill, no problem.

13
00:33.600 --> 00:37.440
So just to confirm if we go to virtual service VIPs or stuff in there,

14
00:37.440 --> 00:42.520
no pools of servers, no pool groups, and if we go over here to infrastructure

15
00:42.520 --> 00:43.040
on the left,

16
00:43.040 --> 00:45.920
we have three services engines that are currently deployed.

17
00:45.920 --> 00:48.880
And let's go ahead and under cloud resources, expand that and say,

18
00:48.880 --> 00:52.160
you know what, for those service engines, and let's also do a drop down and

19
00:52.160 --> 00:53.600
grab our old cloud there.

20
00:53.600 --> 00:55.120
Let's just go ahead and delete them.

21
00:55.120 --> 00:59.120
So just select them all, say delete, and what that will do is in conjunction

22
00:59.120 --> 01:00.240
with vCenter,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:59.120 --> 01:00.240
with vCenter,

23
01:00.240 --> 01:01.840
vCenter just got rid of them.

24
01:01.840 --> 01:04.240
So if we go back to vCenter, those are gone.

25
01:04.240 --> 01:05.760
It immediately deleted those.

26
01:05.760 --> 01:09.670
So back to the controller, let's click on clouds, and there's the default cloud

27
01:09.670 --> 01:09.840
.

28
01:09.840 --> 01:10.960
There's our NSX cloud.

29
01:10.960 --> 01:14.880
We'll go ahead and let's delete that and give that a moment to refresh.

30
01:14.880 --> 01:18.480
So now we're just back to the default and if good to cloud resources,

31
01:18.480 --> 01:19.760
all of this should be empty.

32
01:19.760 --> 01:23.520
So no service engines, no service engine groups, no networks.

33
01:23.520 --> 01:25.440
We have the default service engine group.

34
01:25.440 --> 01:27.200
We have no networks.

35
01:27.200 --> 01:28.640
Fantastic.

36
01:28.640 --> 01:32.240
I also want to take a moment and just verify that in our NSX topology,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:28.640 --> 01:32.240
I also want to take a moment and just verify that in our NSX topology,

37
01:32.240 --> 01:37.440
that we currently have connectivity from the tier one left gateway to the 1050

38
01:37.440 --> 01:37.920
network

39
01:37.920 --> 01:42.810
and also the 1060 network, because we did not use either of those VLAN back

40
01:42.810 --> 01:43.440
segments

41
01:43.440 --> 01:44.560
in our previous skill.

42
01:44.560 --> 01:47.680
So I just want to take a look real quick and make sure they're up and ready.

43
01:47.680 --> 01:50.720
So let's go to the NSX manager to verify that.

44
01:50.720 --> 01:52.560
So here is the NSX manager.

45
01:52.560 --> 01:54.240
We click on networking.

46
01:54.240 --> 01:55.840
Let's go down to segments.

47
01:55.840 --> 01:58.880
And so here is VLAN 5.

48
01:58.880 --> 02:01.040
There is VLAN 6.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
01:58.880 --> 02:01.040
There is VLAN 6.

49
02:01.040 --> 02:01.920
That looks good.

50
02:01.920 --> 02:07.040
And there is the external network 192, which is not using any VLAN tagging.

51
02:07.040 --> 02:09.360
So that's why it has a zero there for the VLAN.

52
02:09.360 --> 02:13.180
But still from the perspective of T1, right, it's an extremely connected

53
02:13.180 --> 02:13.600
network.

54
02:13.600 --> 02:17.430
And this segment right here is the segment that our tier zero gateway is

55
02:17.430 --> 02:18.000
connected

56
02:18.000 --> 02:19.280
up to the external router.

57
02:19.280 --> 02:21.120
So that's VLAN 23 up there.

58
02:21.120 --> 02:22.960
And we took a peek at our network topology.

59
02:22.960 --> 02:24.160
Let's do that next.

60
02:24.160 --> 02:26.160
And here we have our T1 left.

61
02:26.160 --> 02:29.440
And here we have our connections to VLAN 5 and VLAN 6.

62
02:29.440 --> 02:35.680
And we're using the IP address of 10501 for the VLAN 5 connection and 10601 for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
02:29.440 --> 02:35.680
And we're using the IP address of 10501 for the VLAN 5 connection and 10601 for

63
02:35.680 --> 02:37.440
our VLAN 6 connection.

64
02:37.440 --> 02:40.560
So also I just want to go to my top of rack switch just for a moment

65
02:40.560 --> 02:44.350
and just validate that I can ping both those addresses from my top of rack

66
02:44.350 --> 02:44.720
switch,

67
02:44.720 --> 02:48.400
just to confirm that we really do have access through those VLANs

68
02:48.400 --> 02:49.680
to those IP addresses.

69
02:49.680 --> 02:51.200
So here's my top of rack switch.

70
02:51.200 --> 02:53.360
Let's do a ping to 10501.

71
02:53.360 --> 02:55.360
And that is looking good.

72
02:55.360 --> 02:58.480
And let's also do a ping to 106.0.1.

73
02:58.480 --> 02:59.360
And that's looking good.

74
02:59.360 --> 03:00.000
Great, great, great.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

75
03:00.000 --> 03:03.520
So I just want to validate that we really did have that connectivity in place.

76
03:03.520 --> 03:07.280
Because if we want to support servers that are on VLAN 5,

77
03:07.280 --> 03:11.760
we need to make sure that this T1 left really is connected to VLAN 5 right here

78
03:11.760 --> 03:11.760
,

79
03:11.760 --> 03:14.240
which it is also on this top of rack switch.

80
03:14.240 --> 03:19.480
I am providing DHCP services from this top of rack switch to both VLAN 5 and V

81
03:19.480 --> 03:20.320
LAN 6.

82
03:20.320 --> 03:25.410
So if we did a show IP DHCP pool on this top of rack switch and hit the space

83
03:25.410 --> 03:26.640
bar a few times.

84
03:26.640 --> 03:32.800
So here we have a pool for VLAN 5 and we have yet another pool for VLAN 6.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
03:26.640 --> 03:32.800
So here we have a pool for VLAN 5 and we have yet another pool for VLAN 6.

85
03:32.800 --> 03:33.600
And that looks great.

86
03:33.600 --> 03:37.760
So even though the servers here on VLAN 5 are probably not going to be using

87
03:37.760 --> 03:38.320
DHCP

88
03:38.320 --> 03:40.720
to get an IP address because they're statically configured,

89
03:40.720 --> 03:45.690
our service engines, we are going to use DHCP to dynamically assign them an IP

90
03:45.690 --> 03:46.240
address here

91
03:46.240 --> 03:47.920
on the 1060 subnet.

92
03:47.920 --> 03:50.960
And when we do, we should be able to come back to this DHCP server,

93
03:50.960 --> 03:54.740
which in this case is my top of rack switch, and just validate that they did

94
03:54.740 --> 03:55.920
get an IP address.

95
03:55.920 --> 03:59.280
And then the control and management plane between the controller and the

96
03:59.280 --> 04:00.320
service engines
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
03:59.280 --> 04:00.320
service engines

97
04:00.320 --> 04:04.320
would be from the controller who's over here on the 10103 address space.

98
04:04.320 --> 04:09.280
And that traffic would be routed through our NSX environment over to the 10.6.0

99
04:09.280 --> 04:09.600
network,

100
04:09.600 --> 04:11.200
which is VLAN 6.

101
04:11.200 --> 04:14.960
So I also want to take just a moment and confirm in my vCenter environment

102
04:14.960 --> 04:18.720
that we still have our content library ready to go because we're going to need

103
04:18.720 --> 04:19.520
that as well.

104
04:19.520 --> 04:23.120
So here on the vSphere client, let's use the hamburger menu at the top left and

105
04:23.120 --> 04:23.920
click on content

106
04:23.920 --> 04:28.160
libraries. And sure enough, there's our content library right there.

107
04:28.160 --> 04:31.680
So if we open it up, currently there is nothing in it.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

107
04:28.160 --> 04:31.680
So if we open it up, currently there is nothing in it.

108
04:31.680 --> 04:34.960
So once we create the new cloud and create a virtual service,

109
04:34.960 --> 04:38.080
once again, the controller is going to go ahead and start populating the

110
04:38.080 --> 04:39.120
content library with the

111
04:39.120 --> 04:42.430
template. And then from that template, it can start deploying these service

112
04:42.430 --> 04:42.800
engines.

113
04:42.800 --> 04:46.070
Also, one last thing I want to validate at the controller, I just want to

114
04:46.070 --> 04:46.800
validate that I still

115
04:46.800 --> 04:50.610
have the credentials in place that we can use when we create the new cloud to

116
04:50.610 --> 04:51.440
log in and connect

117
04:51.440 --> 04:55.500
to vCenter and also to the NSX manager. So back here at the controller, let's

118
04:55.500 --> 04:56.400
go to the administration

119
04:56.400 --> 05:00.710
tab up on top. And on the left, we'll go down under user credentials and click
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

119
04:56.400 --> 05:00.710
tab up on top. And on the left, we'll go down under user credentials and click

120
05:00.710 --> 05:01.440
on user credentials

121
05:01.440 --> 05:04.990
there. And sure enough, we have our credentials we can use for vCenter and that

122
05:04.990 --> 05:06.400
vCenter is at dot 35

123
05:06.400 --> 05:10.120
on my management network here. And we can use the credentials here for the NSX

124
05:10.120 --> 05:11.440
manager at dot 21.

125
05:11.440 --> 05:14.560
And those are good to go. So now that we've done the cleanup, we're now in

126
05:14.560 --> 05:16.080
great striking position

127
05:16.080 --> 05:20.950
to implement our brand new cloud connector using the advanced load balancer

128
05:20.950 --> 05:21.920
inside of our NSX

129
05:21.920 --> 05:25.220
environment. So I'll see you in the next video as we continue this journey

130
05:25.220 --> 05:25.680
together.

131
05:25.680 --> 05:35.340
[BLANK_AUDIO]