1
00:00:00,900 --> 00:00:07,930
So to configure a port on a switch as a trunk port supporting Cisco IP phones you would do the following.

2
00:00:09,670 --> 00:00:11,040
So first the on off switch.

3
00:00:11,110 --> 00:00:20,690
Well in this case the U.S. 500 I'm going to top the command show the LAN switch to see villans as you

4
00:00:20,690 --> 00:00:27,470
can see here we've got a default LAN and we've got our voice feline which is Bil'in to all interfaces

5
00:00:27,470 --> 00:00:29,970
are currently in the native land.

6
00:00:29,990 --> 00:00:36,900
In other words the default Bil'in So going into global configuration mode I can become Come on interface

7
00:00:37,010 --> 00:00:49,910
range if zero slash one slash one up to three and then I can type the command switchboard trunk encapsulation

8
00:00:50,180 --> 00:00:53,370
and then specify an encapsulation.

9
00:00:53,410 --> 00:01:00,290
Now in the past we may have chosen ISIL or editor or one key subscriber earphones only support one key.

10
00:01:00,530 --> 00:01:08,540
So we get to specify one key that I'm going to say switchboard mode trunk to force these ports to trunk

11
00:01:09,260 --> 00:01:19,990
and then switch port trunk native villaine one then I'm going to type switchboard with voice plan and

12
00:01:19,990 --> 00:01:28,600
in our case it's vigilante tapping the command do show run interface if 0 1 slash 1 will show me the

13
00:01:28,600 --> 00:01:31,960
running configuration of that specific port.

14
00:01:32,030 --> 00:01:35,390
I remember default commands don't show up in the running config.

15
00:01:35,620 --> 00:01:41,170
So you won't necessarily see all the commands we've just typed because some of them are they by default

16
00:01:41,800 --> 00:01:47,330
but as you can see here the port is trunking and the voice line is Vicente.

17
00:01:47,470 --> 00:01:53,080
The problem here is that all the lands will be allowed across the sea port which could potentially cause

18
00:01:53,080 --> 00:01:58,090
that issue where broad costs affect the processing of Cisco IP phones.

19
00:01:58,150 --> 00:02:01,150
So we should manually prune the trunk.

20
00:02:01,330 --> 00:02:08,680
So I'm going to to the command Switchfoot trunk allowed the plan and then I'm going to specify the villains

21
00:02:08,680 --> 00:02:15,150
that are allowed on certain switches you might only need to specify the voice Villon but in the U.S.

22
00:02:15,150 --> 00:02:23,030
500 I'm going to specify all the default villans Plus the voice of the land now tapping the command

23
00:02:23,060 --> 00:02:29,960
do show run and the specific interface shows me that I'm only allowing the native land Bil'in one on

24
00:02:29,960 --> 00:02:37,900
Ethernet Berlanti which is my voice villain and the other default villans supported on Cisco switches.

25
00:02:37,910 --> 00:02:45,860
So once again do show villans switch will allow me to see those default the lens one is the default

26
00:02:45,870 --> 00:02:47,190
the Ethernet.

27
00:02:47,220 --> 00:02:50,610
And then we have the villains for AFTI and Token Ring.

28
00:02:50,940 --> 00:02:53,660
So that's all you can figure an interface to support trunking.

29
00:02:53,670 --> 00:02:55,240
It's no longer recommended.

30
00:02:55,560 --> 00:02:59,760
But if you have an older switch you may need to configure it in this way.

31
00:02:59,960 --> 00:03:09,890
Last Yakutat the command show interface if 0 1 slash 1 switchboard and notice you can see here that

32
00:03:09,890 --> 00:03:15,380
the administrative mode is trunk the operational mode at the moment is trunk and kept solution has dropped

33
00:03:15,380 --> 00:03:16,770
one key.

34
00:03:16,790 --> 00:03:19,570
The native land is villaine one which is the default.

35
00:03:19,910 --> 00:03:27,720
The villains enabled across this interface all 1 to 1000 to 1005 the active villains at the moment of

36
00:03:27,720 --> 00:03:29,070
the 1 and 2.

37
00:03:29,390 --> 00:03:38,590
The voice the lion is the Leonti the recommended way to implement IP phones in a network infrastructure

38
00:03:38,980 --> 00:03:42,460
is to use multiple the land access ports.

39
00:03:42,460 --> 00:03:48,790
In this example we are configuring the port on the switch as an excess port but still configuring TV

