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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Currently mso_schema_site_anp_epg_bulk_staticport supports configuring path_type port behind fex:
This will create a path: "topology/pod-1/paths-1273/extpaths-1110/pathep-[eth1/4]"
In our setup we have a scenario where customer has a VPC configured behind a pair of fex switches, and it doesnt seem to be supported in the current resource.
The example path that should be generated: "topology/pod-2/protpaths-1273-1274/extprotpaths-111-111/pathep-[VPC1]"
In this case there are two fex 111 connected behind leaf switches 1273 and 1274.
If we import existing config it would result in a weird output:
github-actionsbot
changed the title
mso_schema_site_anp_epg_bulk_staticport support for VPC behind pair of fex
mso_schema_site_anp_epg_bulk_staticport support for VPC behind pair of fex (DCNE-226)
Nov 5, 2024
Community Note
Description
Currently mso_schema_site_anp_epg_bulk_staticport supports configuring path_type port behind fex:
This will create a path: "topology/pod-1/paths-1273/extpaths-1110/pathep-[eth1/4]"
In our setup we have a scenario where customer has a VPC configured behind a pair of fex switches, and it doesnt seem to be supported in the current resource.
The example path that should be generated: "topology/pod-2/protpaths-1273-1274/extprotpaths-111-111/pathep-[VPC1]"
In this case there are two fex 111 connected behind leaf switches 1273 and 1274.
If we import existing config it would result in a weird output:
New or Affected Resource(s) + MSO Class(es):
MSO version
APIC version and APIC Platform for Site level Resources
Potential Terraform Configuration
We could reuse the same mechanism as for leaf, where we either specify single fex id for port or list for vpc
References
The text was updated successfully, but these errors were encountered: