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 | XDP | MARVELL Teralynx / Prestera | BROADCOM Trident 4 / Jericho 2 | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
id | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8AS9516-32D | 9 |
Equipment model identifier
Model | WEDGE100BF32X | WEDGE100BF65X | BF2556X-1T | BF6064X-T | INVENTEC D7064Q | WEDGE100BF32QS | AS9516-32D | Netberg Aurora 7108 | X312P-48Y-T |
|---|---|---|---|---|---|---|---|---|---|
id | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
Equipment instance identifier
- GÉANT partner
POP | AMS0001 | FRA0001 | BUD0001 | POZ0001 | GVA0001 | PAR0101 | PRA0101 |
|---|---|---|---|---|---|---|---|
id | 1 | 2 | 3 | 4 | 7 | 10 | 12 |
- RENATER partner
POP | PAR0001 |
|---|---|
id | 6 |
- HEANET partner
POP | DUB0021 |
|---|---|
id | 18 |
- Trinity College of Dublin
POP | TCD0021 |
|---|---|
id | 9 |
- CERN
POP | E513-E-YECWH-1 (CERN) |
|---|---|
id | 13 |
- Starlight
POP | CHI0041 |
|---|---|
id | 8 |
- Caltech
POP | BUR0051 | BUR0001 | BUR0002 | BUR0061 |
|---|---|---|---|---|
id | 14 | 20 | 21 | 22 |
- TENTECH University
POP | BNA0021 |
|---|---|
id | 23 |
- University of Maryland
POP | BWI0001 |
|---|---|
id | 19 |
- AMLight
POP | MIA0001 |
|---|---|
id | 15 |
- RNP partner
POP | RIO0021 |
|---|---|
id | 11 |
- REDNESP partner
POP | SAO0021 |
|---|---|
id | 16 |
- UFES partner
POP | VIT0071 |
|---|---|
id | 17 |
- KISTI partner
POP | JED0101 |
|---|---|
id | 24 |
- KAUST partner
POP | ICN0001 |
|---|---|
id | 25 |
- All partners
POP | AMS0001 | FRA0001 | BUD0001 | POZ0001 | MC36 | PAR0001 | GVA0001 | CHI0041 | TCD0021 | PAR0101 |
|---|---|---|---|---|---|---|---|---|---|---|
id | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| RIO0021 | PRA0101 | E513-E-YECWH-1 (CERN) | BUR0051 | MIA0001 | SAO0021 | VIT0071 | DUB0021 | BWI0001 | BUR0001 |
|---|---|---|---|---|---|---|---|---|---|
| 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 |
BUR0002 | BUR0061 | BNA0021 | ICN0001 | JED0101 | HND0001 | GVA0061 | GVA0062 | GVA0081 | GVA0082 |
|---|---|---|---|---|---|---|---|---|---|
| 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 |
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