zNetLaB › Guided labs › Enterprise
Five vendors, one path — ASA, Arista, Nexus, FRR and Junos
Enterprise Advanced 7 devices 6 checked tasks 110 points Plan lab
An inside PC behind an ASA, then an Arista, a Nexus, an FRR box and a Juniper in a line to a server LAN. Each speaks its own CLI and each has its own catch: nameif and NAT on the ASA, "ip routing" on the Arista, "feature ospf" on the Nexus, vtysh on FRR and a commit on Junos. Get a ping from one end to the other. 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
An inside PC behind an ASA, then an Arista, a Nexus, an FRR box and a Juniper in a line to a server LAN. Each speaks its own CLI and each has its own catch: nameif and NAT on the ASA, "ip routing" on the Arista, "feature ospf" on the Nexus, vtysh on FRR and a commit on Junos. Get a ping from one end to the other.
Your role: a network engineer on the enterprise team. Level: Advanced Done when: all 6 goals show as passed (110 points).
Network status
Devices: 1 PC, 1 firewall, 3 routers, 1 switch, 1 server, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. Inside-PC is a host with 192.168.1.10/24, gateway 192.168.1.1. ASA starts with addresses (G1/1 192.168.1.1/24, G1/2 10.0.1.1/30). Server is a host with 172.16.2.10/24, gateway 172.16.2.1. R-Arista, N9K, R-FRR, R-Juniper 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 ASA’s interfaces are named inside (100) and outside (0) (20 pts) The Arista routes (ip routing is on) (15 pts) The Nexus has OSPF enabled as a feature and two neighbours (20 pts) The Juniper filters telnet on its server-facing input (15 pts) The FRR box learns the server LAN from the Juniper (15 pts) The inside PC reaches the server through all five (25 pts) The activity, in order
The ASA’s interfaces are named inside (100) and outside (0) Why: Each goal is a state the lab can check on the running device. Verify with: show running-config The Arista routes (ip routing is on) Why: Without it the device only switches and never routes between subnets. Verify with: show running-config | include ip routing The Nexus has OSPF enabled as a feature and two neighbours Why: Each goal is a state the lab can check on the running device. Verify with: show running-config The Juniper filters telnet on its server-facing input Why: Each goal is a state the lab can check on the running device. Verify with: show running-config The FRR box learns the server LAN from the Juniper Why: If the prefix is not in the routing table, the router drops packets for it, whatever else is configured. Verify with: show ip route The inside PC reaches the server through all five Why: A ping needs a route in BOTH directions. This is the end-to-end proof that everything before it worked. Verify with: ping 172.16.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
An inside PC behind an ASA, then an Arista, a Nexus, an FRR box and a Juniper in a line to a server LAN. Each speaks its own CLI and each has its own catch: nameif and NAT on the ASA, "ip routing" on the Arista, "feature ospf" on the Nexus, vtysh on FRR and a commit on Junos. Get a ping from one end to the other.
What you will be able to do
The ASA’s interfaces are named inside (100) and outside (0)
The Arista routes (ip routing is on)
The Nexus has OSPF enabled as a feature and two neighbours
The Juniper filters telnet on its server-facing input
The network
PC, ASA 5506-X, Arista vEOS Router, Nexus 9300, FRRouting, vMX, Server — 7 devices in all, already cabled.
Fa0 Gi1/1 192.168.1.1/24 Gi1/2 10.0.1.1/30 Eth1 Eth2 Eth1/1 Eth1/2 eth0 eth1 ge-0/0/0 ge-0/0/1 Fa0 Inside-PC 192.168.1.10/24 · gw 192.168.1.1 ASA R-Arista N9K R-FRR R-Juniper Server 172.16.2.10/24 · gw 172.16.2.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
Inside-PC PC 192.168.1.10 / 255.255.255.0 gw 192.168.1.1 ASA ASA 5506-X configure it R-Arista Arista vEOS Router configure it N9K Nexus 9300 configure it R-FRR FRRouting configure it R-Juniper vMX configure it Server Server 172.16.2.10 / 255.255.255.0 gw 172.16.2.1
Cabling
Inside-PC Fa0 ↔ ASA Gi1/1 ASA Gi1/2 ↔ R-Arista Ethernet1 R-Arista Ethernet2 ↔ N9K Ethernet1/1 N9K Ethernet1/2 ↔ R-FRR eth0 R-FRR eth1 ↔ R-Juniper ge-0/0/0 R-Juniper ge-0/0/1 ↔ Server Fa0
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
ASA
interface GigabitEthernet1/1
ip address 192.168.1.1 255.255.255.0
no shutdown
exit
interface GigabitEthernet1/2
ip address 10.0.1.1 255.255.255.252
no shutdown
exit R-Arista interface Ethernet1
no switchport
ip address 10.0.1.2/30
exit
interface Ethernet2
no switchport
ip address 10.0.2.1/30
exit N9K interface Ethernet1/1
no switchport
ip address 10.0.2.2/30
no shutdown
exit
interface Ethernet1/2
no switchport
ip address 10.0.3.1/30
no shutdown
exit R-FRR vtysh
interface eth0
ip address 10.0.3.2/30
exit
interface eth1
ip address 10.0.4.1/30
exit
exit R-Juniper configure
set interfaces ge-0/0/0 unit 0 family inet address 10.0.4.2/30
set interfaces ge-0/0/1 unit 0 family inet address 172.16.2.1/24
commit
exit 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 ASA’s interfaces are named inside (100) and outside (0) 20 Checked automatically against the device’s live state (asaNameif). and Checked automatically against the device’s live state (asaNameif). 2 The Arista routes (ip routing is on) 15 On R-Arista: show ip route works (routing is enabled). 3 The Nexus has OSPF enabled as a feature and two neighbours 20 Checked automatically against the device’s live state (nxFeature). and On N9K: show ip ospf neighbor shows at least 2 neighbour(s) in FULL. 4 The Juniper filters telnet on its server-facing input 15 Checked automatically against the device’s live state (jFilter). 5 The FRR box learns the server LAN from the Juniper 15 On R-FRR: show ip route lists 172.16.2.0/24. 6 The inside PC reaches the server through all five 25 On Inside-PC: ping 172.16.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:
ASA
interface GigabitEthernet1/1
nameif inside
exit
interface GigabitEthernet1/2
nameif outside
exit
route outside 0 0 10.0.1.2
object network INSIDE-NET
subnet 192.168.1.0 255.255.255.0
nat (inside,outside) dynamic interface
exit
policy-map global_policy
class inspection_default
inspect icmp
exit
exit
write memory R-Arista ip routing
router ospf 1
router-id 2.2.2.2
network 10.0.1.0/30 area 0.0.0.0
network 10.0.2.0/30 area 0.0.0.0 N9K feature ospf
router ospf 1
router-id 3.3.3.3
exit
interface Ethernet1/1
ip router ospf 1 area 0.0.0.0
exit
interface Ethernet1/2
ip router ospf 1 area 0.0.0.0
exit
copy running-config startup-config R-FRR vtysh
router ospf
ospf router-id 4.4.4.4
network 10.0.3.0/30 area 0
network 10.0.4.0/30 area 0
write memory
exit R-Juniper configure
set routing-options router-id 5.5.5.5
set protocols ospf area 0.0.0.0 interface ge-0/0/0.0
set protocols ospf area 0.0.0.0 interface ge-0/0/1.0 passive
set firewall family inet filter PROTECT term NO-TELNET from protocol tcp
set firewall family inet filter PROTECT term NO-TELNET from destination-port telnet
set firewall family inet filter PROTECT term NO-TELNET then discard
set firewall family inet filter PROTECT term REST then accept
set interfaces ge-0/0/1 unit 0 family inet filter input PROTECT
commit
exit 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.