Professional Documents
Culture Documents
Case Study
Case Study
LaSalle Telecom is a company that has several people responsible for designing and implementing the switched infrastructure of the university Campus. Many technicians are involved in the upgrading process. A technician is given the task to complete this design and implementation knowing that the final network has the topology of the exhibit. After deploying the solution, it is important that any documentation explaining the purpose, design, implementation or troubleshooting is recorded for further upgrade.
Case Study
Below are the necessary information related to the implementation of the topology. Addressing Table Device Interface F0/0 F0/0.10 F0/0.20 F0/0.99 S0/0 S0/0 S0/1 Lo0 F0/0 F0/0.10 F0/0.20 F0/0.99 S0/1 VLAN 99 VLAN 99 VLAN 99 NIC NIC NIC NIC IP Address N/A 172.16.10.1 172.16.20.1 172.16.99.1 209.169.100.1 209.169.100.5 209.169.100.2 200.200.200.1 N/A 172.16.10.3 172.16.20.3 172.16.99.3 209.169.100.6 172.16.99.11 172.16.99.12 172.16.99.13 172.16.10.10 172.16.20.20 172.16.10.11 172.16.20.21 Subnet Mask N/A 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.252 255.255.255.252 255.255.255.252 255.255.255.0 N/A 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.252 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 Default Gateway N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A 172.16.99.1 172.16.99.1 172.16.99.1 172.16.10.3 172.16.20.1 172.16.10.3 172.16.20.1
R1
R2
R3
Port Assignments Switch SW1 SW2 SW3 Ports F0/1 - F0/5 F0/11 - F0/15 F0/1 - F0/5 F0/6 - F0/10 F0/1- F0/4 F0/6 - F0/10 F0/11 - F0/15 Assignment 802.1q Trunks (Native VLAN 99) VLAN 20 Marketing 802.1q Trunks (Native VLAN 99) VLAN 10 Sales 802.1q Trunks (Native VLAN 99) VLAN 10 Sales VLAN 20 Marketing Network 172.16.99.0/24 172.16.20.0/24 172.16.99.0/24 172.16.10.0/24 172.16.99.0/24 172.16.10.0/24 172.16.20.0/24
VLANs Information VLAN VLAN 99 (Native) VLAN 10 VLAN 20 VLAN Name Management Sales Marketing
Case Study
Phase 3: Requirements
Switching
configuration
The technician is assigned to create a configuration that meets the following requirements: 1. Basic configuration for all switches. a. Console Password: cisco b. Vty password: cisco c. Enable secret password: class d. Banner MOTD: *************************** This is the <switch_name> CLI. *************************** 5
Case Study
2. The Management VLAN has to be accessible from any other device inside the topology. 3. Virtual Trunking Protocol: a. VTP Domain name: CSCCNA3 b. SW2 is the VTP Server c. SW1 and SW3 are VTP Clients d. VTP Domain Password: csccna3 4. VLAN information is propagated by the VTP server to other switches. 5. Every switch has different ports assigned to VLANs according the table presented in Phase 1. 6. Spanning Tree Protocol: a. Mode: Rapid PVST b. SW1 has a priority of 24576 for VLAN 20 and is the secondary root bridge for VLAN 10 c. SW2 is the primary root bridge for VLAN 10 and has a priority of 28672 for VLAN 20 d. SW3 is the primary root bridge for VLAN 99 e. All ports in access mode transitioning directly to forward state 7. Packets can traverse between VLANs, inter-VLAN Routing. 8. Configure security on ports Fa0/6 and Fa0/11 on S3: a. Port Fa0/6 can learn 2 different MAC addresses b. Port Fa0/6 learns the MAC of PC1 statically and the rest dynamically. If the switch reboots for any reason, the end devices that can be connected have to be the same. c. Port F0/6 drops packets with unknown source addresses until the number of secure MAC addresses drops below the maximum value. d. Port Fa0/11 can learn 3 different MAC addresses. e. Port Fa0/11 learns the MAC of PC2 statically and the rest dynamically. If the switch reboots for any reason, the end devices that can be connected have to be the same. f. Port F0/11 drops packets with unknown source addresses until the number of secure MAC addresses drops below the maximum value and causes the Security Violation counter to increment.
Configuration
Configure IP Addresses of end devices according to the Addressing table presented in Phase 1.
Case Study
Phase 5: Troubleshooting
The technician is assigned to check the connectivity and performance of the network implemented. 1. 2. 3. 4. Ping and Telnet between all devices have to be successful. Packets destined from R1 to 209.169.100.4/30 go through R2 (not the Ethernet LAN). Packets destined from R3 to 209.169.100.0/30 go through R2 (not the Ethernet LAN). If the link between R1 and SW1 fails: a. Is there connectivity between different VLANs? b. Does a VLAN 20 device have connectivity to the outside? And a VLAN 10 device? c. Justify answers and if there are connectivity problems illustrate possible solutions. 5. Check that load balancing is implemented. a. Follow the path of packets for VLAN 20 to Internet and to other devices on the network. b. Follow the path of packets for VLAN 10 to Internet and other devices on the network. 6. Check port security in SW3. The technician provides documentation that specifies how the checking was tested.
Case Study
show vlan show vtp status show spanning-tree show port-security show port-security interface <secured port>
General Documentation:
A complete narrative of the project should be typed using word processing software. Since the scenarios break up the entire task into pieces, take care to address each scenario task so that any layperson could understand that particular task. Microsoft Excel or another spreadsheet program could be used to simply list the equipment and serial numbers. Microsoft Visio or any paint program could be used to draw the network. Provide documentation that specifies how the connectivity was tested.
Technical Documentation:
The technical documentation should include details of the network topology. Visio or any paint program could be used to draw the network. The technical documentation has to include a table or tables with the following details: IP addressing of all interfaces DCE/DTE information Router passwords Banner MOTD Interface descriptions IP addressing and gateway assignments for all PCs Router output from the following commands should be captured and placed into this documentation (for each router): o show cdp neighbors o show ip interface brief o show ip route o show ip protocol o show running-config o show ip ospf neighbors Switch output from the following commands should be captured and placed into this documentation (for each switch): o show cdp neighbors o show ip interface brief 8
Case Study
o o o o o o o
show interfaces trunk show interface vlan <management vlan> show vlan show vtp status show spanning-tree show port-security show port-security interface <secured port>