CloudLabBox
Try the free demo

Cisco NX-OS data centre lab 5 of 15

HSRP and VRRP gateways

Give a server VLAN a gateway that survives failure. A Nexus switch and an IOSv router share HSRP for one virtual address and VRRP for another, and object tracking moves the gateway when the uplink fails.

Run this lab

It needs Lite: its 4 nodes are set to 5 vCPU and 7,680 MB in total. That fits the free demo too.

In your workspace: Shared, then Cisco Nexus NX-OS data centre guided labs, then 05 - HSRP and VRRP gateways

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 50 minutes
Nodes need
5 vCPU, 7,680 MB
Smallest plan
Lite

The scenario

Tenants in hall 3 complain that a single gateway is a single point of failure. VLAN 10 now reaches both N1 (its SVI is 10.10.10.2) and R1 (10.10.10.3), and both have a path to the core router R2. Servers will use the virtual address 10.10.10.1, run by HSRP. The tenant's new load balancer can only join an open standard, so a second virtual address, 10.10.10.254, runs VRRP. R1's half of both groups is ready.

ItemValue
HSRP group 10, version 2Virtual IP 10.10.10.1. N1 priority 110, R1 priority 100. Both preempt.
VRRP group 20Virtual IP 10.10.10.254. N1 priority 110, R1 priority 100.
Track object 1N1's uplink Ethernet1/2. Lower the HSRP priority by 20 when it fails.
H110.10.10.11/24, gateway 10.10.10.1
LoopbacksN1 10.255.0.1, R1 10.255.0.11, R2 10.255.0.12

OSPF is already running between all three, with VLAN 10 passive. Ports Ethernet1/1 and Ethernet1/5 on N1 are access ports in VLAN 10.

What you’ll practise

  • Configure HSRP version 2 on an SVI with priority and preemption
  • Track an uplink so the active gateway moves when it fails
  • Configure VRRP on the same SVI and read its state
  • Identify each protocol's virtual MAC address from a host
  • Prove a failover by following the traffic path

The tasks

  1. Start the lab
  2. HSRP version 2
  3. Track the uplink
  4. VRRP on the same SVI
  5. Use the second gateway

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of HSRP and VRRP gateways4 nodes, 4 links. Every link is listed as text below the diagram.N1R1R2H1e5eth0e2Gi0/0Gi0/1Gi0/1e1Gi0/0
4 nodes, with the interface names each link uses.
Every link, as text
  • N1 e1 to R1 Gi0/0
  • N1 e2 to R2 Gi0/0
  • R1 Gi0/1 to R2 Gi0/1
  • N1 e5 to H1 eth0
Nodes in HSRP and VRRP gateways, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
N1Cisco Nexus 9000vnxosv9k-9300v-9.3.102 vCPU, 6,144 MB
R1Cisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 512 MB
R2Cisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 512 MB
H1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder Cisco Nexus NX-OS data centre guided labs.

  3. Open 05 - HSRP and VRRP gateways and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More Cisco NX-OS data centre labs

All Cisco NX-OS data centre labs

Related labs in other courses

CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.