1 00:00:15,840 --> 00:00:23,900 This is a packet tracer campus network topology that we're gonna use in multiple videos in this course. 2 00:00:23,970 --> 00:00:32,770 This topology gives us a nice basis to learn many of the technologies found in the CCNA exam. 3 00:00:32,790 --> 00:00:39,610 This is a campus network consisting of two core switches and three access switches. 4 00:00:39,870 --> 00:00:42,820 Even though this topology is quite small. 5 00:00:42,870 --> 00:00:50,160 Imagine that you have many access switches in this topology configuring more than three access switches 6 00:00:50,160 --> 00:00:57,960 is redundant and will simply take up time rather than you learning new things so I've limited the topology 7 00:00:57,960 --> 00:01:00,570 to three access switches. 8 00:01:00,690 --> 00:01:09,330 We've also got three PCs in the topology one connected to each access switch as well as a server connected 9 00:01:09,390 --> 00:01:11,550 to one of the core switches. 10 00:01:11,820 --> 00:01:19,830 We have an Internet router that will configure to connect the campus network to the Internet. On the 11 00:01:19,830 --> 00:01:20,310 internet 12 00:01:20,310 --> 00:01:23,870 we have a Google DNS server 13 00:01:24,230 --> 00:01:30,880 8.8.8.8 and a cisco.com server. In the real world 14 00:01:30,900 --> 00:01:40,230 if I ping google.com that DNS name needs to be resolved by a DNS server. 15 00:01:40,230 --> 00:01:46,010 In my example, I'm using 8.8.8.8 as my DNS server. 16 00:01:46,440 --> 00:01:54,610 So that is a Google DNS server and we'll replicate that in our packet tracer network. 17 00:01:54,630 --> 00:02:01,890 Now there's a lot to do and hence we going to split up the configuration of this topology into multiple 18 00:02:01,890 --> 00:02:03,070 videos. 19 00:02:03,180 --> 00:02:05,960 You'll firstly need to power up the switches. 20 00:02:06,150 --> 00:02:13,710 You'll have to configure basics such as hostnames IP addresses usernames and passwords and inter VLAN 21 00:02:13,710 --> 00:02:16,920 routing on the core switches. 22 00:02:16,920 --> 00:02:22,980 As this is a layer 2 topology you're going to need to configure the links between the switches as trunk 23 00:02:22,980 --> 00:02:28,090 ports and the ports to the PCs as access ports. 24 00:02:28,200 --> 00:02:32,330 The PCs in this network are in different VLANs. 25 00:02:32,340 --> 00:02:33,860 PC 1 is in VLAN 10 26 00:02:33,870 --> 00:02:36,000 PC 2 is in VLAN 20 27 00:02:36,000 --> 00:02:44,010 and PC 3 is in VLAN 40, so you'll need to configure these ports on the access switches with the relevant 28 00:02:44,010 --> 00:02:45,330 VLANs. 29 00:02:45,420 --> 00:02:52,150 You'll also need to configure the server in VLAN 100 on this core switch. 30 00:02:52,260 --> 00:02:58,410 In addition, because this is a layer 2 topology spanning tree is going to be used, spanning tree runs 31 00:02:58,410 --> 00:03:02,360 by default on Cisco switches but it's not optimized. 32 00:03:02,490 --> 00:03:07,600 You will need to optimize the spanning tree in this network. 33 00:03:07,680 --> 00:03:13,440 You're going to configure the switch on the left as the route switch for some VLANs and the switch on 34 00:03:13,440 --> 00:03:19,950 the right as the route switch for other VLANs. In the real world on your access switches, you may 35 00:03:19,950 --> 00:03:27,510 have devices in multiple VLANs, so as an example you may have IP phones as well as PCs in your 36 00:03:27,510 --> 00:03:34,320 topology and you're gonna wanna send some traffic to the call using this uplink and other traffic 37 00:03:34,320 --> 00:03:37,050 to the core using this uplink. 38 00:03:37,140 --> 00:03:44,670 So we're going to wanna optimize spanning tree for load sharing but also to ensure that we are not 39 00:03:44,670 --> 00:03:50,640 blocking links that can negatively affect the throughput through our network. 40 00:03:50,760 --> 00:03:57,960 As an example, if access switch 2 became the route it would mess up the forwarding of traffic through 41 00:03:57,960 --> 00:03:59,250 the network. 42 00:03:59,310 --> 00:04:05,040 So we need to optimize our spanning tree to make sure that the core switches are the route switches 43 00:04:05,460 --> 00:04:08,760 and that we load share traffic across them. 44 00:04:08,760 --> 00:04:14,700 We also gonna wanna make sure that these two links in the core are configured to use ether 45 00:04:14,700 --> 00:04:20,700 channel so that both are forwarding rather than having one of the ports blocking. 46 00:04:20,700 --> 00:04:27,510 We need to configure the core switches for inter VLAN routing so they're going to need multiple 47 00:04:27,510 --> 00:04:30,100 switched virtual interfaces configured. 48 00:04:30,480 --> 00:04:36,000 They're gonna have to be configured with routing protocols such as EIGRP so that they can exchange 49 00:04:36,000 --> 00:04:39,020 routes with the ISR router. 50 00:04:39,150 --> 00:04:46,230 The ISR router needs to be configured with basic configurations but it also needs to be configured with 51 00:04:46,230 --> 00:04:55,950 EIGRP and net or network address translation to ensure that these devices in our network can get to 52 00:04:55,950 --> 00:05:03,660 the internet. Now one of the things to think about when you have multiple core switches is which switch 53 00:05:03,750 --> 00:05:09,700 becomes the default gateway for your PCs at the access layer. 54 00:05:09,780 --> 00:05:17,580 We want multiple core switches for redundancy and for load sharing traffic across uplinks but which 55 00:05:17,670 --> 00:05:25,470 switch will be the default gateway for this PC. If we configured the switch as the default gateway 56 00:05:25,890 --> 00:05:28,050 and that switch went down 57 00:05:28,080 --> 00:05:32,750 PC 1 wouldn't be able to send traffic to other VLANs. 58 00:05:32,880 --> 00:05:40,710 So what we gonna wanna do in the core is enable protocols such as HSRP or hot standby running 59 00:05:40,710 --> 00:05:41,910 protocol. 60 00:05:41,910 --> 00:05:46,380 So we need to configure HSRP on our core network. 61 00:05:46,440 --> 00:05:54,300 That means that rather than PC 1, PC 2, and PC 3 using one of the switches in the core as 62 00:05:54,300 --> 00:06:01,620 the default gateway they point to the virtual HSRP router. If one of the core switches goes down 63 00:06:01,620 --> 00:06:09,270 it's not a problem because traffic can be inter VLAN routed by the remaining core router. However 64 00:06:09,360 --> 00:06:13,260 whenever you enable HSRP and you're using it 65 00:06:13,260 --> 00:06:19,360 in addition to spanning tree, you're gonna wanna optimize the link between spanning tree and HS 66 00:06:19,370 --> 00:06:20,340 RP. 67 00:06:20,430 --> 00:06:29,720 In other words, if switch 1 is the HSRP primary router or master router for VLAN 10 you're gonna 68 00:06:29,720 --> 00:06:34,480 want it to be the spanning tree route for VLAN 10. 69 00:06:34,500 --> 00:06:40,710 In other words, you don't want a mismatch between your spanning-tree routes and your HSRP primary routers 70 00:06:41,460 --> 00:06:49,560 or active routers if he's the HSRP active router for VLAN 10 he needs to be the route for VLAN 10 if 71 00:06:49,560 --> 00:06:57,180 the switches the HSRP active router for VLAN 20 it needs to be the route for VLAN 20. So as you can see 72 00:06:57,180 --> 00:07:03,300 there's a lot to do we're gonna configure some of the basics initially and then as we continue we'll 73 00:07:03,300 --> 00:07:07,880 configure more and more to get this network fully working. 74 00:07:08,250 --> 00:07:16,950 I'm hoping that this gives you a practical real world example of how to configure networks but in addition 75 00:07:17,430 --> 00:07:25,470 I'm confident that it'll prepare you well for the CCNA exam so try and do the labs yourself. 76 00:07:25,470 --> 00:07:31,190 Download the packet tracer files and see if you can complete the list of tasks yourself. 77 00:07:31,320 --> 00:07:37,530 If you struggle or if you'd like to learn some additional tips and tricks watch my videos where I con 78 00:07:37,530 --> 00:07:38,700 figure the devices. 79 00:07:38,700 --> 00:07:52,050 Per the requirements given to us so let's get started configuring this campus network.