40
00:03:48,790 --> 00:03:50,180
lands on that port.

41
00:03:50,350 --> 00:03:56,380
The phone will be in the voice Fillon and the PC will be in the data villaine tagged frame's will be

42
00:03:56,380 --> 00:04:01,120
sent to the phone so edited or one key frames are still used.

43
00:04:01,120 --> 00:04:06,690
Even though this is an access port untagged frames are sent to the PC.

44
00:04:06,700 --> 00:04:13,950
Now this flies in the face of what you learned in this CCMA course in the CCMA course we learnt then

45
00:04:13,960 --> 00:04:19,990
an access port belongs to a single plan that is not the case in this scenario.

46
00:04:20,140 --> 00:04:26,260
In this scenario the access port has to villans configured on it.

47
00:04:26,270 --> 00:04:30,730
Now there are multiple advantages to this method of implementation.

48
00:04:30,740 --> 00:04:37,160
The first one is that a multivalent access port can be configured as a secure port unlike the previous

49
00:04:37,160 --> 00:04:40,030
example where we configured the port as a trunk.

50
00:04:40,310 --> 00:04:45,740
The voice of an ID can also be discovered through CTP or L-L DP.

51
00:04:46,190 --> 00:04:50,280
So the manual configuration of villans on the phone is not required.

52
00:04:50,300 --> 00:04:54,220
It also allows for scalability from an IP addressing point of view.

53
00:04:54,530 --> 00:05:00,450
The issue that you may encounter in the real world is that if a glossy address has been allocated to

54
00:05:00,450 --> 00:05:07,740
your PCs and let's say using 80 percent of your addresses say 80 percent of the IP addresses and that

55
00:05:07,740 --> 00:05:15,690
subnet have been allocated to physical devices like PCs and now you Ed Cisco IP phones to the mix youre

56
00:05:15,780 --> 00:05:21,780
centrally doubling the amount of devices that you only have 20 percent of the IP addresses remaining

57
00:05:21,780 --> 00:05:22,950
in that subnet.

58
00:05:23,010 --> 00:05:29,080
So you cannot put the phones and the PC in the same subnet without redoing your IP addressing.

59
00:05:29,100 --> 00:05:35,340
However if you put your phones into a separate subnet that doesn't affect the IP addressing of the PCs

60
00:05:35,910 --> 00:05:43,560
so you allocate a separate subnet for IP phones and the IP subnet allocated to the PCs is left alone.

61
00:05:44,890 --> 00:05:50,740
Theres also a logical separation of voice and data traffic because the phones on a separate subnet to

62
00:05:50,740 --> 00:05:57,790
the PCs it's easier to implement quality of service it's easier to implement your access lists and it's

63
00:05:57,820 --> 00:05:59,760
easier to implement security.

64
00:05:59,950 --> 00:06:06,670
So that's a major advantage to separating the phones in the PCs into separate subnets two devices can

65
00:06:06,670 --> 00:06:11,440
also be connected to a single port on the switch which minimizes cabling.

66
00:06:11,580 --> 00:06:17,610
Your PC is physically connected to the phone which is physically connected to the switch across a single

67
00:06:17,610 --> 00:06:18,730
cable.

68
00:06:18,750 --> 00:06:26,970
However logically the phone and the PC on separate cables because they are indifferent to the lens but

69
00:06:26,970 --> 00:06:31,960
physically you saving on cabling the multiple Bil'in access port.

70
00:06:32,040 --> 00:06:37,680
Implementation tends to be the most common in the real world and is the recommended way to implement

71
00:06:37,800 --> 00:06:43,020
IP phones to configure a multiple violent access port on an interface.

72
00:06:43,080 --> 00:06:51,410
Do the following so on you see 500 or an off switch are going to top the C'mon show Villon switch to

73
00:06:51,410 --> 00:06:56,760
see the villans configured at the moment we have Bil'in one configured on ports.

74
00:06:56,780 --> 00:07:06,820
If 0 1 0 2 0 1 slash 8 no interfaces on the voice Villon I can also do the come on show run interface

75
00:07:06,900 --> 00:07:12,810
if 0 1 slash 1 to show you the configuration on this interface.

76
00:07:13,150 --> 00:07:19,250
And you can see just defaulted the configuration all ports are in excess VLAN 1.

77
00:07:19,690 --> 00:07:27,570
So going into a global config mode and tapping on interface range if 0 1 0 1 2 3 in other words we're

78
00:07:27,580 --> 00:07:32,170
going to configure the three ports that have IP phones connected to them.

