1
00:00:01,220 --> 00:00:08,250
In the section we are going to talk about Meilan and thinking application in campus networks.

2
00:00:08,260 --> 00:00:14,470
Let's take a look at the overview of Willum first we plan is we're to local area.

3
00:00:14,530 --> 00:00:20,200
As you know and each we learn is one word Testament.

4
00:00:20,200 --> 00:00:30,030
And as we discussed before they pro-white isolation to us villain or Rachel or network works in the

5
00:00:30,030 --> 00:00:36,960
same way as a physical local area network with the exception that the hosts don't need to be located

6
00:00:37,020 --> 00:00:40,160
on the same physical network to be linked.

7
00:00:40,290 --> 00:00:47,820
Segmentation is the division of the network into groups work for Connect unspecified groups with each

8
00:00:47,820 --> 00:00:55,600
other regardless of network affiliation and for isolation of groups for security reasons.

9
00:00:55,890 --> 00:01:04,320
Using a best practice approach to segmentation makes it possible to maximize that use while securing

10
00:01:04,500 --> 00:01:16,010
sensitive data Whelan's can be segmented due to first may be terrific parents.

11
00:01:16,050 --> 00:01:20,940
Secondly traffic types

12
00:01:26,760 --> 00:01:39,460
Daughtry's Geographic group I'm writing wonderful as you can see and the effort is department based.

13
00:01:39,460 --> 00:01:45,970
For example this edge Q of a corporate building and

14
00:01:48,930 --> 00:01:56,120
this is the red and blue line and the gray line.

15
00:01:56,350 --> 00:02:03,410
If I signal the last using the department the pull information read we line users.

16
00:02:03,420 --> 00:02:12,020
Maybe human resources blue maybe I-T and gray may be the finance

17
00:02:16,870 --> 00:02:25,210
internet or design and network administrator can design a campus network with one of two modules.

18
00:02:25,210 --> 00:02:29,240
The first one is local Freelon.

19
00:02:29,600 --> 00:02:41,300
The second one is an to and Walen in the local Mudgal the local So which is connected to a distribution

20
00:02:41,360 --> 00:02:43,730
or core switch.

21
00:02:43,730 --> 00:02:49,970
This is where the routing is performed actually local Rylance will all the exits.

22
00:02:50,030 --> 00:02:58,820
But when the local access sewage and the distribution or course which in this model you use different

23
00:02:58,850 --> 00:03:08,840
Whelan's for different geographical regions for example as you can see that in the picture we have accounting

24
00:03:08,950 --> 00:03:20,490
Whelan that's reliant on for this location but for another location we are using we land 30 for the

25
00:03:20,900 --> 00:03:27,760
accounting for example engineering using we land to anyone here.

26
00:03:28,070 --> 00:03:34,720
And then we land 40 in other location of the cardboard building.

27
00:03:39,020 --> 00:03:47,310
And then Whelan's are dispersed throughout the network on multiple Swades no matter where the user plugs.

28
00:03:47,360 --> 00:03:55,670
And they will always be assigned the same wheel and membership resources for this user will be on the

29
00:03:55,670 --> 00:04:03,650
same subnet management of and temp villans typically used v.t. to trunked soulmates.

30
00:04:03,650 --> 00:04:11,210
And this allows for easier management and you can see that in the picture again this building may be

31
00:04:11,330 --> 00:04:22,890
in Paris and the other building may be in Amsterdam and here maybe where €30

32
00:04:25,690 --> 00:04:39,410
and if I is a real one for enginering in here and Villon through is I the and when I'm through is finals

33
00:04:39,560 --> 00:04:48,510
in Parus they are going to be same for Amsterdam and Tokyo to

34
00:04:52,370 --> 00:04:55,630
and let's take a look to the voice real and concept.

35
00:04:55,640 --> 00:05:04,340
Now usually I sit next to a computer on the same desk.

36
00:05:04,340 --> 00:05:12,440
They record the same you pick cables as computers use and they use internet if you want to connect them

37
00:05:12,470 --> 00:05:18,100
to us which we usually use the method in the picture as you can see.

38
00:05:18,260 --> 00:05:22,180
You probably want to separate words and they are terrific.

39
00:05:22,340 --> 00:05:30,900
And this is something we can do with voice Whelan's as you can see that in our figure just one cable

