CloudLabBox
Try the free demo

CCIE Enterprise Infrastructure practice lab 3 of 8

BGP design and routing policy

Build a dual-stack enterprise BGP edge with two ISPs: route reflectors, peer templates, dynamic neighbours, multipath, inbound and outbound policy, conditional advertisement, ORF, aggregation with AS sets, and a merger handled with local-as. A fault injector proves the failover. A 3 to 4 hour practice lab.

Run this lab

It needs Standard: its 12 nodes are set to 12 vCPU and 6,144 MB in total.

In your workspace: Shared, then CCIE Enterprise Infrastructure practice guided labs, then 03 - BGP design and routing 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 12 vCPU and 6,144 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 240 minutes
Nodes need
12 vCPU, 6,144 MB
Smallest plan
Standard

The scenario

Halden Freight's public network is AS 64496. It buys transit from ISP-A and ISP-B, and it has taken over Brennock's old connection to a peer that still believes it talks to AS 64497. OSPF already runs inside AS 64496 (loopbacks and core links only, both address families), so your work is all BGP.

                 T1  AS 65536 (shows as 1.0)
                /  \
   SA -- ISP-A      ISP-B -- SB        SA and SB: AS 64999, split site
   AS 64500 ||       |  AS 64510
      2 links||      |  MD5, GTSM, passive
             E1      E2
             | \    / |  \
             |  \  /  |   \
   C1 ---E1  |   \/   |    E2--- C1    C1: branch, AS 65010, dual homed
             |   /\   |
             R1 ==== R2 ---- M1        M1: AS 64499, peers with "AS 64497"
              \      /
                 D1                    D1: data centre