79
00:07:32,460 --> 00:07:40,640
I cannot type the command switchboard mode access making these ports access ports which is the default.

80
00:07:41,130 --> 00:07:51,320
And I can tap the command switchboard voice with the land and switchboard access villaine one now typing

81
00:07:51,320 --> 00:07:57,860
the command show run interface if 0 1 slash 1 shows me that that interface has been configured with

82
00:07:57,860 --> 00:07:59,150
a voice VLAN.

83
00:07:59,150 --> 00:08:06,890
We don't see the native land or the data plan or the access to the LAN because Villon one is the default

84
00:08:07,010 --> 00:08:12,130
reelin and default configurations don't show up in the running config.

85
00:08:12,650 --> 00:08:21,970
But topping the command show interface of zero once one switch port allows me to see the voice and data

86
00:08:21,970 --> 00:08:23,950
we learn more clearly.

87
00:08:23,950 --> 00:08:31,960
So on the interface it's been configured as a static access port and is acting as a static access port.

88
00:08:32,440 --> 00:08:40,070
The access to the plan is villaine one the default and notice the voice feelin is villaine too.

89
00:08:40,480 --> 00:08:45,980
So even though the operational mode is static access in other words this is acting as an access port.

90
00:08:46,120 --> 00:08:51,570
We are allowing billons one in two across this port.

91
00:08:51,670 --> 00:08:55,770
The fourth way to implement IP phones is to use a 2.1.

92
00:08:55,800 --> 00:09:04,360
He now $82 1 p frame's use the three boats in the edited or 1 Q header to allow for the prioritization

93
00:09:04,510 --> 00:09:07,200
of voice traffic over data traffic.

94
00:09:07,210 --> 00:09:12,300
There are three beds in an editor or one to header called the costs or loss of service.

95
00:09:12,380 --> 00:09:15,160
Let's talk more about these later.

96
00:09:15,460 --> 00:09:22,630
Essentially editor 1 p allows for the mocking of voice traffic with a value of five in the course feel

97
00:09:23,170 --> 00:09:30,240
allowing the switch to see voice traffic has higher priority than data traffic and with a single villain

98
00:09:30,260 --> 00:09:32,290
access port using editor 1.

99
00:09:32,300 --> 00:09:36,490
P The interface is in a single the LAN.

100
00:09:36,640 --> 00:09:46,000
So both the phone and the PC are in the land too but the phone is going to send tagged frames to the

101
00:09:46,000 --> 00:09:47,260
switch.

102
00:09:47,290 --> 00:09:54,010
Now because this is a standard access port the phone uses a special the land number in the edit to the

103
00:09:54,010 --> 00:10:00,130
one Q header to allow for the use of a read through one keyframes.

104
00:10:00,150 --> 00:10:07,950
Now just to recap from the CCMA was a standard Ethan at frame as a source and destination field a length

105
00:10:07,950 --> 00:10:14,210
for each time the data and then a frame check sequence when edited or one cue is used.

106
00:10:14,220 --> 00:10:20,870
A tag is inserted between the source and destination address and the length and either taught field.

107
00:10:21,300 --> 00:10:30,240
That tag consists of four bytes 16 bits is the tag protocol identifier and then the remaining 16 bits

108
00:10:30,540 --> 00:10:34,950
consist of the priority code point or priority field.

109
00:10:35,310 --> 00:10:44,940
The canonical format indicator and the villain ID now editor 1 p specifies the meaning of the priority

110
00:10:44,940 --> 00:10:53,470
field or class of service or Crossfield the property code point field is three bits in length.

111
00:10:53,490 --> 00:11:02,260
In other words the binary values are from triple 0 to triple 1 and decimal values is 0 2 7.

112
00:11:02,280 --> 00:11:08,430
The high priority value the more important the traffic and thus voice will have a binary value of 1

113
00:11:08,440 --> 00:11:12,920
0 1 or the equivalent decimal value of 5.

114
00:11:12,960 --> 00:11:22,590
So the phone is sending a 2 to 1 keyframes to the switch on an access port with the cost field or priority

115
00:11:22,590 --> 00:11:25,750
code point field set to 5.

116
00:11:25,800 --> 00:11:30,710
In other words it's sending an edit to the one frame to the switch.

117
00:11:30,710 --> 00:11:39,060
Now just to reiterate terminology an editor or one cue header is inserted in the Ethan frame which looks

118
00:11:39,060 --> 00:11:40,220
as follows.

