Add secondary ip to floating SVI (DCNE-552)

[diyvol777]

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

the aci_l3out_floating_svi doesn't has opportunity to use secondaty IPv4 Address which we can use as GW

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

• all

APIC version and APIC Platform

• all.

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

• #0000

[akinross]

Hi @diyvol777,

Currently the naming is of the resource (which may change in the future) is not correct but you could already configure the secondary ip already via the https://registry.terraform.io/providers/CiscoDevNet/aci/latest/docs/resources/l3out_path_attachment_secondary_ip resource. See example below.

resource "aci_l3out_floating_svi" "terraform_floating_svi" {
  logical_interface_profile_dn = aci_logical_interface_profile.terraform_logical_int_profile.id
  node_dn                      = "topology/pod-1/node-101"
  encap                        = "vlan-20"
  addr                         = "10.20.30.40/16"
  if_inst_t                    = "ext-svi"
}

resource "aci_l3out_path_attachment_secondary_ip" "terraform_floating_svi_secondary_ip" {
  l3out_path_attachment_dn = aci_l3out_floating_svi.terraform_floating_svi.id
  addr                     = "10.20.30.41/16"
}

This resource manages the same class-name l3extIp, the only difference is the attribute naming of l3out_path_attachment_dn should be seen as parent_dn. This is a change we have been working on for migration of resources and new resource.

From model documentation (https://developer.cisco.com/site/apic-mim-ref-api/?version=6.1(x)) you can see that this class is actually accepted in the below mentioned DN formats:

Dn Format

1. uni/tn-{name}/out-{name}/lnodep-{name}/lifp-{name}/vlifp-[{nodeDn}]-[{encap}]/sharedipcont/addr-[{addr}]
2. uni/tn-{name}/out-{name}/lnodep-{name}/lifp-{name}/vlifp-[{nodeDn}]-[{encap}]/mem-{side}/sharedipcont/addr-[{addr}]
3. uni/tn-{name}/out-{name}/lnodep-{name}/lifp-{name}/rspathL3OutAtt-[{tDn}]/mem-{side}/sharedipcont/addr-[{addr}]
4. uni/tn-{name}/out-{name}/lnodep-{name}/lifp-{name}/rspathL3OutAtt-[{tDn}]/sharedipcont/addr-[{addr}]
5. uni/tn-{name}/out-{name}/lnodep-{name}/lifp-{name}/vlifp-[{nodeDn}]-[{encap}]/rsdynPathAtt-[{tDn}]/addr-[{addr}]
6. uni/tn-{name}/out-{name}/lnodep-{name}/lifp-{name}/vlifp-[{nodeDn}]-[{encap}]/addr-[{addr}]
7. uni/tn-{name}/out-{name}/lnodep-{name}/lifp-{name}/vlifp-[{nodeDn}]-[{encap}]/mem-{side}/addr-[{addr}]
8. uni/tn-{name}/out-{name}/lnodep-{name}/lifp-{name}/rspathL3OutAtt-[{tDn}]/mem-{side}/addr-[{addr}]
9. uni/tn-{name}/out-{name}/lnodep-{name}/lifp-{name}/rspathL3OutAtt-[{tDn}]/addr-[{addr}]

I also want to highlight another option of leveraging the aci_rest_managed resource which provides you the flexibility to configure any currently unsupported configuration.

I will add this issue to the backlog, as a migration item.