om

Free Lab Friday

l.c
Implementing First Hop
Redundancy Protocols
ba
om
db
vi
da
Free Lab Friday – Implementing First Hop Redundancy protocols (FHRP).

Packet Tracer File: Free Lab Friday – Implementing FHRP.pka

Access Credentials:
User Exec: cisco
Privilege Exec: cisco

om
In the previous exercise, the client devices in the Tyrell Corporation network had DHCP
deployed. DHCP is much more favourable to employee mobility and provides a scalability
solution for the large numbers of clients in the enterprise network. The initial layer 2 Local
VLAN and Trunking configurations unique to each device have been applied and the STP
features have been deployed including load-sharing, rapid spanning-tree and layer 2

l.c
protection features.
You are tasked with configuring First Hop Redundancy Protocol (FHRP) features in this
scenario. Implementing FHRP will provide a resilient gateway solution in the event of either
ba
one of the Distribution Switches having connectivity issues. When you have completed the
tasks, you will be able to Check Results.
1. Enable IP routing on the Distribution Switches 1DSW1 and 1DSW2
2. Uplink interfaces to the Core Switches should be enabled. However, this should be
om

implemented in such a way as to create a finite failure domain for Switch Block 1. All
layer 2 potential failure scenarios must be contained within the Switch Block and not
impact the Core Switches CSW1 and CSW2.
3. Implement the supported Cisco proprietary first hop router protocol on the
Distribution switches to provide a redundant gateway solution for the client PCs in the
db

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.
b. The Layer 3 Active gateway should be configured to run alongside the
vi

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
da

d. The IP address used for the Active and Standby routers should be configured
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
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
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
Important Note for this Lab Scenario: Packet Tracer cannot grade HSRP
configurations using Multilayer Switch interface VLAN configurations. For the
purpose of scoring the lab tasks, there are some basic tasks that will be scored.
However, a grade cannot be given for the FHRP configuration.

l.c
A separate Completed Implementing FHRP.pkt file is provided for comparison
of the completed Lab Scenario and completed configurations and validation steps
are provided in the downloads for your comparisons.
ba
Moreover, it is important to note Packet Tracer has a further issue regarding
FHRP configurations
Packet Tracer behaves like older IOS versions in this scenario. The decrement in
the gateway priority is not cumulative if you do not explicitly define the decrement
om

value in the standby track command. The problem with Packet Tracer here is
that it does not allow you to enter the decrement value, and so when the two
uplinks fail the default decrement values are not added together to initiate the
failover.
db

In modern IOS and vIOS, this is different and the decrement values are added
together. The result would be the primary gateway priority is lowered to below
that of the backup gateway, and the backup gateway begins the forwarding role.
********************************************************************************************
vi
da