WEBVTT

1
00:00.000 --> 00:04.290
All right, this time to jump in the lab and do some configuration and our focus

2
00:04.290 --> 00:04.520
isn't

3
00:04.520 --> 00:08.280
really on making sure we know how to get onto a VLAN interface and configure an

4
00:08.280 --> 00:08.920
IP address

5
00:08.920 --> 00:11.920
because that's more CCNA level knowledge.

6
00:11.920 --> 00:16.060
What our focus should be on here is as we are configuring our SVI's and our IP

7
00:16.060 --> 00:16.800
addresses

8
00:16.800 --> 00:19.840
and such that we're thinking about the topology.

9
00:19.840 --> 00:23.550
Again, we want to become one with layer two and layer three and one way as we

10
00:23.550 --> 00:24.240
can do that

11
00:24.240 --> 00:29.210
is really by making sure we're grasping the traffic flow that's going to occur

12
00:29.210 --> 00:29.680
among these

13
00:29.680 --> 00:31.760
different SVI's.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:29.680 --> 00:31.760
different SVI's.

14
00:31.760 --> 00:33.640
So let's just go ahead and go through these lab steps.

15
00:33.640 --> 00:37.080
First of all, we're to configure an SVI for VLAN 10.

16
00:37.080 --> 00:41.450
So I'm going to again switch one first here, do an interface VLAN 10 and we're

17
00:41.450 --> 00:41.920
told to

18
00:41.920 --> 00:50.890
give it an IP address of 10.0.10 and switch one gets .1 and this is a /24 and

19
00:50.890 --> 00:51.240
then VLAN

20
00:51.240 --> 00:55.200
interfaces on most Cisco platforms default to being in a shutdown state.

21
00:55.200 --> 00:56.760
So I'm going to do a no shut.

22
00:56.760 --> 01:01.770
The other big requirement for VLAN interfaces is that the layer two VLAN must
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:56.760 --> 01:01.770
The other big requirement for VLAN interfaces is that the layer two VLAN must

23
01:01.770 --> 01:02.560
exist and it

24
01:02.560 --> 01:07.110
must be enabled on an interface whether that's an access port or enabled on a

25
01:07.110 --> 01:07.920
trunk but either

26
01:07.920 --> 01:11.990
way we need a port in the forwarding state for that VLAN from a spanning tree

27
01:11.990 --> 01:12.800
perspective

28
01:12.800 --> 01:14.720
for the SVI to be online.

29
01:14.720 --> 01:19.100
It has to have traffic that it can, it has to be able to go somewhere basically

30
01:19.100 --> 01:19.280
.

31
01:19.280 --> 01:24.830
And so with VLAN 10, if I do a show VLAN here, we'll see that VLAN 10 has

32
01:24.830 --> 01:26.200
already been configured

33
01:26.200 --> 01:28.400
for us in this lab environment.

34
01:28.400 --> 01:30.520
So everything is good there.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:28.400 --> 01:30.520
So everything is good there.

35
01:30.520 --> 01:36.890
If I do a show interface VLAN 10, we should see that it's up and up and we do

36
01:36.890 --> 01:37.840
see indeed

37
01:37.840 --> 01:40.880
that it's online and operational.

38
01:40.880 --> 01:46.050
Now if I go back to my topology here, let's see here if I can do this, very

39
01:46.050 --> 01:46.760
good.

40
01:46.760 --> 01:51.600
So what I've done now is I've configured an SVI for VLAN 10.

41
01:51.600 --> 01:56.540
But because the switch knows that hey this SVI belongs to VLAN 10, it has

42
01:56.540 --> 01:58.040
mapped it already

43
01:58.040 --> 01:59.880
to the layer two VLAN.

44
01:59.880 --> 02:02.760
But in our topology here we see we don't actually have anywhere to go.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
01:59.880 --> 02:02.760
But in our topology here we see we don't actually have anywhere to go.

45
02:02.760 --> 02:06.800
I don't have an SVI down on switch three or over on switch two.

46
02:06.800 --> 02:10.780
And so I can't actually ping anything other than potentially routing among

47
02:10.780 --> 02:11.480
other layer

48
02:11.480 --> 02:12.480
three interfaces.

49
02:12.480 --> 02:17.990
If I had an SVI over here for a different VLAN, then we can switch traffic via

