Hi, Gyan: Aijun Wang China Telecom
> On May 22, 2021, at 06:59, Gyan Mishra <hayabusa...@gmail.com> wrote: > > > Aijun > > This is a similar concept to what exists today with most vendors CLI > configured reference bandwidth that can be overridden by manual metrics link > by link to skew traffic to avoid bottle necks, but now applying that same > concept that has existed historically to Flex Algo new “bandwidth metric” > static generic metric TLV and new automatic reference bandwidth based metric. > [WAJ] Yes, I know. But the reality is that we rarely use such bandwidth based automatic metric assignments method because it can’t get the determined results as we expected. For example, if two links between the one node pair has different bandwidth, the lower bandwidth link will be not utilized at all. There may exist other issues in large complex network. The operator must take care of each possible unexpected scenario manually. > > With this algorithm change the issue that has existed with IGP ECMP parallel > links is that they are all treated as individual and so the total group > bandwidth is not taken into account. [WAJ] But in some situations, especially the high bandwidth path has multiple hops than the low bandwidth path, the operator must intervene manually to change the automatic obtained bandwidth metric to achieve the expected results, as also agree with Tony in our discussed example. Will you bother yourself for knob? > So this is a major benefit to now being incorporated into Flex Algo. Also > the concept of being able to exclude links based on minimum bandwidth is as > well a benefit so traffic is skewed to the higher bandwidth links. [WAJ] Yes, I agree with the introduction of minimum bandwidth constraints in Flex-Algorithm, but not the bandwidth metric. > > This is basically another option for operators using Flex Algo in the > operators toolbox. > > Kind Regards > > Gyan > > On Fri, May 21, 2021 at 6:40 PM Tony Li <tony...@tony.li> wrote: >> >> Hi Aijun, >> >>>>> With the introduce of additional constraint information, the problem >>>>> described in “Introduction” part(Section 1) can be solved. >>>> >>>> >>>> Please say more. Claims without rationale are not reasoning. >>> [WAJ] The introduction part talks mainly how to divert the elephant >>> traffic away from the low bandwidth link. This can be achieved via the >>> introduction of additional constraints information for Flex-ALGO >> >> >> Which is exactly what we’ve done: added bandwidth constraints. >> >> >>>>> The usage of bandwidth metric in large network is not feasible. >>>> >>> [WAJ] The main reason is that bandwidth metric is not cumulative. >> >> >> ??? What are you seeing that implies that? That is not my understanding at >> all. >> >> >>>>> And, would you like to explain more for the following statements(in >>>>> Section 4.1.1.2) >>>>> “In the interface group mode, every node MUST identify the set of >>>>> parallel links between a pair of nodes based on IGP link >>>>> advertisements and MUST consider cumulative bandwidth of the parallel >>>>> links while arriving at the metric of each link.” >>>>> based on example described in Figure 7? >>>> >>>> >>>> The paragraph immediately above explains exactly that. B->C has two >>>> parallel 10Gbps links, so it should be considered to be 20Gbps. >>>> >>>> >>>>> How the cumulative bandwidth will be used to achieve the result that >>>>> traffic from B to D will prefer B-C-F-D, not B-E-D? >>>> >>>> >>>> B-C-F-D is 20Gbps. B-E-D is 10Gbps. >>> >>> [WAJ] OK, let’s add two nodes between node B and C, say they are node M and >>> N. They have also two parallel links to B and C respectively. The two >>> possible path from B to D will be: >>> Path 1: B-M-N-C-F-D >>> Path 2: B-E-D >>> If the “reference bandwidth” is 100G, then metric for each link in >>> B-M-N-C-F-D will be 5, the cumulative metric from B-D for Path 1 >>> “B—N-C-F-D” will be 25, right? >>> The metric for each link in B-E-D will be 10, the cumulative metric from >>> B-D for Path 2 will be 20, right? >>> How can you prefer to the high bandwidth path? >> >> >> Override the metric on B-E-D to be even higher. >> >> The point of the bandwidth metric (at least in this incarnation) is not to >> make hop count irrelevant. It is to set the metrics relative to the >> bandwidth so that traffic skews towards higher bandwidths. Hops are still >> relevant. An operator can adjust the reference bandwidth and add manual >> metrics to achieve different effects, depending on their precise needs. >> >> Tony >> >> >> >> _______________________________________________ >> Lsr mailing list >> Lsr@ietf.org >> https://www.ietf.org/mailman/listinfo/lsr > -- > > > Gyan Mishra > Network Solutions Architect > Email gyan.s.mis...@verizon.com > M 301 502-1347 >
_______________________________________________ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
