JNCIP-ENT lab 5 of 19
BGP communities and policy
Stop a network being a free transit by labelling every route with a community at the edge, then control exports, ISP behaviour and AS path filtering from those labels.
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 05 - BGP communities and policy
- Level
- Advanced
- Time
- About 90 minutes
- Nodes need
- 12 vCPU, 12,288 MB
- Smallest plan
- Standard
The scenario
Northmere has grown into a small regional network. It buys transit from ISP-A and ISP-B, peers with a neighbour (PEER), and sells connectivity to a customer (CUST). All the sessions are up, but there's no policy, so Northmere is giving every network a free ride over its links. You'll label every route with a community when it arrives, and then let those labels decide where it goes. That's how networks of any size keep policy manageable: the decision is made once, at the edge, and every other router just reads the label.
| AS | Device | Routes |
|---|---|---|
| 64500 | R1, R2 | 10.60.0.0/16, an aggregate on both |
| 64501 | ISP-A (transit) | 203.0.113.0/24, 100.64.9.0/24 |
| 64502 | ISP-B (transit) | 198.51.100.0/24, 100.64.30.0/24 |
| 64503 | PEER (peer) | 172.31.200.0/24 |
| 64504 | CUST (customer) | 192.168.100.0/24 |
| Link | Addresses |
|---|---|
| R1 to R2 | 10.0.12.0/30, with loopbacks 10.255.0.1 and .2 |
| R1 to ISP-A | 198.18.1.1 and .2 |
| R2 to ISP-B | 198.18.2.1 and .2 |
| R1 to CUST | 198.18.4.1 and .2 |
| R2 to PEER | 198.18.5.1 and .2 |
The plan for communities:
| Community | Meaning |
|---|---|
| 64500:100 | Learned from transit |
| 64500:200 | Learned from a peer |
| 64500:300 | Learned from a customer |
What you’ll practise
- Add, match and delete communities
- Write customer, peer and transit export rules
- Use community and AS path regular expressions
- Explain the well-known communities
- Influence an ISP with an action community
The tasks
- Label routes as they arrive
- Let the labels decide
- Match several communities with a regular expression
- Respect the well-known communities
- Use your ISP's action community
- Filter on the AS path
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.
Every link, as text
- R1
ge-0/0/0to R2ge-0/0/0 - R1
ge-0/0/1to ISP-AGi0/0 - R2
ge-0/0/1to ISP-BGi0/0 - R1
ge-0/0/2to CUSTGi0/0 - R2
ge-0/0/2to PEERGi0/0 - ISP-A
Gi0/1to ISP-BGi0/1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| R2 | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| ISP-A | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| ISP-B | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| CUST | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| PEER | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
JNCIP-ENT JN0-650 guided labs.Open
05 - BGP communities and policyand 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
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.