1 00:00:00,820 --> 00:00:09,170 So this awful typology of a U.S. 420 and I'm going to connect three IP phones to the U.S. 500 now I'd 2 00:00:09,170 --> 00:00:14,270 like to demonstrate the power that the phones receive the three phones that we have in this typology 3 00:00:14,270 --> 00:00:20,910 are 79 71 79 60 and a 79 65. 4 00:00:21,000 --> 00:00:25,190 And what I'd like to demonstrate is the amount of power that these phones use. 5 00:00:25,190 --> 00:00:34,470 And let's see if they use POPC or ADA 2.3 A-F as an example 79 60 phone has been around for many years. 6 00:00:34,670 --> 00:00:40,950 And this particular phone only supports P.O.D. that does not support Ada 2.3. 7 00:00:41,210 --> 00:00:43,880 So once again you have to be very careful with your power. 8 00:00:44,120 --> 00:00:50,390 You've got to make sure that the switch or device providing power supports the power that the phone 9 00:00:50,480 --> 00:00:51,380 requires. 10 00:00:51,380 --> 00:00:58,310 In other words edited or 3am or for instance a or 380 or Cisco's power of Ethernet. 11 00:00:58,750 --> 00:01:01,610 So lets connect to the device and see what happens. 12 00:01:03,920 --> 00:01:14,040 So I'm going to tell it to these 500 and log in the C'mon show power in line will show me the power 13 00:01:14,040 --> 00:01:16,460 usage at the moment. 14 00:01:16,530 --> 00:01:27,720 You'll notice that none of these ports if 0 1 0 2 0 1 7 are powered noticed power allocated is zero 15 00:01:27,720 --> 00:01:35,640 what's on all of these ports the max amount of power that this switch or in this case use the 500 supports 16 00:01:35,670 --> 00:01:43,430 is 88 what's also note that the ports have been configured for Orta allocation of power. 17 00:01:43,590 --> 00:01:47,810 Once again you would never set a port on full power. 18 00:01:47,880 --> 00:01:51,010 It's either auto or it's off. 19 00:01:51,060 --> 00:01:56,620 So just to show you that on a port I'm going to go to one of the interfaces and topic them on power 20 00:01:57,150 --> 00:02:03,190 in line and notice the only options auto or never. 21 00:02:03,260 --> 00:02:10,510 So we'll just leave those ports at quarter power allocation at the moment no phones are connected. 22 00:02:10,640 --> 00:02:14,310 I'm going to enable Terman so that we can monitor what's happening. 23 00:02:14,390 --> 00:02:19,240 Even though we telnetting and I'm going to plug in the phones so let's see what happens. 24 00:02:32,450 --> 00:02:36,860 As you can see the interfaces are coming up. 25 00:02:36,860 --> 00:02:40,430 So if I do the same command again show power line. 26 00:02:40,460 --> 00:02:49,820 Now it is at the moment two ports are showing the allocation of I triple E plus three power and the 27 00:02:49,820 --> 00:02:59,090 power allocated is 12 watts for the one phone and fourteen point nine watts for the other phone. 28 00:02:59,180 --> 00:03:00,500 I'll do the KM on the game. 29 00:03:01,550 --> 00:03:10,510 And notice 6.3 Watts has been allocated to the phone on a one slash two and it's using Cisco's power 30 00:03:10,510 --> 00:03:11,510 over Ethernet. 31 00:03:12,830 --> 00:03:18,270 Doing that come on show SCDP neighbor will allow me to see my neighbors. 32 00:03:18,310 --> 00:03:28,950 You can see that we've got IP phones on port 1 2 and 3 let's look at the details so as part diagram 33 00:03:29,160 --> 00:03:33,710 if one slushed to as the 79 60 connected to it. 34 00:03:33,750 --> 00:03:40,920 So once they get to the 79 60 connected to it on forced Ethan it's 0 1 3. 35 00:03:41,060 --> 00:03:47,980 The 79 71 is connected on if the 0 1 1 the 79 65 is connected 36 00:03:50,650 --> 00:04:01,330 show Paula inline rather shows me that the 79 65 is drawing 12 watts of power. 37 00:04:02,120 --> 00:04:09,180 The 79 60 is drawing 6.3 watts of power and the 79 71 is drawing fourteen point nine watts of power 38 00:04:09,930 --> 00:04:12,860 initially in a class 3 device starts up. 39 00:04:12,870 --> 00:04:18,360 So a device that requires added or three if it will use 15 watts of power. 40 00:04:18,740 --> 00:04:25,770 But through CTP the phones negotiate the amount of power that they require and that's what you use less 41 00:04:25,770 --> 00:04:27,820 power or more power. 42 00:04:28,230 --> 00:04:31,910 So to demonstrate that I'm going to shut the interfaces down and then no shut them 43 00:04:42,220 --> 00:04:50,500 so you can see the interfaces went down not tapping to come on to show power in line shows me that there's 44 00:04:50,500 --> 00:04:56,760 no power allocated on no shut those ports do they come on again. 45 00:04:57,080 --> 00:05:02,830 And as you can see they fifteen point four watts of power was allocated to those two ports. 46 00:05:02,920 --> 00:05:09,060 Notice fifteen point four watts of power is allocated to all three ports and now they negotiate the 47 00:05:09,060 --> 00:05:10,790 amount of power that they require. 48 00:05:10,940 --> 00:05:19,840 So the 79 65 has gone down to 12 Fort's the 79 60 down to 6.3. 49 00:05:19,980 --> 00:05:25,540 And let's see that 79 71 will eventually go down in its power requirements. 50 00:05:31,030 --> 00:05:32,760 Now it's taking a while. 51 00:05:32,920 --> 00:05:40,690 So I'll just pause this and wait. 52 00:05:40,700 --> 00:05:42,740 So after a while you'll notice the following. 53 00:05:42,740 --> 00:05:49,020 It was originally fifteen point four watts and then went down to fourteen point nine watts of power. 54 00:05:49,160 --> 00:05:56,480 You can see the maximum available is 88 that city 3.2 have are been used whereas previously just thirty 55 00:05:56,550 --> 00:06:01,130 three point seven before the iPhone successfully negotiated. 56 00:06:01,130 --> 00:06:05,870 Buy a CD with a switch that it required less power. 57 00:06:07,590 --> 00:06:16,100 Once a phone has power the next thing it needs to work out is which of the lan it's configured on. 58 00:06:16,190 --> 00:06:23,480 You can manually configure be lands on Cisco IP phones but in most implementations in the real world 59 00:06:23,680 --> 00:06:28,970 the deal any information would be configured on the switch and the phone would query the switch either 60 00:06:28,970 --> 00:06:38,900 using Cisco discovery protocol or CTP or link delay discovery protocol or else LDP LDP is an industry 61 00:06:38,900 --> 00:06:44,040 standard protocol equivalent to CTP for Cisco IP phones. 62 00:06:44,120 --> 00:06:53,420 The actual LDP version used is L-L DP med the med standing for media in point discovery which is an 63 00:06:53,420 --> 00:07:01,850 enhancement to the standard LDP so the phone will query the switch and find out which villain it belongs 64 00:07:01,850 --> 00:07:02,840 to. 65 00:07:02,840 --> 00:07:09,160 There are multiple ways for connecting a phone and PC to a Cisco switch or other vendor switch. 66 00:07:09,170 --> 00:07:13,760 Once again just note CTP would be used between Cisco phones and Cisco switches. 67 00:07:13,850 --> 00:07:18,470 LDP would be useful since between a Cisco phone and an HP switch. 68 00:07:18,860 --> 00:07:25,190 Newer phones would use LDP between the Cisco phone and the Cisco switch. 69 00:07:25,270 --> 00:07:29,200 I sampled Knology before allocating villans to interface's. 70 00:07:29,290 --> 00:07:35,970 We need to decide which villans to create and what subnets to allocate to those villains. 71 00:07:36,100 --> 00:07:39,880 So we're going to have a data villain and a voice LAN. 72 00:07:39,990 --> 00:07:45,840 Now to give this example very simple we are going to configure Bil'in one as the data villaine with 73 00:07:45,840 --> 00:07:56,090 a subnet of 10 1 1 0 slice 24 and the voice LAN with relend to a subnet of 10 1 2 0 slash 24. 74 00:07:56,400 --> 00:08:02,120 Now in the first example we are going to have the PC and the phone in the same villaine. 75 00:08:02,400 --> 00:08:03,780 That's not recommended. 76 00:08:03,780 --> 00:08:10,460 Cisco would recommend that you put your PCs and phones in separate the lens and thus in separate subnets 77 00:08:12,540 --> 00:08:14,940 so I'm going to telnet to the U.S. 500 78 00:08:19,890 --> 00:08:28,160 into a global configuration mode and create a villain to the last one if you remember exists by default. 79 00:08:28,160 --> 00:08:31,920 I'm going to give it a name or description of voice the land. 80 00:08:32,540 --> 00:08:36,220 I can go back to privilege mode and then top the C'mon show then. 81 00:08:36,500 --> 00:08:37,730 Now new U.S. 500. 82 00:08:37,730 --> 00:08:40,290 It's acting as a robber and as a switch. 83 00:08:40,550 --> 00:08:46,120 So to see the villains on the switch ports you need to top tap the C'mon Chhobi let's switch now as 84 00:08:46,130 --> 00:08:47,740 you can see here. 85 00:08:47,970 --> 00:08:57,630 Interface's if 0 1 0 up to the 0 1 8 on the line 1 default the line no interfaces are in the voice villaine 86 00:08:59,170 --> 00:09:05,140 now the first way to implement the plans is to have a single land access port. 87 00:09:05,150 --> 00:09:11,480 This is essentially where you've got a PC and a phone connected to a port on the switch and they both 88 00:09:11,480 --> 00:09:17,100 within the same deal and so this port is configured as a standard access port. 89 00:09:17,210 --> 00:09:23,660 There is no trunking and no tagging untagged frames are sent to the phone and violently and untacked 90 00:09:23,660 --> 00:09:26,930 frames are sent to the PC on the Leonti. 91 00:09:26,930 --> 00:09:33,860 There is no special tagging or differentiation between frames belonging to the PC and frames belonging 92 00:09:33,860 --> 00:09:37,500 to the phone they both belong to the same Bil'in. 93 00:09:37,640 --> 00:09:42,620 There are some disadvantages to implementing phones in PCs in this way. 94 00:09:42,620 --> 00:09:44,830 The first issue is security. 95 00:09:44,930 --> 00:09:51,580 The pc will be able to sniff traffic from the phone and be able to record the voice conversation. 96 00:09:51,650 --> 00:09:58,760 If an application like Cain and Abel is used on newer phones that functionality can be disabled by the 97 00:09:58,760 --> 00:10:05,750 sea UCM for example Callia service is also harder to implement because you cannot differentiate between 98 00:10:05,750 --> 00:10:09,100 the traffic types based on Bil'in. 99 00:10:09,210 --> 00:10:13,840 There are two scenarios where you may have to set up a single violent access port. 100 00:10:13,950 --> 00:10:19,920 The first one is when you've got a soft phone or in this example the Cisco IP communicator running on 101 00:10:19,920 --> 00:10:20,930 your laptop. 102 00:10:21,240 --> 00:10:28,770 In this example both the softphone and the PC are in the same plan because the Sophonias running on 103 00:10:28,770 --> 00:10:29,930 the PC. 104 00:10:30,150 --> 00:10:37,650 So traffic going to the PC and traffic going to the cellphone are sent across the same port untagged 105 00:10:38,090 --> 00:10:40,660 in the same villain. 106 00:10:40,770 --> 00:10:48,540 The second example of using a single villaine access board is when you've got a non Cisco IP phone solution. 107 00:10:48,870 --> 00:10:53,620 In this example you may need to configure the phone and the PC in the same Bil'in. 108 00:10:54,030 --> 00:11:00,630 However that is less common these days as most phone vendors support the concept of a voice of the land. 109 00:11:00,910 --> 00:11:07,080 But if you come across an older solution or a smaller vendor you may need to implement your villans 110 00:11:07,080 --> 00:11:08,060 in this fashion. 111 00:11:08,920 --> 00:11:17,760 You set up a single Bil'in access board on this page you're simply going to need to face 112 00:11:20,770 --> 00:11:33,900 Antarctica on switchboard mode access switchboard access the LAN to whichever LAN you were going to 113 00:11:33,900 --> 00:11:45,760 use to view the configuration I can top that can on do a show run interface if 0 1 slash 1. 114 00:11:45,880 --> 00:11:51,750 And as you can see they this is just a standard code configured with a standard villain. 115 00:11:52,130 --> 00:11:57,940 It's configured in the same way you would configure it if there was just a PC connected to the port. 116 00:11:57,950 --> 00:12:03,320 Once again this is not recommended that you may need to do this if you've got non Cisco phones connected 117 00:12:03,320 --> 00:12:05,660 to your switch. 118 00:12:05,690 --> 00:12:15,340 I could also do the command show interface if 0 1 slash 1 switchboard. 119 00:12:15,550 --> 00:12:20,640 And notice here you can see that it's being configured for static access. 120 00:12:20,860 --> 00:12:28,240 The operational mode is static access the access villanies violent too and no voice feel and has been 121 00:12:28,240 --> 00:12:29,370 configured. 122 00:12:29,650 --> 00:12:32,750 So this is just a standard access port. 123 00:12:34,160 --> 00:12:41,060 In the old days you used to connect Cisco IP phones to the network infrastructure using trunk ports 124 00:12:41,750 --> 00:12:48,680 a trunk port if you remember can support multiple villans with some traffic sent tagged and some traffic 125 00:12:48,680 --> 00:12:51,330 sent untagged across the native land. 126 00:12:51,650 --> 00:12:57,410 So in this example you put the phone in the voice the land and send traffic to it as tagged as a two 127 00:12:57,410 --> 00:13:05,480 to one keyframes the native land would be used to send traffic to the PC untagged so tagged frames are 128 00:13:05,480 --> 00:13:09,950 sent into the phone and untag frames are sent to the PC. 129 00:13:09,980 --> 00:13:15,000 Once again the phone would learn the villain information directly from the switch. 130 00:13:15,050 --> 00:13:21,020 You wouldn't have to configure the phone with the voice Villon they are once again a number of issues 131 00:13:21,170 --> 00:13:24,710 with configuring your network in this way. 132 00:13:24,710 --> 00:13:28,880 The first issue is that this port cannot be configured as a secure port. 133 00:13:28,910 --> 00:13:33,290 Port security can only be enabled and access ports not trunk ports. 134 00:13:34,120 --> 00:13:41,110 Another issue that used to affect Cisco solutions is that in the old days 79 05 phones which were the 135 00:13:41,110 --> 00:13:47,910 low range basic phones often used to reset because of the number of broadcasts received. 136 00:13:47,920 --> 00:13:53,120 The problem with a trunk link is that a trunk by default allows all the lands across it. 137 00:13:53,530 --> 00:13:58,770 So the phone in the scenario would receive broadcasts going to all the lands. 138 00:13:59,020 --> 00:14:04,750 So if a PC on the right hand side here for example was jabbering and was sending many broadcasts those 139 00:14:04,750 --> 00:14:09,670 broadcasts would be received by the phone and have to be processed by the phone. 140 00:14:09,670 --> 00:14:17,950 So in the past phones like the 79 05 which were a basic low entry IP phones reset because they didn't 141 00:14:17,950 --> 00:14:22,390 have the processing power to process all the broadcasts received. 142 00:14:22,660 --> 00:14:26,760 So this caused a lot of issues because your phones would just randomly reset. 143 00:14:26,770 --> 00:14:31,540 So what you had to do in the old days is you had to configure this as a trunk and then manually prune 144 00:14:31,540 --> 00:14:36,230 the trunk to only allow traffic to the voice of the land and the of the land. 145 00:14:36,400 --> 00:14:42,760 Another issue was that on certain switches hoarfrost couldn't be enabled on Concorde's and to make matters 146 00:14:42,760 --> 00:14:49,640 worse a lot of the IP phones would actually copy the tagged frames that they received out of the PC 147 00:14:49,690 --> 00:14:56,660 port and the PC if running a hacking tool and supporting editor one key could receive all of that traffic. 148 00:14:56,860 --> 00:15:03,470 So the PC would have visibility of other villains not just the villain on which it resides. 149 00:15:03,490 --> 00:15:09,550 So this isn't a recommended implementation today but if you come across a really old switch that doesn't 150 00:15:09,550 --> 00:15:13,860 support multivalent exports which we'll discuss in a moment. 151 00:15:13,990 --> 00:15:16,650 You could configure that port as a transport.