CloudLabBox
Try the free demo

JNCIA-SEC and JNCIS-SEC lab 10 of 16

Cluster failover and troubleshooting

Load a contractor's cluster configuration, find its four faults against the design, then prove failover by hand, by a failed link, and with a download running across it.

Run this lab

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

In your workspace: Shared, then JNCIA-SEC and JNCIS-SEC SRX security guided labs, then 10 - Cluster failover and troubleshooting

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

Level
Advanced
Time
About 90 minutes
Nodes need
6 vCPU, 10,240 MB
Smallest plan
Standard

The scenario

A contractor set up Hartwell's cluster and left a handover file. The first time the office LAN switch port failed, nothing moved, and there's a doubt about the fabric too. You'll load his configuration as it stands, find what's wrong against the design, and then prove failover properly: by hand, by a failed link, and with a download running through it.

DeviceInterfaceAddressNotes
Clusterreth0.010.10.10.1/24Zone trust
Clusterreth1.0203.0.113.1/24Zone untrust
LAN-PCeth010.10.10.10/24Gateway 10.10.10.1
OUTeth0203.0.113.10/24Gateway 203.0.113.1
Port in EVE (before clustering)After clustering, node0After clustering, node1Used for
first data port (ge-0/0/0)em0em0Control link
second (ge-0/0/1)ge-0/0/0ge-7/0/0Fabric link
third (ge-0/0/2)ge-0/0/1ge-7/0/1reth0, the office LAN
fourth (ge-0/0/3)ge-0/0/2ge-7/0/2reth1, the internet
DesignValue
Normal primary for RG0 and RG1node 0 (priority 100, node 1 is 50)
RG1 returns to node 0 by itselfYes (preempt)
A failed monitored linkMoves RG1 straight away
reth0 and reth1A member on each node

What you’ll practise

  • Troubleshoot a cluster from control link upwards
  • Use priorities, preempt and manual failover
  • Set interface-monitor weights that really move a group
  • Read cluster history
  • Prove that a live session survives a failover

The tasks

  1. Form the cluster and load the handover file
  2. Find the faults
  3. Manual failover
  4. A failed link
  5. Failover with a connection running

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 Cluster failover and troubleshooting4 nodes and 2 networks, 8 links. Every link is listed as text below the diagram.SRX-ASRX-BLAN-PCOUTLANWANeth0ge-0/0/3ge-0/0/3eth0ge-0/0/2ge-0/0/2ge-0/0/0ge-0/0/0ge-0/0/1ge-0/0/1
4 nodes and 2 networks, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • SRX-A ge-0/0/0 to SRX-B ge-0/0/0
  • SRX-A ge-0/0/1 to SRX-B ge-0/0/1
  • SRX-A ge-0/0/2 to LAN (network)
  • SRX-B ge-0/0/2 to LAN (network)
  • SRX-A ge-0/0/3 to WAN (network)
  • SRX-B ge-0/0/3 to WAN (network)
  • LAN-PC eth0 to LAN (network)
  • OUT eth0 to WAN (network)
Nodes in Cluster failover and troubleshooting, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
SRX-AJuniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
SRX-BJuniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
LAN-PCEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
OUTEVE-NG GUI server (Docker)eve-gui-server:latest1 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 JNCIA-SEC and JNCIS-SEC SRX security guided labs.

  3. Open 10 - Cluster failover and troubleshooting 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 JNCIA-SEC and JNCIS-SEC labs

All JNCIA-SEC and JNCIS-SEC 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.