HCIP-Datacom Core lab 5 of 14
BGP route control with filters and communities
Run the policy of a small transit provider: peer groups, prefix lists, AS_Path filters, standard and well-known communities, route policies, aggregation and route limits.
Run this lab
It needs Standard: its 5 nodes are set to 5 vCPU and 9,216 MB in total.
In your workspace: Shared, then HCIP-Datacom Core H12-821 guided labs, then 05 - BGP route control with filters and communities
- Level
- Advanced
- Time
- About 90 minutes
- Nodes need
- 5 vCPU, 9,216 MB
- Smallest plan
- Standard
The scenario
Northwind Connect, the group's small ISP (AS 65002, R2), carries two customers, R1 and R3, and buys transit from R4. You run R2's policy. The customers make mistakes: R1 leaks a private network, and R3 passes on a route it has no business carrying. Each customer's tag requests must also be honoured, and the upstream should see tidy aggregates rather than every customer /24.
| Router | AS | Links | Networks it advertises |
|---|---|---|---|
| R1 | 65001 | GE0/0/0 10.0.12.1/24 | 10.1.0.0/24 to 10.1.3.0/24, 10.2.0.0/24, 172.31.1.0/24 (should never have been advertised) |
| R2 | 65002 | GE0/0/0 10.0.12.2/24, GE0/0/1 10.0.23.2/24, GE0/0/2 10.0.24.2/24 | None |
| R3 | 65003 | GE0/0/0 10.0.23.3/24, GE0/0/1 10.3.0.1/24 (PC1 .10) | 10.3.0.0/24, 10.3.1.0/24, 172.20.0.0/24 (with an extra AS on the path, as if R3 were transit for AS 64999) |
| R4 | 65004 | GE0/0/0 10.0.24.4/24 | 203.0.113.0/24 |
What you’ll practise
- Use a peer group for shared configuration
- Filter received routes with an IP prefix list and an AS_Path filter
- Set and act on communities, including no-export
- Build a route policy that matches a community and changes the AS_Path
- Aggregate customer routes and suppress the specifics
- Protect a session with a route limit
The tasks
- Task 0: Load the starting configuration
- Concept: peer groups
- Task 1: Bring up the sessions
- Concept: prefix lists
- Task 2: Accept only R1's registered networks
- Concept: AS_Path filters
- Task 3: Accept only R3's own routes
- Concept: communities
- Task 4: Honour the customers' tags
- Concept: aggregation
- Task 5: Aggregate R1's networks
- Task 6: Limit what R3 can send
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
GE0/0/0to R2GE0/0/0 - R2
GE0/0/1to R3GE0/0/0 - R2
GE0/0/2to R4GE0/0/0 - R3
GE0/0/1to PC1eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| R2 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| R3 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| R4 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| PC1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
HCIP-Datacom Core H12-821 guided labs.Open
05 - BGP route control with filters and communitiesand 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 HCIP-Datacom Core labs
Related labs in other courses
CloudLabBox is independent of Huawei. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.