119
00:11:40,260 --> 00:11:50,210
Edit 2 to 1 p denotes the meaning or values of the already feel or cause feel the value specified here.

120
00:11:50,460 --> 00:11:54,440
Form part of the recommendations of Ada to the one P..

121
00:11:54,450 --> 00:12:02,580
So once again Ed. 1 p specifies the different classes or values of the priority field in an attitude

122
00:12:02,580 --> 00:12:03,860
or one queue header.

123
00:12:05,090 --> 00:12:11,370
The phone is setting the value of the cost field to 5 when sending frame's to the switch.

124
00:12:11,390 --> 00:12:17,260
The switch therefore knows that traffic from the phone has a higher priority than traffic from the PC.

125
00:12:17,270 --> 00:12:21,340
Now that explains how one can be used for quality of service.

126
00:12:21,560 --> 00:12:24,410
But in this example this is an access port.

127
00:12:24,410 --> 00:12:26,020
In other words it's not a trunk port.

128
00:12:26,030 --> 00:12:27,440
It's an access port.

129
00:12:27,650 --> 00:12:31,460
Only one villain has been configured on this port Vila and 2.

130
00:12:31,910 --> 00:12:38,480
So when sending traffic to the switch a villain number has to be specified by the phone and a villain

131
00:12:38,480 --> 00:12:46,760
number used in this case is a villain Zerah the switch therefore knows that when it receives an editor

132
00:12:46,760 --> 00:12:54,860
the one Q frame with the villain number set to 0 that the phone still belongs to the villain configured

133
00:12:54,860 --> 00:12:57,610
on this port as the access villain.

134
00:12:57,980 --> 00:13:06,180
So all traffic from the phone and the PC reside in the Leonti the phone is not in a separate Bil'in

135
00:13:06,180 --> 00:13:09,760
to the PC they both belong to be Leonti.

136
00:13:10,070 --> 00:13:18,840
Thus the use of the special Bil'in of zero when sending editor or one keyframes to the switch on this

137
00:13:18,950 --> 00:13:20,650
access port.

138
00:13:20,840 --> 00:13:27,740
So to configure EDOT 2 to 1 p on an access port you need to do the following.

139
00:13:27,760 --> 00:13:33,430
So before configuring the switch or the U.S. 500 Let's have a look at our villans.

140
00:13:33,590 --> 00:13:41,650
So as you can see here all interfaces on the default Bil'in of the line one once again show run interface

141
00:13:41,670 --> 00:13:51,010
if zero once one shows us that the interface has a default configuration on it going into global config

142
00:13:51,010 --> 00:13:52,930
mode tapping typing interface the range.

143
00:13:52,930 --> 00:14:01,650
If 0 1 stash 1 2 3 the interfaces that have iPhones connected to them I can type the command switch

144
00:14:01,650 --> 00:14:05,270
Ford mode access.

145
00:14:05,580 --> 00:14:12,080
So these ports are not going to be configured as trunk's they configure it as access ports switch port

146
00:14:13,520 --> 00:14:17,670
voice the LAN dot one.

147
00:14:18,330 --> 00:14:22,360
You specify the use of dot one on these ports.

148
00:14:22,560 --> 00:14:31,940
Switch port access in the land to noticed we are not specifying a voice Vilanova up.

149
00:14:31,970 --> 00:14:35,350
We are specifying an Access Villano of T.

150
00:14:35,780 --> 00:14:43,770
So once again show run interface if 0 1 slash 1 shows me that this port is in the land too.

151
00:14:44,240 --> 00:14:50,830
It's an access port but we are using edited a one p on this interface.

152
00:14:50,900 --> 00:14:59,740
The phones will transmit traffic to the switch as tag frames using Wheatland zero in the real identifier.

153
00:15:00,520 --> 00:15:10,930
Both the phone and the PC are in the land to that concludes part 1 of our discussion of the Cisco phone

154
00:15:10,930 --> 00:15:12,490
startup process.

155
00:15:12,490 --> 00:15:20,260
We discussed how an IP phone obtains power Aviles information is provided to the phone using CTP or

156
00:15:20,270 --> 00:15:27,430
L-L DP in the next part we are going to continue the discussion by looking at how an IP phone acquires

157
00:15:27,430 --> 00:15:35,560
an IP address downloads its firmware and configuration and registers with a C UCM will also discuss

158
00:15:35,560 --> 00:15:40,290
the signalling protocols of skinny and thank you for watching.
