1
00:00:02,520 --> 00:00:05,437
(theatrical music)

2
00:00:08,686 --> 00:00:09,938
- So in the last set of videos,

3
00:00:09,938 --> 00:00:12,471
I had a pretty good what
I think as an example

4
00:00:12,471 --> 00:00:16,638
of using GNS3 to build up a
CCNA level EIGRP routing lab.

5
00:00:18,440 --> 00:00:20,599
So, but we also have to
know a little bit about

6
00:00:20,599 --> 00:00:22,995
switching for the CCNA,
so let's do that as well.

7
00:00:22,995 --> 00:00:27,185
Let's build up a CCNA level switching lab.

8
00:00:27,185 --> 00:00:29,440
So as usual, step number one for you

9
00:00:29,440 --> 00:00:31,246
if you were going to
design a lab of your own

10
00:00:31,246 --> 00:00:32,818
is to write out your objectives,

11
00:00:32,818 --> 00:00:34,468
what you want to accomplish.

12
00:00:34,468 --> 00:00:37,651
Step number two, draw
your topology diagram

13
00:00:37,651 --> 00:00:39,960
on a piece of paper or something
so you have it plotted out

14
00:00:39,960 --> 00:00:41,553
and you know what you're going to build.

15
00:00:41,553 --> 00:00:45,187
Then open up GNS3 and
actually start building it.

16
00:00:45,187 --> 00:00:47,670
So what kind of objectives
do we have for this?

17
00:00:47,670 --> 00:00:49,638
Well, this is gonna be pretty much

18
00:00:49,638 --> 00:00:51,227
an all encompassing lab here.

19
00:00:51,227 --> 00:00:53,732
We're gonna have a lot of stuff going on.

20
00:00:53,732 --> 00:00:55,449
So in this particular topology,

21
00:00:55,449 --> 00:00:58,837
we're gonna create three
routers and three switches.

22
00:00:58,837 --> 00:01:00,302
Of those switches,

23
00:01:00,302 --> 00:01:04,643
one of them will be the
built-in Ethernet Switch Node

24
00:01:04,643 --> 00:01:07,907
and the other two will
be EtherSwitch Routers.

25
00:01:07,907 --> 00:01:10,611
So if you're trying to
replicate this lab yourself,

26
00:01:10,611 --> 00:01:13,521
you're definitely gonna need
some IOS software version

27
00:01:13,521 --> 00:01:16,529
that's capable of supporting
the EtherSwitch module

28
00:01:16,529 --> 00:01:19,622
like the 2600 series or the 3700 series

29
00:01:19,622 --> 00:01:21,596
or something like that.

30
00:01:21,596 --> 00:01:25,160
Okay, so here are the
objective we wanna do.

31
00:01:25,160 --> 00:01:28,827
Number one, as far as the
EtherSwitch Routers are concerned,

32
00:01:28,827 --> 00:01:31,605
whenever you connect them together,

33
00:01:31,605 --> 00:01:34,135
the ports on both sides
have to be the same.

34
00:01:34,135 --> 00:01:35,883
In other words, what I mean by that is

35
00:01:35,883 --> 00:01:37,024
you're not to build this lab

36
00:01:37,024 --> 00:01:40,975
where one side of the cable
is connecting to port 1/6

37
00:01:40,975 --> 00:01:44,576
and the other side is
connecting to port 1/2.

38
00:01:44,576 --> 00:01:47,167
They should be the same port number

39
00:01:47,167 --> 00:01:48,365
and that's gonna be relevant

40
00:01:48,365 --> 00:01:50,737
because when we manipulate spanning tree,

41
00:01:50,737 --> 00:01:53,248
that's gonna be important.

42
00:01:53,248 --> 00:01:57,777
Next, we cannot manually
configure VLANs-4 or 5

43
00:01:57,777 --> 00:02:00,973
on the VTP Client and I'll
show you in just a second

44
00:02:00,973 --> 00:02:03,172
what the topology is that
we're gonna build up,

45
00:02:03,172 --> 00:02:05,375
but we're gonna be using VTP in here

46
00:02:05,375 --> 00:02:07,738
and one of the switches
is gonna be a VTP Client

47
00:02:07,738 --> 00:02:11,333
so basically that client is
gonna have to dynamically learn

48
00:02:11,333 --> 00:02:15,500
about these VLANs-4 and 5
via VTP, from the VTP server.

49
00:02:18,260 --> 00:02:20,376
And then the second to the last bullet,

50
00:02:20,376 --> 00:02:23,016
ensure that packets send between
router one and router two

51
00:02:23,016 --> 00:02:25,804
on VLAN-5 traverse across
the two EtherSwitch Routers

52
00:02:25,804 --> 00:02:27,524
on the higher-numbered ports.

53
00:02:27,524 --> 00:02:29,320
I'll clarify that in just a second

54
00:02:29,320 --> 00:02:31,159
when I show you the topology diagram.

55
00:02:31,159 --> 00:02:32,651
And then we're not gonna
use any routing here

56
00:02:32,651 --> 00:02:33,661
other than static routes.

57
00:02:33,661 --> 00:02:35,787
This is not a dynamic routing lab

58
00:02:35,787 --> 00:02:37,128
so we're just gonna use
simple static routes

59
00:02:37,128 --> 00:02:39,128
for end-to-end connectivity.

60
00:02:39,128 --> 00:02:44,079
So this is what we're actually
going to build right here.

61
00:02:44,079 --> 00:02:45,750
So how is this gonna work?

62
00:02:45,750 --> 00:02:49,079
Well, so as far as the built-in

