WEBVTT

1
00:00.000 --> 00:02.280
All right, it's time to get physical.

2
00:02.280 --> 00:04.560
We're gonna take a look at the physical infrastructure here

3
00:04.560 --> 00:06.520
to make sure that these VLANs exist,

4
00:06.520 --> 00:09.640
specifically VLAN 11 and 12 and 13,

5
00:09.640 --> 00:12.680
and also that we have a default gateway IP address

6
00:12.680 --> 00:15.040
associated with our top of rack switch here,

7
00:15.040 --> 00:17.400
connected in association with those VLANs.

8
00:17.400 --> 00:20.520
And we also wanna make sure that we have NAT support

9
00:20.520 --> 00:23.680
out to the internet, either here at this top of rack switch,

10
00:23.680 --> 00:26.560
if it supports it or here at this router,

11
00:26.560 --> 00:28.600
as that traffic is going out to the internet.

12
00:28.600 --> 00:30.560
So with this topology in mind,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:28.600 --> 00:30.560
So with this topology in mind,

13
00:30.560 --> 00:34.320
let's verify VLAN 11, 12 and 13.

14
00:34.320 --> 00:36.720
So here we are at the CLI for my top of rack switch.

15
00:36.720 --> 00:39.720
As I mentioned, I'm using a Cisco catalyst

16
00:39.720 --> 00:40.920
multiplayer switch.

17
00:40.920 --> 00:43.720
So whatever you wanna use for the functionality here

18
00:43.720 --> 00:45.840
for the default gateway,

19
00:45.840 --> 00:47.760
and also for connectivity to these VLANs,

20
00:47.760 --> 00:49.080
is perfectly fine.

21
00:49.080 --> 00:52.480
Whether it's Cisco products or products from HP,

22
00:52.480 --> 00:54.560
or products from some else like Fortinet,

23
00:54.560 --> 00:57.040
once again, it really doesn't matter which vendor you're using,

24
00:57.040 --> 00:58.960
as long as you can provide the services that you need.

25
00:58.960 --> 01:01.760
So let's start off by verifying that we have these VLANs
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
00:58.960 --> 01:01.760
So let's start off by verifying that we have these VLANs

26
01:01.760 --> 01:04.320
that they exist here on my top of rack switch.

27
01:04.320 --> 01:06.000
So on this Cisco multiplayer switch,

28
01:06.000 --> 01:08.880
I'm gonna do a show VLAN brief, just like that,

29
01:08.880 --> 01:11.600
just to verify that the VLANs exist.

30
01:11.600 --> 01:14.800
So here I've got VLANs 11, 12 and 13,

31
01:14.800 --> 01:16.320
and while I'm here, I'm gonna go ahead

32
01:16.320 --> 01:18.840
and just rename those so that when I see them,

33
01:18.840 --> 01:19.800
I won't just be a number,

34
01:19.800 --> 01:21.720
but I can also remember what they're for.

35
01:21.720 --> 01:23.280
So I'm gonna go into configuration mode

36
01:23.280 --> 01:24.720
on this multiplayer switch,

37
01:24.720 --> 01:26.760
and then from here, type in VLAN 11,

38
01:26.760 --> 01:29.360
and say name is gonna be management,

39
01:29.360 --> 01:32.960
and then for VLAN 12, the name is gonna be front end,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:29.360 --> 01:32.960
and then for VLAN 12, the name is gonna be front end,

40
01:32.960 --> 01:36.960
and then for VLAN 13, the name is gonna be workload.

41
01:36.960 --> 01:41.040
Not workload, whatever that is, but workload,

42
01:41.040 --> 01:43.480
and let's do a do show VLAN brief,

43
01:43.480 --> 01:44.640
just to verify this took,

44
01:44.640 --> 01:47.080
and check this out, there's VLAN 11's name,

45
01:47.080 --> 01:48.040
and VLAN 12's name,

46
01:48.040 --> 01:51.280
and they need to exit out here before that third rule takes.

47
01:51.280 --> 01:54.120
So now if we do a show VLAN brief, press enter,

48
01:54.120 --> 01:55.560
then I've got the appropriate names here

49
01:55.560 --> 01:56.520
on those three VLANs.

50
01:56.520 --> 01:58.560
So the actual names aren't too important,

51
01:58.560 --> 02:00.360
what's really important is the actual VLAN numbers
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
01:58.560 --> 02:00.360
what's really important is the actual VLAN numbers

52
02:00.360 --> 02:01.240
that they exist.

53
02:01.240 --> 02:03.360
Next, let's take a look at this multiplayer switch,

54
02:03.360 --> 02:07.080
just to verify that I had the IP address of .1

55
02:07.080 --> 02:09.520
on each of those respective subnets associated

56
02:09.520 --> 02:10.840
with these three VLANs.

57
02:10.840 --> 02:11.920
So on this multiplayer switch,

58
02:11.920 --> 02:15.040
we're gonna do a show IP interface for VLAN 11,

59
02:15.040 --> 02:15.880
and so for the output,

60
02:15.880 --> 02:17.440
let me go ahead and actually only include output

61
02:17.440 --> 02:21.360
that has the text address in it, a press enter,

62
02:21.360 --> 02:22.200
just to confirm.

63
02:22.200 --> 02:25.880
So this is the IP address for the logical layer three interface

64
02:25.880 --> 02:28.480
that's part of our associate with VLAN 11

65
02:28.480 --> 02:29.920
on this multiplayer switch,

66
02:29.920 --> 02:32.000
but we'll specify VLAN 12 right there,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
02:29.920 --> 02:32.000
but we'll specify VLAN 12 right there,

