RARE/freeRtr lab nomenclature (Status: draft work in progress)
This section depicts RARE/freeRtr lab nomenclature used in the GP4L running RARE/freeRtr routing stack.
The routing stack is composed of 3 components:
- Control Plane: freeRtr is used as control plane
- Dataplane: RARE TOFINO P4 dataplane
- Communication interface between the control plane and the dataplane
Equipment Naming convention
All equipment will have by default a naming convention rule:
- 3 letters designating equipment location
- 4 digits
- 1st digit: <reserved for future use>
- 2nd digit: dataplane type identifier
- 3rd digit: equipment model identifier
- 4th digit: number of equipment
Dataplane type identifier
Dataplane | TNA | DPDK | LIBPCAP | NATIVE | BMv2 | SPECTRUM | NPL |
---|---|---|---|---|---|---|---|
id | 0 | 1 | 2 | 3 | 4 | 5 | 6 |
Equipment model identifier
Model | WEDGE100BF32X | WEDGE100BF65X | BF2556X-1T | BF6064X-T | INVENTEC D7064Q | WEDGE100BF32QS |
---|---|---|---|---|---|---|
id | 0 | 1 | 2 | 3 | 4 | 5 |
Equipment instance identifier
POP | AMS | FRA | BUD | POZ | MC36 | PAR | GVA | CHI | TCD | PAR/DPDK | RIO | PRA | E513-E-YECWH-1 (CERN) | BUR (WEDGE1) | MIA | SAO | VIT | DUB | BWI |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
id | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 |
Network assumption
In order to simplify integration and make testing easier, RARE/freeRtr is considered as a worldwide global network domain with the following characteristics:
- Backbone is dual-stack (IPv4 / IPv6)
- Intra-routing domain has IGP set to OSPF (IPv4) and OSPFv3 (IPv6)
router-id will be 10.x.x.x. <x> is allocated based on equipment instance identifier (Cf. table above)
- Both OSPF/OSPFv3 have Segment Routing extension enabled
Node SID is allocated based on Equipment instance identifier (Cf. table above)
- Each equipment have iBGP enabled
- and will be RR client
- of BUD WEDGE100BF32X as RR
- with the following AFI/SAFI: [IPv4 IPv6] / [unicast multicast vpnuni ovpnuni vpls evpn]
- MPLS is enabled on all core facing interfaces across the entire domain
- BIER is enabled on all core facing interfaces across the entire domain
- A L3VPN any to any vrf INB_MGNT is configured in order to provide In band management from any equipment