Lab Report Example - Revision history

BenFranske: /* Description of things learned in the lab: */

2011-01-04T20:09:24Z

Description of things learned in the lab:

← Older revision		Revision as of 20:09, 4 January 2011
Line 144:		Line 144:
	:How to assign ports to a vlan		:How to assign ports to a vlan
	:to change the port speed and duplex settings		:to change the port speed and duplex settings

	~~'''Instructor Sign Off__________________________________________________~~
	~~'''~~

Mart0045 at 15:04, 15 October 2010

2010-10-15T15:04:01Z

← Older revision		Revision as of 15:04, 15 October 2010
Line 1:		Line 1:
	==Name and Lab Description==		==Name and Lab Description==
	'''Dan Martineau'''		'''Dan Martineau'''

	'''Adam Nelson'''		'''Adam Nelson'''

	'''CNT-2530'''		'''CNT-2530'''

	'''Switching Fundamentals and Intermediate Routing'''		'''Switching Fundamentals and Intermediate Routing'''


	'''Lab 2.5.1 Basic Switch Configuration'''		'''Lab 2.5.1 Basic Switch Configuration'''

Mart0045 at 15:03, 15 October 2010

2010-10-15T15:03:45Z

← Older revision		Revision as of 15:03, 15 October 2010
Line 1:		Line 1:
	==Name and Lab Description==		==Name and Lab Description==
	Dan Martineau		'''Dan Martineau'''
	Adam Nelson		'''Adam Nelson'''
	CNT-2530		'''CNT-2530'''
	Switching Fundamentals and Intermediate Routing		'''Switching Fundamentals and Intermediate Routing'''

	Lab 2.5.1 Basic Switch Configuration		'''Lab 2.5.1 Basic Switch Configuration'''

Mart0045 at 15:02, 15 October 2010

2010-10-15T15:02:26Z

← Older revision		Revision as of 15:02, 15 October 2010
Line 1:		Line 1:
			==Name and Lab Description==
	Dan Martineau		Dan Martineau
	Adam Nelson		Adam Nelson

Mart0045 at 14:57, 15 October 2010

2010-10-15T14:57:31Z

← Older revision		Revision as of 14:57, 15 October 2010
Line 66:		Line 66:
	:'''Step 4:''' We cleared the mac address table by issuing the clear mac-address-table dynamic command.		:'''Step 4:''' We cleared the mac address table by issuing the clear mac-address-table dynamic command.

	:Step 5: We found that there were now 20 static addresses and now only 2 dynamic addresses.		:'''Step 5:''' We found that there were now 20 static addresses and now only 2 dynamic addresses.

	:Step 6: After the devices resent frames to switch one the other 2 dynamic addresses were again visible and back on the mac address table.		:'''Step 6:''' After the devices resent frames to switch one the other 2 dynamic addresses were again visible and back on the mac address table.

	:Step 7: We set up a static mac address for PC1 on the switch to 000c.2997.b2d6 by issuing the mac-address-table static 000c.2997.b2d6 vlan 99 interface fa0/18.		:'''Step 7:''' We set up a static mac address for PC1 on the switch to 000c.2997.b2d6 by issuing the mac-address-table static 000c.2997.b2d6 vlan 99 interface fa0/18.

	:Step 8: We verified the results and found that there were 21 static addresses and 23 total mac addresses.		:'''Step 8:''' We verified the results and found that there were 21 static addresses and 23 total mac addresses.

	:Step 9: We removed the static mac address used the same command as before but adding a no in front of it.		:'''Step 9:''' We removed the static mac address used the same command as before but adding a no in front of it.

	:Step 10: We verified the results of step 9 and found that there was 20 static mac addresses now on the table.		:'''Step 10:''' We verified the results of step 9 and found that there was 20 static mac addresses now on the table.

	'''Task 5:'''		'''Task 5:'''

	:Step 1: We setup PC2 with a ip address and default gateway but we did not connect it to the network yet.		:'''Step 1:''' We setup PC2 with a ip address and default gateway but we did not connect it to the network yet.

	:Step 2: We pinged the switch from PC1 and we were successful.		:'''Step 2:''' We pinged the switch from PC1 and we were successful.

	:Step 3: We made sure that the ip addresses where the same as before.		:'''Step 3:''' We made sure that the ip addresses where the same as before.

	:Step 4: We found that on the switch the mac address table had 2 dynamic addresses and it matched PC1.		:'''Step 4:''' We found that on the switch the mac address table had 2 dynamic addresses and it matched PC1.

	:Step 5: We viewed the port security options.		:'''Step 5:''' We viewed the port security options.

	:Step 6: We configured the port security on an access port to 2, sticky, and violation protect.		:'''Step 6:''' We configured the port security on an access port to 2, sticky, and violation protect.

	:Step 7: We verified the security changes that we made on the switch, we found that on fa0/18 was only allowing 2 addresses and if there were more it would shut the port down.		:'''Step 7:''' We verified the security changes that we made on the switch, we found that on fa0/18 was only allowing 2 addresses and if there were more it would shut the port down.

	:Step 8: We examined the running configuration of the switch and found that the security changes where listed.		:'''Step 8:''' We examined the running configuration of the switch and found that the security changes where listed.

	:Step 9: We modified the port security to 1 and violation shutdown.		:'''Step 9:''' We modified the port security to 1 and violation shutdown.

	:Step 10: We then viewed the results and we found that the running configuration was changed to match the settings we had made.		:'''Step 10:''' We then viewed the results and we found that the running configuration was changed to match the settings we had made.

	:Step 11: We unplugged PC1 and plugged in PC2 and almost right away the port shutdown on the switch.		:'''Step 11:''' We unplugged PC1 and plugged in PC2 and almost right away the port shutdown on the switch.

	:Step 12: We verified this by issuing the show interface fa0/18 command on the switch and found that fa0/18 was down and the line protocol was down as well.		:'''Step 12:''' We verified this by issuing the show interface fa0/18 command on the switch and found that fa0/18 was down and the line protocol was down as well.

	:Step 13: We then disconnected PC2 and reconnected PC1 and issued the no shutdown command on the port and it came back up.		:'''Step 13:''' We then disconnected PC2 and reconnected PC1 and issued the no shutdown command on the port and it came back up.

	:Step 14: We cleaned up.		:'''Step 14:''' We cleaned up.


