Multi-vendor troubleshooting lab 1 of 12
OSPF between IOS, Junos, EOS and RouterOS
Four vendors share one OSPF ring, and each link has a different problem: an MTU mismatch, a network-type mismatch, different timers and a mismatched authentication key ID. Read each vendor's symptoms, fix every link and normalise the costs that each vendor picks for itself.
Run this lab
It needs Lite: its 5 nodes are set to 6 vCPU and 7,424 MB in total. That fits the free demo too.
In your workspace: Shared, then Multi-vendor interoperability and troubleshooting guided labs, then 01 - OSPF between IOS Junos EOS and RouterOS
- Level
- Intermediate
- Time
- About 75 minutes
- Nodes need
- 6 vCPU, 7,424 MB
- Smallest plan
- Lite
The scenario
Larkfield Freight has grown by buying two regional hauliers, and its core is now a ring of four vendors: Cisco at Leeds head office, a Juniper SRX at the Hull depot, an Arista switch in the data centre and a MikroTik router at the Goole depot. The links were patched at the weekend and OSPF was enabled everywhere, but the Goole LAN can't reach anything.
Each of the four links has its own problem, and each is the kind that appears only between vendors. Your job is to compare each link with the design standard below and fix the side that breaks it.
| Device | Interface | Address | Connects to |
|---|---|---|---|
| R1 | Gi0/0 | 10.0.12.1/30 | SRX1 ge-0/0/0 (link A) |
| R1 | Gi0/1 | 10.0.41.1/30 | CHR1 ether2 (link D) |
| R1 | Loopback0 | 10.255.0.1/32 | Router ID |
| SRX1 | ge-0/0/0.0 | 10.0.12.2/30 | R1 Gi0/0 (link A) |
| SRX1 | ge-0/0/1.0 | 10.0.23.1/30 | EOS1 Ethernet1 (link B) |
| SRX1 | lo0.0 | 10.255.0.2/32 | Router ID |
| EOS1 | Ethernet1 | 10.0.23.2/30 | SRX1 ge-0/0/1 (link B) |
| EOS1 | Ethernet2 | 10.0.34.1/30 | CHR1 ether1 (link C) |
| EOS1 | Loopback0 | 10.255.0.3/32 | Router ID |
| CHR1 | ether1 | 10.0.34.2/30 | EOS1 Ethernet2 (link C) |
| CHR1 | ether2 | 10.0.41.2/30 | R1 Gi0/1 (link D) |
| CHR1 | ether3 | 10.40.0.1/24 | Goole LAN |
| CHR1 | loopback | 10.255.0.4/32 | Router ID |
| H1 | eth0 | 10.40.0.10/24 | Gateway 10.40.0.1 |
| Design standard | Value |
|---|---|
| Area | 0 (0.0.0.0) on every link |
| Network type | Point-to-point on every ring link |
| Timers | Hello 10 s, dead 40 s, the OSPF default |
| IP MTU | 1500 on every ring link |
| Link D authentication | MD5, key ID 10, key Larkfield-Core1 |
| Cost | 10 on every ring link, in both directions |
What you’ll practise
- Read OSPF neighbour state on Cisco IOS, Junos, Arista EOS and RouterOS
- Recognise an MTU mismatch from a neighbour stuck in ExStart or Exchange
- Find a network-type mismatch that leaves one end at Init and the other end listing nobody
- Find a timer mismatch that hides a neighbour completely
- Match MD5 authentication key IDs across vendors
- Explain why OSPF cost needn't match for an adjacency, and set one cost on all four vendors
The tasks
- Give H1 its address
- Read the symptoms before you touch anything
- Link A, stuck in ExStart
- Link B, Init on one side and nothing on the other
- Link C, no neighbour at all
- Link D, authentication key IDs
- Prove the ring, then normalise cost
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
- R1
Gi0/0to SRX1ge-0/0/0 - SRX1
ge-0/0/1to EOS1Ethernet1 - EOS1
Ethernet2to CHR1ether1 - CHR1
ether2to R1Gi0/1 - CHR1
ether3to H1eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| SRX1 | Juniper vSRX NextGen template | vsrxng-23.4R2-S3.9 | 2 vCPU, 4,096 MB |
| EOS1 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| CHR1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Multi-vendor interoperability and troubleshooting guided labs.Open
01 - OSPF between IOS Junos EOS and RouterOSand 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.