CloudLabBox
Try the free demo

Multi-vendor troubleshooting lab 12 of 12

Capstone with a ten-fault multi-vendor network

The merged Larkfield network has to pass acceptance on Monday. Six vendors stand between a PC and the internet, and ten faults are planted among them, from a bundle at the access layer to NAT at the edge. Find them all, and write up the method for each one.

Run this lab

It needs Standard: its 10 nodes are set to 12 vCPU and 14,336 MB in total.

In your workspace: Shared, then Multi-vendor interoperability and troubleshooting guided labs, then 12 - Capstone with a ten-fault multi-vendor network

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 14,336 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 150 minutes
Nodes need
12 vCPU, 14,336 MB
Smallest plan
Standard

The scenario

Larkfield's integration is finished on paper. The network has to pass acceptance on Monday, and today's dry run failed every test. Exactly ten faults are in the network. None of them is a typing mistake in an address, and each is something you've met earlier in this course.

You're the senior engineer for the day. Nobody is going to give you a step list. Your output is a working network, and a fault log good enough for someone else to follow.

DeviceInterfaceAddressConnects to
EXTeth0203.0.113.1/29The internet test address
FGT1port1 / port2203.0.113.2/29 / 10.0.5.1/30EXT / R1
R1Gi0/210.0.5.2/30FGT1, and the default route for the whole network
R1Gi0/010.0.12.1/30WAN circuit to SRX1
R1Tunnel0169.254.12.1/30IPsec VTI to SRX1, MTU 1400
R1Gi0/110.0.13.1/30EOS1
R1Gi0/310.0.14.1/30CHR1, OSPF MD5 key ID 10, key Larkfield-Core1
R1Loopback010.255.0.1/32DHCP server
SRX1ge-0/0/0.0 / ge-0/0/1.010.0.12.2/30 / 10.2.0.1/24R1 / PC-HULL 10.2.0.10
SRX1st0.0169.254.12.2/30IPsec to R1
EOS1Ethernet410.0.13.2/30R1
EOS1Vlan1010.10.10.2/24VRRP 10 master, priority 150
EOS1Vlan2010.10.20.1/24Gateway for VLAN 20
EOS1Port-Channel1, Ethernet3TrunksSW1 (LACP) and CX1
CHR1vlan10 on ether110.10.10.3/24VRRP 10 backup, priority 100
CHR1ether210.0.14.2/30R1
SW1Po1, Gi0/2, Gi0/3EOS1, H1 eth0 (VLAN 10), CHR1
CX11/1/1, 1/1/2EOS1, H1 eth1 (VLAN 20)
H1eth0 / eth1DHCPA PC in VLAN 10 and in VLAN 20
Design standardValue
OSPFArea 0 on every link between routers; network type point-to-point
VRRPVersion 2, VRID 10, virtual IP 10.10.10.1, 1 second
TrunksVLANs 10 and 20 to every access switch; LACP on the bundle
IPsecIKEv2, AES-256, SHA-256, DH 20; key Larkfield-Hull-27
InternetThe whole of 10.0.0.0/8 reaches it through NAT on FGT1

What you’ll practise

  • Plan a troubleshooting run across a whole network, from an acceptance test
  • Use a consistent method: symptom, hypothesis, test, root cause, fix and proof
  • Choose each vendor's commands to test a hypothesis quickly
  • Work out which faults hide others, and in what order to fix them
  • Record each fault so that someone else could repeat your reasoning

The tasks

  1. Prepare the Linux hosts
  2. The acceptance test
  3. Keep a fault log
  4. Work upwards
  5. Finish the log

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 Capstone with a ten-fault multi-vendor network10 nodes, 12 links. Every link is listed as text below the diagram.FGT1R1SRX1EOS1SW1CX1CHR1H1EXTPC-HULLeth0port1Gi0/1Ethernet4ge-0/0/1eth0Gi0/3ether1Gi0/2eth01/1/2eth1Ethernet1Gi0/0Ethernet2Gi0/1Ethernet31/1/1port2Gi0/2Gi0/0ge-0/0/0Gi0/3ether2
10 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • EXT eth0 to FGT1 port1
  • FGT1 port2 to R1 Gi0/2
  • R1 Gi0/0 to SRX1 ge-0/0/0
  • R1 Gi0/1 to EOS1 Ethernet4
  • R1 Gi0/3 to CHR1 ether2
  • SRX1 ge-0/0/1 to PC-HULL eth0
  • EOS1 Ethernet1 to SW1 Gi0/0
  • EOS1 Ethernet2 to SW1 Gi0/1
  • EOS1 Ethernet3 to CX1 1/1/1
  • SW1 Gi0/3 to CHR1 ether1
  • SW1 Gi0/2 to H1 eth0
  • CX1 1/1/2 to H1 eth1
Nodes in Capstone with a ten-fault multi-vendor network, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
FGT1Fortinet FortiGatefortinet-FGT-v7.0.17.M-build06821 vCPU, 2,048 MB
R1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
SRX1Juniper vSRX NextGen templatevsrxng-23.4R2-S3.92 vCPU, 4,096 MB
EOS1Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
SW1Cisco IOSvL2viosl2-adventerprisek9-m.ssa.high_iron_202009291 vCPU, 768 MB
CX1Aruba AOS-CX virtual switcharubacx-10.142 vCPU, 3,072 MB
CHR1MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
H1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
EXTAlpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
PC-HULLAlpine 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 Multi-vendor interoperability and troubleshooting guided labs.

  3. Open 12 - Capstone with a ten-fault multi-vendor network 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 Multi-vendor troubleshooting labs

All Multi-vendor troubleshooting labs

Related labs in other courses

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