om

Free Lab Friday

l.c
Troubleshooting
Enterprise Local Area
ba
Networks
om
db
vi
da
Free Lab Friday – Troubleshooting Enterprise Local Area Networks.

Packet Tracer File: Free Lab Friday – Troubleshooting Enterprise Local Area
Networks.pka
Access Credentials:
User Exec: cisco
Privilege Exec: cisco

om
Tyrell Corporation’s Network had been functioning well since the implementation of the
FHRP. As well as HSRP, DHCP, layer 2 Local VLAN, Trunking configurations unique to
each device have been applied and STP features had been deployed including load-sharing,
rapid spanning-tree and layer 2 protection features.

l.c
Tyrells Network Manage has asked for a training session for their 2nd and 3rd Line support
staff on Troubleshooting their Enterprise Network. You have created a replica of their
production network to date for the training session, but have broken many elements of the
ba
network in order to create the troubleshooting scenarios. When you have completed the
tasks, you will be able to Check Results.
In order to troubleshoot all the elements successfully, you will need to read the previous
network design criteria for each of the elements involving the local VLAN design, STP
om

enhancements, DHCP and FHRP implementations in order to restore the network to its
functioning state. An outline of the previous design requirements is given below.
This scenario is intended to be a summary challenge Lab, involving multiple elements at the
same time. You will need to plan your troubleshooting and you may need to fix different
db

elements of the network design in order to see them function as a single restored network.
Task 1: Troubleshoot Local VLANS
1. Troubleshoot VLANS existing on all switches.
vi

2. The design called for a Local VLAN design on each of the Access Layer Switches
a. ASW1 has VLANS 11 & 31
b. ASW2 has VLANS 12 & 32
da

c. ASW3 has VLANS 13 & 33

d. ASW4 has VLANS 14 & 34

Task 2: troubleshoot STP enhancements

1. Ensure that the Distribution Switches are the root of the Layer 2 networks
a. DSW1 should be the Root Bridge for VLANs 1,11-14 and 99, while DSW2
provides the backup Root Bridge for these VLANs
b. DSW2 should be the Root Bridge for VLANs 31-34, while DSW1 provides the
backup Root Bridge for these VLANs
c. The Root Bridges priority should be 8192 lower than the default, while the
Backup Root Bridge priority should be 4096 lower than the default
 2. A convergence event should be contained within the 1-2 second timeframe

Task 3: Troubleshoot IOS DHCP

1. DSW1 and DSW2 should be the trusted DHCP servers for the access VLANS in the
Tyrell network.
2. DSW1 and DSW2 should be configured to provide dynamic IP addresses for the
access VLANS with client allocated addresses from the 10.1.X.0 /24 space, where
the X represents the access vlan.
3. Each DHCP scope should have the following:
a. Default-gateway: 10.1.X.254
b. DNS-Server: 10.1.X.254

om
c. Domain-name TYRELL-CORP
4. When configured correctly, Access VLAN PC’s will be able to ping 1DSW1 and
1DSW2 VLAN interface IP addressing. PC’s should not be able to ping out with their
assigned VLAN.
5. Troubleshoot why PC11, PC32, PC13 and PC34 are not able to ping 1DSW and

l.c
1DSW2
Task 4: Troubleshoot FHRP.
1. Implement the supported Cisco proprietary first hop router protocol on the
ba
Distribution switches to provide a redundant gateway solution for the client PCs in the
access VLANS. The solution should achieve the following:
a. The single active gateway that responds to the ARP requests and forwards
the traffic for each VLAN must follow the layer 2 STP topology.
om

b. The Layer 3 Active gateway should be configured to run alongside the

preferred layer 2 STP Root Bridge for each access VLAN
c. The Layer 3 Standby gateway should be configured to run alongside the
preferred Layer 2 STP Backup Root Bridge for each access VLAN
d. The IP address used for the Active and Standby routers should be configured
db

to match the settings in the recently configured DHCP pools for each access
VLAN.
e. The active forwarding gateway for each access VLAN should be configured
with a priority 10 higher than the default FHRP priority. The standby gateway
vi

should not have their priorities altered.

f. In the event that any Standby gateway loses communication with the Active
gateway due to an outage in the VLAN, the Standby gateway should move to
da

the Active state as quickly as possible.

g. After any outage is restored within the VLAN, the higher priority gateway
should regain the Active status and forwarding should be returned through the
preferred gateway according to the design criteria.
h. The design also calls for each preferred Active gateway in the VLAN to
monitor the Gigabit uplinks to the core switches. In the event of a failure of the
first uplink the priority of the switch to be reduced by a default value. In the
event of a further failure of the second uplink, the priority of the active
gateway should fall to below that of the backup gateway. With both uplinks
failed, the redundant gateway should immediately take control and begin
forwarding in the group.
i. When only one of the uplinks to the Core Switches is restored, the Backup
Gateway should retain forwarding the traffic for each affected VLAN. Not until
 both uplinks to the core are restored should the preferred gateway regain the
Active status and forward the traffic for the VLANS.

om
l.c
ba
om
db
vi
da