Week 12 Lab - PT - Troubleshoot Enterprise Networks-1 (1) (1) (1)
.doc
keyboard_arrow_up
School
New Jersey Institute Of Technology *
*We aren’t endorsed by this school
Course
420
Subject
Information Systems
Date
May 1, 2024
Type
doc
Pages
8
Uploaded by MajorCrownFly51 on coursehero.com
2017 - 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public
Page 1 of
8
www.netacad.com
Packet Tracer - Troubleshoot Enterprise Network
Objectives
Part 1: Verify Switching Technologies Part 2: Verify DHCP
Part 3: Verify Routing
Part 4: Verify WAN Technologies Part 5: Verify Connectivity
Scenario
This activity uses a variety of technologies that you have encountered during your CCNA studies, including IPv4 routing, IPv6 routing, port security, EtherChannel, DHCP, and NAT. Your task is to review the requirements, isolate and resolve any problems, and then document the steps you took to verify the requirements.
The company replaced routers R1 and R3 to accommodate a fiber connection between the locations. Configurations from the previous routers with serial connections were modified and applied as a starting configuration. IPv6 is being tested on a small portion of the network and needs to be verified.
Note: Passwords have been removed for ease of troubleshooting in this exercise. The typical password protections should be reapplied; however, the activity will not grade those items.
Addressing Table
Device
Interface
IP Address / Prefix
Default Gateway
R1
G0/0/1
192.168.10.1 /24
N/A
S0/1/0
10.1.1.1 /30
N/A
G0/0/0
10.3.3.1 /30
N/A
R2
G0/0
209.165.200.225 /27
N/A
2001:db8:b:209::1/64
G0/1
192.168.20.1 /30
N/A
2001:db8:b:20::1/64
S0/0/0
10.1.1.2 /30
N/A
G0/1/0
10.2.2.1 /30
N/A
2001:db8:b:10:2::1/64
R3
G0/1.30
192.168.30.1 /24
N/A
G0/1.40
192.168.40.1 /24
N/A
G0/1.50
192.168.50.1 /24
N/A
2001:db8:b:50::1/64
Packet Tracer - Troubleshoot Enterprise Network
2017 - 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public
Page 2 of
8
www.netacad.com
Device
Interface
IP Address / Prefix
Default Gateway
G0/1.99
N/A
N/A
G0/1/0
10.3.3.2 /30
N/A
G0/2/0
10.2.2.2 /30
N/A
2001:db8:b:10:2::2/64
S1
VLAN10
192.168.10.2 /24
192.168.10.1
S2
VLAN11
192.168.99.2 /24
N/A
S3
VLAN30
192.168.99.3 /24
N/A
S4
VLAN30
192.168.99.4 /24
N/A
PC1
NIC
IPv4 DHCP assigned
IPv4 DHCP assigned
PC2
NIC
IPv4 DHCP assigned
IPv4 DHCP assigned
PC3
NIC
IPv4 DHCP assigned
IPv4 DHCP assigned
PC4
NIC
IPv4 DHCP assigned
IPv4 DHCP assigned
2001:db8:b:50::10/64
fe80::3
TFTP Server
NIC
192.168.20.254 /24
192.168.20.1
2001:db8:b:20::254/64
fe80::2
Instructions
Part 1: Verify Switching Technologies
a.
Port security is configured to only allow PC1 to access S1's F0/3 interface. All violations should disable the interface.
Issue the command on S1 to display the current port security status.
S1# show port-security
b.
Enter interface configuration mode for interface F0/3 and set up port security.
S1(config-if)# switchport port-security
S1(config-if)# switchport port-security mac-address sticky
c.
Devices in the LAN on S1 should be in VLAN 10. Display the current state of VLAN configuration.
1)
What ports are currently assigned to VLAN 10?
F0/3, F0/4
d.
PC1 should be receiving an IP address from the router R1.
2)
Does the PC currently have an IP address assigned?
no
Packet Tracer - Troubleshoot Enterprise Network
2017 - 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public
Page 3 of
8
www.netacad.com
e.
Notice the G0/1 interface on R1 is not in the same VLAN as PC1. Change the G0/1 interface to be a member of VLAN 10 and set portfast on the interface.
S1(config-if)# int G0/1
S1(config-if)# switchport access vlan 10
S1(config-if)# spanning-tree portfast
f.
Reset the interface address on PC1 from the GUI or by using the command prompt and the ipconfig
/renew command. Does PC1 have an address? If not, recheck your steps. Test connectivity to the TFTP Server. The ping should be successful.
g.
The LAN connected to R3 had an additional switch added to the topology. Link aggregation using EtherChannel is configured on S2
, S3
, and S4
.
EtherChannel
(aka NIC Teaming, Channel Bonding) is a crucial technology within network infrastructure that allows for the bundling of multiple physical Ethernet links into a single logical link
. o
This aggregation
enhances not only the bandwidth available between two network devices, such as switches, routers, or servers, but also provides redundancy and load balancing. o
By packaging several connections as one, EtherChannel ensures that if one physical link fails, the data can seamlessly transition to the remaining links, minimizing any potential disruption in network communication and improving overall reliability and performance
.
h.
The EtherChannel links should be set to trunk. The EtherChannel links should be set to form a channel without using a negotiation protocol. Issue the command on each switch to determine if the
channel is working correctly.
S2# show etherchannel summary
<output omitted>
1
Po1(SU)
-
Fa0/1(P) Fa0/2(P)
2
Po2(SU)
-
Fa0/3(P) Fa0/4(P)
3)
Were there any problems with EtherChannel?
S3 shows Po1 as down
i.
Modify S3 to include ports F0/1 and F0/2 as port channel 1.
S3(config)# interface range f0/1-2
S3(config-if-range)# channel-group 1 mode on
Check the status of the EtherChannel on S3. It should be stable now. If it is not, check the previous steps.
j.
Verify the trunk status on all switches.
S3# show int trunk
4)
Were there any issues with trunking?
S2 is using VLAN 1 as the Native VLAN on the link G0/1
Correct the trunk issues on S2.
S2(config)# int g0/1
S2(config-if)# switchport trunk native vlan 99
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help