Feature: Generation of Port-Channels following a defined pattern

[chetryan]

Enhancement summary

In large fabrics, a large number of endpoints may be dual homed to two leafs. Currently in AVD this has to be done via individual configuration for each endpoint.

Ideally we would have a way of defining ranges of interfaces on a number of switches that should be paired up in MLAG port-channels. This would only work for fabrics where a strict pattern of allocating interfaces is being followed.

Which component of AVD is impacted

eos_designs

Use case example

Refer to summary.

Describe the solution you would like

The connected endpoints configuration would support a data model that can define a range of devices and ports that can be used for multi-homing endpoints.

Describe alternatives you have considered

No response

Additional context

No response

Contributing Guide

• [X] I agree to follow this project's Code of Conduct

[ClausHolbechArista]

We already support this using the network_ports data model which supports ranges of interfaces and regex matching of switch names. If you enable port-channels under this, it will configure them as you like with one interface in each MLAG port-channel per switch.

[chetryan]

In that case, should we update the documentation here : https://avd.arista.com/devel/roles/eos_designs/doc/connected-endpoints.html#example-using-network-ports-to-configure-multiple-ports-in-the-same-port-channel as it only shows 1 port channel being created using per entry.

[ClausHolbechArista]

No that example is a "trick" to make it into a single port-channel by overriding channel_id. If you don't override it, it will do what you want.

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. The issue will be reviewed by a maintainer and may be closed