BGP in depth lab 8 of 14
Stability and safety nets
One customer leaks a table, another flaps a link all night, and a partner restarts its routing software. Put the safety nets in place on Kestrel Fibre's edge: prefix limits, route-flap dampening, soft reconfiguration and route refresh, and graceful restart between IOS and EOS, then trigger each failure and read what happens.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 3,328 MB in total. That fits the free demo too.
In your workspace: Shared, then BGP in depth guided labs, then 08 - Stability and safety nets
- Level
- Advanced
- Time
- About 90 minutes
- Nodes need
- 4 vCPU, 3,328 MB
- Smallest plan
- Lite
The scenario
Kestrel Fibre's edge router, R1, had a bad night. A customer leaked its internal routes, another customer's flapping link kept the routers busy, and a partner's routing restart dropped traffic that could have kept flowing. You've been asked to put in the safety nets, then trigger each failure in the lab to prove they work.
| Peer | AS | Expected prefixes |
|---|---|---|
| R2 | 64510 | 2: 203.0.113.0/26 and 203.0.113.64/26 |
| EOS1 | 64520 | 1: 198.51.100.0/24 |
| CHR1 | 64530 | 1: 10.100.0.0/24 |
| Device | Interface | Address | Connects to |
|---|---|---|---|
| R1 | Loopback0 | 10.255.0.1/32 | |
| R1 | Loopback1 | 192.0.2.1/24 | |
| R1 | Gi0/0 | 172.16.12.1/30 | R2 Gi0/0 |
| R1 | Gi0/1 | 172.16.13.1/30 | EOS1 Ethernet1 |
| R1 | Gi0/2 | 172.16.14.1/30 | CHR1 ether1 |
| R2 | Loopback0 | 10.255.0.2/32 | |
| R2 | Loopback1 | 203.0.113.1/26 | |
| R2 | Loopback2 | 203.0.113.65/26 | |
| R2 | Loopback11 | 198.18.1.1/24 | |
| R2 | Loopback12 | 198.18.2.1/24 | |
| R2 | Loopback13 | 198.18.3.1/24 | |
| R2 | Loopback14 | 198.18.4.1/24 | |
| R2 | Gi0/0 | 172.16.12.2/30 | R1 Gi0/0 |
| EOS1 | Ethernet1 | 172.16.13.2/30 | R1 Gi0/1 |
| EOS1 | Loopback0 | 10.255.0.3/32 | |
| EOS1 | Loopback1 | 198.51.100.1/24 | |
| CHR1 | ether1 | 172.16.14.2/30 | R1 Gi0/2 |
| CHR1 | lan | 10.100.0.1/24 |
What you’ll practise
- Protect a session with a maximum-prefix limit, a warning threshold and an automatic restart
- Recognise the Idle (PfxCt) state and the log messages that go with it
- Explain how soft reconfiguration differs from route refresh, and when each is used
- Configure route-flap dampening, watch a penalty build and clear a suppressed route
- Negotiate graceful restart between IOS and EOS, and watch routes stay in place through a BGP restart
- Set a route limit on RouterOS
The tasks
- Prefix limits
- Soft reconfiguration or route refresh
- Route-flap dampening
- Graceful restart
- A limit on RouterOS
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
Gi0/0to R2Gi0/0 - R1
Gi0/1to EOS1Ethernet1 - R1
Gi0/2to CHR1ether1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| EOS1 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| CHR1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
BGP in depth guided labs.Open
08 - Stability and safety netsand 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 BGP in depth labs
Related labs in other courses
CloudLabBox is independent of Arista Networks, Cisco, Juniper Networks and MikroTik. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.