WEBVTT

1
00:00.000 --> 00:03.240
So when we go to deploy our edge transport notes,

2
00:03.240 --> 00:04.860
they're going to provide the features like

3
00:04.860 --> 00:09.400
stateful services and VPNs and network address translation.

4
00:09.400 --> 00:12.200
When we deploy those edge nodes in our nested environment,

5
00:12.200 --> 00:14.300
we're going to place those down here on

6
00:14.300 --> 00:16.000
our management ESXi host,

7
00:16.000 --> 00:17.720
that's ESXi-management.

8
00:17.720 --> 00:20.080
So we'll leave the responsibility for

9
00:20.080 --> 00:23.960
ESXi-A and ESXi-B to act as host transport nodes.

10
00:23.960 --> 00:27.120
Then on our management ESXi-host and our nested environment,

11
00:27.120 --> 00:28.820
that's where we'll place both of our edges.

12
00:28.820 --> 00:31.120
So edge one and edge two.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:28.820 --> 00:31.120
So edge one and edge two.

13
00:31.120 --> 00:32.960
Very similar to the logic I use for

14
00:32.960 --> 00:35.880
the host transport nodes for the edges for edge one.

15
00:35.880 --> 00:38.000
I want to make sure I use a specific IP address.

16
00:38.000 --> 00:41.840
So let's use 33.33.33 etc.

17
00:41.840 --> 00:44.720
For edge two, let's use 44.

18
00:44.720 --> 00:46.280
With a default gateway of

19
00:46.280 --> 00:49.880
.1 on each of those respective networks and the benefit in a lab environment,

20
00:49.880 --> 00:52.560
of using specific tunnel endpoint addresses like that,

21
00:52.560 --> 00:55.800
is that it's very clear when you do trace flow or you start

22
00:55.800 --> 00:58.200
capturing packets off the network or off the wire,

23
00:58.200 --> 01:02.020
it makes it that much easier to identify where traffic is flying from and to.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:58.200 --> 01:02.020
it makes it that much easier to identify where traffic is flying from and to.

24
01:02.020 --> 01:06.860
Also for edge one, I use VLANs 103 and for edge two, I use VLAN 104.

25
01:06.860 --> 01:10.380
That also means I want to make sure up here at my top of X switch,

26
01:10.380 --> 01:15.740
I'm also supporting VLAN 103 and 104 because if I fail to support

27
01:15.740 --> 01:20.060
either of those VLANs or the routing between those VLANs and the subnets that

28
01:20.060 --> 01:20.220
they're

29
01:20.220 --> 01:23.300
supporting, that's going to cause my transport network to fail.

30
01:23.300 --> 01:27.980
So down here for edge one, we'll use VLAN 103 and let's use uplink 4.

31
01:27.980 --> 01:31.980
And for edge two, we'll use VLAN 104 and uplink 5.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:27.980 --> 01:31.980
And for edge two, we'll use VLAN 104 and uplink 5.

32
01:31.980 --> 01:34.380
And that way we have nice clear separation.

33
01:34.380 --> 01:38.540
Those two little edge VMs are going to use the uplinks that we specify as part

34
01:38.540 --> 01:39.440
of the deployment.

35
01:39.440 --> 01:43.600
And again, they could use the same exact uplink, that's not a problem.

36
01:43.600 --> 01:46.180
However, for a lab environment and for learning purposes,

37
01:46.180 --> 01:49.620
by separating them into two separate VLANs and having separate IP addressing

38
01:49.620 --> 01:50.740
this very distinctive,

39
01:50.740 --> 01:54.380
it's going to help clarify what is really going on as those edge nodes

40
01:54.380 --> 01:57.560
communicate, talk with each other and as they interact with our host transport

41
01:57.560 --> 01:57.820
nodes

42
01:57.820 --> 01:58.820
as well.

43
01:58.820 --> 02:01.740
So let me give you a peek at what that looks like both from the NSX manager and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
01:58.820 --> 02:01.740
So let me give you a peek at what that looks like both from the NSX manager and

44
02:01.740 --> 02:02.780
also from

45
02:02.780 --> 02:07.140
the compute resource that's being used as the home for these two little VMs.

46
02:07.140 --> 02:11.400
So here in the NSX manager with system selected and fabric expanded, let's go

47
02:11.400 --> 02:12.300
down to notes

48
02:12.300 --> 02:15.100
and we'll click on yes to leave our previous config.

49
02:15.100 --> 02:16.700
So here are two edge nodes.

