CloudLabBox
Try the free demo

JNCIS-SP lab 5 of 16

BGP groups and attributes with policy

Build IBGP and EBGP groups for a small provider, fix hidden routes with next-hop self, steer traffic with attributes, and use communities to carry the customer without becoming a free transit.

Run this lab

It needs Standard: its 6 nodes are set to 9 vCPU and 13,824 MB in total.

In your workspace: Shared, then JNCIS-SP JN0-364 guided labs, then 05 - BGP groups and attributes with policy

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 9 vCPU and 13,824 MB together. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 95 minutes
Nodes need
9 vCPU, 13,824 MB
Smallest plan
Standard

The scenario

Skerry Networks, AS 64510, has a customer on R1 and a transit peer on each of R2 and R3. OSPF already carries the loopbacks and links. You'll build BGP, choose which peer carries outgoing traffic, and make sure Skerry doesn't accidentally carry traffic between its two peers. The customer and the peers are configured already.

DeviceASInterfaceAddressAnnounces
R164510ge-0/0/2, lo0172.16.1.1/30, 10.255.0.1/32
R264510ge-0/0/2, lo0192.0.2.2/30, 10.255.0.2/32
R364510ge-0/0/2, lo0198.51.100.2/30, 10.255.0.3/32
CUST65020Gi0/0172.16.1.2/30198.19.20.0/24, and a private 10.99.0.0/16 that must not spread. MD5 key skerry-cust.
PEERA64496Gi0/0192.0.2.1/30198.18.1.0/24 and 203.0.113.0/24
PEERB64497Gi0/0198.51.100.1/30198.18.2.0/24 and 203.0.113.0/24

Core links are 10.0.12.0/30 (R1 to R2), 10.0.13.0/30 (R1 to R3) and 10.0.23.0/30 (R2 to R3).

What you’ll practise

  • Configure IBGP and EBGP groups
  • Explain next-hop behaviour and hidden routes
  • Apply the path selection order
  • Tag and filter with communities and export policy
  • Use group options such as hold-time and remove-private

The tasks

  1. Internal BGP
  2. External BGP and the next hop
  3. Attributes and path selection
  4. Policy: filter, tag and stop being a transit
  5. Other group options

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 BGP groups and attributes with policy6 nodes, 6 links. Every link is listed as text below the diagram.CUSTR1R2R3PEERAPEERBge-0/0/2Gi0/0ge-0/0/2Gi0/0ge-0/0/2Gi0/0ge-0/0/0ge-0/0/0ge-0/0/1ge-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
  • R1 ge-0/0/0 to R2 ge-0/0/0
  • R1 ge-0/0/1 to R3 ge-0/0/0
  • R2 ge-0/0/1 to R3 ge-0/0/1
  • R1 ge-0/0/2 to CUST Gi0/0
  • R2 ge-0/0/2 to PEERA Gi0/0
  • R3 ge-0/0/2 to PEERB Gi0/0
Nodes in BGP groups and attributes with policy, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
CUSTCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R1Juniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
R2Juniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
R3Juniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
PEERACisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PEERBCisco 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 05 - BGP groups and attributes with policy 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.