40
00:05:30,900 --> 00:05:42,710
is coming to the IP phone and IP phone has two parts the first part is the local area network port which

41
00:05:42,710 --> 00:05:55,210
with Plack actually this cable coming from Savage and the other port is connected to PC and that part

42
00:05:55,210 --> 00:06:04,970
is known as the PC PARC and we are using different villans to carry data and what's terrific in this

43
00:06:04,970 --> 00:06:11,660
example we are using we learn thoroughly and will antenne will unthawed is carrying the worst traffic

44
00:06:11,690 --> 00:06:14,560
and then carrying the PC data.

45
00:06:14,660 --> 00:06:17,270
And here is the conflagrations steps.

46
00:06:17,990 --> 00:06:24,400
For example if we are using Fester's 0 or 16 port

47
00:06:28,060 --> 00:06:35,320
we are going to the interface more by typing interface known and 0 16 and we are tapping the access

48
00:06:35,320 --> 00:06:45,140
port switchboard access real content and we are defining the PC data and we're using the switch port

49
00:06:45,230 --> 00:06:52,010
voice mealand command and riding the worst we land as well.

50
00:06:52,370 --> 00:06:58,020
Let's take a look to the wheel and truanting think again as we talk in our pervious sections.

51
00:06:58,760 --> 00:07:08,850
An access port can Terry just when we land and transports can carry multiple wheelers we can use real

52
00:07:08,850 --> 00:07:15,790
and wandered and just rely on 200 for these two ports.

53
00:07:15,880 --> 00:07:20,420
But this guy can carry both of

54
00:07:25,030 --> 00:07:28,550
here's the configuration steps of the villains.

55
00:07:28,720 --> 00:07:36,280
First we are creating the realigns and the configuration Maat for example on one.

56
00:07:36,350 --> 00:07:38,510
And we can define a name.

57
00:07:38,630 --> 00:07:40,030
This is arbitrary.

58
00:07:41,300 --> 00:07:43,340
And we are defining We 200.

59
00:07:43,370 --> 00:07:53,260
And the name of it to them we are going to the under interface Mauch by typing interface.

60
00:07:53,360 --> 00:07:56,540
Take 0 for example which is this part

61
00:08:00,030 --> 00:08:03,180
we are defining it to the access point by typing.

62
00:08:03,180 --> 00:08:11,260
So we put more access and we are making the villain configuration by typing switchboard access.

63
00:08:11,270 --> 00:08:18,480
We learn and will a number if we want to configure it transport.

64
00:08:18,740 --> 00:08:20,970
We are going under the interface mode.

65
00:08:21,000 --> 00:08:30,260
Again and we are typing switch you're drunk and and encapsulation portico which is about like you for

66
00:08:30,260 --> 00:08:30,810
now.

67
00:08:32,410 --> 00:08:35,490
And we are defining the transport by typing port.

68
00:08:35,530 --> 00:08:47,320
Not to rank and we are defining the villains that we want to carry from this tronk and that's it we

69
00:08:47,320 --> 00:08:55,480
can use to try and link protocols when we want to implement trunking and they are I s.l and that one.

70
00:08:55,480 --> 00:09:03,230
Q I sell as a Cisco property tracking protocol which provides tracking for us and top line.

71
00:09:03,230 --> 00:09:06,970
Q Is an industry standard protocol.

72
00:09:07,030 --> 00:09:17,080
Q Has less framework than ISIL and as a result that one is more effective than s.l especially in small

73
00:09:17,080 --> 00:09:20,600
frame's when that one queue load is 4 bytes.

74
00:09:20,660 --> 00:09:27,580
I hersel is 30 by let's take a look to that my Cuneta real and concept.

75
00:09:27,580 --> 00:09:36,460
Normally a transport can send and receive that one Curiel intact into Italy and France if the switch

76
00:09:36,730 --> 00:09:41,620
receives an antique from Antec frame from the transport.

77
00:09:41,650 --> 00:09:50,080
These friends are forward to another reland configured as the native willat the native realize that

78
00:09:50,080 --> 00:09:59,290
when the true difference which must be say otherwise the native Melanne mismatch warning is taken and

79
00:09:59,470 --> 00:10:06,130
Cisco uses Cisco the skurried protocol CTP when doing this.

80
00:10:06,280 --> 00:10:17,460
And please keep in mind that the fall they too will learn is what here is how we can configure a trunk.