WhatDesign
AS 64496R1 and R2 are route reflectors with one cluster ID, 10.255.3.255. E1, E2 and D1 are clients.
Public ranges198.51.100.0/24 (P1), 203.0.113.0/24 (P2), 192.0.2.0/24 (DR), 198.18.60.0/24 (C1's public LAN)
IPv62001:db8:100::/48 for Halden. ISPs use the links shown.
D1 LANs198.51.100.0/25, 198.51.100.128/25, 203.0.113.0/25, 203.0.113.128/26, 192.0.2.0/24, 2001:db8:100:1::/64, 2001:db8:100:2::/64
M1Originates 172.31.0.0/16 and 203.0.113.192/26, a block it still uses from Halden's P2
C110.60.10.0/24 (internal) and 198.18.60.0/24 (public)
ISP-ASends a default and its full table. Community 64500:80 sets local preference 80 inside ISP-A. Its sessions use timers 10 and 30.
ISP-BFull table, no default. Community 64510:80 sets local preference 80 inside ISP-B. MD5 key Halden-ISPB-2026, TTL security with 1 hop, timers 10 and 30. It accepts prefix-list ORF.

Addressing

DeviceInterfaceAddressConnects to
R1Lo010.255.3.1/32, 2001:db8:255:3::1/128
R1Gi0/010.3.12.1/30, 2001:db8:3:12::1/64R2 Gi0/0
R1Gi0/110.3.111.1/30, 2001:db8:3:111::1/64E1 Gi0/0
R1Gi0/210.3.121.1/30, 2001:db8:3:121::1/64D1 Gi0/0
R1Gi0/310.3.112.1/30, 2001:db8:3:112::1/64E2 Gi0/1
R2Lo010.255.3.2/32, 2001:db8:255:3::2/128
R2Gi0/010.3.12.2/30, 2001:db8:3:12::2/64R1 Gi0/0
R2Gi0/110.3.212.1/30, 2001:db8:3:212::1/64E2 Gi0/0
R2Gi0/210.3.221.1/30, 2001:db8:3:221::1/64D1 Gi0/1
R2Gi0/310.3.211.1/30, 2001:db8:3:211::1/64E1 Gi0/1
R2Gi0/4172.16.99.1/30M1 Gi0/0
E1Lo010.255.3.11/32, 2001:db8:255:3::11/128
E1Gi0/010.3.111.2/30, 2001:db8:3:111::2/64R1 Gi0/1
E1Gi0/110.3.211.2/30, 2001:db8:3:211::2/64R2 Gi0/3
E1Gi0/2172.17.1.2/30, 2001:db8:a:1::2/64ISPA Gi0/0
E1Gi0/3172.17.2.2/30ISPA Gi0/1
E1Gi0/410.60.1.1/29C1 Gi0/0
E2Lo010.255.3.12/32, 2001:db8:255:3::12/128
E2Gi0/010.3.212.2/30, 2001:db8:3:212::2/64R2 Gi0/1
E2Gi0/110.3.112.2/30, 2001:db8:3:112::2/64R1 Gi0/3
E2Gi0/2172.18.1.2/30, 2001:db8:b:1::2/64ISPB Gi0/0
E2Gi0/310.60.2.1/29C1 Gi0/1
D1Lo010.255.3.21/32, 2001:db8:255:3::21/128
D1Gi0/010.3.121.2/30, 2001:db8:3:121::2/64R1 Gi0/2
D1Gi0/110.3.221.2/30, 2001:db8:3:221::2/64R2 Gi0/2
D1Lo10198.51.100.1/25, 2001:db8:100:1::1/64
D1Lo11198.51.100.129/25
D1Lo20203.0.113.1/25, 2001:db8:100:2::1/64
D1Lo21203.0.113.129/26
D1Lo30192.0.2.1/24
C1Lo010.255.3.31/32
C1Lo1010.60.10.1/24
C1Lo11198.18.60.1/24
C1Gi0/010.60.1.2/29E1 Gi0/4
C1Gi0/110.60.2.2/29E2 Gi0/3
ISPALo010.255.3.101/32
ISPALo10198.19.100.1/24
ISPAGi0/0172.17.1.1/30, 2001:db8:a:1::1/64E1 Gi0/2
ISPAGi0/1172.17.2.1/30E1 Gi0/3
ISPAGi0/2172.19.1.1/30, 2001:db8:f:1::1/64T1 Gi0/0
ISPAGi0/3172.19.11.1/30SA Gi0/0
ISPBLo010.255.3.102/32
ISPBLo10198.19.200.1/24
ISPBGi0/0172.18.1.1/30, 2001:db8:b:1::1/64E2 Gi0/2
ISPBGi0/1172.19.2.1/30, 2001:db8:f:2::1/64T1 Gi0/1
ISPBGi0/2172.19.12.1/30SB Gi0/0
T1Lo010.255.3.103/32
T1Lo10198.18.1.1/24, 2001:db8:f00:1::1/64
T1Lo11198.18.2.1/25
T1Lo12198.18.2.129/25
T1Gi0/0172.19.1.2/30, 2001:db8:f:1::2/64ISPA Gi0/2
T1Gi0/1172.19.2.2/30, 2001:db8:f:2::2/64ISPB Gi0/1
SALo010.255.3.111/32
SALo10198.18.71.1/24
SAGi0/0172.19.11.2/30ISPA Gi0/3
SBLo010.255.3.112/32
SBLo10198.18.72.1/24
SBGi0/0172.19.12.2/30ISPB Gi0/2
M1Lo010.255.3.104/32
M1Lo10203.0.113.193/26
M1Lo20172.31.0.1/16
M1Gi0/0172.16.99.2/30R2 Gi0/4

Rules for the whole lab

  • Don't change ISP-A, ISP-B, T1 or M1. Keep every address and interface as given.
  • No static routes and no redistribution between BGP and OSPF. The eBGP link prefixes stay out of OSPF.
  • Don't remove LAB-FAIL-E1.

What you’ll practise

  • Design iBGP with route reflectors, templates and dynamic neighbours
  • Control both directions of traffic with local preference, AS path lists and ISP communities
  • Use conditional advertisement, ORF and aggregation with an AS set where each one is the right tool
  • Handle a merger and split sites with local-as, remove-private-as and allowas-in
  • Prove the design with an injected ISP failure, for IPv4 and IPv6

The tasks

  • Section 1: iBGP at scale (20 points)
  • Section 2: ISP edge and traffic in both directions (28 points)
  • Section 3: Filtering and table management (12 points)
  • Section 4: A merger and a split site (14 points)
  • Section 5: IPv6 and the failure drill (26 points)

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 design and routing policy12 nodes, 17 links. Every link is listed as text below the diagram.R1R2E1E2D1C1ISPAISPBT1SASBM1Gi0/1Gi0/0Gi0/1Gi0/0Gi0/3Gi0/0Gi0/2Gi0/0Gi0/2Gi0/0Gi0/3Gi0/1Gi0/2Gi0/0Gi0/4Gi0/0Gi0/3Gi0/1Gi0/4Gi0/0Gi0/2Gi0/0Gi0/2Gi0/1Gi0/2Gi0/0Gi0/1Gi0/1Gi0/0Gi0/0Gi0/3Gi0/1Gi0/3Gi0/1
12 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • R1 Gi0/0 to R2 Gi0/0
  • R1 Gi0/1 to E1 Gi0/0
  • R1 Gi0/2 to D1 Gi0/0
  • R1 Gi0/3 to E2 Gi0/1
  • R2 Gi0/1 to E2 Gi0/0
  • R2 Gi0/2 to D1 Gi0/1
  • R2 Gi0/3 to E1 Gi0/1
  • R2 Gi0/4 to M1 Gi0/0
  • E1 Gi0/2 to ISPA Gi0/0
  • E1 Gi0/3 to ISPA Gi0/1
  • E2 Gi0/2 to ISPB Gi0/0
  • E1 Gi0/4 to C1 Gi0/0
  • E2 Gi0/3 to C1 Gi0/1
  • ISPA Gi0/2 to T1 Gi0/0
  • ISPB Gi0/1 to T1 Gi0/1
  • ISPA Gi0/3 to SA Gi0/0
  • ISPB Gi0/2 to SB Gi0/0
Nodes in BGP design and routing policy, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
E1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
E2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
D1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
C1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
ISPACisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
ISPBCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
T1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
SACisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
SBCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
M1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 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 CCIE Enterprise Infrastructure practice guided labs.

  3. Open 03 - BGP design and routing 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 CCIE Enterprise Infrastructure practice labs

All CCIE Enterprise Infrastructure practice labs

Related labs in other courses

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