Line 118:		Line 118:
	We tested our lab by running various commands on the switch and the host computers to find things such as mac addresses and running configurations. We also used the TCP/IP settings on the host computers to set up our ip addresses and default gateways and tested these by checking the outputs using the ipconfig /all. We also used the ping command to check all devices and there connectivity on the network that we setup in the lab. We also used the console ports on the switched to tera term into the switch and configure the switches and view various show commands. Some of the commands that we used where:		We tested our lab by running various commands on the switch and the host computers to find things such as mac addresses and running configurations. We also used the TCP/IP settings on the host computers to set up our ip addresses and default gateways and tested these by checking the outputs using the ipconfig /all. We also used the ping command to check all devices and there connectivity on the network that we setup in the lab. We also used the console ports on the switched to tera term into the switch and configure the switches and view various show commands. Some of the commands that we used where:

	:Show run		:'''Show run'''
	:Show mac-address-table		:'''Show mac-address-table'''
	:Show mac-address-table ?		:'''Show mac-address-table ?'''
	:Show interface vlan1		:'''Show interface vlan1'''
	:Show ip interface vlan1		:'''Show ip interface vlan1'''
	:Show version		:'''Show version'''
	:Show interface fa0/18		:'''Show interface fa0/18'''
	:Show vlan		:'''Show vlan'''
	:Show flash		:'''Show flash'''
	:Show start		:'''Show start'''
	:Show interface vlan99		:'''Show interface vlan99'''
	:Show port-security		:'''Show port-security'''


	==Description of things learned in the lab:==		==Description of things learned in the lab:==

Mart0045 at 14:50, 15 October 2010

2010-10-15T14:50:29Z

Mart0045 at 14:47, 15 October 2010

2010-10-15T14:47:05Z