50
02:16.700 --> 02:19.140
There are the management addresses for each of them.

51
02:19.140 --> 02:22.140
There's the host that's supporting those two edge nodes.

52
02:22.140 --> 02:25.260
And there's the tunnel endpoints for each of them as well.

53
02:25.260 --> 02:27.990
So if we went into edit one of them, we'll click on one of them, click on the

54
02:27.990 --> 02:29.260
pencil for edit.

55
02:29.260 --> 02:31.340
There's the name of that edge node edge one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:29.260 --> 02:31.340
There's the name of that edge node edge one.

56
02:31.340 --> 02:35.020
If we scroll down, there's the transport zones that's supporting, which include

57
02:35.020 --> 02:35.380
two that I

58
02:35.380 --> 02:38.700
gave it and one because I set up an NSX federation earlier.

59
02:38.700 --> 02:39.980
So add that to it.

60
02:39.980 --> 02:44.180
Here's the uplink profile using VLAN 103 and VMnik 4.

61
02:44.180 --> 02:46.740
There's the static IP address I configured for it.

62
02:46.740 --> 02:50.800
And if we scroll down, here's where I mapped the name of the uplink profile

63
02:50.800 --> 02:51.420
right here

64
02:51.420 --> 02:54.620
with the port group that leads to VMnik 4.

65
02:54.620 --> 02:58.050
And that's one of the benefits for your edge nodes of naming the port group

66
02:58.050 --> 02:58.500
regarding which

67
02:58.500 --> 02:59.740
uplinks it's using.

68
02:59.740 --> 03:01.820
And that way you can choose the correct uplink that you want to use.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

68
02:59.740 --> 03:01.820
And that way you can choose the correct uplink that you want to use.

69
03:01.820 --> 03:05.360
So in the lab, I just use a single uplink, although in a production environment

70
03:05.360 --> 03:05.900
for fault

71
03:05.900 --> 03:09.400
tolerance and higher throughput, you could actually have multiple uplinks based

72
03:09.400 --> 03:09.660
on the

73
03:09.660 --> 03:11.340
uplink profile you want to use.

74
03:11.340 --> 03:12.340
So no changes there.

75
03:12.340 --> 03:17.100
If we click on cancel and we go to edge two here on the overview tab, it's

76
03:17.100 --> 03:17.500
showing us

77
03:17.500 --> 03:22.040
the transport zones, which host is running that VM, the management IP address

78
03:22.040 --> 03:22.260
of the

79
03:22.260 --> 03:25.780
VM, and if it clicks on monitor, we could take a look at how it's doing with

80
03:25.780 --> 03:26.660
the resources

81
03:26.660 --> 03:27.660
it's been given.

82
03:27.660 --> 03:30.550
If you click here on tunnels, here you're showing it's a tunnel endpoint
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

82
03:27.660 --> 03:30.550
If you click here on tunnels, here you're showing it's a tunnel endpoint

83
03:30.550 --> 03:31.180
address.

84
03:31.180 --> 03:35.340
And currently we have a tunnel up to edge one, which is at 3333.

85
03:35.340 --> 03:39.560
And there's the logical interface, fast path, Ethernet zero using Geneva tunnel

86
03:39.560 --> 03:40.020
ing.

87
03:40.020 --> 03:43.250
So my objective here in this set of videos and the skill was to walk you

88
03:43.250 --> 03:43.900
through and

89
03:43.900 --> 03:47.220
show you the details behind my nested lab environment.

90
03:47.220 --> 03:51.670
So to help reinforce the concept that this is super useful in the next video, I

91
03:51.670 --> 03:51.780
'd like

92
03:51.780 --> 03:52.780
to do two things.

93
03:52.780 --> 03:55.760
Number one, I'd like to go ahead and use this lab environment to go ahead and

94
03:55.760 --> 03:56.780
create connectivity

95
03:56.780 --> 04:00.380
from a VM on one of the segments out to the public internet.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

95
03:56.780 --> 04:00.380
from a VM on one of the segments out to the public internet.

96
04:00.380 --> 04:03.260
And then secondly, I'd like to walk you through how to gracefully shut it all

97
04:03.260 --> 04:04.380
down and snapshot

98
04:04.380 --> 04:05.380
it.

99
04:05.380 --> 04:07.720
So if we need to, we can come right back to the point that we left off and

100
04:07.720 --> 04:08.220
everything

101
04:08.220 --> 04:09.020
is good to go.