mrt.md

MRT injection

This feature requires the basic knowledge about how bgperf2 works. Please refer to this guide.

bgperf supports injecting routes to the target implementation via MRT file. With this feature, you can inject more realistic routes rather than artifitial routes which bgperf automatically generates.

To use the feature, you need to create your own scenario.yaml.

Below is an example configuration to enable MRT injection feature.

$ cat /tmp/bgperf2/scenario.yaml
<%
    import netaddr
    from itertools import islice

    it = netaddr.iter_iprange('100.0.0.0','160.0.0.0')

    def gen_paths(num):
        return list('{0}/32'.format(ip) for ip in islice(it, num))
%>
local_prefix: 10.10.0.0/24
monitor:
  as: 1001
  check-points: [1000]
  local-address: 10.10.0.2
  router-id: 10.10.0.2
target: {as: 1000, local-address: 10.10.0.1, router-id: 10.10.0.1}
testers:
- name: mrt-injector
  type: mrt
  neighbors:
    10.10.0.200:
      as: 1200
      local-address: 10.10.0.200
      router-id: 10.10.0.200
      mrt-file: /path/to/mrt/file
      only-best: true # only inject best path to the tester router (recommended to set this true)
      count: 1000 # number of routes to inject
      skip: 100 # number of routers to skip in the mrt file
- name: tester
  neighbors:
    10.10.0.10:
      as: 1010
      local-address: 10.10.0.10
      paths: ${gen_paths(100)}
      router-id: 10.10.0.10
    10.10.0.100:
      as: 1100
      local-address: 10.10.0.100
      paths: ${gen_paths(100)}
      router-id: 10.10.0.100

By adding type: mrt, tester will be run in mrt mode. The MRT injector can be GoBGP (default) or ExaBGP, depending on the value set on mrt_injector (gobgp, exabgp). The mrt-file can be set both at tester level and at neighbor level: the file provided within the neighbor configuration has priority over the one set at tester level:

As you can see, you can mix normal tester and mrt tester to create more complicated scenario.

...
- name: mrt-injector-gobgp
  type: mrt
  neighbors:
    10.10.0.200:
      as: 1200
      local-address: 10.10.0.200
      router-id: 10.10.0.200
      mrt-file: /path/to/mrt/file1
- name: mrt-injector-exabgp
  type: mrt
  mrt_injector: exabgp
  mrt-file: /path/to/mrt/file2
  neighbors:
    10.10.0.201:
      as: 1201
      local-address: 10.10.0.201
      router-id: 10.10.0.201
    10.10.0.202:
      as: 1202
      local-address: 10.10.0.202
      router-id: 10.10.0.202
      mrt-file: /path/to/mrt/file3

Here, two testers are configured:

• the first one uses GoBGP and injects routes from file1
• the second one sets up 2 neighbors: 10.10.0.201 injects routes from file2 (configured at tester level), while 10.10.0.202 injects routes from file3.

GoBGP injectors can be further configured with the following options:

• only-best: True/False, to inject only best paths
• count and skip: with this configuration, the mrt tester will inject count routes taken from the MRT file with skip offset to the target router.

ExaBGP testers accept the following options:

• high-perf: True/False, to enable ExaBGP High Performance mode.