CCNA ITN - 7.3.7 Lab - View Network Device MAC Addresses(Packet Tracer version)

hey everybody this is mr mckee again with net 125. um i'm going to be going over lab 7.3.7 which is view the switch mac address table now what i did i just set up a um topology that mirrors um what we're looking at right here um because this would require us to actually set up um some physical switches and i'm gonna see if it works with packet tracer just as good as physical switches i will be doing some labs hopefully um with physical switches showing you guys everything um it plugs together but it can connect together but for now this this should work fine all right so there's our grossing table we'll need to know that and what i'm going to do too i'm going to say okay this is switch one all right this is gonna be h2 all right this is going to be pc a and this is going to be pcb all right i'm going to say this all right so this will be this will be the version of the file that you guys will get on the submission link in moodle let me go ahead and configure it all right so the purpose of where to land switch is to deliver ethernet frames to host devices on the local network the switch records host mac addresses that are visible on the network and maps those mac addresses to its own ethernet switch ports the process is called building the mac address table when a switch receives a frame from a pc it examines the frame source and destination mac address the source mac address is recorded and mapped to the switch port for which it from which it arrived then the destination mac address is looked up in the mac address table the destination mac address is is a known address then the frame is forwarded out of the corresponding switch port associated with mac address if the mac address is unknown then a frame is broadcasted remember with all f's for the mac address out all the port switchboards except the one from which it came so it goes out everything but from where it come came from so pca it's plug it's connected to fa06 it won't go in that back out that port but all the other ports all right so where we at it is important to observe and understand the function of a switch and how it delivers data on the network the way switch operates has implications for the network administrators whose job it is to ensure secure and consistent network communication all right switches are used to interconnect and deliver information to computers on local networks such as deliver ethernet frames to host devices identified by network interface card mac addresses all right in part one you will build a multi-switch topology with a trunking link and this is a trunking link right here in our case notice it is a crossover cable not a straight through cable like these other two are going from switch to pcs in part two you will ping various devices and observe how the two switches build their mac address tables all right and it says the switches are used for catalytic 2960s all right but we should be able to use what we got right here all right and ours do not have any sort of configs in there and i'm going to try to remember not to save this i've already saved it just wait it's set up with no configurations all right and just a note right here the fast engine that switches on cisco 2960 switches are auto sensing and ethernet straight through cable may be used between switch one and two but i didn't do that i just wanted to do it correctly all right if using another model cisco switch it might be necessary to use a ethernet crossover cable all right so build and configure the network cable the network according to the topology that's done for you configure pc hosts all right now it says configure the pc host so let's go up here and pca is right there we'll go to desktop.2.168.1.1 all right we're going to leave the default gateway off all right so that's all we need for that one pcb let's do this and then 2.168.1.2 tab down verify okay it is a class c address so that subnet mask is fine all right so let's get back to what we were doing initialize and load switches as necessary configure basic switches basic settings for each switch all right remember configure the device name configure ip address as listed in the dressing table assign cisco as the console and uh vdy passwords assign cisco as the privileged exec password all right so remember first thing we got to do since nothing's net nothing has ip addresses yet configured on the switches you can't just open up a pc open up a terminal and just connect it's not it's not able to connect like that we would have to go down here get our console cable and what i'm going to do i'm going to do a console cable from pc8 to s1 and then a console cable from pcb to s2 all right so that should be good now all right so configure device name i'm gonna go up here so go here i'm gonna go to desktop terminal right notice how it's loaded now and don't get confused remember if you see up here it says it's pca but we're in the terminal and we're remoted into uh with the console cable well actually not really remote we have a console cable plugged between pca and s1 all right notice our our prompt has switched still so it's going to enable and host name s1 all right and we're going to do interface vlan 1 uh what's the ip address 102.168.1.11 all right remember i got turned on so no shut down all right so that one's up now i think that's all it needs to be configured okay so we need to do a assign cisco as a password for the console i believe we can do it from here but let me see all right so i had to use exit go back zero all right i'm gonna get a password cisco remember login line another line it's it's good to practice that over and over again just more or less muscle memory all right so let's exit out of that um do it enable enable password class it doesn't say to do encrypted but i probably would do that but enable password class we do exit share run we notice hostname is configured enable password is configured spacebar down interface vlan 1 uh svi is configured and cisco password is configured for everything all right all right so that one's good so let's go over to pcb and we're going to do s2's stuff all right if you're still having to look up all these commands or just watch me and reproduce it it takes a little while to get get all the commands down all right enable all right so first thing hostname i'm going to change that to s2 all right um all right number one shut down turn it on all right and i don't want to get the password backwards so let me look so let's go back exit all right so my [Applause] all right to 15. oh you don't spell it right it doesn't know all right password cisco all right excellent enable password class all right and from here i can do a do show run do let you go back one without actually exiting all right so hostname s2 enable password class there's my ip address let's verify that that's correct all right and then console in the d2i lines are all cisco all right so we stopped at right here the switch learns mac addresses and builds mac address table as network devices initiate communication on the network open a command prompt on pca and pcb all right config oh all right what are the ethernet physical addresses you guys should be able to see those all right one for pca one for pcb all right and then console into switch one and two and type the show interface uh interface f01 so i'm going to go back all right from the terminal remember i'm connected into s1 there and then here i'm connecting s2 so let me exit out of that all right so s1 i'm going to do show interface f01 all right on the second line of the command output what is the hardware address or burned in address bia it's right there right yeah that's super small but hopefully you guys can see that all right then over here show interface f01 all right there's the address right there all right so console into switch 2 which is the switch to right here notice if i get confused i can look at the command prompt and control c to get out of that all right enter privileged exec mode which i'm at right now all right show mac address table all right so even though there has been no network communications initiated across the network uh it's possible that the switch has learned mac addresses from its connections to pc and other switch and the other switch are there any mac addresses recorded in the mac address table well yeah we have one that's connected to fa01 and if you notice here it knows that one their switch and what is the mac address located in the table what's right there okay to which switch port are they mapped and to which devices do they belong well if you look right there if i go over here actually i can't do that go over here and just right here that's the same one switch one same mac address so it's it's looking at the mac address on the interface of fa01 for switch a all right it says ignore mac addresses that are mapped to the cpu all right if you had not previously recorded mac addresses of network devices in step one how could you tell which devices that mac addresses belong to using only the output from show i should mac address table uh you could answer that you could probably do it just like i did it if you didn't know all right this is working all scenarios you can put that down but i'll let you i'll let you guys answer that yourselves all right so it wants us to clear the s2 mac address table and display the mac address table again for this exec mode type the clear mac address table dynamic clear mac address table dynamic all right quickly type in mac address table it's already back all right clear show all right so did it quick all right now it's empty if you wait for like two seconds it pops back in there all right does the mac address table have any addresses in it for vlan 1 well not now if you do it really fast are there any other mac addresses listed you guys can answer that wait 10 seconds show the mac address table command and then press enter all right you're going to keep getting that one from the other switch all right now from pcb ping the device on the net the devices on the network and observe the switch and observe the switch mac address table all right from pcb i'm going to command prompt control c to get out of that part a all right not including multicast or broadcast addresses how many device ipd mac address pairs have been learned by the arp nothing hopefully this works in packet tracer from the pcb command prompt ping pca s1 and s2 if you don't remember the ip addresses you can go up here and i'm going to ping 92.168.1.1 all right i'm going to ping 1.11. i've got that and pink all right do it's saying all right so everything had a successful ping all right let me find where i was at all the way down here all right so on step four from pcb open the command prompt and type pc part day i pinged all the other three devices did all the devices successfully pop ply you can answer that from the console well it doesn't have any share the art table on pcb but okay so let's see what we want to do s2 so that's on pcb but we're going to go through the terminal all right let's do show history all right so now look since we've we've got pings from pretty much going across the network for everybody that shows what's going on on the network you'll notice right here fae that's ethernet zero 18 one pcb so that should be pcbs mac address and then everything else is going through out fa01 so it knows where to send all the traffic all the traffic for the other three devices will go up that way coming from this side of the network all right how is this has the switch added additional mac addresses to the mac address table yes if so which mac addresses and devices you guys could see those but that's pretty much everybody on the network all right so on pcb which we're on go to the command prompt i can go ahead if it lets me get in there come on um okay let's do up arrow all right now look how it's learned other addresses all right and just to be sure before touching anything else pcbs.2 so these are the three other three devices on the network all right does pcb arp cache have additional entries in the network devices that were not that were sent pings all of them are in there now that it pinged all right reflection question on ethernet networks data is delivered to devices by their mac addresses for this to happen switches and pcs dynamically build arc caches and pc address tables with only a few computers on the network this process seems fairly easy what might be some of the challenges on larger networks well i'll let you guys answer that but um just think about being on another network with multiple uh immediate intermediary devices like switches and things like that it's going to get a lot more complicated so you can just explain why that would be a challenge all right but that's it you guys can use this i'll actually upload this packet tracer i'm gonna i'm gonna close that down exit right so you have to do all your configurations but i'll have it physically cabled through packet tracer alright and that's it thanks for watching

Channel: Mr. Mckee

Views: 5,497

Keywords:

Id: l920T1U6c8c

Length: 25min 23sec (1523 seconds)

Published: Tue Aug 25 2020