JNCIP-ENT lab 7 of 19

BGP scaling and advanced options

Scale iBGP with a route reflector inside a confederation, then handle a merger and a messy edge with local-as, remove-private, prefix limits and damping.

Run this lab

It needs Standard: its 6 nodes are set to 12 vCPU and 12,288 MB in total.

In your workspace: Shared, then JNCIP-ENT JN0-650 guided labs, then 07 - BGP scaling and advanced options

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

Level
Advanced
Time
About 90 minutes
Nodes need
12 vCPU, 12,288 MB
Smallest plan
Standard

The scenario

Northmere bought Holme Haulage, so its BGP now has two parts. It runs as a confederation: one AS, 64500, to the outside world, and two sub-ASs inside. In sub-AS 65001, R1 has iBGP sessions to R2 and R3, but there's no full mesh and R2 and R3 can't see each other's routes. Sub-AS 65002 is Holme's router R4, which is waiting for a session. R2 is the border, with an ISP and a customer who still has old settings. You'll fix each of these and then add some protection against a flapping prefix.

DeviceInterfaceAddressRole
R1ge-0/0/0, ge-0/0/1, ge-0/0/2, lo010.0.12.1/30, 10.0.13.1/30, 10.0.14.1/30, 10.255.0.1/32Hub, sub-AS 65001
R2ge-0/0/0, lo010.0.12.2/30, 10.255.0.2/32Border, sub-AS 65001
R2ge-0/0/1, ge-0/0/2198.18.1.1/30, 198.18.2.1/30To ISP at .2, to CUST at .2
R3Gi0/0, Lo0, Lo1010.0.13.2/30, 10.255.0.3/32, 10.63.1.1/24Depot, sub-AS 65001
R4Gi0/0, Lo0, Lo1010.0.14.2/30, 10.255.0.4/32, 10.64.1.1/24Holme, sub-AS 65002
ISPGi0/0198.18.1.2/30AS 64501, 203.0.113.0/24 and 100.64.5.0/24
CUSTGi0/0198.18.2.2/30AS 64999, a private number, 192.168.99.0/24

OSPF runs across R1, R2, R3 and R4, for their loopbacks and links. The two LANs are only in BGP. If they were in OSPF too, R1 would use the OSPF route, its BGP route would be inactive, and it would have nothing to reflect: Junos advertises only active routes unless you add advertise-inactive.

What you’ll practise

  • Configure a route reflector and read its loop-prevention attributes
  • Configure confederations and read the confederation path
  • Use local-as and remove-private
  • Protect a session with a prefix limit
  • Damp a flapping route

The tasks

  1. Replace the full mesh with a route reflector
  2. Join the sub-ASs
  3. Keep an old AS number for one customer with local-as
  4. Remove a private AS number
  5. Limit prefixes and damp a flapping route

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 scaling and advanced options6 nodes, 5 links. Every link is listed as text below the diagram.R1R2R3R4ISPCUSTge-0/0/1Gi0/0ge-0/0/1Gi0/0ge-0/0/2Gi0/0ge-0/0/2Gi0/0ge-0/0/0ge-0/0/0
6 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in BGP scaling and advanced options, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Juniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
R2Juniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
R3Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R4Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
ISPCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
CUSTCisco 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 JNCIP-ENT JN0-650 guided labs.

  3. Open 07 - BGP scaling and advanced options 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 JNCIP-ENT labs

All JNCIP-ENT 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.