← Older revision		Revision as of 14:47, 15 October 2010
Line 112:		Line 112:
	==Description of problems:==		==Description of problems:==

	:In this lab we had only one problem it was because we were using the vmware and it was adding 2 mac addresses with the vm machine and the host machine in the mac address tables, it was a bit confusing. We were unable to fix this problem so we just ignored the host pc mac addresses on the tables. If we would have used labtops from the lab we would have not had this problem but we made it work so we continued with the lab.		In this lab we had only one problem it was because we were using the vmware and it was adding 2 mac addresses with the vm machine and the host machine in the mac address tables, it was a bit confusing. We were unable to fix this problem so we just ignored the host pc mac addresses on the tables. If we would have used labtops from the lab we would have not had this problem but we made it work so we continued with the lab.

	==How we tested the lab and what the results were:==		==How we tested the lab and what the results were:==

	:We tested our lab by running various commands on the switch and the host computers to find things such as mac addresses and running configurations. We also used the TCP/IP settings on the host computers to set up our ip addresses and default gateways and tested these by checking the outputs using the ipconfig /all. We also used the ping command to check all devices and there connectivity on the network that we setup in the lab. We also used the console ports on the switched to tera term into the switch and configure the switches and view various show commands. Some of the commands that we used where:		We tested our lab by running various commands on the switch and the host computers to find things such as mac addresses and running configurations. We also used the TCP/IP settings on the host computers to set up our ip addresses and default gateways and tested these by checking the outputs using the ipconfig /all. We also used the ping command to check all devices and there connectivity on the network that we setup in the lab. We also used the console ports on the switched to tera term into the switch and configure the switches and view various show commands. Some of the commands that we used where:

	:Show run		:Show run

Mart0045 at 14:46, 15 October 2010

2010-10-15T14:46:27Z

← Older revision		Revision as of 14:46, 15 October 2010
Line 7:		Line 7:


	Description of what we did in the lab:		==Description of what we did in the lab:==

	Task 1:		'''Task 1:'''

	:Step 1: We cabled the network according to the topology so that one computer was connected with an Ethernet cable and a Cross-over cable, and the second pc not currently connected.		:Step 1: We cabled the network according to the topology so that one computer was connected with an Ethernet cable and a Cross-over cable, and the second pc not currently connected.
Line 15:		Line 15:


	Task 2:		'''Task 2:'''

	:Step 1: We entered privileged mode by entering enabled on the switch, and we noticed that the prompt changed from Switch> to Switch#.		:Step 1: We entered privileged mode by entering enabled on the switch, and we noticed that the prompt changed from Switch> to Switch#.
Line 31:		Line 31:
	:Step 7: We issued the show startup-config and again got the message that it was not found because no config had been saved. Then we changed the hostname to S1, and save the config with the copy run start command and now we were able to view the startup config on the switch.		:Step 7: We issued the show startup-config and again got the message that it was not found because no config had been saved. Then we changed the hostname to S1, and save the config with the copy run start command and now we were able to view the startup config on the switch.

	Task 3:		'''Task 3:'''

	:Step 1: We gave the switch a hostname.		:Step 1: We gave the switch a hostname.
Line 56:		Line 56:


	Task 4:		'''Task 4:'''

	:Step 1: We got the mac addresses for all the the computers PC1 was 000c.2997.b2d6 and PC2 was 0027.0e22.0777.		:Step 1: We got the mac addresses for all the the computers PC1 was 000c.2997.b2d6 and PC2 was 0027.0e22.0777.
Line 78:		Line 78:
	:Step 10: We verified the results of step 9 and found that there was 20 static mac addresses now on the table.		:Step 10: We verified the results of step 9 and found that there was 20 static mac addresses now on the table.

	Task 5:		'''Task 5:'''

	:Step 1: We setup PC2 with a ip address and default gateway but we did not connect it to the network yet.		:Step 1: We setup PC2 with a ip address and default gateway but we did not connect it to the network yet.
Line 109:		Line 109:


	Description of problems:
			==Description of problems:==

	:In this lab we had only one problem it was because we were using the vmware and it was adding 2 mac addresses with the vm machine and the host machine in the mac address tables, it was a bit confusing. We were unable to fix this problem so we just ignored the host pc mac addresses on the tables. If we would have used labtops from the lab we would have not had this problem but we made it work so we continued with the lab.		:In this lab we had only one problem it was because we were using the vmware and it was adding 2 mac addresses with the vm machine and the host machine in the mac address tables, it was a bit confusing. We were unable to fix this problem so we just ignored the host pc mac addresses on the tables. If we would have used labtops from the lab we would have not had this problem but we made it work so we continued with the lab.

	How we tested the lab and what the results were:		==How we tested the lab and what the results were:==

	:We tested our lab by running various commands on the switch and the host computers to find things such as mac addresses and running configurations. We also used the TCP/IP settings on the host computers to set up our ip addresses and default gateways and tested these by checking the outputs using the ipconfig /all. We also used the ping command to check all devices and there connectivity on the network that we setup in the lab. We also used the console ports on the switched to tera term into the switch and configure the switches and view various show commands. Some of the commands that we used where:		:We tested our lab by running various commands on the switch and the host computers to find things such as mac addresses and running configurations. We also used the TCP/IP settings on the host computers to set up our ip addresses and default gateways and tested these by checking the outputs using the ipconfig /all. We also used the ping command to check all devices and there connectivity on the network that we setup in the lab. We also used the console ports on the switched to tera term into the switch and configure the switches and view various show commands. Some of the commands that we used where:
Line 131:		Line 132:


	Description of things learned in the lab:		==Description of things learned in the lab:==

	What we learned in this lab:		What we learned in this lab:
Line 138:		Line 139:
	:How to set up port security on the switch		:How to set up port security on the switch
	:How to assign ports to a vlan		:How to assign ports to a vlan
	:~~'''How~~ to change the port speed and duplex settings~~'''~~		:to change the port speed and duplex settings

	'''Instructor Sign Off__________________________________________________		'''Instructor Sign Off__________________________________________________
	'''		'''

Mart0045 at 14:43, 15 October 2010

2010-10-15T14:43:05Z

← Older revision		Revision as of 14:43, 15 October 2010
Line 138:		Line 138:
	:How to set up port security on the switch		:How to set up port security on the switch
	:How to assign ports to a vlan		:How to assign ports to a vlan
	:How to change the port speed and duplex settings		:'''How to change the port speed and duplex settings'''
	:
	:		'''Instructor Sign Off__________________________________________________
	Instructor Sign Off__________________________________________________		'''

Mart0045 at 14:41, 15 October 2010

2010-10-15T14:41:29Z

← Older revision		Revision as of 14:41, 15 October 2010
Line 77:		Line 77:

	:Step 10: We verified the results of step 9 and found that there was 20 static mac addresses now on the table.		:Step 10: We verified the results of step 9 and found that there was 20 static mac addresses now on the table.

			Task 5:

			:Step 1: We setup PC2 with a ip address and default gateway but we did not connect it to the network yet.

			:Step 2: We pinged the switch from PC1 and we were successful.

			:Step 3: We made sure that the ip addresses where the same as before.

			:Step 4: We found that on the switch the mac address table had 2 dynamic addresses and it matched PC1.

			:Step 5: We viewed the port security options.

			:Step 6: We configured the port security on an access port to 2, sticky, and violation protect.

			:Step 7: We verified the security changes that we made on the switch, we found that on fa0/18 was only allowing 2 addresses and if there were more it would shut the port down.

			:Step 8: We examined the running configuration of the switch and found that the security changes where listed.

			:Step 9: We modified the port security to 1 and violation shutdown.

			:Step 10: We then viewed the results and we found that the running configuration was changed to match the settings we had made.

			:Step 11: We unplugged PC1 and plugged in PC2 and almost right away the port shutdown on the switch.

			:Step 12: We verified this by issuing the show interface fa0/18 command on the switch and found that fa0/18 was down and the line protocol was down as well.

			:Step 13: We then disconnected PC2 and reconnected PC1 and issued the no shutdown command on the port and it came back up.

			:Step 14: We cleaned up.


			Description of problems:

			:In this lab we had only one problem it was because we were using the vmware and it was adding 2 mac addresses with the vm machine and the host machine in the mac address tables, it was a bit confusing. We were unable to fix this problem so we just ignored the host pc mac addresses on the tables. If we would have used labtops from the lab we would have not had this problem but we made it work so we continued with the lab.

			How we tested the lab and what the results were:

			:We tested our lab by running various commands on the switch and the host computers to find things such as mac addresses and running configurations. We also used the TCP/IP settings on the host computers to set up our ip addresses and default gateways and tested these by checking the outputs using the ipconfig /all. We also used the ping command to check all devices and there connectivity on the network that we setup in the lab. We also used the console ports on the switched to tera term into the switch and configure the switches and view various show commands. Some of the commands that we used where:

			:Show run
			:Show mac-address-table
			:Show mac-address-table ?
			:Show interface vlan1
			:Show ip interface vlan1
			:Show version
			:Show interface fa0/18
			:Show vlan
			:Show flash
			:Show start
			:Show interface vlan99
			:Show port-security


			Description of things learned in the lab:

			What we learned in this lab:
			:How to view the mac address table on the switch
			:How to set a static mac address on the mac address table
			:How to set up port security on the switch
			:How to assign ports to a vlan
			:How to change the port speed and duplex settings
			:
			:
			Instructor Sign Off__________________________________________________

