This is a technical workshop to teach the Interior Gateway Protocol (IGP) and Border Gateway Protocol (BGP) skills required for configuring interconnections between the autonomous networks that make up the Internet according to current industry best practices.
It runs with up to 8 groups. Each group has:
- A border router (BX)
- A peering router (PX)
- A core router (CX)
- An access router (AX)
- A customer router (CustX)
- A server (srvX)
In addition, there are two "transit" routers which provide the uplinks; and two IXPs each with a switch (IXP), a services router (SR), and an Ubuntu BIRD router server (RS).
You will need the following files:
||student navigation page to go in e.g.
||the GNS3 project|
||VM image with bird preinstalled, for RS and SRV instances|
||cloud-init configs for RS|
||cloud-init configs for SRV in each group|
The total memory allocation of all the devices is 27GB. There should still be enough RAM to run the NOC on a 32GB machine.
Backbone addressing plan
|IP Address||DNS Name|
See the training materials for the addressing plan used inside the network.
These passwords are shared with the students:
(In the initial state "00-blank", the student routers are unconfigured)
The instructor logins are not shared with the students:
|TRx, SRx, IXPx||
lab-PW login also works on these devices, so that students
can inspect the state of the infrastructure, e.g. show BGP status, although
they will not know the enable password.
On the route servers, the
isplab account is not able to
sudo - but it is
bird so they can read
bird.conf and interact using
There are pre-generated snapshots for many different stages of the lab.
Normally this class starts with the routers and switches completely unconfigured. You can reset to this state using the "00-base" snapshot (note that the transit and IXP routers are configured in this snapshot). The uplinks from the IXP services router (SR) are shut down, so that the IXP services subnets do not appear in the initial BGP routing table.
You can restore to any given snapshot using
Edit > Manage Snapshots in the
GNS3 client. Beware that when you restore from a snapshot it will reset
all of the devices - including the Linux servers - and you will also lose
any changes you've made to the network topology itself.
gns3man tool if you want to restore the configuration of an