You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With ECMP, typically these Bn hops will share an AS with a given CIDR prefix. Consider the following Bn hop from a trace for AS13335 (CLOUDFLARENET, US) which has CIDR prefix 141.101.71.0/24:
Today, when calculating flows, Trippy treat each Bn as independent and thus separate flows. This is problematic when there are several hops with ECMP (as is typical in large cloud and CDN providers) as the combination of possible paths becomes very large. i.e. consider a path with 5 hops, 3 of which have 10 ECMP paths (i.e. A > B(n) -> C(n) -> D(n) -> E where N is 10).
In such cases it may be useful to allow flows to be combined based on the AS CIDR prefix.
The text was updated successfully, but these errors were encountered:
With ECMP routing we get multiple paths
Consider a path from A to C via Bn:
With ECMP, typically these Bn hops will share an AS with a given CIDR prefix. Consider the following Bn hop from a trace for
AS13335
(CLOUDFLARENET, US) which has CIDR prefix141.101.71.0/24
:Today, when calculating flows, Trippy treat each Bn as independent and thus separate flows. This is problematic when there are several hops with ECMP (as is typical in large cloud and CDN providers) as the combination of possible paths becomes very large. i.e. consider a path with 5 hops, 3 of which have 10 ECMP paths (i.e.
A > B(n) -> C(n) -> D(n) -> E
where N is 10).In such cases it may be useful to allow flows to be combined based on the AS CIDR prefix.
The text was updated successfully, but these errors were encountered: