Depuis chez Telefonica, voici la route (best) BGP vers 46.227.16.0/23:
[b]46.227.16.0/23[/b] *[BGP/170] 1w0d 15:15:04, localpref 85, from 193.251.245.170
AS path: 5511 29075 43142 I, validation-state: unverified
to 213.140.52.166 via xe-3/0/2.0
to 213.140.55.54 via xe-10/0/6.0
> to 213.140.52.150 via xe-10/0/8.0
Depuis chez Ielo, on constate qu'il y a un more spécific (/24):
RP/0/RSP0/CPU0:frpar02-a9k1#show bgp ipv4 unicast 46.227.16.0
Mon Sep 21 21:47:44.882 UTC
BGP routing table entry for[b] 46.227.16.0/24[/b]
Versions:
Process bRIB/RIB SendTblVer
Speaker 361572657 361572657
Last Modified: Feb 19 08:20:14.015 for 30w4d
Paths: (8 available, best #1)
Advertised to update-groups (with more than one peer):
0.4 0.6 0.11 0.21
Advertised to peers (in unique update groups):
178.248.237.29 212.85.145.245 212.85.145.231
Path #1: Received by speaker 0
Advertised to update-groups (with more than one peer):
0.4 0.6 0.11 0.21
Advertised to peers (in unique update groups):
178.248.237.29 212.85.145.245 212.85.145.231
3215 43142
37.77.38.12 from 37.77.38.1 (37.77.38.1)
Origin IGP, metric 105, localpref 90, valid, external, best, group-best, import-candidate, import suspect
Received Path ID 0, Local Path ID 1, version 361572657
Community: 29075:8150 44530:5 44530:1250
Origin-AS validity: not-found
Path #2: Received by speaker 0
Not advertised to any peer
-> Ce qui veut dire que Adeli annonce un more specific a FT, qui le réannonce à Ielo, qui prend la route "longue" (au lieu de passer sur le lien de transit direct entre ielo et Adeli).
Donc, Telefonica "envoie" a Ielo (qui réannonce le /23 de son client), et Ielo envoie a FT via Hopus car Adeli désaggrege sur son transit FT (et doit peut être demander a FT de ne pas leaker le désaggregat à OTI)