50
02:17.990 --> 02:18.480
layer

51
02:18.480 --> 02:21.280
three among any of these layer three interfaces.

52
02:21.280 --> 02:23.880
That's the nature of a multi layer switch.

53
02:23.880 --> 02:27.400
But this dot is the only one in our topology so far.

54
02:27.400 --> 02:32.320
And so we are clearly going to need to keep configuring.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
02:27.400 --> 02:32.320
And so we are clearly going to need to keep configuring.

55
02:32.320 --> 02:38.080
So back to the lab we go, we're going to go over to switch two now and finish

56
02:38.080 --> 02:38.840
this out

57
02:38.840 --> 02:41.840
by configuring another VLAN 10 interface.

58
02:41.840 --> 02:48.240
This time with an IP address of 10.0.10.2, still a slash 24.

59
02:48.240 --> 02:50.000
And don't forget to no shut it.

60
02:50.000 --> 02:53.680
So while that's coming online, we go back to our topology here.

61
02:53.680 --> 02:58.530
And now we've configured a VLAN 10 interface here, switch two nodes to attach

62
02:58.530 --> 02:59.400
that to VLAN

63
02:59.400 --> 03:00.400
10.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:59.400 --> 03:00.400
10.

64
03:00.400 --> 03:05.450
And based on this topology, we should see that we have communication among

65
03:05.450 --> 03:06.680
these different

66
03:06.680 --> 03:07.680
switches.

67
03:07.680 --> 03:11.230
Now, for the sake of this lab, the physical topology and the layer two

68
03:11.230 --> 03:12.200
configurations

69
03:12.200 --> 03:13.600
already in place.

70
03:13.600 --> 03:17.040
So we can trust that everything down here is where it needs to be.

71
03:17.040 --> 03:21.080
But now let's go and see if our layer three is indeed working.

72
03:21.080 --> 03:23.880
And one of the best ways to do that is to simply do a ping.

73
03:23.880 --> 03:28.040
So I should be able to ping 10.0.10.1 would be switch one.

74
03:28.040 --> 03:30.920
I'm on switch two.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
03:28.040 --> 03:30.920
I'm on switch two.

75
03:30.920 --> 03:35.760
And once our port goes through, we have to find the MAC address of the remote

76
03:35.760 --> 03:36.120
IP.

77
03:36.120 --> 03:38.120
And we do indeed see that we can ping it.

78
03:38.120 --> 03:42.720
So our topology, our logical topology is coming together appropriately.

79
03:42.720 --> 03:48.480
But now we're told to add a secondary subnet.

80
03:48.480 --> 03:52.640
And we're to add two secondary subnets actually to switch one and switch two.

81
03:52.640 --> 03:54.160
So we'll do this quickly.

82
03:54.160 --> 03:58.870
But as we recall in our conversation earlier, all I need to do is get on to V

83
03:58.870 --> 03:59.960
LAN 10.

84
03:59.960 --> 04:03.720
And now I can configure multiple subnets within this broadcast domain that we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
03:59.960 --> 04:03.720
And now I can configure multiple subnets within this broadcast domain that we

85
04:03.720 --> 04:04.260
're calling

86
04:04.260 --> 04:05.500
VLAN 10.

87
04:05.500 --> 04:07.840
So this command is very similar.

88
04:07.840 --> 04:14.860
This time it's going to be an IP address of 10.0.11 for the subnet still slash

89
04:14.860 --> 04:15.840
24.

90
04:15.840 --> 04:19.760
But now I add this secondary term to the end.

91
04:19.760 --> 04:23.200
And I can do the same thing with the dot 12.

92
04:23.200 --> 04:28.350
And so we just want to make sure that we can indeed assign many different

93
04:28.350 --> 04:29.640
secondary IP

94
04:29.640 --> 04:30.640
addresses.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
04:29.640 --> 04:30.640
addresses.

95
04:30.640 --> 04:34.020
So if I do a show run on this interface now, I should see that not only do I

96
04:34.020 --> 04:35.000
have the primary

97
04:35.000 --> 04:38.800
IP address, but I also have the secondary IP addresses.

98
04:38.800 --> 04:43.600
One thing to note is that anytime we do pings, anytime we're doing an operation

99
04:43.600 --> 04:44.320
where I need

100
04:44.320 --> 04:50.240
to source traffic, unless we force it to do so, a switch will never source the

101
04:50.240 --> 04:50.680
ping

102
04:50.680 --> 04:55.040
or source, maybe an SSH session from a secondary IP address.

103
04:55.040 --> 04:58.160
I would need to specify a source IP in that case.

104
04:58.160 --> 05:02.300
But generally speaking, secondary IP addresses are just there to serve as
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

104
04:58.160 --> 05:02.300
But generally speaking, secondary IP addresses are just there to serve as

105
05:02.300 --> 05:03.360
default gateways

106
05:03.360 --> 05:07.600
or whatever the situation is, but we're really not intended to be using them

107
05:07.600 --> 05:08.560
for our primary

108
05:08.560 --> 05:10.160
traffic flows.

109
05:10.160 --> 05:15.130
So now I'm just going to go over to switch to and do the same configuration in

110
05:15.130 --> 05:16.600
VLAN 10

111
05:16.600 --> 05:23.360
and then 10 dot 0 dot 11 dot 2 this time for switch to.

112
05:23.360 --> 05:29.360
And then same thing here for the dot 12 subnet.

113
05:29.360 --> 05:34.160
And if I confirm my configuration, everything looks good now.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

113
05:29.360 --> 05:34.160
And if I confirm my configuration, everything looks good now.

114
05:34.160 --> 05:38.560
So that is the configuration of our secondary subnets.

115
05:38.560 --> 05:44.080
Now we go back to the topology, we're told that we are maybe not quite where we

116
05:44.080 --> 05:44.520
need

117
05:44.520 --> 05:48.680
to be because switch three is down here and we have no way to manage it.

118
05:48.680 --> 05:50.960
So how can we manage it in this case?

119
05:50.960 --> 05:55.400
Well, all we need to do is configure a layer three interface.

120
05:55.400 --> 05:58.910
But yeah, we could potentially find the physical interface and convert that to

121
05:58.910 --> 06:00.200
layer three.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

121
05:58.910 --> 06:00.200
layer three.

122
06:00.200 --> 06:04.000
But probably what we really want to do is take advantage of VLAN 10, configure

123
06:04.000 --> 06:04.720
an SVI

124
06:04.720 --> 06:06.000
and VLAN 10.

125
06:06.000 --> 06:10.120
And this SVI will use the dot three IP address.

126
06:10.120 --> 06:13.640
So let's go ahead and go over to switch three now.

127
06:13.640 --> 06:17.160
Get on to VLAN 10 IP address.

128
06:17.160 --> 06:23.560
Now we got to go back to the 10 dot 0 dot 10 subnet dot three for switch three

129
06:23.560 --> 06:23.760
and then

130
06:23.760 --> 06:27.200
do a no shut.

131
06:27.200 --> 06:31.520
And if everything comes together here, VLAN 10 will come online and I should be
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

131
06:27.200 --> 06:31.520
And if everything comes together here, VLAN 10 will come online and I should be

132
06:31.520 --> 06:31.960
able to

133
06:31.960 --> 06:38.890
ping dot one and dot two because we're all on the same layer two domain at this

134
06:38.890 --> 06:39.800
point.

135
06:39.800 --> 06:40.800
So there we go.

136
06:40.800 --> 06:42.280
That is the end of this lab challenge.

137
06:42.280 --> 06:46.440
Again, it really was just creating VLAN interfaces and IP addresses.

138
06:46.440 --> 06:48.640
And the secondaries was kind of a cool thing.

139
06:48.640 --> 06:52.740
But for the most part, it really is all about maintaining in our minds as we

140
06:52.740 --> 06:53.640
progress through

141
06:53.640 --> 06:57.410
physical and logical topologies that we know how these logical topologies are

142
06:57.410 --> 06:58.840
coming together.

143
06:58.840 --> 07:03.600
And when we even look at the logical topology here, we can see directly how
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

143
06:58.840 --> 07:03.600
And when we even look at the logical topology here, we can see directly how

144
07:03.600 --> 07:04.520
these SVI's are

145
07:04.520 --> 07:08.150
able to communicate with one another because of the way that we express it by

146
07:08.150 --> 07:08.960
sort of blending

147
07:08.960 --> 07:11.240
the physical and logical together.

148
07:11.240 --> 07:13.840
I hope this has been informative for you and I'd like to thank you for viewing.