CloudLabBox
Try the free demo

Nokia SR OS NRS I lab 6 of 14

BGP: iBGP, eBGP and policy

Connect Rivermark to an upstream: iBGP on system addresses, eBGP on link addresses, routes announced by export policy, next-hop-self, and local preference to choose the exit.

Run this lab

It needs Standard: its 3 nodes are set to 6 vCPU and 14,400 MB in total.

In your workspace: Shared, then Nokia SR OS NRS I guided labs, then 06 - BGP - iBGP eBGP and 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 6 vCPU and 14,400 MB together. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 60 minutes
Nodes need
6 vCPU, 14,400 MB
Smallest plan
Standard

The scenario

Rivermark is AS 64510, and it's about to connect to its first upstream, AS 64520. R1 and R2 are Rivermark's routers, with OSPF already running between them, and R3 is the upstream's router, which you also look after in this lab. Each Rivermark router has a link to R3.

Rivermark announces its customer range 203.0.113.0/24, on R1's customers interface. R3 announces 198.51.100.0/24, on its peering interface. Rivermark wants all outbound traffic to leave through R2, because R1's link is the expensive one.

DeviceInterfacePortAddressConnects to
R1system-10.255.0.1/32
R1to-R21/1/c1/110.0.12.1/30R2
R1to-R31/1/c2/110.0.13.1/30R3
R1customers-203.0.113.1/24
R2system-10.255.0.2/32
R2to-R11/1/c1/110.0.12.2/30R1
R2to-R31/1/c2/110.0.23.1/30R3
R3system-10.255.0.3/32
R3to-R11/1/c1/110.0.13.2/30R1
R3to-R21/1/c2/110.0.23.2/30R2
R3peering-198.51.100.1/24

What you’ll practise

  • Build iBGP between system addresses
  • Peer with an external AS
  • Announce routes with prefix lists and export policies
  • Read BGP flags and fix an unresolved next hop
  • Steer outbound traffic with local preference

The tasks

  1. Bring up iBGP on the system addresses
  2. Peer with the upstream and announce routes
  3. Fix the next hop for iBGP
  4. Add the second exit and prefer it

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 - iBGP eBGP and policy3 nodes, 3 links. Every link is listed as text below the diagram.R1R2R3p1/1/2p1/1/1p1/1/2p1/1/2p1/1/1p1/1/1
3 nodes, with the interface names each link uses.
Every link, as text
  • R1 p1/1/1 to R2 p1/1/1
  • R1 p1/1/2 to R3 p1/1/1
  • R2 p1/1/2 to R3 p1/1/2
Nodes in BGP: iBGP, eBGP and policy, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Nokia Integrated router (VSR NG template)timos-ng-21.10.R12 vCPU, 4,800 MB
R2Nokia Integrated router (VSR NG template)timos-ng-21.10.R12 vCPU, 4,800 MB
R3Nokia Integrated router (VSR NG template)timos-ng-21.10.R12 vCPU, 4,800 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 Nokia SR OS NRS I guided labs.

  3. Open 06 - BGP - iBGP eBGP and 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 Nokia SR OS NRS I labs

All Nokia SR OS NRS I labs

Related labs in other courses

CloudLabBox is independent of Nokia. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.