67
02:32.000 --> 02:36.000
and that's 10, 12, 12, 1, that looks good as well.

68
02:36.000 --> 02:38.560
And then a similar treatment for VLAN 13,

69
02:38.560 --> 02:41.040
and that looks good as well.

70
02:41.040 --> 02:42.480
So the next thing I wanna verify

71
02:42.480 --> 02:44.960
is that I have a network address translation set up.

72
02:44.960 --> 02:46.880
So also from the top of rack switch,

73
02:46.880 --> 02:48.040
from a routing perspective,

74
02:48.040 --> 02:49.320
let's verify we can get to the internet

75
02:49.320 --> 02:52.760
that's through a ping out to 8.8.8.8,

76
02:52.760 --> 02:53.760
and that works.

77
02:53.760 --> 02:57.400
We could also a trace out to 8.8.8.8.

78
02:57.400 --> 02:59.200
And let me go ahead and do a break there.

79
02:59.200 --> 03:00.040
I just wanna verify
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
02:59.200 --> 03:00.040
I just wanna verify

80
03:00.040 --> 03:01.680
we're actually getting out to the internet.

81
03:01.680 --> 03:04.280
So this top of rack switch can get out to the internet,

82
03:04.280 --> 03:07.040
which also implies that this router right here

83
03:07.040 --> 03:09.760
is providing network address translation services.

84
03:09.760 --> 03:12.080
So I also wanna verify that this router here

85
03:12.080 --> 03:13.920
is not only doing address translation

86
03:13.920 --> 03:16.200
for clients that are on this common network,

87
03:16.200 --> 03:17.960
but also for clients that are going to the internet

88
03:17.960 --> 03:20.080
sourcing it from the 10 address space as well.

89
03:20.080 --> 03:22.160
So let me take you over to this router here,

90
03:22.160 --> 03:23.840
which in my topology happens to be a little

91
03:23.840 --> 03:25.040
4 to 8 firewall.

92
03:25.040 --> 03:26.600
So here on this router,

93
03:26.600 --> 03:29.360
this is the 4 to 8 device providing these routing services.

94
03:29.360 --> 03:31.440
Here it shows us that it's configured to do NAT
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
03:29.360 --> 03:31.440
Here it shows us that it's configured to do NAT

95
03:31.440 --> 03:33.340
for traffic source from 10 anything.

96
03:33.340 --> 03:35.800
So not only can the top of rack switch

97
03:35.800 --> 03:36.720
get out to the internet,

98
03:36.720 --> 03:39.440
but if traffic is sourced from any of these clients here

99
03:39.440 --> 03:40.720
going out to the internet,

100
03:40.720 --> 03:43.120
it's gonna be able to provide address translation services

101
03:43.120 --> 03:43.960
as well.

102
03:43.960 --> 03:45.440
I also wanna verify that this router

103
03:45.440 --> 03:48.800
knows how to forward back to the 10 network address space.

104
03:48.800 --> 03:51.280
And to do that, let me verify its static routes.

105
03:51.280 --> 03:53.680
So if we go to network on the left here

106
03:53.680 --> 03:55.160
and we go to static routes.

107
03:55.160 --> 03:56.560
So what I'm doing here on this router

108
03:56.560 --> 03:59.520
is I've got a static route that says to get to 10 anything,

109
03:59.520 --> 04:01.440
hand it back to the top of rack switch,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

109
03:59.520 --> 04:01.440
hand it back to the top of rack switch,

110
04:01.440 --> 04:03.600
who can then forward it to the intended party.

111
04:03.600 --> 04:06.120
Now we also could have used dynamic routing protocols

112
04:06.120 --> 04:09.280
like OSPF or BGP, et cetera.

113
04:09.280 --> 04:10.440
However, for the lab environment,

114
04:10.440 --> 04:12.960
I thought a simple static route with no games involved

115
04:12.960 --> 04:14.800
would be more than enough, which it is.

116
04:14.800 --> 04:16.960
Also, one of my intentions in this set of videos

117
04:16.960 --> 04:19.840
is to make sure you see every single part that's involved.

118
04:19.840 --> 04:22.520
So we've taken a look now at the top of rack switch.

119
04:22.520 --> 04:24.840
It has the appropriate logical IP addresses

120
04:24.840 --> 04:26.120
for these three networks here.

121
04:26.120 --> 04:28.760
And also our routing device here

122
04:28.760 --> 04:30.720
is employing address translation
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

122
04:28.760 --> 04:30.720
is employing address translation

123
04:30.720 --> 04:33.240
and also has a route back to the 10 address space.

124
04:33.240 --> 04:36.160
Now, another thing I'd love to do is set up DHGP services

125
04:36.160 --> 04:38.260
for these three networks, the management, front end

126
04:38.260 --> 04:39.100
and workload.

127
04:39.100 --> 04:40.640
Now, even though it's not required,

128
04:40.640 --> 04:43.600
we don't have to use DHGP for Kubernetes services.

129
04:43.600 --> 04:45.560
However, if we have DHGP,

130
04:45.560 --> 04:48.160
it'll make it very easy to drop in a VM

131
04:48.160 --> 04:49.680
on any of these networks.

132
04:49.680 --> 04:53.640
And verify from that perspective of that VM connectivity,

133
04:53.640 --> 04:56.560
including DNS name resolution and connectivity

134
04:56.560 --> 04:57.520
out to the internet.

135
04:57.520 --> 05:00.040
So in the next video, let's work with our top of rack switch
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

135
04:57.520 --> 05:00.040
So in the next video, let's work with our top of rack switch

136
05:00.040 --> 05:03.000
once again and set up the DHGP services

137
05:03.000 --> 05:05.920
for the management, front end and workload networks.