Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Piggybacking (Internet access) wikipedia , lookup
Point-to-Point Protocol over Ethernet wikipedia , lookup
Network tap wikipedia , lookup
Zero-configuration networking wikipedia , lookup
Serial port wikipedia , lookup
Parallel port wikipedia , lookup
IEEE 802.1aq wikipedia , lookup
Cracking of wireless networks wikipedia , lookup
Telephone exchange wikipedia , lookup
ENG653 - WAN & VLAN Solutions Report STUDENT NUMBER – 494308 PARTNER NUMBER – 490645 POD NUMBER - 86 University of Portsmouth Contents Introduction ............................................................................................. Error! Bookmark not defined. Scenarios ................................................................................................................................................. 2 Scenario 1............................................................................................................................................ 2 Scenario 2............................................................................................................................................ 2 Analysis ................................................................................................................................................... 3 Requirements Table ................................................................................................................................ 6 Implementation Table............................................................................................................................. 8 Verification Table .................................................................................................................................. 20 Conclusion ................................................................................................ Error! Bookmark not defined. Bibliography ............................................................................................. Error! Bookmark not defined. Appendix .................................................................................................. Error! Bookmark not defined. Scenarios Scenario 1 Scenario 1 does not meet the customer’s requirements, there are not enough ports on the access switches to support the predicted company growth. Scenario 2 Scenario 2, does meet the customer’s requirement in terms of the network capacity, but it does not offer any redundancy, if the core network fails, then the entire network will go down. Analysis Scenario 3 Scenario 3 is the scenario which we have chosen, it offers capacity for the new small company and the predicted growth, as well as offering the high level of redundancy around the network, if either of the core switches fail, and there is another which is connected to all access switches as well as the servers. The network which we have designed offers a high level of redundancy as well and a much higher level of performance, whilst also ensuring the network has capacity for the additional accountancy practice as well as the predicted 10% growth over the next 3 years. The network consists of two core routers, which branch out to five access layer switches. The core routers have trunked connections to each other as well as the five access switches, this setup provides a high level of performance between the networked switches with the trunked connections providing more performance. The core switches also have direct connections to the servers, while allows for more access ports to the network devices as well as more network redundancy, if either of the core switches fail, the secondary core switch, also has a direct connection to the servers. We have chosen to use the HP ProCurve switches for the core and access layer switches. This is due to the knowledge we have with the hardware as well as the configuration commands. One of the requirements of the network was that there needed to be restricted access to the customer server, to ensure that it is only accessible by the computers of the accounting partners. To ensure this requirement has been met we have put in place VLANs. There are 8 different VLANs on the network one for each user group, one for each of the servers as well as one for the router traffic. The VLANs are shown below; VLAN 10 – Accounting Employees VLAN 20 – Admin Support Employees VLAN 30 – Accounting Partners VLAN 40 – Customer Service Employees VLAN 50 – Meeting Room VLAN 60 – Company Server VLAN 70 – Customer Server The way that this works, will be that we have dedicated ports, for each user group, ports 1-8 on switches 3-6 are assigned to the Accounting Employees, therefore VLAN 10 and VLAN 60, meaning that the Accounting Employees have access to ports 1-8 as well as these users having access to the Company Server. With this network setup, this will ensure that unless the ports are configured to allow VLAN 70 traffic, they will not have access to the Customer Server. This means that ports 13-15 are configured to use VLAN 30, 50 & 70, meaning that the ports allow access to the Accounting Partners, whilst providing access to the Company Server as well as the Customer Server. This meets the requirement that only the Accounting Partners will have access to the Customer Server. We had looked into ACL (Access Control List), but after researching the requirements we found that as our switches do not have IP Routing enabled, the users are currently unable to communicate with other VLANs, meaning that our current VLAN setup provides the perfect restricted access between the users and servers which has been required by the network design. The network which we have configured re-uses all of the existing hardware, with the addition of two new HP ProCurve switches. The requirement that the implementation of the new network must have minimal disruption to the business during the transition phase. To ensure this requirement is being, met we have planned for the implementation of the two new switches to be the core switches, which can be configured at our own office, prior to being implemented, this will save time and ensure minimal disruption to the network. The actual complete implementation process will take place out of hours, primarily over the weekend, the two days over the weekend will allow for the additional 5 access layer switches to be configured. The reason that the configuration process will be so fast is that we actually have all of the commands copied into a word document, modified for each switch, meaning that the entire command list can be copied into a switch CLI and instantly the switch is configured. I will now cover the strengths and weaknesses of the network we have designed. Strengths; - Redundancy - Performance - Scalability - Focused Restriction Weaknesses; - Cost I feel that the requirement of the network to accommodate a new small company as well as a 10% growth, is only going to be met, if the company spend money on the additional switches. The cost could be much worse if we did not plan to use the existing hardware, so as we are using existing hardware and only purchasing two switches, I feel this is the most cost effective way to meet the network requirements. When creating trunked ports, we had to use the following command, which essentially puts the ports 1 and 2, on the device and partners them into a trunk on trk1. The first number in the command is the port number and the second is the trunk group. A trunk is the combination of two ports which act as a single connection, doubling the throughput available on the ports. trunk 1 trk1 trunk 2 trk1 When it comes to configuring VLANs on a network, you begin by entering the VLAN command followed by the VLAN ID you wish to configure. Here we are configuring VLAN 10, after this you then begin tagging the ports, to permit the traffic from the ports, to the VLAN being configured. For example tagging ports 1-8 as shown below will mean that traffic from VLAN 10 is now permitted on ports 1-8. vlan 10 tagged 1-8 tagged trk1-trk2 Requirements Table ID / Name Description Device Status Information Source 1 VLAN 10 is going to be used for the routing of traffic for accounting employees Switch 1 Switch 2 Switch 3 Switch 4 Switch 5 Switch 6 Switch 7 Core Requirements Re-using existing switches and adding in two switches for better management of VLANs, our own design 2 VLAN 20 is going to be used for the routing of traffic for admin support employees Switch 1 Switch 2 Switch 3 Switch 4 Switch 5 Switch 6 Switch 7 Core Requirements Re-using existing switches and adding in two switches for better management of VLANs, our own design 3 VLAN 30 is going to be used for the routing of traffic for accounting partners Switch 1 Switch 2 Switch 3 Switch 4 Switch 5 Switch 6 Switch 7 Core Requirements Re-using existing switches and adding in two switches for better management of VLANs, our own design 4 VLAN 40 is going to be used for the routing of traffic for customer service employees Switch 1 Switch 2 Switch 3 Switch 4 Switch 5 Switch 6 Switch 7 Core Requirements Re-using existing switches and adding in two switches for better management of VLANs, our own design 5 VLAN 50 is going to be used for the routing of traffic for the meeting room Switch 1 Switch 2 Switch 3 Switch 4 Switch 5 Core Requirements Re-using existing switches and adding in two switches for better management of VLANs, our own design 6 VLAN 60 is going to be used for the routing of traffic of employees who need access to the Company server Switch 1 Switch 2 Switch 3 Switch 4 Switch 5 Switch 6 Switch 7 Core Requirements Re-using existing switches and adding in two switches for better management of VLANs, our own design 7 VLAN 70 is going to be used for the routing of traffic of employees who need access to the Customer server Switch 1 Switch 2 Switch 3 Switch 4 Switch 5 Switch 6 Switch 7 Core Requirements Re-using existing switches and adding in two switches for better management of VLANs, our own design 8 An IP address is needed for the interfaces of the router connecting to the network to the internet Router_1 Core Requirements Re-using existing router Implementation Table Step Number Completion Status Device Values & Items to implement 1 100% Switch1 (procurve) conf hostname Switch1 2 100% Switch1 (procurve) vlan 10 name Accounting_Employees 3 100% Switch1 (procurve) vlan 20 name Admin_Support_Employees 4 100% Switch1 (procurve) vlan 30 name Accounting_Partners 5 100% Switch1 (procurve) vlan 40 name Customer_Service_Employees 6 100% Switch1 (procurve) vlan 50 name Meeting_Room 7 100% Switch1 (procurve) vlan 60 name Company_Server 8 100% Switch1 (procurve) vlan 70 name Customer_Server 9 100% Switch1 (procurve) vlan 80 name Core 10 100% Switch1 (procurve) trunk 1 trk1 trunk 2 trk1 trunk 4 trk2 trunk 5 trk3 trunk 6 trk3 trunk 7 trk4 trunk 8 trk4 trunk 9 trk5 trunk 10 trk5 trunk 11 trk6 trunk 12 trk6 trunk 14 trk7 trunk 15 trk7 trunk 16 trk8 trunk 17 trk8 11 100% Switch1 (procurve) vlan 10 tagged trk1-trk6 12 100% Switch1 (procurve) vlan 20 tagged trk1-trk6 13 100% Switch1 (procurve) vlan 30 tagged trk1-trk6 14 100% Switch1 (procurve) vlan 40 tagged trk1-trk6 15 100% Switch1 (procurve) vlan 50 tagged trk1-trk6 16 100% Switch1 (procurve) vlan 60 tagged trk1-trk7 17 100% Switch1 (procurve) vlan 70 tagged trk1-trk6 tagged trk8 18 100% Switch1 (procurve) vlan 10 ip address 192.168.10.1 255.255.255.0 19 100% Switch1 (procurve) vlan 20 ip address 192.168.20.1 255.255.255.0 20 100% Switch1 (procurve) vlan 30 ip address 192.168.30.1 255.255.255.0 21 100% Switch1 (procurve) vlan 40 ip address 192.168.40.1 255.255.255.0 22 100% Switch1 (procurve) vlan 50 ip address 192.168.50.1 255.255.255.0 23 100% Switch1 (procurve) vlan 60 ip address 192.168.60.1 255.255.255.0 24 100% Switch1 (procurve) vlan 70 ip address 192.168.70.1 255.255.255.0 25 100% Switch1 (procurve) vlan 80 ip address 192.168.80.1 255.255.255.0 26 100% Switch2 (procurve) conf hostname Switch2 27 100% Switch2 (procurve) vlan 10 name Accounting_Employees 28 100% Switch2 (procurve) vlan 20 name Admin_Support_Employees 29 100% Switch2 (procurve) vlan 30 name Accounting_Partners 30 100% Switch2 (procurve) vlan 40 name Customer_Service_Employees 31 100% Switch2 (procurve) vlan 50 name Meeting_Room 32 100% Switch2 (procurve) vlan 60 name Company_Server 33 100% Switch2 (procurve) vlan 70 name Customer_Server 34 100% Switch2 (procurve) vlan 80 name Core 35 100% Switch2 (procurve) trunk 1 trk1 trunk 2 trk1 trunk 4 trk2 trunk 5 trk3 trunk 6 trk3 trunk 7 trk4 trunk 8 trk4 trunk 9 trk5 trunk 10 trk5 trunk 11 trk6 trunk 12 trk6 trunk 14 trk7 trunk 15 trk7 trunk 16 trk8 trunk 17 trk8 36 100% Switch2 (procurve) vlan 10 tagged trk1-trk6 37 100% Switch2 (procurve) vlan 20 tagged trk1-trk6 38 100% Switch2 (procurve) vlan 30 tagged trk1-trk6 39 100% Switch2 (procurve) vlan 40 tagged trk1-trk6 40 100% Switch2 (procurve) vlan 50 tagged trk1-trk6 41 100% Switch2 (procurve) vlan 60 tagged trk1-trk7 42 100% Switch2 (procurve) vlan 70 tagged trk1-trk6 tagged trk8 43 100% Switch2 (procurve) vlan 10 ip address 192.168.10.2 255.255.255.0 44 100% Switch2 (procurve) vlan 20 ip address 192.168.20.2 255.255.255.0 45 100% Switch2 (procurve) vlan 30 ip address 192.168.30.2 255.255.255.0 46 100% Switch2 (procurve) vlan 40 ip address 192.168.40.2 255.255.255.0 47 100% Switch2 (procurve) vlan 50 ip address 192.168.50.2 255.255.255.0 48 100% Switch2 (procurve) vlan 60 ip address 192.168.60.2 255.255.255.0 49 100% Switch2 (procurve) vlan 70 ip address 192.168.70.2 255.255.255.0 50 100% Switch2 (procurve) vlan 80 ip address 192.168.80.2 255.255 255.0 51 100% Switch3 (procurve) conf hostname Switch3 52 100% Switch3 (procurve) vlan 10 name Accounting_Employees 53 100% Switch3 (procurve) vlan 20 name Admin_Support_Employees 54 100% Switch3 (procurve) vlan 30 name Accounting_Partners 55 100% Switch3 (procurve) vlan 40 name Customer_Service_Employees 56 100% Switch3 (procurve) vlan 50 name Meeting_Room 57 100% Switch3 (procurve) vlan 60 name Company_Server 58 100% Switch3 (procurve) vlan 70 name Customer_Server 59 100% Switch3 (procurve) trunk 21 trk1 trunk 22 trk1 trunk 23 trk2 trunk 24 trk2 60 100% Switch3 (procurve) vlan 10 tagged 1-8 tagged trk1-trk2 61 100% Switch3 (procurve) vlan 20 tagged 9-12 tagged trk1-trk2 62 100% Switch3 (procurve) vlan 30 tagged 13-15 tagged trk1-trk2 63 100% Switch3 (procurve) vlan 40 tagged 16-17 tagged trk1-trk2 64 100% Switch3 (procurve) vlan 50 tagged 18 tagged trk1-trk2 65 100% Switch3 (procurve) vlan 60 tagged 1-17 tagged trk1-trk2 66 100% Switch3 (procurve) vlan 70 tagged 13-15 tagged trk1-trk2 67 100% Switch3 (procurve) vlan 10 ip address 192.168.10.3 255.255.255.0 68 100% Switch3 (procurve) vlan 20 ip address 192.168.20.3 255.255.255.0 69 100% Switch3 (procurve) vlan 30 ip address 192.168.30.3 255.255.255.0 70 100% Switch3 (procurve) vlan 40 ip address 192.168.40.3 255.255.255.0 71 100% Switch3 (procurve) vlan 50 ip address 192.168.50.3 255.255.255.0 72 100% Switch3 (procurve) vlan 60 ip address 192.168.60.3 255.255.255.0 73 100% Switch3 (procurve) vlan 70 ip address 192.168.70.3 255.255.255.0 74 100% Switch4 (procurve) conf hostname Switch3 75 100% Switch4 (procurve) vlan 10 name Accounting_Employees 76 100% Switch4 (procurve) vlan 20 name Admin_Support_Employees 77 100% Switch4 (procurve) vlan 30 name Accounting_Partners 78 100% Switch4 (procurve) vlan 40 name Customer_Service_Employees 79 100% Switch4 (procurve) vlan 50 name Meeting_Room 80 100% Switch4 (procurve) vlan 60 name Company_Server 81 100% Switch4 (procurve) vlan 70 name Customer_Server 82 100% Switch4 (procurve) trunk 21 trk1 trunk 22 trk1 trunk 23 trk2 trunk 24 trk2 83 100% Switch4 (procurve) vlan 10 tagged 1-8 tagged trk1-trk2 84 100% Switch4 (procurve) vlan 20 tagged 9-12 tagged trk1-trk2 85 100% Switch4 (procurve) vlan 30 tagged 13-15 tagged trk1-trk2 86 100% Switch4 (procurve) vlan 40 tagged 16-17 tagged trk1-trk2 87 100% Switch4 (procurve) vlan 50 tagged 18 tagged trk1-trk2 88 100% Switch4 (procurve) vlan 60 tagged 1-17 tagged trk1-trk2 89 100% Switch4 (procurve) vlan 70 tagged 13-15 tagged trk1-trk2 90 100% Switch4 (procurve) vlan 10 ip address 192.168.10.4 255.255.255.0 91 100% Switch4 (procurve) vlan 20 ip address 192.168.20.4 255.255.255.0 92 100% Switch4 (procurve) vlan 30 ip address 192.168.30.4 255.255.255.0 93 100% Switch4 (procurve) vlan 40 ip address 192.168.40.4 255.255.255.0 94 100% Switch4 (procurve) vlan 50 ip address 192.168.50.4 255.255.255.0 95 100% Switch4 (procurve) vlan 60 ip address 192.168.60.4 255.255.255.0 96 100% Switch4 (procurve) vlan 70 ip address 192.168.70.4 255.255.255.0 97 100% Switch5 (procurve) conf hostname Switch3 98 100% Switch5 (procurve) vlan 10 name Accounting_Employees 99 100% Switch5 (procurve) vlan 20 name Admin_Support_Employees 100 100% Switch5 (procurve) vlan 30 name Accounting_Partners 101 100% Switch5 (procurve) vlan 40 name Customer_Service_Employees 102 100% Switch5 (procurve) vlan 50 name Meeting_Room 103 100% Switch5 (procurve) vlan 60 name Company_Server 104 100% Switch5 (procurve) vlan 70 name Customer_Server 105 100% Switch5 (procurve) trunk 21 trk1 trunk 22 trk1 trunk 23 trk2 trunk 24 trk2 106 100% Switch5 (procurve) vlan 10 tagged 1-8 tagged trk1-trk2 107 100% Switch5 (procurve) vlan 20 tagged 9-12 tagged trk1-trk2 108 100% Switch5 (procurve) vlan 30 tagged 13-15 tagged trk1-trk2 109 100% Switch5 (procurve) vlan 40 tagged 16-17 tagged trk1-trk2 110 100% Switch5 (procurve) vlan 50 tagged 18 tagged trk1-trk2 111 100% Switch5 (procurve) vlan 60 tagged 1-17 tagged trk1-trk2 112 100% Switch5 (procurve) vlan 70 tagged 13-15 tagged trk1-trk2 113 100% Switch5 (procurve) vlan 10 ip address 192.168.10.5 255.255.255.0 114 100% Switch5 (procurve) vlan 20 ip address 192.168.20.5 255.255.255.0 115 100% Switch5 (procurve) vlan 30 ip address 192.168.30.5 255.255.255.0 116 100% Switch5 (procurve) vlan 40 ip address 192.168.40.5 255.255.255.0 117 100% Switch5 (procurve) vlan 50 ip address 192.168.50.5 255.255.255.0 118 100% Switch5 (procurve) vlan 60 ip address 192.168.60.5 255.255.255.0 119 100% Switch5 (procurve) vlan 70 ip address 192.168.70.5 255.255.255.0 120 100% Switch6 (procurve) conf hostname Switch6 121 100% Switch6 (procurve) vlan 10 name Accounting_Employees 122 100% Switch6 (procurve) vlan 20 name Admin_Support_Employees 123 100% Switch6 (procurve) vlan 30 name Accounting_Partners 124 100% Switch6 (procurve) vlan 40 name Customer_Service_Employees 125 100% Switch6 (procurve) vlan 60 name Company_Server 126 100% Switch6 (procurve) vlan 70 name Customer_Server 127 100% Switch6 (procurve) trunk 21 trk1 trunk 22 trk1 trunk 23 trk2 trunk 24 trk2 128 100% Switch6 (procurve) vlan 10 tagged 1-8 tagged trk1-trk2 129 100% Switch6 (procurve) vlan 20 tagged 9-12 tagged trk1-trk2 130 100% Switch6 (procurve) vlan 30 tagged 13-15 tagged trk1-trk2 131 100% Switch6 (procurve) vlan 40 tagged 16-17 tagged trk1-trk2 132 100% Switch6 (procurve) vlan 60 tagged 1-17 tagged trk1-trk2 133 100% Switch6 (procurve) vlan 70 tagged 13-15 tagged trk1-trk2 134 100% Switch6 (procurve) vlan 10 ip address 192.168.10.6 255.255.255.0 135 100% Switch6 (procurve) vlan 20 ip address 192.168.20.6 255.255.255.0 136 100% Switch6 (procurve) vlan 30 ip address 192.168.30.6 255.255.255.0 137 100% Switch6 (procurve) vlan 40 ip address 192.168.40.6 255.255.255.0 138 100% Switch6 (procurve) vlan 60 ip address 192.168.60.6 255.255.255.0 139 100% Switch6 (procurve) vlan 70 ip address 192.168.70.6 255.255.255.0 140 100% Switch7 (procurve) conf hostname Switch7 141 100% Switch7 (procurve) vlan 10 name Accounting_Employees 142 100% Switch7 (procurve) vlan 20 name Admin_Support_Employees 143 100% Switch7 (procurve) vlan 30 name Accounting_Partners 144 100% Switch7 (procurve) vlan 40 name Customer_Service_Employees 145 100% Switch7 (procurve) vlan 60 name Company_Server 146 100% Switch7 (procurve) vlan 70 name Customer_Server 147 100% Switch7 (procurve) trunk 21 trk1 trunk 22 trk1 trunk 23 trk2 trunk 24 trk2 148 100% Switch7 (procurve) vlan 10 tagged 1-9 tagged trk1-trk2 149 100% Switch7 (procurve) vlan 20 tagged 10-14 tagged trk1-trk2 150 100% Switch7 (procurve) vlan 30 tagged 15-18 tagged trk1-trk2 151 100% Switch7 (procurve) vlan 40 tagged 19-20 tagged trk1-trk2 152 100% Switch7 (procurve) vlan 60 tagged 1-20 tagged trk1-trk2 153 100% Switch7 (procurve) vlan 70 tagged 15-18 tagged trk1-trk2 154 100% Switch7 (procurve) vlan 10 ip address 192.168.10.7 255.255.255.0 155 100% Switch7 (procurve) vlan 20 ip address 192.168.20.7 255.255.255.0 156 100% Switch7 (procurve) vlan 30 ip address 192.168.30.7 255.255.255.0 157 100% Switch7 (procurve) vlan 40 ip address 192.168.40.7 255.255.255.0 158 100% Switch7 (procurve) vlan 60 ip address 192.168.60.7 255.255.255.0 159 100% Switch7 (procurve) vlan 70 ip address 192.168.70.7 255.255.255.0 160 100% Router1 (H3C) system-view sysname Router1 161 100% Router1 (H3C) interface ethernet0/0 ip address 192.168.1.1 162 100% Router1 (H3C) interface ethernet0/1 ip address 192.168.2.1 163 100% Router1 (H3C) ip route-static 192.168.1.1 255.255.255.0 192.168.80.1 164 100% Router1 (H3C) ip route-static 192.168.2.1 255.255.255.0 192.168.80.2 Verification Table Completion Status Device Values & Items to Implement Verification Method Yes Switch 1 Ports 1-2 - VLAN 10,20,30,40,50,60,70 Ports 3-4 - VLAN 10,20,30,40,50,60,70 Ports 5-6 - VLAN 10,20,30,40,50,60,70 Ports 7-8 - VLAN 10,20,30,40,50,60,70 Ports 9-10 - VLAN 10,20,30,40,50,60,70 Ports 11-12 - VLAN 10,20,30,40,50,60,70 Port 13 - VLAN 80 (router connection) Port 14-15 - VLAN 60 Port 16-17 - VLAN 70 Run the ‘show run’ command to see all configuration in brief. Run the ‘show vlan’ command to see a list of all VLANs created. Run the ‘show vlan *number*’ command to see specifics of VLAN and which ports are tagged or untagged. Confirm correct ports tagged. Run the ‘show interfaces brief’ command to confirm that all ports have been configured with the correct trunks and the ports that are connected are up. Run the ‘show trunk’ command to confirm correct ports are configured to correct trunks. Run the ‘show lldp info remotedevice’ command to confirm connection to the correct switch on the correct ports. This command confirms that Switch1 is connected to Switch3 on ports 1&2, Switch4 on ports 3&4, Switch5 on ports 5&6, Switch6 on ports 7&8, Switch7 on ports 9&10, Switch2 on ports 11&12 and Router1 on port 13. Run the ‘ping’ command to test connection to connected switches. Also used to test connection to servers. Ping 192.168.10.3 (VLAN 10 on switch3) and 192.168.10.7 (VLAN 10 on switch7) to test connectivity . Yes Switch 2 Ports 1-2 - VLAN 10,20,30,40,50,60,70 Ports 3-4 - VLAN 10,20,30,40,50,60,70 Ports 5-6 - VLAN 10,20,30,40,50,60,70 Ports 7-8 - VLAN 10,20,30,40,50,60,70 Ports 9-10 - VLAN 10,20,30,40,50,60,70 Ports 11-12 - VLAN 10,20,30,40,50,60,70 Port 13 - VLAN 80 (Router connection) Port 14-15 - VLAN 60 Port 16-17 - VLAN 70 Run the ‘show run’ command to see all configuration in brief. Run the ‘show vlan’ command to see a list of all VLANs created Run the ‘show vlan *number*’ command to see specifics of VLAN and which ports are tagged or untagged. Confirm correct ports tagged. Run the ‘show interfaces brief’ command to confirm that all ports have been configured with the correct trunks and the ports that are connected are up. Run the ‘show trunk’ command to confirm correct ports are configured to correct trunks. Run the ‘show lldp info remotedevice’ command to confirm connection to the correct switch on the correct ports. This command confirms that Switch2 is connected to Switch3 on ports 1&2, Switch4 on ports 3&4, Switch5 on ports 5&6, Switch6 on ports 7&8, Switch7 on ports 9&10, Switch2 on ports 11&12 and Router1 on port 13. Run the ‘ping’ command to test connection to connected switches. Also used to test connection to servers. Ping 192.168.10.3 (VLAN 10 on switch3) and 192.168.10.7 (VLAN 10 on switch7) to test connectivity. Yes Switch 3 Ports 1-8 - VLAN 10, VLAN 60 Ports 9-12 - VLAN 20, VLAN 60 Ports 13-15 - VLAN 30, VLAN 60, VLAN 70 Ports 16-17 - VLAN 40, VLAN 60 Ports 18 - VLAN 50 Run the ‘show run’ command to see all configuration in brief. Run the ‘show vlan’ command to see a list of all VLANs created Run the ‘show vlan *number*’ command to see specifics of VLAN and which ports are tagged or Ports 21-22 - VLAN 10,20,30,40,50,60,70 Ports 23-24 - VLAN 10,20,30,40,50,60,70 untagged. Confirm correct ports tagged. Run the ‘show interfaces brief’ command to confirm that all ports have been configured with the correct trunks and the ports that are connected are up. Run the ‘show trunk’ command to confirm correct ports are configured to correct trunks. Run the ‘show lldp info remotedevice’ command to confirm connection to the correct switch on the correct ports. This command confirms that Switch3 is connected to Switch1 on ports 21&22, Switch2 on ports 23&24. Run the ‘ping’ command to test connection to connected switches. Also used to test connection to servers. Ping 192.168.80.1 (VLAN 80 on switch1) and 192.168.80.2 (VLAN 80 on switch2) to test connectivity. Yes Switch 4 Ports 1-8 - VLAN 10, VLAN 60 Ports 9-12 - VLAN 20, VLAN 60 Ports 13-15 - VLAN 30, VLAN 60, VLAN 70 Ports 16-17 - VLAN 40, VLAN 60 Ports 18 - VLAN 50 Ports 21-22 - VLAN 10,20,30,40,50,60,70 Ports 23-24 - VLAN 10,20,30,40,50,60,70 Run the ‘show run’ command to see all configuration in brief. Run the ‘show vlan’ command to see a list of all VLANs created Run the ‘show vlan *number*’ command to see specifics of VLAN and which ports are tagged or untagged. Confirm correct ports tagged. Run the ‘show interfaces brief’ command to confirm that all ports have been configured with the correct trunks and the ports that are connected are up. Run the ‘show trunk’ command to confirm correct ports are configured to correct trunks. Run the ‘show lldp info remotedevice’ command to confirm connection to the correct switch on the correct ports. This command confirms that Switch3 is connected to Switch1 on ports 21&22, Switch2 on ports 23&24. Run the ‘ping’ command to test connection to connected switches. Also used to test connection to servers. Ping 192.168.80.1 (VLAN 80 on switch1) and 192.168.80.2 (VLAN 80 on switch2) to test connectivity. Yes Switch 5 Ports 1-8 - VLAN 10, VLAN 60 Ports 9-12 - VLAN 20, VLAN 60 Ports 13-15 - VLAN 30, VLAN 60, VLAN 70 Ports 16-17 - VLAN 40, VLAN 60 Ports 18 - VLAN 50 Ports 21-22 - VLAN 10,20,30,40,50,60,70 Ports 23-24 - VLAN 10,20,30,40,50,60,70 Run the ‘show run’ command to see all configuration in brief. Run the ‘show vlan’ command to see a list of all VLANs created Run the ‘show vlan *number*’ command to see specifics of VLAN and which ports are tagged or untagged. Confirm correct ports tagged. Run the ‘show interfaces brief’ command to confirm that all ports have been configured with the correct trunks and the ports that are connected are up. Run the ‘show trunk’ command to confirm correct ports are configured to correct trunks. Run the ‘show lldp info remotedevice’ command to confirm connection to the correct switch on the correct ports. This command confirms that Switch3 is connected to Switch1 on ports 21&22, Switch2 on ports 23&24. Run the ‘ping’ command to test connection to connected switches. Also used to test connection to servers. Ping 192.168.80.1 (VLAN 80 on switch1) and 192.168.80.2 (VLAN 80 on switch2) to test connectivity. Yes Switch 6 Ports 1-8 - VLAN 10, VLAN 60 Ports 9-12 - VLAN 20, VLAN 60 Ports 13-15 - VLAN 30, VLAN 60, VLAN 70 Ports 16-17 - VLAN 40, VLAN 60 Ports 21-22 - VLAN 10,20,30,40,50,60,70 Ports 23-24 - VLAN 10,20,30,40,50,60,70 Run the ‘show run’ command to see all configuration in brief. Run the ‘show vlan’ command to see a list of all VLANs created Run the ‘show vlan *number*’ command to see specifics of VLAN and which ports are tagged or untagged. Confirm correct ports tagged. Run the ‘show interfaces brief’ command to confirm that all ports have been configured with the correct trunks and the ports that are connected are up. Run the ‘show trunk’ command to confirm which ports are configured to which trunks. Run the ‘show lldp info remotedevice’ command to confirm connection to the correct switch on the correct ports. This command confirms that Switch3 is connected to Switch1 on ports 21&22, Switch2 on ports 23&24. Run the ‘ping’ command to test connection to connected switches. Also used to test connection to servers. Ping 192.168.80.1 (VLAN 80 on switch1) and 192.168.80.2 (VLAN 80 on switch2) to test connectivity. Yes Switch 7 Ports 1-9 - VLAN 10, VLAN 60 Ports 10-14 - VLAN 20, VLAN 60 Ports 15-18 - VLAN 30, VLAN 60, VLAN 70 Ports 19-20 - VLAN 40, VLAN 60 Ports 21-22 - VLAN 10,20,30,40,50,60,70 Run the ‘show run’ command to see all configuration in brief. Run the ‘show vlan’ command to see a list of all VLANs created Run the ‘show vlan *number*’ command to see specifics of VLAN and which ports are tagged or Ports 23-24 - VLAN 10,20,30,40,50,60,70 untagged. Confirm correct ports tagged. Run the ‘show interfaces brief’ command to confirm that all ports have been configured with the correct trunks and the ports that are connected are up. Run the ‘show trunk’ command to confirm which ports are configured to which trunks. Run the ‘show lldp info remotedevice’ command to confirm connection to the correct switch on the correct ports. This command confirms that Switch3 is connected to Switch1 on ports 21&22, Switch2 on ports 23&24. Run the ‘ping’ command to test connection to connected switches. Also used to test connection to servers. Ping 192.168.80.1 (VLAN 80 on switch1) and 192.168.80.2 (VLAN 80 on switch2) to test connectivity. Yes Router1 IP addresses on ports ethernet0/0 and ethernet 0/1 Configure static routes from eth0/0 to VLAN 80 on switch 1 and eth0/1 to VLAN 80 on switch 2 Run the ‘display interface brief’ command to check interfaces and configured IP addresses. Also confirm if link is up and connected. Run the ‘display lldp neighborinformation brief’ to confirm which port is connected to which device. Confirmed that ethernet0/0 is connected physically to Port 24 on Switch1 and ethernet 0/1 is connected physically to Port 24 on Switch2.