ucs vlan delete but depending objects still resist on that vlan
Hi, maybe anybody has a solution for the following issue ? My UCS setup depends on following model: - create vlans in section lan cloud - create vnic template in section policies (in this example it is one vnic template with vlans in it, also know as a trunk) - the vnic template is used within the SP vnic creation.
This is good for abstraction but I do have one extra step, when I need to delete that vlan. - delete vlan in section lan cloud - delete vlan in the vnic template in that special vnic.
If I delete the vlan int the vnic template, so the other dependent objects e.g. SP vnic gets automatically updatet.
Questions: - is there any other way to delete vlans and all depending objects for that vlan. e.g. if that vlan is used in more than one vnic template i have to find it in all the templates. - is there a way to find all debending objects e.g. vlan xy -> vnic xy -> SP xy -> SP vnic xy ... ? - maybe also via powershell commandlet ?
Best regards Alois
PS: I also found the next dependency to delete. In section VM I also have to delete the port Profile.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...