WEBVTT

1
00:00.000 --> 00:04.000
So based on the screenshots, let's take a look together at what we think might

2
00:04.000 --> 00:05.000
be wrong.

3
00:05.000 --> 00:08.000
So the very first thing I'd love to do is, because I have the live environment

4
00:08.000 --> 00:09.000
in front of me here,

5
00:09.000 --> 00:14.310
let me just go ahead and verify that yes or no, this little VM can or can't get

6
00:14.310 --> 00:15.000
out to the Internet

7
00:15.000 --> 00:19.000
just to verify the symptom. So let me bring in that VM and it is right here.

8
00:19.000 --> 00:23.000
So this is the Site 1 Blue, and let's go to a Command Prompt,

9
00:23.000 --> 00:27.000
and let's do a Ping out to 8888, and press Enter.

10
00:27.000 --> 00:30.000
Network is unreachable. That's not a good sign.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:30.000 --> 00:33.000
So let's try Ping out a default gateway or it should be our default gateway,

12
00:33.000 --> 00:36.000
which is 10.10.0.1 based on how we left it in the lab.

13
00:36.000 --> 00:39.000
And yeah, oh, I think we don't even have an IP address.

14
00:39.000 --> 00:44.000
Let's do an IF config, press Enter, and we do not have an IP version 4 address

15
00:44.000 --> 00:45.000
on our Ethernet interface.

16
00:45.000 --> 00:50.360
So that is a huge problem. So now that we've verified that the client for sure

17
00:50.360 --> 00:51.000
can't get up to the Internet

18
00:51.000 --> 00:54.000
or anywhere else for that matter, because it doesn't have an IP address.

19
00:54.000 --> 00:58.000
Let's use the vSphere client and the global NSX manager and take a look.

20
00:58.000 --> 01:02.670
So let's start here in the vSphere client for Site 1, and that's where we are
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:58.000 --> 01:02.670
So let's start here in the vSphere client for Site 1, and that's where we are

21
01:02.670 --> 01:03.000
right here.

22
01:03.000 --> 01:07.000
And let's go down, find that VM. There it is, Site 1 Blue.

23
01:07.000 --> 01:10.430
And let's confirm it's on the right segment. So if we scroll down, sure enough,

24
01:10.430 --> 01:12.000
it's on Stretch Segment 10.

25
01:12.000 --> 01:15.460
As shown right there, it says it's connected. We can also confirm that by going

26
01:15.460 --> 01:17.000
over here to the Network's tab

27
01:17.000 --> 01:21.550
and going down to our Stretch Segment 10. And sure enough, there it is. So it's

28
01:21.550 --> 01:22.000
powered on.

29
01:22.000 --> 01:25.710
And based on what we just saw on that little VM, it doesn't have any IPV 4

30
01:25.710 --> 01:28.000
address on its Ethernet interface.

31
01:28.000 --> 01:31.520
So if it had been misconfigured statically for some reason, that would have
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:28.000 --> 01:31.520
So if it had been misconfigured statically for some reason, that would have

32
01:31.520 --> 01:34.000
shown up here, but I don't see any IPV 4 address.

33
01:34.000 --> 01:38.680
So that leads me to believe it may be a DHCP issue. So let's take a look at the

34
01:38.680 --> 01:42.000
NSX global manager and let's take a look at the DHCP config.

35
01:42.000 --> 01:47.290
So back at the NSX global manager, let's click on Networking. And let's go down

36
01:47.290 --> 01:49.000
on the left to Profiles.

37
01:49.000 --> 01:54.510
And click on DHCP. And sure enough, we have a relay for Site 1. And that's

38
01:54.510 --> 01:57.000
pointing to the real server at 10.21.01.

39
01:57.000 --> 02:00.390
Now, a lot of things could stop us from getting there. For example, maybe we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:57.000 --> 02:00.390
Now, a lot of things could stop us from getting there. For example, maybe we

40
02:00.390 --> 02:04.000
don't have an external interface connected to that segment on our T0 Gateway.

41
02:04.000 --> 02:08.990
So to confirm that, we could go to our T0 Gateway and take a look. We'll expand

42
02:08.990 --> 02:14.000
the details here for the T0 Gateway, go down to Interfaces,

43
02:14.000 --> 02:20.300
and click on Site 1. And sure enough, we have an interface right here that's

44
02:20.300 --> 02:22.000
connected to that external segment.

45
02:22.000 --> 02:26.840
That's the 10.21.0 address space. And that server is at .1. We can also SSH

46
02:26.840 --> 02:31.610
over to Edge 1. And then from there, go to the VRF for the Services Router for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
02:26.840 --> 02:31.610
over to Edge 1. And then from there, go to the VRF for the Services Router for

47
02:31.610 --> 02:32.000
the T0 Gateway.

48
02:32.000 --> 02:36.680
And try to ping that address 10.21.0.1. And because that'd be pretty easy to do

49
02:36.680 --> 02:39.000
right here to verify that, let's do that real quick.

50
02:39.000 --> 02:43.910
So here at Edge 1, let's do a gateways. And that'll show us the VRF we're using

