JNCIA-SEC and JNCIS-SEC lab 9 of 16
Chassis cluster build
Turn two vSRX firewalls into a chassis cluster: enable it, renumber your thinking, add node groups, fabric links, redundancy groups and reth interfaces, then read the session copied to the standby node.
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 09 - Chassis cluster build
- Level
- Advanced
- Time
- About 80 minutes
- Nodes need
- 6 vCPU, 10,240 MB
- Smallest plan
- Standard
The scenario
Hartwell's Poole office can't afford to lose its firewall during a refit, so a second SRX has arrived. You'll join the two into a chassis cluster: one logical firewall with two nodes, where traffic moves to the survivor if one fails.
| Device | Interface | Address | Notes |
|---|---|---|---|
| Cluster | reth0.0 | 10.10.10.1/24 | Zone trust |
| Cluster | reth1.0 | 203.0.113.1/24 | Zone untrust |
| LAN-PC | eth0 | 10.10.10.10/24 | Gateway 10.10.10.1 |
| OUT | eth0 | 203.0.113.10/24 | Gateway 203.0.113.1 |
Ports change their names once clustering is on. Keep this table beside you:
| Port in EVE (before clustering) | After clustering, node0 | After clustering, node1 | Used for |
|---|---|---|---|
first data port (ge-0/0/0) | em0 | em0 | Control link |
second (ge-0/0/1) | ge-0/0/0 | ge-7/0/0 | Fabric link |
third (ge-0/0/2) | ge-0/0/1 | ge-7/0/1 | reth0, the office LAN |
fourth (ge-0/0/3) | ge-0/0/2 | ge-7/0/2 | reth1, the internet |
The cabling on the canvas is already done. Both firewalls have only a hostname and a login.
What you’ll practise
- Explain control and fabric links, redundancy groups and reth interfaces
- Enable a chassis cluster and handle the renumbered ports
- Use node groups for node-specific settings
- Configure fabric links, priorities and reth interfaces
- Prove that session state reaches the standby node
The tasks
- What a cluster is
- Enable clustering
- Node-specific settings
- Fabric links
- Redundancy groups and reth interfaces
- Zones and policy, as on one firewall
- Read the cluster
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.
Every link, as text
- SRX-A
ge-0/0/0to SRX-Bge-0/0/0 - SRX-A
ge-0/0/1to SRX-Bge-0/0/1 - SRX-A
ge-0/0/2to LAN (network) - SRX-B
ge-0/0/2to LAN (network) - SRX-A
ge-0/0/3to WAN (network) - SRX-B
ge-0/0/3to WAN (network) - LAN-PC
eth0to LAN (network) - OUT
eth0to WAN (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| SRX-A | Juniper vSRX NextGen template | vsrxng-24.4R1.9 | 2 vCPU, 4,096 MB |
| SRX-B | Juniper vSRX NextGen template | vsrxng-24.4R1.9 | 2 vCPU, 4,096 MB |
| LAN-PC | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| OUT | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
JNCIA-SEC and JNCIS-SEC SRX security guided labs.Open
09 - Chassis cluster buildand 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.