Nhgm order

[marian-pritsak]

No description provided.

[marian-pritsak]

@kperumalbfn @condition SAI_NEXT_HOP_GROUP_ATTR_TYPE == SAI_NEXT_HOP_GROUP_TYPE_ECMP cannot be added because it's not NEXT_HOP_GROUP attribute - it's NEXT_HOP_GROUP_MEMBER attribute, so we can only put that in a comment

[kperumalbfn]

We could add another next_hop_group type in sai_next_hop_group_type_t and keep these two attributes valid only for that type. Existing READ_ONLY attribute SAI_NEXT_HOP_GROUP_ATTR_NEXT_HOP_COUNT provides the actual next_hop count in a group.

[marian-pritsak]

Yes, the ECMP type is split as agreed

[abdosi]

should we add more description how priority value should be given(low to high/ high to low) and how it get mapped in order list

[marian-pritsak]

Done. High/Low definition does not really matter because within the same SAI implementation the ordering will stay the same, but the mapping description is provided

[abdosi]

@marian-pritsak : let say we pass NH1 as 1, NH2 as 10 and NH3 as 7 then SAI will order them as { NHI, NH3, NH2 } or {NH2, NH3, NH1}

basically the number we pass here will form in ascending order or descending order ? I want to clarify from that perspective.

[abdosi]

should we add min and max where min is 0 and max is SAI_NEXT_HOP_GROUP_ATTR_REAL_SIZE - 1

[marian-pritsak]

Done