HCIP-Datacom Core lab 4 of 14
BGP attributes and route reflectors
Give a dual-homed AS one route reflector, then steer traffic out with Local_Pref and in with MED and AS_Path, using the path selection order to explain every result.
Run this lab
It needs Standard: its 6 nodes are set to 6 vCPU and 10,240 MB in total.
In your workspace: Shared, then HCIP-Datacom Core H12-821 guided labs, then 04 - BGP attributes and route reflectors
- Level
- Advanced
- Time
- About 90 minutes
- Nodes need
- 6 vCPU, 10,240 MB
- Smallest plan
- Standard
The scenario
Northwind (AS 100) has two Internet links, from R2 and R3, both to its provider R4 (AS 200). R1 is the core router and will be the route reflector, so nobody has to build a full iBGP mesh. OSPF already runs inside AS 100. Finance wants traffic to 20.0.1.0/24 to leave through R3, and each of Northwind's two networks to arrive over a chosen link.
| Router | AS | LoopBack0 | Links |
|---|---|---|---|
| R1 (RR) | 100 | 1.1.1.1 | GE0/0/0 10.0.12.1/24, GE0/0/1 10.0.13.1/24, GE0/0/2 192.168.1.1/24 (PC1 .10), LoopBack1 192.168.2.1/24 |
| R2 | 100 | 2.2.2.2 | GE0/0/0 10.0.12.2/24, GE0/0/1 10.0.24.2/24 (to R4) |
| R3 | 100 | 3.3.3.3 | GE0/0/0 10.0.13.3/24, GE0/0/1 10.0.34.3/24 (to R4) |
| R4 | 200 | none | GE0/0/0 10.0.24.4/24, GE0/0/1 10.0.34.4/24, GE0/0/2 20.0.1.1/24 (PC2 .10), LoopBack1 20.0.2.1/24 |
What you’ll practise
- Build iBGP over loopbacks with a route reflector and two clients
- Solve the next-hop problem with next-hop-local
- Read Originator_ID and Cluster_List on a reflected route
- Steer outbound traffic with Local_Pref and inbound traffic with AS_Path and MED
- Walk through VRP's BGP path selection order
The tasks
- Task 0: Load the starting configuration
- Concept: why route reflectors
- Task 1: Build the BGP sessions
- Concept: the next-hop problem
- Task 2: Fix the next hop
- Concept: path selection on VRP
- Task 3: Leave through R3 for 20.0.1.0/24
- Concept: MED and AS_Path
- Task 4: Choose how traffic comes in
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 - R1
GE0/0/1to R3GE0/0/0 - R2
GE0/0/1to R4GE0/0/0 - R3
GE0/0/1to R4GE0/0/1 - R1
GE0/0/2to PC1eth0 - R4
GE0/0/2to PC2eth0
| 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 |
| PC2 | 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
04 - BGP attributes and route reflectorsand 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.