zNetLaB › Guided labs › Enterprise
Junos and IOS — two vendors, one OSPF area
Enterprise Intermediate 4 devices 5 checked tasks 100 points Plan lab
Configure a Juniper MX with set/commit and a Cisco ISR with the IOS CLI, bring up OSPF between them, and pass traffic end to end. Nothing on the Juniper side takes effect until you commit — try "show | compare" before you do. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
Configure a Juniper MX with set/commit and a Cisco ISR with the IOS CLI, bring up OSPF between them, and pass traffic end to end. Nothing on the Juniper side takes effect until you commit — try "show | compare" before you do.
Your role: a network engineer on the enterprise team. Level: Intermediate Done when: all 5 goals show as passed (100 points).
Network status
Devices: 2 PCs, 2 routers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. PC1 is a host with 10.60.1.10/24, gateway 10.60.1.1. PC2 is a host with 10.60.2.10/24, gateway 10.60.2.1. JunosR, CiscoR start with an empty configuration. Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure. Goals
The Juniper LAN and WAN interfaces are addressed and committed (20 pts) Nothing is left uncommitted on the Juniper (10 pts) The Cisco side is addressed (15 pts) OSPF adjacency forms across the vendor boundary (30 pts) PC1 reaches PC2 (25 pts) The activity, in order
The Juniper LAN and WAN interfaces are addressed and committed Why: A router interface routes nothing until it has an address and is up. Every other task builds on this one. Verify with: show ip interface brief Nothing is left uncommitted on the Juniper Why: Each goal is a state the lab can check on the running device. Verify with: show running-config The Cisco side is addressed Why: A router interface routes nothing until it has an address and is up. Every other task builds on this one. Verify with: show ip interface brief OSPF adjacency forms across the vendor boundary Why: OSPF routes only flow over a FULL adjacency. If a neighbour is stuck in INIT or EXSTART, compare the two ends’ settings. Verify with: show ip ospf neighbor PC1 reaches PC2 Why: A ping needs a route in BOTH directions. This is the end-to-end proof that everything before it worked. Verify with: ping 10.60.2.10 Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong. Why this matters
Configure a Juniper MX with set/commit and a Cisco ISR with the IOS CLI, bring up OSPF between them, and pass traffic end to end. Nothing on the Juniper side takes effect until you commit — try "show | compare" before you do.
What you will be able to do
The Juniper LAN and WAN interfaces are addressed and committed
Nothing is left uncommitted on the Juniper
The Cisco side is addressed
OSPF adjacency forms across the vendor boundary
The network
PC, vMX, ISR 4331 — 4 devices in all, already cabled.
Fa0 ge-0/0/0 ge-0/0/1 Gi0/0/1 Gi0/0/0 Fa0 PC1 10.60.1.10/24 · gw 10.60.1.1 JunosR CiscoR PC2 10.60.2.10/24 · gw 10.60.2.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
PC1 PC 10.60.1.10 / 255.255.255.0 gw 10.60.1.1 JunosR vMX configure it CiscoR ISR 4331 configure it PC2 PC 10.60.2.10 / 255.255.255.0 gw 10.60.2.1
Cabling
PC1 Fa0 ↔ JunosR ge-0/0/0 JunosR ge-0/0/1 ↔ CiscoR Gi0/0/1 CiscoR Gi0/0/0 ↔ PC2 Fa0
What is configured at the start
Nothing is configured to start with beyond the addresses above: you build the configuration from a clean start.
Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 The Juniper LAN and WAN interfaces are addressed and committed 20 On JunosR: show ip interface brief — ge-0/0/0 has 10.60.1.1 and is up/up. and On JunosR: show ip interface brief — ge-0/0/1 has 10.60.12.1 and is up/up. 2 Nothing is left uncommitted on the Juniper 10 Checked automatically against the device’s live state (committed). 3 The Cisco side is addressed 15 On CiscoR: show ip interface brief — Gi0/0/0 has 10.60.2.1 and is up/up. and On CiscoR: show ip interface brief — Gi0/0/1 has 10.60.12.2 and is up/up. 4 OSPF adjacency forms across the vendor boundary 30 On JunosR: show ip ospf neighbor shows at least 1 neighbour(s) in FULL. and On CiscoR: show ip ospf neighbor shows at least 1 neighbour(s) in FULL. 5 PC1 reaches PC2 25 On PC1: ping 10.60.2.10 must succeed.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
JunosR configure
set system host-name JunosR
set interfaces ge-0/0/0 unit 0 family inet address 10.60.1.1/24
set interfaces ge-0/0/1 unit 0 family inet address 10.60.12.1/30
set routing-options router-id 1.1.1.1
set protocols ospf area 0.0.0.0 interface ge-0/0/0 passive
set protocols ospf area 0.0.0.0 interface ge-0/0/1
commit
exit CiscoR interface g0/0/0
ip address 10.60.2.1 255.255.255.0
no shutdown
exit
interface g0/0/1
ip address 10.60.12.2 255.255.255.252
no shutdown
exit
router ospf 1
router-id 2.2.2.2
network 10.60.2.0 0.0.0.255 area 0
network 10.60.12.0 0.0.0.3 area 0 Related labs
Where to start
The lessons all guided labs plans
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.