WEBVTT

1
00:00.000 --> 00:03.200
So in this video, I'd like to go ahead and walk you through the confirmation of

2
00:03.200 --> 00:04.160
which IP

3
00:04.160 --> 00:08.480
discovery segment profile is applied by default to our segments and then also

4
00:08.480 --> 00:09.120
take a look at some

5
00:09.120 --> 00:13.190
of the results that we're learning from that IP discovery segment profile,

6
00:13.190 --> 00:14.320
including information

7
00:14.320 --> 00:17.580
about the layer two addresses and layer three addresses because behind the

8
00:17.580 --> 00:18.800
scenes, the IP discovery

9
00:18.800 --> 00:23.830
profile is doing ARP spoofing and DHCP snooping to dynamically discover that

10
00:23.830 --> 00:25.200
information from our

11
00:25.200 --> 00:28.800
VMs. So because we already have our Mint 10 computer sitting right here on the

12
00:28.800 --> 00:29.520
green segment

13
00:29.520 --> 00:33.280
and there's a default IP discovery segment profile in place, let's take a look
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:29.520 --> 00:33.280
and there's a default IP discovery segment profile in place, let's take a look

14
00:33.280 --> 00:34.400
at the results of the

15
00:34.400 --> 00:37.620
IP discovery profile on a segment and how it was used to discover the

16
00:37.620 --> 00:39.280
information about our Mint 10

17
00:39.280 --> 00:42.990
VM right here, including its layer two information and layer three information.

18
00:42.990 --> 00:44.080
So back in the NSX

19
00:44.080 --> 00:47.660
manager, we'll once again click on the networking tab on top, I'll expand the

20
00:47.660 --> 00:48.640
left hand side so we

21
00:48.640 --> 00:52.810
can navigate here and let's go back to segments. So if we click on segments and

22
00:52.810 --> 00:53.600
we go down to our

23
00:53.600 --> 00:56.560
green segment, in fact, I'm going to go ahead and edit that and I'm going to

24
00:56.560 --> 00:57.120
put a period in

25
00:57.120 --> 01:00.340
front of that. So it's sourced to the top and be a little bit easier to find
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
00:57.120 --> 01:00.340
front of that. So it's sourced to the top and be a little bit easier to find

26
01:00.340 --> 01:01.200
every time I'm looking

27
01:01.200 --> 01:04.880
for that specific segment. So I'm going to put a period there, scroll down,

28
01:04.880 --> 01:05.840
click on save and then

29
01:05.840 --> 01:09.050
click on close editing and there's our green segment sorted to the top.

30
01:09.050 --> 01:10.960
Fantastic. So let's go ahead

31
01:10.960 --> 01:14.570
and look at the details for the green segment. We'll expand it, we'll expand

32
01:14.570 --> 01:15.680
segment profiles and

33
01:15.680 --> 01:19.490
here's the IP discovery profile that's associated with this segment. It is the

34
01:19.490 --> 01:20.640
default one. So if we

35
01:20.640 --> 01:24.560
wanted to edit that, we can click on edit here to edit the segment and then go

36
01:24.560 --> 01:25.600
down to that segment

37
01:25.600 --> 01:29.550
profile. And for the IP discovery, we could click on the three dots and from

38
01:29.550 --> 01:30.800
here we can click on view
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:29.550 --> 01:30.800
here we can click on view

39
01:30.800 --> 01:35.900
and they'll show us all the settings in that current segment profile. So the

40
01:35.900 --> 01:36.880
duplicate IP

41
01:36.880 --> 01:41.430
detection by default is disabled, ARP snooping is enabled. There's a limit of

42
01:41.430 --> 01:42.560
one and then for

43
01:42.560 --> 01:46.800
ND, that's for IPv6, that's neighbor discovery protocol. The ND snooping is

44
01:46.800 --> 01:47.840
disabled by default,

45
01:47.840 --> 01:50.870
however, we can enable it if we wanted to create our own profile. So this

46
01:50.870 --> 01:52.800
little lock symbol implies

47
01:52.800 --> 01:56.740
that this default segment profile cannot be modified. So if we want a different

