1 00:00:14,870 --> 00:00:16,890 He has the switch 2 00:00:19,770 --> 00:00:30,750 sprouted up before I configure the switch on no shot interface f0/0 so that that interface comes up, 3 00:00:31,110 --> 00:00:33,510 you can see it's come up on the switch. 4 00:00:34,380 --> 00:00:38,670 Now you may want to do your configuration in a specific order. 5 00:00:38,760 --> 00:00:45,720 It doesn't really matter if things don't work, shut down ports and re-enable them, for instance, 6 00:00:45,720 --> 00:00:50,130 on the connections to the IP phones to ensure things work properly. 7 00:00:50,960 --> 00:00:53,120 Once you finished your configuration. 8 00:00:53,570 --> 00:00:58,880 Now interface gigabit 101 needs to be configured as a trunk port. 9 00:00:59,120 --> 00:01:01,790 So switch port trunk. 10 00:01:01,790 --> 00:01:06,410 Encapsulation dot one Q switch port mode. 11 00:01:06,620 --> 00:01:07,490 Trunk. 12 00:01:08,180 --> 00:01:09,590 That looks good. 13 00:01:10,160 --> 00:01:17,720 I need to configure my vlans so vlan 100 can give it a name such as data. 14 00:01:19,250 --> 00:01:26,570 You may want to be consistent with the names that you're using on your DHCP pools, but that doesn't 15 00:01:26,570 --> 00:01:27,140 really matter. 16 00:01:27,140 --> 00:01:30,350 So show VLAN brief here we've got. 17 00:01:31,320 --> 00:01:41,160 Data VLAN and voice VLAN configured, but currently all ports on the switch are in VLAN one. 18 00:01:43,200 --> 00:01:53,340 Before I configure the porch to the PCs and phones, I'll configure the switch with its management IP 19 00:01:53,340 --> 00:01:53,970 address. 20 00:01:55,400 --> 00:01:55,980 Management. 21 00:01:56,000 --> 00:01:59,060 IP address needs to be ten 11253. 22 00:01:59,270 --> 00:02:01,460 Default gateway needs to be the router. 23 00:02:04,920 --> 00:02:17,550 No shut to that IP default gateway ten 11254 router needs to be configured so that my switch can get 24 00:02:17,550 --> 00:02:19,050 to remote subnets. 25 00:02:19,530 --> 00:02:21,600 Let's see if the switch camping the router. 26 00:02:22,930 --> 00:02:23,680 Yes, it can. 27 00:02:23,680 --> 00:02:24,850 So that's good. 28 00:02:25,240 --> 00:02:33,550 Now, Cisco, IP phones use CDP or LDAP for communication with the switch. 29 00:02:33,790 --> 00:02:37,990 The phones need to learn which VLAN they belong to. 30 00:02:38,700 --> 00:02:48,060 So in other words, they need the switch to run CDP so that they can query the switch about which VLAN 31 00:02:48,060 --> 00:02:49,260 they belong to. 32 00:02:49,950 --> 00:02:52,980 So we need to enable CDP on the switch. 33 00:02:55,010 --> 00:03:00,800 So that the switch can tell the phones which VLANs they belong to. 34 00:03:01,890 --> 00:03:04,770 After the moment, we don't see any CDP neighbors. 35 00:03:05,010 --> 00:03:06,450 That may take a while. 36 00:03:06,570 --> 00:03:12,150 So while we're waiting for that, let's configure the ports on the switch. 37 00:03:12,330 --> 00:03:18,480 So interface range one zero 2 to 4. 38 00:03:18,930 --> 00:03:24,570 I'm going to configure this port, this port and this port at the same time. 39 00:03:26,330 --> 00:03:28,160 Switchboard mode is access. 40 00:03:28,190 --> 00:03:44,870 These are access ports, but we're going to configure both a data VLAN and a voice VLAN on those ports. 41 00:03:45,810 --> 00:03:48,000 So show run on the switch. 42 00:03:49,430 --> 00:03:55,400 We've got a trunk on this port to the router and then we've enabled. 43 00:03:56,700 --> 00:04:01,650 The voice VLAN and the data VLAN on those ports. 44 00:04:02,010 --> 00:04:06,090 Now, this is a bit of an interesting command on a Cisco switch. 45 00:04:06,630 --> 00:04:08,340 It says it's an access port. 46 00:04:08,340 --> 00:04:15,750 But if we look at that port by using the command show interface, interface number, switch port. 47 00:04:18,720 --> 00:04:26,730 What you'll notice is this port is configured and is operational as a static access port, but it's 48 00:04:26,730 --> 00:04:32,520 allowing both a untagged and tagged a VLAN across it. 49 00:04:32,700 --> 00:04:34,590 So it's a special type. 50 00:04:35,560 --> 00:04:41,680 Of Access port that also accepts tagged frames from phones. 51 00:04:42,630 --> 00:04:45,180 So two VLANs are allowed across that port. 52 00:04:45,300 --> 00:04:48,900 This is not like a standard access port. 53 00:04:49,050 --> 00:04:50,340 Just a bit of history. 54 00:04:50,760 --> 00:04:56,850 In the very, very old days, you used to configure ports to phones as trunk ports. 55 00:04:58,210 --> 00:05:00,700 But it caused issues with broadcasts. 56 00:05:01,000 --> 00:05:05,770 So Cisco changed the way that the trunk ports were configured. 57 00:05:06,160 --> 00:05:12,460 And we have the special type of access port that's kind of an access port, but it's also kind of a 58 00:05:12,460 --> 00:05:13,360 trunk port. 59 00:05:13,660 --> 00:05:20,260 It's essentially a trunk port that's pruned to only allow those two VLANs. 60 00:05:20,380 --> 00:05:23,390 VLAN 100 and VLAN 101. 61 00:05:23,410 --> 00:05:28,810 So it's kind of like an access or a pruning trunk port, if that makes any sense. 62 00:05:30,180 --> 00:05:31,560 Show CDP neighbor. 63 00:05:31,890 --> 00:05:35,970 We can see IP phones connected. 64 00:05:36,620 --> 00:05:37,880 To the ports. 65 00:05:39,020 --> 00:05:40,810 On the switch show. 66 00:05:41,840 --> 00:05:44,930 Power in line. 67 00:05:45,590 --> 00:05:46,130 Just do that. 68 00:05:46,130 --> 00:05:46,850 Come on again. 69 00:05:46,850 --> 00:05:48,290 Show power in line. 70 00:05:48,680 --> 00:05:49,910 Scrolling up. 71 00:05:50,910 --> 00:05:52,200 There's a command. 72 00:05:52,680 --> 00:05:58,050 These three phones are drawing ten watts of power. 73 00:05:58,410 --> 00:06:04,230 So one of the questions we need to answer is verify phone power usage. 74 00:06:04,800 --> 00:06:10,530 We can see that the phones are each drawing ten watts of power. 75 00:06:11,040 --> 00:06:13,290 That's the power used on the switch. 76 00:06:13,680 --> 00:06:15,210 But more is available. 77 00:06:17,550 --> 00:06:17,850 Okay. 78 00:06:17,850 --> 00:06:21,690 So we've configured the switch and the rudder. 79 00:06:22,560 --> 00:06:24,450 With basic configuration. 80 00:06:24,960 --> 00:06:29,400 Let's see if IP addresses are being released to clients. 81 00:06:29,730 --> 00:06:33,930 At the moment we're not seeing any DHCP bindings. 82 00:06:35,010 --> 00:06:37,680 Let's confirm that we've done things right. 83 00:06:38,070 --> 00:06:43,200 I made a mistake in this command, so let's remove that command. 84 00:06:46,550 --> 00:06:47,900 That should be. 85 00:06:48,230 --> 00:06:56,240 IP DHCP excluded range 101 200 to 101 254. 86 00:06:56,300 --> 00:06:58,490 So let's have a look at that again. 87 00:06:58,580 --> 00:06:59,750 That looks better. 88 00:06:59,900 --> 00:07:02,030 Show IP DHCP binding. 89 00:07:02,660 --> 00:07:09,380 Still don't have any bindings or let's verify the other configuration on the router. 90 00:07:10,100 --> 00:07:11,690 So that looks good. 91 00:07:12,110 --> 00:07:13,460 That looks good. 92 00:07:16,190 --> 00:07:17,720 Show CDP neighbor. 93 00:07:18,990 --> 00:07:20,970 Well, enable CDP on the rota. 94 00:07:22,890 --> 00:07:25,380 Hopefully we should learn about the switch. 95 00:07:27,670 --> 00:07:31,360 Still not receiving any DHCP requests. 96 00:07:31,630 --> 00:07:38,290 So lets go back onto the switch and what I'll do is shut the ports down and bring them up again to make 97 00:07:38,290 --> 00:07:42,700 sure that the phones request IP addresses. 98 00:07:42,970 --> 00:07:47,140 So interface range gigabit 10224. 99 00:07:47,170 --> 00:07:51,040 Shut those ports down and no shut to them. 100 00:07:53,380 --> 00:08:00,790 And while we're waiting for spending tree to converge, let's look at the pieces they need to be configured 101 00:08:00,790 --> 00:08:02,800 for DHCP. 102 00:08:05,020 --> 00:08:11,830 So hopefully they'll get IP addresses once spending tree has converged. 103 00:08:13,480 --> 00:08:17,080 Set the pieces to use dhcp. 104 00:08:17,770 --> 00:08:19,090 Do that here. 105 00:08:22,320 --> 00:08:26,840 So on PC three, IP config, IP config. 106 00:08:26,840 --> 00:08:28,860 And notice it got an IP address. 107 00:08:29,430 --> 00:08:33,299 So it should hopefully be able to ping the router, which it can. 108 00:08:34,630 --> 00:08:38,470 Under this PC, it still doesn't have an IP address. 109 00:08:38,470 --> 00:08:46,390 So let's do a renew to force it to request an IP address from the DHCP server. 110 00:08:48,000 --> 00:08:51,660 It's now been given one and it can ping the rotter. 111 00:08:52,350 --> 00:08:55,710 What about this PC IP config? 112 00:08:56,310 --> 00:09:00,810 No IP address for it to get an IP address using a renew. 113 00:09:01,410 --> 00:09:06,240 It's got an IP address and can ping the router. 114 00:09:07,450 --> 00:09:08,710 Back on the router. 115 00:09:08,740 --> 00:09:10,930 Show IP DHCP bindings. 116 00:09:11,970 --> 00:09:16,110 We can see that the PCs have requested IP addresses. 117 00:09:16,650 --> 00:09:18,990 The phones haven't to this point. 118 00:09:19,380 --> 00:09:22,170 So let's configure the telephony service while we wait. 119 00:09:24,330 --> 00:09:27,510 And see if the phones request IP addresses. 120 00:09:28,780 --> 00:09:34,510 Sometimes packet tracer doesn't work precisely like a real device.