← Older revision		Revision as of 14:50, 15 October 2010
Line 11:		Line 11:
	'''Task 1:'''		'''Task 1:'''

	:Step 1: We cabled the network according to the topology so that one computer was connected with an Ethernet cable and a Cross-over cable, and the second pc not currently connected.		:'''Step 1:''' We cabled the network according to the topology so that one computer was connected with an Ethernet cable and a Cross-over cable, and the second pc not currently connected.
	:Step 2: We cleared the configurations on the switch to ensure that no previous configurations on the switch would interfere with our lab.		:'''Step 2:''' We cleared the configurations on the switch to ensure that no previous configurations on the switch would interfere with our lab.


	'''Task 2:'''		'''Task 2:'''

	:Step 1: We entered privileged mode by entering enabled on the switch, and we noticed that the prompt changed from Switch> to Switch#.		:'''Step 1:''' We entered privileged mode by entering enabled on the switch, and we noticed that the prompt changed from Switch> to Switch#.

	:Step 2: We examined the current running configuration by running the show running-config command. We documented how many FastEthernet ports on the switch (24), how many Gigabit Ethernet ports on the switch (2), and the range of values shown for the vty lines (0-15). Then we examined the contents of the NVRAM by running the show startup-config and we found that there was no startup configuration on the switch. Then we examined the characteristics of the virtual interface on vlan1 by running the show interface vlan1 command. We found that there was no ip address for the switch and there was a mac address of 001e.1433.d140 and last the interface was up. Then we issued the show ip interface vlan1 command and we found that the line protocol was down and that the internet protocol processing was disabled.		:'''Step 2:''' We examined the current running configuration by running the show running-config command. We documented how many FastEthernet ports on the switch (24), how many Gigabit Ethernet ports on the switch (2), and the range of values shown for the vty lines (0-15). Then we examined the contents of the NVRAM by running the show startup-config and we found that there was no startup configuration on the switch. Then we examined the characteristics of the virtual interface on vlan1 by running the show interface vlan1 command. We found that there was no ip address for the switch and there was a mac address of 001e.1433.d140 and last the interface was up. Then we issued the show ip interface vlan1 command and we found that the line protocol was down and that the internet protocol processing was disabled.

	:Step 3: We issued the show version command and found the cisco ios version was 12.2, the system image file name was flash:c2960-lanbase-mz.122-35.SE5/ c2960-lanbase-mz.122-35.SE5.bin, and that the base mac address of the switch was 00:1E:14:33:D1:00.		:'''Step 3:''' We issued the show version command and found the cisco ios version was 12.2, the system image file name was flash:c2960-lanbase-mz.122-35.SE5/ c2960-lanbase-mz.122-35.SE5.bin, and that the base mac address of the switch was 00:1E:14:33:D1:00.

	:Step 4: We issued the show interface fastethernet 0/18 and we found that the interface was down and the protocol was down as well. If we plug a cable in we found the the interface would go up. Then we found that the mac address of the interface was 001e.1433.d112, and the speed and duplex setting for the interface were set to auto.		:'''Step 4:''' We issued the show interface fastethernet 0/18 and we found that the interface was down and the protocol was down as well. If we plug a cable in we found the the interface would go up. Then we found that the mac address of the interface was 001e.1433.d112, and the speed and duplex setting for the interface were set to auto.

	:Step5: We issued the show vlan command and found that the name of vlan 1 is default, all ports are in the vlan1, its active, and its type is enet.		:'''Step5:''' We issued the show vlan command and found that the name of vlan 1 is default, all ports are in the vlan1, its active, and its type is enet.

	:Step 6: We examined the contents of the flash memory by issuing the show flash command. We found that there was one file found that was the image file for the switch. Then we issued the dir flash:c2960-lanbase-mz.122-35.SE5 command the name of the cisco iso file was c2960-lanbase-mz.122-35.SE5.bin.		:'''Step 6:''' We examined the contents of the flash memory by issuing the show flash command. We found that there was one file found that was the image file for the switch. Then we issued the dir flash:c2960-lanbase-mz.122-35.SE5 command the name of the cisco iso file was c2960-lanbase-mz.122-35.SE5.bin.

	:Step 7: We issued the show startup-config and again got the message that it was not found because no config had been saved. Then we changed the hostname to S1, and save the config with the copy run start command and now we were able to view the startup config on the switch.		:'''Step 7:''' We issued the show startup-config and again got the message that it was not found because no config had been saved. Then we changed the hostname to S1, and save the config with the copy run start command and now we were able to view the startup config on the switch.

	'''Task 3:'''		'''Task 3:'''

	:Step 1: We gave the switch a hostname.		:'''Step 1:''' We gave the switch a hostname.

	:Step 2: We set the access passwords for the switch to cisco. We found that after setting up a password that it is now required every time for login.		:'''Step 2:''' We set the access passwords for the switch to cisco. We found that after setting up a password that it is now required every time for login.

	:Step 3: We set a password for the privileged EXEC mode to class.		:'''Step 3:''' We set a password for the privileged EXEC mode to class.

	:Step4: We configured the layer 3 address for the switch on interface vlan99 to 172.17.99.11 and issued the no shutdown command, and we noticed that the interface for vlan99 was still down because no ports were assigned to that vlan. Se we then added all the ports to vlan99 and noticed that vlan1 went down and vlan99 went up.		:'''Step4:''' We configured the layer 3 address for the switch on interface vlan99 to 172.17.99.11 and issued the no shutdown command, and we noticed that the interface for vlan99 was still down because no ports were assigned to that vlan. Se we then added all the ports to vlan99 and noticed that vlan1 went down and vlan99 went up.

	:Step 5: We set the default gateway on the switch to 172.17.99.1.		:'''Step 5:''' We set the default gateway on the switch to 172.17.99.1.

	:Step 6: We issued the show interface vlan 99 command to verify the interface settings. We found that the bandwidth was 1000000Kbit, vlan99 was up and the line protocol was up, and that the queuing strategy is fifo.		:'''Step 6:''' We issued the show interface vlan 99 command to verify the interface settings. We found that the bandwidth was 1000000Kbit, vlan99 was up and the line protocol was up, and that the queuing strategy is fifo.

	:Step 7: We configured the PC1 with an ip address and a gateway.		:'''Step 7:''' We configured the PC1 with an ip address and a gateway.

	:Step 8: We pinged from PC1 to the switch and SUCCESS!!!!		:'''Step 8:''' We pinged from PC1 to the switch and SUCCESS!!!!

	:Step 9: We configured the port speed on fastethernet 0/18 to 100 and its duplex to full. Then we issued the show int fa0/18 command to verify the changes.		:'''Step 9:''' We configured the port speed on fastethernet 0/18 to 100 and its duplex to full. Then we issued the show int fa0/18 command to verify the changes.

	:Step 10: We save the configuration to the switch.		:'''Step 10:''' We save the configuration to the switch.

	:Step 11: We issued the show startup-config command to verify our changes.		:'''Step 11:''' We issued the show startup-config command to verify our changes.


	'''Task 4:'''		'''Task 4:'''

	:Step 1: We got the mac addresses for all the the computers PC1 was 000c.2997.b2d6 and PC2 was 0027.0e22.0777.		:'''Step 1:''' We got the mac addresses for all the the computers PC1 was 000c.2997.b2d6 and PC2 was 0027.0e22.0777.

	:Step 2: On the switch we issued the show mac-address-table command and found that there was 4 dynamic addresses and 23 total addresses, and last that the dynamic address matched the PC1 mac address.		:'''Step 2:''' On the switch we issued the show mac-address-table command and found that there was 4 dynamic addresses and 23 total addresses, and last that the dynamic address matched the PC1 mac address.

	:Step 3: We found that there was 13 commands available in the mac address table on the switch, and then we found that we still had 4 dynamic address and that it still matched the PC1 mac address.		:'''Step 3:''' We found that there was 13 commands available in the mac address table on the switch, and then we found that we still had 4 dynamic address and that it still matched the PC1 mac address.

	:Step 4: We cleared the mac address table by issuing the clear mac-address-table dynamic command.		:'''Step 4:''' We cleared the mac address table by issuing the clear mac-address-table dynamic command.

	:Step 5: We found that there were now 20 static addresses and now only 2 dynamic addresses.		:Step 5: We found that there were now 20 static addresses and now only 2 dynamic addresses.