51
02:43.910 --> 02:46.000
for the T0 Services Router, which is right here.

52
02:46.000 --> 02:51.250
So that's VRF 3. And we'll change that VRF by typing in VRF space 3, pressing

53
02:51.250 --> 02:55.000
Enter. And then let's do a get route, press Enter.

54
02:55.000 --> 03:00.340
And let's do a ping to 10.21.0.1. If that works, that means that we have
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
02:55.000 --> 03:00.340
And let's do a ping to 10.21.0.1. If that works, that means that we have

55
03:00.340 --> 03:05.590
connectivity, at least from the T0 Gateway to that DHCP server at that IP

56
03:05.590 --> 03:08.000
address 10.21.0.1.

57
03:08.000 --> 03:12.530
Alright, so that all looks good. And let's also check out the segment. So here

58
03:12.530 --> 03:17.290
is the Stretch segment 10. And right here under the Subnets column, see how we

59
03:17.290 --> 03:21.310
have this IP address, that's the IP address, the logical layer 3 address that

60
03:21.310 --> 03:24.000
the gateway is going to use when it connects to this logical segment.

61
03:24.000 --> 03:28.440
So let's see how it's not a hyperlink. What that implies is that there's no

62
03:28.440 --> 03:32.570
DHCP services set up for this segment. And we can confirm that by going into
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
03:28.440 --> 03:32.570
DHCP services set up for this segment. And we can confirm that by going into

63
03:32.570 --> 03:36.000
the details by editing that segments will edit our segment 10 there.

64
03:36.000 --> 03:39.660
And right here it says Set DHCP config. It says that because it's not currently

65
03:39.660 --> 03:43.000
set. There's no option here to delete it because it's not set.

66
03:43.000 --> 03:46.880
So to fix this, we need to go ahead and set up DHCP relay so that clients who

67
03:46.880 --> 03:51.090
do a discover message that discover and all the other conversations during the

68
03:51.090 --> 03:55.990
door process can go back and forth between those VMs on segment 10 and the DHCP

69
03:55.990 --> 03:58.000
server up on VLAN 21.

70
03:58.000 --> 04:02.910
So we'll click here to set the DHCP config for the type will specify its relay
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
03:58.000 --> 04:02.910
So we'll click here to set the DHCP config for the type will specify its relay

71
04:02.910 --> 04:07.710
because we're using NSX Federation with multiple sites. And for the profile

72
04:07.710 --> 04:12.300
will choose the profile that points to our server at 10.21.0.1 and we'll click

73
04:12.300 --> 04:17.000
on apply and then we'll scroll down and we'll click on save and then we'll

74
04:17.000 --> 04:17.000
click on close editing.

75
04:17.000 --> 04:20.450
So notice now that this logical area three IP address is going to be used by

76
04:20.450 --> 04:24.300
the gateway connected to this segment. Notice how it's now a hyperlink and that

77
04:24.300 --> 04:27.000
implies that we have DHCP services enabled there.

78
04:27.000 --> 04:30.610
And we clicked on this hyperlink right there. It would confirm for us what
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

78
04:27.000 --> 04:30.610
And we clicked on this hyperlink right there. It would confirm for us what

79
04:30.610 --> 04:36.000
those DHCP services are and it's DHCP relay to the server at 10.21.0.1.

80
04:36.000 --> 04:40.130
So now that we've set up the DHCP services, let's bring back our client. So

81
04:40.130 --> 04:44.200
here's our client and let's do an IF config and sure enough in the background

82
04:44.200 --> 04:46.000
it was trying to go ahead and get an IP address and it can be used.

83
04:46.000 --> 04:50.430
So we did a IP address and it got one once the relay was active enough. So now

84
04:50.430 --> 04:56.000
we can go ahead and do a ping to our default gateway and that's working and we

85
04:56.000 --> 05:00.140
do a ping out to the Internet to 888 and for grins we could also launch a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
04:56.000 --> 05:00.140
do a ping out to the Internet to 888 and for grins we could also launch a

86
05:00.140 --> 05:03.000
browser because we now have Internet connectivity.

87
05:03.000 --> 05:06.260
We should be able to get to any site out on the Internet that's reachable over

88
05:06.260 --> 05:10.520
the Internet. So if we go to for example fast.com, which is a speed test

89
05:10.520 --> 05:15.000
provided by Netflix, that seems to be working perfectly fine.

90
05:15.000 --> 05:18.480
So if we want to go to YouTube, we could open up another tab here, go to

91
05:18.480 --> 05:21.000
YouTube, once again working perfectly fine.

92
05:21.000 --> 05:24.380
So thanks for joining me in this set of videos and in the skill regarding

93
05:24.380 --> 05:28.280
working with stretch gateways and stretch segments effectively stretch

94
05:28.280 --> 05:32.000
networking in the world of NSX federations.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
05:28.280 --> 05:32.000
networking in the world of NSX federations.

95
05:32.000 --> 05:36.860
And also you my friend in another set of videos very, very soon. Until then, I

96
05:36.860 --> 05:41.000
hope this has been informative and I'd like to thank you for viewing.