48
01:56.740 --> 01:57.280
setting,

49
01:57.280 --> 02:00.980
we could create our own segment profile and then apply it to this segment. And
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
01:57.280 --> 02:00.980
we could create our own segment profile and then apply it to this segment. And

50
02:00.980 --> 02:01.520
then over here on

51
02:01.520 --> 02:05.790
the right, we have DHCP snooping enabled. If we had DHCP for IPv6, it is

52
02:05.790 --> 02:07.120
disabled by default.

53
02:07.120 --> 02:10.780
And regarding VMware tools, if VMware tools is running on a VM, that's also

54
02:10.780 --> 02:11.680
going to be used by

55
02:11.680 --> 02:15.870
NSX to determine information about that network interface card on that VM,

56
02:15.870 --> 02:17.200
including its IP address

57
02:17.200 --> 02:20.850
and MAC address. And the trust on first use option, which is enabled in the

58
02:20.850 --> 02:21.760
default profile,

59
02:21.760 --> 02:25.840
simply says that as we discover an IP slash MAC address slash VLAN combination

60
02:25.840 --> 02:27.040
for a VM,

61
02:27.040 --> 02:30.320
that will go ahead and just immediately place that in the table. And that's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

61
02:27.040 --> 02:30.320
that will go ahead and just immediately place that in the table. And that's

62
02:30.320 --> 02:30.880
going to stay there

63
02:30.880 --> 02:34.200
persistently. If we create a segment profile and we disable that feature of

64
02:34.200 --> 02:35.200
trust on first use,

65
02:35.200 --> 02:38.720
it would then use a method called trust on every use. So it's still going to

66
02:38.720 --> 02:39.520
add the information

67
02:39.520 --> 02:43.410
to a table instead of NSX. However, there's an expiration timer. So after a

68
02:43.410 --> 02:44.400
period of time,

69
02:44.400 --> 02:47.680
that'll be removed. So if I lab at this point, I'm not using IPv6, so I don't

70
02:47.680 --> 02:48.560
need to enable

71
02:48.560 --> 02:52.960
any of the neighbor's discovery or DHCP snooping for IPv6. And this is pretty

72
02:52.960 --> 02:53.440
much going to serve

73
02:53.440 --> 02:58.650
our purposes. Now, as a result of having this on, let's take a look at Mint 10.

74
02:58.650 --> 02:59.600
So we'll close that

75
02:59.600 --> 03:03.770
and I'll click on close editing here. And for this segment, green segment 10,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

75
02:59.600 --> 03:03.770
and I'll click on close editing here. And for this segment, green segment 10,

76
03:03.770 --> 03:04.080
let me go ahead

77
03:04.080 --> 03:06.840
and collapse the left hand side gives a little more room here. We click here on

78
03:06.840 --> 03:07.360
the ports and

79
03:07.360 --> 03:11.680
interfaces. Here is our Mint 10 machine. And if we expand that and scroll down

80
03:11.680 --> 03:12.000
here, if we

81
03:12.000 --> 03:15.030
expand address binding, if we click right here on discovered bindings and click

82
03:15.030 --> 03:15.600
on view, it's

83
03:15.600 --> 03:18.680
going to show us what was discovered about that VM, including the layer three

84
03:18.680 --> 03:19.280
information,

85
03:19.280 --> 03:24.240
the layer two information, and how it was discovered. So for our network here,

86
03:24.240 --> 03:25.040
I'm going to leave the

87
03:25.040 --> 03:28.750
default segment port profiles in place and also get in here looking at the

88
03:28.750 --> 03:30.240
details for this individual
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

88
03:28.750 --> 03:30.240
details for this individual

89
03:30.240 --> 03:34.640
VM, it's showing us the actual segment port profiles in place and how they got

90
03:34.640 --> 03:35.520
there. And they

91
03:35.520 --> 03:39.210
were inherited from the segment profile that's currently applied to the segment

92
03:39.210 --> 03:40.000
itself. And if

93
03:40.000 --> 03:42.840
And if there was any overrides at this VM, they would show up right here.

94
03:42.840 --> 03:52.840
[BLANK_AUDIO]