63
00:02:49,079 --> 00:02:51,582
Ethernet Switch Node is concerned,

64
00:02:51,582 --> 00:02:54,733
these Ethernet Switch Nodes
do not do spanning tree,

65
00:02:54,733 --> 00:02:58,900
so you never want to connect
an Ethernet Switch Node

66
00:02:59,886 --> 00:03:04,288
to an EtherSwitch Router
because this is like a hub.

67
00:03:04,288 --> 00:03:06,290
It could lead you to have bridging loops

68
00:03:06,290 --> 00:03:08,464
because it doesn't
implement spanning tree,

69
00:03:08,464 --> 00:03:10,689
but we still wanna get experience with it,

70
00:03:10,689 --> 00:03:14,333
with how to use it in GNS3 so
that's why I put it in here,

71
00:03:14,333 --> 00:03:16,868
although technically you're
not gonna be tested on that

72
00:03:16,868 --> 00:03:18,393
at the CCNA level.

73
00:03:18,393 --> 00:03:22,421
So here, we're gonna test
your ability to implement

74
00:03:22,421 --> 00:03:23,993
the Ethernet Switch Node,

75
00:03:23,993 --> 00:03:27,463
make sure that one of the
links is trunking with 802.1q,

76
00:03:27,463 --> 00:03:31,335
the other two links are
access ports in VLANs-2 and 3

77
00:03:31,335 --> 00:03:33,873
and they'll pretty much
max out the capabilities

78
00:03:33,873 --> 00:03:37,438
that you can do in the EtherSwitch Node.

79
00:03:37,438 --> 00:03:39,363
And then as far as these two

80
00:03:39,363 --> 00:03:41,240
EtherSwitch Routers are concerned,

81
00:03:41,240 --> 00:03:42,689
you're gonna have two links.

82
00:03:42,689 --> 00:03:44,904
We're gonna have some redundant links here

83
00:03:44,904 --> 00:03:45,737
and that's gonna allow us to do

84
00:03:45,737 --> 00:03:47,593
some spanning tree manipulation.

85
00:03:47,593 --> 00:03:51,981
One of them, the guy in the
top is gonna be my VTP Server.

86
00:03:51,981 --> 00:03:54,990
The device on the bottom
will be a VTP Client.

87
00:03:54,990 --> 00:03:58,248
Once you have your
802.1q links functional,

88
00:03:58,248 --> 00:04:02,836
VLANs-4 and 5 which will be
configured up here on the server

89
00:04:02,836 --> 00:04:06,684
should be propagated
downstream to the client

90
00:04:06,684 --> 00:04:08,968
and you should see that.

91
00:04:08,968 --> 00:04:12,897
And then lastly, whatever
port numbers you select

92
00:04:12,897 --> 00:04:14,690
are completely up to you,

93
00:04:14,690 --> 00:04:18,329
but let's say for example,
just to put something in here,

94
00:04:18,329 --> 00:04:20,852
we had port 1/2 here

95
00:04:20,852 --> 00:04:24,376
which would then connect to 1/2 down herea

96
00:04:24,376 --> 00:04:28,543
and let's say this one
was 1/4 connecting to 1/4.

97
00:04:31,362 --> 00:04:34,147
As far as spanning tree
manipulation is concerned,

98
00:04:34,147 --> 00:04:37,730
the objective here is
that when router one,

99
00:04:39,819 --> 00:04:41,214
so router one knows,

100
00:04:41,214 --> 00:04:43,580
both of these routers are
gonna participate in two VLANs

101
00:04:43,580 --> 00:04:46,239
so they're actually gonna
have two IP addresses.

102
00:04:46,239 --> 00:04:50,406
Router one will be 1.2.4.1
and he'll also have 1.2.5.1.

103
00:04:53,610 --> 00:04:56,129
And over here, router
two on this interface,

104
00:04:56,129 --> 00:04:58,712
he'll have 1.2.4.2 and 1.2.5.2.

105
00:05:01,055 --> 00:05:04,117
That's why these links
have to be 802.1q trunks

106
00:05:04,117 --> 00:05:06,699
so they support two separate subnets.

107
00:05:06,699 --> 00:05:10,032
So the idea is when router one on VLAN-5

108
00:05:11,298 --> 00:05:14,211
pings router two on VLAN-5,

109
00:05:14,211 --> 00:05:19,029
in other words, when from
router one you ping 1.2.5.2,

110
00:05:19,029 --> 00:05:22,446
those packets should take this path here.

111
00:05:23,376 --> 00:05:26,038
They should take the
highest-numbered port,

112
00:05:26,038 --> 00:05:28,578
whatever that is in your
particular topology.

113
00:05:28,578 --> 00:05:30,306
And then of course the return traffic

114
00:05:30,306 --> 00:05:32,344
should also take that particular path.

115
00:05:32,344 --> 00:05:34,180
As far as spanning tree is concerned,

116
00:05:34,180 --> 00:05:37,024
this link here should be blocked.

117
00:05:37,024 --> 00:05:40,698
There should not be any
traffic on VLAN-5 only

118
00:05:40,698 --> 00:05:42,509
going across that link.

119
00:05:42,509 --> 00:05:44,021
It should be blocked.

120
00:05:44,021 --> 00:05:45,463
Okay, so that being the case,

121
00:05:45,463 --> 00:05:47,800
that concludes this particular video.

122
00:05:47,800 --> 00:05:48,773
In the next video,

123
00:05:48,773 --> 00:05:52,729
we're gonna start building
this topology within GNS3.

124
00:05:52,729 --> 00:05:55,646
(theatrical music)