Packet Tracer Lab Routing Switching Trunking | Cisco CCNA 200-301

Video Statistics and Information

Video
Captions Word Cloud
Reddit Comments
Captions
[Music] and welcome everybody it's great to have you here you know it's more fun than configuring Cisco gear gosh there's a short list probably there may be one or two things above that but our objectives in this video is to provide you with a packet tracer lab that'll have the opportunity for you to practice switching and routing and trunking DHCP DHCP relay and more so my name is keith barker if you're brand new to the channel hey welcome it's great to have you here I am recording this for a life premiere that's gonna happen at 4 p.m. today it is 913 and I am meeting I have another meeting at 10 o'clock so hopefully I can do this walkthrough of inputting the solutions for this packet tracer lab in less than 30 minutes from soup to dessert I'll just leave the camera rolling so it's great to have you here if you are new to Cisco or if you're new to this channel and you want to peruse the master playlist please visit the channel there's a Cisco 200 301 CCNA master playlist just go to that list it's got a lot of great content including it'll cover a lot of most of the tech many of the technologies we're gonna use today as we build this package for lab so let me introduce you to where you can get the lab and then also where you can download it so you can practice it and then I'll do the walkthrough ad together with you let's take a look at the topology and then move my my mic over a little bit and a question might come up with say well a packet tracer where do I get it you get it from net a CAD comm and it's a cisco educational site you can get a free assign them for free and then download for free and you've got packet tracer and then as far as this lab goes I have 4 pcs here let's see here I've got you know I pin out I've got 4 pcs PC 1 2 3 & 4 I've got a server that's acting as a web server and the DNS server I've also got this multi-layer switch and these two access layer switches with the ports involved in between them and a person could just drag these up from the topology and create this topology or we could start with this framework which is what I would encourage you to do and in that light what I done is I've made this available so you can download it right here from the Keith Barker comm and that web page looks like this well part of it does anyway so this is the Keith Barker comm and there's a section for downloads there can you scroll down either way you want yeah and this is a lab right here that we're gonna be focusing on and make sure it's in frame it is great so this is the lab right here Cisco PT o GI T for the original gangster of I T 20 2004 0-7 that was the date that they actually put that framework together that lab and you just click on this download link right here you know download that lab file to your computer so if you have packet tracer installed you can go ahead and open it and start where I am right now so our objective in this lab and I put the in that download it has a PDF with all the instructions I also put I love this I also put the instructions right here in the lab so you can actually look at it and see the instructions as you go through and basically the goal is this we want pcs 1 & 3 let you get out the right pen here we want pcs 1 3 that's this guy and this guy we want them to be in VLAN 10 which means that the access ports here on the switches are going to be associated with VLAN 10 and they want and the the subnet for VLAN 10 is 10 1600 / 24 and if you're a brand new to IP addressing and subnetting all the rest check out our subnet saturdays it's also part of the master playlist on the youtube channel okay so 1016 there'll be VLAN 10 and then for VLAN 20 which I'll put it in a different color for them 20 we have pcs 2 & 4 and that subnet is 170 2.16 dot 0 dot 0 with a 24 bit mask great DHCP assigned addresses for these pcs this is our DHCP server right here and let's see here DHCP and web server is in VLAN 777 so we put yet another color here so VLAN 777 and I mean else yeah let me go back in document this to you 20 and 20 and they go back so villain 777 and this server and this is the seven seven seven is the one ninety two dot one sixty eight one zero network with a 24-bit mask and they want to use dot one hundred for the server okay so you know what helps me when I'm working on a lab is that I create I yesterday I put these together and I'm about to implement the configuration on top of the infrastructure or the underlay but it also helps me to write it out or it's just what I'm doing right now and so if you want take a separate piece of paper and pause and just or when you're doing the lab just write it out you're clear on what goes where the Carpenters rule is measure twice cut once and if I have had this happen more a lot more times I am care to them admit and there's a rush into something and I'll put the wrong address on it or I'll have the wrong subnet in mind or the wrong default gateway and I'll it'll be a problem so just document it take your time planning and then go ahead and implement it alright so DHCP web server is in two thousand seven seven seven subnets that and it's not one hundred great the default gateway is dot one in each subnet alright so that means the default gateway for VLAN 10 is gonna be dot one the default gateway I'll put gateway here will document that the default gateway for than 20 is gonna be dot one the default gateway for 777 is gonna be dot one now I'm looking at this topology and it doesn't really say who the router is but I know who the routers gonna be the only device here that has routing capability for other devices is this guy right here that's gonna be the router which also means that this device this multi-layer switch we're gonna have to have SBI is switched virtual interfaces one to support VLAN 10 one is Part B then twenty and one to support VLAN 777 and it's gonna have a dot one address on each of those interface B lens so if you're new to interface VLANs or SBI's check out those videos in the master place as well alright and then I'm gonna go to my pointer so I can scroll up just a little bit here and it says verify clients can ping each other and verify clients can open up the web page of the server at keithbower.com all right all right well I'm going to leave that marking in the background and let's go to work and let's configure and I think I'm gonna bring up one of my favorite tools to do this and that is notepad and actually maybe I won't leave all that up there we'll see let's see make sure we can see this all right there are certain things although all the devices are on there default configuration up the server has a little bit of information on it but the switches and the PCs are all their defaults so here are a few things that I probably would do on a brand new networking device if it was Cisco and that'd be a gun configuration mode I didn't know IP domain lookup making sure my head isn't on top of that okay and then what else do we wanna do how about line console 0 and logging synchronous I'm just putting shortcuts there and then also no exec - timeout because in the lab environment I don't want to have to log in log out every a lot just put me in and also privilege level 15 so I just connect to the console puts me in privilege level 15 I'm good to go no look there's no log in there by default so that's good what else all these are kind of these three switches or switches so I might as well do this I'm gonna exit just I don't have to use the X I could just jump but the exit there for you and I just realize that we just jumped out of line configuration mode and let's do a spanning tree mode rapid for rapid spanning tree and this also do spanning tree port fast default I'm just doing some of the shortcuts here but that way my clients when they connect if I have to bounce an interface it won't be a long time before they come in and let's see what else I might want to do no IP domain lookup logging synchronous no exact timeout pros l15 and how about a hostname yeah and then I'll just take that and I'll start there with each of the devices so I'll just copy that right click copy and let's go configure switch 1 so there is switch 1 and I'll bring this over to the right a little bit and I think I will hide just my writing for a moment and we'll come back to that if we need to so this is switch 1 making sure we can all see it and then to the CLI and able and then I'm just gonna do a right-click and a paste and I'll call that SW 1 and I'll say that WR is a shortcut for write memory or in the old days in the old days that's a shortcut for copy run start that takes your running config and saves it to the startup config alright and we'll go to switch to and once we have these dialed in by the way the business tab between the R go between these interfaces these devices and we don't have to resize it every time so I'll right click here is on switch to paste and just confirming which one one one one switch to is right there and we'll call it switch 2 and then we'll go to switch 3 and go to CLI and able and paste ok all right so we've got some basic like comfort like comfort food comfort commands on our switches let's next set up the infrastructure let's set trunking oh ok so these interfaces here if you don't want to see them all the time you can go to options and we can go to preferences and we can select instead of always show port labels we can do turn that off and then you can have this option over here show port labels when you mouse over them so I'm gonna leave them up for now unless they get too busy but I think this isn't too bad we can still see where they're at and let's let's configure our trunks and our VTP and our VLANs it's all all important so let's bring up notepad again and you don't have to use notepad I'm just doing it because it's gonna be a little bit more convenient so we did all that I'm gonna get rid of it so I don't do it again and I'll go to configuration mode and will say VTP they're gonna be servers by default so let's say VTP domain og IT and that allow us to replicate our VLANs and oh if we have trunks let's do that too yeah so it'll get an interface on these two switches switch one switch to interface range FA 0 slash 11 comma FA 0 / 22 l+ into interface configuration mode for those two interfaces and we'll say switch port mode trunk so if you have a device that supports ISL which is really really old or 802 W you could say switch port trunk encapsulation dot1q and then that would tell it what type to use then you could say it's the trunk and M and for switched okay I'm also yeah I'll make it clean so we'll do this real quick and then I'll see ya so this would be unjust switch 1 2 and I'll go switch 1 right click paste alright and go to switch to and paste okay and then on switch 3 it's gonna be slightly different so we can just do that manually oh oh I got these gigabit interfaces - they both have gigs 0 1 & 0 okay you know what we have gig 0 right now I can't forget any of these ports so let's do let's do this I am gonna erase my old work and start new so I've got give me one moment here we go I've got this interface gig 0 / 1 & 0 / 1 and 0 2 & 0 2 and if I just made a crypt it said ok 0 1 & 0 2 are all going to be trunks and I well you know what I'll just doing manually I'm trying to save time but it takes more time to explain than just to do it so let me just go into interface configuration mode and do it so here on the switch 1 will go into interface gig 0 / 1 switch port no trunk done and we'll do the same thing on switch to did four gigs eros left to config T interface gig 0/2 switch port mode trunk and then we'll go to switch three and on switch three we need to configure it's alright do this way alright so I'm sorry is we need to do a gig 0 1 & 0 2 as trunks so we have videos on trunking in the master playlist for CCNA check that off you're new to trunking and interface range gig 0 / 1 through 2 and I work and then switch port trunk encapsulation ok doc so this multi-layer switch perhaps supports more than just one trunking protocol so I'm gonna specify dot1q as the standard and then we'll do a switch port and not storm control switch port mode trunk and then we should be able to create our VLANs and they should show up everywhere so VLAN 10 VLAN 20 VLAN 777 show VLAN briefed and let me spread this a little bit further here we go all right so I've got villains 10 20 and 7 7 7 I have no active access ports in it but if we do a show interface trunk I am supporting on my two trunk ports all those VLANs so we are good to go we've got the VLANs and because VTP is enabled we by default and we set the domain if we go to switch 1 we should have a same VLAN there show VLAN briefed sure not what I was expecting those feelings to be there oh did we not make a switch 3 part of that domain hold on a second show VTP status yeah ah we didn't make this hit we didn't makes I didn't make sense we we didn't do this I didn't make such 3a VTP member in that domain so we'll just fix that VTP domain og IT alright so now we have trunking we have a domain set and let's see it let's do a show VLAN brief okay we didn't lose the VLANs that's good and let's go to switch one and see if they're there not yet it's so GI T okay let me I'm gonna do this this is a very real I'm gonna bounce it by just adding a new VLAN that will increment the counter and config T VLAN 999 exit it's the exit as when that VLAN actually becomes active and let's go take a look at switch one show VLAN brief okay see this is kind of like jiggled it loose if we had waited a few minutes it probably have synchronized as well we no longer need VLAN 99 9 so I'm gonna get rid of it no VLAN 99 all right and if we go back to switch one was a show of VLAN brief all right now we're cooking with gas and we gonna switch to make sure he's all happy to show be that brief sure enough all the VLANs that we need exist alright so let's take a look at our playbook here pcs 1 & 3 need to be in VLAN 10 so we need to go to this these two ports FA 0 / 1 + F switch 1 and FA 0 / 3 on switch to and assign them to be in be LAN 10 and we all see to assign FA 0 / 2 for PC 2 and FA 0 / 4 for pc 4 to VLAN 20 so let's do that that's gonna be important to make this work as well so we'll we'll do it let me go to switch 1 and here on switch 1 we'll just do a config T interface FA 0 / 1 switch port mode access and switch port access VLAN 10 and then we'll go up to FA 0 / to do the same thing again except we'll put it into VLAN 20 show VLAN briefed always verify our work afterwards and great so our two ports are assigned correctly based on our plan let's go to switch to alright switch to we're going to put the two respective parts in the VLANs 10 and 20 also so config T and interface FAA is 0/3 switch port mode access and switch port access would be like VLAN 10 and we'll get it oh that's the wrong port so we're not even using port FA 0 / - here it's FA 0 / 3 all right let me do this just to bring it back to normal default interface if a is 0 / 2 boom just setting it back to what it used to be all right interface FA 0 / 3 is where we want to go and we want to do a switch port mode access the switch port access VLAN 10 and then we want to go to interface faz else left for making an access port and make it in view that 20 then we'll verify our work show VLAN briefed all right so I've got those two ports properly a sign all right super I think we're in oh and also this server right here the server that's hanging off of FA 0 / 5 needs to be in VLAN 7 7 7 so let's do that - so config T and config T interface FA 0 / 5 ant Wow look at that 5 and switch port mode access switch port access VLAN 777 and we'll verify our work there - she'll be that brief those look great okay all right we're making progress here all right we got a few minutes on the clock we're still doing good we have our trunking set up we have our VLANs created on all the switches we have the access ports a sign for the four pcs and for the server well since I noticed oh they're gonna need IP addresses and they need to be DHCP assigned addresses okay so we need to create scopes as they would be called in Microsoft DHCP or pools of addresses that the DHCP server can handout now this server is over here in VLAN 777 so we're gonna need some dhcp relays on the clients local network so they can actually get those requests sent over to the server we also have videos in the master playlist on DHCP relay as well so here on the server on this DHCP servers also acting as a web server what we'll do is we'll click on services oh let's check out its IP address to you so if we go to config and go to Fast Ethernet 0 it has the right address that's good 192 168 1 dot 100 and go to settings its default gateway is dot 1 good it needs to be able to communicate off of its local VLAN 777 which is the 192 168 1 Network alright so let's go ahead and click on services and checking my feedback monitor there great so on services and we're looking at this server right here let's go to http we're gonna need up leave that later so HTTP services are working and or at least they're enabled and DHCP it has this default server pool but we need it's not the right addresses though we need two pools of dresses one for the ten dot white network with it one for the ten dot 16-0 Network and one for the ten set once you do 16 Network so let's go ahead and create those and here's how you do it right here in packet tracer first of all we're gonna turn on the service otherwise it won't work and then we'll go ahead and we'll say our pool I'm gonna call the pool be LAN ten just so I want to see it I'll know what it is the default gateway for VLAN 10 is going to be ten dot 16.0 that one based on our plan the DNS server is actually the server and that serves at one ninety two dot one sixty eight dot one that one hundred it's acting as a DNS server and the web server and a DHCP server and we can also verify the DNS service as well as well like right here so it's running DNS all right back to DHCP oh great I didn't save my work so no problem round two all right with VLAN 10 and VLAN 10s default gateways 10.16 dot 0 that one that's why it's good to have it on paper reference you know where you're going the DNS server is one ninety two dot one sixty eight dot one that one hundred great nope yep that's it and I gotta take these in order so you make sure I do right so the starting address for this DHCP pool that we're creating is ten dot 16.0 I'm putting in periods many operating systems you ten dot skips you over packet tracer is making me over maybe tab over so 10.16 zero dot and then I start my first IP address is at ten just because we can I'm gonna hat and the mask is 24 bits that's great join us for subnet Saturdays for more on ipv4 dressing and masking in subnets and the maximum number of clients I'm gonna just do ten I we're only in the two in each subnet ten is gonna be plenty and then here's the important part I got all that information in add and that adds that pool so let's verify our work ten 1601 default gateway DNS server is the server starting address of ten great let's make one more for VLAN twenty one more pool so if you that twenty is 172 sixteen will start at tenth there as well 24-bit mask default gateway is going to be nine seventy 2.16 dot zero dot one that's important DNS servers the same click on add and now we have two pools one for VLAN 10 one three then twenty all right all right I'll write or write and it's enabled so the server looks good let's make sure we're from the server we can ping well I was about let's take sure from the DHCP server we can ping and I realized we don't have any IP addresses on any other devices yet so there's no there's nobody out there at a pain yet to verify basic connectivity so let's next tackle let's tackle the multi-layer switch which is gonna need three VLAN interfaces one for VM ten one for view then 2141 777 with the appropriate IP addresses and then we should be able to ping the from the DHCP server and the web server on that local network we should build a ping one of those interfaces let's do that next alright so back to our topology we go here on switch three we are going to create three SPI is switched virtual interfaces logically or three interfaces again we have some videos in the playlist on exactly what that is and how that works for all those details let's chauvelin reef mmm let's do the show IP interface brief I want to see what layer three interfaces we have so far and this says that we have as far as so we have no IP addresses there's nothing IP address wise here and this also shows VLAN 1 is administratively down I'm not using VLAN 1 so I'm not even gonna worry about that so I'll just do a config T and we'll create interface VLAN 10 this will support and be a logical layer 3 interface for any device that's in VLAN 10 and we'll give the IP address of 10.16 0.1 because that's the default gateway that we're handing out from the dhcp server and we'll put a 24-bit mask on that and that's how you spell a 24-bit mask and dotted decimal and then we'll create interface VLAN 20 and we'll do it IP address or of 172 dot 16.0 that one the first IP address in that ipv4 subnet and the 24-bit mask and 1 4 7 7 7 v 9 7 7 7 so interface VLAN 7 7 7 IP address 192 dot 168 dot one dot one with a 24-bit mask alright and then the key thing here my friends is to verify our work show IP this gives us this chance to verify that the commands took they there wasn't an error and also to remind ourselves of what those addresses were show IP interface brief and if we scroll all the way the bottom we have these 3 logical layer 3 VLAN interfaces supporting their respective VLANs and the clients in those VLANs the addresses all look correct now what we should be able to do because we have the logic on this is as I look at my clock oh yeah we're good so the logic on this is this server is in VLAN 7 7 7 and it's got the IP address of one ninety two dot one sixty eight dot one dot one hundred this switch 3 has a logical interface in VLAN seven seven seven it's called interface VLAN seven seven seven and it's got the IP address ending in dot one so we should be able to ping back and forth between those and let's start there one step at a time so let's go and let's go to switch 3 and su pain to our server at one ninety two dot one sixty eight dot one dot one hundred all right and that first ping usually drops on a Cisco device because of ARP the ARP it does our request and basically fails to even send that first ICMP echo request because doing the ARP and then the second one we should get five out of five great and we should also from this server all right well let's you know there's lots of cool things we could do here let's continue on with our configuration next we need to give these clients IP addresses via DHCP so to do that what we can do is we could try if we just hover over those devices check it out if we hover here well let's go configure it oh oh look at that okay it has an IP address I wasn't expecting you to have an IP address but that's must be because of the previous config so let's go to config on PC one and we'll click on interface and then below interface fa0 oh it's statically assigned so if we want a DHCP assigned address we click on the DHCP radio button and that goes to the Douro process discover offer request technology except in this time it got a 169 address and that is because there's no local DHCP server and we don't have a helper an DHCP relay agent on VLAN 10 forwarding those requests over to the real DHCP server so we have another whole video in the playlist master playlist on DHCP and DHCP relay check that up here if you need to some backfill on that but the short story is we need to configure IP helper addresses on VLAN 10 and VLAN 20 so the clients on those networks can have their discover messages sent shipped over to the DHCP server who can then respond back through the relay and make it work and that happens on the routers in those VLANs and in our case our switch 3 is our multi-layer switch acting as the router so go to configuration mode interface VLAN 10 and we'll say it's DHCP relay but the syntax is IP helper I think yeah oh I see there's two options IP helper address and then we point to the IP address of the real DHCP server so we can route those packets route those packets over to that server so it's one ninety two dot one sixty eight dot one dot one hundred great and we'll do the same thing for interface VLAN 20 and IP helper dress so basically now any clients I'm feeling ten or even twenty when they do their discovers for a DHCP server and those can be packaged by switch three on the road on those associate V them shipped over to the DHCP server who can then relay those back through the IP IP helper function back to the clients so the Douro process still happens from the perspective of the client it's just the back half is being routed back and forth between the helper and the server so let's see if that worked let's go to PC one and it still has a an IP address that says it's no good let's just click on static take a breath and then click on DHCP yeah it got a ten sixteen zero ten great we the same thing for PC two which is in VLAN 20 you should get a one semi 216 address we'll go to config fastethernet click on DHCP that's working for both so it's gonna work everywhere so get a PC three just working for those two beats probably if it's working for those two VLANs that means we're good in good shape PC three DCP and PC for Oh DCP cool so if we so this guy pc4 if everything's working correctly we should be able to ping PC one from PC 4 so let's go ahead and just that guy is 10 16 0 10 let's go to PC 4 and verify we can ping him desktop command prompt pinging 10.16 dot 0 dot 1000 so close so close all right let's see if we can ping our default gateway IP config our default brick that may feel bigger our default gateway is dot 1 let's make sure we can ping him 10 16 0.1 okay and let's do this let's make sure we can ping the other side let's do a ping 10 16 0.1 all right I know what this is so the PC is default gateway is working it can reach and forward packets to non-local IP addresses but switch 3 check this out if we do a nice show IP route see how it doesn't show you the routing codes or anything even though it's a multi-layer switch and even though we have SV eyes on la3 interfaces IP routing is not enabled on this switch and I didn't intend that originally but that's what's happening here so if we go to config T and to enable ipv4 routing its IP routing that's the command so show IP route alright so now we have a routing table before the switch was not willing to route packets on behalf of other devices so if we go back to PC 4 and we hit the up arrow key a few times and try to ping 10 16 0 10 oh there we go okay so that first ARP if the switch needed to go ahead and do art for that final destination all right there we go and as a last test let's go ahead and on the PC what a PC three will mix it up a little bit we'll go to desktop and go to web browser and the goal is to be able to go to w2 go to the keith Barker com that's in the instruction for the lab and there it is I'd like to take Dan on the discards channel and also on the YouTube page for creating and customizing this packet tracer web server for me I was just blown away I thought I'm gonna use that it's can I use that yeah so what's happening behind the scenes that when this when any of these clients go to this URL it's using DNS and the DNS server is the web server it's got an a record that's for the Keith Barker comm that points to the web server and that's why this is working so there's a little mock image of the Keith Barker com you can also go there on the real web to get to download this lab if you want to practice it there's the O GI t com the playlist on YouTube and then there's the discard server as well I've got links for others in the videos as well for all those resources alright so that is that's the that's the packet tracer lab I wanted to present to you and give you a chance to practice and play with because it's not troubleshooting there's really not a spoiler alert it's more of a hey here's a way to practice let's see DHCP DHCP relay access ports trunk ports routing SV eyes multi-layer switch all of it right here in this teeny little packet tracer lab so have a lot of fun with it if you were able to complete this lab and do it and walk through so just post a note associate with this video saying hey I complete the lab and I'm gonna have more of these as they come up if if you haven't yet joined the channel please do so click on subscribe we'd love to have you here and participate with you I dropped videos new videos premieres two to three times a week consistently that's happened since October of 2019 and I'm just adding those to the master playlist I'm gonna be replacing a few videos as well my hope for you as we focus 100% here on this channel on CCNA 200 301 my focus or in the future if they rename it I focuses the technology is associated with Cisco CCNA level technology the meats the meat and potatoes of networking and I have a blast doing it so thank you for your participation thank you for watching if you liked the video hey click on that thumbs up let other people know and I'll see you my friend in a future video thanks and bye for now [Music]
Info
Channel: Keith Barker
Views: 22,361
Rating: 4.977591 out of 5
Keywords: ccna, cisco, 200-301, Cisco CCNA, Cisco Certification, ogit, Keith Barker, Packet Tracer, cisco packet tracer, ccna labs, ccna training, cisco training, packet tracer, packet tracer labs, new ccna, packet tracer lab, packet tracer labs ccna, 200-301 videos, packet tracer labs for beginners, cisco ccna 200-301, 200-301 ccna, cisco ccna training, ccna study videos, packet tracer labs 200-301, new ccna exam (200-301), cisco training for beginners, routing, switching, trunking
Id: A2M_1KC0Ck8
Channel Id: undefined
Length: 35min 23sec (2123 seconds)
Published: Wed Apr 08 2020
Related Videos
Note
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.