81
00:10:17,460 --> 00:10:26,310
We are going under the interface Maut and we are typing the and Cupps lation protocol and we are using

82
00:10:26,310 --> 00:10:31,010
to switch Portmore trunk and this line is actually optional.

83
00:10:31,020 --> 00:10:35,070
We can define it if we can define that better.

84
00:10:35,250 --> 00:10:42,060
But if not all other religions will go from the transport to a fire transport.

85
00:10:42,060 --> 00:10:50,610
We are using show interfaces and the interface name and the switchboard.

86
00:10:50,610 --> 00:10:59,450
Actually we are seeing that the Edmond's through Maut which means what we configured for this port and

87
00:10:59,450 --> 00:11:08,110
the operational mode which means what this port is actually behaving right now.

88
00:11:09,270 --> 00:11:12,760
Is it trunk or is there a problem.

89
00:11:12,780 --> 00:11:21,570
We can't see by using this comment and the other comment that we can verify the trunk port is show interface's

90
00:11:21,930 --> 00:11:27,730
trunk which shows us the interfaces making actual trunking.

91
00:11:27,770 --> 00:11:36,500
At that moment to us and let's take a look to the dynamic trecking trying per local DTP DTP.

92
00:11:36,500 --> 00:11:44,900
Is this Cisco purportedly working Pearla code up by Cisco Systems for the purpose of negotiating trunking

93
00:11:45,020 --> 00:11:52,190
on a link between two villaine wear sweats and for negotiating the type of tracking encapsulation to

94
00:11:52,190 --> 00:11:53,800
be used.

95
00:11:53,870 --> 00:12:02,790
It works on late 2 of the OSA module and we untransformed using DTP may utilize either.

96
00:12:02,810 --> 00:12:11,780
I believe that one Q or Cisco myself in repeat the following switch Portmore settings exists.

97
00:12:13,100 --> 00:12:14,450
And their access

98
00:12:16,890 --> 00:12:23,540
trunk dynamic outhaul and dynamic.

99
00:12:23,570 --> 00:12:28,270
This will that would be better to underline this guy's

100
00:12:31,830 --> 00:12:41,250
dynamic other than this about trying and access access puts the Internet port into permanent non-throwing

101
00:12:41,320 --> 00:12:52,100
mode and negotiates to convert the link into and not try and link the Internet port becomes a non transport.

102
00:12:52,240 --> 00:12:58,000
Even if the neighboring port does not agree to the change.

103
00:12:58,000 --> 00:13:06,320
Trunk puts the Internet port into permanent trunking mode and negotiates to convert the link into the

104
00:13:06,580 --> 00:13:17,420
trunk link the port becomes a transport even if the neighboring port does not agree to the change the

105
00:13:17,420 --> 00:13:23,990
dynamic auto makes the Internet port willing to call to link to a trunk link.

106
00:13:24,290 --> 00:13:26,960
The port becomes a trunk port.

107
00:13:27,020 --> 00:13:32,700
If the neighboring port is set to trank or dynamic boat mode.

108
00:13:33,140 --> 00:13:37,710
This is the default mode for all Internet ports.

109
00:13:38,000 --> 00:13:45,430
And lastly Barragan talk about dynamic desirable which makes the port actively attempt to compare two

110
00:13:45,450 --> 00:13:47,840
linked to the trunk link.

111
00:13:47,990 --> 00:13:49,830
The port becomes a transport.

112
00:13:49,850 --> 00:13:59,360
If the neighboring Internet port is set to trunk dynamic servo or dynamic auto mode and here are the

113
00:13:59,360 --> 00:14:05,110
best practices of the real NS and tracking.

114
00:14:05,140 --> 00:14:15,460
First we need to work using we learn when to write security issues because Villon one is the default

115
00:14:15,460 --> 00:14:19,660
Vila set count.

116
00:14:19,690 --> 00:14:22,870
We need to configure track ports manually.

117
00:14:22,900 --> 00:14:31,220
Long use DTP place you can face with big problems if you use DTP actually.

118
00:14:31,470 --> 00:14:36,680
And third we need to use that key instead of SL.

119
00:14:36,830 --> 00:14:45,440
We need to use S-sh instead of not for remote connections because S-sh news anchor option for the connection

120
00:14:46,670 --> 00:14:54,730
and we need to make the native willen different from real man to prove our DTP spoofing.
