CloudLabBox
Try the free demo

JNCIS-SP lab 13 of 16

High availability from LAG to NSR

Harden a two-router site: bundle links with LACP, detect failures in under a second with BFD, give hosts a gateway that survives with VRRP, and restart routing gracefully. GRES and NSR are configured and read, and the lab says plainly what one Routing Engine can't show.

Run this lab

It needs Standard: its 4 nodes are set to 10 vCPU and 11,776 MB in total.

In your workspace: Shared, then JNCIS-SP JN0-364 guided labs, then 13 - High availability from LAG to NSR

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 10 vCPU and 11,776 MB together. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 100 minutes
Nodes need
10 vCPU, 11,776 MB
Smallest plan
Standard

The scenario

Skerry's Hull site has two routers serving one customer LAN. Each has an uplink to UP, and OSPF runs on the uplinks. A failure should barely be noticed. You'll add a redundant link between the routers, fast failure detection, a redundant gateway for the customer, and protection for the control plane.

DeviceInterfaceAddressNotes
R1ge-0/0/0, ge-0/0/1Members of ae0ae0.0 10.0.12.1/30
R1ge-0/0/210.1.1.2/24Customer LAN
R1ge-0/0/3, lo010.0.13.1/30, 10.255.0.1/32OSPF to UP
R2ge-0/0/0, ge-0/0/1Members of ae0ae0.0 10.0.12.2/30
R2ge-0/0/210.1.1.3/24Customer LAN
R2ge-0/0/3, lo010.0.23.1/30, 10.255.0.2/32OSPF to UP
UPLoopback0198.18.0.1/24The upstream network, in OSPF
H1eth010.1.1.10/24Gateway 10.1.1.1, the virtual address

What you’ll practise

  • Build a LAG with LACP
  • Run BFD for OSPF
  • Configure VRRP with tracking and pre-emption
  • Use graceful restart with a helper
  • Explain GRES, NSR and NSB, and configure them

The tasks

  1. A link aggregation group
  2. BFD
  3. VRRP
  4. Graceful restart
  5. GRES, NSR and NSB: what one Routing Engine can show

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 from LAG to NSR4 nodes and 1 network, 7 links. Every link is listed as text below the diagram.UPR1R2H1LANeth0ge-0/0/2ge-0/0/2ge-0/0/3Gi0/0ge-0/0/3Gi0/1ge-0/0/0ge-0/0/0ge-0/0/1ge-0/0/1
4 nodes and 1 network, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • R1 ge-0/0/0 to R2 ge-0/0/0
  • R1 ge-0/0/1 to R2 ge-0/0/1
  • R1 ge-0/0/2 to LAN (network)
  • R2 ge-0/0/2 to LAN (network)
  • H1 eth0 to LAN (network)
  • R1 ge-0/0/3 to UP Gi0/0
  • R2 ge-0/0/3 to UP Gi0/1
Nodes in High availability from LAG to NSR, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
UPCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R1Juniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
R2Juniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
H1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 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-SP JN0-364 guided labs.

  3. Open 13 - High availability from LAG to NSR 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-SP labs

All JNCIS-SP labs

Related labs in other courses

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