I need to convert a CSS 11506 interface to a trunk. My question is do the CIRCUIT VLAN id numbers need to correlate with catalyst VLANs?
I did not use the switch VLAN numbers on the CSS. I used VLAN 1 (server side) and VLAN 2 (client side). These actually correlate on the Catalyst switch to VLAN 621 and 620 respectively. I have a pair of CSS setup for active/active using VIP and virtual-router/redundant interface failover.
The server side will now need to support a trunk. The catalyst switch server side VLANs are 621 and 622 (new).
If I must have CSS VLANs the same as catalyst then I assume I need to blow away CIRCUIT VLAN 1 configuration and create two new CIRCUIT VLANs on the CSS for 621 and 622. The relevant virtual router/interface redundancy would then be applied to these. Only after that I create a trunk interface and assign these VLAN.
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...