CloudLabBox
Try the free demo

JNCIS-ENT lab 15 of 17

High availability with VRRP and BFD

Give a user LAN a gateway that survives a router or uplink failure with VRRP and interface tracking, cut OSPF failure detection from 40 seconds to under a second with BFD, and enable graceful restart. Along the way you learn what GRES, NSR, NSB and unified ISSU add on dual routing engine systems.

Run this lab

It needs Standard: its 3 nodes are set to 12 vCPU and 15,360 MB in total.

In your workspace: Shared, then JNCIS-ENT JN0-352 guided labs, then 15 - High availability with VRRP and BFD

Run it on Standard from £5 a day

The free demo can’t run it: it has 6 vCPU and 8 GB, and this lab’s nodes need 12 vCPU and 15,360 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 75 minutes
Nodes need
12 vCPU, 15,360 MB
Smallest plan
Standard

The scenario

Ashby Freight's user LAN (10.50.0.0/24) has two gateway routers, GW1 and GW2, both with OSPF uplinks to CORE, where the servers live (10.60.0.0/24). Today the PCs point at GW1's own address, so when GW1 fails, every PC loses its gateway. You will make the gateway highly available, speed up failure detection, and make planned routing restarts invisible to the network.

RequirementDetail
Virtual gatewayVRRP group 1, address 10.50.0.1. GW1 is master (priority 200, pre-empts); GW2 is backup (priority 100)
Uplink trackingIf GW1's uplink fails, GW2 must become master
Failure detectionOSPF neighbours must detect a failure in under a second
RestartsRouting restarts must not disturb forwarding

The test PC is the routing instance PC on CORE, on the user LAN with address 10.50.0.100 and a default route to 10.50.0.1. Run its tests on CORE with routing-instance PC.

What you’ll practise

  • Configure VRRP with priorities, pre-emption, accept-data and interface tracking, and verify fail-over
  • Configure BFD for OSPF and compare failure detection with and without it
  • Configure graceful restart and explain the restarting and helper roles
  • Explain GRES, NSR, NSB and unified ISSU, and when each applies
  • Troubleshoot high-availability features with show vrrp, show bfd session and the logs

The tasks

  1. VRRP
  2. Track the uplink
  3. BFD
  4. Graceful restart and its relatives

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 High availability with VRRP and BFD3 nodes and 2 networks, 6 links. Every link is listed as text below the diagram.GW1GW2COREUser-LANServer-LANge-0/0/2ge-0/0/2ge-0/0/3ge-0/0/0ge-0/0/0ge-0/0/0ge-0/0/1ge-0/0/2
3 nodes and 2 networks, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • GW1 ge-0/0/0 to CORE ge-0/0/0
  • GW2 ge-0/0/0 to CORE ge-0/0/1
  • GW1 ge-0/0/2 to User-LAN (network)
  • GW2 ge-0/0/2 to User-LAN (network)
  • CORE ge-0/0/2 to User-LAN (network)
  • CORE ge-0/0/3 to Server-LAN (network)
Nodes in High availability with VRRP and BFD, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
GW1Juniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
GW2Juniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
COREJuniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 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 JNCIS-ENT JN0-352 guided labs.

  3. Open 15 - High availability with VRRP and BFD 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 JNCIS-ENT labs

All JNCIS-ENT labs

Related labs in other courses

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