You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

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:

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



TNADPDKLIBPCAPNATIVEBMv2SPECTRUMNPLXDPMARVELL TERALYNX/PRESTERA

id



01

2

345678AS9516-32D

Equipment model identifier

Model

WEDGE100BF32XWEDGE100BF65XBF2556X-1TBF6064X-TINVENTEC D7064QWEDGE100BF32QSAS9516-32DNetberg Aurora 710

id

01

2

34567

Equipment instance identifier

POP

AMSFRABUDPOZMC36PARGVACHITCDPAR/DPDKRIOPRAE513-E-YECWH-1 (CERN)BUR (Wedge100BF-32QS)MIASAOVITDUBBWI

BUR0001

(Wedge100BF-32X)

BUR0002

(Wedge100BF-32X)

BUR0061

(AS9516-32D)

BNA0021

id

12

3

4567891011121314151617181920212223

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 


  • No labels