CloudLabBox
Try the free demo

JNCIS-SP lab 16 of 16

Capstone - a new provider site

Build a customer service from a design sheet: dual-stack IS-IS, RSVP LSPs with a standby, a LACP bundle to the customer's switch with IRB, and BGP with aggregates, a conditional default and communities. Then fail the core and prove it survives.

Run this lab

It needs Standard: its 6 nodes are set to 11 vCPU and 14,592 MB in total.

In your workspace: Shared, then JNCIS-SP JN0-364 guided labs, then 16 - Capstone - a new provider site

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 11 vCPU and 14,592 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 150 minutes
Nodes need
11 vCPU, 14,592 MB
Smallest plan
Standard

The scenario

Skerry has won a contract: join a customer's Malton offices (H1, behind SW1) to its remote site (CE2, AS 65002). You have three new routers with addresses and nothing else. SW1, H1 and CE2 are ready. Build the service from this design, with no step-by-step help. The hints and solution are there if you need them.

ItemDesign
LoopbacksPE1 10.255.0.1, P1 10.255.0.2, PE2 10.255.0.3. IPv6 2001:db8:255::N/128
Core linksPE1 to P1 10.0.12.0/30, P1 to PE2 10.0.23.0/30, PE1 to PE2 10.0.13.0/30. IPv6 2001:db8:0:XY::N/64, as on the IPv4 subnet names
IS-ISLevel 2 only, wide metrics only, NETs 49.0001.0000.0000.000N.00, point-to-point, loopbacks passive. Metric 100 on the direct link
MPLSRSVP on all core links. LSPs TO-PE2 and TO-PE1 between the PEs
ProtectionTO-PE2 has a primary path with no hops and a standby DIRECT through 10.0.13.2.
Core ruleP1 runs no BGP
BGPAS 64510, IBGP between PE loopbacks with next-hop self. EBGP from PE2 to CE2 at 172.16.2.2
PE1 to SW1ae0, LACP active, members ge-0/0/2 and ge-0/0/3, trunk for VLAN 100
Customer VLANBridge domain V100, irb.100 198.19.1.1/24 and 2001:db8:1::1/64
AnnouncementsPE1 announces only the aggregate 198.19.0.0/16 in IBGP
CE2 receivesOnly 198.19.0.0/16, and a default generated on PE2 that exists only while 198.19.0.0/16 is present
CE2 sendsAccept only 198.18.2.0/24, tagged with community 64510:200

What you’ll practise

  • Plan and build a provider service end to end
  • Combine IS-IS, RSVP, BGP, bridging and LAG
  • Express a design as routing policy
  • Test the protection by failing the active path

The tasks

  1. The core IGP
  2. MPLS with a standby path
  3. The customer edge at Layer 2
  4. BGP and policy
  5. Prove the protection

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 - a new provider site6 nodes, 7 links. Every link is listed as text below the diagram.H1SW1PE1P1PE2CE2eth0Gi0/2ge-0/0/2Gi0/0Gi0/0ge-0/0/2Gi0/1ge-0/0/3ge-0/0/1ge-0/0/0ge-0/0/0ge-0/0/0ge-0/0/1ge-0/0/1
6 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • H1 eth0 to SW1 Gi0/2
  • SW1 Gi0/0 to PE1 ge-0/0/2
  • SW1 Gi0/1 to PE1 ge-0/0/3
  • PE1 ge-0/0/0 to P1 ge-0/0/0
  • P1 ge-0/0/1 to PE2 ge-0/0/0
  • PE1 ge-0/0/1 to PE2 ge-0/0/1
  • PE2 ge-0/0/2 to CE2 Gi0/0
Nodes in Capstone - a new provider site, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
H1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
SW1Cisco IOSvL2viosl2-adventerprisek9-m.ssa.high_iron_202009291 vCPU, 768 MB
PE1Juniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
P1Juniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 3,584 MB
PE2Juniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 3,584 MB
CE2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 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 JNCIS-SP JN0-364 guided labs.

  3. Open 16 - Capstone - a new provider site 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 JNCIS-SP labs

All JNCIS-SP 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.