Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mso_schema_site_anp_epg_bulk_staticport support for VPC behind pair of fex (DCNE-226) #313

Open
juchowan opened this issue Nov 5, 2024 · 0 comments · May be fixed by #314
Open

mso_schema_site_anp_epg_bulk_staticport support for VPC behind pair of fex (DCNE-226) #313

juchowan opened this issue Nov 5, 2024 · 0 comments · May be fixed by #314
Labels
enhancement New feature or request jira-sync Sync this issue to Jira

Comments

@juchowan
Copy link
Contributor

juchowan commented Nov 5, 2024

Community Note

  • 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:

static_ports {
    path_type            = "port"
    leaf                 = "1273"
    path                 = "eth1/4"
    vlan                 = 207
    fex                  = "110"
  }

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:

static_ports {
    deployment_immediacy = "lazy"
    fex                  = null
    leaf                 = "1273-1274/extprotpaths-111-111" 
    mode                 = "regular"
    path                 = "VPC1"
    path_type            = "vpc"
    pod                  = "pod-2"
    vlan                 = 50

New or Affected Resource(s) + MSO Class(es):

  • mso_schema_site_anp_epg_bulk_staticport

MSO version

  • V 4.2.3k

APIC version and APIC Platform for Site level Resources

  • V 5.2

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

static_ports {
    deployment_immediacy = "lazy"
    fex                  = "111-111"
    leaf                 = "1273-1274"   <----
    mode                 = "regular"
    path                 = "VPC1"
    path_type            = "vpc"
    pod                  = "pod-2"
    vlan                 = 50

References

  • #0000
@juchowan juchowan added the enhancement New feature or request label Nov 5, 2024
@akinross akinross added the jira-sync Sync this issue to Jira label Nov 5, 2024
@github-actions github-actions bot 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request jira-sync Sync this issue to Jira
Projects
None yet
2 participants